WO2011140712A1 - Method and apparatus for implementing internet protocol multimedia sub-system sharing public user identity service for non- internet protocol multimedia sub-system terminal - Google Patents

Abstract

A method and apparatus for implementing sharing Internet protocol Multimedia Sub-system (IMS) public user identity for non-IMS terminal is introduced by the present invention. In the prior art, the non-IMS terminal can access IMS network and share one IMS public user identity with other terminals, but users can not distinguish the non-IMS terminal from other terminals which share the IMS public user identity. The present invention imports a proxy server and a mapping table. Said proxy server transforms a request from the non-IMS terminal to a signaling in IMS network, wherein, by inquiring the mapping table, the identity of the non-IMS terminal is transformed to a unique identity in IMS network (for example Globally Routable User Agent URI (GRUU)). When receiving the request message from IMS network, the proxy server transforms the identity in IMS network correlative to the called party in the request message to a unique identity of the non-IMS terminal by inquiring the mapping table, and thus sends a request to the non-IMS terminal corresponding to the identity of the non-IMS terminal.

Description

 One for non-IMS terminals to implement IMS shared public users

 Method and device for identifying service

 The present invention relates to a communication network, and more particularly to a method and apparatus for implementing an IMS shared public subscriber identity service for a non-IMS terminal in an IMS network. Background technique

 In the leg (IP Multimedia Subsystem, IP Multimedia Subsystem) system,

There are two types of IMS user IDs: Private User Identity and Public User Identity. The private user identity is assigned by the home i-network operator for user registration, authentication, authorization, and accounting, and a terminal device is indicated. Private user IDs are usually not disclosed to third parties, similar to the IMSI (International Mobile Subscriber Identity) number in the GSM (Global System for Mobile communications) network. The public user ID is the user ID in the session, used to initiate a session or be called by another user, which is equivalent to the phone number, email address, etc. in our life. A private user ID can have multiple public user IDs, and multiple private user IDs can also share a common user ID.

 The IMS network provides a large number of flexible and convenient services for IMS users, and sharing a common user identity is one of them. A common public identity service is shared, that is, multiple user terminals can share a common user identity. For example, user Bob has three IMS terminals, namely, a mobile phone, an office phone, and a home phone. The three IMS terminals can share a common user ID X, so that no matter where Bob is, which terminal is used, other users only Bob needs to be found by calling the public user ID X. In addition, the shared public user identification service is also widely used in hotlines and emergency calls, such as customer service telephone systems, 110 telephone systems, and the like.

However, for non-IMS terminals, the above IMS shared public use is not available. The convenience of the household identification service. The non-IMS terminal referred to herein refers to a terminal that cannot access the IMS network through itself, that is, the terminal cannot support the necessary processes defined in the IMS standard, such as a registration process, a call origination process, a call termination process, and the like. The PSTN (Public Switched Telephone Network) telephone and the UMTS (Universal Mobile Telecommunications System) telephone in the traditional network belong to the non-IMS terminal.

 In order to solve the problem that the non-IMS terminal accesses the IMS network, the MG system introduces 7 MGCF (Media Gateway Controller Function), see the relevant provisions of 3GPP TS23.002. Through the MGCF, the non-IMS terminal can access the IMS network and can make a call with the IMS terminal. However, the non-IMS terminal cannot register to the IMS network, that is, the IMS public user identity cannot be allocated, and the non-IMS terminal still cannot enjoy the IMS sharing. Public user identification service.

 A method of accessing a non-IMS terminal to an IMS network is described in U.S. Patent Application No. 20070195805, such that a non-IMS terminal can register with the IMS network and assign a default public user identity. A method for implementing an IMS multi-public subscriber identity service for a non-IMS terminal is disclosed in Chinese Patent Application No. 201010003176.4, such that a non-IMS terminal can register with the IMS network and assign one or more IMS public user identifiers. These two methods make it possible for non-IMS terminals and other terminals to share one IMS public user identity, but they cannot distinguish non-IMS terminals sharing one IMS public user identity from other terminals, which is often required in practice. For example, in the above example, the called user who establishes a call with Bob may wish to know which terminal the Bob uses to initiate the call, or the calling party who establishes the call with Bob wants the read call to be sent to a designated terminal. The prior art cannot achieve the above functions. Summary of the invention

 In order to solve the above-mentioned drawbacks in the prior art, the present invention proposes a method and apparatus for accessing a non-IMS terminal to an IMS network.

