WO2008125058A1 - A method, system and apparatus for determining the routing gateway - Google Patents

Abstract

There are a method, a system and an apparatus for determining the routing gateway, so that when the converged message service user being as the calling party sends a message to the non-converged message service user, the converged message service network is able to correctly determine the gateway within the called network which can routes the message. The method includes that receiving the message sent from the converged message service user to the non-converged message service user; inquiring the message service support capability information of the non-converged message service user; based on the message service support capability information, determining the gateway within the network where the non-converged message service user locates. The address book function entity includes: a saving unit for saving the message service support capability information of the non-converged message service user who is in connection with the converged message service user; a configuration unit for updating the message service support capability information of the corresponding non-converged message service user saved in the saving unit based on the received message service support capability information of the non-converged message service user.

Description

 Method, system and device for determining routing gateway

Technical field

 The present invention relates to the field of communications, and in particular, to a method, system and apparatus for determining a routing gateway. Background technique

 With the development of telecommunication services, more and more message services have emerged, such as SMS (Short Message Service), MMS (Multimedia Message Service), and Instant Message Service (Instance Message). In addition, there is also a push-to-talk cluster service POC that supports voice and multimedia messages, a conferencing multimedia conference service, and an email service that is frequently used every day. In practical applications, depending on the type of network, it can be divided into various types of messaging services based on mobile networks, various types of messaging services based on the Internet, and various types of messaging services based on fixed access networks. . It can be seen that the message service has become an important service in the current telecommunication network and the Internet, and will be one of the essential key services in the next generation of the next generation network.

 However, with the convergence of mobile networks and fixed networks, the boundaries between IP-based networks and traditional telecommunication networks are becoming less and less obvious. Various types of messaging services begin to interact and interact with each other and present many common features, such as: Both support multimedia, both based on presence information, have a single address book, and share some common functions and capabilities, such as XML Document Management Service. The convergence of these features requires a single converged messaging platform to accommodate different technologies and support different messaging experiences for users.

IP-based converged messaging services, for example, CPM (Converged IP Messaging) is one of the new messaging service frameworks defined by OMA Advocacy, providing users with a converged business experience, such as: instant messaging, offline messaging, multimedia sessions, half-duplex Work/full duplex audio, visual Frequency conferences, etc. The Converged Message CPM service allows users to use communication services with different technical features in a unified manner, and overcomes the "slit" (Silos) between non-CPM message services due to technical differences, thereby providing a unified service experience for user services. The various messaging features that will emerge in the future can be used as general-purpose, reusable business capabilities to support a variety of IP-based applications that require messaging capabilities. In order to enable the maximum possible interoperability between various types of users, such as users supporting various IP-based messaging services in the future, and users supporting existing non-CPM traditional messaging services, CPM needs support based on Interworking between IP messaging services and traditional messaging services. In addition, CPM is able to achieve the same business experience regardless of the IP domain of the user, providing a unified and unified implementation technology for different messaging services, and adopting common charging principles.

 While consolidating the basic capabilities of existing messaging services, CPM services are also merging the many business features that emerged during the evolution of mobile data services, such as:

 1. CPM can manage multiple simultaneous sessions with different media types, allowing users to set services according to different devices, contact addresses, and media types.

 2. The CPM service does not depend on the carrier network and the client, so it can provide services in a multi-terminal environment;

 3. CPM provides the ability of users, such as messages and multimedia content, to store personal networks;

 4. CPM supports seamless interconnection with non-CPM messaging systems, enabling maximum interoperability between different types of message users;

 5. CPM not only supports one-to-one, one-to-many data communication services, but also provides the ability to interact with third-party applications. In the process of implementing business capabilities, CPM interacts with other functional entities in OMA, such as presence server and XML. Document management entity.

 With the introduction and continuous research of the CPM topic, a basic high-level framework has been proposed for the future CPM architecture. The existing CPM high-level network architecture is shown in Figure 1.

 Among them, the CPM client communicates with the CPM Competency Center through the SIP/IP Core.

