WO2016101429A1 - 一种mtc分组管理方法、装置及系统，网络实体 - Google Patents

一种mtc分组管理方法、装置及系统，网络实体 Download PDF

Info

Publication number
WO2016101429A1
WO2016101429A1 PCT/CN2015/075073 CN2015075073W WO2016101429A1 WO 2016101429 A1 WO2016101429 A1 WO 2016101429A1 CN 2015075073 W CN2015075073 W CN 2015075073W WO 2016101429 A1 WO2016101429 A1 WO 2016101429A1
Authority
WO
WIPO (PCT)
Prior art keywords
mtc
packet
mtc packet
network entity
key
Prior art date
Application number
PCT/CN2015/075073
Other languages
English (en)
French (fr)
Inventor
余万涛
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2016101429A1 publication Critical patent/WO2016101429A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/04—Key management, e.g. using generic bootstrapping architecture [GBA]
    • H04W12/041—Key generation or derivation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/08—User group management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/10—Integrity
    • H04W12/106—Packet or message integrity

Definitions

  • This document relates to the field of communications, and in particular to an MTC packet management method, apparatus and system, and a network entity.
  • M2M (Machine-to-Machine) communication is a general term for a series of technologies and combinations of application communication technologies that realize data communication and communication between machines and machines, machines and people.
  • FIG. 1 is a schematic diagram of an MTC communication system architecture model according to the prior art).
  • the entities participating in the MTC communication include a large number of MTC devices and MTC applications.
  • MTC devices and MTC applications In order to reduce network load and save network resources, it is necessary to manage and optimize the MTC devices and the MTC applications in groups.
  • the MTC Equipment and MTC applications can be controlled, managed, and billed in groups to meet the needs of operators.
  • the MTC device group is in dynamic change, even one MTC device may belong to different MTC device groups, which increases the MTC device group management and the packet key. The difficulty of management.
  • the idea of the related solution is to create an MTC device group and create a corresponding MTC group key for each MTC device group, and establish an MTC based on the MTC group key. Secure communication between different MTC devices in the device group and between the MTC device and the MTC server.
  • the embodiments of the present invention provide an MTC packet management method, apparatus, and system, and a network entity, which are highly adaptable and capable of ensuring communication security between an MTC packet and a network, to solve the problem that the number of MTC packets and keys in the related art is large and dynamic. This leads to poor communication security between the MTC and the network.
  • an embodiment of the present invention provides an MTC packet management method, including: a network entity creates a unique MTC packet identifier for marking each MTC packet, and generates a unique MTC packet density corresponding to the MTC packet identifier. a key, wherein the network entity is a communication entity in the core network that can be used to manage the MTC packet; the network entity creates an MTC packet whose MTC object is empty or non-empty according to the MTC packet identifier and the MTC packet key; the network entity uses the MTC packet Identifying and managing the MTC packet key, performing a management operation on the MTC packet, wherein the management operation includes: an MTC object registration operation.
  • the network entity performs the MTC object registration operation on the MTC packet by using the MTC packet identifier and the MTC packet key, including: the network entity receiving the registration request for requesting to join the MTC packet sent by the MTC object requesting registration, where The registration request includes the identity information of the MTC object requesting registration and the MTC packet identifier; the network entity authenticates the identity information of the MTC object requesting registration, and adds the MTC object requesting the registration to the MTC packet after the authentication is passed; The entity establishes an association relationship between the MTC packet identifier and the identity information of the MTC object requesting registration; the network entity distributes the MTC packet key, or distributes the MTC packet identifier and the MTC packet key to the MTC object requesting registration.
  • the management operation further includes: an MTC object deletion operation; the network entity performs an MTC object deletion operation on the MTC packet by using an MTC packet identifier and an MTC packet key, and the packet
  • the network entity receives the deletion request sent by the MTC object requesting deletion for requesting to be deleted from the MTC packet, where the deletion request includes the identity information of the MTC object requesting to be deleted and the MTC packet identifier; the MTC object requested by the network entity to delete the MTC object
  • the identity information is authenticated, and after the authentication is passed, the MTC object requested to be deleted is deleted from the MTC packet; the network entity deletes the association relationship between the MTC packet identifier and the identity information of the MTC object requested to be deleted.
  • the management operation further includes: an MTC packet key update operation; the network entity performs an MTC packet key update operation on the MTC packet by using the MTC packet identifier and the MTC packet key, including: each of the network entity to the MTC packet
  • the MTC object sends a key update notification message carrying the MTC packet key, so that the MTC object authenticates the key update notification message, and after the authentication is passed, the network entity sends the updated MTC packet key.
  • the network entity includes one of the following: a mobility management entity MME, a serving GPRS support node SGSN, an MTC service management platform, a home subscriber server HSS, and an MTC interworking function MTC-IWF; and the MTC object includes: an MTC device and/or an MTC application. .
  • an embodiment of the present invention further provides an MTC packet management apparatus, where the network entity is a communication entity that can be used to manage an MTC packet in a core network, where the apparatus includes: a processing module, Set to create a unique MTC packet identifier for marking each MTC packet and generate a unique MTC packet key corresponding to the MTC packet identifier; a creating module for creating an MTC object according to the MTC packet identifier and the MTC packet key An empty or non-empty MTC packet; a management module, configured to perform a management operation on the MTC packet by using the MTC packet identifier and the MTC packet key, where the management operation includes: an MTC object registration operation.
  • the management module includes: a first receiving unit, configured to receive a registration request for requesting to join the MTC packet sent by the MTC object requesting registration, where the registration request includes the identity information of the MTC object requesting registration and the MTC group identifier.
  • the first processing unit is configured to authenticate the identity information of the MTC object requesting registration, and after the authentication is passed, add the MTC object requesting the registration to the MTC packet; the establishing unit is set to establish the MTC group identifier and request registration The association relationship between the identity information of the MTC objects; the distribution unit, configured to distribute the MTC packet key, or distribute the MTC packet identifier and the MTC packet key to the MTC pair requesting registration Elephant.
  • the management operation further includes: an MTC object deletion operation;
  • the management module includes: a second receiving unit, configured to receive a deletion request sent by the MTC object requesting deletion for requesting to be deleted from the MTC packet, where the deletion request includes The identity information of the MTC object requested to be deleted and the MTC packet identifier;
  • the deleting unit is configured to delete the association relationship between the MTC packet identifier and the identity information of the MTC object requested to be deleted.
  • the management operation further includes: an MTC packet key update operation;
  • the management module includes: a second processing unit, configured to send a key update notification message carrying the MTC packet key to each MTC object of the MTC packet
  • the MTC object is configured to authenticate the key update notification message, and after the authentication is passed, the network entity sends the updated MTC packet key to each MTC object of the MTC packet.
  • the network entity includes one of the following: a mobility management entity MME, a serving GPRS support node SGSN, an MTC service management platform, a home subscriber server HSS, and an MTC interworking function MTC-IWF; and the MTC object includes: an MTC device and/or an MTC application. .
  • an embodiment of the present invention provides a network entity, including: the foregoing MTC packet management apparatus.
  • an embodiment of the present invention further provides an MTC packet management system, including: the foregoing network entity, an MTC device, and/or an MTC application, where the MTC device and/or the MTC application are set to the network.
  • the entity sends a request to join the registration request of one MTC packet or a request to delete the deletion from an MTC packet;
  • the MTC device and/or the MTC application is further configured to receive the MTC packet key of the MTC packet requested by the network entity and/or Or the MTC packet identifies and saves the MTC packet key and/or the MTC packet identifier;
  • the MTC device and/or the MTC application is further configured to store the MTC packet identifier of one MTC packet requesting to join or request to be deleted.
  • the embodiment of the present invention further provides a computer readable storage medium, where the storage medium stores a computer program, the computer program includes program instructions, when the program instruction is executed by the MTC packet management device, enabling the device to perform the MTC described above. Group management method.
  • the MTC packet management method, apparatus, and system, and the network entity which are implemented by the embodiments of the present invention, can implement MTC device grouping and MTC application group management, thereby ensuring MTC device grouping and MTC application grouping and network.
  • the communication between the security can implement MTC device grouping and MTC application group management, thereby ensuring MTC device grouping and MTC application grouping and network.
  • FIG. 1 is a schematic diagram of an architecture model of an MTC communication system according to the prior art
  • FIG. 2 is a flowchart of an MTC packet management method according to an embodiment of the present invention.
  • FIG. 3 is a structural block diagram of an MTC packet management apparatus according to an embodiment of the present invention.
  • FIG. 4 is a structural block diagram of a preferred MTC packet management apparatus according to an embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of a network entity including the MTC packet management apparatus shown in FIG. 3 or FIG. 4 according to an embodiment of the present invention
  • FIG. 6 is a schematic structural diagram of an MTC packet management system including the network entity shown in FIG. 5 according to an embodiment of the present invention
  • FIG. 7 is a schematic diagram of a process of creating an MTC packet according to a preferred embodiment of the present invention.
  • FIG. 8 is a schematic diagram of an MTC packet registration process according to a preferred embodiment of the present invention.
  • FIG. 9 is a schematic diagram of an MTC packet key distribution process according to a preferred embodiment of the present invention.
  • FIG. 10 is a schematic diagram of an MTC packet key update process according to a preferred embodiment of the present invention.
  • FIG. 11 is a schematic diagram of an MTC packet deletion process according to a preferred embodiment of the present invention.
  • FIG. 12 is a schematic diagram of an MTC packet management apparatus according to a preferred embodiment of the present invention.
  • FIG. 13 is a schematic diagram of an MTC packet management system in accordance with a preferred embodiment of the present invention.
  • the embodiment of the invention provides an MTC packet management method. 2 is an embodiment in accordance with the present invention
  • Step S202 The network entity creates a unique MTC packet identifier for marking an MTC packet, and generates a unique MTC packet key corresponding to the MTC packet identifier, where the network entity is a communication in the core network that can be used to manage the MTC packet. entity.
  • Step S204 The network entity respectively creates an MTC packet whose MTC object is empty or non-empty according to each MTC packet identifier and the MTC packet key.
  • Step S206 The network entity performs a management operation on each MTC packet by using an MTC packet identifier and an MTC packet key, where the management operation includes: an MTC object registration operation.
  • the network entity first creates a unique MTC packet identifier that marks an MTC packet and a corresponding unique MTC packet key, and then according to each MTC packet identifier and The corresponding MTC packet key creates an MTC packet.
  • multiple different MTC packets may be created, each packet having a unique MTC packet identifier and a corresponding unique MTC packet.
  • the key, each MTC packet created may have an MTC object or no MTC object. In this way, the MTC object can be flexibly added or quit the MTC packet, thereby ensuring secure communication between the MTC packet and the network. .
  • the foregoing step S206 may be implemented in such a manner that the network entity receives the MTC object that is requested to be registered for transmission.
  • the network entity authenticates the identity information of the MTC object requesting registration, and after the authentication is passed, The MTC object requesting registration is added to the MTC packet; the network entity establishes an association relationship between the MTC packet identifier and the identity information of the MTC object requesting registration; the network entity groups the MTC packet key, or the MTC packet identifier and the MTC packet The key is distributed to the MTC object requesting registration.
  • the management operation may also be an MTC object deletion operation in an MTC packet.
  • the foregoing step S206 may be implemented in such a manner that the network entity receives the request.
  • Deleted MTC object sent for application a deletion request deleted from the MTC packet wherein the deletion request includes the identity information of the MTC object requesting the deletion and the MTC packet identifier; the network entity authenticates the identity information of the MTC object requested to be deleted, and after the authentication is passed, the request is The deleted MTC object is deleted from the MTC packet; the network entity deletes the association relationship between the MTC packet identifier and the identity information of the MTC object requested to be deleted.
  • the management operation may also be an MTC packet key update operation.
  • the foregoing step S206 may be implemented in such a manner that the network entity groups into one MTC. All the MTC objects in the transmission send a key update notification message carrying the MTC packet key, and the notification information may include the MTC packet identification information, so that all the MTC objects in the MTC packet respectively authenticate the key update notification message, After the authentication is passed, the network entity sends the updated MTC packet key to all MTC objects in the MTC packet.
  • the network entity may include one of the following: a mobility management entity MME, a serving GPRS support node SGSN, an MTC service management platform, a home subscriber server HSS, and an MTC interworking function MTC-IWF; and the MTC object may include: an MTC device. And / or MTC applications.
  • an embodiment of the present invention further provides an MTC packet management apparatus, where the apparatus may be located in a network entity (here, the network entity is required to be a communication entity in the core network that can be used to manage the MTC packet),
  • the processor and the program storage device are included to implement the foregoing MTC packet management method.
  • FIG. 3 is a structural block diagram of an MTC packet management apparatus according to an embodiment of the present invention.
  • the MTC packet management apparatus may include: a processing module 10, a creation module 20, and a management module 30, where:
  • the processing module 10 is adapted to create a unique MTC packet identifier for marking an MTC packet and generate a unique MTC packet key corresponding to the MTC packet identifier; the creating module 20 is adapted to group and MTC packets according to each MTC packet a key, respectively creating an MTC packet whose MTC object is empty or non-empty; the management module 30 is adapted to perform a management operation on each MTC packet by using an MTC packet identifier and an MTC packet key, where the management operation includes: MTC Object registration operation.
  • the embodiment of the present invention further provides a preferred MTC packet management apparatus, which is also used to implement the foregoing MTC grouping method.
  • FIG. 4 is a structural block diagram of a preferred MTC packet management apparatus according to an embodiment of the present invention. As shown in FIG. 4, in the MTC packet management apparatus:
  • the management module 30 may further include: a first receiving unit 301, configured to receive a registration request for requesting to join an MTC packet sent by the MTC object requesting registration, where the registration request includes identity information and an MTC packet of the MTC object requesting registration
  • the first processing unit 302 is configured to authenticate the identity information of the MTC object that is requested to be registered, and after the authentication is passed, add the MTC object that is requested to be registered to the MTC packet;
  • the establishing unit 303 is adapted to establish the MTC.
  • the distribution unit 304 is adapted to distribute the MTC packet key or distribute the MTC packet identifier and the MTC packet key to the MTC object requesting registration.
  • the management operation may further include: an MTC object deletion operation; based on this, the management module 30 may further include: a second receiving unit 305, configured to receive an MTC object that is requested to be deleted in an MTC packet. And deleting the deletion request from the MTC packet, where the deletion request includes the identity information of the MTC object requesting the deletion and the MTC packet identifier; and the deleting unit 306 is adapted to delete the MTC packet identifier and the identity information of the MTC object requested to be deleted. The relationship between them.
  • the management operation may further include: an MTC packet key update operation; based on this, the management module 30 may further include: a second processing unit 307, configured to send and carry all MTC objects to one MTC packet
  • the key update notification message of the MTC packet key is such that all the MTC objects of the MTC packet respectively authenticate the key update notification message, and after the authentication is passed, the network entity sends the updated MTC packet key to the All MTC objects of the MTC packet.
  • the network entity may include one of the following: a mobility management entity MME, a serving GPRS support node SGSN, an MTC service management platform, a home subscriber server HSS, and an MTC interworking function MTC-IWF; and the MTC object may include: an MTC device. And / or MTC applications.
  • FIG. 5 is a schematic structural diagram of a network entity including the MTC packet management apparatus shown in FIG. 3 or FIG. 4 according to an embodiment of the present invention. As shown in FIG. 5, the network entity includes the MTC packet management shown in FIG. 3 or FIG. Device.
  • FIG. 6 is a schematic structural diagram of an MTC packet management system including the network entity shown in FIG. 5 according to an embodiment of the present invention. As shown in FIG. 6, the system includes: the network entity, the MTC device, and/or the MTC shown in FIG. 5. Application, where:
  • the MTC device and/or the MTC application is adapted to send a registration request to the network entity to request to join an MTC packet or to request a deletion request to be deleted from an MTC packet; the MTC device and/or the MTC application are also applicable to the receiving network entity. Requesting the MTC packet key and/or MTC packet identifier of one MTC packet to join, and saving the MTC packet key and/or the MTC packet identifier; the MTC device and/or the MTC application are also applicable to storing one requesting to join or requesting deletion The MTC packet identifier of the MTC packet.
  • the MTC user, or the operator, or the MTC application provider can create multiple MTC packets through one network entity in the MTC communication system, and perform group management on the MTC device or the MTC application.
  • the network entity may be any communication entity in the core network that can be used to manage the MTC packet, for example, may be an MME, or an SGSN, or an HSS, or an MTC-IWF, or an MTC service management platform.
  • the MTC packet may include an MTC device (belonging to the above MTC object), and the MTC packet may also include an MTC application (belonging to the above MTC object), and the MTC packet may further include an MTC device and an MTC application (both belonging to the above MTC object).
  • FIG. 7 is a schematic diagram of a process for creating an MTC packet according to a preferred embodiment of the present invention. As shown in FIG. 7, the MTC packet creation process specifically includes:
  • the network entity creates an MTC packet identifier for marking an MTC packet
  • the network entity may create a correspondence list of the MTC packet identifier and the MTC device identity information or the MTC application identity information as needed.
  • the mapping relationship between the MTC packet identifier and the MTC device identity information or the MTC application identity information may be an empty table, that is, the identity of the MTC device or the MTC application may not be included in the correspondence relationship list.
  • the correspondence information list may also include the identity information of the MTC device or the MTC application (that is, the two cases of "the MTC object in the MTC packet is empty or non-empty" described in the foregoing embodiment).
  • the network entity can save and manage the packet identifier and its corresponding MTC packet key, and a correspondence list of the MTC packet identifier and the MTC device identity information or the MTC application identity information.
  • FIG. 8 is a schematic diagram of an MTC packet registration process according to a preferred embodiment of the present invention. As shown in FIG. 8, the MTC packet registration process includes the following steps:
  • Step S801 the MTC device or the MTC application sends the MTC packet registration request information to the network entity, requesting registration to an MTC packet, where the MTC packet registration request information may include: MTC device identity information or MTC application identity information, and the MTC packet.
  • MTC packet identification information may include: MTC device identity information or MTC application identity information, and the MTC packet.
  • Step S802 the network entity performs verification or authentication on the MTC device or the MTC application.
  • the verification or authentication of the MTC device or the MTC application by the network entity is implemented and completed by the network entity, or the MTC user, or the operator;
  • Step S803 after the verification or the authentication is passed, the network entity updates and saves the MTC packet identifier and the MTC device identity information and/or the MTC application identity information according to the MTC device identity information and/or the MTC application identity information in the registration request information.
  • the network entity updates and saves the MTC packet identifier and the MTC device identity information and/or the MTC application identity information according to the MTC device identity information and/or the MTC application identity information in the registration request information.
  • Step S804 the network entity may feed back the registration confirmation information to the MTC device and/or the MTC application as needed.
  • FIG. 9 is a schematic diagram of a MTC packet key distribution process according to a preferred embodiment of the present invention. As shown in FIG. 9, the MTC packet key distribution process includes the following steps:
  • Step S901 the network entity sends an MTC packet notification to the MTC device and/or the MTC application.
  • Step S902 the MTC device and/or the MTC application notifies the received MTC packet notification message. Perform authentication;
  • Step S903 after the authentication is passed, the MTC device or the MTC application returns the confirmation information to the network entity.
  • Step S904 the network entity sends the MTC packet identifier of the MTC packet and its corresponding MTC packet key to the MTC device or the MTC application by using a security method;
  • Step S905 after receiving the MTC packet identifier and the MTC packet key, the MTC device or the MTC application securely saves the MTC packet identifier and the MTC packet key.
  • Step S906 the MTC device or the MTC application may return an acknowledgement message to the network entity.
  • FIG. 10 is a schematic diagram of an MTC packet key update process according to a preferred embodiment of the present invention. As shown in FIG. 10, the MTC packet key update process includes the following steps:
  • Step S1001 The network entity sends an MTC packet key update notification of the MTC packet to the MTC device and/or the MTC application.
  • the notification information may include MTC packet identification information for notifying all MTC devices and/or MTC applications in the MTC packet;
  • Step S1002 The MTC device and/or the MTC application authenticates the received MTC packet key update notification message.
  • Step S1003 After the authentication is passed, the MTC device or the MTC application returns the confirmation information to the network entity.
  • Step S1004 The network entity sends the MTC packet identifier and its corresponding new MTC packet key to each MTC device or MTC application in the MTC packet by using a security method.
  • Step S1005 After receiving the MTC packet identifier of the MTC packet and the new MTC packet key, the MTC device or the MTC application updates and securely stores the new MTC packet key corresponding to the MTC packet identifier.
  • step S1006 the MTC device or the MTC application may return an acknowledgement message to the network entity.
  • FIG. 11 is a schematic diagram of an MTC packet deletion process according to a preferred embodiment of the present invention. As shown in FIG. 11, the MTC packet deletion update process includes the following steps:
  • Step S1101 The MTC device or the MTC application sends the deletion request information to the network entity that manages the MTC packet, where the deletion request information includes the MTC to which the MTC device or the MTC application belongs. a packetized MTC packet identifier, and identity information of the MTC device or MTC application;
  • Step S1102 After the network entity authenticates the identity information of the MTC device or the MTC application, the MTC device or the MTC application to be deleted, the correspondence list of the MTC packet identifier and the MTC device identity information corresponding to the MTC packet identifier, or the MTC. Deleting, deleting, and saving a correspondence list of the MTC packet identifier and the MTC device identity information or the MTC application identity information in the correspondence list of the packet identifier and the MTC application identity information;
  • Step S1103 The network entity further updates the MTC packet key corresponding to the MTC packet identifier.
  • Step S1104 The network entity initiates an MTC packet key update procedure for all MTC devices or MTC applications in the updated MTC packet.
  • FIG. 12 is a schematic diagram of an MTC packet management apparatus according to a preferred embodiment of the present invention. As shown in FIG. 12, the MTC packet management apparatus includes:
  • the MTC packet creation module 10 is adapted to generate an MTC packet identifier, and create a correspondence list of the MTC packet and the MTC device identity information or a correspondence relationship list between the MTC packet and the MTC application identity information;
  • the MTC group management module 20 is adapted to save and maintain the MTC group identifier, and save and maintain a correspondence list of the MTC packet and the MTC device identity information or a correspondence list between the MTC packet and the MTC application identity information;
  • the MTC packet key generation module 30 is adapted to generate an MTC packet key corresponding to the MTC packet identifier
  • the MTC packet key management module 40 is adapted to store and maintain an MTC packet key
  • a distribution module 50 configured to distribute an MTC packet identifier and an MTC packet key
  • the receiving module 60 is adapted to receive the MTC packet identifier and the MTC packet key.
  • FIG. 13 is a schematic diagram of an MTC packet management system according to a preferred embodiment of the present invention. As shown in FIG. 13, as shown in FIG. 13, the MTC packet management system includes:
  • An MTC device adapted to receive and save an MTC packet identifier and an MTC packet key
  • An MTC application adapted to receive and save an MTC packet identifier and an MTC packet key
  • the network entity is configured to create an MTC packet, generate an MTC packet identifier and an MTC packet key, create a correspondence list of the MTC packet identifier and the MTC device identity information, or a correspondence list between the MTC packet identifier and the MTC application identity information, and group the MTC packet
  • the identifier, the MTC packet key, and the correspondence list of the MTC device identifier and the MTC device identity information or the MTC application identity information are managed and maintained; the network entity is also responsible for the distribution of the MTC packet identifier and the MTC packet key.
  • the functional modules in the MTC packet management apparatus provided by the preferred embodiment are inconsistent with the names of the functional modules in the foregoing embodiments, and even some modules have overlapping or overlapping functions, but Affect the role of each functional module. Also, the MTC packet management system provided by the preferred embodiment and the entity provided by the above embodiment are also applicable.
  • the embodiment of the present invention proposes a feasible MTC packet communication management method, and since the network entity and the group members in the MTC packet each have a packet identifier and MTC uniquely corresponding to the MTC packet.
  • the packet key therefore, enables secure management of group members in the MTC packet and ensures secure communication of the MTC packets between the networks.
  • all or part of the steps of the above embodiments may also be implemented by using an integrated circuit. These steps may be separately fabricated into individual integrated circuit modules, or multiple modules or steps may be fabricated into a single integrated circuit module. achieve. Thus, the invention is not limited to any specific combination of hardware and software.
  • the devices/function modules/functional units in the above embodiments may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices.
  • each device/function module/functional unit in the above embodiment When each device/function module/functional unit in the above embodiment is implemented in the form of a software function module and sold or used as a stand-alone product, it can be stored in a computer readable storage medium.
  • the above mentioned computer readable storage medium may be a read only memory, a magnetic disk or an optical disk or the like.
  • the MTC packet management method, device and system provided by the embodiments of the present invention can implement management of the MTC device group and the MTC application packet, thereby ensuring communication security between the MTC device group and the MTC application packet and the network.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种MTC分组管理方法、装置及系统，网络实体。其中，该方法包括：网络实体创建用于标记MTC分组的唯一MTC分组标识，并生成对应于MTC分组标识的唯一MTC分组密钥，其中，网络实体是核心网中能够用于管理MTC分组的通信实体；网络实体根据MTC分组标识与MTC分组密钥，创建一个MTC对象为空或者非空的MTC分组；网络实体使用MTC分组标识与MTC分组密钥，对MTC分组执行管理操作，其中，管理操作包括：MTC对象注册操作。通过本发明实施例，达到了管理适应性较强，且能保障MTC分组与网络之间的通信安全的效果。

