WO2014000429A1

WO2014000429A1 - Method and device for realizing terminal mobile service in internet protocol (ip) multimedia subsystem architecture

Info

Publication number: WO2014000429A1
Application number: PCT/CN2013/070074
Authority: WO
Inventors: 郭金卫; 杨恒占
Original assignee: 华为技术有限公司
Priority date: 2012-06-28
Filing date: 2013-01-05
Publication date: 2014-01-03
Also published as: CN102739672A

Abstract

The embodiment of the invention provides a realization method of terminal mobile service in an IP multimedia subsystem architecture, which comprises: in a user communication process, receiving a terminal portability (TP) service trigger request submitted by an integrated services digital network (ISDN) user terminal; according to the TP service request message, establishing a TP service suspending request message; sending the TP service suspending request message to a core network of the IP multimedia subsystem (IMS), thus identifying the TP service suspending request and performing the TP service suspending operation by the core network of the IMS. The embodiment of the invention also provides a realization device of terminal mobile service in the IMS architecture. By using the realization scheme of terminal mobile service in the IMS architecture provided by the embodiments of the invention, the core network of the IMS can identify the TP service initiated by users, the TP service can be distinguished from the Call Hold service, and the process for the TP service, such as billing, traffic statistics and so on, can be separately performed.

Description

Method and device for implementing terminal mobile service under IP multimedia subsystem architecture

The present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for implementing terminal mobile services in an IP multimedia subsystem architecture. Background technique

