Communication method, and apparatus

Abstract

The present application provides a communication method, and an apparatus. The method comprises: a reader-writer acquires one or more first identifiers and time information corresponding to each first identifier among the one or more first identifiers, the one or more first identifiers corresponding to a first service requester; and the reader-writer broadcasts the one or more first identifiers on the basis of the time information corresponding to each first identifier among the one or more first identifiers. The mode helps the reader-writer to trigger the service inventory of the first service requester in a specific time period instead of triggering the service inventory of all service requesters in the coverage range of the reader-writer, thus reducing the signaling overhead.

Description

A communication method and apparatus

[0001] This application claims priority to Chinese Patent Application No. 202311485190.6, filed on November 7, 2023, entitled "A Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of Internet of Things (IoT) technology, and in particular to a communication method and apparatus. Background Technology

[0003] Environmental IoT technology refers to IoT technologies that obtain energy from the environment without being equipped with or relying on batteries, to support data sensing, transmission, and distributed computing. Environmental IoT technology can be applied to business inventory management.

[0004] In environmental IoT-based service inventory management, the service requester sends an inventory command to the base station through the core network. This triggers the base station to randomly connect to and report the identification information of IoT devices within the campus. The core network then sends the identification information of the IoT devices to the service requester, thus completing the service inventory management. Alternatively, the service requester can pre-configure the network to periodically report the IoT devices present in the campus, causing the base station to periodically trigger these devices to report their identification information, thereby achieving service inventory management.

[0005] However, within the same industrial park, there may be IoT devices managed by different service requesters, and these different service requesters may have different needs for inventory management. If the base station triggers inventory management, it may cause multiple IoT devices managed by different service requesters within the park to randomly connect and report identification information, resulting in a significant waste of signaling.

[0006] Summary of the Invention

[0007] This application provides a communication method and apparatus that helps reduce signaling overhead.

[0008] Firstly, embodiments of this application provide a communication method, which can be executed by a reader / writer. The reader / writer can refer to the reader / writer itself, or to a processor, module, chip, or chip system within the reader / writer that implements the method. In this method, the reader / writer acquires one or more first identifiers, and time information corresponding to each of the one or more first identifiers, where each of the one or more first identifiers corresponds to a first service requester. The reader / writer broadcasts the one or more first identifiers based on the time information corresponding to each of the one or more first identifiers.

[0009] In this embodiment, the reader broadcasts one or more first identifiers based on the time information corresponding to each of the one or more first identifiers corresponding to the first service requester, thereby triggering the service inventory of the first service requester or triggering the access process of the IoT terminal corresponding to the first service requester. Compared with the reader broadcasting all identifiers supported by the reader, this method is advantageous in triggering the service inventory of the first service requester within a specific time period, rather than triggering the service inventory of all service requesters within the coverage area of ​​the reader, thus reducing signaling overhead.

[0010] In one optional implementation, after the reader broadcasts one or more first identifiers, it may further perform the following: receiving identification information from a first IoT device, the identification information being used to identify the first IoT device, the first IoT device being an IoT device managed by a first service requester; and sending first information to the core network device, the first information including the identification information.

[0011] As can be seen, the reader can also obtain the identification information reported by the first IoT device managed by the first service requester, and send the identification information to the core network device to realize the service inventory of the first service requester.

[0012] In one optional implementation, the reader acquires one or more first identifiers and time information corresponding to each of the one or more first identifiers, including: receiving one or more first identifiers from the core network device and time information corresponding to each of the one or more first identifiers.

[0013] Understandably, the first service requester sends one or more first identifiers, along with time information corresponding to each of the one or more first identifiers, to the core network device. The core network device then sends one or more first identifiers, along with time information corresponding to each of the one or more first identifiers, to the reader / writer. Consequently, the reader / writer receives one or more first identifiers from the core network device, along with time information corresponding to each of the one or more first identifiers.

[0014] In one optional implementation, the reader further acquires one or more second identifiers, and time information corresponding to each of the one or more second identifiers, wherein the one or more second identifiers correspond to a second service requester; and broadcasts the one or more second identifiers based on the time information corresponding to each of the one or more second identifiers. The time information corresponding to the first identifier is different from the time information corresponding to the second identifier.

[0015] Optionally, one or more first identifiers are used to trigger the business inventory of the first business requester, and one or more second identifiers are used to trigger the business inventory of the second business requester.

[0016] As can be seen, the reader broadcasts the identifiers corresponding to different service requesters at different times, thereby triggering the service inventory of different service requesters at different times, rather than triggering the service inventory of multiple service requesters at the same time, which can reduce signaling overhead.

[0017] In one optional implementation, the first information further includes a third identifier and / or a timestamp of the third identifier broadcast by the reader / writer. The third identifier is the first identifier that the first IoT device responds to when sending the identifier information, and the third identifier is one of one or more first identifiers.

[0018] As can be seen, the identification information used to identify the first IoT device is sent by the first IoT device in response to a third identifier among one or more first identifiers, and the reader sends the third identifier to the core network device through the first information, or sends the timestamp of the third identifier broadcast by the reader. This method is beneficial for the core network device to determine the first service requester managing the first IoT device based on the third identifier or the timestamp of the third identifier broadcast by the reader.

[0019] In one optional implementation, the first information further includes the location information of the first IoT device. This approach helps the core network equipment determine the location of the first IoT device.

[0020] In one optional implementation, the time information corresponding to different first identifiers among one or more first identifiers is different. Therefore, the reader broadcasts different times for each of the one or more first identifiers.

[0021] In one optional implementation, the reader also broadcasts storage area information, which characterizes a storage area storing one or more first identifiers. This approach allows IoT devices to determine whether a match exists or whether to respond to a broadcast message containing one or more first identifiers based on the storage area storing those identifiers.

[0022] In one optional implementation, the time information corresponding to the first identifier can be a broadcast time requirement, that is, a time requirement for broadcasting the first identifier.

[0023] Optionally, the time information for the first broadcast identifier includes one or more of the following: transmission time, transmission period, validity period, transmission frequency, and transmission interval. The transmission time can be one or more of the following: start time, time interval, end time, and transmission duration.

[0024] In one optional implementation, one or more first identifiers are Closed Access Group Identifiers (CAG IDs), which are identifiers used by IoT devices to connect to a private network through a specific area. This approach allows readers and IoT devices to reuse existing identifiers, reducing modifications to the protocol.

[0025] In one optional implementation, one or more first identifiers correspond to environmental IoT services. Therefore, the service managed by the first service requester is the environmental IoT service.

[0026] In one optional implementation, the reader may further perform: acquiring second information, the second information being used to instruct updating the first identifier corresponding to the first service requester; and updating the first identifier corresponding to the first service requester based on the second information.

[0027] In one optional implementation, one or more first identifiers are identifiers used by IoT devices to access the cell, or identifiers of the first service requester, or identifiers of the first service requester's service, or group identifiers.

[0028] Secondly, embodiments of this application also provide a communication method, which can be executed by a core network device. This core network device can refer to the core network device itself, or to a processor, module, chip, or chip system within the core network device that implements the method. In this method, the core network device receives first information sent by a reader / writer. The first information includes identification information used to identify a first IoT device. The core network device determines a first service requester that manages the first IoT device. The core network device sends the identification information to the first service requester.

[0029] In this embodiment of the application, after the core network device receives the identification information used to identify the first IoT device, it sends the identification information to the first service requester that manages the first IoT device. This enables the service inventory of the first service requester, which can reduce signaling overhead.

[0030] In one optional implementation, the first information further includes a third identifier and / or a timestamp of the third identifier broadcast by the reader / writer, and the first service requester is the service requester corresponding to the third identifier.

[0031] In one optional implementation, the first information further includes a third identifier and / or a timestamp of the third identifier broadcast by the reader / writer. When the core network device determines the first service requester managing the first IoT device, the first service requester is determined based on the third identifier and / or the timestamp of the third identifier broadcast by the reader / writer.

[0032] In another optional implementation, the core network device determines the first service requester that manages the first IoT device, including: determining the first service requester that manages the first IoT device from one or more service requesters based on the subscription information of the first IoT device, wherein the subscription information includes the association between the first IoT device and the first service requester.

[0033] In one optional implementation, the first information includes a third identifier, and when the third identifier is a CAG ID, the core network device, before determining the first service requester managing the first IoT device, also allows the first IoT device to access the network through the cell corresponding to the third identifier. Therefore, the core network device can also perform access control on the first IoT device based on the received CAG ID, which is a CAI ID allowed by the first IoT device.

[0034] In one optional implementation, the third identifier is a Closed Access Group ID (CAG ID). This approach allows readers and IoT devices to reuse existing identifiers, reducing modifications to the protocol.

[0035] In one optional implementation, the third identifier corresponds to the environmental IoT service. Therefore, the service managed by the first service requester is the environmental IoT service.

[0036] In one optional implementation, the first information further includes the location information of the first IoT device. Therefore, the core network device also sends the location information of the first IoT device to the first service requester. This method helps the first service requester determine the location of the first IoT device.

[0037] In one optional implementation, the third identifier is the identifier used by the IoT device to access the cell, or the identifier of the first service requester, or the identifier of the service of the first service requester, or the group identifier.

[0038] Thirdly, embodiments of this application also provide a communication method, which can be executed by a first service requester. The first service requester can refer to the first service requester itself, or to a processor, module, chip, or chip system within the first service requester that implements the method. In this method, the first service requester sends one or more first identifiers corresponding to the first service requester, and time information corresponding to each of the one or more first identifiers. The first service requester receives identification information from a core network device. This identification information is used to identify a first IoT device, and the identification information is sent by the first IoT device in response to a third identifier broadcast by a reader / writer. The third identifier is one of one or more first identifiers, and the first IoT device is an IoT device managed by the first service requester.

[0039] In this embodiment, the first service requester sends one or more first identifiers corresponding to itself, as well as time information corresponding to each of the one or more first identifiers, and receives identification information used to identify the first IoT device. The first IoT device is an IoT device managed by the first service requester, thus enabling the inventory of the first service requester's services.

[0040] In one optional implementation, different first identifiers among one or more first identifiers correspond to different time information. This method is beneficial for the reader to broadcast different first identifiers at different times.

[0041] In one optional implementation, the time information includes one or more of the following: transmission time, transmission period and validity period, transmission frequency, and transmission interval. The transmission time can be one or more of the following: start time, time interval, end time, and transmission duration.

[0042] In one optional implementation, one or more first identifiers are Closed Access Group Identifiers (CAG IDs), which are identifiers used by IoT devices to connect to a private network through a specific area. This approach allows readers and IoT devices to reuse existing identifiers, reducing modifications to the protocol.

[0043] In one optional implementation, one or more first identifiers correspond to environmental IoT services, that is, the services managed by the first service requester are environmental IoT services.

[0044] In one optional implementation, the third identifier is the identifier used by the IoT device to access the cell, or the identifier of the first service requester, or the identifier of the service of the first service requester, or the group identifier.

[0045] Fourthly, embodiments of this application also provide a communication method, which can be executed by a reader / writer. Here, the reader / writer can refer to the reader / writer itself, or to a processor, module, chip, or chip system within the reader / writer that implements the method. In this method, the reader / writer acquires one or more access group identifiers and the time information corresponding to the one or more access group identifiers; the reader / writer broadcasts the one or more access group identifiers based on the time information corresponding to the one or more access group identifiers.

[0046] In this embodiment, the reader broadcasts one or more access group identifiers based on time information corresponding to those identifiers, enabling multiple IoT devices to initiate registration processes with the network at different times or within different time periods based on their acquired access group identifiers. This method reduces network congestion compared to multiple IoT devices initiating registration processes with the network at the same time or within the same time period.

[0047] In one optional implementation, the reader broadcasts one or more access group identifiers based on time information corresponding to one or more access group identifiers. This can be achieved by broadcasting some or all of the access group identifiers based on time information corresponding to some or all of the access group identifiers.

[0048] In one optional implementation, when the reader broadcasts one or more access group identifiers based on time information corresponding to one or more access group identifiers, it also broadcasts the first tracking area identifier (TAI) corresponding to the reader. For example, when the reader broadcasts access group identifier a based on the time information of access group identifier a, it also broadcasts the first TAI; when it broadcasts access group identifier b based on the time information of access group identifier b, it also broadcasts the first TAI. This implementation is beneficial because multiple IoT devices moving to the area corresponding to the first TAI can initiate a registration process with the network at different times or different time periods based on their own acquired access group identifiers. Compared with multiple IoT devices moving to the area corresponding to the first TAI initiating a registration process with the network at the same time or at the same point in time, this can reduce network congestion.

[0049] In one optional implementation, after the reader broadcasts one or more access group identifiers, it may further perform the following steps: receiving a registration request from a second IoT device, the registration request including the identification information of the second IoT device, wherein the second IoT device is either an IoT device that has obtained the first access group identifier currently broadcast by the reader, or an IoT device that has switched to the area corresponding to the first TAI and has obtained the first access group identifier currently broadcast by the reader; and sending the identification information of the second IoT device to the core network device. The first access group identifier is one of one or more access group identifiers.

[0050] As can be seen, in this embodiment, the second IoT device that obtains the first access group identifier currently broadcast by the reader can send a registration request to the reader to request network registration; or, the second IoT device that has switched to the area corresponding to the first TAI and has obtained the first access group identifier currently broadcast by the reader can send a registration request to the reader to request network registration. Furthermore, the reader sends the identification information of the second IoT device to the core network device so that the core network device can perform security verification on the second IoT device and determine whether to allow the second IoT device to access the network.

[0051] In one optional implementation, the reader acquires one or more access group identifiers and time information corresponding to the one or more access group identifiers, including: receiving one or more access group identifiers and time information corresponding to the one or more access group identifiers from the core network device.

[0052] As can be seen, in this embodiment, one or more access group identifiers, and the time information corresponding to one or more access group identifiers, can be sent by the core network device to the reader, so that the reader can broadcast different access group identifiers based on the time information corresponding to different access group identifiers, so that different IoT devices can initiate the registration process at different times or different time periods, thereby reducing network congestion.

[0053] In another optional implementation, the reader is configured with one or more access group identifiers and corresponding time information. In this method, the reader obtains one or more access group identifiers and their corresponding time information, which can be understood as: obtaining one or more access group identifiers and their corresponding time information through configuration information. The configuration information can be pre-configured for the reader by the core network equipment.

[0054] In one optional implementation, the time information corresponding to different access group identifiers in one or more access group identifiers is different. Therefore, the reader broadcasts the different times for the different access group identifiers in one or more access group identifiers, which is beneficial for different physical network devices to initiate registration processes with the network at different times or different time periods based on their own acquired access group identifiers.

[0055] In one optional implementation, the time information corresponding to the access group identifier can be a broadcast time requirement, that is, a time requirement for broadcasting the access group identifier.

[0056] In one optional implementation, the time information of the broadcast access group identifier includes one or more of the following: transmission time, transmission period, validity period, transmission frequency, and transmission interval. The transmission time can be one or more of the start time, time interval, end time, and transmission duration. Therefore, the time information corresponding to the access group identifier can be presented in various forms.

[0057] In one optional implementation, one or more access group identifiers are access identifiers used by IoT devices when accessing the cell, such as CAG IDs. This method allows readers and IoT devices to reuse existing access identifiers, reducing changes to the protocol.

[0058] In one optional implementation, the reader can also perform the following: send TAI update information to the second IoT device, the TAI update information including the identifier of the first TAI. This approach is advantageous because the second IoT device does not need to frequently initiate a registration process with the network when it is still within the area corresponding to the first TAI, but only initiates a registration process with the network after moving to the area corresponding to the first TAI, which can reduce the power consumption of the second IoT device.

