Paging method, and device and storage medium

By sending a first message containing multiple pieces of information, the problem of poor paging compatibility for environmental IoT devices is solved, enabling multiple devices to access simultaneously, reducing time overhead, and improving the compatibility of the paging process.

WO2026157535A1PCT designated stage Publication Date: 2026-07-30HONOR DEVICE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
HONOR DEVICE CO LTD
Filing Date
2025-11-28
Publication Date
2026-07-30

AI Technical Summary

Technical Problem

In existing technologies, the paging methods for environmental IoT devices have poor compatibility, which requires the Reader to page multiple Devices one by one, resulting in a large time overhead and failing to meet business needs.

Method used

A paging method is provided that triggers random access of multiple IoT devices in an environment by sending a first message containing various information, including random access type indication, device identification information, and service indication, thereby reducing the number of paging attempts and improving compatibility.

Benefits of technology

With a variety of first message formats, multiple devices can be triggered to access the system simultaneously, reducing time overhead, improving the compatibility of the paging process, and meeting the needs of environmental IoT services.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2025138574_30072026_PF_FP_ABST
    Figure CN2025138574_30072026_PF_FP_ABST
Patent Text Reader

Abstract

A paging method, and a device and a storage medium, which relate to the technical field of communications and the technical field of ambient Internet of Things. The method comprises: sending a first message, wherein the first message is used for triggering random access to one or more ambient IoT devices, or is used for triggering one or more ambient Internet of Things devices to respond to the first message, and the first message comprises at least one of the following: random access type indication information, ambient Internet of Things device identification information, service indication information, first identification information, reader identification information, and indication information indicating paging reception failure of an ambient Internet of Things device, wherein the first identification information is used for identifying the same service request. By means of using the method, a reader can implement paging for a plurality of ambient Internet of Things devices by means of one first message, thereby reducing time overheads. Moreover, the first message has a content-rich format, thereby improving the compatibility of the overall paging process, and thus better meeting requirements of ambient Internet of Things services.
Need to check novelty before this filing date? Find Prior Art

Description

A paging method, device and storage medium

[0001] This application claims priority to Chinese Patent Application No. 202510129645.3, filed on January 27, 2025, entitled "A paging method, device and storage medium", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of environmental Internet of Things (IoT) technology, and in particular to a paging method, device, and storage medium. Background Technology

[0003] Ambient Internet of Things (Ambient IoT), also known as passive IoT, is an IoT network consisting of devices with limited or no battery storage. These devices rely on harvesting energy from the environment to power themselves, such as solar energy, radio waves, heat, or pressure. Cellular-based passive IoT technology can leverage existing large-scale cellular infrastructure to reduce costs, while also utilizing many mature cellular technologies to improve coverage, such as interference management and mobility management.

[0004] Ambient IoT devices, also known as Devices, can be read by network devices or terminal devices. In existing technologies, when a Reader initiates a page to trigger random access to a Device, it only carries a unique Device identifier. This approach suffers from poor compatibility and cannot meet the needs of IoT services. For example, when a Reader needs to page multiple Devices, it must page each Device individually, resulting in significant time overhead. Summary of the Invention

[0005] To address the aforementioned issues, this application provides a paging method, device, and storage medium, which improves the overall compatibility of the paging process and better meets the needs of environmental IoT services.

[0006] In a first aspect, this application provides a paging method that can be applied to a reader / writer of an environmental IoT device. The method includes: sending a first message, which is used to trigger random access of one or more environmental IoT devices or to trigger one or more environmental IoT devices to execute a reply to the first message. The first message includes at least one of the following: random access type indication information, environmental IoT device identification information, service indication information, first identification information, reader / writer identification information, and indication information indicating that the environmental IoT device has failed to receive paging. The first identification information is used to identify a service request.

[0007] In this implementation, the first message sent by the reader can trigger random access from multiple environmental IoT devices or trigger responses from multiple environmental IoT devices to the first message. When the reader needs to page multiple environmental IoT devices, it does not need to page them individually; instead, it can page multiple environmental IoT devices through a single first message, reducing time overhead. Furthermore, the first message does not only carry the identifiers of the environmental IoT devices but can also carry other information, enabling multiple environmental IoT devices to receive more comprehensive and multi-layered instructions and efficiently access the network. Therefore, the first message provided by this solution has a rich format and content, improving the overall compatibility of the paging process and better meeting the needs of environmental IoT services.

[0008] In one possible implementation, the first message includes environmental IoT device identification information, which uses one or more device identification fields to indicate the device identification of one or more environmental IoT devices.

[0009] In one possible implementation, the first message includes indication information indicating whether the first message includes multiple environmental IoT devices. This indication information can be an indication field; when the indication field is a first type of content, it indicates that the message includes indication information for multiple environmental IoT devices; when the indication field is a second type of content, it indicates that the message does not include indication information for multiple environmental IoT devices.

[0010] In one possible implementation, the first message includes a first indication field and / or a first quantity field, wherein the first indication field is used to indicate whether the next device identifier exists, and the first quantity field is used to indicate the number of device identifiers of the environmental IoT devices.

[0011] In one possible implementation, when the first indication field has a first value, it indicates that the next device identifier exists; or, when the first indication field has a second value, it indicates that the next device identifier does not exist, or indicates that the next field of the device identifier field begins to exist, or indicates that the device identifier field ends. The first indication field may occupy one bit. When the first indication field has a first value, it indicates that the next device identifier exists; otherwise, it indicates that the next device identifier does not exist, or indicates that the next field of the device identifier field begins to exist, or indicates that the device identifier field ends.

[0012] In one possible implementation, the device identifier is in either a permanent identifier or a temporary identifier format.

[0013] In this implementation, the first message may also include a second indication field, which indicates the format of the corresponding device identifier. When the second indication field is a first value, the indicated format is a permanent identifier; when the second indication field is a second value, the indicated format is a temporary identifier.

[0014] In one possible implementation, the first message includes a third indication field, which indicates whether the first message includes environmental IoT device identification information. The third indication field may occupy one bit.

[0015] In one possible implementation, the environmental IoT device identification information includes a first device identification field and a second device identification field. The first device identification field is a first device identifier. The second device identification field is the number of environmental IoT devices; or, the second device identification field is the difference between the second device identifier and the first device identifier. The first device identifier is the device identifier of the first environmental IoT device in a plurality of consecutively identified environmental IoT devices, and the second device identifier is the device identifier of the last environmental IoT device in a plurality of consecutively identified environmental IoT devices; or, the second device identifier and the first device identifier are two consecutive device identifiers.

[0016] In this implementation, multiple device identifiers can be indicated using only two indicator fields, eliminating the need to fully carry the device identifier of each environmental IoT device and the number of bits occupied by the environmental IoT device identifier information.

[0017] In one possible implementation, the environmental IoT device identification information includes i device identification fields, where i is an integer greater than 1. The first device identification field is the first device identifier. The j-th device identification field is the difference between the j-th device identifier and the first device identifier, where j = 2, 3, ..., i; or, the j-th device identification field is the difference between the j-th device identifier and the (j-1)-th device identifier, where j = 2, 3, ..., i.

[0018] In this implementation, apart from the first device identifier field, subsequent device identifier fields do not need to carry all complete device identifiers directly in the first message, but only carry the relationship with the first or previous device identifier, which reduces the number of bits occupied and thus avoids resource waste.

[0019] In one possible implementation, one or more device identification fields are located in the last field of the Protocol Data Unit (PDU) or Service Data Unit (SDU) of the first message.

[0020] In one possible implementation, the preceding field of the device identification field is the first protocol data unit, or the information content of the preceding field of the device identification field is the first protocol data unit, and the first message includes a fourth indication field and / or a fifth indication field, wherein the fourth indication field is the length of the data packet of the first message, and the fifth indication field is the length of the data packet of the first protocol data unit.

[0021] In this implementation, the lengths of the fourth and fifth indication fields are associated with the number of device identifiers. The terminal device can determine the number of device identifiers recorded in the device identifier field based on the fourth and fifth indication fields and the format of the device identifier field.

[0022] In one possible implementation, the first message further includes a sixth indication field, which indicates the type of the first message. The sixth indication field can indicate different types of messages through different values, specifically including: paging messages, Msg2, R2D scheduling messages, etc.

[0023] In one possible implementation, the first message also includes a seventh indicator field and / or an eighth indicator field, wherein the seventh indicator field is used to indicate the length of the fourth indicator field and the eighth indicator field is used to indicate the length of the fifth indicator field.

[0024] In one possible implementation, the first message includes random access type indication information, which includes a resource indication field. When the resource indication field includes a third content, it indicates that the resource is a dedicated resource and the random access type is non-contention random access (CFRA). Alternatively, when the resource indication field includes a fourth content, it indicates that the resource is a shared resource and the random access type is contention random access (CBRA).

[0025] In one possible implementation, the first message includes a ninth indication field, which indicates the multiple access transmission method used by the environmental IoT device. That is, the first message also indicates the multiple access transmission method used by the environmental IoT device. The multiple access transmission method can be either Time Division Multiple Access (TDMA) or Frequency Division Multiple Access (FDMA).

[0026] In one possible implementation, the resource indication field specifically includes a tenth indication field and / or an eleventh indication field. The tenth indication field is used to indicate resources of the first multiple access transmission mode, and the eleventh indication field is used to indicate resources of the second multiple access transmission mode.

[0027] In one possible implementation, when the first message indicates that the IoT device in the environment is using the first multiple access transmission method, the eleventh indication field is either the first preset content or the eleventh indication field does not exist; or, when the first message indicates that the IoT device in the environment is using the second multiple access transmission method, the tenth indication field is either the first preset content or the tenth indication field does not exist.

[0028] In one possible implementation, the first message also indicates at least one of the following: modulation scheme, modulation parameters corresponding to the modulation scheme. The first message may indicate the above through the twelfth field.

[0029] In one possible implementation, the first identification information may or may not exist, or the first identification information may be a reserved value, or the first identification information may be preset content.

[0030] In one possible implementation, the first message includes a thirteenth field used to indicate whether the first identification information exists, or whether the first identification information is a reserved value, or whether the first identification information is preset content.

[0031] In one possible implementation, the thirteenth indication field includes environmental IoT device identification information, or the thirteenth indication field indicates that the first identification information is a first value, or the thirteenth indication field indicates that the message type of the first message is not a paging message. The preset content includes at least one of: resource indication information, service indication information, and random access type indication information.

[0032] In one possible implementation, the first message includes environmental IoT device identification information and first identification information. The fields of the first identification information are preset to a fifth content, which indicates that the fields of the first identification information should be ignored; alternatively, the first message includes a fourteenth indication field, which is a sixth content, indicating that the fields of the first identification information should be ignored.

[0033] In one possible implementation, the first message includes first identification information, which is used to indicate a first identifier, and the type of the first identifier includes a first type identifier and / or a second type identifier.

[0034] In one possible implementation, the first type of identifier is assigned by the reader / writer, and the second type of identifier is assigned by the core network.

[0035] In one possible implementation, the first message is also used to indicate the type of the first identifier. The first message may include an identifier type indicator field, which is used to indicate the type of the first identifier.

[0036] In one possible implementation, when the type of the first identifier is a first type identifier, the first message includes reader / writer identifier information.

[0037] In one possible implementation, the first message includes reader identification information, which is used to determine whether the type of the first identifier is a first type identifier.

[0038] Secondly, this application also provides a paging method, which can be applied to environmental IoT devices. The method includes the following steps: receiving a first message, the first message being used to trigger random access of one or more environmental IoT devices or to trigger one or more environmental IoT devices to execute a reply to the first message, the first message including at least one of the following: random access type indication information, environmental IoT device identification information, service indication information, first identification information, reader / writer identification information, and indication information indicating that the environmental IoT device has failed to receive paging, the first identification information being used to identify a service request; and determining whether to respond to the first message based on the first message.

[0039] Using this implementation, when an environmental IoT device receives a page from a reader, the first message does not only carry the device's identifier but can also carry other information. This allows the environmental IoT device to receive more comprehensive and multi-layered instructions and efficiently access the network. Therefore, the format and content of the first message provided by this solution are rich, improving the compatibility of the overall paging process and better meeting the needs of environmental IoT services.

[0040] In one possible implementation, the first message includes environmental IoT device identification information, which uses one or more device identification fields to indicate the device identification of one or more environmental IoT devices.