The CPM Competence Center acts as a business server for processing CPM services in the CPM network. There is an interface directly with the service support component, which is used to use the existing service capability unit provided in various networks, and the interface between the CPM user preference function is used to obtain the settings related to the preference of the CPM user saved in the network. The interface between the information and the third-party application is used by CPM users to use third-party applications. If there is a need for communication with another CPM network, it is routed through the SIP/IP Core network.

 The media and message storage functions are stored in the storage database of the CPM user on the network. The media and messages to be saved can be received from the CPM user. The CPM users can be given open permissions to other CPM users for access or download by other users. The use of the media and message storage capabilities of other CPM users for CPM users is achieved through the CPM Competency Center.

 The Fusion Address Book function, as its name suggests, is an entity that is stored in the network and that combines the address information on each terminal of the CPM user. Its specific usage is similar to that stored on the terminal.

 The interworking function is responsible for accepting messages from the CPM Competence Center, converting them, and converting them into protocol formats supported by other non-CPM messaging services with their interfaces, such as SMS/MMS/IMPS/EMAIL, and sending them to the corresponding message network. The messages received from other non-CPM message networks are converted into CPM messages and sent to the CPM Competency Center.

 The above functional entities, combined with some functional entities that are indirectly related to the CPM network and do not belong to the CPM network, such as service support components, third-party applications, and non-CPM service networks, together constitute a high-level functional framework for CPM service implementation. .

In the CPM system, you need to consider interworking with users in traditional messaging networks, including SMS, MMS, IMPS, and Email. According to the standardization requirements of the CPM service, it is also an inevitable choice for the operator to implement the CPM service process. In the implementation process of the CPM, it cannot affect the traditional network, that is, the traditional message network is not required to be modified and upgraded. Traditional messaging service users can communicate with CPM users. For example, if an IP-based terminal communicates with a terminal based on Signaling No. 7, the traditional messaging network (such as GSM network) does not support IP-based messaging services, and it is impossible to The operator introduced the CPM service and modified and upgraded the old network to communicate with the CPM users. The users in the GSM network may sign up for the SMS service, or may sign the MMS service, or both services. All are signed, then a CPM user as a caller wants to send a message to a user in a traditional message network, and must make a judgment to determine whether the next route is sent to the SMS gateway or the MMS gateway of the called network. If the judgment is wrong, it will lead to waste of network resources and prolonged business processing time.

 At present, according to the media format, message length, user identification and the like of the transmitted message, the CPM server can initially determine whether a message can be transmitted through a certain message system, for example, through an SMS service, an MMS service, or an EMAIL. . But in some cases, such a simple distinction is not enough to make the most accurate positioning:

 1. The called user only signs the SMS service, then some messages that can be transmitted by the MMS message system can only be sent to the SMS gateway;

 2. The called user is currently only CS attached, so the message cannot be received through the MMS message system and can only be received through the SMS message system;

 3. The called user wants all messages to be received by the MMS message system;

 4. The ability of the called terminal is limited, and can only be received by SMS;

 In summary, the inventor believes that in the prior art, when a CPM user sends a message as a caller to a user in a traditional message network, the CPM network cannot accurately determine the gateway in the called network that can route the message. Summary of the invention

 The embodiment of the present invention provides a method, a system, and a device for determining a routing gateway, so that when a converged message service user sends a message to a non-converged message service user as a calling party, the converged message service network can accurately determine that the called network can be routed. The gateway to the message.