[0059] Fifthly, embodiments of this application also provide a communication method, which can be executed by an Internet of Things (IoT) device. Here, the IoT device can refer to the IoT device itself, or to a processor, module, chip, or chip system within the IoT device that implements the method. In this method, a second IoT device receives a first access group identifier broadcast by a reader / writer. The second IoT device is an IoT device that possesses the first access group identifier. The second IoT device sends a registration request to the reader / writer, the registration request including the identification information of the second IoT device.

[0060] As can be seen, in this embodiment, an IoT device that has obtained the first access group identifier can initiate a registration process with the reader after receiving the first access group identifier broadcast by the reader. This method reduces network congestion compared to the situation where IoT devices can initiate a registration process with the reader at any time, resulting in multiple IoT devices initiating registration processes with the reader at the same time or within the same time period.

[0061] In one optional implementation, the second IoT device further receives a first TAI broadcast by the reader. In this approach, the second IoT device can be an IoT device that has switched from other TAIs to the first TAI and obtained a first access group identifier. This method allows multiple IoT devices switching from other TAIs to the first TAI to initiate a registration process with the network only after obtaining the access group identifier currently broadcast by the reader. Compared to multiple IoT devices switching from other TAIs to the first TAI initiating a registration process with the network at the same time or within the same time period, this reduces network congestion.

[0062] In one optional implementation, the second IoT device acquires a first access group identifier, which can be understood as: the second IoT device is pre-configured with a first access group identifier.

[0063] In another optional implementation, the second IoT device obtains the first access group identifier, which can be understood as: the core network device sends the first access group identifier to the second IoT device through a reader / writer.

[0064] It is evident that the first access group identifier obtained by the second IoT device can be either pre-configured or received from the core network device.

[0065] Sixthly, embodiments of this application also provide a communication device. This communication device has some or all of the functions of the reader / writer described in the first or fourth aspect, or some or all of the functions of the core network device described in the second aspect, or some or all of the functions of the first service requester described in the third aspect, or some or all of the functions of the IoT device described in the fifth aspect. For example, the communication device may possess some or all of the functions of the reader / writer described in the first aspect of this application, or it may possess the functions of any one of the embodiments of this application implemented individually. The functions can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0066] In one possible design, the communication device may include a processing unit and a communication unit. The processing unit is configured to support the communication device in performing the corresponding functions described in the above method. The communication unit is used to support communication between the communication device and other communication devices. The communication device may also include a storage unit coupled to the processing unit and the communication unit, which stores necessary program instructions and data for the communication device.

[0067] In one embodiment, the communication device includes a processing unit and a communication unit, the device being applied to a reader / writer, and the communication unit being used for sending and receiving signals / signaling.

[0068] The processing unit is configured to acquire one or more first identifiers, and time information corresponding to each of the one or more first identifiers, wherein the one or more first identifiers correspond to a first service requester;

[0069] The processing unit is further configured to broadcast the one or more first identifiers according to the time information corresponding to each of the one or more first identifiers.

[0070] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the first aspect above, and will not be described in detail here.

[0071] In another embodiment, the communication device includes a processing unit and a communication unit, and the device is applied to core network equipment;

[0072] The communication unit is used to receive first information sent by the reader, the first information including identification information, the identification information being used to identify the first Internet of Things device;

[0073] The processing unit is used to determine the first service requester that manages the first IoT device;

[0074] The communication unit is also used to send the identification information to the first service requester.

[0075] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the second aspect above, and will not be described in detail here.

[0076] In another embodiment, the communication device includes a processing unit and a communication unit, the device being applied to a first service requester, and the processing unit being used to process signals / signaling;

[0077] The communication unit is used to send one or more first identifiers corresponding to the first service requester, and time information corresponding to each of the one or more first identifiers;

[0078] The communication unit is further configured to receive identification information, which is used to identify the first IoT device. The identification information is sent by the first IoT device in response to a third identifier broadcast by the reader / writer. The third identifier is one of the one or more first identifiers. The first IoT device is an IoT device managed by the first service requester.

[0079] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the third aspect above, and will not be described in detail here.

[0080] In another embodiment, the communication device includes a processing unit and a communication unit, the device being applied to a reader / writer, and the communication unit being used for sending and receiving signals / signaling.

[0081] The processing unit is used to obtain one or more access group identifiers and time information corresponding to one or more access group identifiers;

[0082] The processing unit is further configured to broadcast one or more access group identifiers based on the time information corresponding to one or more access group identifiers.

[0083] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the fourth aspect above, and will not be described in detail here.

[0084] In another embodiment, the communication device includes a processing unit and a communication unit, the device being applied to an Internet of Things (IoT) device, and the processing unit being used to process signals / signaling.

[0085] The communication unit is used to receive the first access group identifier broadcast by the reader / writer, and the communication device is an Internet of Things device that obtains the first access group identifier.

[0086] The communication unit is also used to send a registration request to the reader / writer, the registration request including the identification information of the second Internet of Things device.

[0087] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the fifth aspect above, and will not be described in detail here.

[0088] In one embodiment, the communication device includes a processor and a transceiver, the device being applied to a reader / writer, and the transceiver being used for sending and receiving signals / signaling.

[0089] The processor is configured to acquire one or more first identifiers, and time information corresponding to each of the one or more first identifiers, wherein the one or more first identifiers correspond to a first service requester;

[0090] The processor is further configured to broadcast the one or more first identifiers according to the time information corresponding to each of the one or more first identifiers.

[0091] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the first aspect above, and will not be described in detail here.

[0092] In another embodiment, the communication device includes a processor and a transceiver, and the device is applied to core network equipment;

[0093] The transceiver is used to receive first information sent by the reader, the first information including identification information, the identification information being used to identify the first Internet of Things device;

[0094] The processor is further configured to determine a first service requester that manages the first IoT device;

[0095] The transceiver is also used to send the identification information to the first service requester.

[0096] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the second aspect above, and will not be described in detail here.

[0097] In another embodiment, the communication device includes a processor and a transceiver, the device being applied to a first service requester, the processor being used to process signals / signaling;

[0098] The transceiver is used to send one or more first identifiers corresponding to the first service requester, and time information corresponding to each of the one or more first identifiers;

[0099] The transceiver is also used to receive identification information, which is used to identify the first IoT device. The identification information is sent by the first IoT device in response to a third identifier broadcast by the reader / writer. The third identifier is one of the one or more first identifiers. The first IoT device is an IoT device managed by the first service requester.

[0100] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the third aspect above, and will not be described in detail here.

[0101] In another embodiment, the communication device includes a processor and a transceiver, the device being applied to a reader / writer, the transceiver being used for sending and receiving signals / signaling;

[0102] The processor is used to acquire one or more access group identifiers and time information corresponding to one or more access group identifiers;

[0103] The processor is further configured to broadcast one or more access group identifiers based on time information corresponding to one or more access group identifiers.

[0104] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the fourth aspect above, and will not be described in detail here.

[0105] In another embodiment, the communication device includes a processor and a transceiver, the device being applied to an Internet of Things (IoT) device, the processor being used to process signals / signaling;

[0106] The transceiver is used to receive the first access group identifier broadcast by the reader / writer, and the communication device is an Internet of Things device that obtains the first access group identifier.

[0107] The transceiver is also used to send a registration request to the reader, the registration request including the identification information of the second Internet of Things device.

[0108] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the fifth aspect above, and will not be described in detail here.

[0109] In another embodiment, the communication device is a chip or chip system. The processing unit may also be a processing circuit or logic circuit; the communication unit may be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip or chip system.

[0110] In implementation, the processor can be used for, but is not limited to, baseband-related processing, and the transceiver can be used for, but is not limited to, radio frequency transceiver. These devices can be disposed on separate chips, or at least partially or entirely on the same chip. For example, the processor can be further divided into analog baseband processors and digital baseband processors. The analog baseband processor can be integrated with the transceiver on the same chip, while the digital baseband processor can be disposed on a separate chip. With the continuous development of integrated circuit technology, more and more devices can be integrated on the same chip. For example, a digital baseband processor can be integrated with multiple application processors (e.g., but not limited to graphics processors, multimedia processors, etc.) on the same chip. Such a chip can be called a system-on-a-chip (SoC). Whether the various devices are disposed independently on different chips or integrated on one or more chips often depends on the needs of the product design. This application does not limit the implementation form of the above-mentioned devices.

[0111] Seventhly, embodiments of this application also provide a processor for executing the various methods described above. During the execution of these methods, the processes related to sending and receiving the aforementioned information can be understood as the processor outputting the aforementioned information and the processor receiving the input information. When outputting the aforementioned information, the processor outputs the information to a transceiver for transmission. After being output by the processor, the information may require further processing before reaching the transceiver. Similarly, when the processor receives the input information, the transceiver receives the information and inputs it to the processor. Furthermore, after the transceiver receives the information, the information may require further processing before being input to the processor.

[0112] Unless otherwise specified, or unless it contradicts its actual function or internal logic in the relevant description, the transmission and reception operations involved by the processor can be more generally understood as processor output and reception, input and other operations, rather than transmission and reception operations directly performed by radio frequency circuits and antennas.

[0113] In implementation, the processor can be a dedicated processor for executing these methods, or it can be a processor that executes computer instructions stored in memory to execute these methods, such as a general-purpose processor. The memory can be a non-transitory memory, such as read-only memory (ROM), which can be integrated with the processor on the same chip or disposed on different chips. This application does not limit the type of memory or the arrangement of the memory and processor.

[0114] Eighthly, embodiments of this application also provide a communication system that may include a reader / writer and core network equipment. In another possible design, the system may further include other devices that interact with the reader / writer and core network equipment, such as IoT devices and service requesters.

[0115] Ninthly, embodiments of this application provide a computer-readable storage medium for storing instructions that, when executed by a computer, implement the method described in any one of the first to fifth aspects.

[0116] In a tenth aspect, embodiments of this application also provide a computer program product including instructions that, when run on a computer, implement the method described in any one of the first to fifth aspects.

[0117] Eleventhly, embodiments of this application provide a chip system including a processor. The processor is configured to invoke the program or instructions to implement or support a reader / writer in implementing the functions involved in the first or fourth aspects, or to implement or support a core network device in implementing the functions involved in the second aspect, or to implement or support a first service requester in implementing the functions involved in the third aspect, or to implement or support an Internet of Things (IoT) device in implementing the functions involved in the fifth aspect. For example, determining or processing at least one of the data and information involved in the above methods. In one possible design, the chip system further includes a communication interface for acquiring programs or instructions. In one possible design, the chip system further includes a memory for storing necessary program instructions and data for the terminal. This chip system may be composed of chips or may include chips and other discrete devices.

[0118] In a twelfth aspect, embodiments of this application provide a communication device including a processor for executing a computer program or executable instructions stored in a memory, wherein when the computer program or executable instructions are executed, the device performs the methods as described in various possible implementations of the first to fifth aspects.

[0119] In one possible implementation, the processor and memory are integrated together; in another possible implementation, the memory is located outside the communication device.

[0120] The beneficial effects of aspects six through twelfth can be referenced from the beneficial effects of aspects one through five, and will not be repeated here. Attached Figure Description

[0121] Figure 1 is a schematic diagram of a system architecture;

[0122] Figure 2 is a schematic diagram of a passive Internet of Things (IoT) service;

[0123] Figure 3 is a schematic diagram of another passive IoT service;

[0124] Figure 4 is a schematic diagram of another type of passive IoT service;

[0125] Figure 5 is a schematic diagram of an SNPN service and a PLMN / PNI-NPN service;

[0126] Figure 6 is a schematic diagram of the registration process for a terminal device;

[0127] Figure 7 is a schematic diagram of the business inventory process for a label;

[0128] Figure 8 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0129] Figure 9 is an interactive schematic diagram of another communication method provided in an embodiment of this application;

[0130] Figure 10 is an interactive schematic diagram of another communication method provided in an embodiment of this application;

[0131] Figure 11 is an interactive schematic diagram of another communication method provided in an embodiment of this application;

[0132] Figure 12 is an interactive schematic diagram of another communication method provided in an embodiment of this application;

[0133] Figure 13 is an interactive schematic diagram of another communication method provided in an embodiment of this application;

[0134] Figure 14 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0135] Figure 15 is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0136] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0137] To better understand the embodiments of this application, the system architecture involved in the embodiments of this application will be described first below:

[0138] The embodiments of this application can be applied to fourth-generation (4G) mobile communication systems, fifth-generation (5G) mobile communication systems, long-term evolution (LTE) communication systems, non-terrestrial network (NTN) communication systems, vehicle-to-everything (V2X), long-term evolution-vehicle (LTE-V), machine-type communications (MTC), internet of things (IoT), machine-to-machine (M2M), long-term evolution-machine-to-machine (LTE-M), or future mobile communication systems, etc.

[0139] Please refer to Figure 1, which is a schematic diagram of a system architecture provided in an embodiment of this application. As shown in Figure 1, the system architecture includes an Internet of Things (IoT) device, a reader, a core network (CN), and a service requester. The IoT device can be an ambient IoT device, a passive IoT device, or a non-ambient IoT device; this embodiment of the application does not limit its application in this regard. The IoT device can be in the form of a tag, a sensor, or any other terminal; this embodiment of the application does not limit its application in this regard. Other terminal forms include mobile phones, tablets, computers with wireless transceiver capabilities, virtual reality (VR) terminals, augmented reality (AR) terminals, wireless terminals in industrial control, vehicle-mounted terminals, wireless terminals in self-driving vehicles, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, wearable terminals, etc. IoT devices can also be called IoT terminals, and this application does not limit the naming. IoT devices can be fixed or mobile. It is understood that all or part of the functions of the IoT devices in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform).

[0140] The reader / writer can be an access network device. It can also be a terminal device, such as a mobile phone, IoT device, handheld reader / writer, or other forms of terminal device. This application does not limit the form of the reader / writer. The name of the reader / writer is also not limited in this application; it can be called a reader or other names, meaning the terms "reader" and "reader / writer" are interchangeable. The reader / writer possesses the functions described in this application, such as the ability to perform the operations described in this application (e.g., acquiring tag information, inventory operations, read operations, write operations, invalidation operations, or message interaction operations with the tag) on ​​IoT devices (e.g., tags), the ability to acquire billing-related information and / or billing information, and the ability to send billing information to the charging function (CHF). The reader / writer can conduct contactless two-way data communication with IoT devices via radio frequency (RF), for example, using RF to read and write electronic tags or RFID cards, thereby achieving target identification and data exchange. There are two ways for readers and IoT devices to work. One way is that when an IoT device enters the effective identification range of the reader, it receives the radio frequency signal emitted by the reader and uses the energy obtained by the induced current to send out the information stored in the chip. The other way is that the IoT device stores some electrical energy through solar energy or other means, so that it can actively send a signal of a certain frequency. The reader receives the information from the IoT device, decodes it, and sends it to the central information system for relevant data processing.

[0141] Access network equipment includes, but is not limited to: next-generation node B (gNB), evolved node B (eNB), next-generation eNB (ng-eNB), radio backhaul equipment, radio network controller (RNC), node B (NB), home evolved node B (HeNB) or (home node B (HNB)), baseband unit (BBU), transmitting and receiving point (TRP), transmitting point (TP), mobile switching center, device-to-device (D2D), equipment performing base station functions in V2X and M2M communications, pole station, macro station, micro base station, small station (e.g., called Lampsite), integrated access and backhaul node (IAB node), etc., and may also include centralized unit (CU) and distributed unit (CU) in cloud radio access network (C-RAN) systems. Network devices in unit (DU) and NTN communication systems can be deployed on high-altitude platforms or satellites, etc., and this application does not specifically limit them.

