WO2017103680A1 - Method and apparatus for realizing mtc group message delivery - Google Patents

Abstract

An object of the invention is providing methods and apparatuses for realizing MTC group message delivery. Group data that needs to be used in MTC group message delivery is stored and managed in HSS. The HSS becomes a centralized database for managing group data, and other network éléments (e.g., BM-SC SCS, AS, MME, SMSC or MTC-IWF, etc.) may interact with the HSS so as to retrieve the above information. By using the présent invention, the storage resource occupied on BM-SC will be dramatically reduced; the data access by other network éléments is facilitated; the network architecture is simplifïed; when UEs from the same group corne from différent service providers, the HSS may still manage data of thèse UEs; moreover, MTC group message delivery may be implemented in a network without MBMS deployment.

Description

METHOD AND APPARATUS FOR REALIZING MTC GROUP MESSAGE

DELIVERY

FIELD OF THE INVENTION

[0001] The present invention relates to the field of telecommunication, and in particular to the technology of MTC group message delivery.

BACKGROUND OF THE FNVENTATION

[0002] 3GPP MTC (Machine Type Communication) solution defined the Group Message Delivery. Group message delivery is intended to distribute, by the network providing the capacity of MTC, the same content to the members of a group that are located in a particular geographical area on request of the SCS ( Services Capability Server) /AS (Application Server) . Currently, MTC group message delivery is mainly based on MBMS (Multimedia Broadcast Multicast Service) , and the procedure handling for group message delivery based on MBMS is also indicated by 3 GPP.

[0003] Internet of things (IoT), also known as MTC, is being widely used and developed rapidly. Considering MTC message delivering is almost all group based message delivering, therefore, the management of group members becomes a key challenge.

[0004] In the 3 GPP MBMS architecture, the MBMS user subscription information is maintained in the BM-SC ( Broadcast Multicast - Service Center ) , the user subscription information is refer to which MBMS Services that the subscriber can use.

[0005] However, storing the user subscription information in the BM-SC would cause the following situations:

[0006] 1) Big amount of subscriber data storage at the BM-SC. Especially when more and more devices use the MBMS, and the per subscriber MBMS profile data may expand to contain more information for enhanced service information, policy control information, etc., which would also result in the increase on the size of the subscription data maintained in the BM-SC.

[0007] 2) Data access limitation. Since the MBMS user subscription information is maintained in the BM-SC, and there are no interfaces between other NEs and the BM-SC, it will not be available for other NEs to access when they need such data to offer enhanced or value-added services.

[0008] 3) Increasing network complexity. When multiple BM-SC entities are deployed in the network, each BM-SC should have the capacity of serving any subscriber, that means, each BM-SC could configure and store the subscription data of all users in the network. This will require the subscription data configuration system of the service provider must contain interfaces with multiple BM-SC entities, which interfaces are used to configure subscription data, and provide corresponding mechanism to ensure the user data consistency among these BM-SC entities. This will increase the network complexity and make more requires to the service provider's system. [0009] 4) Currently, BM-SC only serves a single service provider and only manage user data of the service provider. Therefore, only when group members belong to the same service provider, the data are stored at BM-SC.

[0010] Besides the MBMS user subscription information, the information that is needed in MTC group message delivery may also contain other group information (e.g. basic information of group members and the like); however, in the existing standard, many issues will be brought when saving and managing such information in BM-SC. Therefore, in order to better realize group message delivery in the MTC network, a more efficient technology for managing information related to MTC group message delivery is needed.

SUMMARY OF THE INVENTION

[0011] An object of the invention is providing methods and apparatuses for realizing MTC group message delivery.

[0012] According to one aspect of the invention, a method for realizing MTC group message delivery in an HSS is provided, wherein the HSS is responsible for storing and managing group data that needs to be used in the MTC group message delivery, the method comprising steps of: receiving a subscriber information request from an MTC-IWF, which including an SCS identification and a group identification, the SCS requests for transmitting a message to the group; transmitting a subscriber information request answer to the MTC-IWF, which including group data corresponding to the group.

[0013] Preferably, the subscriber information request further includes indication information about only requesting for information of a master UE of the group, the subscriber information request answer only includes information of the master UE of the group, without including information of other group members of the group.

[0014] Preferably, the group data at least comprises: - user subscription information;

- group attributes and relevant data of each group; - information of each member in the group.

[0015] According to the second aspect of the invention, a method for realizing MTC group message delivery in an MTC-IWF is provided, the method comprising steps of: receiving a request message from an SCS, which including a group identification, the SCS requests for transmitting a message to members of the group; transmitting a subscriber information request to an HSS, which including an identification of the SCS and the group identification; receiving a subscriber information request answer from the HSS, which including group data corresponding to the group; transmitting a message to group members of the group; wherein the HSS is responsible for storing and managing group data that needs to be used in the MTC group message delivery.

[0016] Preferably, the subscriber information request further includes indication information about only requesting for information of a master UE of the group, the subscriber information request answer only includes information of the master UE of the group, without including information of other group members of the group, the step of transmitting a message to group members of the group further comprises: only transmitting a message to the master UE of the group.

[0017] Preferably, the group data at least comprises: - user subscription information;

- group attributes and relevant data of each group; - information of each member in the group.

