WO2008131630A1 - Procédé, dispositif, système, serveur d'application de terminal d'utilisateur pour sélectionner un service - Google Patents
Procédé, dispositif, système, serveur d'application de terminal d'utilisateur pour sélectionner un service Download PDFInfo
- Publication number
- WO2008131630A1 WO2008131630A1 PCT/CN2007/071399 CN2007071399W WO2008131630A1 WO 2008131630 A1 WO2008131630 A1 WO 2008131630A1 CN 2007071399 W CN2007071399 W CN 2007071399W WO 2008131630 A1 WO2008131630 A1 WO 2008131630A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- service
- information
- server
- meta
- meta information
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/565—Conversion or adaptation of application format or content
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
- H04L67/306—User profiles
Definitions
- the present invention relates to the field of communications technologies, and in particular, to a service selection method, apparatus, system, and client application server.
- Method 1 The operating system of most mobile terminals or desktop computers has a file management function that allows the user to set a file processing program, so that an appropriate service can be selected according to the file suffix of the hosted content. For example, the user can select a picture in the explorer and use the right mouse button to select a program to execute from a process such as picture editing, picture display or mail sending picture.
- Method 2 The user views a certain content through a browser, and the browser program calls a file processing component of the local operating system to automatically execute a service for processing the content. For example, when a user views an MP3 file through a browser, the browser program calls the file processing component of the local operating system to automatically execute the MP3 player program.
- the inventors have found through research that the above prior art solutions all rely on the local operating system and are only applicable to the case where the content processing program is located in the local operating system.
- the prior art solution cannot implement a service server that selects and processes the corresponding content from the network.
- the embodiment of the invention provides a service selection method, device, system and client application server, which can find a service server capable of processing the content according to the current content, and select an appropriate service server for processing.
- a method of business selection including:
- the service list is organized into a format that the client can identify, and is provided to the client, and the corresponding service identifier is obtained according to the confirmation information of the client;
- a service selection device includes: a service selection agent, a service selection server, a meta information registration server, and a central controller, wherein:
- the service selection agent is configured to obtain meta information according to the specified content of the client; organize the received service list into a format that the client can identify, and send the corresponding service identifier from the confirmation information of the client;
- the service identifier requests the interface and address information of the corresponding service server, and sends the obtained interface and address information of the service server to the client;
- the service selection server is configured to send the received user identifier and meta information to the meta information registration server through the central controller; request a service list based on the specified content, and send the obtained service list Selecting an agent for the business;
- the meta information registration server is configured to query a service that matches the meta information, obtain a service list that includes a service identifier, and send the service list to the service selection server by using the central controller;
- the central controller is used for control of requests from various servers and transmission of information between the various servers.
- a service selection system including: a client application server, a service selection device, and a service note
- the service selection device includes: a service selection agent, a service selection server, a meta information registration server, and a central controller, wherein:
- the service selection agent is configured to obtain meta information according to the specified content provided by the client application server; organize the received service list into a format that the client can identify, and send the corresponding service identifier to the client from the confirmation information of the client. And requesting, according to the service identifier, interface and address information of the corresponding service server, and sending interface and address information of the service server obtained from the service registration server to the client application server;
- the service selection server is configured to send the received user identifier and meta information to the meta information registration server through the central controller; request a service list based on the specified content, and send the obtained service list Selecting an agent for the business;
- the meta information registration server is configured to query a service that matches the meta information, obtain a service list that includes a service identifier, and send the service list to the service selection server by using the central controller;
- the central controller is configured to control the request of each server, and transmit information between each server and the service registration server in the service selection device.
- a client application server comprising:
- a sending unit configured to send a service selection request, a selection result, and a service request
- a receiving unit configured to receive information with a service list, and interface and address information of the service server;
- a selecting unit configured to select an appropriate service according to the information with the service list, and transmit the selection result to the sending unit;
- the request generating unit is configured to generate a service selection request according to the specified content of the user, generate a service request according to the interface and the address information of the service server, and transmit the service selection request and the service request to the sending unit.
- the embodiment of the present invention can find the corresponding meta information according to the content specified by the user, and match the service with the meta information to find a suitable service to process the content.
- the embodiment of the present invention implements a service for selecting and processing corresponding content from a network in an open network, and can select an appropriate service according to various meta information of the content and user preferences.
- DRAWINGS 1 is a schematic structural diagram of a service selection system according to an embodiment of the present invention.
- FIG. 2 is a schematic structural diagram of a service selection apparatus according to an embodiment of the present invention.
- FIG. 3 is a schematic structural diagram of a service selection apparatus according to another embodiment of the present invention.
- FIG. 4 is a schematic structural diagram of a client application server according to an embodiment of the present invention.
- FIG. 5 is a schematic flowchart of a service selection method according to an embodiment of the present invention.
- FIG. 6 is a schematic flow chart of a service selection method according to another embodiment of the present invention.
- FIG. 7 is a schematic flow chart of a service selection method according to still another embodiment of the present invention.
- FIG. 8 is a schematic structural diagram of a service selection system according to a first embodiment of the present invention.
- the service by analyzing the meta information of the content in the network, the service is matched with the meta information, so that the content service requester can find the service capable of processing the content according to the current content at any time, and request an appropriate service for processing. .
- meta information refers to any information describing the characteristics of these content, such as: category, format, author, date, field, and so on.
- the meta-information may be provided directly by the content provider, or may be extracted from the content based on features such as the labeling of the service provider and the user or a common content format.
- FIG. 1 is a schematic structural diagram of a service selection system according to an embodiment of the present invention.
- the service selection system includes: a service selection device 100, a service registration server 200, and a client application server 300.
- the service registration server 200 is connected to the service selection device 100 and the client application server 300, and is used to store information about services in the network, such as an interface, a provider, a service server address, etc., and provides registration and query functions.
- the client application server 300 can also connect various content servers, various service servers, and the like, and provide the service selection device 100 with the specified content of the user, and is also configured to receive an optional service menu sent by the service selection device 100.
- the service selection device 100 is configured to find corresponding meta information according to the content specified by the user, and match the service with the meta information to find a service list capable of processing the content, and provide the user with a user to select a suitable service from the user. .
- FIG. 2 it is a schematic structural diagram of a service selection apparatus according to an embodiment of the present invention.
- the service selection apparatus 100 includes at least: a service selection agent 110, a service selection server 120, a meta information registration server 140, and a central controller 160.
- the service selection apparatus 100 may further include: a meta information extraction server 130 and/or a service filtering server 150, according to actual conditions.
- the process of selecting a service through the service selection device 100 is as follows:
- the service selection agent 110 stores the user identifier in the service request, obtains the meta information according to the specified content of the client, and sends the user identifier and the meta information to the service selection server 120 through the central controller 160.
- the service selection server 120 identifies the user identifier and the element.
- the information is sent to the meta information registration server 140 through the central controller 160, requesting to query the service matching the meta information, obtaining the service list including the service identifier, and transmitting the service list to the service selection agent 110; the service selection agent 110
- the service list is organized into a format recognizable by the client, and is provided to the client, and the corresponding service identifier is obtained according to the confirmation information of the client; the service selection agent 110 passes the service identifier to the central controller.
- the 160 is sent to the service registration server 200, requesting interface and address information of the server providing the service, and providing the obtained information to the client.
- the service selection proxy 110 predefines a field used as a content feature for each known format, and extracts the field together with the user identifier to be sent by the central controller 160.
- the meta information extraction server 130 obtains corresponding meta information and transmits it to the service selection server 120 through the central controller 160.
- the service selection server 120 sends the obtained service list to the service filtering server 150 through the central controller 160.
- the service filtering server 150 performs a filtering operation on the service list, obtains the filtered service list, and then passes the service list.
- the central controller 160 transmits to the service selection server 120.
- FIG. 3 is a schematic structural diagram of a service selection apparatus according to another embodiment of the present invention. The various components of the service selection device are described in detail below in conjunction with FIG.
- the service selection agent 110 may include: a content analysis unit 111, an interaction confirmation unit 112, and an interface query unit 113; wherein:
- the content analysis unit 111 is responsible for collecting and analyzing the specified content. Specifically, the content analysis unit 111 obtains the specified content according to the content selection request initiated by the client, and analyzes the specified content: if the specified content includes the meta information description, the meta information is extracted, and the meta information is sent. Subsequent operations are performed on the meta-information registration server 140; otherwise, if the meta-information description is not included in the specified content, a field that can be used as a content feature is predefined for each known format, these fields are extracted, and the fields are sent to the meta
- the information extraction server 130 performs subsequent operations.
- the content analysis unit 111 may include a plurality of processing sub-units for respectively acquiring required fields as content features according to each known format, for example: the content analysis unit 111 may include three processing sub-units, respectively, from known Extracting the required fields from the syntax of Hyper Text Mark-up Language (HTML), extensible Markup Language (XML), and XHTML Embedding RDF in XHTML (RDFa)
- HTML Hyper Text Mark-up Language
- XML extensible Markup Language
- RDFa XHTML Embedding RDF in XHTML
- the interaction confirmation unit 112 is responsible for organizing the service list obtained by the service selection server 120 into a format recognizable by the client, and receiving the confirmation information of the client and obtaining the corresponding service identifier therefrom. For example, users can select and confirm services through various interaction modes such as menu selection through the client. Of course, the client can also initiate a request for re-query, for example, adding a label, changing the filtering policy, and then re-initiating the service selection request.
- the interface query unit 113 is responsible for requesting the service registration server 200 to obtain the interface and address information of the service server through the central controller 160 according to the service identifier confirmed by the client, and sending the information to the client.
- the client can initiate a business request based on this information.
- the content analysis unit 111, the interaction confirmation unit 112, and the interface query unit 113 may be in a separate server, for example, in a web server; or may be wholly or partially on the client side, for example, as a client web browser.
- Plugin for Internet Explorer, IE).
- the service selection server 120 may include at least: a selection control unit 121 and a service query interface 123, and may further include an information management unit 122 and a filter query interface 124;
- the selection control unit 121 is responsible for controlling the process of service selection, and can read the user configuration information according to the user identification, and determine whether the filtering process needs to be performed accordingly.
- the service query interface 123 is responsible for transmitting the user identification and meta information to the meta information registration server 140 under the control of the selection control unit 121, and transmitting the obtained service list including each service identification and basic description to the service selection agent 110. .
- the information management unit 122 is responsible for saving and managing the configuration information of the user for the service selection.
- the filtering query interface 124 is responsible for when the selection control unit 121 reads the information management sheet according to the user identifier.
- the configuration information saved by the element 122 determines that the user has configured the service filtering, and submits the service list to the service filtering server 150 to filter the service to obtain the filtered service list.
- the content information extraction server 130 may further include: a feature matching engine 131 and a content feature library 132, and may further include: a content labeling library 133 and an annotation statistical analysis unit 134; wherein: the content feature library 132 is responsible for saving and managing content features and The relationship of the meta-information includes querying the meta-information according to the content feature and setting the relationship between the content feature and the meta-information.
- the feature matching engine 131 is responsible for matching the relationship between the content feature and the user identity and the content feature and the meta-information stored in the content feature library 132, and transmitting the matching result to the service selection server 120 via the central controller 160.
- the content tag library 133 is responsible for saving and managing the relationship between the content features and the tag information, including querying the tag information based on the user ID and content features, and tagging the content features.
- the annotation information may be a related annotation of the content features by the user, the service provider, the content provider or other users, which may be a non-standard meta-information description.
- the annotation statistical analysis unit 134 correspondingly associates these annotations with the meta-information of the business registration by statistically multi-person annotation and language analysis, thereby establishing the relationship between the annotation information and the meta-information of the business registration.
- the meta-information of the service registration is information indicating what content the service can handle.
- the feature matching engine 131 is further responsible for querying the content tagging library 133 according to the user identifier and the content feature, obtaining relevant tagging information, and matching the tagging information with the meta-information of the service registration to obtain corresponding meta-information.
- the meta information registration server 140 may include: a service query engine 141, a service and meta information relation library 142, a service registration information base 143, and a service registration management unit 144;
- the service registration information base 143 is responsible for saving and managing the service identifier and basic description information, and providing a function for finding the basic description information of the service according to the service identifier.
- the service identifier may be a Universally Unique IDentifier (UUID) allocated in the service registration server 200, or may be a Uniform Resource Locator (URL) of the service.
- UUID Universally Unique IDentifier
- URL Uniform Resource Locator
- the service registration information base 143 may also provide a query interface to the service registration server 200, and obtain basic description information of the service by querying the service registration server 200.
- the business and meta information relationship library 142 is responsible for preserving and managing the relationship between the business and the meta information.
- the business query engine 141 is responsible for storing the meta information with the business and meta information relationship library 142. The relationship is matched, and the service that meets the matching condition of the meta information is queried according to the matching result, and the basic description information corresponding to the service is searched from the service registration information base 143, and the obtained service list including each service identifier and basic description is passed.
- the central controller 160 transmits to the service selection server 120.
- the service registration management unit 144 is responsible for providing an interface for registering service meta information, and the service server pre-registers service meta information through the interface.
- the service filtering server 150 may include at least: a filtering processing unit 151, a filtering policy library 152, a filtering policy subscription unit 153, and an external filtering interface 154;
- the filtering policy subscription unit 153 is responsible for setting the personal filtering policy of the user.
- the filtering policy may be based on the frequency of use of the individual, the popularity of the business, or the recommended business set by the business recommender trusted by the user.
- the filtering policy library 152 is responsible for saving the user's personal filtering policy.
- the filtering processing unit 151 is responsible for the control of the business filtering process.
- the user's personal filtering policy is read from the filtering policy library 152 according to the user identifier, and various information in the service list is queried according to the filtering policy, and the service list is filtered according to the query result, so as to filter out the appropriate multiple services.
- the business generate a new business list, and finally sort the information in the business list.
- the external filtering interface 154 is responsible for providing an external filtering service interface, and the service list is sent to the external filtering service through the interface, and the external filtering server filters the service list according to the filtering policy set in advance, and then returns the filtered content through the interface.
- Business list is responsible for providing an external filtering service interface, and the service list is sent to the external filtering service through the interface, and the external filtering server filters the service list according to the filtering policy set in advance, and then returns the filtered content through the interface.
- the central controller 160 is a main control unit in the service selecting device 100, and is responsible for the control of the request of each server in the service selecting device 100, and the transfer of information between the respective servers in the service selecting device 100 and the service registration server 200.
- FIG. 4 it is a schematic structural diagram of a client application server according to an embodiment of the present invention, including: a sending unit 410, a receiving unit 420, a selecting unit 430, and a request generating unit 440, where: a sending unit 410 is configured to: The service selection request provided by the request generation unit 440, the selection result provided by the selection unit 430, and the service request provided by the request generation unit 440;
- the receiving unit 420 is configured to receive information with a service list, and interface and address information of the service server;
- the selecting unit 430 is configured to select an appropriate service according to the information with the service list, and transmit the selection result to the sending unit 410; for example, the selecting unit 430 selects the dish according to the service menu.
- the request generating unit 440 is configured to generate a service selection request according to the content specified by the user, and generate a service request according to the interface and the address information of the service server, and transmit the service selection request and the service request to the sending unit 410.
- Step 501 A service selection agent saves a user identifier, and obtains meta information of a specified content; a service selection proxy saves a user identifier in a service request , where the user ID is a unique string or number representing a user.
- the service selection agent obtains the corresponding content according to the client's designation; then, according to the format of the content, reads the meta information therein, and converts it into a standard meta information description, for example, by picking up the tongue from the language.
- Gleaning Resource Descriptions from Dialects of Languages (GRDDL) converts RDFa into RDF format.
- Step 502 The service selection agent sends the meta information and the user identifier to the service selection server through the central controller.
- Step 503 The service selection server sends the obtained meta information and the user identifier to the meta information registration server through the central controller, and requests to query the service that matches the meta information;
- Step 504 The meta information registration server queries the service that matches the meta information, obtains a service list that includes the service identifier and the basic description information, and sends the service list to the service selection server through the central controller.
- Step 505 The service selection server sends the service list to the service selection agent, where the service selection agent organizes the service list into a format that the client can recognize, for example, a webpage with a script, and sends the message to the client;
- Step 506 The user selects and confirms the service in various interaction manners through the client, for example, through a menu selection manner;
- Step 507 The service selection agent obtains the corresponding service identifier according to the menu option number confirmed by the client, and then sends the information to the service registration server through the central controller, requesting the interface and address information of the server providing the service;
- Step 508 The service registration server sends the interface and address information of the server that provides the service to the service selection agent through the central controller, and then the service selection agent sends the information to the client. In this way, the client can initiate a business request based on this information.
- FIG. 6 it is a schematic flowchart of a service selection method according to another embodiment of the present invention, which includes:
- Step 601 The service selection agent saves the user identifier, and obtains meta-information of the specified content.
- the service selection proxy obtains the corresponding content according to the specification of the client. Then, the format of the content is obtained, and some fields are predefined as content features for each known format. Analyze whether the specified content contains a recognizable meta-information description, which may be a semantic description of RDFa, or a predefined format in the form of HTML or XML.
- these predefined fields representing the content characteristics are saved. For example, for webpage content, extract information such as a webpage, a webpage block corresponding to the specified content, and the like, and extract information such as a file name and a code header from a Joint Photographic Experts Group (JPG) file.
- JPG Joint Photographic Experts Group
- Step 602 The service selection agent sends the field and the user identifier to the meta information extraction server through the central controller.
- Step 603 The meta information extraction server obtains corresponding meta information according to the fields, and sends the meta information and the user identifier to the service selection server through the central controller.
- the meta information extraction server queries whether the content feature belongs to a common feature of the content format. For example, the ⁇ img src> in the content of the webpage type always indicates that the content is a certain image type; for the multimedia file format header, The file header is parsed according to the coding standard, and the corresponding meta information is obtained.
- the relationship between the generic features of these common content formats and meta-information can be pre-configured by the system administrator.
- the meta-information extraction server may further acquire the relationship between the content feature and the meta-information that the user previously configured in the content feature database according to the user identifier;
- the content characteristics of the user's personal settings obtain relevant annotations, for example, the user has marked frequently accessed books to sell a website in the book list page, has been marked with the title, author, price, publisher and other fields.
- the meta-information extraction server does not find that the user has made any annotations, it can also query whether there is a service provider, content provider or other user matching the content features, and further statistical multi-person annotation and language analysis. , get the corresponding meta information.
- Step 604 The service selection server sends the obtained meta information to the meta information through the central controller. Registering a server, requesting to query a service that matches the meta information;
- Step 605 The meta information registration server queries the service matching the meta information, obtains a service list including the service identifier and the basic description information, and sends the service list to the service selection server through the central controller.
- the meta information registration server is configured according to The meta information queries the service that meets the matching condition of the meta information.
- the meta-information registration server stores the matching relationship between the service and the meta-information. These matching relationships describe the meta-information conditions that the service can handle. For example, the content that ServiceA can process, its meta-information needs to conform to the following expression:
- metaA is the type of meta information and xx is the value of the meta information.
- the meta-information registration server can assist the query by querying the ontology library to obtain a smarter match by using its inference function; of course, it is also possible to use only expression matching.
- the relationship between the service and the meta-information includes: a relationship between a specific service and meta-information configured in the service selection device, where the specific service may be a common service or a contracted service; the service and the meta-information registered by the service provider to the service selection device Relationship; and the relationship between the personal business and the meta information registered by the user to the service selection device.
- the user can specify that the nature of the personal designated relationship is public or private, and the meta information registration server can perform statistical analysis on the disclosed personal designated relationship to obtain a universal matching relationship of different credibility; the user can also be private. Personally specified relationships to get personalized business lookups.
- the meta information registration server queries the basic description information and the identifier of the qualified service according to the matching result to form a service list.
- the meta information registration server stores basic description information of the service and an identifier assigned by the service in the service registration server.
- the service may also register the basic description information and the identifier to the meta information registration server when registering the related meta information.
- the meta information registration server may obtain the service basic description information from the service registration server according to the identifier. Based on these meta-information, the meta-information registration server queries the content characteristics that a certain service can handle.
- Step 606 The service selection agent organizes the service list sent by the service selection server into a client. a recognizable format, for example, a web page with a script, sent to the client;
- Step 607 The user selects and confirms the service through various manners through the client, for example, by selecting a menu;
- Step 608 The service selection agent obtains the corresponding service identifier according to the menu option number confirmed by the client, and then sends the service identifier to the service registration server through the central controller, requesting the interface and address information of the server capable of providing the service;
- Step 609 The service registration server sends the interface and address information of the server that provides the service to the service selection agent through the central controller, and then the service selection agent sends the information to the client, so that the client can initiate the information according to the information. Business request.
- FIG. 7 is a schematic flowchart diagram of a service selection method according to still another embodiment of the present invention, including:
- Steps 701 to 705 are the same as steps 601 to 605 in the above embodiment, and are not described herein again.
- Step 706 The service selection server reads the user configuration information according to the user identifier. The user needs to send the obtained service list to the service filtering server through the central controller.
- Step 707 The service filtering server performs a filtering operation on the received service list, obtains the filtered service list, and sends the new service list to the service selection server through the central controller.
- the service filtering server reads the personal filtering policy according to the user identifier. .
- the user can set a personalized service filtering policy in the service filtering server in advance, for example: according to the frequency of personal use, the popularity of the service, a certain service filtering policy provided by the service selection device, or a combination of these conditions.
- the service filtering policy may also be that the user selects a career, a hobby, a city, and the like, and the service filtering server obtains the type of each service by counting and analyzing the service description, so that a more suitable service filtering policy can be customized for the user.
- the service filtering server queries the personal usage frequency of each service in the input service list, the popularity of the service, and the category of the service according to the user's personal filtering policy; and then filters and sorts the service list according to the query result.
- Step 708 The service selection agent organizes the filtered service list sent by the service selection server into a format that the client can recognize, and sends the format to the client.
- Step 709 to step 711 are the same as step 607 to step 609 in the foregoing embodiment, and details are not described herein again. It should be noted that those skilled in the art can understand that all or part of the steps of implementing the foregoing embodiments may be implemented by hardware related to program instructions, and the program may be stored in a computer readable storage medium.
- the storage medium is, for example, a ROM/RAM, a magnetic disk, an optical disk, or the like.
- FIG. 8 is a schematic structural diagram of a service selection system according to a first embodiment of the present invention.
- the business selection system includes: a service selection device 100, a service registration server 200, a client application server 300, and other various content servers 400 and various service servers 500 connected.
- a service related to the song provided in the network may be selected for a certain specific song. For example: Set as ringtone, set as ring tones, recommend to friends, view lyrics, view related Music TV Video (MTV), etc.
- MTV Music TV Video
- the user identification may be an identifier assigned by the information management unit in the service selection server, and may also use an existing identification, such as a personal mobile phone number.
- the service selection agent obtains the user ID.
- a user reads a webpage containing music content through the client, he or she wants to perform some processing on the favorite music that the website cannot provide. Then, the business selection agent obtains the corresponding content according to the specified operation of the user. If the content of the music is described in the RDFa format, the relevant meta information is as follows:
- Href "http: ⁇ creativecommom. org/licenses/by-nc/2.5/">
- the business selection agent is analyzed to obtain meta-information such as the name, format, author, singer, and authority of the music content. It should be noted that the specific method for describing the meta information is not limited in the embodiment of the present invention. In addition to the RDFa format description, the meta information may be described in other manners.
- Http ⁇ creativecommom. org/licenses/by-nc/2.5 /Non-Commercial
- the service selection agent sends the webpage url: http:// musicsite.example.com, the information fragment described by the above HTML, and the user identifier to the meta information extraction server.
- This step is an optional step that is performed only if the web page does not directly contain meta information.
- the meta information extraction server extracts meta information according to the content features and user identifiers sent by the service selection agent.
- the meta information extraction server queries whether the content feature belongs to a general feature.
- the format of the content belongs to MP3. The meta information is described as follows:
- the meta information extraction server acquires the relationship between the content feature and the meta information that the user has previously configured in the content feature database according to the user identifier. If it is not found that the user has previously marked any page of the website http:// musicsite.example.com, then the meta-information extraction server queries whether the service provider, content provider or other user labels the content features. Match it. It is assumed that the music website itself or the content provider in the embodiment of the present invention has already marked the meta information corresponding to the page structure of the HTML description music, and saves it in the meta information extraction server, so that the meta information extraction server can thereby obtain the content.
- musicsitetag song name ff exampleMusic ff A XMLLiteral
- the meta-information extraction server uses the standard dictionary to obtain the standard description of the meta-information as follows:
- the meta information extraction server obtains the meta information according to the website information as follows:
- the meta information extraction server transmits the meta information obtained in the above step to the service selection server through the central controller.
- the service selection server queries the meta-information server through the central controller to query the meta-information registration server for the service matching the meta-information.
- the meta-information registration server stores the matching relationship between the service and the meta-information.
- the following uses the CRBT service as an example to illustrate the preservation of this relationship:
- the service provider registers the sound files such as MP3 ⁇ WMA ⁇ RM that the business server can handle as http://services, telcom.com/auodiforma.
- the meta-information registration server queries the ⁇ 3 music file 23457 that can be transmitted over the network according to the meta-information obtained in the previous step, and fully complies with the condition of the CRBT service.
- the meta-information registration server continues to query the ring-tone service.
- the basic description of the service is shown in Table 1, and the basic information of the CRBT service is added to the service list. Table 1
- the service filtering step is an optional step.
- the service selection server reads the user configuration according to the user identifier, and the user configures the service filtering, the service selection server sends the service list obtained in the previous step to the service filtering server through the central controller to perform the service. Filter; otherwise you do not need to perform this step.
- the business filtering server reads the personal filtering policy based on the user ID. It is assumed that the user sets a personalized service filtering policy in the service filtering server to filter according to the recent usage frequency of the individual and the popularity of the service, and the service filtering server respectively reads the user usage statistical record of each service in the foregoing service list and is Confirm the statistical records to find the best top 5 businesses.
- the search results are as follows: View lyrics, ring tones subscriptions, download ringtones, and find related songs provided by Company A are services that users often use or popular, while forwarding recommendations, B companies provide related songs and other services are less use. Then, the service filtering server filters and sorts the service list according to the query result, and generates a new service list as shown in Table 3:
- the service selection agent organizes the filtered business list into a scripted web page and sends it to the client.
- the user selects and confirms the service by means of menu selection by the client.
- the service selection agent When the user confirms the ring back tone subscription service at the client, the service selection agent sends the confirmation result to the service selection server.
- the service selection server queries the service registration server to provide the interface and address information of the server of the CRBT service according to the service identifier http: ⁇ www. comtel.com/corhrring/, and then sends the information to the server. To the client. In this way, the client can initiate a business request based on this information.
- the service selection server may send the confirmation statistics to the service filtering server, so that the service filtering server modifies the statistics of the CRBT service.
- users can directly compare the other merchant's merchandise, view the comment, save the information to their profile, or click the dialing method to consult the merchant.
- the merchant's website can provide all of the above services, in many scenarios it may be more appropriate to use a business selection device. For example, users have their own favorite and trusted products to compare business, comment business, and hope to use these services directly; users may have their own product database, and do not want to be restricted by the shopping cart of an e-commerce website; or business website
- the click-to-dial service is not supported, but only the consultation phone number and so on.
- the meta-information feature of the commodity comparison service registered in the service registration server including the commodity index category in the product index link of the above-mentioned website, is displayed in the product information link segment of the above-mentioned website. Book product information.
- the service registration server indexes the product comparison service into the commodity class meta information, and registers the marked web page features to the meta information extraction server.
- the network dial-up service will mark the hotline information category in the contact information network http://books.com and ampk.com/info.htm as the telephone number.
- the user has already associated the user identification with his or her mobile phone number in the network dial-up service.
- the service setting policy of the commodity class is set in the service filtering server by the service selection agent, for example, the product comparison service A and the comment service B.
- the service filtering policy of the phone number is set to provide the network dialing service provided by the operator of the mobile phone.
- the service selection agent is requested to perform business selection.
- the business selection agent acts as a plug-in for the browser, and the user can select the link of the product information by using the mouse.
- the service selection agent first analyzes the relevant meta information: the web page URL and the location of the product link in the web page, and the link string itself are sent as content features to the meta information extraction server; the meta information extraction server returns the meta information of the content type of the book product.
- the business selection agent will link the above product information, the book product information content class, and the meta information.
- the service identifier is sent to the service selection server; the service selection server requests the meta information registration server to obtain the related service list of the data commodity information content class, and filters the service list according to the user identifier through the service filtering server; the service filtering server returns the commodity comparison service A. Commenting the business list of the business B to the business selection agent; the business selection agent organizes it into a webpage with a script and sends it to the client.
- the service selection agent configures the request configuration interface according to the request parameter of the service registration, allows the user to select the request parameter, and returns the request message to the client.
- the request parameter can be the item comparison business A; options that may include comparison: compare similar products of similar prices, compare the same brand goods, limit comparison areas, and so on.
- the client sends a request for the commodity comparison service A.
- the commodity comparison service A takes over the subsequent process and directly compares the products.
- the service selection agent When the user desires to contact the merchant by telephone, the service selection agent is requested to perform business selection.
- the service selection agent first analyzes the relevant meta information and analyzes the type of the content as a phone number.
- the service selection agent sends the phone number string, the content type of the phone number, and the user ID to the service selection server.
- the service selection server requests the meta-information registration server to obtain the service list of the phone number class, and filters the service list according to the user ID through the service filtering server, and returns the network dial-up service provided by the operator of the user's mobile phone to the service selection agent.
- the service selection server uses the proxy mode and the proxy client sends a network dialing request to the network dialup service
- the parameters include the subscriber identity and the merchant's hotline number.
- the network dial-up service establishes a call between the user's mobile phone and the merchant's hotline.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
Description
业务选择方法、 装置、 *** ¾^户端应用服务器
本申请要求于 2007 年 4 月 28 日提交中国专利局、 申请号为 200710097238.0、 发明名称为"业务选择方法、 装置、 ***及客户端应用服务 器"的中国专利申请的优先权, 其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术领域, 特别涉及业务选择方法、 装置、 ***及客户端 应用服务器。
背景技术
在开放的网络中存在大量的内容, 例如: 音乐、 视频、 图片、 地址信息、 各种表格、 商品信息、 文字描述、 地理位置等; 同时, 网络中还存在大量能够 处理这些内容的业务, 例如: 铃音设置、 彩铃设置、 图片发送、 视频共享、 位 置标识、 商品查询、 日程表设置等。 网络中存在的内容和业务通常是由不同的 主体开发和发布的, 并且能够动态的添加、 更改和 4敦销。
目前, 在互联网或电信网中, 用户选择业务以处理相关内容的方式通常有 两种: 一种是用户先选择并执行能够处理某种内容的业务, 然后根据该业务的 程序逻辑, 选择该种内容; 另一种是用户先看到某种内容或其标识, 然后找到 合适的业务对该种内容进行处理。对于后一种情况,现有技术中可以通过如下 方式实现:
方式一: 大多数移动终端或桌面计算机的操作***具有文件管理功能, 允 许用户设置文件处理程序,从而可以根据承载内容的文件后缀选择适当的业务 进行处理。 例如, 用户可以在资源管理器中选择一个图片, 并用鼠标右键从图 片编辑、 图片显示或邮件发送图片等处理程序中选择一个程序执行。
方式二: 用户通过浏览器查看某种内容, 浏览器程序调用本地操作***的 文件处理组件, 自动执行处理该种内容的业务。 例如, 当用户通过浏览器查看 一个 MP3文件时, 浏览器程序调用本地操作***的文件处理组件, 自动的执 行 MP3播放器程序。
在实现本发明的过程中,发明人经过研究发现: 上述现有技术方案均依赖 本地操作***, 只适用于内容处理程序位于本地操作***的情况。 然而, 随着 软件服务化的发展, 越来越多的内容处理服务由开放网络中的业务服务器提
供,对于这种情况, 现有技术方案无法实现从网络上选择处理相应内容的业务 服务器。
发明内容
本发明实施例提供一种业务选择方法、 装置、 ***及客户端应用服务器, 能够根据当前内容找到能够处理这些内容的业务服务器,并从中选择合适的业 务服务器进行处理。
本发明实施例的技术方案包括:
一种业务选择方法, 包括:
根据客户端的指定内容获得元信息;
请求查询与所述元信息匹配的业务, 获得包含所述业务标识的业务列表; 将所述业务列表组织成客户端可以识别的格式提供给客户端,根据客户端 的确认信息得到对应的业务标识;
请求与所述业务标识对应的业务服务器的接口和地址信息 ,将获得的信息 提供给客户端。
一种业务选择装置, 包括: 业务选择代理、 业务选择服务器、 元信息注册 服务器、 以及中央控制器, 其中:
所述业务选择代理, 用于根据客户端的指定内容获得元信息; 将收到的业 务列表组织成客户端可以识别的格式发送给客户端,并从客户端的确认信息获 得对应的业务标识; 根据所述业务标识请求相应业务服务器的接口和地址信 息, 以及将获得的业务服务器的接口和地址信息发送给客户端;
所述业务选择服务器,用于将接收到的所述用户标识和元信息通过所述中 央控制器发送给所述元信息注册服务器;请求基于所述指定内容的业务列表以 及将获得的业务列表发送给所述业务选择代理;
所述元信息注册服务器, 用于查询与所述元信息匹配的业务, 获得包含业 务标识的业务列表,并将所述业务列表通过所述中央控制器发送给所述业务选 择服务器;
所述中央控制器, 用于对各个服务器请求的控制, 以及各个服务器之间信 息的传送。
一种业务选择***, 包括: 客户端应用服务器、 业务选择装置、 及业务注
册服务器; 所述业务选择装置包括: 业务选择代理、 业务选择服务器、 元信息 注册服务器、 以及中央控制器, 其中:
所述业务选择代理,用于根据客户端应用服务器提供的指定内容获得元信 息; 将收到的业务列表组织成客户端可以识别的格式发送给客户端,从客户端 的确认信息获得对应的业务标识;根据所述业务标识请求相应业务服务器的接 口和地址信息,以及将从所述业务注册服务器获得的业务服务器的接口和地址 信息发送给客户端应用服务器;
所述业务选择服务器,用于将接收到的所述用户标识和元信息通过所述中 央控制器发送给所述元信息注册服务器;请求基于所述指定内容的业务列表以 及将获得的业务列表发送给所述业务选择代理;
所述元信息注册服务器, 用于查询与所述元信息匹配的业务, 获得包含业 务标识的业务列表,并将所述业务列表通过所述中央控制器发送给所述业务选 择服务器;
所述中央控制器, 用于对各个服务器请求的控制, 以及所述业务选择装置 中各个服务器与业务注册服务器之间信息的传送。
一种客户端应用服务器, 其特征在于, 包括:
发送单元, 用于发送业务选择请求, 选择结果, 及业务请求;
接收单元, 用于接收带有业务列表的信息,及业务服务器的接口和地址信 息;
选择单元, 用于根据所述带有业务列表的信息选择合适的业务, 并将选择 结果传送到所述的发送单元;
请求生成单元, 用于根据用户的指定内容生成业务选择请求,及根据所述 业务服务器的接口和地址信息生成业务请求, 并将所述业务选择请求、业务请 求传送到所述的发送单元。
本发明实施例能够才艮据用户指定的内容找出相应的元信息,通过将业务与 元信息进行匹配,从而找到合适的业务来处理这些内容。 本发明实施例在开放 网络中实现了从网络上选择处理相应内容的业务,并且能够根据内容的各种元 信息和用户的喜好选择合适的业务。
附图说明
图 1是根据本发明实施例的业务选择***的结构示意图;
图 2是根据本发明一实施例的业务选择装置的结构示意图;
图 3是根据本发明另一实施例的业务选择装置的结构示意图;
图 4是根据本发明实施例的客户端应用服务器的结构示意图;
图 5是根据本发明一实施例的业务选择方法的流程示意图;
图 6是根据本发明另一实施例的业务选择方法的流程示意图;
图 7是根据本发明又一实施例的业务选择方法的流程示意图;
图 8是本发明具体实施例一的业务选择***的结构示意图。
具体实施方式
下面结合附图对本发明实施例作进一步说明。
在本发明实施例中,通过分析网络中内容的元信息,将业务与元信息进行 匹配,使得内容服务请求者可以随时根据当前内容,找到能够处理这些内容的 业务, 并请求合适的业务进行处理。
其中,元信息是指任何描述这些内容特征的信息,例如: 所属类别、格式、 作者、 日期、 领域等。 元信息可以由内容提供者直接提供, 也可以根据业务提 供者和用户的标注或通用的内容格式等特征从内容中提取。
下面, 具体说明本发明技术方案是如何实现的。
为了在网络上实现对业务的选择, 在网络中提供业务选择***。 如图 1所 示,是根据本发明实施例的业务选择***的结构示意图。该业务选择***包括: 业务选择装置 100、 业务注册服务器 200、 客户端应用服务器 300。 其中, 业务 注册服务器 200分别与业务选择装置 100及客户端应用服务器 300相连, 用于保 存网络中业务的信息, 例如接口、 提供者、 业务服务器地址等, 并提供注册和 查询功能。 客户端应用服务器 300还可以连接各种内容服务器、 各种业务服务 器等, 用于向业务选择装置 100提供用户的指定内容, 还用于接收业务选择装 置 100发来的可供选择的业务菜单, 并将用户的确认信息反馈给业务选择装置 100;以及接收业务选择装置 100依照该确认信息获得的业务服务器的接口和地 址信息, 并根据这些信息发起业务请求。 业务选择装置 100 , 用于根据用户指 定的内容找出相应的元信息,通过将业务与元信息进行匹配,找到能够处理这 些内容的业务列表, 并提供给用户以便用户可以从中选择出合适的业务。
如图 2所示, 是根据本发明实施例的业务选择装置的结构示意图。 该业务 选择装置 100至少包括: 业务选择代理 110、 业务选择服务器 120、 元信息注册 服务器 140和中央控制器 160。 此外, 根据实际情况, 该业务选择装置 100还可 以进一步包括: 元信息提取服务器 130和 /或业务过滤服务器 150。
通过业务选择装置 100实现业务选择的过程如下:
业务选择代理 110保存业务请求中的用户标识,根据客户端的指定内容获 得元信息,通过中央控制器 160将该用户标识和元信息发送给业务选择服务器 120; 业务选择服务器 120将该用户标识和元信息通过中央控制器 160发送给 元信息注册服务器 140, 请求查询与所述元信息匹配的业务, 获得包含该业务 标识的业务列表,并将该业务列表发送给业务选择代理 110;业务选择代理 110 将该业务列表组织成客户端可以识别的格式提供给客户端,并根据客户端的确 认信息得到对应的业务标识;业务选择代理 110将该业务标识通过中央控制器
160发送给业务注册服务器 200, 请求提供业务的服务器的接口和地址信息, 并将获得的信息提供给客户端。
需要说明的是, 当所述指定内容不包含元信息描述时, 业务选择代理 110 对每种已知格式,预定义用作内容特征的字段,提取该字段连同用户标识通过 中央控制器 160发送给元信息提取服务器 130, 以获得对应的元信息, 再通过 中央控制器 160发送给业务选择服务器 120。
当用户已经配置业务过滤时,业务选择服务器 120将获得的业务列表通过 中央控制器 160发送给业务过滤服务器 150; 由业务过滤服务器 150对业务列 表进行过滤操作, 获得过滤后的业务列表,再通过中央控制器 160发送给业务 选择服务器 120。
如图 3所示, 是根据本发明另一实施例的业务选择装置的结构示意图。 下 面结合图 3对业务选择装置中的各个组成部分进行详细介绍。
1、 业务选择代理 110可以包括: 内容分析单元 111、 交互确认单元 112、 接 口查询单元 113; 其中:
内容分析单元 111负责对指定内容进行釆集和分析。 具体而言, 内容分析 单元 111根据客户端发起的内容选择请求, 获得指定内容, 并对指定内容进行 分析: 如果指定内容中包含元信息描述, 则提取这些元信息, 并将元信息发送
给元信息注册服务器 140进行后续操作; 否则, 如果指定内容中不包含元信息 描述,则对每种已知格式,预定义有可以作为内容特征的字段,提取这些字段, 并将字段发送给元信息提取服务器 130进行后续操作。 当然, 内容分析单元 111 可以包括多种处理子单元,分别用于根据每种已知格式获取需要的字段作为内 容特征, 例如: 内容分析单元 111可以包含三种处理子单元, 分别从已知的超 文本链接标记语言 (Hyper Text Mark-up Language, HTML ) 、 可扩展标记语 言 (extensible Markup Language, XML), 及 XHTML嵌入 RDF ( Embedding RDF in XHTML, RDFa ) 的语法格式中提取需要的字段, 从而构成资源描述框架 ( Resource Description Framework, RDF)的内容特征。
交互确认单元 112负责将业务选择服务器 120获得的业务列表组织成客户 端可以识别的格式发送给客户端,以及接收客户端的确认信息并从中获得对应 的业务标识。例如, 用户可以通过客户端以菜单选择等各种交互方式选取和确 认业务。 当然, 客户端也可以发起再查询的请求, 例如, 新增标注、 更改过滤 策略后重新发起业务选择请求。
接口查询单元 113负责根据客户端确认的业务标识, 通过中央控制器 160 向业务注册服务器 200请求获得业务服务器的接口和地址信息, 并将该信息发 送给客户端。 客户端可以根据这些信息发起业务请求。
需要说明的是, 内容分析单元 111、 交互确认单元 112、 接口查询单元 113 可以在单独的服务器中, 例如位于网页服务器中; 也可以全部或部分在客户端 侧, 例如, 作为客户端网络浏览器(Internet Explorer, IE ) 的插件。
2、 业务选择服务器 120至少可以包括: 选择控制单元 121、 业务查询接口 123 , 还可以进一步包括信息管理单元 122、 过滤查询接口 124; 其中:
选择控制单元 121负责控制业务选择的过程, 可以根据用户标识读取用户 配置信息, 并据此确定是否需要进行过滤处理。
业务查询接口 123负责在所述选择控制单元 121的控制下,向元信息注册服 务器 140发送用户标识和元信息, 以及将获得的包含每个业务标识和基本描述 的业务列表发送给业务选择代理 110。
信息管理单元 122负责保存和管理用户对业务选择的配置信息。
过滤查询接口 124负责当选择控制单元 121根据用户标识读取信息管理单
元 122保存的配置信息, 确定该用户已经配置业务过滤时, 将业务列表提交给 业务过滤服务器 150, 以对业务进行过滤, 从而获得经过过滤的业务列表。
3、 元信息提取服务器 130至少可以包括: 特征匹配引擎 131和内容特征库 132, 也可以进一步包括: 内容标注库 133及标注统计分析单元 134; 其中: 内容特征库 132负责保存和管理内容特征与元信息的关系, 包括根据内容 特征查询元信息和对内容特征与元信息关系的设置。
特征匹配引擎 131负责根据内容特征和用户标识与内容特征库 132中保存 的内容特征与元信息的关系进行匹配, 并通过中央控制器 160将匹配结果发送 给业务选择服务器 120。
内容标注库 133负责保存和管理内容特征与标注信息的关系, 包括根据用 户标识和内容特征查询标注信息, 以及对内容特征进行标注。该标注信息可以 是用户、 业务提供者、 内容提供者或其他用户对内容特征的相关标注, 其可能 是非标准的元信息描述。
标注统计分析单元 134通过统计多人的标注和语言分析的方式, 将这些标 注与业务注册的元信息相对应, 从而建立标注信息和业务注册的元信息的关 系。 该业务注册的元信息是表明该业务能够处理哪些内容的信息。
相应的, 特征匹配引擎 131还负责根据用户标识和内容特征, 查询内容标 注库 133 , 获取相关标注信息, 以及将该标注信息与业务注册的元信息相匹配, 获取相应的元信息。
4、 元信息注册服务器 140可以包括: 业务查询引擎 141、 业务与元信息关 系库 142、 业务注册信息库 143、 业务注册管理单元 144; 其中:
业务注册信息库 143负责保存和管理业务标识和基本描述信息, 提供根据 业务标识查找业务基本描述信息的功能。其中, 业务标识可以是在业务注册服 务器 200中分配的全球唯一标示符(Universally Unique IDentifier, UUID ) , 也 可以是业务的统一资源定位符 (Uniform Resource Locator, URL)。 当然, 业务 注册信息库 143也可以只是提供对业务注册服务器 200的查询接口,通过查询业 务注册服务器 200获得业务的基本描述信息。
业务与元信息关系库 142负责保存和管理业务与元信息的关系。
业务查询引擎 141负责将元信息与所述业务与元信息关系库 142中保存的
关系进行匹配, 并根据匹配结果查询符合元信息匹配条件的业务,从业务注册 信息库 143中查找与该业务对应的基本描述信息, 并将获得的包含每个业务标 识和基本描述的业务列表通过中央控制器 160发送给业务选择服务器 120。
业务注册管理单元 144负责提供业务元信息注册的接口, 业务服务器通过 该接口预先注册业务元信息。
5、业务过滤服务器 150至少可以包括:过滤处理单元 151、过滤策略库 152、 过滤策略订阅单元 153; 还可以包括: 外部过滤接口 154; 其中:
过滤策略订阅单元 153负责设置用户个人的过滤策略。 例如, 该过滤策略 可以根据个人的使用频度、业务的热门程度或用户信任的业务推荐者设置的推 荐业务等。
过滤策略库 152负责保存用户个人的过滤策略。
过滤处理单元 151负责业务过滤过程的控制。 根据用户标识从过滤策略库 152中读取用户个人的过滤策略,按照该过滤策略查询业务列表中的各种信息, 依照查询结果对业务列表进行过滤,从而从多个可能的业务中过滤出合适的业 务, 生成新的业务列表, 最后对业务列表中的信息进行排序。
外部过滤接口 154负责提供外部过滤服务的接口, 通过该接口将业务列表 发送给外部过滤服务, 由外部过滤服务器根据事先设置的过滤策略,对业务列 表进行过滤处理, 再通过该接口返回过滤后的业务列表。
6、 中央控制器 160是业务选择装置 100中的主控单元, 负责对业务选择装 置 100中各个服务器请求的控制,以及业务选择装置 100中各个服务器与业务注 册服务器 200之间信息的传送。
如图 4所示, 是根据本发明一实施例的客户端应用服务器的结构示意图, 包括: 发送单元 410、接收单元 420、选择单元 430、及请求生成单元 440, 其中: 发送单元 410 , 用于发送请求生成单元 440提供的业务选择请求, 选择单 元 430提供的选择结果, 以及请求生成单元 440提供的业务请求;
接收单元 420 , 用于接收带有业务列表的信息, 及业务服务器的接口和地 址信息;
选择单元 430 , 用于根据该带有业务列表的信息选择合适的业务, 并将选 择结果传送到所述的发送单元 410; 例如, 选择单元 430根据业务菜单选择菜
单选项编号;
请求生成单元 440, 用于根据用户指定内容生成业务选择请求, 及根据所 述业务服务器的接口和地址信息生成业务请求, 并将该业务选择请求、业务请 求传送到所述的发送单元 410。
如图 5所示,是根据本发明一实施例的业务选择方法的流程示意图, 包括: 步骤 501、 业务选择代理保存用户标识, 获得指定内容的元信息; 业务选择代理保存业务请求中的用户标识, 其中, 用户标识为代表一个用 户的唯一的一个字符串或数字。
业务选择代理根据客户端的指定, 获取相应内容; 然后, 按照这类内容的 格式, 读取其中的元信息, 并将其转换为标准的元信息描述, 例如, 通过来自 语言的方言的拾落穗资源描述 ( Gleaning Resource Descriptions from Dialects of Languages, GRDDL )将 RDFa转变为 RDF格式。
步骤 502、 业务选择代理将该元信息和用户标识通过中央控制器发送给业 务选择服务器;
步骤 503、 业务选择服务器将获得的元信息和用户标识通过中央控制器发 送给元信息注册服务器, 请求查询与该元信息匹配的业务;
步骤 504、 元信息注册服务器查询与这些元信息匹配的业务, 获得包含业 务标识和基本描述信息的业务列表, 并通过中央控制器发送给业务选择服务 器;
步骤 505、 业务选择服务器将该业务列表发送给业务选择代理, 由业务选 择代理将该业务列表组织成客户端可以识别的格式, 例如, 带有脚本的网页, 发送给客户端;
步骤 506、 用户通过客户端以各种交互方式选取、 确认业务, 例如通过菜 单选择的方式;
步骤 507、 业务选择代理根据客户端确认的菜单选项编号获得对应的业务 标识,再通过中央控制器发送给业务注册服务器,请求提供该业务的服务器的 接口和地址信息;
步骤 508、 业务注册服务器将提供该业务的服务器的接口和地址信息通过 中央控制器发送给业务选择代理, 再由业务选择代理将该信息发送给客户端,
这样, 客户端就可以根据这些信息发起业务请求。
如图 6所示, 是根据本发明另一实施例的业务选择方法的流程示意图, 包 括:
步骤 601、 业务选择代理保存用户标识, 获得指定内容的元信息; 业务选择代理根据客户端的指定,获取相应内容;然后,获取内容的格式, 对每种已知格式,预定义一些字段作为内容特征, 分析指定内容中是否包含可 识别的元信息描述, 可以是 RDFa的语义描述, 也可以是 HTML或 XML形式预 定义的格式。
如果指定内容不包含元信息描述,则保存这些预定义的代表内容特征的字 段。 例如, 对网页内容, 提取其网址、 指定内容对应的网页块等信息; 对联合 照片专家组 ( Joint Photographic experts Group, JPG )文件提取文件名、 编码 头等信息。
步骤 602、 业务选择代理将这些字段和用户标识通过中央控制器发送给元 信息提取服务器;
步骤 603、 元信息提取服务器根据这些字段获得相应的元信息, 并将该元 信息和用户标识通过中央控制器发送给业务选择服务器;
具体而言,元信息提取服务器查询内容特征是否属于该种内容格式的通用 特征, 例如, 网页类型的内容中 <img src>总是表示该内容是某种图片类型; 对 多媒体文件格式头, 可以根据编码标准解析文件头, 获得相应的元信息。 这些 常见内容格式的通用特征与元信息的关系可以是***管理员事先配置。
但是,通过通用特征的方式提取元信息毕竟数量相对较少,元信息提取服 务器还可以进一步根据用户标识,获取用户事先配置在内容特征库的内容特征 与元信息的关系; 查询该内容特征所匹配的用户个人设置的内容特征, 获取相 关标注, 例如, 用户曾经标注经常访问的书籍销售某网站的书籍列表页面中, 已经标注出书名, 作者、 价格、 出版社等字段。 如果元信息提取服务器没有发 现用户进行过任何标注, 则还可以查询是否有业务提供者、 内容提供者或其他 用户对内容特征的标注与之相匹配,进一步通过统计多人标注和语言分析的方 式, 获得相应的元信息。
步骤 604、 业务选择服务器将获得的元信息通过中央控制器发送给元信息
注册服务器, 请求查询与该元信息匹配的业务;
步骤 605、 元信息注册服务器查询与该元信息匹配的业务, 获得包含业务 标识和基本描述信息的业务列表, 并通过中央控制器发送给业务选择服务器; 具体而言, 首先,元信息注册服务器根据元信息查询符合该元信息匹配条 件的业务。元信息注册服务器保存有业务与元信息的匹配关系, 这些匹配关系 描述了业务所能处理的元信息条件, 例如, ServiceA能够处理的内容, 其元信 息需要符合以下表达式:
( ( metaA =xx ) or ( metaD > =xx ) ) and ( metaB include xx ) and ( metaC include String (xx ) )
其中, metaA为元信息的类型, xx为元信息的值。 匹配过程中, 元信息注 册服务器可以通过查询本体库的方法辅助查询 ,以利用其推理功能获得更智能 的匹配; 当然, 也可以仅釆用表达式匹配。
这些业务与元信息的关系包括:配置在业务选择装置内的特定业务与元信 息的关系, 所述特定业务可以是常见业务或签约业务; 业务提供者向业务选择 装置注册的本业务与元信息的关系;以及用户向业务选择装置注册的个人常用 业务与元信息的关系。
需要说明的是, 用户可以指定这些个人指定关系的性质属于公开或私有, 元信息注册服务器可以对公开的个人指定关系进行统计分析,以获取不同可信 度的通用匹配关系;用户也可以根据私有的个人指定关系获取个性化的业务查 找。
然后,元信息注册服务器根据匹配结果查询符合条件的业务的基本描述信 息和标识, 构成业务列表。
元信息注册服务器保存有业务的基本描述信息和业务在业务注册服务器 中分配的标识。 业务在注册相关元信息时,也可以将基本描述信息和标识注册 到元信息注册服务器。在具体实现中, 元信息注册服务器可以根据该标识从业 务注册服务器中查询获得业务基本描述信息。元信息注册服务器根据这些元信 息, 查询某种业务可以处理的内容特征。这些特征是以元信息的逻辑表达式组 合的形式注册在元信息注册服务器的。
步骤 606、 业务选择代理将业务选择服务器发送的业务列表组织成客户端
可以识别的格式, 例如, 带有脚本的网页, 发送给客户端;
步骤 607、 用户通过客户端以各种交互方式选取、 确认业务, 例如通过菜 单选择的方式;
步骤 608、 业务选择代理根据客户端确认的菜单选项编号获得对应的业务 标识,再通过中央控制器发送给业务注册服务器,请求能够提供该业务的服务 器的接口和地址信息;
步骤 609、 业务注册服务器将提供该业务的服务器的接口和地址信息通过 中央控制器发送给业务选择代理, 再由业务选择代理将该信息发送给客户端, 这样, 客户端就可以根据这些信息发起业务请求。
如图 7所示, 是根据本发明又一实施例的业务选择方法的流程示意图, 包 括:
步骤 701至步骤 705 ,与上述实施例中的步骤 601至 605相同,此处不再赘述。 步骤 706、 业务选择服务器根据用户标识读取用户配置信息, 由于用户已 经配置了业务过滤,则需要将获得的业务列表通过中央控制器发送给业务过滤 服务器;
步骤 707、 业务过滤服务器对接收到的业务列表进行过滤操作, 获得过滤 后的业务列表, 并通过中央控制器将新下业务列表发送给业务选择服务器; 业务过滤服务器根据用户标识读取个人过滤策略。用户可以事先在业务过 滤服务器中设置个性化的业务过滤策略, 例如: 根据个人的使用频度、 业务的 热门程度、 业务选择装置提供的某种业务过滤策略或这些条件的组合。 当然, 业务过滤策略还可以是用户选择职业、 爱好、 所在城市等, 而业务过滤服务器 通过统计和分析业务描述的方法获得各个业务的类型,这样就可以为用户定制 较适合的业务过滤策略。 例如, 业务过滤服务器根据用户个人过滤策略, 查询 输入的业务列表中各个业务的个人使用频度、业务的热门程度、业务所属类别 等信息; 然后根据查询结果对业务列表进行过滤和排序。
步骤 708、 业务选择代理将业务选择服务器发送的经过过滤的业务列表组 织成客户端可以识别的格式, 发送给客户端;
步骤 709至步骤 711 , 与上述实施例中的步骤 607至步骤 609相同, 此处不再 赘述。
需要说明一点,本领域普通技术人员可以理解实现上述实施例方法中的全 部或部分步骤是可以通过程序指令相关的硬件来完成,所述的程序可以存储于 一计算机可读取的存储介质中, 所述的存储介质, 如: ROM/RAM、 磁碟、 光 盘等。
下面结合具体实例, 对本发明再做说明。
具体实例一
如图 8所示, 是本发明具体实施例一的业务选择***的结构示意图。 该业 务选择***包括: 业务选择装置 100、 业务注册服务器 200、 客户端应用服务器 300、 以及连接的其他各种内容服务器 400和各种业务服务器 500。 在包括该业 务选择***的网络中, 用户以某种方式访问内容时, 如音乐搜索、 邮件或网页 中查到歌曲链接,可以对某一首特定歌曲选择网络中提供的与此歌曲相关的业 务, 例如: 设置为铃声、 设置为彩铃、 推荐给朋友、 查看歌词、 查看相关音乐 电视影带 (Music Television Video, MTV )等。
1、 内容分析步骤
假设用户已经在业务选择装置注册, 并获得用户标识, 该用户标识可以是 业务选择服务器中的信息管理单元分配的标识, 也可以使用某种已有的标识, 例如, 个人手机号码等。
用户登录时, 业务选择代理获得用户标识。 当用户通过客户端读取一段包 含音乐内容的网页时, 希望对喜欢的音乐进行该网站不能提供的一些处理。那 么, 业务选择代理根据用户的指定操作获取相应的内容。如果该音乐的内容釆 用 RDFa格式描述相关元信息如下:
<ul>
<li about= "/user/david/music/23456">
<img src= " /user/david/musiccoverimg/23456" />
<span property = " dc : title "〉 exampleMusic </span>
<span property = "dc:Format "> mp3</span>
Creator
<a rel= "dc: creator"
href= "http://example.personal.com/David ">
David
</a>
<a rel= "dc: singer"
href= "http://example.personal.com/Palm ">
David
</a>
licensed under a
<a rel= "cc: license "
href= "http:〃 creativecommom. org/licenses/by-nc/2.5/">
Creative Commons Non-Commercial License
</a>
</li> 则业务选择代理经过分析,可以获得音乐内容的名称、格式、作者、歌手、 权限等元信息。 需要说明一点, 本发明实施例不限定描述元信息的具体方法, 除了釆用 RDFa格式描述之外, 也可以釆取其他方式描述元信息。
保存元信息如下:
< /user/david/music/23456>dc: title ffexampleMusic ff AXMLLiteral
< /user/david/music/23456>dc: Format ffmp3 ff AXMLLiteral
< /user/david/music/23456> dc: creator http://example.personal.com/David
< /user/david/music/23456> dcterm: singer http: //example. personal. com/Palm
</user/david/music/23456>cc: license
http:〃 creativecommom. org/licenses/by-nc/2.5 /Non-Commercial
如果网页中不含有元信息, 例如以下形式:
http:// musicsite. example. com/music. aspx? music id=xxxx925, 音乐描述信息、片段^口 下:
<// class: "li" style = "margin-right: 1 Opx; "〉 target: " blank" http: //musicsite. example, com/user/david/musiccoverimg/23456. mp3</a>
<div class= "right right" >
<div class= "right title "><b> exampleMusic </b></div> <div class= "right desc ">
<ul>
<li〉作曲: David </li>
<li>歌手 Palm</li>
<li〉出版社: CC出版社< >
<//>出版日期: 2007-l-K/li>
</ul>
</div>
</div>
则业务选择代理将网页 url: http:// musicsite. example. com、 上述 HTML描述 的信息片段、 以及用户标识发送到元信息提取服务器。
2、 元信息提取步骤
该步骤为可选步骤, 即仅在网页不直接包含元信息的情况下执行此步骤。 元信息提取服务器根据业务选择代理发送的内容特征和用户标识提取元信息。
首先, 元信息提取服务器查询内容特征是否属于通用特征。
在这里 , <a href= "http:/ musicsite.exampie.com/user/david/musiccoverimg/23456.mp3 " ^^ = "—6/"^>属于通用特征,可以根据 href链接中的文件后缀获得内容的格式 属于 MP3。 元信息描述如下:
< /user /david/music/23456>dc: Format "mp3 t,AAXMLLiteral
然后,元信息提取服务器根据用户标识获取用户事先已经配置在内容特征 库的内容特征与元信息的关系。 假设没有发现用户以前对网站 http:// musicsite. example. com的页面进行过任何标注, 那么, 元信息提取月良务器查询是否 有业务提供者、 内容提供者或其他用户对内容特征的标注与之相匹配。假设本 发明实施例中的音乐网站本身或内容提供者已经标注了上述 HTML描述音乐 的页面结构对应的元信息, 并保存在元信息提取服务器中, 则元信息提取服务 器由此可以获得该内容的标准描述如下:
Prefix: musicsitetag=http:// musicsite. example, com
< /user/david/music/23457> musicsitetag: 歌曲名 ffexampleMusic ff AXMLLiteral
< /user/david/music/23457> musicsitetag:作曲 http://example.personal.com/David
< /user/david/music/23457〉 musicsitetag: 歌手 http:〃 example .per sonal. com/Palm 再后, 元信息提取服务器借助标准字典, 获得元信息的标准描述如下:
< /user/david/music/23457>dc: title "exampleMusic ff AXMLLiteral
< /user/david/music/23457> dc: creator http://example.personal.com/David
< /user/david/music/23457> dcterm:sniger http: //example. per sonal. com/Palm
殳设网站 http:〃 musicsite. example, com声明内容均为原创,并向元信息提取 服务器注册可以拷贝、分发和网络传输, 则元信息提取服务器根据网址信息获 得元信息如下:
< /user/david/music/23457>cc:license http:〃 creativecommons. org/licenses/by-nc/2.5/ to
Share
元信息提取服务器将上述步骤获得的元信息通过中央控制器发送给业务 选择服务器。
3、 业务查询步骤
业务选择服务器将获得的元信息通过中央控制器向元信息注册服务器查 询与该元信息匹配的业务。
元信息注册服务器保存有业务与元信息的匹配关系,下面以彩铃业务为例 说明这种关系的保存:
http:〃 www. comtel. com/cor lorring/:
(dc: license
range = "http:〃 creativecommons. org/licenses/by/2.5/value =NonCommercial# Nonexist ") AND
(dc: format range = "http:// service. scomtel.com/auodiformat" )
其中业务提供者注册了业务服务器能够处理的 MP3\WMA\RM等声音文件 作为 http:// services, telcom. com/auodiforma 定义。
元信息注册服务器根据上一步得到的元信息查询到可以网络传输的 ΜΡ3 音乐文件 23457完全符合彩铃业务的条件, 元信息注册服务器继续查询彩铃业
务的基本描述如表 1所示, 并将彩铃业务的基本信息加入到该业务列表中。 表 1
4、 业务过滤步骤
业务过滤步骤为可选步骤, 当业务选择服务器根据用户标识读取用户配 置, 用户配置了业务过滤时, 业务选择服务器将上一步获得的业务列表通过中 央控制器发送给业务过滤服务器, 对业务进行过滤; 否则不需要执行此步骤。
业务过滤服务器根据用户标识读取个人过滤策略。假设用户在业务过滤服 务器中设置个性化的业务过滤策略为根据个人的最近使用频度和业务的热门 程度过滤,则业务过滤服务器分别读取上述业务列表中每种业务的用户使用统 计记录和被确认的统计记录, 找出最佳的前 5个业务。 查找结果为: 查看歌词、 彩铃订阅、 下载铃声、 A公司提供的查找相关歌曲等业务均为用户本人经常使 用或者热门的业务, 而转发推荐、 B公司提供的查找相关歌曲等业务则较少被 使用。 那么, 业务过滤服务器根据查询结果对业务列表进行过滤和排序, 生成 新的业务列表如表 3所示:
表 3
业务地址 业务提供者 业务描述 业务标记 http:〃 www. comtel. com/ringing/ Comtel corp. http:〃 www. comtel.com/cgi 下载钤声 http:〃 www. comtel. com/corlorring/ Comtel corp. http:〃 www. comtel . com/ws dl/ 彩钤订阅
corlorring.wsdl
http:〃 www. comA.com/lyric/ A corp. http://www.comA.com/cgi 查看歌词 http:〃 www. other, com/service 1 Other corpl Otherl 业务 1 http://www.other.com/service2 Other corp2 0ther2 业务 2
5、 业务选择和确认
业务选择代理将上述过滤后的业务列表组织成带有脚本的网页发送给客 户端。 用户通过客户端以菜单选择的方式选取、 确认业务。
当用户在客户端确认彩铃订阅业务时,业务选择代理将确认结果发送给业 务选择服务器。 业务选择服务器根据客户 端确认的业务标识 http:〃 www. comtel.com/corhrring/,向业务注册月良务器查询提供该彩铃业务的月良 务器的接口和地址信息, 然后将该信息发送给客户端。 这样, 客户端可以根据 这些信息发起业务请求。
同时, 业务选择服务器可以将确认统计发送给业务过滤服务器, 以便业务 过滤服务器修改该彩铃业务的统计数据。
具体实例二
用户在网页中看到一些感兴趣的商品信息,则可以直接比较其他商家的商 品、 查看评论、 将此信息保存到自己的个人资料中、 或点击拨号的方式电话咨 询商家。 虽然商家的网站可以提供以上所有服务, 但在许多场景下, 使用业务 选择装置可能更加合适。 例如, 用户有自己喜爱和信任的商品比较业务、 评论 业务, 希望能够直接使用这些业务; 用户可能有一个自己的商品资料库, 而不 希望被某个电子商务网站的购物车限制; 或商家网站不支持点击拨号业务, 而 只是公布了咨询电话号码等等情况。
"叚设联系信息网页 http://www. bookstoreexample. com/info. htm中热线电话信 息片段描述如下:
<tr>
<td height: "27" align: "left">
<div align: " center" >
<p align= "center"><font styk= "color:#666666' >客服热线:
010 xxxxxxx</font> </p>
</div>
</td>
</tr>
而商品比较业务在业务注册服务器注册商品信息内容的元信息特征,包括 在上述网站的商品索引网 ^ http://www. bookstoreexample. com/index4mai. htm ]商品信 息链接片段中商品信息类别标注为书籍商品信息。业务注册服务器将商品比较 业务索引到商品类元信息中,并将标注的这些网页特征注册到元信息提取服务 器。
网络拨号业务则将联系信息网 http://肩 w. booksto而 ampk.com/info.htm中热 线电话信息类别标注为电话号码。 当然,也可以 4叚设网站本身将电话号码的类 别按照 RDFa格式写在网页中, 描述如下:
<p align= "center "xfont style= "color:#666666">客服热线:
</font></p>
此外,4叚设用户已经在网络拨号业务中将用户标识和自己的手机号码等信 息关联起来。
而用户通过业务选择代理在业务过滤服务器中设置商品类的业务过滤策 略, 例如: 商品比较业务 A、 评论业务 B; 设置电话号码类的业务过滤策略为 自己手机所在运营商提供的网络拨号业务。
1、 当用户浏览商品时, 请求业务选择代理进行业务选择, 例如, 业务选 择代理作为浏览器的插件, 用户可以用鼠标选择上述商品信息的链接。
业务选择代理首先分析相关元信息: 将网页 URL和网页内商品链接的位 置、链接字符串本身作为内容特征发送到元信息提取服务器; 元信息提取服务 器返回内容类型为书籍商品的元信息。
业务选择代理将上述商品信息的链接、书籍商品信息内容类这一元信息和
用户标识发送到业务选择服务器; 业务选择服务器请求元信息注册服务器, 获 取数据商品信息内容类的相关业务列表,并通过业务过滤服务器根据用户标识 对业务列表进行过滤; 业务过滤服务器返回包含商品比较业务 A、 评论业务 B 的业务列表给业务选择代理;业务选择代理将其组织成带有脚本的网页发送给 客户端。
当用户选择商品比较业务 A时, 业务选择代理根据此业务注册的请求参数 配置,生成请求配置界面,让用户选择请求参数,并将请求消息返回给客户端。 例如, 请求参数可以为商品比较业务 A; 可能包括比较的选项: 比较相似价格 的同类商品、 比较同品牌商品、 限定比较地区等。
客户端发送请求商品比较业务 A, 商品比较业务 A接管后续流程, 直接针 对此商品进行比较。
2、 当用户期望通过电话联系商家时, 请求业务选择代理进行业务选择。 业务选择代理首先分析相关元信息, 分析出此内容的类型为电话号码。
业务选择代理将电话号码字符串、电话号码的内容类型这一元信息和用户 标识发送到业务选择服务器。 业务选择服务器请求元信息注册服务器, 获取电 话号码类的相关业务列表,并通过业务过滤服务器根据用户标识对业务列表进 行过滤, 返回用户手机所在运营商提供的网络拨号业务给业务选择代理。
如果业务选择服务器使用代理模式,代理客户端发送网络拨号请求给网络 拨号业务, 则参数包括用户标识和商家的热线电话号码。 网络拨号业务则为用 户手机和商家的热线电话之间建立通话。
以上所述仅为本发明的较佳实施例而已, 并非用于限定本发明的保护范 围。 凡在本发明的精神和原则之内所作的任何修改、 等同替换、 改进等, 均包 含在本发明的保护范围内。
Claims
1、 一种业务选择方法, 其特征在于, 包括:
根据客户端的指定内容获得元信息;
请求查询与所述元信息匹配的业务, 获得包含所述业务标识的业务列表; 将所述业务列表组织成客户端可以识别的格式提供给客户端,根据客户端 的确认信息得到对应的业务标识;
请求与所述业务标识对应的业务服务器的接口和地址信息 ,将获得的信息 提供给客户端。
2、 根据权利要求 1所述的业务选择方法, 其特征在于, 所述根据客户端 的指定内容获得元信息的过程包括:
当所述指定内容包含元信息描述时,按照内容的格式,提取其中的元信息 并转换为标准元信息描述;
当所述指定内容不包含元信息描述时,提取所述指定内容中用作内容特征 的字段, 请求获得与所述字段对应的元信息。
3、 根据权利要求 2所述的业务选择方法, 其特征在于, 所述请求获得与 所述字段对应的元信息的过程包括:
查询所述字段所表示的内容特征是否属于所述内容格式的通用特征,如果 属于, 则根据内容格式通用特征与元信息的关系获取元信息; 和 /或
根据用户标识和所述字段所表示的内容特征,查询事先配置的内容特征与 标注信息的索引关系, 获取相关标注信息; 通过统计和分析, 将所述标注信息 与业务注册的元信息相匹配, 获取相应的元信息。
4、 根据权利要求 1或 2所述的业务选择方法, 其特征在于, 所述将该业 务列表组织成客户端可以识别的格式提供给客户端的步骤之前还包括:
根据事先保存的用户标识读取用户配置信息, 如果用户已经配置业务过 滤, 则对业务列表进行过滤操作, 获得过滤后的新的业务列表。
5、 根据权利要求 4所述的业务选择方法, 其特征在于, 所述对业务列表 进行过滤操作的过程包括:
根据用户标识读取过滤策略,按照所述过滤策略查询业务列表中的各种信 息, 依照查询结果对业务列表进行过滤和排序, 生成新的业务列表。
6、 根据权利要求 1所述的业务选择方法, 其特征在于, 所述请求查询与 所述元信息匹配的业务, 获得包含所述业务标识的业务列表的步骤具体为: 将所述元信息和事先保存的业务与元信息的关系进行匹配,根据匹配结果 查询符合元信息匹配条件的业务,从而获得包含所述业务标识和基本描述的业 务列表。
7、 根据权利要求 6所述的业务选择方法, 其特征在于, 所述业务与元信 息的关系包括以下一种或几种:
特定业务与元信息的关系;
业务提供者注册的业务与元信息的关系; 以及
个人常用业务与元信息的关系。
8、 一种业务选择装置, 其特征在于, 包括: 业务选择代理、 业务选择服 务器、 元信息注册服务器、 以及中央控制器, 其中:
所述业务选择代理, 用于根据客户端的指定内容获得元信息; 将收到的业 务列表组织成客户端可以识别的格式发送给客户端,并从客户端的确认信息获 得对应的业务标识; 根据所述业务标识请求相应业务服务器的接口和地址信 息, 以及将获得的业务服务器的接口和地址信息发送给客户端;
所述业务选择服务器,用于将接收到的所述用户标识和元信息通过所述中 央控制器发送给所述元信息注册服务器请求基于所述指定内容的业务列表;以 及将获得的业务列表发送给所述业务选择代理;
所述元信息注册服务器, 用于查询与所述元信息匹配的业务, 获得包含业 务标识的业务列表,并将所述业务列表通过所述中央控制器发送给所述业务选 择服务器;
所述中央控制器, 用于对各个服务器请求的控制, 以及各个服务器之间信 息的传送。
9、 根据权利要求 8所述的业务选择装置, 其特征在于, 还包括: 元信息提取服务器, 用于保存内容特征与元信息的关系, 和 /或内容特征 与标注信息的关系,根据所述指定内容中用作内容特征的字段和事先保存的用 户标识与所述关系进行匹配, 获取相应的元信息, 并通过所述中央控制器发送 给所述业务选择服务器。
10、 根据权利要求 8或 9所述的业务选择装置, 其特征在于, 还包括: 业务过滤服务器,用于当接收到所述业务选择服务器发出的业务过滤请求 时,根据事先保存的用户标识读取过滤策略,按照所述过滤策略查询所述业务 选择服务器通过所述中央控制器发送来的业务列表中的各种信息,依照查询结 果对业务列表进行过滤和排序, 生成新的业务列表, 并通过所述中央控制器发 送给所述业务选择服务器。
11、 根据权利要求 9所述的业务选择装置, 其特征在于, 所述业务选择代 理包括:
内容分析单元, 用于对所述指定内容进行釆集和分析: 当指定内容中包含 元信息描述时, 提取元信息; 当指定内容中不包含元信息描述时, 提取内容特 征;
交互确认单元,用于将业务列表组织成客户端可以识别的格式发送给客户 端; 以及接收客户端的确认信息并获得对应的业务标识;
接口查询单元, 用于将根据客户端确认的业务标识,请求获得业务服务器 的接口和地址信息, 并将所述信息发送给客户端。
12、 根据权利要求 11所述的业务选择装置, 其特征在于, 所述内容分析单 元、 交互确认单元、接口查询单元在单独的服务器中; 或全部或部分在客户端 侧。
13、 根据权利要求 10所述的业务选择装置, 其特征在于, 所述业务选择服 务器包括:
选择控制单元, 用于控制业务选择的过程;
业务查询接口, 用于在所述选择控制单元的控制下, 向所述元信息注册服 务器发送用户标识和元信息,以及获得包含每个业务标识和基本描述信息的业 务列表, 并将所述的业务列表发送给所述业务选择代理。
14、 根据权利要求 13所述的业务选择装置, 其特征在于, 所述业务选择服 务器还包括:
信息管理单元, 用于保存和管理用户对业务选择的配置信息;
过滤查询接口,用于当所述选择控制单元根据用户标识读取所述信息管理 单元保存的配置信息,确定所述用户已经配置业务过滤时,将业务查询接口获
得的所述的业务列表提交业务过滤服务器, 以获得经过过滤处理的业务列表。
15、 根据权利要求 8所述的业务选择装置, 其特征在于, 所述元信息注册 服务器包括:
业务与元信息关系库, 用于保存和管理业务与元信息的关系;
业务注册信息库, 用于保存和管理业务的业务标识和基本描述信息; 业务查询引擎,用于将元信息与所述业务与元信息关系库保存的关系进行 匹配, 并根据匹配结果查询符合元信息匹配条件的业务,从所述业务注册信息 库中查找对应的基本描述信息,并将获得的包含业务标识和基本描述信息的业 务列表通过所述中央控制器发送给所述业务选择服务器;
业务注册管理单元, 用于提供业务元信息注册的接口。
16、 根据权利要求 9所述的业务选择装置, 其特征在于, 所述元信息提取 服务器包括:
内容特征库, 用于保存和管理内容特征与元信息的关系;
特征匹配引擎, 用于根据内容特征和用户标识与所述关系进行匹配, 获取 相应的元信息, 并通过所述中央控制器发送给所述业务选择服务器。
17、 根据权利要求 16所述的业务选择装置, 其特征在于, 所述元信息提取 服务器还包括:
内容标注库, 用于保存和管理内容特征与标注信息的关系, 以供所述特征 匹配引擎根据用户标识和内容特征进行查询, 获取相关标注;
标注统计分析单元, 用于通过统计标注和语言分析,将标注与业务注册的 元信息相对应, 建立标注信息和元信息的关系, 以供所述特征匹配引擎将获取 的标注与业务注册的元信息相匹配, 获取相应的元信息。
18、 根据权利要求 10所述的业务选择装置, 其特征在于, 所述业务过滤服 务器包括:
过滤策略订阅单元, 用于设置用户个人的过滤策略;
过滤策略库, 用于保存用户个人的过滤策略;
过滤处理单元, 用于根据用户标识从所述过滤策略库中读取过滤策略,按 照所述过滤策略查询业务列表中的各种信息,依照查询结果对业务列表进行过 滤和排序, 生成新的业务列表, 并通过所述中央控制器发送给所述业务选择服
务器。
19、 根据权利要求 18所述的业务选择装置, 其特征在于, 所述业务过滤 服务器还包括:
外部过滤接口, 用于提供外部过滤服务的接口, 通过该接口将业务列表发 送给外部过滤服务器, 由外部过滤服务器处理后, 通过该接口返回过滤后的业 务列表。
20、 一种业务选择***, 其特征在于, 包括: 客户端应用服务器、 业务选 择装置、 及业务注册服务器; 所述业务选择装置包括: 业务选择代理、 业务选 择服务器、 元信息注册服务器、 以及中央控制器, 其中:
所述业务选择代理,用于根据客户端应用服务器提供的指定内容获得元信 息; 将收到的业务列表组织成客户端可以识别的格式发送给客户端,从客户端 的确认信息获得对应的业务标识;根据所述业务标识请求相应业务服务器的接 口和地址信息,以及将从所述业务注册服务器获得的业务服务器的接口和地址 信息发送给客户端应用服务器;
所述业务选择服务器,用于将接收到的所述用户标识和元信息通过所述中 央控制器发送给所述元信息注册服务器请求基于所述指定内容的业务列表;以 及将获得的业务列表发送给所述业务选择代理;
所述元信息注册服务器, 用于查询与所述元信息匹配的业务, 获得包含业 务标识的业务列表,并将所述业务列表通过所述中央控制器发送给所述业务选 择服务器;
所述中央控制器, 用于对各个服务器请求的控制, 以及所述业务选择装置 中各个服务器与业务注册服务器之间信息的传送。
21、 根据权利要求 20所述的业务选择***, 其特征在于, 所述业务选择 装置还包括:
元信息提取服务器, 用于保存内容特征与元信息的关系, 和 /或内容特征 与标注信息的关系,根据所述指定内容中用作内容特征的字段和事先保存的用 户标识与所述关系进行匹配, 获取相应的元信息, 并通过所述中央控制器发送 给所述业务选择服务器。
22、 根据权利要求 20或 21所述的业务选择***, 其特征在于, 所述业务
选择装置还包括:
业务过滤服务器,用于当接收到所述业务选择服务器发出的业务过滤请求 时,根据事先保存的用户标识读取过滤策略,按照所述过滤策略查询所述业务 选择服务器通过所述中央控制器发送来的业务列表中的各种信息,依照查询结 果对业务列表进行过滤和排序, 生成新的业务列表, 并通过所述中央控制器发 送给所述业务选择服务器。
23、 一种客户端应用服务器, 其特征在于, 包括:
发送单元, 用于发送业务选择请求, 选择结果, 及业务请求;
接收单元, 用于接收带有业务列表的信息,及业务服务器的接口和地址信 息;
选择单元, 用于根据所述带有业务列表的信息选择合适的业务, 并将选择 结果传送到所述的发送单元;
请求生成单元, 用于根据指定内容生成业务选择请求,及根据所述业务服 务器的接口和地址信息生成业务请求, 并将所述业务选择请求、 业务请求传送 到所述的发送单元。
24、 根据权利要求 23所述的客户端应用服务器, 其特征在于, 所述的选 择单元根据所述带有业务列表的信息选择合适的业务具体是指:所述的选择单 元根据业务菜单选择菜单选项编号。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP07846225.6A EP2023531B1 (en) | 2007-04-28 | 2007-12-29 | Method, apparatus, system, user terminal application server for selecting service |
US12/190,792 US8219688B2 (en) | 2007-04-28 | 2008-08-13 | Method, apparatus and system for service selection, and client application server |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2007100972380A CN101072116B (zh) | 2007-04-28 | 2007-04-28 | 业务选择方法、装置、***及客户端应用服务器 |
CN200710097238.0 | 2007-04-28 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/190,792 Continuation US8219688B2 (en) | 2007-04-28 | 2008-08-13 | Method, apparatus and system for service selection, and client application server |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2008131630A1 true WO2008131630A1 (fr) | 2008-11-06 |
Family
ID=38899120
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2007/071399 WO2008131630A1 (fr) | 2007-04-28 | 2007-12-29 | Procédé, dispositif, système, serveur d'application de terminal d'utilisateur pour sélectionner un service |
Country Status (5)
Country | Link |
---|---|
US (1) | US8219688B2 (zh) |
EP (1) | EP2023531B1 (zh) |
CN (1) | CN101072116B (zh) |
RU (1) | RU2405267C2 (zh) |
WO (1) | WO2008131630A1 (zh) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2015090608A (ja) * | 2013-11-06 | 2015-05-11 | キヤノン株式会社 | 情報処理端末およびその制御方法、並びにプログラム |
CN105681839A (zh) * | 2015-12-31 | 2016-06-15 | 新奥特(北京)视频技术有限公司 | 一种多屏内容统一发布的业务*** |
Families Citing this family (51)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7743158B2 (en) * | 2002-12-04 | 2010-06-22 | Ntt Docomo, Inc. | Access network dynamic firewall |
US8948046B2 (en) | 2007-04-27 | 2015-02-03 | Aerohive Networks, Inc. | Routing method and system for a wireless network |
CN101072116B (zh) * | 2007-04-28 | 2011-07-20 | 华为技术有限公司 | 业务选择方法、装置、***及客户端应用服务器 |
US8218502B1 (en) | 2008-05-14 | 2012-07-10 | Aerohive Networks | Predictive and nomadic roaming of wireless clients across different network subnets |
CN101610152B (zh) * | 2008-06-19 | 2012-02-01 | 华为技术有限公司 | 内容识别方法和***以及内容管理客户端和服务器 |
US8527651B2 (en) | 2008-06-19 | 2013-09-03 | Huawei Technologies Co., Ltd. | Content identification method and system, and SCIDM client and server |
US9674892B1 (en) | 2008-11-04 | 2017-06-06 | Aerohive Networks, Inc. | Exclusive preshared key authentication |
US8483194B1 (en) | 2009-01-21 | 2013-07-09 | Aerohive Networks, Inc. | Airtime-based scheduling |
US11115857B2 (en) | 2009-07-10 | 2021-09-07 | Extreme Networks, Inc. | Bandwidth sentinel |
US9900251B1 (en) | 2009-07-10 | 2018-02-20 | Aerohive Networks, Inc. | Bandwidth sentinel |
CN101867893B (zh) * | 2010-06-29 | 2014-09-10 | 中兴通讯股份有限公司 | 一种进行增值业务指令处理的方法和业务管理平台设备 |
US8671187B1 (en) | 2010-07-27 | 2014-03-11 | Aerohive Networks, Inc. | Client-independent network supervision application |
US8503980B2 (en) * | 2010-08-31 | 2013-08-06 | International Business Machines Corporation | Providing location-based services in an ad hoc environment |
US20120059932A1 (en) * | 2010-09-02 | 2012-03-08 | Samsung Electronics Co., Ltd. | Applying home network technologies to a wide area network |
US9002277B2 (en) | 2010-09-07 | 2015-04-07 | Aerohive Networks, Inc. | Distributed channel selection for wireless networks |
CN102577237B (zh) * | 2010-12-20 | 2014-04-02 | 华为技术有限公司 | 网站托管服务调度方法、应用访问处理方法、装置及*** |
US8682881B1 (en) * | 2011-09-07 | 2014-03-25 | Google Inc. | System and method for extracting structured data from classified websites |
US10091065B1 (en) * | 2011-10-31 | 2018-10-02 | Aerohive Networks, Inc. | Zero configuration networking on a subnetted network |
US8787375B2 (en) | 2012-06-14 | 2014-07-22 | Aerohive Networks, Inc. | Multicast to unicast conversion technique |
US20140082157A1 (en) * | 2012-09-18 | 2014-03-20 | Artisan Mobile, Inc. | System and method for selectively permitting entry into a defined mode by distributed client-side software applications |
CN103945572A (zh) * | 2013-01-18 | 2014-07-23 | 中兴通讯股份有限公司 | 一种处理新业务的方法和业务服务器 |
US9413772B2 (en) | 2013-03-15 | 2016-08-09 | Aerohive Networks, Inc. | Managing rogue devices through a network backhaul |
US10389650B2 (en) | 2013-03-15 | 2019-08-20 | Aerohive Networks, Inc. | Building and maintaining a network |
GB2514543B (en) | 2013-04-23 | 2017-11-08 | Gurulogic Microsystems Oy | Server node arrangement and method |
RU2530269C1 (ru) * | 2013-06-14 | 2014-10-10 | Общество с ограниченной ответственностью "Новая Рекламная Механика" | Способ вставки сообщений в электронные документы внедренным клиентским скриптом |
US9201900B2 (en) * | 2013-08-29 | 2015-12-01 | Htc Corporation | Related image searching method and user interface controlling method |
US9560055B2 (en) * | 2014-04-30 | 2017-01-31 | Microsoft Technology Licensing, Llc | Client-side integration framework of services |
CN104135512B (zh) * | 2014-07-16 | 2015-08-05 | 小米科技有限责任公司 | 服务注册更新方法、装置、服务器及客户端 |
CN104965857B (zh) * | 2015-06-01 | 2019-04-26 | 百度在线网络技术(北京)有限公司 | 服务信息提供方法、客户端和服务器 |
CN106445694A (zh) * | 2015-08-12 | 2017-02-22 | 优信互联(北京)信息技术有限公司 | 一种应用程序访问方法、装置及*** |
CN105049446A (zh) * | 2015-08-20 | 2015-11-11 | 中国联合网络通信集团有限公司 | 一种url过滤方法及*** |
CN105376225B (zh) * | 2015-11-02 | 2019-07-26 | 亚信科技(南京)有限公司 | 一种软件服务化的方法及装置 |
CN105677614B (zh) * | 2016-01-04 | 2018-09-25 | 浪潮集团有限公司 | 一种多主机控制器、多主机控制方法及*** |
CN107193847B (zh) * | 2016-03-15 | 2021-09-28 | 阿里巴巴集团控股有限公司 | 一种卫星实时轨道信息的查询方法及装置 |
CN107273381A (zh) * | 2016-04-08 | 2017-10-20 | 中兴通讯股份有限公司 | 一种网络业务的检索方法、装置、主服务器及从服务器 |
CN106095891A (zh) * | 2016-06-07 | 2016-11-09 | 广东睿盟计算机科技有限公司 | 一种适用于前台工作人员的业务工作量识别统计方法 |
CN106130787B (zh) * | 2016-07-28 | 2020-04-24 | 中国电信集团工会上海市网络操作维护中心委员会 | 一种基于软件定义网络的业务处理*** |
CN107784548B (zh) * | 2017-02-17 | 2020-09-29 | 平安科技(深圳)有限公司 | 订单处理方法和装置 |
FR3063590A1 (fr) * | 2017-03-03 | 2018-09-07 | Orange | Dispositif d'acces a adressage multiple |
CN107426266B (zh) * | 2017-03-14 | 2020-08-04 | 阿里巴巴集团控股有限公司 | 数据处理方法和服务器 |
CN107483565B (zh) * | 2017-08-01 | 2020-12-22 | 北京信安世纪科技股份有限公司 | 一种服务后台识别方法、代理服务器及计算机存储介质 |
CN110019511B (zh) | 2017-09-30 | 2021-10-22 | 华为技术有限公司 | 通信方法及其通信设备 |
CN109067818B (zh) * | 2018-06-04 | 2019-08-20 | 杭州数梦工场科技有限公司 | 一种业务访问方法及装置 |
CN109871489A (zh) * | 2019-03-06 | 2019-06-11 | 网宿科技股份有限公司 | 一种智能识别***中的资源检索方法及智能识别*** |
CN110351342A (zh) * | 2019-06-20 | 2019-10-18 | 平安科技(深圳)有限公司 | 业务指令处理方法、装置、计算机设备和存储介质 |
CN112910745B (zh) * | 2019-12-04 | 2023-09-19 | Vidaa(荷兰)国际控股有限公司 | 一种智能家居设备的控制方法及设备 |
CN111580967A (zh) * | 2020-05-07 | 2020-08-25 | 拉扎斯网络科技(上海)有限公司 | 一种虚拟资源分配方法、装置、服务器、终端及存储介质 |
CN113709190B (zh) * | 2021-10-27 | 2022-03-01 | 中兴通讯股份有限公司 | 业务设置方法和装置、存储介质及电子设备 |
CN113988722B (zh) * | 2021-12-28 | 2022-09-27 | 恒银金融科技股份有限公司 | 一种应用于综合自助设备的用户习惯自适应方法 |
CN115022390A (zh) * | 2022-05-27 | 2022-09-06 | 中国银行股份有限公司 | 基于弱网络的业务处理方法、装置、存储介质及程序产品 |
CN116974722B (zh) * | 2023-07-18 | 2024-04-05 | 广东南方智媒科技有限公司 | 一种针对媒体业务的ai服务调用方法、装置和*** |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030084096A1 (en) | 2001-10-31 | 2003-05-01 | Bryan Starbuck | Computer system with file association and application retrieval |
US20040064428A1 (en) | 2002-09-26 | 2004-04-01 | Larkin Michael K. | Web services data aggregation system and method |
CN1934839A (zh) * | 2004-06-29 | 2007-03-21 | 西门子公司 | 提供支持一项业务或一组业务的可靠的服务器功能的方法 |
US7200387B1 (en) * | 2004-09-01 | 2007-04-03 | Cellco Partnership | Application invocation on a mobile station using messaging service |
CN101072116A (zh) * | 2007-04-28 | 2007-11-14 | 华为技术有限公司 | 业务选择方法、装置、***及客户端应用服务器 |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5388147A (en) * | 1993-08-30 | 1995-02-07 | At&T Corp. | Cellular telecommunication switching system for providing public emergency call location information |
US6594700B1 (en) * | 1999-06-14 | 2003-07-15 | International Business Machines Corporation | System and method for implementing a universal service broker interchange mechanism |
US6549922B1 (en) * | 1999-10-01 | 2003-04-15 | Alok Srivastava | System for collecting, transforming and managing media metadata |
WO2002093289A2 (en) * | 2001-05-15 | 2002-11-21 | Nokia Corporation | Mobile web utilizing services |
US20040201682A1 (en) * | 2001-08-22 | 2004-10-14 | Lou Chauvin | System, method and software product for allowing a consumer to order image products over a communication network from a plurality of different providers |
US7035922B2 (en) * | 2001-11-27 | 2006-04-25 | Microsoft Corporation | Non-invasive latency monitoring in a store-and-forward replication system |
JP3823929B2 (ja) * | 2002-05-17 | 2006-09-20 | ソニー株式会社 | 情報処理装置、情報処理方法、およびコンテンツ配信装置、コンテンツ配信方法、並びにコンピュータ・プログラム |
CN1588369A (zh) * | 2004-09-06 | 2005-03-02 | 杭州恒生电子股份有限公司 | 一种关系型数据库***及其查询和报表方法 |
US9274830B2 (en) * | 2004-11-18 | 2016-03-01 | Aol Inc. | Service clean-up |
-
2007
- 2007-04-28 CN CN2007100972380A patent/CN101072116B/zh active Active
- 2007-12-29 EP EP07846225.6A patent/EP2023531B1/en active Active
- 2007-12-29 RU RU2008137258/09A patent/RU2405267C2/ru active
- 2007-12-29 WO PCT/CN2007/071399 patent/WO2008131630A1/zh active Application Filing
-
2008
- 2008-08-13 US US12/190,792 patent/US8219688B2/en active Active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030084096A1 (en) | 2001-10-31 | 2003-05-01 | Bryan Starbuck | Computer system with file association and application retrieval |
US20040064428A1 (en) | 2002-09-26 | 2004-04-01 | Larkin Michael K. | Web services data aggregation system and method |
CN1934839A (zh) * | 2004-06-29 | 2007-03-21 | 西门子公司 | 提供支持一项业务或一组业务的可靠的服务器功能的方法 |
US7200387B1 (en) * | 2004-09-01 | 2007-04-03 | Cellco Partnership | Application invocation on a mobile station using messaging service |
CN101072116A (zh) * | 2007-04-28 | 2007-11-14 | 华为技术有限公司 | 业务选择方法、装置、***及客户端应用服务器 |
Non-Patent Citations (1)
Title |
---|
See also references of EP2023531A4 |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2015090608A (ja) * | 2013-11-06 | 2015-05-11 | キヤノン株式会社 | 情報処理端末およびその制御方法、並びにプログラム |
CN105681839A (zh) * | 2015-12-31 | 2016-06-15 | 新奥特(北京)视频技术有限公司 | 一种多屏内容统一发布的业务*** |
Also Published As
Publication number | Publication date |
---|---|
US20080313273A1 (en) | 2008-12-18 |
US8219688B2 (en) | 2012-07-10 |
EP2023531A1 (en) | 2009-02-11 |
RU2008137258A (ru) | 2010-10-27 |
EP2023531A4 (en) | 2009-07-15 |
EP2023531B1 (en) | 2015-02-25 |
CN101072116A (zh) | 2007-11-14 |
CN101072116B (zh) | 2011-07-20 |
RU2405267C2 (ru) | 2010-11-27 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2008131630A1 (fr) | Procédé, dispositif, système, serveur d'application de terminal d'utilisateur pour sélectionner un service | |
TWI479331B (zh) | 聚集及搜尋來自多重服務之設定檔資料 | |
US7277928B2 (en) | Method for facilitating access to multimedia content | |
US20070027857A1 (en) | System and method for searching multimedia and download the search result to mobile devices | |
US8224788B2 (en) | System and method for bookmarking and auto-tagging a content item based on file type | |
US20090006338A1 (en) | User created mobile content | |
US20090012940A1 (en) | Sharing mobile search results | |
US20020107973A1 (en) | Metadata processes for multimedia database access | |
WO2009092214A1 (zh) | 对发布信息进行处理的方法、客户端、服务器和*** | |
US20060112141A1 (en) | System for automatically creating a metadata repository for multimedia | |
US20070288477A1 (en) | Information processing apparatus, information processing system, information processing method, and computer program | |
EP1818930A1 (en) | System and method for the intelligent management, recommendation and discovery of multimedia contents for mobile playback devices | |
TW200834358A (en) | Providing virtual really simple syndication (RSS) feeds | |
US20090132542A1 (en) | Peer-to-Peer Sharing in Media Management Software | |
WO2009124480A1 (zh) | 一种搜索方法、设备及*** | |
WO2010000211A1 (zh) | 搜索方法、搜索服务器和搜索*** | |
TW201101067A (en) | Method and server for providing picture searching | |
JP4934154B2 (ja) | コンテンツ提供装置 | |
JP4177033B2 (ja) | コンテンツ閲覧状態管理システム及びコンテンツ閲覧状態管理方法及びプログラム及び記録媒体 | |
KR100368542B1 (ko) | 인터넷 상에서 브이오아이피를 기반으로 한 080 무료전화검색 및 자동접속 시스템 | |
JP2003006230A (ja) | 情報検索処理方法、情報検索処理サーバ、情報提示方法、情報提示装置、プログラム及び媒体 | |
AU770181B2 (en) | A method for facilitating access to multimedia content | |
KR20050059385A (ko) | 컨텐츠 스크랩 시스템 및 그 방법 | |
JP2009054166A (ja) | 掲載データのクリッピングシステム | |
JP2003203032A (ja) | ウェブサーバ仲介装置、方法および対話型ウェブサーバ仲介ポータルサーバ |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 2007846225 Country of ref document: EP |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 07846225 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2008137258 Country of ref document: RU Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |