CN105307144B

CN105307144B - A kind of register method, method of calling, application server and network domain arrangement

Info

Publication number: CN105307144B
Application number: CN201410347865.5A
Authority: CN
Inventors: 李琴
Original assignee: China Mobile Communications Group Co Ltd
Current assignee: China Mobile Communications Group Co Ltd
Priority date: 2014-07-21
Filing date: 2014-07-21
Publication date: 2019-08-13
Anticipated expiration: 2034-07-21
Also published as: CN105307144A

Abstract

The invention discloses a kind of register methods, applied to application server, the application server is set between first network domain equipment and the second network domain arrangement, the described method includes: after first terminal is registered on first network domain using CUSTOMER ID, when receiving the first registration request of the second terminal from the second network domains, de-registration request is sent to first network domain equipment, carries the CUSTOMER ID in first registration request；After confirmation is nullified successfully, the second network domain arrangement of Xiang Suoshu sends the second registration request, and second registration request is for requesting the second terminal to be registered in second network domains using the CUSTOMER ID.The present invention also discloses a kind of method of calling, application server and network domain arrangements.

Description

Registration method, calling method, application server and network domain equipment

Technical Field

The present invention relates to the field of wireless mobile communications, and in particular, to a registration method, a call method, an application server, and a network domain device.

Background

Currently, in the process of a user using a mobile terminal such as a mobile phone to perform a call and surf the internet, a Subscriber Identity Module (SIM) needs to be inserted into the mobile terminal and controls SIM cards to register in a wireless mobile communication network, each SIM card corresponds to a Subscriber Identity code, and if the Subscriber Identity code needs to be used on other devices or software, the corresponding SIM card needs to be used at the same time.

Therefore, the technical problem of forced binding of the subscriber identity code and the SIM card exists in the prior art.

Disclosure of Invention

In view of this, to solve technical problems in the prior art, embodiments of the present invention are expected to provide a registration method, a call method, an application server, and a network domain device.

In order to achieve the purpose, the technical scheme of the invention is realized as follows:

in a first aspect, an embodiment of the present invention provides a registration method, applied to an application server, where the application server is disposed between a first network domain device and a second network domain device, and the method includes: after a first terminal uses a user identification code to register on a first network domain, when a first registration request of a second terminal from a second network domain is received, a logout request is sent to first network domain equipment, and the registration request carries the user identification code; and after the successful logout is confirmed, sending a second registration request to the second network domain equipment, wherein the second registration request is used for requesting the second terminal to register on the second network domain by using the user identification code.

Further, the sending a logout request to the first network domain device includes: and verifying the user identification code, and sending the logout request to the first network domain device after the user identification code passes the verification.

Further, before the first terminal registers with the first network domain using the subscriber identity, the method further comprises: storing user information corresponding to the user identification code; wherein the user information is used for the first terminal to register on the first network domain by using the user identification code; and/or for the second terminal to register on the second network domain using the subscriber identity.

Further, the confirming that the logout is successful includes: receiving a first authentication challenge sent by the first network domain device; generating a first authentication response based on the user information, and sending the first authentication response to the first network domain device, wherein the first authentication response is applied to the first network domain device to authenticate the user identification code; and when the user identification code passes the authentication, receiving a logout success response from the first network domain equipment and confirming that the logout is successful.

Further, after the sending of the second registration request to the second network domain device, the method further comprises: receiving a second authentication challenge from the second network domain device; generating a second authentication response based on the user information, and sending the second authentication response to the second network domain device, wherein the second authentication response is used for the second network domain device to authenticate the user identification code; and when the user identification code passes the authentication, receiving a registration success response from the second network domain device, and determining that the second terminal successfully registers in the second network domain.

Further, after the sending the second registration request to the second network domain device, the method further comprises: and receiving a registration success response from the second network domain device, and determining that the second terminal is successfully registered in the second network domain.

In a second aspect, an embodiment of the present invention provides a registration method, which is applied to a first network domain device, where the first network domain device is connected to an application server; the method comprises the following steps: after a first terminal uses a user identification code to register on a first network domain, receiving a logout request sent by an application server, and annotating and selling the first terminal on the first network domain; and after successful logout, sending a successful logout response to the application server.

Further, the marketing the first terminal over the first network domain includes: sending a first authentication challenge to the application server; receiving a first authentication response from the application server and authenticating the user identification code based on the first authentication response; and when the user identification code passes the authentication, sending a forced offline message to the first terminal, and modifying the registration state of the first terminal into logout.

In a third aspect, an embodiment of the present invention provides a registration method, which is applied to a second network domain device, where the second network domain device is connected to an application server; the method comprises the following steps: after a first terminal uses a user identification code to register on a first network domain, receiving a first registration request sent by a second terminal in a second network domain, wherein the first registration request carries the user identification code; sending the registration request to the application server to enable the application server to authenticate the user identification code; and receiving a second registration request sent by the application server, and registering the second terminal by using the user identification code.

Further, the registering the second terminal using the user identification code includes: sending a second authentication challenge to the application server; receiving a second authentication response sent by the application server, and verifying the second authentication response according to second user identification information corresponding to the stored user identification code; and after the verification is passed, associating the second user identification information with the address information of the second terminal, and sending a registration success response to the application server.

In a fourth aspect, an embodiment of the present invention provides a calling method, which is applied to an application server, where the application server is disposed between a first network domain device and a second network domain device, a first terminal connected to the first network domain device can register in the first network domain using a user identifier, and a second terminal connected to the second network domain device can register in the second network domain using the user identifier; the method comprises the following steps: receiving a first call request from the first terminal through the first network domain device, wherein the first call request carries a called user identification code; determining a registered network domain of a called terminal corresponding to the called user identification code according to the called user identification code; when the called terminal is registered on a first network domain, the first call request is sent to the first network domain device, and the first network domain device sends the first call request to the called terminal.

Further, after determining the network domain in which the called terminal corresponding to the called subscriber identity is registered, the method further includes: when the called terminal is registered on a second network domain, converting the type of the identification code of the called user so as to update the first call request; and sending the updated first call request to the first network domain equipment, so that the first network domain equipment sends the updated first call request to the called terminal.

Further, the determining, according to the called subscriber identity, the registered network domain of the called terminal corresponding to the called subscriber identity includes: authenticating the user identification code carried in the first call request; and after the authentication is passed, determining the registered network domain of the called terminal according to the identification code of the called user.