[0142] The core network may include one or more core network devices (core network devices may also be referred to as core network elements, core network functions, or core network function elements). In one optional implementation, the core network may include multiple core network devices, such as: access and mobility management function (AMF), IoT terminal management function, user plane function (UPF), session management function (SMF), unified data management (UDM), user data repository (UDR), network exposure function (NEF), network slice specific authentication and authorization function (NSSAAF), application function (AF), network slice selection function (NSSF), and network slice admission control function (NSACF). Wherein:

[0143] AMF can also be referred to as an Access and Mobility Management device, Access and Mobility Management Functional Entity, Access and Mobility Management Functional Network Element, Mobility Management Device, Mobility Management Network Element, or Mobility Management Entity. This device is used to manage the access control and mobility of user equipment. In practical applications, it includes the access and mobility management functions of the Mobility Management Entity (MME) in the LTE network framework, and adds access management functions. Specifically, it can be responsible for user equipment registration, mobility management, tracking area update procedures, reachability detection, selection of session management network elements, and mobility state transition management. For example, in 5G, the access and mobility management network element can be an AMF network element. In future communications, such as 6G, the access and mobility management network element can still be an AMF network element, or it may have other names; this application does not limit this. When the access and mobility management network element is an AMF network element, the AMF can provide Namf services.

[0144] The IoT terminal management function can be a tag management function (TMF) or an ambient IoT management function (AIMF). This function is used to transmit business data from IoT devices or to manage IoT devices (or tags). For example, if the IoT device is a tag, it can transmit and / or manage the tag's business data. This application does not limit the naming of the IoT terminal management function (or tag management function); it can have other names.

[0145] UPF (also known as User Plane Device) is responsible for forwarding and receiving user data within the user equipment. UPF can receive user data from the data network and transmit it to the user equipment via access network elements; UPF can also receive user data from the user equipment via access network elements and forward it to the data network. The transmission resources and scheduling functions providing services to the user equipment in UPF are managed and controlled by the session management function network element.

[0146] A Session Management Function (SMF) is responsible for session management of user equipment (including session establishment, modification, and release), selection and reselection of user plane function network elements, allocation of Internet Protocol (IP) addresses for the user equipment, and quality of service (QoS) control. For example, in 5G, the session management network element can be a Session Management Function (SMF) network element. In future communication systems, such as 6G, the session management network element can still be an SMF network element, or it may have other names; this application does not limit this. When the session management network element is an SMF network element, the SMF can provide NSMF services.

[0147] UDM can also be referred to as a unified data management device, a unified data management network element, a data management device, or a unified data management entity. UDM is used to handle terminal device identification, access authentication, registration, and mobility management. In 5G communication systems, unified data management can be either a UDM or a unified data management device. In future communication systems, such as 6G, unified data management can also be a UDM network element, or it can have other names; this application does not limit the specific names. A unified data management device can be a core network device. A unified data management device can be a control plane device.

[0148] UDR, also known as User Database Device, User Database Entity, or User Database Network Element, can be understood as the naming convention for a unified data storage network element in the 5G architecture. The user database primarily includes the following functions: access to data types such as subscription data, policy data, and application data.

[0149] A service requester (or operation requester or third party) can be understood as a device that sends service requests or operation instructions. For example, a service requester can be a server, a passive internet of things application function (P-IoT AF), an ambient internet of things application function (A-IoT AF), an AF (Automatic Application Function), or any other device that sends service requests or operation instructions. For instance, an application function can be a server. A service requester can correspond to a certain type of user, which can include enterprises, tenants, third parties, or companies, without restriction. Corresponding to a certain type of user means that the service requester belongs to that type of user and is managed by that type of user. The service requester can send an inventory instruction to the reader / writer through the core network, thereby triggering the IoT device to report its identification information. The reader / writer then sends the IoT device's identification information to the service requester through the core network to realize the inventory service.

[0150] In one possible implementation, the IoT device is a tag, and the service requester is a server or application function. The reader can send instructions from the server or application function to the tag, or the reader can send messages from the tag to the server or application function. In another possible implementation, the reader can retrieve information stored in a specified tag based on instructions issued by the server. For example, in an inventory operation (or storage operation), the reader retrieves the tag's identification information; this identification information can be a unique identifier or a temporary identifier for the tag. For example, in a read operation, the reader reads the data from the tag's storage area. Optionally, in situations where it is necessary to rewrite the information stored in the tag, the reader can also have a write function; for example, in a write operation, the reader writes data to the tag's storage area. In addition, the reader can also perform an invalidation operation on the tag. After an invalidation operation is performed, the tag becomes invalid and cannot be used for operations such as retrieving tag information, inventory operations, read operations, message interaction with the tag, or write operations. In one possible implementation, preventing tag information retrieval due to tag failure can be understood as the reader being unable to obtain tag information after a tag fails. In another possible implementation, preventing tag message interaction can be understood as the reader being unable to interact with the failed tag after it fails.

[0151] The following describes the relevant concepts involved in the embodiments of this application:

[0152] 1. Environmental Internet of Things (IoT), and IoT devices within the environmental IoT.

[0153] Environmental IoT refers to cellular IoT communication technology that uses energy from the environment to support data sensing, transmission, and distributed computing without relying on batteries. Environmental IoT can also be called Ambient IoT (A-IoT) or Passive Internet of Things (passive IoT), but this application does not limit the naming of these terms.

[0154] In the Internet of Things (IoT) of the environment, IoT devices / terminals can be passive, semi-passive, semi-active, or active. Passive and semi-passive terminals can communicate via reflected carrier waves, meaning they rely on an external carrier source. Semi-passive terminals can incorporate power amplifiers, thus increasing their communication range compared to passive terminals. Active terminals can actively generate carrier waves (or possess carrier recovery capabilities), allowing them to communicate without relying on an external carrier source, thus enabling active communication. However, active terminals are also backward compatible with the communication mechanisms of passive or semi-passive terminals; for example, an active terminal can trigger a random access procedure and send identification information through external stimulation.

[0155] Furthermore, passive terminals may or may not have energy storage capacitors. If a passive terminal does not have an energy storage capacitor, it needs to obtain energy from the external environment for communication, such as radio frequency energy. Semi-passive terminals typically have energy storage capacitors, which can store energy from the environment, such as solar energy or wireless energy. Active terminals can also have energy storage capacitors and can obtain energy through solar energy, radio frequency energy, wind energy, hydropower, or tidal energy, without any restrictions on the method of energy acquisition.

[0156] Environmental IoT technology is widely used in various industries. Below are two application scenarios:

[0157] Warehouse / Transportation / Materials Management Scenarios: Goods are embedded or affixed with passive or semi-passive IoT tags. Goods are stored in warehouses, shopping malls, etc. During the logistics process, relevant information about the goods is automatically collected by readers. Managers can quickly query goods information in the system, reducing the risk of loss, improving the speed and accuracy of goods handover, and preventing cross-selling and counterfeiting.

[0158] Fixed asset management scenarios: Libraries, art galleries, museums, and other venues with large assets or valuable items require comprehensive management procedures or rigorous protection measures. The system should be able to immediately alert administrators to any unusual changes in the storage information of books or valuable items, allowing for timely intervention.

[0159] Environmental IoT can be applied to inventory management. The following example uses IoT devices as tags, readers as base stations, and the service requester as a server to illustrate environmental IoT services:

[0160] In one implementation, when the server operates on the tag, the server can send operation instructions through the core network. These instructions may include, but are not limited to, performing operations such as acquiring tag information, inventory operations (or storage operations), read operations, write operations, invalidation operations, and interacting with the tag. The operation instructions may also include area location information, tag identification information, etc. The base station sends an access instruction to the tag. After successful random access, the base station sends operation instructions to the tag (the base station can forward operation instructions sent by the core network to the tag). The tag acquires or sends corresponding information according to the operation instructions. For example, when the operation instruction is an inventory instruction or an inventory operation is not performed, the tag sends its identification information. When the operation instruction is a read instruction or a read operation is not performed, the tag sends data information stored in its storage area; when the operation instruction is a write instruction or a write operation is performed, the tag stores the data information to be written to the tag, included in the operation instruction, in its storage area. The base station sends (or forwards) the information sent by the tag to the core network. The core network then sends this information to the server.

[0161] Please refer to Figures 2 and 3, which are schematic diagrams of a passive IoT service. In Figures 2 and 3, core network equipment executes processes related to environmental IoT services, such as IoT device access management, security authentication, command transmission, and tag management. Figure 2 shows an enhanced access management device (e.g., AMF) with IoT management functions (or passive IoT management functions, environmental energy acquisition IoT functions), such as performing IoT device management, data transmission, data routing, and sharing information with third parties. Figure 3 shows a newly added IoT management function (e.g., TMF) to perform tag management. This function can interface with access network equipment, meaning the access network equipment has an interface with this function. It can also interface with access network equipment through AMF, and its network topology is similar to functions such as SMF and PCF. From a deployment perspective, TMF can be co-deployed with AMF.

[0162] The server sends instructions (e.g., operation instructions) via the control plane channel, as shown in Figure 2 or Figure 3. The server sends instructions to the AMF (or other core network devices that manage IoT devices, execute tag instructions, or support passive IoT, such as the TMF) through the NEF or NSSAAF. In this case, the server can be an authentication, authorization, and accounting server (AAAserver), an environmental IoT application (A-IoT AF) function, a passive IoT application function (P-IoT AF), or an application server (AS), etc. Through this architecture, after receiving the instructions, the AMF or TMF parses them from the server and triggers the access network device (e.g., a base station) to perform a random access process for the IoT device (e.g., a tag). This involves the base station sending instructions to the tag to complete the operation. After receiving the instructions, the tag performs random access to the base station and, upon successful random access, registers and sends tag information, including the tag's identifier, to the base station. The base station sends tag information to the AMF, and the AMF sends the tag information to the AAAserver or P-IoT AF via NEF or NSSAAF. Additionally, the AMF can perform access management on the tags based on feedback from the AF, such as determining whether a tag has been connected.

[0163] In one implementation, the requesting party does not actively trigger inventory checks. Instead, it pre-configures the network to periodically report the IoT devices present within the park. Alternatively, tags can be attached to goods, and the network can periodically check the tags to obtain information on the status of goods within the enterprise park or factory, thereby achieving automated warehouse management.

[0164] For example, see Figure 4, which illustrates another passive IoT service. As shown in Figure 4, the AMF or TMF sends instructions to the base station. The base station then sends instructions (such as an inventory instruction) to the tags, triggering random tag access. After successful random access, the tag performs registration and sends tag information, including the tag's identifier, to the base station. The base station then sends the tag information to the AMF or TMF, which in turn sends it to the server, thus enabling tag inventory.

[0165] As can be seen, compared with the passive IoT services in Figures 2 and 3, the trigger for the inventory service in Figure 4 is not the service requester, but the AMF or TMF. However, for tags, the base station is the one that triggers the inventory service; that is, the base station triggers the tag to randomly access the network and reports the tag information after successful random access.

[0166] 2. Non-public network (NPN) and closed access group identifier (CAG ID).

[0167] A non-public network (NPN) is a network that differs from a public network and provides services to specific users. Depending on whether the core network (CN) is independent, non-public networks include standalone NPNs (SNPNs) and public network integrated NPNs (PNI-NPNs).

[0168] In this context, the SNPN does not rely on a public land mobile network (PLMN) and is operated by a standalone, non-public SNPN operator. This can be understood as the SNPN's core network being independent of the PLMN; that is, the SNPN's core network is independently operated by the SNPN.

[0169] PNI-NPN relies on a PLMN and is operated by traditional carriers. It can be understood that PNI-NPN is essentially a PLMN, but the PLMN provides special network slices and / or data networks to deliver NPN services. It can also be understood that not all terminal devices can access this NPN service; terminal devices must pass slice authentication and / or secondary authentication to obtain NPN services. Furthermore, PNI-NPN uses network slices to isolate public network services from private network services, thereby providing private network services to private network users.

[0170] Slice configuration is done at the tracking area (TA) level, meaning base stations (or cells) belonging to the same TA support the same slices. Since PNI-NPN uses specific slices for isolation, the geographical range within which terminal devices can access PNI-NPN services is relatively large. To further limit the scope of PNI-NPN service access, the concept of Closed Access Group ID (CAG ID) has been proposed. Specifically, base stations (or cells) belonging to PNI-NPN can broadcast a list of CAG IDs. The terminal device's subscription data also stores the allowed CAG list. When the terminal device performs the registration process, the base station carries the cell-supported CAG list in the N2 message sent to the AMF. The AMF determines whether to allow the terminal device to access the network through that cell based on the cell-supported CAG list and the terminal device's allowed CAG list. This method restricts terminal devices from accessing the PNI-NPN network through specific cells to obtain services, thus narrowing the access range. For example, if the cell's supported CAG list includes CAG 1 and CAG 2, and the UE's subscribed data includes the allowed CAG list including CAG 2 and CAG 3, then the cell supports CAG 2, and the terminal device's subscribed data also includes CAG 2, thus allowing the terminal device to access the network through that cell.

[0171] For example, Figure 5 is a schematic diagram of SNPN services and PLMN / PNI-NPN services. As shown in Figure 5, in SNPN services, SNPN includes a 5G core network and a next-generation radio access network (NG-RAN). The system information block (SIB) 1 includes a PLMN identifier of A and a network identifier (NID) of Y. If UE1 supports access to the SNPN network with SNPN identifier A+Y (i.e., the identifier of the SNPN network is PLMN=A+NID=Y), then UE1 can access the SNPN shown in Figure 5. That is, when UE1's access mode is SNPN access mode, it can access this SNPN. As shown in Figure 5, when the NPN is PNI-NPN, the PLMN (e.g., PLMN A) can include PLMN / PNI-NPN services. PLMN A includes a 5G core network and two NG-RANs. In one type of NG-RAN, SIB 1 includes a PLMN identifier (PLMN identifier is A) and a CAG ID of X; in another type of NG-RAN, SIB 1 includes a PLMN identifier (PLMN identifier is A) and does not support broadcasting the CAG ID. UE2 supports access to a PLMN with PLMN identifier A but not to a CAG cell; therefore, UE2 can only access the PLMN and cannot access the PNI-NPN. UE3 supports access to CAG cells, for example, it supports access to a PNI-NPN with PLMN identifier A and CAG ID X; therefore, UE3 can access the cell of that PNI-NPN but cannot access the PLMN cell. UE4 supports access to both a PLMN with PLMN identifier A and a PNI-NPN with PLMN identifier A and CAG ID X; therefore, UE4 can access both the PNI-NPN and the PLMN. Furthermore, when a terminal device accesses an SNPN, it cannot directly switch from the SNPN to the PNI-NPN. Similarly, when a terminal device accesses PNI-NPN, it cannot directly switch from PNI-NPN to SNPN.

[0172] 3. Registration process for terminal devices.

[0173] For example, please refer to Figure 6, which is a schematic diagram of the registration process of a terminal device. As shown in Figure 6, the terminal device (UE) sends registration request information to the radio access network (RAN). Correspondingly, the RAN receives the registration request information from the terminal device. The registration request information carries the registration type and the terminal device's identification information. The registration types of the terminal device include initial registration, mobility registration update, periodic registration update, and emergency registration. The terminal device's identification information can be a subscription concealed identifier (SUCI), a 5G globally unique temporary identifier (5G-GUTI), or a permanent equipment identifier (PEI).

[0174] The RAN selects an AMF for the end device. The RAN sends a registration request to the selected AMF. Optionally, the RAN sends a non-access stratum (NAS) message from the end device to the AMF via an N2 message; that is, the N2 message includes the NAS message, thus including the registration request. For PNI-NPN scenarios, this N2 message will also include a list of CAGs supported by the RAN.

