Method for supporting command procedure and inventory procedure for ambient internet of things device, apparatus, and system
By setting the data transmission period of the command process during the random access process of AIoT devices, the communication process of AIoT devices is optimized, the communication complexity problem in cellular mobile systems is solved, stable and reliable wireless communication is achieved, costs are reduced and system performance is improved.
Patent Information
- Application Number
- PCT/CN2025/093590
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-08
- Publication Date
- 2026-11-12
AI Technical Summary
Existing 3GPP cellular mobile systems struggle to effectively support communication for low-cost IoT terminal devices such as AIoT devices, particularly due to complexities in random access and data transmission, which prevent devices from communicating with readers and networks.
By setting the data transmission of the command process during the random access process between the AIoT device and the reader to be completed in the same or subsequent access period, the communication process is optimized to support the wireless communication function of the AIoT device.
It enables stable and reliable communication of AIoT devices in cellular networks, reduces deployment and usage costs, and improves system capacity and spectrum utilization efficiency.
Smart Images

Figure CN2025093590_12112026_PF_FP_ABST
Abstract
Description
Methods, apparatus, and systems for supporting commands and inventory processes for environmental IoT devices. Technical Field
[0001] The embodiments of this application relate to the field of communication technology. Background Technology
[0002] From the early days of 2G to 4G, cellular mobile communication systems primarily served mobile phones—mobile terminal devices held by people. With the rapid development of mobile internet and the Internet of Things (IoT), from the later stages of 4G to the present, the evolution of cellular mobile communication technology has considered and supported increasingly diverse IoT application scenarios. Correspondingly, more types of IoT devices have been supported and implemented in actual network deployments and service applications, such as Enhanced Machine-Type Communication (eMTC) devices, Narrowband Internet of Things (NB-IoT) devices, and Reduced Capability (RedCap) devices. With the increasing diversity of IoT terminal device types, cellular mobile systems have gained increasingly stronger capabilities in providing services and offering services to vertical industries.
[0003] However, among the massive number of IoT devices, the area of large-scale and lower-cost IoT terminal devices remains a gap in cellular mobile communication systems. To provide more robust, reliable, and complete IoT application solutions, how to support lower-cost IoT terminal devices within the 3GPP cellular mobile system has become an urgent problem to be solved.
[0004] In 3GPP cellular mobile systems, low-cost IoT terminal devices are called Ambient IoT devices. Ambient-powered IoT devices are those powered by energy harvesting, without batteries or with limited energy storage capacity (e.g., using capacitors). These devices can be called Ambient IoT (AIoT) devices, passive IoT devices, or simply tags, etc. Devices that communicate directly with AIoT devices are called readers, interrogators, etc.
[0005] The reader can reside in the network device, allowing direct communication between AIoT devices and the 5G network without the need for a terminal device (e.g., a user equipment (UE)) to transmit information between the AIoT device and the 5G network. Alternatively, the reader can reside in the terminal device, enabling indirect network communication for the Ambient IoT, representing communication between the Ambient IoT device and the 5G network, where an Ambient IoT-enabled UE facilitates the transmission of information between the Ambient IoT device and the 5G network.
[0006] It should be noted that the above introduction to the technical background is only for the purpose of providing a clear and complete explanation of the technical solutions of this application and facilitating understanding by those skilled in the art. It should not be assumed that these technical solutions are known to those skilled in the art simply because they have been described in the background section of this application. Summary of the Invention
[0007] In 3GPP's 5G system, tag-based terminal devices (i.e., AIoT devices) can reuse existing base station deployments and support industry applications based on this type of terminal through existing cellular mobile communication networks, thereby effectively reducing deployment and usage costs. 3GPP's 5G system can provide reliable authentication, network coordination, and accurate and stable terminal device management mechanisms, and can also optimize the network to improve system capacity and spectrum utilization efficiency.
[0008] As a new type of IoT terminal in 5G systems, tag-based terminal devices face significant cost constraints. Their hardware capabilities are noticeably weaker than those of ordinary smartphones and other IoT devices. Traditional communication processes for terminal devices, such as random access and uplink / downlink scheduling, may be too complex for new AIoT devices, and their hardware capabilities may not be sufficient. Therefore, figuring out how to utilize the unique access and data transmission methods of AIoT devices is a pressing issue that needs to be addressed.
[0009] For example, the inventors of this application discovered that the overall business process of AIoT devices, such as the command business process including the core network process and the access layer (AS) process, is not standardized. Issues exist regarding whether the command process for a specific device during the AS process needs to be within the same timeframe as the device's random access process, how to determine the end of the paging process, and the validity period of the access layer identifier (AS ID). If these issues are not resolved, AIoT devices cannot communicate with readers and the network. Therefore, the implementation method of the command business process for AIoT devices is a problem that needs to be solved.
[0010] To address at least one of the above-mentioned problems or other similar issues, embodiments of this application provide a method, apparatus, and system for supporting commands and inventory processes for IoT devices in an environment.
[0011] According to one aspect of the embodiments of this application, a method for supporting command and inventory processes of IoT devices in an environment is provided, applied to a terminal device, the method comprising:
[0012] The terminal device establishes a connection with the reader through a random access procedure; and
[0013] The terminal device and the reader transmit data related to the command process.
[0014] Specifically, the data transmission related to the command process is completed during the same access period as the random access process, or the data transmission related to the command process is completed during an access period after the random access process.
[0015] According to one aspect of the embodiments of this application, an apparatus is provided that supports command and inventory processes for IoT devices in an environment, applied to a terminal device. The apparatus includes a first communication module, which is configured to:
[0016] A connection is established with the reader via a random access procedure; and
[0017] Data transmission related to the command process is performed between the reader and the reader.
[0018] Specifically, the data transmission related to the command process is completed during the same access period as the random access process, or the data transmission related to the command process is completed during an access period after the random access process.
[0019] One of the beneficial effects of the embodiments of this application is that by setting the data transmission of the command process and the access time of the random access process, the wireless communication function and related services of AIoT devices in the cellular network can be supported.
[0020] Specific embodiments of this application are disclosed in detail with reference to the following description and accompanying drawings, indicating how the principles of this application can be adopted. It should be understood that the embodiments of this application are not limited in scope. Within the spirit and scope of the appended claims, embodiments of this application include many changes, modifications, and equivalents.
[0021] Features described and / or illustrated for one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.
[0022] It should be emphasized that the term "including / comprises" as used herein refers to the presence of a feature, whole, step, or component, but does not exclude the presence or addition of one or more other features, wholes, steps, or components. Attached Figure Description
[0023] The elements and features described in one drawing or embodiment of this application may be combined with elements and features shown in one or more other drawings or embodiments. Furthermore, in the drawings, similar reference numerals denote corresponding parts in several drawings and can be used to indicate corresponding parts used in more than one embodiment.
[0024] Figure 1 is a schematic diagram of the first topology scenario of this application;
[0025] Figure 2 is a schematic diagram of the second topology scenario of this application;
[0026] Figure 3 is a schematic diagram of a method for supporting command and inventory processes of IoT devices in an environment, according to an embodiment of the first aspect of this application.
[0027] Figure 4 is a schematic diagram of the basic communication flow between the AIoT device and the reader, and between the reader and the AIoT core network node, in the first embodiment of this application for the command process.
[0028] Figure 5 is a schematic diagram of the basic communication flow between the AIoT device and the reader, and between the reader and the AIoT core network node, in the second embodiment of this application for the command process.
[0029] Figure 6 is a schematic diagram of a method for supporting command and inventory processes of IoT devices in an environment, according to an embodiment of the second aspect of this application.
[0030] Figure 7 is a schematic diagram of an apparatus for supporting command and inventory processes of environmental Internet of Things (IoT) devices according to an embodiment of the third aspect of this application;
[0031] Figure 8 is a schematic diagram of an apparatus for supporting command and inventory processes of environmental Internet of Things (IoT) devices according to an embodiment of the fourth aspect of this application;
[0032] Figure 9 is a schematic diagram of an electronic device according to an embodiment of this application. Detailed Implementation
[0033] Referring to the accompanying drawings, the foregoing and other features of this application will become apparent from the following description. Specific embodiments of this application are specifically disclosed in the description and drawings, illustrating partial implementations in which the principles of this application may be employed. It should be understood that this application is not limited to the described embodiments; rather, it includes all modifications, variations, and equivalents falling within the scope of the appended claims.
[0034] In the embodiments of this application, the terms "first," "second," etc., are used to distinguish different elements by name, but do not indicate the spatial arrangement or chronological order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one or more of the terms listed in association and all combinations thereof. The terms "comprising," "including," "having," etc., refer to the presence of the stated features, elements, components, or assemblies, but do not exclude the presence or addition of one or more other features, elements, components, or assemblies.
[0035] In the embodiments of this application, the singular forms "a," "the," etc., including the plural forms, should be broadly understood as "a kind" or "a class" rather than limited to the meaning of "an." Furthermore, the term "the" should be understood to include both the singular and plural forms, unless the context explicitly indicates otherwise. Additionally, the term "according to" should be understood as "at least partially based on…," and the term "based on" should be understood as "at least partially based on…," unless the context explicitly indicates otherwise.
[0036] In the embodiments of this application, the term "communication network" or "wireless communication network" may refer to a network that conforms to any of the following communication standards, such as New Radio (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), etc.
[0037] Furthermore, communication between devices in a communication system can be carried out according to communication protocols at any stage, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G, New Radio (NR), etc., and / or other currently known or future communication protocols.
[0038] In the embodiments of this application, the term "network device" refers, for example, to a device in a communication system that connects a terminal device to a communication network and provides services to that terminal device. Network devices may include, but are not limited to, the following devices: integrated access and backhaul node (IAB-node), base station (BS), access point (AP), transmission and reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.
[0039] The term "base station" can include, but is not limited to, NodeBs (or NBs), evolved NodeBs (or eNodeBs or eNBs), and 5G base stations (gNBs), etc. It can also include Remote Radio Heads (RRHs), Remote Radio Units (RRUs), relays, or low-power nodes (such as femeto, pico, etc.). The term "base station" can encompass some or all of its functions, and each base station can provide communication coverage to a specific geographic area. The term "cell" can refer to a base station and / or its coverage area, depending on the context in which the term is used.
[0040] In the embodiments of this application, the terms "User Equipment" (UE) or "Terminal Equipment" (TE) refer, for example, to a device that accesses a communication network and receives network services through a network device. A terminal device can be fixed or mobile, and may also be referred to as a mobile station (MS), terminal, subscriber station (SS), access terminal (AT), station, etc.
[0041] The terminal device may include, but is not limited to, the following devices: cellular phone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, machine-type communication device, laptop computer, cordless phone, smartphone, smartwatch, digital camera, etc.
[0042] For example, in scenarios such as the Internet of Things (IoT), terminal devices can also be machines or devices for monitoring or measurement, such as including but not limited to: machine-type communication (MTC) terminals, vehicle communication terminals, device-to-device (D2D) terminals, machine-to-machine (M2M) terminals, and so on.
[0043] Furthermore, the terms "network side" or "network equipment side" refer to one side of the network, which can be a base station or include one or more network devices as described above. The terms "user side," "terminal side," or "terminal equipment side" refer to the side of the user or terminal, which can be a UE or include one or more terminal devices as described above.
[0044] In the following description, without causing confusion, the terms “uplink control signal” and “uplink control information (UCI)” or “physical uplink control channel (PUCCH)” are used interchangeably, as are the terms “uplink data signal” and “uplink data information” or “physical uplink shared channel (PUSCH)”.
[0045] The terms “downlink control signal” and “downlink control information (DCI)” or “physical downlink control channel (PDCCH)” are interchangeable, as are the terms “downlink data signal” and “downlink data information (PDSCH)” or “physical downlink shared channel (PDSCH)”.
[0046] Furthermore, sending or receiving a PUSCH can be understood as sending or receiving uplink data carried by the PUSCH; sending or receiving a PUCCH can be understood as sending or receiving uplink information carried by the PUCCH; and sending or receiving a PRACH can be understood as sending or receiving a preamble carried by the PRACH. Uplink signals can include uplink data signals and / or uplink control signals, and can also be referred to as uplink transmission (UL transmission), uplink information, or uplink channel. Sending an uplink transmission on uplink resources can be understood as using those uplink resources to send the uplink transmission. Similarly, downlink data / signals / channels / information can be understood accordingly.
[0047] In the embodiments of this application, higher-layer signaling may be, for example, Radio Resource Control (RRC) signaling; for example, referred to as an RRC message, including MIB, system information, dedicated RRC messages; or referred to as an RRC information element. Higher-layer signaling may also be, for example, Medium Access Control (MAC) signaling; or referred to as a MAC control element. However, this application is not limited to these.
[0048] The following examples illustrate the scenarios of embodiments of this application, but this application is not limited thereto.
[0049] Figure 1 is a schematic diagram of the first topology scenario of this application.
[0050] As shown in Figure 1, in the first topology scenario, the environmental IoT device 102 directly communicates bidirectionally with the network device (e.g., base station) 101. The communication between the network device 101 and the environmental IoT device 102 includes data and / or signaling related to environmental IoT services. In the topology shown in Figure 1, the network device 101 that sends data and / or signaling to the environmental IoT device 102 is the same as the network device 101 that receives data and / or signaling from the environmental IoT device 102; however, in the topology shown in Figure 1, the network device 101 that sends data and / or signaling to the environmental IoT device 102 and the network device 101 that receives data and / or signaling from the environmental IoT device 102 may also be different.
[0051] In various embodiments of this application, a network node, such as an AIoT Radio Access Network (RAN) node, corresponding to base station 101 in Figure 1, is a network device that provides AIoT radio and is connected to a core network element (CN) that supports AIoT specific functions via an interface (such as an NG interface). This AIoT CN, as part of the functional division between the RAN and CN, carries some AIoT functions.
[0052] Figure 2 is a schematic diagram of a second topology scenario of this application. As shown in Figure 2, in the second topology scenario, the environmental IoT device 102 communicates bidirectionally with an intermediate node 103, which communicates with both the environmental IoT device 102 and the network device (e.g., base station) 101. In the topology shown in Figure 2, the intermediate node 103 can be a relay node with environmental IoT capabilities, an integrated access and backhaul (IAB) node, a user equipment (UE), a repeater, etc. The intermediate node 103 transmits environmental IoT service-related data and / or signaling between the network device 101 and the environmental IoT device 102.
[0053] In the various embodiments of this application, the terms Ambient IoT, AIoT, and Environmental Internet of Things have the same meaning and can be used interchangeably.
[0054] In various embodiments of this application, the intermediate UE reader belongs to a UE providing AIoT radio, corresponding to intermediate node 103 in FIG2, and is connected to the gNB (which may be a gNB that enhances AIoT functionality, corresponding to base station 101 in FIG2) via the New Radio User Equipment to Base Station (NR Uu) interface. The network node and the intermediate UE can use the common reader function providing AIoT radio. This reader function resides in either the AIoT RAN node or the UE reader.
[0055] In the various embodiments of this application, the terms "high-level data" and "high-level user data" have the same meaning and can be used interchangeably.
[0056] First aspect of the embodiments
[0057] The AIoT core network allows command requests to be sent to only one terminal device at a time. Before the command process, a data inventory process needs to be performed on the current device and any other potential terminal devices. Therefore, the entire business process for an AIoT device actually includes both the inventory and command processes. After the inventory process, the AIoT core network node initiates the command process through the Next Generation Control (NG-C) plane, sending a command request message to the gNB. This command process can be performed in parallel with the inventory processes of other terminal devices.
[0058] To support AIoT-related services, embodiments of this application provide a method for supporting command and inventory processes for IoT devices in an environment. This method is applied to terminal devices (e.g., AIoT devices). Through the design of the AS process, this method supports AIoT-related services and enables the command process of the terminal device (e.g., AIoT device) to run in parallel with the inventory processes of other terminal devices (e.g., other AIoT devices).
[0059] Figure 3 is a schematic diagram of a method for supporting command and inventory processes of IoT devices in an environment, according to an embodiment of this application. As shown in Figure 3, the method includes:
[0060] Operation 301: The terminal device establishes a connection with the reader through a random access procedure;
[0061] Operation 302: The terminal device and the reader perform data transmission related to the command procedure, wherein the data transmission related to the command procedure is completed during the same access period as the random access procedure, or the data transmission related to the command procedure is completed during the access period after the random access procedure.
[0062] Therefore, the AS process design supports AIoT-related services. In addition, it enables the parallel execution of the command process of terminal devices and the random access process of other terminal devices.
[0063] In Operation 302, the access period can also be called a slot, trigger message interval, or first message (Msg1) interval, etc. The start time of the access period is indicated by a paging message or an Access Occasion Trigger message.
[0064] In some embodiments, the access period is the time interval between two adjacent access timing trigger messages.
[0065] In other embodiments, the access period is the time interval between two adjacent paging messages and an access timing trigger message. For example, the access period is the time interval between a paging message and the next access timing trigger message of that paging message, wherein the paging message and the access timing trigger message are temporally adjacent; or, the access period is the time interval between an access timing trigger message and the next paging message of that access timing trigger message, wherein the access timing trigger message and the paging message are temporally adjacent.
[0066] In some examples, the access timing trigger message can also be called a Reader to Device (R2D) trigger message, used to indicate the start of random access during a certain access period, that is, after the relevant terminal device receives the access timing trigger message, it can send the first message (Msg1). In this application, the access timing trigger message and the Reader to Device (R2D) trigger message have the same meaning and can be used interchangeably.
[0067] The method for supporting command and inventory processes of IoT devices in this application is applicable to both contention-based random access (CBRA) and contention-free random access (CFRA) processes, and is specifically illustrated through the following three embodiments. The contention-free random access process can also be called the contention-free access (CFA) process.
[0068] Example 1
[0069] Because a data inventory process must be performed before command processing, the entire business process includes both the inventory process and the command process. In Example 1, a scenario involving two terminal devices is used as an example, where these two terminal devices randomly access the system during different access periods. Since multiple devices perform inventory simultaneously in one process, the CBRA process is used. The relevant descriptions in Example 1 also apply to scenarios involving three or more terminal devices.
[0070] Figure 4 is a schematic diagram of the communication flow between the AIoT device and the reader, and between the reader and the AIoT core network node, according to an embodiment of this application regarding the command process. As shown in Figure 4, the data transmission related to the command process in this communication flow is completed during the same access period as the random access process, including:
[0071] Operation 1: The AIoT core network node first sends an inventory request message to the Reader, such as a gNB with Reader functionality.
[0072] In Operation 1, the inventory request message contains a Correlation ID and an AIoT Function (AIoTF) ID to identify the inventory session. An AIoTF is a network entity or node in the AIoT core network used to support AIoT-related functions.
[0073] Operation 2: Reader nodes allocate and coordinate AIoT wireless resources.
[0074] Operation 3: The Reader node replies with a disk inventory response message to the AIoT core network node to confirm the disk inventory request.
[0075] Operation 4: The Reader sends a paging message to the first terminal device (AIoT device) via the AIoT wireless interface, thereby starting the inventory process.
[0076] In operation 4, the entire inventory and command process can be called a paging process, or paging round. First, the Reader sends a paging message based on the inventory request from the AIoT core network. The paging message is a broadcast message, indicating the first terminal device that needs to respond.
[0077] In some cases, the paging message includes a transaction ID, generated by the Reader based on the Correlation ID. The first terminal device stores the transaction ID and can use it to determine whether different paging messages are for the same service (i.e., correspond to the same Correlation ID).
[0078] In some cases, the paging message also includes a follow-on command indication, indicating that a command procedure will follow the inventory process corresponding to the random access procedure. In this way, all inventoryed terminal devices will continue to wait for subsequent command requests.
[0079] Operation 5: Transmit the first message (Msg1), the second message (Msg2), and the third message (Msg3) to complete the Reader's inventory process for the first terminal device.
[0080] In operation 5, Msg1 and Msg2 are messages transmitted during the random access procedure. Msg1 is a random identification message, and Msg2 is a random identification response message. Msg3 is the first device-to-reader (D2R) data transmission message, used to send the identifier of the first terminal device. D2R data transmission messages can also be called D2R Upper Layer Data Transfer messages.
[0081] Operation 6: After receiving the inventory results from the first terminal device and other terminal devices that performed access and device identification transmission during the same access period, the Reader sends the inventory report message to the AIoT core network node.
[0082] In operation 6, the inventory report message can contain the identification information of one or more terminal devices, and the Reader node can also send multiple inventory report messages to contain the identification information of multiple terminal devices.
[0083] Operation 7: After receiving the inventory report, the AIoT core network node initiates a command process for each terminal device based on the device identifier in the report. The AIoT core network node sends the command request message to the Reader node.
[0084] In operation 7, the command request message contains a Correlation ID, which is the same as the Correlation ID in the inventory procedure in operation 5.
[0085] In some examples, the command request message also includes the device's Next Generation Application Protocol Identifier (NGAP ID) for the Reader node to identify the terminal device, as well as the AIoT Non-access Stratum Protocol Data Unit (AIoT NAS PDU) for the target to identify.
[0086] Operation 8: The Reader node performs the command process on the AIoT wireless interface. First, it sends the AIoT NAS PDU from the command request message to the first terminal device in an R2D Upper Layer Data Transfer message (Msg4 in Figure 4). Then, the first terminal device sends the command response information as an AIoT NAS PDU in a D2R Upper Layer Data Transfer message (Msg5 in Figure 4) to the Reader.
[0087] Operation 9: The Reader node replies to the AIoT core network node with a command response message. The command response message contains the NGAP ID of the access network AIoT device and the corresponding higher-layer data (NAS PDU).
[0088] Operations 10-15: After completing the command process for all terminal devices in the first access period, the Reader initiates the inventory and command process for the second access period. For example, in operation 10, the Reader sends an access timing trigger message. The second terminal device and other terminal devices that have selected the second access period access randomly upon receiving this trigger message. Subsequent operations 11-15 are similar to operations 5-9 in the first access period.
[0089] Operation 16: After completing the command process for all terminal devices in the second access period, the Reader initiates the inventory and command process for the third access period. For example, in Operation 16, the Reader sends an access timing trigger message.
[0090] In some embodiments, the data transmission related to the command procedure between the terminal device (e.g., the first terminal device and the second terminal device) and the Reader (e.g., Msg4 and Msg5) and the random access procedure of the terminal device (or, the terminal device sending Msg1) are completed within the same access period. Since the random access procedure is part of the inventory procedure, it can also be understood that the command procedure and the inventory procedure for a terminal device are completed within the same access period.
[0091] In some embodiments, the terminal device only needs to listen to access timing trigger messages and paging messages during periods other than the selected access period. This reduces the decoding process and saves energy compared to listening to all R2D messages. Here, "listening" refers to the terminal device determining whether to perform an operation based on the message type after receiving the corresponding R2D MAC PDU. For example, listening to access timing trigger messages means that after receiving an R2D MAC PDU, the terminal device determines whether the PDU is an access timing trigger message based on the message type field in the PDU. If not, the message is discarded or ignored; if it is, subsequent related operations are performed.
[0092] Furthermore, from the reader's perspective, after completing the inventory and command process for all devices accessing during the access period, the reader sends an Access Occasion Trigger message. If it's a paging process involving inventory (i.e., no command process), the inventory process can be completed after receiving the relevant device's Msg3, sending a NACK message, or sending a Msg2 retransmission message and waiting for a period without receiving the corresponding device's Msg3. If it's a command process (i.e., the paging process includes inventory and commands), the command process can be completed after receiving the relevant device's command response (D2R higher-layer data transfer message), or after retransmitting a command request message (R2D higher-layer data transfer message) and waiting for a period without receiving a response from the corresponding device or if the response message is incorrect.
[0093] In some cases, command processes for different terminal devices can be performed concurrently within the same access period. For example, the Reader sends Msg4 to terminal device A, does not receive a reply from terminal device A (e.g., an error has occurred), then sends Msg4 to terminal device B, receives Msg5 from terminal device B, and then resends Msg4 to terminal device A, receiving a reply Msg5 from terminal device A.
[0094] To enable the terminal device to determine the end of the entire paging process so as to properly monitor the next paging process, the Reader instruction method can be used to notify that the paging process has ended, including whether the terminal device commands the process to succeed or fail.
[0095] Scenario 1: The command process on the terminal device is successful.
[0096] In Embodiment 1, since the command process and inventory process of the same terminal device are performed in the same access time period, the next Access Occasion Trigger message after the terminal device executes the command process can be used as an indication of the end of the command process.
[0097] In some cases, for paging procedures that only include an inventory process (i.e., no command process), the next Access Occasion Trigger message after the terminal device completes the inventory process (or the random access process, or the terminal device sends Msg1) can be used as an indication that the command process has ended.
[0098] In some cases, when the command process of the terminal device ends, the terminal device releases the stored AS ID.
[0099] In some embodiments, if the terminal device randomly selects the last access period from the total number of access periods indicated by the paging message, the end of the command process can be indicated in the following two ways:
[0100] Method 1: Use the next paging message after the access period as an indication that the command process has ended.
[0101] Method 1 is an implicit indication and will not add any new signaling overhead.
[0102] Method 2: After all access periods have ended (e.g., all inventory and / or command processes have ended), the Reader sends one or more Access Occasion Trigger messages as an indication that the process has ended.
[0103] Method 2 is an explicit indication, which ensures that the behavior of the terminal device accessing the last slot is consistent with that of other terminal devices. That is, they all determine the end of the command process based on the same access timing trigger message. Multiple trigger messages increase reliability and can solve the problem of behavioral uncertainty caused by a terminal device losing a particular access timing trigger message.
[0104] Scenario 2: Command process of terminal device fails
[0105] If the terminal device fails to resolve the contention during a contention-based random process, or if the terminal device receives a negative acknowledgment (NACK) message from the Reader after sending Msg3, the entire paging process is considered to have failed, the AS ID is released, and the command process is considered to have ended. The terminal device must wait for the next paging message to reconnect.
[0106] In some embodiments, the terminal device determines that the contention resolution has failed when the following conditions are met:
[0107] After the terminal device sends Msg1 containing a random identifier, it does not receive Msg2 before the first moment, or all the random identifiers in all received Msg2 do not match the random identifier contained in Msg1.
[0108] The first moment is any of the following moments:
[0109] A predefined time length (T) has elapsed since the terminal device sent Msg1. D2R_max At the moment of ), where T D2R_max The maximum time length between a D2R message transmission and the corresponding next R2D message transmission;
[0110] When the terminal device receives the next Access Occasion Trigger message after sending Msg1;
[0111] When the terminal device receives the first R2D message other than Msg2 after sending Msg1;
[0112] When a terminal device receives the first R2D higher-layer data transmission message after sending Msg1, which is also a command message, the AS ID carried in this message is not necessarily the AS ID of the terminal device itself; it could be a command message sent to other terminal devices.
[0113] Based on scenarios 1 and 2 above, the conditions under which the terminal device determines the end of the process associated with the currently stored transaction identifier include at least one of the following:
[0114] The terminal device contention resolution failed, and the process of determining the association with the stored transaction identifier failed;
[0115] The terminal device received a NACK message from the Reader carrying the terminal device's AS ID, indicating that the process of determining the association with the stored transaction identifier failed.
[0116] After the terminal device sends Msg1, and before receiving the next Access Occasion Trigger message, it does not receive a NACK message from the Reader carrying the terminal device's AS ID, indicating that the process of confirming association with the stored transaction identifier is successful.
[0117] After the terminal device sends Msg1, and before receiving the next paging message, it does not receive a NACK message from the Reader carrying the terminal device's AS ID. Therefore, the process of determining the association with the stored transaction identifier is successful.
[0118] In some cases, the failure detection of the MAC layer protocol of the terminal device is defined as follows to determine the end of the process:
[0119] The failure detection operations for the MAC entity of the terminal device include:
[0120] If a contention-based random access procedure fails, or if the terminal device receives a NACK message after sending a D2R message but before the next Access Occasion Trigger message, it is determined that the current procedure associated with the stored transaction identifier has failed.
[0121] If the terminal device has an AS ID, then that AS ID is released.
[0122] In some examples, the process of receiving Access Occasion Trigger messages in the MAC layer protocol of a terminal device can be defined as follows to determine the end of the process:
[0123] When the MAC entity of the terminal device receives the Access Occasion Trigger message, it performs the following operations:
[0124] Option 1: If the terminal device has already sent an Msg1 or D2R message, and the process associated with the stored transaction identifier has not been determined to have failed or succeeded, then determine that the current process associated with the stored transaction identifier has succeeded. If the terminal device has an AS ID, then release that AS ID; or
[0125] Option 2: The terminal device decrements the value of the counter used to select the access period by 1. If the value of the counter is equal to -1 and the process associated with the stored transaction identifier is not determined to have failed, then the process of determining the current and stored transaction identifiers is successful. If the terminal device has an AS ID, then the AS ID is released.
[0126] In option 2, the counter is a random number (i.e., a random number between 0 and [total number of access periods - 1]) generated by the device after receiving a paging message, based on the total number of access periods provided in the paging message. Each time an Access Occasion Trigger message is received, the counter is decremented by 1. When the counter reaches 0, the terminal device performs random access (e.g., sending Msg1). Determining that the counter equals -1 is equivalent to determining that the current access period is the next access period after the selected access period.
[0127] In some examples, the paging message indicates the total number of access occasions N, the number of time-domain resources X, and the number of frequency-domain resources Y in each access occasion set. The terminal device can calculate the total number of access occasions using N / (X*Y). An access occasion set refers to the set of time-frequency resources (access occasions) used to select and send Msg1 after each access occasion trigger message.
[0128] In some examples, if the counter counts the total number of access occasions N across all access periods, meaning the initial value of the counter is randomly selected from the range of 0 to [N-1], then each time an Access Occasion Trigger message is received, the counter is subtracted by the number of access occasions m in each access period. m equals the number of time-domain resources X in each access occasion set multiplied by the number of frequency-domain resources Y. Therefore, the condition in option 2 above that the counter equals -1 needs to be replaced with a condition that the counter is greater than or equal to -m and less than or equal to -1. This is equivalent to replacing the counter's condition with "the counter is less than 0 for the first time".
[0129] Example 2
[0130] Example 2 employs the same CBRA process as Example 1. Figure 5 is a schematic diagram of the basic communication flow between the AIoT device and the reader, and between the reader and the AIoT core network node, for the command process in Example 2 of this application. As shown in Figure 5, operations 1 to 6 in Example 2 are the same as operations 1 to 6 in Example 1.
[0131] The difference between Example 2 and Example 1 is that, in the AS process of the Reader and the terminal device, the message transmission of the command procedure for a terminal device and the random access procedure of that device can occur in different access periods. The command procedure of the device can occur at any time after the current process is completed; that is, the data transmission related to the command procedure of the device is completed in an access period after the access period in which the random access procedure occurs. Specifically, this includes:
[0132] 1. The inventory process of the second terminal device during the second access period, such as operation 7' to operation 8', does not need to wait for command requests from the AIoT core network;
[0133] 2. After the Reader receives the command request from the AIoT core network, such as operation 9' or operation 13', the Reader can choose to initiate the command process for the terminal device that has been successfully stored at an appropriate time, such as operation 11' or operation 14'.
[0134] In Example 2, after the inventory process of the first access period shown in Operation 5 is completed (the Reader receives Msg3 from the first terminal device in the figure), and simultaneously (or after) when the Reader sends the inventory report to the AIoT core network as shown in Operation 6, the following operations can be performed:
[0135] Operation 7': The Reader sends an Access Occasion Trigger message on the AIoT wireless interface.
[0136] Operation 8': Execute the inventory process of the second terminal device during the second access period.
[0137] Operation 9': The AIoT core network node sends the command request message of the first terminal device to the Reader node.
[0138] Operation 10': The Reader sends the device identification message stored in the second access period as a storage report to the AIoT core network node. The order of Operations 9' and 10' is not important.
[0139] Operation 11': The Reader performs a command process on the first terminal device based on the command request from the AIoT core network.
[0140] Operation 12': The Reader node forwards the command response message of the first terminal device to the AIoT core network node.
[0141] Operation 13': The AIoT core network node sends the command request message from the second terminal device to the Reader node. The order of Operations 12' and 13' is not important.
[0142] Operation 14': The Reader performs a command process on the second terminal device based on the command request from the AIoT core network.
[0143] Therefore, the method in Embodiment 2 allows the Reader more freedom to perform inventory and command processing on different terminal devices in parallel, reducing the time spent waiting for command requests from the AIoT core network and thus reducing overall process latency. The terminal devices need to listen to all R2D messages throughout the paging process.
[0144] In some embodiments, the end of the command process can be indicated in the following two ways:
[0145] Method 3: The next paging message is used to indicate the end of the command process of the terminal device, i.e., an implicit indication;
[0146] Method 4: The newly introduced first reader to device message or Access Occasion Trigger message received by the terminal device is used to indicate the end of the command process of the terminal device, i.e., to display an indication.
[0147] In Method 4, the method of using Access Occasion Trigger messages is the same as in Method 2 of Embodiment 1, that is, after all access periods have ended (all inventory and / or command processes have ended), the Reader sends one or more Access Occasion Trigger messages as an indication that the command process has ended.
[0148] In some embodiments, when the next paging message indicates the end of the command process for the terminal device, the A-IoT paging process of the A-IoT MAC layer protocol can be defined as follows:
[0149] When a terminal device receives a paging message, the terminal device's MAC entity performs the following operations:
[0150] If the process of associating with the stored transaction identifier is not determined to have failed, then the process of associating with the stored transaction identifier is successful.
[0151] If the transaction identifier in the paging message is the same as the stored transaction identifier, then no response will be given to the paging message.
[0152] In some cases, not responding to a paging message can be understood as ignoring the paging message, not taking any action, or not being selected by the paging message or not being the target device of the paging message.
[0153] In some embodiments, where the first reader-to-device message (e.g., a process end indication message) received by the terminal device is used to indicate the end of the command process of the terminal device, the reception process of the first reader-to-device message of the A-IoT MAC layer protocol can be defined as follows:
[0154] When the terminal device receives the first reader-to-device message, the terminal device's MAC entity performs the following operations:
[0155] If the process associated with the stored transaction ID is not determined to have failed, then the process associated with the current stored transaction ID is determined to have succeeded, wherein if the terminal device has an AS ID, the AS ID is released.
[0156] In some embodiments, when the Access Occasion Trigger message received by the terminal device is used to indicate the end of the terminal device's command and inventory process, the process of receiving the Access Occasion Trigger message of the A-IoT MAC layer protocol can be defined as follows:
[0157] When a terminal device receives an Access Occasion Trigger message, the terminal device's MAC entity performs the following operations:
[0158] If the number of Access Occasion Trigger messages received by the terminal device exceeds the number of access periods indicated in the paging message, and the process associated with the stored transaction identifier is not determined to have failed or succeeded, then the current process associated with the stored transaction identifier is determined to have succeeded. If the terminal device has an AS ID, then the AS ID is released.
[0159] In some examples, the command procedures (transmission and retransmission of Msg4 and Msg5) of a terminal device can be restricted to occur within the same access period. For example, in Figure 5, the command procedure 11' of the first terminal device and the command procedure 14' of the second terminal device both occur within the second access period. That is, the command procedure can occur within the same access period as the inventory procedure, or in a later access period. For example, in Figure 5, the inventory procedure 5 of the first terminal device is in the first access period, and the command procedure 11' of the first terminal device is in the second access period. However, the command procedure cannot span different access periods; for example, in Figure 5, neither the command procedure 11' of the first terminal device nor the command procedure 14' of the second terminal device can span access periods. This allows the Access Occasion Trigger message following the command procedure to still be used as an indication of the command procedure's end.
[0160] Because the command process does not support NACK messages, the end of the command process does not determine whether the current process associated with the saved transaction identifier was successful or failed; the terminal device only considers the current command process to be complete. If the command-related transmission actually fails, it can wait for subsequent processes in the A-IoT core network to potentially re-request the command.
[0161] In some embodiments, when the access occupancy trigger message received by the terminal device is used to indicate the end of the terminal device's command and inventory process, the process of receiving the Access Occasion Trigger message of the A-IoT MAC layer protocol can be defined as follows:
[0162] When a terminal device receives an Access Occasion Trigger message, the terminal device's MAC entity performs the following operations:
[0163] If the terminal device has already sent a D2R higher-level data transfer message, then the process of determining the association between the current and stored transaction identifiers is successful, wherein if the terminal device has an AS ID, then the AS ID is released.
[0164] In some cases, the release conditions for AS IDs can be simplified because AS IDs are only allocated after a command procedure is performed. For example, when an Access Occasion Trigger message is received, if the terminal device has stored an AS ID, then the terminal device's MAC entity releases that AS ID.
[0165] Example 3
[0166] In Example 3, the inventory and command procedures are directed to a single terminal device, and the AS procedure uses either the CFRA or CFA procedure. Since non-contention-based access does not involve contention resolution, there is no determination of random access failure. Furthermore, CFRA does not support NACK and does not support re-access; if the terminal device fails to access, the Reader re-initiates a CFRA-type paging procedure.
[0167] To prevent terminal devices from receiving interfering paging messages from different readers in multi-reader scenarios, the CFRA paging process requires a command / paging process end indication. Since CFRA does not have the concept of an access period and does not inherently require an Access Occasion Trigger message to trigger the transmission of Msg1, it can be designed in a consistent manner with the CBRA scenario, using the Access Occasion Trigger message as the CFRA process end indication.
[0168] In some embodiments, the process of receiving Access Occasion Trigger messages in the MAC layer protocol of a terminal device can be defined as follows:
[0169] When the terminal device receives an Access Occasion Trigger message from the Reader, the terminal device's MAC entity performs the following operations:
[0170] If the current execution is a non-contention-based access procedure, then the procedure that determines the current and stored transaction identifiers is successful, wherein if the terminal device has an AS ID, then the AS ID is released.
[0171] In some embodiments, the paging message indicating that the random access type is CFRA contains a Transaction ID. The Access Occasion Trigger message may contain the same Transaction ID as the paging message. The terminal device determines whether the trigger message is the trigger message for this paging process or the trigger message for an adjacent Reader is mistakenly received by comparing the stored Transaction ID with the Transaction ID in the Access Occasion Trigger message, thereby avoiding interference caused by receiving R2D messages from different Readers.
[0172] Second aspect of the embodiments
[0173] The method for supporting commands and inventory processes of IoT devices in this application embodiment is applied to a reader, which is set in a network device (e.g., network device 101 of FIG1 or FIG2) or a third terminal device (e.g., intermediate node 103 of FIG2). It corresponds to the method of the first aspect embodiment, and the contents that are the same as those in the first aspect embodiment will not be repeated.
[0174] Figure 6 is a schematic diagram of a method for data segmentation of IoT devices in a supporting environment according to an embodiment of the second aspect of this application. As shown in Figure 6, the method includes:
[0175] Operation 601: The reader establishes a connection with the terminal device through a random access procedure; and
[0176] Operation 602: Data transmission related to the command procedure is performed between the reader and the terminal device, wherein the data transmission related to the command procedure is completed during the same access period as the random access procedure, or the data transmission related to the command procedure is completed during the access period after the random access procedure.
[0177] In operation 602, after completing the inventory and command process for all terminal devices accessing the access period, the Reader sends an Access Occasion Trigger message.
[0178] In some cases, if it is a paging process with an inventory process (i.e., no command process), the inventory process can be completed after the Reader receives the Msg3 from the relevant terminal device, or after the Reader sends a NACK message, or after the Reader sends a Msg2 retransmission message and waits for a period of time without receiving the corresponding terminal device's Msg3.
[0179] In some cases, if it is a command procedure (i.e., the paging procedure includes inventory and command procedures), then the completion of the command procedure may be after the Reader receives the command response from the relevant terminal device (e.g., D2R higher-level data transfer message), or after the Reader retransmits the command request message (e.g., R2D higher-level data transfer message) and waits for a period of time without receiving a response from the corresponding terminal device or if the response message is incorrect.
[0180] For a detailed explanation of operations 601 and 602, please refer to the description of the relevant operations of the reader in the first aspect embodiment.
[0181] Third aspect of the embodiments
[0182] This application provides an apparatus for supporting command and inventory processes of environmental IoT devices, applied to a terminal device. This apparatus may be, for example, the terminal device itself, or one or more components or parts configured within the terminal device. It corresponds to the method for supporting command and inventory processes of environmental IoT devices applied to a terminal device in the first aspect embodiment, and the content identical to that in the first aspect embodiment will not be repeated.
[0183] Figure 7 is a schematic diagram of an apparatus for supporting command and inventory processes of IoT devices in an environment, according to an embodiment of the third aspect of this application. As shown in Figure 7, the apparatus 700 includes a first communication module 701 and a determination module 702. The first communication module 701 includes a receiver and / or a transmitter.
[0184] In some embodiments, the first communication module 701 is configured to:
[0185] A connection is established with the reader via a random access procedure; and
[0186] Data transmission related to the command process is performed between the reader and the reader.
[0187] Specifically, the data transmission related to the command procedure is completed during the same access period as the random access procedure, or the data transmission related to the command procedure is completed during the access period after the random access procedure.
[0188] In some embodiments, the access period is the time interval between two adjacent access timing trigger messages, or the time interval between two adjacent paging messages and access timing trigger messages.
[0189] In some embodiments, the data transmission related to the command procedure is completed during the same access period as the random access procedure.
[0190] After the first communication module 701 sends the first message of the random access procedure, the received next access timing trigger message is used to indicate the end of the command procedure.
[0191] In some embodiments, the paging message includes first information (follow on command indication) indicating that a command procedure is included after the inventory procedure corresponding to the random access procedure.
[0192] In some embodiments, the first communication module 701 listens for Access Occasion Trigger messages and paging messages during periods other than the access period.
[0193] In some embodiments, if the access period is the last of a plurality of periods indicated by the paging message, the first communication module 701 determines that the command process has ended when it receives the following message from the reader:
[0194] The next paging message after the access period or the next access opportunity trigger message.
[0195] In some embodiments, the apparatus 700 further includes a determining module 702, which is configured to:
[0196] The conditions for determining the end of the process associated with the current transaction identifier in storage include at least one of the following:
[0197] The terminal device contention resolution failed, and the process of determining the association with the stored transaction identifier failed;
[0198] The first communication module 701 received a negative confirmation message from the reader carrying the access layer identifier of the terminal device, indicating that the process of determining the association with the stored transaction identifier had failed.
[0199] After the first communication module 701 sends the first message, before receiving the next access timing trigger message, it does not receive a negative confirmation message carrying the access layer identifier of the terminal device sent by the reader, and the process of determining the association with the stored transaction identifier is successful.
[0200] After the first communication module 701 sends the first message and before receiving the next paging message, it does not receive a negative confirmation message from the reader carrying the access layer identifier of the terminal device, thus the process of determining the association with the stored transaction identifier is successful.
[0201] In some embodiments, the determining module 702 determines that the race resolution has failed when the following conditions are met:
[0202] After sending a first message containing a random identifier, the first communication module 701 either does not receive a second message before a first moment or all random identifiers in all received second messages do not match the random identifiers contained in the first message.
[0203] The first moment is any of the following moments:
[0204] A predefined time length (T) has elapsed since the first communication module 701 sent the first message. D2R_max The time interval is defined as the maximum time interval between a device-to-reader message transmission and the corresponding next reader-to-device message transmission.
[0205] When the next access timing trigger message is received after the first communication module 701 sends the first message;
[0206] When the first communication module 701 receives a reader-to-device message other than the first second message after sending the first message;
[0207] When the first communication module 701 sends the first message and receives the first reader to transmit data to the higher layer of the device.
[0208] In some embodiments, the failure detection operation of the media access control entity of the terminal device includes:
[0209] If the contention-based random access procedure fails, or if the first communication module 701 receives a negative acknowledgment message after sending a device-to-reader message but before triggering the next access opportunity message, it is determined that the current process associated with the stored transaction identifier has failed.
[0210] If the terminal device has an access layer identifier, then the access layer identifier is released.
[0211] In some embodiments, when the media access control entity of the terminal device receives an access timing trigger message, it performs the following operations:
[0212] If the first communication module 701 has sent the first message or the device-to-reader message, and the process associated with the stored transaction identifier has not been determined to have failed or succeeded, then the current process associated with the stored transaction identifier is determined to be successful; or
[0213] Device 700 decrements the value of the counter used to select the access period by 1. If the counter value equals -1 and the process of associating the current transaction identifier with the stored transaction identifier is not determined to have failed, then the process of determining the association between the current transaction identifier and the stored transaction identifier is successful.
[0214] If the terminal device has an access layer identifier, then the access layer identifier is released.
[0215] In some embodiments, the data transmission related to the command procedure is completed during the access period following the random access procedure.
[0216] in,
[0217] The next paging message is used to indicate the end of the command process on the terminal device; or
[0218] The first communication module 701 receives a first reader to device message or access timing trigger message to indicate the end of the command process of the terminal device.
[0219] In some embodiments, an access timing trigger message is one or more access timing trigger messages sent by the reader after all access periods have ended.
[0220] In some embodiments, when the next paging message is used to indicate the end of the command process for the terminal device...
[0221] When the first communication module 701 receives a paging message, the media access control entity of the terminal device performs the following operations:
[0222] If the process of associating with the stored transaction identifier is not determined to have failed, then the process of associating with the stored transaction identifier is successful.
[0223] If the transaction identifier in the paging message is the same as the stored transaction identifier, then no response will be given to the paging message.
[0224] In some embodiments, when the first reader-to-device message received by the first communication module 701 is used to indicate the end of the command process of the terminal device,
[0225] When the first communication module 701 receives the first reader-to-device message, the media access control entity of the terminal device performs the following operations:
[0226] If the process associated with the stored transaction identifier is not determined to have failed, then the process associated with the current stored transaction identifier is determined to have succeeded.
[0227] If the terminal device has an access layer identifier, then the access layer identifier is released.
[0228] In some embodiments, when the access timing trigger message received by the first communication module 701 is used to indicate the end of the terminal device's command and inventory process,
[0229] When the first communication module 701 receives the access timing trigger message, the media access control entity of the terminal device performs the following operations:
[0230] If the number of access timing trigger messages received by the first communication module 701 exceeds the number of access time periods indicated in the paging message, and the process associated with the stored transaction identifier is not determined to have failed or succeeded, then the current process associated with the stored transaction identifier is determined to be successful.
[0231] If the terminal device has an access layer identifier, then the access layer identifier is released.
[0232] In some embodiments, when the access timing trigger message received by the first communication module 701 is used to indicate the end of the terminal device's command and inventory process,
[0233] When the first communication module 701 receives the access timing trigger message, the media access control entity of the terminal device performs the following operations:
[0234] If the first communication module 701 has already sent the higher-level data transfer message from the device to the reader, then the process of determining the association between the current and saved transaction identifiers is successful.
[0235] If the terminal device has an access layer identifier, then the access layer identifier is released.
[0236] In some embodiments, the first communication module 701 listens for all reader-to-device messages.
[0237] In some embodiments, when the first communication module 701 receives an access timing trigger message sent by the reader, the media access control entity of the terminal device performs the following operations:
[0238] If the current execution is a non-contention-based access procedure, then the procedure that identifies the current and stored transaction identifiers is successful.
[0239] If the terminal device has an access layer identifier, then the access layer identifier is released.
[0240] In some embodiments, the paging message used to indicate that a non-contention-based access procedure includes a transaction ID,
[0241] The transaction identifier contained in the access timing trigger message is the same as the transaction identifier in the paging message.
[0242] Fourth aspect of the embodiment
[0243] This application provides an apparatus for supporting command and inventory processes of environmental IoT devices, applied to a reader located in a network device or a third-party terminal device. This apparatus may be, for example, a terminal device or a network device, or it may be one or more components or parts configured in a terminal device or network device. It corresponds to the method applied to a reader in the second aspect embodiment for supporting command and inventory processes of environmental IoT devices, and the content identical to that in the second aspect embodiment will not be repeated.
[0244] Figure 8 is a schematic diagram of a communication device according to an embodiment of the fourth aspect of this application. As shown in Figure 8, the device 800 includes a second communication module 801, which includes a receiver and / or a transmitter. The second communication module 801 is configured to:
[0245] Establish a connection with the terminal device through a random access procedure; and
[0246] Data transmission related to the command process between the terminal device and the terminal device.
[0247] Specifically, the data transmission related to the command procedure is completed during the same access period as the random access procedure, or the data transmission related to the command procedure is completed during the access period after the random access procedure.
[0248] For a detailed description of the device 800, please refer to the description of the relevant operation of the reader in the first aspect embodiment.
[0249] Fifth aspect of the embodiment
[0250] An embodiment of the fifth aspect of this application provides a communication system that may include a first terminal device, a second terminal device (e.g., an environmental IoT device), and a reader. The reader may be located in a network device or a third terminal device.
[0251] Figure 9 is a schematic diagram of an electronic device according to an embodiment of this application. At least one of the first terminal device (e.g., the environmental IoT device 102 of Figure 1 or Figure 2), the second terminal device (e.g., the environmental IoT device 102 of Figure 1 or Figure 2), the network device (e.g., the network device 101 of Figure 1 or Figure 2), and the third terminal device (e.g., the intermediate node 103 of Figure 2) may have the configuration of the electronic device shown in Figure 9.
[0252] As shown in Figure 9, the electronic device 900 can correspond to the IoT device 102 or network device 101 in the environment of Figure 1. The electronic device 900 may include a processor 910 and a memory 920; the memory 920 stores data and programs and is coupled to the processor 910. It is worth noting that this figure is exemplary; other types of structures can also be used to supplement or replace this structure to achieve telecommunications functions or other functions.
[0253] For example, the processor 910 can be configured to execute programs to perform the functions of at least one of an environmental IoT device, a first network node device, a core network, and an application server.
[0254] As shown in Figure 9, the electronic device 900 may further include: a communication module 930, an input unit 940, a display 950, and a power supply 960. The functions of these components are similar to those in the prior art and will not be described in detail here. It is worth noting that the electronic device 900 does not necessarily include all the components shown in Figure 9; these components are not essential. Furthermore, the electronic device 900 may also include components not shown in Figure 9, which can be referred to in the prior art.
[0255] This application also provides a computer program, wherein when the program is executed in at least one of a first terminal device, a second terminal device, and a reader, the program causes the device to perform a corresponding method to achieve a corresponding function.
[0256] This application embodiment also provides a storage medium storing a computer program, wherein when at least one of a first terminal device, a second terminal device, and a reader executes the program, the program causes the device to perform a corresponding method to achieve a corresponding function.
[0257] The apparatus and methods described above in this application can be implemented in hardware or in combination with software. This application relates to a computer-readable program that, when executed by a logic component, enables the logic component to implement the apparatus or components described above, or to implement the various methods or steps described above. This application also relates to storage media for storing the above programs, such as hard disks, magnetic disks, optical disks, DVDs, flash memory, etc.
[0258] The methods / apparatus described in conjunction with the embodiments of this application can be directly embodied in hardware, software modules executed by a processor, or a combination of both. For example, one or more and / or combinations of one or more functional block diagrams shown in the figures can correspond to various software modules in a computer program flow, or to various hardware modules. These software modules can correspond to the various steps shown in the figures, respectively. These hardware modules can be implemented, for example, using a field-programmable gate array (FPGA) to embed these software modules.
[0259] The software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. A storage medium can be coupled to the processor, enabling the processor to read information from and write information to the storage medium; or the storage medium can be an integral part of the processor. The processor and storage medium can reside in an ASIC. The software module can be stored in the memory of a mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a high-capacity MEGA-SIM card or a high-capacity flash memory device, the software module can be stored in the MEGA-SIM card or the high-capacity flash memory device.
[0260] One or more and / or one or more combinations of functional blocks described in the accompanying drawings can be implemented as a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any suitable combination thereof for performing the functions described herein. One or more and / or one or more combinations of functional blocks described in the accompanying drawings can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.
[0261] The present application has been described above with reference to specific embodiments. However, those skilled in the art should understand that these descriptions are exemplary and not intended to limit the scope of protection of the present application. Those skilled in the art can make various modifications and variations to the present application based on its spirit and principles, and these modifications and variations are also within the scope of the present application.
[0262] Regarding the implementation methods including the above embodiments, the following notes are also disclosed:
[0263] 1. A method for supporting command and inventory processes of IoT devices in an environment, applied to a terminal device, the method comprising:
[0264] The terminal device establishes a connection with the reader through a random access procedure; and
[0265] The terminal device and the reader transmit data related to the command process.
[0266] Specifically, the data transmission related to the command process is completed during the same access period as the random access process, or the data transmission related to the command process is completed during an access period after the random access process.
[0267] 2. A method for supporting commands and inventory processes of IoT devices in an environment, applied to a reader, the method comprising:
[0268] The reader establishes a connection with the terminal device through a random access procedure; and
[0269] The reader and the terminal device transmit data related to the command process.
[0270] Specifically, the data transmission related to the command process is completed during the same access period as the random access process, or the data transmission related to the command process is completed during an access period after the random access process.
[0271] 3. The method as described in Appendix 2, wherein,
[0272] The reader sends a Reader to Device (R2D) message to indicate that the current paging process of the terminal device has ended.
[0273] 4. The method as described in Appendix 3, wherein,
[0274] The reader-to-device message is any of the following:
[0275] Next paging message;
[0276] The message is triggered upon access.
[0277] The first reader receives device messages.
[0278] 5. As described in Appendix 4, wherein,
[0279] After all terminal devices have finished paging during the current paging process, the reader sends one or more access timing trigger messages or one or more first reader-to-device messages.
[0280] 6. A terminal device comprising a memory and a processor, the memory storing a computer program and the processor being configured to execute the computer program to implement the method as described in Appendix 1.
[0281] 7. An electronic device, which is a network device or a terminal device, comprising a memory and a processor, the memory storing a computer program and the processor being configured to execute the computer program to implement the method as described in any one of Appendices 1 to 5.
[0282] 8. A computer program product comprising at least a computer program that, when executed by a processor, causes a terminal device to perform the method as described in Appendix 1, or, when executed by a processor, causes an electronic device to perform the method as described in any one of Appendices 2 to 5.
Claims
1. An apparatus for supporting command and inventory processes of IoT devices in an environment, applied to a terminal device, the apparatus comprising a first communication module configured to: A connection is established with the reader via a random access procedure; and Data transmission related to the command process is performed between the reader and the reader. in, The data transmission related to the command procedure is completed during the same access period as the random access procedure, or the data transmission related to the command procedure is completed during an access period after the random access procedure.
2. The apparatus of claim 1, wherein, The access period is the time interval between two adjacent access timing trigger messages, or the time interval between two adjacent paging messages and access timing trigger messages.
3. The apparatus of claim 2, wherein, The data transmission related to the command procedure is completed during the same access period as the random access procedure. After the first communication module sends the first message of the random access procedure, the received next access timing trigger message is used to indicate the end of the command procedure.
4. The apparatus of claim 3, wherein, The paging message includes a first message (follow on command indication) indicating that a command process follows the inventory process corresponding to the random access procedure.
5. The apparatus of claim 3, wherein, The first communication module listens for Access Occasion Trigger messages and paging messages during other time periods outside the access period.
6. The apparatus of claim 3, wherein, If the access period is the last of the multiple periods indicated by the paging message, the first communication module determines that the command process has ended when it receives the following message from the reader: The next paging message after the access period or the next access timing trigger message.
7. The apparatus of claim 2, wherein, The device further includes a determining module, the determining module being configured to: The conditions for determining the end of the process associated with the current transaction identifier in storage include at least one of the following: The terminal device failed to resolve the contention, and the process of determining the association with the stored transaction identifier failed. The first communication module receives a negative acknowledgment message (NACK) from the reader carrying the access layer identifier (AS ID) of the terminal device, and determines that the process associated with the stored transaction identifier has failed. If, after the first communication module sends the first message, it does not receive a negative confirmation message carrying the access layer identifier (AS ID) of the terminal device from the reader before receiving the next access timing trigger message, it is determined that the process associated with the stored transaction identifier is successful. If the first communication module does not receive a negative confirmation message carrying the access layer identifier (AS ID) of the terminal device from the reader after sending the first message and before receiving the next paging message, it is determined that the process of associating the stored transaction identifier is successful.
8. The apparatus of claim 7, wherein, The determining module determines that the race resolution has failed when the following conditions are met: After the first communication module sends a first message containing a random identifier, it either does not receive a second message before a first moment, or all random identifiers in all received second messages do not match the random identifier contained in the first message. Wherein, the first moment is any of the following moments: A predefined time length (T) has elapsed since the first communication module sent the first message. D2R_max The time at which the predefined time length is the maximum time length between the device-to-reader message transmission and the corresponding next reader-to-device message transmission; When the first communication module receives the next access timing trigger message after sending the first message; When the first communication module receives a reader-to-device message other than the second message after sending the first message; When the first communication module receives the first reader-to-device high-level data transmission message after sending the first message.
9. The apparatus of claim 7, wherein, The failure detection operation of the media access control entity of the terminal device includes: If the contention-based random access procedure fails, or if the first communication module receives a negative acknowledgment message after sending a device-to-reader message but before triggering the next access opportunity message, it is determined that the current process associated with the stored transaction identifier has failed. If the terminal device has an access layer identifier, then the access layer identifier is released.
10. The apparatus of claim 7, wherein, When the media access control entity of the terminal device receives the access timing trigger message, it performs the following operations: If the first communication module has sent the first message or the device-to-reader message, and the process associated with the stored transaction identifier has not been determined to have failed or succeeded, then the current process associated with the stored transaction identifier is determined to be successful. or The device decrements the value of a counter used to select an access period by 1. If the value of the counter equals -1, and the process of associating the current transaction identifier with the stored transaction identifier is not determined to have failed, then the process of determining the association between the current transaction identifier and the stored transaction identifier is successful. If the terminal device has an access layer identifier, then the access layer identifier is released.
11. The apparatus of claim 2, wherein, The data transmission related to the command process is completed during the access period following the random access procedure. in, The next paging message is used to indicate that the command process of the terminal device has ended; or The first reader to device message or access timing trigger message received by the first communication module is used to indicate that the command process of the terminal device has ended.
12. The apparatus of claim 11, wherein, The access timing trigger message is one or more access timing trigger messages sent by the reader after all access periods have ended.
13. The apparatus of claim 11, wherein, In the event that the next paging message indicates the end of the command process for the terminal device... When the first communication module receives the paging message, the media access control entity of the terminal device performs the following operations: If the process of associating with the stored transaction identifier is not determined to have failed, then the process of associating with the stored transaction identifier is successful. If the transaction identifier in the paging message is the same as the stored transaction identifier, then no response will be given to the paging message.
14. The apparatus of claim 11, wherein, In the case where the first reader-to-device message received by the first communication module indicates that the command process of the terminal device has ended. When the first communication module receives the first reader-to-device message, the media access control entity of the terminal device performs the following operations: If the process associated with the stored transaction identifier is not determined to have failed, then the process associated with the current stored transaction identifier is determined to have succeeded. If the terminal device has an access layer identifier, then the access layer identifier is released.
15. The apparatus of claim 11, wherein, When the access timing trigger message received by the first communication module indicates that the command and inventory process of the terminal device has ended, When the first communication module receives the access timing trigger message, the media access control entity of the terminal device performs the following operations: If the number of access timing trigger messages received by the first communication module exceeds the number of access time periods indicated in the paging message, and the process associated with the stored transaction identifier is not determined to have failed or succeeded, then the current process associated with the stored transaction identifier is determined to be successful. If the terminal device has an access layer identifier, then the access layer identifier is released.
16. The apparatus of claim 11, wherein, When the access timing trigger message received by the first communication module indicates that the command and inventory process of the terminal device has ended, When the first communication module receives the access timing trigger message, the media access control entity of the terminal device performs the following operations: If the first communication module has already sent the higher-level data transfer message from the device to the reader, then the process of determining the association between the current and saved transaction identifiers is successful. If the terminal device has an access layer identifier, then the access layer identifier is released.
17. The apparatus of claim 11, wherein, The first communication module listens for all reader-to-device messages.
18. The apparatus of claim 2, wherein, When the first communication module receives the access timing trigger message sent by the reader, the media access control entity of the terminal device performs the following operations: If the current execution is a non-contention-based access procedure, then the procedure that identifies the current and stored transaction identifiers is successful. If the terminal device has an access layer identifier, then the access layer identifier is released.
19. The apparatus of claim 18, wherein, Paging messages used to indicate that a non-contention-based access procedure contains a transaction ID. The transaction identifier contained in the access timing trigger message is the same as the transaction identifier in the paging message.
20. A device for supporting command and inventory processes of environmental Internet of Things (IoT) devices, applied to a reader device, the device comprising a second communication module configured to: Establish a connection with the terminal device through a random access procedure; and Data transmission related to the command process is performed between the terminal device and the terminal device. in, The data transmission related to the command procedure is completed during the same access period as the random access procedure, or the data transmission related to the command procedure is completed during an access period after the random access procedure.
