CN101291297A - Network, capability center entity, interworking function entity and message notification method - Google Patents

Abstract

The invention discloses a network, a capability center entity, an interworking function entity and a message notification method. The network includes a capability center entity, including a sending judging unit, a first entity, and a message notification entity. The sending judging unit is used to judge whether to use a non-SIP protocol-based message to send a notification message to the user; the first entity includes a message construction unit, and the message construction unit is used to determine whether the capability center entity needs to use a non-SIP-based notification message. When the SIP protocol message sends a notification message to the user, the notification message is constructed in a non-SIP protocol-based message manner; the message notification entity is configured to send the notification message constructed by the message construction unit to the user. The invention can avoid the technical problem that the prior art cannot notify the unregistered CPM users, and enables the users to obtain various messages and react and operate in time by performing protocol conversion on the messages whose sources are based on the SIP protocol.

Description

Network, capability center entity, interworking function entity and message notification method

technical field

The present invention relates to the communication field, in particular to the network and its functional entities.

Background technique

IP-based Converged Messaging (CPM, Converged IP Messaging) is a new messaging service framework advocated and defined by the Open Mobile Alliance (OMA, (Open Mobile Alliance)), providing users with a converged service experience. Converged message CPM service allows users to use communication services with different technical characteristics in a unified way, overcomes the "silos" between non-CPM message services caused by technical differences, and provides unified service experience for user services. CPM needs to support the intercommunication between IP-based message service and traditional message service, so as to realize the maximum possible intercommunication between various users. In addition, CPM also needs to achieve the same service experience regardless of which IP network service domain the user is in, provide integrated and unified implementation technologies for different message services, and adopt common charging principles.

Fig. 1 is a schematic diagram of a prior art CPM high-level network framework. The CPM high-level network framework mainly includes a CPM capability center entity, an interworking functional entity, a CPM user preference information entity, a media and message storage functional entity, and an integrated address book functional entity. in:

The CPM capability center entity is a service server that processes CPM services in the CPM network. There is a direct interface between the CPM capability center entity and the supporting components, which is used to use the existing service capability units provided in various networks; an interface is included with the CPM user preference information entity, which is used to obtain the information stored by the CPM user. Setting information about preferences in the network; an interface with third-party applications is included for CPM users to use third-party applications. In addition, the CPM capability center entity and the remote CPM network are routed through a SIP/IP Core (Session Initiation Protocol and/or Internet Protocol Core, core network based on Session Initiation Protocol and/or Internet Protocol) network. Similarly, the CPM capability center entity and the CPM client communicate through SIP/IP Core.

The interworking functional entity is responsible for accepting messages from the CPM capability center entity, and converting them into protocol formats supported by other non-CPM message services, such as Short Message Service (SMS, Short Message Service)/Multimedia Message Service (MMS , Multimedia Message Service)/Instant Messaging (IMPS, Instant Messaging and Presence Services)/Email (EMAIL), etc., are sent to the corresponding message network; and messages received from other non-CPM message networks are converted into The CPM message is sent to the CPM capability center entity.

The media and message storage functional entity is a storage database placed by the CPM user in the network, which can receive media and messages to be saved from the CPM user, and can also open permissions to other CPM users according to the instructions of the CPM user for other CPM users to use. User access or download. The use of the media and message storage functional entity of the CPM user by other CPM users is realized through the CPM capability center entity.

The integrated address book functional entity is an entity stored in the network that integrates the address information of each terminal of the CPM user, and its specific usage is similar to the address book stored on the terminal.

In the application, the CPM user can set the message transmission mechanism according to his preference, which is used when the CPM user is unreachable, for example, the CPM user is not registered in the home network. Each functional entity of the CPM network processes the received message based on the SIP protocol according to this setting. This messaging mechanism can be: 1) discarding the received message based on the SIP protocol; 2) temporarily saving the received message based on the SIP protocol and sending it later, such as when the user becomes reachable again; The received SIP protocol-based message is stored in the user's network storage function, and the user is notified to read the stored SIP protocol-based message, for example, when the user becomes reachable again.

During the creation process of the present invention, the inventor found at least the following problems in the above-mentioned prior art CPM network: the CPM network cannot implement the function of notifying unregistered users. The inventor analyzes and draws the following reasons:

As mentioned above, when a CPM user is not registered in the home CPM network, it is unreachable to see the user's status in the CPM network. Therefore, if there is a CPM message sent to the user at this moment, the CPM network needs to send the The message is stored in a temporary storage entity or a network storage entity, and the user may be notified to obtain the stored information at a specified location. According to the existing CPM high-level architecture, the CPM network can only notify the CPM user by sending a CPM notification message, but because the CPM user has not registered to the CPM service, this notification message cannot be received by the user, therefore, now There is a CPM network architecture that cannot realize the function of notifying unregistered users.