According to a first aspect of the present invention, there is provided a method for accessing a non-IMS terminal to an IMS network in a server, the non-IMS terminal and one or more other The terminal shares an IMS public user identifier, where the method includes: receiving a request message from the non-IMS terminal; extracting an identifier of the non-IMS terminal in the request message; and querying the mapping table, 4 determining according to the identifier of the non-IMS terminal An identifier in the IMS network that uniquely identifies the non-IMS terminal; sends a request message to the IMS call control unit, wherein the identifier in the IMS network that uniquely identifies the non-IMS terminal is included.

 Preferably, the method further comprises: receiving a registration request message from the non-IMS terminal; extracting an identity of the non-IMS terminal in the registration request message; assigning a unique identifier to the non-IMS terminal; sending to the IMS call control unit a registration request message, including the unique identifier and an IMS public user identifier corresponding to the non-IMS terminal; receiving a reply message from the IMS call control unit, where the IMS network uniquely identifies the non-IMS terminal And identifying, in the mapping table, the identifier of the non-IMS terminal and the identifier in the IMS network of the non-IMS terminal that is uniquely marked.

 Preferably, the mapping table is preset.

 According to a second aspect of the present invention, there is provided an apparatus for accessing a non-IMS terminal to an IMS network in a server, the non-IMS terminal and one or more other terminals sharing an IMS public subscriber identity, wherein The device includes: a first receiving device, configured to receive a request message from a non-IMS terminal; a first extracting device, configured to extract an identifier of the non-IMS terminal in the non-IMS network in the request message; And determining, by the non-IMS terminal, an identifier in the IMS network of the non-IMS terminal according to the identifier of the non-IMS terminal in the non-IMS network; the first sending device, configured to send the request message to the IMS call control unit And including the identifier in the IMS network that uniquely identifies the non-IMS terminal.

Preferably, the first receiving device is further configured to receive a registration request message from the non-IMS terminal; the first extracting device is further configured to extract an identifier of the non-IMS terminal in the registration request message; a first allocation device, configured to allocate a unique identifier to the non-IMS terminal; the first sending device is further configured to send a registration request message to the IMS call control unit, where the unique identifier and the non- An IMS public user identifier corresponding to the IMS terminal; the first receiving device is further configured to receive a reply message from the IMS call control unit, including an identifier in the IMS network that uniquely identifies the non-IMS terminal; the apparatus further comprising first recording means for identifying the unique and non-IMS terminal The identity in the IMS network that marks the non-IMS terminal is recorded in a mapping table.

 Preferably, the mapping table is preset.

 According to a third aspect of the present invention, there is provided a method for accessing a non-IMS terminal to an IMS network in a server, the non-IMS terminal and one or more other terminals sharing an IMS public subscriber identity, wherein The method includes: receiving a request message from an IMS call control unit; extracting an identifier in the IMS network related to the called party in the request message; querying a mapping table, and determining a unique non-IMS according to the identifier in the IMS network Identifying the non-IMS terminal according to the identifier of the non-IMS terminal; sending a request message to the non-IMS terminal, where the identifier of the non-IMS terminal is included.

 Preferably, the reading method further comprises: receiving a registration request message from the non-IMS terminal; advancing the identification of the non-IMS terminal in the registration request message; assigning the non-IMS terminal a unique identifier; sending to the IMS call control unit And a registration request message, where the unique identifier and the IMS public user identifier corresponding to the non-IMS terminal are included; receiving a reply message from the IMS call control unit, where the IMS network that uniquely identifies the non-IMS terminal is included And the identifier of the non-IMS terminal and the identifier in the IMS network of the non-IMS terminal that are uniquely marked in the mapping table.

 Preferably, the ejaculation table is preset.

