GROUP MANAGING METHOD AND PUSH SERVER

• US 20130337860A1
• Filed: 08/21/2013
• Published: 12/19/2013
• Est. Priority Date: 02/21/2011
• Status: Active Grant

• Current Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Original Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Inventors: XU, Xiaoying, ZHENG, Xiaoxiao, PANG, Lingli, HUANG, Qufang, ZENG, Qinghai
• Granted Patent: US 9,420,436 B2
• Time in Patent Office: Days
• US Class Current: 455/518
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04W 4/08 User group management

Abstract

The present invention provides a group managing method and a PUSH Server. The method comprises: allocating a first group identifier to a group in an Application Server (AS); acquiring, according to a first identifier of a user joining the group, parameter information of the user, wherein the parameter information of the user comprises a second identifier of the user, location information of a user equipment (UE) corresponding to the user, and an identifier indicating whether the user enables reception of PUSH notification; establishing a group-based transmission bearer with a core network node; and generating group context corresponding to the first group identifier, wherein the group context comprises parameter information of the user in the group and information of the transmission bearer. Therefore, the group management efficiency is improved.

Claims

1. A group managing method, comprising:

allocating, by a PUSH server, a first group identifier to a group of an application server;

acquiring, by the PUSH server, according to a first identifier of a user joining the group, parameter information of the user in a mobile network, wherein the parameter information of the user comprises a second identifier of the user, location information of a user equipment corresponding to the user, and an identifier indicating whether the user enables reception of PUSH notification;

establishing, by the PUSH server, a group-based transmission bearer with a core network node; and

generating, by the PUSH server, a group context corresponding to the first group identifier, wherein the group context comprises the parameter information of the user in the group and information of the group-based transmission bearer.

2. The method according to claim 1, further comprising:

determining, by the PUSH server, a quantity of users joining the group; and

enabling, by the PUSH server, that the reception of the PUSH notification reaches a predetermined threshold.

3. The method according to claim 1, wherein the acquiring, by the PUSH server, according to the first identifier of the user joining the group, the parameter information of the user comprises:

according to the first identifier of the user joining the group, acquiring, by the PUSH server, one of the following (a), (b) and (c);

(a) the parameter information of the user from the core network node, (b) a home subscriber service (HSS), and (c) a home location register (HLR).

4. The method according to claim 1, wherein the establishing, by the PUSH server, the group-based transmission bearer with the core network node comprises:

if the core network node comprises a gateway general packet radio service (GPRS) support node (GGSN) and a service GPRS support node (SGSN), sending, by the PUSH server, indication information to the SGSN through the GGSN, wherein the indication information carries the first identifier of the user and the first group identifier, and the indication information is used to indicate the SGSN to notify the user corresponding to the first identifier to activate the group context;

receiving, by the PUSH server, from the GGSN a first group context activation request, which is sent by the GGSN according to a generated group context activation request received from the SGSN, while the generated group context activation request is sent by the SGSN according to a second group context activation request sent by the user, wherein the first group context activation request sent by the GGSN comprises a first communication port allocated by the GGSN to the group;

allocating, by the PUSH server, a second communication port for communicating with the GGSN to the group; and

establishing, by the PUSH server, a transmission bearer with the GGSN according to the first communication port and the second communication port.

5. The method according to claim 4, further comprising:

establishing, by the PUSH server, a mapping relation between the first group identifier and a second group identifier corresponding to the group of the application server.

6. The method according to claim 5, further comprising:

receiving, by the PUSH server, an update request that carries a first identifier of a user to be updated and the second group identifier, or the update request carries the first identifier of the user to be updated and the first group identifier; and

updating, by the PUSH server, the parameter information of the user to be updated in the group context corresponding to the first group identifier, according to the update request.

7. The method according to claim 6, wherein the receiving, by the PUSH server, the update request comprises:

receiving, by the PUSH server, one of the following (a), (b) and (c);

(a) the update request sent by the application server, the update request sent by the user to be updated, and (c) the update request sent by the GGSN.

8. The method according to claim 5, wherein the first group identifier comprises a public land mobile-communication network (PLMN) identifier and the second group identifier.

9. The method according to claim 1, wherein if the first identifier is a private IP, then the second identifier is a temporary mobile subscriber identity (TMSI), a packet-TMSI (P-TMSI) or an international mobile subscriber identity (IMSI);

or

if the first identifier is the TMSI or the P-TMSI, then the second identifier is the TMSI, the P-TMSI or the IMSI.

10. A PUSH server, comprising:

a first processor, configured to allocate a first group identifier to a group of an application server;

a second processor, configured to acquire, according to a first identifier of a user joining the group, parameter information of the user in a mobile network, wherein the parameter information of the user comprises a second identifier of the user, location information of a user equipment corresponding to the user, and an identifier indicating whether the user enables reception of PUSH notification;