Description

一种MTC分组管理方法、装置及系统，网络实体 技术领域
本文涉及通信领域，尤其是涉及一种MTC分组管理方法、装置及系统，网络实体。
背景技术
未来的通信网络中的通信将更多地以设备与设备，以及设备与数据中心之间的通信为主，越来越便宜的存储技术将使得人与设备获得海量信息成为可能，伴随着芯片处理能力和实时在线技术的发展，设备将成为未来移动通信中的主要参与者。M2M(Machine-to-Machine，机器到机器)通信是指应用通信技术，实现机器与机器、机器与人之间的数据通信和交流的一系列技术及其组合的总称。
由于物联网MTC(Machine Type Communication，机器类通信)整合了通信技术和信息技术，且可用于双向通信，例如，远距离收集信息、设置参数并发送指令，因此，MTC能够实现不同的应用方案，例如，安全监测、自动售货、货物跟踪等。由此可见，几乎所有日常生活中涉及到的设备都有可能成为潜在的服务对象。为便于理解MTC通信系统的架构，这里可以参照图1(图1是根据现有技术的MTC通信系统架构模型示意图)。
在物联网MTC通信系统中，参与MTC通信的实体包括数量众多的MTC设备和MTC应用，为了降低网络负载，节省网络资源，需要对MTC设备和MTC应用以组的方式进行管理优化，这样，MTC设备和MTC应用就可以按组的方式进行控制、管理及计费等，从而适应运营商的需求。但是，由于MTC系统中的MTC设备分组数量众多，且MTC设备分组处在动态变化之中，甚至一个MTC设备可能分属不同的MTC设备组，这种方式增加了MTC设备分组管理和分组密钥管理的难度。
针对该问题，相关的解决方案的思路是：创建MTC设备分组并为每个MTC设备分组创建一个对应的MTC组密钥，并基于MTC组密钥建立MTC 设备分组中不同MTC设备间，以及MTC设备与MTC服务器之间的安全通信。
但是，由于MTC分组和密钥数量众多，并且很多MTC分组和密钥是临时性的，导致现有MTC分组和密钥管理方法很难适应数量巨大且动态变化的MTC设备分组的安全通信。因此，需要设计适应性强的MTC设备分组管理和密钥管理方法，才能保障MTC分组的安全通信。
发明内容
本发明实施例提供一种适应性强、能够保障MTC分组与网络之间的通信安全的MTC分组管理方法、装置及系统，网络实体，以解决相关技术中MTC分组和密钥数量巨大且动态变化导致MTC与网络之间的通信安全性较差问题。
根据本发明的一个方面，本发明实施例提供了一种MTC分组管理方法，包括：网络实体创建用于标记每个MTC分组的唯一MTC分组标识，并生成对应于MTC分组标识的唯一MTC分组密钥，其中，网络实体是核心网中能够用于管理MTC分组的通信实体；网络实体根据MTC分组标识与MTC分组密钥，创建一个MTC对象为空或者非空的MTC分组；网络实体使用MTC分组标识与MTC分组密钥，对MTC分组执行管理操作，其中，管理操作包括：MTC对象注册操作。
可选地，网络实体使用MTC分组标识与MTC分组密钥，对所述MTC分组执行MTC对象注册操作，包括：网络实体接收请求注册的MTC对象发送的用于申请加入MTC分组的注册请求，其中，注册请求包括请求注册的MTC对象的身份信息和MTC分组标识；网络实体对请求注册的MTC对象的身份信息进行鉴权，在鉴权通过后，将请求注册的MTC对象添加到MTC分组；网络实体建立MTC分组标识与请求注册的MTC对象的身份信息之间的关联关系；网络实体将MTC分组密钥，或者将MTC分组标识和MTC分组密钥分发给请求注册的MTC对象。
可选地，管理操作还包括：MTC对象删除操作；网络实体使用MTC分组标识与MTC分组密钥，对所述MTC分组执行MTC对象删除操作，包 括：网络实体接收请求删除的MTC对象发送的用于申请从MTC分组中删除的删除请求，其中，删除请求包括请求删除的MTC对象的身份信息和MTC分组标识；网络实体对请求删除的MTC对象的身份信息进行鉴权，在鉴权通过后，将请求删除的MTC对象从MTC分组中删除；网络实体删除MTC分组标识与请求删除的MTC对象的身份信息之间的关联关系。
可选地，管理操作还包括：MTC分组密钥更新操作；网络实体使用MTC分组标识与MTC分组密钥，对MTC分组执行MTC分组密钥更新操作，包括：网络实体向所述MTC分组的每个MTC对象发送携带有MTC分组密钥的密钥更新通知消息，使得所述MTC对象对密钥更新通知消息进行鉴权，在鉴权通过后，网络实体将更新后的MTC分组密钥下发给所述MTC分组的每个MTC对象。
可选地，网络实体包括以下之一：移动管理实体MME、服务GPRS支持节点SGSN、MTC业务管理平台、归属用户服务器HSS、MTC互通功能MTC-IWF；MTC对象包括：MTC设备和/或MTC应用。
根据本发明的另一个方面，本发明实施例还提供了一种MTC分组管理装置，位于网络实体，网络实体是核心网中能够用于管理MTC分组的通信实体，所述装置包括：处理模块，设置为创建用于标记每个MTC分组的唯一MTC分组标识，并生成对应于MTC分组标识的唯一MTC分组密钥；创建模块，用于根据MTC分组标识与MTC分组密钥，创建一个MTC对象为空或者非空的MTC分组；管理模块，用于使用MTC分组标识与MTC分组密钥，对MTC分组执行管理操作，其中，管理操作包括：MTC对象注册操作。
可选地，管理模块包括：第一接收单元，设置为接收请求注册的MTC对象发送的用于申请加入MTC分组的注册请求，其中，注册请求包括请求注册的MTC对象的身份信息和MTC分组标识；第一处理单元，设置为对请求注册的MTC对象的身份信息进行鉴权，在鉴权通过后，将请求注册的MTC对象添加到MTC分组；建立单元，设置为建立MTC分组标识与请求注册的MTC对象的身份信息之间的关联关系；分发单元，设置为将MTC分组密钥，或将MTC分组标识和MTC分组密钥分发给请求注册的MTC对 象。
可选地，管理操作还包括：MTC对象删除操作；管理模块包括：第二接收单元，设置为接收请求删除的MTC对象发送的用于申请从MTC分组中删除的删除请求，其中，删除请求包括请求删除的MTC对象的身份信息和MTC分组标识；删除单元，设置为删除MTC分组标识与请求删除的MTC对象的身份信息之间的关联关系。
可选地，管理操作还包括：MTC分组密钥更新操作；管理模块包括：第二处理单元，设置为向所述MTC分组的每个MTC对象发送携带有MTC分组密钥的密钥更新通知消息，使得所述MTC对象对密钥更新通知消息进行鉴权，在鉴权通过后，网络实体将更新后的MTC分组密钥下发给所述MTC分组的每个MTC对象。
可选地，网络实体包括以下之一：移动管理实体MME、服务GPRS支持节点SGSN、MTC业务管理平台、归属用户服务器HSS、MTC互通功能MTC-IWF；MTC对象包括：MTC设备和/或MTC应用。
根据本发明的又一个方面，本发明实施例提供了一种网络实体，包括：上述MTC分组管理装置。
根据本发明的还一个方面，本发明实施例还提供了一种MTC分组管理系统，包括：上述网络实体、MTC设备和/或MTC应用，其中，MTC设备和/或MTC应用，设置为向网络实体发送请求加入一个MTC分组的注册请求或请求从一个MTC分组中删除的删除请求；MTC设备和/或MTC应用，还设置为接收网络实体发送的请求加入的MTC分组的MTC分组密钥和/或MTC分组标识，并保存MTC分组密钥和/或MTC分组标识；MTC设备和/或MTC应用，还设置为存储请求加入或请求删除的一个MTC分组的MTC分组标识。
本发明实施例还提供一种计算机可读存储介质，所述存储介质存储有计算机程序，该计算机程序包括程序指令，当该程序指令被MTC分组管理设备执行时，使得该设备可执行上述的MTC分组管理方法。
与现有技术相比，本发明实施例所述的MTC分组管理方法、装置及系统，网络实体，能够实现对MTC设备分组和MTC应用分组进行管理，从而保障MTC设备分组和MTC应用分组与网络之间的通信安全。
附图概述
图1是根据现有技术的MTC通信系统架构模型示意图；
图2是根据本发明实施例的MTC分组管理方法流程图；
图3是根据本发明实施例的MTC分组管理装置的结构框图；
图4是根据本发明实施例的较佳的MTC分组管理装置的结构框图；
图5是根据本发明实施例的包括图3或图4所示的MTC分组管理装置的网络实体的结构示意图；
图6是根据本发明实施例的包括图5所示的网络实体的MTC分组管理系统的结构示意图；
图7是根据本发明较佳实施例的MTC分组创建过程示意图；
图8是根据本发明较佳实施例的MTC分组注册过程示意图；
图9是根据本发明较佳实施例的MTC分组密钥分发过程示意图；
图10是根据本发明较佳实施例的MTC分组密钥更新过程示意图；
图11是根据本发明较佳实施例的MTC分组删除过程示意图；
图12是根据本发明较佳实施例的MTC分组管理装置的示意图；以及
图13是根据本发明较佳实施例的MTC分组管理系统的示意图。
本发明的较佳实施方式
下文中将结合附图对本发明的实施例进行详细说明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。另外，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
本发明实施例提供了一种MTC分组管理方法。图2是根据本发明实施例 的MTC分组管理方法流程图，如图2所示，该流程包括以下步骤(步骤S202-步骤S206)：
步骤S202、网络实体创建用于标记一个MTC分组的唯一MTC分组标识，并生成对应于所述MTC分组标识的唯一MTC分组密钥，其中，网络实体是核心网中能够用于管理MTC分组的通信实体。
步骤S204、网络实体根据每个MTC分组标识与MTC分组密钥，分别创建一个MTC对象为空或者非空的MTC分组。
步骤S206、网络实体使用MTC分组标识与MTC分组密钥，分别对每个MTC分组执行管理操作，其中，管理操作包括：MTC对象注册操作。
通过上述步骤，作为核心网中具有管理MTC分组功能的通信实体，网络实体先创建标记一个MTC分组的唯一的MTC分组标识及其对应的唯一MTC分组密钥，再根据每个MTC分组标识及其对应的MTC分组密钥创建一个MTC分组，此处需要说明的是，根据本发明实施例的方法，可以创建多个不同的MTC分组，每个分组都具有唯一MTC分组标识和对应的唯一MTC分组密钥，创建的每个MTC分组中可以有MTC对象，也可以没有MTC对象，通过这样的方式，可以方便MTC对象灵活地加入或退出MTC分组，从而可以保证MTC分组与网络之间的安全通信。
在本发明实施例的一个较佳实施方式中，当管理操作是MTC对象注册到一个MTC分组的操作时，上述步骤S206可以通过这样的方式来实现：网络实体接收请求注册的MTC对象发送的用于申请加入一个MTC分组的注册请求，其中，注册请求包括请求注册的MTC对象的身份信息和MTC分组标识；网络实体对请求注册的MTC对象的身份信息进行鉴权，在鉴权通过后，将请求注册的MTC对象添加到所述MTC分组；网络实体建立MTC分组标识与请求注册的MTC对象的身份信息之间的关联关系；网络实体将MTC分组密钥，或者将MTC分组标识和MTC分组密钥分发给请求注册的MTC对象。
在本发明实施例的另一个较佳实施方式中，管理操作还可以是一个MTC分组中的MTC对象删除操作，在这样的情况下，上述步骤S206可以通过这样的方式来实现：网络实体接收请求删除的MTC对象发送的用于申请 从MTC分组中删除的删除请求，其中，删除请求包括请求删除的MTC对象的身份信息和MTC分组标识；网络实体对请求删除的MTC对象的身份信息进行鉴权，在鉴权通过后，将请求删除的MTC对象从MTC分组中删除；网络实体删除MTC分组标识与请求删除的MTC对象的身份信息之间的关联关系。
在本发明实施例的又一个较佳实施方式中，管理操作还还可以是MTC分组密钥更新操作，在这种情况下，上述步骤S206可以通过这样的方式来实现：网络实体向一个MTC分组中的所有MTC对象发送携带有MTC分组密钥的密钥更新通知消息，通知信息可以包括该MTC分组标识信息，使得该MTC分组中的所有MTC对象分别对密钥更新通知消息进行鉴权，在鉴权通过后，网络实体将更新后的MTC分组密钥下发给所述MTC分组中的所有MTC对象。
在发明本实施例中，网络实体可以包括以下之一：移动管理实体MME、服务GPRS支持节点SGSN、MTC业务管理平台、归属用户服务器HSS、MTC互通功能MTC-IWF；MTC对象可以包括：MTC设备和/或MTC应用。
对应于上述MTC分组管理方法，本发明实施例还提供了一种MTC分组管理装置，该装置可以位于网络实体(此处，要求网络实体是核心网中能够用于管理MTC分组的通信实体)，包括处理器和程序存储设备，用于实现上述MTC分组管理方法。
图3是根据本发明实施例的MTC分组管理装置的结构框图，如图3所示，该MTC分组管理装置可以包括：处理模块10、创建模块20以及管理模块30，其中：
处理模块10，适用于创建用于标记一个MTC分组的唯一MTC分组标识，并生成对应于所述MTC分组标识的唯一MTC分组密钥；创建模块20，适用于根据每个MTC分组标识与MTC分组密钥，分别创建一个MTC对象为空或者非空的MTC分组；管理模块30，适用于使用MTC分组标识与MTC分组密钥，分别对每个MTC分组执行管理操作，其中，管理操作包括：MTC对象注册操作。
在图3所示的MTC分组管理装置的基础上，本发明实施例还提供了一种较佳的MTC分组管理装置，同样用于实现上述MTC分组方法。
图4是根据本发明实施例的较佳MTC分组管理装置的结构框图，如图4所示，在该MTC分组管理装置中：
管理模块30可以进一步包括：第一接收单元301，适用于接收请求注册的MTC对象发送的用于申请加入一个MTC分组的注册请求，其中，注册请求包括请求注册的MTC对象的身份信息和MTC分组标识；第一处理单元302，适用于对请求注册的MTC对象的身份信息进行鉴权，在鉴权通过后，将请求注册的MTC对象添加到所述MTC分组；建立单元303，适用于建立MTC分组标识与请求注册的MTC对象的身份信息之间的关联关系；分发单元304，适用于将MTC分组密钥，或者将MTC分组标识和MTC分组密钥分发给请求注册的MTC对象。
在本发明实施例中，管理操作还可以包括：MTC对象删除操作；基于此，管理模块30还可以进一步包括：第二接收单元305，适用于接收一个MTC分组中请求删除的MTC对象发送的用于申请从所述MTC分组中删除的删除请求，其中，删除请求包括请求删除的MTC对象的身份信息和MTC分组标识；删除单元306，适用于删除MTC分组标识与请求删除的MTC对象的身份信息之间的关联关系。
在本发明实施例中，管理操作还可以包括：MTC分组密钥更新操作；基于此，管理模块30还可以进一步包括：第二处理单元307，适用于向一个MTC分组的所有MTC对象发送携带有MTC分组密钥的密钥更新通知消息，使得所述MTC分组的所有MTC对象分别对密钥更新通知消息进行鉴权，在鉴权通过后，网络实体将更新后的MTC分组密钥下发给所述MTC分组的所有MTC对象。
在本发明实施例中，网络实体可以包括以下之一：移动管理实体MME、服务GPRS支持节点SGSN、MTC业务管理平台、归属用户服务器HSS、MTC互通功能MTC-IWF；MTC对象可以包括：MTC设备和/或MTC应用。
本发明实施例还提供了一种网络实体，用于实现上述MTC分组管理方 法。图5是根据本发明实施例的包括图3或图4所示的MTC分组管理装置的网络实体的结构示意图，如图5所示，该网络实体包括图3或图4所示的MTC分组管理装置。
本发明实施例还提供了一种MTC分组管理系统，适用于实现上述MTC分组管理方法。图6是根据本发明实施例的包括图5所示的网络实体的MTC分组管理系统的结构示意图，如图6所示，该系统包括：图5所示的网络实体、MTC设备和/或MTC应用，其中：
MTC设备和/或MTC应用，适用于向网络实体发送请求加入一个MTC分组的注册请求或请求从一个MTC分组中删除的删除请求；MTC设备和/或MTC应用，还适用于接收网络实体发送的请求加入的一个MTC分组的MTC分组密钥和/或MTC分组标识，并保存MTC分组密钥和/或MTC分组标识；MTC设备和/或MTC应用，还适用于存储请求加入或请求删除的一个MTC分组的MTC分组标识。
为便于理解上述实施例的实现过程，以下结合图7至图13以及较佳实施例进行更加详细的说明。
较佳实施例
在本较佳实施例中，MTC用户，或者运营商，或者MTC应用提供商都可以通过MTC通信系统中的一个网络实体创建多个MTC分组，并对MTC设备或MTC应用进行分组管理。其中，(1)网络实体可以是核心网中任何可以用于管理MTC分组的通信实体，例如，可以是MME，或者是SGSN，或者是HSS，或者是MTC-IWF，或者是MTC业务管理平台等；(2)MTC分组可以包含MTC设备(属于上述MTC对象)，MTC分组也可以包含MTC应用(属于上述MTC对象)，MTC分组还可以包含MTC设备和MTC应用(都属于上述MTC对象)。
图7是根据本发明较佳实施例的MTC分组创建过程示意图，如图7所示，该MTC分组创建过程具体包括：
(1)网络实体创建一个MTC分组标识，用于标记一个MTC分组；
(2)同时针对创建的分组标识生成一个对应的MTC分组密钥；
(3)网络实体可以根据需要创建MTC分组标识与MTC设备身份信息或MTC应用身份信息的对应关系列表。
需要说明的是，在创建MTC分组时，MTC分组标识与MTC设备身份信息或MTC应用身份信息的对应关系列表可以是一个空表，即对应关系列表中可以不包含任何MTC设备或MTC应用的身份信息，当然，对应关系列表中也可以包含MTC设备或MTC应用的身份信息(即上述实施例所述的“MTC分组中的MTC对象为空或非空”的两种情况)。
而且，网络实体可以保存并管理分组标识及其对应的MTC分组密钥，以及MTC分组标识与MTC设备身份信息或MTC应用身份信息的对应关系列表。
图8是根据本发明较佳实施例的MTC分组注册过程示意图，如图8所示，该MTC分组注册过程包括以下步骤：
步骤S801，MTC设备或MTC应用向网络实体发送MTC分组注册请求信息，请求注册到一个MTC分组；其中，MTC分组注册请求信息可以包括：MTC设备身份信息或MTC应用身份信息，以及所述MTC分组的MTC分组标识信息；
步骤S802，网络实体对所述MTC设备或MTC应用进行验证或认证。网络实体对所述MTC设备或MTC应用的验证或认证由网络实体，或MTC用户，或运营商等实施并完成；
步骤S803，验证或认证通过后，网络实体根据注册请求信息中的MTC设备身份信息和/或MTC应用身份信息，更新并保存所述MTC分组标识和MTC设备身份信息和/或MTC应用身份信息的对应关系列表；
步骤S804，网络实体可以根据需要向所述MTC设备和/或MTC应用反馈注册确认信息。
图9是根据本发明较佳实施例的MTC分组密钥分发过程示意图，如图9所示，该MTC分组密钥分发过程包括以下步骤：
步骤S901，网络实体向MTC设备和/或MTC应用下发MTC分组通知；
步骤S902，该MTC设备和/或MTC应用对接收到的MTC分组通知报文 进行鉴权；
步骤S903，鉴权通过后，该MTC设备或MTC应用向网络实体返回确认信息；
步骤S904，网络实体将所述MTC分组的MTC分组标识及其对应的MTC分组密钥通过安全方法下发到该MTC设备或MTC应用；
步骤S905，所述MTC设备或MTC应用接收到MTC分组标识和MTC分组密钥后，安全保存MTC分组标识和MTC分组密钥；
步骤S906，所述MTC设备或MTC应用可以向网络实体返回确认消息。
图10是根据本发明较佳实施例的MTC分组密钥更新过程示意图，如图10所示，MTC分组密钥更新过程包括以下步骤：
步骤S1001，网络实体向MTC设备和/或MTC应用下发一个MTC分组的MTC分组密钥更新通知。通知信息可以包括MTC分组标识信息，用于通知所述MTC分组中的所有MTC设备和/或MTC应用；
步骤S1002，MTC设备和/或MTC应用对接收到的MTC分组密钥更新通知报文进行鉴权；
步骤S1003，鉴权通过后，MTC设备或MTC应用向网络实体返回确认信息；
步骤S1004，网络实体将MTC分组标识及其对应的新的MTC分组密钥通过安全方法下发到所述MTC分组中的每个MTC设备或MTC应用；
步骤S1005，所述MTC设备或MTC应用接收到该MTC分组的MTC分组标识和新的MTC分组密钥后，更新并安全保存MTC分组标识对应的新的MTC分组密钥；
步骤S1006，MTC设备或MTC应用可以向网络实体返回确认消息。
图11是根据本发明较佳实施例的MTC分组删除过程示意图，如图11所示，MTC分组删除更新过程包括以下步骤：
步骤S1101，MTC设备或MTC应用向管理MTC分组的网络实体发送删除请求信息，删除请求信息中包含所述MTC设备或MTC应用所属的MTC 分组的MTC分组标识，以及所述MTC设备或MTC应用的身份信息；
步骤S1102，网络实体对MTC设备或MTC应用的身份信息进行认证后，将需要删除的MTC设备或MTC应用，从所述MTC分组标识对应的MTC分组标识与MTC设备身份信息的对应关系列表或MTC分组标识与MTC应用身份信息的对应关系列表中删除，更新并保存MTC分组标识与MTC设备身份信息或MTC应用身份信息的对应关系列表；
步骤S1103，网络实体进一步更新MTC分组标识对应的MTC分组密钥；
步骤S1104，网络实体启动针对更新后的MTC分组中的所有MTC设备或MTC应用的MTC分组密钥更新过程。
图12是根据本发明较佳实施例的MTC分组管理装置的示意图，如图12所示，MTC分组管理装置包括：
MTC分组创建模块10，适用于生成MTC分组标识，创建MTC分组与MTC设备身份信息的对应关系列表或MTC分组与MTC应用身份信息的对应关系列表；
MTC分组管理模块20，适用于保存和维护MTC分组标识，保存和维护MTC分组与MTC设备身份信息的对应关系列表或MTC分组与MTC应用身份信息的对应关系列表；
MTC分组密钥生成模块30，适用于生成对应于MTC分组标识的MTC分组密钥；
MTC分组密钥管理模块40，适用于存储和维护MTC分组密钥；
分发模块50，适用于分发MTC分组标识和MTC分组密钥；
接收模块60，适用于接收MTC分组标识和MTC分组密钥。
图13是根据本发明较佳实施例的MTC分组管理系统的示意图，如图13所示，如图13所示，MTC分组管理系统包括：
MTC设备，适用于接收和保存MTC分组标识和MTC分组密钥；
MTC应用，适用于接收和保存MTC分组标识和MTC分组密钥；
网络实体，适用于创建MTC分组，生成MTC分组标识和MTC分组密钥，创建MTC分组标识与MTC设备身份信息的对应关系列表或MTC分组标识与MTC应用身份信息的对应关系列表，并对MTC分组标识、MTC分组密钥及MTC分组标识与MTC设备身份信息或MTC应用身份信息的对应关系列表进行管理和维护；网络实体还负责MTC分组标识和MTC分组密钥的分发。
需要说明的是，本较佳实施例提供的MTC分组管理装置中的各个功能模块与上述实施例中的各个功能模块的名称不一致，甚至某些模块还存在功能交叉或重叠的部分，但是并不影响各个功能模块所起的作用。同样，对于本较佳实施例提供的MTC分组管理系统和上述实施例提供的实体也是适用的。
由以上较佳实施例可以看出，本发明实施例提出了一种切实可行的MTC分组通信管理方法，并且由于网络实体与MTC分组中的组成员各自拥有与MTC分组唯一对应的分组标识和MTC分组密钥，因此，能够对MTC分组中的组成员进行安全管理，并保证MTC分组于网络之间的安全通信。
本领域普通技术人员可以理解上述实施例的全部或部分步骤可以使用计算机程序流程来实现，所述计算机程序可以存储于一计算机可读存储介质中，所述计算机程序在相应的硬件平台上(如系统、设备、装置、器件等)执行，在执行时，包括方法实施例的步骤之一或其组合。
可选地，上述实施例的全部或部分步骤也可以使用集成电路来实现，这些步骤可以被分别制作成一个个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
上述实施例中的各装置/功能模块/功能单元可以采用通用的计算装置来实现，它们可以集中在单个的计算装置上，也可以分布在多个计算装置所组成的网络上。
上述实施例中的各装置/功能模块/功能单元以软件功能模块的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。上述提到的计算机可读取存储介质可以是只读存储器，磁盘或光盘等。
任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应以权利要求所述的保护范围为准。
工业实用性
本发明实施例提供的MTC分组管理方法、装置及系统，网络实体，能够实现对MTC设备分组和MTC应用分组进行管理，从而保障MTC设备分组和MTC应用分组与网络之间的通信安全。

