Communication method and communication device

Abstract

The invention provides a communication method and a communication device, and the method comprises the steps: a first device sends an identifier of a first device group to at least one second device in a coverage range of the first device, the first device is a device with a reading and / or writing function, and the second device is an Internet of Things device; receiving an identifier of the device group sent by the second device; determining that the identifier of the device group sent by the second device corresponds to the identifier of the first device group; and executing an operation corresponding to the identifier of the first device group on the second device. By sending the identifier of the first device group to the at least one device, the Internet of Things management function network element can operate the at least one device corresponding to the identifier of the first device group and the identifier of the belonging device group, so that the signaling overhead can be saved.

Description

Technical Field

[0001] The present application relates to the field of communications, and more specifically, to a communication method and a communication device. Background Art

[0002] The passive internet of things (pIoT), also known as the ambient internet of things (AIoT) or ambient power-enable internet of Things (AIoT), is an IoT device that can obtain energy from the external environment for communication. It has the characteristics of low cost, small size, easy deployment, and maintenance-free.

[0003] In the existing scheme, when the service requester needs to operate the IoT device, the service requester can send an operation instruction to the access network device through the core network, so that the access network device sends an access instruction to the IoT device according to the operation instruction, triggering the random access of the IoT device. When the IoT device is successfully randomly accessed, the access network device sends the above operation instruction to the IoT device, so that the IoT device performs the corresponding operation according to the operation instruction. Among them, the operation instruction can be, for example, an instruction to perform operations such as obtaining IoT device information, inventory operation, read operation, write operation, etc.

[0004] When a service requester needs to operate a group of IoT devices, according to the existing solution, the service requester sends multiple operation requests to the access network device through the core network, and then the access network device processes them one by one, executes the access process of each IoT device in a group of IoT devices, and sends the operation instructions to each IoT device respectively. Subsequently, the access network device sends the information of the IoT device to the service requester. The existing solution for operating IoT devices at the group granularity may bring large signaling overhead. Summary of the invention

[0005] The present application provides a communication method and a communication device, which can save signaling overhead when operating Internet of Things devices at a group granularity.

[0006] In a first aspect, a communication method is provided. The method can be executed by an Internet of Things management function network element, or can also be executed by a chip or circuit used for an Internet of Things management function network element, and the present application does not limit this.

[0007] The method includes: sending an identifier of a first device group to at least one second device within the coverage of the first device through a first device, the first device is a device with a read and / or write function, or is called a reader, and the second device is an Internet of Things device; receiving the identifier of the device group sent by the second device; determining that the identifier of the device group sent by the second device corresponds to the identifier of the first device group; and performing an operation corresponding to the identifier of the first device group on the second device.

[0008] Based on the above scheme, by sending the identifier of the first device group to at least one device, and receiving the identifier of the device group to which any device in the at least one device (for example, the second device) belongs when the identifier of the first device group corresponds to the identifier of the device group to which the second device belongs, the Internet of Things management function network element can operate the second device according to the identifier of the first device group, that is, the Internet of Things management function network element can operate at least one device whose identifier of the device group corresponds to the identifier of the first device group, thereby saving signaling overhead.

[0009] In combination with the first aspect, in certain implementations of the first aspect, before receiving the identifier of the device group sent by the second device, a registration request sent by the second device is received, the registration request including the identifier of the second device; the identifier of the device group to which the second device belongs is determined based on the identifier of the second device; and the identifier of the device group to which the second device belongs is sent to the second device.

[0010] Based on the above scheme, the identifier of the device group to which the second device belongs can be determined based on the identifier of the second device in the registration request initiated by the second device, and the identifier of the device group to which the second device belongs is sent to the second device so that the second device can determine whether the identifier of the device group to which it belongs corresponds to the identifier of the first device group.

[0011] In combination with the first aspect, in certain implementations of the first aspect, before receiving the identifier of the device group sent by the second device, a first indication message sent by the first network element is received, the first indication message carrying the identifier of the device group to which the second device belongs and the identifier of the device in the device group to which the second device belongs, the first indication message indicating a first process for triggering the devices in the device group to which the second device belongs; in the first process, the identifier of the device group to which the second device belongs is sent to the second device.

[0012] Based on the above scheme, the first process of the second device can be initiated based on the first indication information, and the identifier of the device group to which the second device belongs can be sent to the second device in the first process, so that the second device determines whether the identifier of the device group to which it belongs corresponds to the identifier of the first device group.

[0013] In combination with the first aspect, in some implementations of the first aspect, the first process includes any one of the following processes: a registration process, an inventory process, a write process, or a configuration update process. The registration process is a process for the second device to register with the core network, which may include a registration process actively triggered by the second device (device triggered registration procedure) and a registration process triggered by the network (network triggered registration procedure).

[0014] In combination with the first aspect, in certain implementations of the first aspect, when the first process is a registration process, before sending the identifier of the device group to which the second device belongs to the second device, second indication information is sent to the first device according to the first indication information, and the second indication information indicates triggering random access of the second device; a registration request sent by the second device is received, and the registration request includes the identifier of the second device; in response to the registration request, a registration acceptance message is sent to the second device, and the registration acceptance message carries the identifier of the device group to which the second device belongs.

[0015] In combination with the first aspect, in certain implementations of the first aspect, the first network element includes a network open function network element, which receives device group registration information sent by an application server, and the device group registration information carries an identifier of the device group to which the second device belongs and an identifier of a device in the device group to which the second device belongs; the network open function network element sends the first indication information based on the device group registration information.

[0016] In combination with the first aspect, in certain implementations of the first aspect, the network open function network element sends the device group registration information to the data management network element, and the device group registration information includes an identifier of the device group to which the second device belongs and an identifier of a device in the device group to which the second device belongs.

[0017] In certain implementations of the first aspect, the application function network element directly sends the device group registration information to the data management network element, where the device group registration information includes an identifier of the device group to which the second device belongs and an identifier of the device in the device group to which the second device belongs; the data management network element stores the identifier of the device group to which the second device belongs and the identification information of the device in the device group to which the second device belongs.

[0018] In combination with the first aspect, in certain implementations of the first aspect, a query message is sent to the data management network element, the query message carrying an identifier of the second device; and an identifier of the device group to which the second device belongs, sent by the data management network element, is received, wherein the identifier of the device group to which the second device belongs is determined based on the identifier of the second device and the registration information of the device group.

[0019] In combination with the first aspect, in certain implementations of the first aspect, before performing an operation corresponding to the identifier of the first device group on the second device, it is determined whether the identifier of the device group to which the second device belongs corresponds to the identifier of the first device group; when the identifier of the device group to which the second device belongs corresponds to the device group identifier in the operation request, the operation corresponding to the identifier of the first device group is performed on the second device.

[0020] In combination with the first aspect, in certain implementations of the first aspect, before performing an operation corresponding to the identifier of the first device group on the second device, the device group registration information is obtained from the data management network element; and based on the device group registration information, it is determined whether the identifier of the second device corresponds to the identifier of the device group to which the second device belongs.

[0021] In combination with the first aspect, in certain implementations of the first aspect, the identifier of the first device group may come from a service request sent by the application function server; or it may come from the corresponding first device group identifier in an operation pre-configured by a core network element, such as a periodic inventory operation.

[0022] In combination with the first aspect, in certain implementations of the first aspect, the operation corresponding to the identifier of the first device group may come from a service request sent by the application function server, or from an operation pre-configured by a core network element, such as a periodic inventory operation, or from the corresponding operation of the first device group in the device group registration information.

[0023] In combination with the first aspect, in some implementations of the first aspect, identification information allocated to the second device by the core network is sent to the second device, where the identification information includes an identifier of a device group to which the second device belongs.

[0024] Exemplarily, the identification information is sent via a non-access stratum (NAS) message.

