WO2018233719A1

WO2018233719A1 - Group message management method and apparatus, and computer storage medium

Info

Publication number: WO2018233719A1
Application number: PCT/CN2018/092698
Authority: WO
Inventors: 杨坤; 吴昊; 卢忱; 谢芳
Original assignee: 中兴通讯股份有限公司
Priority date: 2017-06-23
Filing date: 2018-06-25
Publication date: 2018-12-27
Also published as: CN109121119A

Abstract

Disclosed in embodiments of the present invention are a group message management method and apparatus, and a computer storage medium. The method comprises: receiving a request message of a group message function; allocating a resource of the group message function according to the request message, and sending, to a network element of a bearer network, request signaling for requesting the use of the group message function; and receiving feedback signaling for the request signaling, which is sent by the network element of the bearer network.

Description

Group message management method, device and computer storage medium

Cross-reference to related applications

The present application is filed on the basis of the Chinese Patent Application No. PCT Application No. PCT Application Serial No.

Technical field

The present invention relates to the field of communications, and in particular, to a method, an apparatus, and a computer storage medium for managing a group message.

Background technique

In the related art Internet of Things Standards Organization (oneM2M) system, a node is an independently identifiable logical entity. The node types included in the oneM2M architecture are: Application Service Node (ASN), Application Dedicated Node (ADN), Intermediate Node (MN), and Infrastructure Node (IN). A node may be a CSE-capable or non-CSE-capable node, where a CSE-capable node is a logical entity, including at least one oneM2M CSE and zero or more oneM2M application entities (AE). , Application Entity). ASN, IN, and MN are all CSE-capable nodes; nodes without CSE capability are a logical entity that does not contain oneM2M CSE and zero or more oneM2M AEs. ADN and nodes that are not oneM2M are nodes that do not have CSE capabilities.

The CSE is different in different nodes. The CSE is based on the services provided by the CSE and the characteristics of the physical entities (eg, different content, firmware) are included in the nodes of the CSE. As a logical object, a node may or may not be mapped to a physical object.

Description of the node type:

1. Application Service Node (ASN):

The ASN acts as a node containing one CSE and at least one AE. There may be zero or more ASNs in a oneM2M system.

The CSE in the ASN communicates with the CSE in the MN or IN through the Mcc reference point; the AE in the ASN communicates with the CSE in the same ASN through the Mca reference point; the ASN communicates with the NSE through the MSN.

Physical mapping example: ASN can exist in an M2M device.

2. Application Specific Node (ADN):

ADN acts as a node that contains at least one AE but does not contain a CSE. There may be zero or more ADNs in a oneM2M system.

The AE in the ADN communicates with the CSE in the MN or IN through the Mca reference point.

Physical mapping example: ADN can exist in a limited M2M device.

3. Intermediate node (MN):

The MN acts as a node containing one CSE and zero or more AEs. There may be zero or more MNs in a oneM2M system.

The CSE in the MN communicates with the CSE in the MN or IN through the Mcc reference point, and also with one or more other CSEs in the MN or ASN; the CSE in the MN passes the Mca reference point with the same MN or ADN The AE communicates; the CSE in the MN communicates with the NSE through the Mcn reference point.

Physical mapping example: The MN can exist in the M2M gateway.

4. Infrastructure node (IN):

IN acts as a node containing one CSE and zero or more AEs. Each oneM2M service provider has an IN. The CSE functionality contained in the CSE in IN may not be applicable to other node types.

The CSE in IN communicates with one or more CSEs in the MN and ASN through the Mcc reference point; the CSE in IN communicates with one or more AEs in the same IN or AND through the Mca reference point; CSE in IN Communicate with the NSE through the Mcn reference point and communicate with the CSE in the IN of other M2M service providers through the Mcc reference point.

Physical mapping example: IN can exist in the M2M service infrastructure.

In the application scenario of the Internet of Things, the number of terminal devices is much larger than that of a conventional mobile phone terminal, and terminals of the same or similar characteristics provided by the same IoT service provider are deployed in one or several fixed areas, for example, in a forest. The forest fire monitoring device of the forest management center is deployed, and, for example, a remote meter reading device of the national grid is deployed in one cell. For these scenarios, such identical or similar devices belonging to the same service provider have great similarities in interaction with the network server. For example, when the software of the device is remotely upgraded, the data sent by the server to each device is the same. of. According to the current process, it is necessary to send data to these devices one by one. A large number of signaling interactions are generated in the entire sending process. For example, between the application and the bearer network, each time a request message is sent, a response message to the request is generated. Further, the interaction between the bearer network and the device also generates a large amount of signaling.

In view of the above problems in the related art, no effective solution has been found yet.

