WO2007137502A1

WO2007137502A1 - Method, device and system for cross-domain receiving service

Info

Publication number: WO2007137502A1
Application number: PCT/CN2007/001631
Authority: WO
Inventors: Jie Xu; Wenyu Liu; Yan Li
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2006-05-29
Filing date: 2007-05-18
Publication date: 2007-12-06

Abstract

A method, device and system for cross-domain receiving service, when a user registers in a certain domain, the service request from another domain is jointed to the user, to realize the cross-domain receiving service. Further, it is used to solve the problems that users have no right to select networks, and when the user terminal joints the new service, it can't process the running original session. The method in the present invention includes: A, when the VCC AS receives a service request from one domain pointing to the user terminal registered in another domain, informing the user terminal; B, the user terminal determines that the presupposition is met, it turns into the initiation domain of the service request; C, VCC AS, the initiation domain of the service request, associating the said service with the user terminal to put the service through.

Description

Method, device and system for receiving service across domains

The present invention relates to the field of communications, and in particular, to a method, apparatus, and system for receiving services across domains. Background technique

In the process of wireless network evolution from 2G network to 3G network, 3G network and 2G network will coexist for a long period of time. In the case of such a dual network coexistence, interoperability between dual networks becomes a research to be studied. Question.

In order to solve the above problems, the 3GPP2 standards organization proposed an architecture called Voice Call Continuity (VCC). The schematic diagram of the architecture is shown in Figure 1.

Two network elements have been added to this architecture, one is the voice call continuity application server VCC AS, and the other is the short message gateway SMS-GW. The SMS-GW is used for interworking of short messages, and has nothing to do with the present invention. A VCC AS is a network entity of an IMS domain, but interfaces with some network elements of the CS domain. It is used to assist the domain where the decision routing is located when the called route is used; it is anchored in the call path when the user conducts the voice call service, and assists in the handover between the IMS domain and the CS domain.

In the IMS domain, the VCC AS is an AS (Application Server) that is aware of the registration status of the user in the IMS domain and is located in the SIP (Session Initiation Protocol) of the user as a Back to Back User Agent (B2BUA). , Session Initiation Protocol) In the session path, the SIP session can be controlled.

In the CS domain, the VCC AS is an SCP (Service Control Point), and the user's call in the CS domain is triggered by it and controlled by it.

According to the 3GPP2 standard procedure, all calls to the subscriber, including lx voice calls, need to be routed to the IMS domain, via VCC AS anchor control.

The VCC architecture defined by the 3GPP standards organization is similar to the above, except that the VCC AS is subdivided into four functional units. The external functions of the VCC AS are relatively consistent. I will not introduce it here. Although vcc is used to solve the dual-network interoperability problem of voice calls, it is also applicable to other multimedia real-time services such as video telephony VT (Video Telephone) services that occur in the IMS domain.

In the VCC architecture of the 3GPP2, the user is allowed to switch to the IMS domain during the voice call in the CS domain. For the specific switching process, see Figure 2.

The user has established a voice call in the CS domain. At the signaling level, the MGCF is between the CS domain and the IMS domain, which plays a signaling role. The VCC AS is anchored between the two ends of the call, and plays B2BUA (Back to Back User Agent Back-to-back User Agent). At the bearer level, the MGW is between the TDM and the IP bearer, acting as a media switch. At this time, the user initiates a switch to the IMS domain:

1. If the user has not registered in the IMS domain, the registration process needs to be initiated first;

2. After the registration is completed, the terminal initiates a SIP session, and the called user ID of the session is the device identifier of the VCC AS.

3. After receiving the SIP session request, the S-CSCF triggers the session to the VCC AS by means of service triggering.

4. The VCC AS initiates a session attribute change process to the calling peer, and causes the call peer to change the media stream connection to the switching user's IMS domain;

5. The call peer returns a successful response, and the VCC AS also returns a session response response to the terminal.

6. The terminal sends an ACK message to connect to the new call;

7. After the VCC AS learns that the new call has been connected, it sends a BYE message to translate the original session to the CS domain;

8. The MGCF releases the BYE to the ISUP RLS message to release the CS domain session;

The follow-up is the normal session release process, which is not repeated here. After the process is completed, the user continues to talk in the IMS domain and the original caller.

The above handover procedure is currently limited to the VCC standard of 3GPP2, and can be applied only when the WLAN accesses the IMS domain. When the CDMA packet network (DO network) accesses the IMS domain, it is not yet There is a standard process of cutting from the CS domain. The reason is that the terminal cannot access the DO network and the CS network (IX network) at the same time. Therefore, if switching from the CS network to the DO network, it is necessary to have a long interruption effect on the ongoing voice call. The user feels bad, so it is not desirable. A solution that has been proposed is to insert a media resource function (MRF) entity in the call path. When the user starts switching, the caller is placed on the call waiting tone until the user re-accesses from the IMS domain. Resume and call the opposite end of the call, so that the user's feelings will be better.

When a user makes a voice call in the CS domain, a video call from the IMS domain needs to be connected to the user. How does VCC AS handle this? The existing 3GPP2 VCC solution provides a process for a user to receive an IMS domain VoIP call in the CS domain. As shown in FIG. 3, the following steps are included:

1. The call comes from the peer to the CSCF entity of the IMS domain where the called user is located;

2. The CSCF triggers the call to the VCC AS by means of service triggering.

3. When the VCC AS detects that the user is in the CS domain, the decision needs to connect the user in the CS domain, and then sends a message to the CS domain HLR to request the user location.

The subsequent step is the normal CS domain voice called flow, which is not repeated here.

The above 3GPP2 solution is to transfer the VoIP call to the CS domain and become a CS domain voice call for connection. It can only solve the problem that the second call is a VoIP call. If the second call is a video call, the video part of the media stream cannot be carried in the CS domain, so the 3GPP2 standard solution cannot solve the problem of video telephony.

Moreover, the above 3GPP2 solution does not mention whether to maintain the original CS domain session.

In the area where the HRPD network overlaps with the CDMA lx network (sometimes written as the lx network in this paper), in order to solve the problem that the user can receive the voice call from the lx network when the user resides under the HRPD network, the standard proposes a cross-paging technology, that is, When the MS resides in a network, it can receive paging from other networks, and the user can choose whether to answer a new call.

In order to achieve cross-paging, an A1/A1P interface between the HRPD AN (access network, sometimes abbreviated as AN) and MSC/MSCe (mobile switching center) is added to the original HRPD IOS standard. After the HRPD network, the AN passes the A1/A1P interface to the MSC/MSCe. The location is registered so that the MSC (Mobile Switch Center) knows which AN the terminal is located on. When the service paging of the HRPD network needs to be sent to the terminal through the lx network, the AN will request the MSC/MSCe, and then the MSC/MSCe delivers the paging to the terminal through the lx network; likewise, when the paging of the lx network When the HRPD network is to be delivered to the terminal, the MSC/MSCe sends the lx page to the terminal through the CSNA (Circuit Service Notification Application) of the HRPD network. The premise of realizing the above functions is that the location registration of the terminal in the HRPD network and the location registration of the terminal in the lx network are all registered on the same MSC/MSCe.

However, in the above cross-paging scheme, the user does not have the right to select the network, which results in insufficient flexibility. For example, if the user wants to preset to not answer the lx call when performing video service under HRPD, the user cannot refuse to answer the lx call because the user does not have the right to select the network.

In order to enable users to receive voice calls from the lx network when the user resides in the HRPD network, another implementation is proposed to convert the voice call of the lx network into VoIP (Voice over IP) and connect to the user in the HRPD network. .

However, the voice quality and service effect of the voice service carried by the IP is not as good as that of the voice service carried by the circuit domain, which causes the received voice call from the lx network to deteriorate in quality, which is undesirable for people to see. . In addition, there is still a problem that the operator's existing circuit domain equipment needs to be modified, that is, it is a great waste for the operator's existing investment in the circuit domain.

Therefore, there is a need for a solution for receiving voice services across domains, which can solve the problems in the related art described above. Summary of the invention

The present invention provides a method, apparatus, and system for receiving services across domains, for when a user terminal is registered in a certain domain, a service request arriving from another domain is connected to the user to implement cross-domain reception.

