WO2008043305A1 - Méthode de sélection d'un courtier de services, et système permettant la sélection d'un courtier de services - Google Patents

Méthode de sélection d'un courtier de services, et système permettant la sélection d'un courtier de services Download PDF

Info

Publication number
WO2008043305A1
WO2008043305A1 PCT/CN2007/070826 CN2007070826W WO2008043305A1 WO 2008043305 A1 WO2008043305 A1 WO 2008043305A1 CN 2007070826 W CN2007070826 W CN 2007070826W WO 2008043305 A1 WO2008043305 A1 WO 2008043305A1
Authority
WO
WIPO (PCT)
Prior art keywords
service agent
service
selection
service broker
trigger
Prior art date
Application number
PCT/CN2007/070826
Other languages
English (en)
French (fr)
Inventor
Sang Wu
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2008043305A1 publication Critical patent/WO2008043305A1/zh

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/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/306—User profiles
    • 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/562—Brokering proxy services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service

Definitions

  • the present invention relates to the field of communication technologies, and in particular, to a service agent selection method and a network system for providing a service agent selection.
  • the IP Multimedia Subsystem was introduced in Release 5 by the 3rd Generation Mobile Communications Standards Partnership Project (3GPP), a Session Initiation Protocol (SIP)-based system that separates the session layer from the service layer and provides open services.
  • SIP Session Initiation Protocol
  • OSA is an open interface that facilitates third-party business development.
  • operators also want to be able to integrate existing services and provide new hybrid services. It can be foreseen that the services that users in the future network can use will become more and more abundant, and the business conflicts will become more and more prominent. These characteristics put forward new requirements for the way of providing services, and in this context, business agents are generated. (Service Broker) technology.
  • Service Broker mainly implements the business capability interaction management function in the IMS network.
  • Service Broker technology is still in the research stage, and the scope of research related to Service Broker in each standard varies. It is precisely because there is no uniform definition of the concept and scope of Service Broker in each standard.
  • the Service Broker functions implemented by various manufacturers are not the same.
  • some vendors provide Service Broker with business mixing capabilities and business interaction management capabilities.
  • Some business agent entities provided by the manufacturer also have enhanced business triggering capabilities.
  • the capabilities implemented by various vendors will not be exactly the same. For example, some manufacturers support the interaction between voice call services and interactive network television IPTV services, and some manufacturers do not.
  • Service Brokers such as Service Broker trigger points
  • Service Broker trigger point can be service call session control (S-CSCF).
  • S-CSCF service call session control
  • this method is only a static configuration choice, can not achieve flexible load balancing, can not provide dynamic Service Broker selection, and can not choose other available Service Broker in the case of specified Service Broker failure; It is also possible to use a non-contracted service after registration, and the non-contracted service may have a business interaction problem with the user's contracted business, if the previously selected Service Broker cannot handle the non-contracted service and the service that the user has used. For business interaction, there is a problem with choosing a new Service Broker. Therefore, the application of this static service agent selection method has certain limitations. Operators, in view of network operation, hope to have a more flexible and dynamic service agent selection method for the network.
  • the technical problem to be solved by the present invention is to provide a service agent selection method and a network system for providing service agent selection.
  • the present invention can implement a dynamic selection of a service agent that satisfies the user service capability requirements in the network.
  • a method of selecting a business agent including:
  • the service agent selection function receives a service agent selection request sent by the service agent selection trigger point; the service agent selection function obtains the service agent selection data from the service agent selection database according to the service agent selection request;
  • the service agent selection function selects a service agent based on the service agent selection data.
  • a network system that provides selection of business agents including:
  • the service agent selects a trigger point for requesting the service agent selection function SBSF for service agent selection
  • a service agent selection function SBSF configured to receive the request for the service agent selection trigger point; communicate with the service agent selection database according to the request, obtain service agent selection data, and select a service agent according to the selection data;
  • the business agent selects a database to provide selection data.
  • a business agent selection trigger point including:
  • a request unit configured to request a service agent selection function, the SBSF performs a service agent selection.
  • a business agent trigger point including:
  • the first triggering unit is configured to request the service agent selection function SBSF to perform service agent selection.
  • a service agent selection function SBSF including:
  • a receiving unit configured to receive the request of the request unit of the service agent selection trigger point; the first selecting unit, according to the request received by the receiving unit, communicates with the service agent selection database to obtain service agent selection data, according to the Select the data selection business agent.
  • the prior art triggers to the Service Broker with a static configuration selection method, and cannot provide dynamic Service Broker selection.
  • the present invention adds a service agent selection trigger point, a service agent selection function (SBSF), and a service agent selection database, and a service agent. Selecting the trigger point request SBSF to perform service agent selection for the user, the SBSF communicates with the service agent selection database, obtains selection data of the service agent selection database, and selects the service agent according to the selection data, thereby realizing the service agent provided according to the user requirement and the network.
  • SBSF service agent selection function
  • FIG. 1 is a network architecture diagram of a preferred embodiment of the present invention
  • Embodiment 1 is a flow chart of Embodiment 1 of the method of the present invention.
  • Figure 5 is a flow chart of Embodiment 3 of the method of the present invention.
  • Figure 6 is a flow chart of Embodiment 4 of the method of the present invention.
  • Figure 7 is a flow chart of Embodiment 5 of the method of the present invention.
  • Figure 8 is a flow chart of Embodiment 6 of the method of the present invention.
  • Embodiment 7 is a flow chart of Embodiment 7 of the method of the present invention.
  • FIG. 10 is a flowchart of Embodiment 8 of the method of the present invention.
  • Figure 11 is a flow chart of Embodiment 9 of the method of the present invention.
  • Figure 12 is a flow chart of Embodiment 10 of the method of the present invention.
  • FIG. 13 is a schematic structural diagram of a network system according to a preferred embodiment of the present invention.
  • FIG. 14 is a schematic structural diagram of a service agent selection trigger point according to a preferred embodiment of the present invention.
  • FIG. 15 is a schematic structural diagram of a service proxy selection function SBSF according to a preferred embodiment of the present invention
  • FIG. 16 is a schematic structural diagram of a service proxy trigger point according to a preferred embodiment of the present invention.
  • the service agent selection method provided by the present invention mainly adds a Service Broker Selection Function (SBSF), a Service Broker Selection Database, and a Service Broker selection trigger point.
  • SBSF provides Service Broker selection capability, which can dynamically select Service Broker for users according to requirements. It can be an independent network element, or it can be located in S-CSCF, or query call session control function (I-CSCF), or home subscriber server (HSS). ), or Service Broker, etc.
  • the Service Broker selection database is used to provide Service Broker selection data, which may be an independent network element or a home subscriber server HSS.
  • the Service Broker selection data includes the Service Broker service capability requirements of the user service, and the Service Broker specified by the operator for the user.
  • the Service Broker selection trigger point provides the function of triggering the Service Broker selection process, that is, providing the function of triggering the SBSF.
  • the Service Broker selection trigger point can be an independent network element, or can be located in the S-CSCF or the I-CSCF, or the Service Broker.
  • Service Broker can not trigger the selection of other Service Brokers when the user requests the user's request to invoke the business interaction processing capability caused by the non-contracted service.
  • FIG. 1 is a network logical architecture diagram of a preferred embodiment of a service proxy selection method provided by the present invention.
  • FIG. 1 includes a Service Broker trigger point, a Service Broker selection trigger point, a service proxy selection function SBSF, and a Service Broker selection database.
  • the Service Broker trigger point is used to trigger the current communication to Service Broker, which may be a Independent network elements, which can also be located in the S-CSCF, etc.;
  • Service Broker is used to provide functions such as service interaction management between different services. It can be an independent network element, or it can be located in an S-CSCF or an application server (AS). . .
  • FIG. 2 is a flowchart of a method according to a preferred embodiment of the present invention, including the steps:
  • the Service Broker selects the trigger point to communicate with the SBSF, and requests the SBSF to select the Service Broker for the user;
  • Service Broker selects trigger conditions for trigger point request SBSF for Service Broker selection Can include the following:
  • the service agent When the service agent selects the trigger point to receive the message, it triggers the SBSF according to the service trigger data indication. For example, the service agent selects the trigger point as the S-CSCF, and the S-CSCF receives the user-initiated registration message or the unregistered user initiates or receives the call message. Triggering to the SBSF according to the iFC data (service trigger data) obtained from the HSS, that is, the server address element in the iFC data is taken as the address of the SBSF;
  • iFC data service trigger data
  • the message indicates that the service agent selection is required.
  • the service agent selects the trigger point as the S-CSCF, and the S-CSCF requests the HSS to download the user service trigger data, and the HSS sends the response to the S-CSCF.
  • the message indicates that a business agent selection is required;
  • the message When the service agent selects the trigger point to receive the message, the message carries the SBSF address.
  • the service agent selects the trigger point as the S-CSCF, the service agent selects the database as the HSS, and the S-CSCF requests the HSS to download the user service trigger data, and the HSS sends the message to the S.
  • the response message of the -CSCF carries the SBSF address.
  • the Service Broker selection trigger point communicates with the SBSF based on the SBSF address and sends a Service Broker Selection Request message to the SBSF.
  • the SB SF address can be obtained by selecting the trigger point local configuration in the Service Broker or in the service trigger data saved in the user subscription database. For example, the server address element of the iFC data is taken as the address of the SBSF and sent to the Service Broker.
  • the trigger point is selected, or the message received by the Service Broker selection trigger point carries the SBSF address.
  • the SBSF address can also default to the Service Broker selection trigger point local address.
  • the Service Broker selects the trigger point to forward the received message that causes the Service Broker to be selected, such as forwarding the user registration message, etc., or the Service Broker selection trigger point sends a message indicating that the Service Broker is selected to the SBSF, for example, the Service Broker selects the trigger point to send.
  • a SIP INVITE message carrying an indication of a request for Service Broker selection.
  • the above message may also be an internal interface message when the SBSF and the Service Broker selection trigger point are on the same physical device.
  • the Service Broker selects the service direction in the Service Broker selection request message sent by the trigger point to the SBSF.
  • the Service Broker selection trigger point is the S-CSCF
  • the iFC triggers the SBSF.
  • the SBSF address in the data is configured separately for the service user direction, that is, the SBSF address served by the calling user and the SBSF address of the called service are separately configured, so that the server address part in the iFC data can be represented by different SBSF addresses.
  • Service direction the SBSF distinguishes the user's service direction based on the SB SF address in the received message.
  • the above Service Broker selection request message may further include the requested service.
  • Service Broker trigger point address and / or Service Broker business capability requirements refer to, for example, the types of services that need to be provided.
  • the ability to carry Service Broker service capability requirements in messages requesting Service Broker selection is generally used to indicate dynamic service capability requirements, rather than Based on the contracted service capability requirements, for example, the user uses the service interaction processing capability requirements caused by the non-contracted service.
  • the role of the Service Broker trigger point address means that, for example, the SBSF can confirm the connectivity between the Service Broker trigger point and the Service Broker to be selected. This information is not required to be carried. For example, when Service Broker selects the trigger point to send the request, the Service Broker selection message does not carry the Service Broker trigger point address. The SBSF sends the message to the Service Broker trigger point by default. For example, the message does not carry the Service Broker service.
  • the capability requirements are met, it can be understood that the user service has no special capability requirements for Service Broker, or it can be obtained from the Service Broker selection database after the Service Broker business capability requirements.
  • A2, SBSF and Service Broker select database communication, obtain Service Broker selection data and select Service Broker according to the data and Service Broker selection algorithm;
  • the SBSF selects the database request from the Service Broker to obtain the selection data, and the Service Broker selects the database to return the requested selection data.
  • the manner in which the SBSF performs the Service Broker selection data request includes at least: using an existing protocol message, for example, the Service Broker selects the database as the HSS, and the SBSF can use the Sh interface message user data request (UDR) to request the Service Broker to select the data; or, the interface protocol
  • the extension is performed, for example, using the Diameter protocol to add a new command code carrying the selection data request message.
  • Service Broker selection data includes at least:
  • Service Broker capability requirements include mandatory capability requirements, optional capability requirements, and may include Service Broker names.
  • Service Broker names can be The address of the Service Broker. In the case where the Service Broker capability request carries the Service Broker name, for example, the registration message processing flow carries the Service Broker name that is temporarily selected for the unregistered user, that is, the Service Broker address;
  • the Service Broker selection data may also include one or more of the following information:
  • the service broker trigger point and the topology connection relationship of the Service Broker in the network such as the Service Broker trigger point and the Service Broker connection '1', etc.;
  • Service Broker the availability of Service Broker in the network, such as whether Service Broker is running normally, etc.; f, Service Broker optimization strategy, for example, when Service Broker and S-CSCF are combined
  • the S-CSCF provides the Service Broker capability required by the user, or the load balancing of the Service Broker;
  • Service Broker trigger point to Service Broker trigger mode data used to determine the unique trigger mode of Service Broker trigger point to Service Broker, for example, SBSF selected a Service Broker for unregistered users, and then selected one when the user registered Different Service Brokers, the SBSF determines whether to update the trigger mode of the Service Broker trigger point to the Service Broker by comparing the Service Broker address in the trigger mode data with the currently selected Service Broker address. For example, when the update is required, the SBSF passes the The HSS Human Machine Language (MML) interface updates the Service Broker trigger point stored on the HSS to the Service Broker's iFC rules, such as updating the server address configured in the iFC rule, which represents the address of the Service Broker.
  • MML Human Machine Language
  • the positioning of the rules that need to be updated on the HSS can be determined by a rule index such as the MML language convention.
  • the Service Broker selection data may include at least one or more of the a ⁇ g information described above.
  • the SBSF After the SBSF obtains the Service Broker selection data, it selects the Service Broker that meets the requirements. If the Service Broker selection data includes the Service Broker specified by the operator for the user, the SBSF directly selects the Service Broker; if the Service Broker selection data does not include the Service Broker specified by the operator for the user, the SBSF selects the data according to the Service Broker described above. And the Service Broker selection algorithm selects Service Broker, for example, SBSF receives according to it. Service Broker is selected by the Service Broker service capability requirements carried in the Service Broker selection request message, the degree of matching of the service capabilities that the Service Broker can provide in the network, and the Service Broker availability. Matching degree refers to the service broker that prioritizes all mandatory capability requirements and provides the most optional capability requirements.
  • the trigger mode includes Service Broker name or service trigger data configured with Service Broker information.
  • the Service Broker name that is, the Service Broker address, where the Service Broker name is used instead of the Service Broker address is to distinguish it from the addresses of other types of entities, such as the address of the application server AS, and the S-CSCF to Service Broker.
  • the trigger mode can be different from the trigger mode for the AS. For example, when using the Service Broker name, the S-CSCF no longer triggers the iFC.
  • the service trigger data to the Service Broker includes a Service Broker address.
  • the determined Service Broker trigger mode is triggered by using iFC, and the server address in the iFC data configuration is configured as the selected Service Broker address.
  • the trigger mode can be passed to the Service Broker trigger point, the user equipment UE, the user subscription database, or the Service Broker selection database.
  • the above entities can be further saved after receiving.
  • Direct transfer trigger mode for example, when Service Broker selects the trigger point and the Service Broker trigger point is in the same physical entity, SBSF selects the response message through Service Broker.
  • the broker name is sent to the S-CSCF (Service Broker trigger point); the indirect transfer trigger mode, for example, when the Service Broker selects the trigger point and the Service Broker trigger point is located in a different physical entity,
  • the SBSF sends the Service Broker name to the I-CSCF (Service Broker Selection Trigger Point) via the Service Broker Select Response message, and the I-CSCF passes the Service Broker name to the S-CSCF (Service Broker Trigger Point). Further, the S-CSCF saves the Service Broker name.
  • the S-CSCF can directly process the communication of the user according to the saved service.
  • the Broker name is triggered to the selected Service Broker.
  • the process by which the SBSF passes the triggering mode to the user equipment UE may be, for example, the SBSF returns the Service Broker name to the UE by a registration response message. Further, the UE saves it Then, the UE subsequently initiates the session message carrying the Service Broker name, and the S-CSCF triggers the specified Service Broker according to the Service Broker name.
  • the process by which the SBSF passes the trigger mode to the HSS may be:
  • the SBSF transmits an iFC rule (service trigger data) configured with Service Broker information to a user subscription database, the user subscription database stores the iFC rule, and the iFC rule It can be updated to the S-CSCF or downloaded actively by the S-CSCF.
  • the user is updated to the S-CSCF.
  • the S-CSCF has previously downloaded the user configuration data, and the user configuration data can be updated; the S-CSCF actively downloads, for example, the unregistered user reselects the S- when registering.
  • CSCF the new S-CSCF downloaded data includes the trigger mode iFC data to Service Broker.
  • the S-CSCF subsequently processes the communication of the user, it may directly trigger to the selected Service Broker according to the iFC rule.
  • the process by which the SBSF passes the trigger mode to the Service Broker selection database may be, for example, the SBSF sends the Service Broker name to the Service Broker selection database, the Service Broker selects the database to save it, and the trigger mode can be saved as the Service Broker selection data. Part of it, such as the name of the Service Broker that is stored in the Service Broker capability requirement.
  • A4 trigger the current communication to the selected Service Broker; the pre-communication triggers to the selected Service Broker, or, after the Service Broker trigger point gets the trigger mode to the Service Broker, triggers the current communication to the selected Service Broker. .
  • A5. Re-initiate the Service Broker selection process when it detects that the selected Service Broker is unavailable or insufficient.
  • SBSF It can be detected by SBSF that Service Broker is not available. For example, if SBSF forwards the message of Service Broker trigger point to Service Broker, Service Broker does not respond. At this time, SBSF detects that the trigger to Service Broker failed.
  • the Service Broker trigger point detects that Service Broker is not available.
  • the Service Broker trigger point is S-CSCF
  • the S-CSCF can trigger to Service Broker according to the Service Broker name, the Service Broker is not responding, and the Service Broker trigger point is detected when J3 ⁇ 4 Trigger to Service Broker failed;
  • Service Broker detects that Service Broker is not available, such as setting up a monitoring server independently, which sends a handshake with Service Broker.
  • Information to detect the availability of Service Broker it can be set separately, can be combined with SBSF, can be combined with Service Broker to select trigger points, or can be combined with Service Broker trigger points.
  • Detection of Service Broker availability is done during the Service Broker selection process and/or after the Service Broker is selected.
  • Service Broker When Service Broker is detected to be unavailable, it can be triggered by Service Broker or Service
  • the Broker selects the trigger point to re-request the SBSF for the Service Broker selection process.
  • the Service Broker selection process can also be re-initiated by the SBSF, as illustrated by the following examples:
  • the Service Broker forwards the message of the Service Broker trigger point to the Service Broker, the Service Broker is not responding, at which point the SBSF re-initiates the Service Broker selection process; or the SBSF subscribes to the selected Service Broker availability information to the entity monitoring the Service Broker availability.
  • the entity notifies the SBSF that the SBSF re-initiates the Service Broker selection process;
  • the Service Broker trigger point is S-CSCF
  • the S-CSCF triggers the Service Broker according to the Service Broker name
  • the Service Broker does not respond.
  • the S-CSCF requests the SBSF to perform the Service Broker selection process.
  • the Service Broker selects the trigger point to know that the Service Broker selected for the user is unavailable, and requests to re-subscribe the Service Broker. If the registered service user is the called user, and the SBSF and the HSS are in the same physical entity, the HSS to the I- CSCF (Service Broker Select Trigger Point) returns the Service Broker previously selected for this user. The I-CSCF detects that the previously selected Service Broker is unavailable and re-initiates the Service Broker selection process.
  • the I-CSCF Service Broker Select Trigger Point
  • Service Broker selects the trigger point and Service Broker are located in the same physical entity.
  • Service Broker performs message processing and finds that the service processing capability provided by itself is insufficient, it will also request the trigger point to request Service Broker selection through Service Broker.
  • Service Broker For example, the user uses non-signed contract.
  • the service broker cannot process the interaction between the non-contracted service and the original service of the user, and triggers the service proxy selection process.
  • the selected Service Broker receives a new service request, for example, the new service requested by the user is an unsigned service, it may cause a business interaction problem with the original contracted service of the user, when selected
  • the Service Broker cannot provide the required business interaction processing capability
  • the Service Broker that satisfies the user's business interaction requirements will be selected according to the selection data and the information in the session. For example, the user on the selected Service Broker has triggered the Game service, and then the user requests to call the IPTV service.
  • the Service Broker cannot handle the interaction between the IPTV service and the Game service, and then re-selects the new Service Broker according to the selection data and the session information. .
  • the information in the session may include: a Service Broker name carried in the signaling message, for example, the user equipment UE carries the Service Broker name in the sent message; the service information that the user has already invoked, for example, which services have been called; the user will call Business information, such as user requests to use non-contracted services.
  • the SBSF is an independent functional entity
  • the Service Broker trigger point and the Service Broker selection trigger point are all S-CSCF
  • the user subscription database and the Service Broker selection database are all HSS
  • the SBSF obtains the Service Broker selection data through the Sh interface.
  • This embodiment describes the corresponding service proxy selection process in the case where the called user of the service receives the SIP INVITE invite message when it is not registered. Please refer to Figure 3, including the steps:
  • the S-CSCF receives an INVITE invite message called an unregistered user
  • the S-CSCF After receiving the INVITE message, the S-CSCF obtains the configuration of the called user from the HSS, and checks the iFC trigger data in the SFC.
  • an iFC configuration data triggered to the SBSF is added to the user configuration of the user, and the SPT description part of the iFC data includes at least ⁇ Method>INVITE ⁇ /Method>, ⁇ SessionCase>2 ⁇ /SessionCase>, that is, the SBSF address in this embodiment is determined by iFC data.
  • the S-CSCF triggers the INVITE message to the SBSF according to the iFC data.
  • the S-CSCF sends an INVITE message to the SBSF, that is, a Service Broker selection request message.
  • the S-CSCF triggers a message on the SBSF to indicate the service direction, for example.
  • the SBSF address is configured as the SBSF address of the called service in the above iFC.
  • the SBSF sends a Sh interface message user data request (UDR) to the HSS.
  • the interface between the SBSF and the HSS is a Sh interface.
  • the SBSF and HSS communicate using the Diameter protocol.
  • the SBSF receives the INVITE message sent by the S-CSCF to perform the Service Broker selection, and the SBSF sends the Sh interface message user data request (UDR) to the HSS, which carries the User-Identity attribute-value pair (AVP), and the value is The public identifier of the service user, the Data-Reference attribute-value pair, the value is the request transparent data (RepositoryData), the Service-Indication attribute-value pair, and the value corresponds to the Service Broker selection data on the HSS. Transparent data index value.
  • the HSS responds to the SBSF with a Sh-interface message User Data Response (UDA), carrying a User-Data attribute-value pair, where the data is the Service Broker selection data.
  • UDA User Data Response
  • the SBSF determines the Service Broker serving the user according to the received Service Broker selection data and the Service Broker selection algorithm; the Service Broker selection algorithm refers to, for example, the service capability of the Service Broker according to the user and the service capability that the Service Broker can provide in the network.
  • the degree of matching is chosen to select Service Broker, etc., for example, to prioritize Service Broker that meets all required competency requirements and provides the most optional capability requirements.
  • SBSF forwards the INVITE message to the determined Service Broker, Service
  • the Broker responds to the 200 OK message and forwards it to the S-CSCF, and then forwards it to the user, and the selected Service Broker can serve the user;
  • SBSF may increase iFC data by using SBSF using Simple Network Management Protocol (SNMP) as a Human Machine Interaction Language (MML) client. Add iFC data that is triggered to Service Broker using the MLS commands supported by HSS.
  • SNMP Simple Network Management Protocol
  • MML Human Machine Interaction Language
  • the HSS returns a success response message to the SBSF;
  • the HSS detects that the user configuration changes, and actively updates the user configuration on the S-CSCF through the Cx interface push configuration request (PPR) command, which carries the iFC data configuration triggered by the foregoing steps to the Service Broker.
  • PPR push configuration request
  • the Cx interface is defined as the interface between the I-CSCF and the HSS or between the S-CSCF and the HSS.
  • the S-CSCF returns a push configuration response (PPA) to the HSS.
  • PPA push configuration response
  • the S-CSCF when the S-CSCF receives the subsequent communication message of the user, it can directly directly report the new iFC data. Triggered to the corresponding Service Broker.
  • the SBSF is an independent functional entity
  • the Service Broker trigger point and the Service Broker selection trigger point are both S-CSCF
  • the user subscription database and the Service Broker selection database are all HSS.
  • This embodiment describes the corresponding service agent selection process when the S-CSCF receives the SIP REGISTER registration request from the user and the first Service Broker selected by the SBSF is unavailable. Please refer to Figure 4, including the steps:
  • the CI, S-CSCF receives the SIP REGISTER registration request from the user;
  • the S-CSCF responds to the user with a 200 OK message
  • S-CSCF obtains the user configuration on the HSS, and checks the iFC trigger data in the user subscription database;
  • S-CSCF sends a SIP REGISTER registration request to the SBSF;
  • SBSF and HSS communicate using the Generic User Profile (GUP) protocol.
  • GUP Generic User Profile
  • the SBSF sends a GUP Query message, where the Resource Identity parameter populates the public identity of the user requesting the query, and the Data references parameter indicates that the request is Service. Broker selects data;
  • the HSS sends a GUP Query Response response message to the SBSF, where the service broker selects the data of the requesting user;
  • the SBSF determines the Service Broker serving the user according to the received Service Broker selection data and the Service Broker selection algorithm
  • Service Broker selection algorithm refers to, for example, selecting Service Broker according to the user's Service Broker capability requirements and the matching degree of the capabilities that Service Broker can provide, that is, prioritizing Service Broker that satisfies all required capability requirements and provides the most optional capability requirements. .
  • the service identified by the embodiment as a user is Service Broker 1.
  • SBSF sends a SIP REGISTER registration request to the identified Service Broker 1;
  • SBSF forwards SIP REGISTER registration to identified Service Broker 2 Request
  • Service Broker 2 responds to the 200 OK message and forwards it to the S-CSCF, and then forwards it to the user, and the selected Service Broker 2 can serve the user;
  • the HSS actively updates the user configuration on the S-CSCF through the Cx interface push configuration request (PPR) command, where the Service Broker name determined by the foregoing steps is carried;
  • PPR push configuration request
  • S-CSCF returns the push configuration response (PPA) to the HSS.
  • PPA push configuration response
  • the S-CSCF when the S-CSCF receives the subsequent communication message of the user, it can directly trigger to the corresponding Service Broker according to the name of the saved Service Broker.
  • the Service Broker selection trigger point is I-CSCF
  • the Service Broker trigger point is S-CSCF
  • the I-CSCF has the SBSF function, the S-CSCF and the Service Broker function are combined, the user subscription database and the Service Broker selection database are both
  • the SBSF function of the I-CSCF is to select the S-CSCF for the user to meet its business requirements and built-in Service Broker functionality.
  • the I-CSCF receives the SIP REGISTER request from the user, and the corresponding service agent selection process is shown in Figure 5, including the steps:
  • I-CSCF receives the user's SIP REGISTER registration request
  • the I-CSCF sends a Cx interface message user authentication request (UAR) to the HSS.
  • UAR user authentication request
  • the HSS sends the S-CSCF capability request to the I-CSCF through the Cx interface message user authentication response (UAA);
  • the HSS Since the Service Broker function is combined with the S-CSCF function, the HSS describes the user's Service Broker capability requirements in the S-CSCF capability requirements.
  • I-CSCF selects the S-CSCF that meets the user requirements
  • the I-CSCF is locally configured with information such as the capabilities provided by the S-CSCF in the network, and based on the information. And the S-CSCF capability sent by the HSS requires S-CSCF selection. At this time, the selected S-CSCF can meet the Service Broker capability requirements of the user at the same time.
  • the I-CSCF sends a SIP REGISTER registration request to the determined S-CSCF;
  • the S-CSCF sends a Cx interface message server assignment request (SAR) to the HSS;
  • SAR Cx interface message server assignment request
  • the HSS sends a Cx interface message server assignment response (SAA) to the S-CSCF;
  • SAA Cx interface message server assignment response
  • the S-CSCF responds to the I-CSCF with a 200 OK message and is forwarded to the user by the I-CSCF. It should be noted that, in this embodiment, the S-CSCF and the Service Broker are combined, and the trigger mode data saved to the Service Broker may not be needed.
  • Service Broker trigger point and the Service Broker selection trigger point are both
  • the S-CSCF, and the S-CSCF is combined with the SBSF function.
  • the user subscription database and the Service Broker selection database are both HSS.
  • the S-CSCF receives the SIP REGISTER request from the user, and the corresponding service agent selection process is shown in Figure 6, including the steps:
  • S-CSCF receives the user's SIP REGISTER registration request
  • the S-CSCF sends a Cx interface message server assignment request (SAR) to the HSS;
  • SAR Cx interface message server assignment request
  • the HSS sends a Cx interface message server assignment response (SAA) to the S-CSCF, where carrying an extended AVP indication requires Service Broker selection;
  • SAA Cx interface message server assignment response
  • the S-CSCF responds to the 200 OK message to the user
  • the S-CSCF sends a Service Broker selection data request message to the HSS, where the message is a Cx interface extension message;
  • the HSS carries the Service Broker selection data in the Service Broker selection data response message, and the message is a Cx interface extension message;
  • S-CSCF selects a Service Broker according to Service Broker selection data and Service Broker selection algorithm, and saves the Service Broker name;
  • the S-CSCF can directly contact the corresponding Service Broker according to the Service Broker name when receiving the subsequent communication message of the user.
  • S-CSCF sends a SIP REGISTER registration request to the identified Service Broker
  • Service Broker responds to the S-CSCF with a 200 OK message.
  • the S-CSCF can also re-trigger the Service Broker selection process when the selected Service Broker is unavailable. For example, the S-CSCF processes the trigger of the Service Broker.
  • S- CSCF reselects other available Service Brokers.
  • step E4 can also be placed after E9, that is, the S-CSCF can select the selected service.
  • the broker name is delivered to the user equipment UE by extending the 200 OK message. For example, a header field is added to carry the service broker name, and the UE saves it after receiving it, and carries the saved Service Broker name in the session message initiated by the subsequent UE, so that the S-CSCF When receiving the subsequent communication message of the user, it can be directly triggered to the corresponding Service Broker according to the Service Broker name. In this case, the S-CSCF in Step E7 may not save the Service Broker name, because the UE may subsequently carry the Service Broker name for the user.
  • the fifth embodiment is described below.
  • the Service Broker selection trigger point is I-CSCF
  • the Service Broker trigger point is S-CSCF.
  • the I-CSCF has the SBSF function, and the user subscription database and the Service Broker selection database are all HSS.
  • the I-CSCF receives the SIP REGISTER request from the user, and the corresponding business agent selection process is shown in Figure 7, including the steps:
  • I-CSCF receives the user's SIP REGISTER registration request
  • the I-CSCF sends a Cx interface message user authentication request (UAR) to the HSS;
  • UAR user authentication request
  • the HSS returns a Cx interface message user authentication response (UAA) to the I-CSCF, where carrying an extended AVP indication requires Service Broker selection;
  • UAA Cx interface message user authentication response
  • the I-CSCF sends a Service Broker selection data request message to the HSS, where the message is a Cx interface extension message.
  • the HSS carries the Service Broker selection data in the Service Broker selection data response message returned to the I-CSCF, where the message is a Cx interface extension message;
  • I-CSCF selects a Service Broker according to Service Broker selection data and Service Broker selection algorithm, and saves the Service Broker name;
  • the I-CSCF when the I-CSCF receives the subsequent communication message of the user, it can be triggered to the corresponding Service Broker through the S-CSCF according to the Service Broker name.
  • F7 and I-CSCF After selecting Service Broker, F7 and I-CSCF send the Service Broker name to the S-CSCF through the SIP REGISTER message.
  • the Service Broker name is here to extend the SIP message, for example, adding a new header field to carry this information.
  • the S-CSCF saves the Service Broker name after receiving the message, and responds to the I-CSCF with a 200 OK message;
  • the I-CSCF forwards the 200 OK message to the user
  • the S-CSCF checks the saved Service Broker name
  • S-CSCF triggers a SIP REGISTER message to the selected Service Broker according to the saved Service Broker name
  • the selected Service Broker responds to the S-CSCF with a 200 OK message.
  • Embodiment 6 is described below.
  • the Service Broker trigger point and the Service Broker selection trigger point are both S-CSCF
  • the user subscription database and the Service Broker selection database are all HSS
  • the HSS has the SBSF function.
  • the S-CSCF receives the SIP REGISTER request from the user, and the corresponding service agent selection process is shown in Figure 8.
  • S-CSCF receive the SIP REGISTER registration request from the user
  • the S-CSCF sends a Cx interface message server assignment request (SAR) to the HSS;
  • SAR Cx interface message server assignment request
  • HSS receives the Cx interface message server assignment request (SAR) sent by the S-CSCF and finds that the user service request is for Service Broker selection. At this time, the Service Broker selection process is initiated, a Service Broker is selected, and the S-CSCF is determined to the Service.
  • the trigger mode of the broker such as iFC configuration or Service Broker name.
  • HSS will trigger the Service Broker, for example, the iFC configuration or Service Broker name triggered to Service Broker will be sent back to the S-CSCF through the Cx interface message server assignment response (SAA);
  • SAA Cx interface message server assignment response
  • the S-CSCF sends a 200 OK message to the user
  • G7 S-CSCF check the saved iFC configuration or Service Broker name
  • S-CSCF triggers iFC to Service Broker according to the saved Service Broker name Configuring or triggering a SIP REGISTER message to the selected Service Broker;
  • the selected Service Broker responds to the S-CSCF with a 200 OK message.
  • the Service Broker re-election process can be initiated, and the Service Broker selection process is re-requested to the HSS.
  • the HSS re-selects Service Broker based on the Service Broker selection data and the Service Broker selection algorithm.
  • the seventh embodiment is described below.
  • the monitoring of the service broker has been set to the S-CSCF by the separate Service Broker availability monitoring server.
  • the user subscription database and the Service Broker selection database are all HSS, and the SBSF is independently set.
  • the corresponding Service Broker reselection process please refer to Figure 9, including the steps:
  • SBSF subscribes to the Service Broker Availability Monitoring Server for available status information for Service Brokers that have been selected for the user;
  • the Service Broker Availability Monitoring Server and the selected Service Broker send handshake messages to each other. For example, the status of the Service Broker can be monitored by sending OPTIONS messages to each other.
  • Service Broker Availability Monitoring Server finds that the monitored Service Broker is unavailable, for example, does not receive a handshake message within a certain period of time, and notifies the SBSF through a NOTIFY message;
  • the subsequent steps are for the SBSF to request the Service Broker to select data from the HSS via the Sh interface for Service Broker reselection and to update the trigger data of the S-CSCF to the selected Service Broker.
  • the SBSF sends a Sh interface message user data request (UDR) to the HSS;
  • UDR Sh interface message user data request
  • the SBSF sends a Sh interface message user data request (UDR) to the HSS, which carries the user identifier
  • User-Identity attribute-value pair (AVP), the value is the public identifier of the service user, the data reference (Data-Reference) attribute-value pair, the value is the request transparent data (RepositoryData), the service indication (Service-Indication)
  • the attribute-value pair which corresponds to the transparent data index value of the Service Broker selection data on the HSS.
  • HSS responds to the SBSF with the Sh interface message User Data Response (UDA), carrying the User-Data attribute-value pair, where the data is Service Broker selection data.
  • UDA User Data Response
  • the SBSF determines the Service Broker serving the user according to the received Service Broker selection data and the Service Broker selection algorithm
  • H9, SBSF and HSS communication request to add an iFC data that triggers to Service Broker or
  • H10 HSS returns a success response message to the SBSF
  • the Cx interface push configuration request (PPR) command actively updates the user configuration on the S-CSCF, which carries the iFC data configuration or Service Broker name triggered by the foregoing steps to the Service Broker.
  • PPR push configuration request
  • S-CSCF saves new iFC data or Service Broker name
  • S-CSCF sends a push configuration response (PPA) to the HSS, indicating that the update is successful.
  • PPA push configuration response
  • Embodiment 8 is described below.
  • the Service Broker trigger point and the Service Broker selection trigger point are all S-CSCF, and the user subscription database and the Service Broker selection database are both HSS and SBSF are set independently.
  • This embodiment describes the process in the case where the S-CSCF receives the unsigned service of the user.
  • the S-CSCF receives the user's unsigned IPTV service request and triggers the request to select Service Broker on the SBSF.
  • Figure 10 including the steps:
  • the S-CSCF receives the INVITE message of the user and requests to invoke the IPTV service.
  • the S-CSCF After receiving the INVITE message, the S-CSCF obtains the user file from the HSS, and performs an iFC trigger check.
  • the S-CSCF triggers the INVITE message to the SBSF according to the iFC data.
  • the SBSF sends a Sh interface message user data request (UDR) to the HSS;
  • the User Data Request (UDR) carries the User-Identity attribute-value pair (AVP), which is the public identifier of the service user, the Data-Reference attribute-value pair, and the value is the request transparent data. (RepositoryData), Service-Indication attribute-value pair, which corresponds to the transparent data index value of the Service Broker selection data on the HSS.
  • AVP User-Identity attribute-value pair
  • RepositoryData Service-Indication attribute-value pair
  • the HSS responds to the SBSF with the Sh interface message User Data Response (UDA), carrying the user data.
  • UDA User Data Response
  • (User-Data) attribute-value pair where the data is the Service Broker selection data.
  • the SBSF determines the Service Broker serving the user according to the received Service Broker selection data and the session information contained in the user-sent message, and the session information refers to, for example, a service requested by the user to be called.
  • the SBSF will send the INVITE message carrying the route header field to the Service Broker.
  • the S-CSCF routes an INVITE message to the determined Service Broker according to the Route header field, and the Service Broker responds to the S-CSCF by sending a 200 OK message to the S-CSCF, and then the selected Service Broker can be User service.
  • the SBSF of this embodiment may also be combined with the Service Broker.
  • the selected Service Broker may be the SBSF itself.
  • Embodiment IX is described below.
  • the Service Broker trigger point and the Service Broker selection trigger point are Service Brokerl
  • the user subscription database and the Service Broker selection database are both HSS
  • the Service Brokerl has the SBSF function.
  • This embodiment describes that the user has triggered the game Game service on Service Broker1, and then the user requests to call the unsigned IPTV service.
  • Service Brokerl cannot handle the interaction between the IPTV service and the Game service, and re-selects the new Service Broker. See Figure 11, including the steps:
  • J3, Service Brokerl receives the INVITE message of the user, which contains the IPTV service call request;
  • the HSS responds to the SBSF with a Sh interface message User Data Response (UDA), which carries the Service Broker selection data and a list of Service Broker service interaction processing capabilities in the network;
  • UDA User Data Response
  • Service Brokerl selects data according to the obtained Service Broker, in the above network Service Broker business interaction processing capability list and the situation that the user has called the Game service and will invoke the IPTV service, select an available Service Broker2 for the user, and save the Service Broker name;
  • Service Brokerl sends the INVITE message to Service Broker2, and the user's IPTV service is triggered by Service Broker1 to Service Broker2.
  • Embodiment 10 is described below.
  • the Service Broker trigger point and the Service Broker selection trigger point are both Service Broker1
  • the user subscription database is HSS
  • the Service Broker selects the database independent setting
  • the SBSF is independently set.
  • Service Brokerl cannot handle the interaction between the IPTV service and the Game service, and re-selects the new Service Broker. For details, see the procedure. Figure 12, including the steps: Kl, Service Brokerl receives the user's INVITE message, which contains a Game service call request;
  • Service Brokerl receives the INVITE message of the user, which contains the IPTV service call request;
  • Service Broker1 sends an INVITE message carrying the service broker selection request indication to the SBSF, which also carries a service capability requirement, indicating that the interaction processing capability of the IPTV and Game services needs to be provided;
  • SBSF selects a database to send a Service Broker selection data request message to the Service Broker
  • the Service Broker selection database returns a Service Broker selection data response message to the SBSF, which carries the Service Broker selection data and a list of Service Broker service interaction processing capabilities in the network;
  • K7, SBSF selects an available Service Broker2 for the user according to the obtained Service Broker selection data, the Service Broker business interaction processing capability list in the above network, and the user has invoked the Game service and will invoke the IPTV service, and saves the Service Broker2 name.
  • K8, SBSF carries Service Broker2 name to Service Broker1 through 200 OK message
  • K9, Service Brokerl sends INVITE message to Service Broker2, and the user's IPTV service is triggered by Service Broker1 to Service Broker2.
  • the present invention provides a network system that can provide service agent selection.
  • the network system includes a user subscription database 100, a Service Broker selection trigger point 200, a service agent selection function SBSF 300, a Service Broker selection database 400, a Service Broker trigger point 500, a Service Broker 600, a monitoring server 700, and a user equipment. 800.
  • the Service Broker Selection Trigger Point 200, Service Agent Selection Function SBSF 300 and Service Broker Selection Database 400 are the primary entities of the present invention relative to existing networks.
  • the user subscription database 100 stores subscription data of the user, such as iFC data, accounting server address data, and the like. Further, the user subscription database 100 may send a trigger point to the Service Broker selection triggering point 200 to include the trigger to the service agent selection function SBSF indication or contain the service. The agent selects the indicated message. All types of user subscription data can be stored on the same physical network element entity or on different physical network element entities.
  • the user subscription database can be a User Home Server (HSS) or a non-HSS data server.
  • Service Broker Select Trigger Point 200 provides the ability to trigger the Service Broker selection process.
  • the Service Broker Selection Trigger Point 200 can be a Serving Call Session Control Function (S-CSCF) or a Query Call Session Control Function (I-CSCF), or even a Service Broker.
  • Service Broker selects the trigger point 200 in the case of Service Broker, such as when Service Broker has insufficient business capabilities to select another Service Broker.
  • the Service Broker selection trigger point 200 includes a request unit 201, further including a third reselection trigger unit 202, and the request unit 201 is configured to request the service agent selection function SBSF 300 to perform service proxy selection, such as receiving a trigger to the service.
  • the agent selection function SBSF indicates or contains a message for performing the service agent selection indication, and then requests the service agent selection function SBSF 300 to perform service agent selection;
  • the third reselection trigger unit 202 is configured to be unavailable in the selected Service Broker. Or trigger a reselection of the business agent process when the ability is insufficient.
  • the selected Service Broker is not available, which means that Service Broker does not respond when triggered to the selected Service Broker.
  • the SBSF 300 provides Service Broker selection capabilities, such as the ability to dynamically select Service Broker for users based on requirements. Service Agent Selection Function The SBSF 300 can be physically set up separately or in combination with any of the other entities mentioned above.
  • the service proxy selection function SBSF 300 includes a receiving unit 301, a first selecting unit 302, and further includes a triggering manner determining unit 303, and further includes a second triggering unit 304, and further includes a first reselection.
  • the trigger unit 305 further includes a second selection unit 306.
  • the receiving unit 301 is configured to receive the request of the requesting unit 201 of the Service Broker selection trigger point 200.
  • the first selecting unit 302 communicates with the service agent selection database 400 according to the request received by the receiving unit 301, and obtains a service agent selection.
  • the second selecting unit 306 is configured to select, according to the selected service data, when the selected service broker cannot meet the service proxy capability requirement caused by the new service request. And session information Wait for other Service Brokers. For example, the user of the selected service agent Service Broker has triggered the game Game service, and then the user requests to call the unsigned IPTV service. The Service Broker cannot handle the interaction between the IPTV service and the Game service, and then selects according to the selection data and the session information. Other Service Broker.
  • the Service Broker selection database 400 is for providing Service Broker selection data, and the first selection unit 302 and the second selection unit 306 of the service agent selection function SBSF 300 may acquire selection data from the Service Broker selection database 400, and select the eligible data according to the selection data. Service Broker.
  • Service Broker selection data can include the following information:
  • the Service Broker selection data includes at least the service agent capability requirements of the user service and the service capabilities of the service agent, that is, a, Service Broker capability requirements of the user service.
  • Service Broker can The force requirements include mandatory capability requirements, optional capability requirements, and may include the Service Broker name, which may be the address of the Service Broker.
  • the Service Broker capability request carries the Service Broker name
  • the registration message processing flow carries the Service Broker name that is temporarily selected for the unregistered user, that is, the Service Broker address; b.
  • the capability that the Service Broker in the network can provide.
  • the Service Broker selection data may also include one or more of the following information:
  • the service broker trigger point and the topology connection relationship of the Service Broker in the network such as the Service Broker trigger point and the Service Broker connection '1', etc.;
  • Service Broker selection database 400 may be combined with the user subscription database 100 or may be combined with the business agent selection function SBSF 300. It should be noted that all types of Service Broker selection data can be stored in the same physical network element entity, for example, in the Service Broker selection database 400, but it is not limited thereto, and can also be stored in different physical network element entities. on.
  • the Service Broker trigger point 500 provides the ability to trigger communication to the Service Broker 600, which may be the Service Call Session Control Function (S-CSCF) or the Service Broker Service Broker trigger point is Service Broker. For example, if the Service Broker business capability is insufficient, it will be triggered to other Service Brokers that can provide the required capabilities.
  • S-CSCF Service Call Session Control Function
  • Service Broker Service Broker trigger point is Service Broker. For example, if the Service Broker business capability is insufficient, it will be triggered to other Service Brokers that can provide the required capabilities.
  • the Service Broker trigger point 500 includes a first trigger unit 501, and further includes a second reselection trigger unit 502.
  • the first triggering unit 501 is configured to trigger the current communication to the selected Service Broker after acquiring the triggering mode. Further, the first triggering unit 501 obtains the triggering manner and may store the second triggering unit 502. , used to trigger the reselection of the business agent process when the selected Service Broker is unavailable or insufficient.
  • Service Broker 600 is used to provide enhanced business triggering capabilities, business mixing capabilities and business delivery One or more of the interoperability capabilities.
  • Service triggering capability can be understood as the ability to trigger a service according to requirements.
  • the service hybridization capability can be understood as the ability to mix different services together to provide new services.
  • the business interaction processing capability can be understood as management when a business conflict occurs. ability.
  • Service Broker 600 can be a separate physical network element entity, or it can be the same physical network element entity as Service Broker trigger point 500 or Service Broker selection trigger point 200.
  • the monitoring server 700 is configured to monitor the status of the selected service agent.
  • the monitoring server 700 monitors the status of the Service Broker 600 by sending a handshake message to the selected Service Broker 600, for example, by sending SIP OPTIONS messages to each other.
  • the monitoring server 700 does not receive the handshake message for a period of time, the monitoring server notifies the system.
  • Other entities such as Service Broker 600 selected by the Service Agent Selection Function SBSF 300 are not available.
  • the monitoring server 700 may not be needed when the service agent selection function SBSF 300 or the Service Broker trigger point 500 detects that the selected service agent is unavailable.
  • the service agent selection function SBSF 300 forwards the message of Service Broker trigger point 500 to Service Broker 600, and Service Broker 600 does not respond. At this time, the service agent selection function SBSF 300 detects that the trigger to Service Broker 600 fails, and Service Broker 600 is unavailable. .
  • Service Broker trigger point 500 is triggered on Service Broker 600 according to the trigger mode. Service Broker 600 has no response. At this time, Service Broker trigger point 500 detects that the trigger to Service Broker 600 fails, and Service Broker 600 is unavailable.
  • the user equipment UE 800 is configured to initiate and receive a communication request. Further, the user equipment selection function SBSF 300 can be used to store a trigger mode. For example, the service proxy selection function SBSF 300 returns the trigger mode to the user equipment UE 800 by using a registration response message. The user equipment UE 800 saves it, and the user equipment UE 800 subsequently initiates a session message carrying a trigger mode, and the Service Broker trigger point 500 is triggered to the designated Service Broker according to the trigger mode.
  • the present invention mainly adds a Service Broker selection trigger point 200, a service agent selection function SBSF 300, and a Service Broker selection database 400, correspondingly, an interface is added for connection.
  • the Service Broker selection trigger point 200 and the service agent selection function SBSF 300 employ an E1 interface, which is mainly used to trigger the Service Broker selection process of the service agent selection function SBSF 300 and the subsequent interaction process.
  • the E1 interface protocol includes at least one of the following: SIP protocol, Diameter protocol, Hypertext Transfer Protocol (HTTP) protocol, internal interface protocol, when service agent selection function
  • HTTP Hypertext Transfer Protocol
  • the SBSF 300 and Service Broker can use the internal interface protocol when the trigger point 200 is located in the same physical entity.
  • the SBSF 300 and Service Broker selection database 400 uses the E4 interface, which is used to request and pass Service Broker selection data.
  • the E4 interface protocol includes at least one of the following: Diameter protocol, Universal User Configuration (GUP) protocol, SIP protocol, Hypertext Transfer Protocol (HTTP) protocol, internal interface protocol, when the service agent selection function SBSF 300 and the Service Broker selection database 400 are located.
  • GUP Universal User Configuration
  • SIP Session Transfer Protocol
  • HTTP Hypertext Transfer Protocol
  • the internal interface protocol can be used when the same physical entity.
  • the SBSF 300 and Service Broker 600 use the E2 interface for the Service Agent Selection function.
  • the SBSF 300 triggers the communication to the Service Broker 600, such as the Service Agent Selection Function.
  • the SBSF 300 forwards the registration message to the Service Broker 600.
  • the E2 interface protocol includes at least one of the following: SIP protocol, internal interface protocol, when the service agent selection function SBSF 300 and Service Broker 600 are located in the same physical entity, the internal interface protocol can be used.
  • the service agent selection function SBSF 300 and the user subscription database 100 use the E3 interface, which is used for the service agent selection function.
  • the SBSF 300 updates the trigger mode data of the Service Broker trigger point 500 to the Service Broker 600.
  • the E3 interface protocol includes at least one of the following: Simple Network Management Protocol (SNMP), Diameter protocol, Universal User Configuration (GUP) protocol, SIP protocol, Hypertext Transfer Protocol (HTTP) protocol, internal interface protocol, when the service agent selects the function SBSF
  • the internal interface protocol can be used when the 300 is in the same physical entity as the user subscription database 100.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Description