Further, the method further comprises: receiving a second call request from a calling terminal through the second network domain device, wherein the second call request is used for requesting to call a terminal corresponding to the subscriber identity, and the calling terminal uses the calling identity to register on the second network domain; deleting the prefix code of the calling party identification code in the second call request; after determining that the terminal corresponding to the user identification code is registered in the first network domain, converting the type of the user identification code in the second call request so as to update the second call request; and sending the updated second call request to the first network domain equipment, so that the first network domain equipment sends the updated second call request to the first terminal.

Further, after the deleting the prefix code of the caller identification code in the second call request, the method further comprises: and when the terminal corresponding to the user identification code is determined not to be registered on the first network domain, sending a call failure response to the second network domain device.

Further, the method further comprises: receiving a third call request from a calling terminal through the first network domain device, wherein the third call request is used for requesting to call a terminal corresponding to the user identification code; after determining that the terminal corresponding to the user identification code is not registered in the first network domain, converting the type of the user identification code in the third call request, and adding a prefix code in front of the converted user identification code to update the third call request; and sending the updated third call request to the first network domain device, so that the first network domain device sends the updated third call request to the second terminal through the second network domain device.

Further, after the sending the updated third call request to the first network domain device, the method further includes: and receiving a call failure response from the second network domain device, and forwarding the call failure response to the first network domain device.

In a fifth aspect, an embodiment of the present invention provides an application server, disposed between a first network domain device and a second network domain device, where the application server includes: a first transceiver and a first processor; the first transceiver is configured to send a first logout request to a first network domain device when a first terminal receives a first registration request from a second terminal in a second network domain after registering the first terminal in the first network domain using a user identifier, where the first registration request carries the user identifier; and after the successful logout is confirmed, sending a second registration request to the second network domain equipment, wherein the second registration request is used for requesting the second terminal to register on the second network domain by using the user identification code.

Further, the first transceiver is configured to receive a second authentication challenge from the second network domain device after sending a second registration request to the second network domain device; the second authentication response is used for the second network domain equipment to authenticate the user identification code; the second terminal is further used for receiving a registration success response from the second network domain device when the user identification code passes the authentication, and determining that the second terminal is successfully registered in the second network domain; the first processor is further configured to generate the second authentication response based on the user information.

Further, the first transceiver is further configured to receive a registration success response from the second network domain device after sending the second registration request to the second network domain device; the first processor is configured to determine that the second terminal is successfully registered in the second network domain.

Further, the application server further comprises: the memory is used for storing user information corresponding to the user identification code before the first terminal uses the user identification code to register on the first network domain; wherein the user information is used for the first terminal to register on the first network domain by using the user identification code; and/or for the second terminal to register on the second network domain using the subscriber identity.

In a sixth aspect, an embodiment of the present invention provides an application processor, which is disposed between a first network domain device and a second network domain device, where a first terminal connected to the first network domain device is capable of registering in a first network domain using a user identifier, and a second terminal connected to the second network domain device is capable of registering in a second network domain using the user identifier; the application server includes: a second transceiver and a second processor; the second transceiver is configured to receive, by the first network domain device, a first call request from the first terminal, where the first call request carries a called subscriber identity; the first network domain device is further configured to send the first call request to the first network domain device when the called terminal corresponding to the called subscriber identity is registered in a first network domain, so that the first network domain device sends the first call request to the called terminal; and the second processor is used for determining the registered network domain of the called terminal according to the identification code of the called user.

Further, the second processor is configured to convert the type of the called subscriber identity to update the first call request when the called terminal is registered in a second network domain; the second transceiver is configured to send the updated first call request to the first network domain device, so that the first network domain device sends the updated first call request to the called terminal.

Further, the second processor is configured to authenticate the user identifier carried in the first call request; and after the authentication is passed, determining the registered network domain of the called terminal according to the identification code of the called user.

Further, the second transceiver is configured to receive, by the second network domain device, a second call request from a calling terminal, where the second call request is used to request to call a terminal corresponding to the subscriber identity, and the calling terminal is registered in the second network domain using the subscriber identity; the first network domain device is further configured to send an updated second call request to the first network domain device, so that the first network domain device sends the updated second call request to the first terminal; the second processor is configured to delete the prefix code of the caller id in the second call request; and after the terminal corresponding to the user identification code is determined to be registered on the first network domain, converting the type of the user identification code in the second call request so as to update the second call request.

Further, the second transceiver is further configured to, after the second processor deletes the prefix code of the calling subscriber identity in the second call request, send a call failure response to the second network domain device when determining that the terminal corresponding to the subscriber identity is not registered in the first network domain.

Further, the second transceiver is further configured to receive, by the first network domain device, a third call request from a calling terminal, where the third call request is used to request to call a terminal corresponding to the subscriber identity; the first network domain device is further configured to send the updated third call request to the first network domain device, so that the first network domain device sends the updated third call request to the second terminal through the second network domain device; the second processor is further configured to determine that the terminal corresponding to the subscriber identity is not registered in the first network domain, convert the type of the subscriber identity in the third call request, and add a prefix code in front of the converted subscriber identity to update the third call request.

Further, the second transceiver is further configured to receive a call failure response from the second network domain device after sending the updated third call request to the first network domain device, and forward the call failure response to the first network domain device.

In a seventh aspect, an embodiment of the present invention provides a network domain device, which is connected to an application server and a first terminal; the network domain device includes: a third transceiver and a third processor; the third transceiver is configured to receive a logout request sent by the application server after the first terminal uses the user identifier to register in the first network domain; after successful logout, sending a successful logout response to the application server; the third processor is configured to annotate the first terminal over the first network domain.

In an eighth aspect, an embodiment of the present invention provides a network domain device, which is connected to an application server and a second terminal; the network domain device includes: a fourth transceiver and a fourth processor; the fourth transceiver is configured to receive a first registration request sent by a second terminal in a second network domain after a first terminal registers in a first network domain using a user identity, where the first registration request includes the user identity; sending the first registration request to the application server to enable the application server to authenticate the user identification code; receiving a second registration request sent by the application server; and the fourth processor is used for registering the second terminal by using the user identification code.

In the registration method, the call method, the application server and the network domain device provided by the embodiment of the invention, after the first terminal uses the user identification code to register on the first network domain, when a first registration request from a second terminal of a second network domain is received, the application server sends a logout request to the first network domain device, wherein the user identification code is carried in the first registration request; and after the successful logout is confirmed, sending a second registration request to the second network domain equipment, wherein the second registration request is used for requesting the second terminal to register on the second network domain by using the user identification code. That is to say, when the second terminal is online, the application server can cooperate with the first network domain device and the second network domain device to forcibly offline the first terminal, and the terminal does not need to be plugged and unplugged, so that the first terminal and the second terminal can realize different-domain same-number replacement without the SIM card, thereby solving the technical problem existing in the prior art that the subscriber identity code is forcibly bound with the SIM card, and realizing hardware decoupling of the subscriber identity code and the SIM card.