The method of the embodiment of the present invention includes: receiving a message sent by a user of a converged message service to a non-converged message service user; and querying message service support capability information of the non-converged message service user; Determining, according to the message service support capability information, a routing gateway in a network where the non-converged message service user is located.

 The fused message service system of the embodiment of the present invention includes: a fused message service client, configured to send a message to the non-converged message service client by using the fused message service capability center; and a fused message service capability center, configured to receive the fused message When the service client sends the message to the non-converged message service client, the address book function entity queries the message service support capability information of the non-converged message service client, and sends an indication to the interworking function entity according to the query result; the address book function entity And the information service support capability information of the non-converged message service user is configured to query the message service support capability information of the non-converged message service client, and the query result is sent to the converged message service capability center; the interworking function entity is used for And determining, according to the indication sent by the Fusion Messaging Service Capability Center, a routing gateway in a network where the non-converged messaging service client is located.

 The address book function entity of the embodiment of the present invention includes: a saving unit, configured to save message service support capability information of a non-converged message service user in which a communication message service user has a contact relationship; a configuration unit, configured to receive the non-converged message service according to the received message The message service support capability information of the user is updated, and the message service support capability information of the corresponding non-converged message service user saved in the save unit is updated.

 The terminal supporting the converged IP message service in the embodiment of the present invention includes: a receiving unit for receiving a message, and further comprising: an address book function unit, configured to save a message of the non-converged message service user that has a relationship with the converged message service user The service supports the capability information, and receives the message service support capability information of the non-converged message service user, and updates the saved message service support capability information of the non-converged message service user that is saved by the configuration information.

In the embodiment of the present invention, the fused IP message fusion message service network, when receiving the message sent by the fused message service user to the non-converged message service user, queries the message service support capability information of the non-converged message service user; The queried message service support capability information determines the routing gateway in the network where the non-converged message service user is located. Since the embodiment of the present invention adds support information about the message service of the called user in the fused message service network, when the fused message service user is used as the calling party to send the message to the non-converged message service user, the fused message service network can be accurate. Determine the gateway in the called network that can route the message. Therefore, it is avoided to judge the inaccuracy of the next route only based on the information such as the message content and the format, and improve the utilization of the network resources. DRAWINGS

 Figure 1 is a schematic diagram of an existing CPM high-level network architecture;

 2 is a flow chart of steps of a method according to an embodiment of the present invention;

 3 is a schematic structural diagram of an address book function entity according to an embodiment of the present invention;

 4 is a schematic structural diagram of a terminal supporting a converged IP message service according to an embodiment of the present invention; FIG. 5 is a schematic structural diagram of a converged message service system according to an embodiment of the present invention;

 Figure 6 is a flowchart of Embodiment 1 of the present invention;

 Figure Ί is a flowchart of Embodiment 2 of the present invention;

 Figure 8 is a flowchart of Embodiment 3 of the present invention;

 Figure 9 is a flowchart of Embodiment 4 of the present invention;

 Figure 10 is a flow chart of Embodiment 5 of the present invention. detailed description

 In order for the CPM user to send a message to the non-CPM user as the calling party, the CPM network can accurately determine the gateway that routes the message in the called network. (The non-CPM user described in the embodiment of the present invention is a user who receives a message by using a non-CPM client, and includes: a user whose client does not support CPM message; and the client supports both CPM and non-CPM messages, but choose not to use CPM. User receiving the message)

An embodiment of the present invention provides a method for determining a routing gateway. Referring to FIG. 2, the method includes the following steps: When receiving the message sent by the CPM user to the non-CPM user, the SI and the CPM network query the message service support capability information of the non-CPM user.

 Before the CPM user sends a message to the non-CPM user, the manner of configuring the non-CPM user's message service support capability information includes but is not limited to the following three types:

 For example, before the CPM user sends the message to the non-CPM user, the CPM user further configures the message service support capability information of the non-CPM user in the address book function entity for query.

 Second, before the CPM user sends the message to the non-CPM user, the method further includes: the non-CPM user sending a message to the CPM user; the interworking function entity in the CPM network identifying the service type of the message, and passing the CPM capability center The service type of the message is configured in the message service support capability information of the non-CPM user in the address book function entity for query. Further, before the service type of the message is configured in the message service support capability information of the non-CPM user in the address book function entity, the identity information of the non-CPM user is verified.

 And before the sending, by the CPM user, the message to the non-CPM user, the service support component sends the message service support capability information of the non-CPM user to the address book function entity; the address book function entity obtains and configures the non-CPM The user's message service supports capability information for query.

 In the third manner of configuring the message service support capability information of the non-CPM user, the service support component sends the message service support capability information of the non-CPM user to the address book function entity, including but not limited to the following three types. Happening:

 Case 1: The address book function entity actively obtains the message service support capability information of the non-CPM user from the service support component.