业务代理选择方法及提供业务代理选择的网络系统
本申请要求于 2006 年 10 月 10 日提交中国专利局、 申请号为 200610149614.1、 发明名称为"业务代理选择方法及提供业务代理选择的网络 系统"的中国专利申请的优先权， 其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术领域，尤其涉及业务代理选择方法及提供业务代理选 择的网络系统。
背景技术
IP 多媒体子系统（IMS ) 由第三代移动通信标准化伙伴项目 （3GPP )在 版本 5中引入， 它是一个基于会话初始化协议（SIP ) 的体系， 其会话层和业 务层分离， 并且提供开放业务接入（OSA )这一类开放的接口， 有利于第三方 进行业务开发。 同时， 运营商也希望能够对已有的业务进行整合， 提供新的混 合业务。 可以预见， 未来的网络内用户可以使用的业务会越来越丰富， 而业务 冲突问题也会越来越突出， 这些特点对于业务提供方式提出了全新的要求，在 这种背景下产生了业务代理（ Service Broker )技术。
Service Broker 主要实现 IMS 网络中的业务能力交互管理功能。 目前 Service Broker技术仍然处于研究阶段， 各个标准中 Service Broker有关的研究 项目研究范围各不相同。 正是由于各个标准中对于 Service Broker的概念和作 用范围没有统一的定义，目前各个厂家实现的 Service Broker功能也不尽相同， 例如有的厂家提供的 Service Broker具备业务混合能力、 业务交互管理能力， 有的厂家提供的业务代理实体还具备增强的业务触发能力。此外， 即便是同类 功能例如业务交互管理能力，各个厂家实现的能力也不会完全一致， 例如有的 厂家支持语音呼叫类业务与交互式网络电视 IPTV业务的交互， 有的厂家就不 支持。
目前在 Service Broker技术的运用中， 可以用配置触发数据的方式来指定
Service Broker , 例如 Service Broker触发点可以通过获取用户签约数据库的初 始过滤规则（ iFC )配置触发到特定的 Service Broker上，则特定的 Service Broker 为用户提供服务。 Service Broker 触发点可以是服务呼叫会话控制功能 ( S-CSCF )。 但釆用这种方式只是一种静态的配置选择方式， 不能实现灵活的 负载均衡， 不能提供动态的 Service Broker选择， 并且在指定的 Service Broker 故障时也不能选择其它可用的 Service Broker; 此外， 用户在注册以后也可能 使用非签约类业务，而所述非签约业务可能会与用户签约业务之间存在业务交 互问题， 如果之前选定的 Service Broker不能处理该非签约业务与用户已使用 的业务间的业务交互， 则就存在选择新的 Service Broker的问题。 因此这种静 态的业务代理选择方式的应用具有一定局限性，运营商出于网络运营考虑， 希 望能有一种为网络提供更灵活的动态的业务代理选择方式。
发明内容
本发明要解决的技术问题是提供一种业务代理选择方法及提供业务代理 选择的网络系统，本发明能够实现在网络中灵活的动态选择满足用户业务能力 要求的业务代理。
本发明的目的是通过以下技术方案实现的：
一种业务代理选择方法， 包括：
业务代理选择功能接收业务代理选择触发点发送的业务代理选择请求； 所述业务代理选择功能根据所述业务代理选择请求，从业务代理选择数据 库中获取业务代理选择数据；
所述业务代理选择功能根据所述业务代理选择数据选择业务代理。
一种提供业务代理选择的网络系统， 包括：
业务代理选择触发点，用于请求业务代理选择功能 SBSF进行业务代理选 择；
业务代理选择功能 SBSF,用于接收所述业务代理选择触发点的所述请求； 根据所述请求与业务代理选择数据库通信， 获取业务代理选择数据，根据所述 选择数据选择业务代理；
业务代理选择数据库， 用于提供选择数据。
一种业务代理选择触发点， 包括：
请求单元， 用于请求业务代理选择功能 SBSF进行业务代理选择。
一种业务代理触发点， 包括：
第一触发单元， 用于请求业务代理选择功能 SBSF进行业务代理选择。 一种业务代理选择功能 SBSF, 包括：
接收单元， 用于接收所述业务代理选择触发点的请求单元的所述请求； 第一选择单元， 根据接收单元接收的所述请求与业务代理选择数据库通 信， 获取业务代理选择数据， 根据所述选择数据选择业务代理。
以上技术方案可以看出：
现有技术釆用静态的配置选择方式触发到 Service Broker, 不能提供动态 的 Service Broker选择， 而本发明新增了业务代理选择触发点、 业务代理选择 功能（SBSF )和业务代理选择数据库， 业务代理选择触发点请求 SBSF 为用 户进行业务代理选择， SBSF与业务代理选择数据库通信， 获取业务代理选择 数据库的选择数据，根据所述选择数据选择业务代理，从而可以实现根据用户 要求和网络提供的业务代理的能力综合考虑进行动态选择业务代理。
附图说明
图 1是本发明较佳实施例的网络架构图；
图 2是本发明较佳实施例方法流程图；
图 3是本发明方法实施例一流程图；
图 4是本发明方法实施例二流程图；
图 5是本发明方法实施例三流程图；
图 6是本发明方法实施例四流程图；
图 7是本发明方法实施例五流程图；
图 8是本发明方法实施例六流程图；
图 9是本发明方法实施例七流程图；
图 10是本发明方法实施例八流程图；
图 11是本发明方法实施例九流程图；
图 12是本发明方法实施例十流程图；
图 13是本发明较佳实施例网络系统结构示意图；
图 14是本发明较佳实施例业务代理选择触发点结构示意图；
图 15是本发明较佳实施例业务代理选择功能 SBSF结构示意图； 图 16是本发明较佳实施例业务代理触发点结构示意图。
具体实施方式 本发明提供的业务代理选择方法，相对于现有技术， 主要增加了业务代理 选择功能 ( SBSF, Service Broker Selection Function )、 Service Broker选择数据 库和 Service Broker选择触发点。 SBSF提供 Service Broker选择能力， 可以根 据要求为用户动态的选择 Service Broker, 可以是一个独立网元， 也可以位于 S-CSCF、 或查询呼叫会话控制功能 （I-CSCF )、 或归属用户服务器 （HSS )、 或 Service Broker等内。
Service Broker选择数据库用于提供 Service Broker选择数据， 可以是一个 独立网元， 也可以是归属用户服务器 HSS等， Service Broker选择数据包括用 户业务的 Service Broker业务能力要求、 运营商为用户指定的 Service Broker, 网络中的 Service Broker可以提供的业务能力、 Service Broker触发点和网络中 的 Service Broker的拓朴连接关系、 网络内 Service Broker的可用性、 Service
Service Broker选择触发点提供触发 Service Broker选择过程的功能， 即提 供触发 SBSF的功能， Service Broker选择触发点可以是一个独立网元，也可以 位于 S-CSCF或者 I-CSCF、 或者 Service Broker等内， 例如 Service Broker不 能满足用户请求调用非签约业务引发的业务交互处理能力要求时，触发选择其 它 Service Broker。
请参阅图 1 , 是本发明提供的业务代理选择方法的较佳实施例的网络逻辑 架构图， 图 1中包括 Service Broker触发点、 Service Broker选择触发点、 业务 代理选择功能 SBSF、 Service Broker选择数据库、 用户签约数据库、 Service Broker, 监视服务器和用户设备， 其中， 用户签约数据库用于保存和管理用户 的签约数据，可以是 HSS; Service Broker触发点用于将当前通讯触发至 Service Broker, 可以是一个独立网元， 也可以位于 S-CSCF等内； Service Broker用于 提供不同业务之间的业务交互管理等功能， 可以是一个独立网元， 也可以位于 S-CSCF或应用服务器（AS )等内。。
请参阅图 2, 是本发明较佳实施例方法流程图， 包括步骤：
Al、 Service Broker选择触发条件满足时， Service Broker选择触发点与 SBSF通信， 请求 SBSF为用户进行 Service Broker的选择；
Service Broker选择触发点请求 SBSF进行 Service Broker选择的触发条件 可以包括以下情况：
业务代理选择触发点接收消息时， 根据业务触发数据指示触发到 SBSF, 例如业务代理选择触发点为 S-CSCF, S-CSCF接收到用户发起的注册消息或 者未注册用户发起或者接收呼叫消息时， 根据从 HSS中获取的 iFC数据（业 务触发数据 )触发至 SBSF, 即 iFC数据中的服务器地址元素取值为 SBSF的 地址；
业务代理选择触发点接收消息时， 消息中指示需要进行业务代理选择， 例 如业务代理选择触发点为 S-CSCF, S-CSCF向 HSS请求下载用户业务触发数 据， HSS在发送给 S-CSCF的响应消息中指示需要进行业务代理选择；
业务代理选择触发点接收消息时， 消息中携带 SBSF地址， 例如业务代理 选择触发点为 S-CSCF, 业务代理选择数据库为 HSS, S-CSCF向 HSS请求下 载用户业务触发数据， HSS在发送给 S-CSCF的响应消息中携带 SBSF地址。
Service Broker选择触发点根据 SBSF地址与 SBSF进行通信， 向 SBSF发 起 Service Broker选择请求消息。 SB SF地址的获取方式可以是在 Service Broker 选择触发点本地配置， 或者在用户签约数据库中保存的业务触发数据中配置， 例如 iFC数据的服务器地址元素取值为 SBSF的地址，并发送给 Service Broker 选择触发点， 或者是 Service Broker选择触发点接收的消息中携带有 SBSF地 址。 此外， 当 SBSF与 Service Broker选择触发点位于同一个物理设备时 SBSF 地址也可以默认为 Service Broker选择触发点本地地址。
Service Broker选择触发点发起 Service Broker选择请求消息的方式可以是
Service Broker选择触发点转发收到的引起 Service Broker选择的前述消息， 例 如转发用户注册消息等； 也可以是 Service Broker选择触发点向 SBSF发送指 示进行 Service Broker选择的消息， 例如 Service Broker选择触发点发送 SIP INVITE消息， 其中携带请求进行 Service Broker选择的指示。 此外， 当 SBSF 与 Service Broker选择触发点位于同一个物理设备的时候上述消息也可以是内 部接口消息。
为了使 SBSF 能够区分为哪个服务用户方选择 Service Broker, Service Broker选择触发点向 SBSF发送的 Service Broker选择请求消息中指示服务方 向， 例如 Service Broker选择触发点是 S-CSCF, 通过 iFC触发到 SBSF, iFC 数据中的 SBSF地址针对服务用户方向分别配置， 即为主叫用户服务的 SBSF 地址和为被叫服务的 SBSF地址区分配置，这样 iFC数据中的服务器地址部分 可以通过不同的 SBSF地址来表示不同的服务方向， SBSF根据收到消息中的 SB SF地址来区分用户的服务方向。
上述 Service Broker选择请求消息中还可以进一步包含请求的 Service
Broker触发点地址和 /或 Service Broker业务能力要求。 Service Broker业务能力 要求， 是指例如需要提供哪几类业务的交互处理能力， 在请求进行 Service Broker选择的消息中携带 Service Broker业务能力要求的情况一般是用于指示 动态的业务能力要求， 而不是基于签约的业务能力要求， 例如用户使用了非签 约业务导致的业务交互处理能力要求等。 Service Broker触发点地址的作用， 是指例如 SBSF可以根据它来确认 Service Broker触发点和待选择的 Service Broker间的连通性。 这些信息不是必须携带的 , 例如 Service Broker选择触发 点发送的请求 Service Broker选择消息中没有携带 Service Broker触发点地址 时， SBSF默认发送消息方为 Service Broker触发点； 又例如发送消息没有携带 Service Broker业务能力要求时， 可以理解为用户业务对 Service Broker没有特 别的能力要求， 也可以是 Service Broker业务能力要求以后从 Service Broker 选择数据库中获取。
A2、 SBSF与 Service Broker选择数据库通信， 获取 Service Broker选择数 据并根据所述数据以及 Service Broker选择算法选择 Service Broker;
SBSF向 Service Broker选择数据库请求获取选择数据， Service Broker选 择数据库返回请求的选择数据。 SBSF进行 Service Broker选择数据请求的方式 至少包括： 使用现有协议消息， 例如 Service Broker选择数据库为 HSS, SBSF 可以使用 Sh接口消息用户数据请求（UDR )来请求 Service Broker选择数据； 或者， 对接口协议进行扩展， 例如使用 Diameter协议增加新的命令码携带选 择数据请求消息。
Service Broker选择数据至少包括：
用户业务的业务代理能力要求和业务代理的业务能力， 即 、 用户业务的 Service Broker业务能力要求。 Service Broker能力要求包括必选能力要求、 可 选能力要求， 还可以包括 Service Broker名称， Service Broker名称可以就是 Service Broker的地址。 在 Service Broker能力要求中携带 Service Broker名称 的情况， 例如注册消息处理流程中携带之前为未注册用户临时选择的 Service Broker名称即 Service Broker地址；
b、 网络中的 Service Broker可以提供的业务能力。
Service Broker选择数据还可以包括以下信息的一项或多项：
c、 运营商为用户指定的 Service Broker;
d、 Service Broker触发点和网络中的 Service Broker的拓朴连接关系，例如 Service Broker触发点和 Service Broker的连通 '1"生等；
e、 网络内 Service Broker的可用性， 例如 Service Broker是否正常运行等； f、 Service Broker优选策略， 例如当 Service Broker与 S-CSCF合设时
S-CSCF是否提供用户需要的 Service Broker能力， 或者 Service Broker的负载 均衡等；
g、 Service Broker触发点至 Service Broker 的触发方式数据， 用于确定 Service Broker触发点到 Service Broker的唯一触发方式， 例如 SBSF为未注册 用户选择了一个 Service Broker, 其后用户注册时又选择了一个不同的 Service Broker, 此时 SBSF通过比较触发方式数据中的 Service Broker地址和当前选 择的 Service Broker地址是否一致来决定是否更新 Service Broker触发点到 Service Broker的触发方式， 例如需要更新时， SBSF通过和 HSS的人机语言 ( MML )接口更新 HSS上保存的 Service Broker触发点至 Service Broker的 iFC 规则，如更新 iFC规则中配置的服务器地址，该服务器地址代表 Service Broker 的地址。 需要更新的规则在 HSS上的定位可以通过例如 MML语言约定的规 则索引确定。
在另一实施例中， Service Broker选择数据可以至少包括上述 a ~ g信息中 的一项或多项。
SBSF获取 Service Broker选择数据后， 选择满足要求的 Service Broker。 如果 Service Broker选择数据中包括运营商为用户指定的 Service Broker, 则 SBSF直接选定该 Service Broker; 如果 Service Broker选择数据中未包括运营 商为用户指定的 Service Broker, 则 SBSF根据上述 Service Broker选择数据以 及 Service Broker选择算法选择 Service Broker, 例如 SBSF根据其收到的 Service Broker选择请求消息中携带的 Service Broker业务能力要求和网络中的 Service Broker可以提供的业务能力的匹配程度、 以及 Service Broker可用性等 来选择 Service Broker。 匹配程度指优先选择满足所有必选能力要求并提供最 多可选能力要求的 Service Broker„
SBSF选择 Service Broker后确定 Service Broker触发点至 Service Broker 的触发方式， 触发方式包括 Service Broker名称， 或者配置有 Service Broker 信息的业务触发数据。 所述 Service Broker名称， 即 Service Broker地址， 这里 用 Service Broker名称而不是 Service Broker地址是为了将其与其它类型实体的 地址区分， 例如与应用服务器 AS的地址区别对待， S-CSCF对 Service Broker 的触发方式与对 AS的触发方式可以不同， 例如使用 Service Broker名称时， S-CSCF不再触发 iFC。 所述至 Service Broker的业务触发数据中包括 Service Broker地址， 例如确定的 Service Broker触发方式为使用 iFC触发， iFC数据 配置中的服务器地址配置为所选择的 Service Broker地址。
确定 Service Broker触发点至 Service Broker的触发方式后，可以将触发方 式传递至 Service Broker触发点、 用户设备 UE、 用户签约数据库或 Service Broker选择数据库， 上述实体接收后可以进一步进行保存。 直接传输触发方式，例如当 Service Broker选择触发点和 Service Broker触发点 位于同一个物理实体时， SBSF 通过 Service Broker选择响应消息将 Service
Broker名称发送给 S-CSCF ( Service Broker触发点）； 间接传输触发方式， 例 如当 Service Broker选择触发点和 Service Broker触发点位于不同物理实体时，
SBSF通过 Service Broker选择响应消息将 Service Broker名称发送给 I-CSCF ( Service Broker选择触发点）， I-CSCF 将所述 Service Broker名称传递给 S-CSCF ( Service Broker触发点）。 进一步的， S-CSCF将所述 Service Broker 名称保存下来。 S-CSCF后续处理所述用户的通信时可直接根据保存的 Service
Broker名称触发到选定的 Service Broker。
SBSF将所述触发方式传递至所述用户设备 UE的过程可以是：例如 SBSF 通过注册响应消息将 Service Broker名称返回给 UE。 进一步的， UE将其保存 下来， UE后续发起会话消息中携带 Service Broker名称， S-CSCF根据 Service Broker名称触发到指定的 Service Broker上。
SBSF将所述触发方式传递至 HSS的过程可以是： SBSF将配置有 Service Broker信息的 iFC规则（业务触发数据 )传送至用户签约数据库， 用户签约数 据库保存所述的 iFC规则，并且所述 iFC规则可以被更新至 S-CSCF或者是被 S-CSCF主动下载。 所述被更新至 S-CSCF, 例如 S-CSCF在此之前已经下载了 用户配置数据， 则可更新用户配置数据； 所述被 S-CSCF主动下载， 例如未注 册用户在注册时重选 S-CSCF, 新的 S-CSCF 下载的数据中包括了至 Service Broker的触发方式 iFC数据。 S-CSCF后续处理所述用户的通信时可直接根据 所述 iFC规则触发到选定的 Service Broker。
SBSF将所述触发方式传递至 Service Broker选择数据库的过程可以是：例 如 SBSF将 Service Broker名称发送到 Service Broker选择数据库， Service Broker选择数据库将其保存下来， 所述触发方式可以保存为 Service Broker选 择数据的一部分，例如存放到 Service Broker能力要求中的 Service Broker名称。
A4、 将当前通信触发至选择的 Service Broker; 前通信触发至选定的 Service Broker, 或者， 也可以是 Service Broker触发点获 取至 Service Broker的触发方式后， 将当前通信触发至选定的 Service Broker。
A5、 在检测到选定的 Service Broker 不可用或能力不足时， 重新发起 Service Broker选择过程。
可以是由 SBSF检测到 Service Broker不可用， 例如 SBSF转发 Service Broker触发点的消息至 Service Broker的情况下， Service Broker无响应， 此时 SBSF检测出至 Service Broker的触发失败；
也可以是 Service Broker触发点检测到 Service Broker不可用，例如 Service Broker触发点为 S-CSCF , S-CSCF可以根据 Service Broker名称触发到 Service Broker, Service Broker无响应, J¾时 Service Broker触发点检测出至 Service Broker的触发失败；
也可以是新增监控 Service Broker可用性的实体检测到 Service Broker不可 用， 例如独立设置一个监视服务器， 它通过与 Service Broker互相发送握手消 息来检测 Service Broker的可用性， 它可以单独设置， 可以与 SBSF合设， 可 以和 Service Broker选择触发点合设， 也可以和 Service Broker触发点合设。
Service Broker可用性的检测包括在 Service Broker选择过程中进行和 /或 在选择 Service Broker以后进行。
当检测出 Service Broker不可用时，可以由 Service Broker触发点或 Service
Broker选择触发点重新请求 SBSF进行 Service Broker选择过程， 也可以由 SBSF重新发起 Service Broker选择过程， 分别举例说明如下：
例如 SBSF转发 Service Broker触发点的消息至 Service Broker的情况下， Service Broker无响应，此时 SBSF重新发起 Service Broker选择过程；或者 SBSF 向监控 Service Broker可用性的实体订阅选择的 Service Broker可用性信息，在 Service Broker不可用时， 该实体通知 SBSF, SBSF重新发起 Service Broker 选择过程；
例如 Service Broker触发点为 S-CSCF, S-CSCF根据 Service Broker名称 触发 Service Broker, Service Broker无响应， 此时 S-CSCF重新请求 SBSF进 行 Service Broker选择过程；
例如 Service Broker选择触发点获知已经为用户选定的 Service Broker不可 用， 请求重新进行 Service Broker选择， 如已经注册的服务用户为被叫用户， SBSF与 HSS位于同一个物理实体时， HSS向 I-CSCF ( Service Broker选择触 发点）返回先前为该用户选择的 Service Broker, I-CSCF检测出先前选择的 Service Broker不可用， 重新发起 Service Broker选择过程。
检测到选定的 Service Broker能力不足，重新发起 Service Broker选择过程 的举例说明如下：
Service Broker选择触发点和 Service Broker位于同一个物理实体, Service Broker进行消息处理，发现自身提供的业务处理能力不足时，也将通过 Service Broker选择触发点重新请求进行 Service Broker选择， 例如用户使用非签约类 业务， 所述 Service Broker不能处理该非签约业务与用户原有业务的交互， 此 时触发业务代理选择过程。
如果已选择的 Service Broker接收到新的业务请求时， 例如用户请求的新 业务是未签约业务， 则可能引发与用户原签约业务的业务交互问题， 当已选择 的 Service Broker不能提供需要的业务交互处理能力时， 则将根据所述选择数 据和会话中的信息选择满足用户业务交互要求的 Service Broker。 例如选定的 Service Broker上用户已经触发了游戏（ Game )业务， 其后用户请求调用 IPTV 业务， Service Broker处理不了 IPTV业务和 Game业务的交互， 则根据选择数 据和会话信息重新选择新的 Service Broker。 所述会话中的信息可以包括： 信 令消息中携带的 Service Broker名称， 例如用户设备 UE在发送的消息中携带 Service Broker名称； 用户已经调用的业务信息， 例如已经调用了哪些业务； 用户将要调用的业务信息， 例如用户请求使用非签约类业务等。
为便于对本发明进一步理解，下面结合具体实施方式对本发明进行更详细 介绍。
以下介绍实施例一。
本实施例中 SBSF为独立的功能实体， Service Broker触发点以及 Service Broker选择触发点均为 S-CSCF, 用户签约数据库以及 Service Broker选择数 据库均为 HSS, SBSF通过 Sh接口获取 Service Broker选择数据。 此实施例描 述的是服务的被叫用户是未注册时收到 SIP INVITE邀请消息的情况下对应的 业务代理选择过程。 请参阅图 3 , 包括步骤：
Bl、 S-CSCF收到被叫为未注册用户的 INVITE邀请消息；
B2、 S-CSCF收到此 INVITE消息后到 HSS上获取被叫用户配置， 并对其 中的 iFC触发数据进行检查；
本实施例中当被叫用户需要进行 Service Broker选择时， 在该用户的用户 配置中增加一条触发至 SBSF的 iFC配置数据，此 iFC数据中 SPT描述部分至 少包括 <Method>INVITE</Method>、 <SessionCase>2</SessionCase>这两项， 即此实施例中 SBSF地址通过 iFC数据确定。
B3、 S-CSCF根据 iFC数据将 INVITE消息触发到 SBSF上；
S-CSCF向 SBSF发送 INVITE消息， 即 Service Broker选择请求消息， 为 了使 SBSF 能够区分是为消息中的主叫还是被叫用户选择 Service Broker, S-CSCF触发到 SBSF上的消息指示服务方向， 例如上述 iFC中对 SBSF地址 配置成为被叫服务的 SBSF地址。
B4、 SBSF向 HSS发送 Sh接口消息用户数据请求（ UDR ); 本实施例中 SBSF与 HSS间的接口为 Sh接口。 SBSF和 HSS使用 Diameter 协议通信。 SBSF收到 S-CSCF发送的 INVITE消息即进行 Service Broker选择， SBSF 向 HSS 发送 Sh接口消息用户数据请求 （UDR ), 其中携带用户标识 ( User-Identity )属性 -值对 （AVP ), 取值为服务用户的公有标识， 数据参考 ( Data-Reference )属性-值对， 取值为请求透明数据（ RepositoryData ), 业务 指示 （ Service-Indication )属性-值对， 取值对应 HSS上 Service Broker选择数 据的透明数据索引值。
B5、 HSS向 SBSF回应 Sh接口消息用户数据响应 （UDA ), 携带用户数 据（User-Data )属性 -值对， 其中的数据为 Service Broker选择数据。
B6、 SBSF根据接收的 Service Broker选择数据以及 Service Broker选择算 法确定为用户服务的 Service Broker; Service Broker选择算法， 是指例如根据 用户的 Service Broker业务能力要求以及网络中得 Service Broker可以提供的业 务能力的匹配程度来选择 Service Broker等， 比如， 优先选择满足所有必选能 力要求并提供最多可选能力要求的 Service Broker。
B7到 B10、 SBSF向已确定的 Service Broker转发 INVITE消息， Service
Broker响应 200 OK消息并转发给 S-CSCF, 再转发给用户， 则选定的 Service Broker可以为用户服务；
Bll、 SBSF与 HSS通信请求添加一条触发至 Service Broker的 iFC数据； 此实施例中 SBSF增加 iFC数据的方式可以是 SBSF使用简单网络管理协 议（ SNMP )， 充当人机交互语言（ MML )客户端， 使用 HSS支持的 MML命 令添加触发至 Service Broker的 iFC数据。
B12、 HSS返回成功响应消息到 SBSF;
B13、 HSS发现用户配置发生变化， 通过 Cx接口推送配置请求 （PPR ) 命令主动更新 S-CSCF上的用户配置，其中携带前述步骤增加的触发到 Service Broker的 iFC数据配置；
Cx接口定义为 I-CSCF和 HSS之间或 S-CSCF和 HSS之间的接口。
B14、 S-CSCF保存新的 iFC数据；
B15、 S-CSCF回送推送配置响应 （PPA )到 HSS。
这样 S-CSCF收到该用户后续的通信消息时可根据新的 iFC数据信息直接 触发至对应的 Service Broker。
以下介绍实施例二。
本实施例中 SBSF为独立的功能实体， Service Broker触发点以及 Service Broker选择触发点均为 S-CSCF, 用户签约数据库以及 Service Broker选择数 据库均为 HSS。此实施例描述的是 S-CSCF收到用户的 SIP REGISTER注册请 求， 并且 SBSF选择的第一个 Service Broker是不可用的情况时对应的业务代 理选择过程。 请参阅图 4, 包括步骤：
CI、 S-CSCF收到用户的 SIP REGISTER注册请求；
C2、 S-CSCF向用户响应 200 OK消息；
C3、 S-CSCF到 HSS上获取用户配置， 并对其中的用户签约数据库中的 iFC触发数据进行检查；
C4、 S-CSCF将 SIP REGISTER注册请求发送给 SBSF;
C5、 SBSF和 HSS使用通用用户档案（GUP )协议通信， SBSF发出 GUP Query消息， 其中的资源标识（ Resource identity )参数填充请求查询的用户的 公有标识， 数据参考（ Data references )参数指示请求为 Service Broker选择数 据；
C6、 HSS向 SBSF回送 GUP Query Response响应消息， 其中携带请求用 户的 Service Broker选择数据；
C7、 SBSF根据接收的 Service Broker选择数据以及 Service Broker选择算 法确定为用户服务的 Service Broker;
Service Broker选择算法，是指例如根据用户的 Service Broker能力要求以 及 Service Broker可以提供的能力的匹配程度来选择 Service Broker等，即优先 选择满足所有必选能力要求并提供最多可选能力要求的 Service Broker。 本实 施例确定为用户服务的为 Service Broker 1。
C8、 SBSF将 SIP REGISTER注册请求发送给已经确定的 Service Broker 1；
C9、 SBSF发现 Service Broker 1超时没有回应 200 OK消息后，发起 Service Broker重选过程,根据 Service Broker选择数据以及 Service Broker选择算法选 择 Service Broker 2;
C10到 C13、 SBSF向已确定的 Service Broker 2转发 SIP REGISTER注册 请求， Service Broker 2响应 200 OK消息并转发给 S-CSCF, 再转发给用户， 则选定的 Service Broker 2可以为用户服务；
C14、 重选的 Service Broker 2回送 200 OK响应以后， SBSF发出 GUP Modify消息， 其中的资源标识（Resource identity )参数填充请求查询的用户 的公有标识， 数据参考（ Data references )参数指示修改的为 Service Broker名 称；
C15、 HSS修改成功后回送 GUP Modify Response消息。
C16、 HSS通过 Cx接口推送配置请求（PPR )命令主动更新 S-CSCF上的 用户配置， 其中携带前述步骤确定的 Service Broker名称；
C17、 S-CSCF保存 Service Broker名称；
C18、 S-CSCF回送推送配置响应 （PPA )到 HSS。
这样 S-CSCF收到该用户后续的通信消息时可根据保存 Service Broker名 称直接触发至对应的 Service Broker。
以下介绍实施例三。
本实施例中 Service Broker选择触发点为 I-CSCF, Service Broker触发点 为 S-CSCF, 其中 I-CSCF具备 SBSF功能， S-CSCF与 Service Broker功能合 设，用户签约数据库以及 Service Broker选择数据库均为 HSS , I-CSCF的 SBSF 功能就是为用户选择满足其业务要求的并且内置 Service Broker 功能的 S-CSCF。
实施例中 I-CSCF收到用户的 SIP REGISTER请求， 对应的业务代理选择 过程请参阅图 5 , 包括步骤：
Dl、 I-CSCF收到用户的 SIP REGISTER注册请求；
D2、 I-CSCF向 HSS发送 Cx接口消息用户鉴权请求（UAR );
D3、 HSS通过 Cx接口消息用户鉴权响应（UAA )携带 S-CSCF能力要求 发送给 I-CSCF;
由于 Service Broker功能与 S-CSCF功能合设， 所以此时 HSS将用户的 Service Broker能力要求统一放到 S-CSCF能力要求中描述。
D4、 I-CSCF选择满足用户要求的 S-CSCF;
I-CSCF本地配置有网络中 S-CSCF提供的能力等信息， 并根据这些信息 以及 HSS发送的 S-CSCF能力要求进行 S-CSCF选择，此时选择的 S-CSCF同 时能够满足用户的 Service Broker能力要求。
D5、 I-CSCF将 SIP REGISTER注册请求发送给已经确定的 S-CSCF;
D6、 S-CSCF向 HSS发送 Cx接口消息服务器指配请求 （SAR );
D7、 HSS向 S-CSCF发送 Cx接口消息服务器指配响应 （ SAA );
D8到 D9、 S-CSCF向 I-CSCF响应 200 OK消息并由 I-CSCF转发给用户。 需要说明的是， 本实施例中 S-CSCF和 Service Broker合设， 可以不需要 保存至 Service Broker的触发方式数据。
以下介绍实施例四。
本实施例中 Service Broker触发点以及 Service Broker选择触发点均为
S-CSCF,并且 S-CSCF与 SBSF功能合设，用户签约数据库以及 Service Broker 选择数据库均为 HSS。
实施例中 S-CSCF收到用户的 SIP REGISTER请求， 对应的业务代理选择 过程请参阅图 6, 包括步骤：
El、 S-CSCF收到用户的 SIP REGISTER注册请求；
E2、 S-CSCF向 HSS发送 Cx接口消息服务器指配请求 （SAR );
E3、 HSS向 S-CSCF发送 Cx接口消息服务器指配响应 （SAA ), 其中携 带一个扩展的 AVP指示需要进行 Service Broker选择；
E4、 S-CSCF响应 200 OK消息给用户；
E5、 S-CSCF向 HSS发送 Service Broker选择数据请求消息， 该消息为 Cx 接口扩展消息；
E6、 HSS在 Service Broker选择数据响应消息中携带 Service Broker选择 数据， 该消息为 Cx接口扩展消息；
E7、 S-CSCF根据 Service Broker选择数据以及 Service Broker选择算法选 定一个 Service Broker, 并保存 Service Broker名称；
这样 S-CSCF收到该用户后续的通信消息时可根据 Service Broker名称直 接触发至对应的 Service Broker„
E8、 S-CSCF将 SIP REGISTER注册请求发送给已经确定的 Service Broker;
E9、 Service Broker向 S-CSCF响应 200 OK消息。 本实施例中 S-CSCF 也可以在选定的 Service Broker 不可用时重新触发 Service Broker选择过程， 例如 S-CSCF对 Service Broker的触发进行处理， 当 步骤 E8 中选择的 Service Broker 无响应时， S-CSCF 重新选择其它可用的 Service Broker。
本实施例中步骤 E4也可以放到 E9之后，即 S-CSCF可以将选择的 Service
Broker名称通过扩展 200 OK消息传递给用户设备 UE, 例如增加一个头域携 带此 Service Broker名称， UE接收后保存下来， 在后续 UE发起的会话消息中 携带保存的该 Service Broker名称， 这样 S-CSCF收到该用户后续的通信消息 时可根据 Service Broker名称直接触发至对应的 Service Broker。对于这种情况 下步骤 E7中 S-CSCF可以不保存 Service Broker名称， 因为 UE后续发起的会 话消息中可以携带为该用户服务的 Service Broker名称。
以下介绍实施例五。
本实施例中 Service Broker选择触发点为 I-CSCF, Service Broker触发点 为 S-CSCF,其中 I-CSCF具备 SBSF功能，用户签约数据库以及 Service Broker 选择数据库均为 HSS。
实施例中 I-CSCF收到用户的 SIP REGISTER请求， 对应的业务代理选择 过程请参阅图 7, 包括步骤：
Fl、 I-CSCF收到用户的 SIP REGISTER注册请求；
F2、 I-CSCF向 HSS发送 Cx接口消息用户鉴权请求（ UAR );
F3、 HSS向 I-CSCF返回 Cx接口消息用户鉴权响应（UAA ), 其中携带一 个扩展的 AVP指示需要进行 Service Broker选择；
F4、 I-CSCF向 HSS发送 Service Broker选择数据请求消息， 该消息为 Cx 接口扩展消息；
F5、 HSS在向 I-CSCF返回的 Service Broker选择数据响应消息中携带 Service Broker选择数据， 该消息为 Cx接口扩展消息；
F6、 I-CSCF根据 Service Broker选择数据以及 Service Broker选择算法选 定一个 Service Broker, 并保存 Service Broker名称；
这样 I-CSCF收到该用户后续的通信消息时可根据 Service Broker名称通 过 S-CSCF触发至对应的 Service Broker。 F7、 I-CSCF选定 Service Broker后通过 SIP REGISTER消息携带 Service Broker名称发送给 S-CSCF。这里携带 Service Broker名称是对 SIP消息进行了 扩展， 例如增加一个新头域携带此信息。
F8、 S-CSCF接收消息后保存下 Service Broker名称，并向 I-CSCF响应 200 OK消息；
F9、 I-CSCF将 200 OK消息转发给用户；
F 10、 S-CSCF检查保存的 Service Broker名称；
Fll、 S-CSCF根据保存的 Service Broker名称触发 SIP REGISTER消息至 所选定的 Service Broker;
F12、 选定的 Service Broker向 S-CSCF响应 200 OK消息。
以下介绍实施例六。
本实施例中 Service Broker 触发点及 Service Broker 选择触发点均为 S-CSCF, 用户签约数据库以及 Service Broker选择数据库均为 HSS, 且 HSS 具备 SBSF功能。
实施例中 S-CSCF收到用户的 SIP REGISTER请求， 对应的业务代理选择 过程请参阅图 8, 包括步骤：
Gl、 S-CSCF收到用户的 SIP REGISTER注册请求；
G2、 S-CSCF向 HSS发送 Cx接口消息服务器指配请求 （SAR );
G3、 HSS收到 S-CSCF发送的 Cx接口消息服务器指配请求（ SAR )后发 现用户业务要求进行 Service Broker选择， 此时发起 Service Broker选择过程， 选定一个 Service Broker并确定 S-CSCF到 Service Broker的触发方式，例如用 iFC配置或者 Service Broker名称。
G4、 HSS将 Service Broker的触发方式， 例如将触发至 Service Broker的 iFC配置或者 Service Broker名称通过 Cx接口消息服务器指配响应（ SAA )回 送给 S-CSCF;
G5、 S-CSCF保存含触发方式的用户配置；
G6、 S-CSCF向用户发送 200 OK消息；
G7、 S-CSCF检查保存的 iFC配置或 Service Broker名称；
G8、 S-CSCF根据保存的 Service Broker名称触发至 Service Broker的 iFC 配置或者触发 SIP REGISTER消息至所选定的 Service Broker上；
G9、 选定的 Service Broker向 S-CSCF响应 200 OK消息。
需要说明的是，如果 S-CSCF发现选择的 Service Broker超时没有回应 200
OK消息后， 可以发起 Service Broker重选过程， 向 HSS重新请求进行 Service Broker选择过程， HSS根据 Service Broker选择数据以及 Service Broker选择 算法重新选择 Service Broker 。
以下介绍实施例七。
本实施例为通过单独的 Service Broker可用性监视服务器监控已经为用户 Service Broker触发点为 S-CSCF , 用户签约数据库以及 Service Broker选择数 据库均为 HSS, SBSF独立设置， 对应的 Service Broker重选过程请参阅图 9, 包括步骤：
Hl、 SBSF 向 Service Broker可用性监视服务器订阅已经为用户选定的 Service Broker的可用状态信息；
H2、 Service Broker可用性监视服务器回送 200 OK响应；
H3、 Service Broker可用性监视服务器与选定的 Service Broker互相发送握 手消息， 例如可以通过互相发送 OPTIONS消息来监视 Service Broker的状态；
H4、 Service Broker可用性监视服务器发现监视的 Service Broker不可用， 例如一段时间内没有收到握手消息， 通过 NOTIFY消息通知 SBSF;
H5、 SBSF回送 200 OK响应消息；
在这之后的步骤为 SBSF通过 Sh接口向 HSS请求 Service Broker选择数 据进行 Service Broker重选，并更新 S-CSCF到选定的 Service Broker的触发数 据。
H6、 SBSF向 HSS发送 Sh接口消息用户数据请求（ UDR );
SBSF向 HSS发送 Sh接口消息用户数据请求（UDR ),其中携带用户标识
( User-Identity )属性 -值对 （AVP ), 取值为服务用户的公有标识， 数据参考 ( Data-Reference )属性-值对， 取值为请求透明数据（ RepositoryData ), 业务 指示 （ Service-Indication )属性-值对， 取值对应 HSS上 Service Broker选择数 据的透明数据索引值。 H7、 HSS向 SBSF回应 Sh接口消息用户数据响应 （UDA ), 携带用户数 据（User-Data )属性 -值对， 其中的数据为 Service Broker选择数据。
H8、 SBSF根据接收的 Service Broker选择数据以及 Service Broker选择算 法确定为用户服务的 Service Broker;
H9、 SBSF与 HSS通信请求添加一条触发至 Service Broker的 iFC数据或
Service Broker名称；
H10、 HSS返回成功响应消息到 SBSF;
Hll、 HSS发现用户配置发生变化， 通过 Cx接口推送配置请求（PPR ) 命令主动更新 S-CSCF上的用户配置，其中携带前述步骤增加的触发到 Service Broker的 iFC数据配置或 Service Broker名称；
H12、 S-CSCF保存新的 iFC数据或 Service Broker名称；
H13、 S-CSCF回送推送配置响应 （PPA )到 HSS, 表示更新成功。
以下介绍实施例八。
本实施例中 Service Broker 触发点及 Service Broker 选择触发点均为 S-CSCF, 用户签约数据库以及 Service Broker选择数据库均为 HSS, SBSF独 立设置。
本实施例描述的是 S-CSCF 收到用户的未签约业务情况下的过程。 例如 S-CSCF 收到用户未签约 IPTV 业务请求触发到 SBSF 上请求选择 Service Broker, 具体过程参阅图 10, 包括步骤：
II、 S-CSCF收到用户的 INVITE消息， 请求调用 IPTV业务；
12、 S-CSCF收到此 INVITE消息后到 HSS上获取用户档案， 并进行 iFC 触发检查；
13、 S-CSCF根据 iFC数据将 INVITE消息触发到 SBSF上；
14、 SBSF向 HSS发送 Sh接口消息用户数据请求 （UDR );
用户数据请求（ UDR )中携带用户标识（ User-Identity )属性 -值对（ AVP ) , 取值为服务用户的公有标识， 数据参考 （Data-Reference )属性 -值对， 取值为 请求透明数据 ( RepositoryData ), 业务指示 ( Service-Indication )属性-值对， 取值对应 HSS上 Service Broker选择数据的透明数据索引值。
15、 HSS向 SBSF回应 Sh接口消息用户数据响应（UDA ), 携带用户数据 ( User-Data )属性 -值对， 其中的数据为 Service Broker选择数据。
16、 SBSF根据接收的 Service Broker选择数据和用户发送消息中含有的会 话信息确定为用户服务的 Service Broker, 所述会话信息是指例如用户请求调 用的业务等；
17、 SBSF将携带路由 Route头域为 Service Broker的 INVITE消息发送给
S-CSCF;
18 到 110、 S-CSCF根据该 Route 头域向已确定的 Service Broker路由 INVITE消息， Service Broker响应 200 OK消息给 S-CSCF, 再由 S-CSCF转发 给用户， 则选定的 Service Broker可以为用户服务。
需要说明的是， 本实施例的 SBSF也可以是和 Service Broker合设的， 这 种情况下选定的 Service Broker可以就是 SBSF自身。
以下介绍实施例九。
本实施例中 Service Broker 触发点和 Service Broker 选择触发点均为 Service Brokerl , 用户签约数据库以及 Service Broker选择数据库均为 HSS, Service Brokerl具备 SBSF功能。
本实施例描述的是 Service Brokerl上用户已经触发了游戏 Game业务，其 后用户请求调用未签约的 IPTV业务， Service Brokerl处理不了 IPTV业务和 Game业务的交互， 重新选择新的 Service Broker, 具体过程请参阅图 11 , 包 括步骤：
Jl、 Service Brokerl收到用户的 INVITE消息， 其中含有 Game业务调用 请求；
J2、 Service Brokerl调用 Game业务的处理；
J3、 Service Brokerl又收到用户的 INVITE消息， 其中含有 IPTV业务调 用请求；
J4、 Service Brokerl发现不能处理 IPTV业务和 Game业务的交互，向 HSS 发送 Sh接口消息用户数据请求（ UDR );
J5、HSS向 SBSF回应 Sh接口消息用户数据响应（UDA ),其中携带 Service Broker选择数据和网络中的 Service Broker业务交互处理能力列表；
J6、 Service Brokerl根据获取的 Service Broker选择数据、 上述网络中的 Service Broker业务交互处理能力列表以及用户已经调用 Game业务和将调用 IPTV 业务的情况， 为用户选择一个可用的 Service Broker2 , 并保存 Service Broker名称；
J7、 Service Brokerl将 INVITE消息发送给 Service Broker2 , 用户的 IPTV 业务被 Service Brokerl触发到 Service Broker2上。
以下介绍实施例十。
本实施例中 Service Broker 触发点和 Service Broker 选择触发点均为 Service Brokerl ,用户签约数据库为 HSS , Service Broker选择数据库独立设置， SBSF独立设置。
本实施例描述的是 Service Brokerl上用户已经触发了 Game业务，其后用 户请求调用未签约的 IPTV业务， Service Brokerl处理不了 IPTV业务和 Game 业务的交互， 重新选择新的 Service Broker, 具体过程请参阅图 12, 包括步骤： Kl、 Service Brokerl收到用户的 INVITE消息， 其中含有 Game业务调用 请求；
K2、 Service Brokerl调用 Game业务的处理；
K3、 Service Brokerl又收到用户的 INVITE消息， 其中含有 IPTV业务调 用请求；
K4、 Service Brokerl 向 SBSF发送携带 Service Broker选择请求指示的 INVITE消息， 其中还携带业务能力要求， 指示需要提供 IPTV和 Game业务 的交互处理能力；
K5、 SBSF向 Service Broker选择数据库发送 Service Broker选择数据请求 消息；
K6、 Service Broker选择数据库向 SBSF返回 Service Broker选择数据响应 消息，其中携带 Service Broker选择数据和网络中的 Service Broker业务交互处 理能力列表；
K7、 SBSF根据获取的 Service Broker选择数据、 上述网络中的 Service Broker业务交互处理能力列表以及用户已经调用 Game业务和将调用 IPTV业 务的情况， 为用户选择一个可用的 Service Broker2 , 并保存 Service Broker2名 称； K8、 SBSF通过 200 OK消息携带 Service Broker2名称给 Service Brokerl； K9、 Service Brokerl将 INVITE消息发送给 Service Broker2,用户的 IPTV 业务被 Service Brokerl触发到 Service Broker2上。
需要说明的是， 以上各实施例仅为示例， 并未罗列所有情况， 对于其它可 能的 SBSF合设情况和各实体间釆用其它类型的接口以及处理流程组合等情 况， 本发明同样适用， 此处不再赘述。
上述介绍了本发明的业务代理选择方法，相应的， 本发明提供一种网络系 统， 可以提供业务代理选择。
请参阅图 13 , 该网络系统包括用户签约数据库 100、 Service Broker选择 触发点 200、 业务代理选择功能 SBSF 300、 Service Broker选择数据库 400、 Service Broker触发点 500、 Service Broker 600、监视服务器 700和用户设备 800。 相对于现有网络， Service Broker选择触发点 200、业务代理选择功能 SBSF 300 和 Service Broker选择数据库 400是本发明主要增加的实体。
用户签约数据库 100存储用户的签约数据， 例如 iFC数据、计费服务器地 址数据等， 进一步的， 用户签约数据库 100可以向 Service Broker选择触发点 200发送含有触发到业务代理选择功能 SBSF指示或者含有进行业务代理选择 指示的消息。各种类型的用户签约数据可以存放在同一个物理网元实体上，也 可以存放在不同的物理网元实体上。 用户签约数据库可以是用户归属服务器 ( HSS ), 也可以是非 HSS的数据服务器。
Service Broker选择触发点 200提供触发 Service Broker选择过程的功能，
Service Broker选择触发点 200可以是服务呼叫会话控制功能（ S-CSCF )或者 查询呼叫会话控制功能（I-CSCF ),甚至可以是 Service Broker 。 Service Broker 选择触发点 200是 Service Broker 的情况， 例如 Service Broker 业务能力不足 时再选择其它 Service Broker。
请参阅图 14 , Service Broker选择触发点 200包括请求单元 201 , 进一步 包括第三重选触发单元 202 , 请求单元 201用于请求业务代理选择功能 SBSF 300进行业务代理选择， 如接收到含有触发到业务代理选择功能 SBSF指示或 者含有进行业务代理选择指示的消息后请求业务代理选择功能 SBSF 300进行 业务代理选择； 第三重选触发单元 202 , 用于在选择的 Service Broker不可用 或能力不足时触发重新选择业务代理过程。 选择的 Service Broker不可用， 是 指例如触发到选择的 Service Broker时 Service Broker没有响应。
业务代理选择功能 SBSF 300提供 Service Broker选择能力，如可以根据要 求为用户动态的选择 Service Broker。业务代理选择功能 SBSF 300物理上可以 单独设置， 也可以与上述提到的其他任意实体合设。
请参阅图 15 , 业务代理选择功能 SBSF 300包括接收单元 301、 第一选择 单元 302, 此外， 进一步包括触发方式确定单元 303 , 此外， 进一步包括第二 触发单元 304, 此外， 进一步包括第一重选触发单元 305 , 此外， 进一步包括 第二选择单元 306。 接收单元 301 , 用于接收 Service Broker选择触发点 200 的请求单元 201的所述请求； 第一选择单元 302, 根据接收单元 301接收的所 述请求与业务代理选择数据库 400通信，并获取业务代理选择数据库 400的选 择数据， 根据所述选择数据选择 Service Broker; 触发方式确定单元 303 , 用于 根据选择的业务代理确定 Service Broker触发点 500到 Service Broker 600的触 发方式， 并进一步传递给用户设备 800、 或业务代理选择数据库 400、 或用户 签约数据库 100、 或业务代理触发点 500存储； 第二触发单元 304, 用于按所 述触发方式将当前通信触发到选择的 Service Broker; 第一重选触发单元 305 , 用于在选择的 Service Broker不可用时触发重新选择业务代理过程； 第二选择 单元 306 , 用于在选择的 Service Broker无法满足新的业务请求引起的业务代 理能力要求时， 根据所述选择数据和会话信息等选择其他 Service Broker。 例 如选定的业务代理 Service Broker上用户已经触发了游戏 Game业务， 其后用 户请求调用未签约的 IPTV业务， Service Broker处理不了 IPTV业务和 Game 业务的交互， 则根据所述选择数据和会话信息选择其他 Service Broker。
Service Broker选择数据库 400用于提供 Service Broker选择数据， 业务代 理选择功能 SBSF 300的第一选择单元 302和第二选择单元 306可以从 Service Broker选择数据库 400 获取选择数据， 根据这些选择数据选择符合要求的 Service Broker。
Service Broker选择数据可以包括以下信息：
Service Broker选择数据至少包括用户业务的业务代理能力要求和业务代 理的业务能力， 即 a、 用户业务的 Service Broker能力要求。 Service Broker能 力要求包括必选能力要求、 可选能力要求， 还可以包括 Service Broker名称， Service Broker名称可以为 Service Broker的地址。 在 Service Broker能力要求 中携带 Service Broker名称的情况， 例如注册消息处理流程中携带之前为未注 册用户临时选择的 Service Broker名称即 Service Broker地址； b、 网络中的 Service Broker可以提供的能力。
Service Broker选择数据还可以包括以下信息中的一项或多项：
c、 运营商为用户指定的 Service Broker;
d、 Service Broker触发点和网络中的 Service Broker的拓朴连接关系，例如 Service Broker触发点和 Service Broker的连通 '1"生等；
e、 网络内 Service Broker的可用性， 例如 Service Broker是否正常运行等； f、 Service Broker优选策略， 例如当 Service Broker与 S-CSCF合设时 S-CSCF是否提供用户需要的 Service Broker能力， 或者 Service Broker的负载 均衡等； 业务代理 Service Broker选择数据库 400可以与用户签约数据库 100合设， 也可以与业务代理选择功能 SBSF 300合设。需要说明的是，各类 Service Broker 选择数据可以存放在在同一个物理网元实体上， 例如都存放在 Service Broker 选择数据库 400, 但并不局限于此， 也可以存放在不同的物理网元实体上。
Service Broker触发点 500提供将通信触发至 Service Broker 600的功能， Service Broker触发点 500可以是服务呼叫会话控制功能（ S-CSCF ) ,也可以是 Service Broker„ Service Broker触发点是 Service Broker的情况, 例如 Service Broker 业务能力不足时再触发到其它可以提供所需要能力的 Service Broker 上。
请参阅图 16 , Service Broker触发点 500包括第一触发单元 501 , 进一步 包括第二重选触发单元 502。 第一触发单元 501 , 用于获取所述触发方式后将 当前通信触发到选择的 Service Broker„ 此外， 进一步的， 第一触发单元 501 获取所述触发方式可以进行存储。 第二重选触发单元 502 , 用于在选择的 Service Broker不可用或能力不足时触发重新选择业务代理过程。
Service Broker 600用于提供增强的业务触发能力、业务混合能力和业务交 互处理能力中的一种或多种功能。业务触发能力可以理解为根据要求触发业务 的能力，业务混合能力可以理解为将不同的几种业务混合到一起提供新的业务 的能力， 业务交互处理能力可以理解为当发生业务冲突时进行管理的能力。 Service Broker 600可以是单独的物理网元实体， 也可以和 Service Broker触发 点 500或 Service Broker选择触发点 200是同一个物理网元实体。
监视服务器 700, 用于监视选择的业务代理的状态。 监视服务器 700通过 与已选择的 Service Broker 600互相发送握手消息来监视 Service Broker 600的 状态， 例如通过互相发送 SIP OPTIONS消息进行监视， 当一段时间监视服务 器 700 没有收到握手消息， 则通知系统中的其他实体例如业务代理选择功能 SBSF 300所选择的 Service Broker 600不可用。
需要说明的是，当由业务代理选择功能 SBSF 300或 Service Broker触发点 500检测选择业务代理不可用时， 可以不需要监视服务器 700。 业务代理选择 功能 SBSF 300转发 Service Broker触发点 500的消息到 Service Broker 600上， Service Broker 600 无响应， 则此时业务代理选择功能 SBSF 300 检测出至 Service Broker 600的触发失败， Service Broker 600不可用。 Service Broker触 发点 500根据触发方式触发到 Service Broker 600上， Service Broker 600无响 应，则此时 Service Broker触发点 500检测出至 Service Broker 600的触发失败， Service Broker 600不可用。
用户设备 UE 800, 用于发起和接收通信请求， 进一步的， 可用于存储业 务代理选择功能 SBSF 300传递的触发方式，例如业务代理选择功能 SBSF 300 通过注册响应消息将触发方式返回给用户设备 UE 800 ,用户设备 UE 800将其 保存下来，用户设备 UE 800后续发起会话消息中携带触发方式， Service Broker 触发点 500根据触发方式触发到指定的 Service Broker上。
因为本发明主要新增 Service Broker选择触发点 200、 业务代理选择功能 SBSF 300、 Service Broker选择数据库 400, 相应的， 增加接口进行连接。
Service Broker选择触发点 200和业务代理选择功能 SBSF 300釆用 E1接 口，该接口主要用于触发业务代理选择功能 SBSF 300的 Service Broker选择过 程以及其后的交互过程。 E1接口协议至少包括如下之一： SIP协议、 Diameter 协议、 超文本传输协议（HTTP )协议、 内部接口协议， 当业务代理选择功能 SBSF 300和 Service Broker选择触发点 200位于同一个物理实体时可以使用内 部接口协议。
业务代理选择功能 SBSF 300和 Service Broker选择数据库 400釆用 E4接 口， 该接口用于请求和传递 Service Broker选择数据。 E4接口协议至少包括如 下之一： Diameter协议、 通用用户配置 （ GUP )协议、 SIP协议、 超文本传输 协议（HTTP )协议、 内部接口协议， 当业务代理选择功能 SBSF 300和 Service Broker选择数据库 400位于同一个物理实体时可以使用内部接口协议。
业务代理选择功能 SBSF 300和 Service Broker 600釆用 E2接口， 该接口 用于业务代理选择功能 SBSF 300将通信触发至 Service Broker 600, 例如业务 代理选择功能 SBSF 300转发注册消息到 Service Broker 600。 E2接口协议至少 包括如下之一： SIP协议、 内部接口协议， 当业务代理选择功能 SBSF 300和 Service Broker 600位于同一个物理实体时可以使用内部接口协议。
业务代理选择功能 SBSF 300和用户签约数据库 100釆用 E3接口， 该接 口用于业务代理选择功能 SBSF 300更新 Service Broker触发点 500至 Service Broker 600的触发方式数据。 E3接口协议至少包括如下之一： 简单网络管理 协议（ SNMP )、 Diameter协议、 通用用户配置（ GUP )协议、 SIP协议、 超文 本传输协议（HTTP )协议、 内部接口协议， 当业务代理选择功能 SBSF 300 和用户签约数据库 100位于同一个物理实体时可以使用内部接口协议。
以上对本发明所提供的一种业务代理选择方法及提供业务代理选择的网 行了阐述， 以上实施例的说明只是用于帮助理解本发明的方法及其核心思想； 同时， 对于本领域的一般技术人员， 依据本发明的思想， 在具体实施方式及应 用范围上均会有改变之处， 综上所述， 本说明书内容不应理解为对本发明的限 制。