[0041] In one possible implementation, the first message includes indication information indicating whether the first message includes multiple environmental IoT devices. This indication information can be an indication field; when the indication field is a first type of content, it indicates that the message includes indication information for multiple environmental IoT devices; when the indication field is a second type of content, it indicates that the message does not include indication information for multiple environmental IoT devices.

[0042] In one possible implementation, the first message includes a first indication field and / or a first quantity field, wherein the first indication field is used to indicate whether the next device identifier exists, and the first quantity field is used to indicate the number of device identifiers of the environmental IoT devices.

[0043] In one possible implementation, when the first indication field has a first value, it indicates that the next device identifier exists; or, when the first indication field has a second value, it indicates that the next device identifier does not exist, or indicates that the next field of the device identifier field begins to exist, or indicates that the device identifier field ends. The first indication field may occupy one bit. When the first indication field has a first value, it indicates that the next device identifier exists; otherwise, it indicates that the next device identifier does not exist, or indicates that the next field of the device identifier field begins to exist, or indicates that the device identifier field ends.

[0044] In one possible implementation, the device identifier is in either a permanent identifier or a temporary identifier format.

[0045] In this implementation, the first message may also include a second indication field, which indicates the format of the corresponding device identifier. When the second indication field is a first value, the indicated format is a permanent identifier; when the second indication field is a second value, the indicated format is a temporary identifier.

[0046] In one possible implementation, the first message includes a third indication field, which indicates whether the first message includes environmental IoT device identification information. The third indication field may occupy one bit.

[0047] In one possible implementation, the environmental IoT device identification information includes a first device identification field and a second device identification field. The first device identification field is a first device identifier. The second device identification field is the number of environmental IoT devices; or, the second device identification field is the difference between the second device identifier and the first device identifier. The first device identifier is the device identifier of the first environmental IoT device in a plurality of consecutively identified environmental IoT devices, and the second device identifier is the device identifier of the last environmental IoT device in a plurality of consecutively identified environmental IoT devices; or, the second device identifier and the first device identifier are two consecutive device identifiers.

[0048] In this implementation, multiple device identifiers can be indicated using only two indicator fields, eliminating the need to fully carry the device identifier of each environmental IoT device and the number of bits occupied by the environmental IoT device identifier information.

[0049] In one possible implementation, the environmental IoT device identification information includes i device identification fields, where i is an integer greater than 1. The first device identification field is the first device identifier. The j-th device identification field is the difference between the j-th device identifier and the first device identifier, where j = 2, 3, ..., i; or, the j-th device identification field is the difference between the j-th device identifier and the (j-1)-th device identifier, where j = 2, 3, ..., i.

[0050] In this implementation, apart from the first device identifier field, subsequent device identifier fields do not need to carry all complete device identifiers directly in the first message, but only carry the relationship with the first or previous device identifier, which reduces the number of bits occupied and thus avoids resource waste.

[0051] In one possible implementation, one or more device identification fields are located in the last field of the Protocol Data Unit (PDU) or Service Data Unit (SDU) of the first message.

[0052] In one possible implementation, the preceding field of the device identification field is the first protocol data unit, or the information content of the preceding field of the device identification field is the first protocol data unit, and the first message includes a fourth indication field and / or a fifth indication field, wherein the fourth indication field is the length of the data packet of the first message, and the fifth indication field is the length of the data packet of the first protocol data unit.

[0053] In this implementation, the lengths of the fourth and fifth indication fields are associated with the number of device identifiers. The terminal device can determine the number of device identifiers recorded in the device identifier field based on the fourth and fifth indication fields and the format of the device identifier field.

[0054] In one possible implementation, the first message further includes a sixth indication field, which indicates the type of the first message. The sixth indication field can indicate different types of messages through different values, specifically including: paging messages, Msg2, R2D scheduling messages, etc.

[0055] In one possible implementation, the first message also includes a seventh indicator field and / or an eighth indicator field, wherein the seventh indicator field is used to indicate the length of the fourth indicator field and the eighth indicator field is used to indicate the length of the fifth indicator field.

[0056] In one possible implementation, the first message includes random access type indication information, which includes a resource indication field. When the resource indication field includes a third content, it indicates that the resource is a dedicated resource and the random access type is non-contention random access (CFRA). Alternatively, when the resource indication field includes a fourth content, it indicates that the resource is a shared resource and the random access type is contention random access (CBRA).

[0057] In one possible implementation, the first message includes a ninth indication field, which indicates the multiple access transmission method used by the environmental IoT device. That is, the first message also indicates the multiple access transmission method used by the environmental IoT device. The multiple access transmission method can be either Time Division Multiple Access (TDMA) or Frequency Division Multiple Access (FDMA).

[0058] In one possible implementation, the resource indication field specifically includes a tenth indication field and / or an eleventh indication field. The tenth indication field is used to indicate resources of the first multiple access transmission mode, and the eleventh indication field is used to indicate resources of the second multiple access transmission mode.

[0059] In one possible implementation, when the first message indicates that the IoT device in the environment is using the first multiple access transmission method, the eleventh indication field is either the first preset content or the eleventh indication field does not exist; or, when the first message indicates that the IoT device in the environment is using the second multiple access transmission method, the tenth indication field is either the first preset content or the tenth indication field does not exist.

[0060] In one possible implementation, the first message also indicates at least one of the following: modulation scheme, modulation parameters corresponding to the modulation scheme. The first message may indicate the above through the twelfth field.

[0061] In one possible implementation, the first identification information may or may not exist, or the first identification information may be a reserved value, or the first identification information may be preset content.

[0062] In one possible implementation, the first message includes a thirteenth field used to indicate whether the first identification information exists, or whether the first identification information is a reserved value, or whether the first identification information is preset content.

[0063] In one possible implementation, the thirteenth indication field includes environmental IoT device identification information, or the thirteenth indication field indicates that the first identification information is a first value, or the thirteenth indication field indicates that the message type of the first message is not a paging message. The preset content includes at least one of: resource indication information, service indication information, and random access type indication information.

[0064] In one possible implementation, the first message includes environmental IoT device identification information and first identification information. The fields of the first identification information are preset to a fifth content, which indicates that the fields of the first identification information should be ignored; alternatively, the first message includes a fourteenth indication field, which is a sixth content, indicating that the fields of the first identification information should be ignored.

[0065] In one possible implementation, the first message includes first identification information, which is used to indicate a first identifier, and the type of the first identifier includes a first type identifier and / or a second type identifier.

[0066] In one possible implementation, the first type of identifier is assigned by the reader / writer, and the second type of identifier is assigned by the core network.

[0067] In one possible implementation, the first message is also used to indicate the type of the first identifier. The first message may include an identifier type indicator field, which is used to indicate the type of the first identifier.

[0068] In one possible implementation, when the type of the first identifier is a first type identifier, the first message includes reader / writer identifier information.

[0069] In one possible implementation, the first message includes reader identification information, which is used to determine whether the type of the first identifier is a first type identifier.

[0070] In one possible implementation, determining whether to respond to the first message based on the first message includes at least one of the following: responding to the first message when no first message including the first identification information has been received; responding to the first message when a first message including the first identification information has been received and a response to the first message including the first identification information or a random access procedure corresponding to the first message including the first identification information has not been completed; not responding to the first message when a first message including the first identification information has been received and a response to the first message including the first identification information or a random access procedure corresponding to the first message including the first identification information has been completed; and responding to the first message when the received first message includes a device identifier.

[0071] In one possible implementation, the first message includes reader identification information. Determining whether to respond to the first message based on the first message includes at least one of the following: when the first identifier is a first type identifier and no first message including the first identifier information of a reader or writer identified by reader identification information has been received, respond to the first message; when the first identifier is a first type identifier and a first message including the first identifier information of a reader or writer identified by reader identification information has been received, and a response to the first message including the first identifier information of the reader or writer has not been completed or a random access procedure corresponding to the first message including the first identifier information has not been completed, respond to the first message; when the first identifier is a first type identifier and a first message including the first identifier information of a reader or writer identified by reader identification information has been received, and a response to the first message including the first identifier information of the reader or writer has been completed or a random access procedure corresponding to the first message including the first identifier information has been completed, do not respond to the first message; when the first identifier is a first type identifier and the first message includes a device identifier, respond to the first message.

[0072] In one possible implementation, it is determined that a first message including the first identification information has not been received based on one or more of the following conditions: the identification content of the first identification information in the previously received first message is different from the identification content of the first identification information in the first message; the identification content of the stored first identification information is different from the identification content of the first identification information in the first message; the first identification information in the previously received first message does not exist or is a reserved value; the identification content of the first identification information in the first message is received for the first time. It is determined that a first message including the first identification information has been received based on one or more of the following conditions: the identification content of the first identification information in the previously received first message is the same as the identification content of the first identification information in the first message; the identification content of the stored first identification information is the same as the identification content of the first identification information in the first message.

[0073] In one possible implementation, it is determined that the response to the first message including the first identification information or the random access procedure corresponding to the first message including the first identification information has not been completed, based on one or more of the following conditions: no response to the first message including the first identification information; failure to respond to the first message including the first identification information; no receipt of the second random access message during the random access procedure; receipt of a failure message during the random access procedure; no response or incomplete random access procedure for the status information corresponding to the identifier content of the stored first identification information. It is then determined that the response to the first message including the first identification information or the random access procedure corresponding to the first message including the first identification information has been completed, based on one or more of the following conditions: successful response to the first message including the first identification information; receipt of the second random access message during the random access procedure; receipt of a success message during the random access procedure; sending the first or third message during the random access procedure; and, after sending the third message, determining the start of the next random access opportunity. The status information corresponding to the identifier content of the stored first identification information has been responded to or the random access procedure has been completed.

[0074] In one possible implementation, it is determined that the response to the first message including the first identification information of the reader / writer has not been completed or the random access procedure corresponding to the first message including the first identification information has not been completed based on one or more of the following conditions: for the reader / writer, no response was made to the first message including the first identification information; for the reader / writer, the response to the first message including the first identification information failed; for the reader / writer, the second message of random access was not received during the random access procedure; for the reader / writer, a failure message was received during the random access procedure; for the reader / writer, the status information corresponding to the identifier content of the stored first identification information was not responded to or the random access procedure was not completed. It is determined that the response to the first message including the first identification information of the reader / writer has been completed or the random access procedure corresponding to the first message including the first identification information has not been completed based on one or more of the following conditions: for the reader / writer, the response to the first message including the first identification information was successful; for the reader / writer, the second message of random access was received during the random access procedure; for the reader / writer, a success message was received during the random access procedure; for the reader / writer, the first message or the third message during the random access procedure was sent; for the reader / writer, after sending the third message, the random access timing is determined to begin. For the reader / writer, the status information corresponding to the identifier content of the stored first identifier information has been responded to or the random access process has been completed.

[0075] Thirdly, this application also provides a reader / writer device, the network device including a processor and a memory. The processor is coupled to the memory, the memory is used to store instructions, and the processor is used to execute the computer program or instructions stored in the memory to implement the method as described in the first aspect and any implementation thereof.

[0076] Fourthly, this application also provides an electronic device including a processor and a memory. The processor is coupled to the memory, the memory is used to store instructions, and the processor is used to execute the computer program or instructions stored in the memory to implement the method as described in the second aspect and any implementation thereof above.

[0077] Fifthly, this application also provides a computer storage medium for storing a computer program, which, when executed, implements the method described in the first aspect and any implementation thereof, or implements the method described in the second aspect and any implementation thereof. Attached Figure Description

[0078] Figure 1 is a schematic diagram of the architecture of a communication system provided in this application;

[0079] Figure 2 is a schematic diagram of the architecture of another communication system provided in this application;

[0080] Figure 3 is a flowchart of a method for a paging environment Internet of Things device provided in this application;

[0081] Figure 4 is a flowchart of a paging method provided in an embodiment of this application;

[0082] Figure 5 is a schematic diagram of the format of the first message provided in an embodiment of this application;

[0083] Figure 6 is a schematic diagram of the format of the first message provided in the embodiment of this application;

[0084] Figure 7 is a schematic diagram of the format of the first message provided in the embodiments of this application;

[0085] Figure 8 is a schematic diagram of the format of the first message provided in the embodiments of this application;

