JP2010528507A - Method, system, and apparatus for processing service messages using multiple terminals - Google Patents

Abstract

  A method, system, and apparatus for processing business messages using multiple terminals are disclosed. The method includes receiving from a terminal a request message carrying request information of the terminal, and transmitting a business message to the terminal according to the request information. When the user has a plurality of terminals, the push transmission agent selects a specific terminal according to the notification reservation request from the terminal and the terminal request information carried by the notification reservation request. When business arrives, the business message is sent only to the selected terminal, thus avoiding sending the business message to all the terminals of the user.

Description

  This application is a continuation application of International Application No. PCT / CN2008 / 073016 filed on November 11, 2008 claiming the priority of Chinese Patent Application No. 20071016927.4 filed on November 13, 2007 The contents of the application are hereby incorporated by reference in their entirety.

  The present invention relates to mobile communication technology, and more particularly, to a method, system, and apparatus for processing a service message using a plurality of terminals of one user.

  Push technology (Push technology) is a technology based on a client-server mechanism in which a server actively sends information to a client. Push technology is applied in mobile value-added services (VAS) to transfer relevant content in a timely manner and to help users obtain content conveniently. The push mechanism is a content delivery mechanism that operates in a client-server mode in which the server delivers the content desired by the client to the client without receiving a request from the client. FIG. 1 shows a push service in the prior art. The service is started by the server. The push initiator (PI) that generates the push message pushes information to the push proxy gateway (PPG) and transmits the command, and the push content is further transmitted to the user by the PPG. The system includes a PPG, a PI, and a terminal. The PPG obtains a message from the push server via a password authentication protocol (PAP) and sends the content to a wireless application protocol (WAP) user via the push over the air (OTA) protocol. The PI transmits the push content and the transfer command to the PPG, and the PPG transfers the push content to the terminal according to the transfer command.

  FIG. 2 shows a Session Initiation Protocol (SIP) push service in the prior art. The SIP push service is a push OTA on the SIP service defined by the Open Mobile Alliance (OMA). In this service, the push OTA content is encapsulated in a SIP message, and an existing SIP / IP core network is created. Transferred through. SIP is an application layer protocol for setting up multimedia sessions between two or more participants. The PPG and the client serve as interface points for the SIP / IP core network. In the SIP push process, SIP can provide the following functions: User reachability, user availability, user capabilities, session setup, and session management. User reachability, user availability, user capabilities, user capabilities, session setup, and session management.

  The SIP / IP core network provides rich end-to-end media sessions and sessions between clients and servers. The SIP / IP core network includes a SIP gateway and a registration server, provides service authentication and authorization to SIP clients, and provides SIP registration and routing functions. PPG and push client are the interface points to the SIP / IP core in function.

  The SIP-based event notification reservation mechanism, or SIP event framework, defines the permission for notification of asynchronous events in the notification reservation process. After initial registration, the push client must send a SUBSCRIBE request to the PPG. If the push client needs to make a push event notification reservation for a specific push service, eg, transfer of client capability information or a specific event notification reservation, the PPG and the push client will use the SUBSCRIBE method and NOTIFY It is expected to support methods. In particular, the push client must support the SUBSCRIBE function for specific push content and must support the reception of push content. The PPG must support the NOTIFY function, a SUBSCRIBE request is received from the push client and the push information is sent to the client via the PPG.

  The user ID is a public user identity. One or more public user identities are assigned to one user to use the network. When a user requests to communicate with another user, he uses the public user identity. A single user may have various appearances. Each appearance includes a different public user identity. The format of the public user identity is a hierarchical SIP uniform resource identifier (URI). The SIP URI may be configured via a telephone number or a host name (SIP: user@company.com, etc.). A SIP URI is similar to an email address and is therefore easily associated with a user's email address.

  However, if the user has many terminals, such as a computer, 2G terminal, or 3G terminal, the home network assigns a device ID to each terminal. The device ID controls the uniqueness of each terminal within the network. For example, the device ID is used for authentication, authorization, and management.

  The push client may send a SUBSCRIBE request to update the notification reservation and to declare available applications and versions via the “appid” parameter.

When the push client makes a notification reservation for only one application (for example, “app1” which is a multimedia message service (MMS)), the SUBSCRIBE request is as follows.
SUBSCRIBE sip: user-aor @ example. com SIP / 2.0
Event: ua-profile; profile-type = oma-app; appid = “+ g.oma.iari.Push.mms.ua”;

When the push client makes notification reservations for a plurality of applications (for example, app1, app2, app3), the SUBSCRIBE request is as follows.
SUBSCRIBE sip: user-aor @ example. com SIP / 2.0
Event: ua-profile; profile-type = oma-app; appid = “app1, app2, app3”;