Claims

权 利 要 求
1、 一种业务代理选择方法， 其特征在于， 包括：
业务代理选择功能接收业务代理选择触发点发送的业务代理选择请求； 所述业务代理选择功能根据所述业务代理选择请求，从业务代理选择数据 库中获取业务代理选择数据；
所述业务代理选择功能根据所述业务代理选择数据选择业务代理。
2、 根据权利要求 1所述的业务代理选择方法， 其特征在于：
所述选择数据至少包括用户业务的业务代理能力要求和业务代理的业务 能力。
3、 根据权利要求 1所述的业务代理选择方法， 其特征在于， 所述业务代 理选择请求中包括： 请求进行业务代理选择的指示。
4、 根据权利要求 3所述的业务代理选择方法， 其特征在于， 所述业务代 理选择请求中还包括： 服务方向。
5、 根据权利要求 3或 4所述的业务代理选择方法， 其特征在于， 所述业 务代理选择请求中还包括： 业务代理触发点地址和 /或业务代理能力要求。
6、 根据权利要求 1所述的业务代理选择方法， 其特征在于， 所述接收业 务代理选择触发点发送的业务代理选择请求之前， 进一步包括：
业务代理选择触发点接收到含有触发到业务代理选择功能 SBSF指示或者 含有进行业务代理选择指示的消息后， 发起业务代理选择请求。
7、 根据权利要求 1或 6所述的业务代理选择方法， 其特征在于， 所述根 据业务代理选择数据选择业务代理之后， 进一步包括：
根据选择的业务代理确定触发方式；
将当前通信按所述触发方式触发到选择的业务代理。
8、 根据权利要求 7所述的业务代理选择方法， 其特征在于：
所述触发方式为业务代理名称触发，或配置有业务代理信息的业务触发数 据触发。
9、 根据权利要求 7所述的业务代理选择方法， 其特征在于：
将所述触发方式进行保存， 以及，后续所述用户的通信按所述触发方式触 发到选择的业务代理。
10、 根据权利要求 9所述的业务代理选择方法， 其特征在于：
保存所述触发方式的实体为业务代理触发点、或用户设备、或用户签约数 据库、 或业务代理选择数据库。
11、 根据权利要求 7所述的业务代理选择方法， 其特征在于： 所述将当前 通信按所述触发方式触发到选择的业务代理的步骤包括：
业务代理选择功能 SBSF将当前通信按所述触发方式触发到选择的业务代 理； 方式触发到选择的业务代理。
12、 根据权利要求 1所述的业务代理选择方法， 其特征在于， 所述根据选 择数据选择业务代理之后， 进一步包括：
检测到选择的业务代理不可用时， 重新发起业务代理选择过程。
13、 根据权利要求 1所述的业务代理选择方法， 其特征在于， 所述根据选 择数据选择业务代理之后， 进一步包括：
选择的业务代理无法满足新业务请求引起的业务代理能力要求时，重新选 择其他业务代理。
14、 一种提供业务代理选择的网络系统， 其特征在于， 包括：
业务代理选择触发点，用于请求业务代理选择功能 SBSF进行业务代理选 择；
业务代理选择功能 SBSF,用于接收所述业务代理选择触发点的所述请求； 根据所述请求与业务代理选择数据库通信， 获取业务代理选择数据，根据所述 选择数据选择业务代理；
业务代理选择数据库， 用于提供选择数据。
15、根据权利要求 14所述的提供业务代理选择的网络系统， 其特征在于： 所述网络系统还包括用户签约数据库， 用于存储用户的签约数据， 向所述业务 代理选择触发点发送含有触发到业务代理选择功能 SBSF指示或者含有进行业 务代理选择指示的消息。
16、根据权利要求 15所述的提供业务代理选择的网络系统， 其特征在于： 所述网络系统还包括业务代理触发点，
所述业务代理选择功能 SBSF还用于根据选择的业务代理确定业务代理触 发点到业务代理的触发方式；
所述业务代理触发点，用于获取所述触发方式后将当前通信触发到选择的 业务代理。
17、根据权利要求 16所述的提供业务代理选择的网络系统， 其特征在于： 所述网络系统还包括用户设备， 用于存储所述触发方式； 或者，
所述业务代理选择数据库、或用户签约数据库、或业务代理触发点还用于 存储所述触发方式。
18、根据权利要求 17所述的提供业务代理选择的网络系统， 其特征在于： 所述业务代理选择功能 SBSF还用于按所述触发方式将当前通信触发到选 择的业务代理。
19、根据权利要求 18所述的提供业务代理选择的网络系统， 其特征在于： 所述业务代理选择功能 SBSF还用于在选择的业务代理不可用时触发重新 选择业务代理过程；在选择的业务代理无法满足新的业务请求引起的业务代理 能力要求时， 根据所述选择数据和会话信息选择其他业务代理
所述业务代理触发点还用于在选择的业务代理不可用时触发重新选择业 务代理过程；
所述业务代理选择触发点还用于在选择的业务代理不可用时触发重新选 择业务代理过程。
20、 根据权利要求 14到 19任一项所述的提供业务代理选择的网络系统， 其特征在于：
所述网络系统还包括监视服务器， 用于监视选择的业务代理的状态。
21、 一种业务代理选择触发点， 其特征在于， 包括：
请求单元， 用于请求业务代理选择功能 SBSF进行业务代理选择。
22、 根据权利要求 21所述的业务代理选择触发点， 其特征在于： 还包括： 第三重选触发单元，用于在选择的业务代理不可用时触发重新选择业务代 理过程。
23、 一种业务代理触发点， 其特征在于， 包括：
第一触发单元， 用于请求业务代理选择功能 SBSF进行业务代理选择。
24、 根据权利要求 23所述的业务代理触发点， 其特征在于： 还包括： 第二重选触发单元，用于在选择的业务代理不可用时触发重新选择业务代 理过程。
25、 一种业务代理选择功能 SBSF, 其特征在于， 包括：
接收单元， 用于接收所述业务代理选择触发点的请求单元的所述请求； 第一选择单元， 根据接收单元接收的所述请求与业务代理选择数据库通 信， 获取业务代理选择数据， 根据所述选择数据选择业务代理。
26、根据权利要求 25所述的业务代理选择功能 SBSF, 其特征在于： 还包 括触发方式确定单元，用于根据选择的业务代理确定业务代理触发点到业务代 理的触发方式。
27、根据权利要求 26所述的业务代理选择功能 SBSF, 其特征在于： 还包 括第二触发单元， 用于按所述触发方式将当前通信触发到选择的业务代理。
28、根据权利要求 27所述的业务代理选择功能 SBSF, 其特征在于： 还包 括第一重选触发单元，用于在选择的业务代理不可用时触发重新选择业务代理 过程。
29、根据权利要求 28所述的业务代理选择功能 SBSF, 其特征在于： 还包 括第二选择单元，用于在选择的业务代理无法满足新的业务请求引起的业务代 理能力要求时， 根据选择数据和会话信息选择其他业务代理。
PCT/CN2007/070826 2006-10-10 2007-09-29 Méthode de sélection d'un courtier de services, et système permettant la sélection d'un courtier de services WO2008043305A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200610149614.1 2006-10-10
CN200610149614.1A CN101163150A (zh) 2006-10-10 2006-10-10 业务代理选择方法及提供业务代理选择的网络系统

