CN101998667A - Number converting method and service continuity application server - Google Patents

Abstract

The present invention provides a number conversion method, including: a calling user initiates a call in the circuit domain, and the core network of the circuit domain sends a session invitation message to the service continuity application server (SC AS) to which the calling user belongs, and the SC After receiving the session invitation message, the AS compares the calling number in the session invitation message with the user data of the calling user, sets the calling number in the session invitation message according to the comparison result, and forwards the Send the above session invitation message to the called user. The invention also provides a service continuity application server. The invention converts the calling number, and can send the corresponding calling number to the called user as required.

Description

A number conversion method and business continuity application server

technical field

The invention relates to the communication field, in particular to an IP multimedia subsystem number conversion method and a business continuity application server.

Background technique

IP (Internet Protocol, Internet Protocol) multimedia subsystem IMS (IP MultimediaCore Network Subsystem) is an IP-based network architecture proposed by the 3rd Generation Partnership Project 3GPP (3rd Generation Partnership Project), which builds an open and flexible business environment, support multimedia applications, and provide users with rich multimedia services.

IMS is an IP-based telecommunications network architecture and has nothing to do with access technology. In addition to providing services for packet access networks such as GPRS (General Packet Radio Service) and WLAN (Wireless Local Area Network, wireless local area network), it also provides It can provide services for mobile cellular networks such as GSM (Global System for Mobile communications, Global System for Mobile Communications), UMTS (Universal Mobile Telecommunications System, Unified Mobile Communications System).

Mobile cellular networks such as GSM and UMTS adopt circuit switching technology, called circuit (Circuit Switched, CS for short) domain, which can provide users with basic voice services and supplementary services based on voice services. When the CS domain accesses the IMS, it evolves into an access mode, and services are completely provided by the IMS. This technology is called IMS Centralized Service (ICS for short).

The user terminal (User Equipment, UE) maintains voice continuity during switching between the PS domain and the CS domain. The technology to ensure this continuity is called IMS Voice Call Continuity (Voice Call Continuity, VCC for short).

Fig. 1 is a system reference frame diagram of IMS session transfer. The whole framework includes User Equipment (UE for short) 101, Mobile Switch Center (MSC for short) 102, Media Gateway Control Function (MGCF for short) 103, Media Gateway (MGW for short) 104. Proxy Call Session Control Function (ProxyCall Session Control Function, P-CSCF for short) 105. Interrogating Call Session Control Function (Interrogating Call Session Control Function, I-CSCF for short) 106. Home Subscriber Server (Home Subscriber Server, HSS for short) 107. Serving Call Session Control Function (ServingCall Session Control Function, S-CSCF for short) 108, Service Continuity Application Server (Service Continuity Application Server, SC AS for short) 109, Service Control Point (Service Control Point, SCP for short) 110.

SC AS 109 provides multimedia service continuity server, multimedia service server, etc., and can provide users with services such as multimedia service continuity and multimedia service.

SCP 110 is an intelligent network service control network element, which mainly performs third-party service control on traditional circuit domain services through intelligent services.

The correlation number (Correlation MSISDN, C-MSISDN) is used for session transfer, the only number associated with a session to solve the problem of session transfer in the IMS number sharing scenario. In the IMS field, there is a one-to-one correspondence between the associated number and the user's private user ID. The associated number is usually brought to the SC AS by the S-CSCF through a third-party registration when the user registers with the IMS, or the SC AS obtains it from the HSS according to the user's private user ID when receiving the third-party registration. When a user initiates a session, the SC AS anchors the session with the associated number. When the user initiates an inter-domain call transfer, the SC AS associates the anchored session with the associated number in the newly established session request and switches it.

Figure 2 is a schematic diagram of session transfer in a number sharing scenario. The number 123 is shared by UE 1 and UE2 at the same time. When UE 1 uses the number 123 to initiate a session with the remote UE3, UE 2 also uses the number 123 to initiate a session with the remote UE4. At this time, UE 2 may decide to use the current The session is switched to the CS domain.

Figure 3 is a flow chart of session transfer in the number sharing scenario. Both UE 1 and UE 2 are VCC users, which specifically includes the following steps:

301. There is a communication session between UE 1 and UE 3 in the packet domain. The service control signaling of the session service is anchored on the IMS network SC AS. The number of UE 1 is 123, and the number of UE 3 is 444, where The SC AS anchors the session with UE 1's associated number 111;

302. UE 2 and UE 4 also have a communication session in the packet domain. The service control signaling of the session service is also anchored on the IMS network SC AS. The number of UE 2 is shared with UE 1, which is 123. UE 4's number is 555, where the SC AS anchors the session with UE 2's associated number 222;

303. At this time, UE 2 may wish to transfer the current session to the circuit domain due to air interface wireless quality or user movement;

304. UE 2 executes a standard attach procedure on the target circuit domain network;

305. After successfully attaching, UE 2 sends a call establishment request message to the circuit domain network, and the message includes the user identity and the called number. The called number is set to the statically configured session transfer number (Session Transfer Number, STN) of the terminal;

Among them, the STN is mainly used for routing and identifying session transfer. When the CS domain core network receives a call establishment request message, it routes the session request to the SC AS of the UE 2 home network according to the STN. After the SC AS receives the session request, it The STN judges that this session request is for session switching and replaces the original session, see steps 306-311 for details.

306. The MSC Server (mobile switching center server) receives the call establishment request message of UE 2, and according to the analysis of the STN number, sends an address initial message to UE 2's home domain IMS network MGCF, which includes the called number and calling number , where the called number is STN, and the calling number is set as the associated number of UE 2.

There are usually two ways for MSC Server to obtain the associated number. One way is that in step 304, HSS sends the associated number (C-MSISDN) to MSC Server as the user number; The intelligent service replaces the associated number (C-MSISDN) with the user's calling number;

307. After the MGCF receives the address initial message, it packs a SIP (Session Initial Protocol, Session Initial Protocol) session invitation message, the target address in the message is STN, and sends it to the SC AS;

308. The SC AS receives the session invitation message, judges that the session invitation message is a session transfer request message according to the target address in the message being STN, and finds the previously anchored UE 2 according to the calling number in the message, that is, the associated number of UE 2 packet domain session;

309. The SC AS updates the remote UE 4 media peer IP address and port address to the IP address and port number of the new session;

310. After the remote update is successful, the SC AS releases the original packet domain session;

311. The SC AS returns a session success message to UE 2, indicating that the session transfer is successful.

In the above scenario, if UE1 initiates a normal call process, there will be problems, as shown in Figure 4, including:

401. UE 1 initiates an attach process on the CS network;

402. UE 1 initiates a call in the CS domain, and sends a call setup message to the MSC Server, and the called number carried in the message is UE 2's number;

403. The MSC Server receives the call setup message from UE1, triggers the intelligent service, and obtains the IP Multimedia Routing Number (IMRN for short) from the SC AS where the user belongs, and the message carries the called number (that is, the number of UE2) .

404. After successfully obtaining the IMRN, the MSC Server sends an address initial message to the user's home IMS network according to the IMRN, and the message carries the calling number and the called number, wherein the calling number is the associated number of UE1, and the called number is the IMRN;

405. After receiving the address initial message, the MGCF packs a SIP (Session Initial Protocol, SIP for short) session invitation message, and the target address in the message is IMRN, and sends it to the SC AS;

406. The SC AS receives the session invitation message, associates the original called number in step 403 according to the IMRN in the message, and sets the called number in the session invitation message as the original called number, and the SC AS sends a message to the called UE (ie UE2) Forwarding the session invitation, the calling number in the session invitation message forwarded to the called UE (i.e. UE2) is an associated number;

407. Session response.

In the above process, in step 406, the calling number in the session invitation message forwarded by the SC AS to UE2 is an associated number, and the associated number is a number associated with a session generated inside the network. There is still a difference between the associated number and the user number. According to the above steps, the calling number received by the called UE is an associated number, which affects services such as calling number display and calling blacklist of the called user.

In the above scenario, there are also problems when UE1 is called, as shown in Figure 5, including:

501. UE 3 sends a session invitation message to UE 1, where the target address in the message is UE 1 user number 123;

502-504. After receiving the session invitation message, the S-CSCF determines that it is a CS domain user according to the target address in the message, and forwards the session invitation message to the MGCF;

