WO2008128469A1

WO2008128469A1 - Network, ability center entity, interworking function entity and message notifying method

Info

Publication number: WO2008128469A1
Application number: PCT/CN2008/070739
Authority: WO
Inventors: Yajuan Wu
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-04-19
Filing date: 2008-04-17
Publication date: 2008-10-30
Also published as: CN101291297A

Abstract

A network, an ability center entity, an interworking function entity and a message notifying method are provided. The network includes: a sending judging unit to judge whether to send the notifying message to user based on non-SIP message; a message constructing unit to construct the notifying message based on non-SIP message when the sending judging unit determines that there is a need to send the notifying message based on the non-SIP message to user; and a message notifying entity to send the notifying message constructed by the message constructing unit to the user.

Description

Network, capability center entity, interworking function entity and message notification method This application claims to be submitted to the Chinese Patent Office on April 19, 2007, the application number is 200710096963.6, and the invention name is "network, capability center entity, interworking function entity and message notification method". The priority of the Chinese Patent Application, the entire contents of which is incorporated herein by reference. Technical field

The present invention relates to the field of communications, and in particular, to a network and its functional entities and a message notification method.

Background technique

IP-based Converged IP Messaging (CPM, Converged IP Messaging) is the Open Mobile Alliance

(OMA, Open Mobile Alliance) advocates a defined new messaging business framework that provides users with a converged business experience. The CPM service allows users to use communication services with different technical features in a unified manner to overcome the gap between non-CPM message services caused by technical differences, and provide a unified service experience for user services. CPM needs to support IP-based messages. Interworking between services and traditional messaging services to enable maximum interoperability between users. In addition, CPM needs to achieve the same business experience regardless of the IP domain of the user. The messaging service provides a unified implementation of the technology and uses common billing principles.

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 10, an interworking function entity 11, a CPM user preference information entity 12, a media and message storage function entity 13, and a converged address book function. Entity 14, where:

The CPM Competency Center entity 10 is a service server that processes CPM services in the CPM network. The CPM Competency Center entity 10 and the supporting component include a direct interface for using existing service capability units provided in various networks; and an interface between the CPM user preference information entity 12 for obtaining CPM user saves. Setting information about preferences and the like in the network; and an interface with the third-party application entity 15 for the CPM user to use the third-party application. In addition, the CPM Competency Center entity 10 and the remote CPM network 16 are routed through a Session Initiation Protocol and/or Internet Protocol Core based on Session Initiation Protocol and/or Internet Protocol Core. Similarly, CPM Competency Center Entity 10 and CPM Client 17 communicate via SIP/IP Core. The interworking function entity 11 is responsible for accepting messages from the CPM Competency Center entity 10 and converting the message into a protocol format supported by other non-CPM message services, such as Short Message Service (SMS)/Multimedia Message Service (MMS, Multimedia). Message Service) / Instant Messaging and Presence Services (IMPS), etc., sent to the corresponding message network; and will be from other non-CPM message networks, for example, from non-CPM business function entities The message received in 18 is converted into a CPM message and sent to the CPM Competency Center entity 10.

The media and message storage function entity 13 is a storage database set 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 users. Visit or download. The use of the CPM user's media and message storage functional entity 13 by other CPM users is accomplished through the CPM Competency Center entity 10.

The fused address book function entity 14 is an entity that is stored in the network and incorporates address information on 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 messaging mechanism according to his or her preference for use when it is not reachable, for example, when the CPM user is not registered in the home network. Each functional entity of the CPM network processes the received SIP-based message according to the setting. The messaging mechanism can be: 1) discarding the received SIP-based message; 2) temporarily saving the received SIP-based message and transmitting it later, such as when the user becomes reachable again; 3) The received SIP-based message is stored in the user's network storage function entity, and the user is notified to read the saved SIP-based message, such as when the user becomes reachable again.