Claims (13)

  1. 一种MTC分组管理方法，包括：
    网络实体创建用于标记每个MTC分组的唯一MTC分组标识，并生成对应于所述MTC分组标识的唯一MTC分组密钥，其中，所述网络实体是核心网中能够用于管理MTC分组的通信实体；
    所述网络实体根据所述MTC分组标识与所述MTC分组密钥，创建一个MTC对象为空或者非空的MTC分组；
    所述网络实体使用所述MTC分组标识与所述MTC分组密钥，对所述MTC分组执行管理操作，其中，所述管理操作包括：MTC对象注册操作。
  2. 根据权利要求1所述的方法，其中，所述网络实体使用所述MTC分组标识与所述MTC分组密钥，对所述MTC分组执行MTC对象注册操作，包括：
    所述网络实体接收请求注册的MTC对象发送的用于申请加入所述MTC分组的注册请求，其中，所述注册请求包括所述请求注册的MTC对象的身份信息和所述MTC分组标识；
    所述网络实体对所述请求注册的MTC对象的身份信息进行鉴权，在鉴权通过后，将所述请求注册的MTC对象添加到所述MTC分组；
    所述网络实体建立所述MTC分组标识与所述请求注册的MTC对象的身份信息之间的关联关系；
    所述网络实体将所述MTC分组密钥分发给所述请求注册的MTC对象，或者将所述MTC分组标识和所述MTC分组密钥分发给所述请求注册的MTC对象。
  3. 根据权利要求1所述的方法，其中，
    所述管理操作还包括：MTC对象删除操作；
    所述网络实体使用所述MTC分组标识与所述MTC分组密钥，对所述MTC分组执行MTC对象删除操作，包括：
    所述网络实体接收请求删除的MTC对象发送的用于申请从所述MTC分 组中删除的删除请求，其中，所述删除请求包括所述请求删除的MTC对象的身份信息和所述MTC分组标识；
    所述网络实体对所述请求删除的MTC对象的身份信息进行鉴权，在鉴权通过后，将所述请求删除的MTC对象从所述MTC分组中删除；
    所述网络实体删除所述MTC分组标识与所述请求删除的MTC对象的身份信息之间的关联关系。
  4. 根据权利要求1所述的方法，其中，
    所述管理操作还包括：MTC分组密钥更新操作；
    所述网络实体使用所述MTC分组标识与所述MTC分组密钥，对所述MTC分组执行MTC分组密钥更新操作，包括：
    所述网络实体向所述MTC分组的每个MTC对象发送携带有所述MTC分组密钥的密钥更新通知消息，使得所述MTC对象对所述密钥更新通知消息进行鉴权，在鉴权通过后，所述网络实体将更新后的MTC分组密钥下发给所述MTC分组的每个MTC对象。
  5. 根据权利要求1至4中任一项所述的方法，其中，所述网络实体包括以下之一：
    移动管理实体MME、服务GPRS支持节点SGSN、MTC业务管理平台、归属用户服务器HSS、MTC互通功能MTC-IWF；
    所述MTC对象包括：MTC设备和/或MTC应用。
  6. 一种MTC分组管理装置，位于网络实体，所述网络实体是核心网中能够用于管理MTC分组的通信实体，所述装置包括：
    处理模块，设置为创建用于标记每个MTC分组的唯一MTC分组标识，并生成对应于所述MTC分组标识的唯一MTC分组密钥；
    创建模块，设置为根据所述MTC分组标识与所述MTC分组密钥，创建一个MTC对象为空或者非空的MTC分组；
    管理模块，设置为使用所述MTC分组标识与所述MTC分组密钥，对所述MTC分组执行管理操作，其中，所述管理操作包括：MTC对象注册操作。
  7. 根据权利要求6所述的装置，其中，所述管理模块包括：
    第一接收单元，设置为接收请求注册的MTC对象发送的用于申请加入所述MTC分组的注册请求，其中，所述注册请求包括所述请求注册的MTC对象的身份信息和所述MTC分组标识；
    第一处理单元，设置为对所述请求注册的MTC对象的身份信息进行鉴权，在鉴权通过后，将所述请求注册的MTC对象添加到所述MTC分组；
    建立单元，设置为建立所述MTC分组标识与所述请求注册的MTC对象的身份信息之间的关联关系；
    分发单元，设置为将所述MTC分组密钥，或者将所述MTC分组标识和所述MTC分组密钥分发给所述请求注册的MTC对象。
  8. 根据权利要求6所述的装置，其中，
    所述管理操作还包括：MTC对象删除操作；
    所述管理模块包括：
    第二接收单元，设置为接收请求删除的MTC对象发送的用于申请从所述MTC分组中删除的删除请求，其中，所述删除请求包括所述请求删除的MTC对象的身份信息和所述MTC分组标识；
    删除单元，设置为删除所述MTC分组标识与所述请求删除的MTC对象的身份信息之间的关联关系。
  9. 根据权利要求6所述的装置，其中，
    所述管理操作还包括：MTC分组密钥更新操作；
    所述管理模块包括：
    第二处理单元，设置为向所述MTC分组的每个MTC对象发送携带有所述MTC分组密钥的密钥更新通知消息，使得所述MTC对象对所述密钥更新通知消息进行鉴权，在鉴权通过后，所述网络实体将更新后的MTC分组密钥下发给所述MTC分组的每个MTC对象。
  10. 根据权利要求6至9中任一项所述的装置，其中，所述网络实体包括以下之一：
    移动管理实体MME、服务GPRS支持节点SGSN、MTC业务管理平台、归属用户服务器HSS、MTC互通功能MTC-IWF；
    所述MTC对象包括：MTC设备和/或MTC应用。
  11. 一种网络实体，包括：权利要求6至10中任一项所述的MTC分组管理装置。
  12. 一种MTC分组管理系统，包括：权利要求13所述的网络实体、MTC设备和/或MTC应用，其中，
    所述MTC设备和/或所述MTC应用，设置为向所述网络实体发送请求加入一个MTC分组的注册请求或请求从MTC分组中删除的删除请求；
    所述MTC设备和/或所述MTC应用，还设置为接收所述网络实体发送的请求加入的一个MTC分组的MTC分组密钥和/或MTC分组标识，并保存所述MTC分组密钥和/或MTC分组标识；
    所述MTC设备和/或所述MTC应用，还设置为存储请求加入或请求删除的一个MTC分组的MTC分组标识。
  13. 一种计算机可读存储介质，所述存储介质存储有计算机程序，该计算机程序包括程序指令，当该程序指令被MTC分组管理设备执行时，使得该设备可执行权利要求1-5任一项的方法。