Summary of the invention

The embodiments of the present invention provide a method, a device, and a computer storage medium for managing a group message, so as to at least solve the technical problem of wasting network resources when the IoT node interacts in the related art.

According to an embodiment of the present invention, a method for managing a group message is provided, including: receiving a request message of a group message function; configuring a resource of the group message function according to the request message, and sending the resource to the bearer network element for transmitting Requesting to use the request signaling of the group message function; receiving feedback signaling of the request signaling sent by the bearer network element.

In an embodiment, after receiving the feedback signaling of the request signaling sent by the bearer network element, the method further includes: setting an attribute value corresponding to the resource according to the feedback signaling.

In an embodiment, the request message includes at least one of: an identifier or a group identifier of an AE that receives the group message request, an identifier of the CSE that receives the group message request, or a group identifier.

In an embodiment, the request message is used to request one of the following: a resource for creating a group message function, and a resource for updating a group message function.

In an embodiment, the attribute of the resource comprises a multicast type.

In an embodiment, the request signaling for requesting to use the group message function to the bearer network element includes: when the multicast type is a Multimedia Broadcast Multicast Service (MBMS) group, The network element sends request signaling for requesting the use of the group message function.

In an embodiment, the request signaling includes one of: assigning a Temporary Mobile Group Identity (TMGI) request, a group message request.

In an embodiment, when the request signaling includes allocating a TMGI request, the feedback signaling is an allocation TMGI response message.

In an embodiment, when the request signaling includes a group message request, the feedback signaling is a group message acknowledgement message.

In an embodiment, the allocating TMGI response message includes a TMGI assigned by the core network.

In an embodiment, the group message acknowledgement message includes a port address assigned by the core network.

In an embodiment, the request message further includes: a preset start time of the group message function.

In an embodiment, configuring the resource of the group message function according to the request message comprises: configuring at least one of the following attributes of the resource of the group message function: an external group identifier, and a startup time.

In an embodiment, when the startup time is not configured in the resource of the group message function, a default value corresponding to the startup time is set in the group message request.

In an embodiment, the setting a default value corresponding to the startup time includes: setting the startup time to a next start time of a time cross, wherein the time cross indicates that the group member supports communication through the core network. period.

In an embodiment, after the request signaling includes allocating a TMGI request, after receiving the request message of the group message function, the method further includes: sending the allocated TMGI request to the core network element.

In an embodiment, after the request signaling includes a group message request, after receiving the request message of the group message function, the method further includes: sending the group message request to the core network element.

In an embodiment, the method further includes: receiving a subscription resource creation request message, and creating a subscription sub-resource for the resource of the group message function according to the subscription resource creation request message; The attribute is set to receive the identifier or group identifier of the AE or CSE of the group message request; and set the second attribute of the subscription sub-resource to: the notification trigger condition is one of the following attributes: TMGI, startup time, port address.

In an embodiment, the method further comprises: sending a notification request to the AE or CSE on the terminal or the gateway, wherein the request message includes one of the following attributes of the resource: TMGI, start time, port address.

In an embodiment, the method further includes: sending the group message request to the core network element according to the startup time.

In an embodiment, after receiving the feedback signaling of the request signaling sent by the bearer network element, the method further includes: sending, according to the port address, the group message request to a core network. yuan.

According to another embodiment of the present invention, there is provided a management apparatus for a group message, comprising: a first receiving module configured to receive a request message of a group message function; and a management module configured to receive according to the receiving module The request message configures the resource of the group message function, and sends request signaling for requesting to use the group message function to the bearer network element; the second receiving module is configured to receive the request signaling sent by the bearer network element Feedback signaling.

In an embodiment, the apparatus further includes: a setting module configured to set an attribute value corresponding to the resource according to the feedback signaling.

According to still another embodiment of the present invention, there is further provided a computer storage medium comprising a stored computer program, the computer program being executed by a processor to perform a method of managing a group message according to an embodiment of the present invention.

According to still another embodiment of the present invention, there is also provided a management apparatus for a group message, comprising: a processor and a memory for storing a computer program executable on a processor, the processor for running the computer program The method for managing the group message according to the embodiment of the present invention is executed.

The technical solution of the embodiment of the present invention, by receiving a request message of a group message function, configuring a resource of the group message function according to the request message, and sending request signaling for requesting to use a group message function to the bearer network element and receiving Feedback signaling. By using the bearer network to manage group messages, the signaling interaction is reduced, and the technical problem of wasting network resources when the IoT nodes interact in the related art is solved.

DRAWINGS

The drawings described herein are intended to provide a further understanding of the invention, and are intended to be a part of the invention. In the drawing:

1 is a flowchart of a method for managing a group message according to an embodiment of the present invention;