[0086] Figure 9 is a schematic diagram of the format of the first message provided in the embodiments of this application;

[0087] Figure 10 is a schematic diagram of the sub-header information of the data packet of the first message provided in an embodiment of this application;

[0088] Figure 11 is a schematic diagram of the sub-header information of the data packet of the first message provided in the embodiment of this application;

[0089] Figure 12 is a schematic diagram of the format of the first message provided in the embodiment of this application;

[0090] Figure 13 is a schematic diagram of the format of the first message provided in the embodiment of this application;

[0091] Figure 14 is a schematic diagram of the random access timing provided in an embodiment of this application;

[0092] Figure 15 is a flowchart of another paging method provided in an embodiment of this application;

[0093] Figure 16 is a flowchart of another paging method provided in an embodiment of this application;

[0094] Figure 17 is a schematic diagram of a network device provided in an embodiment of this application;

[0095] Figure 18 is a schematic diagram of an Internet of Things (IoT) device provided in an embodiment of this application. Detailed Implementation

[0096] To enable those skilled in the art to better understand the solution of this application, the application scenario of the technical solution of this application will be described first below.

[0097] With the development of Internet of Things (IoT) technology, a consensus has been reached on classifying IoT nodes into three different speed levels: high-speed IoT, medium-speed IoT, and low-speed IoT. High-speed IoT is primarily supported by technologies such as 5G (Enhanced Mobile Broadband), 4G Category 4+, and Wi-Fi 6. Medium-speed IoT is mainly supported by technologies such as 4G Cat.1, 3G, and 2G. Low-speed IoT is primarily supported by technologies such as Narrowband Internet of Things (NB-IoT), Long Range Wide Area Network (LoRaWAN), and Bluetooth Low Energy (BLE). Different speeds also correspond to different power consumption levels, forming three distinct scenarios and addressing three different levels of IoT connection numbers.

[0098] Low-speed IoT standards such as NB-IoT, LoRaWAN, and BLE can support tens of billions of connections, while medium-speed and high-speed IoT standards can only achieve a much smaller connection scale. Based on these three types of IoT scenarios, Ambient IoT, also known as passive IoT, will become the main source of hundreds of billions of IoT connections.

[0099] The main application scenarios of Ambient IoT include, but are not limited to, industrial sensor networks, logistics and warehousing, smart wearable devices, healthcare, smart homes, and other fields, which will be explained in detail below.

[0100] Industrial sensor networks: Industrial sensor networks are mainly used in industrial production processes, such as temperature and humidity monitoring, vibration monitoring, and production line monitoring, thereby achieving industrial automation and intelligent management. Taking railway track measurement as an example, by deploying zero-power sensing devices under the tracks, rail pressure, temperature, and other information can be monitored and collected. Furthermore, these devices can also be deployed in extreme environments where batteries cannot sustain long-term operation, such as high and low temperatures, moving or rotating parts, high vibration conditions, and high humidity.

[0101] Logistics and Warehousing: With the continued growth of the logistics industry, enterprises are facing increasing pressure on warehousing and labor costs. Digital management of logistics parcels can not only further improve the efficiency of logistics and warehousing management but also save significant labor costs. Zero-power communication technology involves attaching communication terminal tags to the surface of parcels or goods packaging for acquiring logistics information and managing the entire logistics process, making warehousing operations simpler and more efficient. These communication terminal tags can also be used for environmental IoT devices.

[0102] Smart wearable devices: Following mobile phones, smart wearable devices are among the personal consumer terminals with the greatest potential for large-scale application. Currently, various wearable devices have achieved wireless connectivity. Depending on the functional positioning of different products, they can realize multiple application scenarios such as health monitoring, sports monitoring, motion sensing, and mobile positioning. The goal of zero-power communication technology is to ultimately break free from battery limitations, achieving longer battery life, more convenient energy security, and a better user experience.

[0103] Healthcare: Portable medical devices can meet consumers' home health service needs, but due to the special nature of medical monitoring equipment (especially implantable devices), issues such as battery life and power supply portability greatly limit the expansion of their application scenarios. Zero-power IoT technology can achieve extremely low power consumption; at the same time, eliminating the need for batteries allows for smaller size, facilitates flexible folding, and eliminates concerns about liquid immersion, thus aiding in real-time monitoring of medical device data and efficient digital management of health status.

[0104] Smart Home: The application of zero-power communication technology in the field of smart homes can eliminate complex wiring, enabling each terminal to be controlled independently and achieving long-lasting online operation without human power intervention.

[0105] Traditional radio frequency identification (RFID) is a passive Internet of Things (IoT) technology that uses radio frequency for non-contact, two-way data communication. It reads and writes data to recording media (electronic tags or RFID cards) to identify targets and exchange data. However, this technology lacks interference management, does not support mobility, and has a coverage distance of only about 10 meters. Therefore, it is difficult to support the future demand of hundreds of billions of users. Consequently, the 3rd Generation Partnership Project (3GPP) is discussing the development of passive IoT technologies based on cellular communication. On the one hand, it can leverage existing large-scale cellular infrastructure to reduce costs; on the other hand, it can utilize many mature cellular communication technologies to improve the coverage of passive IoT, such as interference management and mobility management.

[0106] The architecture of the communication system in the embodiments of this application will be introduced first below.

[0107] See Figure 1, which is a schematic diagram of the architecture of a communication system provided in this application.

[0108] The communication system includes network device 201, Ambient IoT device 204, and intermediate node 202.

[0109] Intermediate node 202 can be a user equipment (UE), an integrated access and backhaul (IAB) node, a repeater, etc. Intermediate node 202 communicates with network device 201 via the Uu interface. Here, uppercase U represents the user-to-network interface (UNI), and lowercase u represents universal.

[0110] The intermediate node 202 in Figure 1 can also be called a Reader, meaning that in this architecture, the intermediate node 202 can act as a reader / writer, reader / writer terminal, reader, or reader terminal, etc. The Ambient IoT device 204 can also be called a Device.

[0111] See Figure 2, which is a schematic diagram of the architecture of another communication system provided in this application.

[0112] The communication system includes a network device 201 and an Ambient IoT device 204. The Ambient IoT device 204 can establish communication with the network device 201, which can be located indoors.

[0113] The network device 201 in Figure 2 can also be called a Reader, meaning that the network device 201 can act as a reader / writer, or a reader / writer terminal. The Ambient IoT device 204 can also be called a Device.

[0114] The resource allocation method provided in this application can be applied to cellular communication systems related to the 3rd generation partnership project (3GPP), such as 4th generation (4G) communication systems, such as Long Term Evolution (LTE) communication systems, and can also be applied to 5th generation (5G) communication systems. th 5G communication systems, such as 5G New Radio (NR) communication systems, or various future communication systems, such as 6th generation (6G) communication systems.

[0115] The method provided in this application can also be applied to Bluetooth systems, Wi-Fi systems, LoRa systems, or vehicle-to-everything (V2X) systems, supporting communication systems that integrate multiple wireless technologies, and device-to-device (D2D) systems. The method provided in this application can also be applied to satellite communication systems. The satellite communication system can be integrated with the aforementioned communication systems. The wireless communication systems involved in this application also include, but are not limited to: narrowband internet of things (NB-IoT), global system for mobile communications (GSM), enhanced data rate for GSM evolution (EDGE), wideband code division multiple access (WCDMA), code division multiple access 2000 (CDMA2000), or time division-synchronization code division multiple access (TD-SCDMA).

[0116] The aforementioned network device 201 can be an access network device for a 3GPP-related cellular system, such as a 4G mobile communication system or a 5G mobile communication system. The network device can also be an access network device in an open RAN (O-RAN or ORAN) or a cloud radio access network (CRAN). Alternatively, the network device can be an access network device in a communication system resulting from the integration of two or more of the above communication systems.

[0117] Network equipment 201 includes, but is not limited to: evolved Node B (eNB), radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved NodeB, or home Node eB, HNB), base band unit (BBU), access point (AP) in a wireless fidelity (WIFI) system, macro base station, micro base station, wireless relay node, donor node, radio controller in CR AN scenarios, wireless backhaul node, transmission point (TP), or transmission and receiving point (TRP). Network equipment can also be access network equipment in a 5G mobile communication system. For example, next-generation Node B (gNB) in a new radio (NR) system, TRP, TP, or one or more antenna panels (including multiple antenna panels) of a base station in a 5G mobile communication system. Alternatively, network devices can also be network nodes constituting a gNB or transmission point. Examples include centralized units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs). CUs and DUs can be separate entities or included in the same network element, such as a BBU. RUs can be included in radio equipment or radio units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs). Alternatively, network devices can also be servers, wearable devices, vehicles, or in-vehicle equipment. For example, in V2X technology, network devices can be roadside units (RSUs).

[0118] It should be noted that the network device can be the device or apparatus shown above, or a component (e.g., a chip), module, or unit in the device or apparatus shown above; this application does not limit the specifics.

[0119] Intermediate node 202 can be user equipment (UE), mobile station (MS), mobile terminal (MT), etc. In some scenarios, intermediate node 202 can be a device that provides voice or data connectivity to the user. Specifically, it includes devices that provide voice connectivity to the user, devices that provide data connectivity to the user, or devices that provide both voice and data connectivity to the user. For example, it can include a handheld device with wireless connectivity or a processing device connected to a wireless modem. Intermediate node 202 can also be a terminal device that can communicate with the core network via a radio access network (RAN), exchanging voice or data with the RAN, or interacting with the RAN for both voice and data. Currently, terminal devices can include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices (such as smartwatches, smart bracelets, pedometers, etc.), in-vehicle devices (such as cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.), virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, smart home devices (such as refrigerators, televisions, air conditioners, electricity meters, etc.), intelligent robots, workshop equipment, wireless terminals in autonomous driving, wireless terminals in remote surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, or wireless terminals in smart homes, and flying equipment (such as intelligent robots, hot air balloons, drones, airplanes), etc. Terminal devices can also be other devices with terminal functions; for example, a terminal device can also be a device that performs terminal functions in D2D communication.Terminal equipment can also include vehicle-to-everything (V2X) terminal equipment, machine-to-machine / machine-type communications (M2M / MTC) terminal equipment, Internet of Things (IoT) terminal equipment, light UE, reduced capability UE (REDCAP UE), subscriber unit, subscriber station, mobile station, remote station, access point (AP), remote terminal, access terminal, user terminal, user agent, or user device, and drone equipment. For example, it can include mobile phones (or "cellular" phones), computers with mobile terminal devices, portable, pocket-sized, handheld, and computer-embedded mobile devices, etc. Examples include personal communication service (PCS) telephones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, and personal digital assistants (PDAs). It also includes limited devices, such as devices with low power consumption, limited storage capacity, or limited computing power. Examples include information sensing devices such as barcode scanners, radio frequency identification (RFID), sensors, global positioning systems (GPS), and laser scanners. In this application, terminal devices with wireless transceiver capabilities and chips that can be installed in the aforementioned terminal devices are collectively referred to as terminal devices.

[0120] It should be noted that the intermediate node 202 may be a device or apparatus with a chip, or a device or apparatus with integrated circuitry, or a chip, module or control unit in the device or apparatus shown above. This application does not limit the specific details.

[0121] See Figure 3, which is a flowchart of a method for paging environment Internet of Things device provided in this application.

[0122] For the topology shown in Figure 2, the Reader is generally a base station, and the A-IoT controller is a core network element. Specifically, it can be an Access and Mobility Management Function (AMF) network element or a User Plane Function (UPF) network element, or a separately set network element applied to environmental IoT services.

[0123] The application function (AF) network elements in Figure 3 involve application layer services. The AF network element instructs the A-IoT controller via S1 whether the specific service is inventory or command (i.e., DL command).

[0124] The inventory service instructs the device to report device information or service data. The command service issues commands to the device, which can be control commands or service operation commands.

[0125] The A-IoT controller indicates specific services to the gNB via S2, enabling the gNB to trigger Radio Resource Control (RRC) reconfiguration via S3. The Reader sends an initial message to the Device, which also serves as a paging message. Upon receiving the paging message from the Reader, the Device triggers a 2-step or 3-step random access procedure or a Contention-Free Random Access (CFRA) procedure. The paging message is used to trigger inventory checks or command transmission.

[0126] For the topology shown in Figure 1, the Reader is generally a UE, and the UE needs to communicate with the base station and the AIoT controller.