The TP (Terminal Portability) service is a user-specific service of an ISDN (Integrated Service Digital Network) network in a PSTN (Public Switched Telephone Network) network, allowing users to An S interface (the S interface refers to the S interface in the ISDN network, that is, the interface that the user accesses the network, which can be understood as a subscriber line is an S interface), and moves one phone from one socket to another (the socket refers to A port connected to a user terminal on the same S interface, or a call from one phone to another on the same S interface.

In the prior art, the TISPAN ts-183036 document defines an implementation method for implementing a TP service by an AGCF (Access Gateway Control Function) under the IMS (IP Multimedia Subsystem) architecture:

After receiving the SUSPEND message sent when the terminal operation request is suspended, the AGCF/VGW (voice over IP gateway) constructs a relnvite message carrying the SDP: a=sendonly and sends it to the IMS Core (IMS core network) to request to hang. Call

After the call is suspended, the AGCF/VGW receives the RESUME message sent when the terminal operation request is restored, and constructs a relnvite message carrying the SDP: a=sendrecv and sends it to the IMS Core to request to resume the call.

The above solution for implementing the TP service is for the SIP interface between the AGCF/VGW and the IMS Core. The definition of the information is exactly the same as the Call Hold (CH) service definition. As a result, the IMS cannot identify whether the message is a TP service request or a CH (Call Hold) service request, and cannot perform independent charging and traffic statistics processing for the TP service. If the call peer terminal is an ISDN terminal, the peer network side cannot send a correct Notify notification message to the ISDN terminal because the message cannot be identified as a TP service message. Summary of the invention

In order to solve the technical problem that the IMS core network cannot identify the TP service request message in the prior art, the embodiment of the present invention provides a method for implementing the terminal mobile service in the IP multimedia subsystem architecture, including:

Receiving a terminal mobile TP service trigger request submitted by the ISDN user terminal of the integrated service digital network during the call of the user; constructing a TP service suspension request message according to the TP service request message; and transmitting the TP service core message to the IP multimedia subsystem IMS core network The TP service suspends the request message, so that the IMS core network identifies the TP service suspension request, and performs the TP service suspension operation; in the process of the user call suspension, receiving the ISDN user terminal And submitting the TP service recovery request message according to the TP service recovery request; sending the TP service recovery request message to the IMS core network, so that the IMS core network identifies the TP service The request is restored, and the TP service recovery operation is performed.

The embodiment of the present invention provides an apparatus for implementing a terminal mobile service in an IP multimedia subsystem architecture, including: a receiving unit, configured to receive a terminal mobile TP service triggered by an ISDN user terminal of an integrated service digital network during a call of a user. a requesting unit, configured to: construct a TP service suspension request message according to the TP service trigger request received by the receiving unit, and send, by the sending unit, to the IP multimedia subsystem IMS core network The TP service suspends the request message, so that the IMS core network identifies the TP service suspend request, and performs the TP service suspend operation; the receiving unit is further configured to suspend the user call Receiving, by the ISDN user terminal, the TP service recovery request; the building unit is further configured to: according to the Receiving, by the receiving unit, the TP service recovery request, the TP service recovery request message, where the sending unit is further configured to send, by using the TP core, a TP service recovery request message that is configured by the The IMS core network identifies the TP service recovery request and performs the TP service recovery operation.

Using the implementation scheme of the terminal mobile service in the IMS architecture disclosed in this embodiment, the IMS core network can identify the TP service initiated by the user, and can be separated from the Call Hold service, and can separately perform charging and traffic statistics processing for the TP service. DRAWINGS

FIG. 1 is a schematic diagram of a solution for implementing a terminal mobile service in an IMS architecture according to an embodiment of the present invention;

FIG. 2 is a flowchart of processing a TP service when two users are in a call in an IMS domain according to an embodiment of the present invention;

FIG. 3 is a flowchart of processing a TP service in a cross-domain call according to an embodiment of the present invention; FIG. 4 is a flowchart of processing a TP service in a cross-domain call according to an embodiment of the present invention; A schematic structural diagram of an apparatus for implementing a terminal mobile service in an IMS architecture provided by an embodiment of the present invention. detailed description

Embodiments of the present invention will now be described in conjunction with the drawings in order to facilitate the understanding of the invention.

In order to solve the technical problem that the TP service and the CH service cannot be distinguished in the prior art, the embodiment of the present invention provides a method for implementing the terminal mobile service in the IP multimedia subsystem, which is used to indicate that the request message is a TP service request message. It is distinguished from the CH service request message.

FIG. 1 is a schematic diagram of a solution for implementing a terminal mobile service in an IMS architecture according to an embodiment of the present invention. The steps of the program are detailed below: Step 101: Receive a terminal mobile TP service trigger request submitted by the ISDN user terminal of the integrated service digital network in the process of the user's call;

As mentioned above, the terminal mobile service (TP service) is a service unique to the ISDN user, allowing the user to move a phone from one jack to another on the same S interface during a call, or on the same S interface. Move a call from one phone to another.

The peer end of the user who initiates the TP service can be either an ISDN user or a non-ISDN user. The difference between these two types of users will be described in detail in the subsequent embodiments.

The ISDN user initiates the terminal mobile service during the call and initiates a TP service request through its terminal. If the user is a user in the IMS domain, the TP service request is sent to the AGCF/VGW (Access Gateway Control Function, Voice over IP Gateway, IP Call Gateway) to which the user belongs. The AGCF/VGW processes the TP service request of the user. If the user is not an IMS domain user, the TP service request is sent to the MGCF (Media Gateway Control Function) and processed by the MGCF.

The processing flow of the TP service request initiated by the user in the IMS domain is described in detail in the following embodiments.

Step 102: Construct a TP service suspension request message according to the TP service trigger request.

In order to distinguish from the existing CH service, the embodiment of the present invention provides a solution for constructing a TP service suspension request message. If the user who initiates the TP service is a user in the IMS domain, it is constructed by the AGCF/VGW in which it is located. If the user who initiates the TP service is not a user in the IMS domain, it is constructed by the MGCF.

Specifically, in the embodiment of the present invention, if the user initiating the TP service is a user in the IMS domain, the TP service suspension request message is specifically: extending a relnvite message (re-negotiation request message) under the SIP protocol (session initiation protocol), The content of the TP service suspension request is carried in the renvite message. If the user who initiates the TP service is an IMS domain user, the TP service suspension request message is specifically: Converting the TP service suspension request into a renvite message under the SIP protocol. , carried in the rernvite message Characterizes the content of the TP service suspension request.

Specifically, the content of the TP service suspension request is carried in the renvite message, and the method includes: adding a P-Notification header field to the rernvite message, indicating that the relnvite message is a request message for suspending the TP service, and adding a P-Notification The content of the header field can be: P-Notification: user-susperided; user.

In another embodiment of the present invention, after the foregoing extension of the relnvite message, the session description protocol SDP may also carry a=sendonly for indicating the attribute of the current session.

Step 103: Send a TP service suspension request message to the IP multimedia subsystem IMS core network, so that the IMS core network identifies the TP service suspension request, and performs a TP service suspension operation.

In the embodiment of the present invention, the IMS core network is a general term for the IMS architecture, and includes multiple network elements. The interaction between the network elements in the IMS core network is not involved in the embodiment of the present invention.

After receiving the TP service suspension request message, the IMS core network can recognize that the message is a request to trigger the TP service, and will not be confused with the CH service.

The IMS core network performs the TP service suspension operation, which is specifically: sending the TP service suspension request message to the AGCF/VGW where the call peer is located, so that the AGCF or the VGW suspends the call, and in the case that the call peer is an ISDN user terminal, , sending a Notify notification message to the opposite end of the call;

Alternatively, the TP service suspension request message is sent to the MGCF where the opposite end of the call is located, so that the MGCF converts the TP service suspension request message into a call suspension message recognizable by the call peer, and sends the call suspension message to the opposite end of the call.

The details of the IMS core network performing the TP service suspension operation are described in the following embodiments.

After the call is suspended, the user who initiates the TP service can move the terminal, and can move one phone from one socket to another on the same S interface, or move one call from one phone to another on the same S interface. A phone.

Step 104: Receive the TP service recovery submitted by the ISDN user terminal during the suspension of the call. Request

Step 105: Construct a TP service recovery request message according to the TP service recovery request.

In the process of the call being suspended, the user sends a TP service recovery request through his terminal to request to resume the suspended call. Corresponding to the foregoing step 102, the intra-/out-user of the IMS domain is distinguished, and the network element that receives the TP service recovery request from the user terminal is the AGCF/VGW or the MGCF, and accordingly, the TP service recovery request is constructed by the AGCF/VGW or the MGCF.

Specifically, in the embodiment of the present invention, if the user who initiates the TP service recovery request is a user in the IMS domain, the TP service recovery request message is specifically: the relnvite message in the extended SIP protocol, and the rep service message in the renvite message carries the TP service recovery request. If the user who initiates the TP service recovery request is an IMS domain recovery request, the TP service recovery request message is specifically: the TP service recovery request is converted into a renvvite message in the SIP protocol, and the renvite message carries the TP service recovery request. content.

Specifically, the carrying the content of the TP service recovery request in the renvite message includes: adding a P-Notification header field to the renvv message, indicating that the renvite message is a request message for restoring the TP service, and adding a P-Notification header field The content can be: P-Notification: user-resumed; user.

In another embodiment of the present invention, after performing the foregoing extension on the relnvite message, a=sendrecv may also be carried in the session description protocol SDP, which is used to indicate the attribute of the current session.

Step 106: Send a TP service recovery request message to the IMS core network, so that the IMS core network identifies the TP service recovery request, and performs a TP service recovery operation.

After receiving the TP service recovery request message, the IMS core network can recognize that the message is a call that triggers the TP service to hang before requesting recovery.

The IMS core network performs the TP service recovery operation, specifically: sending the TP service recovery request message to the AGCF/VGW where the call peer is located, so that the AGCF or the VGW resumes the call, and in the case that the call peer is an ISDN user terminal, The call peer sends a Notify notification message; Alternatively, the TP service recovery request message is sent to the MGCF where the opposite end of the call is located, so that the MGCF converts the TP service recovery request message into a call recovery message recognizable by the call peer end, and sends the call recovery message to the call peer end.

The details of the IMS core network performing the TP service recovery operation are described in the following embodiments.

Using the implementation scheme of the terminal mobile service in the IMS architecture disclosed in this embodiment, the IMS core network can identify the TP service initiated by the user, and can be separated from the Call Hold service, so that the charging and traffic statistics can be separately processed for the TP service. .

In combination with the implementation of the terminal mobile service in the IMS architecture disclosed in the foregoing embodiments, the embodiment of the present invention discloses a specific application implementation of the foregoing solution in different scenarios.

Each IMS network is a separate domain. All users belonging to the IMS network are intra-domain users, and users not belonging to the IMS domain are extra-domain users. At the same time, there are CS i or (circuit Switched) in the traditional core network. Domain, circuit switched i or) and PS i or (Packet Switched Domain). In the embodiment of the present invention, a call between users in the same IMS domain is called intra-domain call, a call between a user in the IMS domain and a user outside the IMS domain, and a call between the CS domain user and the PS domain user are collectively referred to as a cross-domain call.