2 is a block diagram showing the structure of a group message management apparatus according to an embodiment of the present invention.

Detailed ways

The invention will be described in detail below with reference to the drawings in conjunction with the embodiments. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.

It is to be understood that the terms "first", "second", and the like in the specification and claims of the present invention are used to distinguish similar objects, and are not necessarily used to describe a particular order or order.

Example 1

In this embodiment, a method for managing a group message is provided. FIG. 1 is a flowchart of a method for managing a group message according to an embodiment of the present invention. As shown in FIG. 1, the process includes the following steps:

Step S102, receiving a request message of a group message (Group Message) function;

Step S104: Configure a resource of the group message function according to the request message, and send, to the bearer network (Underlying Network) network element, request signaling for requesting to use the group message function;

Step S106: Receive feedback signaling of request signaling sent by the network element of the bearer network.

Through the above steps, the request message of the group message function is received; the resource of the group message function is configured according to the request message, and the request signaling for requesting to use the group message function is sent to the bearer network element and the feedback signaling is received. By using the bearer network to manage group messages, the signaling interaction is reduced, and the technical problem of wasting network resources when the IoT nodes interact in the related art is solved.

In an embodiment, the execution body of the above steps may be IN-CSE or the like, but is not limited thereto.

In an embodiment, after receiving the feedback signaling of the request signaling sent by the network element of the bearer network, the method further includes: setting an attribute value corresponding to the resource according to the feedback signaling.

In an embodiment, the request message includes at least one of: an identifier or a group identifier of the AE receiving the group message request, an identifier of the CSE receiving the group message request, or a group identifier.

In an embodiment, the request message is used to request one of the following: a resource that creates a group message function, and a resource that updates the group message function.

Specifically, the attribute of the resource contains the multicast type.

In this embodiment, sending the request signaling for requesting to use the group message function to the bearer network element includes: sending a request message for requesting to use the group message function to the bearer network element when the multicast type is the MBMS group make.

In an embodiment, the request signaling includes one of: assigning a TMGI request, a group message request.

In an embodiment, when the request signaling includes allocating a TMGI request, the feedback signaling is a TMGI response message.

In an embodiment, the assigned TMGI response message includes a TMGI assigned by the core network.

In an embodiment, the request message further includes: a start time of the preset group message function.

In an embodiment, configuring the resource of the group message function according to the request message includes: configuring at least one of the following attributes of the resource of the group message function: an external group identifier, a startup time.

In an alternative embodiment, when the startup time is not configured in the resource of the group message function, a default value corresponding to the startup time is set in the group message request.

Here, the setting a default value corresponding to the startup time includes: setting the startup time to a next start time of a time cross, wherein the time cross indicates a time period in which a group member supports communication through a core network.

Specifically, the default value indicates that the start time shall be set to the next start time of the time intersection; the time cross indicates the time when the member node can communicate through the underlying network. The time intersection indicate the time periods when the member node can communicate via the Underlying Network.

In an embodiment, after the request signaling includes the allocation of the TMGI request, after receiving the request message of the group message function, the method in this embodiment further includes: sending the allocated TMGI request to the core network element.

In an embodiment, after the request signaling includes the group message request, after receiving the request message of the group message function, the method further includes: sending the group message request to the core network element.

In an embodiment, the method of this embodiment further includes:

S11. Receive a subscription resource creation request message, and create a subscription sub-resource for the resource of the group message function according to the subscription resource creation request message.

S12. Set a first attribute of the sub-subscription resource to an identifier or a group identifier of the AE or CSE that receives the group message request; and set a second attribute of the sub-subscription resource to: the notification trigger condition is one of the following attributes: TMGI, start Time, port address.

In an embodiment, the method further comprises: transmitting a notification request to the AE or CSE on the terminal or the gateway, wherein the request message includes one of the following attributes of the resource: TMGI; start time, port address.

In an embodiment, after receiving the feedback signaling of the request signaling sent by the network element of the bearer network, the method further includes: sending the group message request to the core network element according to the port address.

Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk, The optical disc includes a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present invention.

Example 2

In the embodiment, a group message management device is also provided, which is used to implement the above-mentioned embodiments and preferred embodiments, and has not been described again. As used below, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.

2 is a structural block diagram of a group message management apparatus according to an embodiment of the present invention. As shown in FIG. 2, the apparatus includes:

The first receiving module 20 is configured to receive a request message of a group message function;

The management module 22 is configured to configure a resource of the group message function according to the request message received by the receiving module 20, and send request signaling for requesting to use the group message function to the network element of the bearer network;

The second receiving module 24 is configured to receive feedback signaling of the request signaling sent by the network element.

