Method and apparatus for supporting random access, and communication system

Abstract

Provided in the embodiments of the present application are a method and apparatus for supporting random access, and a communication system. The apparatus supporting random access is applied to a first terminal device. The apparatus comprises: a second sending module, which sends a first message (AIoT Msg1) to a reader; and a second receiving module, which receives a second message (Msg2) by means of a physical reader-to-device channel (PRDCH), wherein one PRDCH corresponds to at least one first message sent by the second sending module.

Description

Methods, apparatus and communication systems supporting random access 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] Low-cost IoT terminal devices in 3GPP cellular mobile systems 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, A-IoT) 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 a network device, enabling direct communication between AIoT devices and the 5G network without requiring 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 a terminal device, enabling indirect network communication for AIoT devices, representing communication between AIoT devices and the 5G network, where an AIoT-enabled UE facilitates information transfer between the AIoT 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.

[0007] Summary of the Invention

[0008] 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.

[0009] 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 access layer (AS) protocol stacks for terminal devices may be too complex for new AIoT devices, and their hardware capabilities may not be sufficient.

[0010] The inventors of this application have discovered that the access methods and data transmission methods for AIoT devices are not standardized, making it impossible for AIoT devices to communicate with readers and networks. For example, how to transmit message 2 and / or message 3 during random access is a problem that needs to be solved.

[0011] To address at least one of the above-mentioned problems or other similar problems, embodiments of this application provide a method, apparatus, and communication system for random access.

[0012] According to one aspect of the embodiments of this application, a device supporting random access is provided, applied to a reader, the device comprising:

[0013] The first receiving module receives a first message (AIoT Msg1) from the first terminal device; and

[0014] The first sending module sends a second message (Msg2) using a Physical Reader-to-Device Channel (PRDCH), wherein one of the PRDCHs corresponds to the first message received from at least one of the first terminal devices.

[0015] According to one aspect of the embodiments of this application, an apparatus supporting random access is provided, applied to a first terminal device, the apparatus comprising:

[0016] The second sending module sends the first message (AIoT Msg1) to the reader; and

[0017] The second receiving module receives a second message (Msg2) via a Physical Reader-to-Device Channel (PRDCH), wherein one PRDCH corresponds to at least one first message sent by the second sending module.

[0018] In this embodiment, a physical reader to device channel corresponds to a MAC PDU (protocol data unit) at the MAC layer (layer 2). Therefore, the physical reader to device channel in this embodiment can also be replaced by a MAC PDU, Msg2 MAC PDU, MAC message, layer 2 message, etc.

[0019] One of the beneficial effects of the embodiments of this application is that the transmission design of Msg2 and / or Msg3 in random access can support the wireless communication function of AIoT devices in cellular networks.

[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 shows schematic diagrams of D2R resource allocation based on FDMA, TDMA, and FDMA plus TDMA, respectively.

[0027] Figure 4 is a schematic diagram of a method supporting random access according to an embodiment of this application;

[0028] Figure 5 shows an example of the message flow of Method 1 in the scenario of resource allocation using TDMA and FDMA methods;

[0029] Figure 6 shows a schematic diagram of a transmission sequence using Msg2 and Msg3 as an example;

[0030] Figure 7 shows an example of Msg2;

[0031] Figure 8 is a schematic diagram of a method supporting random access according to an embodiment of the second aspect of this application;

[0032] Figure 9 is a schematic diagram of a device supporting random access according to an embodiment of this application;

[0033] Figure 10 is a schematic diagram of a device supporting random access according to an embodiment of this application;

[0034] Figure 11 is a schematic diagram of an electronic device. Detailed Implementation

[0035] 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.

[0036] 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.

[0037] 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.

[0038] 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.

[0039] 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.

[0040] 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.

[0041] 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.

[0042] 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.

[0043] 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.

[0044] 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.

[0045] 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.

[0046] 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)”.

[0047] 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)”.

[0048] 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.

[0049] 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.

[0050] The following examples illustrate the scenarios of embodiments of this application, but this application is not limited thereto.

[0051] Figure 1 is a schematic diagram of the first topology scenario of this application.

[0052] As shown in Figure 1, in the first topology scenario, the environmental IoT device 2 directly communicates bidirectionally with the network device (e.g., base station) 1. The communication between the network device 1 and the environmental IoT device 2 includes data and / or signaling related to environmental IoT services. In the topology shown in Figure 1, the network device 1 that sends data and / or signaling to the environmental IoT device 2 is the same as the network device 1 that receives data and / or signaling from the environmental IoT device 2; alternatively, in the topology shown in Figure 1, the network device 1 that sends data and / or signaling to the environmental IoT device 2 and the network device 1 that receives data and / or signaling from the environmental IoT device 2 may also be different.

[0053] 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 2 communicates bidirectionally with an intermediate node 3, which communicates with both the environmental IoT device 2 and the network device (e.g., base station) 1. In the topology shown in Figure 2, the intermediate node 3 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 3 transmits data and / or signaling related to environmental IoT services between the network device 1 and the environmental IoT device 2.

[0054] 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.

[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] D2R (device to reader) messages are messages from the device to the reader, also known as uplink data; R2D (reader to device) messages are messages from the physical reader to the device, also known as downlink data.

[0058] AIoT devices can use Slotted ALOHA as the basic method for random access. For contention-based random access, when each slot (in the Slotted ALOHA algorithm, a slot can be understood as a time interval, such as the duration between two R2D trigger messages, or a time-independent slot) only supports one AIoT device to successfully access, the following simple steps (taking the first message not containing high-level data as an example) can be used to resolve the contention:

[0059] AIoT Msg1 (First Message): When an AIoT device identifies the start time of its own access occasion, it sends a 16-bit random identifier generated by the AIoT device to the reader. An access occasion, also called an access opportunity, is a time-domain resource opportunity for an AIoT device to perform access (e.g., sending AIoT Msg1). Access occasions for different AIoT devices are scheduled using R2D messages (e.g., R2D messages that trigger random access).

[0060] AIoT Msg2 (Second Message): The reader sends the successfully received random identifier as a response message.

[0061] If the AIoT device receives Msg2 containing a random identifier, and this random identifier is the same as the random identifier sent in the previous AIoT Msg1, then the race condition is considered to have been resolved successfully.

[0062] If a slot can support successful access for multiple AIoT devices, when an R2D transmission triggering random access initiates multiple Msg1 transmissions, Msg2 may need to respond to multiple Msg1 transmissions. How to design the Msg2 transmission needs to be addressed.

[0063] In addition, during the access process, AIoT Msg3 (third message) needs to respond to the transmission of one or more Msg2 messages from a specific set. The design also needs to address how to perform D2R transmission based on FDMA and / or TDMA for Msg3 messages from multiple AIoT devices. This design includes how to allocate time and frequency resources for Msg3 messages to perform D2R transmission based on FDMA and / or TDMA.

[0064] To address the aforementioned or similar issues, embodiments of the first aspect of this application provide a method for supporting random access. This method designs the transmission of Msg2 and / or Msg3 in random access, particularly how to implement time-slotted ALOHA random access based on TDMA / FDMA, focusing on how to support messages 2 and 3, thereby supporting communication and services from AIoT devices to the network. It is applicable to both first and second topologies.

[0065] In various embodiments of this application, the wireless interface between the AIoT device and the access network node of topology 1 is referred to as the first interface, such as AIoT interface, AIoT Uu, A-Uu, etc. If the intermediate node 3 (such as the second terminal device) has a reader function (as shown in topology 2 in Figure 2), then the wireless interface between the AIoT-enabled intermediate UE and the AIoT device can also be referred to as the first interface. The reader function refers to the function of communicating with the AIoT device via AIoT radio. It can be implemented as a general functional entity of the network device and the second terminal device, such as a RAN-reader entity, or it can be an existing functional entity aggregated in the network device or the second terminal device.

[0066] The physical layer of the first interface has the following characteristics: For AIoT devices, since they may be passive devices, data must be transmitted via backscattering. The carrier providing the backscattering is called the first waveform, which can be a blank carrier, a carrier wave, a continuous wave, a sine wave, a backscattered / backscattering wave, or an uplink wave, etc., and this application embodiment is not limited to these. The first waveform is used to provide power to the AIoT device. The first waveform can be emitted by a device communicating with the AIoT, such as the base station in topology 1 shown in Figure 1, or the intermediate UE in topology 2 shown in Figure 2. The first waveform can also be emitted by an independent third-party device.

[0067] For example, an AIoT device transmits a signal by backscattering a first waveform. This first waveform is a waveform sent by a network device or a third-party device. The first terminal device modulates the information it intends to send to the network device onto the first waveform by adjusting its backscatter circuit, and then backscatters the modulated first waveform.

[0068] For example, the first terminal device autonomously generates a second signal and transmits it. The first terminal device autonomously generates a first waveform and modulates the information to be sent to the network device onto the first waveform before transmitting it.