[0018] According to the third aspect of the invention, a method for realizing MTC group message delivery in an HSS is provided, wherein the HSS is responsible for storing and managing group data that needs to be used in the MTC group message delivery, the method comprising steps of: receiving a subscriber information request from a BM-SC, which including an identification of a UE and at least one MBMS service, the UE requests for registration to the at least one MBMS service; determining, based on locally stored group data, whether the UE has rights to register to the at least one MBMS service; transmitting a subscriber information request answer to the BM-SC, which including a result of determining whether the UE has rights to register to the at least one MBMS service, and further including corresponding group data of the UE in each MBMS service registered under authorization.

[0019] Preferably, the group data at least comprises: - user subscription information;

- group attributes and relevant data of each group; - information of each member in the group.

[0020] According to the fourth aspect of the invention, a method for realizing MTC group message delivery in a BM-SC is provided, the method comprising steps of: responding to a registration request from a UE, transmitting a subscriber information request to an HSS, the subscriber information request includes an identification of the UE and at least one MBMS service, the UE requests for registration to the at least one MBMS service; receiving a subscriber information request answer from the HSS, which including a result of determining whether the UE has rights to register to the at least one MBMS service, and further including corresponding group data of the UE in each MBMS service registered under authorization; wherein the HSS is responsible for storing and managing group data that needs to be used in the MTC group message delivery.

[0021] Preferably, the group data at least comprises: - user subscription information;

- group attributes and relevant data of each group; - information of each member in the group.

[0022] Preferably, the method further comprising steps of: generating, for the UE, an MSK and an MTK corresponding to the MBMS service based on the corresponding group data of the UE in each MBMS service registered under authorization; transmitting the MSK and the MTK to the UE; wherein the MSK and the MTK are used for encryption processing to group message transmitted to a corresponding group.

[0023] According to the fifth aspect of the invention, an apparatus for realizing MTC group message delivery in an HSS is provided, wherein the HSS is responsible for storing and managing group data that needs to be used in the MTC group message delivery, the apparatus comprising: a first receiving module configured to receive a subscriber information request from an MTC-IWF, which including an SCS identification and a group identification, the SCS requests for transmitting a message to the group; a first transmitting module configured to transmit a subscriber information request answer to the MTC-IWF, which including group data corresponding to the group.

[0024] According to the sixth aspect of the invention, an apparatus for realizing MTC group message delivery in an MTC-IWF is provided, the apparatus comprising: a second receiving module configured to receive a request message from an SCS, which including a group identification, the SCS requests for transmitting a message to members of the group; a second transmitting module configured to transmit a subscriber information request to an HSS, which including an identification of the SCS and the group identification; a third receiving module configured to receive a subscriber information request answer from the HSS, which including group data corresponding to the group; a third transmitting module configured to transmit a message to group members of the group; wherein the HSS is responsible for storing and managing group data that needs to be used in the MTC group message delivery.

[0025] According to the seventh aspect of the invention, an apparatus for realizing MTC group message delivery in an HSS is provided, wherein the HSS is responsible for storing and managing group data that needs to be used in the MTC group message delivery, the apparatus comprising: a fourth receiving module configured to receive a subscriber information request from a BM-SC, which including an identification of a UE and at least one MBMS service, the UE requests for registration to the at least one MBMS service; a determining module configured to determine, based on locally stored group data, whether the UE has rights to register to the at least one MBMS service; a fourth transmitting module configured to transmit a subscriber information request answer to the BM-SC, which including a result of determining whether the UE has rights to register to the at least one MBMS service, and further including corresponding group data of the UE in each MBMS service registered under authorization.

[0026] According to the eighth aspect of the invention, an apparatus for realizing MTC group message delivery in a BM-SC is provided, the apparatus comprising: a fifth transmitting module configured to respond to a registration request from a UE, transmitting a subscriber information request to an HSS, the subscriber information request includes an identification of the UE and at least one MBMS service, the UE requests for registration to the at least one MBMS service; a fifth receiving module configured to receive a subscriber information request answer from the HSS, which including a result of determining whether the UE has rights to register to the at least one MBMS service, and further including corresponding group data of the UE in each MBMS service registered under authorization; wherein the HSS is responsible for storing and managing group data that needs to be used in the MTC group message delivery.

[0027] Compared with the existing MTC group message delivery technology, the present invention proposes storing and managing group data that needs to be used in MTC group message delivery in HSS (not in BM-SC). Compared with the prior art, the present invention has the following advantages: [0028] 1) Storing group data centralized on the HSS, such that the BM-SC only needs to store temporary data of the served user for a short time, which will dramatically reduce the storage resource occupied on BM-SC.

[0029] 2) HSS has interfaces with most network elements for facilitating other network elements to access data.

[0030] 3) Storing group data centralized on the HSS; therefore, HSS will uniformly provide data configuration interfaces, which facilitates configuration of user data configuration system of a service provider, thereby simplifying network architecture.

[0031] 4) HSS may provide user data storage for multiple service providers; when the UE from the same group come from different service providers, the HSS may still manage data of these UEs.

[0032] 5) MTC group message delivery may be implemented in a network without MBMS deployment.

