WO2014005317A1

WO2014005317A1 - Method and corresponding device for presence server to find non-presence user service capability

Info

Publication number: WO2014005317A1
Application number: PCT/CN2012/078267
Authority: WO
Inventors: 梁刚
Original assignee: 华为技术有限公司
Priority date: 2012-07-06
Filing date: 2012-07-06
Publication date: 2014-01-09
Also published as: CN103999425A; CN103999425B

Abstract

Disclosed are a method and corresponding device for a presence server to find non-presence user service capability.The method comprises: a presence server receiving a service capability subscription request sent by a first terminal and carrying an identifier of a second terminal; according to the identifier of the second terminal, determining an SIP OPTIONS capability discovery mechanism supported by an operator to which the second terminal is subordinate; sending to an inter-working function module (IWF) a presence request for subscribing the service capability information about the second terminal so that the IWF converts the presence request into an SIP OPTIONS request, the presence request carrying the identifier of the second terminal; and receiving a NOTIFY message sent by the IWF, the NOTIFY message being converted by the IWF from an SIP OPTIONS response sent to the IWF by an IMS network to which the second terminal is subordinate after the IMS network receives the SIP OPTIONS request sent by the IWF, the NOTIFY message and the SIP OPTIONS response containing the service capability information about the second terminal. Using the present invention, a presence server can obtain service capability information about a non-presence user, thereby avoiding problems such as the inability to obtain service capability and failure of service session invitation due to the utilisation of different service capability mechanisms.

Description

Method and corresponding device for presenting server to discover non-rendering user service capability

The present invention relates to the field of wireless communications, and in particular, to a method and corresponding apparatus for a presence server to discover non-presentation user service capabilities. Background technique

Rich Communication Suite (RCS) is a collection of services based on address book that provides a variety of functions including instant messaging, file transfer, video calling, and video sharing. RCS provides a capability discovery mechanism to discover the type of service that the other party currently supports (such as whether a video call is currently available, whether file transfer is possible, etc.). Only when you know that the other party supports a certain business capability, you can initiate a business invitation to make a call, thereby reducing the invitation failure caused by the other party's failure to support certain business capabilities.

The principle of the Presence-based service capability discovery mechanism is: the requested party terminal publishes its currently available service capability information to the Presence server; the requestor terminal subscribes to the Presence server for the currently available service capability information of the requested party terminal; the Presence server requests the request The party terminal delivers the service capability information available to the requested party terminal. If the service capability information of the requested party terminal changes, the requested terminal will notify the presence server to update; the Presence server will pass the updated service capability information of the requested party terminal through the session initiation protocol (SIP, Session Initiation Protocol). The NOTIFY signaling in ) is sent to the requesting terminal.

The principle of the SIP OPTIONS-based service capability discovery mechanism is: The requesting terminal sends a SIP OPTIONS request to the requested party terminal, and the requested party terminal receives the request and returns a corresponding response, where the response includes the service supported by the requested party terminal. Capability information.

In existing systems, two operators may adopt different service capability discovery mechanisms. For example: Carrier A uses the SIP OPTIONS mechanism and Carrier B uses the Presence mechanism. Since the carrier A does not have the corresponding Presence service support for the service capability discovery, the Presence server cannot obtain the service capability information of the terminal belonging to the operator A. Summary of the invention

The technical problem to be solved by the embodiment of the present invention is to provide a presentation of a presence server. It is not a method and corresponding device for presenting the user's business capabilities. The presence server can be made to discover the business capabilities of non-rendering users.

In order to solve the above technical problem, according to a first aspect of the embodiments of the present invention, an embodiment of the present invention provides a method for a Presence Server to discover a non-presentation user service capability, including: a presence server receiving a subscription second terminal sent by a first terminal The service capability subscription request of the service capability information, the service capability subscription request carrying the identifier of the second terminal; determining, according to the identifier of the second terminal, the operator of the second terminal to support the session initiation protocol, selecting the SIP OPTIONS capability a discovery mechanism: sending a presence request to the second terminal's service capability information to an Interworking Function (IFF), so that the IWF converts the presence request into a SIP OPTIONS request and belongs to the second terminal The IP Multimedia Subsystem (IMS) network sends the SIP OPTIONS request, the Presence request carries the identifier of the second terminal, receives a NOTIFY message sent by the IWF, and the NOTIFY message is sent by the IWF. The IMS to which the second terminal belongs In the transmission network after receiving the SIP OPTIONS request to the IWF in response to the SIP OPTIONS and transformed into the NOTIFY SIP OPTIONS message and said response comprising service capability information of the second terminal.

As a first possibility of the first aspect of the embodiment of the present invention, the determining, by the identifier of the second terminal, that the operator of the second terminal belongs to the session initiation protocol, selects a SIP OPTIONS capability discovery mechanism, including: the presence server is configured according to The identifier of the first terminal and the identifier of the second terminal in the service capability subscription request determine that the second terminal and the first terminal belong to different operators; the presence server operates according to different storages thereof The service capability discovery mechanism supported by the quotient determines that the operator to which the second terminal belongs supports the SIP OPTIONS capability discovery mechanism; if the presence server fails to determine the second terminal according to the service capability discovery mechanism supported by different operators The operator supports the SIP OPTIONS capability discovery mechanism, and the presence server sends the presence request to the second terminal according to the identifier of the second terminal and the IMS network, and the operator that the second terminal belongs to is received. Determining the response of the presence, determining the second terminal It belongs to the operator the ability to support SIP OPTIONS discovery mechanism.

As a second possibility of the first aspect of the embodiment of the present invention, the determining, according to the identifier of the second terminal, that the operator of the second terminal belongs to the session initiation protocol, selects a SIP OPTIONS capability discovery mechanism, including: the presence server is configured according to The identifier of the second terminal and the sending of the presence request to the second terminal by using an IMS network, and receiving an indication that the operator of the second terminal does not support The response of the Presence determines that the operator to which the second terminal belongs supports the SIP OPTIONS capability discovery mechanism.

In combination with the first aspect or the first possible or the second possible third possibility of the embodiment of the present invention, the sending a Presence request for subscribing to the service capability information of the second terminal includes: when the service capability subscription request is periodic At the time of the subscription, the presence server stores a subscription relationship in which the first terminal periodically subscribes to the second terminal service capability information, where the subscription relationship includes a time interval set by the operator or the user to which the first terminal belongs; The time interval set by the operator or the user to which the first terminal belongs is sent, and the presence request is sent.

In combination with the first aspect of the embodiment of the present invention or the first possible or the second possible or the third possible fourth possible, the sending a Presence request to the interworking function module IWF that subscribes to the service capability information of the second terminal includes: The presence server directly communicates with the IWF to send the presence request to the IWF; the receiving the NOTIFY message sent by the IWF includes: the presence server directly communicating with the IWF to receive the IWF sending The NOTIFY message.

In combination with the first aspect or the first possible or the second possible or the third possible fifth possibility of the embodiment of the present invention, the sending a Presence request to the interworking function module IWF that subscribes to the service capability information of the second terminal includes: The presence server sends the presence request to the IWF through the IMS network to which the first terminal belongs; the receiving the NOTIFY message sent by the IWF includes: the presence server receives the location through the IMS network to which the first terminal belongs The second aspect of the embodiment of the present invention is provided by the IWF. The embodiment of the present invention provides a method for the Presence server to discover the service capability of the non-Presence user, including: the interworking function module IWF receives the subscription station sent by the presence server. a presence request of the second terminal service capability information, where the presence request carries the identifier of the second terminal; the Presence request is converted into a SIP OPTIONS request; and the second terminal belongs to the second terminal according to the identifier of the second terminal Sending, by the IMS network, the SIP OPTIONS request; receiving the second terminal belongs to And the SIP OPTIONS response sent by the IMS network to the IWF after receiving the SIP OPTIONS request, and converting the SIP OPTIONS response into a NOTIFY message, where the SIP OPTIONS response and the NOTIFY message include the service of the second terminal Capability information; the NOTIFY message is sent to the presence server.