[0069] In the embodiments of this application, both the first signal and the second signal are single-carrier signals. Compared with multi-carrier signals, single-carrier signals have lower modulation (e.g., using OOK, On-Off Keying modulation) and demodulation complexity, and lower requirements for hardware capabilities and accuracy, effectively reducing the complexity and cost of terminal devices.

[0070] In various embodiments of this application, the environmental IoT device 2 of FIG1 or FIG2 can also be referred to as the first terminal device, and the intermediate node 3 of FIG2 can also be referred to as the second terminal device.

[0071] In this embodiment, the network node, such as the AIoT RAN node, corresponding to network device 1 in Figure 1, is a core network element (AIoT CN) that provides AIoT radio and connects to the AIoT network function-supporting core network element via a second interface (e.g., the NG interface). This AIoT core network element, as part of the functional division between the RAN and CN, carries certain AIoT functions. The intermediate UE reader is a UE that provides AIoT radio, corresponding to intermediate node 2 in Figure 2, and is connected to the gNB (which may be a gNB that enhances AIoT functions, corresponding to network device 1 in Figure 2) via the NR Uu interface. The network node (e.g., network device 1) and the intermediate UE can use the common reader function that provides AIoT radio. The reader function resides in the AIoT RAN node (i.e., the reader is located in the network device) or in the UE reader (i.e., the reader is located in the second terminal device).

[0072] In the embodiments of this application, when it is necessary to identify multiple AIoT devices and expect responses from multiple devices, a contention-based AIoT access procedure initiated by the reader can be used. Slotted ALOHA, FDMA (Frequency Division Multiple Access), and TDMA (Time Division Multiple Access) can be used together to complete the access procedure. For example, in a slot, if FDMA is used for frequency domain resource allocation for Msg1, the device can determine the frequency domain resource allocation through the reader's instruction or its own configuration. During the access process, the response message from the device to the reader is transmitted on the Physical Device-to-Reader Channel (PDRCH). If TDMA is used, an R2D transmission that triggers random access (e.g., paging message, Msg0, R2D trigger, access round trigger, etc.) determines one or more time domain resources for D2R transmissions for Msg1, wherein each D2R transmission for Msg1 occurs in one of these one or more time domain resources. FDMA and TDMA can be used simultaneously.

[0073] Figure 3 shows schematic diagrams of D2R resource allocation based on FDMA, TDMA, and FDMA, respectively. Specifically, Figure 3a) is a schematic diagram of D2R resource allocation based on FDMA, Figure 3b) is a schematic diagram of D2R resource allocation based on TDMA, and Figure 3c) is a schematic diagram of D2R resource allocation based on both FDMA and TDMA.

[0074] If an R2D transmission that triggers random access initiates multiple Msg1 transmissions, that is, if FDMA and / or TDMA resource allocation methods are used in a slot to specify the access timing for Msg1, then Msg2 needs to respond to multiple Msg1s.

[0075] The method for supporting random access according to the first aspect of this application can be applied to the above-described scenario. The method for supporting random access according to this application will now be described from the perspective of the reader.

[0076] Figure 4 is a schematic diagram of a method for supporting random access according to an embodiment of this application. As shown in Figure 4, the method for supporting random access includes:

[0077] Operation 401: Receive the first message from the first terminal device; and

[0078] Operation 402: Send a second message using a Physical Reader-to-Device Channel (PRDCH), wherein one of the PRDCHs corresponds to the first message received from at least one of the first terminal devices.

[0079] In various embodiments of this application, the first terminal device is, for example, an AIoT device (e.g., the environmental IoT device 2 of FIG1 or 2).

[0080] In various embodiments of this application, the reader may be located at a network node (e.g., network node 1 in FIG1) or an intermediate node (e.g., intermediate node 3 in FIG2), wherein the intermediate node may also be referred to as an intermediate UE (user equipment) or a second terminal device.

[0081] In various embodiments of this application: the first message is, for example, the aforementioned AIoT Msg1, which can also be written as Msg1 in this application, that is, the AIoT Msg1 and Msg1 recorded in this application can be interchanged with each other; the second message is, for example, the aforementioned AIoT Msg2, which can also be written as Msg2 in this application, that is, the AIoT Msg2 and Msg2 recorded in this application can be interchanged with each other.

[0082] In operation 402 of this application, method 1 and method 2 can be used to transmit the second message (e.g., Msg2). The following description, using Example 1, will explain the relevant aspects of method 1 and method 2.

[0083] Example 1:

[0084] Method 1:

[0085] In Method 1, a Physical Reader-to-Device Channel (PRDCH) corresponds to a first message received from a first terminal device. That is, a PRDCH for transmitting Msg2 corresponds to an AIoT Msg1 received from a first terminal device. For example, a Layer 2 message, a MAC PDU (Media Access Control Protocol Data Unit), or an R2D transport block may contain a response to an AIoT device's Msg1. The response to Msg1 may be a random identifier that repeats the Msg1 transmission. This random identifier can also be called a random access identifier, access layer (AS) identifier, device temporary identifier, etc.

[0086] After the reader receives Msg1 (e.g., a 16-bit random identifier) ​​from one or more devices at the access time of the current slot allocation, it responds (replies) with a Msg2 (i.e., PRDCH) for each successfully received random identifier.

[0087] Figure 5 shows an example of the message flow for Method 1 in the resource allocation scenarios of TDMA and FDMA.

[0088] In Method 1, the design of the specific PRDCH (Msg2 MAC PDU) can be any of the following methods: Method 1-1, Method 1-2, Method 1-3, and Method 1-4.

[0089] Method 1-1: Each Msg2 contains a random identifier, which is equal to the random identifier of a certain AIoT device (sent in Msg1). Sequence numbers are not required; multiple Msg2s are sent consecutively, and the sending order of the Msg2s does not need to be considered. In general, the device determines whether the Msg2 is intended for it by receiving the random identifier carried by the Msg2, and proceeds with subsequent transmissions accordingly.

[0090] If an AIoT device receives an AIoT Msg2 containing a random identifier that is the same as the random identifier in the AIoT Msg1 previously sent by the device, the AIoT device determines that the contention has been successfully resolved.

[0091] Method 1-2: Each Msg2 contains a random identifier and first information indicating the corresponding access timing. This access timing refers to the access timing used by Msg1 in the response to Msg2. The first information can be used to resolve ID conflicts caused by two or more devices using the same random identifier, and devices can be identified through different access timings. The first information can be considered as the temporary access network ID used by the AIoT device during random access. In summary, the device determines whether Msg2 is intended for the AIoT device by receiving the random identifier and first information carried by Msg2, and proceeds with subsequent transmissions accordingly.

[0092] In method 1-2, if the AIoT device receives an AIoT Msg2 containing a random identifier that is the same as the random identifier in the AIoT Msg1 previously sent by the AIoT device, and the first information contained in Msg2 corresponds to the access timing used by Msg1, the AIoT device determines that the contention has been resolved successfully.

[0093] The above method for determining the success of a competition resolution is equivalent to:

[0094] If an AIoT device receives an AIoT Msg2, which contains first information corresponding to the access timing used by Msg1, and the random identifier corresponding to the first information in Msg2 is the same as the random identifier in the AIoT Msg1 previously sent by the AIoT device, the AIoT device determines that the contention has been successfully resolved.

[0095] In some examples, this first information can be a sequence number or index corresponding to different access opportunities. For example, in Figure 5, the time-frequency resources of Msg1 are divided into 8 access opportunities, and 0 to 7 can be used as the index for each access opportunity.

[0096] In other examples, the first information can also be indirect information corresponding to the access timing, and does not need to be explicitly included in Msg2. For example, the first information can be implicitly indicated as a scrambling code. Different access timings correspond to different scrambling codes, and both the reader and the device calculate the scrambling code using a predefined calculation method based on the access resources (timing). Msg2 is scrambled using the scrambling code corresponding to the access timing, and the device descrambles it using the scrambling code derived from the access timing corresponding to Msg1. If the descrambled information contains a random identifier and is equal to the random identifier it sent, then the contention is considered resolved successfully.

[0097] In some other examples, the first piece of information can also be an implicit indication of the CRC (Cyclic Redundancy Check) algorithm or parameters corresponding to the access timing. Both the reader and the device define the correspondence between the access timing and the CRC algorithm or parameters using a predefined method. The reader generates a CRC checksum using the CRC algorithm or parameters corresponding to the received Msg1 access timing, and the device uses the CRC algorithm or parameters corresponding to the Msg1 access timing to verify whether the data has changed. After a successful CRC check, it then checks whether the random identifier in Msg2 matches the random identifier it sent.

[0098] Methods 1-3: In addition to the random identifier, Msg2 also contains all or part of the device identifier. This method can be used when Msg1 contains higher-level data (such as the device identifier), for example, in a two-step random access method. This method can also resolve conflicts caused by identical random identifiers. In summary, the first terminal device determines whether Msg2 is intended for that device by receiving all or part of the random identifier and device identifier carried in Msg2, thereby determining whether the contention has been successfully resolved and proceeding with subsequent transmissions accordingly.