FIG. 2 is a flowchart of processing a TP service when two users are in a call in an IMS domain according to an embodiment of the present invention. The UE-A and the UE-B are two user terminals in the same IMS domain, where UE-A is an ISDN user terminal, and UE-B can be an ISDN user terminal or a non-ISDN user terminal; Core is the IMS core network. The IMS core network is a general term for the IMS architecture, and includes multiple network elements. The interaction between the network elements in the IMS core network is not involved in the embodiment of the present invention.

In the following, during the call between two users, User A initiates a TP service as an example to describe the main steps of the process:

Step 201: During the conversation between user A and user B, user A sends a TP service request through its terminal UE-A, and sends a SUSPEND message requesting to suspend the call. AGCF/VGW to which user A belongs After receiving the SUSPEND message sent by the UE-A, the user is identified as requesting to initiate the TP service, that is, the relnvite message is sent to the IMS core network, where the P-Notification: user-suspended; user indicates that the message is a TP service call. Suspend the request and carry the SDP: a=sendonly , which indicates the attributes of the current session;

Wherein, the P-Notification is the AGCF/VGW in the SIP (Session) in the embodiment of the present invention.

Initiation Protocol, a header field (header) constructed in the message, user-suspended; user is the parameter of the header field; SDP: a=sendonly is the SDP (Session Description Protocol) carried in the SIP message A parameter in ) that is used to represent the properties of the current session.