[0033] 6) HSS may associate the group data with other user data stored in the HSS (e.g., location information, QoS information, subscriber services information, etc.) so as to provide data basis for more value-added services.

BRIEF DESCRIPTION OF THE DRAWINGS [0034] Other features, purposes and advantages of the invention will become more explicit by means of reading the detailed statement of the non-restrictive embodiments made with reference to the accompanying drawings.

[0035] Fig. 1 shows a schematic diagram of a procedure for realizing MTC group message delivery according to one embodiment of the present invention;

[0036] Fig. 2 shows a schematic diagram of a procedure for realizing MTC group message delivery according to one embodiment of the present invention;

[0037] Fig. 3 shows a schematic diagram of an apparatus for realizing MTC group message delivery in HSS according to one embodiment of the present invention;

[0038] Fig. 4 shows a schematic diagram of an apparatus for realizing MTC group message delivery in MTC-IWF according to one embodiment of the present invention;

[0039] Fig. 5 shows a schematic diagram of an apparatus for realizing MTC group message delivery in HSS according to another embodiment of the present invention;

[0040] Fig. 6 shows a schematic diagram of an apparatus for realizing MTC group message delivery in BM-SC according to one embodiment of the present invention;

[0041] The same or similar reference signs in the drawings represent the same or similar component parts.

DETAILED DESCRIPTION OF THE INVENTION

[0042] First, a plurality of English abbreviations appearing in this disclosure will be explained:

[0043] AS : Application Server

[0044] D2D: Device to Device [0045] HSS : Home Subscriber Server

[0046] MME: Mobility Management Entity

[0047] MSC: Mobile Switching Center

[0048] MTC-IWF: Machine Type Communications-Inter Working Function

[0049] SCS: Services Capability Serve

[0050] SGSN: Serving GPRS Support Node

[0051 ] SMS-SC : Short Message Service- Service Centre

[0052] In order to solve the above problems in the prior art, the present invention proposes storing and managing group data that needs to be used in MTC group message delivery in HSS. During MTC group message delivery of the present invention , HSS becomes a centralized database for managing group data. Other network elements (e.g., BM-SC, SCS, AS, MME, SMSC or MTC-IWF, and the like) may interact with the HSS to retrieve the above information.

[0053] The group data here at least comprises the following information:

[0054] 1) User subscription information

[0055] Because 3 GPP implements MTC group message delivery by an MBMS architecture, each group in the group message delivery corresponds to one MBMS service. In the present invention, the user subscription information refers to a group-based service authorized to be used that the user subscribes to. One user may have a plurality of group-based services, i.e., one user may belong to one or more groups.

[0056] 2) Group Attributes and Relevant Data of Each Group

[0057] The group attributes here refer to basic information of the group, e.g., which may contain at least one, but not limited to, of the following information:

[0058] - group identification

[0059] - MBMS service corresponding to the group

[0060] - current members of the group

[0061] - maximum number of members of the group, etc.

[0062] - a correspondence relationship between an internal group identification and an external group identification of the group

[0063] - identification of a network element to which a member of the group is currently attached or registered, e.g., the identification of MME or SGSN

[0064] - the policy of group message delivery for the group, e.g., delivery frequency, delivery period of time, etc.

[0065] - whether an SCS allows transmitting a message to the group

[0066] 3) Information of Each Member in the Group

[0067] Such information refers to basic information of each member in the group, features of each member in the group, etc.; for example, it may include at least one, but not limited to, of the following information:

[0068] - identification of the UE;

[0069] - identification of the network element to which the UE is attached or registered; [0070] - whether the UE is a master UE or a slave UE in each group.

[0071] In one group, one or more UEs may become master UEs, while other UEs are slave UEs. In some cases, when the slave UE is in a sleep state or a state that cannot be reached by the radio frequency band; in this case, the master UE may transmit a message to the slave UE via D2D or WiFi. In addition, the answer message or data report may be transmitted to the master UE from the slave UE, such that the master UE could summarize all data; then, the master UE only transmits one message to the server; in this way, the communication traffic of the MTC messages in the network may be reduced.

[0072] - security level of the UE for each group

[0073] Different UEs within the same group may have different security levels. For security level-based group message delivery, the message will be transmitted based on the UE's security level, i.e., transmitting the message to a UE having a corresponding security level.

[0074] Below, details of the invention will be further provided in combination with the accompanying drawings.

[0075] Fig. 1 shows a schematic diagram of a procedure for realizing MTC group message delivery according to one embodiment of the present invention. In the embodiment, the MTC group 1 comprises UE11, UE12,...,UEln. The HSS stores group data that needs to be used in the MTC group message delivery.

[0076] This procedure starts from step S 101.

[0077] In step S101, the SCSI 03 decides to transmit a group message to all members in MTC group 1, which transmits a request message to the MTC-IWF 102, e.g., the device trigger as illustrated in Fig. 1, including the identification of SCSI 03 and the identification of MTC group 1. The device trigger as shown in Fig. 1 is only exemplary, and the present invention is also applicable for other group message delivery requests.

[0078] Next, in step S102, the MTC-IWF102 determines whether the SCS103 has rights to transmit a group message request.

