WO2006099815A1 - Procede d'enregistrement d'un utilisateur dans le sous-systeme multimedia ip et systeme associe - Google Patents

Procede d'enregistrement d'un utilisateur dans le sous-systeme multimedia ip et systeme associe Download PDF

Info

Publication number
WO2006099815A1
WO2006099815A1 PCT/CN2006/000502 CN2006000502W WO2006099815A1 WO 2006099815 A1 WO2006099815 A1 WO 2006099815A1 CN 2006000502 W CN2006000502 W CN 2006000502W WO 2006099815 A1 WO2006099815 A1 WO 2006099815A1
Authority
WO
WIPO (PCT)
Prior art keywords
user equipment
user
information
registration
identifier
Prior art date
Application number
PCT/CN2006/000502
Other languages
English (en)
Chinese (zh)
Inventor
Yajuan Wu
Fenqin Zhu
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2006099815A1 publication Critical patent/WO2006099815A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1073—Registration or de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1083—In-session procedures
    • H04L65/1095—Inter-network session transfer or sharing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways

Definitions

  • the present invention relates to the field of Internet Protocol (IP) Multimedia Subsystem (IMS), and in particular, to a method and system for implementing user registration in IMS.
  • IP Internet Protocol
  • IMS Internet Multimedia Subsystem
  • the 3GPP (3GPP, 3rd Generation Partnership Project) standards organization has introduced an IMS architecture to provide a standardized open architecture in a communication network to enable a wide range of multimedia applications. Users offer more choices and richer feelings.
  • FIG. 1 shows a schematic diagram of the IMS architecture.
  • IMS IP Multimedia Subsystem domain
  • CSCF Call Session Control Function
  • MRF Media Resource Function
  • HSS Home Subscriber Server
  • S-CSCF service CSCF
  • P-CSCF proxy CSCF
  • I-CSCF query CSCF
  • the P-CSCF is an access point for the terminal user to access the IMS, and is used for completing user registration and performing quality of service (QoS) control. And security management, etc.; I-CSCF is used to implement route lookup, such as interworking between IMS domain and IMS domain, manage the allocation of S-CSCF, and hide the topology and configuration of the network from external networks and other IMS domains. , generate billing information, and more.
  • the MGCF implements the function of the control gateway to implement interworking between the IMS network and other networks.
  • the MRF provides media resources, such as receiving and receiving audio, encoding and decoding information transmitted between end users, and a multimedia conference bridge.
  • the MRF includes: A Multimedia Resource Function Controller (MRFC) and a Multimedia Resource Function Processor (MRFP).
  • MRFC Multimedia Resource Function Controller
  • MRFP Multimedia Resource Function Processor
  • the user-assigned server (HSS) is a user information database, which stores subscription data and configuration information of users in the IMS network.
  • the 3GPP defined IMS architecture can also be applied to other packet networks other than the 3GPP defined packet domain network, such as the packet network defined by 3GPP2, and the wireless local area network (WLA).
  • WLA wireless local area network
  • Next-generation network (NGN), etc. achieves independence from user terminal types and independence from access network types.
  • IMS is not restricted to 3GPP-related networks and applications, other types of access.
  • the services and applications of the network and the 7-carrier network can also be implemented through the IMS architecture.
  • SIP Session Initiation Protocol
  • IETF Internet Engineering Task Force
  • SIP is used to initiate a session and is capable of building multimedia sessions with multiple participants. Controlling and terminating, and dynamically adjusting and modifying session attributes, which may include: session bandwidth requirements, media types transmitted, such as voice, video, and text, media encoding and decoding formats, and multicast and Unicast support, etc.
  • SIP is used to provide the necessary protocol mechanism to ensure that the terminal system and proxy server can provide the following services: 1. User location; 2. User capability; 3. User availability; 4. Call setup; 5. Call processing; 6.
  • Call forwarding including: equivalent 800 type of call, no answer call forwarding, busy call forwarding, unconditional call forwarding; 7, call number transfer, the number can be named by any mechanism; 8, personal mobility, mainly The called party is reached by a single, location-independent address, even if the called party changes the user equipment; 9.
  • the terminal type negotiation and selection the calling party can select and give the way to the called party, such as through the Internet. Telephone, mobile phone or answering service, etc.; 10. Terminal capability negotiation; 11. Caller and called party authentication; 12. Uninformed and directed call transfer; 13. Invitation to multicast conference.
  • protocol mechanisms provided by SIP above include:
  • Feature negotiation when not all parties of the call can support the same level of features, the group related to the call is allowed to agree on the supported features, which can be a multi-party call;
  • the call feature changes.
  • the user should be able to change the call feature during the call. For example, a call is placed as a voice call, but during the call, the user can turn on the video function as needed, that is, a call-in call.
  • a third party can open different call features in order to join the call.
  • the IMS home network allocates one or more users for each IMS service contract.
  • Private User Identity used in the process of registration, authorization, management, and accounting, can use the format of Network Access Identifier (NAI); each user who has signed an IMS service also has One or more Public User Identities (IMPUs) for identifying themselves when communicating with other IMS users.
  • NAI Network Access Identifier
  • IMPUs Public User Identities
  • the private user identifier is not disclosed to the public, but the public user identifier is publicly disclosed, and the public user identifier is used in the session process of various services.
  • the following users who have contracted the IMS service are referred to as IMS users.
  • each IMS user has one or more logical names, which may be public user identifiers, expressed in a format of a SEP Uniform Resource Identifier (URI), for use with Other IMS users identify themselves when communicating.
  • logical names may be public user identifiers, expressed in a format of a SEP Uniform Resource Identifier (URI), for use with Other IMS users identify themselves when communicating.
  • URI Uniform Resource Identifier
  • the IMS user corresponding to each logical name also has a physical contact address, which is placed in the Contact field for the transmission of the message.
  • the logical name of the IMS user is relatively fixed, and other IMS users will communicate with the IMS user through the logical name; and the physical contact address is dynamically changed, and changes with the location of the IMS user, according to the bearer network where the IMS user is located. Differently, different physical contact addresses are allocated by the corresponding bearer network, and the physical relationship is communicated between the network entity and the IMS user.
  • the registration process is required to notify the IMS network of the current physical contact address of the IMS user, that is, the user agent sends a registration carrying the private user identity, the public user identity (ie, the logical name), and the physical contact address to the registration server (REGISTER). ) Request.
  • the physical contact address is placed in the Contact field of the registration request, so that the IMS network can know the physical contact address of the IMS user; when other IMS users communicate with the IMS user by logical name, the IMS network can respond accordingly.
  • Information is sent to the physical contact address.
  • the user agent described above can be an IMS user. It can also be a server.
  • the registration server described above may be an S-CSCF in the home network of the IMS user.
  • the IMS user needs to provide the private user identity, the public user identity, and the physical contact address to the IMS network when registering.
  • the private user identity is used by the IMS network to authenticate, authorize, and charge the user. If the IMS user is authenticated, the public user identity and the physical contact address of the IMS user, and the corresponding relationship between the two can be stored on the service control function entity of the IMS network; when the IMS user communicates with other IMS users
  • the service control function entity in the IMS network can perform corresponding processing by using the public user identifier and the physical contact address.
  • the IMS network is required to avoid duplicate registration or inconsistent storage information during the registration process. For example: When an IMS user moves from the original IMS network to the new IMS network, although the IMS user has already registered in the new IMS network, the related registration information such as the physical contact address is not logged out in the original IMS network. Or a change in the roaming protocol parameters between the two IMS networks results in a change in the conditions for the roaming user to serve. To meet this requirement, the usual process is: When the IMS user moves to the new IMS network and initiates registration with the S-CSCF in the IMS network, the S-CSCF located in the home network of the IMS user discovers the public with the same private user identity.
  • the last registration of the user ID has not expired, but the physical contact address carried in the new registration request is different from the currently stored physical contact address, and the related registration information such as the currently stored physical contact address must be deleted.
  • This process is completed by the S-CSCF initiating the logout process on the IMS network side, in order to avoid duplicate registration.
  • the S-CSCF stores related registration information such as a new physical contact address.
  • the S-CSCF in the home network of the IMS subscriber is required to log out of the old physical contact address and use the new physical contact address. Processing will make other There is a problem with the IMS session and is explained below.
  • the S-CSCF When the other IMS user requests to establish a session with the public user identifier, the S-CSCF sends a corresponding request to the physical contact address corresponding to the public user identifier according to the correspondence between the public user identifier and the physical contact address. Since the IMS network allows IMS users to register multiple physical contact addresses using the same public user identity, and the IMS network does not restrict the same private user identity to only correspond to one physical contact address. Therefore, the two physical contact addresses should correspond to the same private user ID and the same public user ID, and such use needs exist in practical applications.
  • a mobile handset accessed by an IMS user via a mobile communication network and a laptop accessed via a wireless local area network (WLAN) may have the same private user identity and public user identity, and may register different physics in the IMS network. contact address.
  • the specification has a mandatory limitation that the S-CSCF must deregister the old physical contact address and use the new physical contact address, so that the two physical contact addresses should correspond to the same private user ID and the same public user ID. The situation cannot be seen at all. Because, as long as the IMS user initiates the second registration using the second related device, the first registration initiated by the first related device is cancelled by the IMS network, and the first related device of the first registration is deleted. Physical contact address.
  • the main purpose of the present invention is to provide a method and system for implementing user registration in an IMS, so that the registration process of the IMS user in the IMS network is more complete and reasonable. According to the above object, the technical solution of the present invention is achieved as follows:
  • the invention discloses a method for realizing user registration in the IMS multimedia subsystem IMS.
  • the user sends a registration request carrying the registration information to the IMS registration function entity, and the registration information includes at least: the user identifier and The physical contact address; the registration information further includes user equipment information for identifying the user equipment currently used by the user, and the method includes:
  • the IMS registration function entity determines, according to the registration request, the user identifier, the physical contact address, and the user setting information currently requested to be registered; the user currently requesting registration has the same user identifier and different physical contact address as the registered user.
  • step B Determine, according to the user equipment information in the current registration information, whether the user equipment used by the user currently requesting registration is the same as the user equipment used by the registered user. If they are the same, the registration information carried in the current registration request is stored and the registration is cancelled.
  • the registration information corresponding to the same user identifier in step A otherwise, storing the registration information carried in the current registration request and retaining the registration information corresponding to the same user identifier described in step A.
  • the method for determining that the user currently requesting registration has the same user identifier and different physical contact address as the registered user is: the user identifier currently registered to be registered with any user identifier in the registered registration information. At the same time, determining the registered physical contact address corresponding to the same user identifier in the registered registration information; when the determined registered physical contact address is different from the physical contact address currently requested to be registered, determining the user currently requesting registration and Registered users have the same user ID and different physical contact addresses.
  • step B the determining, according to the user equipment information in the current registration information, whether the user equipment used by the user currently requesting registration is the same as the user equipment used by the registered user is: determining step A in the registered registration information. Determining the registered user equipment information corresponding to the registered physical contact address, determining whether the currently requested user equipment information is the same as the determined registered user equipment information, and if the same, determining the current request The user device used by the registered user is the same as the user device used by the registered corpse; otherwise, it is determined that the user device currently requested to be registered is different from the user device used by the registered user.
  • the user information includes the access network information and the user equipment identifier.
  • Step ⁇ The method for determining whether the currently requested user equipment information is the same as the determined registered user equipment information is:
  • the method for further including the user equipment information in the registration information carried by the registration request is: using the newly added information domain or the original information domain in the registration request to carry the user equipment information.
  • the registration request is a session initiation protocol SIP message
  • the method for using the newly added information field to carry the user equipment information is: adding a feature tag to the contact information of the SIP message as the registration request, and using the feature tag to carry the user equipment information;
  • the method for using the original information domain to carry the user equipment information is: extending a call information Call-Info information field of a SIP message as a registration request, and using the extended Call-Info information field to carry the User device information.
  • the user equipment information includes: access network information and/or user equipment identifier; the user equipment identifier includes: a user equipment identifier, or a combination of a user equipment identifier type and a user equipment identifier.
  • the method for carrying the user equipment identifier in the user setting information is:
  • the user equipment identification type and the user equipment identifier are carried as two independent information; or
  • the combination of the user equipment identification type and the user equipment identifier is carried as a piece of information.
  • the user equipment identifier is an IMEI value saved in the user equipment when the user equipment identifier type is an international mobile subscription subscriber identity IMEI; and the user equipment identifier is a media access control MAC, the user equipment identifier
  • the method further includes: setting a user equipment registration server, where the user equipment registration server is configured to save the correspondence between the user equipment information and the status thereof;
  • the user equipment information in the registration information is further sent to the user equipment registration server; when the state of the user equipment changes, the user equipment information is further reported and a current state to the user equipment registration server, where the user equipment registration server updates the status corresponding to the user equipment information;
  • the user equipment registration server queries the status of the user equipment according to the user equipment information, and if the status is available, provides the IMS service requested by the user equipment; otherwise, refuses to provide the IMS service requested by the user equipment.
  • the IMS registration function entity is a service call session control in an IMS network.
  • Function S-CSCF Function S-CSCF.
  • the user equipment information includes: information of the calling user equipment and/or information of the called user equipment.
  • the invention also discloses a system for realizing user registration in an IMS, the system comprising: a user equipment and an IMS registration function entity,
  • the user equipment is configured to send a registration request to the IMS registration function entity, where the registration information carried by the registration request at least includes: user equipment information, a user identifier, and a physical contact address;
  • the IMS registration function entity is configured to receive a registration request from the user equipment, and obtain registration information from the registration request; when the user currently requesting registration has the same user identifier and different physical contact address as the registered user,
  • the user equipment information in the current registration information determines whether the user equipment used by the user currently requesting registration is the same as the user equipment used by the registered user. If they are the same, the registration information carried in the current registration request is stored and the registered registration is cancelled.
  • the registration information corresponding to the same user identifier otherwise, the registration information carried in the current registration request is stored and the registration information corresponding to the registered same user identifier is retained.
  • the IMS registration function entity includes: a registration request parsing module, configured to parse the registration information from the received registration request and output the registration information to the registration processing module;
  • a registration processing module configured to receive registration information from the registration request parsing module, and determine, according to user equipment information in the current registration information, that the user currently requesting registration has the same user identifier and different physical contact address as the registered user Whether the user equipment used by the user who requested the registration is the same as the user equipment used by the registered user. If they are the same, the registration information carried in the current registration request is stored and the registration information corresponding to the registered same user identifier is cancelled; otherwise, Store the registration information carried in the current registration request and protect The registration information corresponding to the registered same user identifier is retained.
  • the system further includes: a user equipment registration server, configured to receive a state of the user equipment from the outside, and save a correspondence between each user equipment and its state, from the
  • the IMS registration function entity receives the user equipment information in the registration information and returns a corresponding user equipment status to the IMS registration function entity.
  • the IMS registration function entity is an S-CSCF in the IMS network.
  • the IMS registration function entity such as the S-CSCF determines that the physical contact address carried in the registration request is inconsistent with the stored physical contact address corresponding to the current user identifier
  • the judgment of the user equipment information may be further determined. Determine if the two different physical contact addresses correspond to different user devices. In this way, registration of different user devices using the same user identity is made possible.
  • the user registration information described above may be access network information and/or user equipment identification.
  • the present invention further enables the IMS network to manage the user equipment according to the user equipment information based on the above-mentioned request for providing the user equipment identity to the IMS network through the registration request.
  • Figure 1 shows a schematic diagram of an IMS architecture
  • FIG. 2 is a flow chart showing a preferred embodiment of IMS user registration in the method of the present invention
  • FIG. 3 is a flow chart showing another preferred embodiment of IMS user registration in the present invention
  • FIG. 4 shows a system 1 of the present invention.
  • the invention discloses a method for realizing user registration in IMS, the method is applicable to existing IMS
  • the user registration method is improved, and its main design idea is:
  • the registration information carried in the registration request includes at least a user identifier and a physical contact address
  • the present invention further includes a user identifier for identifying the user equipment currently used by the user in the information carried in the registration request.
  • the process includes: the user sends a registration request carrying the registration information to the IMS registration function entity, and the IMS registration function entity determines, according to the registration request, the user identity, the physical contact address, and the user equipment information that are currently requested to be registered;
  • the user currently requesting registration has the same user ID and different physical contact address as the registered user, the user equipment information in the current registration information is used to determine whether the user equipment currently used by the user requesting registration is used by the registered user.
  • the user equipments are the same.
  • the registration information carried in the current registration request is stored and the registration information corresponding to the registered same user identifier is deregistered; otherwise, the registration information carried in the current registration request is stored and the registered office is retained.
  • the registration information corresponding to the same user identifier is described.
  • the method for determining that the user currently requesting registration has the same user identifier and different physical contact address as the registered user is: any one of the user identifier currently registered and the registration information registered by the IMS registration function entity.
  • the registered physical contact address corresponding to the same user identifier in the registered registration information is determined; when the determined registered physical contact address is different from the physical contact address currently requested to be registered, determining that the current request is registered
  • the user has the same user ID and different physical contact address as the registered user.
  • the determining, according to the user equipment information in the current registration information, whether the user equipment used by the user currently requesting registration is the same as the user equipment used by the registered user is: determining that the registered information is registered in the registration information.
  • the user equipment information corresponding to the physical contact address is used to determine whether the user equipment information currently registered is the same as the determined registered user equipment information. If they are the same, the current request for registration is determined.
  • the user equipment used by the user is the same as the user equipment used by the registered user; otherwise, it is determined that the user equipment currently requested to be registered is different from the user equipment used by the registered user.
  • the IMS registration function entity is mainly the S-CSCF in the IMS network.
  • the user equipment information further included in the registration information for identifying the user equipment currently used by the user may also be referred to as additional registration information.
  • additional registration information In this way, when the S-CSCF cannot determine whether the current registration process is initiated by a different user equipment that uses the same user identifier according to the user identifier and the physical contact address, that is, the S-CSCF determines that the physical contact address carried in the registration request and the stored correspondence correspond to the current If the physical contact address of the user identifier is inconsistent, the user equipment corresponding to the current registration request is determined to be the same as the user equipment corresponding to the stored registration information of the current user identifier. In this way, registration of different user devices using the same user identity is made possible.
  • FIG. 2 is a flow chart showing a preferred embodiment of the IMS user registration in the present invention. As shown in FIG. 2, the registration implementation process of the IMS user includes the following steps:
  • Step 201 to step 202 The S-CSCF receives a registration request, where the registration request carries a private user identifier, a public user identifier, a physical contact address, and additional registration information, and then the S-CSCF determines whether the private user identifier and the public user are searched for.
  • the corresponding registration information is identified, and if yes, step 204 is performed; otherwise, step 203 is performed.
  • the additional registration information described above may be access network information and/or user equipment identification.
  • Step 203 The S-CSCF performs a normal registration process, and stores related registration information, including: a private user identifier, a public user identifier, a physical contact address, and additional registration information, and ends the current processing flow.
  • related registration information including: a private user identifier, a public user identifier, a physical contact address, and additional registration information, and ends the current processing flow.
  • Step 204 The S-CSCF determines whether the physical contact address carried in the registration request is the same as the physical contact address in the searched, currently stored registration information. If yes, step 205 is performed; otherwise, step 206 is performed.
  • the searched, currently stored registration information The contact address is the physical contact address corresponding to the private user ID and the public user ID.
  • Step 205 The S-CSCF performs a normal re-registration process, and stores related registration information, including: a private user identifier, a public user identifier, a physical contact address, and additional registration information, and ends the current processing flow.
  • Step 206 The S-CSCF determines whether the additional registration information carried in the registration request is the same as the additional registration information in the searched, currently stored registration information. If yes, step 207 is performed; otherwise, step 208 is performed.
  • the additional registration information in the currently stored registration information that is searched for is the additional registration corresponding to the private user identification and the public user identification.
  • Step 207 The S-CSCF stores new registration information, including: a new private user identifier, a public user identifier, a physical contact address, and additional registration information, and cancels the original registration information (that is, the searched registration information), including: The original private user ID, public user ID, physical contact address, and additional registration information complete the current processing flow.
  • Step 208 The S-CSCF stores new registration information, including: a new private user identifier, a public user identifier, a physical contact address, and additional registration information, and retains the original registration information, that is, the searched registration information, including: Private user ID, public user ID, physical contact address, and additional registration information.
  • each user equipment can only support one access mode, that is, the user equipment is a single-mode terminal, the user equipment can distinguish by access network information, so the additional registration information can be access network information.
  • the S-CSCF may determine whether the current registration request is a registration process initiated by a different user equipment that uses the same user identifier by comparing the access network information in the registration request with the searched and currently stored access network information.
  • the determination in step 206 is: determining the access network information (ie, the new access network information) carried in the registration request and the access network information in the searched, currently stored registration information (ie, the old access network) Letter If the old and new access networks are different, that is, the old and new access modes are different, it indicates that the current registration process is initiated by different user devices using the same user ID, and the S-CSCF will store the new registration information and keep it.
  • the original registration information if the old and new access network information is the same, that is, the old and new access methods are the same, it indicates that the current registration process is initiated by the same user equipment using the same user identifier, and the S-CSCF stores the new registration information and cancels the original Some registration information.
  • the access network information described above may be P-Access-Network-Info.
  • the additional registration information may be a user equipment that can uniquely identify the user equipment. logo.
  • the S-CSCF can determine whether the current registration request is a registration process initiated by different user equipments using the same user identifier by comparing the user equipment identifier in the registration request with the searched, currently stored user equipment identifier.
  • the determination in step 206 is: determining whether the user equipment identifier (ie, the new user equipment identifier) carried in the registration request and the searched user equipment identifier (ie, the old user equipment identifier) in the currently stored main volume information are Similarly, if the old and new user equipment identifiers are different, it indicates that the current registration process is initiated by different user equipments that use the same user identifier, and the S-CSCF will store the new registration information and retain the original registration information; if the old and new user equipment identifiers are the same , indicating that the current registration process is initiated by the same user equipment using the same user identifier, and the S-CSCF will store the new registration information and cancel the original registration information.
  • the user equipment identifier ie, the new user equipment identifier
  • the searched user equipment identifier ie, the old user equipment identifier
  • S-CSCF The user equipment that does not carry the device identifier in the registration request may be regarded as a default user equipment identifier, that is, the user equipment identifier is not carried in the registration request, and a user equipment is also identified. If the user equipment identifier is carried in the registration request, and the user equipment identifier is not included in the registration information stored in the IMS network, the S-CSCF considers the current registration process to be initiated by different user equipments using the same user identifier.
  • the S-CSCF will store the new registration information and retain the original registration information; vice versa. If the user equipment identifier is not carried in the new and old registration information, the S-CSCF regards the current registration process as being initiated by the same user equipment using the same user identifier, and the S-CSCF stores the new related registration information and cancels the original registration information. Registration information.
  • the user equipment identity of the present invention may use a Media Access Control (MAC) address that uniquely identifies the user equipment.
  • MAC Media Access Control
  • the type of the access network used by the user equipment to access the IMS network may be determined first, and then the user equipment identifier is further determined. That is, the user equipments of different access modes are differentiated according to the access network information. If the access network information is the same, it is still impossible to determine whether the current registration process is initiated by different user equipments using the same user identifier, and then further It is determined according to the user equipment identifier that the current registration process is initiated by different user equipments that use the same user identifier or the same user equipment.
  • MAC Media Access Control
  • the user equipment identifier of the user equipment accessed by the GSM/GPRS/WCDMA method is an International Mobile Subscriber Identity (IMEI), and the user equipment identifier of the user equipment accessed through the xDSL/WLAN may be a MAC address.
  • IMEI International Mobile Subscriber Identity
  • MEID Mobile Equipment Identifier
  • some access networks may not yet define related information such as the user equipment identifier, so in order to meet future needs, The user equipment identification and other related information are defined for these access networks, but it is necessary to ensure that one user equipment can be uniquely identified in all networks using such access technologies.
  • FIG. 3 is a flow chart showing another preferred embodiment of the IMS user registration in the present invention. As shown in Figure 3, the specific processing steps include:
  • Step 301 to step 302 The S-CSCF receives a registration request, and the registration request carries a private The user identifier, the public user identifier, the physical contact address, the access network information, and the user equipment identifier, and then the S-CSCF determines whether the registration information corresponding to the private user identifier and the public user identifier is searched, and if yes, performs the step. 304; Otherwise, go to step 303.
  • Step 303 The S-CSCF performs a normal registration process, and stores related registration information, including: a private user identifier, a public user identifier, a physical contact address, an access network information, and a user equipment identifier, and ends the current processing flow.
  • Step 304 The S-CSCF determines whether the physical contact address carried in the registration request is the same as the physical contact address in the searched, currently stored registration information. If yes, step 305 is performed; otherwise, step 306 is performed.
  • the physical contact address in the searched, currently stored registration information is a physical contact address corresponding to the private user identifier and the public user identifier.
  • Step 305 The S-CSCF performs a normal re-registration process, and stores related registration information, including: a private user identifier, a public user identifier, a physical contact address, an access network information, and a user equipment identifier, and ends the current processing flow.
  • related registration information including: a private user identifier, a public user identifier, a physical contact address, an access network information, and a user equipment identifier, and ends the current processing flow.
  • Step 306 The S-CSCF compares the access network information carried in the registration request with the searched access network information in the currently stored registration information, and determines whether the access mode is the same. If yes, step 307 is performed; Otherwise, go to step 309.
  • the access network information in the searched, currently stored registration information is access network information corresponding to the private user identifier and the public user identifier.
  • Step 307 The S-CSCF determines whether the user equipment identifier carried in the registration request is the same as the user equipment identifier in the searched, currently stored registration information. If yes, step 308 is performed; otherwise, step 309 is performed.
  • the user equipment identifier in the searched, currently stored registration information is the user equipment identifier corresponding to the private user identifier and the public user identifier.
  • Step 308 The S-CSCF stores new registration information, including: a new private user identifier, The public user ID, the physical contact address, the access network information, and the user equipment identifier, and the original registration information (that is, the searched registration information) are up and deleted, including: the original private user identifier, the public user identifier, the physical contact address, Access network information and user equipment identification, and end the current processing.
  • Step 309 The S-CSCF stores new registration information, including: a new private user identifier, a public user identifier, a physical contact address, an access network information, and a user equipment identifier, and retains the original registration information, that is, the search information that is searched. , including: original private user ID, public user ID, physical contact address, access network information, and user equipment ID.
  • the concept of the access network information and/or the user equipment identifier is introduced in the IMS network using the SIP as the signaling control protocol, that is, the user equipment identifier and/or the access network are carried by the SIP message.
  • the user equipment described herein may also be referred to as a terminal device.
  • Various methods of carrying user equipment identity and/or access network information over SIP messages are set forth in detail below.
  • the method for carrying the access network information by using the SIP message because the existing SIP message has an information field for carrying the access network information, the present invention can use the existing information domain to carry the access network information.
  • message format As shown in the following message format:
  • Access Network Information Access-Network-Info": Access Network Specification
  • Access Network Specification Access Type * (SEMI Access Information)
  • Device ID "device-identifier” (referenced string)
  • Access information 3GPP cell global identity / 3GPP UMTS access network cell identity / extended access information
  • 3GPP cell global identifier "cgi-3gpp" (token/referenced string)
  • 3GPP UMTS access network cell identity "utran-cell-id-3gpp” (token string referenced by token I)
  • extended access information value generated during processing
  • token is the meaning of token or token.
  • the message format of the access network information based on the above Chinese expression is as follows: an example of a message format expressed in English:
  • Access-net-spec access-type * ( SEMI access-info )
  • Device identifier " device-identifier” EQUAL ( quoted-string )
  • Access-info cgi-3gpp I utran-cell-id-3gpp I
  • extension-access- Info gen-value. Since the present invention uses the information domain of the existing SIP message to carry the access network information, the various message formats in which the existing SIP message carries the access network information are not described in detail herein, but are all in the protection scope of the present invention. within.
  • the user equipment identifier may be placed under the access type, and the specific user equipment identifier is determined according to the access type when used. For example: If the access type is "IEEE-802.11a" or "IEEE-802.11b M , the user equipment identity can be a MAC address; if the access type is "3GPP-GERAN” or “3GPP-UTRAN-FDD” or “3GPP-UTRAN-TDD", the user equipment identifier is IMEI; if the access type is "3GPP-CDMA2000", the user equipment identifier is MEID.
  • the security mechanism of the IMS network can ensure this.
  • the user equipment identifier may be provided as part of the access network information and provided when the user equipment provides the access network information to the IMS network.
  • the functional entity responsible for processing the service in the IMS network may use the user equipment identifier, and sometimes combine other information to assist the processing of the service.
  • Method 1 The information field added in the SIP message is used to carry and transmit user equipment identification information.
  • the following describes a method for carrying a SIP message bearer and transmitting a user equipment identifier by adding a new information field (that is, adding a new parameter) in the Contact header field of the SIP message.
  • a new feature tag is added to the Contact header field defined by the SIP specification, and the feature tag is used to indicate a user equipment identifier, and the feature tag can be similarly defined as: sip.device_id, but the invention is not limited
  • the feature tag is specifically defined.
  • the user equipment identifier of the present invention may be: a user equipment identifier, or a combination of a user equipment identification type and a user equipment identifier. Therefore, the feature tag can directly carry a specific user equipment identifier, such as: an identifier for identifying the user equipment that is uniformly allocated according to a certain rule in the SIP network; the feature label can also carry the user equipment identifier type and the specific User device identifier.
  • the feature tag may also be used to indicate a part of the user equipment identifier, and the other part may be information originally carried in the Contact header field, such as a public user identity.
  • the feature tag can be represented by a character string, for example: first explicitly indicating the user device identification type, and further indicating a specific user equipment identifier.
  • the value of the user equipment identification type of the present invention may be: MAC, or IMEI, or MEID, and the like.
  • the user equipment identification type is not limited to the above three types, and does not exclude other user equipment identification types, but all are within the protection scope of the present invention.
  • the specific user equipment identifier needs to be determined, for example: if the user equipment identifier type is IMEI, the user equipment identifier is saved in the user equipment corresponding to the SIP user agent (UA).
  • the user equipment identifier may be a Universally Unique IDentifier (UUID) or .
  • UUID Universally Unique IDentifier
  • Example 1 The message format of the user equipment identification type and the user equipment identifier in the Contact header field is as follows:
  • the new feature tag in the Contact header field is: device_id, and the user device identifier type is: IMEI.
  • the specific user device identifier is: 350112408932969.
  • User device identifiers here can have their own independent naming conventions, as well as existing naming conventions.
  • Example 2 The user equipment identification type and the user equipment identifier in the Contact header field are put together to represent the message format:
  • the new feature tag in the Contact header field is: device_id
  • the user device identifier type is: IMEI
  • the specific user device identifier is: 350112408932969.
  • the user device identifier here can have its own independent naming convention, or it can use the existing naming convention.
  • the new feature tag in the Contact header field is: device_id, and the user device identifier is: 00-20-ed-aa-49-e8.
  • the user equipment identifier here should have its own independent naming principle.
  • Example 4 The message format for setting only the user equipment identifier in the Contact header field is:
  • the new feature tag in the Contact header field is: device_id, and the content in the feature tag is part of the user device identifier, such as: the second half or the first half or the middle part Wait.
  • the user equipment identifier may be formed by a public user identifier (such as IMPU or MSISDN) and an index value of the user equipment, and the user equipment identifier may distinguish one of several user equipments sharing the same public user identifier.
  • the user equipment identifier in the example 4 is formed by the index values in the IMPU and the device-id carried in the Contact header field, that is, the user equipment identifier is sip:user@example.com: 03, where the index value is Independent naming principles.
  • the SIP node can use the transmission mechanism of the Contact header field in the current SIP network to implement the transmission of the user equipment identifier.
  • Example 5 In the feature tag added to the Contact header field, the UUID (UniU unique IDentifier) namespace is reused, and the UUID is used to uniquely identify a user device, which can be expressed as:
  • the method for constructing the user equipment identifier of the present invention and the method for carrying and transmitting the user equipment identifier in the new information field of the SIP message It is not limited to the several forms listed above.
  • the user equipment identifier carried in the new information domain of the SIP message may be the identity of the calling user equipment or the user equipment of the called user, or the identity of the calling user equipment and the called user equipment identifier. Hosted in the new information domain.
  • Method 2 The information domain existing in the SIP message is used to carry and transmit the user equipment identifier, that is, the information domain existing in the SIP specification is extended, so that the extended information domain can carry the user equipment identifier.
  • the transmission of the user equipment identity can be implemented using existing mechanisms.
  • the SIP node that does not recognize the extended information domain does not process the extended information domain, that is, skips the unrecognized information domain according to the existing SIP protocol. Then, the other information fields of the SIP message continue to be processed, and therefore, the implementation process of the existing SIP protocol is not affected.
  • the following is an example of extending the existing call information (Call-Info) information field as an example to describe a method for carrying and transmitting a user equipment identifier by using an existing information field of a SIP message.
  • the Call-Info information field is used to carry the additional information of the calling party, and the Call-Info information field is used to carry the additional information of the called party in the response message. Therefore, the Call-Info information field is very suitable for transmitting the main message. Call the user equipment ID of both parties.
  • Example 6 Add a purpose in the Call-Info information field to indicate that the user equipment identifier is carried in the Call-Info information field, and the user equipment identifier type and the user equipment identifier are separately represented, and the message format is as follows: Show.
  • the so-called new purpose does not refer to the newly added information field, but the value of the existing information domain is extended, and the value of the new purpose is used to indicate whether the current device is the user equipment identifier.
  • the user equipment identification type is: IMEI
  • the specific user equipment identifier is: 350112408932969.
  • the user equipment identifiers here can have their own independent naming principles or existing naming conventions.
  • Example 7 The existing purpose is used to carry the user equipment identifier.
  • the user device identification type is: IMEI
  • the specific user device identifier is: 350112408932969.
  • the SIP network function entity that processes this information needs to understand the naming principle of the user equipment identity, so that it can parse and determine whether the user equipment identity information or the original additional information is carried in the Call-Info information domain.
  • the user equipment identifiers here can have their own independent naming principles or existing naming conventions.
  • Example 8 adding a purpose in the Call-Info information field to indicate that the user equipment identifier is carried in the Call-Info information field, and the user equipment identifier information only includes: the user equipment identifier.
  • the message format is as follows:
  • the user device identifier is: 00-20-ed-aa-49-e8.
  • the user device identifier here should have its own independent naming convention.
  • Example 9 In the Contact header field, only the user equipment identifier is set.
  • the user equipment identifier is sip:user@example.com:03
  • the user equipment identifier may be composed of a public user identifier (such as IMPU or MSISDN) and an index value of the user equipment, the user equipment
  • the identifier can be used to identify one of several user devices that share the same public user identity.
  • the first half of the user equipment identifier (such as sip:user@example.com) can use the existing naming principle, and the second half (such as 03) should have its own independent naming principle.
  • the existing SIP network does not consider how to transmit information such as the user equipment identifier of the SIP terminal to each functional entity in the SIP network, after the user device is lost, any user who obtains the user equipment can use the user.
  • the equipment without any cost, is unavoidable for IMS users, which will greatly reduce the user satisfaction of the IMS network, which is not conducive to the IMS service.
  • What is more serious is that the user equipment stores more or less user information, such as: IP Multimedia Service Identity Module (ISIM) or Universal User Equipment Identity Module (USIM) configured on the IMS user equipment for storing private users. Information such as logos and many public user IDs. Therefore, if the user equipment is lost, it may have a serious impact on the communication security of the IMS user.
  • ISIM IP Multimedia Service Identity Module
  • USIM Universal User Equipment Identity Module
  • the registration request received by the S-CSCF carries the user equipment identifier, so that the IMS network using SIP as the signaling control protocol can implement management of the user equipment.
  • the user equipment registration server (DIR, Device Identity Register) can be set up in the IMS network, and the user equipment registration server is used to store the user equipment identifier of the IMS user, such as: IMEI, MAC For the address, MEID, etc., the device identification server manages the user device ID uniformly.
  • the user equipment registration server may first query the status identifier of the corresponding user equipment identifier. If the status identifier is available, the IMS network provides various services to the IMS user; otherwise, the IMS network is refused to be provided to the user.
  • the user equipment registration server may first query the status identifier of the corresponding user equipment identifier. If the status identifier is available, the IMS network provides various services to the IMS user; otherwise, the IMS network is refused to be provided to the user.
  • IMEI User Equipment identifier
  • the IMS network roots the user equipment identifier registered at the time of the user subscription, and is identified at the user equipment registration server, such as adding a disable identifier.
  • the user equipment is disabled, so that when the user equipment accesses the IMS network, the user equipment identifier will be carried to the IMS network through the registration request, and the IMS network determines the user equipment by querying the user equipment registration server.
  • the identity is disabled, and the user currently using the user device to access the IMS network cannot use the various services provided by the IMS network.
  • the IMS network can combine the location service, track the lost user equipment, and obtain the specific location where the user equipment is currently located for related processing.
  • the S-CSCF after the S-CSCF receives the registration request, the judgment of the additional registration information such as the user equipment identifier and/or the access network information is added, so that registration of different user equipments using the same user identifier becomes possible.
  • An IMS user has both a PDA that supports WLAN/GPRS access and a mobile terminal that supports GPRS access. These two user devices use the same IMPI and IMPU, then when the IMS user uses handheld power The time of the brain can be registered to the IMS network by means of GPRS; thereafter, when the IMS user also registers another mobile terminal to the IMS network by using the GPRS access mode, the S-CSCF can identify the user equipment of the mobile terminal.
  • this is a registration process initiated by the user equipment of the original handheld computer.
  • the handheld computer and the mobile terminal use the identifier of the GPRS network that uniquely identifies the user equipment, so the S-CSCF can distinguish the two different user equipments, so that the network side logout process is not initiated to delete the stored handheld computers.
  • Registration information if the PDA has been registered in the IMS network by means of GPRS, and subsequently the IMS user carries the PDA to roam to another GPRS network, the GPRS mode is initiated again without logging off the previous registration.
  • the S-CSCF can determine that this is a duplicate registration initiated by the same user equipment through the current user equipment identifier, thereby initiating the network side logout process, deleting the original registration information of the old handheld computer, and storing the new palm. Current registration information for the computer.
  • the present invention also provides a system for implementing user registration in an IMS, the system comprising: a user equipment and an IMS registration function entity; the system is different from the existing user registration system in that: The user equipment is configured to send a registration request to the IMS registration function entity, and the registration information carried by the registration request at least includes: user equipment information, a user identifier, and a physical contact address; the IMS registration function entity is configured to receive from the user equipment Registration request, parsing the registration information including the user equipment information, the user identifier, and the physical contact address from the registration request; when the user currently requesting registration has the same user ID and different physical contact address as the registered user, The user equipment information determines whether the user equipment used by the user currently requesting registration is the same as the user equipment used by the registered user.
  • Fig. 4 is a block diagram showing the structure of a preferred embodiment of the system of the present invention.
  • the system of the embodiment includes: a user equipment and an IMS registration function entity, where the IMS registration function entity includes: a registration request parsing module and a registration processing module. Since the present invention is concerned with the improvement of the prior art of the present invention, for the description of the cylinder, only the functional modules related to the processing of the present invention in the user equipment and the IMS registration function entity are shown in FIG. 4, for the existing and the present invention. The irrelevant functional modules are not described herein, but the user equipment and the IMS registration functional entity including these existing functional modules unrelated to the present invention and including the modules shown in Fig. 4 are still within the scope of the present invention.
  • the user equipment is configured to send a registration request to the IMS registration function entity, and the registration information carried by the registration request at least includes: user equipment information, a user identifier, and a physical contact address.
  • the registration request parsing module is configured to parse the registration information from the registration request from the user equipment and output the registration information to the registration processing module, the registration information including at least: user equipment information, a user identifier, and a physical contact address.
  • the registration processing module is configured to receive registration information from the registration request parsing module, and determine the received registration information and the registered registration information, when the user currently requesting registration has the same user identifier and different physical contact address as the registered user.
  • the system may further comprise: a user equipment registration server coupled to the registration processing module in the IMS registration function entity.
  • the user equipment registration server is configured to acquire the state of each user equipment in real time from the outside through a GSM or GPRS or IMS process, and save a correspondence between each user equipment and its state, and receive the registration information from the registration processing module connected to itself.
  • User equipment information and return the corresponding user equipment status to the IMS registration function Can be an entity.
  • the IMS registration function entity can determine the state of the user equipment used by the current user (for example, whether the user equipment is in an available state) when the user requests to use the IMS service, thereby determining whether to allow the user to use the IMS service.
  • the IMS registration function entity in the system of the present invention usually adopts an S-CSCF in the IMS network.
  • the method and system of the present invention can meet the requirements of users simultaneously registering different user equipments by using the same user identifier, so that the registration process of the IMS user in the IMS network is more complete and reasonable.