The relnvite message constructed by the AGCF/VGW in the embodiment of the present invention is exemplified in the following:

INVITE sip: 191.132.61.35 :5060 SIP/2.0

Via: SIP/2.0/UDP 191.103.200.3 :5061; branch=z9hG4bKc68q4puv6kppku5r4mp7q57ov Route:

<sip: 191.133.4.130;lr;Dpt=7574_116;Role=3;CxtId=3;spln=S;X-HwB2bUaCookie=22884>

Call-ID: 544rnu7mnwonqwqkcu4cqn6qc5v767pk@UAC

From: <sip:+8675556271001 @domain4.huawei.com>;tag=8vpm5owc-CC-24-TRC-519 To: <tel:56271002#;phone-context=+86755>;tag=uxug4vo5-CC-58

CSeq: 3 INVITE

Contact: <sip: 191.103.200.3 :5060>

Session-Expires: 1800; refresher=uac

Supported: timer

Max-Forwards: 70

P -Notification: user-susable; user <a parameter in the SDP constructed in the embodiment of the present invention >

X-Trace: 521

Content-Length: 163

Content-Type: application/sdp v=0

o=HuaweiSoftX3000 49 50 IN IP4 191.103.200.3

s=Sip Call c=IN IP4 191.103.230.1

t=0 0

m=audio 232 RTP/AVP 8

a=rtpmap:8 PCMA/8000

a=ptime:20

a=sendonly <a parameter in the SDP constructed in the embodiment of the invention>

After receiving the relnvite message sent by the AGCF/VGW where the user A is located, the IMS core network determines that the message is a TP service call suspension request by using the P-Notification: user-suspended; user carried therein, and the IMS service network can be independent for the TP service. Billing and traffic statistics processing will no longer be confused with Call Hold business requests.

After the IMS core network determines that the message is a TP service call suspension request, it sends an application to the MRFP (Multimedia Resource Function Processor) to play the user B, and informs the other party (user A) that the call has been suspended, and the application is made. After the playback is successful, the media information carried in the renvite message is updated by the IMS core network to the MRFP, so that the UE-B receives the playback normally.

The IMS core network sends the updated relnvite message to the AGCF/VGW where the user B is located. Step 202: The AGCF/VGW where the user B is located receives the relnvite message, modifies the media resource of the call according to the SDP content carried in the message, and suspends the call. User B listens to the sound through his terminal. The AGCF/VGW where the user B is located sends a 200 OK message to the IMS core network. After receiving the 200 OK message forwarded by the IMS core network, the AGCF/VGW of the user A sends a SUSPEND ACK message to the terminal of the user A to notify the peer end (user B). The TP service suspension request has been received. At the same time, the AGCF/VGW where the user B is located triggers the TP service according to the SIP message header i or P-Notification: user-suspended; As described above, the user B can be an ISDN terminal user, or a non-ISDN terminal user, and the AGCF/VGW where the user B is located. If the user B is an ISDN terminal user, a Notify message is sent to notify the user B of the peer user. A has been suspended; if User B is a non-ISDN terminal user, the Notify message is not sent;

After the call is suspended, the user A is allowed to move the terminal, which can take the phone from the same S interface. Move the jacks to another jack, or move the call from one phone to another on the same S interface.

Step 203: When the user A wants to resume the call, the UE-A may send a RESUME message to the AGCF/VGW to which the UE A belongs, requesting to resume the previously suspended call with the user B. After receiving the RESUME message sent by the UE-A, the AGCF/VGW of the user A identifies that the user A requests to resume the call with the user B, and then constructs a rernvite message to be sent to the IMS core network, and carries the P-Notification: user in the message. -resumed; user identifies the message as a TP service call recovery request, and can also carry the SDP: a=sendrecv;

The P-Notification is a header field (header) constructed in the SIP message in the embodiment of the present invention, where user-resumed; user is a parameter of the header field; SDP: a=sendrecv is in the SDP carried in the SIP message. A parameter that represents the properties of the current session.

See the example of the rennvite message mentioned in step 201 above. The renvite message constructed in this step is different from the P-Notification: user-resumed; user and SDP: a= sendrecv. See the previous example. Say it again.