In the second case, the service support component actively sends the message service support capability information of the non-CPM user to the address book function entity. Further, after receiving the message service support capability information of the non-CPM user delivered by the service support component, the address book function entity may perform the verification operation. In the third case, the address book function entity subscribes the message service support capability information of the non-CPM user to the service support component, and when the message service support capability information of the non-CPM user is updated, the service support component sends the message to the address book function entity. Message service support capability information for non-CPM users.

 The S2 and the CPM network determine the routing gateway in the network where the non-CPM user is located according to the queried message service support capability information.

 Further, the CPM capability center or the interworking function entity in the CPM network is based on the queried message service support capability information, and/or related information of the message, and/or related information of the non-CPM user, and/or operation. The policy information of the quotient determines the gateway that routes the message in the network where the non-CPM user is located.

 In the high-level network architecture of the CPM system, there is currently a network-stored converged address book function entity for storing a comprehensive address book information of a CPM user, for example, when a CPM user has one or more terminal devices, each terminal When the address book saved on the device is not completely the same, the fused address book function entity includes the contact manner, the PRESENCE presentation status, the belonging group, and the corresponding service capability and preference of all the communication objects of the CPM user. Communication mode.

 The embodiment of the present invention further provides an address book function entity, which can provide capability support information when a CPM user sends a message to a non-CPM user. For example, the existing converged address book function entity is extended, or exists in the existing CPM network, or an address book function is added to the CPM terminal (see the terminal supporting the converged IP message service in the embodiment of the present invention, And determine the network of the routing gateway). Referring to FIG. 3, the address book functional entity includes: a storage unit and a configuration unit.

 The saving unit is configured to save, by the CPM user, message service support capability information of a non-CPM user that has a relationship with the CPM user.

The configuration unit is configured to receive external configuration information, and update message service support capability information of the non-CPM user pointed by the configuration information saved in the storage unit. According to the present invention In the description in the example, the external configuration information refers to the message service support capability information of the non-CPM user.

 The embodiment of the present invention further provides a terminal supporting the converged IP message service. Referring to FIG. 4, the method includes: a receiving unit and an address book function unit.

 The receiving unit is configured to receive a message.

 The address book function unit is configured to save, according to a CPM user unit, message service support capability information of a non-CPM user that has a relationship with the CPM user, and receive external configuration information, and update the saved configuration information to Message service support capability information for non-CPM users. According to the description in the embodiment of the present invention, the external configuration information refers to the message service support capability information of the non-CPM user.

 The embodiment of the present invention further provides a converged message service system. As shown in FIG. 5, the method includes: a CPM client, a CPM capability center, an address book function entity, and an interworking function entity; and further includes a service support component.

 CPM client, used to send messages to non-CPM clients.

 The CPM Competency Center is configured to send a query message when receiving a message sent by the CPM client to the non-CPM client, and issue an indication according to the returned query result.

 The address book function entity is configured to receive the query message sent by the CPM capability center, query the locally configured message service support capability information of the non-CPM client, and return the query result to the CPM capability center. The address book functional entity is located in the CPM client or is independent of the CPM client and is located in the CPM network.

 An interworking function entity, configured to determine, according to an indication sent by the CPM capability center, a routing gateway in the network where the non-CPM client is located.

 Configure the message service support capability information of the non-CPM client saved locally by the address book function entity, including but not limited to the following three methods:

The CPM user configures the message service support capability information of the non-CPM client in the address book function entity through an interface between the CPM client and the address book function entity. Second, the interworking function entity receives the message sent by the non-CPM client, and then configures the service type of the message in the message service support capability information of the non-CPM client in the address book function entity through the CPM capability center.

 And the service support component sends the message service support capability information of the non-CPM user to the address book function entity; the address book function entity obtains and configures the message service support capability information of the non-CPM user.

 The following is specifically described by the five embodiments.

 Embodiment 1. A fused address book is configured by a user. When the CPM user acts as the calling party and sends a communication setup request message to non-CPM users in other non-CPM message networks (traditional message networks), as shown in Figure 6, the following steps are included:

 Step 0, step 0 and subsequent steps are independent of each other, and can be executed before step 2 of the embodiment. The CPM user configures the message service support capability information of the contact of the CPM user (including the non-CPM user) in the address book function entity through the interface between the CPM client and the converged address book function entity.

 Step 1. The CPM user (calling user) wants to send a message to a contact, which is a non-CPM user (called user), and therefore sends a communication establishment request to the CPM Competence Center, where the carrying can identify the non-CPM user. Information.

 Step 2: The CPM capability center uses the called user identification information in the received communication request to query the address book function entity for the message service support capability information of the called user.

 Step 3: The address book function entity searches for local data, and returns the obtained message service support capability information about the called user to the CPM capability center.

 Step 4: The CPM capability center performs processing related to the service control, for example, according to the obtained message service support capability information about the called user, determining that the communication request needs to be forwarded to the interworking function entity for processing.

Step 5: The CPM capability center adds information about the support capability of the called user to the message service in the communication request message, to indicate the gateway in the called network that can complete the next route, and then The communication request is sent to the interworking function entity.

 Step 6: The interworking function entity determines, according to the obtained message service support capability indication about the called user, which non-CPM message service is used for message conversion, and sends the message to the corresponding message gateway; where the processing involves the called network. That is, various non-CPM message service networks, the processing after the gateway device receives the converted communication request is the same as the processing in the existing network, and therefore the description is not added.

 Step 7 ~ 9, the response message returned by the called user.

 The CPM service is divided into a session-related message and a session-independent message. The former needs to establish a session through the session establishment request, and then performs message delivery in the session. The latter is a separately sent message, and does not require a session to be established. The process, the same reason, there is no process of releasing the conversation. In the following description, the two message types are no longer distinguished, collectively referred to as a communication request message, and the specific implementation is applicable to both message types.

 Based on the IMS network, the related message for transmitting the message service support capability information of the called user in this embodiment may be implemented by extending the SIP message header field, such as adding a feature tag to indicate the message service supported by the user. Type, specific values include but are not limited to: one or more of SMS, MMS, IMPS and EMAIL. The specific value may also be increased according to the increase of the non-CPM message service. For example, the POC service and the IM service are added as non-CPM message services, and the value herein may be expanded accordingly, so that the device has a certain scalability. Sex.

 Correspondingly, the gateway for routing the message in the network where the non-CPM user is located in the embodiment of the present invention includes, but is not limited to, a gateway of an SMS network, a gateway of an MMS network, a gateway of an IMPS network, and a gateway of an EMAIL network; It also has some scalability.

 Embodiment 2: The CPM Competence Center configures the converged address book to complete the message routing of the CPM user to send messages to non-CPM users.

The CPM Competency Center configures the process of merging the address book part. As shown in Figure 7, the following steps are included: Step 1. The user (calling user) of the non-CPM network sends a communication request to the CPM user (called user), and the message is first sent to the interworking function entity in the CPM network. The request may be a session-independent message or a session-related session establishment request.

 Step 2. The interworking function entity converts the received communication request from a non-CPM message format to a message protocol format supported by the CPM, wherein information about the message service type used by the calling user is added to send the message. Then send it to the CPM Competency Center.

 Step 3: The CPM Competency Center performs the operation of number verification and the like in the address book function entity according to the caller ID information in the received communication request, and what message is used by the relevant calling user in the received communication request. The service type sends the message to the address book function entity.

 Step 4: The address book function entity performs related processing according to the received request, where the information about the received message type is used to send the message to the calling user, and if all relevant checks and verifications are passed, This information is saved under the corresponding user number.

 Step 5. The address book function entity returns the verification result to the CPM capability center after the processing is completed.

 Step 6. The CPM Competency Center continues the subsequent transmission of the message, but can no longer carry information about the message service type used by the calling user to send the message to the CPM user as the called party.

 Then, the CPM user can send a message to the non-CPM user as a calling user. This part of the process is similar to steps 2-9 of Embodiment 1.

 Based on the IMS network, the related message for transmitting the message service support capability information of the called user in this embodiment may be implemented by extending the SIP message header field, such as adding a feature tag to indicate the message service supported by the user. Type, the specific value can be one or more of SMS, MMS, IMPS and EMAIL.

 For the embodiment 2, the processing in the specific case includes the following.