As a first possibility of the second aspect of the embodiment of the present invention, the method further includes: receiving, by the IWF, a presence request sent by the presence server to subscribe to the second terminal service capability information. And determining, by the IWF, that the operator to which the second terminal belongs supports the SIP OPTIONS capability discovery mechanism, according to the identifier of the second terminal, before the request is converted to the SIP OPTIONS request.

With reference to the second aspect of the embodiment of the present invention or the first possible second possibility, the IWF receiving the presence request sent by the presence server and subscribing to the service capability information of the second terminal includes: the IWF directly interacting with the presence server Communicating to receive the Presence request; the transmitting the NOTIFY message to the presence server comprises: the IWF directly communicating with the presence server to send the NOTIFY message to the presence server.

With reference to the second aspect or the first possible third possibility of the embodiment of the present invention, the IWF receiving the presence request sent by the presence server to subscribe to the service capability information of the second terminal includes: the IWF passing the first terminal The IMS network receives the Presence request; the sending the NOTIFY message to the presence server includes: sending, by the IWF, the NOTIFY message to the presence server by using an IMS network to which the first terminal belongs.

According to a third aspect of the present invention, an embodiment of the present invention further provides a presentation of a presence server, including: a first receiving module, configured to receive a service capability subscription that is sent by a first terminal and subscribes to service capability information of a second terminal. Requesting, the service capability subscription request carries the identifier of the second terminal; and receiving a NOTIFY message sent by the interworking function module IWF, where the NOTIFY message is used by the IWF to belong to the IP multimedia subsystem IMS to which the second terminal belongs The network converts the SIP OPTIONS response sent to the IWF after receiving the SIP OPTIONS request, the NOTIFY message and the SIP OPTIONS response include the service capability information of the second terminal, and the first determining module is configured to The identifier of the second terminal determines that the operator to which the second terminal belongs supports the SIP OPTIONS capability discovery mechanism, and the first sending module is configured to send a presence request for subscribing to the service capability information of the second terminal to the IWF, so that The IWF converts the presence request into the SIP OPTIONS request and to the first IMS network sends the terminal belongs SIP OPTIONS request, the request carries the identifier Presence of the second terminal.

As a first possibility of the third aspect of the embodiment of the present invention, the first determining module includes: a second determining module, configured to: according to the identifier of the first terminal and the second in the service capability subscription request Determining, by the identifier of the terminal, that the second terminal and the first terminal belong to different operators; a first storage module, configured to store a service capability discovery mechanism supported by different operators; and a third determining module, configured to: A service capability discovery mechanism corresponding to different operators stored by a storage module determines The operator of the second terminal supports the SIP OPTIONS capability discovery mechanism.

As a second possibility of the third aspect of the embodiment of the present invention, the first determining module includes: a second sending module, configured to send, according to the identifier of the second terminal, to the second terminal by using an IMS network, a second receiving module, configured to receive a response indicating that the operator to which the second terminal belongs does not support Presence, and a fourth determining module, configured to receive, by the second receiving module, that the second terminal belongs to the operation When the Provider does not support the response of the Presence, it is determined that the operator to which the second terminal belongs supports the SIP OPTIONS capability discovery mechanism.

With reference to the second possible third possibility of the third aspect of the embodiment of the present invention, the first determining module further includes: a fifth determining module, configured to: according to the identifier of the first terminal in the service capability subscription request Determining, by the identifier of the second terminal, that the second terminal and the first terminal belong to different operators; the second storage module is configured to store a service capability discovery mechanism supported by different operators; And determining, according to the service capability discovery mechanism supported by the different operators stored by the second storage module, that the operator of the second terminal supports the SIP OPTIONS capability discovery mechanism, and if not, the second sending module is triggered.

In conjunction with the third aspect of the present invention or the first possible or the second possible or the third possible fourth possible, the presence server further includes: a third storage module, configured to store the first terminal periodic subscription a subscription relationship of the service capability information of the second terminal, where the subscription relationship includes a time interval set by the operator or the user to which the first terminal belongs, and a timing triggering module, configured to set according to the operator or user to which the first terminal belongs The time interval triggers the presence server to send the presence request.

In combination with the third aspect of the embodiment of the present invention or the first possible or the second possible or the third possible or the fourth possible fifth possible, the first sending module is configured to determine the second in the first determining module After the operator of the terminal supports the SIP OPTIONS capability discovery mechanism, the Presence request is sent to the IWF by using the IMS network to which the first terminal belongs; the first receiving module is configured to receive by using the IMS network to which the first terminal belongs. The NOTIFY message sent by the IWF.

With reference to the third aspect of the present invention or the first possible or the second possible or the third possible or the fourth possible sixth possible, the presence server includes the IWF, and the IWF includes: a third receiving module, Directly communicating with the first sending module to receive the Presence request sent by the first sending module, and for receiving the SIP OPTIONS response; and a converting module, configured to convert the Presence request into the SIP An OPTIONS request, and for converting the SIP OPTIONS response into the NOTIFY message; a third sending module, configured to send the SIP OPTIONS request, And for communicating directly with the first receiving module to send the NOTIFY message to the first receiving module.

According to a fourth aspect of the present invention, an embodiment of the present invention further provides an interworking function module IWF, including: a receiving module, configured to receive a presence request sent by a presence server of a first terminal to subscribe to second terminal service capability information The Presence request carries the identifier of the second terminal, and is configured to receive a SIP OPTIONS response sent by the IP Multimedia Subsystem IMS network to which the second terminal belongs to the IWF after receiving the SIP OPTIONS request, the SIP The OPTIONS response includes the service capability information of the second terminal; a conversion module, configured to convert the Presence request into the SIP OPTIONS request, and to convert the SIP OPTIONS response to include the second terminal service capability a NOTIFY message of the information; the sending module, configured to send the SIP OPTIONS request to the IMS network to which the second terminal belongs according to the identifier of the second terminal, and to send the NOTIFY message to the presence server.

As a first possibility of the fourth aspect of the embodiment of the present invention, the IWF further includes: a determining module, configured to determine, according to the identifier of the second terminal in the Presence request, after the receiving module receives the Presence request The operator to which the second terminal belongs supports the SIP OPTIONS capability discovery mechanism.

In conjunction with the fourth aspect of the present invention or the first possible second possibility, the receiving module is configured to directly communicate with the presence server to receive the Presence request sent by the presence server, where the sending module is used to Directly communicating with the presence server to send the NOTIFY message to the presence server.

In conjunction with the fourth aspect of the present invention or the first possible third possibility, the receiving module is configured to receive, by using an IMS network to which the first terminal belongs, the Presence request sent by the presence server, where the sending module is used by Sending the NOTIFY message to the presence server by the IMS network to which the first terminal belongs.

The implementation of the embodiment of the present invention has the following beneficial effects: The IWF is used to perform the corresponding signaling conversion, so that the user who selects the Presence as the service capability discovery mechanism can obtain the service of the user who selects the SIP OPTIONS as the service capability discovery mechanism. The capability information thus avoids the problem that the business capability cannot be obtained due to the adoption of different business capability mechanisms, and the business session invitation fails. DRAWINGS In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description For some embodiments of the present invention, other drawings may be obtained from those skilled in the art without departing from the drawings.

1 is a schematic flow chart of a method for a Presence server to discover non-Presence user service capabilities according to an embodiment of the present invention;

2 is a schematic flow chart of a method for a Presence server to discover non-Presence user service capabilities according to an embodiment of the present invention;