The IMS core network determines that the user A wants to resume the call according to the P-Notification: user-resumed; user in the relnvite message, and then notifies the MRFP to stop the playback of the user B, and sends the relnvite message to the AGCF/VGW where the user B is located.

Step 204: After receiving the relnvite message, the AGCF/VGW of the user B modifies the media resource according to the SDP content carried in the message, and the user A and the user B resume the call. The AGCF/VGW where the user B is located sends a 200 OK message to the IMS core network. After receiving the 200 OK message forwarded by the IMS core network, the AGCF/VGW of the user A sends a RESUME ACK message to the UE-A to notify the peer end (user B). Has received a request to resume the call;

At the same time, the AGCF/VGW where the user B is located is based on the SIP message header field carried in the renvv message, and the P-Notification: user-resumed; user knows that the peer triggers the TP service call recovery. If the user B is an ISDN terminal user, the UE- B sends a Notify message to inform the peer that the call has been resumed; If User B is a non-ISDN terminal user, the Notify message is not sent.

FIG. 3 is a flowchart of processing a TP service during cross-domain call according to an embodiment of the present invention. User A is a user in the IMS domain, and the terminal is a UE-A. The user B is a PSTN (Public Switched Telephone Network) or a PLMN (Public Land Mobile Network) user. The terminal is a UE. -B. MGCF (Media Gateway Control Function), an integral part of IMS, provides protocols between SIP-based (SIPs within the IMS domain) and ISUP-based signaling (PSTN or protocols used by PLMN users) For the conversion, the functions of other network elements shown in FIG. 3 are the same as those shown in FIG. 2, and details are not described herein again.

In this embodiment, during the process in which user A makes a call with user B, user A initiates a TP service. The following is a detailed description of the steps of the TP service processing flow when inter-domain calls are combined with the following figure:

Step 301: During the conversation between user A and B, user A sends a TP service request through its terminal UE-A, and sends a SUSPEND message requesting to suspend the call. After the AGCF/VGW where the user A is located receives the SUSPEND message (the TP service call suspension request) sent by the UE-A, the relnvite message is sent to the IMS core network, where the P-Notification: user-susable is carried. The message is a TP service call suspension request, and can also carry the SDP: a=sendonly; a header field constructed in the information, user-suspended; user is a parameter of the header field; SDP: a=sendonly is a SIP message A parameter in the SDP carried in, used to represent the attributes of the current session.

After receiving the relnvite message sent by the AGCF/VGW where the user A is located, the IMS core network can determine that the message is a TP service call suspension request by using the SIP message header field: P-Notification: user-susable; user Independent billing and traffic statistics processing for TP services will no longer be confused with Call Hold business requests.

The IMS core network applies for the MRFP to play the UE-B, notifying the user B that the other party (user A) has suspended the call, and then sends the relnvite message to the MGCF.

Step 302: The MGCF receives the rernvite message according to P-Notification: user-suspended; user After the IMS terminal (user A terminal) suspends the call, the renvite message is converted into a SUS call suspension message recognizable by the PSTN/PLMN user terminal (UE-B) and sent, and the Subscriber initiated is carried in the SUS message. To indicate that the message is requested by the user;

The SUS call suspension message is a message in the ISUP (ISDN User Part) signaling, which is a message that can be sent by any party in the call, indicating that the calling user or the called user is temporarily disconnected.

The MGCF sends a 200 OK message to the IMS core network. After receiving the 200 OK message forwarded by the IMS core network, the AGCF/VGW of the user A sends a SUSPEND ACK message to the UE-A to notify the peer (user B) that the TP service has been received. Call suspension request;

After the call is suspended, the user A is allowed to move the terminal, which can move the phone from one jack to another on the same S interface, or move the call from one phone to another on the same s interface.

Step 303: When the user A wants to resume the call, the UE-A may send a RESUME message to the AGCF/VGW where the user A is located, requesting to resume the previously suspended call with the user B. After receiving the RESUME message sent by the user A, the AGCF/VGW of the user A constructs a renvite message and sends it to the IMS core network. The message carries the P-Notification: user-resumed; the user identifies the message as the TP service call recovery request. , can also carry SDP: a=sendrecv;

A header field (header), user-resumed; user is a parameter of the header field; SDP: a= sendrecv is a parameter in the SDP carried in the SIP message, used to represent the attributes of the current session.

The IMS core network determines that the user A wants to resume the call according to the P-Notification: user-resumed; user in the relnvite message, and notifies the MRFP to stop the playback of the user B, and sends a relnvite message to the MGCF.