Drawings

FIG. 1 is a diagram of a network architecture in an embodiment of the invention;

fig. 2 is a schematic flowchart of a registration method at an application server side according to an embodiment of the present invention;

fig. 3 is a flowchart illustrating a registration method at a first network domain device side according to an embodiment of the present invention;

fig. 4 is a flowchart illustrating a registration method at a second network domain device side according to an embodiment of the present invention;

FIG. 5 is a flowchart illustrating a calling method according to an embodiment of the present invention;

FIG. 6 is a flow chart illustrating a called party method according to an embodiment of the present invention;

FIG. 7 is a flow chart illustrating another callee method in an embodiment of the invention;

fig. 8 is a schematic structural diagram of an application server according to an embodiment of the present invention;

fig. 9 is a schematic structural diagram of another application server in the embodiment of the present invention;

fig. 10 is a schematic structural diagram of a network domain device in an embodiment of the present invention;

fig. 11 is a schematic structural diagram of another network domain device in the embodiment of the present invention.

Detailed Description

The technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention.

Fig. 1 is a schematic diagram of a network architecture in an embodiment of the present invention, and referring to fig. 1, the network includes a first network domain device 10, a second network domain device 20, an application server 30, a first terminal 11, and a second terminal 21; wherein, the application server 30 is disposed between the first network domain device 10 and the second network domain device 20; the first network domain device 10 is connected with the first terminal 11 through a wireless access network, the second network domain device 20 is connected with the second terminal 21 through a wireless access network, the first terminal 11 can register on the first network domain by using the user identification code, and the second terminal 21 can also register on the second network domain by using the user identification code.

With reference to the embodiment of the present invention, in the above network, the application server 30 is configured to send a logout request to the first network domain device 10 when receiving a first registration request from the second terminal 21 of the second network domain device 20 after the first terminal 11 uses the user identifier to register in the first network domain, where the first registration request carries the user identifier; after confirming that the logout is successful, a second registration request is sent to the second network domain device 20, where the second registration request is used to request the second terminal 21 to register in the second network domain using the user identification code.

The first network domain device 10 is configured to receive a logout request sent by the application server 30 after the first terminal 11 uses the user identifier to register in the first network domain, and to annotate and sell the first terminal 11 in the first network domain; after successful logoff, a successful logoff response is sent to the application server 30.

The second network domain device 20 is configured to receive a first registration request sent by a second terminal 21 in a second network domain after the first terminal 11 uses the user identifier to register in the first network domain, where the first registration request carries the user identifier; sending a first registration request to the application server 30, so that the application server 30 authenticates the user identification code; receiving the second registration request transmitted from the application server 30, the second terminal 21 is registered with the user identification code.

In practical applications, the first network domain may be a Circuit Switched (CS) domain and may also be an Internet Protocol Multimedia Subsystem (IMS) domain; the second network domain may also be the CS domain or the IMS domain, which is not specifically limited in this application.

Accordingly, when the first network domain is a CS domain, the first network domain device 10 may be a Mobile Switching Center (MSC), and the first terminal 11 may be a smartphone; when the first network domain is an IMS domain, the first network domain device 10 may be a Serving Call Session Control Function (SCSCF), and the first terminal 11 may be a software client installed on a Personal Computer (PC); when the second network domain is a CS domain, the second network domain device 20 may be an MSC, and the second terminal 21 may be a smartphone; when the second network domain is an IMS domain, the second network domain device 20 may be an SCSCF, and the second terminal 21 may be a software client installed on a PC.

It should be noted that, after the user opens the soft terminal Number sharing service through the Mobile business hall with the user identification code, for example, the Mobile phone Number, the Home Location Register (HLR) in the CS domain sends the stored Mobile phone Number in the e.164 format and the corresponding International Mobile subscriber identification code (IMSI), Mobile phone authentication Key summary (Ki), and other user information to the application server 30, and the application server 30 stores the user information for the subsequent registration of the first terminal 11 in the first network domain and/or the registration of the second terminal 21 in the second network domain; the Home Subscriber Server (HSS) in the IMS domain stores the e.164-formatted mobile phone number, an IMSI-derived network Protocol Multimedia Public Identity (IMPU), an network Protocol Multimedia Private Identity (IMPI), and Ki at the same time, signs the service on the MSC and SCSCF, and generates a registration password for registration of the IMS application soft terminal.

The workflow of the above network is described below in terms of a single-sided network element.

The embodiment of the invention provides a registration method which is applied to an application server. Fig. 2 is a schematic flowchart of a registration method on an application server side in an embodiment of the present invention, and referring to fig. 2, the method includes:

s201: after a first terminal uses a user identification code to register on a first network domain, when a first registration request from a second network domain device is received, a logout request is sent to the first network domain device;

wherein, the first registration request carries the user identification code.

In a specific implementation process, the step of sending a logout request to the first network domain device may be: and verifying the user identification code, and sending a logout request to the first network domain device after the user identification code passes the verification.

Specifically, after a first terminal uses a user identification code and is registered in a first network domain, at this time, a second terminal also uses the user identification code to register in a second network domain, first, the second terminal sends a first registration request to a second network domain device, the first registration request includes the user identification code, the second network domain device forwards the first registration request to an application server, after the application server receives the first registration request, the application server firstly verifies the user identification code, and sends a logout request to the first network domain device after the verification is passed, so as to request to logout the first terminal.

Then, after receiving the logout request, the first network domain device sends a first authentication challenge to the application server, the application server receives the first authentication challenge, generates a first authentication response based on the stored user information, such as IMSI and Ki corresponding to the mobile phone number, and sends the first authentication response to the first network domain device, so that the first network domain device authenticates the user identification code according to the first authentication response; when the user identification code passes the authentication, the first network domain equipment sends a forced offline message to the first terminal, modifies the registration state of the first terminal into logout, sends a logout success response to the application server, and the application server receives the logout success response and confirms that the logout is successful.

S202: and after the successful logout is confirmed, sending a second registration request to the second network domain device.

Wherein the second registration request is for requesting the second terminal to register on the second network domain using the subscriber identity.