PCT/CN2015/075073 2014-12-23 2015-03-25 一种mtc分组管理方法、装置及系统，网络实体 WO2016101429A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410812341.9 2014-12-23
CN201410812341.9A CN105792196B (zh) 2014-12-23 2014-12-23 一种mtc分组管理方法、装置及系统，网络实体

Publications (1)

Publication Number Publication Date
WO2016101429A1 true WO2016101429A1 (zh) 2016-06-30

Family

ID=56149049

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/075073 WO2016101429A1 (zh) 2014-12-23 2015-03-25 一种mtc分组管理方法、装置及系统，网络实体

Country Status (2)

Country Link
CN (1) CN105792196B (zh)
WO (1) WO2016101429A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020142970A1 (en) * 2019-01-10 2020-07-16 Telefonaktiebolaget Lm Ericsson (Publ) METHOD AND APPARATUS FOR MANAGING ONE OR MORE GROUPS OF MACHINE‐TYPE COMMUNICATION (MTC) DEVICES IN A CELLULAR NETWORk

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111586593B (zh) * 2019-02-18 2021-12-07 成都鼎桥通信技术有限公司 临时组呼的发起方法、装置及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102457844A (zh) * 2010-10-28 2012-05-16 中兴通讯股份有限公司 一种m2m组认证中组密钥管理方法及系统
CN102469455A (zh) * 2010-11-08 2012-05-23 中兴通讯股份有限公司 基于通用引导架构的机器类通信设备分组管理方法及系统
WO2014183569A1 (zh) * 2013-10-25 2014-11-20 中兴通讯股份有限公司 一种实现机器类通信设备间安全通信的方法及网络实体

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102457844A (zh) * 2010-10-28 2012-05-16 中兴通讯股份有限公司 一种m2m组认证中组密钥管理方法及系统
CN102469455A (zh) * 2010-11-08 2012-05-23 中兴通讯股份有限公司 基于通用引导架构的机器类通信设备分组管理方法及系统
WO2014183569A1 (zh) * 2013-10-25 2014-11-20 中兴通讯股份有限公司 一种实现机器类通信设备间安全通信的方法及网络实体

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020142970A1 (en) * 2019-01-10 2020-07-16 Telefonaktiebolaget Lm Ericsson (Publ) METHOD AND APPARATUS FOR MANAGING ONE OR MORE GROUPS OF MACHINE‐TYPE COMMUNICATION (MTC) DEVICES IN A CELLULAR NETWORk