Further, the problem that the user in the prior art does not select the network and the problem that the current session that is currently in progress cannot be processed when the user terminal connects to the newly arrived service is solved. The method of the present invention includes the following steps: A. When the voice call continuity application server VCC AS receives a service request arriving from one domain and points to a user terminal registered in another domain, notifying the user terminal; B. the user terminal determines to satisfy The preset condition is transferred to the originating domain of the service request; C. The VCC AS associates the service with the user terminal in the originating domain of the service request to connect to the service.

The VCC AS entity of the present invention is configured to perform call anchoring and domain switching, and the VCC AS entity further includes: a determining module, configured to determine whether the user terminal pointed to by the service request arriving from one domain is currently registered in another domain, If yes, a trigger signal is sent; a notification module, configured to send a notification message to the user terminal after receiving the trigger signal sent by the determining module; and an association module, configured to: when the user terminal transfers the service request After the domain is initiated, the service is associated with the user terminal to connect to the service.

The user terminal of the present invention is capable of accessing and conducting a call service under a plurality of networks, and the user terminal further includes: a network interface module, configured to receive a notification from the network side, where the notification indicates that a service request arrives from a certain domain; And interacting with the network side; the control module determines, according to the preset condition, whether to receive the arrived service, and provides the processing result to the network interface module, and controls the user terminal to transfer when determining to receive the arrived service The originating domain of the service request.

The system for receiving services in a cross-domain manner includes: a voice call continuity application server VCC AS, configured to notify the user terminal when receiving a service request arriving from one domain and pointing to a user terminal registered in another domain; The initiating domain of the service request associates the service with the user terminal to connect to the service; and the user terminal is configured to transfer to the originating domain of the service request when determining that the preset condition is met.

When the user terminal is registered in a certain domain and the service request of another domain needs to be connected to the user terminal, the method of the present invention enables the network entity and the terminal to cooperate together, and the user terminal is transferred to the location according to various policies and methods. The originating domain of the service request receives the service. In the case that the user terminal has other services in the original registration domain, the present invention also provides various schemes for the network, the user terminal, or the user to make a session priority decision by itself, and determines whether to continue the newly arrived service according to the session priority. Through the invention, the user can receive services from other domains when only one domain is registered, which improves the service connection rate and enhances the user experience.

In order to support the method of the present invention, the present invention also provides a VCC AS entity, a user terminal, and a corresponding system for receiving services across domains. DRAWINGS

Figure 1 is a schematic diagram of a voice call continuity VCC architecture;

Figure 2 shows the signaling of an existing user to switch to the IMS domain during a voice call in the CS domain.

3 is a signaling flowchart of an existing user receiving an IMS domain VoIP call in a CS domain; FIG. 4 is a schematic structural diagram of a VCC AS entity according to the present invention;

FIG. 5 is a schematic structural diagram of Embodiment 1 of a user terminal according to the present invention;

6 is a schematic structural diagram of Embodiment 2 of a user terminal according to the present invention;

Figure 7 is a schematic structural view of the system of the present invention;

Figure 8 is a flow chart of the method steps of the present invention;

9 is a flow chart of steps performed on a VCC AS in an embodiment of the present invention;

FIG. 10 is a flowchart of steps performed on a user terminal according to an embodiment of the present invention;

11 is a signaling flowchart of Embodiment 1 of a method according to the present invention;

12 is a signaling flowchart of Embodiment 2 of a method according to the present invention;

13 is a signaling flowchart of Embodiment 3 of a method according to the present invention;

14 is a signaling flowchart of Embodiment 4 of a method according to the present invention;

15 is a signaling flowchart of Embodiment 5 of a method according to the present invention;

16 is a signaling flowchart of Embodiment 6 of a method according to the present invention;

17 is a signaling flowchart of Embodiment 7 of the method according to the present invention;

18 is a signaling flowchart of Embodiment 8 of the method according to the present invention;

19 is a signaling flowchart of Embodiment 9 of a method according to the present invention;

20 is a signaling flowchart of Embodiment 10 of the method according to the present invention;

21 is a signaling flowchart of Embodiment 11 of the method according to the present invention; 22 is a signaling flowchart of Embodiment 12 of the method according to the present invention;

23 is a signaling flowchart of Embodiment 13 of the method according to the present invention;

FIG. 24 is a signaling flowchart of Embodiment 14 of the method according to the present invention. detailed description

In order to connect a service request arriving from another domain to the user when the user terminal is registered in a certain domain, the cross-domain reception service is implemented.

The present invention provides a VCC AS entity having a call anchoring and domain switching function. Referring to FIG. 4, the method further includes: an association module, and a judging module and a notification module connected to each other; further comprising: call holding Module.

The determining module is configured to determine whether the user terminal pointed to by the service request arriving from one domain is currently registered in another domain, and if yes, issue a trigger signal. The further determining module may further detect whether the user terminal is currently performing services in another domain after receiving the service request; when detecting that the user terminal is currently performing services in another domain, determining whether the session priority is based on the session priority A trigger signal is issued.

The notification module is configured to send a notification message to the user terminal after receiving the trigger signal sent by the determining module.

The association module is configured to associate the service with the user terminal to connect to the service after the user terminal transits to the originating domain of the service request. The specific mode is: the association module initiates a first session from the initiating domain of the service request to the user terminal, and forwards the service request to the user terminal, and the user terminal moves to the originating domain of the service request. Connect to the business. Or the notification module generates a first special number that uniquely corresponds to the arrived service request, and is carried in a notification sent to the user terminal; and the association module identifies that the user terminal turns to the initiation of the service request When the second session initiated by the domain carries the first special number, the second session is associated with the arrived service according to a unique correspondence between the first special number and the arrived service request, to Connect to the business.

The call holding module is configured to mark the currently ongoing service, and at the user terminal When the service is interrupted, the session to the opposite end of the service is maintained. There are two ways to maintain the session to the currently ongoing service peer: Method 1: Insert the MRF in the session path, and instruct the MRF to complete the playback and call waiting control; or, the second mode, to the current ongoing The peer end of the service sends a session update indication indicating that the media stream direction is changed to one-way or two-way blocking.

After the two methods are used to maintain the ongoing session of the service peer, the service currently being performed by the terminal can be switched to the initiated domain of the incoming service request. In the specific implementation, at least the following three implementation scenarios exist:

The notification module generates a second special number uniquely corresponding to the currently ongoing service, and is carried in a notification sent to the user terminal; and the association module identifies that the user terminal transfers to the service request When the second special number is carried in the first switching session initiated by the initiating domain, according to the correspondence between the second special number and the currently ongoing service, the first switching session and the current The ongoing services are associated at the signaling level.

Second, the association module initiates a third session to the user terminal, to forward the currently ongoing service to the user terminal; and after the user terminal receives the third session, the current session is The opposite end of the performed service is associated with the user terminal at the signaling level.

The association module associates the first session, the session to the peer that is currently performing the service, and the session to the peer that arrives at the service.

In order to cooperate with the above VCC AS entity, the present invention also provides a user terminal. In the specific scenario, the user terminal is not registered in the originating domain of the arrived service request, or the network currently located by the user terminal cannot be connected to the arrived service request.

Referring to FIG. 5, the first embodiment of the user terminal includes: a network interface module and a control module that are connected to each other; and a new session initiation module that is respectively connected to the network interface module and the control module, and is connected to the control module. The switching module, the switching session initiation module respectively connected to the network interface module and the switching module, and the conversion module connected to the switching module.

The network interface module is configured to receive a notification from a network side, where the notification indicates that a service request arrives from a certain domain; and interacts with the network side.

The control module determines, according to a preset condition, whether to receive the arrived service, and ―

The processing result is provided to the network interface module, and when it is determined to receive the arrived service, the user terminal is controlled to transfer to the originating domain of the service request. The preset condition by which the control module is based is one of the following: The control module processes according to the service indication carried in the notification; the control module first detects whether the user terminal is performing services in another domain, according to which the session priority is processed; the control module will The notification is presented to the user and processed according to the user's selection.

The new session initiating module is configured to: after the control module controls the user terminal to transfer to the initiating domain of the service request, receive the network interface module from the second session initiated by the network interface module to the network side Get the first special number in the notification. Corresponding to the specific manner of processing the associated module in the VCC AS entity, the VCC AS entity is connected to the arrived service.