[0025] In combination with the first aspect, in some implementations of the first aspect, the identification information is any one of the following: a globally unique temporary identifier (GUTI), a temporary mobile subscription identifier (TMSI), an international mobile subscriber identity (IMSI), a special passive IoT device identifier (such as TagID, TID), an electronic product code (EPC), other user equipment identifiers, for example, a subscription permanent identifier (SUPI), a subscription concealed identifier (SUCI), a generic public subscription identifier (GPSI, etc. Among them, the TMSI can be 5G-S-TMSI, 5G-TMSI, SAE temporary mobile subscription identifier (SAE-temporary mobile subscription identifier, S-TMSI), a truncated 5G-S-TMSI (Truncated5G-S-TMSI) or a temporary mobile subscription identifier of 6G and future versions, etc.

[0026] Exemplarily, the identification information is sent via radio resource control (RRC) signaling.

[0027] In combination with the first aspect, in some implementations of the first aspect, the identification information may be a radio network temporary identifier (RNTI). The RNTI may be an inactive radio network temporary identifier (I-RNTI), a cell radio network temporary identifier (C-RNTI), or a 6G and future versions of a radio network temporary identifier.

[0028] In combination with the first aspect, in some implementations of the first aspect, identification information of a device group to which the second device belongs is sent to the second device.

[0029] Exemplarily, the identification information is sent via a NAS message.

[0030] Alternatively, the identification information is sent via RRC signaling.

[0031] In a second aspect, a communication method is provided. The method may be executed by a second device, or may be executed by a chip or circuit used for the second device, and the present application does not limit this.

[0032] The method includes: a second device receives an identifier of a first device group sent by an Internet of Things management function network element through a first device, the first device is a device with a read and / or write function, and the second device is an Internet of Things device; the second device determines that the identifier of the first device group corresponds to the identifier of the device group to which the second device belongs; the second device sends the identifier of the device group to which the second device belongs to the Internet of Things management function network element, and the identifier of the device group to which the second device group belongs is used to determine whether to perform an operation corresponding to the identifier of the first device group on the second device.

[0033] Based on the above scheme, by receiving the identifier of the first device group from the Internet of Things management function network element, and when the identifier of the first device group corresponds to the identifier of the device group to which the second device belongs, sending the identifier of the device group to which the second device belongs to the Internet of Things management function network element, the Internet of Things management function network element can operate the second device according to the identifier of the first device group, that is, the Internet of Things management function network element can operate at least one device whose identifier of the device group corresponds to the identifier of the first device group, thereby saving signaling overhead.

[0034] In conjunction with the second aspect, in certain implementations of the second aspect, before the second device sends the identifier of the device group to which the second device belongs to the Internet of Things management function network element, the second device receives the identifier of the device group to which the second device belongs, which is sent by the Internet of Things management function network element, and the identifier of the device group to which the second device belongs corresponds to the identifier of the second device. The identifier of the device group to which the second device belongs can be obtained through a user equipment configuration update process, or can be obtained through other downlink NAS messages.

[0035] In combination with the second aspect, in certain implementations of the second aspect, before the second device sends the identifier of the device group to which the second device belongs to the Internet of Things management function network element, the second device sends a registration request to the Internet of Things management function network element, and the registration request includes the identifier of the second device; the second device receives the identifier of the device group to which the second device belongs sent by the Internet of Things management function network element, and the identifier of the device group to which the second device belongs corresponds to the identifier of the second device.

[0036] In combination with the second aspect, in certain implementations of the second aspect, in the first process, the second device receives an identifier of a device group to which the second device belongs, which is sent by the Internet of Things management function network element.

[0037] In combination with the second aspect, in some implementations of the second aspect, the first process includes any one of the following processes: a registration process, an inventory process, a write process, or a configuration update process.

[0038] In combination with the second aspect, in certain implementation methods of the second aspect, when the first process is a registration process, before the second device receives the identifier of the device group to which the second device belongs sent by the Internet of Things management function network element, the second device receives a random access request sent by the first device; performs a random access process with the first device according to the random access request; the second device sends a registration request to the Internet of Things management function network element in the random access process, and the registration request includes the identifier of the second device; the second device receives a registration acceptance message sent by the Internet of Things management function network element, and the registration acceptance message carries the identifier of the device group to which the second device belongs.

[0039] In combination with the second aspect, in certain implementations of the second aspect, the second device receives identification information assigned to the second device by the core network and sent by the Internet of Things management function network element, and the identification information includes an identification of the device group to which the second device belongs.

[0040] Exemplarily, the identification information is received via a NAS message.

[0041] In combination with the second aspect, in some implementations of the second aspect, the identification information is any one of the following: GUTI, TMSI, IMSI, TID, EPC, other user equipment identifiers, for example, SUPI, SUCI, GPSI, etc. Among them, the TMSI can be 5G-S-TMSI, 5G-TMSI, S-TMSI, Truncated 5G-S-TMSI, or a temporary mobile subscription identifier of 6G and future versions.

[0042] Exemplarily, the identification information is received via RRC signaling.

[0043] In conjunction with the second aspect, in some implementations of the second aspect, the identification information may be an RNTI, wherein the RNTI may be an I-RNTI, a C-RNTI, or a wireless network temporary identifier of 6G and future versions.

[0044] In combination with the second aspect, in some implementations of the second aspect, identification information of a device group to which the second device belongs is received.

[0045] Exemplarily, the identification information is received via a NAS message.

[0046] Alternatively, the identification information is received via RRC signaling.

[0047] In a third aspect, a communication method is provided. The method may be executed by a first device, or may be executed by a chip or circuit used for the first device, and the present application does not limit this.

[0048] The method includes: sending an identifier of a first device group to at least one second device, the second device being an Internet of Things device; receiving an identifier of a device group to which the second device belongs, which is sent by the second device; sending an identifier of the device group to which the second device belongs to an Internet of Things management function network element, so that the Internet of Things management function network element determines whether the identifier of the device group to which the second device belongs corresponds to the identifier of the first device group; and sending an operation instruction to the second device for executing an operation corresponding to the identifier of the first device group on the second device.

[0049] Based on the above scheme, by sending the identifier of the first Internet of Things device group to at least one device, and receiving the identifier information from the device group corresponding to the second device when the identifier of the first Internet of Things device group corresponds to the identifier of the device group corresponding to any device in the at least one device (for example, the second device), the Internet of Things management function network element can operate the second device according to the identifier of the device group corresponding to the second device, that is, the Internet of Things management function network element can operate at least one device whose device group identifier corresponds to the identifier of the first Internet of Things device group, thereby saving signaling overhead.

[0050] In combination with the third aspect, in certain implementations of the third aspect, before receiving the identifier of the device group sent by the second device, a registration request sent by the second device is received, the registration request including the identifier of the second device; the registration request is sent to an Internet of Things management function network element; the identifier of the device group to which the second device belongs, sent from the Internet of Things management function network element, is received, and the identifier of the device group to which the second device belongs is determined based on the identifier of the second device; and the identifier of the device group to which the second device belongs is sent to the second device.

[0051] In combination with the third aspect, in certain implementations of the third aspect, before receiving the identifier of the device group sent by the second device, a second indication message sent by the Internet of Things management function network element is received, and the second indication message triggers random access of the second device; according to the second indication message, a random access indication, a paging message or a select message is sent to the second device, and the random access indication, the paging message or the select message carries the identifier of the device group to which the second device belongs.

[0052] In combination with the third aspect, in certain implementations of the third aspect, a registration request sent by the second device is received, the registration request including an identifier of the second device; a registration acceptance message is sent to the second device, the registration acceptance message carrying an identifier of the device group to which the second device belongs.

[0053] In combination with the third aspect, in certain implementations of the third aspect, identification information allocated to the second device by the core network is sent to the second device, and the identification information includes an identifier of a device group to which the second device belongs.

[0054] Exemplarily, the identification information is sent via a NAS message.

[0055] In combination with the third aspect, in some implementations of the third aspect, the identification information is any one of the following: GUTI, TMSI, IMSI, TID, EPC, other user equipment identifiers, for example, SUPI, SUCI, GPSI, etc. Among them, TMSI can be 5G-S-TMSI, 5G-TMSI, S-TMSI, Truncated 5G-S-TMSI, or a temporary mobile subscription identifier of 6G and future versions.

[0056] Exemplarily, the identification information is sent via RRC signaling.

[0057] In conjunction with the third aspect, in certain implementations of the third aspect, the identification information may be an RNTI, wherein the RNTI may be an I-RNTI, a C-RNTI, or a wireless network temporary identifier of 6G and future versions.

[0058] In combination with the third aspect, in some implementations of the third aspect, identification information of the device group to which the second device belongs is sent.

[0059] Exemplarily, the identification information is sent via a NAS message.

[0060] Alternatively, the identification information is sent via RRC signaling.

[0061] In a fourth aspect, a communication method is provided. The method may be executed by a data management network element, or may be executed by a chip or circuit used for a data management network element, and the present application does not limit this.

[0062] The method includes: receiving device group registration information from a first network element, the device group registration information including an identifier of a device group to which the second device belongs and an identifier of a device in the device group to which the second device belongs; receiving a query message from an Internet of Things management function network element, the query message carrying an identifier of the second device; determining an identifier of the device group to which the second device belongs based on the identifier of the second device and the device group registration information, and sending the identifier of the device group to which the second device belongs to the Internet of Things management function network element.

[0063] In combination with the fourth aspect, in certain implementations of the fourth aspect, the device group registration information is sent to an Internet of Things management function network element, and the device group registration information is used by the Internet of Things management function network element to determine whether the identifier of the second device corresponds to the identifier of the device group to which the second device belongs.

[0064] In a fifth aspect, a communication method is provided. The method can be executed by an Internet of Things management function network element, or can also be executed by a chip or circuit used for an Internet of Things management function network element. This application does not limit this.

[0065] The method includes: sending, through a first device, an identification of a second device to at least one second device within a service range of the first device; wherein the identification of the second device includes an identification of a device group to which the second device belongs, the first device is a device with read and / or write functions, and the second device is an Internet of Things device.

[0066] Based on the above solution, by sending the identifier of the device group to which the second device belongs to at least one second device, the second device obtains the corresponding device group identifier, enabling the core network to perform group operations on the at least one second device.

[0067] In combination with the fifth aspect, in certain implementations of the fifth aspect, before sending the identifier of each second device to at least one second device within a service range of the first device through the first device, the identifier of the device group to which the second device belongs is obtained.

[0068] In conjunction with the fifth aspect, in certain implementations of the fifth aspect, an identifier of a device group to which the second device belongs and stored in the data management network element is obtained from the data management network element. Exemplarily, the data management network element may obtain the identifier of the device group to which the second device belongs through an application function network element, or obtain the identifier of the device group to which the second device belongs through other core network network elements (such as a network open function network element or other Internet of Things functions).

[0069] In combination with the fifth aspect, in certain implementations of the fifth aspect, first indication information sent by a first network element is received, the first indication information carrying an identifier of a device group to which the second device belongs and an identifier of a device in the device group to which the second device belongs, and the first indication information indicates a first process for triggering a device in the device group to which the second device belongs; in the first process, the identifier of the device group to which the second device belongs is sent to the second device.

[0070] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the first process includes any one of the following processes: a registration process, an inventory process, a write process, or a configuration update process. The registration process is a process for the second device to register with the core network, which may include a registration process actively triggered by the second device and a registration process triggered by the network.

[0071] In combination with the fifth aspect, in certain implementations of the fifth aspect, when the registration process is a registration process, before sending the identifier of the device group to which the second device belongs to the second device, second indication information is sent to the first device according to the first indication information, and the second indication information indicates triggering random access of the second device; a registration request sent by the second device is received, and the registration request includes the identifier of the second device; in response to the registration request, a registration acceptance message is sent to the second device, and the registration acceptance message carries the identifier of the device group to which the second device belongs.

[0072] In combination with the fifth aspect, in certain implementations of the fifth aspect, the device group identifier to which the second device belongs may be sent via a NAS message.

[0073] Exemplarily, the NAS message may be a registration accept, a service request, a downlink NAS message, a UE configuration update command, a write service request, an information interaction operation with an IoT device, etc.

[0074] In combination with the fifth aspect, in certain implementations of the fifth aspect, the NAS message may carry identification information allocated by the core network to the second device, where the identification information includes an identifier of a device group to which the second device belongs.

[0075] In combination with the fifth aspect, in some implementations of the fifth aspect, the identification information is any one of the following: GUTI, TMSI, IMSI, TID, EPC, other user equipment identifiers, for example, SUPI, SUCI, GPSI, etc. Among them, TMSI can be 5G-S-TMSI, 5G-TMSI, S-TMSI, Truncated 5G-S-TMSI, or a temporary mobile subscription identifier of 6G and future versions.

[0076] In combination with the fifth aspect, in certain implementations of the fifth aspect, the NAS message may directly carry identification information allocated by the core network to the second device.

[0077] In combination with the fifth aspect, in certain implementations of the fifth aspect, the device group identifier of the second device may be sent via an RRC message.

[0078] In conjunction with the fifth aspect, in certain implementations of the fifth aspect, the identification information may be an RNTI, wherein the RNTI may be an I-RNTI, a C-RNTI, or a wireless network temporary identifier of 6G and future versions.

[0079] In combination with the fifth aspect, in certain implementations of the fifth aspect, indication information is received from an application function network element, wherein the indication information indicates that an operation corresponding to the first device group is to be performed on a device corresponding to an identifier of the first device group; the identifier of the first device group is sent to the at least one second device through the first device according to the indication information; the identifier of the device group to which the second device belongs is received from the second device, and when the identifier of the device group to which the second device belongs corresponds to the identifier of the first device group, the operation corresponding to the first device group is performed on the second device.

[0080] In combination with the fifth aspect, in some implementations of the fifth aspect, before sending an identifier of the device group to which the second device belongs to at least one second device within the coverage of the first device, a mask is sent to the at least one second device within the coverage of the first device.

[0081] In combination with the fifth aspect, in certain implementations of the fifth aspect, device group registration information is received from the first network element, the device group registration information including an identifier of the device group to which the second device belongs and an identifier of a device in the device group to which the second device belongs, the device group registration information also including a network identifier to which the second device belongs, such as a PLMN identifier, an NID, etc., a user identifier to which the second device belongs (such as an AF identifier or an identifier of a service requester, etc.), and a serial number of the second device (such as an EPC code); a mask is constructed using the network identifier to which the second device belongs, the user identifier to which the second device belongs, and the serial number of the second device.

[0082] In a sixth aspect, a communication device is provided, which includes a transceiver unit and a processing unit, wherein the transceiver unit is used to send an identifier of a first device group to at least one second device within the coverage range of the first device through a first device, the first device is a device with read and / or write functions, or called a reader, and the second device is an Internet of Things device; the transceiver unit is also used to receive the identifier of the device group sent by the second device; determine that the identifier of the device group sent by the second device corresponds to the identifier of the first device group; and the processing unit is used to perform an operation corresponding to the identifier of the first device group on the second device.

[0083] In combination with the sixth aspect, in certain implementations of the sixth aspect, the transceiver unit is also used to receive a registration request sent by the second device, the registration request including an identifier of the second device; the processing unit is also used to determine an identifier of the device group to which the second device belongs based on the identifier of the second device; the transceiver unit is also used to send the identifier of the device group to which the second device belongs to the second device.

[0084] In combination with the sixth aspect, in certain implementations of the sixth aspect, the transceiver unit is also used to receive first indication information sent by the first network element, the first indication information carries an identifier of the device group to which the second device belongs and an identifier of a device in the device group to which the second device belongs, and the first indication information indicates a first process for triggering the device in the device group to which the second device belongs; the transceiver unit is also used to send the identifier of the device group to which the second device belongs to the second device in the first process.

[0085] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the first process includes any one of the following processes: a registration process, an inventory process, a write process, or a configuration update process. The registration process is a process for the second device to register with the core network, which may include a registration process actively triggered by the second device and a registration process triggered by the network.

[0086] In combination with the sixth aspect, in certain implementations of the sixth aspect, when the first process is a registration process, the transceiver unit is also used to send second indication information to the first device based on the first indication information, and the second indication information indicates triggering random access of the second device; the transceiver unit is also used to receive a registration request sent by the second device, and the registration request includes an identifier of the second device; the transceiver unit is also used to send a registration acceptance message to the second device in response to the registration request, and the registration acceptance message carries the identifier of the device group to which the second device belongs.

[0087] In combination with the sixth aspect, in certain implementations of the sixth aspect, the first network element includes a network open function network element, which receives device group registration information sent by an application server, the device group registration information carries an identifier of the device group to which the second device belongs and an identifier of a device in the device group to which the second device belongs; the network open function network element sends the first indication information based on the device group registration information.

[0088] In combination with the sixth aspect, in certain implementations of the sixth aspect, the network open function network element sends the device group registration information to the data management network element, and the device group registration information includes the identifier of the device group to which the second device belongs and the identifier of the device in the device group to which the second device belongs.

[0089] In combination with the sixth aspect, in certain implementations of the sixth aspect, the transceiver unit is also used to send a query message to the data management network element, and the query message carries an identifier of the second device; the transceiver unit is also used to receive the identifier of the device group to which the second device belongs, which is sent by the data management network element, and the identifier of the device group to which the second device belongs is determined based on the identifier of the second device and the registration information of the device group.

[0090] In combination with the sixth aspect, in certain implementations of the sixth aspect, the processing unit is also used to determine whether the identifier of the device group to which the second device belongs corresponds to the identifier of the first device group; the processing unit is specifically used to perform the operation corresponding to the identifier of the first device group on the second device when the identifier of the device group to which the second device belongs corresponds to the identifier of the device group in the operation request.

[0091] In combination with the sixth aspect, in certain implementations of the sixth aspect, the transceiver unit is also used to obtain the device group registration information from the data management network element; the processing unit is specifically used to determine whether the identifier of the second device corresponds to the identifier of the device group to which the second device belongs based on the device group registration information.

[0092] In combination with the sixth aspect, in certain implementations of the sixth aspect, the identifier of the first device group may come from a service request sent by the application function server; it may also come from the corresponding first device group identifier in the pre-configured operation of the core network network element, such as a periodic inventory operation.

[0093] In combination with the sixth aspect, in certain implementations of the sixth aspect, the operation corresponding to the identifier of the first device group may come from a service request sent by the application function server, or from an operation pre-configured by a core network element, such as a periodic inventory operation, or from the corresponding operation of the first device group in the device group registration information.

[0094] In combination with the sixth aspect, in certain implementations of the sixth aspect, the transceiver unit is specifically used to send identification information allocated by the core network to the second device to the second device, and the identification information includes an identification of the device group to which the second device belongs.

[0095] The identification information and the method for sending the identification information may refer to the description in the first aspect.

[0096] In the seventh aspect, a communication device is provided, which includes a transceiver unit and a processing unit, the transceiver unit is used to receive the identifier of a first device group sent by an Internet of Things management function network element through a first device, the first device is a device with read and / or write functions, and the second device is an Internet of Things device; the processing unit is used to determine that the identifier of the first device group corresponds to the identifier of the device group to which the second device belongs; the transceiver unit is also used to send the identifier of the device group to which the device belongs to the Internet of Things management function network element, and the identifier of the device group to which the device belongs is used to determine whether to perform an operation corresponding to the identifier of the first device group on the device.

[0097] In conjunction with the seventh aspect, in certain implementations of the seventh aspect, the transceiver unit is further configured to receive an identifier of a device group to which the device belongs, sent by the Internet of Things management function network element, and the identifier of the device group to which the device belongs corresponds to the identifier of the device. The identifier of the device group to which the device belongs can be obtained through a user equipment configuration update process or through other downlink NAS messages.

[0098] In combination with the seventh aspect, in certain implementations of the seventh aspect, the transceiver unit is also used to send a registration request to the Internet of Things management function network element, and the registration request includes an identifier of the second device; the transceiver unit is also used to receive an identifier of the device group to which the device belongs, which is sent by the Internet of Things management function network element, and the identifier of the device group to which the device belongs corresponds to the identifier of the device.

[0099] In combination with the seventh aspect, in certain implementations of the seventh aspect, the transceiver unit is specifically used to receive, in the first process, an identifier of the device group to which the device belongs, which is sent by the Internet of Things management function network element.

[0100] In combination with the seventh aspect, in certain implementations of the seventh aspect, the first process includes any one of the following processes: a registration process, an inventory process, a write process, or a configuration update process.

[0101] In combination with the seventh aspect, in certain implementation methods of the seventh aspect, when the first process is a registration process, the transceiver unit is also used to receive a random access request sent by the first device; the processing unit is also used to execute a random access process with the first device according to the random access request; the transceiver unit is also used to send a registration request to the Internet of Things management function network element in the random access process, and the registration request includes an identifier of the device; the transceiver unit is also used to receive a registration acceptance message sent by the Internet of Things management function network element, and the registration acceptance message carries the identifier of the device group to which the device belongs.

[0102] In combination with the seventh aspect, in certain implementations of the seventh aspect, the transceiver unit is specifically used to receive identification information assigned to the device by the core network and sent by the Internet of Things management function network element, and the identification information includes an identification of the device group to which the device belongs.

[0103] The identification information and the method for sending the identification information may refer to the description in the second aspect.

[0104] In an eighth aspect, a communication device is provided, which includes a transceiver unit, wherein the transceiver unit is used to send an identifier of a first device group to at least one second device, wherein the second device is an Internet of Things device; the transceiver unit is also used to receive an identifier of the device group to which the second device belongs, which is sent by the second device; the transceiver unit is also used to send the identifier of the device group to which the second device belongs to an Internet of Things management function network element, so that the Internet of Things management function network element determines whether the identifier of the device group to which the second device belongs corresponds to the identifier of the first device group; the transceiver unit is also used to send an operation instruction to the second device for performing an operation corresponding to the identifier of the first device group on the second device.

[0105] In combination with the eighth aspect, in certain implementations of the eighth aspect, the transceiver unit is also used to receive a registration request sent by the second device, the registration request including an identifier of the second device; and send the registration request to the Internet of Things management function network element; the transceiver unit is also used to receive an identifier of the device group to which the second device belongs, sent from the Internet of Things management function network element, and the identifier of the device group to which the second device belongs is determined based on the identifier of the second device; the transceiver unit is also used to send the identifier of the device group to which the second device belongs to the second device.

[0106] In combination with the eighth aspect, in certain implementations of the eighth aspect, the transceiver unit is also used to receive second indication information sent by the Internet of Things management function network element, and the second indication information triggers random access of the second device; the processing unit is also used to send a random access indication, a paging message or a selection message to the second device according to the second indication information, and the random access indication, the paging message or the selection message carries the identifier of the device group to which the second device belongs.

[0107] In combination with the eighth aspect, in certain implementations of the eighth aspect, the transceiver unit is also used to receive a registration request sent by the second device, the registration request including an identifier of the second device; the transceiver unit is also used to send a registration acceptance message to the second device, the registration acceptance message carries the identifier of the device group to which the second device belongs.

[0108] In combination with the eighth aspect, in certain implementations of the eighth aspect, the transceiver unit is further used to send identification information allocated by the core network to the second device to the second device, and the identification information includes an identification of the device group to which the second device belongs.

[0109] The identification information and the method for sending the identification information may refer to the description in the third aspect.

[0110] In a ninth aspect, a communication device is provided, which includes a transceiver unit and a processing unit, the transceiver unit being used to receive device group registration information from a first network element, the device group registration information including an identifier of the device group to which the second device belongs and an identifier of a device in the device group to which the second device belongs; the transceiver unit is also used to receive a query message from an Internet of Things management function network element, the query message carrying an identifier of the second device; the processing unit is used to determine an identifier of the device group to which the second device belongs based on the identifier of the second device and the device group registration information, and send the identifier of the device group to which the second device belongs to the Internet of Things management function network element.

[0111] In combination with the ninth aspect, in certain implementations of the ninth aspect, the transceiver unit is also used to send the device group registration information to the Internet of Things management function network element, so that the Internet of Things management function network element determines whether the identifier of the second device corresponds to the identifier of the device group to which the second device belongs based on the device group registration information.

[0112] In a tenth aspect, a communication device is provided, which includes a transceiver unit, and the transceiver unit is used to send an identification of a second device to at least one second device within a service range of the first device through a first device; wherein the identification of the second device includes an identification of a device group to which the second device belongs, the first device is a device with read and / or write functions, and the second device is an Internet of Things device.

[0113] In combination with the tenth aspect, in certain implementations of the tenth aspect, the transceiver unit is further used to obtain a device group identifier to which the second device belongs.

[0114] In conjunction with the tenth aspect, in certain implementations of the tenth aspect, the transceiver unit is specifically used to obtain from the data management network element an identifier of the device group to which the second device belongs, which is stored in the data management network element. Exemplarily, the data management network element may obtain the identifier of the device group to which the second device belongs through an application function network element, or obtain the identifier of the device group to which the second device belongs through other core network network elements (such as a network open function network element, or other Internet of Things functions).

[0115] In combination with the tenth aspect, in certain implementations of the tenth aspect, the transceiver unit is specifically used to receive first indication information sent by a first network element, the first indication information carries an identifier of the device group to which the second device belongs and an identifier of a device in the device group to which the second device belongs, and the first indication information indicates a first process for triggering the device in the device group to which the second device belongs; the transceiver unit is specifically used to send the identifier of the device group to which the second device belongs to the second device in the first process.

[0116] In conjunction with the tenth aspect, in some implementations of the tenth aspect, the first process includes any one of the following processes: a registration process, an inventory process, a write process, or a configuration update process. The registration process is a process for the second device to register with the core network, which may include a registration process actively triggered by the second device and a registration process triggered by the network.

[0117] In combination with the tenth aspect, in certain implementations of the tenth aspect, when the first process is a registration process, the transceiver unit is also used to: send second indication information to the first device according to the first indication information, and the second indication information indicates triggering random access of the second device; receive a registration request sent by the second device, and the registration request includes an identifier of the second device; in response to the registration request, send a registration acceptance message to the second device, and the registration acceptance message carries the identifier of the device group to which the second device belongs.

[0118] In combination with the tenth aspect, in certain implementations of the tenth aspect, the device group identifier to which the second device belongs may be sent via a NAS message.

[0119] Exemplarily, the NAS message may be a registration acceptance, a service request, a downlink NAS message, a user equipment configuration command, a write request, an information interaction operation with an IoT device, etc.

[0120] In combination with the tenth aspect, in certain implementations of the tenth aspect, the NAS message may carry identification information allocated by the core network to the second device, and the identification information includes an identifier of a device group to which the second device belongs.

[0121] In combination with the tenth aspect, in some implementations of the tenth aspect, the identification information is any one of the following: GUTI, TMSI, IMSI, TID, EPC, other user equipment identifiers, for example, SUPI, SUCI, GPSI, etc. Among them, the TMSI can be 5G-S-TMSI, 5G-TMSI, S-TMSI, Truncated 5G-S-TMSI, or a temporary mobile subscription identifier of 6G and future versions.

[0122] In combination with the tenth aspect, in certain implementations of the tenth aspect, the NAS message may directly carry identification information allocated by the core network to the second device.

[0123] In combination with the tenth aspect, in certain implementations of the tenth aspect, the device group identifier of the second device may be sent via an RRC message.

[0124] In conjunction with the tenth aspect, in certain implementations of the tenth aspect, the identification information may be an RNTI, wherein the RNTI may be an I-RNTI, a C-RNTI, or a wireless network temporary identifier of 6G and future versions.

[0125] In combination with the tenth aspect, in certain implementations of the tenth aspect, the transceiver unit is further used to: receive indication information from an application function network element, the indication information instructing to perform an operation corresponding to the first device group on a device corresponding to the identifier of the first device group; send the identifier of the first device group to the at least one second device through the first device according to the indication information; receive the identifier of the device group to which the second device belongs, which is sent by the second device, and when the identifier of the device group to which the second device belongs corresponds to the identifier of the first device group, perform the operation corresponding to the first device group on the second device.

[0126] In combination with the tenth aspect, in certain implementations of the tenth aspect, the transceiver unit is further used to send a mask to the at least one second device within the coverage range of the first device.

[0127] In combination with the tenth aspect, in certain implementations of the tenth aspect, the transceiver unit is also used to receive device group registration information from the first network element, the device group registration information including the identifier of the device group to which the second device belongs and the identifier of the device in the device group to which the second device belongs, the device group registration information also includes the network identifier to which the second device belongs, such as a PLMN identifier, NID, etc., the user identifier to which the second device belongs (such as an AF identifier or an identifier of the service requester, etc.), and the serial number of the second device (such as an EPC code); a mask is constructed using the network identifier to which the second device belongs, the user identifier to which the second device belongs, and the serial number of the second device.

[0128] In an eleventh aspect, a communication device is provided, comprising a processor. The processor is coupled to a memory and can be used to execute instructions in the memory to implement the method in the first aspect or the fifth aspect and any possible implementation of the first aspect or the fifth aspect. Exemplarily, the communication device also includes a memory. The communication device also includes a communication interface, and the processor is coupled to the communication interface.

[0129] In one implementation, the communication device is an Internet of Things management function network element. When the communication device is an Internet of Things management function network element, the communication interface may be a transceiver, or an input / output interface.

[0130] In another implementation, the communication device is a chip configured in an IoT management function network element. When the communication device is a chip configured in an IoT management function network element, the communication interface may be an input / output interface.

[0131] Exemplarily, the transceiver may be a transceiver circuit. The input / output interface may be an input / output circuit.

[0132] In a twelfth aspect, a communication device is provided, comprising a processor. The processor is coupled to a memory and can be used to execute instructions in the memory to implement the method in the second aspect and any possible implementation of the second aspect. Exemplarily, the communication device also includes a memory. The communication device also includes a communication interface, and the processor is coupled to the communication interface.

[0133] In one implementation, the communication device is an Internet of Things device. When the communication device is an Internet of Things device, the communication interface may be a transceiver, or an input / output interface.

[0134] In another implementation, the communication device is a chip configured in an IoT device. When the communication device is a chip configured in an IoT device, the communication interface may be an input / output interface.

[0135] Exemplarily, the transceiver may be a transceiver circuit. The input / output interface may be an input / output circuit.

[0136] In a thirteenth aspect, a communication device is provided, comprising a processor. The processor is coupled to a memory and can be used to execute instructions in the memory to implement the method in the third aspect and any possible implementation of the third aspect. Exemplarily, the communication device also includes a memory. The communication device also includes a communication interface, and the processor is coupled to the communication interface.

[0137] In one implementation, the communication device is a reader. When the communication device is a reader, the communication interface may be a transceiver, or an input / output interface.

[0138] In another implementation, the communication device is a chip configured in a reader. When the communication device is a chip configured in a reader, the communication interface may be an input / output interface.

[0139] Exemplarily, the transceiver may be a transceiver circuit. The input / output interface may be an input / output circuit.

[0140] In a fourteenth aspect, a communication device is provided, comprising a processor. The processor is coupled to a memory and can be used to execute instructions in the memory to implement the method in the fourth aspect and any possible implementation of the fourth aspect. Exemplarily, the communication device also includes a memory. The communication device also includes a communication interface, and the processor is coupled to the communication interface.

[0141] In one implementation, the communication device is a data management function network element. When the communication device is a data management function network element, the communication interface may be a transceiver, or an input / output interface.

[0142] In another implementation, the communication device is a chip configured in a data management function network element. When the communication device is a chip configured in a data management function network element, the communication interface may be an input / output interface.

[0143] Exemplarily, the transceiver may be a transceiver circuit. The input / output interface may be an input / output circuit.

[0144] In a fifteenth aspect, a processor is provided, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is used to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor executes the method in any possible implementation of the first to fifth aspects.

[0145] In the specific implementation process, the processor can be one or more chips, the input circuit can be an input pin, the output circuit can be an output pin, and the processing circuit can be a transistor, a gate circuit, a trigger, and various logic circuits. The input signal received by the input circuit can be, for example, but not limited to, received and input by a receiver, and the signal output by the output circuit can be, for example, but not limited to, output to a transmitter and transmitted by the transmitter, and the input circuit and the output circuit can be the same circuit, which is used as an input circuit and an output circuit at different times. The embodiments of the present application do not limit the specific implementation methods of the processor and various circuits.

[0146] In a sixteenth aspect, a processing device is provided, comprising a processor and a memory. The processor is used to read instructions stored in the memory, and can receive signals through a receiver and transmit signals through a transmitter to execute the method in any possible implementation of the first to fifth aspects.

[0147] Exemplarily, the processor is one or more and the memory is one or more.

[0148] Exemplarily, the memory may be integrated with the processor, or the memory may be arranged separately from the processor.

[0149] In the specific implementation process, the memory can be a non-transitory memory, such as a read-only memory (ROM), which can be integrated with the processor on the same chip or can be set on different chips respectively. The embodiments of the present application do not limit the type of memory and the setting method of the memory and the processor.

[0150] It should be understood that the relevant data interaction process, such as sending indication information, can be a process of outputting indication information from the processor, and receiving capability information can be a process of receiving input capability information from the processor. Specifically, the data output by the processor can be output to the transmitter, and the input data received by the processor can come from the receiver. Among them, the transmitter and the receiver can be collectively referred to as a transceiver.

[0151] The processing device in the above-mentioned sixteenth aspect may be one or more chips. The processor in the processing device may be implemented by hardware or by software. When implemented by hardware, the processor may be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor may be a general-purpose processor implemented by reading software codes stored in a memory, and the memory may be integrated in the processor or located outside the processor and exist independently.

[0152] In the seventeenth aspect, a computer program product is provided, which includes: a computer program (also referred to as code, or instruction), which, when executed, enables a computer to execute a method in any possible implementation of the first to fifth aspects above.

[0153] In the eighteenth aspect, a computer-readable storage medium is provided, which stores a computer program (also referred to as code, or instructions). When the computer-readable storage medium is run on a computer, the method in any possible implementation of the first to fifth aspects above is executed.

[0154] In the nineteenth aspect, a communication system is provided, including an Internet of Things management function network element, a data management function network element, at least one Internet of Things device and at least one reader, the Internet of Things management function network element is used to execute the method in the first aspect or the fifth aspect and any possible implementation of the first aspect or the fifth aspect, each Internet of Things device in the at least one Internet of Things device is used to execute the method in the second aspect and any possible implementation of the second aspect, the reader is used to execute the method in the third aspect and any possible implementation of the third aspect, and the data management network element is used to execute the method in the fourth aspect and any possible implementation of the fourth aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0155] Figure 1 It is a schematic diagram of a network architecture applicable to an embodiment of the present application.