[0175] The AMF identifies the Authentication Service Function (AUSF) and performs authentication and other security procedures. Understandably, the terminal device, AMF, ASF, and UDM interact to complete these security procedures.

[0176] The AMF determines whether to allow the terminal device to access the network. Specifically, after the terminal device successfully authenticates with the network side, the AMF interacts with the UDM to obtain the terminal device's subscription data. For the PNI-NPN scenario, the AMF compares the terminal device's allowed CAG list stored in the Unified Data Management Function (UDM) with the supported Closed Access Group Identifier (CAG) list reported by the access network device via N2 messages. If at least one CAG in the RAN-supported CAG list is a CAG in the UE's allowed CAG list, the AMF allows the terminal device to access the network.

[0177] The AMF sends an N2 message to the RAN. The N2 message includes a NAS message that the RAN needs to forward to the terminal device. The NAS message contains a registration acceptance message from the AMF to the terminal device, which includes a registration area (TAI) list. The RAN then forwards the registration acceptance message (NAS message) from the AMF to the terminal device.

[0178] 4. Schematic diagram of the inventory process for IoT terminals.

[0179] For example, please refer to Figure 7, which is a schematic diagram of the tag service inventory process. As shown in Figure 7, the base station (gNB) sends a select command, which carries mask information (such as the range identified by the tag) and storage area information matching the mask information. After receiving the select command, the tag determines whether it belongs to the tag range to be judged in the select command. For example, the tag uses the storage area indicated by the storage area information to match the mask information to determine whether it belongs to the tag selected by the select command. If it belongs, it generates a random number and provides feedback information after hearing the query command; if it does not belong, no further processing is performed.

[0180] The gNB continues to send Query commands or repeats the QueryRep command. Each time the tag receives a Query command or QueryRep command, it decrements the value of the generated random number by one; when the generated random number reaches 0, the tag triggers a random access initiation. Specifically, the tag sends a random number RN16 to the gNB, i.e., a 16-bit random number. When the gNB receives the random number RN16 from the tag, it sends an acknowledgment (ACK) to the tag, which includes the received random number RN16. When the tag receives the ACK from the gNB, it verifies the random number RN16 carried in the ACK.

[0181] If the random number RN16 carried in the ACK is the same as the random number RN16 generated by the tag, the tag sends Non-Access Stratum (NAS) data to the gNB. The NAS data includes the tag's identification information. The gNB then sends the tag's NAS data to the AMF. The AMF then sends data, including the tag's identification information, to the AF to complete the inventory process.

[0182] However, within the same industrial park, there may be IoT devices belonging to different business requesters, and these requesters may have different needs for inventory management. For example, some requesters may request that inventory management be performed every hour from 8:00 AM to 6:00 PM to obtain the identification and / or location information of the IoT devices they manage. Other requesters, however, may prefer to perform inventory management during evening hours.

[0183] Therefore, if the base station triggers an inventory check based on the needs of different service requesters, multiple IoT devices corresponding to different service requesters within the park may randomly connect and report identification information, leading to a significant waste of signaling. Furthermore, if the core network does not store the mapping between IoT devices and service requesters, when the core network receives a registration request from an IoT terminal, it will only perform a security authentication process and will not send identification information back to the corresponding service requester, thus failing to perform the inventory check. In other words, even if the core network knows that identification information needs to be sent back to the service requester, it cannot send the acquired data back to the corresponding service requester due to the lack of a mapping between IoT devices and service requesters.

[0184] To facilitate understanding of the embodiments disclosed in this application, the following two points are explained.

[0185] (1) The scenarios in the embodiments disclosed in this application are illustrated using the scenario of a new radio (NR) network. It should be noted that the solutions in the embodiments disclosed in this application can also be applied to other wireless communication networks, and the corresponding names can be replaced by the names of the corresponding functions in other wireless communication networks.

[0186] (2) The embodiments disclosed in this application will be presented in relation to systems including multiple devices, components, modules, etc. It should be understood and appreciated that individual systems may include additional devices, components, modules, etc., and / or may not include all devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Furthermore, combinations of these approaches may also be used.

[0187] This application proposes a communication method 100. In this method 100, a reader acquires one or more first identifiers and time information corresponding to each of the one or more first identifiers, where each of the one or more first identifiers corresponds to a first service requester. Based on the time information corresponding to each of the one or more first identifiers, the reader broadcasts one or more first identifiers to trigger the service inventory of the first service requester or to trigger the access process of the IoT terminal corresponding to the first service requester. Compared with the reader broadcasting all identifiers supported by the reader at the same time, this method is advantageous in that the reader triggers the service inventory of the first service requester within a specific time period, rather than triggering the service inventory of all service requesters within the reader's coverage area. This not only reduces signaling overhead but also distinguishes the IoT devices associated with different service requesters. In addition, when multiple first identifiers correspond to different services of the first service requester (e.g., different first identifiers correspond to different services of the first service requester), this method is also advantageous in triggering the service inventory of a specific service of the first service requester (or in triggering the inventory of the terminal corresponding to a specific service of the first service requester), thereby executing the access process of IoT devices corresponding to different services (or distinguishing IoT devices corresponding to different services).

[0188] This application also proposes a communication method 200 for a reader / writer broadcasting a third identifier, where the third identifier is any one of one or more first identifiers corresponding to a first service requester. In this communication method 200, the reader / writer broadcasts the third identifier based on time information corresponding to the third identifier, and the third identifier corresponds to the first service requester. A first IoT device sends identification information to the reader / writer, which identifies the first IoT device, which is either managed or corresponding to the first service requester. The reader / writer sends first information to the core network device, including the identification information. The core network device determines the first service requester that manages the first IoT device. The core network device then sends the identification information to the first service requester. Therefore, by broadcasting the third identifier corresponding to the first service requester within a specific time period, the reader / writer performs service inventory checks on the first service requester. This method reduces signaling overhead compared to the reader / writer simultaneously broadcasting all identifiers supported by the reader / writer to trigger service inventory checks on all service requesters within its coverage area.

[0189] In this embodiment of the application, the time information corresponding to each of the one or more first identifiers can be understood as: the time information corresponding to some or all of the one or more first identifiers. Therefore, the reader broadcasting one or more first identifiers based on the time information corresponding to each of the one or more first identifiers can be understood as: the reader broadcasting some or all of the first identifiers based on the time information corresponding to some or all of the one or more first identifiers.

[0190] This application provides a communication method 100, and Figure 8 is a flowchart of the communication method 100. The communication method 100 is described from the perspective of a reader / writer. The communication method 100 includes, but is not limited to, the following steps:

[0191] S801. The reader obtains one or more first identifiers, and the time information corresponding to each of the one or more first identifiers, and the one or more first identifiers correspond to the first service requester.

[0192] In this context, one or more first identifiers correspond to a first service requester. This can be understood as one or more first identifiers being associated with a service of the first service requester, and one first identifier being associated with one service of the first service requester. Different first identifiers can be associated with different services of the first service requester, or they can be associated with the same service of the first service requester. In one possible implementation, the service of the first service requester can be an environmental IoT service, meaning that one or more first identifiers can correspond to the environmental IoT service of the first service requester. Thus, the first identifier can be a dedicated identifier for the environmental IoT service, which can also be called an environmental energy harvesting IoT service, or a passive IoT service. For example, the services of the first service requester may include service 1 (e.g., warehouse management) and service 2 (e.g., asset inventory). Each service corresponds to a different IoT terminal. For example, the IoT terminal for warehouse management can be associated with goods (e.g., the IoT terminal is attached to the goods), and the IoT terminal for asset inventory can be associated with assets (e.g., the IoT terminal is attached to the assets). For example, the environmental IoT service of the first service requester includes service 1 and service 2, where service 1 is associated with first identifier a, and service 2 is associated with first identifier b. Therefore, the first identifier a and the first identifier b correspond to the first service requester.

[0193] In one optional implementation, one or more first identifiers can be access identifiers used by IoT devices when accessing a cell, such as Closed Access Group IDs (CAG IDs). A CAG ID is an identifier used by an IoT device to connect to a network (e.g., a public or non-public network) through a specific area, as described above, and will not be repeated here. Therefore, one or more first identifiers can reuse existing CAG IDs in the protocol, reducing modifications to the protocol; or, it can be understood as enabling the extension of existing CAG IDs to environmental IoT services.

[0194] In another optional implementation, when the number of first identifiers is one, the first identifier can be the identifier of the first service requester. The identifier of the first service requester can be globally unique identifier information, operator-specific globally unique identifier information, etc. Alternatively, the identifier of the first service requester can also be the application function identifier corresponding to the first service requester, such as AF ID, AF identifier, or AF identity. When the number of first identifiers is multiple, the first identifier can be the service identifier corresponding to different services of the first service requester, such as service identifier, service ID, service identity, application (APP) ID, APP identifier, or APP identity, etc.

[0195] In another optional implementation, the first identifier can be a group identifier, such as a group ID, an external group ID, or an internal group ID. The group identifier can be understood as the identifier of the group to which the IoT device belongs.

[0196] In one optional implementation, the time information corresponding to the first identifier can be a broadcast time requirement, that is, a time requirement for broadcasting the first identifier. Specifically, the time information corresponding to the first identifier includes one or more of the following: transmission time, transmission period, validity period, transmission frequency, and transmission interval. For example, the time information corresponding to the first identifier is the transmission time of the first identifier. Another example is that the time information corresponding to the first identifier is the transmission time and transmission period of the first identifier. Yet another example is that the time information corresponding to the first identifier includes the transmission time, transmission period, transmission interval, and validity period of the first identifier.

[0197] It is understood that the specific form of the time information corresponding to each of the one or more first identifiers may be the same or different, and this application embodiment does not limit this. For example, multiple first identifiers include first identifier a and first identifier b, where the time information corresponding to first identifier a is the transmission time and transmission period of first identifier a, and the time information corresponding to first identifier b is the transmission time and transmission period of first identifier b. As another example, multiple first identifiers include first identifier a and first identifier b, where the time information corresponding to first identifier a is the transmission time and transmission period of first identifier a, and the time information corresponding to first identifier b is the transmission time and validity period of first identifier b.

[0198] In addition, the sending time of the first identifier can be one or more of the start time, time interval, end time and sending duration of the first identifier. The embodiments of this application do not limit the specific method of sending time.

[0199] In one optional implementation, the time information corresponding to different first identifiers among one or more first identifiers is different, thus the broadcast times of different first identifiers among one or more first identifiers are not the same. This method is beneficial for the reader to broadcast different first identifiers among one or more first identifiers at different time periods.

[0200] In one optional implementation, the reader acquires one or more first identifiers and time information corresponding to each of the one or more first identifiers, including receiving one or more first identifiers and time information corresponding to each of the one or more first identifiers from a core network device. In one possible implementation, a first service requester sends one or more first identifiers corresponding to the first service requester and time information corresponding to each of the one or more first identifiers to the core network device. In another possible implementation, the core network device acquires one or more first identifiers corresponding to the first service requester and time information corresponding to each of the one or more first identifiers through subscription data or configuration information. Then, the core network device sends one or more first identifiers corresponding to the first service requester and time information corresponding to each of the one or more first identifiers to the reader. Correspondingly, the reader receives one or more first identifiers and time information corresponding to each of the one or more first identifiers from the core network device.

[0201] Optionally, the reader obtains one or more first identifiers, and time information corresponding to each of the one or more first identifiers, including: the reader obtains one or more first identifiers corresponding to the first service requester from the operation, administration and maintenance (OAM) system (which can be referred to as the network management system), and time information corresponding to each of the one or more first identifiers.

[0202] Optionally, the reader is configured with one or more first identifiers corresponding to the first service requester, and time information corresponding to each of the one or more first identifiers. Therefore, the reader obtaining one or more first identifiers and the time information corresponding to each of the one or more first identifiers can be understood as: the reader obtains one or more first identifiers and the time information corresponding to each of the one or more first identifiers through configuration information. For example, the one or more first identifiers corresponding to the first service requester and the time information corresponding to each of the one or more first identifiers configured in the reader are configured by the core network device or network management system for the reader.

[0203] As can be seen, the reader can flexibly acquire one or more first identifiers, as well as the time information corresponding to each of the one or more first identifiers, through various methods. This application does not limit the specific implementation methods for the reader to acquire one or more first identifiers, and the time information corresponding to each of the one or more first identifiers.

[0204] In one possible implementation, the method by which the reader obtains one or more first identifiers may differ from the method by which it obtains the time information corresponding to those one or more first identifiers. For example, the reader may obtain one or more first identifiers through core network equipment and obtain the time information corresponding to those one or more first identifiers through network management or configuration information. Both the method by which the reader obtains one or more first identifiers and the method by which it obtains the time information corresponding to those one or more first identifiers can be obtained in the manner described above (e.g., from core network equipment, from network management system, from configuration information, etc.).

[0205] In one optional implementation, the time information corresponding to each of the one or more first identifiers corresponding to the first service requester is determined by the first service requester, the core network equipment, or the network management system based on the service requirements (e.g., inventory service requirements) corresponding to that first identifier. Therefore, for different services of the first service requester, the time information corresponding to different first identifiers is different, which facilitates the reader / writer in triggering the inventory of different services of the first service requester at different times or time periods. In one possible implementation, the service requirement can be determined through negotiation between the enterprise corresponding to the service requester and the operator.

[0206] For example, the services of the first service requester include service 1, service 2, and service 3, which correspond to first identifier 1, first identifier 2, and first identifier 3, respectively. The first service requester's inventory requirements for service 1 are from 10:00 to 12:00 every day, for service 2 from 14:00 to 16:00 every day, and for service 3 from 19:00 to 20:00 every day. Then, the first service requester determines that the time information corresponding to first identifier 1 includes a start time of 10:00, an end time of 12:00, a sending period of 24 hours, and a sending interval of every minute; the time information corresponding to first identifier 2 includes a start time of 14:00, an end time of 16:00, a sending period of 24 hours, and a sending interval of every 2 minutes; and the time information corresponding to first identifier 3 includes a start time of 19:00, an end time of 20:00, a sending period of 24 hours, and a sending interval of every 5 minutes.

[0207] S802. The reader broadcasts one or more first identifiers based on the time information corresponding to each of the one or more first identifiers.

[0208] Understandably, the reader broadcasts a first identifier based on the time information corresponding to each of the one or more first identifiers. Alternatively, it can be understood that, for any one of the one or more first identifiers, the reader broadcasts that first identifier based on the time information corresponding to that first identifier. For example, if multiple first identifiers include first identifier a and first identifier b, the reader broadcasts first identifier a based on time information 1 corresponding to first identifier a, and the reader broadcasts first identifier b based on time information 2 corresponding to first identifier b.

[0209] As can be seen, the reader broadcasts one or more first identifiers at the same time or within the same time period, rather than broadcasting a list of identifiers supported by the reader, i.e., not all identifiers supported by the reader. This allows the reader to trigger the service inventory of the first service requester corresponding to a first identifier (or trigger random access of the IoT terminal of the first service requester corresponding to the first identifier), rather than triggering the service inventory of all service requesters within the reader's coverage area (or random access of IoT terminals corresponding to all service requesters). This reduces signaling overhead and can effectively identify the service requester corresponding to the IoT terminal accessing the network and perform the same data routing.

[0210] In addition, when multiple first identifiers correspond to different services of the first service requester (e.g., different first identifiers correspond to different services of the first service requester), the reader broadcasts one of the multiple first identifiers at the same time or within the same time period. This is beneficial for triggering the service inventory of the specific service of the first service requester (or for triggering the inventory of the terminal corresponding to the specific service of the first service requester), thereby enabling the execution of the access process of IoT devices corresponding to different services (or enabling the differentiation of IoT devices corresponding to different services).

