WO2006099815A1 - A method for implementing the user registering in the ip multimedia subsystem and the system thereof - Google Patents

Abstract

A method for implementing the user registering in the ISM includes that the user sends register request including the register information to the IMS register function entity when it initiates the register process to the IMS, the register information comprises the user equipment information, the method further includes the steps of : A, the IMS register function entity performs step B when the user which requests the register currently has the same user identifier and the different physics connection address with the registered user, B, the user equipment used by the user which requests the register currently and the user equipment used by the registered user are determined whether they are same according to the user equipment information, if they are same , then stores the current register information and logoffs the register information corresponding to the registered same user identifier; otherwise, stores the current register information and reserves the register information corresponding to the registered same user identifier. And a system can register the different user equipment with the same user identifier.

Description

 Method and system for realizing user registration in internet protocol multimedia subsystem

 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. Background of the invention

 With the development of broadband networks, mobile communication will not only be limited to traditional voice communication, multimedia services combining multiple media types such as audio, video, pictures and text will gradually develop, through and presence services, short messages. Business, web page (WEB) The combination of data services such as browsing service, positioning service, push (PUSH) service, and file sharing service can meet the various needs of users. For example: instant messaging in messaging services, chat rooms, multimedia short messages, entertainment in video services, multimedia information, daily communication, product catalogs in e-commerce, search engines, shopping carts, order management, payments, gaming services Single-player, group games, location-finding, wizards, alarms, address books in the personal assistant business, calendars, bookmark management, file storage, event reminders, emails, and more.

 Driven by a variety of applications, 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.

Figure 1 shows a schematic diagram of the IMS architecture. As shown in Figure 1, in the R5 (Release 5) phase of 3GPP, an IP Multimedia Subsystem domain, referred to as IMS, is introduced. The IMS is superimposed on the packet switching network by the Call Session Control Function (CSCF). Media Gateway Control Function (MGCF, Media Gateway Control Function) Media Resource Function (MRF, Multimedia Resource Function) and Home Subscriber Server (HSS, Home Subscriber Server) and other functional entities. Among them, CSCF can be divided into three logical entities: service CSCF (S-CSCF), proxy CSCF (P-CSCF) and query CSCF (I-CSCF) according to different functions implemented. S-CSCF is the service switching center of IMS. For performing session control, maintaining session state, managing user information, generating charging information, and the like; 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). The user-assigned server (HSS) is a user information database, which stores subscription data and configuration information of users in the IMS network.

 Since the structure of the IMS is independent of the underlying bearer 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). Next-generation network (NGN), etc., achieves independence from user terminal types and independence from access network types. Here, 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.

In IMS, a Session Initiation Protocol (SIP) is usually used as a signaling control protocol for an IP multimedia session. SIP is an IP telephony signaling protocol proposed by the Internet Engineering Task Force (IETF). As implied by its name, 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.

 The protocol mechanisms provided by SIP above include:

 1. Name translation and user location, ensuring that the call arrives wherever the called party is, performing any mapping of the description information to the location information, ensuring that the details of the call or session are supported;

 2. 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;

 3. Call participant management. During the call, participants can introduce other users to join the call, or cancel the connection of other users. In addition, the user can be transferred or placed as a call hold;

4. 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 (IMPI), 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. Generally, 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.

 In an IMS network using SIP as a signaling control protocol, 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. At the same time, according to the current location of the IMS user, 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.

In order to be able to complete the call, 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. When an IMS user moves from one IMS network to another, the old physical contact address needs to be deleted through the logout process, and the new physical contact address is notified to the current IMS network through the new registration process. 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.

 According to the provisions of the existing specifications, 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. At the same time, the S-CSCF stores related registration information such as a new physical contact address.

As can be seen from the above description, in order to avoid repeated registrations that may occur when an IMS user moves to a new IMS network, 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.

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. For example: 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. However, as mentioned above, 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. In this way, when other IMS users request to establish a session with the public user identity, the physical contact address of the first related device at the time of one registration cannot receive the request of other IMS users. That is to say: different physical contact addresses corresponding to the same private user identifier and the same public user identifier cannot be used to receive information of the IMS network at the same time, so that the user uses the same private user identifier and the same public user identifier at the same time, and has different The requirements for multiple devices with physical contact addresses cannot be met. SUMMARY OF THE INVENTION In view of this, 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. When the user initiates the registration process to the 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:

 A. 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. When performing step B;

 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.

 In the 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.