[0127] In existing technologies, the paging message only indicates a single Device ID in the overall paging process design. This approach suffers from poor compatibility and cannot meet the needs of IoT applications. For example, when a reader needs to page multiple devices, it requires paging each device individually, resulting in significant time overhead. Furthermore, when a reader needs to page multiple devices, it cannot provide more specific information, hindering efficient access for multiple devices.

[0128] To address the aforementioned technical issues, this application provides a paging method, device, and storage medium. The first message sent by the reader / writer can trigger random access from multiple environmental IoT devices or trigger multiple environmental IoT devices to respond to the first message. Furthermore, the first message does not only carry the identifiers of the environmental IoT devices but can also carry other information, enabling multiple environmental IoT devices to receive more comprehensive and multi-layered instructions and efficiently access the system. Therefore, this solution improves the overall compatibility of the paging process and better meets the needs of environmental IoT services. The implementation of this application's technical solution is described in detail below with reference to the accompanying drawings.

[0129] Referring to Figure 4, this figure is a flowchart of a paging method provided in an embodiment of this application.

[0130] The method includes the following steps:

[0131] S10: The Reader sends the first message to the Device.

[0132] S11: The Device determines whether to respond to the first message based on the first message.

[0133] Responding to the first message includes initiating random access or sending the second message.

[0134] The first message in this embodiment, also known as a Paging message, is used to trigger random access from one or more Devices or to trigger a response from one or more Devices. That is, in this solution, the Reader can simultaneously send the first message to multiple Devices to improve access efficiency in multi-Device scenarios. The second message is a response to the first message.

[0135] The first message in this application embodiment may include one or more of the following: random access type indication information, environmental IoT device identification information, service indication information, first identification information, reader / writer identification information, and indication information indicating that the environmental IoT device failed to receive paging. These will be described separately below.

[0136] Random Access (RA) type indication information is used to indicate the type of random access used by the device. In one possible implementation, the type of random access may include Contention-Free Random Access (CFRA) or Contention-Based Random Access (CBRA). It may also include two-step or three-step random access in the case of CBRA.

[0137] Random Access Type Indication (RA) information can directly indicate the RA type, for example, through an indicator field. In one example, a value of 1 in the indicator field indicates that the RA type is CFRA, and a value of 0 indicates that the RA type is CBRA. The 1 and 0 in the above example can be interchanged or replaced with other binary numbers.

[0138] Furthermore, the random access type can be indicated implicitly, or the random access type indication information can be used to indicate the RA type along with the resource information indication field. In one example, if the indication field indicates that the resource type is a private resource, the RA type is also indicated as CFRA; if the indication field indicates that the resource type is a shared resource, the RA type is also indicated as CBRA. This indication field can be resource information for the device to calculate the time slot (random access opportunity), such as the Q value, where the device accesses a time slot (random access opportunity) less than or equal to 2. Q -1 time slot. For example, if the number of resources indicated by the indicator field is greater than or equal to the number of devices, then the type of resource is a dedicated resource; if the number of resources indicated by the indicator field is less than the number of devices, then the type of resource is a shared resource.

[0139] The environmental IoT device identification information is used to indicate the Device ID, that is, to indicate the specific environmental IoT device that needs to receive a paging message or ignore it. When an environmental IoT device determines that its own Device ID matches the Device ID indicated by the environmental IoT device identification information, it can determine that it is the recipient of the first message paging, or that it needs to ignore the Reader paging message that sent the first message. Typically, the Device ID indicated by the environmental IoT device identification information in the first message is the identifier of the device being paging by the Reader, requiring these devices to initiate random access or respond to the first message.

[0140] Service indication information is related to specific services. For example, service indication information can indicate specific DL command services, which may include read, write, configuration, temporary disable, and permanent disable; or service indication information can be used to indicate whether there are subsequent services to be sent, such as whether a DL command will be sent.

[0141] The first identification information is used to identify the service request. Specifically, the first identification information is used to identify whether it is a paging message corresponding to the same service request. The service request is initiated by the AF (application function) side, which sends the service to the AIoTF (Ambient IoT (Internet of Things) function). The AIoTF then sends the service request to the base station. In topology 1, the base station, acting as a reader, sends paging messages for the service request; in topology 2, the base station forwards the service request to the reader (e.g., the UE). For the same reader, the first identification information in the paging messages corresponding to different service requests is generally different. If the first identification information in two paging messages sent by the same reader is the same, it is considered a retransmission of the paging message corresponding to the service request. In the embodiments of this application and the following descriptions, the first identifier indicated by the first identification information can be called a Task ID, and the first identification information can also be a paging ID, a transaction ID, or a correlation identifier related to the responses of the request.

[0142] The reader identification information is used to indicate the reader ID, which enables the device receiving the first message to identify the reader that sent the first message.

[0143] The indication message of paging failure received by the environmental IoT device is used to identify that the first message was not sent by the Reader for the first time. The Reader has previously sent the first message to page the target Device, but the paging failed. Therefore, the Reader can carry the indication message of paging failure received by the Device in the first message sent again.

[0144] In summary, the solution provided in this application allows the reader to send a first message that can trigger random access of multiple environmental IoT devices or trigger multiple environmental IoT devices to respond to the first message. When the reader needs to page multiple environmental IoT devices, it does not need to page them one by one; instead, it can page multiple environmental IoT devices through a single first message, reducing time overhead. Furthermore, the first message can carry various other information, enabling multiple environmental IoT devices to receive more comprehensive and multi-layered instructions and efficiently access the network. Therefore, the format and content of the first message provided by this solution are rich, improving the compatibility of the overall paging process. In other words, this first message, as a paging message, can better accommodate the evolution of subsequent environmental IoT services and better meet the needs of environmental IoT services.

[0145] The following explanation will focus on the specific implementation of the first message.

[0146] Referring to Figure 5, this figure is a schematic diagram of the format of the first message provided in the embodiment of this application.

[0147] The illustration uses an example where each line of the first message contains 8 bits. The first message includes environmental IoT device identification information. This information uses one or more device identification fields to indicate the device ID of one or more environmental IoT devices. The device identification field can also be group device identification information, which can associate multiple devices, such as filter information. For ease of explanation, this application and the following embodiments use an example where the environmental IoT device identification information uses multiple device identification fields to indicate the device ID of multiple environmental IoT devices.

[0148] A Device ID can be indicated by x rows of Device ID fields. This application embodiment does not impose specific limitations, and the specific value of x is related to the length of the Device ID. As shown in Figure 5, when x is 1, the length of the Device ID is 6 bits; when x is 2, the length of the Device ID is 14 bits; and when x is 1, the length of the Device ID is 22 bits.

[0149] After receiving the first message, the device can read the Device ID of the corresponding length according to the protocol.

[0150] The first message may include a first indication field and / or a first quantity field. The first indication field indicates whether the next device identifier exists, and the first quantity field indicates the number of device identifiers for the environmental IoT devices.

[0151] Specifically, the first indication field is represented by N in Figure 5. When the first indication field is a first content, it indicates that the next device identifier exists. When the first indication field is a second content, it indicates that the next device identifier does not exist; or it indicates that the next field of the device identifier field begins to exist, that is, the device identifier field ends. In this embodiment, the next field of the device identifier field is not specifically limited. For example, it can be a Service Data Unit (SDU) field, or a Protocol Data Unit (PDU) field as shown in Figure 5; or, the first indication field can also directly indicate the end of the device identifier field. Specifically, the first indication field can correspond to a device identifier and indicate whether the next device identifier of that device identifier exists. When the first indication field indicates that the next device identifier of that device identifier does not exist, then that device identifier is the last device identifier.

[0152] This application does not specifically limit the first and second contents in its embodiments. In one possible implementation, when the first indicator field N occupies 1 bit as shown in Figure 5, the first content can be 1 and the second content can be 0; or, the first content can be 0 and the second content can be 1. When the first indicator field N occupies more bits, the first and second contents can be other binary numbers, which will not be elaborated here.

[0153] Referring to Figure 6, this figure is a schematic diagram of the format of the first message provided in the embodiment of this application.

[0154] If the first message uses the first quantity field E to indicate the number of Device IDs, then the first quantity field E can be placed before the device identification field. In this case, the device first reads the first quantity field to determine the number of Device IDs, and then reads the Device IDs one by one. In the example of Figure 6, since the number of Device IDs is known, the first indicator field N can be omitted in the first message. It is understandable that the first indicator field N can also be set in the first message.

[0155] The F field is used to indicate the length of the first quantity field E. When the F field is 1, the length of E is 7 bits, and the number of Device IDs ranges from 0 to 128. The format of the first message is shown in part 6-(A) of Figure 6. When the F field is 0, the length of E is 5 bits, and the number of Device IDs ranges from 0 to 32. The format of the first message is shown in part 6-(B) of Figure 6. The R field is a reserved field, which is used to implement the alignment function of the format.

[0156] Referring also to Figures 5 and 6, the first message may also include a second indicator field DT, which indicates the format of the corresponding Device ID. The format of the Device ID is either a permanent identifier or a temporary identifier.

[0157] The permanent identifier remains fixed for a single device; the temporary identifier can be assigned to the device by the core network, thus protecting user privacy.

[0158] In one possible implementation, when the second indicator field DT occupies 1 bit as shown in Figure 5 or Figure 6, the first value of DT indicates that the Device ID is in permanent format, and the second value indicates that the Device ID is in temporary format. The first value can be 1, and the second value can be 0; or, the first value can be 0, and the second value can be 1. When the second indicator field DT occupies more bits, the first and second values ​​can be other binary numbers, which will not be elaborated here.

[0159] The Resource Info field in Figures 5 and 6 indicates resource-related information, such as resource type, multiple access mode used by the device, modulation scheme, and modulation parameters. The 3-bit Resource Info field in Figures 5 and 6 is merely an example; it's understood that the Resource Info field can occupy more bits to indicate sufficient information.

[0160] When the Resource Info field indicates the resource type, it can implicitly indicate the RA type. For example, if the resource type is a private resource, the RA type is also indicated as CFRA; if the resource type is a shared resource, the RA type is also indicated as CBRA.

[0161] In Figures 5 and 6, the RA field is used to indicate the RA type. When the RA field occupies 1 bit, a value of the first content indicates that the RA type is type 1, and a value of the second content indicates that the RA type is type 2. The first content can be 1, and the second content can be 0; or the first content can be 0, and the second content can be 1. When the RA field occupies more bits, the first and second contents can be other binary numbers, which will not be elaborated here. The first and second types mentioned above can be CFRA and CBRA respectively; or the first and second types mentioned above can be 2-step random access type or 3-step random access type respectively.

[0162] In Figures 5 and 6, the Task ID field corresponds to the first identification information and is used to identify the same business request, that is, to identify whether it is a Paging message for the same business request, in order to avoid the device from executing duplicate responses.

[0163] In addition, the first message may also include a third indication field (not shown in the figure), which indicates whether the first message includes environmental IoT device identification information. When the first message indicates environmental IoT device identification information via Device ID, it does not include environmental IoT device identification information, i.e., it does not include Device ID. In one possible implementation, the device may consider the first message to be for all devices. Upon receiving the message, the device needs to initiate random access or respond to the first message. The third indication field may also indicate the type of environmental IoT device identification information, such as not including Device ID, being of type Device ID, or being of type Device filter information (i.e., group device identification). This application embodiment does not limit the specific location of the third indication field. The third indication field may be located before the device identification field or in the field containing the sub-header information of the first message, which may also be called control information.

[0164] The following details how the first message indicates the identification information of environmental IoT devices through the device identification field.

[0165] When a Reader pages multiple Devices via a first message, a single Device ID might occupy a significant number of bits, such as 48 or 80 bits. In this case, directly including all complete Device IDs in the first message would result in a significant waste of resources. To address this issue, the Device Identifier field in this embodiment records the relationship between multiple Device IDs, thereby saving the number of bits occupied by the Device Identifier field. This will be explained in detail below with reference to the accompanying drawings.

[0166] Referring to Figure 7, this figure is a schematic diagram of the format of the first message provided in the embodiments of this application.

[0167] Taking environmental IoT device identification information as an example, which includes i device identification fields, where i is an integer greater than 1. Each of the i device identification fields indicates a corresponding Device ID, meaning the first message can indicate i Device IDs.