Specifically, the application server receives the successful logout response, after confirming that the logout is successful, the application server sends a second registration request to the second network domain device, and receives a second authentication challenge from the second network domain device, the application server generates a second authentication response based on the stored user information, such as IMPI and Ki corresponding to the mobile phone number, and sends the second authentication response to the second network domain device, the second network domain device authenticates the user identifier according to the second authentication response, when the user identifier passes the authentication, the second network domain device sends a successful registration response, and the application server receives the successful registration response, and determines that the second terminal is successfully registered in the second network domain.

In another embodiment, after receiving the logout success response, the application server sends a second registration request to the second network domain device, and the second network domain device changes the registration state of the second terminal into registration directly according to the second registration request and sends a registration success response to the application service request. And after receiving the registration success response, the application server determines that the second terminal is successfully registered in the second network domain.

At this point, the registration process of the second terminal replacing the first terminal is completed.

One or more of the above embodiments are described below with specific examples.

The first embodiment is as follows:

it is assumed that the first network domain is a CS domain and the second network domain is an IMS domain.

Firstly, a software client logs in, a user inputs a mobile phone number and a registration password, a registration request carrying the mobile phone number and the registration password is sent to an SCSCF through a Proxy Call Session Control Function (PCSCF), the SCSCF inquires whether the number opens a soft terminal common number service, and after the mobile phone number is inquired to open the service, a service message and the registration request are sent to an application server according to the requirements of an Initial Filter Criterion (iFC).

Then, after confirming that the mobile phone number opens the service, the application server verifies the mobile phone number and the registration password in the registration request to confirm the validity of the software client user, and then sends a logout request to the MSC after the verification is successful. The MSC forwards the logout request, the HLR sends a first authentication challenge to the application server through the MSC after receiving the logout request, the application server calculates a response number according to the stored IMSI and Ki, namely a first authentication response, and sends the response number to the HLR through the MSC. The HLR authenticates the mobile phone number based on the response number, after the authentication is passed, the MSC sends a forced offline message to the mobile phone user, changes the registration state of the number into logout, and then sends a successful logout response to the application server. Then, after receiving the successful logout response from the CS domain, the application server sends a registration request to the HSS through the scff, where the registration request carries an IMPU and an IMPI corresponding to the mobile phone number. After receiving the registration request sent by the application server, the HSS sends a second authentication challenge to the application server, and the application server calculates a response number, i.e., a second authentication response, according to the stored IMPI and Ki and sends the response number to the HSS. And the HSS authenticates the mobile phone number according to the response number, sends a registration success response to the application server through the SCSCF after the authentication is passed, and associates the IMPU with the IP address of the software client.

And finally, after receiving the registration success response, the application server sends a registration success message to the software client.

Example two:

it is assumed that the first network domain is an IMS domain and the second network domain is a CS domain.

Firstly, a mobile phone in a CS domain initiates a registration request, an MSC acquires a signing Service of a mobile phone number, when the number is inquired to open a soft terminal common number Service, the Service is triggered to a Service Control Point (SCP), and the SCP sends a cancellation request to an application server; after receiving the request, the application server sends the request to HSS, HSS sends a second authentication challenge to the application server, after successfully receiving the second authentication challenge, the application server receives a successful logout response sent by HSS and returns the successful logout response to SCP.

Then SCP continues to transmit the registration request of mobile phone to HLR, HLR registers mobile phone.

To sum up, when the second terminal is online, the application server cooperates with the first network domain device and the second network domain device to forcibly offline with the first terminal, so that the first terminal and the second terminal can realize different-domain same-number replacement without the SIM card, and decoupling of the mobile phone number and the SIM card hardware is realized. And only one network element of the application server is added in the network, so that the change of the network is small.

Based on the same inventive concept, the embodiment of the invention provides a registration method, which is applied to a first network domain device, and the first network domain device is connected with an application server. Fig. 3 is a flowchart illustrating a registration method on a first network domain device side in an embodiment of the present invention, and referring to fig. 3, the method includes:

s301: after a first terminal uses a user identification code to register on a first network domain, receiving a logout request sent by an application server, and annotating and selling the first terminal on the first network domain;

specifically, S301 may be: sending a first authentication challenge to an application server; receiving a first authentication response from the application server, and authenticating the user identification code based on the first authentication response; and when the user identification code passes the authentication, sending a forced offline message to the first terminal, and modifying the registration state of the first terminal into logout.

S302: and after successful logout, sending a successful logout response to the application server.

Based on the same inventive concept, the embodiment of the invention provides a registration method, which is applied to a second network domain device, and the second network domain device is connected with an application server. Fig. 4 is a flowchart illustrating a registration method on the second network domain device side in an embodiment of the present invention, and referring to fig. 4, the method includes:

s401: receiving a first registration request sent by a second terminal in a second network domain, wherein the first registration request comprises a user identification code;

s402: inquiring the service of the user identification code, and sending a service message to an application server to enable the first network domain equipment to log off the first terminal;

s403: and receiving a second registration request sent by the application server, and registering the second terminal by using the user identification code.

Specifically, after receiving the registration request sent by the application server, S403 may be: sending a second authentication challenge to the application server; receiving a second authentication response sent by the application server, and verifying the second authentication response according to second user identification information corresponding to the stored user identification code; and after the verification is passed, associating the second user identification information with the address information of the second terminal, and sending a registration success response to the application server.

At this point, the second terminal replaces the first terminal, and the registration process is completed.

Based on the same inventive concept, the embodiment of the invention provides a calling method, which is applied to an application server, wherein the application server is arranged between a first network domain device and a second network domain device.

In this embodiment, the first network domain device is consistent with the first network domain device in the one or more embodiments, and the second network domain device is consistent with the second network domain device in the one or more embodiments. A first terminal connected to a first network domain device can be registered with the first network domain using a subscriber identity, and a second terminal connected to a second network domain device can be registered with the second network domain using the subscriber identity.

Firstly, a calling process of opening a user identification code of a soft terminal common number service as a calling user identification code is introduced. Fig. 5 is a flowchart illustrating a calling method in an embodiment of the present invention, and referring to fig. 5, the method includes:

s501: receiving a first call request from a first terminal through first network domain equipment, wherein the first call request carries a called user identification code;

specifically, when a subscriber identity of the soft terminal common number service is opened as a calling subscriber identity, a first terminal sends a first call request, where the request may include a called subscriber identity, a first network domain device receives the first call request and sends the first call request to an application server, and the application server receives the request.

S502: according to the called user identification code, determining a registered network domain of the called terminal corresponding to the called user identification code;

that is, it is determined whether the terminal corresponding to the called subscriber identity is registered on the first network domain or the second network domain.