[0099] AIoT devices determine whether the contention has been resolved by determining whether the random identifier and (whole or part) device identifier match their own random identifier and (whole or part) device identifier, respectively.

[0100] Methods 1-4: Use pre-configured time resources corresponding to the access opportunity to transmit Msg2. In general, the device determines whether Msg2 is the information sent to the device by receiving the random identifier carried by Msg2 and the time resources used by Msg2, and proceeds with subsequent transmission accordingly.

[0101] For example, the first terminal device can be pre-configured by assigning a mapping relationship between each access opportunity and the time resource of Msg2. This time resource is a relative time resource, which can also be understood as a temporal sequence. For example, in Figure 5, access opportunities 0 to 7 correspond to the 8 time resources after Msg1 is sent. The Msg2 received by the device at the corresponding time corresponds to the corresponding Msg1. That is, the device can receive Msg2 on the Msg2 time resource corresponding to the access opportunity used by Msg1, and then determine whether the random identifier in the message matches its own random identifier. The temporal sequence can also use sequence numbers to represent time resources. For example, the order in which access opportunities 0 to 7 correspond to Msg2 allows the device to determine its corresponding access opportunity by the order in which it receives Msg2.

[0102] In Method 1, since multiple Msg2 messages may be transmitted consecutively, the first terminal device needs to know how many Msg2 messages to listen for in order to resolve contention and proceed with subsequent D2R data transmission (e.g., Msg3 transmission). For example, as shown in Figure 5, multiple Msg2 messages may be transmitted consecutively in a slot within an Ambient Internet of Things (AIoT) paging process / cycle. In this case, at least one of Options 1, 2, and 3 described below can be used to inform the first terminal device that the transmission of multiple consecutive Msg2 messages has ended.

[0103] Option 1: After Msg1, the first Msg2 message sent by the reader carries information indicating the number of Msg2 messages. This number refers to how many Msg1 messages the reader successfully received and responded to in the current slot (i.e., the current slot in the IoT paging context), specifically, how many Msg1 messages the reader successfully received and responded to during the access period in the current slot. In this way, after receiving the first Msg2, the AIoT device knows how many more Msg2 messages are expected, thus adjusting the timing of subsequent Msg2 listening and preparing for the transmission of Msg3.

[0104] Option 2: Each Msg2 contains 1 bit to indicate whether the transmission of Msg2 has ended. For example, this bit could be an extension bit (E bit). If the extension bit has a first value (e.g., 1), it indicates that there are more Msg2s to follow; if the extension bit has a second value (e.g., 0), it indicates that there are no more Msg2s to follow. Alternatively, this bit could be a stop bit, where a value of 1 indicates that this is the last Msg2, otherwise there are more Msg2s to follow.

[0105] Option 3: Use a first timer on the first terminal device side to determine whether to continue listening for Msg2. The timer's duration corresponds to a time window used to listen for random access response messages; this time window can be called the random access response window. The timer's duration (e.g., the random access response window length) can be predefined, configured by the reader for the first terminal device, or indicated in the paging message or the first Msg2 message. This timer can be started after the device sends Msg1, after the first terminal device receives the R2D message that triggers random access, or after all access opportunities for Msg1 have ended. The first terminal device can obtain the time when all access opportunities for Msg1 have ended through the time-frequency resource information for the access opportunity set indicated in the R2D trigger message. When the timer expires, the first terminal device stops listening for Msg2 and can prepare for the transmission of Msg3.

[0106] Methods 1-1, 1-2, 1-3, and 1-4 described above can be used in combination with options 1, 2, and 3. Depending on the method used, after sending Msg1, the AIoT device can continuously listen to Msg2 (e.g., if the AIoT device has sufficient power), or the AIoT device can stop listening to Msg2 if either of the following conditions is met (i.e., it will continue listening to Msg2 until either of the following conditions is satisfied):

[0107] The competition was successfully resolved;

[0108] Received the next R2D trigger message;

[0109] If the received (listening) Msg2 indicates that there is no next Msg2, for example, by using method 1 or method 2 to determine that there is no next Msg2;

[0110] The first timer timed out.

[0111] In Method 1, there is another way to transmit Msg2 and subsequent messages (e.g., possible Msg3, Msg4): after each Msg2 and before the next Msg2, the first terminal device corresponding to that Msg2 (i.e., the first terminal device responding to Msg2, the first terminal device corresponding to the random identifier in Msg2, or the first terminal device that resolved contention through that Msg2) sends Msg3. Then, the reader sends Msg4 (if any) to that first terminal device, along with any subsequent possible D2R data transmissions. After data transmission for a certain first terminal device is completed, the reader sends the next Msg2, continuing the contention resolution and data transmission for the next device, and so on.

[0112] Figure 6 illustrates a transmission sequence using Msg2 and Msg3 as an example. Unlike the method in Figure 5, in the transmission sequence shown in Figure 6, Msg3 immediately follows Msg2. As shown in Figure 6, for a first terminal device, Msg2, Msg3, and subsequent possible messages are adjacent in time.

[0113] In some examples, for the transmission sequence shown in Figure 6, in order to effectively listen to Msg2, the first terminal device can choose to continuously listen to each Msg2 to obtain its own contention resolution information, provided there is sufficient power. Once the contention is successfully resolved, Msg3 can be transmitted immediately. The time-frequency resources used to transmit Msg3 can be referred to in the following embodiment two.

[0114] In other examples, to save energy, monitoring Msg2 can involve listening to each R2D message and receiving the scheduling information within that R2D message. This allows the first terminal device to obtain the time resource information used by the D2R messages following each R2D message. If the Msg2 message is not sent to itself, the first terminal device can predict the end time of subsequent D2R messages from other devices and then start listening for the next R2D message at that end time. In other words, the first terminal device can sleep during the predicted D2R message transmission time and wake up to listen for R2D signals when the D2R message ends.

[0115] In some other examples, listening to Msg2 can also be done without receiving scheduling information for other devices. Instead, an estimated duration is used to skip the D2R transmission time of other devices before listening for the next Msg2. That is, after receiving an Msg2 sent to another device, the transmission time of Msg3 (e.g., a fixed-length device identifier plus header size) is estimated and added to a first duration to determine the appropriate sleep time. After the sleep period ends, the device wakes up to listen for R2D signals. Here, the first duration refers to the minimum time between an R2D transmission and its subsequent corresponding D2R transmission, for example, denoted as T. R2D_min .

[0116] All methods in Method 1 (e.g., Method 1-1, Method 1-2, Method 1-3, Method 1-4) and options (Option 1, Option 2, Option 3) can be applied to the transmission method shown in Figure 6.

[0117] Method 2:

[0118] In Method 2, a Physical Reader to Device Channel (PRDCH) corresponds to one or more first messages received from one or more first terminal devices. For example, a single PRDCH for transmitting Msg2 can be used to correspond to multiple AIoT Msg1 messages received from different devices.

[0119] A Msg2 MAC PDU (the MAC PDU corresponding to PRDCH) can send random access responses to multiple devices simultaneously, and each random access response contains a random identifier corresponding to Msg1.

[0120] After the reader receives Msg1 (e.g., a 16-bit random identifier) ​​from one or more devices during the access time allocated in the current slot, it responds (replies) with a Msg2 (i.e., PRDCH) for the multiple successfully received random identifiers. An example of the message flow for Method 2 can be found in Figure 3 (taking an example where a Msg2 message contains responses to all received Msg1 messages).

[0121] In Method 2, the design of the specific PRDCH (Msg2 MAC PDU) can adopt any one of the following methods: Method 2-1, Method 2-2, Method 2-3, Method 2-4, and Method 2-5.

[0122] Method 2-1: Each Msg2 contains one or more random identifiers, which are equal to the random identifier of an AIoT device (sent in Msg1). These random identifiers can be included in a list. In Method 2-1, Msg2 does not need to include a sequence number, and the order of the multiple random identifiers does not need to be considered. In summary, the AIoT device determines whether Msg2 is intended for it by receiving the random identifiers carried in Msg2, and proceeds with subsequent transmissions accordingly.

[0123] For example, if an AIoT device receives an AIoT Msg2 containing a random identifier that is the same as the random identifier in the AIoT Msg1 previously sent by the device, the device considers the race to be resolved successfully.

[0124] Method 2-2: Each Msg2 contains one or more random identifiers, and first information indicating the access timing associated with each random identifier. This access timing refers to the access timing used by the Msg1 response to that random identifier. The first information can be used to resolve ID conflicts caused by two or more devices using the same random identifier, and devices can be identified through different access timings. The first information can be considered as a temporary access network ID used by the AIoT device during random access. In summary, the device determines whether Msg2 is intended for it by receiving the random identifier and corresponding first information carried by Msg2, and proceeds with subsequent transmissions accordingly.

[0125] If an AIoT device receives an AIoT Msg2 containing a random identifier that is the same as the random identifier in the AIoT Msg1 previously sent by the device, and the first information in Msg2 corresponding to the random identifier corresponds to the access timing used by Msg1, the device considers the contention to be resolved successfully.