In 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:

 1) judging whether the access network information in the user equipment information currently requested to be registered is the same as the access network information in the determined registered user information, if the same, performing step 2); otherwise, the judgment result is Not the same, ending the current judgment;

 2) judging whether the user equipment identifier in the user equipment information currently requested to be registered is the same as the user equipment identifier in the determined registered user equipment, and if the same, the judgment result is the same; otherwise, the judgment result is different. .

 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. When the user equipment identifier includes the user equipment identifier type and the 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 MAC address saved on the user equipment; when the user equipment identifier type is the mobile device identifier MEID, the user equipment identifier is the MEID value saved in the user equipment; when the user equipment identifier type is empty or the user equipment identifier is only When the user equipment identifier is included, the user equipment identifier is a globally unique identifier UUID or is empty.

 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;

 After the IMS registration function entity saves the currently registered registration information, 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;

 When the user equipment requests to use the IMS service, 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.

 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.

 According to the method of the present invention, when 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. In addition, 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. BRIEF DESCRIPTION OF THE DRAWINGS

 Figure 1 shows a schematic diagram of an IMS architecture;

 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. A schematic diagram of the composition of the preferred embodiment. Mode for carrying out the invention

 The present invention will be further described in detail below with reference to the accompanying drawings.

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:

 In the existing user registration process, the registration information carried in the registration request includes at least a user identifier and a physical contact address, and 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. . When the user initiates the registration process to the IMS, 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; When 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. 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 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. When the user identifier is the same, 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.

In addition, 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. 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.

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.

^ Interest.

 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.

If 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. At this time, 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.

 If the user equipment can support multiple access modes at the same time, that is, the user equipment is a multi-mode terminal, the user equipment cannot be distinguished only by the access network information. Therefore, the additional registration information may be a user equipment that can uniquely identify the user equipment. Logo. In this way, 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. At this time, 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.

In addition, consider backward compatibility, that is, consider that a part of the user equipment in the IMS network can send the user equipment identity to the IMS network, and another part of the user equipment cannot send the user equipment identity to the IMS network, 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. Considering that the user equipment identification and naming may be different in different access networks, 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. 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. The user equipment identifier of the user equipment accessed by cdma2000 is the Mobile Equipment Identifier (MEID); and 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.

 The present invention also proposes another preferred embodiment based on the method of determining whether the current registration process is initiated by a different user device using the same user identity as described in the previous paragraph. Figure 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.

 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.

 In order to implement the foregoing embodiment, 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. information. 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. As shown in the following message format:

 Access Network Information = Access-Network-Info": Access Network Specification

 Access Network Specification = Access Type * (SEMI Access Information)

Access Type = "IEEE-802.11a" / ^M IEEE-802.11b" / "3GPP-GERAN" I

 "3GPP-UTRAN-FDD" / "3GPP-UTRAN-TDD" /

 "3GPP-CDMA2000" / token

 Device ID = "device-identifier" (referenced string)

 Access information = 3GPP cell global identity / 3GPP UMTS access network cell identity / extended access information

Where 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:

 P-Access-Network-Info="P-Access-Network-Info" HCOLON

 Access-net-spec

 Access-net-spec=access-type * ( SEMI access-info )

 Access-type="IEEE-802.11a" / "IEEE-802.11b" I "3GPP-GERAN" I

 "3GPP-UTRAN-FDD" I "3GPP-UTRAN-TDD" /

 "3GPP-CDMA2000" I token

 Device identifier= " device-identifier" EQUAL ( quoted-string )

 Access-info=cgi-3gpp I utran-cell-id-3gpp I

 Extension-access-info

 Among them, cgi-3gpp="cgi-3gpp" EQUAL ( token I quoted-string ) , utran-cell-id-3gpp="utran-cell-id-3gpp" EQUAL ( token I quoted-string ), 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.

Since user equipment identification is very important to users and operators, To ensure the security of the user equipment identity, the security mechanism of the IMS network can ensure this. In a specific application, 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.

 The methods for carrying user equipment identifiers through SIP messages are as follows: 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.

 Here, 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. Of course, 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.

After the value of the user equipment identification type is determined, 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). IMEI value; if user equipment The identifier type is the MAC address, and the user equipment identifier is the MAC address stored in the user equipment corresponding to the SIP UA; if the user equipment identifier type is the MEID, the user equipment identifier is the MEID value saved in the user equipment corresponding to the SIP UA; If the user equipment identifier type is empty or the user equipment identifier includes only the user equipment identifier (ie, no user equipment identification type), the user equipment identifier may be a Universally Unique IDentifier (UUID) or .

 The above-mentioned user equipment identification type and user equipment identifier have various manifestations in the Contact header field. Here are a few specific examples to illustrate:

 Example 1. The message format of the user equipment identification type and the user equipment identifier in the Contact header field is as follows:

 Contact: <sip:user@example.com>;audio;video;mobility="mobile";