In a specific implementation process, the first call request may also carry a subscriber identity, that is, a calling subscriber identity, for activating a soft terminal common number service, and then S502 may be: authenticating the user identification code carried in the first call request; and after the authentication is passed, determining the registered network domain of the terminal according to the identification code of the called user.

Specifically, after receiving the first call request, the application server authenticates the user identification code according to the calling user identification code carried in the first call request, determines whether the number opens the soft terminal common number service, and verifies the identity of the terminal corresponding to the calling user identification code, that is, the user of the first terminal. And after the authentication is passed, determining the registered network domain of the terminal corresponding to the identification code of the called user according to the identification code of the called user.

S503 a: when the called terminal corresponding to the called user identification code is registered on the first network domain, a first call request is sent to the first network domain device, so that the first network domain device sends the first call request to the called terminal.

Specifically, when it is determined that the called terminal corresponding to the called user identifier is registered in the first network domain through S502, the application server sends the first call request to the first network domain device, so that the first network domain device forwards the first call request to the called terminal.

For example, assuming that the subscriber identity of the soft terminal sharing service is the calling subscriber identity, the first terminal uses the calling subscriber identity to register in the IMS domain, and the called terminal corresponding to the called subscriber identity also registers in the IMS domain.

Firstly, a software client on an IMS domain, namely a first terminal, initiates a first call request, wherein the first call request carries a called user identification code, and an SCSCF receives the first call request through a PCSCF and sends a service message to an application server according to an iFC requirement.

Then, the application server receives the authentication challenge sent by HSS, and calculates a response number according to the stored IMPI and Ki, and sends the response number to HSS to authenticate the calling user identification code, when the authentication is passed, the application server resends the first call request to SCSCF.

Finally, the SCSCF forwards the first call request to the network domain device to which the called subscriber identity belongs, that is, the query call Session Control Function (ICSCF) to which the called subscriber identity corresponds in the IMS domain. The first call request is routed to the called terminal corresponding to the identification code of the called user by the ICSCF.

In another embodiment, after S502, the method may include:

s503 b: when the called terminal corresponding to the called user identification code is registered on the second network domain, converting the type of the called user identification code to update the first call request;

s504, 504 b: and sending the updated first call request to the first network domain equipment, so that the first network domain equipment sends the updated first call request to the called terminal.

Specifically, when it is determined that the called terminal corresponding to the called party identifier is registered in the second network domain through S502, the application server converts the called party identifier into a type that can be identified by the second network domain device, and updates the first call request accordingly, and then sends the updated first call request to the first network domain device, so that the first network domain device forwards the updated first call request to the second network domain device, and the second network domain device identifies and routes the first call request to the called terminal.

For example, assume that the subscriber identity of the soft terminal number sharing service is the calling subscriber identity, the first terminal uses the calling subscriber identity to register in the IMS domain, and the terminal corresponding to the called subscriber identity registers in the CS domain.

Then, the application server receives the authentication challenge sent by HSS, and calculates a response number according to the stored IMPI and Ki, and sends the response number to HSS to authenticate the calling user identification code, when the authentication is passed, the application server converts the type of the called user identification code in the first call request to update the first call request, and sends it to SCSCF again.

Finally, the SCSCF forwards the first call request to the network domain equipment to which the identification code of the called user belongs, namely the ICSCF to which the called user identifies the corresponding user in the IMS domain. The first call request is routed by the ICSCF to the MSC of the CS domain via a Media Gateway Control Function (MGCF) and then to the called terminal by the MSC.

The called process of using the subscriber identity of the soft terminal common number service as the called subscriber identity is introduced below.

Fig. 6 is a flowchart illustrating a called party method in an embodiment of the present invention. Referring to fig. 6, the method includes:

s601: receiving a second call request from the calling terminal through second network domain equipment, wherein the second call request is used for requesting to call a terminal corresponding to the user identification code, and the calling terminal uses the calling identification code to register on a second network domain;

specifically, when the calling terminal in the second network domain calls the subscriber identity of the soft terminal common number service, the second network domain device sends the second call request to the application server through the first network domain device.

S602: deleting the prefix code of the calling party identification code in the second call request;

that is, the application server deletes the prefix code of the caller identification code.

S603: after determining that the terminal corresponding to the user identification code is registered in the first network domain, converting the type of the called user identification code in the second call request so as to update the second call request;

specifically, the application server determines that the subscriber identity is registered in the first network domain according to the subscriber identity from which the prefix code is deleted, that is, when the terminal corresponding to the called subscriber identity is determined to be the first terminal, the application server converts the type of the subscriber identity into a type that can be identified by the first network device, so as to update the second call request.

S604 a: and sending the updated second call request to the first network domain equipment, so that the first network domain equipment sends the updated second call request to the first terminal.

In practical applications, if it is determined that the subscriber identity is not registered in the first network domain, that is, the subscriber identity is not registered in both the first network domain and the second network domain, after S603, the method may further include:

s604 b: and after determining that the terminal corresponding to the user identification code is not registered in the first network domain, sending a call failure response to the second network domain device.

Specifically, when the application server determines that the subscriber identity code is not registered in the first network domain according to the subscriber identity code from which the prefix code is deleted, that is, when the application server determines that the subscriber identity code is not registered in either the first network domain or the second network domain, the application server sends a call failure response to the second network domain device to inform of the call failure.

For example, a calling mobile phone user initiates a call in the CS domain, and the called user identification code is a mobile phone number in e.164 format that opens the soft terminal common number service. Firstly, according to a second call request sent by a terminal corresponding to a calling mobile phone number, an MSC (mobile switching center) of a CS (circuit switched) domain inquires that the registration state of a called mobile phone number in the CS domain is an unregistered state, and obtains subscription information of the called mobile phone number, the MSC triggers a service message to an SCP (service control point), the SCP adds a specific prefix code in front of the called mobile phone number, and also adds a prefix code for preventing callback in front of the calling mobile phone number, and then routes the added called mobile phone number and the calling mobile phone number to an MGCF (media control gateway).

Then, MGCF removes the specific prefix code before the called mobile phone number after receiving, and transfers the call request to SCCF to which the called mobile phone number belongs, the SCSCF transfers the call request to the application server according to the iFC requirement, the application server finds that the prefix code is in front of the calling mobile phone number, deletes the calling prefix code, and judges that the called mobile phone number has been successfully registered in the IMS domain, and converts the mobile phone number in E.164 format into a format that the SCSCF can recognize, namely the communication address registered by the software client corresponding to the called mobile phone number, and updates the second call request according to the prefix code, and then sends the updated second call request to the SCSCF, and transfers the second call request to the software client through PCSCF, and establishes a call; if the application server judges that the called mobile phone number is not registered in the IMS domain, the application server replies a registration failure response to the MSC of the calling user through the SCSCF and the MGCF, and the user is indicated to be unregistered.