[0126] The above method for determining the success of a competition resolution is equivalent to:

[0127] If an AIoT device receives an AIoT Msg2, which contains first information corresponding to the access timing used by Msg1, and the random identifier corresponding to the first information in Msg2 is the same as the random identifier in the AIoT Msg1 previously sent by the AIoT device, the AIoT device determines that the contention has been successfully resolved.

[0128] The first piece of information can be a sequence number or index corresponding to different access times, and its specific content is similar to that of Method 1.

[0129] Method 2-3: Each Msg2 contains one or more random identifiers, as well as a bitmap, the number of bits corresponding to the number of access opportunities allocated to Msg1 (in the R2D trigger message). Each bit position in the bitmap corresponds to an access opportunity, and the bit value at that position indicates whether the second message contains a random identifier received at that access opportunity. In other words, the bitmap indicates which access opportunities Msg2 responded to for which Msg1. The bit positions in the bitmap are similar to the indices in Method 2-2. For example, if the bit value at bit position i is 1, then Msg2 contains a random identifier received at the access opportunity corresponding to index i. The order of the multiple random identifiers in Msg2 is sorted by their corresponding indices, for example, sorted in ascending order by index. In Msg2, the bitmap can be placed before the random identifier. After receiving (decoding) the bitmap, if the bit value at the index position corresponding to the access timing used to send Msg1 is 1, then the device can continue to decode the subsequent random identifier and decode the random identifier sent to itself according to the bitmap information at the corresponding position (for example, according to which bit position of the bit in the bitmap corresponding to the access timing used is equal to 1, to obtain the byte position of the random identifier in the Msg2 MAC PDU); if the above bit value is 0, the subsequent random identifier does not need to be decoded (i.e., this Msg2 is ignored).

[0130] Figure 7 shows an example of Msg2. Assuming the R2D trigger message allocates 8 time-frequency resources as access opportunities for Msg1 (e.g., as shown in Figure 3c), then 8 bits (1 byte) can be used as the bitmap, with each bit corresponding to one access opportunity. If N bits in the bitmap are 1, then 2N bytes are needed to indicate random identifiers, with each pair of bytes corresponding to a random identifier. The order of these random identifiers is determined by the bit position. For example, if bit position 2 and bit position 5 are both 1, and the bits are arranged in ascending order of their bit positions, then the random identifier corresponding to bit position 2 will come first, followed by the random identifier corresponding to bit position 5.

[0131] If an AIoT device receives an AIoT Msg2 message, and the value of the bit position corresponding to the access timing used by Msg1 in the bitmap is 1, and the random identifier of the corresponding bit position in the second message is the same as the random identifier in the AIoT Msg1 message previously sent by the device, the AIoT device considers the contention resolution successful.

[0132] Methods 2-4: Similar to methods 1-3, Msg2 contains one or more random identifiers, as well as the entirety or partial device identifier corresponding to each random identifier. This method can be used when Msg1 contains higher-level data (such as device identifiers). It can also resolve conflicts caused by identical random identifiers. In general, the device determines whether Msg2 is intended for it by receiving all or part of the random identifiers and device identifiers carried in Msg2, and proceeds with subsequent transmissions accordingly.

[0133] AIoT devices determine whether the contention has been resolved successfully by determining whether the random identifier and (partial) device identifier match their own random identifier and (partial) device identifier.

[0134] Methods 2-5: Similar to methods 1-4, a predetermined number of bytes at a fixed position in each of the second messages (Msg2) contains a random identifier corresponding to a specific access opportunity. That is, the length of Msg2 is fixed; regardless of how many Msg1 messages are successfully received, two bytes at a fixed position in the Msg2 message will contain the random identifier corresponding to a particular access opportunity. In summary, the device determines whether Msg2 is intended for it by receiving the random identifier carried in it and its position within the message, and proceeds with subsequent transmissions accordingly.

[0135] For example, the device can be pre-configured or instructed in the R2D trigger message to assign sequence numbers (e.g., 0-7) to each access opportunity. Then, Msg2 will always contain 16 bytes, with each two bytes corresponding to a random identifier received on an access opportunity with a given sequence number. If an access opportunity does not receive Msg1, the corresponding two bytes will have a value of 0. The device can find the corresponding byte position in Msg2 based on the access opportunity used by Msg1, decode it, and then determine whether the random identifier in the message matches its own random identifier.

[0136] In some examples of Method 2, if all device response messages are transmitted in a single Msg2 message, then the device only needs to listen for the next Msg2 message after sending Msg1.

[0137] In other examples of Method 2, if the reader cannot place all Msg1 response information into a single Msg2 MAC PDU due to transport block size limitations, then it can be transmitted in multiple PRDCHs. Each PRDCH contains a portion of the Msg2 content that needs to be responded to (such as the multiple random identifiers mentioned in the sub-methods above), meaning multiple Msg2 responses are used to address the device. In this case, the methods 2-1, 2-2, 2-3, 2-4, and 2-5 still apply. Furthermore, the grouping of response information needs to be specified, and the monitoring of Msg2 can be enhanced, for example, using options 2a-1, 2a-2, and 2a-3 as follows.

[0138] Option 2a-1: The reader may group the random identifiers to be sent (e.g., based on the implementation, divide the random identifiers to be sent into at least 2 groups) and send the multiple groups of random identifiers using multiple Msg2s.

[0139] The first terminal device can use options 1 to 3 in Method 1 to listen to and stop listening to multiple Msg2.

[0140] The first of the plurality of second messages (Msg2) carries information indicating the number of second messages (Msg2).

[0141] For example, each second message (Msg2) carries 1 bit of information to indicate whether the transmission of multiple second messages (Msg2) has ended. This 1 bit is an extension bit (E bit). A first value indicates that the transmission of multiple second messages (Msg2) has not ended, while a second value indicates that the transmission of multiple second messages (Msg2) has ended.

[0142] For example, the first terminal device uses a first timer to determine whether to continue listening for the second message (Msg2).

[0143] For example, after the first terminal device sends the first message (AIoT Msg1):

[0144] The first terminal device continuously listens for the second message (Msg2); or,

[0145] The first terminal device stops listening to the second message (Msg2) if at least one of the following conditions is met:

[0146] The competition was successfully resolved;

[0147] Received the next Reader to Terminal Device (R2D) trigger message;

[0148] The second message (Msg2) being monitored indicates that there will be no next second message (Msg2);

[0149] The first timer times out, which is used to determine whether to continue listening for the second message (Msg2).

[0150] Option 2a-2: Use one Msg2 message for each Msg1 response received on each time-domain resource. That is, one Msg2 message contains one or more random identifiers of one or more Msg1 messages received during the access time on the same time-domain resource. Since the device knows the number of time-domain resources used for the Msg1 access time, it also knows the number of Msg2 messages and can therefore listen for Msg2 messages at the appropriate times. For example, if Msg2 messages are sent consecutively, the two time-domain resources in Figure 5 correspond to two Msg2 messages. If the device sends an Msg1 message on the second time-domain resource, it can ignore the first Msg2 message upon receiving it and wait to receive the second Msg2 message. Alternatively, it can receive the R2D control information of the first Msg2 message to obtain the end time of the R2D message, and then continue listening for the second Msg2 message after the end time. In other words, it can hibernate after receiving the control information of the first Msg2 message and wake up after the expected message end, thus saving energy.

[0151] Options 2a-3: For devices that support IF-ED (Intermediate Frequency-Envelope Detector) or ZIF (Zero IF) receivers, such as type 2b devices, frequency division multiplexing can be used for Msg2 transmission. One Msg2 message is used for each response message received on each frequency domain resource, and this message is transmitted on that same frequency domain resource. The device can then listen for Msg2 on the frequency band used by Msg1 after transmitting Msg1.

[0152] The following describes the transmission design for a third message (e.g., Msg3) through Example 2.

[0153] Example 2:

[0154] Since multiple devices access the network during a single slot, their responses to one or more Msg2 sets during access are handled by Msg3. How to multiplex Msg3 D2R transmissions from multiple devices, such as FDMA and / or TDMA, requires scheduling by a reader. Example 2 addresses how to use scheduling information to allocate time-frequency resources for Msg3. Example 2 can be used in conjunction with the Msg2 transmission method in Example 1.

[0155] In one embodiment of Example 2, the reader can use explicit scheduling information to allocate the time-frequency resources of the device's Msg3.

[0156] For example, regarding method 2 in Embodiment 1, if a Msg2 message contains response information from all successfully accessed devices, then the Msg2(PRDCH) can contain scheduling information for Msg3 from all successfully accessed devices. This scheduling information can include information related to a device's time-domain resources, frequency-domain resources, modulation and coding scheme, chip duration, device-associated identifier (e.g., the device's access layer identifier), and repetition count. In the examples below, the scheduling information has the same meaning.

[0157] For example, in method 1 of embodiment 1, Msg2 contains terminal device to reader (D2R) scheduling information of the first terminal device responding to the third message (Msg3).