505. The MGCF sends an address initial message to the target MSC Server according to the analysis of the called number 123, and the called number in the message is 123.

After the MSC Server receives the address initial message, it searches for the called party according to the called number 123, but under certain circumstances, as in the above step 306, the C-MSISDN acquisition method 1, the user number saved by the MSC Server is the user's associated number (C-MSISDN) 111, at this time, MSC Server will think that the user with number 123 is not within its jurisdiction, and reject the call, resulting in failure to page the user.

Contents of the invention

The technical problem to be solved by the present invention is to provide a number conversion method and a service continuity application server, so as to solve the problem of call origination and termination of a VCC user in a number sharing scenario.

In order to solve the above problems, the present invention provides a number conversion method, comprising:

The calling user initiates a call in the CS domain, and the CS domain core network sends a session invitation message to the Service Continuity Application Server (SC AS) to which the calling user belongs, and the SC AS receives the session invitation message, and sends the The calling number in the session invitation message is compared with the user data of the calling user, and after the calling number in the session invitation message is set according to the comparison result, the session invitation message is forwarded to the called user.

Further, the above method may also have the following features, the method further includes, after the SC AS receives the session invitation message, according to the calling number in the session invitation message, The location register obtains the user data of the calling user, or, after the SC AS receives the IP multimedia routing number request sent by the mobile switching center server in the circuit domain core network, according to the primary address in the IP multimedia routing number request The calling number obtains the subscriber data of the calling subscriber from the home location register to which the calling subscriber belongs.

Further, the above method may also have the following features, the user data includes the calling user's public user number table, or includes the calling user's public user number table and associated numbers, or includes the calling user The calling user's public subscriber number table, the associated number and the display number set by the calling user in the home location register.

Further, the above method may also have the following features, the SC AS setting the calling number in the session invitation message according to the comparison result includes: if the user data contains a display number and the calling number in the session invitation message The number is not the displayed number, and the SC AS sets the displayed number as the calling number in the session invitation message.

Further, the above method may also have the following characteristics, the public user number list includes a default number;

Setting the calling number in the session invitation message by the SC AS according to the comparison result includes: if the user data does not include a display number and the calling number in the session invitation message is not included in the public user number example table and the calling number is an associated number, the SC AS sets the default number in the public user number table as the calling number in the session invitation message.

Further, the above method may also have the following features, the SC AS setting the calling number in the session invitation message according to the comparison result includes: if the user data contains a display number and the calling number in the session invitation message The number is the display number, or, if the user data does not contain a display number and the calling number in the session invitation message is included in the public user number table, the SC AS retains the session invitation message The calling number in .

The present invention also provides a number conversion method, including: the calling user initiates a call to the called user in the circuit domain, the SC AS receives the session invitation message of the calling user, and transfers the purpose in the session invitation message to The address is compared with the number currently used by the called user, and after the destination address in the session invitation message is set according to the comparison result, the session invitation message is forwarded to the called user.

Further, the above method may also have the following feature, the SC AS obtains the number currently used by the called user from the home location register to which the called user belongs according to the destination address in the session invitation message.

Further, the above method may also have the following features, the SC AS setting the destination address in the session invitation message according to the comparison result includes: when the destination address in the session invitation message is the same as the number currently used by the called user At the same time, the SC AS sets the destination address in the session invitation message as the number currently used by the called user; when the destination address in the session invitation message is the same as the number currently used by the called user, The SC AS reserves the destination address in the session invitation message.

The present invention also provides a service continuity application server. The service continuity application server is configured to, when receiving a session invitation message sent by the circuit domain core The user data of the calling user is compared, and after the calling number in the session invitation message is set according to the comparison result, the session invitation message is forwarded to the called user.

Further, the above-mentioned business continuity application server may also have the following characteristics, the SC AS is configured to, after receiving the session invitation message, send the caller number from the calling party to which the calling user belongs according to the calling number in the session invitation message The home location register obtains the user data of the calling user, or is used for receiving the IP multimedia routing number request sent by the mobile switching center server in the circuit domain core network, according to the calling party in the IP multimedia routing number request The number obtains the subscriber data of the calling subscriber from the home location register to which the calling subscriber belongs.