In carrying out the creation process of the present invention, the inventors have found that at least the following problems exist in the above-mentioned prior art CPM network: As described above, if there is a CPM message sent to a CPM user, the CPM network needs to have the message in a temporary storage entity or network. The storage entity saves, and further informs the user to specify the location to retrieve the saved information. According to the existing CPM high-level architecture, the CPM network can only notify the CPM user by sending a CPM notification message, but when the CPM user is not registered in the home CPM network, the status of the user is unreachable in the CPM network. Therefore, this notification message cannot be received by the user. It can be seen that the existing CPM network architecture cannot implement the notification function for CPM users who are not registered in the home CPM network. Summary of the invention

An embodiment of the present invention provides a network that can send a notification message to an unregistered CPM user.

Another aspect of an embodiment of the present invention provides a capability center entity, an interworking function entity, and a message notification entity to support sending a notification message to an unregistered CPM user.

Another aspect of an embodiment of the present invention provides a message notification method for implementing a notification message to an unregistered CPM user.

An embodiment of the present invention provides a network, including:

a sending determining unit, configured to determine whether to send a notification message to the user by using a non-SIP-based message;

a message construction unit, configured to construct the notification message by using a non-SIP-based message manner when the sending determination unit determines that a non-SIP-based message transmission notification message needs to be sent to the user;

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

The embodiment of the present invention avoids the technical problem that the prior art cannot notify the unregistered CPM user by directly using the SIP protocol-based message by modifying and enhancing the existing network, by using the source-based SIP protocol-based message. The protocol conversion enables the unregistered CPM user to receive the message content or obtain a related notification, so that the CPM network architecture can solve the problem of how to send the notification message to the unreachable user, and the user can get the SIP-based message as soon as possible. , so that you can react and operate in time.

An embodiment of the present invention provides a capability center entity, including:

The message constructing unit is configured to construct the notification message by using a non-SIP-based message manner when the sending determining unit determines that it is necessary to use a non-SIP-based message to send a notification message to the user. The capability center entity of the embodiment of the present invention can cooperate with the message notification entity to enable the unregistered CPM user to receive the converted message by converting the source-based SIP protocol-based message, so that the network can solve how to reach the unreachable user. The problem of sending a notification message, the user can get it as soon as possible The source is a SIP-based message, so that it can react and operate in time.

And a request sending unit, configured to: when the sending determining unit determines that a non-SIP-based message sending notification message needs to be sent to the user, send a request message carrying the identifier of the user and the notification content. By using the capability center entity of the embodiment of the present invention, it is possible to avoid the technical problem that the prior art cannot notify the unregistered CPM user by directly using the SIP protocol-based message, and by converting the source-based SIP-based message, The unregistered CPM user can receive the converted message, so that the CPM network architecture can solve the problem of how to send a notification message to the unreachable user, and the user can get the source-based SIP protocol-based message as soon as possible, so that the response and operation can be performed in time.

An embodiment of the present invention provides an interworking function entity, including:

a request receiving unit, configured to receive a request message that carries a user identifier and a notification content;

a message construction unit, configured to construct a notification message carrying the user identifier and the notification content by using a non-SIP-based message manner;

a message sending unit, configured to send the notification message.

The interworking function entity of the embodiment of the present invention can avoid the technical problem that the prior art cannot notify the unregistered CPM user by directly using the SIP protocol-based message, and can convert the source-based SIP-based message. The unregistered CPM user can receive the converted message, so that the CPM network architecture can solve the problem of how to send a notification message to the unreachable user, and the user can get the source-based SIP protocol-based message as soon as possible, so that the response and operation can be performed in time.

An embodiment of the present invention provides a message notification method, including:

Determining whether to send a notification message to the user by using a message that is not based on the session initiation SIP protocol; and when determining that the notification message needs to be sent to the user by using a non-SIP-based message, constructing the notification by using a non-SIP-based message mode Message

The constructed notification message is sent to the user.

By using the message notification method of the embodiment of the present invention, the prior art can be avoided due to the direct use of the base. The technical problem of not being able to notify the unregistered CPM user by the message of the SIP protocol, by performing protocol conversion on the source of the SIP-based message, enables the unregistered CPM user to receive the message content or obtain a related notification, so that the CPM network The architecture can solve the problem of how to send notification messages to unreachable users. Users can get the SIP-based messages as soon as possible, so that they can react and operate in time.