In an embodiment, the apparatus of this embodiment further includes: a setting module, configured to set an attribute value corresponding to the resource according to the feedback signaling received by the second receiving module 24.

In an embodiment, the attribute of the resource comprises a multicast type.

In an embodiment, the management module 22 is configured to send request signaling for requesting to use the group message function to the bearer network element when the multicast type is an MBMS group.

In an embodiment, the management module 22 is configured to configure at least one of the following attributes of the resources of the group message function: an external group identifier, and a startup time.

In an embodiment, the setting module is further configured to: when the startup time is not configured in the resource of the group message function, set a default value corresponding to the startup time in the group message request.

In an embodiment, the apparatus further includes: a sending module, configured to: after the request signaling includes allocating a TMGI request, after the first receiving module 20 receives the request message of the group message function, The TMGI request is sent to the core network element.

In an embodiment, the apparatus further includes: a sending module, configured to: after the request signaling includes a group message request, after the first receiving module 20 receives the request message of the group message function, the group is The message request is sent to the core network element.

In an embodiment, the apparatus further includes a third receiving module configured to receive a subscription resource creation request message;

The management module 22 is configured to create a subscription sub-resource for the resource of the group message function according to the subscription resource creation request message; set the first attribute of the subscription sub-resource to the AE that receives the group message request or The identifier or group identifier of the CSE; and setting the second attribute of the subscription sub-resource to: the notification trigger condition is one of the following attributes: TMGI; startup time; port address.

In an embodiment, the apparatus further includes: a sending module, configured to send a notification request to the AE or CSE on the terminal or the gateway, wherein the request message includes one of the following attributes of the resource: TMGI, startup time Port address.

In an embodiment, the apparatus further includes: a sending module, configured to send the group message request to the core network element according to the startup time.

In an embodiment, the device further includes: a sending module, configured to: after the second receiving module 24 receives the feedback signaling of the request signaling sent by the bearer network element, according to the port address Sending the group message request to the core network element.

It should be noted that the management apparatus of the group message provided by the foregoing embodiment is only exemplified by the division of each of the foregoing program modules when performing group message management. In actual applications, the foregoing processing may be allocated to different programs according to needs. The module is completed, dividing the internal structure of the device into different program modules to complete all or part of the processing described above. In addition, the management device of the group message provided by the foregoing embodiment is the same as the embodiment of the method for managing the group message, and the specific implementation process is described in detail in the method embodiment, and details are not described herein again.

Example 3

This embodiment considers a bearer network in the related art. For example, a 3GPP network can provide an MBMS service, that is, a multimedia broadcast multicast service, and can transmit data in a broadcast form to a device connected to a 3GPP network without a device feedback message. On this basis, the application establishes a mechanism to use the service provided by the 3GPP network to implement request message transmission for a group of identical or similar devices, thereby reducing signaling overhead and saving network resources.

The solution of the embodiment includes: the IN-CSE may create a resource and an attribute for sending a group message according to the request of the AE or the CSE, and trigger a request to use the group message function to the bearer network, and after the bearer network successfully responds, correspondingly The group message receiving parameters are sent to the AE or CSE on the terminal or gateway.

The implementation steps of this embodiment include:

1. The IN-CSE receives the resource operation request sent by the AE.

2. The IN-CSE creates or updates a resource according to the resource operation request, and sends a signaling requesting to use the group message function to the NSE according to the resource operation request.

3. The IN-CSE receives the response message of the NSE, and sets the attribute of the resource according to the response message.

4. The IN-CSE sends the parameters related to the receiving group message to the AE or CSE on the terminal or gateway.

5. The IN-CSE sends a group message to the AE or CSE on the terminal or gateway through the bearer network element.

This implementation includes the following multiple embodiments:

Embodiment 1 (the startup request is not included in the creation request of the AE, and the IN-CSE directly transmits the reception parameter)

1. The AE sends a create resource request message to the IN-CSE, where the request message includes:

1) Resource type: group message;

2. After receiving the request message, the IN-CSE verifies whether the AE has the right to create the resource of the type;

3. After the verification is passed, IN-CSE creates a group type resource <Group Message>, creates attributes "TMGI" and "start time", and sets the value of the attribute "start time" to the default value.

4. The IN-CSE checks whether the attribute "multicast type" is included in the local area. If the value is "3GPP MBMS group", the Allocate TMGI Request message is sent to the NSE in the core network. The request message includes:

1) the number of TMGI;

The number of TMGIs may be indicated by the AE in the request message, or the IN-CSE is set according to the local policy, and the default value is 1.

5. The IN-CSE receives the Allocate TMGI Response message of the NSE, and the response message includes:

1) TMGI: The value of the TMGI assigned by the core network.

6. The IN-CSE sets the value of the received TMGI to the value of the attribute "TMGI" of the resource <Group Message>.

7. The IN-CSE sends a Group Message Indication message to the ADN/ASN/MN on the terminal or the gateway. The indication message includes:

1) TMGI: the value of the attribute "TMGI";

2) start time: the value of the attribute "start time".

8. The IN-CSE sends a Group Message Request message to the NSE according to the attribute value of the attribute "start time" of the resource <Group Message>, and the request message includes:

1) TMGI: the value of the attribute "TMGI";

2) start time: the value of the attribute "start time".

Embodiment 2 (the update request of AE includes start time, and IN-CSE directly sends receive parameters)

1. The AE sends an update resource request message to the IN-CSE, where the request message includes:

1) Target: resource <Group Message>;

2) Content: parameter "starting time" and its parameter value

2. After receiving the request message, the IN-CSE verifies whether the AE has the authority to update the resource <Group Message>;

3. After the verification is passed, the IN-CSE creates the attribute "start time" of the resource <Group Message>, and sets the value of the attribute "start time" to the parameter value of the parameter "starting time" in the request message.

4. The IN-CSE sends an Allocate TMGI Request message to the NSE in the core network, and the request message includes:

1) the number of TMGI;

1) TMGI: The value of the TMGI assigned by the core network.

1) TMGI: the value of the attribute "TMGI";

2) start time: the value of the attribute "start time".

1) TMGI: the value of the attribute "TMGI";

2) start time: the value of the attribute "start time".

Embodiment 3 (Startup time is not included in the creation request of AE, and IN-CSE creates subscription resource/notification subscription resource)

1) Resource type: group message;

3. After the verification is passed, IN-CSE creates a group type resource <Group Message> and creates the attribute "TMGI".

4. The ADN/ASN/MN on the terminal or the gateway sends a subscription resource creation request message to the IN-CSE, where the request message includes:

1) Resource Type: Subscription

2) Content: parameter "notification identifier list", and its value is the identifier or group identifier of the AE or CSE receiving the group message.

The parameter "event notification condition" and its value is "attribute = 'start time'", or "attribute = 'TMGI'", or "attribute = 'port address'"

5. The IN-CSE creates a subscription type sub-resource <subscription> for the resource <Group Message> according to the subscription resource creation request message;

Setting the value of the attribute "notificationURI" of the sub-resource <subscription> is the value of the parameter "notification identifier list" in the request message;

The value of the attribute "eventNotificationCriteria" of the sub-resource <subscription> is set to the value of the parameter "event notification condition" in the request message.

6. The IN-CSE sends an Allocate TMGI Request message to the NSE in the core network, and the request message includes:

1) the number of TMGI;

7. The IN-CSE receives the response message of the NSE, and the response message includes:

1) TMGI: The value of the TMGI assigned by the core network.

8. The IN-CSE sets the value of the received TMGI to the value of the attribute "TMGI" of the resource <Group Message>.

9. The IN-CSE sends a Notification Request message to the ADN/ASN/MN on the terminal or the gateway. The request message includes:

1) TMGI: the value of the attribute "TMGI";

2) start time: the value of the attribute "start time".

10. The IN-CSE sends a Group Message Request message to the NSE. The request message includes:

1) TMGI: The value of the attribute "TMGI".

As a supplementary or alternative embodiment of the present embodiment, the IN-CSE may send a Group Message Request message to the NSE according to the attribute value of the attribute “port address” of the resource <Group Message>, where the request message includes: 1) a port address: The value of the property "port address".

Through this implementation, the signaling interaction can be reduced and the network resources can be saved without affecting the application to the AE or CSE sending request on multiple terminals or gateways.

Example 4

Embodiments of the present invention also provide a computer storage medium. The storage medium includes a stored computer program, when executed by the processor, executing: receiving a request message of a group message function; configuring a resource of the group message function according to the request message, and transmitting the resource to the network element of the bearer network Request signaling for requesting to use the group message function; receiving feedback signaling of the request signaling sent by the bearer network element.

In an embodiment, when the computer program is executed by the processor, after receiving the feedback signaling of the request signaling sent by the network element of the bearer network, setting corresponding to the resource according to the feedback signaling Property value.

The request message includes at least one of the following: an identifier or a group identifier of the application entity AE that receives the group message request, an identifier of the public service entity CSE that receives the group message request, or a group identifier.

The request message is used to request one of the following: a resource for creating a group message function, and a resource for updating a group message function.

The attribute of the resource includes a multicast type.

In an embodiment, the computer program is executed by the processor to: when the multicast type is an MBMS group, send request signaling for requesting to use the group message function to the bearer network element.