[0158] For example, in the scenario of multiple Msg2s in method 2 of embodiment 1, each Msg2 contains scheduling information about Msg3 for all devices responding to that Msg2.

[0159] In another embodiment of Example 2, when there are multiple Msg2 messages, the last Msg2 message schedules the Msg3 message for all successfully connected devices, that is, it contains the scheduling information for the Msg3 messages of all successfully connected devices. This can bring the scheduling information as close as possible to the actual scheduling time, avoiding device time offset caused by sending the scheduling information too early.

[0160] In another embodiment of Example 2, time-frequency resources can be allocated to Msg3 implicitly. This eliminates the need for the reader to send scheduling information.

[0161] The first terminal device uses the same frequency resource as Msg1 (the frequency band corresponding to the access timing selected by Msg1) as the frequency domain resource for Msg3 transmission, and the relative time offset corresponding to the time domain resource used by Msg1 as the time domain resource for Msg3. For example, in method 2, if the device selects the second time domain resource for Msg1, it can estimate the time it takes for other devices to send one Msg3 (i.e., add a time offset after receiving Msg2), and then transmit Msg3 in the selected frequency band.

[0162] In another embodiment of Example 2, scheduling can be performed using implicit indication with frequency domain resources and explicit indication with time resources, which can save some signaling overhead. For specific combinations, please refer to the above description.

[0163] Second aspect of the embodiments

[0164] The random access method of this application embodiment is applied to a first terminal device. This random access method 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.

[0165] Figure 8 is a schematic diagram of a method for supporting random access according to an embodiment of the second aspect of this application. As shown in Figure 8, the method for supporting random access includes:

[0166] 801. Send the first message (AIoT Msg1) to the reader; and

[0167] 802. Receive a second message (Msg2) via a Physical Reader-to-Device Channel (PRDCH), wherein one of the Physical Reader-to-Device Channels (PRDCH) corresponds to the first message sent by at least one of the first terminal devices.

[0168] In some embodiments, a Physical Reader to Device Channel (PRDCH) corresponds to a first message received from a first terminal device.

[0169] In some embodiments, each of the second messages (Msg2) includes a random identifier that is equal to a random identifier sent by the first terminal device in the first message (Msg1).

[0170] In some embodiments, each of the second messages (Msg2) includes a random identifier and first information indicating the corresponding access timing.

[0171] In some embodiments, if the first terminal device receives the second message (Msg2), and the random identifier contained in the second message is the same as the random identifier in the first message (Msg1) previously sent by the first terminal device, and the first information contained in the second message (Msg2) corresponds to the access timing used by the first message (Msg1), the first terminal device determines that the contention resolution is successful.

[0172] In some embodiments, the first information is a sequence number or index corresponding to the access timing.

[0173] In some embodiments, each of the second messages (Msg2) includes a random identifier and all or part of a device identifier; or

[0174] The second message (Msg2) is received using the pre-configured time resources corresponding to the access opportunity.

[0175] In some embodiments, multiple of the second messages (Msg2) are received continuously in a slot of an Ambient Internet of Things (AIoT) paging.

[0176] In some embodiments, the first of a plurality of second messages (Msg2) carries information indicating the number of second messages (Msg2).

[0177] In some embodiments, each of the second messages (Msg2) carries 1 bit of information to indicate whether the transmission of the plurality of second messages (Msg2) has ended.

[0178] In some embodiments, the 1-bit information is an extension bit (E bit).

[0179] Wherein, the 1 bit information having a first value indicates that the transmission of multiple second messages (Msg2) has not ended, and the 1 bit information having a second value indicates that the transmission of multiple second messages (Msg2) has ended.

[0180] In some embodiments, the first terminal device uses a first timer to determine whether to continue listening for the second message (Msg2).

[0181] In some embodiments, after the first terminal device sends the first message (AIoT Msg1):

[0182] The first terminal device continuously listens for the second message (Msg2); or,

[0183] The first terminal device stops listening to the second message (Msg2) if at least one of the following conditions is met:

[0184] The competition was successfully resolved;

[0185] Received the next Reader to Terminal Device (R2D) trigger message;

[0186] The second message (Msg2) being monitored indicates that there is no next second message (Msg2);

[0187] The first timer times out, wherein the first timer is used to determine whether to continue listening for the second message (Msg2).

[0188] In some embodiments, the random access method further includes:

[0189] After each of the second messages (Msg2) and before the next second message, a third message (Msg3) sent by the first terminal device corresponding to the previous second message (Msg2) is sent to the reader; and / or

[0190] Receive the fourth message (Msg4) sent by the reader; and / or

[0191] Send terminal device to reader (D2R) data to the reader.

[0192] In some embodiments, the first terminal device continuously listens to each of the second messages (Msg2) to obtain contention resolution information belonging to the first terminal device, and transmits the third message (Msg3) if the contention is successfully resolved.

[0193] In some embodiments, the first terminal device listens to the second message (Msg2) and receives the scheduling information in the second message to obtain the time resource information used by the terminal device to reader (D2R) message after the reader to terminal device (R2D) message. If the second message (Msg2) is not sent to the first terminal device, the first terminal device predicts the end time of the terminal device to reader (D2R) messages of other terminal devices, and then starts listening to the next reader to terminal device (R2D) message at the end time.

[0194] In some embodiments, one of the physical reader-to-device channels (PRDCH) corresponds to one or more of the first messages received from one or more of the first terminal devices.

[0195] In some embodiments, each of the second messages (Msg2) contains one or more random identifiers, each random identifier corresponding to a random identifier of the first terminal device.

[0196] In some embodiments, each of the second messages (Msg2) includes one or more random identifiers, and first information corresponding to each random identifier for indicating the access timing associated with that random identifier.

[0197] In some embodiments, if the first terminal device receives the second message (Msg2), and a random identifier contained in the second message is the same as the random identifier in the first message (Msg1) previously sent by the first terminal device, and the first information corresponding to the random identifier contained in the second message (Msg2) corresponds to the access timing used by the first message (Msg1), the first terminal device determines that the contention resolution is successful.

[0198] In some embodiments, the first information is a sequence number or index corresponding to the access timing.

[0199] In some embodiments, each of the second messages (Msg2) contains one or more random identifiers and a bitmap.

[0200] In some embodiments, the number of bits in the bitmap is the number of access opportunities allocated for the first message (Msg1), each bit position in the bitmap corresponds to one access opportunity, and the bit value of the bit position is used to indicate whether the second message contains a random identifier received during that access opportunity.

[0201] In some embodiments, if the first terminal device receives a second message (Msg2), the value of the bit position corresponding to the access timing used by the first message (Msg1) in the bitmap is 1, and the random identifier corresponding to the bit position in the second message is the same as the random identifier in the first message (Msg1) previously sent by the first terminal device, the first terminal device determines that the contention has been successfully resolved.

[0202] In some embodiments, each of the second messages (Msg2) includes one or more random identifiers, and all or part of a device identifier corresponding to each random identifier; or

[0203] Each second message (Msg2) contains a predetermined number of bytes at a fixed position, which contains a random identifier corresponding to a specific access opportunity.

[0204] In some embodiments, one or more of the second messages (Msg2) are received via one or more of the Physical Reader to Device Channel (PRDCH).

[0205] In some embodiments, the first of a plurality of second messages (Msg2) carries information indicating the number of second messages (Msg2).

[0206] In some embodiments, each of the second messages (Msg2) carries 1 bit of information to indicate whether the transmission of the plurality of second messages (Msg2) has ended.

[0207] In some embodiments, the 1-bit information is an extension bit (E bit), wherein the 1-bit information having a first value indicates that the transmission of multiple second messages (Msg2) has not ended, and the 1-bit information having a second value indicates that the transmission of multiple second messages (Msg2) has ended.

[0208] In some embodiments, the first terminal device uses a first timer to determine whether to continue listening for the second message (Msg2).

[0209] In some embodiments, after the first terminal device sends the first message (AIoT Msg1):

[0210] The first terminal device continuously listens for the second message (Msg2); or,

[0211] The first terminal device stops listening to the second message (Msg2) if at least one of the following conditions is met:

[0212] The competition was successfully resolved;

[0213] Received the next Reader to Terminal Device (R2D) trigger message;

[0214] The second message (Msg2) being monitored indicates that there is no next second message (Msg2);

[0215] The first timer times out, wherein the first timer is used to determine whether to continue listening for the second message (Msg2).

[0216] In some embodiments, the reader divides the random identifiers to be sent into at least two groups and sends the at least two groups using a plurality of the second message (Msg2).

[0217] In some embodiments, a response message to the first message (Msg1) sent on each time-domain resource is received using a second message (Msg2); or

[0218] The response message to the first message (Msg1) received on each frequency domain resource is received using a second message (Msg2), and the second message (Msg2) is received using the frequency domain resource.

[0219] In some embodiments, the second message (Msg2) includes scheduling information for a third message (Msg3) for all successfully accessed first terminal devices.