[0211] Optionally, one of the multiple first identifiers can correspond to multiple service requesters. When one of the multiple first identifiers corresponds to multiple service requesters, the reader broadcasts the first identifier based on the time information corresponding to that first identifier. If the reader receives identification information reported by multiple IoT devices in response to the first identifier, the reader determines the service requester managing each IoT device based on the subscription information of each IoT device, and sends the identification information for each IoT device to the service requester managing that IoT device. In this method, the reader can trigger service inventory of multiple service requesters corresponding to that identifier by broadcasting a first identifier, which can reduce signaling overhead and improve the efficiency of service inventory.

[0212] For example, multiple first identifiers include identifier #1, which identifies service 1. Both service requester 1 and service requester 2 have service inventory records for service 1. The reader broadcasts identifier #1 based on its time information. Since both IoT device 1 and IoT device 2 are configured with identifier #1, both IoT device 1 and IoT device 2 respond to the reader's broadcast identifier #1. IoT device 1 and IoT device 2 respectively send identifier information #1 (identifying IoT device 1) and identifier information #2 (identifying IoT device 2) to the reader. Based on the subscription information of IoT device 1 and IoT device 2, the reader determines that the service requester managing IoT device 1 is service requester 1, and the service requester managing IoT device 2 is service requester 2. Therefore, the reader sends identifier information to service requester 1 and identifier information to service requester 2. Thus, by broadcasting identifier #1, the reader enables service requesters 1 and 2 to inventory service inventory records for service 1.

[0213] In one optional implementation, for any one of one or more first identifiers, when the time information corresponding to the first identifier is the transmission time of the first identifier, the reader broadcasts the first identifier based on the transmission time of the first identifier. For example, if the transmission time of the first identifier is the start time and end time (or deadline) of the first identifier, then the reader broadcasts the first identifier within the time period starting from the start time and ending at the end time. As another example, if the transmission time of the first identifier is the start time and the transmission duration of the first identifier, then the reader broadcasts the first identifier within the transmission duration starting from the start time. Yet another example, if the transmission time of the first identifier is the start time and the time interval, then the reader broadcasts the first identifier once every time interval starting from the start time.

[0214] In another optional implementation, when the time information corresponding to any one of the one or more first identifiers is the transmission time and transmission period of the first identifier, the reader broadcasts the first identifier based on the transmission time and transmission period of the first identifier. For example, if the time information corresponding to the first identifier is the transmission time and transmission period of the first identifier, and the transmission time of the first identifier is the start time and the end time, and the transmission period is T1, then the reader broadcasts the first identifier within the time period starting from the start time and ending at the end time, and after broadcasting the first identifier within the time period starting from the start time and ending at the end time, periodically broadcasts the first identifier every T1 interval.

[0215] In another optional implementation, when the time information corresponding to any one of the one or more first identifiers is the validity period of that first identifier, the reader broadcasts the first identifier within the validity period of that first identifier. Optionally, when the time information corresponding to any one of the one or more first identifiers is the transmission period and validity period of that first identifier, the reader periodically broadcasts the first identifier according to the transmission period within the validity period of that first identifier. It is evident that when the forms of the time information corresponding to the first identifier are different, the reader can flexibly broadcast the first identifier in multiple ways.

[0216] In one alternative implementation, the reader can also broadcast storage area information, which characterizes a storage area storing one or more first identifiers. This approach allows IoT devices to determine whether a match exists or whether to respond to a broadcast message containing one or more first identifiers based on the storage area storing those identifiers.

[0217] In an optional implementation, the reader may further perform the following steps: acquiring second information, the second information being used to instruct updating the first identifier corresponding to the first service requester; and updating the first identifier corresponding to the first service requester based on the second information. The implementation method for the reader to acquire the second information can refer to the implementation method for the reader to acquire one or more first identifiers, and the implementation method for the reader to acquire time information corresponding to each of the one or more first identifiers, and will not be repeated here.

[0218] Optionally, the second information is specifically used to instruct the deletion of at least one of the one or more first identifiers. For example, the second information is specifically used to instruct the deletion of at least one of the one or more first identifiers corresponding to the first service requester, such as deleting identifier 1 from the one or more first identifiers. In one possible implementation, the reader deletes identifier 1 from the one or more first identifiers corresponding to the first service requester based on the second information, for example, by unbinding the correspondence between identifier 1 and the first service requester, and when broadcasting the first identifiers corresponding to the first service requester again, it no longer broadcasts identifier 1. In another possible implementation, the reader no longer broadcasts identifier 1 based on the second information. In this method, the second information can be deletion configuration information, which is used to delete at least one of the one or more first identifiers corresponding to the first service requester.

[0219] For example, if one or more first identifiers corresponding to the first service requester include identifier a, identifier b, and identifier c, and the second information is used to indicate the deletion of identifier b corresponding to the first service requester, then the reader will unbind the correspondence between identifier b and the first service requester. When broadcasting the identifiers corresponding to the first service requester again, it will broadcast identifier a based on the time information corresponding to identifier a, and broadcast identifier c based on the time information corresponding to identifier c, but will no longer broadcast identifier b. As another example, if one or more first identifiers corresponding to the first service requester include identifier a, identifier b, and identifier c, and the second information is used to indicate the deletion of identifier b corresponding to the first service requester, then when the reader broadcasts the identifiers corresponding to the first service requester again, it will broadcast identifier a based on the time information corresponding to identifier a, and broadcast identifier c based on the time information corresponding to identifier c, but will no longer broadcast identifier b.

[0220] Optionally, the second information is specifically used to indicate the addition of a first identifier and the time information corresponding to the addition of the first identifier. For example, the second information is specifically used to indicate the addition of a first identifier and the time information of the first identifier to the first service requester, such as adding identifier 2 to the first service requester and the time information corresponding to identifier 2. In one possible implementation, the reader associates identifier 2 with the first service requester based on the second information and adds corresponding time information to identifier 2. The reader broadcasts identifier 2 based on the time information corresponding to identifier 2. In another possible implementation, when the reader broadcasts the identifier corresponding to the first service requester based on the second information, it also broadcasts identifier 2 based on the time information corresponding to identifier 2. For example, if one or more first identifiers corresponding to the first service requester include identifier a and identifier b, and the second information is used to indicate the addition of identifier c corresponding to the first service requester, then when the reader broadcasts the identifier corresponding to the first service requester again, it broadcasts identifier a based on the time information corresponding to identifier a, broadcasts identifier b based on the time information corresponding to identifier b, and broadcasts identifier c based on the time information corresponding to identifier c. In this method, the second information can be creation configuration information, which is used to add the identifier corresponding to the first service requester.

[0221] Optionally, the second information is specifically used to instruct the modification of the time information corresponding to at least one of the one or more first identifiers. For example, the second information is specifically used to instruct the modification of at least one of the one or more first identifiers corresponding to the first service requester, such as modifying the time information corresponding to identifier 3. Thus, the reader modifies the time information corresponding to identifier 3 based on the second information. Furthermore, when the reader broadcasts the one or more first identifiers corresponding to the first service requester again, it broadcasts identifier 3 based on the modified time information corresponding to identifier 3. In this method, the second information can be configuration modification information, which is used to modify the time information corresponding to at least one of the one or more first identifiers corresponding to the first service requester.

[0222] As can be seen, the reader can acquire the second information and update the broadcast first identifier and / or time information based on the second information. Furthermore, when the reader broadcasts the first identifier again, it broadcasts the updated identifier based on the time information corresponding to the updated identifier.

[0223] In one optional implementation, the reader further acquires one or more second identifiers, and time information corresponding to each of the one or more second identifiers, wherein the one or more second identifiers correspond to a second service requester. Based on the time information corresponding to each of the one or more second identifiers, the reader broadcasts the one or more second identifiers. The time information corresponding to the second identifier can be a broadcast time requirement, that is, a time requirement for broadcasting the second identifier. Furthermore, the time for broadcasting the first identifier determined by the reader based on the time information corresponding to the first identifier is different from the time for broadcasting the second identifier determined based on the time information corresponding to the second identifier.

[0224] Optionally, one or more first identifiers are used to trigger the service inventory of the first service requester (or to trigger the IoT device corresponding to the first service requester to initiate random access), and one or more second identifiers are used to trigger the service inventory of the second service requester (or to trigger the IoT device corresponding to the second service requester to initiate random access). In this application, the IoT device initiating random access can be understood as the IoT device executing a random access procedure, or triggering the IoT device to initiate random access can be understood as triggering the IoT device's access procedure or random access procedure.

[0225] The parameter types included in the time information corresponding to the second identifier can be referred to the parameter types included in the time information corresponding to the first identifier, and will not be repeated here. Each service in the second service requester is associated with a second identifier, so each service in one or more services of the second service requester is associated with a second identifier, and thus the second service requester corresponds to one or more second identifiers.

[0226] The time at which the reader broadcasts the first identifier, determined based on the time information corresponding to the first identifier, is different from the time at which it broadcasts the second identifier, determined based on the time information corresponding to the second identifier. Therefore, the reader can trigger the service inventory of the first service requester and the second service requester at different times. It is evident that the reader can trigger the service inventory of different service requesters at different times, which reduces signaling overhead compared to the reader triggering the service inventory of all service requesters at the same time.

[0227] In this embodiment, the reader obtains one or more first identifiers corresponding to the first service requester, and time information corresponding to each of the one or more first identifiers. Based on the time information corresponding to each of the one or more first identifiers, the reader broadcasts one or more first identifiers to trigger the service inventory of the first service requester. Compared with the reader broadcasting a list of identifiers supported by the reader, this method allows the reader to trigger the service inventory of the first service requester within a specific time period, rather than triggering the service inventory of all service requesters within the reader's coverage area. This not only reduces signaling overhead but also distinguishes the IoT devices corresponding to different service requesters. In addition, when one or more first identifiers correspond to different services, this method is also beneficial for triggering the service inventory of the first service requester for a specific service, distinguishing the IoT devices corresponding to different services.

[0228] This application also proposes a communication method 200 for a reader / writer broadcasting any one of one or more first identifiers corresponding to a first service requester. For ease of description, this communication method 200 is illustrated using the example of a third identifier being one of one or more first identifiers corresponding to the first service requester. Figure 9 is an interactive schematic diagram of the communication method 200. The communication method 200 is described from the perspective of the interaction between the reader / writer, the IoT device, the core network device, and the first service requester. The communication method 200 includes, but is not limited to, the following steps:

[0229] S901. The reader broadcasts the third identifier based on the time information corresponding to the third identifier, and the third identifier corresponds to the first service requester.

[0230] Understandably, before broadcasting the third identifier, the reader / writer obtains one or more first identifiers corresponding to the first service requester, as well as the time information corresponding to each of the one or more first identifiers. The one or more first identifiers include the third identifier. For example, the one or more first identifiers include identifier #a, identifier #b, and identifier #c, with identifier #b being the third identifier.

[0231] Furthermore, the implementation method of the third identifier can be found in the implementation method of the first identifier in communication method 100, and will not be repeated here. The parameter types included in the time information corresponding to the third identifier can also be found in the parameter types included in the time information corresponding to the first identifier in the aforementioned communication method 100, and will not be repeated here.

[0232] The reader broadcasts the third identifier based on the time information corresponding to the third identifier, thereby triggering the first service requester to perform a service inventory or triggering the IoT device corresponding to the first service requester to initiate random access. The specific implementation method for the reader to broadcast the third identifier based on the time information corresponding to the third identifier can be found in S802 above, and will not be repeated here.

[0233] In one optional implementation, the reader uses a select message to broadcast a third identifier. Therefore, the reader broadcasts a select message based on the time information corresponding to the third identifier, and this select message includes the third identifier.

[0234] The reader broadcasts the third identifier based on the time information corresponding to the third identifier. This can be understood as the reader broadcasting the third identifier from one or more identifiers supported by the reader at the same time, rather than broadcasting one or more identifiers supported by the reader, i.e., not all identifiers supported by the reader. This is beneficial for the reader to trigger the service inventory of the first service requester corresponding to the third identifier, rather than triggering the service inventory of all service requesters within the reader's coverage area, thus reducing signaling overhead.

[0235] In one optional implementation, the third identifier corresponds to the environmental IoT service; that is, the third identifier is the identifier associated with the environmental IoT service of the first service requester. The environmental IoT service can also be referred to as the environmental energy harvesting IoT service, or as the passive IoT service.

[0236] In one optional implementation, the environmental IoT business of the first business requester includes multiple environmental IoT businesses, and the multiple environmental IoT businesses include the first environmental IoT business. The third identifier corresponds to the first environmental IoT business (e.g., warehousing and logistics business or asset inventory business), that is, the third identifier is the identifier associated with the first environmental IoT business of the first business requester.

[0237] Optionally, the reader can also broadcast storage area information, which is used to characterize the storage area storing the third identifier, thereby enabling IoT devices to match the third identifier or determine to initiate random access based on the third identifier in the storage area storing the third identifier.

[0238] S902. The first IoT device sends identification information to the reader, which is used to identify the first IoT device. Correspondingly, the reader receives the identification information from the first IoT device.

[0239] Understandably, each IoT device obtains configuration information during the initialization process. This configuration information includes an identifier configured for the IoT device and / or the IoT device's identification information. For example, during the initialization process, IoT device a obtains configuration information a, which includes one or more identifiers (e.g., CAG IDs) allowed by the access cell configured for IoT device a.

[0240] After the reader broadcasts the third identifier based on the time information of the third identifier, each IoT device receives the third identifier broadcast by the reader via a broadcast message (e.g., blind detection). If an IoT device has been configured with the third identifier, then that IoT device will determine whether to initiate or execute a random access procedure to the reader.

[0241] The first IoT device is an IoT device that has been configured with a third identifier. Therefore, after receiving the third identifier, the first IoT device performs a random access procedure to the reader / writer. This random access procedure is illustrated in Figure 7 above and will not be repeated here. After randomly accessing the reader / writer, the first IoT device sends identification information to the reader / writer to identify itself. This identification information can be an identifier used to identify the first IoT device, or it can be other information used to identify the first IoT device.

[0242] As can be seen, after receiving the third identifier, the first IoT device, configured with the third identifier, performs a random access procedure to the reader, and after successful random access, reports the identification information used to identify the first IoT device to the reader. Therefore, the identification information received by the reader is sent by the first IoT device in response to the third identifier broadcast by the reader.

[0243] In one optional implementation, after the first IoT device randomly connects to the reader, it sends a radio resource control (RRC) message to the reader. The RRC message includes a non-access-stratum (NAS) message, which includes identification information for identifying the first IoT device. Optionally, the NAS message may be a registration request message for the first IoT device.

[0244] S903. The reader sends first information to the core network equipment, the first information including identification information. Correspondingly, the core network equipment receives the first information sent by the reader.

[0245] In one possible implementation, the core network device receives first information sent by the reader, including: the core network device receiving identification information sent by the reader. The core network device receiving the identification information sent by the reader can be the core network device receiving identification information forwarded by the reader. For example, a first IoT device sends identification information to the reader (i.e., the identification information originates from the first IoT device), and the core network device receives the identification information from the first IoT device from the reader through the first information.

[0246] After receiving the identification information from the first IoT device, the reader sends first information, which includes the identification information, to the core network device. This method helps the core network device obtain the identification information reported by the first IoT device.

[0247] In one optional implementation, the reader sends an N2 message (or Next Generation Application Protocol (NGAP) message) to the core network device. The N2 message includes identification information, i.e., the first message is an N2 message.