Contents of the invention

The technical problem to be solved by the embodiments of the present invention is to provide a network capable of sending notification messages to unreachable users.

The technical problem to be solved by the embodiments of the present invention is to provide a capability center entity, an interworking function entity and a message notification entity that support sending notification messages to unreachable users.

In order to solve the above technical problems, the purpose of the embodiments of the present invention is achieved by the following first technical solution:

A network is provided, including a capability center entity, including a sending judging unit, a first entity, and a message notification entity. The sending judging unit is used to judge whether to use a non-SIP protocol-based message to send a notification message to the user; the first entity includes a message construction unit, and the message construction unit is used to determine whether the capability center entity needs to use a non-SIP-based notification message. When the SIP protocol message sends a notification message to the user, the notification message is constructed in a non-SIP protocol-based message manner; the message notification entity is configured to send the notification message constructed by the message construction unit to the user.

In order to solve the above technical problems, the purpose of the embodiments of the present invention is achieved by the following second technical solution:

A capability center entity is provided, including a sending judgment unit and a message construction unit. The sending judging unit is used to judge whether to use a non-SIP protocol-based message to send a notification message to the user; the message construction unit is used to determine whether the capability center entity needs to use a non-SIP protocol-based message to send a notification message to the user Constructing the notification message in a message manner not based on the SIP protocol.

In order to solve the above technical problems, the purpose of the embodiments of the present invention is achieved by the following third technical solution:

A capability center entity is provided, including a sending judging unit and a request sending unit. The sending judging unit is used to judge whether to use a message not based on the SIP protocol to send a notification message to the user; the request sending unit is used to send a carrying The SIP protocol-based request message of the user's identification and notification content is sent to the first entity including the message construction function.

In order to solve the above-mentioned technical problems, the purpose of the embodiments of the present invention is achieved by the following fourth technical solution:

An interworking functional entity is provided, including a request receiving unit, a message constructing unit and a message sending unit. The request receiving unit is used to receive the request message carrying the user identification and notification content from the capability center entity; the message construction unit is used to construct the notification message carrying the user identification and notification content in a non-SIP protocol-based message mode ; The message sending unit is configured to send the notification message to the user through a message notification entity.

In order to solve the above technical problems, the purpose of the embodiments of the present invention is achieved by the following fifth technical solution:

A message notification method is provided, comprising: judging whether to use a non-session-initiated SIP protocol-based message mode to send a notification message to a user; Constructing the notification message in a message manner; sending the constructed notification message to the user.

As can be seen from the first technical solution above, this solution modifies and enhances the existing network. When receiving the request message from the request receiving unit, if it is determined that a non-SIP protocol-based message needs to be used to send a notification message to the user, Then the message construction unit generates a notification message not based on the SIP protocol that the unreachable user can receive, and then sends the notification message to the user through the message notification entity. That is to avoid the technical problem of not being able to notify unregistered CPM users due to the direct adoption of messages based on the SIP protocol in the prior art, by performing protocol conversion on messages based on the SIP protocol, unregistered CPM users can receive the content of the message Or get a related notification, so that the CPM network architecture can solve the problem of how to send a notification message to unreachable users, and the user can get the source of the message based on the SIP protocol as soon as possible, so that they can respond and operate in time.

It can be seen from the second technical solution above that this solution modifies and enhances the existing network architecture, adopts the method of adding a sending judgment unit and a message construction unit in the capability center entity, and uses a non-SIP-based protocol in the capability center entity The notification message is constructed in the message mode and sent to unregistered users through the message notification unit. That is to say, the implementation mode of the capability center entity of the present invention can cooperate with the message notification entity, and by converting the source of the message based on the SIP protocol, the unregistered CPM user can receive the converted message, so that the network can solve how to send the message to the unreachable For the problem of the user sending a notification message, the user can get the source of the message based on the SIP protocol as soon as possible, so that the user can respond and operate in time.

It can be seen from the third technical solution above that this solution modifies and enhances the existing network, and adopts the method of adding a sending judgment unit in the capability center entity, and the sending judgment unit judges that it is necessary to use a non-SIP protocol-based message sending notification When the message is sent to the user, a request message is generated, so that the first entity generates a non-SIP-based notification message that the unreachable user can receive. That is to avoid the technical problem of not being able to notify unregistered CPM users due to the direct use of messages based on the SIP protocol in the prior art, by converting the source of messages based on the SIP protocol, the unregistered CPM users can receive the converted Messages enable the CPM network architecture to solve the problem of how to send notification messages to unreachable users, and users can get messages based on the SIP protocol as soon as possible, so that they can respond and operate in a timely manner.