If the push client makes a notification subscription for app1, app2, and app3, but the PPG supports only app1 and app2, the NOTIFY message returned by the PPG contains only two parameters, app1 and app2. Indicates that one application service has been successfully scheduled for notification. The SUBSCRIBE request and NOTIFY message are as follows.
SUBSCRIBE sip: user-aor @ example. com SIP / 2.0
Event: ua-profile; profile-type = oma-app; pid = “app1, app2, app3”;
NOTIFY
Event: ua-profile; profile-type = oma-app; appid = “app1, app2”;

  When the user makes an MMS notification reservation, when the PPG receives the MMS for the terminal, the MMS notification is transmitted to the user's terminal. The notification indicates that the user has an incoming MMS message and that the message may be retrieved from the PPG by the user. The user may configure the terminal to automatically retrieve and store the MMS message on the terminal, or retrieve the message at a convenient time after receiving the MMS notification.

  In the SIP push service, the same user may currently have a plurality of terminals. For example, a user has a 2G mobile phone, a 3G mobile phone, a desktop computer, and a notebook computer at the same time. The PPG stores a public user identity to identify the user. The PPG also stores the device address of the terminal to identify the terminal in order to send a call or message for each device. The PPG also stores information regarding a specific service for which each terminal has made a notification reservation. When any service arrives that is reserved for notification by a plurality of terminals, all the terminals may receive the service. Services that can respond to notification reservations include MMS, Short Message Service (SMS), email notification, and device management. When the PPG transmits an MMS message to a user via the SIP / IP core network, there is a scenario in which each user terminal that has made an MMS notification reservation receives the notification of the MMS message.

  FIG. 3 is a flowchart of MMS communication when a user has a plurality of terminals in the prior art. If the user has a first terminal, a second terminal, and a third terminal at the same time, the multimedia message service center (MMSC) is a PI and the PPG is a PPG. The flow includes the following steps.

  Step S301: The MMSC has an MMS notification message for the user, and transmits the MMS notification to the PPG. After receiving the MMS notification, the PPG finds that the user has three terminals and therefore forwards the notification to each of the three terminals.

  Step S302: The user sets automatic retrieval of the notified MMS message, so that each of the three terminals sends a hypertext transfer protocol (HTTP) GET message to the MMSC PPG to request retrieval of the MMS message. To do.

  Step S303: After receiving the GET message from the first terminal, the PPG transmits an HTTP 200 OK response carrying the MMS message to the first terminal.

  Step S304: The MMSC PPG deletes the MMS message already retrieved by the first terminal, and the second terminal and the third terminal receive the HTTP 4xx error response returned by the MMSC. The MMS notification may be transferred to the three terminals by the SIP / IP core network.

  In the process of realizing the present invention, the inventor has found at least the following disadvantages in the prior art.

  Each terminal of the user receives the same MMS notification, which results in wasted resources and increases network transmission load. In addition, the user must receive the same information repeatedly. Even worse, the MMSC does not recognize the number of terminals currently held by the user. After the MMSC sends the notification, the PPG or SIP / IP core network forwards the notification to each user terminal. If the user sets automatic retrieval of the MMS message from the PPG, only one terminal can successfully retrieve the MMS message. The remaining terminals either fail to retrieve the message or the MMSC informs the user that the message does not exist or has already been retrieved. Therefore, the user experience gets worse.

  In order to overcome the drawbacks in the prior art, the PPG sends service messages to all terminals with the same user ID, thus wasting resources, increasing network transmission load and worsening user experience. In this embodiment, a method, system, and apparatus for processing a service message using multiple terminals of a user are provided.

  To achieve the foregoing objective, in one embodiment of the present invention, a method for processing service messages using multiple terminals of one user is provided. The method includes receiving a request message carrying request information of the terminal from the terminal and transmitting a service message to the terminal according to the request information.

  Furthermore, in one embodiment of the present invention, a system is provided for processing service messages using multiple terminals of one user. The system includes a PPG and at least two terminals having the same user ID. The terminal is configured to send a request message carrying the request information of the terminal to the PPG. The PPG is configured to receive a request message from the terminal and send a service message to the terminal according to the request information.

Still further, in one embodiment of the present invention, a PPG is provided. PPG is
A request receiving module configured to receive a request message carrying terminal request information from the terminal;
And a processing module configured to send a service message to the terminal according to the request information when the service arrives.

  Compared with the prior art, the technical solution according to the present invention has the following advantages.

  The PPG does not send a service message to all terminals, but needs to send only the corresponding service message to a specific terminal according to the request information sent by the terminal. Therefore, it is not necessary for a plurality of terminals of the same user to receive the same service message repeatedly, and resource waste is avoided.