Step 304: The MGCF receives the rernvite message, and according to the P-Notification: user-resumed; user, the IMS terminal (the user A terminal) requests to resume the call, and the renvite message is converted into The RES call recovery message that is identifiable by the PSTN/PLMN user terminal (UE-B) is sent and sent, wherein the RES message carries a Subscriber initiated, to indicate that the message is requested by the user;

The RES call recovery message is a message in the ISUP signaling, which is a message that can be sent by any party in the call, indicating that the calling user or the called user resumes the previously disconnected call.

The MGCF sends a 200 OK message to the IMS core network. After receiving the 200 OK message forwarded by the IMS core network, the AGCF/VGW, where the user A is located, sends a RESUME ACK message to the UE-A to notify the peer (user B) that it has received the resume call. Request.

FIG. 4 is a flowchart of processing a TP service during a cross-domain call according to another embodiment of the present invention. Different from the flow shown in FIG. 3, in this embodiment, the TP service is started by the user outside the domain, where UE-A is the terminal of PSTN/PLMN user A, and UE-B is the terminal of user B in the IMS domain.

Step 401: During the conversation between user A and B, user A sends a TP service request through its terminal UE-A, and sends a SUS call suspension message to request to suspend the call;

After receiving the SUS message, the MGCF converts the message into a SIP protocol renvite message and sends it to the IMS core network. The relnvite message carries the SIP message header field P-Notification: user-suspended; user is used to indicate that the message is TP. The service call suspends the request and can also carry the SDP: a=sendonly (or SDP: a=inacive );

The P-Notification is a header field constructed by the MGCF in the SIP message in the embodiment of the present invention, user-suspended; user is a parameter of the header field; SDP: a=sendonly (or SDP: a=inacive) It is a parameter in the SDP carried in the SIP message and is used to indicate the attributes of the current session.

After receiving the relnvite message sent by the MGCF, the IMS core network sends the relnvite message to the AGCF/VGW where the user B is located.

Step 402: The AGCF/VGW where the user B is located receives the rernvite message, modifies the media resource of the current call according to the SDP content carried in the message, and suspends the call. The AGCF/VGW where the user B is located sends a 200 OK message to the IMS core network. After receiving the 200 OK message forwarded by the IMS core network, the MGCF feeds back an ACK message to the AGCF/VGW where the user B is located through the IMS core network. At the same time, the AGCF/VGW where the user B is located triggers the TP service according to the SIP message header i or P-Notification: user-suspended; As described above, the user B may be an ISDN terminal user or a non-ISDN terminal user, and may be judged by the AGCF/VGW where the user B is located. If the user B is an ISDN terminal user, a Notify message is sent to notify the user B that the peer has Suspend; if User B is a non-ISDN terminal user, the Notify message is not sent; after the call is suspended, User A is allowed to move the terminal, which can move the phone from one socket to another on the same S interface, or Move a call from one phone to another on the same S interface.

Step 403: When user A wants to resume the call with user B, it sends a RES call recovery message to resume the call through its terminal UE-A. After receiving the RES message, the MGCF converts the message into a renvite message of the SIP protocol, and sends the message to the IMS. The core network sends, in the rennvite message, the SIP message header field P-Notification: user-resumed; user indicates that the TP service request is restored, and can also carry the SDP: a=sendrecv, which is used to indicate that the current session belongs to the '1';

The IMS core network sends the received relnvite message to the AGCF/VGW where the user B is located.

Step 404: After receiving the relnvite message, the AGCF/VGW of the user B modifies the media resource according to the SDP content carried in the message, and the user A and the user B resume the call. The AGCF/VGW where the user B is located sends a 200 OK message to the IMS core network. After receiving the 200 OK message forwarded by the IMS core network, the MGCF feeds back an ACK message to the AGCF/VGW where the user B is located through the IMS core network. The AGCF/VGW where the user B is located According to the SIP message header field carried in the renvite message, the P-Notification: user-resumed; user knows that the peer triggers the TP service call recovery. If the user B is an ISDN terminal user, it sends a Notify message to the UE-B to notify the peer that the peer has Resume the call; if User B is a non-ISDN terminal user, the Notify message is not sent.

In conjunction with the implementation method of the terminal mobile service in the IMS architecture disclosed in the foregoing embodiment, the embodiment discloses a device for implementing the terminal mobile service in the IMS architecture, which is used to implement the method disclosed in the foregoing embodiment. FIG. 5 is a schematic structural diagram of an apparatus for implementing a terminal mobile service in an IMS architecture according to an embodiment of the present invention. Details the components of the device are as follows:

The receiving unit 501 is configured to receive a terminal mobile TP service trigger request submitted by the ISDN user terminal during a call by the user;