[0248] In one optional implementation, the first information further includes a third identifier. Therefore, the reader also sends the third identifier to the core network device via the first information. This method facilitates the core network device in determining the identification information used to identify the first IoT device, which is reported by the first IoT device in response to the third identifier sent by the reader. This, in turn, allows the core network device to send the identification information used to identify the first IoT device to the first service requester corresponding to the third identifier, thereby completing the service inventory of the first service requester. In this application, reporting and sending can be interchanged.

[0249] Furthermore, in the first information, if the third identifier is a CAG ID, the reader sends the CAG ID of the first IoT device's response to the core network device, instead of sending all CAG IDs from the reader's supported CAG ID list. This allows the core network device to perform fine-grained access control on the first IoT device based on the CAG ID of the first IoT device's response.

[0250] In another optional implementation, the first information does not include the third identifier, but may include the timestamp of the third identifier broadcast by the reader / writer. When the reader / writer receives the identifier information from the first IoT device, it can determine that the identifier information was sent by the first IoT device in response to the third identifier. Therefore, when the reader / writer sends the first information to the core network device, it can include the timestamp of the broadcast third identifier in the first information. This approach allows the core network device to determine, based on the timestamp of the third identifier broadcast by the reader / writer, that the received identifier information was reported by the first IoT device in response to the third identifier broadcast by the reader / writer. This, in turn, allows the core network device to send the identifier information to the first service requester corresponding to the third identifier, thereby completing the service inventory of the first service requester. Furthermore, in this approach, the reader / writer does not need to modify the N2 message, reducing modifications to the protocol.

[0251] In one possible implementation, the core network device acquires time information corresponding to one or more first identifiers. The one or more first identifiers include a third identifier. For example, this can be understood as the core network device acquiring time information corresponding to a third identifier. The core network device determines, based on the timestamp of the third identifier and the time information corresponding to the one or more first identifiers, that the received identifier information was reported by the first IoT device in response to a reader broadcast a third identifier.

[0252] In another optional implementation, the first information includes a third identifier and a timestamp of the third identifier broadcast by the reader, thereby enabling the reader to determine the first service requester managing the first IoT device based on the third identifier and the timestamp of the third identifier broadcast by the reader.

[0253] Optionally, the first message may also include the location information of the first IoT device. The location information of the first IoT device may be one or more of the following: reader identifier (e.g., base station identifier or terminal identifier), cell identifier, CAG ID, and radio access network node identifier (RAN node ID), or it may be location information determined based on one or more of the following: reader identifier, cell identifier, and RAN node ID. The determined location information may be, for example, the longitude, latitude, and coordinate values ​​of the first IoT device.

[0254] S904. The core network equipment identifies the first service requester that manages the first IoT device.

[0255] In one optional implementation, when the first information includes a third identifier and / or a timestamp of the third identifier broadcast by the reader / writer, the first service requester is the service requester corresponding to the third identifier. Specifically, when the first information includes a third identifier, the core network device determines the first service requester managing the first IoT device by: obtaining one or more identifiers corresponding to each of the one or more service requesters, wherein the one or more service requesters include the first service requester; and determining the first service requester managing the first IoT device from the one or more service requesters based on the third identifier and the one or more identifiers corresponding to each service requester. In this application, the core network device determining the first service requester managing the first IoT device can be understood as the core network device determining the first service requester corresponding to the first IoT device.

[0256] As can be seen, when the first information includes the third identifier, the core network device determines the service requester corresponding to the third identifier based on one or more identifiers corresponding to each service requester among one or more service requesters. The service requester corresponding to the third identifier is the first service requester that manages the first IoT device.

[0257] Optionally, when the first information includes the timestamp of the third identifier broadcast by the reader / writer, the core network device determines the first service requester managing the first IoT device, including: obtaining one or more identifiers corresponding to each of the one or more service requesters, and time information corresponding to each of the one or more identifiers corresponding to each service requester; determining the third identifier based on the timestamp and the time information corresponding to each identifier; and determining the first service requester managing the first IoT device from the one or more service requesters based on the third identifier and the one or more identifiers corresponding to each service requester.

[0258] The core network device obtains one or more identifiers corresponding to each of the one or more service requesters, and time information corresponding to each of the one or more identifiers corresponding to each service requester, which can be achieved by receiving one or more identifiers corresponding to each of the one or more service requesters and time information corresponding to each of the one or more identifiers corresponding to each service requester from a reader / writer; or by receiving one or more identifiers from each of the one or more service requesters and time information corresponding to each of the one or more identifiers; or by receiving one or more identifiers from another core network device or network management system and time information corresponding to each of the one or more identifiers. This application does not limit the acquisition method of the core network device.

[0259] As can be seen, when the first information includes the timestamp of the third identifier broadcast by the reader / writer, the core network device determines the third identifier of the response of the first IoT device based on the timestamp, and thus the service requester corresponding to the third identifier is the first service requester managing the first IoT device.

[0260] Optionally, when the first information includes the third identifier and the timestamp of the third identifier broadcast by the reader / writer, the core network device determines the first service requester managing the first IoT device based on the third identifier and the timestamp of the third identifier broadcast by the reader / writer. The determination method can refer to the above-mentioned method based on the third identifier or based on the timestamp of the third identifier broadcast by the reader / writer, and will not be repeated here.

[0261] In this application, a timestamp can be understood as time information; for example, it can be used to represent the time information of an action.

[0262] In another optional implementation, when the first information does not include the third identifier or the timestamp of the third identifier broadcast by the reader / writer, the core network device determines that the first IoT device is responding to the third identifier broadcast by the reader / writer based on the time information corresponding to each of the one or more identifiers corresponding to each service requester, and the time of receiving the identifier information. Thus, the core network device determines the first service requester managing the first IoT device based on the third identifier broadcast by the reader / writer and one or more identifiers of each of the one or more service requesters.

[0263] Understandably, the time information corresponding to each of the one or more identifiers corresponding to each service requester is different, and the time information corresponding to the identifiers corresponding to multiple service requesters is also different. Therefore, the reader broadcasts one or more identifiers at different time periods or at different time points, meaning the broadcast times of the reader's one or more identifiers do not overlap. Consequently, the core network device can, based on the time of receiving the identifier information and the time information corresponding to each of the one or more identifiers, determine the identifier whose time information is earlier than the time of receiving the identifier information and is closest to the time of receiving the identifier information as the third identifier for the first IoT device's response. Furthermore, based on the third identifier and one or more identifiers of each of the one or more service requesters, the core network device determines the first service requester managing the first IoT device.

[0264] Optionally, the core network device acquires one or more identifiers corresponding to each of the one or more service requesters, and time information corresponding to each of the one or more identifiers corresponding to each service requester. In one optional implementation, the core network device acquiring one or more identifiers corresponding to each of the one or more service requesters, and time information corresponding to each of the one or more identifiers corresponding to each service requester, includes: receiving one or more identifiers corresponding to each of the one or more service requesters, and time information corresponding to each of the one or more identifiers corresponding to each service requester, sent by a reader / writer.

[0265] In another optional implementation, the core network device determines the first service requester managing the first IoT device by: determining the first service requester managing the first IoT device based on the subscription information of the first IoT device, wherein the subscription information includes the association relationship between the first IoT device and the first service requester. Therefore, when the subscription information of the first IoT device includes the correspondence between the first IoT device and the first service requester, the core network device can determine the first service requester managing the first IoT device based on the subscription information of the first IoT device.

[0266] In one optional implementation, the first information includes a third identifier. Before the core network device determines the first service requester managing the first IoT device, it also performs access control on the first IoT device based on the third identifier and a list of allowed first identifiers configured for the first IoT device. When the core network device includes the received third identifier in the list of allowed first identifiers configured for the first IoT device, it allows the first IoT device to access the network through the cell corresponding to the third identifier.

[0267] In one optional implementation, the first information includes a third identifier. When the third identifier is a CAG ID, before the core network device determines the first service requester managing the first IoT device, it also performs access control on the first IoT device based on the CAG ID and the list of allowed CAG IDs configured for the first IoT device. When the core network device includes the received CAG ID in the list of allowed CAG IDs configured for the first IoT device, it allows the first IoT device to access the network through the cell corresponding to the CAG ID.

[0268] Optionally, when the core network equipment allows the first IoT device to access the network through the cell corresponding to the received CAG ID, it can also send response information to the first IoT device via a reader / writer. This response information can be a registration acceptance message. Thus, the first IoT device can learn from the response information that it can access the network through the cell corresponding to the responding CAG ID.

[0269] As can be seen, the first information also includes a third identifier, which is a CAG ID. When the first IoT device is configured with this CAG ID, the core network device allows the first IoT device to access the network through the cell corresponding to this CAG ID. In this method, the core network device performs access control on the first IoT device based on the CAG ID responded by the first IoT device, which can improve the accuracy of access control. In addition, when the third identifier is a CAG ID, the reader can trigger the service inventory of the first service requester based on the CAG ID mechanism, which can reduce modifications to the network.

[0270] S905. The core network equipment sends identification information to the first service requester. Correspondingly, the first service requester receives the identification information from the core network equipment.

[0271] After the core network equipment identifies the first service requester that manages the first IoT device, it sends identification information to the first service requester to identify the first IoT device in order to complete the service inventory of the first service requester, that is, to complete the inventory of the services associated with the third identifier.

[0272] In one optional implementation, when the first information further includes the location information of the first IoT device, the core network device also sends the location information of the first IoT device to the first service requester so that the first service requester can obtain the location of the first IoT device.

[0273] In this embodiment, the reader broadcasts a third identifier based on the time information of the third identifier. A first IoT device configured with the third identifier responds to the third identifier broadcast by the reader and, after randomly accessing the reader, reports identification information used to identify the first IoT device. Thus, the reader reports the identification information used to identify the first IoT device to the core network device. After receiving the identification information, the core network device determines the first service requester managing the first IoT device and sends the identification information to the first service requester to perform service inventory for the first service requester. It can be seen that the reader performs service inventory for the first service requester by broadcasting the third identifier corresponding to the first service requester within a specific time period. This method reduces signaling overhead compared to the reader triggering service inventory for all service requesters within its coverage area by broadcasting a list of identifiers supported by the reader.

[0274] Please refer to Figure 10. Figure 10 provides a detailed description of communication method 200, using the first IoT device as tag a, the core network equipment including AMF, the first service requester as AF#1, and the third identifier as CAG ID#1 as an example. As shown in Figure 10, the interaction process between tag a, the reader, AMF, and AF#1 includes, but is not limited to, the following steps:

[0275] S1001. The reader broadcasts a select message based on the time information corresponding to CAG ID#1. The select message includes CAG ID#1, and CAG ID#1 corresponds to AF#1.

[0276] Optionally, the select message may also include storage area information, which identifies the storage area where the CAG ID#1 is stored. This method allows the tag to determine the CAG ID#1 based on this storage area information.

[0277] Optionally, before broadcasting the select message, the reader / writer obtains one or more CAG IDs corresponding to AF#1, as well as the time information corresponding to each of the one or more CAG IDs, including CAG ID#1. Then, based on the time information corresponding to CAG ID#1, the reader / writer broadcasts CAG ID#1 by broadcasting the select message.

[0278] Furthermore, CAG ID#1 is one of one or more CAG IDs supported by the reader. Therefore, the reader broadcasts one of the one or more CAG IDs it supports, rather than all of them. This allows the reader to trigger service inventory for the service requester corresponding to CAG ID#1 (i.e., AF#1), rather than triggering service inventory for all service requesters within the reader's coverage area, thus reducing signaling overhead.

[0279] S1002. The reader sends a Query command or a QueryRep command to tag a.

[0280] Understandably, the reader sends Query or QueryRep commands multiple times.

[0281] S1003. Tag a sends a random number RN16 to the reader. Correspondingly, the reader receives the random number RN16 from tag a.

[0282] Understandably, after receiving the CAG ID#1 broadcast by the reader, tag a generates a random number. Each time tag a receives a Query command or QueryRep command, it decrements the generated random number by one. When the generated random number is 0, tag a sends a 16-bit random number to the reader, i.e., it sends the random number RN16.

[0283] S1004. The reader sends an acknowledgment (ACK) to tag a, which includes a random number RN16. Tag a then receives the ACK from the reader.

[0284] Understandably, after receiving the random number RN16 from tag a, the reader sends an ACK carrying the random number RN16 back to the tag.

[0285] S1005. Tag a sends identification information to the reader to identify tag a, which is a tag configured with CAG ID#1. Correspondingly, the reader receives the identification information from tag a.

[0286] If tag a confirms that the random number RN16 included in the ACK from the reader is the same random number RN16 that tag a sent to the reader, then tag a sends identification information to the reader to identify tag a. It can be seen that the identification information used to identify tag a is sent by tag a in response to the CAG ID#1 broadcast by the reader.

[0287] In one optional implementation, tag a sends an RRC message to the reader, the RRC message including identification information for identifying tag a. Optionally, the RRC message includes a NAS message, the NAS message including identification information for identifying tag a. Optionally, the NAS message may be a registration request message for tag a.

[0288] S1006. The reader sends identification information, CAG ID#1, and / or the timestamp of the reader broadcasting CAG ID#1 to the AMF. Correspondingly, the AMF receives the identification information sent by the reader, CAG ID#1, and / or the timestamp of the reader broadcasting CAG ID#1.

[0289] In one optional implementation, the reader sends an N2 message (or NGAP message) to the AMF, which includes identification information for identifying tag a, and CAG ID#1 and / or a timestamp of the reader broadcasting CAG ID#1, wherein the identification information for identifying tag a comes from tag a.

[0290] Here, CAG ID#1 is one of one or more CAG IDs supported by the reader / writer. Therefore, the reader / writer does not send one or more CAG IDs it supports to the AMF, but rather CAG ID#1 from one or more CAG IDs it supports. This allows the reader / writer to perform fine-grained access control on tag a based on CAG ID#1.

[0291] Understandably, after receiving the identification information from tag a, the reader sends the identification information, along with the timestamp of the CAG ID#1 responded by tag a or the CAG ID#1 broadcast by the reader, to the AMF. This helps the AMF determine that the identification information was reported by tag a in response to the CAG ID#1 broadcast by the reader.

[0292] S1007.AMF determines the AF#1 of the management label a.

[0293] In one optional implementation, when the AMF receives CAG ID#1 from the reader, the AMF determines the AF#1 corresponding to CAG ID#1 based on CAG ID#1 and one or more CAG IDs corresponding to each of the one or more AFs. The AF#1 corresponding to CAG ID#1 is the AF#1 of the management tag a.

[0294] In another optional implementation, when the AMF receives the timestamp of the reader broadcasting CAG ID#1 from the reader, the AMF determines that the identification information is reported by tag a in response to CAG ID#1 based on the timestamp of the reader broadcasting CAG ID#1 and the time of receiving the identification information. Then, the reader determines the AF#1 corresponding to CAG ID#1 based on CAG ID#1 and one or more CAG IDs corresponding to each of the one or more AFs. The AF#1 corresponding to CAG ID#1 is the AF#1 managing tag a.

[0295] In another optional implementation, the AMF obtains the subscription information of tag a identified by the identification information. If the subscription information of tag a includes AF#1 associated with tag a, the AMF directly determines the AF managing tag a as AF#1 based on the subscription information of tag a.

[0296] Optionally, the AMF performs access control on tag a before determining the AF#1 of tag a. Optionally, the AMF interacts with the UDM to perform access control on tag a. If CAG ID#1 is a CAG ID allowed by tag a, the AMF allows tag a to access the network through the cell corresponding to CAG ID#1, such as accessing a cell that supports the IoT service / access technology type of the environment. In this method, the AMF performs access control on tag a based on the CAG ID#1 responded by tag a, rather than based on all CAG IDs supported by the reader, thereby achieving precise access control for tag a.