As can be seen from the above fourth technical solution, this solution modifies and enhances the existing network, and when receiving the request message of the request receiving unit, the message construction unit generates a non-SIP protocol-based, unreachable user The notification message can be received, and then the notification message is sent to the user through the message notification entity. That is to avoid the technical problem of not being able to notify unregistered CPM users due to the direct use of messages based on the SIP protocol in the prior art, by converting the source of messages based on the SIP protocol, the unregistered CPM users can receive the converted Messages enable the CPM network architecture to solve the problem of how to send notification messages to unreachable users, and users can get messages based on the SIP protocol as soon as possible, so that they can respond and operate in a timely manner.

As can be seen from the fifth technical solution above, this solution modifies and enhances the existing network. When receiving the request message from the request receiving unit, if it is determined that a non-SIP protocol-based message needs to be used to send a notification message to the user, Then a notification message not based on the SIP protocol is generated and sent to the user for the unreachable user to receive. That is to avoid the technical problem of not being able to notify unregistered CPM users due to the direct adoption of messages based on the SIP protocol in the prior art, by performing protocol conversion on messages based on the SIP protocol, unregistered CPM users can receive the content of the message Or get a related notification, so that the CPM network architecture can solve the problem of how to send a notification message to unreachable users, and the user can get the source of the message based on the SIP protocol as soon as possible, so that they can respond and operate in time.

Description of drawings

FIG. 1 is a high-level architecture diagram of a prior art CPM network;

Fig. 2 is a functional block diagram of the first embodiment of the network of the present invention;

Fig. 3 is a functional block diagram of the second embodiment of the network of the present invention;

Fig. 4 is a functional block diagram of the third embodiment of the network of the present invention;

FIG. 5 is a functional block diagram of a fourth embodiment of the network of the present invention;

Fig. 6 is a functional block diagram of the fifth embodiment of the network of the present invention;

Fig. 7 is a functional block diagram of the first embodiment of the capability center entity of the present invention;

Fig. 8 is a functional block diagram of the second embodiment of the capability center entity of the present invention;

Fig. 9 is a functional block diagram of the first embodiment of the interworking functional entity of the present invention;

Fig. 10 is a functional block diagram of the first embodiment of the message notification method of the present invention.

Detailed ways

Referring to Figure 2, the present invention provides a first implementation of the network, including a capability center entity, including:

A sending judging unit, configured to judge whether to use a non-SIP protocol-based message to send a notification message to the user,

The first entity includes a message construction unit, the message construction unit is used to construct the notification in a non-SIP protocol-based message mode when the capability center entity judges that a non-SIP protocol-based message needs to be used to send a notification message to the user information,

A message notification entity, configured to send the notification message constructed by the message construction unit to the user.

As can be seen from the above, by modifying and enhancing the existing network in this embodiment, when receiving the request message from the request receiving unit, if it is determined that a non-SIP protocol-based message needs to be used to send a notification message to the user, then by The message construction unit generates a notification message not based on the SIP protocol that the unreachable user can receive, and then sends the notification message to the user through the message notification entity. That is to avoid the technical problem of not being able to notify unregistered CPM users due to the direct adoption of messages based on the SIP protocol in the prior art, by performing protocol conversion on messages based on the SIP protocol, unregistered CPM users can receive the content of the message Or get a related notification, so that the CPM network architecture can solve the problem of how to send a notification message to unreachable users, and the user can get the source of the message based on the SIP protocol as soon as possible, so that they can respond and operate in time.

In order to make the purpose, technical solution, and advantages of the present invention clearer, the present invention will be further described in detail below with reference to the accompanying drawings and embodiments.

Referring to FIG. 3 , it is a schematic structural diagram of a second embodiment of the network of the present invention. In this implementation manner or other implementation manners, the network may be a network that bears an IP-based converged message service, and a SIP-based message refers to an IP-based converged message. The network includes a CPM capability center entity, an interworking functional entity, a CPM user preference information entity, a media and message storage functional entity, a converged address book functional entity, and a message notification entity.

The media and message storage functional entity is a storage database placed by the CPM user in the network, which can receive media and messages to be saved from the CPM user, and can also open permissions to other CPM users according to the instructions of the CPM user for other CPM users to use. User access or download. The use of the media and message storage functional entity of the CPM user by other CPM users is realized through the CPM capability center entity.

The integrated address book functional entity is an entity stored in the network that integrates the address information of each terminal of the CPM user, and its specific usage is similar to the address book stored on the terminal.