The request signaling includes one of the following: allocating a TMGI request, a group message request.

Wherein, when the request signaling includes allocating a TMGI request, the feedback signaling is a TMGI response message.

The feedback signaling is a group message acknowledgement message when the request signaling includes a group message request.

The allocated TMGI response message includes a TMGI allocated by the core network.

The group message acknowledgement message includes a port address allocated by the core network.

The request message further includes: a preset start time of the group message function.

In an embodiment, the computer program is executed by the processor to: configure at least one of the following attributes of the resource of the group message function: an external group identifier, a startup time.

In an embodiment, when the computer program is executed by the processor, when the startup time is not configured in the resource of the group message function, setting a short message corresponding to the startup time in the group message request Savings.

In an embodiment, the computer program is executed by the processor to: set the startup time to a next start time of time crossing, wherein the time cross indicates a time period during which group members support communication through the core network.

In an embodiment, the computer program is executed by the processor: when the request signaling includes allocating a TMGI request, after receiving the request message of the group message function, sending the allocated TMGI request to the core network yuan.

In an embodiment, the computer program is executed by the processor: when the request signaling includes a group message request, after receiving the request message of the group message function, sending the group message request to the core network yuan.

In an embodiment, the computer program is executed by the processor to: receive a subscription resource creation request message, and create a subscription sub-resource for the resource of the group message function according to the subscription resource creation request message; The first attribute of the sub-resource is set to receive the identifier or group identifier of the AE or CSE requested by the group message; and the second attribute of the sub-sub-resource is set to: the notification trigger condition is one of the following attributes: TMGI, start Time, port address.

In an embodiment, the computer program is executed by the processor to: send a notification request to the AE or CSE on the terminal or the gateway, wherein the request message includes one of the following attributes of the resource: TMGI, startup time Port address.

In an embodiment, the computer program is executed by the processor to: send the group message request to the core network element according to the startup time.

In an embodiment, when the computer program is executed by the processor, after receiving the feedback signaling of the request signaling sent by the bearer network element, the group message request is performed according to the port address. Send to the core network element.

In this embodiment, the foregoing storage medium may include, but not limited to, a U disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk. A variety of media that can store program code.

For specific examples in this embodiment, reference may be made to the examples described in the foregoing embodiments and the optional embodiments, and details are not described herein again.

Example 5

An embodiment of the present invention further provides a group message management apparatus, including: a processor and a memory for storing a computer program capable of running on a processor, where the processor is configured to: receive when the computer program is executed a request message of the group message function; configuring, according to the request message, the resource of the group message function, sending request signaling for requesting to use the group message function to the bearer network element; receiving the Feedback signaling for request signaling.

In an embodiment, when the processor is configured to run the computer program, performing: after receiving the feedback signaling of the request signaling sent by the bearer network element, setting the The attribute value corresponding to the resource.

The attribute of the resource includes a multicast type.

In an embodiment, when the processor is configured to run the computer program, performing: sending, when the multicast type is an MBMS group, request signaling for requesting to use a group message function to a bearer network element.

In an embodiment, when the processor is configured to run the computer program, perform: configuring at least one of the following attributes of the resource of the group message function: an external group identifier, a startup time.

In an embodiment, when the processor is configured to run the computer program, executing: setting the startup time in the group message request when the startup time is not configured in a resource of the group message function Corresponding default value.

In an embodiment, when the processor is configured to run the computer program, performing: setting the startup time to a next start time of a time cross, wherein the time cross indicates that the group member supports communication through the core network segment.

In an embodiment, when the processor is configured to run the computer program, executing: when the request signaling includes allocating a TMGI request, sending the allocated TMGI request to the request message after receiving the group message function Core network element.

In an embodiment, when the processor is configured to run the computer program, executing: when the request signaling includes a group message request, after receiving the request message of the group message function, sending the group message request to Core network element.

In an embodiment, when the processor is configured to run the computer program, execute: receiving a subscription resource creation request message, and creating a subscription sub-resource for the resource of the group message function according to the subscription resource creation request message; The first attribute of the subscription sub-resource is set to receive an identifier or a group identifier of the AE or CSE requested by the group message; and the second attribute of the subscription sub-resource is set to: the notification trigger condition is one of the following attributes: TMGI, boot time, port address.

In an embodiment, the processor is configured to: when the computer program is executed, send a notification request to an AE or a CSE on a terminal or a gateway, wherein the request message includes one of the following attributes of the resource: TMGI , startup time, port address.

In an embodiment, when the processor is configured to run the computer program, executing: sending the group message request to a core network element according to the startup time.