The constructing unit 502 is configured to construct a TP service suspension request message according to the TP service trigger request received by the receiving unit 501.

Specifically, in the embodiment of the present invention, if the user that initiates the TP service is a user in the IMS domain, the constructing unit 502 constructs a TP service suspension request message, which is specifically: a relnvite message under the extended SIP protocol (session initiation protocol) (re-negotiation request) The message is: carrying the content of the TP service suspension request in the renvite message; if the user initiating the TP service is the IMS domain user, the building unit 502 constructs the TP service suspension request message, specifically: converting the TP service suspension request into The relnvite message in the SIP protocol carries the content that represents the TP service suspension request in the relnvite message.

The sending unit 503 is configured to send, to the IMS core network, a TP service suspension request message constructed by the building unit 502, so that the IMS core network identifies the TP service suspension request, and performs a TP service suspension operation;

The receiving unit 501 is further configured to: in the process of suspending the foregoing user call, receive a TP service recovery request submitted by the user terminal;

The constructing unit 502 is further configured to: construct a TP service recovery request message according to the TP service recovery request received by the receiving unit 501; Specifically, in the embodiment of the present invention, if the user who initiates the TP service recovery request is the user in the IMS domain, the constructing unit 502 constructs the TP service recovery request message, which is specifically: the relnvite message in the extended SIP protocol, and the representation TP in the renvite message The content of the service recovery request; if the user who initiates the TP service recovery request is an IMS domain user, the constructing unit 502 constructs the TP service recovery request message by: converting the TP service recovery request into a relnvite message under the SIP protocol, and carrying the relnvite message in the renvite message Characterizes the content of the TP service recovery request.

The sending unit 503 is further configured to send the TP service recovery request message constructed by the building unit 502 to the IMS core network, so that the IMS core network identifies the TP service recovery request, and performs a TP service recovery operation.

Specifically, when the user who initiates the TP service request is a user in the IMS domain, the device for implementing the terminal mobile service in the IMS architecture provided by the embodiment may be an AGCF or a VGW; The implementation device of the terminal mobile service in the IMS architecture provided by the embodiment may be an MGCF.

Those skilled in the art will appreciate that the various method steps and elements described in connection with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both, in order to clearly illustrate the interoperability of hardware and software. The steps and composition of the various embodiments have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. Those skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention. The method steps described in connection with the embodiments disclosed herein may be implemented in hardware, a software program executed by a processor, or a combination of both. Software programs can be placed in random access memory (RAM), memory, read only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM or technology Any other form of storage medium known.

While some embodiments of the present invention have been shown and described, it will be understood by those skilled in the art The scope of the invention.

Claims

claims

1. A method for implementing terminal mobile services under an IP multimedia subsystem architecture, characterized in that the method includes:

During the user's call, receive the terminal mobile TP service trigger request submitted by the Integrated Services Digital Network ISDN user terminal;

Construct a TP service suspension request message according to the TP service trigger request;

Send the TP service suspension request message to the IP multimedia subsystem IMS core network, so that the IMS core network can identify the TP service suspension request and perform the TP service suspension operation; while the call is suspended In the process, receive the TP service recovery request submitted by the ISDN user terminal;

Construct a TP service recovery request message according to the TP service recovery request;

Send the TP service recovery request message to the IMS core network, so that the IMS core network can identify the TP service recovery request and perform the TP service recovery operation.

2. The method according to claim 1, characterized in that, when the ISDN user is a user in the IMS domain, the construction of the TP service suspension request message is specifically:

The renegotiation request message under the extended session initialization protocol SIP carries content representing the TP service suspension request.

3. The method according to claim 1, characterized in that when the ISDN user is a user outside the IMS domain, the construction of the TP service suspension request message is specifically:

The TP service trigger request is converted into a renegotiation request message under the session initialization protocol SIP, and the renegotiation request message carries content representing the TP service suspension request.

4. The method according to claim 2 or 3, characterized in that the renegotiation request message carries content representing the TP service suspension request, specifically:

Add a P-Notification header field to the renegotiation request message to indicate that the renegotiation request The request message is a request message for suspending the TP service;

The contents of the added P-Notification header field are:

P-Notification: user-suspended;user.

5. The method according to claim 4, further comprising:

The session description SDP in the renegotiation request message carries a=sendonly.

6. The method according to claim 1, characterized in that, when the ISDN user is a user in the IMS domain, the construction of the TP service recovery request message is specifically:

The renegotiation request message under the extended session initialization protocol SIP carries content representing the TP service recovery request.

7. The method according to claim 1, characterized in that, when the ISDN user is a user outside the IMS domain, the construction of the TP service recovery request message is specifically:

The TP service recovery request is converted into a renegotiation request message under the session initialization protocol SIP, and the renegotiation request message carries content representing the TP service recovery request.

8. The method according to claim 6 or 7, characterized in that the renegotiation request message carries content representing the TP service recovery request, specifically:

Add a P-Notification header field to the renegotiation request message to indicate that the renegotiation request message is a request message for resuming the TP service;

The contents of the added P-Notification header field are:

P-Notification: user-resumed;user„

9. The method according to claim 8, further comprising:

The session description SDP in the renegotiation request message carries a= sendrecv.

10. The method according to any one of claims 1 to 9, characterized in that,

The IMS core network performs the TP service suspension operation, specifically:

The IMS core network sends the TP service suspension request message to the access gateway control function entity AGCF or IP call gateway VGW where the call peer is located, so that the AGCF or VGW Suspend the call, and when the call counterparty is an ISDN user terminal, send a Notify notification message to the call counterparty;

The IMS core network performs the TP service recovery operation, specifically as follows:

The IMS core network sends the TP service recovery request message to the AGCF or VGW where the call counterpart is located, so that the AGCF or VGW resumes the call, and when the call counterpart is an ISDN user terminal Next, send a Notify notification message to the call peer.

11. The method according to any one of claims 1 to 9, characterized in that,

The IMS core network sends the TP service suspension request message to the media gateway controller MGCF where the call counterpart is located, so that the MGCF converts the TP service suspension request message into a message that can be used by the call counterpart. Identify the call pause message, and send the call pause message to the call peer;

The IMS core network sends the TP service recovery request message to the MGCF where the call peer is located, so that the MGCF converts the TP service recovery request message into a call recovery message identifiable by the call peer, and sends the call resumption message to the call counterparty.

12. A device for realizing terminal mobile services under an IP multimedia subsystem architecture, characterized in that the device includes:

The receiving unit is used to receive the terminal mobile TP service trigger request submitted by the Integrated Services Digital Network ISDN user terminal during the user's call;

A construction unit, configured to construct a TP service suspension request message according to the TP service trigger request received by the receiving unit;

A sending unit, configured to send the TP service suspension request message constructed by the construction unit to the IP multimedia subsystem IMS core network, so that the IMS core network can identify the TP service suspension request and execute the TP Business suspension operation; The receiving unit is also configured to, during the call suspension process, receive the TP service recovery request submitted by the ISDN user terminal;

The construction unit is also configured to construct a TP service restoration request message according to the TP service restoration request received by the receiving unit;

The sending unit is also configured to send the TP service recovery request message constructed by the construction unit to the IMS core network, so that the IMS core network can identify the TP service recovery request and execute the TP service Resume operations.

13. The device according to claim 12, characterized in that, when the ISDN user is a user in the IMS domain, the construction unit is used to construct the TP service suspension request message, specifically: Extended Session Initialization Protocol The re-negotiation request message under SIP carries content representing the TP service suspension request.

14. The device according to claim 12, characterized in that, when the ISDN user is a user outside the IMS domain, the construction unit is used to construct the TP service suspension request message, specifically: The service triggering request is converted into a renegotiation request message under the Session Initiation Protocol SIP, and the renegotiation request message carries content representing the TP service suspension request.

15. The device according to claim 13 or 14, wherein the renegotiation request message carries content representing the TP service suspension request, specifically:

Add a P-Notification header field to the renegotiation request message to indicate that the renegotiation request message is a request message for suspending the TP service;

The contents of the added P-Notification header field are:

P-Notification: user-suspended;user.

16. The apparatus according to claim 15, wherein the construction unit is further configured to carry a=sendonly in the session description SDP in the renegotiation request message.

17. The device according to claim 12, characterized in that, when the ISDN user is a user in the IMS domain, the construction unit is used to construct the TP service recovery request message, specifically: The re-negotiation request message under the Session Initiation Protocol SIP is extended, and the re-negotiation request message carries content representing the TP service recovery request.

18. The device according to claim 12, characterized in that, when the ISDN user is a user outside the IMS domain, the construction unit is used to construct the TP service recovery request message, specifically: The recovery request is converted into a renegotiation request message under the Session Initiation Protocol SIP, and the renegotiation request message carries content representing the TP service recovery request.

19. The device according to claim 17 or 18, characterized in that the renegotiation request message carries content representing the TP service recovery request, specifically:

The contents of the added P-Notification header field are:

P-Notification: user-resumed;user„

20. The apparatus according to claim 19, wherein the construction unit is further configured to carry a= sendrecv ₀ in the session description SDP in the renegotiation request message.