The switching module is configured to switch the service currently being performed by the user terminal to the originating domain of the service request. That is, when the user terminal is performing services in another domain, and the control module determines that the arrived service should be received according to a preset condition, the currently performing service is processed by the switching module.

The switching session initiating module is configured to carry the network interface in a first switching session initiated by the network interface module to the network side after the switching module transfers the service currently being performed by the user terminal to the initiating domain of the service request The module gets the second special number from the notification received. Corresponding to the first case in the specific implementation of the call holding module in the VCC AS entity, the VCC AS entity completes the switching between the currently ongoing service and the arrived service.

The conversion module is configured to: after the switching module transfers the service currently being performed by the user terminal to the originating domain of the service request, using a session update indication, indicating that the VCC AS or the MRF is in the ongoing service and the Converting between the arriving services (corresponding to the third case in the specific implementation of the call holding module in the VCC AS entity); or modifying the currently ongoing service and the media of the arrived service by using a session update indication The flow direction is used to implement a transition between the currently ongoing service and the arrived service (corresponding to the first case and the second case in the specific implementation of the call holding module in the VCC AS entity).

♦ Embodiment 2 of the user terminal, as shown in FIG. 6, includes: a network interface module and a control module that are connected to each other; and further comprising: a network interface module and a control module respectively connected A new session initiation module, and an abort module connected to the control module.

The network connection module, the control module, and the new session initiation module are the same as the user terminal embodiment 1.

The suspension module is configured to suspend a service currently being performed by the user terminal. That is, when the user terminal is performing services in another domain, and the control module determines that the arrived service should be received according to a preset condition, the currently ongoing service is processed by the suspension module.

In combination with the VCC AS entity and the user terminal, the present invention further provides a system for receiving services across domains, as shown in FIG. 7, which includes: a VCC AS entity (ie, the VCC AS entity of the present invention described above), and a user terminal. (i.e., the user terminal of the present invention described above includes an embodiment of two user terminals).

The VCC AS entity, configured to notify the user terminal when receiving a service request arriving from one domain to a user terminal registered in another domain; and in the originating domain of the service request, the service and the The user terminal is associated to connect to the service.

The user terminal is configured to transfer to the origin of the service request when it is determined that the preset condition is met.

Applying the above VCC AS entity, user terminal and system, the present invention provides a method for receiving services across domains, as shown in Figure 8, which includes the following main steps:

S1. The VCC AS receives a service request arriving from one domain and points to a user terminal registered in another domain.

The service request arriving from a domain is not limited to a service request arriving from the IMS domain; the domain registered by the user terminal is not limited to the CS domain.

S2, the VCC AS notifies the user terminal.

♦ The VCC AS detects the current state of the user terminal, and if the user terminal is currently in an idle state, the VCC AS directly notifies the user terminal.

♦ The VCC AS detects the current state of the user terminal, and if the user terminal is currently performing services, the VCC AS directly notifies the user terminal, or according to the service currently being performed by the user terminal and the requested service request. The level of priority is handled accordingly. The VCC AS determines whether the priority of the VCC AS can be based on the user's intention, the operator's configuration, the network status, and the like. The network status determines whether the current network capability of the user terminal can connect to the arrived service.

The corresponding processing is performed, including:

- If the priority of the currently ongoing service of the user terminal is higher, the VCC AS rejects the service request that is reached. When the VCC AS rejects the incoming service request, it can also notify the user terminal that the network side has performed the reject operation.

- If the priority of the arriving service request is higher, the VCC AS notifies the user terminal to turn on the incoming service request.

In this step, if the VCC AS determines whether the incoming service is turned on, and the result of the determination is that the V200 AS sends a notification to the user terminal, the notification sent by the VCC AS to the user terminal carries an originating field indicating that the user terminal transfers to the service request. Instructing to turn on the incoming service request; further if the user terminal is currently performing a service, but the priority of the arrived service request is higher, the notification may further carry the service that is being performed on the user terminal. The processing indication is to suspend the ongoing service or to switch the ongoing service to the originating domain of the service request. Or, notify the network side that a rejection has been performed.

In this step, if the user terminal determines whether to turn on the incoming service, the notification sent by the VCC AS to the user terminal does not carry the indication that the service request is received, but needs to carry at least the notification. Business type and calling number.

The manner of notifying the user terminal may be a short message in the CS domain, which may be a playback, may be a flash message, may be USSD signaling, or may be an INFO, MESSAGE, NOTIFY message, etc. in the IMS domain, or may be It is playback.

S3. When the user terminal determines that the preset condition is met, the user terminal transfers to the originating domain of the service request. After the user terminal receives the notification,

♦ If the user terminal is currently in an idle state, and the notification does not carry the indication that the service request is received, the user terminal directly provides the notification to the user, and the user selects whether to accept the arrived service; or The user terminal directly transfers to the originating domain of the service request. ♦ If the user terminal is currently in an idle state, and the notification carries an indication that the service request is received, the user terminal transits to the originating domain of the service request.

♦ If the user terminal is performing the service, and the notification does not carry the indication that the service request is received, the user terminal determines the level between the current service and the priority of the arrived service request. And processing correspondingly; or, the user terminal directly provides the notification to the user, and the user selects whether to accept the arrived service. Further, if the notification further carries a processing instruction for the ongoing service, the user terminal processes the ongoing service according to the indication; otherwise, the user terminal side processes the ongoing service by itself; that is, the suspension is being performed. The ongoing service or the ongoing service is switched to the originating domain of the service request.

♦ If the user terminal is performing a service, and the notification carries an indication that the service request is received, the user terminal transits to the originating domain of the service request. Further, if the notification further carries a processing instruction for the ongoing service, the user terminal processes the ongoing service according to the indication; otherwise, the user terminal processes the ongoing service by itself; that is, the suspension is ongoing. The service or the ongoing service is switched to the originating domain of the service request.

The priority between the service currently being performed by the user terminal and the priority of the incoming service request is determined according to the user's willingness to set, the configuration of the operator, or the network status; and the user is determined according to the network condition. Whether the current network capability of the terminal can connect to the arrived service.

The manner in which the user terminal returns the result to the network side may be through a short message, which may be a receiving operation, or may be SIP signaling such as INFO, MESSAGE, NOTIFY, and the like.

S4. The VCC AS associates the service with the user terminal in the initiating domain of the service request to connect to the service.

This step can be performed in one of the following ways:

♦ The VCC AS initiates a first session from the originating domain of the service request to the user terminal, forwards the service request to the user terminal, and connects the service terminal to the originating domain of the service request.

In step S2, the VCC AS carries the first special number in the notification, and the first special number uniquely corresponds to the arrived service request; in step S3, the user terminal receives the notification from the notification Obtaining the first special number, and carrying the first special number in a second session initiated after being sent to the originating domain of the service request; and after receiving the second session by the VCC AS, according to the A unique correspondence between a special number and the arriving service request, associating the second session with the arrived service to connect to the service.

Further, if the service currently being performed by the user terminal is switched to the origin of the service request, and the reservation is performed, step S5 is further included.

S5. When the user terminal interrupts the ongoing service, the session to the opposite end of the service is maintained for conversion.

The session mode that is held to the peer end is that the VCC AS inserts a media resource function entity MRF in the session path, and the VCC AS instructs the MRF to play the peer end of the currently ongoing service, and maintains the session to the peer end. Or sending a session update indication to the opposite end of the currently ongoing service for the VCC AS, indicating that the media flow direction is changed to one-way or two-way blocking.

Further, when the user terminal transits to the domain initiated by the service, how to deal with the currently ongoing service, there are three implementation situations in the specific implementation:

In step S2, the notification sent by the VCC AS to the user terminal further carries a second special number; the second special number uniquely corresponds to the currently ongoing service; in step S3, the user terminal turns The first special number initiated by the initiating domain of the service request carries the second special number; after the step S3, when the switching session received by the VCC AS carries the second special number, Corresponding relationship between the second special number and the currently ongoing service, connecting the first handover session with the currently ongoing service at a signaling level; thereafter, the user terminal is modified by a session update indication The currently ongoing service and the media flow direction of the arrived service to implement a transition between the currently ongoing service and the arrived service.

After the step S4, the VCC AS initiates a third session to the user terminal, to forward the currently ongoing service to the user terminal, and after the user terminal receives the third session, The peer end of the currently ongoing service is connected to the user terminal at a signaling level; then the user terminal modifies the currently ongoing service and the The media flow direction of the arrived service to implement a transition between the currently ongoing service and the arrived service.