Landscapes

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

Abstract

Procédé d'enregistrement d'un utilisateur dans le ISM comprenant les étapes suivantes: envoi par l'utilisateur d'une demande d'enregistrement comprenant l'information sur l'enregistrement à l'entité de fonction d'enregistrement IMS lors du lancement de l'enregistrement sur IMS, l'information sur l'enregistrement contenant l'information sur l'équipement utilisateur. Le procédé comprend les deux étapes suivantes: A) l'entité de fonction d'enregistrement IMS réalise l'étape B) lorsque l'utilisateur demandant l'enregistrement actuel a le même identificateur utilisateur et une adresse de connexion physique différente de l'utilisateur enregistré; B) on détermine si l'équipement utilisateur utilisé par l'utilisateur qui demande l'enregistrement actuel et l'équipement utilisateur utilisé par l'utilisateur enregistré sont semblables d'après l'information sur l'équipement utilisateur. Dans le cas positif, l'information sur l'enregistrement actuel est mémorisée et l'information sur l'enregistrement concernant le même identificateur utilisateur enregistré n'est plus sur la session.Dans le cas contraire, l'information sur l'enregistrement actuel est mémorisée et l'information sur l'enregistrement correspondant au même identificateur utilisateur enregistré est maintenue. Système susceptible d'enregistrer un équipement utilisateur différent avec le même identificateur utilisateur.
PCT/CN2006/000502 2005-03-24 2006-03-24 Procede d'enregistrement d'un utilisateur dans le sous-systeme multimedia ip et systeme associe WO2006099815A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200510058908.9 2005-03-24
CNB2005100589089A CN100362807C (zh) 2005-03-24 2005-03-24 一种实现网际协议多媒体子系统中用户注册的方法