According to a fourth aspect of the present invention, there is provided an apparatus for accessing a non-IMS terminal to an IMS network in a server, the non-IMS terminal and one or more other terminals sharing an IMS public subscriber identity, wherein The device includes: a second receiving device, configured to receive a request message from the IMS call control unit; a second extracting device, configured to extract an identifier in the IMS network related to the called party in the request message; And determining, by the query mapping table, an identifier of a unique non-IMS terminal according to the identifier in the IMS network; and determining, by the terminal, the identifier according to the non-IMS terminal The second sending device is configured to send a request message to the non-IMS terminal, where the identifier of the non-IMS terminal is included.

 Preferably, the second receiving device is further configured to receive a registration request message from the non-IMS terminal; the second extracting device is further configured to extract an identifier of the non-IMS terminal in the registration request message; a second allocation device, configured to allocate a unique identifier to the non-IMS terminal; the second sending device is further configured to send a registration request message to the IMS call control unit, where the unique identifier and the non- The IMS public user identifier corresponding to the IMS terminal; the second receiving device is further configured to receive a reply message from the IMS call control unit, where the identifier in the IMS network that uniquely identifies the non-IMS terminal is included; And a second recording device, configured to record the identifier of the non-IMS terminal and the identifier in the IMS network of the non-IMS terminal that is uniquely marked in the mapping table.

 Preferably, the mapping table is preset.

 By using the method and apparatus of the present invention, a non-IMS terminal that shares an IMS public subscriber identity with one or more other terminals can be distinguished, and when it acts as a calling party, the called subscriber can know that the call is shared by the IMS public subscriber. Which non-IMS terminal is identified, and when called, the call can specify a particular non-IMS terminal to be sent to the shared IMS public user identity. At the same time, when the user selects a certain configuration, the privacy of the user can be protected to some extent. DRAWINGS

 Other features, objects, and advantages of the present invention will become apparent from the Detailed Description of Description

 1 is a schematic diagram of a process of accessing a non-IMS terminal to an IMS network according to an embodiment of the present invention;

 2 is a schematic diagram of a process of accessing a non-IMS terminal to an IMS network according to an embodiment of the present invention;

3 is a schematic diagram of a process of accessing a non-IMS terminal to an IMS network according to an embodiment of the present invention; 4 is a structural block diagram of an apparatus for accessing a non-IMS terminal to an IMS network in a server according to an embodiment of the present invention;

 Figure 5 is a block diagram showing the structure of an apparatus for accessing a non-IMS terminal to an IMS network in a server in accordance with an embodiment of the present invention. detailed description

 In the IMS network, in order to distinguish between multiple terminals sharing a common user identity, the concept of GRUU (Globally Routable User Agent URI (User Resource Identifier), globally routable user agent uniform resource identifier) is introduced. The relevant provisions are given in 3GPP TS 23.228 version 8.

 The GRUU is used to uniquely identify a combination of a public user identifier and a specific terminal, so that the terminal can send a SIP (Session Initial Protocol) message to a specific terminal corresponding to a public user identifier instead of sending it to the specific terminal. Public user ID, which ensures that SIP messages will not be sent to other registered terminals corresponding to this public user ID. There are two types of GRUU: public GRUU (Public GRUU) and temporary GRUU (Temporary GRUU). The public GRUU contains the user's public user ID and is valid for a long time. The URI in the temporary GRUU does not disclose the user's public user identity and is only valid before the user cancels the registration or the validity period of the registration. Since it does not disclose the user's public user identity, the temporary GRUU can well contain the user's privacy. For example, a public user ID is alice@example.com, and its corresponding public GRUU may be alice@example.com; gr=kjh29x97us97d; its corresponding temporary GRUU may be asd887f d kk76690@example.com;gr. A public GRUU and a temporary GRUU corresponding to a certain public user identity are assigned to the terminal together with the terminal when it is registered and re-registered. Each pair of public GRUUs and temporary GRUUs correspond to a common user identity and a specific terminal. At subsequent re-registration, the terminal is assigned to the same public GRUU and a new, different temporary GRUU.