3 is a schematic diagram of a communication flow of a Presence user discovering non-Presence user service capabilities according to an embodiment of the present invention;

4 is a schematic diagram of a communication flow of a Presence user discovering non-Presence user service capabilities according to an embodiment of the present invention;

FIG. 5 is a schematic structural diagram of a Presence Server according to an embodiment of the present invention; FIG.

6A is a schematic diagram showing the structure of a first determining module of a Presence Server according to an embodiment of the present invention;

6B is a schematic diagram showing the structure of a first determining module of a Presence Server according to an embodiment of the present invention;

6C is a schematic diagram showing the structure of a first determining module of a Presence Server according to an embodiment of the present invention;

7 is a schematic structural diagram of a Presence Server according to an embodiment of the present invention;

FIG. 8 is a schematic structural diagram of a Presence Server according to an embodiment of the present invention; FIG.

9 is a schematic structural diagram of a Presence Server according to an embodiment of the present invention;

FIG. 10 is a schematic structural diagram of a Presence server according to an embodiment of the present invention; FIG. 11 is a schematic structural diagram of an IWF according to an embodiment of the present invention;

FIG. 12 is a schematic structural diagram of an IWF according to an embodiment of the present invention. detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, but not all of the embodiments. Based on the embodiments of the present invention, one of ordinary skill in the art does not create All other embodiments obtained under the premise of sexual labor are within the scope of protection of the present invention. FIG. 1 is a schematic flowchart of a method for a Presence server to discover non-Presence user service capabilities according to an embodiment of the present invention. Referring to FIG. 1, the method includes:

S100: The Presence server receives a service capability subscription request that is sent by the first terminal to subscribe to the service capability information of the second terminal, where the service capability subscription request carries the identifier of the second terminal, where the identifier of the second terminal includes a mobile phone number and a universal resource identifier. Uniform Resource Identifier (URI), etc.

S200: Determine, according to the identifier of the second terminal, that the operator to which the second terminal belongs supports the SIP OPTIONS capability discovery mechanism;

S300: Send a presence request to subscribe to the service capability information of the second terminal to the interworking function module IWF, so that the IWF converts the presence request into a SIP OPTIONS request and sends the SIP OPTIONS request to the IP multimedia subsystem IMS network to which the second terminal belongs, The Presence request carries the identifier of the second terminal;

S400: Receive a NOTIFY message sent by the IWF, where the NOTIFY message is converted by the IWF to the SIP OPTIONS response sent by the IMS network of the second terminal to the IWF after receiving the SIP OPTIONS request, and the NOTIFY message and the SIP OPTIONS response include the second The service capability subscription request in the step S100 of the terminal is as follows. It should be noted that the forms of the various messages described in the specification are merely exemplary so that those skilled in the art can fully understand the technical solution claimed by the present invention. It does not limit the scope of protection of the present invention):

SUBSCRIBE sip:deviceA@domainl .com SIP/2.0

To: <sip:deviceB @domain2.com>

From: <sip : device A @ domain 1.com>; tag= 12341234

Call-ID: 12345678

CSeq: 1 SUBSCRIBE

Max-Forwards: 70

Expires: 0

Event: presence

Contact: sip: device A @ domain 1.example.com

Content-Length: 396 <?xml version="1.0" encodings "UTF- 8 "?>

<ns-bindings>

<ns-binding prefix="pidf" urn="urn:ietf:params:xml:ns:pidf"/>

<ns-binding prefix="pdm" urn="urn:ietf:params:xml:ns:pidf:data-model"/>

</ns-bindings>

<what>

<include>//pidf:presence/pdm:service-id</include>

<include>//pidf:presence/pdm:version</include>

</what>

</filter>

</filter-set>

From and To represent the subscriber (first terminal) and the subscriber (second terminal) respectively, Expires indicates the subscription period (the value of Expires is in seconds, the value of Expires is 0 for single subscription, and the value of Expires is greater than 0. Periodic subscription), the second half of the service capability subscription request is Body (message body), indicating that you want to subscribe to the Service ID and Version, which means to subscribe to the other party's business capability information.

In an implementation manner of this embodiment, the Presence server may determine that the operator to which the second terminal belongs supports the SIP OPTIONS capability discovery mechanism in the following two manners:

Manner 1: After step S100, the Presence server sends a p _resence request to the second terminal according to the identifier of the second terminal and the IMS network, and if the operator that the second terminal belongs does not support

Presence response (the response may be a 4XX, 5XX or 6XX response, and the specific response number may be determined according to a protocol signed by the operator of the first terminal and the operator of the second terminal, for example, may indicate that the second terminal belongs to the operation If the 488 response of the presence is not supported, the operator of the second terminal is determined to support the SIP OPTIONS capability discovery mechanism. This method of determination is based on: There are only two modes of the existing RCS service: Presence and OPTIONS, and the two must choose one. Therefore, the operator adopting RCS either supports the Presence service capability discovery mechanism or supports the SIP OPTIONS capability discovery mechanism.

Manner 2: The Presence server can determine, according to the stored information, that the operator to which the second terminal belongs supports the SIP OPTIONS capability discovery mechanism. For example, Presence can store the names of different carriers, The address information and its corresponding supported service capability discovery mechanism are shown in Table 1:

Table 1 )

Specifically, the Presence server may determine, according to the identifier of the first terminal in the From header field of the service capability subscription request and the identifier of the second terminal in the To header field, that the second terminal and the first terminal belong to different operators (for example, if the service capability subscription is In the request, the domain information of the first terminal in the From header field is ©chinamobile.com or starts with 138, and the domain information of the second terminal in the To header field is @chinaunicom.com or starts with 130, then the first terminal belongs to China. Move, the second terminal belongs to China Unicom), and do the following:

The presence server determines the operator to which the second terminal belongs according to the identifier of the second terminal in the To header field of the service capability subscription request, and determines, according to the stored service capability discovery mechanism supported by the different operators, that the operator of the second terminal supports the SIP OPTIONS capability. The discovery mechanism (in this case, the service capability discovery mechanism supported by the different operators stored by the Presence server includes the service capability discovery mechanism supported by the operator to which the second terminal belongs); or, the Presence server supports the corresponding carrier according to the storage. The service capability discovery mechanism cannot determine that the operator of the second terminal supports the SIP OPTIONS capability discovery mechanism. (The Presence server may not store the service capability discovery mechanism of all operators, so in some cases, the judgment cannot be made. For example, the Presence server may not be stored. The service capability discovery mechanism information supported by the operator to which the second terminal belongs, the Presence server sends a presence request to the second terminal through the IMS network according to the identifier of the second terminal, and receives the representation indicating that the second terminal belongs to Business Presence does not support the response, it is determined that the second terminal operator that owns the ability to support SIP OPTIONS discovery mechanism.

In an implementation manner of this embodiment, the Presence server can send a Presence request for subscribing to the service capability information of the second terminal to the IWF in the following two manners: Manner 1: When the service capability subscription request received by the presence server is a single subscription, the Presence server sends a presence request for subscribing to the service capability information of the second terminal to the interworking function module IWF.

Manner 2: When the request for the service capability information received by the Presence server is a periodic subscription, the Presence server stores a subscription relationship in which the first terminal periodically subscribes to the second terminal service capability information, where the subscription relationship includes the operator to which the first terminal belongs or The time interval set by the user, the Presence server periodically sends a presence request to the IWF according to the time interval. For example, the Presence server sends a presence request according to the time interval set by the operator or the user. Specifically, the operator can set the trigger period of the subscription according to its own situation, for example, it is set to 3600 seconds, and the user can also set it by itself (or modify it in the background after setting). The trigger period, for example, is set to 1800 seconds. In this case, according to the carrier's policy, you can select 1800 seconds as the trigger period (that is, the user setting priority), or you can select 3600 seconds as the trigger period (that is, the operator setting priority), and the Presence server can trigger the presence request through the timer. Send.

2 is a schematic flowchart of a method for a Presence server to discover non-Presence user service capabilities according to an embodiment of the present invention. Referring to FIG. 2, the method includes:

S200: The IWF receives a Presence request sent by the Presence server to subscribe to the service capability information of the second terminal, where the Presence request carries the identifier of the second terminal.

S202: Convert the Presence request into a SIP OPTIONS request;

S204: Send a SIP OPTIONS request to the IMS network to which the second terminal belongs according to the identifier of the second terminal.

S206: Receive a SIP OPTIONS response and convert it into a NOTIFY message, where the SIP OPTIONS response is sent by the IMS network to which the second terminal belongs to the IWF after receiving the SIP OPTIONS request, and the SIP OPTIONS response and the NOTIFY message include the service capability of the second terminal. Information

S208: Send a NOTIFY message to the Presence server.

In an implementation manner of this embodiment, the IWF communicates with the Presence server through the IMS network to which the first terminal belongs.

In an implementation manner of this embodiment, the IWF directly performs signaling interaction with the Presence server. FIG. 3 is a schematic diagram of a communication process for a Presence user to discover non-Presence user service capabilities according to an embodiment of the present invention. Referring to FIG. 3, the communication process includes:

Step 1 to Step 2: The first terminal A goes to the Presence Server A through its IMS network A. Sending a service capability subscription request for subscribing to the service capability information of the second terminal (for a description of the service capability subscription request, refer to the corresponding description in the embodiment shown in FIG. 1);

Step 3 to Step 4: The Presence Server A determines the address of the second terminal B according to the identifier of the second terminal in the To header field of the Presence request, and then sends the subscription to the IMS network B to which the second terminal B belongs through the IMS network A. Second, the Presence request of the service capability information of the terminal B, the presence request is as follows:

SUBSCRIBE sip:deviceA@domainl .com SIP/2.0

To: <sip:deviceB @domain2.com>

From: <sip : device A @ domain 1.com>; tag= 12341234

Call-ID: 12345678

CSeq: 1 SUBSCRIBE

Max-Forwards: 70

Expires: 0

Event: presence

Contact: sip: device A @ domain 1.example.com

Content-Length: 396

<?xml version="1.0" encodings "UTF- 8 "?>

<ns-bindings>

<ns-binding prefix="pidf" urn="urn:ietf:params:xml:ns:pidf"/>

<ns-binding prefix="pdm" urn="urn:ietf:params:xml:ns:pidf:data-model"/>

</ns-bindings>

<what>

<include>//pidf:presence/pdm:service-id</include>

<include>//pidf:presence/pdm:version</include>

</what>

</filter>

</filter-set> Step 5 to Step 6: The IMS network B finds that the network does not have the corresponding Presence service support (that is, the operator to which the second terminal belongs does not support the Presence capability discovery mechanism), so the IMS network B sends the non-2XX to the Presence server A through the IMS network A. The response (which may be a 4XX, 5XX, or 6XX response, the specific response number may be determined according to the protocol signed by the operator of the first terminal A and the operator of the second terminal B, for example, may indicate that the operator of the second terminal belongs to Supporting the 488 response of Presence), indicating that there is no corresponding Presence service support in IMS network B;

Step 7 to Step 8: Because there is no corresponding Presence service support in the IMS network B, the Presence Server A determines that the IWF needs to be interoperable, and the Presence Server A sends the Presence request to the IWF through the IMS network A.

Step 9: After receiving the presence request, the IWF may determine, according to the identifier of the second terminal in the presence request, that the operator to which the second terminal belongs supports the SIP OPTIONS capability discovery mechanism (specifically, the IWF may determine according to the identifier of the second terminal B in the presence request) The operator of the second terminal B further determines, according to the information about the service capability discovery mechanism supported by the operator that is sent by the stored or Presence server A, that the operator of the second terminal B supports the SIP OPTIONS capability discovery mechanism, and then sends a message. Converting to convert the presence request into a SIP OPTIONS request and sending the SIP OPTIONS request to the IMS network A; or the IWF receives the _presence request and directly performs signaling conversion to convert the _resenCe request into a SIP OPTIONS request, and The SIP OPTIONS request is sent to IMS network A. In the signaling conversion, the SIP OPTIONS command is used to replace the SUBSCRIBE command in the presence request. The converted SIP OPTIONS request is as follows (omit the message body):

OPTIONS sip: deviceA@domainl .com SIP/2.0

To: <sip:deviceB @domain2.com>

From: Alice <sip : device A @ domain 1.com>; tag=1928301774

Call-ID: a84b4c76e66710

CSeq: 63104 OPTIONS

Contact: <sip: device A @ domain 1.com>;

Accept: application/sdp

Content-Length: 0

Among them, OPTIONS indicates that the request message is a service capability discovery request, and FROM and TO respectively represent the requester (from the header i or the Presence request) and the requested party (the TO header field from the Presence request). Step 10: IMS network A forwards the SIP OPTIONS request to the IMS network B;

Step 11: IMS network B forwards the SIP OPTIONS request to the second terminal B;

Step 12 to Step 14: After receiving the SIP OPTIONS request, the second terminal B generates a corresponding

SIP OPTIONS responds and sends a SIP OPTIONS response to the IWF over IMS network B and IMS network A. The SIP OPTIONS response is as follows:

SIP/2.0 200 OK

To: <sip:deviceB @domain2.com>; tag=93810874

From: Alice <sip : device A @ domain 1.com>; tag=1928301774

Call-ID: a84b4c76e66710

CSeq: 63104 OPTIONS

Contact: <sip:deviceB @domain2.com> ; feature tag =

+g gpp jari-ref="um:urn-7:3gpp-application.ims.iari.gsma-vs'' , +g gpp jari-ref="um:um-7:3gpp-serviceims.icsi.mmtel. Video''

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE

Accept: application/sdp

The OPTIONS response starts with SIP/2.0 plus three digits. FROM and TO represent the subscriber (first terminal A) and the subscriber (second terminal B) respectively. The Feature Tag in the CONTACT header field indicates the first The service capabilities supported by Terminal B (refer to Table 2).

Step 15 to Step 16: The IWF sends a 202 Accept response to the Presence Server A through the IMS network A, indicating that the subscription is accepted;

Step 17 to Step 18: Presence Server A sends a 202 Accept response to the first terminal A through the IMS network A, indicating that the subscription is accepted;

Step 19 to Step 20: After receiving the SIP OPTIONS response including the service capability information of the second terminal B, the IWF performs signaling conversion to convert the SIP OPTIONS response into a NOTIFY message, and sends the IMS network A to the Presence server A. Sending the NOTIFY message; in the signaling conversion process, according to the correspondence between the Tag (feature value) and the Service Tuple (the service tuple, including the service ID and the Version) in the table (2), the SIP OPTIONS response is The Feature Tag is converted into the corresponding Service Tuple information, and the Service Tuple information is placed in the corresponding part of the Body of the NOTIFY message. Of course, in addition to the services listed in Table (2), there are many other services. The relationship between their Feature Tag and Service Tuple is not here. Another example.

Table 2 )

The NOTIFY message is represented by NOTIFY, and FROM and TO respectively represent the subscriber (second terminal B) and the subscriber (first terminal A) described above, that is, the notification is notified by the subscriber to the subscriber. The NOTIFY message carries the service capability information through its message body. The NOTIFY message is as follows:

NOTIFY sip:deviceB@ domain2.com SIP/2.0 To: <sip : device A @ domain 1.com>; tag= 12341234

From: <sip:deviceB @domain2.com>; tag=abcdl234