Fig. 7 is a flowchart illustrating another method for called party in the embodiment of the present invention. Referring to fig. 7, the method includes:

s701: receiving a third call request from the calling terminal through the first network domain device, wherein the third call request is used for requesting to call a terminal corresponding to the user identification code;

for example, when the IMS domain user calls a user identification code, that is, a mobile phone number, which opens the soft terminal number sharing service, the called mobile phone number in the sent third call request is a phone Resource Identifier (Tel URI) of the software client, the SCSCF to which the calling mobile phone number belongs converts the Tel URI in the third call request into a Session Initiation Protocol (SIP) URI format after being queried, and sends the third call request to the ICSCF to which the called mobile phone number belongs, and the ICSCF finds the SCSCF to which the called mobile phone number belongs, and sends the third call request to the application server according to the IFC requirement, and the application server receives the third call request.

S702: after determining that the terminal corresponding to the user identification code is not registered in the first network domain, converting the type of the called user identification code in the third call request, and adding a prefix code in front of the converted user identification code to update the third call request;

for example, when the application server determines that the called mobile phone number is not registered in the IMS domain according to the third call request, the application server converts the called user identifier from the SIP URI format to the e.164 format, and adds a prefix code before the called user identifier in the e.164 format, thereby updating the third call request.

S703 a: and sending the updated third call request to the first network domain equipment, so that the first network domain equipment sends the updated third call request to the second terminal through the second network domain equipment.

For example, the application server sends the updated third call request to the SCSCF to send the third call request, so that the SCSCF routes the updated third call request to the MGCF, and the MGCF adds a prefix code for preventing callback in front of the calling mobile phone number. After receiving the updated third call request, MGCF removes the prefix code of the called mobile phone number and routes the call request to MSC. MSC forwards to SCP, SCP finds that the calling mobile phone number has prefix code in front of it, deletes the prefix code of calling mobile phone number, then MSC determines that the called user identification code is registered in CS domain, then sends down connection message, and establishes call.

In practical applications, the called subscriber identity may not be registered in the CS domain, and the method further includes:

s703 b: a call failure response from the second network domain device is received and forwarded to the first network domain device.

For example, the MSC returns a call failure response to the application server when it determines that the called subscriber identity is not registered in the CS domain.

Based on the same inventive concept, the embodiment of the invention provides an application server, which is arranged between a first network domain device and a second network domain device; fig. 8 is a schematic structural diagram of an application server in an embodiment of the present invention, and referring to fig. 8, the application server includes: a first transceiver 81 and a first processor 82; the first transceiver 81 is configured to send a logout request to a first network domain device when receiving a first registration request from a second terminal in a second network domain after the first terminal uses a user identifier to register in the first network domain, where the first registration request carries the user identifier; and after the successful logout is confirmed, sending a second registration request to the second network domain equipment, wherein the registration request is used for requesting the second terminal to register on the second network domain by using the user identification code.

Further, the first transceiver 81 is configured to receive a second authentication challenge from the second network domain device after sending the second registration request to the second network domain device; the second authentication response is used for the second network domain equipment to authenticate the user identification code; the second terminal is further used for receiving a registration success response from the second network domain device when the user identification code passes the authentication, and determining that the second terminal is successfully registered in the second network domain; the first processor 82 is further configured to generate a second authentication response based on the user information.

Further, the first transceiver 81 is further configured to receive a registration success response from the second network domain device after sending the second registration request to the second network domain device; a first processor 82 for determining that the second terminal has successfully registered with the second network domain.

Further, the application server further comprises: the memory is used for storing user information corresponding to the user identification code before the first terminal uses the user identification code to register on the first network domain; the user information is used for the first terminal to register on the first network domain by using the user identification code; and/or for the second terminal to register on the second network domain using the subscriber identity.

Based on the same inventive concept, the embodiment of the invention provides an application server, which is arranged between a first network domain device and a second network domain device; a first terminal connected with a first network domain device can register on a first network domain by using a user identification code, and a second terminal connected with a second network domain device can register on a second network domain by using the user identification code; the first network domain device is consistent with the first network domain device in one or more embodiments described above, and the second network domain device is consistent with the second network domain device in one or more embodiments described above. Fig. 9 is a schematic structural diagram of another application server in an embodiment of the present invention, and referring to fig. 9, the application server includes: a second transceiver 91 and a second processor 92, the second transceiver 91 is configured to receive a first call request from a first terminal through a first network domain device, where the first call request carries a called user identifier; the first network domain device is used for sending a first call request to the first network domain device when a called terminal corresponding to the identification code of the called user is registered on the first network domain, so that the first network domain device sends the first call request to the called terminal; and a second processor 92, configured to determine, according to the called subscriber identity, a network domain in which the called terminal is registered.

Further, a second processor 92, configured to convert the type of the called party identifier and update the first call request when the called terminal is registered in the second network domain; the second transceiver 91 is configured to send the updated first call request to the first network domain device, so that the first network domain device sends the updated first call request to the called terminal.

Further, the second processor 92 is configured to authenticate the user identifier carried in the first call request; and after the authentication is passed, determining the registered network domain of the called terminal according to the identification code of the called user.

Further, the second transceiver 91 is configured to receive a second call request from the calling terminal through a second network domain device, where the second call request is used to request to call a terminal corresponding to the subscriber identity, and the calling terminal uses the subscriber identity to register in a second network domain; the first network domain device is further configured to send the updated second call request to the first network domain device, so that the first network domain device sends the updated second call request to the first terminal; a second processor 92, configured to delete the prefix code of the caller id in the second call request; and after determining that the terminal corresponding to the user identification code is registered in the first network domain, converting the type of the user identification code in the second call request so as to update the second call request.

Further, the second transceiver 91 is further configured to send a call failure response to the second network domain device when the first processor determines that the terminal corresponding to the subscriber identity is not registered in the first network domain after deleting the prefix code of the calling subscriber identity in the second call request.

Further, the second transceiver 91 is further configured to receive a third call request from the calling terminal through the first network domain device, where the third call request is used to request to call a terminal corresponding to the called subscriber identity; the first network domain device is further configured to send the updated third call request to the first network domain device, so that the first network domain device sends the updated third call request to the second terminal through the second network domain device; the second processor 92 is further configured to determine that the terminal corresponding to the subscriber identity is not registered in the first network domain, convert the type of the subscriber identity in the third call request, and add a prefix code before the converted subscriber identity to update the third call request.