It is the schematic of the push service in a prior art. It is the schematic of the SIP push service in a prior art. It is a flowchart in MMS communication in case a user has a some terminal in a prior art. It is a flowchart which transmits the service notification reservation request in one Embodiment of this invention. FIG. 4 shows a schematic diagram of a SUBSCRIBE request sent by a user in an embodiment of the present invention. FIG. 6 shows a schematic diagram of a 200 OK message in an embodiment of the present invention. FIG. 6 shows a schematic diagram of a service notification reservation activation instruction in an embodiment of the present invention. FIG. 6 shows a schematic diagram of a request of a second terminal in an embodiment of the present invention. 6 is a flowchart of optional steps in an embodiment of the invention. 6 is a flowchart for making a notification reservation for only one service using a SUBSCRIBE request in another embodiment of the present invention. FIG. 6 shows a schematic diagram of a SUBSCRIBE request sent by a user in another embodiment of the present invention. FIG. 6 shows a schematic diagram of activation of an MMS notification subscription in another embodiment of the present invention. FIG. 7 shows a schematic diagram of notification reservation by a second terminal in another embodiment of the present invention. FIG. 6 shows a schematic diagram of activation of a service notification reservation in another embodiment of the present invention. 6 is a flowchart for making a notification reservation for a plurality of services using a SUBSCRIBE request in another embodiment of the present invention. FIG. 6 shows a schematic diagram of a SUBSCRIBE request sent to a PPG by a first terminal in another embodiment of the present invention. FIG. 4 shows a schematic diagram of activation instructions in another embodiment of the present invention. FIG. 7 shows a schematic diagram of notification reservation by a second terminal in another embodiment of the present invention. FIG. 6 shows a schematic diagram of activation of a service notification reservation by a second terminal in another embodiment of the present invention. 6 is a flowchart illustrating a method for a PPG to select a higher priority device to receive a service in another embodiment of the present invention. FIG. 6 shows a schematic diagram of a SUBSCRIBE request sent by a user in another embodiment of the present invention. FIG. 6 shows a schematic diagram of a 200 OK message in another embodiment of the present invention. FIG. 6 shows a schematic diagram of activation of a service notification reservation in another embodiment of the present invention. 6 is a flowchart for transmitting a service request to a PPG via HTTP in another embodiment of the present invention. 6 shows a configuration of a system for processing a service message using a plurality of terminals of one user according to another embodiment of the present invention.

  Embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

  Embodiments of the present invention handle a method for receiving the same message using multiple terminals in a push mechanism. Several solutions are proposed here, in the notification reservation process, where a SIP push requires that only one terminal be able to make a notification reservation for a particular service, or The solution is that priorities for specific services need to be set in the notification reservation. In this way, when the PPG has a specific service message to be transmitted to a user having multiple terminals, a terminal with the corresponding device ID is selected to receive the service message instead of all terminals. Therefore, waste of network resources is avoided, multiple terminals of one user do not need to receive the same message repeatedly, and reception of other services is affected by the repeated reception of the same message There is nothing. Depending on the specific service, the implementation is classified into the following modes:

  1. In the notification reservation process, only one terminal among all the terminals of one user is allowed to make a service notification reservation. That is, if the current terminal has already made a notification notification for a service, and if another terminal of that user requests to make a notification reservation for the same service, the service cannot be used because the service has already been reserved for notification. The PPG notifies the terminal.

  2. After the first terminal has successfully reserved for service notification, a notification indicating that the service has already been reserved for notification is transmitted to the other terminals. In this way, repeated notification reservations are avoided and the service is reserved for notification by only one terminal.

  3. All terminals are allowed to make service notification subscriptions. In the notification reservation process, the priority of the terminal is set. The priority policy is stored on the PPG, which controls message delivery. Therefore, when this service arrives, only one terminal receives the service message first, and no other terminal receives the service message at the same time.

  4). All terminals are allowed to make service notification subscriptions. The PPG sets the priority of the terminal. Depending on the network status, the PPG selects a terminal for receiving the service message, and other terminals do not receive the service message at the same time.

  User information, terminal information, or service notification reservation information may be sent to the PPG via a REGISTER request and / or a SUBSCRIBE request.

  Taking the SUBSCRIBE request as an example, an embodiment of the present invention in the above-described mode will be described in detail below. A message carrying request information is not limited to a SUBSCRIBE request. Other messages capable of this function are within the protection scope of the present invention.