DRAWINGS

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

2 is a schematic block diagram of a first embodiment of the network of the present invention;

3 is a schematic block diagram of a second embodiment of the network of the present invention;

4 is a schematic block diagram of a third embodiment of the network of the present invention;

Figure 5 is a schematic block diagram of a fourth embodiment of the network of the present invention;

6 is a schematic block diagram of a fifth embodiment of the network of the present invention;

7 is a schematic block diagram of a first embodiment of a capability center entity of the present invention;

8 is a schematic block diagram of a second embodiment of a capability center entity of the present invention;

9 is a schematic block diagram of a first embodiment of an interworking function entity of the present invention;

Figure 10 is a schematic block diagram of a first embodiment of the message notification method of the present invention.

detailed description

Referring to FIG. 2, a first embodiment of the network provided by the present invention includes a CPM capability center entity 21, a first entity 22, and a message notification entity 23. among them:

The CPM capability center entity 21 includes a sending determining unit, configured to determine whether to use a non-SIP-based message to send a notification message to the user; the first entity 22 includes a message constructing unit, configured to determine, at the capability center entity 21, that the non-based When the message of the SIP protocol sends a notification message to the user, the notification message is constructed by using a non-SIP-based message manner; the message notification entity 23 is configured to send the notification message constructed by the message construction unit to the user.

As can be seen from the above, the present embodiment performs the modification and enhancement of the existing network, and when it is determined that the non-SIP-based message transmission notification message needs to be sent to the user, the message construction unit generates a non-SIP-based protocol. The notification message is sent to the user by the message notification entity, thereby avoiding the technical problem that the prior art cannot notify the unregistered CPM user due to directly using the SIP protocol-based message. By agreeing on a source-based SIP-based message The conversion enables the unregistered CPM user to receive the message content or obtain a related notification, so that the CPM network architecture can solve the problem of how to send the notification message to the unreachable user, and the user can obtain the source-based SIP protocol-based message, thereby Respond and operate in a timely manner.

The present invention will be further described in detail below with reference to the 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 embodiment or other implementation manners, the network may be a network carrying an IP-based converged message service, and the SIP-based message refers to an IP-based converged message. The network includes a CPM Competency Center entity, an Interworking Function Entity, a CPM User Preferences 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 function entity is a storage database set 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 User access or download. The use of the media and message storage functional entities of the CPM user by other CPM users is implemented through the CPM Competency Center entity.

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

The CPM capability center entity and the support component include a direct interface for using existing service capability units provided in various networks; and an interface between the CPM user preference information entity for obtaining CPM user saves Setting information about preferences in the network; including an interface with third-party application entities to facilitate CPM users to use third-party applications. In addition, the CPM capability center entity and the remote CPM network are routed through the SIP/IP Core network. Similarly, CPM Competency Center entities and CPM clients communicate over SIP/IP Core. The CPM capability center entity further includes a sending determining unit and a request sending unit (not shown). The sending determining unit is configured to determine whether to send a notification message to the user by using a non-SIP-based message, and the request sending unit is configured to: in the sending determining unit, determine that the notification message needs to be sent by using a non-SIP-based message When the user is given, a request message carrying the identifier of the CPM user and the notification content is sent to the interworking function entity.

The SIP protocol mentioned in this embodiment is a SIP protocol that enhances the CPM service. In other embodiments, it may also be an enhanced SIP protocol for other services, such as a cellular network-based Push to talk Over cellular (POC) and a multimedia conference service (Multimedia Conferencing) SIP protocol, so-called enhancement. The SIP protocol refers to the SIP protocol that extends part of the message header and message body content based on the standard SIP protocol. As mentioned in this embodiment, it is determined that the non-SIP-based message sending notification message needs to be used by the user to: determine that it is necessary to use any possible non-CPM-based enhanced SIP protocol message.