Call-ID: 12345678

CSeq: 1 NOTIFY

Event: presence

Contact: sip:pa.example.com

Content- Type: application/pidf+xml

Content- Length: 972

<pr:provide-services>

<op:service-id> org.gsma.videoshare

</op:service-id>

<op:service-id> org.3gpp.urn:urn-7:3gpp-service.ims.icsi.mmtel

</op:service-id>

</pr:provide-services> Step 21 to Step 22: Presence Server A sends the NOTIFY message to the first terminal A through the IMS network A after receiving the NOTIFY message;

Step 23 to Step 24: After receiving the NOTIFY message, the first terminal A returns a 200 ok response to the Presence Server A through the IMS network A, and confirms that the NOTIFY message is received.

In this embodiment, the Presence server is separately configured from the IWF, that is, the IWF is a physical entity, and the two perform signaling interaction through the IMS network A.

In an implementation manner of this embodiment, steps 15 to 18 and step 9 have no temporal sequence.

In an implementation manner of this embodiment, step 3 to step 6 may also be replaced by the following manner: Presence server A determines, by using the second type in the embodiment shown in FIG. 1 , that the operator of the second terminal supports SIP OPTIONS capability discovery. The way the mechanism is determined. In another embodiment of the invention, the IWF is integral with the Presence Server and communicates with each other. For example, referring to FIG. 4, FIG. 4 is a schematic diagram of a communication flow in which a Presence user discovers a non-Presence user service capability according to an embodiment of the present invention. (To facilitate the description of the communication process, the IWF and the Presence Server A are still separately expressed in the figure. But in fact, the two constitute a whole). In this embodiment, the Presence Server A stores service capability information corresponding to different operators (including the operator to which the second terminal B belongs). specific:

Step a1 to step a2: The first terminal A sends a service capability subscription request for subscribing to the service capability information of the second terminal B to the presence server A through its IMS network A, and the Exprires value in the service capability subscription request is greater than 0, for example, the Exprires value is 3600 (the format of the service capability subscription request, the Presence request, the SIP OPTIONS request, the SIP OPTIONS response, and the NOTIFY message in this embodiment, and the conversion between the signaling, please refer to FIG. 1 and FIG. Corresponding description in the embodiment, no further details here;

Step a3: The Presence Server A determines that the subscription is a periodic subscription according to the value of the Exprires in the service capability subscription request, and then stores the periodic subscription relationship in which the first terminal A periodically subscribes to the service capability information of the second terminal B; Presence Server A Determining the operator to which the first terminal A and the second terminal B belong according to the identifier of the first terminal A in the From header field and the identifier of the second terminal B in the To header field in the service capability subscription request, and determining the second terminal B and the second terminal A terminal A belongs to different operators, and then determines that the operator of the second terminal B supports the SIP OPTIONS capability discovery mechanism according to the service capability mechanism supported by the different operators stored in the Presence server; the Presence server A according to the carrier in the periodic subscription relationship Or sending a presence request to the IWF at a time interval set by the user (specifically, refer to the corresponding description in the embodiment shown in FIG. 1);

Step b to step d: After receiving the presence request, the IWF converts it into a SIP OPTIONS request (or the IWF receives the presence request and determines, according to the identifier of the second terminal in the Presence request, that the operator of the second terminal supports the SIP OPTIONS capability discovery mechanism. Afterwards, the Presence request is converted into a SIP OPTIONS request;), and the SIP OPTIONS request is sent to the second terminal B through the IMS network A and the IMS network B;

Step e to step g: After receiving the SIP OPTIONS request, the second terminal B sends the SIP OPTIONS response to the IWF through the IMS network B and the IMS network A. The SIP OPTIONS response includes the service capability information of the second terminal B.

Step h: The IWF sends a response indicating that the subscription is accepted to the Presence Server A (202 Accept response);

Step i: The IWF converts the SIP OPTIONS response into a NOTIFY message, and sends the NOTIFY message to the Presence server A;

Step j to step K: Presence server A sends a NOTIFY message to the first terminal A through the IMS network A;

Step 1 to Step m: The first terminal A sends a response to the Presence Server A through the IMS network A to confirm receipt of the NOTIFY message.

In an implementation manner of this embodiment, step h and step b have no prioritized sequence. In an implementation manner of this embodiment, in the periodic subscription, during the subscription period (determined according to the Expires value in the Presence subscription request), the second terminal B may include the latest when the service capability changes. The SIP OPTIONS response of the service capability information is sent to the IWF to be converted by the IWF into a NOTIFY message and sent to the Presence Server A, without sending a corresponding response only when receiving the SIP OPTIONS request; Presence Server A receives the NOTIFY message. If it is determined that the service capability of the second terminal B has not changed, the NOTIFY message may not be sent to the first terminal A, and the NOTIFY message may be sent to the first terminal A only when the service capability of the second terminal B changes.

Of course, whether it is a single subscription or a periodic subscription, the Presence Server and the IWF can be used as physical entities alone or in combination.

In an embodiment of the present invention, when the second terminal B is offline, the IMS network B to which the second terminal B belongs receives the SIP OPTIONS request and returns a SIP OPTIONS response indicating that the second terminal B is offline (for example: 480 response, indicating that the message is temporarily unreachable). For example, in the embodiment shown in FIG. 3, if the second terminal B is not online, step 11 and step 12 are not performed in the communication flow; and, for example, in the embodiment shown in FIG. 4, if the second terminal B is not online Then, step d to step e are not performed in the communication process. Of course, the SIP OPTIONS response and the NOTIFY message converted by the response may also be changed. For example, SIP OPTIONS may be:

SIP/2.0480 Temporarily Unavailable

To: <sip:deviceB @domain2.com>; tag=93810874

From: Alice <sip : device A @ domain 1.com>; tag=1928301774

Call-ID: a84b4c76e66710

CSeq: 63104 OPTIONS Contact: <sip:deviceB @domain2.com>;

Accept: application/sdp

After receiving the response, the IWF converts the response to a SIP NOTIFY message by blanking the contents of the <pr:provide-services> tag in the message body to indicate that the other party's service capability is not obtained. The NOTIFY message can be:

NOTIFY sip: deviceB@domain2.com SIP/2.0

To: <sip : device A @ domain 1.com>; tag= 12341234

From: <sip:deviceB @domain2.com>; tag=abcdl234

Call-ID: 12345678

CSeq: 1 NOTIFY

Event: presence

Contact: sip:pa.example.com

Content- Type: application/pidf+xml

Content- Length: 376

<pr:provide-servicesx/pr:provide-services> Of course, the SIP OPTIONS response that does not contain the service capability information may be another 4XX response indicating that the request failed, in addition to the 480 response indicating that the message is temporarily unreachable, indicating that the server is in error. The 5XX response, the 6XX response indicating the system error, etc., the corresponding NOTIFY message also does not include the service capability information of the second terminal.

FIG. 5 is a schematic structural diagram of a Presence server according to an embodiment of the present invention. The Presence server 50 includes:

The first receiving module 500 is configured to receive a service capability subscription request that is sent by the first terminal to subscribe to the service capability information of the second terminal, where the service capability subscription request carries the identifier of the second terminal, and is configured to receive the NOTIFY message sent by the IWF. The NOTIFY message is converted by the IWF to the SIP OPTIONS response sent by the IMS network to which the second terminal belongs to the IWF after receiving the SIP OPTIONS request, and the NOTIFY message and the SIP OPTIONS response include the service capability information of the second terminal;

The first determining module 502 is configured to determine, according to the identifier of the second terminal, the operator support of the second terminal SIP OPTIONS capability discovery mechanism;

The first sending module 504 is configured to send a Presence request for subscribing to the service capability information of the second terminal to the IWF, so that the IWF converts the Presence request into a SIP OPTIONS request and sends a SIP OPTIONS request to the IMS network to which the second terminal belongs, the Presence request Carry the identifier of the second terminal.

The first determining module 502 can have multiple implementation manners. For example, referring to FIG. 6A, the first determining module 502 can include:

a second determining module 600, configured to determine, according to the identifier of the first terminal and the identifier of the second terminal in the service capability subscription request, that the second terminal and the first terminal belong to different operators; a storage module 602, configured to store a service capability discovery mechanism supported by different operators; and a third determining module 604, configured to determine the second according to a service capability discovery mechanism supported by different operators stored by the first storage module 602 The operator of the terminal supports the SIP OPTIONS capability discovery mechanism. Specifically, the second determining module 600 or the third determining module 604 may determine, according to the identifier of the second terminal, which carrier the second terminal belongs to, and then according to the first storage module 600. The stored information determines that the operator supports the business capability discovery mechanism.

Alternatively, referring to FIG. 6B, the first determining module 502 may include:

The second sending module 610 is configured to send a presence request to the second terminal according to the identifier of the second terminal and by using the IMS network. For example, after the Presence server receives the service capability subscription request, the Presence request may be sent to the second terminal by using the IMS network. , or trigger the sending of a presence request through a timer.

The second receiving module 612 is configured to receive a response indicating that the operator to which the second terminal belongs does not support Presence;

The fourth determining module 614 is configured to: when the second receiving module 612 receives the response indicating that the operator to which the second terminal belongs does not support the Presence, determine that the operator to which the second terminal belongs supports the SIP OPTIONS capability discovery mechanism.

Alternatively, referring to FIG. 6C, the first determining module 502 may include the foregoing second sending module 610, second receiving module 612, fourth determining module 614, and:

The fifth determining module 616 is configured to determine, according to the identifier of the first terminal and the identifier of the second terminal in the service capability subscription request, that the second terminal and the first terminal belong to different operators;

The second storage module 618 is configured to store a service capability discovery mechanism supported by different operators. The sixth determination module 620 is configured to support different operators according to the second storage module 618. The service capability discovery mechanism determines that the operator to which the second terminal belongs supports the SIP OPTIONS capability discovery mechanism; if not, the second sending module 610 is triggered to send a presence request to the second terminal through the IMS network.

In an implementation manner of the embodiment shown in FIG. 5, the Presence server and the IWF each constitute a physical entity, and the two can perform various signaling interactions through the IMS network to which the first terminal belongs. The various signaling includes: a Presence request, The NOTIFY message, and the response sent by the IWF to the Presence Server indicating acceptance of the subscription (eg, 202 response), the response may be received by the first receiving module of the Presence Server.

In an implementation of the embodiment shown in FIG. 5, referring to FIG. 7, the Presence server 50 and the IWF 70 are integrated, that is, the Presence server 50 includes an IWF 70, and the IWF 70 includes:

The third receiving module 700 is configured to directly communicate with the first sending module 504 to receive the Presence request sent by the first sending module 504, and to receive a SIP OPTIONS response, where the SIP OPTIONS response may be generated by the second terminal;

The conversion module 702 is configured to convert the Presence request into a SIP OPTIONS request, and to convert the SIP OPTIONS response into a NOTIFY message;

The third sending module 704 is configured to send a SIP OPTIONS request to the IMS network to which the second terminal belongs, and to directly communicate with the first receiving module 500 to send the NOTIFY message to the first receiving module 500.

The conversion module 702 can include: a first conversion module and a second conversion module.

Specifically, the first conversion module is configured to convert the SIP SUBSCRIBE command used in the Presence request into a SIP OPTIONS command;

The second conversion module is configured to convert the feature value indicating the service capability information in the SIP OPTIONS response into the corresponding service tuple information and fill the service tuple information into the NOTIFY in the case that the SIP OPTIONS response includes the second terminal service capability information. In the message body of the message; in the case that the SIP OPTIONS response does not include the second terminal service capability information, the content in the tag indicating the service capability information in the message body of the NOTIFY message is blanked.

In this implementation, the third sending module 704 of the IWF can directly communicate with the first receiving module 500 to send a response indicating acceptance of the subscription to the first receiving module 500.

FIG. 8 is a schematic structural diagram of a presence server according to an embodiment of the present invention. Referring to FIG. 8, the Presence server 80 includes: a first receiving module 800, a first determining module 802, and a first sending module. Block 804, and:

The third storage module 806 is configured to store a subscription relationship in which the first terminal periodically subscribes to the second terminal service capability information (for example, when the service capability subscription request received by the first receiving module 800 indicates a periodic subscription), the subscription The relationship includes a time interval set by an operator or a user to which the first terminal belongs;

The timing triggering module 808 is configured to trigger the Presence server to send a Presence request according to a time interval set by an operator or a user to which the first terminal belongs.

For the description of the first receiving module 800, the first determining module 802, and the first sending module 804, please refer to the first receiving module 500, the first determining module 502, and the first sending module 504 in the embodiment shown in FIG. Description, no longer detailed here.

In an implementation manner of the embodiment shown in FIG. 8, the Presence server and the IWF each constitute a physical entity, and the two can perform various signaling interactions through the IMS network to which the first terminal belongs. The various signaling includes: a Presence request, The NOTIFY message, and the response sent by the IWF to the Presence Server indicating acceptance of the subscription (eg, 202 response), the response may be received by the first receiving module 800 of the Presence Server.

In an implementation manner of the embodiment shown in FIG. 8, referring to FIG. 9, the Presence server 80 and the IWF 90 are integrated, that is, the Presence server 80 includes an IWF 90, and the IWF 90 includes: a third receiving module 900, a conversion module 902, and a Three transmitting module 904. For a description of the third receiving module 900, the converting module 902, and the third sending module 904, refer to the description of the third receiving module 700, the converting module 702, and the third sending module 704 in the embodiment shown in FIG. No longer detailed.

FIG. 10 is a schematic structural diagram of a Presence server according to an embodiment of the present invention. The Presence server 100 includes: a transceiver 101, a memory 102, and a processor 103.

In an implementation manner of the embodiment, the transceiver 101 is configured to communicate with an external device, receive a service capability subscription request that is sent by the first terminal and subscribe to the service capability information of the second terminal, and send a service to the IWF to subscribe to the second terminal. The presence request of the capability information, and the reception of the NOTIFY message and the transmission of the service capability information of the second terminal to the first terminal, and the reception and transmission of other messages are not limited herein. The memory 102 is coupled to a processor 103 for storing various programs and applications, and is called by the processor 103 to execute the programs and applications to perform the corresponding functions. Specifically, the processor 103 can be used to determine that the operator of the second terminal supports the SIP OPTIONS capability discovery mechanism. For the specific determination manner, refer to the corresponding description in the embodiment shown in FIG. 1.

In addition, the processor 103 in this implementation manner may also be used to execute the method embodiment shown in FIG. The steps of the description and the steps performed by the server in the embodiment shown in FIG. 3 and FIG. 4 are not described in detail herein.

In another implementation manner of the embodiment, the transceiver 101 is configured to communicate with an external device, and receive a service capability subscription request that is sent by the first terminal and subscribe to the service capability information of the second terminal, and send the service capability subscription request to the IMS network to which the second terminal belongs. The SIP OPTIONS request, and receiving the SIPOPTIONS response sent by the IMS network to which the second terminal belongs after receiving the SIP OPTIONS request, and transmitting the service capability information of the second terminal to the first terminal, and receiving and transmitting other messages, the present invention implements The example is not limited here. The memory 102 is coupled to a processor 103 for storing various programs and applications, and is called by the processor 103 to execute the programs and applications to perform the corresponding functions. Specifically, the processor 103 may be configured to determine, according to the identifier of the second terminal, that the operator to which the second terminal belongs supports the SIP OPTIONS capability discovery mechanism (refer to the corresponding description in the embodiment shown in FIG. 1 for the specific determination manner); The conversion of the Presence request and the SIP OPTIONS request and the conversion of the SIP OPTIONS response and the NOTIFY message (refer to the corresponding description in the embodiment shown in FIG. 3 for the specific signaling conversion manner) and the like. In this implementation, the IWF and the Presence server are integrated, and the processor 103 calls the program and the application in the memory 102 to implement message passing between the two, including: a Presence request, a NOTIFY message, a 202Accept response, and the like.

In addition, the processor 103 in this implementation manner may also be used to perform the steps described in the method embodiments shown in FIG. 1 and FIG. 2 and the steps performed by the presentation server and the IWF in the embodiments shown in FIG. 3 and FIG. The embodiments of the present invention are not described in detail herein.

FIG. 11 is a schematic structural diagram of an IWF according to an embodiment of the present invention. Referring to FIG. 11, the IWF 110 includes:

The receiving module 1100 is configured to receive a Presence request sent by the Presence server of the first terminal to subscribe to the service capability information of the second terminal, where the Presence request carries the identifier of the second terminal, and is configured to receive the IMS network to which the second terminal belongs to receive a SIP OPTIONS response sent to the IWF after the SIP OPTIONS request, the SIP OPTIONS response containing the service capability information of the second terminal; the conversion module 1102, configured to convert the Presence request into a SIP OPTIONS request, and convert the SIP OPTIONS response to include The NOTIFY message of the second terminal service capability information;

The sending module 1104 is configured to send, according to the identifier of the second terminal, a SIP OPTIONS request to the IMS network to which the second terminal belongs, and send a NOTIFY message to the presence server.

The determining module 1106 is configured to, according to the Presence, after the receiving module 1100 receives the presence request The identifier of the second terminal in the request determines that the operator to which the second terminal belongs supports the SIP OPTIONS capability discovery mechanism, thereby ensuring the conversion module 1102 performs the conversion of the presence request and the validity of the sending module 1104 to perform the SIP OPTIONS request. The determining module 1106 is a selectable module, that is, the IWF 110 may not have the determining module 1106 without affecting the normal implementation of the embodiment of the present invention.

The receiving module 1100 can directly communicate with the Presence server to receive the Presence request sent by the Presence server. The sending module 1104 can directly communicate with the Presence server to send a NOTIFY message to the Presence server. At this time, the sending module 1104 can also directly communicate with the Presence server to send. Represents a response to accept a subscription (for example: 202 response). Alternatively, the receiving module 1100 may receive the presence request sent by the Presence server through the IMS network to which the first terminal belongs; the sending module 1104 may send a NOTIFY message to the Presence server through the IMS network to which the first terminal belongs, and the sending module 1104 may also pass the first The IMS network to which the terminal belongs sends a response to the Presence Server indicating acceptance of the subscription.

The conversion module 1102 can include: a first conversion module and a second conversion module.

The second conversion module is configured to convert, in the case that the SIP OPTIONS response includes the second terminal service capability information, a feature value indicating the service capability information in the SIP OPTIONS response into a corresponding service tuple information and the service The tuple information is filled in the message body of the NOTIFY message; in the case that the SIP OPTIONS response does not include the second terminal service capability information, the content in the label indicating the service capability information in the message body of the NOTIFY message is Blanking.

FIG. 12 is a schematic structural diagram of an IWF according to an embodiment of the present invention. The IWF 120 includes: a transceiver 121, a memory 122, and a processor 123.

Specifically, the transceiver 121 can be configured to communicate with the outside, for example, receiving a presence request sent by the Presence server to subscribe to the second terminal service capability information, sending a SIP OPTIONS request to the second terminal, and receiving the SIP OPTIONS response and sending the response to the Presence server. The NOTIFY message, and the receiving and sending of other messages, are not limited herein. The memory 122 is coupled to a processor 122 for storing various programs and applications, and is called by the processor 123 to execute the programs and applications to implement the corresponding functions. Specifically, the processor 123 is configured to convert the Presence request received by the transceiver 121 into a SIP OPTIONS request, and convert the SIP OPTIONS response received by the transceiver 121 into a corresponding NOTIFY message. For the specific conversion process, refer to FIG. 3 Corresponding description in the illustrated embodiment.

In the various device embodiments of the present invention, for a detailed description of the conversion of various signaling and signaling therein, and a description of the method for implementing the corresponding functions of each module of the device, refer to the corresponding in the method embodiment above. description.

A person skilled in the art can understand that all or part of the process of implementing the above embodiment method can be completed by a computer program to instruct related hardware, and the program can be stored in a computer readable storage medium. In execution, the flow of an embodiment of the methods as described above may be included. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

The above description is only a preferred embodiment of the present invention, and the scope of the present invention is not limited thereto, and the equivalent changes made by the claims of the present invention are still within the scope of the present invention.

Claims

Rights request

1. A method for a presence server to discover the service capabilities of non-presence users, characterized in that the method includes:

The presence server receives a service capability subscription request sent by the first terminal to subscribe to the service capability information of the second terminal, where the service capability subscription request carries the identifier of the second terminal;

Determine that the operator to which the second terminal belongs supports the session initialization protocol and select the SIP OPTIONS capability discovery mechanism according to the identifier of the second terminal;

Send a presence request for subscribing to the service capability information of the second terminal to the interworking function module IWF, so that the IWF converts the presence request into a SIP OPTIONS request and sends the presence request to the IMS network of the IP multimedia subsystem to which the second terminal belongs. The SIP OPTIONS request, the Presence request carries the identity of the second terminal;

Receive the notification NOTIFY message sent by the IWF. The NOTIFY message is formed by the IWF converting the SIP OPTIONS response sent to the IWF by the IMS network to which the second terminal belongs after receiving the SIP OPTIONS request, so The NOTIFY message and the SIP OPTIONS response include service capability information of the second terminal.

2. The method according to claim 1, characterized in that, determining based on the identifier of the second terminal that the operator to which the second terminal belongs supports session initialization protocol selection SIP OPTIONS capability discovery mechanism includes:

The presence server determines that the second terminal and the first terminal belong to different operators based on the identity of the first terminal and the identity of the second terminal in the service capability subscription request;

The presence server determines that the operator to which the second terminal belongs supports the SIP OPTIONS capability discovery mechanism based on the service capability discovery mechanisms stored by the presence server corresponding to different operators. If the capability discovery mechanism cannot determine that the operator to which the second terminal belongs supports the SIP OPTIONS capability discovery mechanism, the presence server sends the presence request to the second terminal according to the identifier of the second terminal and through the IMS network, and receives When receiving a response indicating that the operator to which the second terminal belongs does not support Presence, it is determined that the operator to which the second terminal belongs supports the SIP OPTIONS capability discovery mechanism.

3. The method according to claim 1, characterized in that, determining based on the identifier of the second terminal that the operator to which the second terminal belongs supports session initialization protocol selection SIP OPTIONS capability discovery mechanism includes:

The presence server sends the presence request to the second terminal according to the identity of the second terminal and through the IMS network, and upon receiving a response indicating that the operator to which the second terminal belongs does not support presence, determines that the first The operator to which the second terminal belongs supports the SIP OPTIONS capability discovery mechanism.

4. The method according to any one of claims 1 to 3, characterized in that said sending a Presence request for subscribing to the service capability information of the second terminal includes:

When the service capability subscription request is a periodic subscription, the presence server stores a subscription relationship for the first terminal to periodically subscribe to the service capability information of the second terminal. The subscription relationship includes an operation to which the first terminal belongs. The time interval set by the supplier or user;

The presence request is sent according to the time interval set by the operator or user of the first terminal.

5. The method according to any one of claims 1 to 4, characterized in that,

The sending of the Presence request for subscribing the service capability information of the second terminal to the interworking function module IWF includes:

The presence server communicates directly with the IWF to send the Presence request to the IWF;

The receiving the NOTIFY message sent by the IWF includes:

The presence server communicates directly with the IWF to receive the NOTIFY message sent by the IWF.

6. The method according to any one of claims 1 to 4, characterized in that,

The presence server sends the Presence request to the IWF through the IMS network to which the first terminal belongs;

The receiving the NOTIFY message sent by the IWF includes: The presence server receives the NOTIFY message sent by the IWF through the IMS network to which the first terminal belongs.

7. A method for a presence server to discover the service capabilities of non-presence users, characterized in that the method includes:

The interworking function module IWF receives a Presence request sent by the presence server to subscribe to the service capability information of the second terminal, where the Presence request carries the identity of the second terminal;

Convert the Presence request into a SIP OPTIONS request;

Send the SIP OPTIONS request to the IMS network to which the second terminal belongs according to the identification of the second terminal;

Receive the SIP OPTIONS response sent to the IWF by the IMS network to which the second terminal belongs after receiving the SIP OPTIONS request and convert the SIP OPTIONS response into a NOTIFY message, where the SIP OPTIONS response and the NOTIFY message include Business capability information of the second terminal;

Send the NOTIFY message to the presence server.

8. The method according to claim 7, characterized in that, the method further includes:

After the IWF receives the presence request sent by the presence server to subscribe to the service capability information of the second terminal, and before converting the presence request into a SIP OPTIONS request, the IWF determines the presence of the second terminal according to the identity of the second terminal. It is determined that the operator to which the second terminal belongs supports the SIP OPTIONS capability discovery mechanism.

9. The method according to claim 7 or 8, characterized in that,

The IWF receiving the Presence request sent by the presence server to subscribe to the service capability information of the second terminal includes:

The IWF communicates directly with the presence server to receive the Presence request;

Sending the NOTIFY message to the presence server includes:

The IWF communicates directly with the presence server to send the NOTIFY message to the presence server.

10. The method according to claim 7 or 8, characterized in that,

The IWF receives the Presence request through the IMS network to which the first terminal belongs; sending the NOTIFY message to the presence server includes:

The IWF sends the NOTIFY message to the presence server through the IMS network to which the first terminal belongs.

11. A presence server, characterized in that, the presence server includes: a first receiving module: configured to receive a business capability subscription request sent by a first terminal to subscribe to the business capability information of a second terminal, the business capability subscription The request carries the identification of the second terminal; and is used to receive the NOTIFY message sent by the interworking function module IWF. The NOTIFY message is sent by the IWF to the IP multimedia subsystem IMS network to which the second terminal belongs after receiving the SIP OPTIONS request. The NOTIFY message and the SIP OPTIONS response include the service capability information of the second terminal;

A first determination module, configured to determine, according to the identifier of the second terminal, that the operator to which the second terminal belongs supports the SIP OPTIONS capability discovery mechanism;

A first sending module, configured to send a presence request for subscribing to the service capability information of the second terminal to the IWF, so that the IWF converts the presence request into the SIP OPTIONS request and sends it to the second terminal. The IMS network sends the SIP OPTIONS request, and the Presence request carries the identity of the second terminal.

12. The presence server of claim 11, wherein the first determination module includes: a second determination module, configured to determine based on the identity of the first terminal and the third terminal in the service capability subscription request. The identifiers of the two terminals determine that the second terminal and the first terminal belong to different operators; the first storage module is used to store the service capability discovery mechanisms correspondingly supported by different operators; the third determination module is used to determine according to the The service capability discovery mechanism correspondingly supported by different operators stored in the first storage module determines that the operator to which the second terminal belongs supports the SIP OPTIONS capability discovery mechanism.

13. The presence server of claim 11, wherein the first determining module includes: a second sending module, configured to send the information to the second terminal according to the identity of the second terminal and through the IMS network. Described Presence request;

A second receiving module, configured to receive a response indicating that the operator to which the second terminal belongs does not support Presence;

The fourth determination module is configured to determine that the operator to which the second terminal belongs supports the SIP OPTIONS capability discovery mechanism when the second receiving module receives a response indicating that the operator to which the second terminal belongs does not support Presence.

14. The presentation server according to claim 13, wherein the first determination module further includes:

A fifth determination module, configured to determine that the second terminal and the first terminal belong to different operators based on the identity of the first terminal and the identity of the second terminal in the service capability subscription request; second The storage module is used to store the service capability discovery mechanisms correspondingly supported by different operators; the sixth determination module is used to determine the second terminal to which the second terminal belongs based on the service capability discovery mechanisms correspondingly supported by different operators stored in the second storage module. The operator supports the SIP OPTIONS capability discovery mechanism. If it cannot be determined, the second sending module is triggered.

15. The presentation server according to any one of claims 11 to 14, characterized in that, the presentation server further includes:

A third storage module configured to store a subscription relationship in which the first terminal periodically subscribes to the service capability information of the second terminal, where the subscription relationship includes a time interval set by the operator or user to which the first terminal belongs;

A timing triggering module, configured to trigger the presence server to send the presence request according to a time interval set by the operator or user to which the first terminal belongs.

16. The presentation server according to any one of claims 11 to 15, characterized in that,

The first sending module is configured to send the presence request to the first terminal through the IMS network to which the first terminal belongs after the first determining module determines that the operator to which the second terminal belongs supports the SIP OPTIONS capability discovery mechanism. IWF; The first receiving module is configured to receive the NOTIFY message sent by the IWF through the IMS network to which the first terminal belongs.

17. The presentation server according to any one of claims 11 to 15, characterized in that the presentation server includes the IWF, and the IWF includes:

A third receiving module, configured to communicate directly with the first sending module to receive the Presence request sent by the first sending module, and to receive the SIP OPTIONS response;

A conversion module, used to convert the Presence request into the SIP OPTIONS request, and used to convert the SIP OPTIONS response into the NOTIFY message;

The third sending module is used to send the SIP OPTIONS request, and is used to directly communicate with the first receiving module to send the NOTIFY message to the first receiving module.

18. An interoperability function module IWF, characterized in that the IWF includes:

A receiving module, configured to receive a presence request sent by the presence server of the first terminal to subscribe to the service capability information of the second terminal, where the presence request carries the identification of the second terminal; and to receive the IP multimedia to which the second terminal belongs. After receiving the SIP OPTIONS request, the subsystem IMS network sends a SIP OPTIONS response to the IWF, where the SIP OPTIONS response contains the service capability information of the second terminal;

A conversion module for converting the Presence request into the SIP OPTIONS request, and for converting the SIP OPTIONS response into a NOTIFY message containing the second terminal service capability information;

A sending module, configured to send the SIP OPTIONS request to the IMS network to which the second terminal belongs according to the identity of the second terminal, and to send the NOTIFY message to the presence server.

19. The IWF according to claim 18, characterized in that the IWF further includes:

A determining module, configured to determine that the operator to which the second terminal belongs supports the SIP OPTIONS capability discovery mechanism based on the identity of the second terminal in the presence request after the receiving module receives the presence request.

20. The IWF according to claim 18 or 19, characterized in that, The receiving module is used to communicate directly with the presence server to receive the Presence request sent by the presence server, and the sending module is used to communicate directly with the presence server to send the NOTIFY message to the presence server. ; or,

The receiving module is configured to receive the Presence request sent by the presence server through the IMS network to which the first terminal belongs, and the sending module is used to send the NOTIFY to the presence server through the IMS network to which the first terminal belongs. information.