There is a direct interface between the CPM capability center entity and the supporting components, which is used to use the existing service capability units provided in various networks; an interface is included with the CPM user preference information entity, which is used to obtain the information stored by the CPM user. Settings information about preferences in the network; an interface with third-party applications is included to facilitate CPM users to use third-party applications. In addition, the CPM capability center entity and other CPM networks are routed through the SIP/IP Core network. Similarly, the CPM capability center entity and the CPM client communicate through SIP/IP Core. The CPM capability center entity also includes a sending judging unit and a request sending unit. The sending judging unit is used to judge whether to use a non-SIP protocol-based message to send a notification message to the user; the request sending unit is used to send a notification message carrying the Send a request message of the identity of the CPM user and notification content to the interworking functional entity.

The SIP protocol mentioned in this embodiment refers to the enhanced SIP protocol for the CPM service, and in other embodiments, it can also be the enhanced SIP protocol for other services, such as the push-to-talk service based on the cellular network ( POC, Push to talk Over cellular) and Multimedia Conferencing. As mentioned in this embodiment, it is judged that it is necessary to use a non-SIP protocol-based message to send a notification message to the user may refer to: it is judged that it is necessary to use any possible non-CPM service-based enhanced SIP protocol message.

In other implementation manners, the SIP protocol may be an enhanced SIP protocol for PoC services. At this time, it is determined that it is necessary to use a non-SIP protocol-based message to send a notification message to the user: it is determined that any possible non-SIP-based The PoC business carries out enhanced SIP protocol messages. The same goes for other businesses.

That is to say; the SIP protocol in the "non-SIP protocol-based message" mentioned elsewhere in this article can be determined according to the applied network.

The interworking functional entity is responsible for receiving messages from the CPM capability center entity and converting them into protocol formats supported by the non-SIP protocol-based message services, such as short message service/multimedia message service/instant messaging message/ Emails, etc., are sent to the corresponding message network; and messages received from other non-SIP protocol-based message networks are converted into SIP-based messages, and sent to the CPM capability center entity. A communication interface is included between the interworking function entity and the message notification entity. The interworking function entity also includes a message construction unit and an interface with the message notification entity. The message construction unit is configured to receive the message carrying the identity of the CPM user and notification content when the sending judgment unit of the capability center entity judges that a non-SIP protocol-based message needs to be used to send a notification message to the CPM user. request message, and construct the notification message in a non-SIP-based message manner according to the CPM user's identity and notification content.

The message notification entity is configured to send the notification message constructed by the message construction unit to the user. Described message notification entity can be exactly the same as the short message center in the existing GSM/GPRS/PSTN network, even can be exactly the short message center in the existing GSM/GPRS/PSTN network; This message notification entity can also be other Non-CPM message processing entities, such as the MMS server of MMS, the IMPS server of IMPS, or the mail server in EMAIL service, etc., may depend on which non-SIP-based service the operator decides to use to send notifications. As mentioned above, the message not based on the SIP protocol is determined corresponding to a specific message notification entity. For example, if the message notification entity is a mail server, the message not based on the SIP protocol is simply SMTP (Simple Mail Transfer Protocol). Mail Transfer Protocol message.

The message notification entity can be used as a component of the network alone, or as a service component of various service support components that have an interface with the network. In this embodiment, the message notification entity appears as a service support component, and a communication interface is included between the interworking function entity and the service support component.

In the application, CPM users can set the message transmission mechanism according to their own preferences, so as to facilitate the processing of messages when the messages are unreachable. For example, the CPM user is not registered in the home network, and each functional entity of the CPM network processes the received CPM message according to the setting. This messaging mechanism can be: 1) discarding received CPM messages; 2) temporarily storing received CPM messages for later delivery, such as when the user becomes reachable again; 3) storing functions in the media and messaging network The entity saves the received CPM messages and notifies the user to read the saved CPM messages, for example when the user becomes reachable again.

In the case of mechanisms 2) and 3), when each CPM capability center entity receives a message to be sent to a certain CPM user, the sending judging unit of the CPM capability center entity determines that it is necessary to use non-SIP protocol-based message transmission A notification message is sent to the unreachable CPM user, and the request sending unit sends a request message to the interworking function, which carries the CPM user identification to be notified, the content to be notified (such as information storage address, etc.), relevant information, etc., indicating the interworking The functional entity initiates the notification procedure. The message construction unit in the interworking function entity constructs the notification message in a non-SIP protocol-based message manner according to the CPM user's identification and notification content, and sends the notification message through the communication interface with the message notification entity To the message notification entity, and then sent to the CPM user through the message notification entity, so that he can go to the designated location to extract the saved information. Or, the message sent to the CPM user itself includes the content of the message received by the CPM capability center entity at the beginning and to be sent to the CPM user.

The specific protocol format of the notification message is related to the type of message service supported by the message notification entity. For example, if the message notification entity is a short message center, the constructed notification message may be of the short message type. The specific content of the notification message has nothing to do with the protocol format of the message.