In other embodiments, the SIP protocol may be an enhanced SIP protocol for the PoC service. In this case, it is determined that the notification message needs to be sent to the user by using a non-SIP-based message: The enhanced SIP protocol message is based on the PoC-based service. The same is true for other businesses.

That is to say, the SIP protocol in the "non-SIP-based messages" mentioned elsewhere in this document may depend on the network of the application. Of course, if the requirements are met, the SIP protocol mentioned in the present invention can also be a standard SIP protocol.

The interworking function entity is responsible for receiving a message from the CPM capability center entity, converting it, and converting the protocol format supported by the non-SIP-based message service, such as a short message service format, or a multimedia message service format, or Instant messaging message format, or email format, etc., sent to the corresponding message network; and will convert messages received from other non-SIP-based message networks, such as non-CPM service function entities, into SIP-based protocols Messages are sent to the CPM Competency Center entity. A communication interface is included between the interworking function entity and the message notification entity. The interworking function entity includes a message construction unit (not shown) and an interface with the message notification entity. The message constructing unit is configured to: when the sending determining unit of the capability center entity determines that a non-SIP-based message sending notification message needs to be sent to the CPM user, receive a message carrying the identifier and the notification content of the CPM user. And then according to the identification and notification content of the CPM user, the notification message is constructed by using a non-SIP protocol based message mode.

The message notification entity is configured to send the notification message constructed by the message construction unit to the user. The message notification entity may be identical to the short message center in the existing GSM/GPRS/PSTN network, or even a short message center in the existing GSM/GPRS/PSTN network; the message notification entity may also be other Non-CPM message processing entities, such as MMS MMS The server, the IMPS server of the IMPS, or the mail server in the EMAIL service may depend on which non-SIP-based service is used by the operator to send the notification. As described above, the non-SIP-based message is corresponding to a specific message notification entity, for example, the message notification entity is a mail server, and the non-SIP-based message is simply SMTP (Simple Mail Transfer Protocol). Mail transfer protocol message.

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

In the application, CPM users can set up a messaging mechanism according to their own preferences, which is convenient for processing messages when the message is 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. The messaging mechanism can be: 1) discarding the received CPM message; 2) temporarily saving the received CPM message and then transmitting it, such as when the user becomes reachable again; 3) in the media and message network storage The function entity stores the received CPM message and notifies the user to read the saved CPM message, for example, when the user becomes reachable again.

In the case of mechanisms 2) and 3), each time the CPM Competency Center entity receives a message to be sent to a CPM user, the CMU Capability Center entity's transmission judging unit judges that it is necessary to use a non-SIP-based message. Sending a notification message to the unreachable CPM user, the request sending unit sends a request message to the interworking function entity, where the CPM user identifier to be notified, the notification content (such as information storage address, message original text, message digest, etc.), Related information, etc., instructs the interworking function entity to initiate the notification process. The message constructing unit in the interworking function entity constructs the notification message by using a non-SIP-based message manner according to the CPM user identifier and the notification content, and sends the notification message by using a communication interface with the message notification entity. The message is notified to the entity, and the notification message is sent to the CPM user through the message notification entity, and the extracted information is extracted to the specified location. Or, the message sent to the CPM user carries the message content to be sent to the CPM user received by the CPM capability center entity.

The specific protocol format of the notification message is related to the type of the 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 Is a short message type. The specific content of the notification message is independent of the protocol format of the message.

In the above network, the interworking function entity determines, according to the received message from the CPM capability center entity, what measures are taken: if it is a normal communication request message, the message is converted according to the identity of the called user, and then sent to the corresponding The non-SIP-based service processing entity in the other network; if the notification message is to be sent, the notification message is constructed according to the identifier of the receiving user to send the notification, that is, the format conversion of the message is sent to the specified message notification entity. .