[0079] If the MTC-IWF 102 determines that the SCSI 03 has rights to transmit a group message; then, in step SI 03, the MTC-IWF 102 transmits a subscriber information request to the HSS 101, including the identification of the SCSI 03 and the identification of the MTC group 1, for indicating to the HSS 101 that the SCSI 03 requests transmitting a group message to all members in the MTC group 1. The subscriber information request may be a Subscriber Information Request message. In the existing standard, the interface between the MTC-IWF and the HSS does not contain the above group identification information; therefore, the present invention needs to enhance the interface between the MTC-IWF and the HSS.

[0080] In step SI 04, the HSS 101 retrieves the locally saved group data based on the received subscriber information request, so as to further determine the SCSI 03 has rights to transmit a message to the MTC group 1. [0081] If the HSS101 determines the SCSI 03 has rights to transmit a message to the MTC group 1; then, the HSS101 will retrieve group data corresponding to the MTC group 1, e.g., group basic information of the MTC group 1, basic information of group members of the MTC group 1, etc.

[0082] It should be noted that the step SI 04 is not essential, but optional; after receiving the subscriber information request, the HSS101 may directly retrieve the group data corresponding to the MTC group 1.

[0083] Then, in step S105, the HSS101 transmits a subscriber information request answer to the MTC-IWF102, the answer message including the above group data corresponding to the MTC group 1, which including information of group members of the MTC group 1. The subscriber information request answer may be a Subscriber Information Answer message. In the existing standards, the interface between the MTC-IWF and the HSS does not contain the above information; therefore, the present invention needs to enhance the interface between the MTC-IWF and the HSS.

[0084] After receiving the subscriber information request answer, the MTC-IWF102 may get all group members included in the MTC group 1; then, in step SI 06, a message is transmitted to group members in the MTC group 1 based on the local policy information, etc., i.e., transmitting a message to all group members in the MTC group 1, i.e., triggering the device trigger procedures of respective members in the MTC group 1 in succession. The procedure here and the subsequent procedures belong to prior art, which will not be detailed here. It should be noted that the MTC-IWF 102 transmitting a message to group members in the MTC group 1 needs to go through a plurality of network elements, e.g., MME, MSC, SMS-SC, etc., and the MTC-IWF 102 may transmit a group message to corresponding network elements based on registered or attached network elements of the group members of the group, then, further, these network elements transmit messages to these group members.

[0085] In a still embodiment, the subscriber information request in the step SI 03 further comprises a piece of indication information, the indication information indicating that the MTC-IWF 102 only requests for information of the master UE in the MTC group 1. Correspondingly, the subscriber information request answer in step SI 05 only includes information of the master UE in the MTC group 1, without including the information of other group members in the MTC group 1. Correspondingly, in step SI 06, the MTC-IWF 102 only transmits a message to the master UE in the MTC group 1 , and the master UE in the MTC group 1 forwards the massage to other group members in the MTC group 1.

[0086] It may be seen that with the technology of the present invention, delivery of MTC group messages is implemented in a network without MBMS deployment.

[0087] Fig. 2 shows a schematic diagram of a procedure for realizing MTC group message delivery according to one embodiment of the present invention. The embodiment is located in a network deployed with MBMS. The HSS203 stores group data that needs to be used in the MTC group message delivery. Correspondingly, the BM-SC202 does not store the user subscription data and other group data related to the MTC group message delivery.

[0088] This procedure starts from step S201. [0089] In step S201, the UE201 transmits a registration request to the BM-SC202, including at least one MBMS service; the UE201 requests for registering to the at least one MBMS service. In the registration request message, a list of MBMS services may be contained, the list of services lists the above one or more MBMS services which the UE201 requests for registration.

[0090] Because the BM-SC202 locally does not have a user subscription data and other group data related to the MTC group message delivery, it will request for the above information to the HSS203.

[0091] Then, in step S202, the BM-SC202 transmits a subscriber information request to the HSS203, including the identification of the UE201 and the at least one MBMS service. In the existing standard, there is no interface between the BM-SC and the HSS. Therefore, the present invention needs to newly add an interface between the BM-SC and the HSS, e.g., the subscriber information request, and carry the information therein.

[0092] Next, in step S203, the HSS203 determines whether the UE201 has rights to register to the at least one MBMS service based on locally saved group data. For each MBMS service above, the HSS203 may determine based on the user subscription data in the group data. If the UE201 may register to a certain MBMS service, this MBMS service generally corresponds to a group; the HSS203 further retrieves group data of the UE201 in the MBMS service that is registered under authorization, e.g., whether the UE201 is a master UE or a slave UE in the group of the MBMS service registered under authorization, the security level of the UE201 in the group, etc.

[0093] Then, in step S204, the HSS203 transmits a subscriber information request answer to the BM-SC202, including a result of determining whether the UE201 has rights to register to the at least one MBMS service. For each MBMS service above, the subscriber information request answer has a corresponding determination result, i.e., whether the UE201 has rights to register to the MBMS service. For the MBMS service registered under authorization of the UE201, the subscriber information request answer further includes group data corresponding to the UE201 in the MBMS service registered under authorization. In the existing standard, there is no interface between the BM-SC and the HSS. Therefore, the present invention needs to newly add an interface between the BM-SC and the HSS, e.g., the above subscriber information request answer, and carry the above information therein.