In the above network, the interworking functional entity decides what measures to take according to the message received from the CPM capability center entity: if it is a normal communication request message, it will convert the message according to the identity of the called user and send it to the corresponding Non-SIP protocol-based service processing entities in other networks; if a notification message is to be sent, a notification message is constructed according to the identity of the receiving user who wants to send the notification—that is, the format of the message is converted and sent to the specified message notification entity.

As can be seen from the above, this embodiment modifies and enhances the existing CPM network architecture, and adopts the method of adding a sending judgment unit and a request sending unit in the CPM capability center entity, and the CPM capability center entity needs to adopt a non-SIP-based When the message of the protocol sends a notification message to the user, generate a request message to the interworking functional entity; adopt the method of adding a message construction unit in the interworking functional entity, and use a non-SIP protocol-based message to construct the unreachable according to the received request message The user can receive the notification message, and then send the notification message to the user through the message notification entity. That is to avoid the technical problem of not being able to notify unregistered CPM users due to the direct adoption of messages based on the SIP protocol in the prior art, by converting the source to messages based on the SIP protocol, unregistered CPM users can receive the converted The news enables the CPM network architecture to solve the problem of how to send notification messages to unreachable users, and the users can get the messages based on the SIP protocol as soon as possible, so that they can respond and operate in time.

While achieving the above-mentioned technical effect, this implementation mode does not greatly modify the CPM capability center entity. For example, because the interworking functional entity needs to intercommunicate with existing non-SIP-based services, it has already supported functions such as short messages and other non-SIP-based services, message processing, etc. In the CPM capability center entity and the interworking functional entity The interfaces provided for transmitting request messages do not bring any new burden to the interworking functional entities. This architecture will not affect the independent evolution and development of each function of the CPM network architecture, so the cost of network upgrade and redesign is not large.

Finally, this embodiment also makes the operator pay a very small price, thereby protecting the investment of the operator.

Referring to FIG. 4 , the third embodiment of the network of the present invention is similar to the above-mentioned second embodiment, except that the message construction unit is integrated in the CPM capability center entity instead of the interworking function entity. This embodiment is described in detail as follows:

The network includes a CPM capability center entity, a CPM user preference information entity, a media and message storage functional entity, a converged address book functional entity, and a message notification entity. The CPM user preference information entity, media and message storage functional entity, and integrated address book functional entity may be similar to the corresponding entities in the above-mentioned second embodiment, and will not be repeated here.

The CPM capability center entity includes a sending judging unit and a message constructing unit. The sending judging unit is used for judging whether to use a non-SIP protocol-based message to send the notification message to the user. The message construction unit is configured to construct the notification message in a non-SIP protocol-based message manner when the sending judging unit judges that a non-SIP protocol-based message needs to be used to send the notification message to the user.

A communication interface is included between the CPM capability center entity and the message notification entity. In specific implementation, this message notification entity can be exactly the same as the short message center in the existing GSM/GPRS/PSTN network, even can be exactly the short message center in the existing GSM/GPRS/PSTN network; It can be other non-SIP-based message processing entities, such as the MMS server of MMS, the IMPS server of IMPS, or the mail server in the EMAIL service, etc., depending on which non-SIP-based service the operator decides to use to send notifications. Certainly. As mentioned above, the non-SIP protocol-based message is determined corresponding to a specific message notification entity. For example, if the message notification entity is an IMPS server, the non-SIP protocol-based message is an IMPS message.

The message notification entity can be used as a component of the network alone, or as a service component of various service support components that have an interface with the network, depending on the network setting of the operator.

Every time the CPM capability center entity receives a message to be sent to the CPM user, if the CPM user is currently unreachable, it will decide whether to A notification message is sent to the CPM user when the CPM user becomes reachable. If the CPM capability center entity decides to use the CPM message to send the notification, it will directly construct the CPM notification message and send it to the CPM user through the SIP/IP Core. When the sending judging unit of the CPM capability center entity judges that it is necessary to use a non-SIP protocol-based message to send a notification message to the unreachable CPM user, the message construction unit uses a non-SIP protocol-based message to construct the notification message. The notification message, and then send the notification message to the message notification entity through the communication interface between the CPM capability center entity and the message notification entity, and send the notification message to the CPM user through the message notification entity. The specific protocol format of the notification message is related to the type of message service supported by the message notification entity. For example, if the message notification entity is a short message center, the constructed notification message is of the short message type.