[0168] The first device identifier field is the first device identifier, namely Device ID1. Subsequent device identifier fields no longer record the complete Device ID, but rather record its relationship with the previous Device ID or with Device ID1, which will be explained below.

[0169] In one possible implementation, the j-th device identifier field is the difference between the j-th device identifier and the first device identifier, where j = 2, 3, ..., i. In this case, D1 = Device ID2 - Device ID1 in Figure 7; D2 = Device ID3 - Device ID1, and so on. i-1 =Device ID i -Device ID1. At this point, each Device ID requires only one line of bits to indicate. For example, when the Reader wants the Device IDs of multiple Devices paged by the first message to be consecutive, D1 = 000001, D2 = 000010, D3 = 000011, ..., and so on. i-1 The maximum value is 111111. When the Device receives the first message, it first reads the first Device ID, that is, determines Device ID1. Then, it overlays the Device ID1 with the subsequent device identification fields to determine the identifier of all Devices indicated by the first message.

[0170] In another possible implementation, the j-th device identifier field is the difference between the j-th device identifier and the (j-1)-th device identifier, where j = 2, 3, ..., i. In this case, D1 = Device ID2 - Device ID1; D2 = Device ID3 - Device ID2, and so on in Figure 7. i-1 =Device ID i -Device ID i-1 In this case, each Device ID only requires one line of bits to indicate it. For example, when all Device IDs are consecutive, D1 = D2 = ... = D i-1 =000001. When the Device receives the first message, it first reads the first Device ID, that is, determines Device ID1, and then adds the subsequent device identification fields to it, so as to determine the identification of all the Devices indicated by the first message.

[0171] In another possible implementation, the first device identifier field is the first device identifier, the difference between devices is N, then the second device identifier is the first device identifier plus N, the third device identifier is the first device identifier plus 2N, and so on.

[0172] When the Device IDs of multiple Devices batch-paged by the Reader through the first message are consecutive, the indication of multiple Device IDs can be achieved through the first Device Identifier field and the second Device Identifier field, as explained in detail below with reference to the attached diagram.

[0173] Referring to Figure 8, this figure is a schematic diagram of the format of the first message provided in the embodiments of this application.

[0174] In one possible implementation, the first device identifier field is Device ID1. The second device identifier field P represents the number i of IoT devices in the environment. For example, when the number of Device IDs indicated by the first message is 5, the second device identifier field P is 000101. In this case, only one bit is needed to indicate all subsequent Device IDs. When a device receives the first message, it first reads the first Device ID, i.e., determines Device ID1. Based on the second device identifier field P, all Device IDs can be determined.

[0175] In another possible implementation, the first device identifier field is Device ID1. The second device identifier field P represents the number i of the remaining IoT devices in the environment. For example, when the first message indicates 5 Device IDs, the value of the second device identifier field P is 000100. In this case, only one bit is needed to indicate all subsequent Device IDs. When a device receives the first message, it first reads the first Device ID, i.e., determines Device ID1. Based on the second device identifier field P, all Device IDs can be determined.

[0176] In another possible implementation, the first device identifier field is Device ID1. The second device identifier field P is the difference between the second device identifier and the first device identifier. Here, the first device identifier is the device identifier of the first environmental IoT device among a group of consecutively identified environmental IoT devices, and the second device identifier is the device identifier of the last environmental IoT device among a group of consecutively identified environmental IoT devices. For example, when the number of consecutive Device IDs is 5, the value of the second device identifier field P is 000100. In this case, only one bit is needed to indicate all subsequent Device IDs. When a device receives the first message, it first reads the first Device ID, i.e., determines Device ID1. Based on the second device identifier field P, all Device IDs can be determined.

[0177] Furthermore, when the Reader pages two Devices via the first message, since the number of Device IDs is relatively small, it can be directly indicated using two device identifier fields. That is, the first device identifier field is the first device identifier, and the second device identifier field is the second device identifier. The first device identifier and the second device identifier can be consecutive or non-consecutive.

[0178] The following describes the implementation method when one or more device identifier fields of the first message are located in the last field of the PDU or SDU of the first message.

[0179] Referring to Figure 9, this figure is a schematic diagram of the format of the first message provided in the embodiment of this application.

[0180] Figure 9 illustrates this by using the example of multiple device identification fields located in the last field of the PDU of the first message.

[0181] In this implementation, the field preceding the device identifier field is the first protocol data unit, or the information content of the field preceding the device identifier field is the first protocol data unit. After the device reads the field preceding the device identifier field, the total length of the device identifier field can be determined. Based on the length of the device ID, the number of device IDs can be determined, and each device ID can be determined based on the number of device IDs. This will be explained in detail below.

[0182] Each device identifier field includes a DT field indicating the format used for the device identifier and a field recording the Device ID, as shown in Figure 9. When a Device ID needs to be indicated by x rows, it occupies a length of 8x bits. Once the total length occupied by the device identifier field is determined, the number of Device IDs can be determined, and each Device ID can be read sequentially.

[0183] For example, when x is 4, a Device ID requires 4 rows and a total length of 32 bits. When the Device ID field is determined to occupy a total length of 96 bits, the number of Device IDs can be determined to be 3. At this point, one Device ID is read every 32 bits. After reading 3 Device IDs, it can be determined that the Device ID reading is complete.

[0184] The first message in the embodiments of this application may include a fourth indication field and / or a fifth indication field.

[0185] The fifth indication field corresponds to field L in Figure 9, and is used to indicate the data packet length of the field preceding the device identification field, i.e., the data packet length of the first protocol data unit. The first protocol data unit in Figure 9 is a 4-line PDU, which is only an example and does not constitute a limitation on the technical solution of this application.

[0186] The fourth indicator field is the length of the data packet of the first message. The fourth indicator field can be located in the sub-header information (i.e., control information) of the data packet of the first message, as explained in detail below.

[0187] See also Figures 10 and 11. Figure 10 is a schematic diagram of the sub-header information of the data packet of the first message provided in the embodiment of this application; Figure 11 is a schematic diagram of the sub-header information of the data packet of the first message provided in the embodiment of this application.

[0188] The fourth indication field L1 included in the first message indicates the length of the subsequent data packet. In this embodiment of the application, L1 is used to indicate the total length of the data packet in the first message.

[0189] The first message also includes a sixth indication field MT, which can be used to indicate the type of the first message. In this embodiment, the type of the first message is a paging message. The paging message can carry DL commands via a NAS PDU, or it can carry information related to the inventory service.

[0190] Furthermore, the format of the first message can be reused for other messages, so the type of the first message can also be MSG2, R2D (Reader to Device) scheduling message, etc. This embodiment only uses the sixth indicator field MT occupying 2 bits as an example, but it does not constitute a limitation on the technical solution of this application.

[0191] Furthermore, the first message also includes a seventh indicator field and / or an eighth indicator field, wherein the seventh indicator field F is used to indicate the length of the fourth indicator field L1, and the eighth indicator field is used to indicate the length of the fifth indicator field L.

[0192] In Figures 10 and 11, the seventh indicator field is F, which is used to indicate the length of the fourth indicator field L1. When the value of the seventh indicator field F in Figure 10 is the first content, the length of the fourth indicator field L1 is 5 bits; when the value of the seventh indicator field F in Figure 11 is the second content, the length of the fourth indicator field L1 is 7 bits.

[0193] In Figures 10 and 11, when the seventh indicator field F occupies 1 bit, the first content can be 1 and the second content can be 0; or the first content can be 0 and the second content can be 1.

[0194] In Figures 10 and 11, field R is a reserved field, used to implement format alignment.

[0195] After the Device reads the fourth indicator field L1, the total length of the first message data packet can be determined. After the Device reads the fifth indicator field L as shown in Figure 9, the total length of the first protocol data unit before the device identifier field can be determined. The difference between the total length of the data packet, the total length of the first protocol data unit, and some control fields (e.g., resource information, RA field, first identifier information, etc.) is the total length occupied by the device identifier field. Once the total length occupied by the device identifier field is determined, the number of Device IDs can be determined, and each Device ID is read sequentially. It is understood that the device identifier field can also adopt the implementation method corresponding to Figure 7 or Figure 8. In this case, the number of bits in the field indicating the first Device ID is different from the number of bits in the field indicating subsequent Device IDs. The Device can determine the number of Device IDs according to the specific structure of the device identifier field. For example, when the device identifier field adopts the implementation method shown in Figure 7, after determining the total length L0 occupied by the device identifier field, the number of Device IDs = (L0-8x) / 8+1.

[0196] In the above embodiments, the Resource Info field occupies a small number of bits and can indicate a limited amount of information. In order to enable the Device to obtain more comprehensive resource-related information, this application embodiment also provides another method for indicating resource information.

[0197] See also Figures 12 and 13. Figure 12 is a schematic diagram of the format of the first message provided in the embodiment of this application (Figure 6); Figure 13 is a schematic diagram of the format of the first message provided in the embodiment of this application (Figure 7).

[0198] Figures 12 and 13 only illustrate the fields related to resource information in the first message.

[0199] In this embodiment, the first message may include a ninth indication field T / F, which indicates the multiple access transmission method used by the IoT device in the environment. The multiple access transmission method may include a first multiple access transmission method and a second multiple access transmission method. In one possible implementation, the first multiple access transmission method may be Time Division Multiple Access (TDMA), and the second multiple access transmission method may be Frequency Division Multiple Access (FDMA).

[0200] In this embodiment of the application, the first message includes random access type indication information, which includes a resource indication field.

[0201] In one possible implementation, when the resource indication field contains a third element, it indicates that the resource is a dedicated resource and the random access type is Contention-Free Random Access (CFRA). When the resource indication field contains a fourth element, it indicates that the resource is a shared resource and the random access type is Contention-Based Random Access (CBRA).

[0202] In another possible implementation, the resource indication field includes a tenth indication field and / or an eleventh indication field. The following explanation uses an example that includes both the tenth and eleventh indication fields. In this case, the tenth indication field is field Q in Figures 12 and 13, where Q indicates the number of random access opportunities, and the time-domain resources may also include the number of time-domain multiplexing. The eleventh indication field is field F in Figures 12 and 13, where F indicates frequency point information and / or frequency domain bandwidth information and / or the number of frequency domain bands, and may indicate the number of frequency-domain multiplexing. The tenth indication field Q indicates the resources of the first multiple access transmission mode, and the eleventh indication field indicates the resources of the second multiple access transmission mode.

[0203] Taking TDMA as the first multiple access transmission mode and FDMA as the second multiple access transmission mode as an example.

[0204] When the first message indicates that the Device uses TDMA, only time-domain related information will exist. In this case, the eleventh indication field will either contain the first preset content or not exist. For example, when indicating TDMA, as shown in Figure 12, when Q and F are on the same row, F can contain the first preset content, such as 0. As shown in Figure 13, when Q and F are on different rows, F can indicate that time-domain related resources do not exist.

[0205] When the first message indicates that the Device uses FDMA, only frequency domain-related information will exist. In this case, the tenth indication field will either contain the first preset content or not exist at all. For example, when indicating FDMA, if Q and F are on the same line, Q can contain the first preset content, such as 0. If Q and F are on different lines, Q can indicate that time domain-related resources do not exist.

[0206] The random access type can be indicated by a specific value for Q. For example, a first value for Q indicates CFRA, and a second value for Q indicates CBRA. Alternatively, the random access type can be indicated by the resource type specified by Q. For instance, a specific value for Q indicating a dedicated resource type also indicates CFRA; a specific value for Q indicating a shared resource type also indicates CBRA.

[0207] Furthermore, the first message may also include a twelfth indication field (not shown in Figures 12 and 13), which may indicate one or more of the following: modulation mode, modulation parameters corresponding to the modulation mode.

[0208] The modulation method may include, but is not limited to, on-off keying (OOK), binary phase shift keying (BPSK), minimum-shift keying (MSK), etc., and the embodiments of this application do not impose specific limitations.

[0209] The modulation parameters corresponding to the modulation method include, but are not limited to, modulation-related phase parameters and phase indication information.

[0210] To enable those skilled in the art to better understand the paging method provided in this application, the process of random access for a Reader paging Device is described below.

[0211] First, let's explain when the device is accessed.

[0212] Referring to Figure 14, this figure is a schematic diagram of the random access timing provided in an embodiment of this application.