[0094] After receiving the subscriber information request answer above, the BM-SC202 may temporarily save information contained in the subscriber information request answer. What is different from the prior art, the BM-SC202 only saves the group data temporarily. After the user in the group data is cancelled, these data will be removed from the BM-SC202.

[0095] Then, in step S205, the BM-SC202 transmits a registration request answer to the UE201, including the above result of determining whether the UE201 has rights to register to the at least one MBMS service.

[0096] Till now, the registration procedure between the UE201 and the BM-SC202 is completed. Afterwards, the UE201 may use those MBMS services that allow registration, thereby achieving MTC group messages delivery. [0097] In another embodiment, the procedure further comprises a step S206. In step S206, for each MBMS service registered under authorization of the UE201, the BM-SC202 generates an MSK (MBMS Service Key) and an MTK (MBMS Traffic Key) based on the corresponding group data of the UE201 in the MBMS service registered under authorization. The corresponding group data may be features of the UE201 in the group, e.g., security level, master UE or slave UE, etc. For example, the BM-SC202 generates different MSKs and MTKs for UEs with different security levels within one group, while generates different MSKs and MTKs for the master UEs and slave UEs within the same group. In this way, different security measures may be adopted for different UEs. Then, the BM-SC202 will transmit the generated MSK and MTK to the UE201. The MSK and the MTK perform encryption processing to the group message transmitted to the corresponding group. Because the transmitting group messages by the BM-SC202 is broadcast, when the BM-SC202 transmits a group message to the corresponding group where the UE201 is located, encryption processing is performed to the message using the corresponding MSK and MTK; only a UE with the same MSK and MTK can perform decoding after having received the encryption message, thereby achieving an objective of transmitting a message only to a specific UE within the same group.

[0098] Afterwards, the BM-SC202 receives a request from a SCS to request for transmitting a group message to a certain group. The BM-SC202 will process the request from the SCS based on temporarily stored group data and transmits a message to the members of the group. These procedures belong to prior art, which will not be detailed here.

[0099] Fig. 3 shows a schematic diagram of an apparatus for realizing MTC group message delivery in HSS101 according to one embodiment of the present invention. The apparatus 300 comprises a first receiving module 301 and a first transmitting module 302.

[00100] In the embodiment, the HSS101 is responsible for storing and managing group data that needs to be used in the MTC group message delivery.

[00101] Hereinafter, a work procedure of the apparatus 300 will be described in detail with reference to Fig. 1.

[00102] Firstly, the first receiving module 301 receives a subscriber information request from the MTC-IWF102, including the identification of the SCS 103 and the identification of the MTC group 1. HSS101 receives the request and gets that the SCS 103 requests for transmitting a group message to all members in the MTC group 1. The subscriber information request may be a Subscriber Information Request message. In the existing standard, the interface between the MTC-IWF and the HSS does not contain the above group identification information; therefore, the present invention needs to enhance the interface between the MTC-IWF and the HSS.

[00103] Then, the HSS101 retrieves the locally saved group data based on the received subscriber information request, so as to further determine the SCS 103 has rights to transmit a message to the MTC group 1.

[00104] If the HSS 101 determines the SCS 103 has rights to transmit a message to the MTC group 1; then, the HSS 101 will retrieve group data corresponding to the MTC group 1, e.g., group basic information of the MTC group 1, basic information of group members of the MTC group 1, etc.

[00105] It should be noted that the determination of the HSSlOl is not essential, but optional; after receiving the subscriber information request, the HSSlOl may directly retrieve the group data corresponding to the MTC group 1.

[00106] Then, the first transmitting module 302 transmits a subscriber information request answer to the MTC-IWF102, the answer message including the above group data corresponding to the MTC group 1, which including information of group members of the MTC group 1. The subscriber information request answer may be a Subscriber Information Answer message. In the existing standards, the interface between the MTC-IWF and the HSS does not contain the above information; therefore, the present invention needs to enhance the interface between the MTC-IWF and the HSS.

[00107] In a still embodiment, the subscriber information request received by the first receiving module 301 further comprises a piece of indication information, the indication information indicating that the MTC-IWF 102 only requests for the information of the master UE in the MTC group 1. Correspondingly, the subscriber information request answer transmitted by the first transmitting module 302 only contains the information of the master UE in the MTC group 1 , without containing the information of other group members in the MTC group 1.

[00108] Fig. 4 shows a schematic diagram of an apparatus for realizing MTC group message delivery in MTC-IWF 102 according to one embodiment of the present invention. The apparatus 400 comprises a second receiving module 401, a second transmitting module 402, a third receiving module 403 and a third transmitting module 404.

[00109] In the embodiment, the HSSlOl is responsible for storing and managing group data that needs to be used in the MTC group message delivery.

[00110] Hereinafter, a work procedure of the apparatus 400 will be described in detail with reference to Fig. 1.

[00111] Firstly, the second receiving module 401 receives a request message from the SCS103, e.g., the device trigger as illustrated in Fig. 1, including the identification of SCSI 03 and the identification of MTC group 1. The message shows that the SCSI 03 requests for transmitting a group message to all members of the MTC group 1. It should be noted that the device trigger as shown in Fig. 1 is only exemplary, and the present invention is also applicable for other group message delivery requests.