[0156] Figure 2 It is a schematic diagram of an ambient energy harvesting Internet of Things service.

[0157] Figure 3 It is a schematic diagram of the random access process of IoT devices.

[0158] Figure 4 It is a schematic flow chart of the communication method 400 provided in an embodiment of the present application.

[0159] Figure 5 It is a schematic flow chart of the communication method 500 provided in an embodiment of the present application.

[0160] Figure 6 It is a schematic flow chart of the communication method 600 provided in an embodiment of the present application.

[0161] Figure 7 It is a schematic flow chart of the communication method 700 provided in an embodiment of the present application.

[0162] Figure 8 It is a schematic block diagram of a communication device provided in an embodiment of the present application.

[0163] Fig. 9 It is a schematic block diagram of a communication device provided in an embodiment of the present application.

[0164] Fig.10 It is a schematic block diagram of a chip system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0165] The technical solution in this application will be described below in conjunction with the accompanying drawings.

[0166] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: the fifth generation (5th generation, 5G) system or new radio (new radio, NR), long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD), universal mobile telecommunication system (universal mobile telecommunication system, UMTS) or other evolved communication systems. The technical solutions provided in the present application can also be applied to future communication systems, such as the sixth generation (6th generation, 6G) mobile communication system.

[0167] The technical solution of the embodiment of the present application can also be applied to machine type communication (MTC), long term evolution-machine (LTE-M), device-to-device (D2D) network, machine-to-machine (M2M) network, Internet of Things (IoT) network or other networks. Among them, the IoT network can include, for example, the Internet of Vehicles. Among them, the communication methods in the Internet of Vehicles system are collectively referred to as vehicle to other devices (vehicle to X, V2X, X can represent anything), for example, the V2X can include: vehicle to vehicle (V2V) communication, vehicle to infrastructure (V2I) communication, vehicle to pedestrian (V2P) communication or vehicle to network (V2N) communication, etc.