FIG. 4 is a flowchart for transmitting a service notification reservation request according to an embodiment of the present invention. The first terminal and the second terminal are two different devices of the same user. In this embodiment, only one terminal is allowed to make a service notification subscription. That is, if the current terminal has already made a service notification reservation, and another user's terminal requests to make the same service notification reservation, the service has already been reserved for notification and cannot be used. The PPG notifies the terminal. Different terminals of a user can be an international mobile telephone subscriber identification number (IMSI), a private user ID (identity), a globally routable user agent URI (GRUU), multiple contact information, an IP address, a telephone number, or a device It may be distinguished by a number. The detailed steps are as follows.

  Step S401: In this embodiment, taking the user “john.doe@home1.net” as an example, the first terminal of the user “john.doe@home1.net” transmits a SUBSCRIBE request to the PPG. This request carries the user ID, device ID, and application ID, and is intended to make a notification reservation for the MMS service.

  FIG. 5 shows a SUBSCRIBE request sent by a user in an embodiment of the present invention. First, the PPG identifies the user's user ID, device ID, and application ID. After such an ID is identified as correct, the first terminal sends a request for making an MMS service notification subscription to the PPG. After the request is accepted, the device ID is written into the database. This device ID may distinguish between terminals.

  Step S402: After the SIP SUBSCRIBE request for the “ua_profile” event package is received, the PPG authenticates the identity of the initiator and is allowed for the user to subscribe for service notifications via the current device. Whether or not is determined according to the local rule. If the authentication is successful, the PPG creates a notification reservation session for the “ua_profile” event package, provides a method for identifying data changes according to the “Event” header field parameter, and then the first terminal Returns a 200 OK message to A 200 OK message in this step is shown in FIG.

  Step S403: The PPG generates and transmits an initial SIP NOTIFY message that carries an empty body and indicates that the service notification reservation has been activated. FIG. 7 shows a service notification reservation activation instruction in the embodiment of the present invention. In order to validate the MMS service reserved for notification, the notification reservation for the MMS service needs to be activated in this step.

  Step S404: The push client on the first terminal responds using a 200 OK message.

  When the PPG receives the service request, it submits the push content by adding the push content to the SIP NOTIFY message. The SIP NOTIFY message is transmitted to the terminal that transmitted the service request.

  Step S405: The user's second terminal transmits a request for making a notification reservation for the MMS service. The public user identity of the second terminal is “john.doe@home1.net”, and the device ID of the second terminal is different from the device ID of the first terminal. FIG. 8 shows a request of the second terminal in the embodiment of the present invention. This step is different from step S401 in the apparatus used. That is, the device ID is different. The device ID identifies the device that sends the request.

  Step S406: The PPG confirms that the user's public user identity is also “john.doe@home1.net”, that the service to be notified of notification is also MMS, and that the user has received the MMS service via another device. Find out that you have already booked a notification. Therefore, the PPG returns a 4XX response, indicating that the service is not available because it has already been successfully reserved for notification.

  The user's first terminal has already made a reservation for notification of the MMS service from the PPG. Accordingly, the PPG determines that the user has already reserved for notification of the MMS service, and returns a 4XX response to the user's second terminal.

  The optional steps in this embodiment are as follows. After the first terminal successfully subscribes for service notification, the PPG sends a NOTIFY message to all registered terminals, the service has already been successfully subscribed for notification, and further notification reservations Indicates that it is not necessary. Other terminal addresses may be stored in the PPG or SIP / IP core network and may be tied to the user at the time of registration of each terminal. Through such an address, the message may be notified to all terminals of the user.

  FIG. 9 is a flowchart of optional steps in an embodiment of the invention, described in detail below.

  Step S901: The first terminal of the user “john.doe@home1.net” transmits a SUBSCRIBE request to the PPG. This request carries the user ID, device ID, and application ID, and is intended to make a notification reservation for the MMS service.

  Step S902: After the SIP SUBSCRIBE request for the “ua_profile” event package is received, the PPG verifies the identity of the initiator and is allowed for the user to subscribe for service notifications via the current device. Whether or not is determined according to the local rule. If the authentication is successful, the PPG creates a notification reservation session for the “ua_profile” event package, provides a method for identifying data changes according to the “Event” header field parameter, and then the first terminal Returns a 200 OK message to

  Step S903: The PPG generates and transmits an initial SIP NOTIFY message that carries an empty body and indicates that the service notification reservation has been activated.

  Step S904: The push client on the first terminal responds using a 200 OK message.

  Step S905: The PPG transmits a NOTIFY message to other terminals. The header field or body of the NOTIFY message carries information indicating that the MMS service has been successfully notified and reserved by the first terminal and cannot be used by other terminals.

  Step S906: The other terminal returns a 200 OK message to indicate that the request has been accepted.

  In the notification reservation process of this embodiment, the SIP push mechanism allows only one terminal to make a notification reservation for a particular service. Thus, if the PPG has a specific service message sent to the user, only this authorized terminal can receive the message, not all of the user's devices, thus avoiding waste of network resources. The