[00112] Then, the MTC-IWF102 determines whether the SCS103 has rights to transmit a group message request. If the MTC-IWF102 determines that the SCS103 has rights to transmit a group message; then, the second transmitting module 402 transmits a subscriber information request to the HSSlOl, including the identification of the SCSI 03 and the identification of the MTC group 1, for indicating to the HSSlOl that the SCSI 03 requests transmitting a group message to all members in the MTC group 1. The subscriber information request may be a Subscriber Information Request message. In the existing standard, the interface between the MTC-IWF and the HSS does not contain the above group identification information; therefore, the present invention needs to enhance the interface between the MTC-IWF and the HSS.

[00113] Then, the third receiving module 403 receives a subscriber information request answer from the HSS 101, the answer message including group data corresponding to the MTC group 1 , which including information of group members of the MTC group 1. The subscriber information request answer may be a Subscriber Information Answer message. In the existing standards, the interface between the MTC-IWF and the HSS does not contain the above information; therefore, the present invention needs to enhance the interface between the MTC-IWF and the HSS.

[00114] After receiving the subscriber information request answer, the MTC-IWF 102 may get all group members included in the MTC group 1; then, the third transmitting module 404 may transmits a message to group members in the MTC group 1 based on the local policy information, etc., i.e., transmitting a message to all group members in the MTC group 1, i.e., triggering the device trigger procedures of respective members in the MTC group 1 in succession. The procedure here and the subsequent procedures belong to prior art, which will not be detailed here. It should be noted that the MTC-IWF 102 transmitting a message to group members in the MTC group 1 needs to go through a plurality of network elements, e.g., MME, MSC, SMS-SC, etc., and the MTC-IWF 102 may transmit a group message to corresponding network elements based on registered or attached network elements of the group members of the group, then, further, these network elements transmit messages to these group members.

[00115] In a still embodiment, the subscriber information request transmitted by the second transmitting module 402 further comprises a piece of indication information, the indication information indicating that the MTC-IWF 102 only requests for the information of the master UE in the MTC group 1. Correspondingly, the subscriber information request answer received by the third receiving module 403 only contains the information of the master UE in the MTC group 1, without containing the information of other group members in the MTC group 1. Correspondingly, the third transmitting module 404 only transmits a message to the master UE in the MTC group 1, and the master UE in the MTC group 1 forwards the massage to other group members in the MTC group 1.

[00116] Fig. 5 shows a schematic diagram of an apparatus for realizing MTC group message delivery in HSS203 according to another embodiment of the present invention. The apparatus 500 comprises a fourth receiving module 501, a determining module 502 and a fourth transmitting module 503.

[00117] In the embodiment, the HSS203 is responsible for storing and managing group data that needs to be used in the MTC group message delivery.

[00118] Hereinafter, a work procedure of the apparatus 500 will be described in detail with reference to Fig. 2.

[00119] Firstly, the fourth receiving module 501 receives a subscriber information request from the BM-SC202, including the identification of the UE201 and the at least one MBMS service; the UE201 requests for registering to the at least one MBMS service. In the existing standard, there is no interface between the BM-SC and the HSS. Therefore, the present invention needs to newly add an interface between the BM-SC and the HSS, e.g., the subscriber information request, and carry the information therein.

[00120] Next, the determining module 502 determines whether the UE201 has rights to register to the at least one MBMS service based on locally saved group data. For each MBMS service above, the HSS203 may determine based on the user subscription data in the group data. If the UE201 may register to a certain MBMS service, this MBMS service generally corresponds to a group; the HSS203 further retrieves group data of the UE201 in the MBMS service that is registered under authorization, e.g., whether the UE201 is a master UE or a slave UE in the group of the MBMS service registered under authorization, the security level of the UE201 in the group, etc.

[00121] Then, the fourth transmitting module 503 transmits a subscriber information request answer to the BM-SC202, including a result of determining whether the UE201 has rights to register to the at least one MBMS service. For each MBMS service above, the subscriber information request answer has a corresponding determination result, i.e., whether the UE201 has rights to register to the MBMS service. For the MBMS service registered under authorization of the UE201, the subscriber information request answer further includes group data corresponding to the UE201 in the MBMS service registered under authorization. In the existing standard, there is no interface between the BM-SC and the HSS. Therefore, the present invention needs to newly add an interface between the BM-SC and the HSS, e.g., the above subscriber information request answer, and carry the above information therein.

[00122] Fig. 6 shows a schematic diagram of an apparatus for realizing MTC group message delivery in BM-SC202 according to one embodiment of the present invention. The apparatus 600 comprises a fifth transmitting module 601 and a fifth receiving module 602.

[00123] In the embodiment, the HSS203 is responsible for storing and managing group data that needs to be used in the MTC group message delivery.

[00124] Hereinafter, a work procedure of the apparatus 600 will be described in detail with reference to Fig. 2.

[00125] Firstly, the BM-SC202 receives a registration request from the UE201, including at least one MBMS service; the UE201 requests for registering to the at least one MBMS service. In the registration request message, a list of MBMS services may be contained, the list of services lists the above one or more MBMS services which the UE201 requests for registration.