As can be seen from the above, this embodiment modifies and enhances the existing CPM network architecture, adopts the method of adding a sending judgment unit and a message construction unit in the CPM capability center entity, and judges that it is necessary to use a non-based When the message of the SIP protocol sends a notification message to the user, the message construction unit generates a notification message that is not based on the SIP protocol and allows the unreachable CPM user to receive, and then sends the notification message to the CPM through the message notification entity user. That is to avoid the technical problem of not being able to notify unregistered CPM users due to the direct use of messages based on the SIP protocol in the prior art, by converting the source of messages based on the SIP protocol, the unregistered CPM users can receive the converted Messages enable the CPM network architecture to solve the problem of how to send notification messages to unreachable users, and users can get messages based on the SIP protocol as soon as possible, so that they can respond and operate in a timely manner.

Referring to Fig. 5 and Fig. 6, the fourth and fifth implementations of the network of the present invention are similar to the above-mentioned second implementation, the difference is that the message construction unit is integrated in the third-party application entity instead of the interworking functional entity. The fourth and fifth implementation modes of the network of the present invention are described in detail as follows:

The network includes a CPM capability center entity, a CPM user preference information entity, a media and message storage functional entity, a converged address book functional entity, a message notification entity, and a third-party application. The CPM user preference information entity, media and message storage functional entity, and integrated address book functional entity may be similar to the corresponding entities in the above-mentioned second embodiment, and will not be repeated here.

The CPM capability center entity includes a sending judging unit and a request sending unit. The sending judging unit is used to judge whether to use a non-SIP protocol-based message to send a notification message to the user; the request sending unit is used to send a notification message carrying the The request message of the identification of the CPM user and the notification content is sent to the third-party application entity.

The third-party application is a common concept in the service network, which refers to those application servers that do not belong to the user's home network or the user's roaming network, such as China Mobile users who watch news on Sina.com through the GPRS network, The news service provided by Sina.com can be regarded as a third-party application. The third-party application also includes a message construction unit and an interface with the message notification entity. The message construction unit is configured to: when the sending judging unit of the capability center entity judges that a non-SIP protocol-based message needs to be used to send a notification message to the CPM user, receive the identification and notification content carrying the CPM user The request message, and then construct the notification message in a non-SIP protocol-based message manner according to the CPM user's identity and notification content.

Referring to Fig. 5, the third-party application entity is an access platform server, which can be shared by multiple services. In this embodiment, the message notification entity first accesses the access platform server, and then receives the message from the CPM capability center entity and converted by the message construction unit through the access platform server. The message notification entity then sends the notification message constructed by the message construction unit to the user.

Referring to FIG. 6, in the fifth embodiment of the network of the present invention, the message notification entity is integrated in the third-party application entity, and is an application server for sending notification messages. The application server can directly implement the message notification entity, Therefore, there is a direct interface with the CPM competence center entity.

The function and realization of the message notification entity may be the same as that of the message notification entity in the foregoing two implementation manners, and the description will not be repeated here.

Every time the CPM capability center entity receives a message to be sent to the CPM user, if the CPM client is currently unreachable, it will decide whether to A notification message should be sent to the CPM user when the CPM user becomes reachable. If the CPM capability center entity decides to use the CPM message to send the notification, it will directly construct the CPM notification message and send it to the CPM client through the SIP/IP Core. If the sending judging unit of the CPM capability center entity judges that it is necessary to use a message not based on the SIP protocol to send a notification to the unreachable user, the request sending unit sends a request message to the message notification application server in the third-party application or accesses the message notification The entity's access platform server. It carries the CPM user ID to be notified, the content to be notified (such as the address of the media data stored in the network, etc.), relevant information, etc., and instructs the third-party application to initiate the notification process. The message construction unit in the third-party application can construct a notification message in a non-SIP-based message manner, and send it to the CPM user through the message notification entity. The specific protocol format of the notification message is related to the type of message service supported by the message notification entity. For example, if the message notification entity is a short message center, the constructed notification message is of the short message type.

This embodiment can realize the function of sending a notification message to the user when the user is unreachable, and achieve a technical effect similar to that of the above third embodiment of the network.

In other implementation manners, the notification content of the message constructed by the message construction unit may also include any one or a combination of at least two of the following:

1) Any message sent by other users to said user;

2) Obtain the address information of the media data;

3) Instruction information instructing the user to perform service registration; for example, when the CPM user is unreachable, the CPM capability center entity may try to notify the CPM user to register based on the SIP protocol service by sending a notification message;

4) prompt information to remind the user to recharge; for example, before the CPM user is about to be shut down due to arrears, the CPM capability center entity notifies the CPM user to recharge in time by sending a notification message, so that the currently ongoing session can continue without interruption;

5) Notification information prompting a user corresponding to a certain identifier to communicate with the user.

In other implementation manners, the network may not be limited to a network carrying IP-based converged message services, but may also be a POC or multimedia conference service network, etc., and the cellular network-based push-to-talk service or multimedia conference service network The structure can be similar to the structure in the above-mentioned network embodiment of the present invention, and both can be used in the present invention to realize message notification.