[0168] For the convenience of description, the 5G network will be used as an example in the embodiments of the present application.

[0169] Figure 1 It is a schematic diagram of a network architecture 100 provided in an embodiment of the present application.

[0170] Figure 1 (a) is a schematic diagram of the 5G network architecture based on a point-to-point interface. Figure 1As shown in (a), the network architecture may include but is not limited to the following network elements (or referred to as functional network elements, functional entities, nodes, devices, etc.): user equipment (UE), (radio) access network equipment (radio access network, (R)AN), user plane function (UPF) network element, data network (DN), access and mobility management function (AMF) network element, session management function (SMF) network element, policy control function (PCF) network element, application function (AF) network element, network slice selection function (NSSF), authentication server function (AUSF), unified data management (UDM) network element, network exposure function (NEF) network element, unified data repository (UDR) network element, etc.

[0171] Below Figure 1 The network elements shown in (a) are briefly introduced as follows:

[0172] 1. User equipment (UE): It can be called terminal equipment, which is a device that provides voice / data connectivity to users, such as handheld devices and vehicle-mounted devices with wireless connection functions. At present, some examples of terminals may be: mobile phones, tablet computers, computers with wireless transceiver functions (such as laptops, PDAs, etc.), mobile Internet devices (MID), virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDA), handheld devices with wireless communication functions, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in 5G networks, or terminal devices in future evolved PLMNs, etc.

[0173] Among them, wearable devices can also be called wearable smart devices, which are a general term for the intelligent design and development of wearable devices for daily wear using wearable technology, such as glasses, gloves, watches, clothing and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also can achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and independent of smartphones to achieve complete or partial functions, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0174] In addition, the terminal device can also be a terminal device in the Internet of Things (IoT) system. IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection. IoT technology can achieve massive connections, deep coverage, and terminal power saving through narrowband (NB) technology, for example.

[0175] The terminal devices in the IoT system (which can be called IoT devices) can be passive, semi-passive or active. Among them, passive and semi-passive terminals can communicate through reflected carriers, that is, they need to rely on external carrier sources to communicate. Passive terminals may or may not have energy storage capacitors. If there is no energy storage capacitor, it needs to rely on the external environment to obtain energy (for example, radio frequency energy) for communication; for semi-passive terminals, they can have power amplifiers, so that the communication distance is improved compared to passive terminals. Semi-passive terminals usually have energy storage capacitors, which can store energy in the environment such as solar energy, radio energy, etc. in capacitors; for active terminals, they can actively generate carriers (or can be understood as having carrier recovery capabilities), and do not need to rely on external carrier sources for communication, so active terminals can have active communication capabilities. At the same time, active terminals can also be backward compatible with the communication mechanism of passive or semi-passive terminals, that is, they can be triggered by external excitation to initiate a random access process and send identification information. In one possible implementation, the active terminal may also have an energy storage capacitor, that is, it can obtain energy through solar energy, radio frequency, wind energy, hydropower or tidal energy. This application does not limit the way in which passive or semi-active terminals obtain energy.

[0176] It should be noted that the IoT device involved in this application can be in the form of a passive IoT device, or it can be in the form of any terminal.

[0177] 2. Access network (AN): provides network access for authorized users in a specific area, and can use transmission tunnels of different qualities according to the user level, business requirements, etc. The access network can be an access network that uses different access technologies. Current access network technologies include: the wireless access network technology used in the third generation (3rd generation, 3G) system, the wireless access network technology used in the fourth generation (4th generation, 4G) system, or the next generation radio access network (NG-RAN) technology (such as the wireless access technology used in the 5G system, etc.).

[0178] An access network that implements access network functions based on wireless communication technology can be called a radio access network (RAN). The radio access network can manage wireless resources, provide access services to terminals, and then complete the forwarding of control signals and user data between terminals and the core network.

[0179] The wireless access network device may be, for example, a base station (NodeB), an evolved NodeB (eNB or eNodeB), a next generation Node Base station (gNB) in a 5G mobile communication system, a base station in a future mobile communication system, or an access point (AP) in a wifi wireless hotspot system, etc. It may also be a wireless controller in a cloud radio access network (CRAN) scenario, or the wireless access network device may be a relay station, an access point, a vehicle-mounted device, a drone, a wearable device, a network device in a 5G network, or a network device in an evolved PLMN, etc. The embodiments of the present application do not limit the specific technology and specific device form adopted by the wireless access network device.

[0180] Taking the gNB in ​​the 5G mobile communication system as an example, in some deployments, the gNB may include a centralized unit (CU) and a DU. The gNB may also include an active antenna unit (AAU). The CU and DU implement some functions of the gNB respectively. For example, the CU is responsible for processing non-real-time protocols and services, and implementing the functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers; the DU is responsible for processing the physical layer protocols and real-time services, and implementing the functions of the radio link control (RLC) layer, the media access control (MAC) layer, and the physical (PHY) layer; the AAU implements some physical layer processing functions, RF processing, and related functions of active antennas. Since the information of the RRC layer will eventually become the information of the PHY layer, or be converted from the information of the PHY layer, therefore, under this architecture, high-level signaling, such as RRC layer signaling, can also be considered to be sent by the DU, or, considered to be sent by the DU+AAU.

[0181] It is understandable that the access network device may be a device including one or more of a CU node, a DU node, and an AAU node. In addition, the CU may be divided into an access network device in an access network (radio access network, RAN), or may be divided into an access network device in a core network (core network, CN), which is not limited in this application.

[0182] The access network device can provide services for the cell, and the terminal device communicates with the base station through the transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell. The cell can be a cell corresponding to the base station (for example, a base station), and the cell can belong to a macro base station or a base station corresponding to a small cell. The small cell here can include: a metro cell, a micro cell, a pico cell, a femtocell, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services. The access network device can be a macro base station, a micro base station or an indoor station, a relay node or a donor node, a device that provides wireless communication services for user equipment in a V2X communication system, a wireless controller in a cloud radio access network (CRAN) scenario, a relay station, a vehicle-mounted device, a wearable device, and an access network device in a future evolution network. The embodiments of the present application do not limit the specific technology and specific form of the access network device.

[0183] The access network device in the embodiment of the present application may also be an open radio access network (open-radio access network, O-RAN) device (open RAN, or ORAN). The O-RAN device may include an open distributed unit (open-distributed unit, O-DU) and an open centralized unit (open-central unit, O-CU). In the embodiment of the present application, the function of the access network device may be performed by a module (such as a chip) in the access network device, or by a control subsystem including the function of the access network device. The control subsystem including the function of the access network device here may be a control center in the above-mentioned application scenarios such as smart grid, industrial control, smart transportation, and smart city.

[0184] 3. User plane function (UPF): used for packet routing and forwarding, as well as quality of service (QoS) processing of user plane data.

[0185] In a 5G communication system, the user plane network element may be a UPF network element, which may include an intermediate user plane function (I-UPF) network element and an anchor user plane function (PDU Session anchor user plane function, PSA-UPF) network element.

[0186] 4. Data network (DN): A network used to provide data transmission.

[0187] In the 5G communication system, after the terminal device accesses the network, it can establish a protocol data unit (PDU) session, access the DN through the PDU session, and interact with the application function network element deployed in the DN (such as the application server). Depending on the DN accessed by the user, the network can select the UPF accessing the DN as the PDU Session Anchor (PSA) according to the network policy, and access the application function network element through the N6 interface of the PSA.

[0188] 5. Access and mobility management function (AMF): Mainly used for mobility management and access management, etc. It can be used to implement other functions of the mobility management entity (MME) except session management, such as lawful monitoring and access authorization / authentication.

[0189] 6. Session management function (SMF): Mainly used for session management, allocation and management of Internet protocol (IP) addresses of terminal devices, selection of endpoints of manageable terminal device plane functions, policy control and charging function interfaces, and downlink data notification.

[0190] In a 5G communication system, the session management network element may be an SMF network element, which may include an intermediate session management function (I-SMF) network element and an anchor session management function (A-SMF) network element.

[0191] 7. Policy control function (PCF): A unified policy framework used to guide network behavior and provide policy rule information to control plane function elements (such as AMF, SMF elements, etc.).

[0192] In a 4G communication system, the policy control network element may be a policy and charging rules function (PCRF) network element. In a 5G communication system, the policy control network element may be a PCF network element.

[0193] 8. Application function (AF): The AF can interact with the 5G system through the AF to access the network open function element or interact with the policy framework for policy control.

[0194] 9. Network slice selection function (NSSF): It is mainly used to select a group of network slice instances for the UE, determine the allowed network slice selection assistance information (NSSAI), and determine the AMF set that can serve the UE.

[0195] 10. Authentication server function (AUSF): used for authentication services, generating keys to achieve two-way authentication of terminal devices, and supporting a unified authentication framework.

[0196] 11. Data management network element: used to process terminal device identification, access authentication, registration and mobility management, etc.

[0197] In a 5G communication system, the data management network element may be a unified data management (UDM) network element or a unified data repository (UDR) network element.

[0198] The UDM or UDR network element in the embodiment of the present application may refer to a user database, and may exist as a single logical storage repository for storing user data.

[0199] 12. Network exposure function (NEF) network element: used to provide customized functions for network exposure.

[0200] The 5G communication system can also open up the capabilities supported by 5GC to external application function network elements through NEF network elements.

[0201] Figure 1 (b) is a schematic diagram of the 5G network architecture based on service-oriented interfaces. Figure 1 As shown in (b) of FIG. 1 , the network architecture may include but is not limited to the following network elements (or referred to as functional network elements, functional entities, nodes, devices, etc.): UE, (R)AN, UPF network element, DN, AMF network element, SMF network element, PCF network element, AF network element, NSSF network element, AUSF network element, UDM network element, NEF network element, UDR network element, etc. The functions of each network element can be referred to in Figure 1 The introduction of the corresponding network element functions in (a) will not be repeated here.

[0202] Figure 1 Nnssf, Nnef, Nudr, Nausf, Namf, Npcf, Nsmf, Nudm, and Naf shown in (b) are service interfaces provided by the above-mentioned NSSF, NEF, UDR, AUSF, NEF, AMF, PCF, SMF, UDM, and AF, respectively, for invoking corresponding service operations. N1, N2, N3, N4, and N6 are interface serial numbers. The meanings of these interface serial numbers can be found in the meanings defined in the standard protocol of the 3rd Generation Partnership Project (3GPP), and are not limited here.

[0203] It should be understood that the 5G system described above is only an example, and the network architecture applicable to the embodiments of the present application is not limited thereto. Any network architecture that can implement the functions of the above-mentioned network elements is applicable to the embodiments of the present application. Figure 1 The network elements not shown in the figure, of course, the communication method provided in the embodiment of the present application may also only include Figure 1 Some network elements are shown.

[0204] It should also be understood that Figure 1 (a) or Figure 1 The AMF, SMF, UPF, PCF, NEF, etc. shown in (b) can be understood as network elements used to implement different functions, for example, they can be combined into network slices as needed. These network elements can be independent devices, or they can be integrated into the same device to implement different functions, or they can be network elements in hardware devices, or they can be software functions running on dedicated hardware, or they can be virtualized functions instantiated on a platform (for example, a cloud platform). This application does not limit the specific form of the above network elements.

[0205] It should also be understood that the above naming is only defined for the convenience of distinguishing different functions and should not constitute any limitation to this application. This application does not exclude the possibility of using other naming in 5G networks and other future networks. For example, in a 6G network, some or all of the above network elements may use the terminology in 5G, or may use other names.

[0206] It should also be understood that Figure 1 (a) or Figure 1 The interface name between the network elements in (b) is only an example. The interface name in the specific implementation may be other names, and this application does not specifically limit this. In addition, the name of the message (or signaling) transmitted between the above network elements is only an example and does not constitute any limitation on the function of the message itself.

[0207] The above network element or function can be a network element in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform). Optionally, the above network element or function can be implemented by one device, or by multiple devices together, or can be a functional module in one device, and the embodiments of the present application do not specifically limit this.

[0208] This application describes the embodiments of this application using a 5G communication system as an example, but the technical solution of this application is not limited to a 5G system. When this solution is used in an LTE system, a 5G system, or a future communication system, each network element in the solution can be replaced by another network element with corresponding functions, and this application does not limit this.

[0209] Figure 2 The schematic diagram of an environmental energy harvesting IoT service is shown in FIG. The environmental energy harvesting IoT architecture may include IoT devices, readers, IoT management function network elements, and servers.