Another Embodiment FIG. 10 is a flow chart of command transmission when the SUBSCRIBE request is intended to subscribe for notification of only one service in the embodiment of the present invention. The first terminal and the second terminal shown in this embodiment are two different devices of the same user. When the first terminal sends a request for making a service notification reservation to the PPG, the first terminal is identified by the public user ID and the private user ID, and the request is a priority parameter “Qvalue”. carry. The priority parameter indicates the following: For the service reserved for notification, the PPG sends the service to the terminal with the highest priority, and if the service is successfully sent, the PPG will not send the service to the second terminal Is not successfully transmitted, the PPG transmits the service to the terminal with the next priority, and so on.

  In the service implementation, the terminal submits a priority list to the PPG when sending a SUBSCRIBE request. Therefore, the terminal desired by the user first receives the service message. A higher Qvalue indicates a higher importance of a given location. The range of Qvalue may be 0-1.

  Different terminals of a user may be distinguished by IMSI, private user ID, GRUU, multiple contact information, IP address, telephone number, or device number. This embodiment is implemented via two solutions. When the SUBSCRIBE request is a request for making a notification reservation for only one service (that is, when there is only one application ID), the steps are as follows.

  Step S1001: The first terminal of the user “john.doe@home1.net” transmits a SUBSCRIBE request to the PPG. This request carries a user ID, a device ID, a Qvalue parameter, and an application ID, and is intended to make a notification reservation for the MMS service. The request indicates that the user's first terminal has the highest priority in receiving the MMS service. When a service arrives, the service is first sent to this terminal. FIG. 11 shows a SUBSCRIBE request message sent by a user in an embodiment of the present invention. First, the user is identified, then the MMS service notification is reserved, and finally the priority is set in “CONTACT:”. In this embodiment, the priority set is 0.7 (Contact: <sip: [5555 :: aaa: bbb: ccc: ddd]: 1357; comp = sigcomp>; q = 0.7). Through such priority setting, the service message may be sent to the selected terminal.

  Step S1002: After the SIP SUBSCRIBE request for the “ua_profile” event package in FIG. 10 is received, the PPG authenticates the identity of the initiator, and the user subscribes for service notification via the current device. Is determined according to the local rule. If the authentication is successful, the PPG creates a notification reservation session for the “ua_profile” event package, provides a method for identifying data changes according to the “Event” header field parameter, and then the first terminal Returns a 200 OK message to

  Step S1003: The PPG generates and transmits an initial SIP NOTIFY message that carries an empty body and indicates that the service notification reservation has been activated. The priority information of other terminals may also be notified to the first terminal via the Contact header field. FIG. 12 illustrates activation of MMS notification reservations in an embodiment of the present invention.

  Step S1004: The push client on the first terminal responds using a 200 OK message.

  When the PPG receives the service request, it submits the push content by adding the push content to the SIP NOTIFY message sent to the push client in the notification reservation process.

  Step S1005: Similarly, the second terminal may make an MMS service notification reservation and may send a SUBSCRIBE request to the PPG. This request carries a user ID, a device ID, a Qvalue parameter, and an application ID, and is intended to make a notification reservation for the MMS service. The request indicates that in receiving the MMS service, the user's second terminal has a priority next to the highest priority. When the service arrives, if the first terminal fails to successfully receive the service, the service is transmitted to the second terminal. FIG. 13 shows a notification reservation by the second terminal in an embodiment of the present invention. The priority set in the second terminal is (Contact: <sip: [5555 :: aaa: bbb: ccc: ddd]: 1357; comp = sigcomp>; q = 0.6). In this embodiment, the priority set is 0.6. The priority of the second terminal is lower than the priority of the first terminal. Thus, if the first terminal fails to successfully receive the service message, the second priority terminal is selected to receive the service message.

  Step S1006: After the SIP SUBSCRIBE request for the “ua_profile” event package is received, the PPG authenticates the identity of the initiator and is allowed for the user to subscribe for service notifications via the current device. Whether or not is determined according to the local rule. If the authentication is successful, the PPG creates a notification reservation session for the “ua_profile” event package, provides a method for identifying the data change according to the “Event” header field parameter, and then the second terminal Returns a 200 OK message to

  Step S1007: The PPG generates and sends an initial SIP NOTIFY message that carries an empty body and indicates that the service notification reservation has been activated. FIG. 14 shows activation of service notification reservation in the embodiment of the present invention. In this step, the MMS service reserved for notification is activated. The priority information of other terminals may be notified to the second terminal via the Contact header field.

  Step S1008: The push client on the second terminal responds using a 200 OK message.

Another Embodiment FIG. 15 is a flowchart in the case where a SUBSCRIBE request is intended to subscribe for notification of a plurality of services in the embodiment of the present invention. In this embodiment, a plurality of application IDs are involved, and the user “john.doe@home1.net” is taken as an example here. The detailed steps are as follows.

  Step S1501: The first terminal of the user “john.doe@home1.net” transmits a SUBSCRIBE request to the PPG. This request carries a user ID, a device ID, a Qvalue parameter, and a plurality of application IDs, and is intended to make a notification reservation for a plurality of services. The request indicates that the user's first terminal has the highest priority in receiving the App1 service. When the App1 service arrives, the App1 service is first transmitted to the first terminal. App2 is the second-priority service of the first terminal, and App3 is the third-priority service of the first terminal. FIG. 16 shows a SUBSCRIBE request sent to the PPG by the first terminal in the embodiment of the present invention. There are three different priority values in the App field, appid = “app1; q = 0.7, app2; q = 0.6, app3; q = 0.5, from high priority to low priority Through the priorities, the PPG may recognize which services are prioritized by the terminal and may send higher priority services to the terminals. After the second degree service is transmitted, the PPG may transmit a lower priority service.

  Step S1502: After the SIP SUBSCRIBE request for the “ua_profile” event package is received, the PPG authenticates the identity of the initiator and is allowed for the user to subscribe for service notifications via the current device. Whether or not is determined according to the local rule. If the authentication is successful, the PPG creates a notification reservation session for the “ua_profile” event package, provides a method for identifying data changes according to the “Event” header field parameter, and then the first terminal Returns a 200 OK message to

  Step S1503: The PPG generates and transmits an initial SIP NOTIFY message that carries an empty body and indicates that the service notification reservation has been activated. FIG. 17 shows activation instructions in the embodiment of the present invention. The message may indicate to the first terminal whether the notification subscription for each service has been activated.

  Step S1504: The push client on the first terminal responds using a 200 OK message. When the PPG receives the service request, it submits the push content by adding the push content to the SIP NOTIFY message sent to the push client in the notification reservation process.

  Step S1505: The second terminal transmits a SUBSCRIBE request to the PPG. This request carries a user ID, a device ID, a Qvalue parameter, and a plurality of application IDs, and is intended to make a notification reservation for a plurality of services. The request indicates that the terminal of the user has the highest priority in receiving the app2 service. When the app2 service arrives, the app2 service is first transmitted to the second terminal. App1 is the second priority service of the second terminal, and App3 is the third priority service of the second terminal. FIG. 18 shows a notification reservation by the second terminal in the embodiment of the present invention. Initially, a user is identified. After the user ID, device ID, and Qvalue parameter are identified as correct, the priority needs to be written into each notification reserved service. In this embodiment, APP2 has the highest priority of 0.7 and the device ID is written last. In this step, the device is a second terminal.

  Step S1506: After the SIP SUBSCRIBE request of the “ua_profile” event package is received, the PPG authenticates the identity of the second terminal and that the user subscribes for notification of service via the current device. Whether it is permitted is determined according to local rules. If the authentication is successful, the PPG creates a notification reservation session for the “ua_profile” event package, provides a method for identifying the data change according to the “Event” header field parameter, and then the second terminal Returns a 200 OK message to

  Step S1507: The PPG generates and transmits an initial SIP NOTIFY message that carries an empty body and indicates that the service notification reservation has been activated. The priority information of other terminals may also be notified to the second terminal via the Contact header field. FIG. 19 shows activation of service notification reservation by the second terminal in the embodiment of the present invention. When it is necessary to notify the second terminal of the priority information of the other terminal, the priority information of the other terminal may be added before the Contact header field.

  Step S1508: The push client on the second terminal responds using a 200 OK message.

  In this embodiment, a priority is set. When a service notification is reserved, if a higher priority terminal fails to receive the service, a lower priority terminal may receive the service instead, and two terminals may receive the same service simultaneously. Impossible. Therefore, a plurality of user terminals do not receive the same message repeatedly, and reception of other services is not affected by the arrival of the same message.