It is precisely because the IMS network introduces the GRUU mechanism that multiple IMS terminals sharing a certain public user identity can be distinguished, the call can be initiated or terminated based on the GRUU, and the privacy of the user can be protected. Not the IMS terminal, although it can pass the existing technology. The IMS network is accessed and registered with the IMS public user identity, but it does not support the GRUU mechanism, so that non-IMS terminals sharing an IMS public user identity cannot be distinguished from other terminals. In order to solve the problems in the prior art, the basic idea of the present invention is to introduce a GRUU mechanism for a non-IMS terminal sharing an IMS public user identity, so that the non-IMS terminal can enjoy the same convenience as the IMS terminal.

 To this end, the present invention introduces a proxy server located between a non-IMS terminal and an IMS network, which is capable of converting the identity of a non-IMS terminal in a non-IMS network into an identity in a unique IMS network (such as a public GRUU or temporary GRUU) can also convert the identity in the IMS network into a unique non-IMS terminal identity. At the same time, the proxy server can process the signaling of the network where the non-IMS terminal is located and the signaling in the IMS network, and can convert between the two types of signaling. The proxy server can be a separate entity or existing in an existing network element, such as the MGCF.

 In addition, the present invention also needs to introduce a mapping table, which stores the correspondence between the identifier of the non-IMS terminal in the non-IMS network and its unique identifier in the IMS network, and may include the non-IMS terminal identifier and its corresponding IMS public. User ID, instance ID, its corresponding GRUU collection, and so on. Taking the PSTN terminal as an example, the form of the mapping table may be as shown in Table 1, but is not limited to the form of Table 1. In Table 1, the PSTN terminal A is identified as 58541240 in the PSTN network, and the PSTN terminal B is identified as 58541241. Terminal A and Terminal B can access the IMS network and share an IMS public user identity alice@example.com. The value 0 in the GRUU set corresponds to the public GRUU, and the value 1 corresponds to the temporary GRUU. The system can predefine which GRUU to use as the default GRUU.