When CPM User A is called, the interworking function entity in the CPM network will receive Communication requests from non-CPM User Bs of other networks, including communication requests from non-CPM networks, where the non-CPM network includes networks for messaging services via SMS, MMS, IMPS, and EMAIL. When the interworking function entity receives the communication request, it is a gateway device that can know which network the communication request comes from and which message service, such as from the SMS-GMSC or from the MMS SERVER. Therefore, the interworking function entity can determine that the user B that sends the communication request supports the message service according to the message type of the communication request, and the information is carried in the converted CPM message and sent to the CPM capability center. After receiving the message, the CPM Capability Center interacts with the address book function entity to perform the user B identity check operation. In the message sent to the address book function entity, the CPM capability center also carries the relevant information received from the interworking function entity. The indication information of the message service supported by the user B that initiated the request is configured by the address book function entity. The address book function entity first searches the database for the existence of the user B that initiated the request. If it does not exist, the related check cannot be performed. The address book function entity returns the corresponding message to reply to the CPM Competence Center "The information of User B is not saved", CPM capability. The center performs corresponding processing according to the response message; if yes, it checks whether the information about the message service it supports is saved under the user B address information, and if not, saves the received indication information in the corresponding location, if any If the received indication information is the same, no processing is performed. If there is and is different from the received indication information, the address book function entity returns a corresponding message to reply to the CPM Competency Center "Saved User B Information and Received Different", and then The address book function entity may send a notification to the user A notifying that the relevant information of the user B in the address book has been updated, and the user A decides whether to accept the update and synchronize on the terminal. (Note: The message interaction process described above for the address book function entity and the CPM Competency Center may also be just the transfer of data, no response message carrying detailed processing results, or just a confirmation message.) CPM Competency Center and Address After the interaction of the book function entity, the received message is forwarded to the CPM user A as the called party, and the indication information about the message service supported by the calling user may no longer be carried.

For the above CPM user as the called process, the CPM Competency Center only receives the communication. The message is sent to the address book function entity when requested, which prevents the messages between the CPM Competency Center and the Address Book function entity from being exchanged too frequently.

 After that, when CPM user A wants to communicate with user B who is not CPM, user A only needs to send a CPM message to the CPM capability center. After receiving the request, the CPM capability center searches the address book function entity for the corresponding called party. User B's related information, including what kind of message service B is supported by user B, such as CPM or non-CPM. If it is non-CPM, it is SMS, MMS, IMP S or EMAIL. The address book functional entity returns this information it has saved to the CPM Competency Center. Based on the returned result, the CPM Competence Center judges that the called user B does not support CPM, but can support both SMS and MMS. Therefore, the next step is to send a message to the interworking function entity, which carries the called user B and supports both SMS and MMS. After receiving the message, the interworking function entity can further determine the media type, size and format of the received CPM message according to the indication information, and further determine the combination with the operator's configuration and policy. The received CPM message is converted into a message in the SMS or MMS format and sent to the gateway of the corresponding message service.

 For a functional entity that does not directly interface with the address book function entity, such as an interworking function entity, the information configuration of the address book functional entity can be implemented by the method of Embodiment 2. For a functional entity that has a direct interface with the address book functional entity, the address book functional entity can be directly configured through the interface. Similar functional entities include: rendering server, location server, XDMS, Shared XDMS, etc., these functional entities and addresses The interface of the book function entity is the interface between the service support component and the address book function entity in FIG. 1, and the above-mentioned presence server, location server, XDMS, Shared XDMS, etc. can be regarded as a service support component. It can therefore be applied between all supported components and address book functional entities.

 Embodiment 3: The address book function entity uses the pull method to actively request information from the service support component, and configures the process of the address book part. As shown in FIG. 8, the following steps are included:

Step 1. The address book function entity sends a request message to the corresponding service support component in order to obtain the required information from a certain service support component. Step 2. The service support component sends the requested information to the address book function entity.

 Step 3: The address book function entity configures the obtained information into the message service support capability information of the non-CPM user for query.

 Embodiment 4: Using the subscribe/notify subscription/notification mechanism, the service support component automatically notifies the address book function entity of the latest information, and configures the flow of the address book part. As shown in FIG. 9, the following steps are included:

 Step 1. The address book function entity sends a subscription request to the service support component, and subscribes to a certain non-

Message service support capability information of CPM users.

 Step 2. The service support component accepts the subscription request and returns a success response message.

 Step 3. The service support component sends the latest subscription information to the address book function entity using a NOTIFY message.

 Step 4: The address book function entity configures the obtained information into the message service support capability information of the non-CPM user for query.

 Step 5. Subsequently, if the information subscribed to in the service support component is changed, the NOTIFY message is actively used to notify the address book function entity.

 Step 6. The address book function entity updates the configuration information.

 Embodiment 5: The service support component uses the pull mode to actively send information to the address book function entity, and configures the process of the address book part. As shown in FIG. 10, the following steps are included: Step 1. The service support component actively forwards to the address book. The functional entity issues relevant information.

 Step 2: The address book function entity configures the obtained information into the information service capability information of the corresponding non-CPM user for query. Further, in this step, the authentication process of the service support component by the address book function entity may be involved, and only the information through the security check and the identity/content authentication may be configured into the address book function.

Step 3. The address book function entity returns an acknowledgement message to the service support component. (Optional) In some cases, when the CPM user is the calling party, the message service support capability information about the called user (non-CPM user) may not be found from the address book function entity. In this case, the interworking function entity finally determines a non-CPM message service to interact with the called user through some methods. The information can also be sent as information about the support capability of the called non-CPM user to the message service. Configure to the address book functional entity. Specifically, the information may be carried in the message returned to the CPM capability center by the interworking function, for example, the interworking function entity carries the message about the called party in the message returned to the CPM capability center when receiving the first final response. The type of service support is then sent by the CPM Competence Center to the address book function entity for configuration. This method works for both session-independent single messages and session-related session messages.

 The address book function entity considers that the user has multiple terminal devices, and the address information requirements of other users that different terminal devices want to save are different, and the function of storing a complete address information in the network is introduced, if the function is not used. Then, all the address information is still placed on the user terminal as before, and the foregoing description of what kind of message service other users support is always transmitted to the user terminal, and a CPM user is initiating the message service. When requesting, you will also refer to the other party's message service support in your address book. Therefore, the embodiment of the present invention is also applicable to the case where the address book information is stored on the terminal. In this case, all the information sent to the CPM client and sent to the address book function entity is the same piece of information.

 In summary, in the embodiment of the present invention, the fused IP message CPM network queries the message service support capability information of the non-CPM user when receiving the message sent by the CPM user to the non-CPM user; the CPM network according to the queried message service Support capability information to determine the routing gateway in the network where the non-CPM user is located.

Since the embodiment of the present invention adds support information about the message service of the called user in the CPM network, when the CPM user can send the message to the non-CPM user as the calling party, the CPM network can accurately determine that the called network can be routed. The gateway to the message. Therefore, the inaccuracy of the next route is judged based on the information such as the message content and the format, the utilization of the network resources is improved, and the number of communication failures caused by the inconsistent terminal capabilities of both parties is improved, and the connection is improved. Efficiency.

 Those skilled in the art can also know that when the message calling user's network exists similarly

When an entity such as a CPM Competency Center and an Address Book Functional Entity, even if the calling subscriber is not a CPM User but other types of messaging users, the calling subscriber can still determine the routing gateway in a manner similar to that of the embodiment of the present invention.

 Through the description of the above embodiments, those skilled in the art can clearly understand that the present invention can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is a better implementation. the way. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium, including a plurality of instructions for causing the network device The methods described in various embodiments of the invention are performed. The spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and modifications of the invention

Claims