In an embodiment, when the processor is configured to run the computer program, performing: after receiving the feedback signaling of the request signaling sent by the bearer network element, according to the port address, The group message request is sent to the core network element.

It will be appreciated that the device also includes a communication interface. The various components in the device can be coupled together by a bus system. It will be appreciated that the bus system is used to implement connection communication between these components. In addition to the data bus, the bus system includes a power bus, a control bus, and a status signal bus.

It will be appreciated that the memory can be either volatile memory or non-volatile memory, and can include both volatile and nonvolatile memory. The non-volatile memory may be a Read Only Memory (ROM), a Programmable Read-Only Memory (PROM), or an Erasable Programmable Read (EPROM). Only Memory), Electrically Erasable Programmable Read-Only Memory (EEPROM), Ferromagnetic Random Access Memory (FRAM), Flash Memory, Magnetic Surface Memory , CD-ROM, or Compact Disc Read-Only Memory (CD-ROM); the magnetic surface memory can be a disk storage or a tape storage. The volatile memory can be a random access memory (RAM) that acts as an external cache. By way of example and not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access (SSRAM). DRAM (Dynamic Random Access Memory), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), enhancement Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), Synchronous Dynamic Random Access Memory (SLDRAM), Direct Memory Bus Random Access Memory (DRRAM) ). The memories described in the embodiments of the present invention are intended to include, but are not limited to, these and any other suitable types of memory.

The method disclosed in the above embodiments of the present invention may be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in a processor or an instruction in a form of software. The above processor may be a general purpose processor, a digital signal processor (DSP), or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or the like. The processor may implement or perform the methods, steps, and logic blocks disclosed in the embodiments of the present invention. A general purpose processor can be a microprocessor or any conventional processor or the like. The steps of the method disclosed in the embodiment of the present invention may be directly implemented as a hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium, the storage medium being located in the memory, the processor reading the information in the memory, and completing the steps of the foregoing methods in combination with the hardware thereof.

In an exemplary embodiment, the management device of the group message may be configured by one or more Application Specific Integrated Circuits (ASICs), DSPs, Programmable Logic Devices (PLDs), and Complex Programmable Logic Devices. (CPLD, Complex Programmable Logic Device), Field-Programmable Gate Array (FPGA), general-purpose processor, controller, microcontroller (MCU, Micro Controller Unit), microprocessor (Microprocessor), or Other electronic components are implemented to perform the aforementioned methods.

In the several embodiments provided by the present invention, it should be understood that the disclosed method and apparatus may be implemented in other manners. The device embodiments described above are merely illustrative. For example, the division of the modules is only a logical function division. In actual implementation, there may be another division manner, for example, multiple modules or components may be combined, or Can be integrated into another system, or some features can be ignored or not executed. In addition, the communication connections between the various components shown or discussed may be indirect coupling or communication connections through some interfaces, devices or modules, and may be electrical, mechanical or otherwise.

The modules described above as separate components may or may not be physically separated. The components displayed as modules may or may not be physical modules, that is, may be located in one place or distributed to multiple network modules; Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, each functional module in each embodiment of the present invention may be integrated into one processing module, or each module may be separately used as one module, or two or more modules may be integrated into one module; The module can be implemented in the form of hardware or in the form of hardware plus software function modules.

It will be understood by those skilled in the art that all or part of the steps of implementing the foregoing method embodiments may be performed by hardware related to program instructions. The foregoing program may be stored in a computer readable storage medium, and when executed, the program includes The foregoing steps of the method embodiment; and the foregoing storage medium includes: a removable storage device, a ROM, a magnetic disk, or an optical disk, and the like, which can store program codes.

Alternatively, the above-described integrated module of the embodiment of the present invention may be stored in a computer readable storage medium if it is implemented in the form of a software function module and sold or used as a stand-alone product. Based on such understanding, the technical solution of the embodiments of the present invention may be embodied in the form of a software product in essence or in the form of a software product stored in a storage medium, including a plurality of instructions. A computer device (which may be a personal computer, server, or network device, etc.) is caused to perform all or part of the methods described in various embodiments of the present invention. The foregoing storage medium includes various media that can store program codes, such as a mobile storage device, a ROM, a magnetic disk, or an optical disk.

The method and the device for managing the group message described in the embodiments of the present invention are exemplified by the above-mentioned embodiments. However, the present invention is not limited thereto, and those skilled in the art should understand that the technical solutions described in the foregoing embodiments can still be performed. Modifications, or equivalents to some or all of the technical features, and the modifications or substitutions do not depart from the scope of the technical solutions of the embodiments of the present invention.

The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention.

Industrial applicability