Publications (1)

Publication Number Publication Date
WO2008043305A1 true WO2008043305A1 (fr) 2008-04-17

Family

ID=39282428

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/070826 WO2008043305A1 (fr) 2006-10-10 2007-09-29 Méthode de sélection d'un courtier de services, et système permettant la sélection d'un courtier de services

Country Status (2)

Country Link
CN (1) CN101163150A (zh)
WO (1) WO2008043305A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116033011A (zh) * 2023-03-31 2023-04-28 新云网科技集团股份有限公司 一种数据通信方法、装置、设备及存储介质

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101686253A (zh) * 2008-09-23 2010-03-31 华为技术有限公司 服务选择方法、装置和系统
CN106790647B (zh) * 2017-01-15 2020-06-23 网宿科技股份有限公司 一种自适应服务管理的方法和系统
CN115695381A (zh) * 2021-07-30 2023-02-03 中兴通讯股份有限公司 通信方法、信令控制网元、媒体控制网元及通信系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002109278A (ja) * 2000-10-02 2002-04-12 Kanazawa Inst Of Technology 代行依頼システム
WO2005067337A1 (en) * 2003-12-29 2005-07-21 Telefonaktiebolaget L M Ericsson (Publ) Dynamic selection of a packet data serving node
WO2006035871A1 (ja) * 2004-09-30 2006-04-06 Matsushita Electric Industrial Co., Ltd. 通信システム及び移動端末並びに認証サーバ

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002109278A (ja) * 2000-10-02 2002-04-12 Kanazawa Inst Of Technology 代行依頼システム
WO2005067337A1 (en) * 2003-12-29 2005-07-21 Telefonaktiebolaget L M Ericsson (Publ) Dynamic selection of a packet data serving node
WO2006035871A1 (ja) * 2004-09-30 2006-04-06 Matsushita Electric Industrial Co., Ltd. 通信システム及び移動端末並びに認証サーバ

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116033011A (zh) * 2023-03-31 2023-04-28 新云网科技集团股份有限公司 一种数据通信方法、装置、设备及存储介质