Another Embodiment FIG. 20 is a flowchart illustrating a method by which a PPG selects a higher priority device for receiving services in an embodiment of the present invention. All terminals of the user in this embodiment are allowed to make notification reservations for the same service. The PPG sets the priority of the terminal. Depending on the network status, the PPG selects a terminal for receiving the service message, and other terminals do not receive the service message at the same time. All terminals of a user may use a public user ID to send a request to make a service notification subscription to the PPG, and the request may include a private user ID (which may be a contact address). Carry. The PPG returns a response to indicate to all terminals of the user that the service reserved for notification has been activated. Different terminals of a user may be distinguished by IMSI, private user ID, GRUU, multiple contact information, IP address, telephone number, or device number. The detailed steps are as follows.

  Step S2001: In this embodiment, taking the user “john.doe@home1.net” as an example, the first terminal of the user “john.doe@home1.net” transmits a SUBSCRIBE request to the PPG. This request carries the user ID, device ID, and application ID, and is intended to make a notification reservation for the MMS service. FIG. 21 shows a SUBSCRIBE request message sent by the user in the embodiment of the present invention. Initially, a user is identified. After the user ID is authenticated as correct, the MMS service notification is reserved. Finally, the device ID of the terminal is added to indicate that the terminal has made a service notification reservation.

  Step S2002: After the SIP SUBSCRIBE request for the “ua_profile” event package is received, the PPG verifies the identity of the initiator and is allowed for the user to subscribe for service notifications via the current device. Whether or not is determined according to the local rule. If the authentication is successful, the PPG creates a notification reservation session for the “ua_profile” event package, provides a method for identifying data changes according to the “Event” header field parameter, and then the first terminal Returns a 200 OK message to FIG. 22 shows a 200 OK message in the embodiment of the present invention.

  Step S2003: The PPG generates and sends an initial SIP NOTIFY message that carries an empty body and indicates that the service notification reservation has been activated. FIG. 23 shows activation of service notification reservation in the embodiment of the present invention.

  Step S2004: The push client on the first terminal responds using a 200 OK message. When the PPG receives the service request, it submits the push content by adding the push content to the SIP NOTIFY message sent to the push client in the notification reservation process.

  Steps S2005 to S2008: The second terminal makes a reservation for notification of the MMS service from the PPG. First, the user ID is confirmed, and notification reservation for the MMS service is made, and then the device ID is written. Finally, the MMS service notification subscription is activated.

  Step S2009: When an MMS message to be transmitted to the user arrives, the PPG selects the user's preferred terminal according to the set selection criteria, and transmits a service message to the selected terminal. The preferred terminal is considered the first terminal.

  The PPG automatically determines the priority of the terminal according to the priority of the terminal device. Generally, priority is determined by network quality. The PPG may select a terminal with better network quality so that the user can obtain a better information service. In this embodiment, the first terminal is a preferred terminal, and the user obtains the information service via the first terminal.

  Step S2010: A service message is transmitted to the first terminal via a NOTIFY message.

  Step S2011: The first terminal returns a 200 OK message to indicate that the message has been normally received.

Another Embodiment FIG. 24 shows a flowchart for sending a service request to a PPG via HTTP in an embodiment of the present invention. In order to notify the PPG of the service that the terminal expects to receive, it is assumed that the terminal sends a request to the PPG. In the second solution of the present embodiment, as will be described in detail below, the terminal transmits a service reception priority list set by the terminal to the PPG via HTTP.

  Step S2401: The user sets a list of HTTP Post policies for receiving a service using the first terminal.

  The policy list may be a priority list. This priority list may indicate services that are prioritized by the terminal. In the second solution of the embodiment, an MMS service is taken as an example. That is, the first terminal expects to receive the MMS service first.

  Step S2402: The PPG returns a 200 OK message to indicate that the PPG has received the list of HTTP Post policies from the terminal.

  Step S2403: The user uses the second terminal to set a list of HTTP Post policies for receiving services.

  In this embodiment, similar to the first terminal, the second terminal may indicate that the second terminal expects the second terminal to receive it first.

  Step S2404: A 200 OK message is returned to indicate that the PPG has received the list of HTTP Post policies from the terminal.

  In this embodiment, the priority of the terminal is set, or a list of service reception policies based on HTTP is set. A higher priority terminal is selected to provide the user with a higher priority information service. When the service message is transmitted, other terminals do not receive the service message at the same time. Therefore, service quality is improved and repeated data transmission is avoided. The PPG in this embodiment may be another server capable of this function.