a third processor, configured to establish a group-based transmission bearer with a core network node; and

a forth processor, configured to generate a group context corresponding to the first group identifier, wherein the group context comprises the parameter information of the user in the group and information of the group-based transmission bearer.

11. The PUSH Server according to claim 10, further comprising:

a fifth processor, configured to determine a quantity of users joining the group and enabling the reception of the PUSH notification reaches a predetermined threshold.

12. The PUSH Server according to claim 10, wherein the second processor is specifically configured to acquire, one of the following (a) (b) and (c):

(a) the parameter information of the user from the core network node, (b) a home subscriber service (HSS), and (c) a home location register (HLR), according to the first identifier of the user joining the group.

13. The PUSH Server according to claim 10, further comprising:

a transmitter, configured to send indication information to a gateway general packet radio service (GPRS) support node (GGSN) and a service GPRS support node (SGSN), if the core network node comprises the GGSN and the SGSN, wherein the indication information carries the first identifier of the user and the first group identifier, and the indication information is used to indicate the SGSN to notify the user corresponding to the first identifier to activate the group context; and

a receiver, configured to receive from the GGSN a first group context activation request, which is sent by the GGSN according to a generated group context activation request received from the SGSN, while the generated group context activation request is sent by the SGSN according to a second group context activation request sent by the user, wherein the first group context activation request sent by the GGSN comprises a first communication port allocated by the GGSN to the group;

wherein, the first processor is further configured to allocate to the group a second communication port for communicating with the GGSN; and

the third processor is further configured to establish a transmission bearer with the GGSN according to the first communication port and the second communication port.

14. The PUSH Server according to claim 13, wherein the third processor is further configured to establish a mapping relation between the first group identifier and a second group identifier corresponding to the group of the application server.

15. The PUSH Server according to claim 14, wherein

the receiver is further configured to receive an update request that carries a first identifier of a user to be updated and the second group identifier, or the update request carries the first identifier of the user to be updated and the first group identifier;

and

the PUSH Server is further comprises a sixth processor, configured to update the parameter information of the user to be updated in the group context corresponding to the first group identifier, according to the update request.

16. The PUSH Server according to claim 15, wherein the receiver is further configured to receive one of the following (a), (b) and (c):

(a) the update request sent by the application server, (b) the update request sent by the user to be updated, and (c) the update request sent by the GGSN.

17. The PUSH Server according to claim 14, wherein the first group identifier comprises a public land mobile-communication network (PLMN) identifier and the second group identifier.

18. The PUSH Server according to claim 10, wherein if the first identifier is a private IP, then the second identifier is a temporary mobile subscriber identity (TMSI), a packet-TMSI (P-TMSI) or an international mobile subscriber identity (IMSI);

or

if the first identifier is the TMSI or the P-TMSI, then the second identifier is the TMSI, the P-TMSI or the IMSI.

19. A non-transitory machine-readable medium having stored thereon, a computer program comprising at least one code section for distributing data, the at least one code section being executable by a PUSH Server for causing the PUSH Server to perform the following:

allocating a first group identifier to a group of an application server;

acquiring according to a first identifier of a user joining the group, parameter information of the user in a mobile network, wherein the parameter information of the user comprises a second identifier of the user, location information of a user equipment corresponding to the user, and an identifier indicating whether the user enables reception of PUSH notification;

establishing a group-based transmission bearer with a core network node; and

generating a group context corresponding to the first group identifier, wherein the group context comprises the parameter information of the user in the group and information of the group-based transmission bearer.

20. The non-transitory machine-readable medium according to claim 19, wherein the PUSH Server is further configured to perform of the following:

determining a quantity of users joining the group; and

enabling the reception of the PUSH notification reaches a predetermined threshold.

21. The non-transitory machine-readable medium according to claim 19, wherein the PUSH Server is further configured to perform of the following:

acquiring, one of the following (a), (b) and (c);

(a) the parameter information of the user from the core network node, (b) a home subscriber service (HSS), and (c) a home location register (HLR), according to the first identifier of the user joining the group.

22. The non-transitory machine-readable medium according to claim 19, wherein the PUSH Server is further configured to perform the following:

if the core network node comprises a gateway general packet radio service (GPRS) support node (GGSN) and a service GPRS support node (SGSN), sending indication information to the SGSN through the GGSN, wherein the indication information carries the first identifier of the user and the first group identifier, and the indication information is used to indicate the SGSN to notify the user corresponding to the first identifier to activate the group context;

receiving from the GGSN a first group context activation request, which is sent by the GGSN according to a generated group context activation request received from the SGSN, while the generated group context activation request is sent by the SGSN according to a second group context activation request sent by the user, wherein the first group context activation request sent by the GGSN comprises a first communication port allocated by the GGSN to the group;

allocating a second communication port for communicating with the GGSN to the group; and

establishing a transmission bearer with the GGSN according to the first communication port and the second communication port.