Further, the second transceiver 91 is further configured to receive a call failure response from the second network domain device after sending the updated third call request to the first network domain device, and forward the call failure response to the first network domain device.

It should be noted that the functions of the application server described in fig. 8 and the functions of the application server described in fig. 9 may be implemented by the same application server, or may be implemented by two separate application servers, and the present invention is not limited in particular.

Based on the same inventive concept, embodiments of the present invention provide a network domain device, consistent with the first network domain device described in one or more embodiments above, connected to an application server and a first terminal; fig. 10 is a schematic structural diagram of a network domain device in an embodiment of the present invention, and referring to fig. 10, the network domain device includes: a second transceiver 101 and a second processor 102; the second transceiver 101 is configured to receive a logout request sent by an application server after the first terminal uses the user identifier to register in the first network domain; after successful logout, sending a successful logout response to the application server; a second processor 102 for marketing the first terminal over the first network domain.

Based on the same inventive concept, an embodiment of the present invention provides a network domain device, which is consistent with the second network domain device described in one or more embodiments above, and is connected to an application server and a second terminal; fig. 11 is a schematic structural diagram of another network domain device in the embodiment of the present invention, referring to fig. 11,

the network domain device includes: a third transceiver 111 and a third processor 112; the third transceiver 111 is configured to receive a registration request sent by a second terminal in a second network domain, where the registration request includes a user identifier; sending the service message to an application server to enable the first network domain equipment to log off the first terminal; receiving a registration request sent by an application server; a third processor 112, configured to query a service of the subscriber identity; and registering the second terminal by using the user identification code.

The functions of the multiple network domain devices may be integrated in one physical entity, or may be respectively disposed in different physical entities, which is not limited in the present invention.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of a hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.

Claims

1. A registration method is applied to an application server, wherein the application server is arranged between a first network domain device and a second network domain device, and the method comprises the following steps:

after a first terminal uses a user identification code IMSI to register on a first network domain, when receiving a first registration request of a second terminal from a second network domain, sending a logout request to a first network domain device, wherein the registration request carries the IMSI;

and after the successful logout is confirmed, sending a second registration request to the second network domain equipment, wherein the second registration request is used for requesting the second terminal to register on the second network domain by using the IMSI.

2. The method of claim 1, wherein sending a deregistration request to the first network domain device comprises:

and verifying the IMSI, and sending the logout request to the first network domain equipment after the IMSI passes the verification.

3. The method of claim 1, wherein before the first terminal registers with the first network domain using the IMSI, the method further comprises:

storing the user information corresponding to the IMSI; wherein the user information is used for the first terminal to register on the first network domain by using the IMSI; and/or for the second terminal to register on the second network domain using the IMSI.

4. The method of claim 3, wherein confirming the log-off was successful comprises:

receiving a first authentication challenge sent by the first network domain device;

generating a first authentication response based on the user information, and sending the first authentication response to the first network domain device, wherein the first authentication response is applied to the first network domain device to authenticate the IMSI;

and when the IMSI passes the authentication, receiving a logout success response from the first network domain equipment, and confirming that the logout is successful.

5. The method of claim 3, wherein after the sending the second registration request to the second network domain device, the method further comprises:

receiving a second authentication challenge from the second network domain device;

generating a second authentication response based on the user information, and sending the second authentication response to the second network domain device, where the second authentication response is used for the second network domain device to authenticate the IMSI;

and when the IMSI authentication is passed, receiving a registration success response from the second network domain equipment, and determining that the second terminal is successfully registered in the second network domain.

6. The method of claim 4, wherein after the sending the second registration request to the second network domain device, the method further comprises:

and receiving a registration success response from the second network domain device, and determining that the second terminal is successfully registered in the second network domain.

7. A registration method is applied to a first network domain device, and is characterized in that the first network domain device is connected with an application server; the method comprises the following steps:

after a first terminal uses a user identification code IMSI to register on a first network domain, receiving a logout request sent by the application server, and annotating and canceling the first terminal on the first network domain;

and after successful logout, sending a successful logout response to the application server so that the application server requests the second terminal to register on the second network domain by using the IMSI.

8. The method of claim 7, wherein the first terminal is provisioned on the first network domain, comprising:

sending a first authentication challenge to the application server;

receiving a first authentication response from the application server, and authenticating the IMSI based on the first authentication response;

and when the IMSI passes the authentication, sending a forced offline message to the first terminal, and modifying the registration state of the first terminal into logout.

9. A registration method is applied to a second network domain device, and is characterized in that the second network domain device is connected with an application server; the method comprises the following steps:

after a first terminal uses a user identification code IMSI to register on a first network domain, receiving a first registration request sent by a second terminal in a second network domain, wherein the first registration request carries the IMSI;

sending the registration request to the application server to enable the application server to authenticate the IMSI;

and receiving a second registration request sent by the application server, and registering the second terminal by using the IMSI.

10. The method of claim 9, wherein the registering the second terminal with the IMSI comprises:

sending a second authentication challenge to the application server;

receiving a second authentication response sent by the application server, and verifying the second authentication response according to the stored second user identification information corresponding to the IMSI;

and after the verification is passed, associating the second user identification information with the address information of the second terminal, and sending a registration success response to the application server.

11. A calling method is characterized in that the calling method is applied to an application server, the application server is arranged between a first network domain device and a second network domain device, a first terminal connected with the first network domain device can use a user identification code IMSI to register on the first network domain, and a second terminal connected with the second network domain device can use the IMSI to register on the second network domain; the method comprises the following steps:

receiving a first call request from the first terminal through the first network domain device, wherein the first call request carries a called IMSI;

determining a registered network domain of a called terminal corresponding to the called IMSI according to the called IMSI;

when the called terminal is registered on a first network domain, the first call request is sent to the first network domain device, and the first network domain device sends the first call request to the called terminal.

12. The method of claim 11, wherein after the determining the network domain to which the called terminal corresponding to the called IMSI is registered, the method further comprises:

when the called terminal is registered on a second network domain, converting the type of the called IMSI so as to update the first call request;

and sending the updated first call request to the first network domain equipment, so that the first network domain equipment sends the updated first call request to the called terminal.

13. The method according to claim 11 or 12, wherein the determining, according to the called IMSI, a network domain in which the called terminal corresponding to the called IMSI is registered includes:

authenticating the IMSI carried in the first call request;