As can be seen from the above, the present embodiment modifies and enhances the existing CPM network architecture, and uses the method of adding the sending judgment unit and the request sending unit in the CPM capability center entity, and the entity in the CPM capability center needs to use the non- When the message sent by the SIP protocol is sent to the user, the request message is generated to the interworking function entity; the message construction unit is added to the interworking function entity, and the message construction unit uses the non-SIP-based message mode according to the received request message. Constructing a notification message that the unreachable user can receive, and then sending the notification message to the user through the message notification entity, thereby avoiding the technical problem that the prior art cannot notify the unregistered CPM user due to directly using the SIP protocol-based message. By converting the source-based SIP-based message, the unregistered CPM user can receive the converted message, so that the CPM network architecture can solve the problem of how to send the notification message to the unreachable user, and the user can obtain the source. For SIP-based , Which can react and operate in a timely manner.

While the above technical effects are achieved, the modification of the CPM capability center entity in this embodiment mode is small. The interworking function entity needs to communicate with the existing non-SIP-based services. Therefore, it has supported other non-SIP-based services such as short messages and message processing functions. It is used in the CPM capability center entity and interworking function entities. The interface to transmit the request message does not impose any new burden on the interworking function entity. This architecture also does not affect the independent evolution and evolution of the various functions of the CPM network architecture, so the cost of network upgrades and redesigns is small.

This embodiment also makes the operator pay a very small price, thereby protecting the operator's investment. Referring to FIG. 4, the third embodiment of the network of the present invention is similar to the second embodiment described above, except that the message construction unit is integrated in the CPM capability center entity without interworking functional entities. This embodiment is described in detail as follows:

The network includes a CPM Competency Center entity, a CPM User Preferences Information Entity, a Media and Message Storage Functional Entity, a Converged Address Book Functional Entity, and a Message Notification Entity. The CPM user preference letter The entity entity, the media and message storage function entity, and the fused address book function entity may be similar to the corresponding entities of the second embodiment described above, and are not described again.

The CPM capability center entity includes a transmission judging unit and a message construction unit (not shown). The sending determining unit is configured to determine whether to send a notification message to the user by using a non-SIP-based message; the message constructing unit is configured to: in the sending determining unit, determine that the notification message needs to be sent by using a non-SIP-based message When the user is in the user, the notification message is constructed by using a non-SIP-based message.

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

The message notification entity may be separately used as an integral part of the network or as a service component of various service support components that have interfaces with the network, depending on the operator's networking settings.

Each time the CPM Competency Center entity receives a message to be sent to a CPM user, if the CPM user is currently unreachable, it decides whether or not to use the policy information such as the user's preference, or the user's settings in the network, or the operator's settings. A notification message is sent to the CPM user when the CPM user becomes reachable. If the CPM Competency Center entity decides to send a notification using the CPM message, the CPM notification message is directly constructed to be sent to the CPM user through the SIP/IP Core. When the sending judgment unit of the CPM capability center entity determines that a non-SIP-based message sending notification message needs to be used for the unreachable CPM user, the message constructing unit uses a non-SIP-based message mode. The notification message is constructed, and then the notification message is sent to the message notification entity through a communication interface between the CPM capability center entity and the message notification entity, and is sent to the CPM user by 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 It is a short message type.

As can be seen from the above, the present embodiment modifies and enhances the existing CPM network architecture, and uses the manner of adding the transmission judgment unit and the message construction unit in the CPM capability center entity, and determines that the transmission judgment unit needs to use the method. When the non-SIP-based message sends a notification message to the user, the non-SIP-based notification message is generated by the message construction unit, and the notification message is sent to the CPM user by the message notification entity, thereby avoiding the existing The technology causes technical problems that cannot be notified to unregistered CPM users due to the direct use of SIP-based messages. By converting the source-based SIP protocol-based message, the unregistered CPM user can receive the converted message, so that the CPM network architecture can solve the problem of how to send the notification message to the unreachable user, and the user can obtain the source based on The SIP protocol message allows for timely response and operation.

Referring to FIG. 5 and FIG. 6, the fourth and fifth embodiments of the network of the present invention are similar to the second embodiment described above, except that the message construction unit is integrated in the third-party application entity without interworking function entities. The fourth and fifth embodiments of the network of the present invention are detailed as follows:

The network includes a CPM Competency Center entity, a CPM User Preferences Information Entity, a Media and Message Storage Functional Entity, a Converged Address Book Functional Entity, a Message Notification Entity, and a Third Party Application Entity. The CPM user preference information entity, the media and message storage function entity, and the fused address book function entity may be similar to the corresponding entities in the second embodiment described above, and are not described again.

The CPM capability center entity includes a transmission determining unit and a request sending unit (not shown). The sending determining unit is configured to determine whether to send a notification message to the user by using a non-SIP-based message; the request sending unit is configured to determine, in the sending determining unit, that the notification message needs to be sent by using a non-SIP-based message When the user is given, a request message carrying the CPM user identifier and the notification content is sent to the third-party application entity.

The third-party application is a common concept in a service network, and refers to those application servers that do not belong to the user's home network and do not belong to the user's roaming network. The third party application entity further includes a message construction unit (not shown) and an interface with the message notification entity. The message constructing unit is configured to: when the sending determining unit of the CPM capability center entity determines that a non-SIP-based message sending notification message needs to be sent to the CPM user, receiving the identifier and the notification carrying the CPM user The message of the content is then constructed according to the identifier of the CPM user and the notification content, and the notification message is constructed by using a non-SIP-based message. Referring to FIG. 5, the third-party application entity may be an access platform server, which may be shared by multiple services. In this implementation manner, the message notification entity receives the message from the CPM capability center entity and is converted by the message construction unit by first accessing the access platform server, and then through the access platform server. The message notification entity then sends the notification message constructed by the message construction unit to the CPM user.

Referring to FIG. 6, in a fifth implementation manner 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 a notification message, where the application server can directly implement a message notification entity. This directly interfaces with the CPM Competency Center entity.

The message notification entity may be the same as the message notification entity in the foregoing two embodiments, and the description is not repeated here.

Each time the CPM Competency Center entity receives a message to be sent to the CPM user, if the CPM client is currently unreachable, it determines whether the CPM client is currently unreachable, based on the user's preferences, or the user's settings in the network, or the operator's settings. A notification message is sent to the CPM user when the CPM user becomes reachable. If the CPM Competency Center entity decides to use the CPM message to send a notification, the CPM notification message is directly configured to be sent to the CPM client through the SIP/IP Core. If the sending judgment unit of the CPM capability center entity determines that the non-SIP-based message transmission notification needs to be sent to the unreachable user, the request sending unit sends the request message to the message notification entity or the access message in the third-party application entity. Notify the entity's access platform server. The request message carries a notification to be notified

The CPM user identification, the notification content (such as the address of the media data stored in the network, etc.), related information, etc., instruct the third party application to initiate the notification process. The message construction unit (not shown) in the third-party application entity may construct a notification message by using a non-SIP-based message manner, and send the message to the CPM user through the message notification entity. The specific protocol format of the notification message is related to the type of the 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 a short message type.

This embodiment can implement the function of transmitting a notification message to the user when the user is unreachable, and achieves a technical effect similar to the third embodiment of the network described above.

In other embodiments, the notification content of the message constructed by the message construction unit may further include any one or a combination of at least two:

1) a summary of any message or message sent by other users to the user; 2) obtaining address information of the media data;

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

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

5) A notification message indicating that the user corresponding to a certain identifier wants to communicate with the user.

In other embodiments, the network may be not limited to a network carrying an IP-based converged message service, or may be a POC or a multimedia conference service network, and the network structure of the POC service or the multimedia conference service based on the cellular network may be Similar to the structure in the network embodiment of the present invention described above, message notification can be implemented.

Referring to FIG. 7, an embodiment of the present invention further provides a capability center entity, where the capability center entity 70 includes:

The sending determining unit 701 is configured to determine whether to send a notification message to the user by using a non-SIP-based message;

The message construction unit 702 is configured to construct the notification message by using a non-SIP-based message manner when the transmission determining unit 701 determines that a non-SIP-based message is required to send a notification message to the user.