[0213] Device access timing refers to the time and frequency resource opportunity for a device to access the network (e.g., the device sends A-IoT Msg1).

[0214] The timing of access for different devices is scheduled by the R2D message that triggers random access. The device side may maintain a counter value to track device access timing; this counter value may be (0, 2). Q The random value in -1) is decremented by 1 when an R2D indication message (random access timing indication message) is received or a random access timing occurs. When the count value is 0, the Device initiates a random access procedure.

[0215] After receiving the first message, the Device in this embodiment of the application may initiate a process to determine the random access type and access timing resources.

[0216] The device determines the random access type through the first message, which can be either CFRA or CBRA.

[0217] If the random access type is CBRA, in a TDMA scenario, the Device can randomly select an access time to send MSG1.

[0218] The following solutions can be adopted for specific competition resolution.

[0219] Option 1: The Device determines the start of its access time by sending a randomly generated 16-bit ID to the Reader via Msg1. The Reader replies with Msg2 in response to the successfully received random ID. If the Device receives a random ID in Msg2 that matches the random ID previously sent in Msg1, the contention is considered resolved successfully.

[0220] Option 2: When the Device determines the start of its access period, it sends MSG1, which includes upper-layer data such as the Device ID and / or any other upper-layer data, as well as a 16-bit random ID generated by the A-IoT Device for the reader. The Reader may reply with Msg2 in response to the successfully received random ID. If the Device receives an Msg2 containing a random ID that matches the random ID in the previously sent Msg1, the contention is considered resolved successfully. If the Device does not receive Msg2, it cannot autonomously initiate the re-access process; only the Reader can control the re-access.

[0221] Option 3: When the Device determines the start of its access time, it sends a randomly generated 16-bit random ID to the Reader via Msg1. Additionally, the Reader controls whether to send uplink data (e.g., a command, or an instruction for the device to report uplink data or its ID). Uplink data includes the Device ID and / or any other upper-layer data. The Reader replies with Msg2 in response to the successfully received random ID. If the Device receives a Msg2 containing the same random ID as the one previously sent in Msg1, the contention is considered successfully resolved.

[0222] If the random access type is CFRA, the Device selects the indicated D2R (Device-to-Reader) resource timing. At this time, the Device sends Msg1 to the Reader. Msg1 may carry upper-layer data, which may include the Device ID and / or any other upper-layer data. If the Paging message received by the Device includes the Access Stratum (AS) ID, then Msg1 may correspond to the AS ID. The Device may receive Msg2, which may include an acknowledgment message or an unacknowledgment message; in one possible implementation, the Device may not receive Msg2, i.e., CFRA only includes the Device sending Msg1.

[0223] Based on the above access process, the Reader's requirement to repeatedly page the Device is mainly used to solve problems arising in the following scenarios:

[0224] (1) Resolve the conflict problem: there is a conflict in the random access triggered after paging, and different devices select the same random ID;

[0225] (2) When the device is out of power and does not receive the paging message, the Reader needs to resend the paging message to paging more devices.

[0226] Therefore, after the Reader's initial paging, duplicate paging messages may be sent. These two paging messages correspond to the same service request, and the Device that has already responded should not respond again. Therefore, this application introduces an ID in the first message to identify that the first message represents the same service request. In this embodiment, this ID is called the first identifier, i.e., the Task ID, indicated by the first identifier information. If the Device has received a first message with the same Task ID, it does not respond if the random access procedure is complete; otherwise, it responds. If the Device has not previously received a first message with the same Task ID, it responds.

[0227] The purpose of Task IDs is to prevent devices from making duplicate responses. In some scenarios, Task IDs are not always necessary. For example, when the Device ID can be determined by the data packet of the first message, the device may not need to rely on the Task ID to determine whether to reply to the first message. Instead, it may only need to reply when its own Device ID appears among the various Device IDs indicated in the first message data packet. Therefore, Task IDs are not always guaranteed to be present. They may exist, be absent, be reserved, or contain preset information.

[0228] The first message may include a thirteenth field, which can be positioned before the field corresponding to the Task ID. The thirteenth field indicates whether the first identifier exists, whether it is a reserved value, or whether it is preset content. When the first identifier is a reserved value, it indicates that the Task ID has no specific meaning and can be ignored; typically, the reserved value is 0, and the first identifier will be reserved and set to 0. Preset content can be resource indication information, RA indication, etc. That is, when the field containing the first identifier is not used to identify the first identifier but to indicate resource information such as RA, the thirteenth field can be the environmental IoT device identifier, such as Device ID. In this case, the first identifier may not exist, be a reserved value, or be preset content; the device determines that the first identifier does not exist, is a reserved value, or is preset content. When the environmental IoT device identifier is filter information or there is no device identifier, the first identifier may exist; the device determines that the first identifier exists. The number of Device IDs can be one or more. When the environmental IoT device identification information is a Device ID and the number of Devices is one, the first identification information can be non-existent, a reserved value, or preset content. Alternatively, when the environmental IoT device identification information is a Device ID and the number of Devices is multiple, optionally, additional indication information is needed to determine whether the first identification information can be non-existent, a reserved value, or preset content. In one implementation, if the device determines that the first identification information is non-existent or a reserved value, it will not store the first identification information.

[0229] In one possible implementation, the first message includes environmental IoT device identification information and first identification information. The first identification information field is preset to a fifth content, which indicates that the field of the first identification information should be ignored; alternatively, the first message further includes a fourteenth indication field, which is a sixth content, indicating that the field of the first identification information should be ignored. In this case, the device does not determine whether to reply to the first message based on the Task ID, but rather determines whether random access or a reply to the first message is required based on the Device ID indicated by the first message.

[0230] Furthermore, the first message mentioned above is one type of R2D downlink message. R2D downlink messages can also include other types of messages, which can be used to indicate one or more of the following: resource indication information, service indication information, random access type indication information, etc. In this case, the format of the first message can be reused for other downlink messages. At this time, the thirteenth indication field can include environmental IoT device identification information, or the thirteenth indication field indicates that the first identification information is a first value, or the thirteenth indication field indicates that the message type of the first message is not a paging message. In one possible implementation, when the thirteenth indication field indicates that the first identification information is preset content, the preset content includes at least one of: resource indication information, service indication information, and random access type indication information. This indicates that the type of the first message is not a paging message, but rather another type of R2D downlink message.

[0231] In this embodiment, the first identification information is used to indicate a first identifier, which is the Task ID. The Task ID can have different types; for example, the first identifier may include a first type identifier and / or a second type identifier. The following explanation uses the example of a first identifier including both a first type identifier and a second type identifier. The first type identifier is assigned by the Reader, while the second type identifier is assigned by the Core Network (CN).

[0232] In one possible implementation, the first message may also include an identifier type indicator field, which indicates the type of the Task ID. In one example, the length of the Task ID assigned by the Reader is different from the length of the Task ID assigned by the CN. Therefore, the identifier type indicator field can indicate the type of the Task ID by indicating the length of the Task ID. For example, when the length of the Task ID is a first length, it corresponds to a first type identifier; when the length of the Task ID is a second length, it corresponds to a second type identifier.

[0233] In one possible implementation, when the Task ID of the first message is of type 1, the first message includes reader identification information, that is, the first message includes a Reader ID, so that the Device can distinguish the Reader that sent the first message.

[0234] In one possible implementation, the first message includes reader identification information, which is used to determine whether the type of the first identifier is a first type identifier. For example, if the device receives two first messages with the same Task ID, the Reader IDs included in these two first messages may be different. In this case, the device can identify the type of the first identifier as a first type identifier (Reader assignment).

[0235] The following section first explains the paging process when the Task ID is assigned by the CN, i.e., when the Task ID type is a second type identifier.

[0236] Referring to Figure 15, this figure is a flowchart of another paging method provided in an embodiment of this application.

[0237] S21: Reader1 sends the first message to Device, and Task ID1 in the first message is assigned by CN.

[0238] S22: Device responds to the first message.

[0239] Responding to the first message can include replying to the first message or initiating random access.

[0240] In one example, if the Device has not received a first message containing the first identifier information, it indicates that the first message is a new paging message, and the Device initiates random access. As shown in the figure, when the Device receives the first message sent by Reader1 in S21, it replies in S22.

[0241] Specifically, the Device may determine that it has not received a first message including the first identifier information based on one or more of the following conditions.

[0242] 1: The identifier content of the first identifier information of the previously received first message is different from the identifier content of the first identifier information of the first message; for example, if the identifier content of the first identifier information of the previously received first message is 001 and the identifier content of the first identifier information of the first message is 010, then the two are different.

[0243] 2: The identifier content of the stored first identifier information is different from the identifier content of the first identifier information of the first message. For example, if the identifier content of the stored first identifier information is 001, and the identifier content of the first identifier information of the first message is 010, then the two are different.

[0244] 3: The first identifier information of the previously received first message does not exist or is a reserved value. For example, if the identifier content of the first identifier information of the previously received first message is 000, but it is determined to be a reserved value, then the identifier content of the first identifier information of the current first message is 000, and the currently received first message is a new first message that has not been received before.

[0245] 4: The identifier content of the first identifier information received for the first time in the first message, or the identifier content of the first identifier information in the first message received for the first time in the first message.

[0246] S23: Reader2 sends the first message to Device, in which Task ID1 is assigned by CN.

[0247] Since Task ID1 in S23 is the same as Task ID1 in S21, the Device can determine that it has received the first message including the first identification information.

[0248] Specifically, the Device determines that it has received a first message including first identification information based on one or more of the following conditions:

[0249] The identifier content of the first identifier information of the previously received first message is the same as the identifier content of the first identifier information of the first message. For example, if the identifier content of the first identifier information of the previously received first message is 001, the identifier content of the first identifier information of the first message is also 001.

[0250] The identifier content of the stored first identifier information is the same as the identifier content of the first identifier information of the first message. For example, the identifier content of the stored first identifier information is 001, and the identifier content of the first identifier information of the first message is 001.

[0251] If the Device has already responded to the first message or performed random access in S22, the Device will not respond to the first message sent by Reader2, nor will it perform random access.

[0252] Specifically, the Device may determine that it has completed the response to the first message including the first identification information sent by Reader1 or the random access procedure corresponding to the first message including the first identification information sent by Reader1 has been completed based on one or more of the following conditions:

[0253] The response to the first message, which includes the first identifier information, was successful;

[0254] During the random access process, the second random access message MSG2 was received;

[0255] A success message was received during the random access process;

[0256] Send the first message MSG1 or the third message MSG3 during the random access process;

[0257] After the third message MSG3 is sent, the next random access opportunity begins;

[0258] The status information corresponding to the identifier content of the stored first identifier information has been responded to or the random access process has been completed.

[0259] The method for determining the start of the next random access opportunity includes: receiving the indication information for the start of the next time slot or the start of a random access opportunity; and determining the start of the next random access opportunity based on the division of time or time slot.

[0260] In another example, after the Device has completed replying to the first message or performing random access in S22, if the Device receives the first message sent by Reader2 (the Task ID1 of the first message is the same as in S21), the Device can also reply to the first message sent by Reader2, or perform random access for Reader2. Similarly, the Device can determine that it has completed the response to the first message sent by Reader1 including the first identification information or completed the random access procedure corresponding to the first message sent by Reader1 including the first identification information based on one or more of the conditions in the above examples.

[0261] In another example, when the Device has received a first message containing the first identifier information, but has not completed a response to the first message containing the first identifier information or has not completed the random access procedure corresponding to the first message containing the first identifier information, it initiates random access. That is, when the Device receives the first message sent by Reader2 in S23, and S22 is not completed, it can reply to Reader2 or initiate random access for Reader2.

[0262] Specifically, the Device may determine that a response to the first message containing the first identification information sent by Reader1 has not been completed, or that the random access procedure corresponding to the first message containing the first identification information sent by Reader1 has not been completed, based on one or more of the following conditions:

[0263] The first message, which includes the first identification information, was not responded to.

[0264] The response to the first message, which includes the first identifier information, failed.

[0265] The second random access message, Msg2, was not received during the random access process;

[0266] A failure message was received during the random access process;

[0267] The status information corresponding to the identifier content of the stored first identifier information has not responded or the random access process has not been completed.

[0268] The following describes the paging process when the Task ID is assigned by the Reader, i.e., when the Task ID type is a first-type identifier.