+message= ^M TRUE";device_id="IMEr';imei="350112408932969";methods="INVITE,OPTIONS,BYE,CANCEL,ACK^M;schemes=

"sip,http"

 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.

 The above message format can be converted into the following assertions:

 (;& (audio=TRUE)

 (video=TRUE)

 (sip.mobility=mobile)

 (message=TRUE)

 (I (sip.identifier=IMEI) (sip.identifier.imei=350112408932969)) (I (sip.methods=INVITE) sip.methods=OPTIONS)(sip.methods=

BYE)(sip.methods=CANCEL)(sip.methods=ACK)) (I (sip.schemes=sip) (sip .schemes=http)))

 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:

 Contact: <sip:user@example.com>;audio;video;mobility="mobile";

+message="TRUE";device_id= ^,, IMEI:350112408932969";

Methods= ^M INVITE,OPTIONS,BYE,CANCEL,ACK ^M ;schemes=

"sip,http"

 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. The user device identifier here can have its own independent naming convention, or it can use the existing naming convention.

Example 3: The message format for setting only the user equipment identifier in the Contact header field is: Contact: <sip:user@example.com>;audio;video;mobility="mobile ^M ;

+message="TRUE";device_id="00-20-ed-aa-49-e8";methods="INVITE,OPTIONS,BYE,CANCEL ₃ ACK";schemes= "sip,http"

 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:

Contact: <sip :user@example. com>; audio; video; mobility = "mobile "; +message= "TRUE";device_id= "03";

Methods="INVITE,OPTIONS ₅ BYE,CANCEL,ACK ^M ;schemes=

"sip,http"

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. Because the string is filled in here, and the two indexes can represent 100 different values from 0 to 99, this example can distinguish 100 different user devices under the same IMPU. The combination of IMPU and index values can uniquely identify multiple terminals owned by one user and share the same IMPU. Moreover, after the user equipment identifier is set in the Contact header field, 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:

 Device_id=" <urn:uuid:f81d4fae-7dec-lld0-a765-00a0c91e6bf6>" Of course, 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. In the first method, 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. Thus, 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. Here, in the request 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. Here, 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.

 Call-Info: <urn:imei:350112408932969>; purpose=di

 Where di is the new purpose, the user equipment identification type is: IMEI, and 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 message format is as follows: Call-Info: <urn:imei:350112408932969>; purpose=info

 Where info is the existing purpose, the user device identification type is: IMEI, and 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:

 Call-Info: <urn:00-20-ed-aa-49-e8>;purpose=di

 Where di is the new purpose, and 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 message format is: Call-Info: <urn: sip:user@example.com:03>;purpose=di

 Where di is the new purpose, the user equipment identifier is sip:user@example.com:03, and 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 above various message formats represent only one possible expression, which is merely an example given by the present invention, and is not intended to limit the scope of the present invention, and other expressions may achieve the same purpose.

In addition, since 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. In addition, considering that with the development of technology, multiple access technologies will coexist, and future user equipment will also move toward multi-mode To evolve, a user equipment can use different access methods to access the IMS network in different access networks. For the maintenance and management needs of operators, it is also very useful to uniquely identify the user equipment within a certain range. of. Therefore, based on the user registration process of the present invention, 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.

 For example, 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. When the IMS user uses the service, 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. Various businesses. In this way, when the user equipment is lost, the user can access the IMS network, and 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. In this way, 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. Further, 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.

Therefore, in the present invention, 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. For example: 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. It is judged that this is a registration process initiated by the user equipment of the original handheld computer. At this time, 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. However, 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. During the new registration process, 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.

Based on the above method of the present invention, 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. If they are the same, the registration information carried in the current registration request is stored and the registered same user identifier is deleted. Registration information; 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. 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.

 As shown in FIG. 4, 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. And determining, according to the user equipment information in the current registration information, whether the user equipment currently used by the user to be registered is the same as the user equipment used by the registered user, and if the same, storing the registration information carried in the current registration request and canceling the registered registration The registration information corresponding to the same user identifier; otherwise, storing the registration information carried in the current registration request and retaining the registration information corresponding to the registered same user identifier.

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. In this way, 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.

 In summary, 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.

 The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the present invention. Within the scope of protection.