[0210] Among them, the Internet of Things device can refer to the above description of the terminal device in the IoT system. The Internet of Things device can also be called a tag, a response device, an electronic tag, a wireless radio frequency identification (RFID) tag, a radio frequency tag, a transponder, a data carrier, a recording medium, a radio frequency card, an Internet of Things terminal, etc. For the convenience of description, this application is uniformly referred to as an Internet of Things device. The Internet of Things device can be in the form of a passive Internet of Things device, a sensor form, etc., or it can be any other terminal form without limitation. Among them, the passive Internet of Things device can include a passive terminal (passive device), a semi-passive terminal (semi-passive device), an active terminal (active device), etc.

[0211] The IoT management function network element can be a network element with IoT management function (or passive IoT management function, environmental energy acquisition IoT function). The IoT management function can include access management, security authentication, command transmission, passive IoT device management and other functions for IoT devices. The IoT management function can be integrated into the existing core network network elements, such as Figure 2 The AMF in (a); or the IoT function is integrated into a newly added IoT management function network element, such as Figure 2 The tag management function (TMF) network element in (b). TMF can communicate with IoT devices through access network equipment, or through AMF and access network equipment. When TMF communicates with IoT terminals through AMF and access network equipment, its network topology position is similar to SMF, PCF, etc. When AMF integrates the IoT management function, it can also be regarded as an IoT management function network element, that is, the IoT management function network element below can be AMF, TMF, AMF and TMF jointly established network element, etc. In other words, a network element with IoT management function can be called an IoT management function network element.

[0212] The reader is a device that reads the information of a tag and / or writes information to a tag. The reader can perform non-contact two-way data communication by wireless radio frequency, that is, read and write IoT devices or radio frequency cards (Tags) by wireless radio frequency, so as to achieve the purpose of identifying targets and exchanging data. Exemplarily, the reader can be an access network device in a wireless communication system, or the function of the reader is integrated into the access network device; the reader can also be a terminal device, such as a mobile phone, IoT device, handheld reader, etc. The reader can also be an integrated access and backhaul (IAB) node, etc. The specific form of the reader is not limited in this application. The reader is also called a reader-writer, a read-write device, a readout device, a scanner, a reader head, a communicator, an interpreter, a device with read and / or write functions, etc. For the convenience of description, this application is uniformly referred to as a reader.

[0213] The reader can work in two ways.

[0214] 1) When the IoT device enters the effective identification range of the reader, the IoT device receives the radio frequency signal emitted by the reader and uses the energy obtained from the induced current to send out the information stored in the chip; after the reader receives and decodes the information, it sends it to the central information system (e.g., server) for data processing.

[0215] 2) The reader receives and decodes the signal sent by the IoT device (for example, the IoT device can actively send a signal of a certain frequency when storing some electrical energy (such as solar energy); the reader sends the decoded information to the central information system for data processing.

[0216] The above working method can be widely used in various industries. Here are two common application scenarios:

[0217] 1) Goods / Material Logistics Management: Goods are embedded or attached to IoT devices and stored in warehouses, shopping malls, etc. During the logistics process, relevant information is automatically collected by readers, so managers can quickly query product information in the system, which can reduce the risk of discarding or theft, increase the speed of goods delivery, and prevent channel diversion and counterfeiting.

[0218] 2) Fixed asset management: In places with large assets or valuable items, such as libraries, art galleries and museums, complete management procedures or rigorous protection measures are required. IoT devices can be embedded or attached to books or valuable items. When there are abnormal changes in the storage information of books or valuable items, the change signal can be automatically collected by the reader, thereby alerting the administrator in the system.

[0219] In the embodiment of the present application, the party that initiates the operation on the IoT device in the IoT system is called the service requester. Figure 2 In the scenario shown, the service requester can be an application server (AS) or AF. For example, if AS is integrated on AF (or AS and AF are integrated into one network element), the service requester can be considered to be AF; if AF and AS are separated into two different network elements, such as AF is located in the core network and AS is located in DN, the service requester can be considered to be AS. In addition to AS / AF, the service requester can also be other network elements. This application does not limit the specific implementation method of the service requester.

[0220] In addition, the service requester may have different names, such as server, third party, etc. In addition, the service requester may be directly referred to by the name of a network element, such as Figure 2 In the scenario shown, the service requester may also be referred to as AF / AS.

[0221] exist Figure 2 In the scenario shown, the process for the service requester to perform operations on the IoT device is as follows:

[0222] When the service requester operates the IoT device, an operation instruction can be sent to the IoT device through the IoT management function network element. For example, the operation instruction can be one of an inventory operation (or an inventory operation), a read operation, a write operation, a deactivation operation, an operation to obtain IoT device information, or an operation to interact with IoT devices.

[0223] Among them, the inventory operation can also be understood as obtaining the identification information of the IoT device. In the inventory process, the service requester can issue an inventory instruction. The inventory instruction may include information such as the identification range of the IoT device, the identification of the reader, and location information. After receiving the inventory instruction, the reader can inventory the IoT device according to the inventory instruction and send the identification information of the IoT device to the service requester. Alternatively, the service requester sends an inventory instruction, and the reader forwards the inventory instruction to the IoT device; the IoT device knows that it is an inventory operation based on the content of the inventory instruction, and thus sends the identification information of the IoT device to the reader; after receiving the identification information of the IoT device, the reader sends the identification information of the IoT device to the service requester; or, the IoT device sends the identification information of the IoT device to the core network element through the reader, and the core network element sends the identification information to the service requester after receiving the identification information of the IoT device.

[0224] The read operation can be understood as reading data from an IoT device. An IoT device may have a storage area, and its storage area may store data. For example, if a service requester needs to perform a read operation on an IoT device, the service requester may send a read instruction to a reader or a core network element, and the reader or core network element performs a read operation on the IoT device according to the read instruction, for example, reading data from the IoT device storage area and sending the data to the service requester.

[0225] The write operation can be understood as writing data to the IoT device. For example, if the service requester needs to write to the IoT device, the service requester can send a write instruction to the reader or the core network element, and the reader or the core network performs a write operation on the IoT device according to the write instruction, for example, writing data to the storage area of ​​the IoT device.

[0226] The deactivation operation can invalidate or deactivate the IoT device. For example, the service requester can send a deactivation instruction to the reader or core network element, which may include the identifier of the IoT device (i.e. the identifier of the IoT device that is to be deactivated or invalidated); the reader or core network element performs the deactivation operation on the IoT device according to the instruction. After the operation is completed, the IoT device will be invalidated or deactivated, and it will no longer be counted or subjected to other operations.

[0227] Acquiring IoT device information may include inventory operations and read operations on IoT devices, that is, if the service requester sends an operation instruction to obtain IoT device information, the service requester does not distinguish whether it is an inventory operation on IoT devices or reading IoT device data. The operation will obtain the information of the IoT device, and the information of the IoT device may be the identifier of the IoT device or the data or information stored in the storage area of ​​the IoT device.

[0228] The operation of exchanging information with an IoT device may include any of the above operations. That is, after receiving the instruction of the operation of exchanging information with an IoT device sent by the service requester, the reader or the core network element exchanges information or messages with the IoT device and sends the information from the IoT device to the service requester. In this operation, the reader may not check the content of the instruction, but is only responsible for forwarding the message sent by the service requester to the IoT device, and the message sent by the IoT device to the service requester. Therefore, in this scenario, the operation performed by the reader on the IoT device can be understood as the operation of exchanging information with the IoT device.

[0229] The above operation instructions may include regional location information, identification information of the IoT device, etc. Among them, the identification information of the IoT device may be a globally unique code, such as an electronic product code (EPC), and the identification information of the IoT device may also be a temporary identification. In addition, before the reader or the core network element sends an operation instruction to the IoT device, the reader may send an access instruction to the IoT device to execute the random access process of the IoT device (the random access process of the IoT device can refer to Figure 3 Steps shown). When the IoT device is successfully randomly accessed, the reader sends an operation instruction to the IoT device (the operation instruction sent by the core network element to the IoT device can be forwarded by the reader). The IoT device obtains or sends corresponding information according to the operation instruction. For example, when the instruction is an inventory instruction or is to perform an inventory operation, the IoT device sends the identification information of the IoT device; when the instruction is a read instruction or is to perform a read operation, the IoT device sends the data stored in the storage area of ​​the IoT device; when the instruction is a write instruction or is to perform a write operation, the IoT device stores the data to be written included in the instruction in the storage area of ​​the IoT device. The reader sends (or forwards) the information sent by the IoT device to the core network element; the core network element sends the information to the service requester. Subsequently, the core network element can also perform access management operations on the IoT device based on the feedback information of the service requester.

[0230] Figure 3 This is a schematic diagram of the random access process of an IoT device. Figure 3 As shown, the random access process may include the following steps.

[0231] S301, the reader sends a Select command to the IoT device. Correspondingly, the IoT device receives the Select command from the reader.

[0232] Exemplarily, when the reader receives an inventory instruction from the service requester, the reader generates a Select command and sends the Select command to the IoT device. The command may carry the range of IoT devices (for example, carrying a certain specific range of EPCs).

[0233] S302, the reader sends a query command to the IoT device. Correspondingly, the IoT device receives the query command from the reader.

[0234] Exemplarily, after listening to the Select command, the IoT device determines whether it belongs to the range of IoT devices carried in the Select command. If so, it feeds back the identification information of the IoT device after listening to the Query or QueryRep command.

[0235] The Query command may include a value (denoted as Q value), and the IoT device may generate a random number based on the Q value, for example, a random number between 0 and 2 to the power of Q. Subsequently, the IoT device may reduce the random number by 1 each time the reader sends a Query or QueryRep instruction, and when the random number is reduced to 0, the IoT device initiates random access.

[0236] S303, the IoT device sends a random number to the reader. Correspondingly, the reader receives the random number from the IoT device.

[0237] Exemplarily, when the IoT device finds that it belongs to the IoT device range in the Select command, it can send a random number, such as RK16, to the reader in a competitive manner (for example, when the random number is reduced to zero in S302, RK16 can be understood as a random number with a length of 16 bits).

[0238] S304, the reader sends an Acknowledgement (ACK) command to the IoT device. Correspondingly, the IoT device receives the ACK command from the reader.

[0239] When the reader receives the random number from the IoT device, the reader sends an ACK command to the IoT device, which includes the random number (RN16) received by the reader from the IoT device.

[0240] S305, the IoT device sends the identification information of the IoT device to the reader. Correspondingly, the reader receives the identification information from the IoT device.

[0241] When the IoT device receives the ACK command from the reader and verifies that the random number is correct, it can feedback the reader's representation information of the IoT device, such as EPC.

[0242] For the reading and writing process of IoT devices, in the reading and writing process, the reader can set the range of IoT devices to be read and written through the Select command (for example, if a certain EPC code is carried in the Select command, it means to perform read and write operations on the IoT device corresponding to the EPC code).

[0243] In addition, the reader can also use paging instructions to allow tags to randomly access the reader.

[0244] Alternatively, in some scenarios, the network side can actively report (for example, configured to periodically report) the information of the IoT device, that is, the above process does not need to be triggered by the service requester.

[0245] For example, in the inventory business, the network side periodically reports the IoT devices in the park, or attaches IoT devices to goods, and the network side periodically counts the goods, learns the status of goods in the enterprise park or factory, and realizes automated warehouse management. Subsequently, the network side reports the information of the IoT devices to the service requester to realize the periodic inventory business.

[0246] When the service requester or the network side needs to operate a group of IoT devices (IoT device group), according to the existing solution, the service requester can send multiple operation requests to the reader through the IoT management function, and then the reader processes them one by one, executes the access process of each IoT device in the IoT device group, and sends the operation instructions to each IoT device respectively. Subsequently, the IoT management function network element sends the information of the IoT device to the service requester. The existing solution for operating IoT devices at the group granularity has a large signaling overhead.

[0247] In view of this, the present application provides a communication method and a communication device, which are beneficial to improving or solving the above problems.

[0248] Before introducing the solution of this application, the following points are made:

[0249] (1) In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between the different embodiments are consistent and can be referenced to each other. The technical features in the different embodiments can be combined to form a new embodiment according to their internal logical relationships.

[0250] (2) In this application, "first" and "second" are only used for convenience of description and to distinguish objects, and are not used to limit the scope of the embodiments of this application. They are not used to describe the order or precedence of features. It should be understood that the objects described in this way can be interchanged under appropriate circumstances so as to be able to describe solutions other than the embodiments of this application.

[0251] Figure 4 A schematic flow chart of a communication method 400 provided in an embodiment of the present application is shown. The various steps included in the method 400 are described in detail below.

[0252] S410: The Internet of Things management function network element sends an identifier of a first device group to at least one second device within the coverage of the first device through a first device. Correspondingly, the second device receives the identifier of the first device group from the Internet of Things management function network element.