[0220] In some embodiments, the scheduling information includes at least one of the following information for at least one of the first terminal devices:

[0221] Time domain resources, frequency domain resources, modulation and coding scheme related information, chip duration, device-associated identifier, and repetition count.

[0222] In some embodiments, the second message (Msg2) includes terminal device to reader (D2R) scheduling information of the first terminal device responding to the second message (Msg2) regarding the third message (Msg3); or

[0223] In the case of receiving multiple second messages (Msg2), each second message (Msg2) contains scheduling information about the third message (Msg3) from all the first terminal devices that responded to the second message (Msg2); or

[0224] In the event that multiple second messages (Msg2) are received, the last second message (Msg2) schedules the third message (Msg3) for all successfully accessed first terminal devices.

[0225] Third aspect of the embodiments

[0226] This application provides a random access device applied to a reader. This device corresponds to the method applied to a reader in the first aspect embodiment, and the contents identical to those in the first aspect embodiment will not be repeated.

[0227] Figure 9 is a schematic diagram of a device supporting random access according to an embodiment of this application. As shown in Figure 9, the device 900 supporting random access includes a first receiving module 901 (e.g., a receiver) and a first transmitting module 902 (e.g., a transmitter).

[0228] The first receiving module 901 receives a first message (AIoT Msg1) from the first terminal device; and

[0229] The first sending module 902 sends a second message (Msg2) using a Physical Reader-to-Device Channel (PRDCH), wherein one of the PRDCHs corresponds to the first message received from at least one of the first terminal devices.

[0230] In some embodiments, a Physical Reader to Device Channel (PRDCH) corresponds to a first message received from a first terminal device.

[0231] In some embodiments, each of the second messages (Msg2) includes a random identifier that is equal to a random identifier sent by the first terminal device in the first message (Msg1).

[0232] In some embodiments, each of the second messages (Msg2) includes a random identifier and first information indicating the corresponding access timing.

[0233] In some embodiments, if the first terminal device receives the second message (Msg2), and the random identifier contained in the second message is the same as the random identifier in the first message (Msg1) previously sent by the first terminal device, and the first information contained in the second message (Msg2) corresponds to the access timing used by the first message (Msg1), the first terminal device determines that the contention resolution is successful.

[0234] In some embodiments, the first information is a sequence number or index corresponding to the access timing.

[0235] In some embodiments, each of the second messages (Msg2) includes a random identifier and all or part of a device identifier; or

[0236] The second message (Msg2) is transmitted using the pre-configured time resources corresponding to the access opportunity.

[0237] In some embodiments, the first sending module continuously sends multiple second messages (Msg2) in a slot of an Ambient Internet of Things (AIoT) paging.

[0238] In some embodiments, the first of a plurality of second messages (Msg2) carries information indicating the number of second messages (Msg2).

[0239] In some embodiments, each of the second messages (Msg2) carries 1 bit of information to indicate whether the transmission of the plurality of second messages (Msg2) has ended.

[0240] In some embodiments, the 1-bit information is an extension bit (E bit).

[0241] Wherein, the 1 bit information having a first value indicates that the transmission of multiple second messages (Msg2) has not ended, and the 1 bit information having a second value indicates that the transmission of multiple second messages (Msg2) has ended.

[0242] In some embodiments, the first terminal device uses a first timer to determine whether to continue listening for the second message (Msg2).

[0243] In some embodiments, after the first terminal device sends the first message (AIoT Msg1):

[0244] The first terminal device continuously listens for the second message (Msg2); or,

[0245] The first terminal device stops listening to the second message (Msg2) if at least one of the following conditions is met:

[0246] The competition was successfully resolved;

[0247] Received the next Reader to Terminal Device (R2D) trigger message;

[0248] The second message (Msg2) being monitored indicates that there is no next second message (Msg2);

[0249] The first timer times out, wherein the first timer is used to determine whether to continue listening for the second message (Msg2).

[0250] In some embodiments, after each of the second messages (Msg2) and before the next second message, the first receiving module reads the third message (Msg3) sent by the first terminal device corresponding to the previous second message (Msg2); and / or

[0251] The first sending module sends a fourth message (Msg4) to the first terminal device; and / or

[0252] The first receiving module receives terminal device to reader (D2R) data sent by the first terminal device.

[0253] In some embodiments, the first terminal device continuously listens to each of the second messages (Msg2) to obtain contention resolution information belonging to the first terminal device, and transmits the third message (Msg3) if the contention is successfully resolved.

[0254] In some embodiments, the first terminal device listens to the second message (Msg2) and receives the scheduling information in the second message to obtain the time resource information used by the terminal device to reader (D2R) message after the reader to terminal device (R2D) message.

[0255] If the second message (Msg2) is not sent to the first terminal device, the first terminal device predicts the end time of subsequent terminal device to reader (D2R) messages from other terminal devices, and then starts listening for the next reader to terminal device (R2D) message at the end time.

[0256] In some embodiments, one of the physical reader-to-device channels (PRDCH) corresponds to one or more of the first messages received from one or more of the first terminal devices.

[0257] In some embodiments, each of the second messages (Msg2) contains one or more random identifiers, each random identifier corresponding to a random identifier of the first terminal device.

[0258] In some embodiments, each of the second messages (Msg2) includes one or more random identifiers, and first information corresponding to each random identifier for indicating the access timing associated with that random identifier.

[0259] In some embodiments, if the first terminal device receives the second message (Msg2), and a random identifier contained in the second message is the same as the random identifier in the first message (Msg1) previously sent by the first terminal device, and the first information corresponding to the random identifier contained in the second message (Msg2) corresponds to the access timing used by the first message (Msg1), the first terminal device determines that the contention resolution is successful.

[0260] In some embodiments, the first information is a sequence number or index corresponding to the access timing.

[0261] In some embodiments, each of the second messages (Msg2) contains one or more random identifiers and a bitmap.

[0262] In some embodiments, the number of bits in the bitmap is the number of access opportunities allocated for the first message (Msg1), each bit position in the bitmap corresponds to one access opportunity, and the bit value of the bit position is used to indicate whether the second message contains a random identifier received during that access opportunity.

[0263] In some embodiments, if the first terminal device receives a second message (Msg2), the value of the bit position corresponding to the access timing used by the first message (Msg1) in the bitmap is 1, and the random identifier corresponding to the bit position in the second message is the same as the random identifier in the first message (Msg1) previously sent by the first terminal device, the first terminal device determines that the contention has been successfully resolved.

[0264] In some embodiments, each of the second messages (Msg2) includes one or more random identifiers, and all or part of a device identifier corresponding to each random identifier; or

[0265] Each second message (Msg2) contains a predetermined number of bytes at a fixed position, which contains a random identifier corresponding to a specific access opportunity.

[0266] In some embodiments, the first sending module sends one or more of the second messages (Msg2) through one or more of the Physical Reader to Device Channel (PRDCH).

[0267] In some embodiments, the first of a plurality of second messages (Msg2) carries information indicating the number of second messages (Msg2).

[0268] In some embodiments, each of the second messages (Msg2) carries 1 bit of information to indicate whether the transmission of the plurality of second messages (Msg2) has ended.

[0269] In some embodiments, the 1-bit information is an extension bit (E bit).

[0270] Wherein, the 1 bit information having a first value indicates that the transmission of multiple second messages (Msg2) has not ended, and the 1 bit information having a second value indicates that the transmission of multiple second messages (Msg2) has ended.

[0271] In some embodiments, the first terminal device uses a first timer to determine whether to continue listening for the second message (Msg2).

[0272] In some embodiments, after the first terminal device sends the first message (AIoT Msg1):

[0273] The first terminal device continuously listens for the second message (Msg2); or,

[0274] The first terminal device stops listening to the second message (Msg2) if at least one of the following conditions is met:

[0275] The competition was successfully resolved;

[0276] Received the next Reader to Terminal Device (R2D) trigger message;

[0277] The second message (Msg2) being monitored indicates that there is no next second message (Msg2);

[0278] The first timer times out, wherein the first timer is used to determine whether to continue listening for the second message (Msg2).

[0279] In some embodiments, the first sending module divides the random identifiers to be sent into at least two groups and sends the at least two groups using multiple second messages (Msg2).

[0280] In some embodiments, a response message to the first message (Msg1) received on each time-domain resource is sent using a second message (Msg2); or

[0281] A response message to the first message (Msg1) received on each frequency domain resource is sent using a second message (Msg2), and the second message (Msg2) is sent using the frequency domain resource.

[0282] In some embodiments, the second message (Msg2) includes scheduling information for a third message (Msg3) for all successfully accessed first terminal devices.

[0283] In some embodiments, the scheduling information includes at least one of the following information for at least one of the first terminal devices:

[0284] Time domain resources, frequency domain resources, modulation and coding scheme related information, chip duration, device-associated identifier, and repetition count.

[0285] In some embodiments, the second message (Msg2) includes terminal device to reader (D2R) scheduling information of the first terminal device responding to the second message (Msg2) regarding the third message (Msg3); or