The technical solution of the embodiment of the present invention receives the request message of the group message function, configures the resource of the group message function according to the request message, and sends request signaling for requesting to use the group message function to the bearer network element and receives the feedback. Signaling. By using the bearer network to manage group messages, the signaling interaction is reduced, and the technical problem of wasting network resources when the IoT nodes interact in the related art is solved.

Claims

A method for managing group messages, including:

Receiving a request message of a group message function;

And configuring, according to the request message, a resource of the group message function, and sending, to the bearer network element, request signaling for requesting to use the group message function;

Receiving feedback signaling of the request signaling sent by the bearer network element.
The method of claim 1, wherein after receiving the feedback signaling of the request signaling sent by the bearer network element, the method further comprises:

And setting an attribute value corresponding to the resource according to the feedback signaling.
The method according to claim 1, wherein the request message comprises at least one of: an identifier or a group identifier of an application entity AE that receives a group message request, an identifier of a public service entity CSE that receives a group message request, or a group identifier.
The method of claim 1, wherein the request message is for requesting one of: creating a resource of a group message function, and updating a resource of a group message function.
The method of claim 1 wherein the attribute of the resource comprises a multicast type.
The method according to claim 5, wherein the sending request signaling for requesting to use the group message function to the bearer network element comprises:

When the multicast type is a multimedia broadcast multicast service MBMS group, request signaling for requesting to use the group message function is sent to the bearer network element.
The method of claim 1, wherein the request signaling comprises one of: assigning a temporary mobility group identity TMGI request, a group message request.
The method of claim 7, wherein the feedback signaling is an allocation TMGI response message when the request signaling comprises assigning a TMGI request.
The method of claim 7, wherein the feedback signaling is a group message acknowledgement message when the request signaling comprises a group message request.
The method of claim 8 wherein said assigning TMGI response message comprises a TMGI assigned by a core network.
The method of claim 9 wherein said group message acknowledgement message comprises a port address assigned by the core network.
The method of claim 3, wherein the request message further comprises: a preset start time of the group message function.
The method of claim 1, wherein configuring resources of the group message function according to the request message comprises:

Configuring at least one of the following attributes of the resource of the group message function: an external group identifier, a startup time.
The method according to claim 7, wherein when the startup time is not configured in the resource of the group message function, a default value corresponding to the startup time is set in the group message request.
The method of claim 14, wherein the setting a default value corresponding to the startup time comprises:

The start time is set to be the next start time of the time cross, wherein the time cross indicates the time period during which the group members support communication through the core network.
The method of claim 7, wherein, after the request signaling comprises assigning a TMGI request, after receiving the request message of the group message function, the method further comprises:

Sending the allocated TMGI request to the core network element.
The method according to claim 7, wherein, after the request signaling includes a group message request, after receiving the request message of the group message function, the method further comprises:

Sending the group message request to the core network element.
The method of claim 7 wherein the method further comprises:

Receiving a subscription resource creation request message, and creating a subscription sub-resource for the resource of the group message function according to the subscription resource creation request message;

Setting a first attribute of the subscription sub-resource to an identifier or group identifier of an AE or CSE that receives the group message request; and setting a second attribute of the subscription sub-resource to: a notification trigger condition is one of the following attributes : TMGI, boot time, port address.
The method of claim 1 or 18, wherein the method further comprises:

Sending a notification request to the AE or CSE on the terminal or gateway, wherein the request message includes one of the following attributes of the resource: TMGI, start time, port address.
The method of claim 12 or 14, wherein the method further comprises:

Sending the group message request to the core network element according to the startup time.
The method of claim 11, wherein after receiving the feedback signaling of the request signaling sent by the bearer network element, the method further comprises:

Sending the group message request to the core network element according to the port address.
A group message management device, comprising:

a first receiving module, configured to receive a request message of a group message function;

a management module, configured to configure, according to the request message received by the receiving module, a resource of the group message function, and send, to the bearer network element, request signaling for requesting to use a group message function;

The second receiving module is configured to receive the feedback signaling of the request signaling sent by the bearer network element.
The device of claim 22, wherein the device further comprises:

And a setting module configured to set an attribute value corresponding to the resource according to the feedback signaling.
The apparatus according to claim 22, wherein the request message comprises at least one of: an identifier or a group identifier of an application entity AE that receives the group message request, an identifier or a group identifier of a public service entity CSE that receives the group message request.
The apparatus of claim 22, wherein the request message is for requesting one of: creating a resource of a group message function, and updating a resource of a group message function.
A computer storage medium, comprising a stored computer program, wherein the computer program is executed by a processor to perform the method of any one of claims 1 to 21.
A management apparatus for a group message, comprising: a processor and a memory for storing a computer program executable on a processor, the processor for executing the computer program, executing any one of claims 1 to 21 Said method.