Further, the above-mentioned service continuity application server may also have the following characteristics, the SC AS is configured to: when the user data contains a display number and the calling number in the session invitation message is not the display number, it will The display number is set as the calling number in the session invitation message.

Further, the above-mentioned business continuity application server may also have the following characteristics, the SC AS is configured to not include a display number in the user data and the calling number in the session invitation message is not included in the public user If the calling number is in the number list and the calling number is an associated number, the default number in the public user number list is set as the calling number in the session invitation message.

Further, the above-mentioned business continuity application server may also have the following characteristics, the SC AS is configured to include a display number in the user data and the calling number in the session invitation message is the display number, or, If the user data does not include a display number and the calling number in the session invitation message is included in the public user number list, retain the calling number in the session invitation message.

The present invention also provides a service continuity application server. The service continuity application server is configured to, when the calling user initiates a call to the called user in the circuit domain and receives a session invitation message from the calling user, The destination address in the session invitation message is compared with the number currently used by the called user, and after the destination address in the session invitation message is set according to the comparison result, the session invitation message is forwarded to the called user.

Further, the above-mentioned business continuity application server may also have the following characteristics, the SC AS is configured to obtain the current address of the called user from the home location register to which the called user belongs according to the destination address number in the session invitation message. number used.

Further, the above-mentioned service continuity application server may also have the following characteristics, the SC AS is used to invite the session invitation message when the destination address in the session invitation message is different from the number currently used by the called user The destination address in the message is set to the number currently used by the called user; when the destination address in the session invitation message is the same as the number currently used by the called user, the destination address in the session invitation message is reserved.

Using the present invention, in the number sharing scenario of the UE, the SC AS can solve the problems of call origination and call termination by converting the number.

Description of drawings

Figure 1 is a system reference frame for IMS session transfer;

Figure 2 is a schematic diagram of session transfer in an IMS number sharing scenario;

FIG. 3 is a flow chart of session transfer in an IMS number sharing scenario;

FIG. 4 is a flow chart of initiating a call under an existing IMS number sharing scenario;

FIG. 5 is a flow chart of call termination under the existing IMS number sharing scenario;

FIG. 6 is a flow chart of an embodiment of calling number conversion in the IMS number sharing scenario of the present invention;

Fig. 7 is a flow chart of an embodiment of terminal number conversion in the IMS number sharing scenario of the present invention.

Detailed ways

The technical solution of the present invention will be described in more detail below with reference to the drawings and embodiments.

The present invention provides a number conversion method, comprising: the calling user initiates a call in the circuit domain, the circuit domain core network sends a session invitation message to the SC AS to which the calling user belongs, and the SC AS sends the session invitation message in the session invitation message comparing the calling number with the user data of the calling user, setting the calling number in the session invitation message according to the comparison result, and then forwarding the session invitation message to the called user.

Wherein, after the SC AS receives the session invitation message, it obtains the user data of the calling user from the home location register to which the calling user belongs according to the calling number in the session invitation message; or, the After the SC AS receives the IP multimedia routing number request sent by the mobile switching center server, it obtains the user name of the calling user from the home location register to which the calling user belongs according to the calling number in the IP multimedia routing number request. data.

The user data includes the public subscriber number list of the calling user, or includes the public subscriber number list and associated numbers of the calling user, or includes the public subscriber number list and associated numbers of the calling user and the display number set by the calling party in the home location register, and the public subscriber number list includes a default number.

The SC AS compares the calling number in the session invitation message with the user data of the calling user, and setting the calling number in the session invitation message according to the comparison result specifically includes:

If the user data includes a display number and the calling number in the session invitation message is not the display number, the SC AS sets the display number as the calling number in the session invitation message;

If the user data does not contain a display number and the calling number in the session invitation message is not included in the public user number example table and the calling number is an associated number, the SC AS adds the public user number example The default number in the table is set to the calling number in the session invitation message;

If the user data contains a display number and the calling number in the session invitation message is the display number, or, if the user data does not contain a display number and the calling number in the session invitation message contains In the public user number example table, the SC AS reserves the calling number in the session invitation message.

The present invention also provides a number conversion method, including: the calling user initiates a call to the called user in the circuit domain, the SC AS receives the session invitation message of the calling user, and transfers the purpose in the session invitation message to The address is compared with the number currently used by the called user, and after the destination address of the session invitation message is set according to the comparison result, the session invitation message is forwarded to the called user.