[0286] In the case of sending multiple second messages (Msg2), each second message (Msg2) contains scheduling information about the third message (Msg3) from all the first terminal devices that responded to the second message (Msg2); or

[0287] In the case of sending multiple second messages (Msg2), the last second message (Msg2) schedules the third message (Msg3) of all successfully accessed first terminal devices.

[0288] Fourth aspect of the embodiment

[0289] This application provides an apparatus for supporting random access, applied to a first terminal device. This apparatus corresponds to the method applied to the first terminal device in the second aspect embodiment, and the contents identical to those in the second aspect embodiment will not be repeated.

[0290] Figure 10 is a schematic diagram of a device supporting random access according to an embodiment of this application. As shown in Figure 10, the random access device 1000 includes a second receiving module 1001 (e.g., a receiver) and a second transmitting module 1002 (e.g., a transmitter). In addition, the random access device 1000 may also include a processing module 1003.

[0291] In some embodiments, the second sending module 1002 sends a first message (AIoT Msg1) to the reader; the second receiving module 1001 receives a second message (Msg2) through a Physical Reader-to-Device Channel (PRDCH), wherein one PRDCH corresponds to at least one first message sent by the second sending module.

[0292] In some embodiments, a Physical Reader to Device Channel (PRDCH) corresponds to a first message sent by a first terminal device.

[0293] In some embodiments, each of the second messages (Msg2) contains a random identifier that is equal to a random identifier sent by the second sending module in the first message (Msg1).

[0294] In some embodiments, each of the second messages (Msg2) includes a random identifier and first information indicating the corresponding access timing.

[0295] In some embodiments, if the second receiving module receives the second message (Msg2), and the random identifier contained in the second message is the same as the random identifier in the first message (Msg1) previously sent by the second sending module, and the first information contained in the second message (Msg2) corresponds to the access timing used by the first message (Msg1), the processing module of the device determines that the contention resolution is successful.

[0296] In some embodiments, the first information is a sequence number or index corresponding to the access timing.

[0297] In some embodiments, each of the second messages (Msg2) includes a random identifier and all or part of a device identifier; or

[0298] The second message (Msg2) is received using the pre-configured time resources corresponding to the access opportunity.

[0299] In some embodiments, multiple of the second messages (Msg2) are received continuously in a slot of an Ambient Internet of Things (AIoT) paging.

[0300] In some embodiments, the first of a plurality of second messages (Msg2) carries information indicating the number of second messages (Msg2).

[0301] In some embodiments, each of the second messages (Msg2) carries 1 bit of information to indicate whether the transmission of the plurality of second messages (Msg2) has ended.

[0302] In some embodiments, the 1-bit information is an extension bit (E bit), wherein the 1-bit information having a first value indicates that the transmission of multiple second messages (Msg2) has not ended, and the 1-bit information having a second value indicates that the transmission of multiple second messages (Msg2) has ended.

[0303] In some embodiments, the processing module of the device uses a first timer to determine whether to continue listening for the second message (Msg2).

[0304] In some embodiments, after the second sending module sends the first message (AIoT Msg1):

[0305] The second receiving module continuously listens for the second message (Msg2); or,

[0306] The second receiving module stops listening to the second message (Msg2) if at least one of the following conditions is met:

[0307] The competition was successfully resolved;

[0308] Received the next Reader to Terminal Device (R2D) trigger message;

[0309] The second message (Msg2) being monitored indicates that there is no next second message (Msg2);

[0310] The first timer times out, wherein the first timer is used to determine whether to continue listening for the second message (Msg2).

[0311] In some embodiments, after each of the second messages (Msg2) and before the next second message, a third message (Msg3) sent by the first terminal device corresponding to the previous second message (Msg2) is sent to the reader; and / or

[0312] Receive the fourth message (Msg4) sent by the reader; and / or

[0313] Send terminal device to reader (D2R) data to the reader.

[0314] In some embodiments, the second receiving module continuously listens to each of the second messages (Msg2) to obtain contention resolution information belonging to the first terminal device, and transmits the third message (Msg3) if the contention is successfully resolved.

[0315] In some embodiments, the second receiving module listens to the second message (Msg2) and receives the scheduling information in the second message to obtain the time resource information used by the terminal device to reader (D2R) message after the reader to terminal device (R2D) message.

[0316] If the second message (Msg2) is not sent to the first terminal device, the processing module of the device predicts the end time of subsequent terminal device to reader (D2R) messages for other terminal devices, and then starts listening for the next reader to terminal device (R2D) message at the end time.

[0317] In some embodiments, one of the physical reader-to-device channels (PRDCH) corresponds to one or more of the first messages sent from one or more of the first terminal devices.

[0318] In some embodiments, each of the second messages (Msg2) contains one or more random identifiers, each random identifier corresponding to a random identifier of the first terminal device.

[0319] In some embodiments, each of the second messages (Msg2) includes one or more random identifiers, and first information corresponding to each random identifier for indicating the access timing associated with that random identifier.

[0320] In some embodiments, if the second receiving module receives the second message (Msg2), and a random identifier contained in the second message is the same as the random identifier in the first message (Msg1) previously sent by the second sending module, and the first information corresponding to the random identifier contained in the second message (Msg2) corresponds to the access timing used by the first message (Msg1), the processing module of the device determines that the contention resolution is successful.

[0321] In some embodiments, the first information is a sequence number or index corresponding to the access timing.

[0322] In some embodiments, each of the second messages (Msg2) contains one or more random identifiers and a bitmap.

[0323] In some embodiments, the number of bits in the bitmap is the number of access opportunities allocated for the first message (Msg1), each bit position in the bitmap corresponds to one access opportunity, and the bit value of the bit position is used to indicate whether the second message contains a random identifier received during that access opportunity.

[0324] In some embodiments, if the second receiving module receives a second message (Msg2) in the bit diagram where the value of the bit position corresponding to the access timing used by the first message (Msg1) is 1, and the random identifier in the second message corresponding to the bit position is the same as the random identifier in the first message (Msg1) previously sent by the second sending module, the processing module of the device determines that the contention has been successfully resolved.

[0325] In some embodiments, each of the second messages (Msg2) includes one or more random identifiers, and all or part of a device identifier corresponding to each random identifier; or

[0326] Each second message (Msg2) contains a predetermined number of bytes at a fixed position, which contains a random identifier corresponding to a specific access opportunity.

[0327] In some embodiments, one or more of the second messages (Msg2) are received via one or more of the Physical Reader to Device Channel (PRDCH).

[0328] In some embodiments, the first of a plurality of second messages (Msg2) carries information indicating the number of second messages (Msg2).

[0329] In some embodiments, each of the second messages (Msg2) carries 1 bit of information to indicate whether the transmission of the plurality of second messages (Msg2) has ended.

[0330] In some embodiments, the 1-bit information is an extension bit (E bit).

[0331] Wherein, the 1 bit information having a first value indicates that the transmission of multiple second messages (Msg2) has not ended, and the 1 bit information having a second value indicates that the transmission of multiple second messages (Msg2) has ended.

[0332] In some embodiments, the processing module of the device uses a first timer to determine whether to continue listening for the second message (Msg2).

[0333] In some embodiments, after the second sending module sends the first message (AIoT Msg1):

[0334] The second receiving module continuously listens for the second message (Msg2); or,

[0335] The second receiving module stops listening to the second message (Msg2) if at least one of the following conditions is met:

[0336] The competition was successfully resolved;

[0337] Received the next Reader to Terminal Device (R2D) trigger message;

[0338] The second message (Msg2) being monitored indicates that there is no next second message (Msg2);

[0339] The first timer times out, wherein the first timer is used to determine whether to continue listening for the second message (Msg2).

[0340] In some embodiments, the reader divides the random identifiers to be sent into at least two groups and sends the at least two groups using a plurality of the second message (Msg2).

[0341] In some embodiments, a response message to the first message (Msg1) sent on each time-domain resource is received using a second message (Msg2); or

[0342] The response message to the first message (Msg1) received on each frequency domain resource is received using a second message (Msg2), and the second message (Msg2) is received using the frequency domain resource.

[0343] In some embodiments, the second message (Msg2) includes scheduling information for a third message (Msg3) for all successfully accessed first terminal devices.

[0344] In some embodiments, the scheduling information includes at least one of the following information for at least one of the first terminal devices:

[0345] Time domain resources, frequency domain resources, modulation and coding scheme related information, chip duration, device-associated identifier, and repetition count.

[0346] In some embodiments, the second message (Msg2) includes terminal device to reader (D2R) scheduling information of the first terminal device responding to the second message (Msg2) regarding the third message (Msg3); or

[0347] In the case of receiving multiple second messages (Msg2), each second message (Msg2) contains scheduling information about the third message (Msg3) from all the first terminal devices that responded to the second message (Msg2); or

[0348] In the event that multiple second messages (Msg2) are received, the last second message (Msg2) schedules the third message (Msg3) for all successfully accessed first terminal devices.