and after the authentication is passed, determining the registered network domain of the called terminal according to the called IMSI.

14. The method of claim 11, further comprising:

receiving a second call request from a calling terminal through the second network domain device, wherein the second call request is used for requesting to call a terminal corresponding to the IMSI, and the calling terminal uses a calling identification code to register on the second network domain;

deleting the prefix code of the calling IMSI in the second call request;

after determining that the terminal corresponding to the IMSI is registered in the first network domain, converting the type of the IMSI in the second call request so as to update the second call request;

and sending the updated second call request to the first network domain equipment, so that the first network domain equipment sends the updated second call request to the first terminal.

15. The method of claim 14, wherein after the deleting the prefix code of the calling IMSI in the second call request, the method further comprises:

and when the terminal corresponding to the IMSI is determined not to be registered on the first network domain, sending a call failure response to the second network domain equipment.

16. The method of claim 11, further comprising:

receiving a third call request from a calling terminal through the first network domain device, wherein the third call request is used for requesting to call a terminal corresponding to the IMSI;

after determining that the terminal corresponding to the IMSI is not registered in the first network domain, converting the type of the IMSI in the third call request, and adding a prefix code in front of the converted IMSI to update the third call request;

and sending the updated third call request to the first network domain device, so that the first network domain device sends the updated third call request to the second terminal through the second network domain device.

17. The method of claim 16, wherein after the sending the updated third call request to the first network domain device, the method further comprises:

and receiving a call failure response from the second network domain device, and forwarding the call failure response to the first network domain device.

18. An application server disposed between a first network domain device and a second network domain device, the application server comprising: a first transceiver and a first processor; wherein,

the first transceiver is configured to send a first deregistration request to the first network domain device when a first terminal receives a first registration request from a second terminal in a second network domain after registering the first terminal in the first network domain by using a subscriber identity IMSI, where the first registration request carries the IMSI; and after the successful logout is confirmed, sending a second registration request to the second network domain equipment, wherein the second registration request is used for requesting the second terminal to register on the second network domain by using the IMSI.

19. The application server of claim 18, wherein the first transceiver is configured to receive a second authentication challenge from the second network domain device after sending a second registration request to the second network domain device; the terminal is further configured to send a second authentication response to the second network domain device, where the second authentication response is used for the second network domain device to authenticate the IMSI; the terminal is further configured to receive a registration success response from the second network domain device when the IMSI authentication passes, and determine that the second terminal is successfully registered in the second network domain;

the first processor is further configured to generate the second authentication response based on user information.

20. The application server of claim 18, wherein the first transceiver is further configured to receive a registration success response from the second network domain device after sending the second registration request to the second network domain device;

the first processor is configured to determine that the second terminal is successfully registered in the second network domain.

21. The application server of claim 18, wherein the application server further comprises: the memory is used for storing the user information corresponding to the IMSI before the first terminal uses the IMSI to register on a first network domain; wherein the user information is used for the first terminal to register on the first network domain by using the IMSI; and/or for the second terminal to register on the second network domain using the IMSI.

22. An application server is arranged between a first network domain device and a second network domain device, a first terminal connected with the first network domain device can use a subscriber identity IMSI to register on a first network domain, and a second terminal connected with the second network domain device can use the IMSI to register on a second network domain; the application server includes: a second transceiver and a second processor; wherein,

the second transceiver is configured to receive, by the first network domain device, a first call request from the first terminal, where the first call request carries a called IMSI; the first network domain device is further configured to send the first call request to the first network domain device when the called terminal corresponding to the called IMSI is registered in a first network domain, so that the first network domain device sends the first call request to the called terminal;

and the second processor is used for determining the registered network domain of the called terminal according to the called IMSI.

23. The application server of claim 22, wherein the second processor is configured to translate the type of the called IMSI to update the first call request when the called terminal is registered with a second network domain;

the second transceiver is configured to send the updated first call request to the first network domain device, so that the first network domain device sends the updated first call request to the called terminal.

24. The application server according to claim 22 or 23, wherein the second processor is configured to authenticate the IMSI carried in the first call request; and after the authentication is passed, determining the registered network domain of the called terminal according to the called IMSI.

25. The application server of claim 22, wherein the second transceiver is configured to receive a second call request from a calling terminal through the second network domain device, wherein the second call request is used to request to call a terminal corresponding to the IMSI, and the calling terminal is registered in the second network domain using a calling identity; the first network domain device is further configured to send an updated second call request to the first network domain device, so that the first network domain device sends the updated second call request to the first terminal;

the second processor is configured to delete the prefix code of the calling IMSI in the second call request; and after the terminal corresponding to the IMSI is determined to be registered in the first network domain, converting the type of the IMSI in the second call request so as to update the second call request.

26. The application server of claim 25, wherein the second transceiver is further configured to, after deleting the prefix code of the calling IMSI in the second call request, send a call failure response to the second network domain device when determining that the terminal corresponding to the IMSI is not registered in the first network domain.

27. The application server of claim 22, wherein the second transceiver is further configured to receive a third call request from a calling terminal through the first network domain device, where the third call request is used to request to call a terminal corresponding to the IMSI; the first network domain device is further configured to send the updated third call request to the first network domain device, so that the first network domain device sends the updated third call request to the second terminal through the second network domain device;

the second processor is further configured to determine that the terminal corresponding to the IMSI is not registered in the first network domain, convert the type of the IMSI in the third call request, and add a prefix code in front of the converted IMSI to update the third call request.

28. The application server of claim 27, wherein the second transceiver is further configured to receive a call failure response from the second network domain device after sending the updated third call request to the first network domain device, and to forward the call failure response to the first network domain device.

29. A network domain device, characterized by being connected to an application server and a first terminal; the network domain device includes: a third transceiver and a third processor; wherein,

the third transceiver is configured to receive a logout request sent by the application server after the first terminal registers in the first network domain using the subscriber identity IMSI; after successful logout, sending a successful logout response to the application server so that the application server requests the second terminal to register on the second network domain by using the IMSI;

the third processor is configured to annotate the first terminal over the first network domain.

30. A network domain device, characterized by being connected to an application server and a second terminal; the network domain device includes: a fourth transceiver and a fourth processor; wherein,

the fourth transceiver is configured to receive a first registration request sent by a second terminal in a second network domain after the first terminal registers in the first network domain using the subscriber identity IMSI, where the first registration request includes the IMSI; sending the first registration request to the application server, so that the application server authenticates the IMSI; receiving a second registration request sent by the application server;

and the fourth processor is configured to register the second terminal with the IMSI.