The destination address of the session invitation message set by the SC AS according to the comparison result includes:

When the destination address in the session invitation message is different from the number currently used by the called user, the SC AS sets the destination address in the session invitation message as the number currently used by the called user; for example, the When the number currently used by the called user is an associated number, the SC AS sets the destination address in the session invitation message as the associated number of the called user;

When the destination address in the session invitation message is the same as the number currently used by the called user, the SC AS retains the destination address in the session invitation message.

Wherein, after the SC AS receives the session invitation message, according to the destination address number in the session invitation message, the number currently used by the called user is obtained from the home location register to which the called user belongs.

Embodiment one

Fig. 6 is the signaling process of number switching and calling in the IMS number sharing scenario according to the embodiment of the present invention. The SC AS receives the session invitation message and judges whether the calling number in the message needs to be replaced. If it needs to be replaced, the The calling number is replaced and forwarded to the called party, including:

601. UE1 initiates an attach process on the CS network;

602. UE1 initiates a call in the CS domain, and sends a call establishment message to the MSC Server, and the called number carried in the message is the UE 2 number;

603. The MSC Server receives the call setup message from UE1, triggers the intelligent service, and sends an IP Multimedia Routing Number (IP Multimedia Routing Number, IMRN) request message to the user's home SC AS, and the message carries the called number (that is, the UE2 number) and calling number;

604. After successfully obtaining the IMRN, the MSC Server sends an address initial message to the user's home IMS network according to the IMRN, and the message carries the calling number and the called number, wherein the calling number is the associated number of UE1, and the called number is the IMRN;

605. After the MGCF receives the address initial message, it packs a SIP session invitation message, and the target address in the message is IMRN, and sends it to the SC AS;

606. The SC AS receives the session invitation message, associates the original called number in step 503 according to the IMRN in the message, and sets the called number in the session invitation message as the original called number, and the SC AS obtains the calling number in the session invitation message number, and obtain the user's public user number (Public User Identities, PUI) list, associated number and display number set by the user in the HSS from the HSS to which the user belongs according to the calling number.

The displayed number refers to the number displayed by the other party when the user calls other users; the PUI example table includes user numbers in two formats, SIP URI (Universal Resource Identities, URI) and Tel URI, and the PUI example table Also contains a default number.

607. The HSS returns user data to the SC AS;

608. After the SC AS successfully obtains the user data, compare the calling number in the session invitation message with the user data, and set the calling number in the session invitation message according to the result, specifically including:

The SC AS judges whether the user data includes a display number:

If the user data contains the display number, the SC AS continues to judge whether the caller number in the received session invitation message is the same as the display number, if not, the SC AS sets the display number as the caller number in the session invitation message ; If they are the same, keep the calling number in the session invitation message;

If the user data does not include the display number, the SC AS continues to judge whether the calling number in the received session invitation message is included in the PUI example table, and if so, does not replace the calling number, that is, retains the calling number in the session invitation message number; if the calling number is not included in the PUI example table, and the calling number is an associated number, the SC AS sets the default number in the PUI example table as the calling number in the session invitation message;

609. The SC AS forwards the session invitation message to the remote UE (that is, UE2);

610. Conversation response.

In another embodiment of the present invention, after receiving the IP multimedia routing number request message in step 603, the SC AS may also request the user data of the calling user from the HSS according to the calling number in the request message.

In yet another embodiment of the present invention, the user data requested by the SC AS from the HSS may only include a user number and an associated number. When the calling number in the session invitation message is the associated number, the SC AS directly sends the session invitation message Set the calling number in the user ID as the user number.

Embodiment two

Fig. 7 is the number conversion termination call signaling flow in the second IMS number sharing scenario of the present invention, the SC AS receives the termination call session invitation message, and obtains the called user's ID from the HSS to which the called user belongs according to the called number in the message The associated number and the number currently used by the user. If the currently used number is an associated number, the SC AS changes the destination address in the received final call message to an associated number, specifically including:

701. UE 3 calls UE 1 through the subscriber number of UE 1;

702. The I-CSCF/S-CSCF forwards the session invitation message to the SC AS;