[00126] Because the BM-SC202 locally does not have a user subscription data and other group data related to the MTC group message delivery, it will request for the above information to the HSS203.

[00127] To correspond to the registration request, the fifth transmitting module 601 transmits a subscriber information request to the HSS203, which including the identification of the UE201 and the at least one MBMS service. In the existing standard, there is no interface between the BM-SC and the HSS. Therefore, the present invention needs to newly add an interface between the BM-SC and the HSS, e.g., the subscriber information request, and carry the information therein.

[00128] Next, the fifth receiving module 602 receives the subscriber information request answer from the HSS203, which including a result of determining whether the UE has rights to register to the at least one MBMS service. For each MBMS service above, the subscriber information request answer has a corresponding determination result, i.e., whether the UE201 has rights to register to the MBMS service. For the MBMS service registered under authorization of the UE201, the subscriber information request answer further includes group data corresponding to the UE201 in the MBMS service registered under authorization. In the existing standard, there is no interface between the BM-SC and the HSS. Therefore, the present invention needs to newly add an interface between the BM-SC and the HSS, e.g., the above subscriber information request answer, and carry the above information therein.

[00129] After receiving the subscriber information request answer above, the BM-SC202 may temporarily save information contained in the subscriber information request answer. What is different from the prior art, the BM-SC202 only saves the group data temporarily. After the user in the group data is cancelled, these data will be removed from the BM-SC202.

[00130] In another embodiment, the apparatus 600 further comprises a key generating module 603(not shown in the Fig.) and a sixth transmitting module 604(not shown in the Fig.).

[00131] For each MBMS service registered under authorization of the UE201, the key generating module 603 generates an MSK ( MBMS Service Key) and an MTK (MBMS Traffic Key) based on the corresponding group data of the UE201 in the MBMS service registered under authorization. The corresponding group data may be features of the UE201 in the group, e.g., security level, master UE or slave UE, etc. For example, the key generating module 603 generates different MSKs and MTKs for UEs with different security levels within one group, while generates different MSKs and MTKs for the master UEs and slave UEs within the same group. In this way, different security measures may be adopted for different UEs. Then, the sixth transmitting module 604 will transmit the generated MSK and MTK to the UE201. The MSK and the MTK perform encryption processing to the group message transmitted to the corresponding group. Because the transmitting group messages by the BM-SC202 is broadcast, when the BM-SC202 transmits a group message to the corresponding group where the UE201 is located, encryption processing is performed to the message using the corresponding MSK and MTK; only a UE with the same MSK and MTK can perform decoding after having received the encryption message, thereby achieving an objective of transmitting a message only to a specific UE within the same group.

[00132] It should be noted that the present invention may be implemented in software and/or a combination of software and hardware, for example, it may be implemented by an application-specific integrated circuit (ASIC), a general purpose computer or any other similar hardware device. In one embodiment, the software program of the present invention may be executed through a processor to implement the steps or functions as mentioned above. Likewise, the software program of the present invention (including relevant data structure) may be stored in the computer-readable recording medium, for example, RAM memory, magnetic or optic driver or flappy disk or similar devices. Besides, some steps or functions of the present invention may be implemented by hardware, for example, as a circuit cooperating with the processor to execute various steps or functions.

[00133] Besides, a part of the present invention may be applied as a computer program product, e.g., computer program instructions, which, when being executed by the computer, may invoke or provide the method and/or technical solution according to the present invention through operations of the computer, while the program instructions for invoking the method of the present invention may be stored in a fixed or mobile recording medium, and/or transmitted through broadcast or a data stream in other signal carrier medium, and/or stored in a work memory of a computer device running based on the program instructions. Here, one embodiment according to the present invention comprises an apparatus, which comprising a memory for storing the computer program instructions and a processor for executing the program instructions, wherein when the computer program instructions are executed by the processor, the apparatus is triggered to run the above mentioned methods and/or technical solutions according to multiple embodiments of the present invention.

[00134] To those skilled in the art, it is apparent that the present invention is not limited to the details of above exemplary embodiments, and the present invention can be implemented with other specific embodiments without departing the spirit or basic features of the present invention. Thus, from any perspective, the embodiments should be regarded as illustrative and non-limiting. The scope of the present invention is limited by the appended claims, instead of the above description. Thus, meanings of equivalent elements falling within the claims and all variations within the scope are intended to be included within the present invention. Any reference numerals in the claims should not be regarded as limiting the involved claims. Besides, it is apparent that such terms as "comprise" and "include" do not exclude other units or steps, and a single form does not exclude a plural form. The multiple units or modules as stated in apparatus claims can also be implemented by a single unit or module through software or hardware. Terms such as first and second are used to represent names, not representing any specific sequence.

Claims

We claim:

1. A method for realizing MTC group message delivery in an HSS, wherein the HSS is responsible for storing and managing group data that needs to be used in the MTC group message delivery, the method comprising steps of:

receiving a subscriber information request from an MTC-IWF, which including an SCS identification and a group identification, the SCS requests for transmitting a message to the group;

transmitting a subscriber information request answer to the MTC-IWF, which including group data corresponding to the group.

2. The method according to claim 1, wherein the subscriber information request further includes indication information about only requesting for information of a master UE of the group, the subscriber information request answer only includes information of the master UE of the group, without including information of other group members of the group.