After the step S4, the VCC AS or the MRF associates the first session, the session to the peer that is currently performing the service, and the session to the peer that reaches the service; and then the user terminal uses the session update. Instructing to instruct the VCC AS or MRF to switch between the currently ongoing service and the arriving service.

• The following is a detailed description of the respective execution steps of the VCC AS and the user terminal.

♦ Referring to Figure 9, for VCC AS, the execution steps include:

1. When the VCC AS receives a session service request arriving from a domain, it determines that the called user terminal is registering in another domain.

2. The VCC AS determines whether the capability of the network where the user terminal is located can satisfy the requirements of the call. If yes, go to step 3; otherwise, go to step 10 and return to reject the call.

3. The VCC AS determines whether the user terminal is in an idle state. If yes, go to step 5; otherwise, go to step 4.

4. If the user terminal has other services in progress, the VCC AS determines whether to compare the priorities of the two sessions. If you want to compare, go to step 7; otherwise, go to step 5.

5. The VCC AS sends a session notification message to the user terminal and waits for a response.

6. The user terminal returns a response message to whether the session is accepted. If yes, go to step 9; otherwise, go to step 10.

7. The VCC AS determines the priority order of the two sessions. If the ongoing session has a higher priority, go to step 10; otherwise, go to step 8.

8. The VCC AS notifies the user terminal to connect to the new session, including the processing indication of the ongoing session: abort or switch. The VCC AS does not wait for the response from the user terminal, and proceeds directly to step 9.

9. The VCC AS connects the session from the arriving domain to the user terminal.

10. The VCC AS returns a rejection response to the new session.

♦ Referring to FIG. 10, after receiving the notification message sent by the VCC AS, the user terminal waits for a response period after the VCC AS sends a notification message to the user terminal in step 5 of FIG. 1 The execution steps include:

11. The user terminal receives the notification message sent from the VCC AS.

12. The user terminal determines whether it is idle. If yes, go to step 13; otherwise go to step

15.

13. The user terminal displays the notification to the user and waits for the user's selection.

14. If the user terminal detects that the user selection result is an acceptance session, then proceeds to step 21; otherwise, proceeds to step 22.

15. If the user is performing other services, the user terminal determines whether there is an indication in the notification sent by the VCC AS to continue the new session. If yes, go to step 16; otherwise, go to step 19.

16. The user terminal determines whether other services that the user is performing need to be reserved. If the reservation is required, go to Step 17; otherwise, go to Step 18.

17. If other services that the user is in need of need to be reserved, the user terminal switches it to the originating domain of the new session. Then go to step 21.

18. If the other services that the user is doing are not needed, the user terminal will stop. Then go to step 21.

19. The VCC AS notification does not include an indication of whether to continue the session, and the user terminal determines whether it needs to connect itself according to the pre-configured priority decision. If yes, go to step 20; otherwise, go to step 13.

20. User terminal > According to pre-configuration, determine the priority order of the two sessions. If the newly arrived session has a higher priority, go to step 16; otherwise, go to step 22.

21. The user terminal returns an acceptance response to the VCC AS, and goes to the domain where the new session arrives, accepting the new session.

22. The user terminal returns a response message rejecting the session to the VCC AS.

The method of the present invention is specifically described below by 14 examples.

♦ Method Example 1. The user terminal registers in the CS domain, and when it is in an idle state, it reaches a session from the IMS domain. After receiving the VCC AS, it makes a judgment and notifies the user terminal. After receiving the notification, the user terminal goes to the IMS domain to connect to the IMS session. Referring to Figure 11, the following specific steps are included: 1. The user terminal registers with the HSS/HLR through the CS domain.

2. The IMS domain service arrives at the VCC AS.

3. The VCC AS queries the HSS/HLR for the registration status and registration location of the user terminal, and the user terminal is currently registered in the CS domain.

4. The VCC AS further determines that the user terminal is currently in an idle state according to the call state of the user terminal.

5. The VCC AS then sends a service notification to the user terminal through the CS domain. Here is an example of a short message notification.

6. After receiving the notification, the user terminal displays the selection to the user. The user chooses to accept the IMS service. The user terminal returns to accept the response.

7. The user terminal converts the working mode to IMS, and moves to the IMS domain for registration.

8. After receiving the acceptance response returned by the user terminal, the VCC AS initiates an IMS session connection process to the user terminal through the IMS domain.

9. After receiving the session in the IMS domain, the user terminal connects to the session.

♦ Method instance 2: The user terminal is registered in the CS domain and is in the CS domain. At this time, the IMS domain arrives at a session. After receiving the VCC AS, the VCC AS judges and notifies the user terminal. After receiving the notification, the user terminal transfers to the IMS domain. Receive a session. Referring to Figure 12, the following specific steps are included:

1. The user terminal registers with the HSS/HLR through the CS domain.

2. The user terminal is doing business in the CS domain.

3. The IMS domain service arrives at the VCC AS.

4. The VCC AS queries the HSS/HLR for the registration status and registration location of the user terminal, and obtains that the user terminal is currently registered in the CS domain.

5. The VCC AS determines that the user terminal is currently in the session state according to the call state of the user terminal. For example, the IMS session has a higher priority.

7. The VCC AS then judges how to handle the ongoing CS session according to various strategies. If you need to release it here.

8. The VCC AS then sends a service notification to the user terminal through the CS domain. Here is an example of a short message notification. The notification content is that the user terminal is required to receive the IMS session and release the original CS session.

9. After receiving the notification, the user terminal suspends the original CS session and transfers to the IMS domain for registration.

10. After the VCC AS sends a notification, it does not wait for the response from the user terminal to initiate an IMS session connection process directly to the user terminal through the IMS domain. In order to give the user terminal time to prepare for the work, the session connection request can be delayed for a short period of time.

11. After receiving the session in the IMS domain, the user terminal connects to the session.

♦ Method Example 3: The user terminal is registered in the CS domain and is in the CS domain. At this time, the IMS domain arrives at a session. After receiving the VCC AS, the VCC AS notifies the user terminal. After receiving the notification, the user terminal judges and goes to the IMS domain. Receive a session. See Figure 13 for the following specific steps:

1. The user terminal registers with the HSS/HLR through the CS domain.

2. The user terminal is doing business in the CS domain.

3. The IMS domain service arrives at the VCC AS.

5. The VCC AS sends a service notification to the user terminal through the CS domain. Here is an example of a short message notification.

6. The user terminal further determines that the user is currently in a session state according to the call state of the user.

7. The user terminal determines the priority of the CS session and the IMS session according to the pre-configured policy of the user, where the IMS session has a higher priority.

8. The user terminal then returns to accept the response.

9. The user terminal will continue to judge how the ongoing CS session is handled according to various policies, if it needs to be released. This judgment process and the sequence of step 8 can be reversed.

10. The user terminal transfers to the IMS domain to perform registration and the like, and performs preparation for switching the original CS session to the IMS domain at the same time. After receiving the acceptance response returned by the user terminal, the VCC AS initiates an IMS session connection process to the user terminal through the IMS domain.

12. After receiving the session in the IMS domain, the user terminal connects to the session.

13. The user terminal switches the original CS session to the IMS domain, and initiates a handover operation request in the IMS domain.

14. After receiving the handover request, the VCC AS performs a handover control operation to switch the original CS session to the IMS domain. Then return to switch successful response.

♦ Method Example 4: The user registers in the CS domain and is in a session, arriving from the IMS to a multimedia session (here, VT calls are taken as an example). The VCC AS notifies the user with a short message that the user chooses to retain the original CS domain session. See Figure 14 for the following specific steps:

The multimode end user is making a voice call with the calling peer in the CS domain, and the VCC AS is anchored in the call path.

1. A VT call request arrives from the IMS domain, and ^^ is triggered by the service to the VCC AS.

2. When the VCC AS detects that the user is in the CS domain voice service, the user sends a short message to the user to notify the user. The notification message can carry the calling number of the VT call so that the user can select whether to answer the call. At the same time, it can carry a first special number that uniquely corresponds to the VT call.

3. The MSC sends the short message to the user.

4. The MSC returns a short message to the VCC AS to send a successful response.