Rights request  A method for determining a routing gateway, comprising the steps of: receiving a message sent by a converged message service user to a non-converged message service user;  Querying message service support capability information of the non-converged message service user;  And determining, according to the message service support capability information, a routing gateway in a network where the non-converged message service user is located.  The method for determining a routing gateway according to claim 1, wherein the receiving the message of the converged message service to the non-converged message service user further includes:  The message service support capability information of the non-converged message service user is configured in the address book function entity.  The method for determining a routing gateway according to claim 2, wherein the information of the message service support capability of the non-converged messaging service user in the address book function entity is:  Configuring the message service support capability information of the non-converged message service user in the address book function entity by the fused message service user; or  Receiving a message sent by a non-converged message service user; identifying a service type of the message sent by the non-converged message service user; configuring a service type of the message as a message of the non-converged message service user in the address book function entity Business support capability information; or,  Sending the message service support capability information of the non-converged message service user to the address book function entity; configuring the message service support capability information as the message service support capability information of the non-converged message service user.  The method for determining a routing gateway according to claim 3, wherein before the service type of the message is configured as the message service support capability information of the non-converged message service user in the address book function entity, the method further includes: Verifying the non-converged messaging service user. The method for determining a routing gateway according to claim 3, wherein the message service support capability information of the non-converged message service user is sent to the address book function entity Specifically:  Receiving, by the address book function entity, a request for acquiring the message service support capability information of the non-converged message service user; sending the message service support capability information of the non-converged message service user to the address book function entity; or  Actively sending the message service support capability information of the non-converged message service user to the address book function entity; or  Receiving, by the address book function entity, a request for subscribing to the message service support capability information of the non-converged message service user; and when the message service support capability information of the non-converged message service user is updated, to the address book function The entity delivers the message service support capability information of the non-converged message service user.  The method for determining a routing gateway according to claim 1, wherein, according to the message service support capability information, determining that the routing gateway in the network where the non-converged message service user is located is: The capability information is sent to the interworking function entity, and the message service support capability information is determined.  The method for determining a routing gateway according to claim 6, wherein the message service support capability information is carried in a SIP message header field and sent to the interworking function entity.  The method for determining a routing gateway according to claim 1 or 6, wherein the routing gateway in the network where the non-converged messaging service user is located is further sent to the non-converged messaging service user according to the convergence message service user. Any one of the related information of the message, the related information of the non-converged messaging service user, and the operator's policy information, or any combination thereof.  9. A converged messaging service system, characterized by comprising:  a converged message service client, configured to send a message to the non-converged message service client by using the converged message service capability center; The merging message service capability center is configured to query the address book function entity for the message service support capability information of the non-converged message service client, and receive the message sent by the fused message service client to the non-converged message service client, and Issued to the interworking function entity based on the query result Instruction  The address book function entity is configured to configure the message service support capability information of the non-converged message service user, query the message service support capability information of the non-converged message service client, and send the query result to the convergence message service capability center;  The interworking function entity is configured to determine, according to the indication sent by the converged message service capability center, a routing gateway in a network where the non-converged messaging service client is located.  The fused message service system according to claim 9, wherein the fused message service user and/or the interworking function entity are further configured to configure a message of the non-converged message service client in the address book function entity. Business support capability information.  The fused message service system according to claim 9, wherein the network further comprises: a service support component, configured to send, to the address book function entity, message service support capability information of the non-converged message service user .  The fused message service system according to claim 9, wherein the address book function entity is located in the fused message service client or in the fused message service network.  13. An address book functional entity, comprising:  a saving unit, configured to save message service support capability information of the non-converged messaging service user in which the communication message service user has a contact relationship;  And a configuration unit, configured to update, according to the received message service support capability information of the non-converged message service user, message service support capability information of the corresponding non-converged message service user saved in the save unit.  A terminal for supporting a converged IP message service, comprising: a receiving unit, configured to receive a message, further comprising:  An address book function unit, configured to save message service support capability information of a non-converged message service user that has a relationship with a converged message service user, and receive message service support capability information of the non-converged message service user, and update the saved configuration information The message service support capability information of the non-converged message service user pointed to.