703. The SC AS obtains the number currently used by the called user from the HSS to which the called user belongs according to the destination address in the session invitation message, and also obtains the associated number of the called user from the HSS;

704. The HSS returns the number currently used by the called user, and may also return the associated number of the called user;

705. After the SC AS obtains the currently used number successfully, it compares the destination address in the session invitation message with the number currently used by the called user, and sets the destination address in the session invitation message according to the comparison result;

Specifically comprising: when the destination address in the session invitation message is different from the number currently used by the called user, the SC AS sets the destination address in the session invitation message as the number currently used by the called user; For example, when the number currently used by the called user is an associated number, the SC AS sets the destination address in the session invitation message as the associated number of the called user;

When the destination address in the session invitation message is the same as the number currently used by the called user, the SC AS retains the destination address in the session invitation message.

In this embodiment, the number currently used by the user is an associated number, and the destination address in the session invitation message is set as the associated number;

706-707. After the conversion is successful, the SC AS sends the converted session invitation message to the called side network;

708. The MSC Server at the called side receives the address initial message, finds the location of the user according to the user associated number, and initiates a call establishment request message to UE 1;

709. The called UE 1 connects to the session and talks with UE 3.

The present invention also provides a service continuity application server. The service continuity application server is configured to, when receiving a session invitation message sent by the circuit domain core The user data of the calling user is compared, and after the calling number in the session invitation message is set according to the comparison result, the session invitation message is forwarded to the called user.

Wherein, the SC AS is configured to, after receiving the session invitation message, obtain the user data of the calling user from the home location register to which the calling user belongs according to the calling number in the session invitation message, Or, after receiving the IP multimedia routing number request sent by the mobile switching center server in the circuit domain core network, obtain it from the home location register to which the calling user belongs according to the calling number in the IP multimedia routing number request User data of the calling user.

Wherein, the SC AS is configured to set the displayed number as the displayed number in the session invitation message when the user data contains the displayed number and the calling number in the session invitation message is not the displayed number Calling number; it is also used to set The default number in the public user number list is set to the calling number in the session invitation message; it is also used to include a display number in the user data and the calling number in the session invitation message is the display number , or, if the user data does not include a display number and the calling number in the session invitation message is included in the public user number list, retain the calling number in the session invitation message.

The present invention also provides a service continuity application server. The service continuity application server is configured to, when the calling user initiates a call to the called user in the circuit domain and receives a session invitation message from the calling user, The destination address in the session invitation message is compared with the number currently used by the called user, and after the destination address in the session invitation message is set according to the comparison result, the session invitation message is forwarded to the called user.

Wherein, the SC AS is configured to set the destination address in the session invitation message as the number currently used by the called user when the destination address in the session invitation message is different from the number currently used by the called user. number; when the destination address in the session invitation message is the same as the number currently used by the called user, retain the destination address in the session invitation message.

Wherein, the SC AS is configured to obtain the number currently used by the called user from the home location register to which the called user belongs according to the destination address number in the session invitation message.

Of course, the present invention can also have other various embodiments, and those skilled in the art can make various corresponding changes and deformations according to the present invention without departing from the spirit and essence of the present invention, but these corresponding Changes and deformations should belong to the scope of protection of the appended claims of the present invention.

Claims (17)