5. The user returns to the MSC to answer the VT call, and at the same time requests to keep the SMS indication of the original voice call.

6. The MSC forwards the short message to the VCC AS.

7. The VCC AS returns a short message to the MSC to receive a successful response.

8. After the terminal obtains the user's choice, the terminal starts to put the current voice call and goes to the DO network.

9. After receiving the notification that the user releases the call, the MSC releases the call route to the MGCF.

10. After receiving the call release notification, the MGCF releases the session to the VCC AS. The session release message should arrive at the VCC AS via the S-CSCF, and is not shown in detail in the figure for the sake of omission.

11. When the VCC AS knows that the user needs to answer the VT call, it starts to perform auxiliary work. First of all A SIP session request is sent to the MRF to insert an RF in the call path. The VCC AS sends the request message to the MRF through the S-CSCF. In the figure, the detailed flow is not drawn for the sake of convenience.

12. After the MRF allocates the media resources, the resource information is returned to the VCC ASo.

13. The VCC AS sends a media change request to the voice call peer to place a call hold tone.

14. The voice call peer accepts the media change request.

15. The VCC AS instructs the MRF to start placing a call hold tone to the voice call peer.

16. The VCC AS also returns to the VT call peer. The 180 Ringing response indicates that the user is being connected.

After the user moves to the IMS network, the device ID or the pre-configured service number of the VCC AS is used as the called number to initiate a SIP new session; or the first special number notified by the VCC AS is used as the called number to initiate a SIP new session.

18. After receiving the new session, the S-CSCF triggers the session to the VCC AS.

19. The VCC AS returns a call acceptance response for this new session.

20. The response message is forwarded to the terminal.

21. The VCC AS sends a call-on response to the VT call peer, and connects the VT session and the new session. After that, the terminal enters the call waiting service state in the IMS domain and the original voice call and VT call.

The VCC AS can perform conversion operations between two calls based on the user's operation.

♦ Method Example 5: The user terminal registers in the CS domain and is in a session, from the IMS domain to a multimedia session (here, taking a VT call as an example), the VCC AS prompts the user through CCDIR or RUIDIR playback, ^^ according to the user selection to switch Instructions. Referring to Figure 15, the following specific steps are included:

1. A VT call request is sent from the IMS domain, and the request message is triggered by the service to the VCC AS.

2. When the VCC AS detects that the user is performing the CS domain voice service, the VCC sends a CCDIR (Call Control Directive) message or a RUIDIR (Remote User Interaction Directive) message to the MSC. Tone indication has VT The call arrives and the calling party number is notified.

(Note that according to the IS-826 protocol before S, the CCDIR process can only play sounds and cannot perform the number-receiving operation. Therefore, if you need to use this message here, you need to extend the function of the CCDIR message to perform the number-receiving operation. According to the current ANSI-41D/E protocol, the RUIDIR message cannot be initiated as a TCAP session and needs to be used in an already established TCAP session. Therefore, if a RUIDIR message needs to be used here, it needs to be extended. Initiated as a separate TCAP session.)

3. The MSC plays the voice to the user, and the user selects the operation type according to the playback indication and inputs the selection number.

4. The MSC returns the user's selection input to the VCC AS.

5. The VCC AS determines, according to the user's selection input, that the user chooses to abort the current CS domain voice call and forwards to the IMS domain to answer the VT call, and then sends an INFODIR (Information Directive Information Indication) message to the MSC, so that the MSC can indicate that the terminal can perform the handover. Bring a first special number for switching.

6. The MSC sends a Flash with Information message to the terminal, with the first special number content in the message. The MSC then returns a response to the VCC AS.

7. The VCC AS can return to the VT call peer. The 180 Ringing message indicates that the call is being connected.

8. After obtaining the handover indication, the terminal releases the current voice call and goes to the DO network.

9. After receiving the notification of the user # put the call, the MSC releases the call route to the MGCF.

11. The VCC AS sends a BYE message to the CS domain voice call peer to release the voice call.

12. After the user terminal transfers to the IMS network, the first special number notified by the VCC AS is used as the called number to initiate a SIP new session.

13. After receiving the new session, the S-CSCF triggers the session to the VCC AS.

14. The VCC AS returns a call acceptance response for this new session.

15. The response message is forwarded to the terminal. 16. The VCC AS sends a call-on response to the VT call peer, and connects the VT session and the new session. ♦ Method Example 6: The user terminal registers in the CS domain and is in a call, and arrives at a multimedia session from the IMS domain (here, taking a VT call as an example). The VCC AS broadcasts the notification through the MRF, and obtains the user selection according to the numbering operation to perform the switching operation judgment. Referring to Figure 16, the following specific steps are included:

The difference from method example four begins with step 2:

2. The VCC AS sends an INVITE to the MRF to prepare to insert MRP resources into the call path.

3. The MRF returns resource information.

4. The VCC AS sends a media change request to the MGCF to connect the CS domain call to the MRF.

5. The MGCF redirects the CS domain call to the MRF resource and returns to the media change success response.

6. After the terminal and the MRF bearer channel are connected, the VCC AS instructs the MRF to put a prompt tone to the user, informs the user that there is a VT call incoming and informs the calling number, and waits for the user to input the selection.

7. The user listens to the prompt tone and makes a selection. The MRF extracts the user's input number from the band and sends it to the VCC AS.

8. The VCC AS determines, according to the user selection, that the user decides to go to the IMS domain to answer the VT call while retaining the original voice call, and is ready to perform the handover operation. First, an INFODIR message is sent to the MSC, and the MSC instructs the terminal to start switching while notifying the required number information (special number) for handover.

9. After receiving the INFODIR message, the MSC sends a Flash with Information message to the terminal, where the message carries the first special number.

10. After receiving the Flash with Information message with the handover indication, the terminal interrupts the current voice call and goes to the DO network.

11. After receiving the CS domain voice call interruption indication, the MSC releases the call route to the MGCF.

12. After receiving the call release indication, the MGCF sends a session release message BYE to the VCC AS. This message is triggered to the VCC AS via the S-CSCF, which is omitted from the figure.

13. When the terminal releases the CS domain call, the VCC AS sends a media change request to the MRF to change the MF resource to the opposite end of the CS domain voice call. 14, MRF returned to change successfully.

15. The VCC AS also sends a media change request to the CS domain voice call peer to redirect the call peer to the MRF resource.

16. The voice call peer returns a media change and responds successfully.

17. The VCC AS instructs the MRF to place a call hold tone to the opposite end of the voice call.

The subsequent process is the same as method example four.

♦ Method Example 7: The user terminal registers in the CS domain and is in a call, from the IMS domain to a multimedia session (here, VT call is taken as an example). The VCC AS notifies the user by short message, and the user chooses to keep the original CS domain session, and the terminal itself performs call hold control without inserting the MRF entity. See Figure 17, which includes the following specific steps:

The difference from method example four is that in step 2, the VCC AS assigns a special number to each of the CS domain session and the VT session, and brings them to the terminal. Other differences start with step 11.

11. The VCC AS learns that the user needs to answer the VT call and needs to retain the original CS session, and then starts the auxiliary work. First, a re-INVITE message is sent to the opposite end of the CS session, and the message indicates that the direction of the media stream is only sent, so that the opposite end of the CS session is held.

12. The VCC AS also returns to the VT call peer. The 180 Ringing response indicates that the user is being connected.

13. After the CS session is interrupted, the user terminal transits to the IMS network, and initiates a SIP new session with the second special number notified by the VCC AS as the called number, and the session is forwarded by the CSCF to the VCC AS, and the CSCF forwarding process is omitted in the figure. .

14. The VCC AS associates with the original CS domain session through the second special number, and then returns a response to the new session. The response message indicates that the session is connected to the original CS domain session, and the session is in a held state.

15. The VCC AS also notifies the CS session peer to redirect the media stream to the user terminal in the IMS domain. Thus, the user terminal is connected to the original CS session in the IMS domain, but the session is in a held state.

16. The user terminal then uses the first special number notified by the VCC AS to initiate another in the IMS domain. SIP session, the session is forwarded by the CSCF to the VCC AS.

17. The VCC AS associates the VT session with the first special number and then returns a response message to the new session indicating that the session is connected to the VT session.