Referring to Figure 7, the present invention also provides a capability center entity, including:

A sending judging unit, configured to judge whether to use a non-SIP protocol-based message to send a notification message to the user;

A message construction unit, configured to construct the notification message in a non-SIP protocol-based message manner when the capability center entity judges that a non-SIP protocol-based message needs to be used to send a notification message to the user.

The capability center entity and the CPM client communicate through the SIP/IP Core, and each time the CPM capability center entity receives a message to be sent to a certain CPM user from the CPM client, the sending judgment unit of the CPM capability center entity It is determined that a non-SIP protocol-based message needs to be used to send a notification message to the unreachable CPM user, and then a message construction unit is used to construct the notification message in a non-SIP protocol-based message manner. Finally, unregistered users can be notified through the message notification unit

It can be seen from the above that this embodiment modifies and enhances the existing network architecture, adopts the method of adding a sending judgment unit and a message construction unit in the capability center entity, and uses non-SIP protocol-based messages in the capability center entity The notification message is constructed in the way and sent to unregistered users through the message notification unit. That is to say, the implementation mode of the capability center entity of the present invention can cooperate with the message notification entity, and by converting the source of the message based on the SIP protocol, the unregistered CPM user can receive the converted message, so that the network can solve how to send the message to the unreachable For the problem of the user sending a notification message, the user can get the source of the message based on the SIP protocol as soon as possible, so that the user can respond and operate in time.

Referring to Figure 8, the present invention also provides a capability center entity, including:

A sending judging unit, configured to judge whether to use a non-SIP protocol-based message to send a notification message to the user,

The request sending unit is used to send a request message based on the SIP protocol carrying the user's identification and notification content to the first entity including the message construction function when it is determined that a non-SIP protocol-based message needs to be used to send a notification message to the user .

A communication interface is included between the capability center entity and the first entity including the message construction function. In a specific implementation, the first entity including the message construction function may be a capability center entity, a third-party application entity, or an interworking function entity. Construct a notification message that the unregistered user can receive through the first entity, and then notify the unregistered user via the message notification entity

As can be seen from the above, this embodiment modifies and enhances the existing network, and adopts the method of adding a sending judging unit in the capability center entity, and the sending judging unit judges that it is necessary to use a message not based on the SIP protocol to send a notification message to When the user is a user, a request message is generated, so that the first entity generates a notification message not based on the SIP protocol that the unreachable user can receive. That is to avoid the technical problem of not being able to notify unregistered CPM users due to the direct use of messages based on the SIP protocol in the prior art, by converting the source of messages based on the SIP protocol, the unregistered CPM users can receive the converted Messages enable the CPM network architecture to solve the problem of how to send notification messages to unreachable users, and users can get messages based on the SIP protocol as soon as possible, so that they can respond and operate in a timely manner.

When the first entity is an interworking functional entity, while achieving the above-mentioned technical effects, the modification of the CPM capability center entity is not significant. The innovation of the invention will not affect the independent evolution and development of each function of the existing network, so the cost of network upgrade and redesign is not large.

Finally, this embodiment also makes the operator pay a very small price, thereby protecting the investment of the operator.

Referring to FIG. 9, the present invention also provides an interworking functional entity, including:

a request receiving unit, configured to receive a request message carrying a user identifier and notification content from a capability center entity,

A message construction unit, configured to construct a notification message carrying the user identifier and notification content in a non-SIP protocol-based message manner,

A message sending unit, configured to send the notification message to the user through a message notification entity.

As can be seen from the above, in this embodiment, by modifying and enhancing the existing network, when receiving the request message from the request receiving unit, the message construction unit generates a non-SIP protocol-based message that unreachable users can receive. The notification message, and then send the notification message to the user through the message notification entity. That is to avoid the technical problem of not being able to notify unregistered CPM users due to the direct use of messages based on the SIP protocol in the prior art, by converting the source of messages based on the SIP protocol, the unregistered CPM users can receive the converted Messages enable the CPM network architecture to solve the problem of how to send notification messages to unreachable users, and users can get messages based on the SIP protocol as soon as possible, so that they can respond and operate in a timely manner.

Referring to Figure 10, the present invention also provides a message notification method, including:

Step 1001: Determine whether to send a notification message to the user in a non-session initiated SIP protocol-based message manner;

Step 1002: When it is judged that a non-SIP protocol-based message needs to be used to send a notification message to the user, construct the notification message in a non-SIP protocol-based message manner;

In this step, the notification message may be constructed by means of a non-SIP-based message through the capability center entity, interworking function entity or third-party entity.

Step 1003: Send the constructed notification message to the user.

Wherein, the structured notification message may be sent to the user through the short message center, MMS server, IMPS server or mail server of the GSM/GPRS/PSTN network.