[0269] Referring to Figure 16, this figure is a flowchart of another paging method provided in an embodiment of this application.

[0270] S31: Reader1 sends the first message to the Device, and Task ID1 in the first message is assigned by the Reader.

[0271] At this point, Task ID1 is specifically assigned by Reader1, and the first message can carry Reader1's ID.

[0272] S32: Device responds to the first message.

[0273] In one example, when the first identifier is a first type identifier, if the Device has not received a first message containing the first identifier information from a reader / writer identified by the reader / writer identifier information, it initiates random access. That is, when the Device has not received a first message containing the first identifier information sent by Reader1, it indicates that the first message is a new paging message, and the Device initiates random access. As shown in Figure 16, when the Device receives the first message sent by Reader1 in S31, it replies in S32.

[0274] Specifically, the Device can determine that it has not received a first message including the first identifier information based on one or more of the following conditions:

[0275] The identifier content of the first identifier information of the previously received first message is different from the identifier content of the first identifier information of the first message.

[0276] The identifier content of the stored first identifier information is different from the identifier content of the first identifier information in the first message;

[0277] The first identifier information of the previously received first message does not exist or is a reserved value;

[0278] The identifier content of the first identifier information received for the first time.

[0279] S33: Reader1 sends the first message to Device, and Task ID1 in the first message is assigned by Reader.

[0280] At this time, Task ID1 is specifically assigned by Reader1. Since Task ID1 in S33 is the same as Task ID1 in S31, Device can determine that it has received the first message including the first identification information.

[0281] Specifically, the Device determines that it has received a first message including first identification information based on one or more of the following conditions:

[0282] The identifier content of the first identifier information of the previously received first message is the same as the identifier content of the first identifier information of the first message.

[0283] The identifier content of the stored first identifier information is the same as the identifier content of the first identifier information of the first message.

[0284] When the Device has already completed replying to the first message or performing random access in S32, the Device will not reply to the first message sent by Reader1, nor will it perform random access.

[0285] Specifically, the Device may determine whether to complete the response to the first message including the first identification information sent by Reader1 or to complete the random access procedure corresponding to the first message including the first identification information sent by Reader1 based on one or more of the following conditions:

[0286] For Reader1, the response to the first message, which includes the first identifier information, was successful;

[0287] For Reader1, the second message Msg2 of the random access process is received during the random access process;

[0288] For Reader1, a success message was received during the random access process;

[0289] For Reader1, send either the first message Msg1 or the third message Msg3 during the random access process;

[0290] For Reader1, after sending the third message Msg3, the start of the next random access opportunity is determined. See Figure 14 for reference. The time slot start indication is the R2D message sent by Reader1, or the random access opportunity start indication information sent before each random access opportunity.

[0291] For Reader1, the status information corresponding to the identifier content of the stored first identifier information has been responded to or the random access process has been completed.

[0292] In another example, after the Device has completed replying to the first message or performing random access in S32, if the Device receives the first message sent by Reader1 again (the Task ID1 of the first message is the same as in S21), the Device can also reply to the first message sent by Reader1 or perform random access for Reader1. Similarly, the Device can determine that it has completed the response to the first message sent by Reader1 including the first identification information or completed the random access procedure corresponding to the first message sent by Reader1 including the first identification information based on one or more of the conditions in the above examples.

[0293] In another example, when the Device receives a first message containing the first identification information from a reader identified by the reader identification information, but has not completed a response to the first message containing the first identification information from the reader identified by the reader identification information, or has not completed the random access procedure corresponding to the first message containing the first identification information from the reader identified by the reader identification information, it initiates random access. That is, when the Device receives the first message sent by Reader1 in S33, and S32 is not completed, it can reply to Reader1 or initiate random access for Reader1.

[0294] Specifically, the Device may determine whether a response to the first message including the first identification information sent to Reader1 was incomplete or the random access procedure corresponding to the first message including the first identification information sent to Reader1 was incomplete based on one or more of the following conditions:

[0295] For Reader1, no response was given to the first message, which included the first identifier information;

[0296] For Reader1, responding to the first message, which includes the first identifier information, failed.

[0297] For Reader1, the second message Msg2 of the random access was not received during the random access process;

[0298] For Reader1, a failure message was received during the random access process;

[0299] For Reader1, the status information corresponding to the identifier content of the stored first identifier information has not responded or the random access process has not been completed.

[0300] For the above S33, it can be triggered by Reader1 when S32 is not completed. For example, after Reader1 sends the first message in S31, if the random access process of S32 fails, Reader1 can resend the first message through S32 to achieve repeated paging.

[0301] S34: Reader2 sends the first message to the Device, and Task ID1 in the first message is assigned by Reader.

[0302] S35: Device responds to the first message.

[0303] At this point, Task ID1 is specifically assigned by Reader2, and the first message can carry Reader2's ID. When Device has not received a first message containing the first identification information sent by Reader2, it indicates that the first message is a new paging message, and Device initiates random access.

[0304] Understandably, if the Device determines that it has not received the first message sent by Reader2, the Device can either reply to Reader2 or randomly connect.

[0305] In the above embodiments, for the first type of identifier, after the CN allocates a Task ID, it transmits it to the Reader. The CN can indicate to the Reader whether a Task ID has been allocated through indication information. In one possible implementation, the CN can allocate Task IDs based on a certain area or cell list.

[0306] Furthermore, even if the CN assigns a Task ID, the Reader can determine whether to reassign the Task ID based on the size of the first message. For example, if the first message contains a large number of paging devices, the Task ID assigned by the CN might be too long, potentially leading to insufficient available resources for the first message. In this case, the Reader can reassign a new Task ID based on the Task ID assigned by the CN.

[0307] In summary, the solution provided by the embodiments of this application can carry multiple indication information, including reader identification information, in the first message, so that multiple environmental IoT devices can receive more comprehensive and multi-level indications and efficiently perform random access. Therefore, the format and content of the first message provided by this solution are rich, which improves the compatibility of the overall paging process and can better meet the needs of environmental IoT services.

[0308] Based on the paging method provided in the above embodiments, this application also provides a network device, which will be described in detail below with reference to the accompanying drawings.

[0309] Referring to Figure 17, this figure is a schematic diagram of a network device provided in an embodiment of this application.

[0310] Taking the network device as a base station as an example, the base station includes a processor 1110, a memory 1120, and a transceiver 1130.

[0311] The processor 1110 is mainly used for baseband processing and controlling the base station; the processor 1110 is usually the control center of the base station, used to control the base station to execute the paging method in the above method embodiment.

[0312] The memory 1120 is mainly used to store computer program code and data.

[0313] The transceiver 1130 is mainly used for transmitting and receiving radio frequency signals and for converting radio frequency signals to baseband signals. The transceiver 1130 can also be called a transceiver module, transceiver, transceiver circuit, or transceiver, etc.

[0314] The transceiver module of transceiver 1130, also known as a transceiver unit, includes antenna 1133 and radio frequency (RF) circuitry (not shown in the figure), where the RF circuitry is mainly used for RF processing. Optionally, the device in transceiver 1130 that performs the receiving function can be considered a receiver, and the device that performs the transmitting function can be considered a transmitter; that is, transceiver 1130 includes receiver 1132 and transmitter 1131. The receiver can also be called a receiving module, receiver circuit, etc., and the transmitter can be called a transmitting module, transmitter, or transmitting circuit, etc.

[0315] The processor 1110 and memory 1120 may include one or more boards, and each board may include one or more processors and one or more memories.

[0316] The processor is used to read and execute programs in memory to implement baseband processing functions and control the base station.

[0317] If multiple boards exist, they can be interconnected to enhance processing capabilities. Alternatively, multiple boards can share one or more processors, one or more memories, or multiple boards can simultaneously share one or more processors.

[0318] It should be understood that Figure 17 is merely an example and not a limitation, and the network devices described above, including processors, memory, and transceivers, may not depend on the structure shown in Figure 17.

[0319] Referring to Figure 18, this figure is a schematic diagram of an Internet of Things (IoT) device provided in an embodiment of this application.

[0320] This application does not specifically limit the type of IoT device. The IoT device can be used to receive excitation signals or backscattered signals; it may not be a power storage device and cannot independently generate or amplify signals; it may be a power storage device but cannot independently generate or amplify signals; it may be a power storage device and can also independently generate or amplify signals; it may be a power storage device (capacitor) or a super capacitor.

[0321] The IoT device shown in Figure 18 includes a processor 310, an energy storage unit 320, a sensor module 330, an indicator 340, an internal memory 350, a communication module 360, and an antenna 370. It is understood that the structure illustrated in this embodiment does not constitute a specific limitation on the electronic device. In other embodiments, the electronic device may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0322] Processor 310 may include one or more processing units, such as a processor, a modem processor, a controller, a digital signal processor (DSP), a baseband processor, etc. Different processing units may be independent devices or integrated into one or more processors.

[0323] It is understood that the interface connection relationships between the modules illustrated in this embodiment are merely illustrative and do not constitute a limitation on the structure of the electronic device. In other embodiments of this application, the electronic device may also employ different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.

[0324] The energy storage unit 320 can be a battery, capacitor, or other energy storage element. It is understood that when the electronic device is an Ambient IoT device, it may not have an energy storage unit, but can directly collect energy from the environment to power itself, such as solar energy, radio waves, motion, vibration, heat, or pressure.

[0325] The sensor module 330 may include one or more of the following: pressure sensor, gyroscope sensor, barometric pressure sensor, magnetic sensor, accelerometer, distance sensor, proximity sensor, fingerprint sensor, temperature sensor, touch sensor, ambient light sensor, bone conduction sensor, etc., to achieve the detection function.

[0326] Indicator 340 can be an indicator light, used to indicate whether the device is started or to indicate a message, etc. Indicator 340 may also be omitted.

[0327] Internal memory 350 can be used to store computer executable program code, including instructions. Processor 310 executes various functional applications and data processing of the electronic device by running the instructions stored in internal memory 350. Internal memory 350 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application required for a function, etc. The data storage area may store data collected or generated during the use of the IoT device. Internal memory 350 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc.

[0328] The wireless communication function of environmental IoT devices can be achieved through communication module 360 ​​and antenna 370. Antenna 370 may include one or more. When the electronic device is an environmental IoT device, antenna 370 can also serve as an energy receiving unit, using the collected electromagnetic wave energy to power the IoT device.

[0329] This application also provides a communication system, which may include a network device as shown in FIG17 and an environmental Internet of Things device as shown in FIG18.

[0330] Furthermore, embodiments of this application also provide a computer-readable storage medium storing a program that, when executed by a processor, implements the paging method executed by the reader side or the paging method executed by the environmental IoT device side in the above embodiments.

[0331] Computer-readable storage media include both permanent and non-permanent, removable and non-removable media, and can be implemented using any method or technology to store information. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically-erasable programmable read-only memory (EEPROM), flash memory, or other memory technologies.

[0332] Specifically, the computer-readable storage medium includes program instructions that instruct an environmental Internet of Things (IoT) device to perform the above-described method, or instruct a reader / writer to perform the above-described method.

[0333] This application also provides a computer program product containing instructions. The computer program product may be software or program products containing instructions, capable of running on an environmental IoT device or reader / writer, or stored on any available medium. When the computer program product runs on an environmental IoT device, it causes the environmental IoT device to perform the paging method described above; or, when the computer program product runs on a reader / writer, it causes the reader / writer to perform the paging method described above.

[0334] It should be understood that in this application, "at least one (item)" means one or more, and "more than" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects 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.

[0335] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A paging method, characterized in that, The method includes: Send a first message, which is used to trigger random access of one or more environmental IoT devices or to trigger one or more environmental IoT devices to execute a reply to the first message. The first message includes at least one of the following: random access type indication information, environmental IoT device identification information, service indication information, first identification information, reader / writer identification information, and environmental IoT device paging failure indication information. The first identification information is used to identify the service request.

2. The method according to claim 1, characterized in that, The first message includes the environmental IoT device identification information, which uses one or more device identification fields to indicate the device identification of one or more environmental IoT devices.

3. The method according to claim 2, characterized in that, The first message includes indication information indicating whether the first message includes multiple of the environmental IoT devices.

4. The method according to claim 3, characterized in that, The first message includes a first indication field and / or a first quantity field, wherein the first indication field is used to indicate whether the next device identifier exists, and the first quantity field is used to indicate the number of device identifiers of the environmental IoT devices.