18. The VCC AS also notifies the peer end of the VT session to connect to the user terminal in the IMS domain. Thus, the user terminal also has a VT session in the IMS domain.

It should be noted that the above steps 13, 14, and 15 can be exchanged with 16, 17, and 18, that is, after the user accesses the IMS domain, the user can first connect to the original CS session, or can connect to the VT session first.

After the above steps, the user is connected to the VS domain and the VT session, and is in a normal call state; and is also connected to the original CS domain session in the hold state. The user can perform any conversion between the two sessions, such as holding the VT session and restoring the call with the CS session. The conversion steps are as follows:

19. The user sends a media update message to the CS session, where the message indicates that the direction of the restored media stream is a two-way call.

20. The VCC AS forwards the message to the peer end of the CS session. After the CS session peer returns to accept the response, the user can resume the call (this step is not shown in the figure).

21. The user also needs to send a media update message to the VT session, and the message indicates that the direction of the media stream is modified to be sent only.

22. The VCC AS forwards the message to the opposite end of the VT session. After the VT session peer returns to accept the response, it is held by the user.

♦ Method Example 8: The user terminal registers in the CS domain and is in a call, from the IMS domain to a multimedia session (here, VT call is taken as an example). The VCC AS notifies the user by short message, the user chooses to keep the original CS domain session, and the terminal itself performs call hold control without inserting the MRF entity, and the user only needs to initiate one session after the user transfers to the IMS domain, and the other session is initiated by the network. See Figure 18, which includes the following specific steps:

The difference from method instance seven is that in step 2, the VCC AS only needs to assign a special number to the VT session and bring it to the user terminal. Other differences start with step 13.

13. After the user terminal interrupts the CS session, the user terminal transfers to the IMS network, and the VCC AS informs the special The unique number is used as the called number to initiate a SIP new session. After the session is forwarded by the CSCF, the session arrives at the VCC AS. The CSCF forwarding process is omitted.

14. The VCC AS associates to the VT session through the first special number, and then returns a response to the new session, indicating that the session is connected to the VT session.

15. The VCC AS also notifies the peer end of the VT session to connect to the user terminal in the IMS domain. Thus the user terminal is connected to the VT session in the IMS domain.

16. After detecting that the user has accessed the IMS domain and connected to the VT session, the VCC AS forwards the original CS domain session to the user.

17. After receiving the session, the user selects to connect and returns a response;

18. After receiving the user's connection response, the VCC AS notifies the original CS session peer to connect with the user terminal in the IMS domain. In this way, the user terminal is also connected to the original CS session in the IMS domain, but is in the call hold state.

The subsequent steps and methods of Example 7 are the same.

It should be noted that the VCC AS assigns a special number in step 2 and brings the terminal to the original CS session instead of the VT session. Then, in step 13, when the user accesses the IMS domain and uses the special number to initiate the SIP session, it is connected to the original CS session. After the VCC AS controls the user to connect with the original CS session, the session connection initiated to the user in step 16 is The VT session is connected to the user.

♦ Method Example 9: The user terminal registers in the CS domain and is in a call, from the IMS domain to a multimedia session (here, VT call is taken as an example). The VCC AS notifies the user by short message, the user chooses to keep the original CS domain session, and the terminal itself performs call hold control without inserting the MRF entity, and only needs to initiate a session after the user transfers to the IMS domain, and the VCC AS will use this session and the original CS. Domain sessions, VT sessions are associated together. Referring to Figure 19, the following specific steps are included: The difference from the method example eight is from the 16th step.

After the VCC AS detects that the user has accessed the IMS domain and is connected to the VT session, it indicates that the original CS domain session is also connected to the user terminal of the IMS domain. Since the CS domain session is maintained at this time, the connection is only signaling. At the level, the media level is still being maintained.

At this time, at the signaling level, the user terminal is connected to the VT session and the original CS session. The VCC AS performs a three-way session association. At the media level, the user terminal is connected to the VT session and the original CS session is maintained. If the user wants to resume a conversation with the original CS domain session and keeps the VT session, then:

17. The user initiates an indication to the VCC AS, indicating that the original CS domain session is connected, and the VT session is maintained;

18. The VCC AS receives the indication from the user, and initiates a session change indication to the user terminal, and connects the user terminal to the original CS domain session at the media level.

19. The VCC AS sends a session change indication to the original CS domain session peer to indicate that the original CS domain session is re-established.

20. The VCC AS also sends a session change indication to the VT session peer to hold it.

♦ Method Example X. The user terminal is registered in the IMS domain and arrives at the voice call from the CS domain. The VCC AS notifies the user when the CS domain receives the call, and the user waits for the network paging after going to the lx network. See Figure 20, which includes the following specific steps:

Step S402, the GMSC of the dual-mode terminal user home network receives the voice call request; Step S404, the GMSC applies the user information to the HLR (Home Location Register);

Step S406, the HLR returns a list of the user's subscription trigger address;

Step S408, the GMSC triggers the ANLYZD message to the VCC AS according to the trigger address list. In step S410, the VCC AS detects that the user is in the HRPD network, and directly sends an INFO message to the user in the IMS domain. Alternatively, the MESSAGE or NOTIFY may also be used here. For other SIP messages, the message may have a calling party number for the user's reference;

Step S412, the user returns a receiving response.

Step S414, the user can make a selection at this time, requesting to answer the voice call. Alternatively, the user can also omit this step, and the default is that the user needs to answer the voice call;

Step S416, the VCC AS returns a receiving response. If the above step S414 is not performed, the step may also be omitted. The user interrupts the connection with the HRPD network at this time, and returns to the lx network to prepare to receive the voice call page.

Step S418, after receiving the user's selection, the VCC AS determines that the lx call needs to be connected. Then the GMSC is returned with an indication to continue the connection at lx. In order to wait for the user to return to the lx grid, the VCC AS may wait here for a while before returning to the connection indication;

Steps S420 ~ S428, these steps are the standard lx call in the CS domain called the connection process; Step S430, after the user visited the MSC receives the incoming call, initiates a paging message to the user;

The user returns a response after receiving the page, and the subsequent step is the standard lx called connection process.

Method Example 11: The user terminal registers in the IMS domain and arrives at the voice call from the CS domain. VCC

The AS notifies the user in the IMS domain that the user returns to the lx network to wait for network paging. See Figure 21 for the following specific steps:

Step S502: The GMSC of the home domain of the dual mode terminal user receives a voice call call request from the lx network.

Step S504, the GMSC applies for user information to the HLR.

Step S506, since the user is a VCC user, the smart trigger is signed, and the HLR returns the trigger address list of the user B to the GMSC.

Step S508, the GMSC triggers the ANLYZD message to the VCC AS according to the trigger address list information of the user;

Step S510, the VCC AS decision needs to perform call anchoring in the IMS domain, and then returns an IMS Routing Number to the GMSC;

Step S512, the GMSC routes the call to the MGCF (Media Gateway Control Function) according to the IMS Routing Number;

Step S514, the MGCF sends a SIP call through the PSI to the VCC AS via a CSCF (Call Session Control Function);

Step S516: After receiving the call, the VCC AS detects that the user is in the HRPD network, and sends an INFO message to the user in the IMS domain to prompt that a voice call arrives. Other SIP messages such as MESSAGE may also be used here. The message may also be carried in the message for the user to refer to; in step S518, the user's terminal returns a response;

In step S520, the user can make a selection and request to answer the voice call. You don't need this step either. The default user of the VCC AS needs to answer the call;

Step S522, the VCC AS returns a receiving response to the terminal. If the previous step is omitted, this step can also be omitted. The user interrupts the connection with the HRPD network and returns to the lx network to prepare to receive the lx call.

Step S524: The VCC AS takes the user roaming information from the HLR of the user.

Step S526, the HLR takes the user roaming number to the visited network of the user;

Step S528, the visited network returns a roaming number;

Step S530, the HLR returns the roaming number to the VCC AS.

Step S532, the VCC AS initiates a new SIP session by using the roaming number, and the session reaches the MGCF via the CSCF;

Step S534, the MGCF initiates a call request to the VMSC according to the roaming number;

Step S536, the VMSC starts to initiate paging to the user B on the lx network;

The user responds after receiving the page on the lx network, and the subsequent step is the standard lx called connection process. Method Example 12: The user terminal registers in the IMS domain and arrives at the voice call from the CS domain. VCC