Also Published As

Publication number Publication date
CN101163150A (zh) 2008-04-16

Similar Documents

Publication Publication Date Title
US12114382B2 (en) Associated device discovery in IMS networks
USRE44412E1 (en) Digital home networks having a control point located on a wide area network
DK3007406T3 (en) PROCEDURE, DEVICES AND COMPUTER PROGRAM FOR DYNAMIC CONFIGURATION OF A PROXY CALL SESSION CONTROL FUNCTION OF THE IP MULTIMEDIA SUBSYSTEM FROM A POLICY CONTROL RULES SERVER
JP5175931B2 (ja) 使用される無線アクセス技術タイプと許容される無線アクセス技術タイプのマッチング
JP4994449B2 (ja) ネットワークにアクセスする方法、システムおよびデバイス
CA2613478C (en) System and method of device discovery and control in ip multimedia subsystem networks
JP4875165B2 (ja) ベアラへのユーザ装置ごとのサービス要求条件を保証する装置および方法
US8054780B1 (en) Transparent application data notification during IMS registrations
EP2037658B1 (en) Assignment of a serving entity in a communication system
US20100189017A1 (en) Method and apparatuses for influencing the invoking of a service provided by an application server to a user equipment
WO2008058486A1 (fr) Procédé d&#39;enregistrement de groupe d&#39;utilisateurs, procédé de mise à jour d&#39;état, équipement de traitement, entité de réseau ims et système de communication
US20230028216A1 (en) Method and apparatus for selecting user plane function
WO2008043305A1 (fr) Méthode de sélection d&#39;un courtier de services, et système permettant la sélection d&#39;un courtier de services
WO2008106885A1 (fr) Procédé et système permettant une compatibilité de services
WO2008113272A1 (fr) Procédé, système et dispositif de déclenchement de service

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07817017

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 07817017

Country of ref document: EP

Kind code of ref document: A1