[0253] Among them, the first device can be a device with reading and / or writing functions, a read-write device, a relay node device (for example, integrated wireless access and backhaul (IAB), a reading device, a scanner, a reader, a communicator, a reader, an interpreter, etc. The first device can be in the form of a terminal or an access network device. The first device can refer to the description of the reader above.

[0254] The second device may be a transponder, an electronic tag, a radio frequency identification (RFID) tag, a radio frequency tag, a transponder, a data carrier, a recording medium, a radio frequency card, an Internet of Things device, etc. The second device may be in the form of a terminal. The second device may refer to the description of the Internet of Things device above.

[0255] Exemplarily, after receiving an operation request from a service requester, the Internet of Things management function network element sends an indication message to the first device to instruct the first device to send an identifier of the first device group to at least one second device within its coverage area.

[0256] The operation request is used to request an operation on an IoT device in the first device group, and the operation request may carry an identifier of the first device group. Optionally, the operation request also includes an operation type corresponding to the first device group. The operation type corresponding to the first device group may be understood as an operation type that needs to be operated on the device in the first device group.

[0257] For example, the operation type corresponding to the first device group may be any one of the following: inventory, read operation, write operation, sending instructions, positioning operation, and reporting the information of the second device to the service requester.

[0258] Specifically, after receiving the indication information sent from the Internet of Things management function network element, the first device can send a random access indication, a paging message or a selection message (an example of the second indication information) to the at least one second device according to the indication information, and the paging message or the selection message carries the identifier of the first device group.

[0259] Exemplarily, after a periodic timer (such as a periodic inventory timer) corresponding to the first device group expires, the Internet of Things management function network element sends the indication information to the first device to instruct the first device to send the identifier of the first device group to at least one second device within its coverage area.

[0260] S420, the second device sends the identifier of the device group to the Internet of Things management function network element. Correspondingly, the Internet of Things management function network element receives the identifier of the device group sent by the second device.

[0261] The identifier of the device group sent by the second device may be the identifier of the device group (referred to as device group #1) to which the second device belongs.

[0262] Exemplarily, the second device is a device in the at least one second device to which the device group belongs corresponds to the first device group. In other words, when it is determined that the identifier of the first device group corresponds to the identifier of the device group to which the second device belongs, the second device in the at least one second device sends the identifier of the device group to which the second device belongs to the IoT management function network element.

[0263] In a possible implementation, the second device sends the identifier of the second device to the IoT management function network element, and the identifier of the second device may include the identifier of the device group to which the second device belongs. That is, the second device sends the identifier information of the second device to the IoT management function network element, so that the IoT management function network element determines the identifier of the device group to which the second device belongs based on the identifier information of the second device, or in other words, so that the IoT management function network element obtains the identifier of the device group to which the second device belongs from the identifier information of the second device.

[0264] Exemplarily, the identification information of the second device may be any one of a subscription concealed identifier (SUCI), a subscription permanent identifier (SUPI), a globally unique AMF identifier (GUAMI), a globally unique temporary UE identity (GUTI), a temporary mobile subscriber identifier (TMSI), and an EPC.

[0265] Alternatively, the identifier of the device group to which the second device belongs is independent of the identifier of the second device, that is, the second device sends the identification information of the second device and the identifier of the device group to which the second device belongs to the Internet of Things device respectively.

[0266] It can be understood that before the second device receives the identifier of the first device group from the Internet of Things management function network element, the second device obtains (stores) the identifier of device group #1.

[0267] In a possible implementation, the second device obtains the identifier of device group #1 through a NAS message. For example, in the registration process of the second device, the second device receives the identifier of device group #1 sent by the Internet of Things management function network element.

[0268] In one example, the second device sends a registration request message to the Internet of Things management function network element through the first device, and the registration request message can carry the identifier of the second device; the Internet of Things management function network element receives the registration request message and completes the authentication of the second device according to the registration request message (the specific authentication process can refer to the existing relevant description); if the authentication is successful, the Internet of Things management function network element sends a registration accept message to the second device, and the registration accept message can carry the identifier of device group #1.

[0269] The identifier of the device group #1 sent by the IoT management function network element through the registration acceptance message may be included in other identifier information. Exemplarily, the identifier information may be identifier information allocated by the core network to the second device.

[0270] For example, the identification information may be a globally unique temporary identifier (GUTI) or a temporary mobile subscription identifier (TMSI).

[0271] Alternatively, the identifier of the device group #1 sent by the IoT management function network element through the registration acceptance message may also be sent separately. Exemplarily, the identifier of the device group #1 may be internal group identifier information (Internal Group ID) allocated by the core network to the second device.

[0272] In this implementation, the present application does not limit the specific process for the second device to obtain the identifier of device group #1, that is, before the IoT management function network element sends the identifier of the first device group to the second device, it can also receive the identifier of the second device through other processes, and determine the identifier of the device group to which the second device belongs based on the identifier of the second device, and send the identifier of the device group to which the second device belongs to the second device through the NAS message in the other process. For example, the other process can be an inventory process, a read and write process, and a user configuration update process (user configuration update).

[0273] Optionally, the second device can obtain the identifier of device group #1 through an RRC message, such as the Internet of Things management function network element sends the identification information assigned by the core network to the first device; the first device constructs the identification information assigned by the first device to the second device based on the identification information.

[0274] For example, the identification information allocated by the first device to the second device may be a radio network temporary identifier (RNTI). When the identification information allocated by the core network to the second device includes the identification of device group #1, the first device may construct the identification information allocated by the first device to the second device based on the identification information, and the identification information may include the identification of device group #1.

[0275] The identifier of the device group #1 described above can be determined by the identifier of the second device and the first corresponding relationship. The first corresponding relationship includes the corresponding relationship between the identifier of the device group and the identifier of the IoT device belonging to the device group. The identifier of the device group includes the identifier of the device group #1. That is, the first corresponding relationship includes the corresponding relationship between the identifier of the device group #1 and the identifier of the second device. Optionally, the first corresponding relationship also includes the corresponding relationship between the identifier of the device group and the identifier of the IoT device belonging to the device group and the identifier of the service requester corresponding to the IoT device.

[0276] Exemplarily, the IoT management function network element may send a query request to the data management network element to query the identifier of the device group to which the second device belongs. The query request may carry the identifier of the second device; the data management network element determines the identifier of the device group to which the second device belongs based on the identifier of the second device and the first corresponding relationship; the query result sent by the data management network element to the IoT management function network element includes the identifier of the device group corresponding to the identifier of the second device, that is, the identifier of the device group (device group #1) to which the second device belongs.

[0277] Optionally, the query request may carry the identifier of the second device and the identifier of the service requester corresponding to the second device (the service requester to which the second device belongs or who uses the second device). The data management network element determines the identifier of the device group to which the second device belongs based on the identifier of the second device, the identifier of the service requester corresponding to the second device, and the first corresponding relationship.

[0278] It can be understood that before the data management network element determines the identifier of the device group to which the second device belongs according to the identifier of the second device and the first corresponding relationship, the data management network element stores the first corresponding relationship.

[0279] Exemplarily, the data management network element may receive the first correspondence sent by the service requester. For example, the service requester may send a device group registration message to the data management network element through the network open function network element, and the device group registration message may carry the first correspondence, that is, the device group registration message includes the identifier of the device group to which the second device belongs (recorded as device group #1), and the identifier of at least one IoT device belonging to the device group #1. Optionally, the device group registration message carries the first correspondence and also includes the identification information of the service requester.

[0280] Optionally, the device group registration message may also include an operation type corresponding to the device group #1, that is, an operation type for performing operations on the IoT devices in the device group #1.

[0281] The identifier of the device group #1 sent by the service request direction to the data management network element can be an external identifier (external ID) or an internal identifier (internal ID). The external identifier can be understood as an identifier that can be recognized (understood) outside the network; the internal identifier can be understood as an identifier that can be recognized inside the network.

[0282] Optionally, when the identifier of device group #1 is an external identifier, the data management network element may convert the external identifier into an internal identifier. In this case, the identifier of device group #1 sent by the data management network element to the Internet of Things management function network element may be an internal identifier.

[0283] Optionally, after receiving the device group registration message from the service requester, the first network element may also obtain the identifier of the service requester corresponding to the device group registration message. Subsequently, the first network element may send the identifier of the service requester to the Internet of Things management function network element so that the Internet of Things management function network element transmits subsequent data or information to the service requester; or, after receiving the subsequent data or information from the Internet of Things management function network element, the first network element transmits the data or information to the service requester according to the identifier of the service requester.

[0284] The identifier of the corresponding device group obtained by the second device mentioned above can be composed of the internal identifier or the external identifier and the identifier of the second device. The identifier of the second device can be one or more of the following: user permanent identifier (SUPI), subscription concealed identifier (SUCI), generic public subscription identifier (GPSI), Internet protocol (IP) quintuple, identifier of the Internet of Things device in the newly constructed IoT system, etc.

[0285] The above example can be understood as that in the process of active registration of the second device, the Internet of Things management function network element sends the identifier of device group #1 to the second device.

[0286] In another example, the network side may trigger a registration process for the second device, and the IoT management function network element sends an identifier of device group #1 to the second device in the registration process for the second device triggered by the network side.

[0287] Exemplarily, in the above-mentioned service requester sending a device group registration message to the data management network element through the first network element, after receiving the first corresponding relationship, the first network element can instruct the Internet of Things management function network element to trigger the registration process of the at least one Internet of Things device in device group #1. The at least one Internet of Things device includes the second device. The first network element may include at least one of the following network elements: NEF, SMF, AMF or TMF.

[0288] For example, the first network element sends indication information to the Internet of Things management function network element, and the indication information may include the identifier of the device group #1 and the identifier of the at least one Internet of Things device. The identifier of the device group #1 included in the indication information may be an internal identifier. In the case where the identifier of the device group #1 sent by the service requester is an external identifier, the first network element may query the internal identifier corresponding to the external identifier from the data management network element according to the external identifier.

[0289] After receiving the indication information from the first network element, the Internet of Things management function network element sends the random access indication to the first device. The random access indication is used to indicate the triggering of random access of the second device; the first device and the second device execute the random access process of the second device. Further, the second device sends a registration request message to the Internet of Things management function network element through the first device, and the registration request message may carry the identifier of the second device; the Internet of Things management function receives the registration request message and completes the authentication process of the second device; the Internet of Things management function network element sends a registration acceptance message to the second device, and the registration acceptance message carries the identifier of the device group #1 (the identifier of the device group #1 comes from the indication information sent by the first network element).

[0290] The identifier of the device group #1 sent by the IoT management function network element through the registration acceptance message may be included in other identifier information. Exemplarily, the identifier information may be identifier information allocated by the core network to the second device.

[0291] Alternatively, the identifier of the device group #1 sent by the Internet of Things management function network element through the registration acceptance message can also be sent separately.

[0292] Optionally, the second device may obtain the identifier of device group #1 through an RRC message, such as the IoT management function network element sending the identifier information assigned by the core network to the first device; the first device constructs the identifier information assigned by the first device to the second device based on the identifier information. For details, please refer to the description in the first example.

[0293] The present application does not limit the process by which the second device obtains the identification of the device group to which the second device belongs. By way of example, in addition to the registration process mentioned above, the second device may also obtain the identification of the device group to which the second device belongs in a writing process, such as by writing the identification of the device group to which the second device belongs, or information containing the identification of the device group to which the second device belongs, into a storage area of ​​the second device through the writing process; the identification of the device group to which the second device belongs may also be obtained in an inventory process, such as by sending the identification of the device group to which the second device belongs, or information containing the identification of the device group to which the second device belongs, to the second device through the inventory process.

[0294] S430: The Internet of Things management function network element determines that the identifier of the device group sent by the second device corresponds to the identifier of the first device group.

[0295] Exemplarily, after receiving the identifier of the device group sent by the second device, the IoT management function network element determines whether the identifier of the device group sent by the second device corresponds to the identifier of the first device group, and if so, executes subsequent steps.

[0296] For example, after receiving the identifier of the device group sent by the second device, the Internet of Things management function network element determines whether the identifier of the device group sent by the second device is the first device group identifier based on the first device group identifier carried in the operation request received from the service requester. If so, execute subsequent steps.

[0297] S440, the Internet of Things management function network element performs an operation corresponding to the identifier of the first device group on the second device.

[0298] The operations corresponding to the first device group refer to the description in S410.

[0299] Exemplarily, the Internet of Things management function network element sends an instruction to execute the operation corresponding to the first device group to the second device through the first device; the second device performs the corresponding operation according to the instruction. The instruction may come from an operation request from the service requester, or the instruction is an operation type corresponding to the first device group queried from the data management network element, or the instruction comes from an inventory operation triggered by the expiration of a periodic inventory timer. For example, when the instruction is an inventory instruction or an inventory operation is performed, the second device sends the identification information of the second device to the first device; when the instruction is a read instruction or a read operation is performed, the second device sends the data information stored in the second device to the first device; when the instruction is a write instruction or a write operation is performed, the second device stores the data information to be written included in the instruction. If the first device receives information from the second device (for example, the identification of the second device), the first device sends the information to the Internet of Things management function network element; subsequently, the Internet of Things management function network element reports the information to the service requester.

[0300] Optionally, before executing the operation, the IoT management function network element may query from the data management network element whether the identifier of the second device corresponds to the identifier of device group #1. The IoT management function network element executes the operation corresponding to the first device group on the second device, including: when the identifier of the second device corresponds to the identifier of device group #1, executing the operation corresponding to the first device group on the second device.

[0301] Exemplarily, the Internet of Things management function network element sends a group information query request to the data management network element, and the request may carry the identifier of the second device and the identifier of device group #1; the data management network element determines whether the identifier of the second device corresponds to the identifier of device group #1 based on the identifier of the stored device group corresponding to the second device; or, the data management network element sends the identifier of the stored device group corresponding to the second device to the Internet of Things device, and the Internet of Things management function network element determines whether the identifier of the device group corresponding to the second device corresponds to the identifier of device group #1.

[0302] Optionally, when the second device does not correspond to the identifier of the device group #1, the Internet of Things management function network element may also send to the second device the identifier of the device group (device group #2) corresponding to the identifier of the second device queried from the data management network element, so as to facilitate subsequent execution of operations corresponding to the device group #2 on the second device.

[0303] By querying the data management network element whether the identifier of the second device corresponds to the identifier of device group #1, the IoT device can be prevented from reporting a tampered device group identifier, or erroneous operation of the second device caused by an update of the device group corresponding to the second device can be avoided.

[0304] Figure 5 A schematic flow chart of a communication method 500 provided by the present application is shown. Method 500 describes in detail how device #1 (an example of a second device) obtains information about a device group corresponding to device #1 in an active registration process. Method 500 is illustrated by taking an IoT terminal (i.e., device #1) in a device group as an example. The other IoT terminals in the device group obtain information about the device group in a similar manner to that of device #1. The steps included in method 500 are described in detail below.

[0305] S501, AF (an example of a service requester) sends information #1 to UDM or UDR.

[0306] For example, the AF sends information #1 (an example of device group registration information) to the UDM / UDR (an example of a data management network element). The information #1 may be forwarded to the UDM / UDR via the NEF.

[0307] Information #1 may include an identifier of a device group, and the identifier of the device group corresponds to an identifier of at least one IoT device. The at least one IoT device includes device #1. For example, information #1 includes an identifier of the at least one IoT device, and the identifier of each IoT device in the identifier of the at least one IoT device includes an identifier of the device group to which each IoT device belongs.

[0308] Optionally, the identifier of the IoT device may include one or more of a network identifier (such as a PLMN identifier, NID) to which the IoT device belongs, a user identifier (such as an identifier of the service requester, or an AF identifier) ​​to which the IoT device belongs, and a serial number (such as an EPC code, etc.) of the IoT device.

[0309] Information #1 may also include the identification of the service requester.

[0310] Optionally, information #1 includes indication information #1. Indication information #1 indicates an operation type. The operation type indicates the type of operation that needs to be performed on the IoT device in the device group. For details, please refer to the description in S410.

[0311] If the identifier of the device group sent by the AF is an external group ID, the method may further include:

[0312] The UDM or UDR converts the external group ID to an internal group ID.

[0313] S502, device #1 sends a registration request message to AMF / TMF (an example of an IoT management function network element) through a reader (an example of a first device). Correspondingly, AMF / TMF receives the registration request message from device #1.

[0314] For example, when device #1 is started or is a newly joined device group, device #1 sends the registration request message to AMF / TMF through a reader.

[0315] Exemplarily, when device #1 monitors the broadcast message of the reader, it sends the registration request message to the reader.

[0316] The registration request message may carry the identifier of device #1.

[0317] Optionally, the registration request message carries the type of device #1 for subsequent security authentication of device #1. For example, the type of device #1 may be a passive terminal, a semi-passive terminal, an active terminal, etc.

[0318] S503, AMF / TMF obtains the identifier of the device group corresponding to device #1.

[0319] Exemplarily, after receiving the registration request message from device #1, AMF / TMF obtains the identifier of the device group corresponding to device #1 from UDM / UDR according to the identifier of device #1 included in the registration request message, for example, the internal group ID corresponding to device #1.

[0320] In S501, UDM / UDR receives the identifier of the device group from AF and the identifier of at least one IoT device corresponding to the device group. The at least one IoT device includes the device #1. Therefore, UDM / UDR can query the identifier of the device group corresponding to the device #1 based on the identifier of the device #1 received from AMF / TMF.

[0321] Optionally, S504, AMF / TMF constructs an identifier assigned by the core network to device #1 according to the identifier of the device group corresponding to device #1.

[0322] The identifier allocated by the core network to device #1 refers to the description in S410.

[0323] For example, the identifier is 5G GUTI. 5G GUTI may include the identifier of the PLMN (for example, composed of a mobile country code (MCC) and a mobile network code (MNC) in a 5G communication system), the identifier of the AMF / TMF, and the 5G-TMSI. Optionally, the globally unique temporary identifier may also include the identifier of the service requester (for example, AF).

[0324] When the globally unique temporary identifier includes the identifier of the PLMN, the AMF / TMF can construct an identifier of a device group that is unique within the PLMN; when the globally unique temporary identifier includes the identifier of the AF, the AMF / TMF can construct an identifier of a device group that is unique within the PLMN and the AF.

[0325] The method also includes: AMF / TMF sends the identifier allocated to device #1 to device #1.

[0326] There are two specific ways:

[0327] Method 1:

[0328] S505a, AMF / TMF sends the identifier assigned by the core network to device #1 to device #1 through the reader. Correspondingly, device #1 receives the identifier assigned by the core network to device #1 from AMF / TMF.

[0329] For example, AMF / TMF sends the identifier assigned by the core network to device #1 to the reader through a Registration Accept message, and the reader sends the identifier assigned by the core network to device #1 to the device #1.

[0330] Method 2:

[0331] S505b, AMF / TMF sends the identifier assigned by the core network to device #1 to the reader. Correspondingly, the reader receives the identifier assigned by the core network to device #1 from AMF / TMF. The identifier can be sent via NAS information.

[0332] Exemplarily, AMF / TMF sends the identifier assigned by the core network to device #1 to the reader via a registration acceptance message.

[0333] S506: The reader constructs an RNTI according to the identifier allocated by the core network to device #1.

[0334] That is, the reader constructs a temporary identifier of device #1 when transmitting information between device #1 and the reader according to the identifier assigned to device #1 by the core network.

[0335] S507, the reader sends the wireless network temporary identifier to device #1. Correspondingly, device #1 receives the wireless network temporary identifier from the reader. The identifier can be sent via RRC information.

[0336] Figure 6 A schematic flow chart of a communication method 600 provided by the present application is shown. Method 600 introduces in detail how device #1 (an example of a second device) obtains information about a device group corresponding to device #1 in a registration process triggered by a network. For example, in a scenario where an IoT device cannot initiate active registration due to its own limited capabilities, the registration process of the IoT device can be triggered by the network. Method 600 is illustrated by taking an IoT device (i.e., device #1) in a device group as an example, and the way in which other IoT devices in the device group obtain information about the device group is similar to the way in which device #1 obtains information. The method includes the following steps.

[0337] S601, AF sends information #1 to UDM or UDR via NEF.

[0338] The information #1 may include an identifier of a device group and an identifier of at least one IoT device corresponding to the device group.

[0339] For details of this step, please refer to the description of S501.

[0340] S602, NEF sends indication information #1 to AMF / TMF. Correspondingly, AMF / TMF receives indication information #1 from NEF.

[0341] Exemplarily, after receiving the information #1 from the AF, the NEF sends the indication information #1 to the AMF. The indication information #1 is used to indicate the registration process of at least one IoT device in the triggering device group.

[0342] One possible implementation is that NEF is triggered by AF information #1 to send an indication message to AMF.

[0343] Another possible implementation is that NEF is triggered by a periodic registration timer to send an indication message to AMF. The periodic registration timer can be stored in UDM / UDR or in NEF.

[0344] The indication information #1 may carry the identifier of the device group, for example, the identifier of the device group is an internal group ID (when the identifier of the device group is an external group ID, the NEF may convert the external group ID into an internal group ID, refer to the description in S502).

[0345] Optionally, the indication information #1 carries an identifier of the AF. The identifier of the AF can be used to construct a mask for the AMF / TMF.

[0346] Optionally, the method further includes: AMF / TMF constructing a mask.

[0347] The mask can also be called a filter, which is used to filter IoT devices. That is, after receiving the mask, the IoT device can query whether the information in the mask matches its own information, and respond to corresponding operations if they match.

[0348] Exemplarily, AMF / TMF constructs a mask based on at least one of the following information: the identification of the device included in indication information #1, the identification of the service requester (such as AF ID), the list of IoT device identifications, and the network identification (such as PLMN ID).

[0349] S603, AMF / TMF sends indication information #2 to the reader. Correspondingly, the reader receives indication information #2 from AMF / TMF.

[0350] The indication information #2 may indicate triggering a random access procedure for an IoT device in a device group.

[0351] Exemplarily, upon receiving indication information #1 from NEF, AMF / TMF sends indication information #2 to the reader.

[0352] If AMF / TMF constructs a mask according to the indication information #1, the indication information #2 includes the mask. For example, AMF / TMF can construct a mask according to one or more of the network identifier to which the IoT device belongs, the user identifier to which the IoT device belongs, and the serial number of the IoT device. When the identifier of the IoT device contains one or more of the network identifier to which the IoT device belongs, the user identifier to which the IoT device belongs, the serial number of the IoT device, and the identifier of the IoT group to which it belongs, AMF / TMF can strip the IoT group identifier from the IoT device identifier to construct a mask.

[0353] S604, the reader executes a random access procedure of device #1 (an example of an IoT device in the device group).

[0354] For the random access process, reference may be made to the existing related description.

[0355] S605, device #1 sends the identification of device #1 to AMF / TMF through the reader.

[0356] For example, after random access is completed, device #1 sends a registration request message to AMF / TMF, and the registration request message carries the identifier of device #1.

[0357] Optionally, the registration request message carries the device type of device #1. The type of device #1 is used for security authentication of device #1 by AMF / TMF.

[0358] S606, AMF / TMF obtains the identifier of the device group corresponding to device #1.

[0359] For this step, refer to the description of S503.

[0360] Optionally, in S607, AMF / TMF constructs an identifier assigned by the core network to device #1 according to the identifier of the device group corresponding to device #1.

[0361] The identifier allocated by the core network to device #1 refers to the description in S410.

[0362] The method also includes: AMF / TMF sends the identifier of the device group corresponding to device #1 to device #1.

[0363] There are two specific ways:

[0364] Method 1:

[0365] S608a, AMF / TMF sends the identifier assigned by the core network to device #1 to device #1 through the reader. Correspondingly, device #1 receives the identifier assigned by the core network to device #1 from AMF / TMF.

[0366] For example, AMF / TMF sends the identifier assigned by the core network to device #1 to the reader through a Registration Accept message, and the reader sends the identifier assigned by the core network to device #1 to the device #1.

[0367] Method 2:

[0368] S608b, AMF / TMF sends the identifier assigned by the core network to device #1 to the reader. Correspondingly, the reader receives the identifier assigned by the core network to device #1 from AMF / TMF.

[0369] Exemplarily, AMF / TMF sends the identifier assigned by the core network to device #1 to the reader via a registration acceptance message.

[0370] S609, the reader constructs a wireless network temporary identifier according to the identifier allocated by the core network to device #1.

[0371] That is, the reader constructs a temporary identifier of device #1 when transmitting information between device #1 and the reader according to the identifier assigned to device #1 by the core network.

[0372] S610: The reader sends the wireless network temporary identifier to device #1. Correspondingly, device #1 receives the wireless network temporary identifier from the reader.

[0373] Figure 7 A schematic flow chart of a communication method 700 provided by the present application is shown. The method 700 can be used for group operation of IoT devices in a device group. The various steps included in the method 700 are described in detail below.

[0374] S701, AF sends an operation request to AMF / TMF.

[0375] The operation request carries the identifier of device group #1 (an example of the first device group), the identifier of the device corresponding to device group #1, and an optional operation type.

[0376] If the identifier of device group #1 is an external identifier (external group id), the method may further include:

[0377] S702, AMF / TMF obtains the internal identifier (internal group id) corresponding to the external group id from UDM / UDR according to the external group id.

[0378] Optionally, if the operation request in S701 does not have an operation type, AMF / TMF may also obtain a preset operation type from UDM / UDR according to the internal groupid.

[0379] S703, AMF / TMF sends a random access indication to the reader.

[0380] Exemplarily, the random access indication carries the identifier of device group #1.

[0381] For example, the random access indication carries mask information, and the mask information includes the identifier of device group # 1. Optionally, the mask information may also include PLMN ID and / or AF ID.

[0382] Optionally, the random access indication may also carry indication information, where the indication information is used to indicate the position and length of the identifier of device group #1 in the mask information.

[0383] The random access indication may be sent to the reader via an N2 message. The random access indication may instruct the reader to broadcast a Select command, which may carry a mask; or, the random access indication is used to instruct the reader to broadcast a Paging message, which may carry a mask. When the random access indication is used to instruct the reader to broadcast a Paging message, the random access indication may be a Paging Message. The mask may be carried in the random access indication, or may be carried in an N2 message together with the random access indication.

[0384] S704, the reader sends a broadcast message to the IoT devices within the coverage area of ​​the reader.

[0385] The broadcast message may be a paging message or a select message. The broadcast message carries the mask information.

[0386] S705, device #1 (an example of an IoT device within the coverage of the reader) determines whether the received identifier of device group #1 corresponds to the identifier of the device group to which device #1 belongs.

[0387] If the identifier of device group #1 corresponds to the identifier of the device group to which device #1 belongs, device #1 executes a random access procedure to access the reader.

[0388] Exemplarily, after receiving the identifier of device group #1, if the AF identifier is used in the temporary identifier previously constructed by the AMF / TMF, the Internal Group ID is converted to the Group ID in the identifier, and the device optionally obtains the Group ID in the GUTI / RNTI based on the nvalue for comparison. If the n value is not provided, it can be considered that the device is configured with the ability to identify the group identifier in the A-IoT GUTI.

[0389] S706, device #1 feeds back to AMF the identifier of the device group to which device #1 belongs.

[0390] Optionally, device #1 feeds back the identifier of device #1 to AMF.

[0391] Optionally, in S707, AMF / TMF queries UDM / UDR whether the identifier of the device group to which device #1 belongs corresponds to the identifier of device #1.

[0392] S708, AMF / TMF executes the operation corresponding to the identifier of device group #1 on device #1 through the reader.

[0393] For this step, reference may be made to the description in S440.

[0394] S709, AMF / TMF reports the information of device #1 to AF.

[0395] The order of the steps in the above process is determined according to the internal logic of the method. The serial numbers shown in the above flowchart are only examples and do not limit the order of the steps of this application.

[0396] Above, combined Figures 4 to 7 The communication method provided by the embodiment of the present application is described in detail. Figures 8 to 10 The communication device provided in the embodiment of the present application is described in detail. It should be understood that the description of the device embodiment corresponds to the description of the method embodiment, so the contents not described in detail can be referred to the method embodiment above, and will not be repeated here for the sake of brevity.

[0397] Figure 8 A schematic diagram of a communication device 800 provided in an embodiment of the present application is shown. The device 800 includes an interface unit 810, which can be used to implement corresponding communication functions. The interface unit 810 can also be called a communication interface or a communication unit.

[0398] Optionally, the device 800 may further include a processing unit 820, which may be used to perform data processing.

[0399] Optionally, the device 800 also includes a storage unit, which can be used to store instructions and / or data. The processing unit 820 can read the instructions and / or data in the storage unit so that the device implements the actions of different devices in the aforementioned method embodiments.

[0400] In one possible design, the device 800 may be the IoT management function network element in the aforementioned embodiment, or may be a component (such as a chip) of the IoT management function network element. The device 800 may implement the steps or processes corresponding to those performed by the IoT management function network element in the above method embodiment. Among them, the interface unit 810 may be used to perform the operations related to the sending and receiving of the IoT management function network element in the above method embodiment; the processing unit 820 may be used to perform the operations related to the processing of the IoT management function network element in the above method embodiment.

[0401] In another possible design, the device 800 may be the second device in the aforementioned embodiment, or may be a component (such as a chip) of the second device. The device 800 may implement the steps or processes corresponding to those performed by the second device in the above method embodiment. Among them, the interface unit 810 may be used to perform the operations related to the transmission and reception of the second device in the above method embodiment; and the processing unit 820 may be used to perform the operations related to the processing of the second device in the above method embodiment.

[0402] In another possible design, the device 800 may be the first device in the aforementioned embodiment, or may be a component (such as a chip) of the first device. The device 800 may implement the steps or processes corresponding to those performed by the first device in the above method embodiment. Among them, the interface unit 810 may be used to perform the operations related to the transmission and reception of the first device in the above method embodiment; and the processing unit 820 may be used to perform the operations related to the processing of the first device in the above method embodiment.

[0403] Fig. 9 9 is a schematic block diagram of a communication device 900 provided in an embodiment of the present application. The device 900 includes a processor 910, and the processor 910 is coupled to a memory 920. Optionally, the memory 920 is further included. The memory 920 is used to store computer programs or instructions and / or data, and the processor 910 is used to execute the computer programs or instructions stored in the memory 920, or read the data stored in the memory 920, so as to execute the methods in the above method embodiments.

[0404] Optionally, there are one or more processors 910 .

[0405] Optionally, the memory 920 is one or more.

[0406] Optionally, the memory 920 is integrated with the processor 910 or provided separately.

[0407] Alternatively, if Fig. 9 As shown, the device 900 further includes a transceiver 930, which is used to receive and / or send signals. For example, the processor 910 is used to control the transceiver 930 to receive and / or send signals. The transceiver 930 may also be referred to as an interface.

[0408] As a solution, the device 900 is used to implement the operations performed by the Internet of Things management function network element in the above method embodiments.

[0409] For example, the processor 910 is used to execute the computer program or instructions stored in the memory 920 to implement the relevant operations of the Internet of Things management function network element in the above various method embodiments.

[0410] As another solution, the apparatus 900 is used to implement the operations performed by the second device in each of the above method embodiments.

[0411] For example, the processor 910 is configured to execute a computer program or instruction stored in the memory 920 to implement related operations of the second device in each of the above method embodiments.

[0412] As another solution, the apparatus 900 is used to implement the operations performed by the first device in each of the above method embodiments.

[0413] For example, the processor 910 is configured to execute a computer program or instruction stored in the memory 920 to implement related operations of the first device in each of the above method embodiments.

[0414] In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in the processor 910 or an instruction in the form of software. The method disclosed in conjunction with the embodiment of the present application can be directly embodied as a hardware processor for execution, or a combination of hardware and software modules in the processor for execution. The software module can be located in a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory 920, and the processor 910 reads the information in the memory 920 and completes the steps of the above method in conjunction with its hardware. To avoid repetition, it is not described in detail here.

[0415] It should be understood that in the embodiments of the present application, the processor may be one or more integrated circuits for executing related programs to execute the embodiments of the methods of the present application.

[0416] The processor (e.g., processor 910) may include one or more processors and be implemented as a combination of computing devices. The processor may include one or more of the following: a microprocessor, a microcontroller, a digital signal processor (DSP), a digital signal processing device (DSPD), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a programmable logic device (PLD), a gating logic, a transistor logic, a discrete hardware circuit, a processing circuit or other suitable hardware, firmware and / or a combination of hardware and software for performing the various functions described in the present disclosure. The processor may be a general-purpose processor or a dedicated processor. For example, processor 910 may be a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data. The central processing unit may be used to enable the device to execute a software program and process data in the software program. In addition, a portion of the processor may also include a non-volatile random access memory. For example, the processor may also store information about the type of device.

[0417] Program in this application is used to refer to software in a broad sense. Non-limiting examples of software include: program code, program, subroutine, instruction, instruction set, code, code segment, software module, application, or software application, etc. The program can be run in a processor and / or computer. So that the device performs various functions and / or processes described in this application.

[0418] The memory (e.g., memory 920) can store data required by the processor (e.g., processor 910) when executing software. The memory can be implemented using any suitable storage technology. For example, the memory can be any available storage medium that can be accessed by the processor and / or computer. Non-limiting examples of storage media include random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM), static RAM (SRAM), dynamic RAM (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM) and direct rambus RAM (DR RAM), removable media, optical disk storage, magnetic disk storage media, magnetic storage devices, flash memory, registers, state memory, remote mounted storage, local or remote storage components, or any other medium capable of carrying or storing software, data or information and accessible by a processor / computer. It should be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0419] The memory (e.g., memory 920) and the processor (e.g., processor 910) may be provided separately or integrated together. The memory may be used to connect to the processor so that the processor can read information from the memory and store and / or write information in the memory. The memory may be integrated in the processor. The memory and the processor may be provided in an integrated circuit (e.g., the integrated circuit may be provided in a UE or other network node).

[0420] Fig.101 is a schematic block diagram of a chip system 1000 provided in an embodiment of the present application. The chip system 1000 (or also referred to as a processing system) includes a logic circuit 1010 and an input / output interface 1020 .

[0421] Among them, the logic circuit 1010 can be a processing circuit in the chip system 1000. The logic circuit 1010 can be coupled to a storage unit and call instructions in the storage unit so that the chip system 1000 can implement the methods and functions of each embodiment of the present application. The input / output interface 1020 can be an input / output circuit in the chip system 1000, outputting information processed by the chip system 1000, or inputting data or signaling information to be processed into the chip system 1000 for processing.

[0422] As a solution, the chip system 1000 is used to implement the operations performed by the Internet of Things management function network element in the above method embodiments.

[0423] For example, the logic circuit 1010 is used to implement the processing-related operations performed by the Internet of Things management function network element in the above method embodiment; the input / output interface 1020 is used to implement the sending and / or receiving-related operations performed by the Internet of Things management function network element in the above method embodiment.

[0424] As another solution, the chip system 1000 is used to implement the operations performed by the second device in each of the above method embodiments.

[0425] For example, the logic circuit 1010 is used to implement the processing-related operations performed by the second device in the above method embodiment; the input / output interface 1020 is used to implement the sending and / or receiving-related operations performed by the second device in the above method embodiment.

[0426] As another solution, the chip system 1000 is used to implement the operations performed by the first device in each of the above method embodiments.

[0427] For example, the logic circuit 1010 is used to implement the processing-related operations performed by the first device in the above method embodiment; the input / output interface 1020 is used to implement the sending and / or receiving-related operations performed by the first device in the above method embodiment.

[0428] An embodiment of the present application also provides a computer-readable storage medium on which computer instructions are stored for implementing the methods executed by a communication device (such as an Internet of Things management function network element, a first device, and a second device) in the above-mentioned method embodiments.

[0429] An embodiment of the present application also provides a computer program product, comprising instructions, which, when executed by a computer, implement the methods performed by a communication device (such as an Internet of Things management function network element, a first device, and a second device) in the above-mentioned method embodiments.

[0430] An embodiment of the present application also provides a communication system, which includes at least one of the Internet of Things management function network element, the first device, the second device, the data management network element, the network open function network element and the service requester in the above embodiments.

[0431] The explanation of the relevant contents and beneficial effects of any of the above-mentioned devices can be referred to the corresponding method embodiments provided above, which will not be repeated here.

[0432] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the above units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0433] The units described above as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to implement the solution provided by this application.

[0434] In addition, each functional unit in each embodiment of the present application may be integrated into one unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0435] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0436] When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loading and executing computer program instructions on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network or other programmable devices. For example, the computer can be a personal computer, a server, or a network device, etc. The computer instruction can be stored in a computer-readable storage medium, or transmitted from a computer-readable storage medium to another computer-readable storage medium, for example, the computer instruction can be transmitted from a website site, a computer, a server or a data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. About computer-readable storage medium, it can be described with reference to the above.