Publications (1)

Publication Number Publication Date
WO2006099815A1 true WO2006099815A1 (fr) 2006-09-28

Family

ID=37015872

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2006/000502 WO2006099815A1 (fr) 2005-03-24 2006-03-24 Procede d'enregistrement d'un utilisateur dans le sous-systeme multimedia ip et systeme associe

Country Status (2)

Country Link
CN (1) CN100362807C (fr)
WO (1) WO2006099815A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8935374B2 (en) 2008-08-15 2015-01-13 Zte Corporation Method, system, and device for realizing registration mechanism of IP multimedia subsystem
CN111092949A (zh) * 2019-12-20 2020-05-01 北京百度网讯科技有限公司 用于注册设备的方法及装置

Families Citing this family (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101155186A (zh) * 2006-09-30 2008-04-02 华为技术有限公司 一种因特网协议多媒体业务子系统的鉴权方法
CN101043526B (zh) * 2007-04-30 2010-08-04 华为技术有限公司 在ims网络中处理消息的方法、装置及系统
CN101299697B (zh) 2007-04-30 2012-09-05 华为技术有限公司 注销无线ip接入网联系地址的方法和设备
CN101316262B (zh) * 2007-05-31 2011-07-13 中兴通讯股份有限公司 一种控制同帐号终端重复注册的方法
CN101330717B (zh) * 2007-06-26 2011-05-25 中兴通讯股份有限公司 Ip多媒体子系统中用户多个联系地址同时注册的方法
US8913585B2 (en) * 2007-06-28 2014-12-16 Motorola Mobility Llc Method and system for providing IMS session continuity to a user equipment across a plurality of communication networks
CN101330645B (zh) * 2007-07-31 2011-08-10 中兴通讯股份有限公司 一种ip多媒体子系统中建立会话的方法
CN101127769B (zh) * 2007-08-20 2012-04-04 华为技术有限公司 基于会话发起协议的用户注册的方法、系统及终端、服务器
ES2371961T3 (es) * 2007-10-26 2012-01-12 Telefonaktiebolaget Lm Ericsson (Publ) Agrupamiento de identidades de usuario en un subsistema multimedia ip.
CN101217541B (zh) * 2008-01-15 2011-05-11 中兴通讯股份有限公司 一种会话初始协议终端向服务器联动注册的方法
WO2009150092A1 (fr) 2008-06-11 2009-12-17 Nokia Siemens Networks Oy Procédé, appareil, système et produit de programme d'ordinateur apparenté pour une gestion de transfert
US8880067B2 (en) * 2008-08-08 2014-11-04 Qualcomm Incorporated Correlating registrations originating from a device
CN101820381B (zh) 2009-02-27 2013-06-12 华为技术有限公司 一种业务路由的方法,系统和装置
CN101841801B (zh) * 2009-03-16 2012-12-26 中国移动通信集团公司 一种在ims网络中注册及通信的方法、系统及用户终端
CN101931935B (zh) * 2009-06-25 2013-09-11 华为技术有限公司 终端接入方法、网络设备和通信系统
US8560410B2 (en) * 2010-08-13 2013-10-15 T-Mobile Usa, Inc. Mapping a mobile device location to billing regions in internet protocol multimedia subsystems
CN103888434B (zh) * 2012-12-21 2017-08-08 中国移动通信集团北京有限公司 一种ims网络中控制用户终端登录的方法和装置
CN107547489A (zh) * 2016-06-29 2018-01-05 北京信威通信技术股份有限公司 一种重新注册的方法、装置及系统
CN110417705B (zh) * 2018-04-26 2022-03-01 视联动力信息技术股份有限公司 一种用户账号的注册方法和装置
CN111260304B (zh) * 2019-11-26 2024-03-08 上海赛连信息科技有限公司 一种试用账户管理和发放方法和装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002082731A1 (fr) * 2001-04-03 2002-10-17 Nokia Corporation Enregistrement d'un utilisateur dans un reseau de telecommunication
US20030159067A1 (en) * 2002-02-21 2003-08-21 Nokia Corporation Method and apparatus for granting access by a portable phone to multimedia services
WO2003081431A1 (fr) * 2002-03-22 2003-10-02 Nokia Corporation Identite provisoire pour l'authentification avec un protocole de lancement de session
US20040153667A1 (en) * 2002-05-22 2004-08-05 Georg Kastelewicz Method for registering a communication terminal

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100452715C (zh) * 2002-10-01 2009-01-14 华为技术有限公司 一种智能终端管理方法
CN1225864C (zh) * 2002-11-01 2005-11-02 华为技术有限公司 一种网络综合接入设备的安全管理方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002082731A1 (fr) * 2001-04-03 2002-10-17 Nokia Corporation Enregistrement d'un utilisateur dans un reseau de telecommunication
US20030159067A1 (en) * 2002-02-21 2003-08-21 Nokia Corporation Method and apparatus for granting access by a portable phone to multimedia services
WO2003081431A1 (fr) * 2002-03-22 2003-10-02 Nokia Corporation Identite provisoire pour l'authentification avec un protocole de lancement de session
US20040153667A1 (en) * 2002-05-22 2004-08-05 Georg Kastelewicz Method for registering a communication terminal

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8935374B2 (en) 2008-08-15 2015-01-13 Zte Corporation Method, system, and device for realizing registration mechanism of IP multimedia subsystem
CN111092949A (zh) * 2019-12-20 2020-05-01 北京百度网讯科技有限公司 用于注册设备的方法及装置
CN111092949B (zh) * 2019-12-20 2022-05-03 北京百度网讯科技有限公司 用于注册设备的方法及装置

Also Published As

Publication number Publication date
CN1838610A (zh) 2006-09-27
CN100362807C (zh) 2008-01-16

Similar Documents

Publication Publication Date Title
WO2006099815A1 (fr) Procede d'enregistrement d'un utilisateur dans le sous-systeme multimedia ip et systeme associe
US9906566B2 (en) Voice session termination for messaging clients in IMS
JP4700105B2 (ja) Ｉｐマルチメディアサブシステム（ｉｍｓ）おける呼転送
US9031067B2 (en) Routing messages
JP4493104B2 (ja) ホーム加入者サーバのインターフェイス負荷を軽減する方法
EP1758323B1 (fr) Procede destine a un terminal d'identification de commande de routage d'interaction de capacite pendant que ims et cs sont co-instantanes
KR101332891B1 (ko) 멀티미디어 서브시스템 서비스로의 그룹 액세스
EP2192742B1 (fr) Contrôleur de session locale, sous-système multimédia ip et procédé d'enregistrement de session
CN100563235C (zh) 互通功能网元、csi终端与ims终端互通系统及其方法
WO2007036123A1 (fr) Procede et systeme de communication pour un utilisateur du domaine cs accedant au domaine ims
WO2006136106A1 (fr) Procede et systeme d'authentification de terminal d'usager
US8661097B2 (en) Service node, control method thereof, user node, and control method thereof
WO2006010312A1 (fr) Procede d'information de la modification de capacite au terminal au reseau
JP2010506467A (ja) 通信ネットワークにおけるアクセス情報の提供
WO2006136097A1 (fr) Procédé pour traiter une anomalie lors de la procédure d'inscription d'un utilisateur
WO2007079673A1 (fr) Procede de detection de l'identite d'usager public dans le profil de service d'un systeme de communication et appareil associe
KR20060113284A (ko) 이종망간에 음성 서비스를 지원하는 아이엠에스 시스템 및그에 따른 호 설정 방법
US8345596B2 (en) Call control method for seamless mobility service
US9692835B2 (en) Method and apparatuses for the provision of network services offered through a set of servers in an IMS network
KR101360151B1 (ko) Ｇｒｕｕ 사용 가입자 간의 ｉｍｓ망에서의 ｓｉｐ 메시지 전송 방법 및 그 장치
WO2007104191A1 (fr) Procédé de clôture de session d'adresses ip
WO2011134157A1 (fr) Procédé, équipement et système pour l'inscription d'un élément de réseau personnel
WO2007082493A1 (fr) Procédé et entité de réseau pour le traitement du contenu de message de protocole d'ouverture de session
WO2006032204A1 (fr) Procede pour permettre une communication dans les serveurs d’application
KR20100060422A (ko) 메시지 라우팅 제어 방법 및 시스템

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: DE

NENP Non-entry into the national phase

Ref country code: RU

WWW Wipo information: withdrawn in national office

Country of ref document: RU

122 Ep: pct application non-entry in european phase

Ref document number: 06722154

Country of ref document: EP

Kind code of ref document: A1

WWW Wipo information: withdrawn in national office

Ref document number: 6722154

Country of ref document: EP