System Embodiment FIG. 25 shows a system configuration for processing a service message using a plurality of terminals of one user in an embodiment of the present invention. This system includes a PPG 1 and at least two terminals 2 having the same user ID. Terminal 2 is configured to send a SUBSCRIBE request to PPG1. The SUBSCRIBE request carries terminal request information. The PPG 1 is configured to receive a SUBSCRIBE request from the terminal 2 and transmit a service message to the terminal 2 according to the request information. The request information includes a user ID, a device ID, and an application ID.

  The PPG 1 and the request receiving module 11 configured to receive a SUBSCRIBE request from the terminal 2 (where the SUBSCRIBE request carries the request information of the terminal 2), and when a service arrives, the terminal 2 according to the request information And a processing module 12 configured to send a service message to the server.

  The processing module 12 is configured to determine whether the service requested by the terminal 2 has already been requested by the terminal having the same user ID according to the user ID and the application ID in the request information. 121, when the determination submodule 121 determines that any terminal with the same user ID has not yet requested a service, the terminal 2 is configured to transmit a service notification reservation activation instruction. It includes a notification reservation instruction transmission sub-module 122 and a service message transmission sub-module 123 configured to transmit a service message to the terminal 2 when a service arrives.

  When the determination submodule 121 determines that a terminal with the same user ID has already requested a service, the processing module 12 returns a prompt response indicating a service notification reserved state to the terminal 2. It further includes a configured prompt response return sub-module 124.

  The processing module 12 further includes a prompt message transmission submodule 125. The prompt message transmission submodule 125 transmits a NOTIFY message to other terminals having the same user ID as the terminal 2 after the notification reservation instruction transmission submodule 123 transmits an instruction for activating the service notification reservation to the terminal 2. Here, the NOTIFY message instructs other terminals not to make service notification reservations thereafter.

  The processing module 12 determines whether it is necessary to send a service message to the terminal 2 according to the service priority reported by the terminal 2, and sends the service message to the terminal 2 as necessary. A priority determination sub-module 126 configured to notify the sub-module 124 is included.

  The processing module 12 includes a network configuration storage submodule 127 and a priority terminal determination submodule 128. The network configuration storage submodule 127 is configured to store a network configuration. The priority terminal determination submodule 128 determines whether the terminal 2 is a priority terminal according to the network configuration stored by the network configuration storage submodule 127 and the device ID of the terminal 2, and the terminal 2 is prioritized. The service message transmission sub-module 124 is notified to transmit a service message to the terminal 2.

  The processing module 12 is configured to receive an HTTP Post policy list from the terminal 2 and a policy list reception sub-module 129 (where the HTTP Post policy list is the priority of the terminal 2 for receiving services). And a policy decision sub-module 130 configured to select the highest priority terminal that receives the service message according to the HTTP Post policy list when a service arrives.

  The user ID may be any identifier that identifies the user, such as a SIP URI or a TEL URI. The SIP URI is sip: a @ example. com or sip: 1234567890@example.com. com.

  The TEL URI may be tel: 1-123-456-7890. For example, the private user ID is username @ example. com.

  The aforementioned embodiments of the present invention provide a solution for sending a message to multiple terminals of a user in a push mechanism. If the user has multiple terminals, the specific terminal for receiving the incoming service is selected according to the terminal request and the terminal request information carried in the request. When the service arrives, the service message is transmitted to the terminal selected according to the request information. Thus, service messages are not sent to all terminals of the user, avoiding wasted network resources, multiple terminals of the user will not receive the same message repeatedly, and other due to the arrival of the same message Service reception is not affected.

  The messages shown herein are for illustrative purposes only. The present invention is not limited to the message methods or message header fields shown, but other message methods and message header fields capable of the functions of the present invention are included in the protection scope of the present invention.

  Through the foregoing description of the embodiments of the present invention, those skilled in the art will clearly recognize that the present invention may be implemented in hardware or by software and the required general purpose hardware platform. Therefore, the technical solution according to the present invention may be implemented as a software product. The software product may be stored on a non-volatile storage medium (such as a CD-ROM, a USB disk, or a mobile hard disk), and the method provided in the embodiments of the present invention is applied to a computer device (personal computer, server, or It may include a number of instructions that allow a network device, etc.) to execute.

  Although the invention has been described through several preferred embodiments, the invention is not limited to such embodiments. It will be apparent to those skilled in the art that modifications and variations can be made to the present invention without departing from the spirit and scope of the invention. The present invention is intended to cover those modifications and variations provided they fall within the scope of protection defined by the claims or their equivalents.

Claims (26)