[0297] Optionally, after tag a accesses the IoT environment via the cell corresponding to CAG ID#1, AMF also sends response information to tag a via a reader, such as a registration message, to inform tag a that it can access the network via the cell corresponding to CAG ID#1.

[0298] S1008.AMF sends identification information to AF#1 to identify tag a.

[0299] The AMF sends identification information to AF#1 to identify tag a, enabling the inventory of services in AF#1, specifically the inventory of services associated with CAG ID#1 in AF#1. Therefore, the reader / writer can achieve the inventory of specific services in AF#1 by broadcasting CAG ID#1.

[0300] Optionally, if the reader also sends the location information of tag a to the AMF, the AMF can also send the location information of tag a to AF#1. The specific format of the location information of tag a can be found in the communication method 200 described above, and will not be repeated here.

[0301] As can be seen, after the reader broadcasts CAG ID#1, tag a, configured with CAG ID#1, randomly accesses the reader and reports identification information to identify tag a. The reader then sends the identification information and CAG ID#1 to the AMF. Based on CAG ID#1, the AMF determines the AF#1 that manages tag a. Furthermore, the AMF sends the identification information for tag a to AF#1, enabling service inventory management of AF#1. Additionally, AF#1 can perform fine-grained access control on tag a based on CAG ID#1, meaning it can determine whether tag a can access the network based on the cell corresponding to CAG ID#1.

[0302] Please refer to Figure 11, which is a schematic diagram of another communication method. The communication method shown in Figure 11 differs from that described in Figure 10 in that, after receiving the identification information from tag a, the reader sends the identification information to the AMF, but does not send the CAG ID#1 responded by tag a, nor does it send the timestamp of the reader broadcasting the CAG ID#1. This method allows the reader to maintain the N2 message without modification, reducing changes to the protocol.

[0303] In addition, during the initialization process, the AMF obtains one or more CAG IDs corresponding to each of the one or more service requesters, as well as the time information corresponding to each of the one or more CAG IDs. Therefore, after receiving the identification information from the reader, the AMF determines, based on the time information corresponding to each of the one or more CAG IDs for each service requester, that the identification information was reported by tag a in response to the reader's broadcast of CAG ID#1. Furthermore, based on CAG ID#1, the AMF determines the AF#1 managing tag a and sends the identification information to AF#1, thus enabling service inventory management of AF#1. Additionally, the AMF can also perform fine-grained access control on tag a based on CAG ID#1.

[0304] As can be seen, the difference between S1101 to S1108 in Figure 11 and S1001 to S1008 in Figure 10 is that in S1106, the reader sends identification information for tag a to the AMF. That is, in S1106, the reader does not send identification information, CAG ID#1, or the timestamp of the reader broadcasting CAG ID#1. Furthermore, in S1107, the AMF determines the AF#1 for managing tag a, specifically by determining the CAG ID#1 of tag a's response based on the time information corresponding to one or more identifiers of each of the one or more service requesters, and the time of receiving the identification information, and then determining the AF#1 for managing tag a based on the CAG ID#1. In contrast, in S1007, the AMF directly determines the AF#1 for managing tag a based on the CAG ID#1 or the timestamp of the reader broadcasting CAG ID#1.

[0305] Please refer to Figure 12, which is an interactive schematic diagram of another communication method 300. As shown in Figure 12, this communication method includes, but is not limited to, the following steps:

[0306] S1201. The reader obtains one or more access group identifiers, as well as the time information corresponding to one or more access group identifiers.

[0307] The time information corresponding to one or more access group identifiers can be: time information corresponding to some or all of the access group identifiers in one or more access group identifiers. One or more access group identifiers can be access identifiers used by IoT devices when accessing a cell, such as the CAG ID mentioned above; this embodiment does not limit this. Additionally, the access group identifier can also be called a group access identifier, or other identifiers used to distinguish different terminals performing the access process; this embodiment does not limit this.

[0308] Furthermore, the difference between the one or more access group identifiers and the first identifier mentioned above is that the access group identifier in the one or more access group identifiers may or may not correspond to the service requester, that is, there may or may not be an association between the access group identifier and the service requester. In other words, this application embodiment does not limit the relationship between the access group identifier and the service requester.

[0309] The time information corresponding to one or more access group identifiers is similar to the time information corresponding to one or more first identifiers mentioned above. For example, the time information corresponding to an access group identifier can be a broadcast time requirement, that is, a broadcast access group identifier time requirement, which will not be elaborated further. The specific forms of the time information corresponding to different access group identifiers among the one or more access group identifiers can be the same or different, and this application embodiment does not limit this.

[0310] In one optional implementation, the time information corresponding to different access group identifiers in one or more access group identifiers is different, thus the broadcast times of different access group identifiers in one or more access group identifiers are different. This method is beneficial for the reader to broadcast different access group identifiers in one or more access group identifiers at different time periods, which in turn is beneficial for IoT devices that have obtained different access group identifiers to initiate the registration process with the network at different time periods, thereby reducing network congestion.

[0311] In this embodiment of the application, the registration process can be replaced by an access process, and the process used to enable the terminal to access the network can be considered as a registration process or an access process.

[0312] In one optional implementation, the reader acquires one or more access group identifiers and corresponding time information, including receiving one or more access group identifiers and corresponding time information from the core network device. In one possible implementation, to ensure that the number of IoT devices accessing the network at the same time does not exceed a certain threshold, the core network device determines one or more access group identifiers and corresponding time information, allowing multiple IoT devices to access the network at different times based on different access group identifiers, thus reducing network congestion. Furthermore, the core network device sends the determined one or more access group identifiers and their corresponding time information to the reader, so that the reader broadcasts different access group identifiers at different times, thereby facilitating access by different core network devices at different times or within different time periods.

[0313] In another optional implementation, the reader is configured with one or more access group identifiers and corresponding time information. Therefore, the reader obtaining one or more access group identifiers and their corresponding time information can be understood as: obtaining one or more access group identifiers and their corresponding time information through configuration information. This configuration information may be pre-configured to the reader by the core network equipment.

[0314] S1202. The reader broadcasts one or more access group identifiers based on the time information corresponding to one or more access group identifiers.

[0315] In one optional implementation, the reader broadcasts one or more access group identifiers based on the time information corresponding to one or more access group identifiers. This can be understood as the reader broadcasting some or all of the access group identifiers based on the time information corresponding to some or all of the access group identifiers among the one or more access group identifiers.

[0316] Optionally, the reader broadcasts one or more access group identifiers based on the time information corresponding to one or more access group identifiers. This can also be understood as: for any one of the one or more access group identifiers, the reader broadcasts the access group identifier based on the time information corresponding to that access group identifier.

[0317] For example, the first TAI is TAI#1, and the multiple access group identifiers include access group identifier 1 and access group identifier 2. The time information corresponding to access group identifier 1 is time t1, and the time information corresponding to access group identifier 2 is time t2. Then the reader broadcasts access group identifier 1 at time t1 and access group identifier 2 at time t2.

[0318] As can be seen, the reader can broadcast different access group identifiers at different times or within different time periods based on the time information corresponding to different access group identifiers in one or more access group identifiers. This allows multiple IoT devices to initiate registration processes with the network at different times or within different time periods based on their own acquired access group identifiers. Compared to multiple IoT devices initiating registration processes with the network at the same time or within the same time period, this method reduces the number of IoT devices initiating registration processes with the network at the same time or within the same time period, thus reducing network congestion.

[0319] In addition, when the time information corresponding to the access group identifier is in different forms, the reader broadcasts the access group identifier based on the time information corresponding to the access group identifier. For the implementation method of broadcasting the first identifier based on the time information corresponding to the first identifier when the time information corresponding to the first identifier is in different forms, please refer to S802 above. This implementation method will not be repeated here.

[0320] In one optional implementation, when broadcasting one or more access group identifiers based on time information corresponding to one or more access group identifiers, the reader also broadcasts a first TAI. This allows multiple IoT devices moving from other TAIs to the first TAI to initiate registration procedures with the network at different times or within different time periods based on their own acquired access group identifiers. This method reduces network congestion compared to multiple IoT devices moving from other TAIs to the first TAI initiating registration procedures with the network at the same time or within the same time period.

[0321] The first TAI can be the tracking area identifier corresponding to the reader / writer. In one possible implementation, other devices (such as core network devices) configure the corresponding tracking area identifier based on the physical location of the reader / writer or the coverage area of ​​the reader / writer. In another possible implementation, the tracking area is a logical tracking area used to distinguish different readers / writers and is independent of the actual physical deployment location.

[0322] For example, the reader broadcasts access group identifier 1 and TAI#1 at time t1 corresponding to access group identifier 1, and broadcasts access group identifier 2 and TAI#1 at time t2 corresponding to access group identifier 2. It can be seen that since TAI is broadcast periodically and is unrelated to the broadcast access group identifier, the reader broadcasts TAI#1 at both t1 and t2. However, the access group identifier broadcast by the reader is different at different times.

[0323] Optionally, the TAI mentioned above can be replaced with other identification information, such as identification information set for AmbientIoTDevice to perform mobility management, or other identification information used to distinguish different areas or different logical areas. This application does not limit the TAI.

[0324] Optionally, when the reader broadcasts an access group identifier and the first TAI, it can also broadcast other system information, such as the PLMN ID.

[0325] In this embodiment, the reader broadcasts one or more access group identifiers based on time information corresponding to those identifiers, enabling multiple IoT devices to initiate registration processes with the network at different times or within different time periods based on their acquired access group identifiers. This method reduces network congestion compared to multiple IoT devices initiating registration processes with the network at the same time or within the same time period.

[0326] This application also proposes a communication method 400 for a reader / writer broadcasting any one of one or more access group identifiers. For ease of description, this communication method 400 is illustrated using the example of the first access group identifier being one of one or more access group identifiers. Figure 13 is an interactive schematic diagram of the communication method 400. The communication method 400 is described from the perspective of the interaction between the reader / writer, the IoT device, and the core network device. The communication method 400 includes, but is not limited to, the following steps:

[0327] S1301. The reader broadcasts third information based on the time information corresponding to the first access group identifier, the third information including the first access group identifier.

[0328] In one optional implementation, before the reader executes S1301, it acquires one or more access group identifiers and time information corresponding to one or more access group identifiers. The one or more access group identifiers include a first access group identifier. The implementation of this method can be found in S1201 above, and will not be repeated here.

[0329] The first access group identifier is any one of one or more access group identifiers. The reader broadcasts the third information based on the time information corresponding to the first access group identifier. This can be understood as: for any one of one or more access group identifiers, the reader broadcasts the third information based on the time information corresponding to that access group identifier.

[0330] It is evident that the reader broadcasts one of one or more access group identifiers at the same time or within the same time period, rather than broadcasting all access group identifiers. This is beneficial for triggering the access process of the IoT device that obtains the first access group identifier broadcast by the reader at the current time, rather than multiple IoT devices initiating access processes at the same time or within the same time period, which would cause network congestion.

[0331] In one optional implementation, the third information further includes the first TAI corresponding to the reader / writer. Alternatively, when the reader / writer broadcasts the first access group identifier based on the time information corresponding to the first access group identifier, it also broadcasts the first TAI. For example, one or more access group identifiers include access group identifier a and access group identifier b. The reader / writer broadcasts third information #1 based on the time information corresponding to access group identifier a, and broadcasts third information #2 based on the time information corresponding to access group identifier b. Third information #1 includes access group identifier a and the first TAI, and third information #2 includes access group identifier b and the first TAI.

[0332] It is evident that when a reader broadcasts one of one or more access group identifiers at the same time or within the same time period, it can also broadcast the first TAI. This is beneficial for triggering IoT devices that have moved from other TAIs to the first TAI and have stored the first access group identifier broadcast by the reader at the current time to initiate the access process, rather than a large number of IoT devices initiating the access process at the same time or within the same time period when they move from other TAIs to the first TAI, causing network congestion.

[0333] Optionally, when broadcasting third-party information, the reader / writer can also broadcast other system information, such as the PLMN ID. Optionally, the third-party information can also include other system information, such as the PLMN ID.

[0334] S1302. The second IoT device sends a registration request to the reader. The registration request includes the identification information of the second IoT device. The second IoT device is an IoT device that has obtained the identification of the first access group.

[0335] In one alternative implementation, the second IoT device is an IoT device that moves from another TAI to the first TAI. Therefore, when the second IoT device enters the range corresponding to the first TAI, it does not obtain the first TAI and needs to initiate a registration process.

[0336] Optionally, the second IoT device acquires the first access group identifier, which can be understood as: the second IoT device is pre-configured with the first access group identifier.

[0337] Optionally, the second IoT device is not pre-configured with a first access group identifier. The first access group identifier obtained by the second IoT device is sent to the second IoT device by the core network device (such as AMF) through a reader / writer. In one possible implementation, the core network device determines whether to send an access group identifier to the second IoT device based on the number of IoT devices currently connected and managed / served by the core network device. In another possible implementation, the core network device determines whether to send an access group identifier to the second IoT device based on the access group corresponding to one or more IoT devices currently connected and managed / served by the core network device. For example, if there are few currently connected IoT devices and packet access is not required, the core network device determines that it does not need to send an access group identifier to the second IoT device; if there are many currently connected IoT devices and packet access is required, it determines to send an appropriate access group identifier (such as a first access group identifier) ​​to the second IoT device to reduce network congestion by keeping the number of IoT devices corresponding to that access group identifier within a suitable range.

[0338] Therefore, when the second IoT device with the first access group identifier receives the first access group identifier (optionally, and the first TAI) broadcast by the reader, it determines that it can initiate a registration process with the network, such as sending a registration request to the reader to request access to the network.