[0349] Fifth aspect of the embodiment

[0350] An embodiment of the fifth aspect of this application provides a communication system that may include a first terminal device (e.g., an environmental IoT device) and a reader. The reader may be located in a network device or a second terminal device.

[0351] Among them, at least one of the first terminal device, the network device, and the second terminal device may have the schematic diagram of the electronic device shown in Figure 11.

[0352] As shown in Figure 11, the electronic device 1100 may correspond to the terminal device 102 or network device 101 of Figure 1. The electronic device 1100 may include a processor 1110 and a memory 1120; the memory 1120 stores data and programs and is coupled to the processor 1110. It is worth noting that this figure is exemplary; other types of structures may also be used to supplement or replace this structure to achieve telecommunications functions or other functions.

[0353] For example, processor 1110 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.

[0354] As shown in Figure 11, the terminal device 1100 may further include: a communication module 1130, an input unit 1140, a display 1150, and a power supply 1160. The functions of these components are similar to those in the prior art and will not be described again here. It is worth noting that the terminal device 1100 does not necessarily include all the components shown in Figure 11; these components are not essential. Furthermore, the terminal device 1100 may also include components not shown in Figure 11, which can be referred to in the prior art.

[0355] This application also provides a computer program, wherein when the program is executed in at least one of a first terminal device and a reader, the program causes the device to perform a corresponding method to achieve a corresponding function.

[0356] This application embodiment also provides a storage medium storing a computer program, wherein when at least one of a first terminal device and a reader executes the program, the program causes the device to perform a corresponding method to achieve a corresponding function.

[0357] 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.

[0358] 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.

[0359] 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.

[0360] 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.

[0361] 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.

[0362] Regarding the implementation methods including the above embodiments, the following notes are also disclosed:

[0363] 1. A device supporting random access, applied to a reader, the device comprising:

[0364] The first receiving module receives a first message (AIoT Msg1) from the first terminal device; and

[0365] The first sending module sends a second message (Msg2) using a Physical Reader-to-Device Channel (PRDCH), wherein one of the PRDCHs corresponds to the first message received from at least one of the first terminal devices.

[0366] 2. The apparatus as described in Appendix 1, wherein,

[0367] One of the physical reader-to-device channels (PRDCH) corresponds to one of the first messages received from one of the first terminal devices.

[0368] 3. The apparatus as described in Appendix 2, wherein,

[0369] The first sending module continuously sends multiple second messages (Msg2) in one slot of the AIoT paging.

[0370] 4. The apparatus as described in Appendix 2, wherein,

[0371] After each of the second messages (Msg2) and before the next second message, the first receiving module reads the third message (Msg3) sent by the first terminal device corresponding to the previous second message (Msg2); and / or

[0372] The first sending module sends a fourth message (Msg4) to the first terminal device; and / or

[0373] The first receiving module receives the terminal device-to-reader (D2R) data sent by the first terminal device.

[0374] 5. The apparatus as described in Appendix 4, wherein,

[0375] The first terminal device continuously listens to each of the second messages (Msg2) to obtain contention resolution information belonging to the first terminal device, and transmits the third message (Msg3) if the contention is successfully resolved.

[0376] 6. The apparatus as described in Appendix 4, wherein,

[0377] The first terminal device listens to the second message (Msg2) and receives the scheduling information in the second message to obtain the time resource information used by the terminal device to reader (D2R) message after the reader to terminal device (R2D) message.

[0378] If the second message (Msg2) is not sent to the first terminal device, the first terminal device predicts the end time of subsequent terminal device to reader (D2R) messages from other terminal devices, and then starts listening for the next reader to terminal device (R2D) message at the end time.

[0379] 7. The apparatus as described in Appendix 1, wherein,

[0380] One of the Physical Reader to Device Channels (PRDCH) corresponds to one or more of the first messages received from one or more of the first terminal devices.

[0381] 8. The apparatus as described in Appendix 7, wherein,

[0382] The first sending module sends one or more of the second messages (Msg2) through one or more of the physical readers to the device channel (PRDCH).

[0383] 9. The apparatus as described in Appendix 8, wherein,

[0384] The first sending module divides the random identifiers to be sent into at least two groups and sends the at least two groups using multiple second messages (Msg2).

[0385] 10. The apparatus as described in Appendix 9, wherein,

[0386] For each time-domain resource, a response message to the first message (Msg1) received is sent using a second message (Msg2); or

[0387] A response message to the first message (Msg1) received on each frequency domain resource is sent using a second message (Msg2), and the second message (Msg2) is sent using the frequency domain resource.

Claims

An apparatus supporting random access, applied to a first terminal device, the apparatus comprising: The second sending module sends the first message (AIoT Msg1) to the reader; as well as The second receiving module receives a second message (Msg2) via a Physical Reader-to-Device Channel (PRDCH), wherein one PRDCH corresponds to at least one first message sent by the second sending module. The apparatus of claim 1, wherein, One of the Physical Reader to Device Channels (PRDCH) corresponds to one of the first messages sent by the first terminal device. The apparatus of claim 2, wherein, Each of the second messages (Msg2) contains a random identifier and first information indicating the corresponding access timing. The apparatus of claim 3, wherein, If the second receiving module receives the second message (Msg2), and the random identifier contained in the second message is the same as the random identifier in the first message (Msg1) previously sent by the second sending module, and the first information contained in the second message (Msg2) corresponds to the access timing used by the first message (Msg1), the processing module of the device determines that the contention has been successfully resolved. The apparatus of claim 1, wherein, One of the Physical Reader to Device Channels (PRDCH) corresponds to one or more of the first messages sent from one or more of the first terminal devices. The apparatus of claim 5, wherein, Each of the second messages (Msg2) contains one or more random identifiers, each random identifier corresponding to a random identifier of the first terminal device. The apparatus of claim 5, wherein, Each of the second messages (Msg2) contains one or more random identifiers, and first information corresponding to each random identifier for indicating the access timing associated with that random identifier. The apparatus of claim 7, wherein, If the second receiving module receives the second message (Msg2), the second message contains a The random identifier is the same as the random identifier in the first message (Msg1) previously sent by the second sending module, and the first information corresponding to the random identifier contained in the second message (Msg2) corresponds to the access timing used by the first message (Msg1). The processing module of the device determines that the contention is resolved successfully. The apparatus of claim 7, wherein, The first piece of information is the sequence number or index corresponding to the access timing. The apparatus of claim 5, wherein, Each of the second messages (Msg2) contains one or more random identifiers, as well as a bitmap. The apparatus of claim 10, wherein, The number of bits in the bitmap is the number of access opportunities allocated for the first message (Msg1). Each bit position in the bitmap corresponds to one access opportunity, and the bit value of the bit position is used to indicate whether the second message contains a random identifier received during that access opportunity. The apparatus of claim 11, wherein, If the second receiving module receives a second message (Msg2), and the value of the bit position corresponding to the access timing used by the first message (Msg1) in the bit diagram is 1, and the random identifier corresponding to the bit position in the second message is the same as the random identifier in the first message (Msg1) previously sent by the second sending module, the processing module of the device determines that the contention has been successfully resolved. The apparatus of claim 5, wherein, One or more of the second messages (Msg2) are received through one or more of the physical readers to the device channel (PRDCH). The apparatus of claim 13, wherein, The first of the plurality of second messages (Msg2) carries information indicating the number of second messages (Msg2). The apparatus of claim 13, wherein, Each of the second messages (Msg2) carries 1 bit of information to indicate whether the transmission of multiple second messages (Msg2) has ended. The apparatus of claim 13, wherein, The device's processing module uses a first timer to determine whether to continue listening for the second message (Msg2). The apparatus of claim 13, wherein, After the second sending module sends the first message (AIoT Msg1): The second receiving module continuously listens for the second message (Msg2); or, The second receiving module stops listening to the second message (Msg2) if at least one of the following conditions is met: The competition was successfully resolved; Received the next Reader to Terminal Device (R2D) trigger message; The second message (Msg2) being monitored indicates that there is no next second message (Msg2); The first timer times out, wherein the first timer is used to determine whether to continue listening for the second message (Msg2). The apparatus of claim 1, wherein, The second message (Msg2) contains scheduling information for the third message (Msg3) for all successfully accessed first terminal devices. The apparatus of claim 18, wherein, The scheduling information includes at least one of the following information for at least one of the first terminal devices: Time domain resources, frequency domain resources, modulation and coding scheme related information, chip duration, device-associated identifier, and repetition count. The apparatus of claim 19, wherein, The second message (Msg2) contains terminal device to reader (D2R) scheduling information of the first terminal device responding to the second message (Msg2) regarding the third message (Msg3); or In the case of receiving multiple second messages (Msg2), each second message (Msg2) contains scheduling information about the third message (Msg3) from all the first terminal devices that responded to the second message (Msg2); or In the event that multiple second messages (Msg2) are received, the last second message (Msg2) schedules the third message (Msg3) for all successfully accessed first terminal devices.

Images