The above-mentioned implementation of the capability center entity and the interworking function entity may be a CPM capability center entity of a CPM network or a capability center entity of a push-to-talk service or a multimedia conference service network based on a cellular network.

It is worth noting that the sending judging unit and the request sending unit in the embodiment of the capability center entity of the present invention can be integrated into one processing module; at the same time, the request receiving unit, the message construction unit and the message The sending unit can also be integrated in a processing module. Similarly, each unit in the embodiment of the message notification entity of the present invention may also be integrated into one processing module.

It is also worth noting that each unit in the embodiments of the network, capability center entity, interworking function entity, and message notification entity of the present invention can be implemented in the form of hardware or software function modules. The above-mentioned units that can be implemented in the form of software can be sold or used as independent products, or can be stored in a computer-readable storage medium.

A network, a capability center entity, an interworking function entity, and a message notification method provided by the present invention have been described above in detail through specific embodiments. The description of the above embodiments is only used to help understand the method and idea of the present invention; at the same time, For those of ordinary skill in the art, according to the idea of the present invention, there will be changes in the specific implementation and scope of application. In summary, the contents of this specification should not be construed as limiting the present invention.

Claims (15)

1. A network, characterized in that, comprising: The capability center entity includes a sending judging unit for judging whether to use a message not based on the session initiation SIP protocol to send a notification message to the user, The first entity includes a message construction unit, the message construction unit is used to construct the notification in a non-SIP protocol-based message mode when the capability center entity judges that a non-SIP protocol-based message needs to be used to send a notification message to the user information, A message notification entity, configured to send the notification message constructed by the message construction unit to the user. 2. The network according to claim 1, characterized in that said first entity is said competence center entity. 3. The network according to claim 1, wherein the first entity is an interworking function entity, and the capability center entity further includes a request sending unit, configured to use a non-SIP protocol-based message When sending a notification message to the user, send a request message carrying the user identifier and notification content to the message construction unit. 4. The network according to claim 1, wherein the first entity is a third-party application entity, and the capability center entity further includes a request sending unit, configured to use a non-SIP protocol-based When the message sending notification message is sent to the user, a request message carrying the user ID and notification content is sent to the message construction unit. 5. The network according to claim 4, wherein the message notification entity is integrated in the third-party application entity. 6. The network according to claim 1, characterized in that, the notification content in the message constructed by the message construction unit includes any one or a combination of at least two of the following: any messages sent by other users to said user; Obtain the address information of the media data; Instruction information instructing the user to perform service registration; A prompt message reminding the user to recharge; Notification information that prompts a user corresponding to a certain identifier to communicate with the user. 7. The network according to any one of claims 1 to 6, wherein the message notification entity is a short message center, a multimedia message service server, an instant messaging message service server or a mail server of a GSM/GPRS/PSTN network . 8. The network according to any one of claims 1 to 6, characterized in that, the network is a network that bears an IP-based converged message CPM service, and the message based on the SIP protocol refers to an IP-based converged message. 9. A competence center entity, characterized in that it comprises: A sending judging unit, configured to judge whether to use a non-SIP protocol-based message to send a notification message to the user, A message construction unit, configured to construct the notification message in a non-SIP protocol-based message manner when the sending judging unit judges that a non-SIP protocol-based message needs to be used to send a notification message to the user, and send it to the message notification entity. 10. A competence center entity, characterized in that it comprises: A sending judging unit, configured to judge whether to use a non-SIP protocol-based message to send a notification message to the user, The request sending unit is configured to send a request message carrying the user's identification and notification content to the first entity including the message construction function when it is determined that a notification message needs to be sent to the user using a message not based on the SIP protocol. 11. The capability center entity according to claim 10, wherein the first entity is an interworking function entity or a third-party application entity. 12. An interworking functional entity, comprising: a request receiving unit, configured to receive a request message carrying a user identifier and notification content from a capability center entity, A message construction unit, configured to construct a notification message carrying the user identifier and notification content in a non-SIP protocol-based message manner, A message sending unit, configured to send the notification message to the user through a message notification entity. 13. A message notification method, characterized in that, comprising: Determine whether to use a non-session-initiated SIP protocol-based message mode to send a notification message to the user; When judging that a non-SIP protocol-based message needs to be used to send a notification message to the user, the non-SIP protocol-based message mode is used to construct the notification message; sending the constructed notification message to the user. 14. The message notification method according to claim 13, wherein the notification message is constructed by a capability center entity, an interworking function entity or a third-party entity. 15. message notification method according to claim 13, is characterized in that, the notification message of described construction is sent by the short message center of GSM/GPRS/PSTN network, multimedia message service server, instant message message service server or mail server to said user.

Images