5. The method according to claim 4, characterized in that, When the first indication field is a first content, it indicates that the next device identifier exists; or, when the first indication field is a second content, it indicates that the next device identifier does not exist, or indicates that the next field of the device identifier field begins to exist, or indicates that the device identifier field ends.

6. The method according to claim 2, characterized in that, The device identifier may be either a permanent identifier or a temporary identifier.

7. The method according to claim 1, characterized in that, The first message includes a third indication field, which is used to indicate whether the first message includes the identification information of the environmental IoT device.

8. The method according to claim 2, characterized in that, The environmental IoT device identification information includes a first device identification field and a second device identification field, wherein the first device identification field is a first device identifier; The second device identification field is the number of environmental IoT devices; Alternatively, the second device identifier field is the difference between the second device identifier and the first device identifier, wherein the first device identifier is the device identifier of the first environmental IoT device among a plurality of consecutive environmental IoT devices, and the second device identifier is the device identifier of the last environmental IoT device among the plurality of consecutive environmental IoT devices; Alternatively, the second device identifier and the first device identifier may be two consecutive device identifiers.

9. The method according to claim 2, characterized in that, The environmental IoT device identification information includes i device identification fields, where i is an integer greater than 1, and the first device identification field is the first device identifier; The j-th device identifier field is the difference between the j-th device identifier and the first device identifier, where j = 2, 3, ..., i; or, the j-th device identifier field is the difference between the j-th device identifier and the (j-1)-th device identifier, where j = 2, 3, ..., i.

10. The method according to claim 2, characterized in that, The one or more device identification fields are located in the last field of the Protocol Data Unit (PDU) or Service Data Unit (SDU) of the first message.

11. The method according to claim 10, characterized in that, The preceding field of the device identification field is a first protocol data unit, or the information content of the preceding field of the device identification field is a first protocol data unit. The first message includes a fourth indication field and / or a fifth indication field, wherein the fourth indication field is the length of the data packet of the first message, and the fifth indication field is the length of the data packet of the first protocol data unit.

12. The method according to claim 10, characterized in that, The first message also includes a sixth indication field, which is used to indicate the type of the first message.

13. The method according to claim 10, 11, or 12, characterized in that, The first message further includes a seventh indication field and / or an eighth indication field, wherein the seventh indication field is used to indicate the length of the fourth indication field and the eighth indication field is used to indicate the length of the fifth indication field.

14. The method according to claim 1, characterized in that, The first message includes random access type indication information, which includes a resource indication field. When the resource indication field includes a third element, it indicates that the resource is a dedicated resource and the random access type is non-contentionable random access (CFRA); or, when the resource indication field includes a fourth element, it indicates that the resource is a shared resource and the random access type is contentionable random access (CBRA).

15. The method according to claim 14, characterized in that, The first message includes a ninth indication field, which indicates the multiple access transmission method used by the environmental IoT device.

16. The method according to claim 15, characterized in that, The resource indication field specifically includes a tenth indication field and / or an eleventh indication field, wherein the tenth indication field is used to indicate resources of the first multiple access transmission mode, and the eleventh indication field is used to indicate resources of the second multiple access transmission mode.

17. The method according to claim 16, characterized in that, When the first message instructs the environmental IoT device to use the first multiple access transmission method, the eleventh indication field is a first preset content or the eleventh indication field does not exist; or, when the first message instructs the environmental IoT device to use the second multiple access transmission method, the tenth indication field is a first preset content or the tenth indication field does not exist.

18. The method according to claim 17, characterized in that, The first message also includes a twelfth indication field, which indicates at least one of the following: Modulation method and the corresponding modulation parameters.

19. The method according to claim 1 or 2, characterized in that, The first identification information may exist or not exist, or the first identification information may be a reserved value, or the first identification information may be preset content.

20. The method according to claim 19, characterized in that, The first message includes a thirteenth field used to indicate whether the first identification information exists, or whether the first identification information is a reserved value, or whether the first identification information is preset content.

21. The method according to claim 20, characterized in that, The thirteenth indication field includes the environmental IoT device identification information, or the thirteenth indication field indicates that the first identification information is a first value, or the thirteenth indication field indicates that the message type of the first message is not a paging message; The preset content includes at least one of the following: resource indication information, service indication information, and random access type indication information.

22. The method according to claim 1 or 2, characterized in that, The first message includes the environmental IoT device identification information and the first identification information; The field of the first identification information is preset to the fifth content, and the fifth content indicates that the field of the first identification information should be ignored; or... The first message includes a fourteenth indication field, which is a sixth content field, and the sixth content field indicates that the first identification information field should be ignored.

23. The method according to claim 1, characterized in that, The first message includes the first identification information, which is used to indicate a first identifier, and the type of the first identifier includes a first type identifier and / or a second type identifier.

24. The method according to claim 23, characterized in that, The first type of identifier is assigned by the reader / writer, and the second type of identifier is assigned by the core network.

25. The method according to claim 23 or 24, characterized in that, The first message includes an identifier type indication field, which indicates the type of the first identifier.

26. The method according to claim 24, characterized in that, When the type of the first identifier is the first type identifier, the first message includes the reader / writer identifier information.

27. The method according to claim 24, characterized in that, The first message includes the reader identification information, which is used to determine whether the type of the first identifier is the first type identifier.

28. A paging method, characterized in that, The method includes: Receive a first message, the first message being used to trigger random access of one or more environmental IoT devices or to trigger one or more environmental IoT devices to execute a reply to the first message, the first message including at least one of the following: random access type indication information, environmental IoT device identification information, service indication information, first identification information, reader identification information, and environmental IoT device paging failure indication information, the first identification information being used to identify the service request; Determine whether to respond to the first message based on the first message.

29. The method according to claim 28, characterized in that, The first message includes the environmental IoT device identification information, which uses one or more device identification fields to indicate the device identification of one or more environmental IoT devices.

30. The method according to claim 29, characterized in that, The device identifier may be either a permanent identifier or a temporary identifier.

31. The method according to claim 29, characterized in that, The environmental IoT device identification information includes a first device identification field and a second device identification field, wherein the first device identification field is a first device identifier; The second device identification field is the number of environmental IoT devices; Alternatively, the second device identifier field is the difference between the second device identifier and the first device identifier, wherein the first device identifier is the device identifier of the first environmental IoT device among a plurality of consecutive environmental IoT devices, and the second device identifier is the device identifier of the last environmental IoT device among the plurality of consecutive environmental IoT devices; Alternatively, the second device identifier and the first device identifier may be two consecutive device identifiers.

32. The method according to claim 29, characterized in that, The one or more device identification fields are located in the last field of the Protocol Data Unit (PDU) or Service Data Unit (SDU) of the first message.

33. The method according to claim 32, characterized in that, The preceding field of the device identification field is a first protocol data unit, or the information content of the preceding field of the device identification field is a first protocol data unit. The first message includes a fourth indication field and / or a fifth indication field, wherein the fourth indication field is the length of the data packet of the first message, and the fifth indication field is the length of the data packet of the first protocol data unit.

34. The method according to claim 28, characterized in that, The first message includes the first identification information, which is used to indicate a first identifier, and the type of the first identifier includes a first type identifier and / or a second type identifier.

35. The method according to claim 34, characterized in that, The first type of identifier is assigned by the reader / writer, and the second type of identifier is assigned by the core network.

36. The method according to claim 34 or 35, characterized in that, The first message includes an identifier type indication field, which indicates the type of the first identifier.

37. The method according to claim 35, characterized in that, When the type of the first identifier is the first type identifier, the first message includes the reader / writer identifier information.

38. The method according to claim 35, characterized in that, The first message includes the reader identification information, which is used to determine whether the type of the first identifier is the first type identifier.

39. The method according to claim 28, characterized in that, The step of determining whether to respond to the first message based on the first message includes at least one of the following: If no first message including the first identifier information has been received, respond to the first message; When a first message containing the first identification information has been received, and a response to the first message containing the first identification information has not been completed or a random access procedure corresponding to the first message containing the first identification information has not been completed, the first message is responded to. When a first message containing the first identification information has been received, and a response to the first message containing the first identification information has been completed or a random access procedure corresponding to the first message containing the first identification information has been completed, the first message is not responded to. When the first message received includes the device identifier, respond to the first message.

40. The method according to claim 37, characterized in that, The first message includes reader identification information, and determining whether to respond to the first message based on the first message includes at least one of the following: When the first identifier is a first type identifier and a first message including the first identifier information has not been received from a reader that has been identified by the reader identifier information, the first message is responded to; When the first identifier is a first type identifier, and a first message including the first identifier information of a reader or writer identified by the reader / writer identifier information has been received, and the response to the first message including the first identifier information of the reader or writer has not been completed or the random access procedure corresponding to the first message including the first identifier information has not been completed, the first message is responded to. When the first identifier is a first type identifier, and a first message including the first identifier information of a reader or writer identified by the reader / writer identifier information has been received, and the response to the first message including the first identifier information of the reader or writer has been completed or the random access procedure corresponding to the first message including the first identifier information has been completed, the first message is not responded to; When the first identifier is a first type identifier and the first message includes a device identifier, respond to the first message.

41. The method according to claim 39, characterized in that, It is determined that the first message including the first identification information has not been received based on one or more of the following conditions: The identifier content of the first identifier information of the previously received first message is different from the identifier content of the first identifier information of the first message. The identifier content of the stored first identifier information is different from the identifier content of the first identifier information in the first message; The first identifier information of the previously received first message does not exist or is a reserved value; The identifier content of the first identifier information received for the first time. It is determined that a first message including the first identification information has been received based on one or more of the following conditions: The identifier content of the first identifier information of the previously received first message is the same as the identifier content of the first identifier information of the first message. The identifier content of the stored first identifier information is the same as the identifier content of the first identifier information of the first message.

42. The method according to claim 39, characterized in that, The response to the first message containing the first identification information or the random access procedure corresponding to the first message containing the first identification information is not completed based on one or more of the following conditions: The first message, which includes the first identification information, was not responded to. The response to the first message, which includes the first identifier information, failed. The second random access message was not received during the random access process; A failure message was received during the random access process; The status information corresponding to the identifier content of the stored first identifier information has not responded or the random access process has not been completed; The response to the first message containing the first identification information or the random access procedure corresponding to the first message containing the first identification information is completed based on one or more of the following conditions: The response to the first message, which includes the first identifier information, was successful; The second random access message was received during the random access process; A success message was received during the random access process; Send the first or third message during the random access process; After sending the third message, the timing for the next random access is determined. The status information corresponding to the identifier content of the stored first identifier information has been responded to or the random access process has been completed.

43. The method according to claim 40, characterized in that, The response to the first message containing the first identification information from the reader or the random access procedure corresponding to the first message containing the first identification information is determined to be incomplete based on one or more of the following conditions: The reader did not respond to the first message, which included the first identification information. The reader failed to respond to the first message, which included the first identification information. For the reader / writer, no second message for random access was received during the random access process; For the reader / writer, a failure message is received during the random access process; For the reader / writer, the status information corresponding to the identifier content of the stored first identifier information has not responded or the random access process has not been completed; The response to the first message containing the first identification information from the reader is completed or the random access procedure corresponding to the first message containing the first identification information is not completed, based on one or more of the following conditions: The reader successfully responded to the first message, which included the first identification information. For the reader / writer, a second message of random access is received during the random access process; For the reader / writer, a successful access message is received during the random access process; For the reader / writer, send either the first or third message during the random access process; For the reader / writer, the random access timing is determined after the third message is sent. For the reader / writer, the status information corresponding to the identifier content of the stored first identifier information has been responded to or the random access process has been completed.

44. A reader / writer device, characterized in that, Including processor and memory; The processor is coupled to the memory; The memory is used to store instructions; The processor is used to execute computer programs or instructions stored in the memory to implement the method as described in any one of claims 1-27.

45. An electronic device, characterized in that, The electronic device includes a processor and a memory; The processor is coupled to the memory; The memory is used to store instructions; The processor is configured to execute computer programs or instructions stored in the memory to implement the method as described in any one of claims 28-43.

46. ​​A computer storage medium, characterized in that, The computer storage medium is used to store a computer program, which, when executed, implements the method as described in any one of claims 1-27, or implements the method as described in any one of claims 28-43.