The AS notifies the user in the CS domain that the user initiates a call after returning to the lx network. See Figure 22, which includes the following specific steps:

Steps S602 to S608 in the method example are similar to steps S402 to S408 of the method example ten, with the difference that, starting from step S610:

Step S610: When the VCC AS prompts the user to have a voice call, the VCC AS carries a call reference number in the message to identify the current call.

Steps S612 to S616 are substantially the same as steps S412 to S416 of the tenth embodiment. Step S618, the VCC AS returns an IMS routing number to instruct the GMSC to route the call to the IMS domain.

Step S620, the GMSC uses the IMS routing number to route the call to the MGCF.

Step S622, the MGCF initiates a SIP session in the IMS domain by using the IMS routing number, and the session reaches the VCC AS via the CSCF;

Step S624, after the HRPD network receives the notification, the user interrupts the connection with the HRPD network. Return to the Ix network and initiate an lx call with the received call reference number;

Step S626, the MSC routes the call to the MGCF by performing number analysis on the call. The reference number; Step S628, the MGCF initiates a SIP session in the IMS domain by using the call reference number, and the session reaches the VCC AS via the CSCF;

The VCC AS can find the original lx session by calling the reference number, and then associate the two sessions so that the lx call is connected to the user.

Method Example 13: The user terminal registers in the IMS domain and arrives at the voice call from the CS domain. The VCC AS notifies the user in the IMS domain that the user initiates a call after returning to the lx network. See Figure 23, which includes the following specific steps:

The difference between the method example and the method example eleven is that, in step S716, the VCC AS carries a call reference number in the notification message, and the call reference number corresponds to the current session. The other areas start from step S724:

Step S724, after the HRPD network receives the notification, the user interrupts the connection with the HRPD network, returns to the lx network, and initiates the lx call with the received call reference number;

Step S726, the MSC routes the call to the MGCF by performing number analysis on the call reference number. Step S728, the MGCF initiates a SIP session in the IMS domain by using the call reference number, and the session reaches the VCC AS via the CSCF;

Example 14 of the luxury method, the user terminal is registered in the IMS domain, and the voice call is reached from the CS domain. The VCC AS notifies the user in the IMS domain. After the user returns to the lx network, the call is initiated after the call is initiated. In step S418 in the tenth embodiment, after receiving the instruction that the user goes to the lx network to receive the call, the VCC AS immediately controls the call to be connected in the lx network, but in actuality, the user may not have registered after going to the lx network. At this point, the call on the lx network is not connected. Therefore, an optional option is given in the tenth embodiment, that is, the VCC AS can wait a few seconds and then return to the continuation indication at step S418, thus providing time for user registration. However, this method is also flawed because the calling user may feel bad because of the long waiting time. In the method instance 12 and the method example thirteen, the user speeds up the connection by sending the initial call to the lx network. This scheme may cause improper charging for the user, because the user originally answered the call and now becomes When making a call, the fees of the two may be inconsistent, causing losses to the user.

Therefore, in the example 14 of the method example given here, the user is prompted to initiate an initial call process after going to the lx network. If the user is not registered in the lx network, the initial call process triggers an implicit registration process, and the user is Register to the HLR. After receiving the message from the user, the VCC AS can determine that the user has already registered, and then release the original call message, indicating that the waiting lx call continues to connect to the user. In this way, on the one hand, the call connection speed is accelerated, and on the other hand, the billing error caused by the called process becoming the calling process is avoided.

Referring to FIG. 24, the difference between the method example and the method example ten is that, starting from step S824:

Step S824: After receiving the calling message initiated by the lx network, the VCC AS determines that the user has successfully registered, and then terminates the current calling process, and returns a call release message to the user. #放消息 Directly to the user via CSCF/MGCF/MSC—release the call;

Step S826, the VCC AS returns an indication that the GMSC continues to connect the user on the lx network; the subsequent process is consistent with the process starting from step S420 in the method instance 10.

From the above description, it can be seen that with the cross-domain receiving voice method or apparatus according to the present invention, after receiving the CS voice call, the VCC AS notifies the dual-mode terminal user residing in the IMS network to the CS after using the SIP message. The network then connects the dual-mode end user to the CS call peer in the CS network, that is, the user is notified through the IMS network, and the user is allowed to connect to the CS network.

• w-call The spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and variations of the inventions

Claims

Rights request

A method for receiving services across domains, characterized in that it comprises the following steps:

A. When the voice call continuity application server receives the service request arriving from one domain and points to the user terminal registered in another domain, the user terminal is notified;

B. When the user terminal determines that the preset condition is met, the user terminal transfers to the originating domain of the service request.

C. The VCC AS associates the service with the user terminal in the originating domain of the service request to connect to the service.

2. The method according to claim 1, wherein in the step A, the VCC AS detects the current state of the user terminal, and if the user terminal is currently in an idle state, the VCC AS directly notifies the user. Terminal

If the user terminal is currently performing a service, the VCC AS directly notifies the user terminal, or performs processing according to the level between the current service of the user terminal and the priority of the arrived service request.

The method according to claim 2, wherein the processing is performed according to the level between the priority of the service currently being performed by the user terminal and the priority of the arrived service request, including:

If the priority of the currently ongoing service of the user terminal is high, the VCC AS rejects the service request that is reached;

If the priority of the arrived service request is higher, the VCC AS notifies the user terminal to turn on the arrived service request.

4. The method according to claim 3, wherein when the VCC AS rejects the arrived service request, the user terminal is notified that the network side performs the reject operation.

The method according to claim 1, wherein the notification sent by the VCC AS to the user terminal carries an indication that the user terminal transfers to the originating domain of the service request to turn on the arrived service request. .

6. The method of claim 1, wherein if the VCC AS sends to the user terminal The notification does not carry the indication of the arrival of the service request, and the notification carries at least the service type and the calling number.

7. The method according to claim 1, wherein, before the step B, after the user terminal receives the notification,

If the user terminal is currently in an idle state, and the notification does not carry the indication that the service request is received, the user terminal directly provides the notification to the user, and the user selects whether to accept the arrived service; or, the user The terminal directly performs step B;

If the notification carries an indication to turn on the arrival service request, the user terminal performs step B;

If the user terminal is performing a service, and the notification does not carry the indication that the service request is received, the user terminal determines the priority between the current service and the priority of the arrived service request, and The processing is performed accordingly; or, the user terminal directly provides the notification to the user, and the user selects whether to accept the arrived service.

The method according to claim 7, wherein if the user terminal is performing a service, and the notification carries an indication that the arrival service request is turned on, further if the notification further carries an ongoing The processing instruction of the service, the user terminal processes the ongoing service according to the indication; otherwise, the user terminal processes the ongoing service by itself.

The method according to claim 2, 3, 4, 7 or 8, wherein the priority between the currently ongoing service of the user terminal and the priority of the arrived service request is set by the user. Willingness, operator configuration, or network status.

The method according to claim 1, wherein the VCC AS associates the service with the user terminal in the originating domain of the service request, and the method for connecting to the service includes one of the following:

In the step C, the VCC AS initiates a first session from the originating domain of the service request to the user terminal, forwards the service request to the user terminal, and the user terminal turns to the originating domain of the service request and then connects. The business;

- In the step A, the VCC AS carries the first special number in the notification, the first special The unique number corresponds to the arrived service request uniquely; in the step B, the user terminal acquires the first special number from the received notification, and initiates the second after the transfer to the originating domain of the service request The session carries the first special number; and in the step C, after the VCC AS receives the second session, according to the unique correspondence between the first special number and the arrived service request, The second session is associated with the arriving service to connect to the service.

The method according to any one of claims 1 to 8, wherein the processing of the ongoing service of the user terminal comprises: suspending the currently ongoing service, or performing the currently ongoing service. Switch to the originating domain of the service request.

The method according to claim 11, wherein if the service currently being performed by the user terminal is switched to the originating domain of the service request, and the reservation is performed, the VCC AS keeps until the user terminal interrupts the service. The conversation of the opposite end of the business.

The method according to claim 12, wherein the session mode held to the peer end is: the VCC AS inserts a media resource function entity MRF in the session path, and the VCC AS indicates that the MRF is currently in progress Play the opposite end of the service and keep the session to the peer; or:

The VCC AS sends a session update indication to the peer end of the currently ongoing service, indicating that the media stream direction is changed to one-way or two-way blocking.

The method according to claim 13, wherein in the step A, the notification sent by the VCC AS to the user terminal further carries a second special number; the second special number and the current The only correspondence of ongoing business;

In the step B, the first switching session initiated by the user terminal to the originating domain of the service request carries the second special number;

After the step B, when the switching session received by the VCC AS carries the second special number, the first switching session is compared according to the correspondence between the second special number and the currently ongoing service. The currently ongoing service is connected at the signaling level; the user terminal then modifies the current ongoing service and the media flow direction of the arrived service by using a session update indication to implement the current The conversion between the conducted business and the arriving business.

The method according to claim 13, wherein after the step C, the VCC AS initiates a third session to the user terminal, to forward the currently ongoing service to the user terminal; After the user terminal receives the third session, the peer end of the currently ongoing service is connected to the user terminal at a signaling level; and then the user terminal uses the session update indication to modify the current ongoing And the media flow direction of the arrived service to implement a transition between the currently ongoing service and the arrived service.

The method according to claim 13, wherein, after the step C, the VCC AS or the MRF, the first session, the session to the peer that is currently performing the service, and the arrival service The peer end of the session is associated with each other; the user terminal then uses the session update indication to instruct the VCC AS or MRF to switch between the currently ongoing service and the arriving service.

A VCC AS entity, configured to perform call anchoring and domain switching, wherein the VCC AS entity further includes:

a determining module, configured to determine whether the user terminal pointed to by the service request arriving from one domain is currently registered in another domain, and if yes, issue a trigger signal;

a notification module, configured to send a notification message to the user terminal after receiving the trigger signal sent by the determining module;

The association module is configured to associate the service with the user terminal to connect to the service after the user terminal transits to the originating domain of the service request.

The entity of claim 17, wherein the determining module is further configured to: after receiving the service request, detecting whether the user terminal is currently performing services in another domain; when detecting the user When the terminal is currently performing traffic in another domain, it determines whether to issue a trigger according to the session priority.

The entity according to claim 17, wherein the association module associates the service with the user terminal in the originating domain of the service request, and the method for connecting to the service includes one of the following:

- the association module initiates a first session from the originating domain of the service request to the user terminal, The service request is forwarded to the user terminal, and the user terminal connects to the originating domain of the service request and then connects the service;

The notification module generates a first special number uniquely corresponding to the arriving service request and carries it in a notification sent to the user terminal; and the association module identifies that the user terminal is transferred to the originating domain of the service request When the second session is carried in the second session, the second session is associated with the arrived service according to the unique correspondence between the first special number and the arrived service request. Through the business.

20. The entity of claim 17, 18 or 19, wherein the entity further comprises:

The call holding module is configured to mark the currently ongoing service, and maintain a session to the opposite end of the service when the user terminal interrupts the service.

The entity according to claim 20, wherein the call holding module maintains a session to the currently ongoing service peer in one of the following manners:

Inserting an MRF in the session path, and instructing the MRF to complete the playback and call waiting control; sending a session update indication to the opposite end of the currently ongoing service, indicating that the media stream direction is changed to one-way or two-way blocking.

The entity according to claim 21, wherein the notification module generates a second special number uniquely corresponding to the currently ongoing service, and carries the notification to the user terminal;

The association module identifies, according to the correspondence between the second special number and the currently ongoing service, when the second special number is carried in the first switching session initiated by the user terminal after being transferred to the initiating domain of the service request The relationship, the first handover session is associated with the currently ongoing service at a signaling level.

The entity according to claim 21, wherein the association module initiates a third session to the user terminal, to forward the currently ongoing service to the user terminal; and at the user After receiving the third session, the terminal associates the peer end of the currently ongoing service with the user terminal at a signaling level.

The entity according to claim 21, wherein the association module sets the first session, the session to the peer currently performing the service, and the session to the peer of the arriving service. Association.

A user terminal, which is capable of accessing and conducting a call service in a plurality of networks, wherein the user terminal further includes:

a network interface module, configured to receive a notification from a network side, where the notification indicates that a service request arrives from a certain domain; and interacts with the network side;

The control module determines whether to receive the arrived service according to a preset condition, and provides the processing result to the network interface module, and controls the initiation of the user terminal to transfer the service request when determining to receive the arrived service area.

The terminal according to claim 25, wherein the control module is based on one of the following conditions:

The control module processes according to the service indication carried in the notification;

The control module first detects whether the user terminal is performing services in another domain, and accordingly processes according to the session priority;

The control module presents the notification to the user and processes it according to the user's selection.

The terminal according to claim 25, wherein the network interface module is further configured to acquire the first special number from the received notification.

The terminal according to claim 27, wherein the terminal further comprises: a new session initiation module, configured to: after the control module controls the user terminal to transfer to the originating domain of the service request, by using a network interface The module carries the first special number in the second session initiated by the network side.

The terminal according to claim 26, wherein the user terminal further comprises: a suspension module, configured to suspend a service currently being performed by the user terminal; and/or

a switching module, configured to switch a service currently being performed by the user terminal to an originating domain of the service request;

When the user terminal is performing services in another domain, and the control module determines that the arrived service should be received according to a preset condition, the current processing is being processed by the suspension module or the switching module. Conducted business.

The terminal according to claim 29, wherein the network interface module is further configured to acquire a second special number from the received notification.

The terminal according to claim 30, wherein the terminal further includes: a handover session initiation module, configured to: after the handover module switches the service currently being performed by the user terminal to the initiation domain of the service request, The second special number is carried in the first switching session initiated by the network interface module to the network side.

The terminal according to claim 29, 30 or 31, wherein the terminal further comprises:

a conversion module, configured to: after the switching module transfers the currently ongoing service of the user terminal to the originating domain of the service request, using a session update indication, indicating that the VCC AS or the MRF is in the current ongoing service and the arrived Converting between the services; or modifying, by the session update indication, the media stream direction of the currently ongoing service and the arrived service, to implement conversion between the currently ongoing service and the arrived service .

The terminal according to claim 25, wherein the notification received by the network interface module from the network side indicates that a service request arrives from a domain, and the domain is a domain that is not registered by the user terminal; or The service request sent by the domain cannot be connected to the network where the user terminal is currently located.

34. A system for receiving services across domains, comprising:

a voice call continuity application server VCC AS, configured to notify the user terminal when receiving a service arriving from one domain to point to a user terminal registered in another domain; and in the originating domain of the service request, The service is associated with the user terminal to connect to the service;

The user terminal is configured to transfer to the originating domain of the service request when determining that the preset condition is met.

The system of claim 34, wherein the VCC AS comprises: a determining module, configured to determine whether a user terminal pointed to by a service request arriving from one domain is currently registered in another domain, and if so, Issue a trigger signal;

a notification module, configured to send a notification message to the user terminal after receiving the trigger signal sent by the determining module; The association module is configured to associate the service with the user terminal to connect to the service after the user terminal transits to the originating domain of the service request.

The system of claim 35, wherein the VCC AS further comprises: a call holding module, configured to mark the currently ongoing service, and maintain the service when the user terminal interrupts the service. The peer's session.

The system of claim 34, wherein the user terminal is capable of accessing and conducting a call service under a plurality of networks, and the method further includes:

a network interface module, configured to receive a notification from a network side, where the notification indicates that a service request arrives from a domain; and returns a processing result to the network side;

The control module determines whether to receive the arrived service according to a preset condition, and when determining to receive the arrived service, controls the user terminal to transfer to the originating domain of the service request, and provides the processing result to the network interface. Module.

The system of claim 37, wherein the user terminal further comprises: a suspension module, configured to suspend a service currently being performed by the user terminal; and/or

When the user terminal is performing services in another domain, and the control module determines that the arrived service should be received according to a preset condition, the currently performing service is processed by the suspension module or the switching module.

The system according to claim 38, wherein, if the user terminal includes a handover module, the user terminal further includes: a conversion module, configured to switch, by the handover module, the service currently being performed by the user terminal to the After the initiating domain of the service request, the session update indication is used to instruct the VCC AS or the MRF to perform conversion between the currently ongoing service and the arrived service; or modify the currently ongoing by using a session update indication The media flow direction of the service and the arrived service to implement a transition between the currently ongoing service and the arrived service.