[0339] For example, if the TAI (e.g., TAI#1) obtained by the second IoT device does not include the TAI (TAI#2) currently broadcast by the reader, it indicates that the IoT device has moved out of the previous area and entered a new area. In this case, the second IoT device needs to re-access the network in the new area to perform mobility management. The second IoT device also stores an access group identifier 2. The reader broadcasts third information #1 at time t1 and third information #2 at time t2. Third information #1 includes TAI#2 and access group identifier 1, while third information #2 includes TAI#2 and access group identifier 2. The second IoT device receives the third information #1 broadcast by the reader at time t1, but because its stored access group identifier (access group identifier 2) is not the same as the access group identifier 1 in third information #1, the second IoT device does not initiate a registration process with the network at time t1. The second IoT device receives the third information #2 broadcast by the reader at time t2, and because its stored access group identifier (access group identifier 2) is the same as the access group identifier in third information #2, the second IoT device initiates a registration process with the network to request network access. It is evident that the second IoT device only initiates the registration process with the network when it moves to the TAI currently broadcast by the reader and the obtained access group identifier is the same as the access group identifier broadcast by the reader. This allows different IoT devices to request network access at different times or in different time periods, thereby reducing network congestion.

[0340] S1303. The reader sends the identification information of the second IoT device to the core network equipment.

[0341] The identification information of the second IoT device is used to identify the second IoT device. For example, the identification information of the second IoT device is the device identifier of the second IoT device.

[0342] Optionally, after receiving a registration request from the second IoT device, the reader sends the identification information of the second IoT device to the core network device so that the core network device can perform security verification on the second IoT device and determine whether to allow the second IoT device to join the network.

[0343] S1304. The core network equipment performs security verification on the second IoT device based on the identification information of the second IoT device.

[0344] The implementation of S1304 can be found in Figure 6 above, where the terminal device, AMF, AUSF, and UDM interact and perform security processes such as authentication, which will not be described in detail here.

[0345] Optionally, after the core network device passes the security verification of the second IoT device, it can also send a NAS message to the second IoT device through the reader / writer. The NAS message includes a registration acceptance message sent by the AMF to the terminal device. The registration acceptance message can be seen in Figure 6 above, and will not be described again.

[0346] In one alternative implementation, the core network device (such as AMF) can send TAI update information to the second IoT device, which includes the identifier of the first TAI. Therefore, when the second IoT device is still within the area corresponding to the first TAI, it does not need to frequently initiate a registration process with the network. Instead, it only initiates a registration process after moving out of the area corresponding to the first TAI, thus reducing the power consumption of the second IoT device.

[0347] Optionally, the core network device (such as the AMF) can determine whether to remove or update the access group identifier for the second IoT device based on the number of IoT devices currently connected and managed / served by the AMF. If an update is required, the core network device sends the new access group identifier to the second IoT device.

[0348] As can be seen, in this embodiment, the reader broadcasts the first access group identifier based on the time information corresponding to the first access group identifier. Therefore, the second IoT device that receives the first access group identifier broadcast by the reader and acquires the first access group identifier initiates a registration process with the network to request network access. This method allows IoT devices that have acquired different access group identifiers to access the network in batches at different times, preventing these IoT devices from simultaneously initiating a large number of access processes and causing network congestion.

[0349] Optionally, when the reader broadcasts the first access group identifier based on the time information corresponding to the first access group identifier, it also broadcasts the first TAI corresponding to the reader. This allows second IoT devices that move from other TAIs to the first TAI and receive the first access group identifier broadcast by the reader, as well as those that have obtained the first access group identifier themselves, to initiate a registration process to access the network. This method allows a large number of IoT devices to move from other TAIs to the first TAI, with IoT devices obtaining different access group identifiers accessing the network in batches at different times, preventing these IoT devices from simultaneously initiating a large number of access processes and causing network congestion.

[0350] The following section further describes the corresponding device implementation scheme in relation to the technical solution described above.

[0351] To achieve the functions of the methods provided in the embodiments of this application, the reader, core network device, and first service requester may include hardware structures and / or software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular function is executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.

[0352] As shown in Figure 14, this application embodiment provides a communication device 1400. The communication device 1400 can be a component of a reader / writer (e.g., an integrated circuit, a chip, etc.), a component of a core network device (e.g., an integrated circuit, a chip, etc.), or a component of a first service requester (e.g., an integrated circuit, a chip, etc.). The communication device 1400 can also be other communication units used to implement the methods in the method embodiments of this application. The communication device 1400 may include a communication unit 1401 and a processing unit 1402. Optionally, it may also include a storage unit 1403.

[0353] In one possible design, one or more units as shown in Figure 14 may be implemented by one or more processors, or by one or more processors and memory; or by one or more processors and transceivers; or by one or more processors, memory, and transceivers. This application embodiment does not limit this. The processors, memory, and transceivers can be configured individually or integrated.

[0354] The communication device 1400 is equipped with the functions of a reader / writer described in the embodiments of this application, or the functions of a core network device. For example, the communication device 1400 includes modules, units, or means corresponding to the site-related steps in the above method embodiments, which can be implemented by software, hardware, or hardware executing corresponding software, or a combination of software and hardware. Further details can be found in the corresponding descriptions in the foregoing method embodiments.

[0355] In one possible design, the communication device 1400 may include a processing unit 1402 and a communication unit 1401, the device being applied to a reader / writer, the communication unit 1401 being used for transmitting and receiving signaling / signals;

[0356] The processing unit is configured to acquire one or more first identifiers, and time information corresponding to each of the one or more first identifiers, wherein the one or more first identifiers correspond to a first service requester;

[0357] The processing unit is further configured to broadcast the one or more first identifiers based on the time information corresponding to each of the one or more first identifiers.

[0358] In addition, other optional implementations of the communication device 1400 can be found in the relevant content of the above-described method embodiments, which will not be described in detail here.

[0359] The embodiments of this application and the method embodiments shown above are based on the same concept and have the same technical effects. For the specific principles, please refer to the description of the embodiments shown above, which will not be repeated here.

[0360] In another possible design, the communication device 1400 may include a processing unit 1402 and a communication unit 1401, the device being applied to a core network device;

[0361] The communication unit 1401 is used to receive first information sent by the reader, the first information including identification information, the identification information being used to identify the first Internet of Things device;

[0362] The processing unit 1402 is used to determine the first service requester managing the first IoT device;

[0363] The communication unit 1401 is also used to send the identification information to the first service requester.

[0364] In addition, other optional implementations of the communication device 1400 can be found in the relevant content of the above-described method embodiments, which will not be described in detail here.

[0365] The embodiments of this application and the method embodiments shown above are based on the same concept and have the same technical effects. For the specific principles, please refer to the description of the embodiments shown above, which will not be repeated here.

[0366] In another possible design, the communication device 1400 may include a processing unit 1402 and a communication unit 1401, the device being applied to a first service requester, the processing unit 1402 being used to process signals / signaling;

[0367] The communication unit 1401 is used to send one or more first identifiers corresponding to the first service requester, and time information corresponding to each of the one or more first identifiers;

[0368] The communication unit 1401 is further configured to receive identification information, which is used to identify a first IoT device. The identification information is sent by the first IoT device in response to a third identifier broadcast by a reader / writer. The third identifier is one of the one or more first identifiers. The first IoT device is an IoT device managed by the first service requester.

[0369] In another possible design, the communication device 1400 may include a processing unit 1402 and a communication unit 1401, the device being applied to the reader / writer, the communication unit 1401 being used for transmitting and receiving signaling / signals;

[0370] The processing unit 1402 is used to obtain one or more access group identifiers and time information corresponding to one or more access group identifiers;

[0371] The processing unit 1402 is further configured to broadcast one or more access group identifiers based on the time information corresponding to one or more access group identifiers.

[0372] In another embodiment, the communication device 1400 includes a processing unit 1402 and a communication unit 1401. The device is applied to an Internet of Things (IoT) device, and the processing unit 1402 is used to process signals / signaling.

[0373] The communication unit 1401 is used to receive the first access group identifier broadcast by the reader / writer, and the communication device is an Internet of Things device that obtains the first access group identifier.

[0374] The communication unit 1401 is also used to send a registration request to the reader, the registration request including the identification information of the second Internet of Things device.

[0375] In addition, other optional implementations of the communication device 1400 can be found in the relevant content of the above-described method embodiments, which will not be described in detail here.

[0376] The embodiments of this application and the method embodiments shown above are based on the same concept and have the same technical effects. For the specific principles, please refer to the description of the embodiments shown above, which will not be repeated here.

[0377] This application also provides a communication device 1500, and Figure 15 is a schematic diagram of the communication device 1500. The communication device 1500 can be a reader / writer, or a chip, chip system, or processor that supports the reader / writer in implementing the above methods; alternatively, it can be a core network device, or a chip, chip system, or processor that supports the core network device in implementing the above methods; it can be a first service requester, or a chip, chip system, or processor that supports the first service requester in implementing the above methods. This device can be used to implement the methods described in the above method embodiments, and specific details can be found in the descriptions in the above method embodiments.

[0378] The communication device 1500 may include one or more processors 1501. The processor 1501 may be a general-purpose processor or a special-purpose processor. For example, it may be a baseband processor, digital signal processor, application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control the communication device (e.g., base station, baseband chip, terminal, terminal chip, distributed unit (DU) or centralized unit (CU), execute software programs, and process data from the software programs.

[0379] Optionally, the communication device 1500 may include one or more memories 1502, which may store instructions 1504 that can be executed on the processor 1501, causing the communication device 1500 to perform the methods described in the above method embodiments. Optionally, the memory 1502 may also store data. The processor 1501 and the memory 1502 may be provided separately or integrated together.

[0380] Optionally, the communication device 1500 may further include a transceiver 1505 and an antenna 1506. The transceiver 1505 may be referred to as a transceiver unit, transceiver, or transceiver circuit, etc., and is used to implement the transmission and reception functions. The transceiver 1505 may include a receiver and a transmitter. The receiver may be referred to as a receiver or receiving circuit, etc., and is used to implement the receiving function; the transmitter may be referred to as a transmitter or transmitting circuit, etc., and is used to implement the transmitting function.

[0381] In one possible design, the communication device 1500 can be applied to a reader / writer. Specifically, the processor 1501 is used to execute S801 and S802 in the above-mentioned communication method 100, S1201 and S1202 in the communication method 300, and S1301 in the communication method 400; the transceiver 1505 is used to execute S901, S902 and S903 in the above-mentioned communication method 200, and S1302 and S1303 in the communication method 400.

[0382] In another possible design, the communication device 1500 can be applied to a core network device. Specifically, the processor 1501 is used to execute S904 in the above-mentioned communication method 200 and S1304 in the communication method 400; the transceiver 1505 is used to execute S903 and S905 in the above-mentioned communication method 200 and S1303 in the communication method 400.

[0383] In another possible design, the communication device 1500 can be applied to core network equipment, specifically, the transceiver 1505 is used to perform S905 in the above-described communication method 200.

[0384] Optionally, the processor 1501 may store instructions 1503, which, when executed on the processor 1501, cause the communication device 1500 to perform the methods described in the above method embodiments. Instructions 1503 may be embedded in the processor 1501; in this case, the processor 1501 may be implemented in hardware.

[0385] The embodiments of this application and the method embodiments shown in the above-described communication methods 100 to 400 are based on the same concept and have the same technical effects. For the specific principles, please refer to the description of the embodiments shown in the above-described communication methods 100 to 400, which will not be repeated here.

[0386] This application also provides a computer-readable storage medium for storing computer software instructions, which, when executed by a communication device, implement the functions of any of the above method embodiments.

[0387] This application also provides a computer program product for storing computer software instructions, which, when executed by a communication device, implement the functions of any of the above method embodiments.

[0388] This application also provides a computer program that, when run on a computer, implements the functions of any of the above method embodiments.

[0389] This application also provides a communication system that may include a reader / writer and a core network device. In another possible design, the system may further include other devices that interact with the reader / writer and the core network device, such as IoT devices and service requesters.

[0390] The terms "first" and "second," etc., in the specification, claims, and drawings of this application are used to distinguish different objects, not to describe a specific order. "First," "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Therefore, a feature defined with "first," "second," etc., may explicitly or implicitly include one or more of that feature. In the description of this embodiment, unless otherwise stated, "a plurality of" means two or more.

[0391] Furthermore, the terms “comprising” and “having”, and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the steps or units listed, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus.

[0392] In this application, the term "embodiment" is used to mean that a specific feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a mutually exclusive, independent, or alternative embodiment. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0393] In the embodiments of this application, "at least one (item)" refers to one or more, "more than one" refers to two or more, and "and / or" is used to describe the association relationship of related objects, indicating that there can be three relationships. For example, "A and / or B" can represent three cases: only A exists, only B exists, and A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0394] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

[0395] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., SSDs), etc.

[0396] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

A communication method, characterized in that, The method is applied to a reader / writer, and the method includes: Obtain one or more first identifiers, and time information corresponding to each of the one or more first identifiers, wherein the one or more first identifiers correspond to a first service requester; Based on the time information corresponding to each of the one or more first identifiers, the one or more first identifiers are broadcast. The method according to claim 1, characterized in that, After broadcasting the one or more first identifiers, the method further includes: Receive identification information from a first IoT device, the identification information being used to identify the first IoT device, the first IoT device being an IoT device managed by the first service requester; Send first information to the core network equipment, the first information including the identification information. The method according to claim 1 or 2, characterized in that, The step of obtaining one or more first identifiers, and the time information corresponding to each of the one or more first identifiers, includes: Receive one or more first identifiers from the core network device, and time information corresponding to each of the one or more first identifiers. The method according to any one of claims 1 to 3, characterized in that, The method further includes: Obtain one or more second identifiers, and time information corresponding to each of the one or more second identifiers, wherein the one or more second identifiers correspond to a second service requester; Based on the time information corresponding to each of the one or more second identifiers, broadcast the one or more second identifiers; The time information corresponding to the first identifier is different from the time information corresponding to the second identifier. The method according to claim 2, characterized in that, The first information also includes a third identifier and / or a timestamp of the third identifier broadcast by the reader / writer. The third identifier is a first identifier that the first IoT device responds to when sending the identifier information, and the third identifier is one of the one or more first identifiers. The method according to claim 2 or 5, characterized in that, The first information also includes the location information of the first IoT device. The method according to any one of claims 1 to 6, characterized in that, The time information corresponding to different first identifiers in the one or more first identifiers is different. The method according to any one of claims 1 to 7, characterized in that, The method further includes: Broadcast storage area information, which is used to characterize the storage area storing the one or more first identifiers. The method according to any one of claims 1 to 8, characterized in that, The time information includes one or more of the following: sending time, sending period, valid time, sending frequency, and sending interval. The method according to any one of claims 1 to 9, characterized in that, The one or more first identifiers are closed access group identifiers. The method according to any one of claims 1 to 10, characterized in that, The one or more first identifiers correspond to environmental IoT services. The method according to any one of claims 1 to 11, characterized in that, The method further includes: Obtain second information, which is used to instruct the updating of the first identifier corresponding to the first service requester; Based on the second information, update the first identifier corresponding to the first service requester. The method according to any one of claims 1 to 11, characterized in that, The one or more first identifiers are identifiers used by IoT devices to access the cell, or identifiers of the first service requester, or identifiers of the first service requester's service, or group identifiers. A communication method, characterized in that, The method is applied to core network equipment, and the method includes: The system receives first information sent by a reader / writer, the first information including identification information, the identification information being used to identify a first Internet of Things (IoT) device. Identify the first service requester that manages the first IoT device; The identification information is sent to the first service requester. The method according to claim 14, characterized in that, The first information also includes a third identifier and / or the timestamp of the third identifier broadcast by the reader / writer, wherein the first service requester is the service requester corresponding to the third identifier. The method according to claim 14, characterized in that, The process of determining the first service requester managing the first IoT device includes: Based on the subscription information of the first IoT device, a first business requester is identified to manage the first IoT device. The contract information includes the association between the first IoT device and the first service requester. The method according to claim 15, characterized in that, Before determining the first service requester managing the first IoT device, the method further includes: The first IoT device is allowed to access the network through the cell corresponding to the third identifier. The method according to claim 15 or 17, characterized in that, The third identifier is the closed access group identifier. The method according to claim 15 or 17, characterized in that, The third identifier corresponds to the environmental Internet of Things (IoT) service. The method according to any one of claims 14 to 19, characterized in that, The first information also includes the location information of the first IoT device, and the method further includes: Send the location information of the first IoT device to the first service requester. The method according to any one of claims 14 to 20, characterized in that, The third identifier is the identifier used by the IoT device to access the cell, or the identifier of the first service requester, or the identifier of the first service requester's service, or a group identifier. A communication device, characterized in that, The communication device includes a module for performing the method according to any one of claims 1 to 13, or includes a module for performing the method according to any one of claims 14 to 21. A communication device, characterized in that, The communication device includes a processor configured to perform the method according to any one of claims 1 to 13, or configured to perform the method according to any one of claims 14 to 21. A communication system, characterized in that, It includes at least one of the following: means for performing the method according to any one of claims 1 to 13, and means for performing the method according to any one of claims 14 to 21. A computer-readable storage medium, characterized in that, The computer-readable storage medium is configured to store instructions that, when executed on a computer, cause the method according to any one of claims 1 to 13 to be performed, or cause the method according to any one of claims 14 to 21 to be performed. A computer program product containing instructions, characterized in that, When it is run on a computer, it causes the method according to any one of claims 1 to 13 to be performed, or causes the method according to any one of claims 14 to 21 to be performed.

Images