Also Published As

Publication number Publication date
CN105792196B (zh) 2020-06-16
CN105792196A (zh) 2016-07-20

Similar Documents

Publication Publication Date Title
US10972463B2 (en) Blockchain-based NB-IoT devices
US11411963B2 (en) Network access sharing
CN107579958B (zh) 数据管理方法、装置及系统
US10454909B2 (en) Key negotiation method and system, network entity and computer storage medium
CN111338906B (zh) 终端设备、边缘节点及基于区块链的应用监管方法和系统
CN109561429B (zh) 一种鉴权方法及设备
CN111355986B (zh) 一种直播间中的消息处理方法、装置和存储介质
EP4044512A1 (en) Data sharing method, device, and system
WO2019162563A1 (en) Profile information sharing
WO2015154459A1 (zh) 订阅资源变更通知的方法及装置
WO2014079019A1 (zh) 一种机器通信中群组管理的方法和装置
WO2015117446A1 (zh) 控制资源变更通知消息发送方法及装置
WO2022222745A1 (zh) 一种通信方法及装置
CN111095904A (zh) 通信网络中的服务层消息模板
CN103812672A (zh) 一种新增网元设备的发现方法、相关设备及系统
WO2016101429A1 (zh) 一种mtc分组管理方法、装置及系统，网络实体
CN112492592A (zh) 一种多个nrf场景下的授权方法
WO2015184870A1 (zh) 分组通信管理方法、装置和系统
CN113099449B (zh) 分布式核心网的鉴权方法和系统、归属签约用户服务器
CN106162515B (zh) 一种机器类通信安全通信的方法、装置和系统
CN104469770A (zh) 面向第三方应用的wlan认证方法、平台和系统
CN104080087A (zh) 一种视频监控系统的无线接入方法及装置
WO2016197783A2 (zh) 控制消息的发送方法及装置
US20220215038A1 (en) Distributed storage of blocks in blockchains
US10187866B2 (en) Registering, deregistering and standby processing methods and systems for terminal peripheral

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15871507

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15871507

Country of ref document: EP

Kind code of ref document: A1