WO2005069645A1 - Procede servant a limiter la charge d'interface d'un serveur d'abonnes local - Google Patents

Procede servant a limiter la charge d'interface d'un serveur d'abonnes local Download PDF

Info

Publication number
WO2005069645A1
WO2005069645A1 PCT/CN2005/000021 CN2005000021W WO2005069645A1 WO 2005069645 A1 WO2005069645 A1 WO 2005069645A1 CN 2005000021 W CN2005000021 W CN 2005000021W WO 2005069645 A1 WO2005069645 A1 WO 2005069645A1
Authority
WO
WIPO (PCT)
Prior art keywords
cscf
user
information
hss
message
Prior art date
Application number
PCT/CN2005/000021
Other languages
English (en)
French (fr)
Inventor
Yajuan Wu
Wenlin Zhang
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
Priority claimed from CNB2004100023103A external-priority patent/CN1299533C/zh
Priority claimed from CNB2004100042072A external-priority patent/CN100362838C/zh
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Priority to JP2006548075A priority Critical patent/JP4493104B2/ja
Priority to CA2552531A priority patent/CA2552531C/en
Priority to EP05700396A priority patent/EP1703746B1/en
Priority to US10/585,288 priority patent/US20070189215A1/en
Publication of WO2005069645A1 publication Critical patent/WO2005069645A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10Architectures or entities
    • H04L65/1016IP multimedia subsystem [IMS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066Session management
    • H04L65/1073Registration or de-registration
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/02Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/04Registration at HLR or HSS [Home Subscriber Server]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/02Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08Mobility data transfer
    • H04W8/12Mobility data transfer between location registers or mobility servers

Definitions

  • the present invention relates to the field of mobile communication technology, and in particular, to a server for reducing home subscription users.
  • mobile communications will not only be limited to traditional voice communications.
  • Data services such as presence, short message, web page browsing, positioning information, push service (PUSH), and file sharing
  • mobile communication can implement services of multiple media types, such as audio, video, pictures, and text, to meet the multiple needs of users.
  • the short message service can provide instant messaging, chat rooms, and multimedia short message services
  • the video service can provide entertainment, multimedia information, and daily communication services
  • the e-commerce service can provide product catalogs, search engines, shopping carts, order management, and Payment services
  • Game business can provide services such as single-player and group games
  • Positioning business can provide services such as tracing, guidance, and alarm
  • Personal assistant business can provide address books, calendars, bookmark luxury, file storage, events Reminders and email services.
  • IP-based Multimedia Subsystem IMS
  • 3GPP 3rd Generation Mobile Communication Standardization Partnership Project
  • 3GPP2 3rd Generation Mobile Communication Standardization Partnership Project 2
  • IMS IP-based Multimedia Subsystem
  • the IMS architecture is superimposed on the packet domain network and is composed of functional entities such as a Call State Control Function (CSCF) entity, a Media Gateway Control Function (MGCF) entity, a Media Resource Function (MRF) entity, and a Home Subscriber Subscriber Server (HSS).
  • CSCF can be divided into three service entities: service CSCF (S-CSCF), proxy CSCF (P-CSCF) and query CSCF (I-CSCF).
  • S-CSCF service CSCF
  • P-CSCF proxy CSCF
  • I-CSCF query CSCF
  • the three logical entities may be on different physical devices, or they may be on the same physical device. Within different functional modules of a physical device.
  • S-CSCF is the service switching center of IMS, which is used to perform session control, maintain session state, manage user information, generate billing information, etc .
  • P-CSCF is an access point for end users to access IMS, and is used to complete user registration. Quality of service (QoS) control and security management, etc .
  • I-CSCF is responsible for the inter-communication between IMS domains, manages the allocation of S-CSCF, hides the network topology and configuration information to the outside, and generates billing data.
  • MGCF is used to implement interworking between the IMS network and other networks; MRF is used to provide media resources, such as radio playback, codec, and multimedia conference bridge.
  • HSS is a very important user database that stores user's contract data information and configuration information, such as user identification, number, and addressing information; user security information; user location information and user profile information (user profile information), etc. .
  • HSS is used to support the processing of calls and sessions by various network entities. There are one or more HSSs in a home network. The specific number of HSSs depends on the number of mobile subscribers, the capacity of network equipment, and the specific networking situation.
  • the IMS network structure has nothing to do with the underlying bearer network
  • the IMS network defined by 3GPP can also be applied to other packet networks other than the packet domain network defined by 3GPP. Therefore, IMS is not restricted to be applied only to 3GPP-related networks and In applications, services and applications of other types of access networks and bearer networks can also be implemented using the IMS architecture.
  • a user includes at least one public user identifier, and the public user identifier is used to identify a service to be requested by the user.
  • All public user IDs of a user are registered separately, that is, the registration process of each public user ID is independent, but because these public user IDs belong to the same user, the specification states that when a user uses a public user ID After the registration is successful and the S-CSCF assigned by the network is obtained, the user uses another public user identity When registering, the network must return the same S-CSCF to the user. Registration has a life cycle.
  • the S-CSCF assigned by a network to a user each time is only responsible for processing all IMS session signaling related to the UE during this registration. For specific implementation, refer to the 3GPP TS 23.228 specification.
  • Each user who has signed an IMS service is assigned one or more private user IDs by the home network operator for use in the registration, authorization, management, and accounting processes.
  • NAI Network Access Identifier Each user who has signed an IMS service is assigned one or more private user IDs by the home network operator for use in the registration, authorization, management, and accounting processes.
  • NAI Network Access Identifier Private user identities are generally not publicly available, while public user identities are publicly available and are used during sessions that use various types of services.
  • the process of initiating registration for the public user identity based on the IMS architecture is taken as an example to specifically explain the interaction process between the HSS and the network entity.
  • FIG. 1 is a flowchart of the first registration of a public user identity based on the IMS architecture in the prior art.
  • the initial session protocol (SIP) is used as the signaling control protocol of the IP multimedia session, and the Cx interface between HSS and I-CSCF and HSS and S-CSCF uses Diameter protocol to transmit related information.
  • SIP initial session protocol
  • the Cx interface between HSS and I-CSCF and HSS and S-CSCF uses Diameter protocol to transmit related information.
  • the network topology hiding function is not needed, and the UE is in the visited network.
  • Step 101 After the user (UE) establishes a physical connection carried by the underlying layer, the user (UE) sends a Register message to the P-CSCF in the access network to which the user (UE) belongs, the message including: a public user identifier, a private user identifier, and a home network domain name. , And information such as the IP address of the UE applying for registration.
  • Step 102 The P-CSCF receiving the Register message parses the home network domain name information in the message to obtain the address of the home network access point I-CSCF, and then forwards the UE to the I-CSCF in the home network.
  • the Register message includes: the name or address of the P-CSCF, the public user identity, the private user identity, the identity of the network to which the P-CSCF is located, and the IP address of the UE applying for registration.
  • the Cx-Query message includes: Public user identity, private user identity, and the identity of the network where the P-CSCF is located.
  • Step 104 After receiving the Cx-Query message from the I-CSCF, the HSS first determines whether the UE is allowed to initiate a registration request in the current network according to the user's subscription information and the operator's policy. The I-CSCF returns a response message Cx-Query Resp containing the refusal to accept the registration information, and the I-CSCF returns a registration failure message to the user through the P-CSCF, and ends the process;
  • the HSS updates or upgrades the content of the subscription file of the requesting registered user according to whether the HSS holds the name of the S-CSCF that has served the UE.
  • the I-CSCF returns a corresponding letter. If the user applying for registration has at least one public user ID registered in the HSS, that is, the HSS itself holds the name of the S-CSCF serving the UE, and the S-CSCF is within the validity period. And, if the content of the subscription file of the requesting registered user saved by itself is not updated or upgraded, the HSS returns to the I-CSCF the Cx-Query Res containing the name of the S-CSCF currently serving the user, and executes step 107;
  • the user has at least one public user ID whose registration status is Unregistered or the registration has expired, but the name of the S-CSCF that the user last used is still stored in the HSS, or the user has been registered as unregistered
  • the called party is assigned an S-CSCF by the HSS, and the 'J HSS returns to the I-CSCF the Cx-Query Res containing the name of the S-CSCF served to the user, and executes step 107;
  • the HSS will After the I-CSCF returns a Cx-Query Resp containing the S-CSCF name and the existing S-CSCF capability set information, the I-CSCF further determines whether the returned S-CSCF name is available. If it can be used, step 107 is performed. Otherwise, step 105 is executed, the 1-CSCF reselects the S-CSCF; if the HSS itself does not already have an S-CSCF name that has been served for the UE, the HSS returns to the I-CSCF only the existing S-CSCF capabilities. After the Cx-Query Resp of the information is set, step 105 is performed.
  • Step 105 The I-CSCF sends a Cx-Select-Pull request message to the HSS, and the user authorization type (User-Authorization-Type) in the message is REGISTRATION— AND— CAPABILITIES, the purpose of which is to make it clear that the I-CSCF requires the HSS to return
  • the S-CSCF capability set information that supports the most stringent service contracting requirements of the registered user of the application is used as input information when selecting the S-CSCF.
  • the Cx-Select-Pull request message includes: public user identification, private user identification, and other information.
  • Step 106 After receiving the Cx-Select-Pull request message from the I-CSCF, the HSS returns a Cx-Select-Pull Resp message to the I-CSCF, and the Cx-Select-Pull Resp message includes: capable of supporting the application for registered users Step 107 of the S-CSCF capability set for the most stringent service contracting requirements, the I-CSCF performs domain name resolution based on the name of the S-CSCF returned by the HSS, or from the S-CSCF capability set that can support the most stringent business contracting requirements for the registered user of the application In the information, select an S-CSCF that can provide services to users, and then perform domain name resolution on the name of the S-CSCF to obtain the address of the S-CSCF, and send a Register message to the S-CSCF.
  • the Register message includes the P- CSCF domain name or address, public user identity, private user identity, identity of the network where the P-CSCF is located, IP address for applying for registration of UE
  • the I-CSCF If the I-CSCF cannot obtain a new S-CSCF based on the capability set information that can support the most stringent service contracting requirements of the registered user of the application, the I-CSCF gives the user a P-CSCF A registration failure message is returned, and the process ends.
  • Step 108 The S-CSCF sends a Cx-Put message to the HSS, so that the HSS saves the name of the S-CSCF for the user, where the Cx-Put message includes: a public user identifier and / or a private user identifier, and the S-CSCF name. And other information;
  • Step 109 The HSS returns a Cx-Put Resp response message, indicating that it has saved the name information of the S-CSCF;
  • Step 110 After receiving the Cx-Put Resp from the HSS, the S-CSCF sends a Cx-Pull request message to the HSS to request to obtain user subscription information.
  • the Cx-Pull message includes information such as a public user identity and a private user identity.
  • Step 111 The HSS performs an inquiry based on the public user identity and / or the private user identity, and returns a Cx-Pull Resp message including the user subscription information to the S-CSCF, that is, the Cx-Pull Resp message includes: user description information, and security information. Etc., where the user description information is used for users to access various service control platforms;
  • Step 112 The S-CSCF sends the registration information to the relevant service control platform to execute an appropriate service control process according to the filtering rules obtained from the user description information.
  • Step 113 The S-CSCF returns a 200 OK message to the UE through the I-CSCF and the P-CSCF.
  • the role of the Cx-Put message in step 108 is to request the HSS to save the name of the S-CSCF serving the user, and the Cx-Put Resp message in step 109 only indicates the confirmation of the above-mentioned request message; the Cx-Put in step 110
  • the role of the Pull message is to request the user subscription information required for subsequent processing from the HSS.
  • the Cx-Pull Resp in step 111 is to send the user subscription information to the S-CSCF.
  • the HSS uses two messages to save and confirm the S-CSCF name confirmation and return the user contract information to the S-CSCF, which increases The load on the Cx interface between HSS and S-CSCF.
  • Step 105 and step 106 are triggered because the information returned by the HSS to the I-CSCF in step 104 is incomplete. That is, if the HSS only returns information to the I-CSCF that includes the existing S-CSCF capability set, it needs to be triggered. Step 105 and step 106, to obtain information of an S-CSCF capability set capable of supporting the most stringent service subscription requirements of the registered user of the application.
  • steps 105 and 103 are basically the same. The only difference is that the user authorization type information is different, but this difference is only a type difference. It does not bring any new information to HSS. Similarly, in step 106, the information returned by the HSS does not return more and more valuable information to the I-CSCF. According to the above analysis, it can be seen that steps 105 and 106 are redundant steps, which increase the load on the interface between the HSS and the I-CSCF.
  • the purpose of the present invention is to provide two methods for reducing the load on the HSS interface to optimize business processes and reduce the load on the HSS interface.
  • a method for reducing the load on a server interface of a home subscriber includes the following steps:
  • the home subscription user server HSS After receiving a request message from the serving call status functional entity S-CSCF containing the request to save the name information of the S-CSCF and the user subscription information, the home subscription user server HSS first saves the S-CSCF name information in the message, and then According to the message The user ID in the query is queried, and a response message containing user subscription information is directly returned to the S-CSCF.
  • the method further comprises: the HSS, after receiving the inquiry S-CSCF information from the inquiry call status function entity I-CSCF, returns an inquiry response message to the I-CSCF containing the information required to determine the S-CSCF, The I-CSCF determines the S-CSCF capable of providing services to the user according to the information returned in the response message, and forwards the user's request message to the determined S-CSCF.
  • the HSS after receiving the inquiry S-CSCF information from the inquiry call status function entity I-CSCF, returns an inquiry response message to the I-CSCF containing the information required to determine the S-CSCF
  • the I-CSCF determines the S-CSCF capable of providing services to the user according to the information returned in the response message, and forwards the user's request message to the determined S-CSCF.
  • the HSS determines that the I-CSCF is not required to re-select an S-CSCF to serve the user, the determining S-CSCF
  • the required information is: the name of the S-CSCF currently serving the user;
  • the HSS allocates an S-CSCF, and the information required for determining the S-CSCF is: the name of the S-CSCF that has served the user;
  • the information required to determine the S-CSCF is: The S-CSCF name served for the UE and the S-CSCF capability set information that can support the most stringent service contracting requirements of the registered user;
  • the information required to determine the S-CSCF is: S-CSCF capability set information that can support the most stringent service subscription requirements of the registered user of the application.
  • the method for the I-CSCF to determine the S-CSCF capable of providing services to the user is: the I-CSCF determines the returned information
  • the S-CSCF in the S-CSCF can provide services to users;
  • the method by which the I-CSCF determines the S-CSCF capable of providing services to the user is: I-CSCF According to the S-CSCF capability set information returned in the response message, select a new S-CSCF that can meet the current user's business needs, and determine that the newly selected S-CSCF is an S-CSCF that can provide services to the user;
  • the method for the I-CSCF to determine the S-CSCF capable of providing services to the user is :
  • the I-CSCF judges whether the S-CSCF can meet the business needs of the current user based on the returned S-CSCF name. If so, determines that the returned S-CSCF is an S-CSCF capable of providing services to the user. Otherwise, according to The S-CSCF capability set information in the response message selects a new S-CSCF that can meet the service needs of the current user, and determines that the newly selected S-CSCF is an S-CSCF that can provide services to the user.
  • the HSS further includes: judging that the user UE is allowed to initiate in the current network according to the user's subscription information and the operator's policy. After registering the request, perform the next steps.
  • the HSS receives the message for querying S-CSCF information from the I-CSCF, which is carried by the Cx-Query message, and the query response message returned by the HSS to the I-CSCF, which contains the information needed to determine the S-CSCF, is sent by the Cx-Quer Resp Message bearer, or
  • the HSS receives the message from the I-CSCF to query the S-CSCF information, which is carried by the Cx-Select-pull message.
  • the query response message returned by the HSS to the I-CSCF which contains the information needed to determine the S-CSCF, is sent by the Cx- Select-pull Resp message bearer.
  • the HSS If the HSS itself holds the name of the S-CSCF that has served the UE, according to the system System configuration, the HSS returns a response message containing the S-CSCF name to the I-CSCF, and the I-CSCF forwards the user's request session message to the S-CSCF; or, the HSS returns the I-CSCF containing the S-CSCF name and
  • the I-CSCF can determine the S-CSCF capability set information that can support the user's most stringent service subscription requirements, and forward the user's request session message to the determined S-CSCF;
  • the HSS directly returns to the I-CSCF a response message containing the S-CSCF capability set information that can support the user's most stringent service subscription requirements, and then the I-CSCF Determine an S-CSCF capable of providing services to the user, and forward the user's request session message to the determined S-CSCF.
  • the HSS receives a message for querying S-CSCF information from the I-CSCF, which is carried by the Cx-Location-Query message, and the query response message returned by the HSS to the I-CSCF, which contains the information needed to determine the S-CSCF, is sent by the Cx- Location-Query Resp message bearer, or
  • the message that the HSS receives the I-CSCF query S-CSCF information is
  • the Cx-Select-pull message is carried, and the query response message returned by the HSS to the I-CSCF containing the information required to determine the S-CSCF is carried by the Cx-Select-pull Resp message.
  • the request message including the request to save the S-CSCF name information and the user subscription information is carried by a Cx-Put message
  • the response message returned by the HSS to the S-CSCF is carried by a Cx-Put Res message, or ,
  • the request message including the request to save the S-CSCF name information and the user subscription information is carried by a Cx-Pull message, and the response message returned by the HSS to the S-CSCF is carried by a Cx-Pull Resp message.
  • the user subscription information in the response message including the user subscription information returned to the S-CSCF includes at least description information of the user.
  • a method for reducing the load on a home subscription user server interface the method includes the following steps:
  • the HSS After the HSS receives the S-CSCF information query message from the I-CSCF, it returns a query response message to the I-CSCF containing the information required to determine the S-CSCF.
  • the I-CSCF returns the query response message according to the response message.
  • the information determines the S-CSCF capable of providing services to the user, and forwards the user's request message to the determined S-CSCF.
  • the HSS determines that the I-CSCF is not required to re-select an S-CSCF to serve the user, the determining S-CSCF
  • the required information is: the name of the S-CSCF currently serving the user;
  • the HSS allocates an S-CSCF, and the information required for determining the S-CSCF is: the name of the S-CSCF that has served the user;
  • the information required to determine the S-CSCF is: The S-CSCF name served for the UE and the S-CSCF capability set information that can support the most stringent service contracting requirements of the registered user;
  • the information required for determining the S-CSCF is: S-CSCF capability set information that can support the most stringent service contracting requirements of the registered user of the application.
  • the method for the I-CSCF to determine the S-CSCF capable of providing services to the user is: the I-CSCF determines that the S-CSCF in the returned information is S-CSCF capable of serving users; If the information returned by the HSS contains only the S-CSCF capability set information that can support the most stringent business contracting requirements of the registered user of the application, the method by which the I-CSCF determines the S-CSCF capable of providing services to the user is: According to the S-CSCF capability set information returned in the response message, select a new S-CSCF that can meet the current user's business needs, and determine that the newly selected S-CSCF is the S-CSCF that can provide services to the user;
  • the method for the I-CSCF to determine the S-CSCF capable of providing services to the user is :
  • the I-CSCF judges whether the S-CSCF can meet the business needs of the current user according to the returned S-CSCF name, and if so, determines that the returned S-CSCF is an S-CSCF capable of providing services to the user.
  • the S-CSCF capability set information in the home response message selects a new S-CSCF capable of meeting the current user service needs, and determines that the newly selected S-CSCF is an S-CSCF capable of providing services to the user.
  • the HSS further includes: judging that the user UE is allowed to initiate registration in the current network according to the user's subscription information and the operator's policy. After requesting, perform the next steps.
  • the HSS receives the message from the I-CSCF to query the S-CSCF information, which is carried by the Cx-Query message.
  • the query response message returned by the HSS to the I-CSCF, which contains the information required to determine the S-CSCF, is sent by the Cx-Query Res. Message bearer, or
  • the HSS receives the message from the I-CSCF to query the S-CSCF information, which is carried by the Cx-Select-pull message.
  • the query response message returned by the HSS to the I-CSCF which contains the information needed to determine the S-CSCF, is sent by the Cx- Select-pull Resp message bearer.
  • the HSS If the HSS itself holds the name of the S-CSCF that has served the UE, according to the system configuration, the HSS returns a response message containing the S-CSCF name to the I-CSCF, and the The I-CSCF forwards the user's request session message to the S-CSCF; or, the HSS returns to the I-CSCF the S-CSCF capability set information containing the name of the S-CSCF and the user's most stringent service subscription requirements.
  • the I-CSCF Determining an S-CSCF capable of providing services to the user, and forwarding the user's request session message to the determined S-CSCF;
  • the HSS directly returns to the I-CSCF a response message containing the S-CSCF capability set information that can support the user's most stringent service subscription requirements, and then the I-CSCF Determine an S-CSCF capable of providing services to the user, and forward the user's request session message to the determined S-CSCF.
  • the HSS receives the message from the I-CSCF to query the S-CSCF information, which is carried by the Cx-Location-Query message, and the query response message returned by the HSS to the I-CSCF containing the information needed to determine the S-CSCF is sent by the Cx- Location-Query Resp message bearer, or
  • the HSS receives the message from the I-CSCF to query the S-CSCF information, which is carried by the Cx-Select-pull message.
  • the query response message returned by the HSS to the I-CSCF which contains the information needed to determine the S-CSCF, is sent by the Cx- Select-pull Resp message bearer.
  • the HSS when the HSS receives a request message from the S-CSCF containing the request to save the S-CSCF name information and the user subscription information, it first saves the name of the S-CSCF in the message, and then the queried user
  • the contract information is directly returned to the S-CSCF that applied for query, thereby simplifying the steps of querying user contract information, optimizing business processes, and reducing the load on the HSS interface.
  • the HSS receives a request message from the I-CSCF containing the query S-CSCF name or capability set information, it directly reports to the I-CSCF -CSCF returns a response message containing the S-CSCF name and S-CSCF capability set information that can support the user's most stringent service subscription requirements, and then Then continue to perform the subsequent steps.
  • the redundant steps in the prior art are refined, the user registration process and session process are optimized, and the load of the HSS interface is reduced.
  • the invention has no impact on the existing network structure and service implementation, and does not need to modify the existing interface specifications, so it has good compatibility and scalability.
  • FIG. 1 is a flowchart of the first registration of a public user identity based on the IMS architecture in the prior art
  • FIG. 2 is a flowchart of an embodiment in which a public user identity based on the IMS architecture is applied to initiate registration for the first time;
  • FIG. 2A shows a flowchart of another embodiment in which a public user identity based on the IMS architecture of the present invention is first registered
  • FIG. 3 is a flowchart showing the registration of a public user identity based on the IMS architecture not being initiated for the first time;
  • FIG. 4 shows a partial call flow chart of an embodiment of a user based on the IMS framework as a called party to which the present invention is applied;
  • FIG. 4A shows a partial call flow chart of another embodiment of a user based on an IMS framework as a called party to which the present invention is applied.
  • the idea of the present invention is: After receiving the request message from the S-CSCF containing the request to save the S-CSCF name information and the user subscription information, the HSS first saves the S-CSCF name information in the message, and then according to the message The user ID in the query, and A response message containing the user subscription information is directly returned to the S-CSCF.
  • the HSS receives a request message from the I-CSCF containing the query S-CSCF name or capability set information, it directly returns to the I-CSCF a message containing the S-CSCF name and / or capable of supporting the user's most stringent service contracting requirements.
  • the I-CSCF determines the final S-CSCF according to the information returned in the response message, and forwards the user's request message to the final S-CSCF.
  • FIG. 2 is a flowchart of an embodiment in which a public user identity based on the IMS architecture of the present invention is firstly registered.
  • the SIP protocol is used as the signaling control protocol of the IP multimedia session.
  • the Cx interface between HSS and I-CSCF and HSS and S-CSCF uses Diameter protocol to transmit related information.
  • a network topology hiding function is required, and the UE is in the visited network.
  • step 201 after the UE establishes the physical connection of the underlying bearer, it sends a Register message to the P-CSCF in the visited network to which the UE belongs.
  • the message includes: a public user identifier, a private user identifier, a home network domain name, and an IP for applying for registration of the UE. Address and other information.
  • Step 202 The P-CSCF that receives the Register message, parses the home network domain name information in the message to obtain the address of the home network access point I-CSCF, and then forwards the UE's Register to the I-CSCF in the home network.
  • the forwarded Register message includes: the name or address of the P-CSCF, the public user identity, the private user identity, the identity of the network to which the P-CSCF is located, and the IP address of the UE applying for registration.
  • Step 203 The I-CSCF sends a Cx-Query message to the HSS, and the user authorization type (User- Authorization-Type) in the message is REGISTRATION, which indicates that it is a registration request message.
  • the Cx-Query message includes: the public user identifier , The identity of the private user, and the identity of the network where the P-CSCF is located.
  • Step 204 After receiving the Cx-Query message from the I-CSCF, the HSS first determines whether the UE is allowed in the current network according to the user's subscription information and the operator's policy. If the registration request is not allowed, the C-Query Resp response message containing the refusal to accept the registration information is returned directly to the I-CSCF, and the I-CSCF returns a registration failure message to the user through the P-CSCF. Process;
  • the HSS updates or upgrades the content of the subscription file of the requesting registered user according to whether the HSS holds the name of the S-CSCF that has served the UE.
  • the I-CSCF returns a corresponding letter. If the user applying for registration has at least one public user ID registered in the HSS, that is, the HSS itself holds the name of the S-CSCF serving the UE, and the S-CSCF is in the validity period. And, if the content of the contracted file of the requesting registered user saved by itself is not updated or upgraded, the HSS returns to the I-CSCF the Cx-Query Res containing the name of the S-CSCF currently serving the user, and performs step 207;
  • the HSS allocates an S-CSCF, and the HSS returns to the I-CSCF the Cx-Query Resp containing the name of the S-CSCF served to the user, and executes step 207;
  • the HSS If the HSS itself holds the name of the S-CSCF that has served the UE, and the HSS thinks that the I-CSCF may need to re-select an S-CSCF to serve the user, for example, the content of the contract file of the requesting registered user that has been saved by itself occurs After the update or upgrade, the HSS returns a Cx-Query Resp containing the S-CSCF name and the existing S-CSCF capability set information to the I-CSCF, and the I-CSCF further determines whether the returned S-CSCF name is available, if it can If it is used, go to step 207, otherwise, go to step 205, 1-CSCF re-selects the S-CSCF; if the HSS itself does not have an assigned S-CSCF name for the UE, the HSS only returns to the I-CSCF Cx-Query of existing S-CSCF capability set information After Resp, step 205.
  • Step 205 The I-CSCF sends a Cx-Select-Pull request message to the HSS.
  • the user-authorization-type in the message is REGISTRATION— AND— CAPABILITIES, the purpose of which is to clearly indicate that the I-CSCF requires the HSS to return
  • the S-CSCF capability set information that supports the most stringent service contracting requirements of the registered user of the application is used as input information when selecting the S-CSCF.
  • the Cx-Select-Pull request message includes: public user identification, private user identification, and other information.
  • Step 206 After receiving the Cx-Select-Pull request message from the I-CSCF, the HSS returns a Cx-Select-Pull Resp message to the I-CSCF, where the Cx-Select-Pull Resp message includes: capable of supporting the application for registered users S-CSCF capability set information required for the most stringent service contract.
  • Step 207 The I-CSCF performs domain name resolution according to the name of the S-CSCF returned by the HSS, or selects an S-CSCF capable of providing services to the user from the S-CSCF capability set information that can support the most stringent business subscription requirements of the registered user of the application.
  • the S-CSCF perform domain name resolution on the name of the S-CSCF to obtain the address of the S-CSCF, and send a Register message to the S-CSCF, where the Register message includes the P-CSCF domain name or address, public user identity, private user identity, The identity of the network where the P-CSCF is located, the IP address of the application for registration of the UE; if the I-CSCF cannot obtain a new S-CSCF based on the capability set information that can support the most stringent service contracting requirements of the registered user of the application, the I-CSCF The P-CSCF returns a registration failure message to the user and ends this process.
  • Step 208 The S-CSCF sends a request message to the HSS that contains the request to save the S-CSCF name information and the user subscription information.
  • the message includes: public user identification and / or private user identification, S-CSCF name and other information; and
  • the message can be carried by a Cx-Put message or a Cx-Pull message;
  • Step 209 The HSS receives a request from the S-CSCF to save the S-CSCF name information.
  • the S-CSCF name in the message is first saved, and then a local query is performed according to the public user identifier and / or the private user identifier, and a response containing the user contract information is directly returned to the S-CSCF.
  • the user contract information in the response message includes user description information, and security information, where the user description information is used for the user to access various service control platforms; the response message is a Cx-Put Resp message or Cx-Pull Resp message 7 is included.
  • Step 210 The S-CSCF sends the registration information to the relevant service control platform to execute an appropriate service control process according to the filtering rules obtained from the user description information.
  • Step 211 The S-CSCF returns a 200K message to the UE through the I-CSCF and the P-CSCF.
  • the S-CSCF queries the HSS for user description information, which reduces the load on the HSS interface.
  • steps 205 and 206 can be further refined so that the I-CSCF can obtain the required information once.
  • steps 205 and 206 see FIG. 2A. Because the difference between FIG. 2A and FIG. 2 is that steps 205 and 206 are omitted, steps 201 to 203 in FIG. 2 and steps 201a to 203a in FIG. 2A Exactly the same, the description is not repeated here.
  • Step 204a performs the following operations:
  • the HSS After receiving the Cx-Query message from the I-CSCF, the HSS first determines whether the UE is allowed to initiate a registration request in the current network according to the user's subscription information and the operator's policy. If it is not allowed, it directly sends the request to the I-CSCF. Return the response message Cx-Query Resp containing the refusal to accept the registration information, and then the I-CSCF returns the registration failure message to the user through the P-CSCF, and the process ends;
  • the HSS will register according to whether it holds the name of the S-CSCF that has served the UE, and the request registration saved by itself. If the content of the user's contract file is updated or upgraded, a corresponding letter is returned to the I-CSCF.
  • the HSS determines that the I-CSCF does not need to re-select an S-CSCF to serve the user, for example, the content of the contract file of the requesting registered user saved by itself is not updated or upgraded,
  • the HSS returns to the I-CSCF a Cx-Query Resp containing the name of the S-CSCF currently serving the user, and performs step 205a;
  • the HSS allocates an S-CSCF, and the HSS returns to the I-CSCF the Cx-Query Resp containing the name of the S-CSCF served to the user, and then executes step 205a;
  • the HSS directly returns to the I-CSCF a response message containing the S-CSCF name and the S-CSCF capability set information that can support the most stringent business contracting requirements of the registered user of the application, and performs step 205a;
  • the HSS If the HSS itself has not assigned the name of the S-CSCF that has served the U3 ⁇ 4, the HSS returns a response message to the I-CSCF containing the S-CSCF capability set information that can support the most stringent service subscription requirements for the registered user of the application. Go to step 205a.
  • the HSS receives the query request message from the I-CSCF and is carried by the Cx-Query message, and the response message returned by the HSS to the I-CSCF is carried by the Cx-Query Resp message.
  • the HSS receives the I-CSCF message from the I-CSCF.
  • -CSCF query request message can also be The Cx-Select-pull message is carried, and the HSS returns ⁇
  • the response message can also be carried by the Cx-Select-pull Resp message.
  • step 205a in FIG. 2A is also equivalent to step 207 in FIG. 2.
  • the operation performed by step 205a is as follows:
  • the I-CSCF determines the S-CSCF capable of providing services to users based on the information returned by the HSS, and performs domain name resolution based on the name of the S-CSCF to obtain the S-CSCF address.
  • the specific process is: If the HSS returns a response message containing only the S-CSCF name, the I-CSCF determines that the S-CSCF is an S-CSCF capable of providing services to the user; if the HSS returns only contains the most capable of supporting the application for registered users In response to the S-CSCF capability set information required by the strict service contract, the I-CSCF selects a new S-CSCF based on the S-CSCF capability set information and can satisfy the current user service needs, and determines the newly selected S- The CSCF is an S-CSCF capable of providing services to the user; if the HSS returns a response message containing the S-CSCF name that has served the UE and the S-CSCF capability set information that can support the most stringent service subscription requirements for the registered user of the application
  • Steps 206a to 209a are exactly the same as steps 208 to 211 in FIG. 2 and will not be repeated here.
  • FIG. 3 is a flowchart illustrating the registration of a public user identity based on the IMS architecture not initiated for the first time by applying the present invention.
  • the SIP protocol is used as the signaling control protocol of the IP multimedia session.
  • the Cx interface between HSS and I-CSCF and HSS and S-CSCF uses Diameter protocol to transmit relevant information. There is no description information of related users in the S-CSCF, and the network topology hiding function is not required in this embodiment, and the UE is accessing Ask the network.
  • Step 301 The UE sends a Register message to the P-CSCF in the visited network to which the UE belongs, and the message includes: a public user identifier, a private user identifier, a home network domain name, and information such as an IP address of the UE for which registration is requested.
  • Step 302 The P-CSCF receiving the Register message parses the home network domain name information in the message to obtain the address of the home network access point I-CSCF, and then forwards the UE's Register to the I-CSCF in the home network.
  • the forwarded Register message includes: the name or address of the P-CSCF, the public user identity, the private user identity, the identity of the network to which the P-CSCF is located, and the IP address of the UE applying for registration.
  • Step 303 The I-CSCF sends a Cx-Query message to the HSS.
  • the Cx-Query message includes information such as a public user identity, a private user identity, and an identity of a network where the P-CSCF is located.
  • Step 304 the HSS receives the Cx-Query message from the I-CSCF, and determines that the user has already registered, and directly returns a response message Cx-Query Resp to the I-CSCF containing an indication that the user has been assigned S-CSCF information.
  • the Cx-Query Resp includes a name of an S-CSCF that has been serving the user ⁇ _.
  • Step 305 The I-CSCF performs domain name resolution according to the name of the S-CSCF returned by the HSS, obtains the address of the S-CSCF, and sends a Register message to the S-CSCF.
  • the Register message includes the P-CSCF domain name or address, and the public user identifier. , The private user identity, the identity of the network where the P-CSCF is located, and information such as the application for registration of the IP address of the UE.
  • Step 306 The S-CSCF sends a request message to the HSS that contains the request to save the S-CSCF name information and the user subscription information.
  • the message includes: public user identification and / or private user identification, S-CSCF name and other information; and
  • the message can be carried by a Cx-Put message or a Cx-Pull message;
  • Step 307 The HSS receives a request from the S-CSCF to save the name information of the S-CSCF.
  • the S-CSCF name in the message is first saved, and then a local query is performed according to the public user identifier and / or the private user identifier, and a response containing the user contract information is directly returned to the S-CSCF.
  • the user contract information in the response message includes user description information, and security information, where the user description information is used for the user to access various service control platforms; the response message is a Cx-Put Resp message or Cx-Pull Res message bearer.
  • Step 308 The S-CSCF sends the registration information to the relevant service control platform to execute an appropriate service control process according to the filtering rules obtained from the user description information.
  • Step 309 The S-CSCF returns a 200 OK message to the UE through the I-CSCF and the P-CSCF.
  • FIG. 4 shows a partial call flow chart of an embodiment of an IMS-based user as a called party to which the present invention is applied.
  • the SIP protocol is used as the signaling control protocol of the IP multimedia session.
  • the Cx interface between HSS and I-CSCF and HSS and S-CSCF uses Diameter protocol to transmit relevant information. There is no description information of the related user in the S-CSCF, and the public user identity used by the user has not been registered.
  • Step 401 The I-CSCF receives the forwarded INVITE message from the calling user, where the message includes public user identification information.
  • Step 402 The 1-CSCF sends a location query message (Cx-Location-Query) message to the HSS to query the current location information of the user.
  • Cx-Location-Query a location query message
  • Step 403 According to the pre-configuration of the system, the HSS returns a response message Cx-Location-Query Resp to the I-CSCF containing the unregistered information indicating the public user ID, and then executes step 404, or the HSS returns to the I-CSCF a message containing After the user assigns the S-CSCF name information and the existing S-CSCF capability set information, step 404 is performed, or the HSS sends the I-CSCF Return a response message Cx-Location-Query Resp containing S-CSCF name information previously assigned to the user, and execute step 407.
  • the I-CSCF sends a Cx-Select-Pull request message to the HSS to request to obtain the S-CSCF capability set information that can support the most stringent requirements.
  • the parameters carried in the request message mainly include: public user identity and so on.
  • Step 405 After receiving the Cx-Select-Pull request message, the HSS returns a Cx-Select-Pull Resp message to the I-CSCF.
  • the message includes the S- that the I-CSCF needs to support the user's most stringent service subscription requirements. CSCF capability set information.
  • Step 406 The I-CSCF selects an S-CSCF capable of serving the user from the S-CSCF capability set information returned by the HSS, and resolves the S-SCSF address according to the name of the S-CSCF, and then executes step 407 ;
  • the I-CSCF designates an S-CSCF itself to serve the unregistered public user identity, and then executes the steps 407. '
  • Step 407 The 1-CSCF forwards the received INVITE message to the determined S-CSCF.
  • Step 408 The S-CSCF that receives the INVITE message sends a request message to the HSS that contains the request to save the S-CSCF name information and the user subscription information.
  • the message includes: a public user identifier and / or a private user identifier, and the S-CSCF name. And other information; and the message may be carried by a Cx-Put message or a Cx-Pull message.
  • Step 409 After receiving the message from the S-CSCF requesting to save the S-CSCF name information and requesting the user's subscription information, the HSS first saves the S-CSCF name in the message, and then the public user identity and / or private user The identifier is queried locally, and a response message containing user subscription information is directly returned to the S-CSCF, that is, the user subscription information in the response message includes user description information and security information, and the user description information is used for user access.
  • the response message is composed of Cx-Put Resp message or Cx-Pull Res message bearer.
  • Step 410 The S-CSCF sends the registration information to the relevant service control platform to execute an appropriate service control process according to the filtering rules obtained from the user description information.
  • Step 411 The S-CSCF continues to perform subsequent operations.
  • the above call flow streamlines the steps for the S-CSCF to query the user description information from the HSS and reduces the load on the HSS interface.
  • steps 404 and 405 can be further streamlined in the above process, so that the I-CSCF can obtain the required information one time.
  • steps 404 and 405 are simplified, see FIG. 4A. Because the difference between FIG. 4A and FIG. 4 is that steps 404 to 4064 are omitted, steps 401 to 402 in FIG. 4 are exactly the same as steps 401a to 402a in FIG. 4A. , Which will not be repeated here.
  • Step 403a performs the following operations:
  • the HSS After receiving the message from the I-CSCF that contains the user's current location information, the HSS determines whether it holds the name of the S-CSCF that has served the UE. If the HSS itself holds the name of the S-CSCF that has served the UE, Name, according to the system configuration, the HSS returns an I-CSCF response message containing the S-CSCF name, or the HSS returns the I-CSCF containing the S-CSCF name and the S-CSCF capability that can support the user ’s most stringent service contracting requirements After collecting information, perform step 404a;
  • the HSS directly returns to the I-CSCF a response message containing S-CSCF capability set information capable of supporting the user's most stringent service subscription requirements, and then executes step 404a.
  • step 404a in FIG. 4A is also equivalent to step 406 in FIG. 4, and the operation performed by step 404a is as follows:
  • the I-CSCF determines the S-CSCF capable of providing services to users based on the information returned by the HSS, and performs domain name resolution based on the name of the S-CSCF to obtain the address of the S-CSCF.
  • the specific process is as follows: If the HSS returns a response message containing only the S-CSCF name, the I-CSCF does The S-CSCF is determined to be an S-CSCF capable of providing services to the user; if the HSS returns a response message containing only the S-CSCF capability set information that can support the most stringent business contracting requirements of the registered user of the application, the I-CSCF is based on the S -CSCF capability set information Select a new S-CSCF that can meet the current user's business needs, and determine that the newly selected S-CSCF is an S-CSCF that can provide services to the user; if the HSS returns include the service that has served the UE The S-CSCF name and the response message that can support the S-CSCF capability set information required by the user
  • the returned S-CSCF is an S-CSCF capable of providing services to the user; otherwise, a new S-CSCF capable of meeting the current user's service needs is selected according to the S-CSCF capability set information in the response message.
  • CSCF and determine that the newly selected S-CSCF is an S-CSCF capable of providing services to users.
  • the I-CSCF designates an S-CSCF for the An unregistered public user ID.
  • the above-mentioned HSS receives the query message from the I-CSCF carried by the Cx-Location-Queiy message, and the response message returned by the HSS to the I-CSCF is carried by the Cx-Location-Quer Resp message, or the above HSS receives the message from the I-CSCF
  • the query message is carried by the Cx-Select-puU message, and the response message returned by the HSS to the I-CSCF is carried by the Cx-Select-pull Resp message.
  • Steps 405a to 409a are completely the same as steps 407 to 411 in FIG. 4 and will not be repeated here.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Databases & Information Systems (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Description

减轻归属签约用户服务器接口负荷的方法 技术领域
本发明涉及移动通信技术领域, 特别是指减轻归属签约用户服务器
( HSS )接口负荷的方法。 发明背景
随着宽带网络的发展, 移动通信将不仅仅局限于传统的话音通信, 通过与呈现业务(presence ), 短消息、 网页 (WEB )浏览、 定位信息、 推送业务(PUSH ) 以及文件共享等数据业务的结合, 移动通信能够实 现音频、 视频、 图片和文本等多种媒体类型的业务, 以满足用户的多种 需求。
例如, 短消息业务能够提供即时消息、 聊天室以及多媒体短消息的 服务; 视频业务能够提供娱乐、 多媒体信息和日常交流等服务; 电子商 务业务能够提供产品目录、 搜索引擎、 购物车、 订单管理以及支付等服 务; 游戏业务能够提供单人游戏和群组游戏等服务; 定位业务能够提供 寻人、 向导以及报警等服务; 个人助理业务能够提供地址本、 日程表、 书签奢理、 文件存储、 事件提醒以及电子邮件等服务。
第三代移动通信标准化伙伴项目' ( 3GPP )以及第三代移动通信标准 化伙伴项目 2 ( 3GPP2 )等组织都先后推出了基于 IP 的多媒体子系统 ( IMS )架构, 其目的是在移动网络中使用一种标准化的开放结构来实 现多种多样的多媒体应用, 以给用户提供更多的选择和更丰富的感受。
IMS架构叠加在分组域网络之上, 由呼叫状态控制功能(CSCF )实 体、 媒体网关控制功能(MGCF ) 实体、 媒体资源功能(MRF ) 实体和 归属签约用户服务器 (HSS )等功能实体组成。 CSCF又可以分成服务 CSCF ( S-CSCF )、 代理 CSCF ( P-CSCF )和 查询 CSCF ( I-CSCF )三个遷辑实体, 该三个逻辑实体可能在不同的物 理设备上,也可能在同一个物理设备的不同功能模块内。 S-CSCF是 IMS 的业务交换中心, 用于执行会话控制, 维持会话状态, 管理用户信息, 产生计费信息等; P-CSCF是终端用户接入 IMS的接入点, 用于完成用 户注册, 服务质量( QoS )控制和安全管理等; I-CSCF负责 IMS域之间 的互通, 管理 S-CSCF的分配, 对外隐藏网络拓朴结构和配置信息, 并 产生计费数据等。
MGCF用于实现 IMS网絡和其它网络的互通; MRF用于提供媒体 资源, 如收放音, 编解码和多媒体会议桥等。
HSS是非常重要的用户数据库, 存储用户的签约数据信息和配置信 息等; 如用户的标识、 编号以及寻址信息; 用户的安全信息; 用户的位 置信息以及用户的描述信息 (user profile information )等。 HSS用于支 持各个网络实体对呼叫和会话的处理。 一个归属网络内有一个或者一个 以上 HSS, HSS的具体数量取决于移动签约用户的数量、 网络设备的容 量以及具体的组网情况。
因为 IMS网络结构做到了和底层承载网络无关, 因此 3GPP定义的 IMS 网络也可以应用在 3GPP 定义的分组域网络之外的其他分组网络 上, 因此在这里不限制 IMS只应用在 3GPP相关的网络和应用上, 其他 类型的接入网络和承载网络的业务和应用也可以用 IMS架构来实现。
一个用户至少包括一个公共用户标识, 该公共用户标识用于标识用 户待请求的业务。 一个用户的所有公共用户标识分別进行注册, 即每个 公共用户标识的注册过程是独立的, 但是因为这些公共用户标识都属于 同一个用户, 所以规范中规定, 当某个用户使用一个公共用户标识注册 成功, 得到网络为其分配的 S-CSCF后, 该用户使用其它公共用户标识 进行注册时, 网络必须返回同一个 S-CSCF给用户使用。 注册是有生存 周期的, 网络为某个用户每次分配的 S-CSCF, 只负责处理在此次注册 期间所有和该 UE相关的 IMS会话信令, 具体实现参见 3GPP TS 23.228 规范。
每个签署了 IMS业务的用户都由归属网络运营商为其分配了一个或 一个以上私有用户标识, 用于在注册、 授权、 管理和计费过程中使用, 该标识使用网洛接入标识(NAI Network Access Identifier ) 的格式。 私 有用户标识一般不对外公开, 而公共用户标识是对外公开的, 在使用各 类业务的会话过程中使用。
下面以基于 IMS构架的公共用户标识第一次发起注册的流程为例, 具体说明 HSS与网络实体之间的交互过程。
图 1所示为现有技术的基于 IMS构架的公共用户标识第一次发起注 册的流程图。 在本实施例中, 使用初始会话协议(SIP )作为 IP多媒体 会话的信令控制协议, HSS和 I-CSCF以及 HSS和 S-CSCF之间的 Cx 接口使用 Diameter协议来传送相关信息的,本实施例中不需要网络拓朴 隐藏功能, UE处于访问网络中。
步驟 101 , 用户 (UE )建立了底层承载的物理连接之后, 向其所属 的访问网络中的 P-CSCF发送注册(Register )消息, 该消息中包括: 公 共用户标识, 私有用户标识, 归属网络域名, 以及申请注册 UE的 IP地 址等信息。
, 步骤 102, 接收到 Register消息的 P-CSCF, 对该消息中的归属网络 域名信息进行解析, 以获取归属网絡接入点 I-CSCF的地址, 然后向归 属网络中的 I-CSCF转发 UE的 Register消息, 该转发的 Register消息中 包括: P-CSCF的名称或者地址,公共用户标识,私有用户标识, P-CSCF 所在访问网络的标识, 以及申请注册 UE的 IP地址等信息。 步骤 103 , I-CSCF发送查询(Cx-Query ) 消息给 HSS, 该消息中的 用户授权类型 ( User- Authorization-Type ) 为 REGISTRATION, 其表明 是一次注册请求消息, 该 Cx-Query 消息中包括: 公共用户标识, 私有 用户标识, 以及 P-CSCF所在网络的标识等信息。
步骤 104, HSS接收到来自 I-CSCF的 Cx-Query消息后, 首先根据 用户的签约信息以及运营商的策略, 判断是否允许该 UE在当前的网络 内发起注册请求, 如果不允许, 则直接给 I-CSCF返回包含拒绝接受此 次注册信息的应答消息 Cx-Query Resp, 再由 I-CSCF通过 P-CSCF给用 户返回注册失败的消息, 结束本流程; '
如果允许 UE在当前的网络内发起注册请求, 则 HSS根据自身是否 保存有为该 UE服务过的 S-CSCF的名称, 以及自身保存的该请求注册 用户的签约文件内容是否发生更新或者升级, 给 I-CSCF返回相应的信 如果申请注册的用户至少有一个公共用户标识曾在 HSS中进行了注 册, 即 HSS 自身保存有为该 UE服务的 S-CSCF的名称, 且该 S-CSCF 处于有效期内, 而且自身保存的该请求注册用户的签约文件内容没有发 生更新或者升级, 则 HSS 给 I-CSCF 返回包含当前为该用户服务的 S-CSCF名称的 Cx-Query Res 后, 执行步驟 107;
如果该用户至少有一个公共用户标识的注册状态是未注册 ( Unregistered )或者注册已经过期, 但 HSS 中还保存有该用户上次使 用的 S-CSCF的名称, 或者, 该用户曾作为没有注册的被叫由 HSS分配 了一个 S-CSCF, 贝' J HSS给 I-CSCF返回包含该为用户服务过 S-CSCF 名称的 Cx-Query Res 后, 执行步骤 107;
如果 HSS自身保存有为该 UE服务过的 S-CSCF的名称, 且自身保 存的该请求注册用户的签约文件内容发生了更新或者升级, 则 HSS 给 I-CSCF返回包含 S-CSCF名称和现有的 S-CSCF能力集信息的 Cx-Query Resp后, 由 I-CSCF进一步判断返回的 S-CSCF名称是否可用 , 如果可 以使用,则执行步驟 107,否则,执行步骤 105 , 1-CSCF重新选择 S-CSCF; 如果 HSS自身没有已经分配的为该 UE服务过的 S-CSCF的名称, 则 HSS只给 I-CSCF返回包含现有的 S-CSCF能力集信息的 Cx-Query Resp后, 执行步骤 105。
步骤 105, I-CSCF向 HSS发送 Cx-Select-Pull请求消息, 该消息中 的 用 户 授 权 类 型 ( User-Authorization-Type ) 为 REGISTRATION— AND— CAPABILITIES, 其目的是明确表明 I-CSCF要 求 HSS返回能够支持该申请注册用户最严格业务签约要求的 S-CSCF能 力集信息, 作为选择 S-CSCF时的输入信息, 该 Cx-Select-Pull请求消息 中包括: 公共用户标识, 私有用户标识等信息。
步骤 106, HSS接收到来自 I-CSCF的 Cx-Select-Pull请求消息后, 给 I-CSCF返回 Cx-Select-Pull Resp消息 , 该 Cx-Select-Pull Resp消息中 包括: 能够支持该申请注册用户最严格业务签约要求的 S-CSCF能力集 步骤 107, I-CSCF根据 HSS返回的 S-CSCF的名称进行域名解析, 或者, 从能够支持该申请注册用户最严格业务签约要求的 S-CSCF能力 集信息中选择一个能够为用户提供服务的 S-CSCF, 然后再对该 S-CSCF 的名称进行域名解析, 得到 S-CSCF的地址, 向该 S-CSCF发送 Register 消息, 该 Register消息中包括 P-CSCF域名或者地址, 公共用户标识, 私有用户标识, P-CSCF所在网络的标识, 申请注册 UE的 IP地址等信 白 ·
如果 I-CSCF无法根据能够支持该申请注册用户最严格业务签约要 求的能力集信息得到一个新的 S-CSCF, 则 I-CSCF通过 P-CSCF给用户 返回注册失败的消息, 结束本流程。
步骤 108, S-CSCF给 HSS发送 Cx-Put消息, 以使 HSS保存用于该 用户的 S-CSCF的名称, 其中该 Cx-Put消息包括: 公共用户标识和或私 有用户标识, S-CSCF名称等信息;
步骤 109, HSS返回 Cx-Put Resp应答消息,表明其已保存该 S-CSCF 的名称信息;
步骤 110, S-CSCF接收到来自 HSS的 Cx-Put Resp后, 向 HSS发送 Cx-Pull请求消息, 请求获取用户签约信息; 该 Cx-Pull消息中包括: 公 共用户标识和或私有用户标识等信息;
步驟 111 , HSS根据公共用户标识和或私有用户标识进行查询, 并 给 S-CSCF返回包括用户签约信息的 Cx-Pull Resp消息, 即该 Cx-Pull Resp消息中包括: 用户描述信息, 以及安全信息等, 其中的用户描述信 息用于用户接入到各种业务控制平台;
步骤 112, S-CSCF根据从用户描述信息中得到的过滤规则, 将注册 信息发送到相关的业务控制平台执行适当的业务控制流程;
步骤 113 , S-CSCF通过 I-CSCF以及 P-CSCF, 给 UE返回 200OK 消息。
至此, 该用户的一个公共用户标识完成第一次注册。
在上述流程中, 步骤 108中 Cx-Put消息的作用是请求 HSS保存为 用户服务的 S-CSCF的名称,步骤 109中 Cx-Put Resp消息仅仅表明对上 述请求消息的确认; 步骤 110中 Cx-Pull消息的作用是向 HSS请求后续 处理所需的用户签约信息, 步骤 111的 Cx-Pull Resp才是将用户的签约 信息发送给 S-CSCF。
通过上述分析可以看出, 在现有实现中, HSS将对 S-CSCF名称的 确认保存信息和给 S-CSCF返回用户签约信息用两条消息实现, 其增加 了 HSS和 S-CSCF之间 Cx接口的负荷。
上述步骤 105 和步骤 106 的触发是由于步骤 104 中 HSS返回给 I-CSCF的信息不全而导致的,即如果 HSS只给 I-CSCF返回包含现有的 S-CSCF能力集的信息, 则需要触发步骤 105和步骤 106, 以获取能够支 持该申请注册用户最严格业务签约要求的 S-CSCF能力集的信息。
而步骤 105与步驟 103的请求消息中, 所携带的信息基本相同, 其 唯一的区别在于用户授权类型信息有所差别, 但这种差别仅仅是类型的 区别而已, 其并没有带给 HSS任何新的信息, 同样地, 在步骤 106中, HSS所返回的倌息也没有给 I-CSCF返回更多的更有价值的信息。 根据 上述分析可以看出, 步驟 105和步骤 106是冗余的步驟, 其增加了 HSS 和 I-CSCF之间接口的负荷。
虽然上述分析基于用户的某个公共用户标识第一次进行注册的过 程,但在用户的某个公共用户标识进行非第一次注册以及 IMS用户进行 会话等所有涉及到向 HSS查询用户签约信息的流程, 和向 HSS查询为 用户服务的 S-CSCF的流程中, 均存在此问题。 发明内容
有鉴于此, 本发明的目的在于提供两种减轻 HSS接口负荷的方法, 以优化业务流程, 减轻 HSS接口负荷。
为达到上述目的, 本发明的技术方案是这样实现的:
一种減轻归属签约用户服务器接口负荷的方法, 该方法包括以下步 骤:
归属签约用户服务器 HSS 接收到来自服务呼叫状态功能实体 S-CSCF的包含请求保存本 S-CSCF名称信息和请求用户签约信息的请 求消息后, 首先保存该消息中 S-CSCF的名称信息, 然后再根据该消息 中的用户标识进行查询, 并直接给该 S-CSCF返回包含用户签约信息的 响应消息。
较佳地, 该方法进一步包括: HSS接收到来自查询呼叫状态功能实 体 I-CSCF 的查询 S-CSCF信息的.消息后, 向 I-CSCF 返回包含确定 S-CSCF所需信息的查询应答消息, 由 I-CSCF根据应答消息中返回的信 息确定能够为用户提供服务的 S-CSCF,并向该确定的 S-CSCF转发用户 的请求消息。
较佳地, 在某个公共用户标识信息第一次注册时,
如果该申请注册用户至少有一个公共用户标识曾在 HSS 中进行了 注册, 且处于有效期内, 而且 HSS确定不需要 I-CSCF 重新选择一个 S-CSCF为该用户服务,则所述确定 S-CSCF所需信息为: 当前为该用户 服务的 S-CSCF名称;
如果该用户至少有一个公共用户标识的注册状态是未注册或者注册 已经过期,但 HSS中还保存有该用户上次使用的 S-CSCF的名称,或者, 该用户曾作为没有注册的被叫由 HSS分配了一个 S-CSCF, 则所述确定 S-CSCF所需信息为: 曾为该用户服务过的 S-CSCF名称;
如果 HSS自身保存有为该 UE服务过的 S-CSCF的名称,且 HSS不 确定是否需要 I-CSCF重新选择一个 S-CSCF为该用户服务,则所述确定 S-CSCF所需信息为: 曾为该 UE服务过的 S-CSCF名称和能够支持该申 请注册用户最严格业务签约要求的 S-CSCF能力集信息;
如果 HSS自身没有已经分配的为该 UE服务过的 S-CSCF的名称, 则所述确定 S-CSCF所需信息为: 能够支持该申请注册用户最严格业务 签约要求的 S-CSCF能力集信息。
较佳地,如果 HSS返回的信息中只包含 S-CSCF名称,则所述 I-CSCF 确定能够为用户提供服务的 S-CSCF的方法为: I-CSCF确定该返回信息 中的 S-CSCF为能够为用户提供服务的 S-CSCF;
如果 HSS返回的信息中只包含能够支持该申请注册用户最严格业 务签约要求的 S-CSCF能力集信息,则所述 I-CSCF确定能够为用户提供 服务的 S-CSCF的方法为: I-CSCF根据应答消息中返回的 S-CSCF能力 集信息选择一个新的能够满足当前用户业务需要的 S-CSCF, 并确定该 新选择的 S-CSCF为能够为用户提供服务的 S-CSCF;
如果 HSS返回的信息中包含 S-CSCF名称和能够支持该申请注册用 户最严格业务签约要求的 S-CSCF能力集信息,则所述 I-CSCF确定能够 为用户提供服务的 S-CSCF的方法为: I-CSCF根据返回的 S-CSCF名称 判断该 S-CSCF能否满足当前用户的业务需要, 如果可以, 则确定该返 回的 S-CSCF为能够为用户提供服务的 S-CSCF,否则,根据应答消息中 的 S-CSCF 能力集信息选择一个新的能够满足当前用户业务需要的 S-CSCF,并确定该新选择的 S-CSCF为能够为用户提供服务的 S-CSCF。
较佳地, '所述 HSS接收到来自 I-CSCF的查询 S-CSCF信息的消息 后, 进一步包括: 根据用户的签约信息以及运营商的策略, 判断出允许 该用户 UE在当前的网络内发起注册请求后, 再执行后续步驟。
较佳地, 在某个公共用户标识信息进行第一次注册时,
所述 HSS 接收到来自 I-CSCF 的查询 S-CSCF 信息的消息由 Cx-Query消息承载, 所述 HSS给 I-CSCF返回的包含确定 S-CSCF所需 信息的查询应答消息由 Cx-Quer Resp消息承载, 或者,
所述 HSS 接收到来自 I-CSCF 的查询 S-CSCF 信息的消息由 Cx-Select-pull消息承载, 所述 HSS给 I-CSCF返回的包含确定 S-CSCF 所需信息的查询应答消息由 Cx-Select-pull Resp消息承载。
较佳地, 当某个用户在会话过程时,
如果 HSS自身保存有为该 UE服务过的 S-CSCF的名称, 则根据系 统的配置, HSS给 I-CSCF返回包含 S-CSCF名称的应答消息, 并由 I-CSCF向该 S-CSCF转发用户的请求会话消息; 或者, HSS给 I-CSCF 返回包含 S-CSCF 名称和能够支持该用户最严格业务签约要求的 S-CSCF 能力集信息, 由 I-CSCF 确定一个能够为用户提供服务的 S-CSCF, 并向该确定的 S-CSCF转发用户的请求会话消息;
如果 HSS自身没有为该 UE服务过的 S-CSCF的名称,则 HSS直接 给 I-CSCF返回包含能够支持该用户最严格业务签约要求的 S-CSCF能力 集信息的应答消息后, 由 I-CSCF 确定一个能够为用户提供服务的 S-CSCF, 并向该确定的 S-CSCF转发用户的请求会话消息。
较佳地, 当某个用户在会话过程时,
所述 HSS 接收到来自 I-CSCF 的查询 S-CSCF 信息的消息由 Cx-Location-Query 消息承载, 所述 HSS 给 I-CSCF 返回的包含确定 S-CSCF所需信息的查询应答消息由 Cx- Location-Query Resp消息承载, 或者,
所述 HSS 接收到来自 I-CSCF 的查询 S-CSCF 信息的消息由
Cx-Select-pull消息承载, 所述 HSS给 I-CSCF返回的包含确定 S-CSCF 所需信息的查询应答消息由 Cx-Select-pull Resp消息承载。
较佳地, 所述包含请求保存本 S-CSCF名称信息和请求用户签约信 息的请求消息由 Cx-Put消息承载, 所述 HSS给 S-CSCF返回的响应消 息由 Cx-Put Res 消息承载, 或者,
所述包含请求保存本 S-CSCF名称信息和请求用户签约信息的请求 消息由 Cx-Pull消息承载,所述 HSS给 S-CSCF返回的响应消息由 Cx-Pull Resp消息承载。
较佳地, 所述给 S-CSCF返回包含用户签约信息的响应消息中的用 户签约信息中至少包括该用户的描述信息。 一种減轻归属签约用户服务器接口负荷的方法, 该方法包括以下步 骤:
HSS接收到来自查询呼叫状态功能实体 I-CSCF的查询 S-CSCF信 息的消息后,向 I-CSCF返回包含确定 S-CSCF所需信息的查询应答消息, 由 I-CSCF 根据应答消息中返回的信息确定能够为用户提供服务的 S-CSCF, 并向该确定的 S-CSCF转发用户的请求消息。
较佳地, 在某个公共用户标识信息第一次注册时,
如果该申请注册用户至少有一个公共用户标识曾在 HSS 中进行了 注册, 且处于有效期内, 而且 HSS 确定不需要 I-CSCF 重新选择一个 S-CSCF为该用户服务,则所述确定 S-CSCF所需信息为: 当前为该用户 服务的 S-CSCF名称;
如果该用户至少有一个公共用户标识的注册状态是未注册或者注册 已经过期,但 HSS中还保存有该用户上次使用的 S-CSCF的名称,或者, 该用户曾作为没有注册的被叫由 HSS分配了一个 S-CSCF, 则所述确定 S-CSCF所需信息为: 曾为该用户服务过的 S-CSCF名称;
如果 HSS自身保存有为该 UE服务过的 S-CSCF的名称,且 HSS不 确定是否需要 I-CSCF重新选择一个 S-CSCF为该用户服务,则所述确定 S-CSCF所需信息为: 曾为该 UE服务过的 S-CSCF名称和能够支持该申 请注册用户最严格业务签约要求的 S-CSCF能力集信息;
如果 HSS 自身没有已经分配的为该 UE服务过的 S-CSCF的名称, 则所述确定 S-CSCF所需信息为: 能够支持该申请注册用户最严格业务 签约要求的 S-CSCF能力集信息。
较佳地,如果 HSS返回的信息中只包含 S-CSCF名称,则所述 I-CSCF 确定能够为用户提供服务的 S-CSCF的方法为: I-CSCF确定该返回信息 中的 S-CSCF为能够为用户提供服务的 S-CSCF; 如果 HSS 返回的信息中只包含能够支持该申请注册用户最严格业 务签约要求的 S-CSCF能力集信息,则所述 I-CSCF确定能够为用户提供 服务的 S-CSCF的方法为: I-CSCF根据应答消息中返回的 S-CSCF能力 集信息选择一个新的能够满足当前用户业务需要的 S-CSCF, 并确定该 新选择的 S-CSCF为能够为用户提供服务的 S-CSCF;
如果 HSS返回的信息中包含 S-CSCF名称和能够支持该申请注册用 户最严格业务签约要求的 S-CSCF能力集信息,则所述 I-CSCF确定能够 为用户提供服务的 S-CSCF的方法为: I-CSCF根据返回的 S-CSCF名称 判断该 S-CSCF能否满足当前用户的业务需要, 如果可以, 则确定该返 回的 S-CSCF为能够为用户提供服务的 S-CSCF,否贝' j , 居应答消息中 的 S-CSCF 能力集信息选择一个新的能够满足当前用户业务需要的 S-CSCF,并确定该新选择的 S-CSCF为能够为用户提供服务的 S-CSCF。
较佳地, 所述 HSS接收到来自 I-CSCF的查询 S-CSCF信息的消息 后, 进一步包括: 根据用户的签约信息以及运营商的策略, 判断出允许 该用户 UE在当前的网络内发起注册请求后, 再执行后续步驟。
较佳地, 在某个公共用户标识信息进行第一次注册时,
所述 HSS 接收到来自 I-CSCF 的查询 S-CSCF 信息的消息由 Cx-Query消息承载 , 所述 HSS给 I-CSCF返回的包含确定 S-CSCF所需 信息的查询应答消息由 Cx-Query Res 消息承载, 或者,
所述 HSS 接收到来自 I-CSCF 的查询 S-CSCF 信息的消息由 Cx-Select-pull消息承载, 所述 HSS给 I-CSCF返回的包含确定 S-CSCF 所需信息的查询应答消息由 Cx-Select-pull Resp消息承载。
较佳地, 当某个用户在会话过程时,
如果 HSS自身保存有为该 UE服务过的 S-CSCF的名称, 则根据系 统的配置, HSS 给 I-CSCF返回包含 S-CSCF 名称的应答消息, 并由 I-CSCF向该 S-CSCF转发用户的请求会话消息; 或者, HSS给 I-CSCF 返回包含 S-CSCF 名称和能够支持该用户最严格业务签约要求的 S-CSCF 能力集信息, 由 I-CSCF 确定一个能够为用户提供服务的 S-CSCF, 并向该确定的 S-CSCF转发用户的请求会话消息;
如果 HSS自身没有为该 UE服务过的 S-CSCF的名称,则 HSS直接 给 I-CSCF返回包含能够支持该用户最严格业务签约要求的 S-CSCF能力 集信息的应答消息后, 由 I-CSCF 确定一个能够为用户提供服务的 S-CSCF, 并向该确定的 S-CSCF转发用户的请求会话消息。
较佳地, 当某个用户在会话过程时,
所述 HSS 接收到来自 I-CSCF 的查询 S-CSCF 信息的消息由 Cx-Location-Query 消息承载, 所迷 HSS 给 I-CSCF 返回的包含确定 S-CSCF所需信息的查询应答消息由 Cx- Location-Query Resp消息承载, 或者,
所述 HSS 接收到来自 I-CSCF 的查询 S-CSCF 信息的消息由 Cx-Select-pull消息承载, 所述 HSS给 I-CSCF返回的包含确定 S-CSCF 所需信息的查询应答消息由 Cx-Select-pull Resp消息承载。
应用本发明,当 HSS接收到来自 S-CSCF的包含请求保存本 S-CSCF 名称信息和请求用户签约信息的请求消息时,首先保存该消息中 S-CSCF 的名称, 然后再将所查询的用户签约信息直接返回给申请查询的 S-CSCF, 从而精简了查询用户签约信息的步骤, 优化了业务流程, 减轻 了 HSS接口负荷。
另外, 在用户的某个公共用户标识进行注册的过程中或在用户的会 话过程中, 当 HSS接收到来自 I-CSCF的包含查询 S-CSCF名称或能力 集信息的请求消息后,直接向 I-CSCF返回包含 S-CSCF名称和或能够支 持该用户最严格业务签约要求的 S-CSCF能力集信息的应答消息, 然后 再继续执行后续步骤, 精筒了现有技术中的冗余步骤, 优化了用户的注 册流程以及会话流程, 减轻了 HSS接口的负荷。
本发明对现有网络结构和业务实现没有任何影响, 也不需要修改现 有的接口规范, 因而具有很好的兼容性和可扩展性。 附图简要说明
图 1所示为现有技术的基于 IMS构架的公共用户标识第一次发起注 册的流程图;
图 2所示为应用本发明的基于 IMS构架的公共用户标识第一次发起 注册的一实施例的流程图;
图 2A所示为应用本发明的基于 IMS构架的公共用户标识第一次发 起注册的另一实施例的流程图;
图 3所示为应用本发明的基于 IMS构架的公共用户标识非第一次发 起注册的流程图;
图 4所示为应用本发明的基于 IMS构架用户作为被叫的一实施例的 部分呼叫流程图;
图 4A所示为应用本发明的基于 IMS构架用户作为被叫的另一实施 例的部分呼叫流程图。 实施本发明的方式
为使本发明的技术方案更加清楚, 下面结合具体实施例及其附图对 本发明再做进一步地详细说明。
本发明的思路是: HSS 接收到来自 S-CSCF 的包含请求保存本 S-CSCF名称信息和请求用户签约信息的请求消息后, 首先保存该消息 中 S-CSCF的名称信息, 然后再根据该消息中的用户标识进行查询, 并 直接给该 S-CSCF返回包含用户签约信息的响应消息。 同时, 在 HSS接 收到来自 I-CSCF的包含查询 S-CSCF名称或能力集信息的请求消息后, 直接向 I-CSCF返回包含 S-CSCF名称和 /或能够支持该用户最严格业务 签约要求的 S-CSCF能力集信息的应答消息,由 I-CSCF根据应答消息中 返回的信息确定最终的 S-CSCF,并向该最终的 S-CSCF转发用户的请求 消息。
图 2所示为应用本发明的基于 IMS构架的公共用户标识第一次发起 注册的一实施例的流程图。在本实施例中,使用 SIP协议作为 IP多媒体 会话的信令控制协议, HSS和 I-CSCF以及 HSS和 S-CSCF之间的 Cx 接口使用 Diameter协议来传送相关信息的,且本实施例中不需要网絡拓 朴隐藏功能, UE处于访问网络中。
步骤 201, UE建立了底层承载的物理连接之后, 向其所属访问网络 中的 P-CSCF发送 Register消息, 该消息中包括: 公共用户标识, 私有 用户标识, 归属网络域名, 以及申请注册 UE的 IP地址等信息。
步骤 202, 接收到 Register消息的 P-CSCF, 对该消息中的归属网络 域名信息进行解析, 以获取归属网络接入点 I-CSCF的地址, 然后向归 属网络中的 I-CSCF转发 UE的 Register消息, 该转发的 Register消息中 包括: P-CSCF的名称或者地址,公共用户标识,私有用户标识, P-CSCF 所在访问网絡的标识, 以及申请注册 UE的 IP地址等信息。
步骤 203 , I-CSCF发送 Cx-Query消息给 HSS , 该消息中的用户授 权类型 ( User- Authorization-Type ) 为 REGISTRATION, 其表明是一次 注册请求消息, 该 Cx-Query 消息中包括: 公共用户标识, 私有用户标 识, 以及 P-CSCF所在网絡的标识等信息。
步骤 204, HSS接收到来自 I-CSCF的 Cx-Query消息后, 首先根据 用户的签约信息以及运营商的策略, 判断是否允许该 UE在当前的网络 内发起注册请求, 如果不允许, 则直接给 I-CSCF返回包含拒绝接受此 次注册信息的应答消息 Cx-Query Resp, 再由 I-CSCF通过 P-CSCF给用 户返回注册失败的消息, 结束本流程;
如果允许 UE在当前的网络内发起注册请求, 则 HSS根据自身是否 保存有为该 UE服务过的 S-CSCF的名称, 以及自身保存的该请求注册 用户的签约文件内容是否发生更新或者升级, 给 I-CSCF返回相应的信 如果申请注册的用户至少有一个公共用户标识曾在 HSS 中进行了 注册,即 HSS自身保存有为该 UE服务的 S-CSCF的名称,且该 S-CSCF 处于有效期内, 而且自身保存的该请求注册用户的签约文件内容没有发 生更新或者升级, 则 HSS 给 I-CSCF 返回包含当前为该用户服务的 S-CSCF名称的 Cx-Query Res 后, 执行步骤 207;
如果该用户至少有一个公共用户标识的注册状态是未注册或者注册 已经过期,但 HSS中还保存有该用户上次使用的 S-CSCF的名称,或者, 该用户曾作为没有注册的被叫由 HSS分配了一个 S-CSCF, 则 HSS给 I-CSCF返回包含该为用户服务过 S-CSCF名称的 Cx-Query Resp后, 执 行步骤 207;
如果 HSS自身保存有为该 UE服务过的 S-CSCF的名称,且 HSS认 为可能需要 I-CSCF重新选择一个 S-CSCF为该用户服务,比如自身保存 的该请求注册用户的签约文件内容发生了更新或者升級, 则 HSS 给 I-CSCF返回包含 S-CSCF名称和现有的 S-CSCF能力集信息的 Cx-Query Resp后, 由 I-CSCF进一步判断返回的 S-CSCF名称是否可用, 如果可 以使用,则执行步骤 207,否则,执行步骤 205, 1-CSCF重新选择 S-CSCF; 如果 HSS自身没有已经分配的为该 UE服务过的 S-CSCF的名称, 则 HSS只给 I-CSCF返回包含现有的 S-CSCF能力集信息的 Cx-Query Resp后, 执行步骤 205
步骤 205 , I-CSCF向 HSS发送 Cx-Select-Pull请求消息, 该消息中 的 用 户 授 权 类 型 ( User- Authorization-Type ) 为 REGISTRATION— AND— CAPABILITIES, 其目的是明确表明 I-CSCF要 求 HSS返回能够支持该申请注册用户最严格业务签约要求的 S-CSCF能 力集信息, 作为选择 S-CSCF时的输入信息, 该 Cx-Select-Pull请求消息 中包括: 公共用户标识, 私有用户标识等信息。
步骤 206, HSS接收到来自 I-CSCF的 Cx-Select-Pull请求消息后, 给 I-CSCF返回 Cx-Select-Pull Resp消息, 该 Cx-Select-Pull Resp消息中 包括: 能够支持该申请注册用户最严格业务签约要求的 S-CSCF能力集 信息。
步驟 207, I-CSCF根据 HSS返回的 S-CSCF的名称进行域名解析, 或者, 从能够支持该申请注册用户最严格业务签约要求的 S-CSCF能力 集信息选择一个能够为用户提供服务 S-CSCF,然后再对该 S-CSCF的名 称进行域名解析, 得到 S-CSCF的地址, 向该 S-CSCF发送 Register消 息, 该 Register消息中包括 P-CSCF域名或者地址, 公共用户标识, 私 有用户标识, P-CSCF所在网络的标识, 申请注册 UE的 IP地址等信息; 如果 I-CSCF无法根据能够支持该申请注册用户最严格业务签约要 求的能力集信息得到一个新的 S-CSCF, 则 I-CSCF通过 P-CSCF给用户 返回注册失败的消息, 并结束本流程。
步驟 208, S-CSCF给 HSS发送包含请求保存本 S-CSCF名称信息和 请求用户签约信息的请求消息, 该消息中包括: 公共用户标识和 /或私有 用户标识, S-CSCF名称等信息; 且该消息可由 Cx-Put消息或 Cx-Pull 消息承载;
步骤 209, HSS接收到来自 S-CSCF的请求保存本 S-CSCF名称信息 和请求用户签约信息的消息后, 首先保存该消息中的 S-CSCF名称, 然 后, 根据公共用户标识和 /或私有用户标识在本地进行查询, 并直接给 S-CSCF返回包含用户签约信息的响应消息, 该响应消息中的用户签约 信息包括用户描述信息, 以及安全信息等, 其中的用户描述信息用于用 户接入到各种业务控制平台; 该响应消息由 Cx-Put Resp消息或 Cx-Pull Resp消息7 载。
步骤 210, S-CSCF根据从用户描述信息中得到的过滤规则, 将注册 信息发送到相关的业务控制平台执行适当的业务控制流程。
步骤 211 , S-CSCF通过 I-CSCF以及 P-CSCF, 给 UE返回 200ΟΚ 消息。
至此, 该用户的一个公共用户标识完成第一次注册。 在上述注册流 程中, 精筒了 S-CSCF向 HSS查询用户描述信息的步骤, 减轻了 HSS 接口的负荷。
同时, 在上述流程中可进一步精筒步骤 205和步骤 206, 使 I-CSCF 一次即可得到所需的信息。精简步骤 205和步驟 206后的流程参见图 2Α, 由于图 2Α与图 2的区别仅在于少了步骤 205和步骤 206, 因此, 图 2 中的步骤 201〜203与图 2Α中的步骤 201a~203a完全相同, 在此不再重 复叙述, 步骤 204a执行如下操作:
HSS接收到来自 I-CSCF的 Cx-Query消息后, 首先根据用户的签约 信息以及运营商的策略, 判断是否允许该 UE在当前的网络内发起注册 请求, 如果不允许, 则直接给 I-CSCF返回包含拒绝接受此次注册信息 的应答消息 Cx-Query Resp, 再由 I-CSCF通过 P-CSCF给用户返回注册 失败的消息, 结束本流程;
如果允许 UE在当前的网絡内发起注册请求, 则 HSS根据自身是否 保存有为该 UE服务过的 S-CSCF的名称, 以及自身保存的该请求注册 用户的签约文件内容是否发生更新或者升级, 给 I-CSCF返回相应的信 如果申请注册的用户至少有一个公共用户标识曾在 HSS 中进行了 注册,即 HSS自身保存有为该 UE服务的 S-CSCF的名称,且该 S-CSCF 处于有效期内, 而且 HSS确定不需要 I-CSCF重新选择一个 S-CSCF为 该用户服务, 比如自身保存的该请求注册用户的签约文件内容没有发生 更新或者升级,则 HSS给 I-CSCF返回包含当前为该用户服务的 S-CSCF 名称的 Cx-Query Resp后, 执行步驟 205a;
如果该用户至少有一个公共用户标识的注册状态是未注册或者注册 已经过期,但 HSS中还保存有该用户上次使用的 S-CSCF的名称,或者, 该用户曾作为没有注册的被叫由 HSS分配了一个 S-CSCF, 则 HSS给 I-CSCF返回包含该为用户服务过 S-CSCF名称的 Cx-Query Resp后, 执 行步骤 205a;
如果 HSS自身保存有为该 UE服务过的 S-CSCF的名称,且 HSS不 确定是否需要 I-CSCF重新选择一个 S-CSCF为该用户服务, 比如 HSS 自身保存的该请求注册用户的签约文件内容发生了更新或者升级, 则 HSS直接给 I-CSCF返回包含 S-CSCF名称和能够支持该申请注册用户 最严格业务签约要求的 S-CSCF 能力集信息的应答消息后, 执行步骤 205a;
如果 HSS自身没有已经分配的为该 U¾服务过的 S-CSCF的名称, 则 HSS给 I-CSCF返回包含能够支持该申请注册用户最严格业务签约要 求的 S-CSCF能力集信息的应答消息后, 执行步骤 205a。
上述实施例中 HSS接收到来自 I-CSCF的查询请求消息由 Cx-Query 消息承载, HSS给 I-CSCF返回的应答消息由 Cx-Query Resp消息承载, 在实际应用时, 上述 HSS接收到来自 I-CSCF的查询请求消息也可以由 Cx-Select-pull 消息承载, HSS 给 I-CSCF 返回^ |应答消息也可以由 Cx-Select-pull Resp消息承载。
相应地, 图 2A中的步骤 205a也就相当于图 2中的步骤 207, 步骤 205a执行的操作如下:
I-CSCF根据 HSS返回的信息,确定能够为用户提供服务的 S-CSCF, 并根据该 S-CSCF的名称进行域名解析得到 S-CSCF的地址。 具体处理 过程为: 如果 HSS返回只包含 S-CSCF名称的应答消息, 则 I-CSCF确 定该 S-CSCF为能够为用户提供服务的 S-CSCF; 如果 HSS返回只包含 能够支持该申请注册用户最严格业务签约要求的 S-CSCF能力集信息的 应答消息,则 I-CSCF根据该 S-CSCF能力集信息选择一个新的能够满足 当前用户业务需要的 S-CSCF,并确定该新选择的 S-CSCF为能够为用户 提供服务的 S-CSCF; 如果 HSS返回包含为该 UE服务过的 S-CSCF名 称和能够支持该申请注册用户最严格业务签约要求的 S-CSCF能力集信 息的应答消息,则 I-CSCF根据返回的 S-CSCF名称判断该 S-CSCF能否 满足当前用户的业务需要, 如果可以, 则确定该返回的 S-CSCF为能够 为用户提供服务的 S-CSCF,否则,根据应答消息中的 S-CSCF能力集信 息选择一个新的能够满足当前用户业务需要的 S-CSCF, 并确定该新选 择的 S-CSCF为能够为用户提供服务的 S-CSCF。
步骤 206a〜步驟 209a与图 2中的步骤 208〜步骤 211完全相同,在此 不再重复叙述。
图 3所示为应用本发明的基于 IMS构架的公共用户标识非第一次发 起注册的流程图。在本实施例中,使用 SIP协议作为 IP多媒体会话的信 令控制协议, HSS和 I-CSCF以及 HSS和 S-CSCF之间的 Cx接口使用 Diameter协议来传送相关信息的, I-CSCF解析出的 S-CSCF内没有相关 用户的描述信息, 且本实施例中不需要网络拓朴隐藏功能, UE 处于访 问网絡中。
步驟 301 , UE向其所属访问网络中的 P-CSCF发送 Register消息, 该消息中包括: 公共用户标识, 私有用户标识, 归属网络域名, 以及申 请注册 UE的 IP地址等信息。
步骤 302, 接收到 Register消息的 P-CSCF, 对该消息中的归属网絡 域名信息进行解析, 以获取归属网络接入点 I-CSCF的地址, 然后向归 属网络中的 I-CSCF转发 UE的 Register消息, 该转发的 Register消息中 包括: P-CSCF的名称或者地址,公共用户标识,私有用户标识, P-CSCF 所在访问网络的标识, 以及申请注册 UE的 IP地址等信息。
步骤 303 , I-CSCF发送 Cx-Query消息给 HSS, 该 Cx-Query消息中 包括: 公共用户标识, 私有用户标识, 以及 P-CSCF所在网络的标识等 信息。
步骤 304 , HSS接收到来自 I-CSCF的 Cx-Query消息, 判断出该用 户已经注册后, 直接给 I-CSCF返回包含指示说明已经为该用户分配了 S-CSCF信息的应答消息 Cx-Query Resp , 该 Cx-Query Resp中包括一个 已经为该用户^ _务的 S-CSCF的名称。
步骤 305 , I-CSCF根据 HSS返回的 S-CSCF的名称进行域名解析, 得到 S-CSCF的地址, 向该 S-CSCF发送 Register消息, 该 Register消息 中包括 P-CSCF域名或者地址, 公共用户标识, 私有用户标识, P-CSCF 所在网络的标识, 申请注册 UE的 IP地址等信息。
步骤 306, S-CSCF给 HSS发送包含请求保存本 S-CSCF名称信息和 请求用户签约信息的请求消息, 该消息中包括: 公共用户标识和 /或私有 用户标识, S-CSCF名称等信息; 且该消息可由 Cx-Put消息或 Cx-Pull 消息承载;
步骤 307, HSS接收到来自 S-CSCF的请求保存本 S-CSCF名称信息 和请求用户签约信息的消息后, 首先保存该消息中的 S-CSCF名称, 然 后, 根据公共用户标识和 /或私有用户标识在本地进行查询, 并直接给 S-CSCF返回包含用户签约信息的响应消息, 该响应消息中的用户签约 信息包括用户描述信息, 以及安全信息等, 其中的用户描述信息用于用 户接入到各种业务控制平台; 该响应消息由 Cx-Put Resp消息或 Cx-Pull Res 消息承载。
步驟 308, S-CSCF根据从用户描述信息中得到的过滤规则, 将注册 信息发送到相关的业务控制平台执行适当的业务控制流程。
步骤 309, S-CSCF通过 I-CSCF以及 P-CSCF, 给 UE返回 200OK 消息。
至此, 该用户的一个公共用户标识实现了重新注册, 且精简了 S-CSCF向 HSS查询用户描述信息的步骤, 减轻了 HSS接口的负荷。
图 4所示为应用本发明的基于 IMS构架用户作为被叫的一实施例的 部分呼叫流程图。在本实施例中,使用 SIP协议作为 IP多媒体会话的信 令控制协议, HSS和 I-CSCF以及 HSS和 S-CSCF之间的 Cx接口使用 Diameter协议来传送相关信息的, I-CSCF解析出的 S-CSCF内没有相关 用户的描述信息, 且该用户所使用的公共用户标识没有注册过。
步骤 401 , I-CSCF接收到经转发的来自主叫用户的邀请 ( INVITE ) 消息, 该消息中包括公共用户标识信息。
步骤 402, 1-CSCF向 HSS发送查询用户当前位置信息的位置查询消 息 ( Cx-Location-Query ) 消息。
步骤 403,根据系统预先配置, HSS给 I-CSCF返回包含指示该公共 用户标识未注册信息的响应消息 Cx-Location-Query Resp后, 执行步骤 404, 或者, HSS给 I-CSCF返回包含以前为该用户分配的 S-CSCF名称 信息和现有 S-CSCF能力集信息后,执行步骤 404,或者, HSS给 I-CSCF 返回包含以前为该用户分配的 S-CSCF 名称信息的响应消息 Cx-Location-Query Resp , 并执行步骤 407。
步骤 404, I-CSCF给 HSS发送 Cx-Select-Pull请求消息, 以请求获 取能够支持最严格要求的 S-CSCF能力集信息, 该请求消息中携带的参 数主要包括: 公共用户标识等。
步骤 405, HSS接收到 Cx-Select-Pull请求消息之后, 给 I-CSCF返 回 Cx-Select-Pull Resp消息,该消息中包括 I-CSCF所需的能够支持该用 户最严格业务签约要求的 S-CSCF能力集信息。
步骤 406, I-CSCF从 HSS返回的 S-CSCF能力集信息中选择出能够 为该用户提供服务的 S-CSCF,并根据该 S-CSCF的名称解析出该 S-SCSF 地址后, 执行步驟 407;
如果 I-CSCF不能从 HSS返回的 S-CSCF能力集信息中解析出所需 的 S-CSCF地址,则 I-CSCF自己指定一个 S-CSCF为该未注册的公共用 户标识进行服务, 然后执行步骤 407。 '
步骤 407 , 1-CSCF将接收到的 INVITE消息转发给已确定的 S-CSCF。 步骤 408, 接收到 INVITE消息的 S-CSCF给 HSS发送包含请求保 存本 S-CSCF名称信息和请求用户签约信息的请求消息 , 该消息包括: 公共用户标识和 /或私有用户标识, S-CSCF名称等信息; 且该消息可由 Cx-Put消息或 Cx-Pull消息承载。
步骤 409, HSS接收到来自 S-CSCF的请求保存本 S-CSCF名称信息 和请求用户签约信息的消息后, 首先保存该消息中的 S-CSCF名称, 然 后, 居公共用户标识和 /或私有用户标识在本地进行查询, 并直接给 S-CSCF返回包含用户签约信息的响应消息, 即该响应消息中的用户签 约信息包括用户描述信息, 以及安全信息等, 其中的用户描述信息用于 用户接入到各种业务控制平台; 该响应消息由 Cx-Put Resp 消息或 Cx-Pull Res 消息承载。
步驟 410, S-CSCF根据从用户描述信息中得到的过滤规则, 将注册 信息发送到相关的业务控制平台执行适当的业务控制流程。
步骤 411 , S-CSCF继续执行后续操作。
上述呼叫流程精简了 S-CSCF向 HSS查询用户描述信息的步骤, 减 轻了 HSS接口的负荷。
同时, 在上述流程中可进一步精简步骤 404和 405 , 使 I-CSCF—次 即可得到所需的信息。 精简步骤 404和 405后的流程参见图 4A, 由于 图 4A与图 4的区别仅在于少了步驟 404〜4064, 因此, 图 4 中的步驟 401〜402与图 4A中的步骤 401a〜402a完全相同,在此不再重复叙述, 步 骤 403a执行如下操作:
HSS接收到来自 I-CSCF的包含查询用户当前位置信息的消息后, 判断自身是否保存有为该 UE服务过的 S-CSCF的名称, 如果 HSS自身 保存有为该 UE服务过的 S-CSCF 的名称, 则根据系统配置, HSS 给 I-CSCF返回包含 S-CSCF名称的应答消息, 或者, HSS给 I-CSCF返回 包含 S-CSCF名称和能够支持该用户最严格业务签约要求的 S-CSCF能 力集信息后, 执行步骤 404a;
如果 HSS自身没有为该 UE服务过的 S-CSCF的名称,则 HSS直接 给 I-CSCF返回包含能够支持该用户最严格业务签约要求的 S-CSCF能力 集信息的应答消息后, 执行步骤 404a。
相应地, 图 4A中的步骤 404a也就相当于图 4中的步骤 406, 步骤 404a执行的操作如下:
I-CSCF根据 HSS返回的信息,确定能够为用户提供服务的 S-CSCF, 并根据该 S-CSCF的名称进行域名解析得到 S-CSCF的地址。 具体处理 过程为: 如果 HSS返回只包含 S-CSCF名称的应答消息, 则 I-CSCF确 定该 S-CSCF为能够为用户提供服务的 S-CSCF; 如果 HSS返回只包含 能够支持该申请注册用户最严格业务签约要求的 S-CSCF能力集信息的 应答消息,则 I-CSCF根据该 S-CSCF能力集信息选择一个新的能够满足 当前用户业务需要的 S-CSCF,并确定该新选择的 S-CSCF为能够为用户 提供服务的 S-CSCF; 如果 HSS返回包含为该 UE服务过的 S-CSCF名 称和能够支持该申请注册用户最严格业务签约要求的 S-CSCF能力集信 息的应答消息,则 I-CSCF根据返回的 S-CSCF名称判断该 S-CSCF能否 满足当前用户的业务需要, 如果可以, 则确定该返回的 S-CSCF为能够 为用户提供服务的 S-CSCF, 否则,根据应答消息中的 S-CSCF能力集信 息选择一个新的能够满足当前用户业务需要的 S-CSCF, 并确定该新选 择的 S-CSCF为能够为用户提供服务的 S-CSCF。
如果 I-CSCF不能从 HSS返回的能够支持该申请注册用户最严格业 务签约要求的 S-CSCF 能力集信息中解析出所需的 S-CSCF 地址, 则 I-CSCF自己指定一个 S-CSCF为该未注册的公共用户标识进行服务。
上迷 HSS接收到来自 I-CSCF的查询消息由 Cx-Location-Queiy消息 承载, HSS给 I-CSCF返回的应答消息由 Cx-Location-Quer Resp消息承 载, 或者, 上述 HSS接收到来自 I-CSCF的查询消息由 Cx-Select-puU 消息承载, HSS给 I-CSCF返回的应答消息由 Cx-Select-pull Resp消息承 载。
步骤 405a〜步骤 409a与图 4中的步驟 407〜步骤 411完全相同,在此 不再重复叙述。
以上所述仅为本发明的较佳实施例而已, 并不用以限制本发明, 凡 在本发明的精神和原则之内, 所作的任何修改、 等同替换、 改进等, 均 应包含在本发明的保护范围之内。

Claims

权利要求书
1、 一种减轻归属签约用户服务器接口负荷的方法, 其特征在于, 该方法包括以下步骤:
归属签约用户服务器 HSS 接收到来自服务呼叫状态功能实体 S-CSCF的包含请求保存本 S-CSCF名称信息和请求用户签约信息的请 求消息后, 首先保存该消息中 S-CSCF的名称信息, 然后再根据该消息 中的用户标识进行查询, 并直接给该 S-CSCF返回包含用户签约信息的 响应消息。 -
2、 根据权利要求 1所述的方法, 其特征在于, 该方法进一步包括: HSS接收到来自查询呼叫状态功能实体 I-CSCF的查询 S-CSCF信息的 消息后,向 I-CSCF返回包含确定 S-CSCF所需信息的查询应答消息, 由 I-CSCF 根据应答消息中返回的信息确定能够为用户提供服务的 S-CSCF, 并向该确定的 S-CSCF转发用户的请求消息。
3、 根据权利要求 2所述的方法, 其特征在于, 在某个公共用户标 识信息第一次注册时,
如果该申请注册用户至少有一个公共用户标识曽在 HSS 中进行了 注册, 且处于有效期内, 而且 HSS 确定不需要 I-CSCF 重新选择一个 S-CSCF为该用户服务,则所述确定 S-CSCF所需信息为: 当前为该用户 服务的 S-CSCF名称;
如果该用户至少有一个公共用户标识的注册状态是未注册或者注册 已经过期,但 HSS中还保存有该用户上次使用的 S-CSCF的名称,或者, 该用户曾作为没有注册的被叫由 HSS分配了一个 S-CSCF, 则所述确定 S-CSCF所需信息为: 曾为该用户^ ^务过的 S-CSCF名称;
如果 HSS自身保存有为该 UE服务过的 S-CSCF的名称,且 HSS不 确定是否需要 I-CSCF重新选择一个 S-CSCF为该用户服务,则所述确定 S-CSCF所需信息为: 曾为该 UE服务过的 S-CSCF名称和能够支持该申 请注册用户最严格业务签约要求的 S-CSCF能力集信息;
如果 HSS自身没有已经分配的为该 UE服务过的 S-CSCF的名称, 则所述确定 S-CSCF所需信息为: 能够支持该申请注册用户最严格业务 签约要求的 S-CSCF能力集信息。
4、 根据权利要求 3所述的方法, 其特征在于,
如果 HSS返回的信息中只包含 S-CSCF名称, 则所述 I-CSCF确定 能够为用户提供服务的 S-CSCF的方法为: I-CSCF确定该返回信息中的 S-CSCF为能够为用户提供服务的 S-CSCF;
如果 HSS 返回的信息中只包含能够支持该申请注册用户最严格业 务签约要求的 S-CSCF能力集信息,则所述 I-CSCF确定能够为用户提供 服务的 S-CSCF的方法为: I-CSCF根据应答消息中返回的 S-CSCF能力 集信息选择一个新的能够满足当前用户业务需要的 S-CSCF, 并确定该 新选择的 S-CSCF为能够为用户提供服务的 S-CSCF;
如果 HSS返回的信息中包含 S-CSCF名称和能够支持该申请注册用 户最严格业务签约要求的 S-CSCF能力集信息,则所述 I-CSCF确定能够 为用户提供服务的 S-CSCF的方法为: I-CSCF根据返回的 S-CSCF名称 判断该 S-CSCF能否满足当前用户的业务需要, 如果可以, 则确定该返 回的 S-CSCF为能够为用户提供服务的 S-CSCF,否则,才 据应答消息中 的 S-CSCF 能力集信息选择一个新的能够满足当前用户业务需要的 S-CSCF,并确定该新选择的 S-CSCF为能够为用户提供服务的 S-CSCF。
5、 根据权利要求 2所述的方法, 其特征在于, 所述 HSS接收到来 自 I-CSCF的查询 S-CSCF信息的消息后,进一步包括:才艮据用户的签约 信息以及运营商的策略, 判断出允许该用户 UE在当前的网络内发起注 册请求后, 再执行后续步骤。
6、 根据权利要求 2 所述的方法, 其特征在于, 在某个公共用户标 识信息进行第一次注册时,
所述 HSS 接收到来自 I-CSCF 的查询 S-CSCF 信息的消息由 Cx-Query消息承载, 所述 HSS给 I-CSCF返回的包含确定 S-CSCF所需 信息的查询应答消息由 Cx-Query Resp消息承载, 或者,
所述 HSS 接收到来自 I-CSCF 的查询 S-CSCF 信息的消息由 Cx-Select-pull消息承载, 所述 HSS给 I-CSCF返回的包含确定 S-CSCF 所需信息的查询应答消息由 Cx-Select-pull Resp消息 载。
7、 根据权利要求 2所述的方法, 其特征在于, 当某个用户在会话 过程时,
如果 HSS自身保存有为该 UE服务过的 S-CSCF的名称, 则根据系 统的配置, HSS 给 I-CSCF返回包含 S-CSCF名称的应答消息, 并由 I-CSCF向该 S-CSCF转发用户的请求会话消息; 或者, HSS给 I-CSCF 返回包含 S-CSCF 名称和能够支持该用户最严格业务签约要求的 S-CSCF 能力集信息, 由 I-CSCF 确定一个能够为用户提供服务的 S-CSCF, 并向该确定的 S-CSCF转发用户的请求会话消息;
如果 HSS自身没有为该 UE服务过的 S-CSCF的名称,则 HSS直接 给 I-CSCF返回包含能够支持该用户最严格业务签约要求的 S-CSCF能力 集信息的应答消息后, 由 I-CSCF 确定一个能够为用户提供服务的 S-CSCF, 并向该确定的 S-CSCF转发用户的请求会话消息。
8、 根据权利要求 2 所述的方法, 其特征在于, 当某个用户在会话 过程时,
所述 HSS 接收到来自 I-CSCF 的查询 S-CSCF 信息的消息由 Cx-Location-Query 消息承载, 所述 HSS 给 I-CSCF 返回的包含确定 S-CSCF所需信息的查询应答消息由 Cx- Location-Query Resp消息承载, 或者,
所述 HSS 接收到来自 I-CSCF 的查询 S-CSCF 信息的消息由 Cx-Select-pull消息承载, 所述 HSS给 I-CSCF返回的包含确定 S-CSCF 所需信息的查询应答消息由 Cx-Select-pull Resp消息承载。
9、 根据权利要求 1所述的方法, 其特征在于,
所述包含请求保存本 S-CSCF名称信息和请求用户签约信息的请求 消息由 Cx-Put消息承载 ,所述 HSS给 S-CSCF返回的响应消息由 Cx-Put Resp消息承载, 或者,
所述包含请求保存本 S-CSCF名称信息和请求用户签约信息的请求 消息由 Cx-Pull消息承载,所述 HSS给 S-CSCF返回的响应消息由 Cx-Pull Resp消息承载。
10、 根据权利要求 1所述的方法, 其特征在于, 所述给 S-CSCF返 回包含用户签约信息的响应消息中的用户签约信息中至少包括该用户 的描述信息。
11、 一种减轻归属签约用户服务器接口负荷的方法, 其特征在于, 该方法包括以下步骤:
HSS接收到来自查询呼叫状态功能实体 I-CSCF的查询 S-CSCF信 息的消息后,向 I-CSCF返回包含确定 S-CSCF所需信息的查询应答消息, 由 I-CSCF 根据应答消息中返回的信息确定能够为用户提供服务的 S-CSCF, 并向该确定的 S-CSCF转发用户的请求消息。
12、 根据权利要求 11 所述的方法, 其特征在于, 在某个公共用户 标识信息第一次注册时,
如果该申请注册用户至少有一个公共用户标识曾在 HSS 中进行了 注册, 且处于有效期内, 而且 HSS 确定不需要 I-CSCF 重新选择一个 S-CSCF为该用户服务,则所述确定 S-CSCF所需信息为: 当前为该用户 服务的 S-CSCF名称;
如果该用户至少有一个公共用户标识的注册状态是未注册或者注册 已经过期,但 HSS中还保存有该用户上次使用的 S-CSCF的名称,或者, 该用户曾作为没有注册的被叫由 HSS分配了一个 S-CSCF, 则所述确定 S-CSCF所需信息为: 曾为该用户服务过的 S-CSCF名称;
如果 HSS自身保存有为该 UE服务过的 S-CSCF的名称,且 HSS不 确定是否需要 I-CSCF重新选择一个 S-CSCF为该用户服务,则所述确定 S-CSCF所需信息为: 曾为该 UE服务过的 S-CSCF名称和能够支持该申 请注册用户最严格业务签约要求的 S-CSCF能力集信息;
如果 HSS自身没有已经分配的为该 UE服务过的 S-CSCF的名称, 则所述确定 S-CSCF所需信息为: 能够支持该申请注册用户最严格业务 签约要求的 S-CSCF能力集信息。
13、 根据权利要求 12所述的方法, 其特征在于,
如果 HSS返回的信息中只包含 S-CSCF名称, 则所述 I-CSCF确定 能够为用户提供服务的 S-CSCF的方法为: I-CSCF确定该返回信息中的 S-CSCF为能够为用户提供服务的 S-CSCF;
如果 HSS 返回的信息中只包含能够支持该申请注册用户最严格业 务签约要求的 S-CSCF能力集信息,则所述 I-CSCF确定能够为用户提供 服务的 S-CSCF的方法为: I-CSCF根据应答消息中返回的 S-CSCF能力 集信息选择一个新的能够满足当前用户业务需要的 S-CSCF, 并确定该 新选择的 S-CSCF为能够为用户提供服务的 S-CSCF;
如果 HSS返回的信息中包含 S-CSCF名称和能够支持该申请注册用 户最严格业务签约要求的 S-CSCF能力集信息,则所述 I-CSCF确定能够 为用户提供服务的 S-CSCF的方法为: I-CSCF根据返回的 S-CSCF名称 判断该 S-CSCF能否满足当前用户的业务需要, 如果可以, 则确定该返 回的 S-CSCF为能够为用户提供服务的 S-CSCF,否则,根据应答消息中 的 S-CSCF 能力集信息选择一个新的能够满足当前用户业务需要的 S-CSCF,并确定该新选择的 S-CSCF为能够为用户提供服务的 S-CSCF。
14、 根据权利要求 11所述的方法, 其特征在于, 所述 HSS接收到 来自 I-CSCF的查询 S-CSCF信息的消息后,进一步包括:根据用户的签 约信息以及运营商的策略, 判断出允许该用户 UE在当前的网络内发起 注册请求后, 再执行后续步驟。
15、 根据权利要求 11 所述的方法, 其特征在于, 在某个公共用户 标识信息进行笫.一次注册时,
所述 HSS 接收到来自 I-CSCF 的查询 S-CSCF 信息的消息由 Cx-Query消息承载, 所述 HSS给 I-CSCF返回的包含确定 S-CSCF所需 信息的查询应答消息由 Cx-Query Resp消息承载, 或者,
所述 HSS 接收到来自 I-CSCF 的查询 S-CSCF 信息的消息由 Cx-Select-pull消息 载, 所述 HSS给 I-CSCF返回的包含确定 S-CSCF 所需信息的查询应答消息由 Cx-Select-pull Resp消息承载。
16、 根据权利要求 11 所述的方法, 其特征在于, 当某个用户在会 话过程时,
如果 HSS自身保存有为该 UE服务过的 S-CSCF的名称, 则根据系 统的配置, HSS 给 I-CSCF返回包含 S-CSCF名称的应答消息, 并由 I-CSCF向该 S-CSCF转发用户的请求会话消息; 或者, HSS给 I-CSCF 返回包含 S-CSCF 名称和能够支持该用户最严格业务签约要求的 S-CSCF 能力集信息, 由 I-CSCF 确定一个能够为用户提供服务的 S-CSCF, 并向该确定的 S-CSCF转发用户的请求会话消息;
如果 HSS自身没有为该 UE服务过的 S-CSCF的名称,则 HSS直接 给 I-CSCF返回包含能够支持该用户最严格业务签约要求的 S-CSCF能力 集信息的应答消息后, 由 I-CSCF 确定一个能够为用户提供服务的 S-CSCF, 并向该确定的 S-CSCF转发用户的请求会话消息。
17、 根据权利要求 11 所述的方法, 其特征在于, 当某个用户在会 话过程时,
所述 HSS 接收到来自 I-CSCF 的查询 S-CSCF 信息的消息由 Cx-Location-Query 消息承载, 所述 HSS 给 I-CSCF 返回的包含确定 S-CSCF所需信息的查询应答消息由 Cx- Location-Query Resp消息 载, 或者,
所述 HSS 接收到来自 I-CSCF 的查询 S-CSCF 信息的消息由
Cx-Select-pull消息承载, 所述 HSS给 I-CSCF返回的包含确定 S-CSCF 所需信息的查询应答消息由 Cx-Select-pull Resp消息承载。
PCT/CN2005/000021 2004-01-07 2005-01-06 Procede servant a limiter la charge d'interface d'un serveur d'abonnes local WO2005069645A1 (fr)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2006548075A JP4493104B2 (ja) 2004-01-07 2005-01-06 ホーム加入者サーバのインターフェイス負荷を軽減する方法
CA2552531A CA2552531C (en) 2004-01-07 2005-01-06 A method for reducing interface load of home subscriber server
EP05700396A EP1703746B1 (en) 2004-01-07 2005-01-06 A method for reducing interface load of home subscriber server
US10/585,288 US20070189215A1 (en) 2004-01-07 2005-01-06 Method for reducing interface load of home subscriber server

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CNB2004100023103A CN1299533C (zh) 2004-01-07 2004-01-07 一种用户到归属签约用户服务器进行注册的方法
CN200410002310.3 2004-01-07
CN200410004207.2 2004-02-10
CNB2004100042072A CN100362838C (zh) 2004-02-10 2004-02-10 一种减轻归属签约用户服务器接口负荷的方法

Publications (1)

Publication Number Publication Date
WO2005069645A1 true WO2005069645A1 (fr) 2005-07-28

Family

ID=34796375

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2005/000021 WO2005069645A1 (fr) 2004-01-07 2005-01-06 Procede servant a limiter la charge d'interface d'un serveur d'abonnes local

Country Status (6)

Country Link
US (1) US20070189215A1 (zh)
EP (1) EP1703746B1 (zh)
JP (1) JP4493104B2 (zh)
KR (1) KR100741152B1 (zh)
CA (1) CA2552531C (zh)
WO (1) WO2005069645A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2010506467A (ja) * 2006-10-03 2010-02-25 テレフオンアクチーボラゲット エル エム エリクソン(パブル) 通信ネットワークにおけるアクセス情報の提供
JP2010531017A (ja) * 2007-06-22 2010-09-16 テレフオンアクチーボラゲット エル エム エリクソン(パブル) ユーザ・データベース・サーバ、サービス・ポリシー・サーバ、及びアプリケーション・サーバを含むipマルチメディア・サブシステム通信ネットワークにおいてユーザ装置を通じてサービスを提供する方法
US10303066B2 (en) 2003-07-28 2019-05-28 Asml Netherlands B.V. Lithographic projection apparatus and device manufacturing method

Families Citing this family (30)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006066149A2 (en) 2004-12-17 2006-06-22 Tekelec Methods, systems, and computer program products for clustering and communicating between internet protocol multimedia subsystem (ims) entities
CN1327681C (zh) 2005-08-08 2007-07-18 华为技术有限公司 一种实现初始因特网协议多媒体子系统注册的方法
EP1921796B1 (en) * 2005-08-31 2009-12-16 Huawei Technologies Co., Ltd. Method of session processing in an ims and interrogating-call state control function
KR20090009925A (ko) * 2006-04-28 2009-01-23 노키아 코포레이션 어플리케이션 서버 발신 요청들에 대한 s-cscf 선택
US8149725B2 (en) * 2006-07-31 2012-04-03 Tekelec Methods, systems, and computer program products for a hierarchical, redundant OAM&P architecture for use in an IP multimedia subsystem (IMS) network
CN101119410B (zh) * 2006-08-01 2012-02-15 华为技术有限公司 一种实现计费提醒补充业务的方法及系统
US8046019B2 (en) * 2006-08-04 2011-10-25 Futurewei Technologies, Inc. Method and system for optimal allocation of uplink transmission power in communication networks
FR2906951B1 (fr) * 2006-10-04 2008-12-12 Alcatel Sa Dispositif et methode de controle et de securite d'un sous-systeme multimedia.
US8467290B2 (en) * 2006-12-26 2013-06-18 Ciena Corporation Methods and systems for distributed authentication and caching for internet protocol multimedia subsystem and other session initiation protocol systems
US8325654B2 (en) 2006-12-28 2012-12-04 Futurewei Technologies, Inc. Integrated scheduling and power control for the uplink of an OFDMA network
JP4909773B2 (ja) * 2007-03-16 2012-04-04 日本電気株式会社 ホーム加入者サーバ構成方法、構成システム、プログラム及び記憶媒体
GB0711592D0 (en) * 2007-06-15 2007-07-25 Ericsson Telefon Ab L M Access domain selection in a communications network
US8214512B2 (en) * 2007-07-11 2012-07-03 Telefonaktiebolaget Lm Ericsson (Publ) Control entity and method for setting up a session in a communications network, subscriber database and communications network
CN101383725B (zh) 2007-09-28 2013-03-13 华为技术有限公司 Ip多媒体子系统及容灾恢复方法
EP2213069B1 (en) * 2007-10-19 2012-08-01 Telefonaktiebolaget LM Ericsson (publ) Establishing a multimedia communications session
CN102098652B (zh) * 2008-01-18 2012-12-12 华为技术有限公司 一种为用户提供业务的方法、系统和装置
JP5759064B2 (ja) 2011-05-06 2015-08-05 テケレック・インコーポレイテッドTekelec, Inc. 加入者をアクセスネットワーク間で誘導するための方法、システム、およびコンピュータ可読媒体
US20140095653A1 (en) * 2012-09-28 2014-04-03 Suzann Hua Optimization Of SH Traffic By A Cache-And-Try-First Mechanism
US9319378B2 (en) 2013-01-23 2016-04-19 Tekelec, Inc. Methods, systems, and computer readable media for using a diameter routing agent (DRA) to obtain mappings between mobile subscriber identification information and dynamically assigned internet protocol (IP) addresses and for making the mappings accessible to applications
EP3075127B1 (en) 2013-11-29 2019-03-27 Telefonaktiebolaget LM Ericsson (publ) Method and apparatus for an i-cscf to assign to a user equipment a s-cscf server in an ims system.
US9871828B2 (en) * 2014-07-18 2018-01-16 T-Mobile Usa, Inc. Enhanced IMS services restriction and selection control for mobile devices roaming in foreign networks
US10951519B2 (en) 2015-06-17 2021-03-16 Oracle International Corporation Methods, systems, and computer readable media for multi-protocol stateful routing
US10084755B2 (en) 2015-08-14 2018-09-25 Oracle International Corporation Methods, systems, and computer readable media for remote authentication dial in user service (RADIUS) proxy and diameter agent address resolution
US9923984B2 (en) 2015-10-30 2018-03-20 Oracle International Corporation Methods, systems, and computer readable media for remote authentication dial in user service (RADIUS) message loop detection and mitigation
US10554661B2 (en) 2015-08-14 2020-02-04 Oracle International Corporation Methods, systems, and computer readable media for providing access network session correlation for policy control
US9668135B2 (en) 2015-08-14 2017-05-30 Oracle International Corporation Methods, systems, and computer readable media for providing access network signaling protocol interworking for user authentication
US9668134B2 (en) 2015-08-14 2017-05-30 Oracle International Corporation Methods, systems, and computer readable media for providing access network protocol interworking and authentication proxying
US10015671B2 (en) 2016-01-19 2018-07-03 T-Mobile Usa, Inc. Network service access control
CN109995721B (zh) * 2017-12-29 2021-10-22 华为技术有限公司 业务请求处理方法、装置及通信系统
US11283883B1 (en) 2020-11-09 2022-03-22 Oracle International Corporation Methods, systems, and computer readable media for providing optimized binding support function (BSF) packet data unit (PDU) session binding discovery responses

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20020086163A (ko) * 2001-05-11 2002-11-18 에스케이 텔레콤주식회사 차세대 이동 통신 시스템의 패킷 기반 망에서의 다중 관문운용장치
KR20030055417A (ko) * 2001-12-26 2003-07-04 삼성전자주식회사 Ip 멀티미디어 서비스 가입자의 이동성 관리를 위한가입자 데이터 관리 장치 및 방법

Family Cites Families (51)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6144916A (en) * 1992-05-15 2000-11-07 Micron Communications, Inc. Itinerary monitoring system for storing a plurality of itinerary data points
US5889474A (en) * 1992-05-18 1999-03-30 Aeris Communications, Inc. Method and apparatus for transmitting subject status information over a wireless communications network
US5629693A (en) * 1993-11-24 1997-05-13 Trimble Navigation Limited Clandestine location reporting by a missing vehicle
GB2301725B (en) * 1995-05-31 2000-02-02 Gen Electric A reduced-power GPS-based system for tracking multiple objects from a central location
US5608412A (en) * 1995-06-07 1997-03-04 General Electric Company Protocol and mechanism for mutter mode communication for stationary master tracking unit
US5691980A (en) * 1995-06-07 1997-11-25 General Electric Company Local communication network for power reduction and enhanced reliability in a multiple node tracking system
US5682139A (en) * 1995-06-07 1997-10-28 General Electric Company Railcar location using mutter networks and locomotive transmitter during transit
US5633875A (en) * 1995-06-07 1997-05-27 General Electric Company Protocol and mechanism for centralized asset tracking communications
US5588005A (en) * 1995-06-07 1996-12-24 General Electric Company Protocol and mechanism for primary and mutter mode communication for asset tracking
US5686888A (en) * 1995-06-07 1997-11-11 General Electric Company Use of mutter mode in asset tracking for gathering data from cargo sensors
US5917433A (en) * 1996-06-26 1999-06-29 Orbital Sciences Corporation Asset monitoring system and associated method
US6069570A (en) * 1996-09-20 2000-05-30 Atx Technologies, Inc. Asset location system
US5959529A (en) * 1997-03-07 1999-09-28 Kail, Iv; Karl A. Reprogrammable remote sensor monitoring system
US5835377A (en) * 1997-03-24 1998-11-10 International Business Machines Corporation Method and system for optimized material movement within a computer based manufacturing system utilizing global positioning systems
US5864315A (en) * 1997-04-07 1999-01-26 General Electric Company Very low power high accuracy time and frequency circuits in GPS based tracking units
US6108524A (en) * 1998-02-20 2000-08-22 General Electric Company Inbound messaging transmission device and system for railcar asset tracking using high frequency signaling
US6512455B2 (en) * 1999-09-27 2003-01-28 Time Domain Corporation System and method for monitoring assets, objects, people and animals utilizing impulse radio
US6311060B1 (en) * 1998-05-21 2001-10-30 Cellemetry Llc Method and system for registering the location of a mobile cellular communications device
US6067044A (en) * 1998-09-21 2000-05-23 National Systems And Research Company Remote tracking and sensing system and method
US20020169539A1 (en) * 2001-03-28 2002-11-14 Menard Raymond J. Method and system for wireless tracking
US6392692B1 (en) * 1999-02-25 2002-05-21 David A. Monroe Network communication techniques for security surveillance and safety system
US6545601B1 (en) * 1999-02-25 2003-04-08 David A. Monroe Ground based security surveillance system for aircraft and other commercial vehicles
US6510380B1 (en) * 1999-03-31 2003-01-21 C2 Global Technologies, Inc. Security and tracking system
WO2001001366A2 (en) * 1999-06-25 2001-01-04 Telemonitor, Inc. Smart remote monitoring system and method
US6512478B1 (en) * 1999-12-22 2003-01-28 Rockwell Technologies, Llc Location position system for relay assisted tracking
US6456937B1 (en) * 1999-12-30 2002-09-24 General Electric Company Methods and apparatus for locomotive tracking
US6490523B2 (en) * 1999-12-30 2002-12-03 Ge Harris Railway Electronics, Inc. Methods and apparatus for locomotive tracking
WO2001054021A1 (en) * 2000-01-18 2001-07-26 Richard Liming System and method providing a spatial location context
JP3671795B2 (ja) * 2000-01-26 2005-07-13 松下電工株式会社 通報システム
US6519529B2 (en) * 2000-04-27 2003-02-11 Terion, Incorporated Intermodal movement status monitoring system
US20020128769A1 (en) * 2000-05-17 2002-09-12 Viken Der Ghazarian Electronic vehicle monitoring system
US6339397B1 (en) * 2000-06-01 2002-01-15 Lat-Lon, Llc Portable self-contained tracking unit and GPS tracking system
US6980813B2 (en) * 2000-07-14 2005-12-27 Norbelle, Llc Locating system and method
FI111312B (fi) * 2000-08-25 2003-06-30 Nokia Corp Yhteyden päätelaitteeseen valvonta tietoliikennejärjestelmässä
US7034683B2 (en) * 2000-11-06 2006-04-25 Loran Technologies, Inc. Electronic vehicle product and personnel monitoring
AU2001221632A1 (en) * 2000-11-28 2002-06-11 Nokia Corporation System and method for authentication of a roaming subscriber
US7136832B2 (en) * 2000-12-07 2006-11-14 Savi Technology, Inc. Supply chain visibility for real-time tracking of goods
US20020116123A1 (en) * 2001-02-21 2002-08-22 Lampe Steve C. System and method for event execution responsive to roving unit location
GB0110900D0 (en) * 2001-05-03 2001-06-27 Nokia Corp Registrations in a communication system
US7072668B2 (en) * 2001-05-22 2006-07-04 Geospatial Technologies, Inc. Durable global asset-tracking device and a method of using the same
ATE286641T1 (de) * 2001-07-03 2005-01-15 Ericsson Telefon Ab L M Verfahren und system zur behandlung von mehrfachanmeldungen
US6871070B2 (en) * 2001-07-31 2005-03-22 Lucent Technologies Inc. Communication system for providing roaming between an internet protocol multimedia system and a circuit-switched domain
CA2355426A1 (en) * 2001-08-17 2003-02-17 Luther Haave A system and method for asset tracking
US20030069648A1 (en) * 2001-09-10 2003-04-10 Barry Douglas System and method for monitoring and managing equipment
GB0205399D0 (en) * 2002-03-07 2002-04-24 Nokia Corp Allocation of an S-CSCF to a subscriber
US8121597B2 (en) * 2002-03-27 2012-02-21 Nokia Siemens Networks Oy Method of registering and deregistering a user
US6788676B2 (en) * 2002-10-30 2004-09-07 Nokia Corporation User equipment device enabled for SIP signalling to provide multimedia services with QoS
US6931453B2 (en) * 2003-01-03 2005-08-16 Nokia Corporation Method and apparatus for resolving protocol-agnostic schemes in an internet protocol multimedia subsystem
US9451422B2 (en) * 2003-03-17 2016-09-20 Nokia Technologies Oy Method, system and network device for routing a message to a temporarily unavailable network user
GB0307853D0 (en) * 2003-04-04 2003-05-14 Nokia Corp Registrations in a communication system
US7283506B2 (en) * 2003-10-13 2007-10-16 Nokia Corporation System and method for releasing sessions at network entities associated with the sessions

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20020086163A (ko) * 2001-05-11 2002-11-18 에스케이 텔레콤주식회사 차세대 이동 통신 시스템의 패킷 기반 망에서의 다중 관문운용장치
KR20030055417A (ko) * 2001-12-26 2003-07-04 삼성전자주식회사 Ip 멀티미디어 서비스 가입자의 이동성 관리를 위한가입자 데이터 관리 장치 및 방법

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP1703746A4 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10303066B2 (en) 2003-07-28 2019-05-28 Asml Netherlands B.V. Lithographic projection apparatus and device manufacturing method
JP2010506467A (ja) * 2006-10-03 2010-02-25 テレフオンアクチーボラゲット エル エム エリクソン(パブル) 通信ネットワークにおけるアクセス情報の提供
JP4944202B2 (ja) * 2006-10-03 2012-05-30 テレフオンアクチーボラゲット エル エム エリクソン(パブル) 通信ネットワークにおけるアクセス情報の提供
JP2010531017A (ja) * 2007-06-22 2010-09-16 テレフオンアクチーボラゲット エル エム エリクソン(パブル) ユーザ・データベース・サーバ、サービス・ポリシー・サーバ、及びアプリケーション・サーバを含むipマルチメディア・サブシステム通信ネットワークにおいてユーザ装置を通じてサービスを提供する方法

Also Published As

Publication number Publication date
EP1703746A1 (en) 2006-09-20
EP1703746A4 (en) 2007-03-28
US20070189215A1 (en) 2007-08-16
KR100741152B1 (ko) 2007-07-20
JP4493104B2 (ja) 2010-06-30
CA2552531C (en) 2011-01-04
CA2552531A1 (en) 2005-07-28
KR20060105049A (ko) 2006-10-09
EP1703746B1 (en) 2012-10-03
JP2007518317A (ja) 2007-07-05

Similar Documents

Publication Publication Date Title
WO2005069645A1 (fr) Procede servant a limiter la charge d'interface d'un serveur d'abonnes local
CN1278519C (zh) 将终端能力变化通知给网络的方法
JP4700105B2 (ja) Ipマルチメディアサブシステム(ims)おける呼転送
CN100362807C (zh) 一种实现网际协议多媒体子系统中用户注册的方法
US9031067B2 (en) Routing messages
CN100596076C (zh) 个人网管理中用户设备登记、激活系统、方法及装置
US20040246965A1 (en) System and method for routing messages
CN101563903B (zh) 用于向用户提供ip多媒体子系统通信服务的方法和设备
EP2192742B1 (en) Local session controller, ip multimedia subsystem and session registration method
CN1299533C (zh) 一种用户到归属签约用户服务器进行注册的方法
US20100232368A1 (en) Method for multiple registration of a multimodal communication terminal
WO2007079673A1 (fr) Procede de detection de l'identite d'usager public dans le profil de service d'un systeme de communication et appareil associe
CN100362838C (zh) 一种减轻归属签约用户服务器接口负荷的方法
JP2010527170A (ja) Ipマルチメディアサブシステムにおけるユーザidの処理
US9692835B2 (en) Method and apparatuses for the provision of network services offered through a set of servers in an IMS network
KR100703426B1 (ko) 아이피 기반 멀티미디어 서브시스템에서 가입자 정보유실시 발신 및 착신 호를 가능하게 하는 방법 및 장치
CN100583837C (zh) 一种基于ims的业务实现方法
WO2007090348A1 (fr) Procédé, appareil et système de vérification de la validité pour système uri d'agent utilisateur globalement routable
EP2083577B1 (en) User device and registration method of user device
WO2006047957A1 (fr) Procede pour determiner l'occasion de lancer une selection d'entite a fonction de commande d'appel de service
CN100536484C (zh) 一种ip地址注销方法
CN1997024A (zh) 一种减轻归属签约用户服务器接口负荷的方法
WO2007082493A1 (fr) Procédé et entité de réseau pour le traitement du contenu de message de protocole d'ouverture de session

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 2552531

Country of ref document: CA

WWE Wipo information: entry into national phase

Ref document number: 2005700396

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2006548075

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE

WWW Wipo information: withdrawn in national office

Ref document number: DE

WWE Wipo information: entry into national phase

Ref document number: 1020067015936

Country of ref document: KR

WWP Wipo information: published in national office

Ref document number: 2005700396

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 1020067015936

Country of ref document: KR

WWE Wipo information: entry into national phase

Ref document number: 2007189215

Country of ref document: US

Ref document number: 10585288

Country of ref document: US

WWP Wipo information: published in national office

Ref document number: 10585288

Country of ref document: US