3. The method according to claim 1 or 2, wherein the group data at least comprises:

- user subscription information;

- group attributes and relevant data of each group;

- information of each member in the group.

4. A method for realizing MTC group message delivery in an MTC-IWF, the method comprising steps of:

receiving a request message from an SCS, which including a group identification, the SCS requests for transmitting a message to members of the group;

transmitting a subscriber information request to an HSS, which including an identification of the SCS and the group identification;

receiving a subscriber information request answer from the HSS, which including group data corresponding to the group;

transmitting a message to group members of the group;

wherein the HSS is responsible for storing and managing group data that needs to be used in the MTC group message delivery.

5. The method according to claim 4, wherein the subscriber information request further includes indication information about only requesting for information of a master UE of the group, the subscriber information request answer only includes information of the master UE of the group, without including information of other group members of the group, the step of transmitting a message to group members of the group further comprises: only transmitting a message to the master UE of the group.

6. The method according to claim 4 or 5, wherein the group data at least comprises:

- user subscription information; - group attributes and relevant data of each group;

- information of each member in the group.

7. A method for realizing MTC group message delivery in an HSS, wherein the HSS is responsible for storing and managing group data that needs to be used in the MTC group message delivery, the method comprising steps of:

receiving a subscriber information request from a BM-SC, which including an identification of a UE and at least one MBMS service, the UE requests for registration to the at least one MBMS service;

determining, based on locally stored group data, whether the UE has rights to register to the at least one MBMS service;

transmitting a subscriber information request answer to the BM-SC, which including a result of determining whether the UE has rights to register to the at least one MBMS service, and further including corresponding group data of the UE in each MBMS service registered under authorization.

8. The method according to claim 7, wherein the group data at least comprises:

- user subscription information;

- group attributes and relevant data of each group;

- information of each member in the group.

9. A method for realizing MTC group message delivery in a BM-SC, the method comprising steps of:

responding to a registration request from a UE, transmitting a subscriber information request to an HSS, the subscriber information request includes an identification of the UE and at least one MBMS service, the UE requests for registration to the at least one MBMS service;

receiving a subscriber information request answer from the HSS, which including a result of determining whether the UE has rights to register to the at least one MBMS service, and further including corresponding group data of the UE in each MBMS service registered under authorization;

wherein the HSS is responsible for storing and managing group data that needs to be used in the MTC group message delivery.

10. The method according to claim 9, wherein the group data at least comprises:

- user subscription information;

- group attributes and relevant data of each group;

- information of each member in the group.

11. The method according to claim 9 or 10, the method further comprising steps of: generating, for the UE, an MSK and an MTK corresponding to the MBMS service based on the corresponding group data of the UE in each MBMS service registered under authorization;

transmitting the MSK and the MTK to the UE; wherein the MSK and the MTK are used for encryption processing to group message transmitted to a corresponding group.

12. An apparatus for realizing MTC group message delivery in an HSS, wherein the HSS is responsible for storing and managing group data that needs to be used in the

MTC group message delivery, the apparatus comprising:

a first receiving module configured to receive a subscriber information request from an MTC-IWF, which including an SCS identification and a group identification, the SCS requests for transmitting a message to the group;

a first transmitting module configured to transmit a subscriber information request answer to the MTC-IWF, which including group data corresponding to the group.

13. An apparatus for realizing MTC group message delivery in an MTC-IWF, the apparatus comprising:

a second receiving module configured to receive a request message from an SCS, which including a group identification, the SCS requests for transmitting a message to members of the group;

a second transmitting module configured to transmit a subscriber information request to an HSS, which including an identification of the SCS and the group identification; a third receiving module configured to receive a subscriber information request answer from the HSS, which including group data corresponding to the group;

a third transmitting module configured to transmit a message to group members of the group;

wherein the HSS is responsible for storing and managing group data that needs to be used in the MTC group message delivery.

14. An apparatus for realizing MTC group message delivery in an HSS, wherein the HSS is responsible for storing and managing group data that needs to be used in the MTC group message delivery, the apparatus comprising:

a fourth receiving module configured to receive a subscriber information request from a BM-SC, which including an identification of a UE and at least one MBMS service, the UE requests for registration to the at least one MBMS service;

a determining module configured to determine, based on locally stored group data, whether the UE has rights to register to the at least one MBMS service;

a fourth transmitting module configured to transmit a subscriber information request answer to the BM-SC, which including a result of determining whether the UE has rights to register to the at least one MBMS service, and further including corresponding group data of the UE in each MBMS service registered under authorization.

15. An apparatus for realizing MTC group message delivery in a BM-SC, the apparatus comprising:

a fifth transmitting module configured to respond to a registration request from a UE, transmitting a subscriber information request to an HSS, the subscriber information request includes an identification of the UE and at least one MBMS service, the UE requests for registration to the at least one MBMS service;

a fifth receiving module configured to receive a subscriber information request answer from the HSS, which including a result of determining whether the UE has rights to register to the at least one MBMS service, and further including corresponding group data of the UE in each MBMS service registered under authorization;

wherein the HSS is responsible for storing and managing group data that needs to be used in the MTC group message delivery.