A method of processing service messages using multiple terminals,
Receiving a request message carrying request information of the terminal from the terminal;
Sending a service message to the terminal according to the request information.   The method of claim 1, wherein the request message comprises a SUBSCRIBE request and / or a REGISTER request.   The method of claim 1, wherein the request information includes a user identifier (ID), a device ID, or an application ID, or any combination thereof. Sending the service message to the terminal according to the request information,
Determining whether the service requested by the terminal has already been requested by another terminal of the same user ID according to the user ID and the application ID in the request information;
If any terminal with the same user ID has not yet requested the service, the terminal transmits a service notification reservation activation instruction to the terminal, and transmits the service message to the terminal when the service arrives. The method according to claim 3. 5. If another terminal with the same user ID has already requested the service, further comprising sending a prompt message to the terminal to indicate that the service has already been reserved for notification. The method described in 1. After the activation instruction for service notification reservation is transmitted to the terminal, the method includes:
5. The method of claim 4, further comprising: sending a prompt message to another terminal having the same user ID as the terminal to instruct the other terminal. The request information further includes a priority,
Sending the service message to the terminal according to the request information,
Send service notification reservation activation instruction to the terminal,
The method according to claim 3, comprising determining whether the service message is transmitted to the terminal according to the priority reported by the terminal when a service arrives. The method of claim 7, further comprising: first transmitting the service message to the terminal with the highest service priority. Further comprising transmitting the service message to the terminal with the second highest priority after the service message fails to be transmitted to the terminal with the highest priority. Item 9. The method according to Item 8.   The method of claim 7, wherein the request information carries a plurality of requested services and corresponding priorities. Sending the service message to the terminal according to the request information,
The method includes determining whether the terminal is a preferred terminal according to the device ID and / or network configuration of the terminal, and transmitting the service message only to the preferred terminal. The method described in 1. Prior to sending the service message to the terminal according to the request information, the method comprises:
The method according to claim 11, further comprising: transmitting an instruction to activate a service notification reservation to the terminal.   The method of claim 11, wherein the device ID may be carried in a request uniform resource identifier (URI) and / or message header field to identify the particular terminal. Further comprising sending a policy list by the terminal to a push proxy gateway (PPG), wherein the policy list is a list of priorities of the terminal for receiving services;
Sending the service message to the terminal according to the request information,
The method according to claim 3, comprising: determining whether the service message is transmitted to the terminal according to the user ID, the application ID, and the policy list by the PPG.   The device ID is an international mobile telephone subscriber identification number (IMSI), a private user ID, a globally routable user agent URI (GRUU), a plurality of contact information, an Internet protocol (IP) address, a telephone number, or a device number. The method of claim 3, wherein   The method of claim 1, wherein the request information may be carried in a Contact header field.   The method of claim 1, wherein the request information may be received, processed, and stored by a receiver and used when a service arrives. A system for processing service messages using a plurality of terminals, comprising a push proxy gateway (PPG) and at least two terminals having the same user identifier (ID),
The terminal is configured to send a request message to the PPG, the request message carrying request information of the terminal;
The system, wherein the PPG is configured to receive the request message from the terminal and transmit a service message to the terminal according to the request information.   The system according to claim 18, wherein the request information includes the user ID, device ID, or application ID, or any combination thereof. A request receiving module configured to receive a request message carrying request information of the terminal from the terminal;
A push proxy gateway (PPG) comprising: a processing module configured to send a service message to the terminal according to the request information when a service arrives. The processing module is
Configured to determine whether the service requested by the terminal is already requested by another terminal with the same user identifier (ID) according to the user ID and application ID in the request information; A decision submodule;
A notification configured to send a service notification reservation activation instruction to the terminal when the determination sub-module determines that no terminal of the same user ID has yet requested the service; A reservation instruction transmission submodule;
21. The PPG of claim 20, comprising: a service message transmission submodule configured to transmit the service message to the terminal when the service arrives. The processing module is
When the determination submodule determines that another terminal with the same user ID has already requested the service, it returns a prompt response indicating the service notification reserved state to the terminal. The PPG of claim 21 further comprising a prompt response return submodule configured in The processing module is
A prompt message configured to send a NOTIFY message to other terminals having the same user ID as the terminal after the notification reservation instruction sending submodule sends the activation notice of service notice reservation to the terminal. A transmission sub-module,
The PPG according to claim 21, wherein the NOTIFY message instructs the other terminal not to make a notification notification for the service. The processing module is
A service is performed to determine whether the service message is transmitted to the terminal according to the service priority reported by the terminal, and to transmit the service message to the terminal when the service message is to be transmitted. 21. The PPG of claim 20, comprising a priority determination submodule configured to notify a message transmission submodule. The processing module is
A network configuration storage sub-module configured to store the network configuration;
In accordance with the network configuration stored by the network configuration storage submodule and the device identifier (ID) of the terminal, it is determined whether the terminal is a preferred terminal, and the terminal is the preferred terminal. 21. The PPG of claim 20, comprising: a priority terminal determination submodule configured to notify a service message transmission submodule to transmit the service message to the terminal when determined to be present. The processing module is
A policy list receiving sub-module configured to receive a policy list that is a list of terminal priorities for receiving the service from the terminal;
21. A policy determination sub-module configured to select the terminal with the highest priority for transmitting the service message according to the policy list when the service arrives. PPG.

Images