The capability center entity 70 and the CPM client communicate through the SIP/IP Core, and each time the CPM capability center entity 70 receives a message from the CPM client to be sent to a CPM user, the transmission determination unit 701 of the CPM capability center entity 70 It is determined that the non-SIP-based message transmission notification message needs to be sent to the unreachable CPM user, and the notification message is constructed by the message construction unit 702 in a non-SIP-based message manner. The unregistered user 72 is then notified by the message notification entity 71.

As can be seen from the above, the present embodiment modifies and enhances the existing network architecture by using a method of adding a sending judgment unit and a message construction unit in the capability center entity, and the capability center entity needs to use a non-SIP-based protocol. The message mode constructs a notification message, which is sent to the unregistered user through the message notification unit. The capability center entity of the embodiment of the present invention can cooperate with the message notification entity to enable the unregistered CPM user to receive by converting the source-based SIP-based notification message. The converted notification message enables the network to solve the problem of how to send a notification message to an unreachable user, and the user can obtain a notification message based on the SIP protocol, so that the response and operation can be performed in time.

Referring to FIG. 8, an embodiment of the present invention further provides a capability center entity, where the capability center entity 80 includes:

The sending determining unit 81 is configured to determine whether to send a notification message to the user by using a non-SIP-based message.

The request sending unit 802 is configured to: when the sending determining unit 81 determines that the non-SIP-based message sending notification message needs to be sent to the user, send a SIP protocol-based message carrying the user's identifier and the notification content to the include message structure. The first entity 81 of unit 811.

A communication interface is included between the capability center entity 80 and the first entity 81. In a specific implementation, the first entity 81 may be integrated in the capability center entity, or may be a third-party application entity, or may be an interworking function entity. The notification message that the unregistered user can receive is constructed by the message construction unit 811 in the first entity 81, and then notified to the unregistered user 83 via the message notification entity 82.

It can be seen from the above that the present embodiment modifies and enhances the existing network, and uses the manner of adding the transmission judgment unit in the capability center entity, and the transmission judgment unit determines that it is necessary to use the non-SIP-based message transmission notification. When the message is sent to the user, the request message is generated, and the first entity constructs a non-SIP-based notification message that the unreachable user can receive according to the request message, thereby preventing the prior art from being unable to directly use the SIP-based message. Notify technical issues of unregistered CPM users. By converting the source-based SIP protocol-based message, the unregistered CPM user can receive the converted message, so that the CPM network architecture can solve the problem of how to send the notification message to the unreachable user, and the user can obtain the source based on The SIP protocol message allows for timely response and operation.

When the first entity is an interworking function entity, the modification of the CPM capability center entity is small, and the capability center entity of the embodiment of the present invention does not affect the independent evolution and development of each function of the existing network. Therefore, the cost of network upgrade and redesign is small.

This embodiment also makes the operator pay a very small price, thereby protecting the operator's investment. Referring to FIG. 9, an embodiment of the present invention further provides an interworking function entity, where the interworking function entity 90 includes: The request receiving unit 901 is configured to receive a request message that carries the user identifier and the notification content from the capability center entity 92, where

The message construction unit 902 is configured to construct a notification message carrying the user identifier and the notification content by using a non-SIP-based message manner.

The message sending unit 903 is configured to send the notification message to the unregistered user 93 by the message notification entity 91.

As can be seen from the above, the present embodiment can modify and enhance the existing network. When receiving the request message of the request receiving unit, the message construction unit generates a non-SIP-based protocol, so that the unreachable user can receive The notification message is sent to the user by the message notification entity, thereby avoiding the technical problem that the prior art cannot notify the unregistered CPM user by directly using the SIP protocol-based message, and the source is based on The notification message of the SIP protocol is converted, so that the unregistered CPM user can receive the converted notification message, so that the CPM network architecture can solve the problem of how to send the notification message to the unreachable user, and the user can obtain the source based on the SIP protocol. Notification messages so that responses and operations can be made in a timely manner.

Referring to FIG. 10, the present invention further provides a message notification method, including:

Step 1001: Determine whether to send a notification message to the user by using a message that is not based on the session initiation SIP protocol;

Step 1002: When it is determined that a non-SIP-based message is sent to the user, the notification message is constructed by using a non-SIP-based message manner;

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

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

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

The foregoing capability center entity and the interworking function entity implementation manner may be a CPM capability center entity of the CPM network or a capability center entity of the POC service or the multimedia conference service network of the cellular network.

It should be noted that the sending judgment unit and the request sending unit in the implementation manner of the capability center entity of the present invention may be integrated into one processing module; the request connection in the implementation manner of the interworking function entity of the present invention The receiving unit, the message construction unit, and the message sending unit can also be integrated in one processing module. Similarly, each unit in the embodiment of the message notification entity of the present invention can also be integrated into one processing module.

Those skilled in the art can also know that when the network where the message calling user is located has a high-level network architecture similar to CPM, even if the calling user is not a CPM user but other types of message users, the calling user can still use the present invention. Embodiments are similar to methods for implementing message notifications.

It should also be noted that each unit in the implementation manner of the network, the capability center entity, the interworking function entity, the message notification entity, and the like may be implemented in the form of hardware or in the form of a software function module. The units described above in the form of software can be sold or used as stand-alone products or in a computer readable storage medium.

The foregoing provides a network, a capability center entity, an interworking function entity, and a message notification method provided by the present invention in detail through specific implementation manners. The foregoing description of the embodiments is only used to help understand the method and the idea of the present invention; For those skilled in the art, the details of the present invention and the scope of the application are subject to change without departing from the scope of the invention.

Claims

Rights request

A network, comprising:

The network according to claim 1, wherein the sending determining unit is configured on the capability center entity, and the capability center entity further includes:

And a request sending unit, configured to send, when the sending determining unit determines that a non-SIP-based message sending notification message is sent to the user, the request message carrying the user identifier and the notification content to the message construction unit.

The network according to claim 1, wherein the message construction unit is disposed on the interworking function entity or a third-party application entity.

The network according to claim 3, wherein, when the message construction unit is set on the third-party application entity, the message notification entity is disposed on the third-party application entity.

5. The network according to claim 1, wherein the message construction unit is disposed on a capability center entity.

The network according to any one of claims 1 to 3 or 5, wherein the message notification entity is a service support component.

The network according to claim 1, wherein the notification content in the notification message constructed by the message construction unit includes any one of the following or a set of at least two types:

a summary of any message or message sent by other users to the user;

Obtaining address information of the media data;

Instructing the user to perform service registration indication information;

Reminding the user to prompt information for recharging; A notification message prompting other users to communicate with the user.

The network according to any one of claims 1 to 3 or 5, wherein the message notification entity is set in a short message center of a GSM network or a GPRS network or a PSTN network, a multimedia message service server, and instant messaging. Message service server or mail server.

9. A capability center entity, comprising:

And a message constructing unit, configured to construct the notification message by using a non-SIP-based message manner when the sending determining unit determines that a non-SIP-based message sending notification message needs to be sent to the user.

10. A capability center entity, comprising:

a sending determining unit, configured to determine whether to send a notification message to the user by using a non-SIP-based message,

And a request sending unit, configured to: when the sending determining unit determines that a non-SIP-based message sending notification message needs to be sent to the user, send a request message carrying the identifier of the user and the notification content.

11. An interworking functional entity, comprising:

a request receiving unit, configured to receive a request message carrying a user identifier and a notification content, and a message construction unit configured to construct a notification message carrying the user identifier and the notification content by using a non-SIP-based message manner;

a message sending unit, configured to send the notification message.

12. A message notification method, comprising:

The constructed notification message is sent to the user.

The message notification method according to claim 12, wherein the notification content in the notification message comprises any one of the following or a set of at least two:

a summary of any message or message sent by other users to the user; Obtaining address information of the media data;

Instructing the user to perform service registration indication information; prompting the user to perform recharge prompt information;

A notification message prompting other users to communicate with the user.