The mapping table may exist in a separate database or may be stored in an existing data storage device, such as an HLR (Home Location Register), an HSS (Home Subscriber Server, a Home Subscriber Server), and the like. The mapping table may be preset by the system, or may be generated after the non-IMS terminal registers with the IMS network. If the mapping table is pre-set, then the value of GRUU must be guaranteed to be unique. PSTN final IMS public GRUU collection

 End identifier user ID

 585412 alice@exa {0- alice@example.com;gr=kjh29x97us97d; 40 mple.com 1- asd887f9dfkk76690(3⁄4example.com;gr}

585412 alice@exa {0- alice@example.com;gr=kjh28x97us97d; 41 mple.com 1- asd887f9dfkk76691 (3⁄4example.com;gr} Table 1 On non-IMS terminals, a new user interface needs to be defined to complete the pair Operation of the IMS network. The definition of the new interface varies according to the type of non-IMS terminal and the type of network it is in. For PSTN terminals or UMTS terminals, the IMS network can be completed by defining a new service type code. Operation, such as:

 The button "*54" indicates that the default IMS public user ID corresponding to the PSTN terminal is registered and supports the GRUU; "*54*i," indicates that the i-th IMS public user ID corresponding to the PSTN terminal is registered and supports the GRUU;

 The button "*55*called number" indicates that the called party corresponding to the called number is called by the default GRUU in the IMS network corresponding to the PSTN terminal, and "*55*1*called number" indicates that the PSTN terminal corresponds to The public GRUU in the IMS network calls the called party corresponding to the called number, and the "*55*2*called number" indicates that the called party number corresponding to the called party is called by the temporary GRUU in the IMS network corresponding to the PSTN terminal. call.

FIG. 1 exemplarily shows a process diagram of accessing a non-IMS terminal to an IMS network according to an embodiment of the present invention. In the figure, the non-IMS terminal is the PSTN terminal A, and the above proxy server is located in the MGCF. The PSTN terminal A shares one IMS public user identity with one or more other terminals. ISST (ISDN User Part) signaling is used between the PSTN terminal A and the MGCF, and the SIP message is used between the MGCF and the P-CSCF (Proxy - Call Session Control Function) in the IMS network. make. In step 1, the PSTN terminal is directed to The MGCF initiates a registration request, requesting to register with the IMS network with an IMS public user identity. It should be noted that this step may employ any method of registering a non-IMS terminal to the IMS network in the prior art. In the present invention, the method described in Chinese Patent Application 201010003176.4 is employed. The user registers *54*1 on the PSTN terminal A to indicate that it is registered to the IMS network with the first IMS public user identity, and the IMS public user identity is also shared by other terminals. The PSTN terminal A sends a registration request message to the MGCF, such as an IAM (Initial Address Message) message in the figure. At this time, the value of the GRUU corresponding to the PSTN terminal A in the mapping table is null. When the proxy server in the MGCF receives the above registration request message, it will perform the following steps:

 - Authenticate the PSTN terminal to determine if it has the right to use the shared IMS public user identity service, however, it must be noted that the authentication process is not required;

 - Extract the identifier of the PSTN terminal A in the IAM message 58541240;

 - Assign a unique instance identifier to PSTN Terminal A, such as ID 1;

 - sending a registration request message Register to the P-CSCF, which includes the IMS public user identifier corresponding to the PSTN terminal A and the above-mentioned assigned instance identifier, and also includes an indicator supporting the GRUU, which needs to be pointed out in the prior art. The MGCF has a protocol conversion function, which can convert an IAM message into a Register message, and the process will not be described here.

 After receiving the above Register message, the P-CSCF performs the same actions as in the standard 3GPP TS 23.228 version 8. The subsequent steps 3 to 12 in Fig. 1 are also the same as the above criteria, wherein the S-CSCF (Serving - Call Session Control Function), after receiving the above registration request, includes the IMS public The user identity, the instance identifier described above, and the indicator supporting the GRUU assign a unique public GRUU and a unique new temporary GRUU to the combination of the IMS public user identity and the instance identity.

In step 12, when the proxy server in the MGCF receives a registration reply message from the P-CSCF, such as the 200 OK in the figure, it will be included in the public in the reply message. The GRUU and the temporary GRUU are recorded in the record corresponding to the PSTN terminal A in the mapping table. At this point, the corresponding content in the mapping table is generated for subsequent operations.

 FIG. 2 exemplarily shows a process diagram of accessing a non-IMS terminal to an IMS network according to an embodiment of the present invention. In the figure, the non-IMS terminal is the PSTN terminal A, and the above proxy server is located in the MGCF. The user initiates a call to the IMS network by typing *55* 1 * the called number on the PSTN terminal A. When the proxy server in the MGCF receives the above IAM message, it performs the following steps:

 - Authenticate the PSTN terminal to determine if it has permission to use the GRUU service, however, it must be noted that the authentication process is not required;

 - Extract the identifier of the PSTN terminal A in the IAM message 58541240;

 - Query the mapping table shown in Table 1, find its corresponding GRUU set through index 58541240, and then determine a unique GRUU according to the index code in the IAM message. Here, index code 1 corresponds to the public GRUU. It should be noted that the index code is not required. If the index code is empty, the call is initiated by the default GRUU. The system can pre-define the default GRUIL.

 - Send an INVITE message to the P-CSCF, where the information of the calling part contains the GRUU obtained after the above query mapping table. It should be noted that in the prior art, the MGCF has a protocol conversion function, which can convert an IAM message into an INVITE message, and the process is not described here.

 The subsequent steps shown in Figure 2 are the same as those specified in subclause 5.6 of the standard 3GKP TS 23.228 version 8.6.0. Thus, when the called party receives the call, it can know that the call comes from the PSTN terminal A sharing the public subscriber identity, not only knowing that the call is from a certain public subscriber identity. If the user specifies to initiate a call with a temporary GRUU, the called user cannot know the public user identity of the calling party, which can well protect the privacy of the user.

FIG. 3 exemplarily shows a process diagram of accessing a non-IMS terminal to an IMS network according to an embodiment of the present invention. In the figure, the non-IMS terminal is the PSTN terminal A, and the above proxy server is located in the MGCF. When the proxy server in the MGCF receives the call request INVITE message from the IMS network, it will perform the following steps. The INVITE message is sent to a GRUU that shares the public user ID:

 - extracting the GRUU of the called part of the INVITE message;

 - Query the mapping table shown in Table 1, and obtain a unique PSTN terminal identification according to GRUU 58541240;

 - determine its corresponding PSTN terminal A according to the identifier 58541240;

 - Send an IAM message to PSTN Terminal A, which contains the identifier 58541240. Thus, when a user calls a GRUU that shares a common user identity, the call is sent to a particular non-IMS terminal, and the other terminals sharing the public user identity are not simultaneously called.

 4 is a block diagram exemplarily showing an apparatus for accessing a PSTN terminal A to an IMS network in a proxy server according to an embodiment of the present invention. The PSTN terminal A shares one IMS public user identity with one or more other terminals. The device 400 includes: a first receiving device 401 for receiving a request message from the PSTN terminal A, such as the IAM message in FIG. 1; a first extracting device 403 for extracting the PSTN terminal in the IAM request message Identification of A in the PSTN network; a first mapping means 404 for querying the mapping table and determining an identity in the IMS network uniquely marking the PSTN terminal, such as a public GRUU or temporary, based on the identity of the PSTN terminal A in the PSTN network The first sending device 402 is configured to send a request message, such as an INVITE message, to the IMS call control unit P-CSCF, where the public GRUU or temporary GRUU is included.

The mapping table may be preset or generated by registration. When the mapping table is obtained by registration, the first receiving device 401 is further configured to receive a registration request message, such as an IAM message, from the PSTN terminal A. The first extracting device 403 is further configured to extract the IAM message. The identifier of the PSTN terminal A; the device 400 further comprises a first allocation device 405 for assigning a unique identifier to the PSTN terminal A; the first transmitting device 402 is further configured to send to the IMS call control unit P-CSCF The registration request message, such as the Register message, includes the unique identifier and the IMS public user identifier corresponding to the PSTN terminal A. The first receiving device 401 is further configured to receive a reply message from the P-CSCF, such as 200. OK message, where An identifier in the IMS network that uniquely identifies the non-IMS terminal, such as a public GRUU and/or a temporary GRUU; the apparatus 400 further includes a first recording device 406 for identifying the PSTN terminal A and the The public GRUU and the temporary GRUU are recorded in a mapping table in the database 407.

 Figure 5 exemplarily shows a block diagram of an apparatus for accessing PSTN terminal A to an IMS network in a proxy server in accordance with an embodiment of the present invention. The PSTN terminal A shares one IMS public user identity with one or more other terminals. The device 500 includes: a second receiving device 501, configured to receive a request message from the IMS call control unit P-CSCF, such as an INVITE message; and a second extracting device 503, configured to extract the INVITE message and associated with the called party An identifier in the IMS network, such as a public GRUU or a temporary GRUU; a second mapping means 504 for querying the mapping table and determining an identity of a unique non-IMS terminal based on the public GRUU or the temporary GRUU; the terminal determining means 508, The identifier for the non-IMS terminal determines its corresponding PSTN terminal A; the second sending device 502 is configured to send a request message, such as an IAM message, to the PSTN terminal A, where the PSTN terminal A is included. Logo.

The mapping table may be preset or generated by registration. When the mapping table is obtained by registration, the second receiving device 501 is further configured to receive a registration request message, such as an IAM message, from the PSTN terminal A. The second extracting device 503 is further configured to extract the IAM message. The identifier of the PSTN terminal A; the apparatus 500 further includes a second allocation means 505 for assigning a unique identifier to the PSTN terminal A; the second transmitting means 502 is further configured to send to the IMS call control unit P-CSCF The registration request message, such as the Register message, includes the unique identifier and the IMS public user identifier corresponding to the PSTN terminal A. The second receiving device 501 is further configured to receive a reply message from the P-CSCF, such as 200. An OK message, which includes an identifier in the IMS network that uniquely identifies the non-IMS terminal, such as a public GRUU and/or a temporary GRUU; the apparatus 500 further includes a second recording device 506 for identifying the identity of the PSTN terminal A The public GRUU and the temporary GRUU are recorded in a mapping table in the database 507. The specific embodiments of the present invention have been described above. It is to be understood that the invention is not limited to the specific embodiments described above, and those skilled in the art can make various changes or modifications within the scope of the appended claims.

Claims

Claim A method for accessing a non-IMS terminal to an IMS network in a server, the non-IMS terminal and one or more other terminals sharing an IMS public user identity, the method comprising:  Receiving a request message from a non-IMS terminal;  Extracting an identifier of the non-IMS terminal in the request message;  Querying a mapping table, and determining, according to the identifier of the non-IMS terminal, an identifier in the IMS network that uniquely identifies the non-IMS terminal;  And transmitting a request message to the IMS call control unit, where the identifier in the IMS network of the non-IMS terminal is uniquely indicated.  2. The method according to claim 1, wherein the method further comprises:  Receiving a registration request message from a non-IMS terminal;  Extracting an identifier of the non-IMS terminal in the registration request message;  Assigning a unique identifier to the non-IMS terminal;  Sending a registration request message to the IMS call control unit, where the unique identifier and the IMS public user identifier corresponding to the non-IMS terminal are included;  Receiving a reply message from the IMS call control unit, which includes an identifier in the IMS network that uniquely identifies the non-IMS terminal;  The identifier of the non-IMS terminal and the identifier in the IMS network of the non-IMS terminal that uniquely identifies the non-IMS terminal are recorded in a mapping table.  3. The method according to claim 1, wherein the mapping table is pre-set.  The method according to any one of claims 1 to 3, wherein the identifier in the IMS network of the non-IMS terminal that is uniquely marked is a public global routable user agent uniform resource identifier (P-GRUU) Or Temporary Globally Scalable User Agent Uniform Resource Identifier (T-GRUU). 5. A device for accessing a non-IMS terminal to an IMS network in a server, The non-IMS terminal and the other one or more terminals share an IMS public user identifier, and the device includes:  a first receiving device, configured to receive a request message from a non-IMS terminal;  a first extracting device, configured to extract an identifier of the non-IMS terminal in the request message in the non-IMS network;  a first mapping device, configured to query a mapping table and determine, according to the identifier of the non-IMS terminal in the non-IMS network, an identifier in the IMS network that uniquely identifies the non-IMS terminal;  And a first sending device, configured to send a request message to the IMS call control unit, where the identifier in the IMS network that uniquely identifies the non-IMS terminal is included.  6. Apparatus according to claim 5 wherein:  The first receiving device is further configured to receive a registration request message from the non-IMS terminal; the first extracting device is further configured to extract an identifier of the non-IMS terminal in the registration request message;  The apparatus also includes first allocating means for assigning a unique identifier to the non-IMS terminal;  The first sending device is further configured to send a registration request message to the IMS call control unit, where the unique identifier and the IMS public user identifier corresponding to the non-IMS terminal are included;  The first receiving device is further configured to receive a reply message from the IMS call control unit, where the identifier in the IMS network that uniquely identifies the non-IMS terminal is included; the device further includes a first recording device, The identifier of the non-IMS terminal and the unique identifier in the IMS network of the non-IMS terminal are recorded in a mapping table.  7. Method according to claim 5, characterized in that the mapping table is pre-set. The method according to any one of claims 5-8, wherein the identifier in the IMS network of the unique identifier non-IMS terminal is a public global routable user agent uniform resource identifier (P-GRUU) Or temporary global routable user agent unified resource Identifier (T-GRUU).  A method for accessing a non-IMS terminal to an IMS network in a server, the non-IMS terminal and one or more other terminals sharing an IMS public user identity, the method comprising:  Receiving a request message from an IMS call control unit;  Extracting an identifier in the IMS network related to the called party in the request message;  Querying a mapping table, and determining an identifier of a unique non-IMS terminal according to the identifier in the IMS network;  Determining the corresponding non-IMS terminal according to the identifier of the non-IMS terminal; sending a request message to the non-IMS terminal, where the identifier of the non-IMS terminal is included.  10. The method of claim 9, wherein the method further comprises:  Receiving a registration request message from a non-IMS terminal;  The identifier of the non-IMS terminal in the registration request message in advance;  Assigning a unique identifier to the non-IMS terminal;  Sending a registration request message to the IMS call control unit, where the unique identifier and the IMS public user identifier corresponding to the non-IMS terminal are included;  Receiving a reply message from the IMS call control unit, which includes an identifier in the IMS network that uniquely identifies the non-IMS terminal;  The identifier of the non-IMS terminal and the identifier in the IMS network of the non-IMS terminal that uniquely identifies the non-IMS terminal are recorded in a mapping table.  11. The method of claim 9, wherein the radiance table is pre-set.  The method according to any one of claims 9-1, wherein the identifier in the IMS network is a public global routable user agent uniform resource identifier (P-GRUU) or temporary global routable User Agent Uniform Resource Identifier (T-GRUU). 13. A device for accessing a non-IMS terminal to an IMS network in a server, The non-IMS terminal and the other one or more terminals share an IMS public user identifier, and the device includes:  a second receiving device, configured to receive a request message from the IMS call control unit, where the second extracting device is configured to extract an identifier in the IMS network related to the called party in the request message;  a second mapping device, configured to query a mapping table and determine an identifier of a unique non-IMS terminal according to the identifier in the IMS network;  a terminal determining apparatus, configured to determine, according to the identifier of the non-IMS terminal, a corresponding non-IMS terminal;  And a second sending device, configured to send a request message to the non-IMS terminal, where the identifier of the non-IMS terminal is included.  14. Apparatus according to claim 13 wherein:  The second receiving device is further configured to receive a registration request message from the non-IMS terminal; the second extracting device is further configured to extract an identifier of the non-IMS terminal in the registration request message;  The apparatus also includes second assigning means for assigning a unique identifier to the non-IMS terminal;  The second sending device is further configured to send a registration request message to the IMS call control unit, where the unique identifier and the IMS public user identifier corresponding to the non-IMS terminal are included;  The second receiving device is further configured to receive a reply message from the IMS call control unit, where the identifier of the IMS network that uniquely identifies the non-IMS terminal is included; the device further includes a second recording device, The identifier of the non-IMS terminal and the unique identifier in the IMS network of the non-IMS terminal are recorded in a mapping table.  15. The apparatus according to claim 13, wherein the mapping table is preset. The apparatus according to any one of claims 13-15, wherein the identifier in the IMS network is a public global routable user agent uniform resource identifier (P-GRUU) or Temporary Globally Scalable User Agent Uniform Resource Identifier (T-GRUU).