[0437] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A communication method, characterized in that: include: Sending, by a first device, an identifier of a first device group to at least one second device within a coverage range of the first device, wherein the first device is a device having a read and / or write function, and the second device is an Internet of Things device; receiving, from the second device, an identifier of a device group to which the second device belongs; Determining that the identifier of the device group sent by the second device corresponds to the identifier of the first device group; An operation corresponding to the identifier of the first device group is performed on the second device.

2. The method according to claim 1, characterized in that Before receiving the identifier of the device group sent by the second device, the method further includes: receiving a registration request sent by the second device, where the registration request includes an identifier of the second device; determining, according to the identifier of the second device, an identifier of the device group to which the second device belongs; An identifier of a device group to which the second device belongs is sent to the second device.

3. The method according to claim 1, characterized in that Before receiving the identifier of the device group sent by the second device, the method further includes: receiving first indication information sent by a first network element, where the first indication information carries an identifier of a device group to which the second device belongs, and the first indication information indicates triggering a first process of a device in the device group to which the second device belongs; In the first process, an identifier of a device group to which the second device belongs is sent to the second device.

4. The method according to claim 3, characterized in that The first process includes any one of the following processes: Registration process, inventory process, write process, or configuration update process.

5. The method according to claim 4, characterized in that When the first process is a registration process, after receiving the first indication information sent by the first network element, the method further includes: Sending second indication information to the first device according to the first indication information, where the second indication information indicates triggering random access of the second device; The sending, to the second device, an identifier of a device group to which the second device belongs, includes: receiving a registration request sent by the second device, where the registration request includes an identifier of the second device; In response to the registration request, a registration acceptance message is sent to the second device, where the registration acceptance message carries an identifier of a device group to which the second device belongs.