Claims

Claim

 A method for realizing user registration in the IMS multimedia subsystem IMS. When the user initiates the registration process with the 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 connection. The address information is characterized in that: the registration information further includes user equipment information for identifying a user equipment currently used by the user, and the method includes:

 A. The IMS registration function entity determines, by 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 ID and different physical contact address as the registered user. When performing step B;

 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 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 according to claim 1, wherein in step A, the method for determining that the currently requested user and the registered user have the same user identifier and different physical contact addresses is:

 Determining, when the user identifier currently registered for registration is the same as any one of the registered registration information, the registered physical contact address corresponding to the same user identifier in the registered registration information; when the determined registered physical entity is determined; When the contact address is different from the physical contact address currently requested to be registered, it is determined that the currently oddly registered user has the same user ID and different physical contact address as the registered user.

The method according to claim 2, wherein, in 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 user equipment used by the registered user The same method is: Determining the registered user equipment information corresponding to the registered physical contact address determined in step A in the registered registration information, determining whether the currently requested user equipment information is the same as the determined registered user equipment information, if the same Then, it is determined that the user equipment currently requested to be registered is the same as the user equipment used by the registered user; otherwise, it is determined that the user equipment currently used by the user requesting registration is different from the user equipment used by the registered user.

 The method according to claim 3, wherein the user equipment information includes access network information and user equipment identifier, and step B determines the user equipment information currently requested to be registered and the determined registered user. The method of whether device information is the same is:

 1) judging whether the access network information in the currently requested user setting information is the same as the access network information in the determined registered user equipment information, if the same, performing step 2); otherwise, the judgment result is Not the same, ending the current judgment;

 2) It is judged whether the user equipment identifier in the user equipment information currently requested to be registered is the same as the user equipment identifier in the determined registered user equipment information, and if they are the same, the judgment result is the same; otherwise, the judgment result is different.

 The method according to claim 1, wherein the registration information carried by the registration request further includes user equipment information by: using a new information domain or an original information domain in the registration request to carry the location User equipment information.

 The method according to claim 5, wherein 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 as follows: 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: expanding a call information Call-Info information field of a SIP message as a registration request, using the extension The subsequent Call-Info information field carries the user equipment information.

 The method according to claim 6, wherein the user equipment information comprises: access network information and/or user equipment identifier; the user equipment identifier comprises: a user equipment identifier, or a user equipment identifier type A combination with a user device identifier.

 The method according to claim 7, wherein when the user equipment identifier includes a user equipment identifier type and a user equipment identifier, the bearer user equipment information carries the user equipment in the user equipment information. The method of identification is:

 User equipment identification type and 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 method according to claim 7, wherein when the user equipment identification type is an international mobile subscription subscriber identity IMEI, the user equipment identifier is an IMEI value saved in the user equipment; The type is a media access control MAC, the user equipment identifier is a MAC address saved on the user equipment; when the user equipment identifier type is a mobile device identifier MEID, the user equipment identifier is a MEID value saved in the user equipment; When the user equipment identity type is empty or the user equipment identity includes only the user equipment identifier, the user equipment identifier is a globally unique identifier UUID or is empty.

 The method according to claim 1, wherein the method further comprises: setting a user equipment registration server, wherein the user equipment registration server is configured to save a correspondence between the user equipment information and its status;

After the IMS registration function entity saves the currently registered registration information, 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 The current state to the user equipment registration server, the user equipment registration server updates the corresponding user equipment information State

 When the user equipment requests to use the IMS service, 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 method according to any one of claims 1 to 10, wherein the IMS registration function entity is a serving call session control function S-CSCF in an IMS network.

 The method according to any one of claims 1 to 10, wherein the user setting information comprises: information of the calling user equipment and/or information of the called user equipment.

 13. A system for implementing user registration in an IMS, the system comprising: a user equipment and an IMS registration function entity, wherein:

 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.

 14. The system according to claim 13, wherein the IMS registration function entity comprises:

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, The registration information carried in the current registration request is stored and the registration information corresponding to the registered same user identifier is retained.

 15. The system of claim 13 wherein the system further comprises:

 a user equipment registration server, configured to receive a state of the user equipment from the outside, save a correspondence between each user equipment and its state, receive user equipment information in the registration information from the IMS registration function entity, and return the corresponding user equipment The status is registered with the IMS functional entity.

 The system according to any one of claims 13 to 15, wherein the IMS registration function entity is an S-CSCF in an IMS network.