1. A number conversion method, characterized in that, comprising: The calling user initiates a call in the CS domain, and the CS domain core network sends a session invitation message to the Service Continuity Application Server (SC AS) to which the calling user belongs, and the SC AS receives the session invitation message, and sends the The calling number in the session invitation message is compared with the user data of the calling user, and after the calling number in the session invitation message is set according to the comparison result, the session invitation message is forwarded to the called user. 2. The method according to claim 1, further comprising: after the SC AS receives the session invitation message, according to the calling number in the session invitation message, from the calling party The home location register to which the user belongs obtains the user data of the calling user, or, after the SC AS receives the IP multimedia routing number request sent by the mobile switching center server in the circuit domain core network, according to the IP multimedia routing number The calling number in the request obtains the subscriber data of the calling subscriber from the home location register to which the calling subscriber belongs. 3. The method according to claim 1 or 2, characterized in that, the user data includes the public subscriber number list of the calling user, or includes the public subscriber number list and associated numbers of the calling subscriber , or include the public subscriber number table of the calling user, the associated number and the display number set by the calling user in the home location register. 4. The method according to claim 3, wherein the SC AS setting the calling number in the session invitation message according to the comparison result comprises: if the user data contains a display number and the session invitation message The calling number in is not the displayed number, and the SC AS sets the displayed number as the calling number in the session invitation message. 5. The method of claim 3, wherein, The public user number list includes a default number; Setting the calling number in the session invitation message by the SC AS according to the comparison result includes: if the user data does not include a display number and the calling number in the session invitation message is not included in the public user number example table and the calling number is an associated number, the SC AS sets the default number in the public user number table as the calling number in the session invitation message. 6. The method of claim 3, wherein, The SC AS setting the calling number in the session invitation message according to the comparison result includes: if the user data contains a display number and the calling number in the session invitation message is the display number, or, if the The user data does not include a display number and the calling number in the session invitation message is included in the public user number list, and the SC AS reserves the calling number in the session invitation message. 7. A number conversion method, characterized in that it comprises: the calling user initiates a call to the called user in the circuit domain, the SC AS receives the session invitation message of the calling user, and transfers the session invitation message in the session invitation message The destination address of the user is compared with the number currently used by the called user, and after the destination address in the session invitation message is set according to the comparison result, the session invitation message is forwarded to the called user. 8. The method according to claim 7, wherein the SC AS obtains the number currently used by the called user from the HLR to which the called user belongs according to the destination address in the session invitation message. 9. The method according to claim 7 or 8, wherein the SC AS setting the destination address in the session invitation message according to the comparison result comprises: when the destination address in the session invitation message is the same as the When the numbers currently used by the calling user are different, the SC AS sets the destination address in the session invitation message as the number currently used by the called user; when the destination address in the session invitation message is different from the current number of the called user When the numbers used are the same, the SC AS retains the destination address in the session invitation message. 10. A business continuity application server, characterized in that, The business continuity application server is configured to compare the calling number in the session invitation message with the user data of the calling user when receiving the session invitation message sent by the circuit domain core network, and set After the calling number in the session invitation message is forwarded, the session invitation message is forwarded to the called user. 11. The business continuity application server according to claim 10, wherein the SC AS is configured to, after receiving the session invite message, send the call from the caller ID according to the caller number in the session invite message. Calling the home location register to which the user belongs to obtain the user data of the calling user, or for receiving the IP multimedia routing number request sent by the mobile switching center server in the circuit domain core network, according to the IP multimedia routing number request The calling number in obtains the subscriber data of the calling subscriber from the home location register to which the calling subscriber belongs. 12. The business continuity application server according to claim 10, wherein the SC AS is configured to include a display number in the user data and the calling number in the session invitation message is not the display number When the number is displayed, the displayed number is set as the calling number in the session invitation message. 13. The business continuity application server according to claim 10, characterized in that, The SC AS is configured to: when the user data does not include a display number and the calling number in the session invitation message is not included in the public user number list and the calling number is an associated number, set The default number in the public subscriber number list is set to the calling number in the session invitation message. 14. The business continuity application server according to claim 10, characterized in that, The SC AS is configured to include a display number in the user data and the calling number in the session invitation message is the display number, or, if the user data does not contain a display number and the session invitation When the calling number in the message is included in the public user number list, the calling number in the session invitation message is reserved. 15. A business continuity application server, characterized in that, The business continuity application server is configured to, when the calling user initiates a call to the called user in the circuit domain and receives the calling user's session invitation message, combine the destination address in the session invitation message with the called The number currently used by the user is compared, and after the destination address in the session invitation message is set according to the comparison result, the session invitation message is forwarded to the called user. 16. The business continuity application server according to claim 15, wherein the SC AS is configured to obtain the HLR to which the called user belongs according to the destination address number in the session invitation message The number currently used by the called user. 17. The business continuity application server according to claim 15 or 16, wherein the SC AS is configured to use when the destination address in the session invitation message is different from the number currently used by the called user , setting the destination address in the session invitation message to the number currently used by the called user; when the destination address in the session invitation message is the same as the number currently used by the called user, retain the session invitation message The destination address in .

Images