6. The method according to any one of claims 3 to 5, characterized in that The first network element includes a network open function network element, and the method further includes: The network open function network element receives device group registration information sent by the application server, where the device group registration information carries an identifier of the device group to which the second device belongs and an identifier of a device in the device group to which the second device belongs; The network open function network element sends the first indication information according to the device group registration information.

7. The method according to claim 6, characterized in that The method further comprises: The network open function network element sends the device group registration information to the data management network element.

8. The method according to claim 7, characterized in that The determining, according to the identifier of the second device, the identifier of the device group to which the second device belongs includes: Sending a query message to the data management network element, where the query message carries an identifier of the second device; An identifier of a device group to which the second device belongs is received and sent by the data management network element, where the identifier of the device group to which the second device belongs is determined according to the identifier of the second device and the device group registration information.

9. The method according to claim 7 or 8, characterized in that: Before performing the operation corresponding to the identifier of the first device group on the second device, the method further includes: Acquire the device group registration information from the data management network element; determining, according to the device group registration information, whether the identifier of the second device corresponds to the identifier of the device group to which the second device belongs; The performing, on the second device, an operation corresponding to the identifier of the first device group, includes: When the identifier of the second device corresponds to the identifier of the device group to which the second device belongs, an operation corresponding to the identifier of the first device group is performed on the second device.

10. The method according to any one of claims 2 to 9, characterized in that The sending the identifier of the second IoT device group to the second device includes: Sending identification information allocated by the core network to the second device to the second device, where the identification information includes an identifier of a device group to which the second device belongs.

11. The method according to claim 10, characterized in that The identification information includes any of the following: Globally unique temporary identifier, temporary mobile station identifier, international mobile subscriber identity code, passive IoT device identifier, product electronic code.

12. A communication method, characterized in that: include: The second device receives an identifier of a first device group sent by an Internet of Things management function network element through a first device, wherein the first device is a device having a read and / or write function, and the second device is an Internet of Things device; Determining, by the second device, that the identifier of the first device group corresponds to the identifier of the device group to which the second device belongs; The second device sends the identifier of the device group to which the second device belongs to the Internet of Things management function network element, and the identifier of the device group to which the second device group belongs is used to determine whether to perform an operation corresponding to the identifier of the first device group on the second device.

13. The method according to claim 12, characterized in that Before the second device sends the identifier of the device group to which the second device belongs to the Internet of Things management function network element, the method further includes: The second device sends a registration request to the Internet of Things management function network element, where the registration request includes an identifier of the second device; The second device receives an identifier of a device group to which the second device belongs, which is sent by the Internet of Things management function network element, and the identifier of the device group to which the second device belongs corresponds to the identifier of the second device.

14. The method according to claim 12, characterized in that Before the second device sends the identifier of the device group to which the second device belongs to the Internet of Things management function network element, the method further includes: In the first process, the second device receives an identifier of a device group to which the second device belongs, which is sent by the Internet of Things management function network element.

15. The method according to claim 14, characterized in that The first process includes any one of the following processes: Registration process, inventory process, write process, or configuration update process.

16. The method according to claim 15, characterized in that When the first process is a registration process, before the second device receives the identifier of the device group to which the second device belongs, sent by the Internet of Things management function network element, the method further includes: The second device receives a random access request sent by the first device; Execute a random access procedure according to the random access request; The second device receives, from the Internet of Things management function network element, an identifier of a device group to which the second device belongs, including: The second device sends a registration request to the Internet of Things management function network element, where the registration request includes an identifier of the second device; The second device receives a registration acceptance message sent by the Internet of Things management function network element, where the registration acceptance message carries an identifier of the device group to which the second device belongs.

17. The method according to any one of claims 13 to 16, characterized in that The second device receives, from the Internet of Things management function network element, an identifier of a device group to which the second device belongs, including: The second device receives identification information allocated to the second device by the core network and sent by the Internet of Things management function network element, where the identification information includes an identification of a device group to which the second device belongs.

18. The method according to claim 17, characterized in that The identification information includes any of the following: Globally unique temporary identifier, temporary mobile station identifier, international mobile subscriber identity code, passive IoT device identifier, product electronic code.

19. A communication device, characterized in that: include: A processor, wherein the processor is configured to execute a computer program stored in a memory, so that the apparatus executes the method according to any one of claims 1 to 11, or executes the method according to any one of claims 12 to 18.

20. The device according to claim 19, characterized in that The apparatus also includes the memory.

21. A communication system, characterized in that: It includes at least one of an Internet of Things management function network element, a network open function network element and an Internet of Things device, The Internet of Things management function network element is used to execute the method as described in any one of claims 1 to 5 and 8 to 11, the network open function network element is used to execute the method as described in any one of claims 6 or 7, and the Internet of Things device is used to execute the method as described in any one of claims 12 to 18.

22. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed on a computer, the computer is enabled to execute the method according to any one of claims 1 to 11, or execute the method according to any one of claims 12 to 18.

23. A computer program product, characterized in that The computer program product comprises instructions for executing the method of any one of claims 1 to 11, or comprises instructions for executing the method of any one of claims 12 to 18.

Images