Reader-to-device message design to trigger random access message 1 transmission
The R2D message optimizes Msg1 transmission in A-IoT devices by providing independent triggers, addressing inefficiencies in existing systems and enhancing communication efficiency and reliability.
Patent Information
- Application Number
- PCT/CN2025/093079
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-07
- Publication Date
- 2026-11-12
AI Technical Summary
Existing wireless communication systems face challenges in efficiently triggering message 1 (Msg1) transmission in random access procedures for Ambient Internet of Things (A-IoT) devices, particularly when there are failures or delays in receiving initial access messages, leading to inefficiencies and communication delays.
The introduction of a Reader-to-Device (R2D) message that includes parameters such as message type, transaction identifier, re-access indication, reader identifier, and device identifier, which is designed to trigger Msg1 transmission independently of paging messages, optimizing signaling processes and resource allocation for A-IoT devices.
The R2D message enhances flexibility, scalability, and resource efficiency, reduces communication delays, and ensures successful data exchange in R2D random access procedures by providing alternative triggers for Msg1 transmission.
Smart Images

Figure CN2025093079_12112026_PF_FP_ABST
Abstract
Description
READER-TO-DEVICE MESSAGE DESIGN TO TRIGGER RANDOM ACCESS MESSAGE 1 TRANSMISSIONFIELD
[0001] The present disclosure relates to wireless communication, and more specifically, to wireless communication between a reader and a device, such as an Internet of Things (IoT) device.BACKGROUND
[0002] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.
[0003] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. An example telecommunication standard is 5G New Radio (NR) . 5G NR is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (such as with Internet of Things (IoT) ) , and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB) , massive machine type communications (mMTC) , and ultra-reliable low latency communications (URLLC) . Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard.
[0004] Additional developments are desired for new standards, such as for communications with IoT devices in 6G telecommunication systems.SUMMARY
[0005] The systems, methods and devices of this disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein.
[0006] An example aspect includes a method of wireless communication, comprising transmitting a reader to device (R2D) message configured to trigger transmission of a message 1 message of a random access procedure at one or more ambient IoT devices, wherein the R2D message includes one or more of a message type, a transaction identifier, a re-access indication, a resource adjustment, a reader identifier, or a device identifier. The method further includes monitoring for reception of one or more message 1 messages from the one or more ambient IoT devices.
[0007] Another example aspect includes an apparatus for wireless communication, comprising one or more memories and one or more processors coupled with the one or more memories and configured to perform, individually or in any combination, the following actions. The one or more processors are configured to transmit a reader to device (R2D) message configured to trigger transmission of a message 1 message of a random access procedure at one or more ambient IoT devices, wherein the R2D message includes one or more of a message type, a transaction identifier, a re-access indication, a resource adjustment, a reader identifier, or a device identifier. The one or more processors are further configured to monitor for reception of one or more message 1 messages from the one or more ambient IoT devices.
[0008] Another example aspect includes an apparatus for wireless communication, comprising means for transmitting a reader to device (R2D) message configured to trigger transmission of a message 1 message of a random access procedure at one or more ambient IoT devices, wherein the R2D message includes one or more of a message type, a transaction identifier, a re-access indication, a resource adjustment, a reader identifier, or a device identifier. The apparatus further includes means for monitoring for reception of one or more message 1 messages from the one or more ambient IoT devices.
[0009] Another example aspect includes a computer-readable medium comprising stored instructions for wireless communication, wherein the instructions are executable by one or more processors, individually or in any combination, to transmit a reader to device (R2D) message configured to trigger transmission of a message 1 message of a random access procedure at one or more ambient IoT devices, wherein the R2D message includes one or more of a message type, a transaction identifier, a re-access indication, a resource adjustment, a reader identifier, or a device identifier. The instructions are further executable to monitor for reception of one or more message 1 messages from the one or more ambient IoT devices.
[0010] An example aspect includes a method of wireless communication, comprising receiving a reader to device (R2D) message configured to trigger transmission of a message 1 message of a random access procedure at one or more ambient IoT devices, wherein the R2D message includes one or more of a message type, a transaction identifier, a re-access indication, a resource adjustment, a reader identifier, or a device identifier. The method further includes transmitting the message 1 message based on reception of the R2D message.
[0011] Another example aspect includes an apparatus for wireless communication, comprising one or more memories and one or more processors coupled with the one or more memories and configured to perform, individually or in any combination, the following actions. The one or more processors are configured to receive a reader to device (R2D) message configured to trigger transmission of a message 1 message of a random access procedure at one or more ambient IoT devices, wherein the R2D message includes one or more of a message type, a transaction identifier, a re-access indication, a resource adjustment, a reader identifier, or a device identifier. The one or more processors are further configured to transmit the message 1 message based on reception of the R2D message.
[0012] Another example aspect includes an apparatus for wireless communication, comprising means for receiving a reader to device (R2D) message configured to trigger transmission of a message 1 message of a random access procedure at one or more ambient IoT devices, wherein the R2D message includes one or more of a message type, a transaction identifier, a re-access indication, a resource adjustment, a reader identifier, or a device identifier. The apparatus further includes means for transmitting the message 1 message based on reception of the R2D message.
[0013] Another example aspect includes a computer-readable medium comprising stored instructions for wireless communication, wherein the instructions are executable by one or more processors, individually or in any combination, to receive a reader to device (R2D) message configured to trigger transmission of a message 1 message of a random access procedure at one or more ambient IoT devices, wherein the R2D message includes one or more of a message type, a transaction identifier, a re-access indication, a resource adjustment, a reader identifier, or a device identifier. The instructions are further executable to transmit the message 1 message based on reception of the R2D message.
[0014] Details of one or more implementations of the subject matter described in this disclosure are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages will become apparent from the description, the drawings and the claims. Note that the relative dimensions of the following figures may not be drawn to scale.BRIEF DESCRIPTION OF THE DRAWINGS
[0015] The disclosed aspects are described in conjunction with the appended drawings, which are provided to illustrate and not to limit the disclosed aspects, and in which like designations denote like elements, and wherein dashed lines may indicate optional elements.
[0016] FIG. 1 is a diagram illustrating an example of a wireless communications system including one or more reader devices transmitting a reader-to-device (R2D) message configured to initiate transmission of the random access procedure message 1 (Msg1) by one or more ambient-Internet of Things (A-IoT devices) , according to aspects of the present disclosure.
[0017] FIG. 2A is a diagram illustrating an example of a first frame.
[0018] FIG. 2B is a diagram illustrating an example of downlink (DL) channels within a subframe.
[0019] FIG. 2C is a diagram illustrating an example of a second frame.
[0020] FIG. 2D is a diagram illustrating an example of a subframe.
[0021] FIG. 3 is a diagram illustrating an example of a base station (BS) and user equipment (UE) in a wireless communication system.
[0022] FIG. 4 is a diagram illustrating an example disaggregated base station architecture.
[0023] FIG. 5 is an example structure of an R2D message that may be utilized in the wireless communication system of Fig. 1.
[0024] FIG. 6 is an example structure of an R2D medium access control (MAC) protocol data unit (PDU) including the R2 message structure of Fig. 5.
[0025] FIG. 7 is an example structure of an R2D MAC PDU including a MAC header carrying the R2 message structure of Fig. 5.
[0026] FIG. 8 is an example structure of an R2D MAC PDU including a MAC subPDU having a MAC control element (CE) carrying the R2 message structure of Fig. 5.
[0027] FIG. 9 is an example structure of an R2D MAC PDU including multiple MAC CEs each carrying a portion of the R2 message structure of Fig. 5.
[0028] FIG. 10 is an example structure of an R2D MAC PDU including a MACE header and a MAC CE each carrying a portion of the R2 message structure of Fig. 5.
[0029] FIG. 11 is an example structure of an R2D layer 1 (L1) control field and an R2D MAC PDU, e.g., in a MAC CE, each carrying a portion of the R2 message structure of Fig. 5.
[0030] FIG. 12 is an example structure of an R2D L1 control field carrying the R2 message structure of Fig. 5.
[0031] FIG. 13 is a example R2D messaging timeline of R2D random access control messages and resources over time, including the R2D message occurring after a paging message and before or after a Msg1 message, according to aspects of the present disclosure.
[0032] FIG. 14 is a example R2D messaging timeline of R2D random access control messages and resources over time, including the R2D message occurring after a paging message and a Msg3 message, according to aspects of the present disclosure.
[0033] FIG. 15 is a example R2D messaging timeline of R2D random access control messages and resources over time, including the R2D message occurring after a paging message and after a not acknowledged (NACK) message associated with a Msg3 transmission, according to aspects of the present disclosure.
[0034] FIG. 16 is a example R2D messaging timeline of R2D random access control messages and resources over time, including the R2D message occurring after a failure to receive a Msg1 message subsequent to a paging message, according to aspects of the present disclosure.
[0035] FIG. 17 is a example R2D messaging diagram of R2D random access control messages associated with the message timelines of FIGS. 15 and 16.
[0036] FIG. 18 is a example R2D messaging timeline of R2D random access control messages and resources over time, including the R2D message occurring after all Msg3 messages have been received, according to aspects of the present disclosure.
[0037] FIG. 19 is a example R2D messaging diagram of R2D random access control messages associated with the message timeline of FIG. 18.
[0038] FIG. 20 is a example R2D messaging timeline of R2D random access control messages and resources over time, including the R2D message occurring before a last access occasion as signaled by a paging message, according to aspects of the present disclosure.
[0039] FIG. 21 is a example R2D messaging diagram of R2D random access control messages associated with the message timeline of FIG. 20.
[0040] FIG. 22 is an example architecture diagram of the reader device.
[0041] FIG. 23 is a flowchart of a method of wireless communication by the reader device.
[0042] FIG. 24 is a block diagram of additional aspects of the method of FIG. 23.
[0043] FIG. 25 is an example architecture diagram of the A-IoT device.
[0044] FIG. 26 is a flowchart of a method of wireless communication by the A-IoT device.
[0045] FIG. 27 is a block diagram of additional aspects of the method of FIG. 26.DETAILED DESCRIPTION
[0046] Aspects of the present disclosure relate to the design of a new R2D (Reader-to-Device) message within the context of wireless communication systems, such as 6G system, specifically for use as an alternative or addition to a paging message in triggering a message 1 (Msg1) message transmission in an R2D random access procedure. The described apparatus and methods optimize the signaling process for initial access and re-access procedures in wireless communication networks, particularly for A-IoT (Ambient-Internet of Things) devices.
[0047] Aspects of the disclosure include multiple approaches to implementing the R2D message, including formats that carry the R2D message and / or its fields or data elements within the R2D MAC (Medium Access Control) layer protocol data unit (PDU) , including in MAC headers, MAC Control Elements (CEs) , or combinations thereof, and / or within the R2D L1 (Physical Layer) control. The R2D message described herein is designed to indicate various parameters for A-IoT device to reader device communications, including optionally reserving portions of the R2D message for future improvements. Moreover, the aspects described herein define scenarios for the location and timing of the R2D message within the R2D random access procedure, which can help to efficiently overcome the failure to receive certain random access procedure messages without having to resort to an additional paging message. Further, aspects defining the location and timing of the R2D message within the R2D random access procedure enable additional data exchange by multiple groups or subgroups of A-IoT devices sharing the same resources for transmitting the Msg1 message. As such, the aspects described herein may help to improve flexibility, scalability, and / or resource efficiency, and enhance resource allocation, reduce communication delays, and ensure successful data exchange in R2D random access procedure signaling.
[0048] FIG. 1 is a diagram illustrating an example of a wireless communications network 100 that includes one or more reader devices 114 configured to transmit, and one or more Ambient Internet of Things (A-IoT) devices 116 configured to receive, a reader-to-device (R2D) message 120 configured to trigger the one or more A-IoT devices 116 to respond with a Message 1 (Msg1) message 122 of a random access procedure 124 to initiate or re-initiate communications and transfer data from the one or more A-IoT devices 116 to the one or more reader devices 114. In particular, the R2D message 120 is independent of and subsequent to a paging message 118 that was previously sent to the one or more A-IoT devices 116 by the one or more reader devices 114. The paging message 118 configures the one or more A-IoT devices 116 with one or more access occasions for transmitting the Msg1 message 122. As such, the R2D message 120 is an alternative to the paging message 118 used to quickly and efficiently trigger the Msg1 message 122.
[0049] For instance, the R2D message 120 may be utilized by the one or more reader devices 114 for one or more reasons, such as: not receiving the Msg1 message 122 within a threshold amount of time after the access occasions have occurred, and / or after all Message 3 (Msg3) messages of the RACH procedure 124 are received, and / or after the one or more reader devices 114 transmit a not acknowledged (NACK) message in response to not receiving a Msg3 message, and / or before a last one of the access occasions occurs, as described below in more detail. In any case, after transmitting the R2D message 118 and receiving the Msg1 message 120 and the subsequent messages of the RACH procedure 124, the one or more reader devices 114 may then collect and analyze the data from the one or more A-IoT devices 116 and / or communicate the data to one or more base stations 102 via a communication link 112 for collection and / or analysis at one or more other network devices.
[0050] Additionally, and as will be discussed below in more detail, the R2D message 120 may include various fields and / or data elements carrying information related to the Msg1 message 122 and / or subsequent messages. Further, as will be described below in more detail, the R2D message 120 may be carried by any one of a plurality of different messaging structures and / or resources.
[0051] In one implementation, for example, the one or more reader devices 114 include a A-IoT signaling component 126 configured to exchange communications with a corresponding A-IoT signaling component 128 of the one or more A-IoT devices 116. According to the present aspects, the A-IoT signaling component 126 of the one or more reader devices 114 includes a Msg1 trigger component 130 configured to initiate the transmission of the R2D message 120, after the paging message 118 has already been sent, in order to trigger the Msg1 message 120. Correspondingly, the A-IoT signaling component 128 of the one or more reader devices 114 includes a Msg1 trigger response component 132 configured recognize the R2D message 120 being received after the paging message 118, and to initiate the transmission of the Msg1 message 120.
[0052] It should be noted that the one or more A-IoT devices 116 may including a plurality of A-IoT devices organized into multiple groups and or sub-groups, such as a first group or subgroup 134 through a nth group or subgroup 136. In such cases, in some implementations, the one or more reader devices 114 may utilize multiple R2D messages 120 to trigger a response from different groups or subgroups of A-IoT devices 116 having a same set of Msg1 resources, e.g., a same set of access occasions.
[0053] In an aspect, the one or more reader devices 114 may be any type of wireless communication device configured to communicate with both the one or more A-IoT devices 116 and with one or more other devices within the wireless communication network 100. For instance, the present disclosure may be implemented using or more different topologies. One example topology includes the one or more A-IoT devices 116 communicating bidirectionally with an intermediate node between the A-IoT devices 116 and a base station 102, as described herein. In this topology, the intermediate node is the reader device 114, which can be a relay, an integrated access backhaul (IAB) node, a UE 104 as described herein, a repeater, etc., or any other device which is capable of A-IoT communications. The intermediate node transfers A-IoT data and / or signaling between the base station 102 and the one or more A-IoT devices 116. Another example topology includes the one or more A-IoT devices 116 directly communicating with the base station 102 in a bi-directional manner, e.g., the base station 102 is the reader device 114. The communication between the base station 102 and the one or more A-IoT devices 116 includes A-IoT data and / or signaling. In a further example, one topology includes the one or more A-IoT devices 116 transmitting data / signaling to the base station 102, and receiving data / signaling from an assisting node, such as UE 104, or the one or more A-IoT devices 116 receiving data / signaling from the base station 102 and transmitting data / signaling to the assisting node. In this topology, the assisting node can be a relay, IAB, UE 104, repeater, etc., or any device which is capable of A-IoT communication. In yet another example, one topology may include the one or more A-IoT devices 116 communicating bidirectionally with one or more UE 104, as described herein. Communication between the one or more UEs 104 and the one or more A-IoT devices 116 includes A-IoT data and / or signaling.
[0054] Further details of the present disclosure are described later herein with reference to various example aspects.
[0055] The wireless communications system (also referred to as a wireless wide area network (WWAN) ) includes base stations 102, UEs 104, an Evolved Packet Core (EPC) 160, and another core network 190 (such as a 6G Core (6GVC) and / or a 5G Core (5GC)) . The base stations 102 may include macrocells (high power cellular base station) or small cells (low power cellular base station) . The macrocells include base stations. The small cells include femtocells, picocells, and microcells. The small cells include femtocells, picocells, and microcells. The base stations 102 can be configured in a Disaggregated RAN (D-RAN) or Open RAN (O-RAN) architecture, where functionality is split between multiple units such as a central unit (CU) , one or more distributed units (DUs) , or a radio unit (RU) . Such architectures may be configured to utilize a protocol stack that is logically split between one or more units (such as one or more CUs and one or more DUs) . In some aspects, the CUs may be implemented within an edge RAN node, and in some aspects, one or more DUs may be co-located with a CU, or may be geographically distributed throughout one or multiple RAN nodes. The DUs may be implemented to communicate with one or more RUs.
[0056] The base stations 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) ) may interface with the EPC 160 through one or more first backhaul links 162 (such as S1 interface) , which may be wired or wireless. The base stations 102 configured for 6G and / or 5G NR (collectively referred to as Next Generation RAN (NG-RAN) ) may interface with core network 190 through one or more second backhaul links 184, which may be wired or wireless. In addition to other functions, the base stations 102 may perform one or more of the following functions: transfer of user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (such as handover, dual connectivity) , inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS) , subscriber and equipment trace, RAN information management (RIM) , paging, positioning, and delivery of warning messages. The base stations 102 may communicate directly or indirectly (such as through the EPC 160 or core network 190) with each other over third backhaul links 164 (such as X2 interface) . The third backhaul links 164 may be wired or wireless.
[0057] The base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, the small cell 102' may have a coverage area 110' that overlaps the coverage area 110 of one or more macro base stations 102. A network that includes both small cell and macrocells may be known as a heterogeneous network. A heterogeneous network also may include Home Evolved Node Bs (eNBs) (HeNBs) , which may provide service to a restricted group known as a closed subscriber group (CSG) . The communication links 112 between the base stations 102 and the UEs 104 may include UL (also referred to as reverse link) transmissions from a UE 104 to a base station 102 or DL (also referred to as forward link) transmissions from a base station 102 to a UE 104. The communication links 112 may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, or transmit diversity. The communication links may be through one or more carriers. The base stations 102 / UEs 104 may use spectrum up to Y MHz (such as 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (such as more or fewer carriers may be allocated for DL than for UL) . The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell) .
[0058] Certain UEs 104 may communicate with each other using device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , and a physical sidelink control channel (PSCCH) . D2D communication may be through a variety of wireless D2D communications systems, such as for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.
[0059] The wireless communications system may further include a Wi-Fi access point (AP) 150 in communication with Wi-Fi stations (STAs) 152 via communication links 154 in a 5 GHz unlicensed frequency spectrum. When communicating in an unlicensed frequency spectrum, the STAs 152 / AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.
[0060] The small cell 102' may operate in a licensed or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell 102' may employ NR and use the same 5 GHz unlicensed frequency spectrum as used by the Wi-Fi AP 150. The small cell 102', employing NR in an unlicensed frequency spectrum, may boost coverage to or increase capacity of the wireless communication system.
[0061] A base station 102, whether a small cell 102' or a large cell (such as macro base station) , may include an eNB, gNodeB (gNB) , or other type of base station. Some base stations, such as gNB 180 may operate in one or more frequency bands within the electromagnetic spectrum.
[0062] The electromagnetic spectrum is often subdivided, based on frequency / wavelength, into various classes, bands, channels, etc. In 5G NR two initial operating bands have been identified as frequency range designations FR1 (410 MHz –7.125 GHz) and FR2 (24.25 GHz –52.6 GHz) . The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” (mmW) band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz –300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.
[0063] With the above aspects in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, or may be within the EHF band. Communications using the mmW radio frequency band have extremely high path loss and a short range. The mmW base station 180 may utilize beamforming 182 with the UE 104 to compensate for the path loss and short range.
[0064] The EPC 160 may include a Mobility Management Entity (MME) , other MMEs, a Serving Gateway, a Multimedia Broadcast Multicast Service (MBMS) Gateway, a Broadcast Multicast Service Center (BM-SC) , and a Packet Data Network (PDN) Gateway. The MME may be in communication with a Home Subscriber Server (HSS) 174. The MME is the control node that processes the signaling between the UEs 104 and the EPC 160. Generally, the MME provides bearer and connection management. All user Internet protocol (IP) packets are transferred through the Serving Gateway, which itself is connected to the PDN Gateway. The PDN Gateway provides UE IP address allocation as well as other functions. The PDN Gateway and the BM-SC are connected to the IP Services 176. The IP Services 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS) , a PS Streaming Service, or other IP services. The BM-SC may provide functions for MBMS user service provisioning and delivery. The BM-SC may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN) , and may be used to schedule MBMS transmissions. The MBMS Gateway may be used to distribute MBMS traffic to the base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start / stop) and for collecting eMBMS related charging information.
[0065] The core network 190 may include an Access and Mobility Management Function (AMF) , other AMFs 193, a Session Management Function (SMF) , and a User Plane Function (UPF) . The AMF may be in communication with a Unified Data Management (UDM) . The AMF is the control node that processes the signaling between the UEs 104 and the core network 190. Generally, the AMF provides QoS flow and session management. All user Internet protocol (IP) packets are transferred through the UPF. The UPF provides UE IP address allocation as well as other functions. The UPF is connected to the IP Services 197. The IP Services 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS) , a PS Streaming Service, or other IP services.
[0066] The base station may include or be referred to as a gNB, Node B, eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS) , an extended service set (ESS) , a transmit reception point (TRP) , or some other suitable terminology. The base station 102 provides an access point to the EPC 160 or core network 190 for a UE 104. Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA) , a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (such as a MP3 player) , a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similar functioning device. Some of the UEs 104 may be referred to as IoT devices (such as a parking meter, gas pump, toaster, vehicles, heart monitor, etc. ) . The UE 104 also may be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.
[0067] Although the following description may be focused on 6G systems, the concepts described herein may be applicable to other similar areas, such as 5G NR, LTE, LTE-A, CDMA, GSM, and other future wireless technologies.
[0068] Referring to FIGS. 2A –2D, example of frames and frame structures may be used by any of the devices in FIG. 1 and other figures herein for communication. FIG. 2A is a diagram 200 illustrating an example of a first frame. FIG. 2B is a diagram 230 illustrating an example of DL channels within a subframe. FIG. 2C is a diagram 250 illustrating an example of a second frame. FIG. 2D is a diagram 280 illustrating an example of a subframe. The 5G NR frame structure may be FDD in which for a particular set of subcarriers (carrier system bandwidth) , subframes within the set of subcarriers are dedicated for either DL or UL, or may be TDD in which for a particular set of subcarriers (carrier system bandwidth) , subframes within the set of subcarriers are dedicated for both DL and UL. A subset of the total cell bandwidth of a cell is referred to as a Bandwidth Part (BWP) and bandwidth adaptation is achieved by configuring the UE with BWP (s) and telling the UE which of the configured BWPs is currently the active one. In an aspect, a narrow bandwidth part (NBWP) refers to a BWP having a bandwidth less than or equal to a maximum configurable bandwidth of a BWP. The bandwidth of the NBWP is less than the carrier system bandwidth.
[0069] In the examples provided by Figs. 2A, 2C, the 5G NR frame structure is assumed to be TDD, with subframe 4 being configured with slot format 28 (with mostly DL) , where D is DL, U is UL, and X is flexible for use between DL / UL, and subframe 3 being configured with slot format 34 (with mostly UL) . While subframes 3, 4 are shown with slot formats 34, 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0, 1 are all DL, UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. UEs are configured with the slot format (dynamically through DL control information (DCI) , or semi-statically / statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI) . Note that the description infra applies also to a 5G NR frame structure that is TDD.
[0070] Other wireless communication technologies may have a different frame structure or different channels. A frame (10 milliseconds (ms) ) may be divided into 10 equally sized subframes (1 ms) . Each subframe may include one or more time slots. Subframes also may include mini-slots, which may include 7, 4, or 2 symbols. Each slot may include 7 or 14 symbols, depending on the slot configuration. For slot configuration 0, each slot may include 14 symbols, and for slot configuration 1, each slot may include 7 symbols. The symbols on DL may be cyclic prefix (CP) OFDM (CP-OFDM) symbols. The symbols on UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also referred to as single carrier frequency-division multiple access (SC-FDMA) symbols) (for power limited scenarios; limited to a single stream transmission) . The number of slots within a subframe is based on the slot configuration and the numerology. For slot configuration 0, different numerologies μ 0 to 5 allow for 1, 2, 4, 8, 16, and 32 slots, respectively, per subframe. For slot configuration 1, different numerologies 0 to 2 allow for 2, 4, and 8 slots, respectively, per subframe. Accordingly, for slot configuration 0 and numerology μ, there are 14 symbols / slot and 2μ slots / subframe. The subcarrier spacing and symbol length / duration are a function of the numerology. The subcarrier spacing may be equal to 2μ*15 kHz, where μ is the numerology 0 to 5. As such, the numerology μ=0 has a subcarrier spacing of 15 kHz and the numerology μ=5 has a subcarrier spacing of 480 kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figs. 2A–2D provide an example of slot configuration 0 with 14 symbols per slot and numerology μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 microseconds (μs) .
[0071] A resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs) ) that extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs) . The number of bits carried by each RE depends on the modulation scheme.
[0072] As illustrated in FIG. 2A, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include demodulation RS (DMRS) (indicated as Rx for one particular configuration, where 100x is the port number, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. The RS also may include beam measurement RS (BRS) , beam refinement RS (BRRS) , and phase tracking RS (PT-RS) .
[0073] FIG. 2B illustrates an example of various DL channels within a subframe of a frame. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) , each CCE including nine RE groups (REGs) , each REG including four consecutive REs in an OFDM symbol. A primary synchronization signal (PSS) may be within symbol 2 of particular subframes of a frame. The PSS is used by a UE 104 to determine subframe / symbol timing and a L1 identity. A secondary synchronization signal (SSS) may be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine a L1 cell identity group number and radio frame timing. Based on the L1 identity and the L1 cell identity group number, the UE can determine a physical cell identifier (PCI) . Based on the PCI, the UE can determine the locations of the aforementioned DMRS. The physical broadcast channel (PBCH) , which carries a master information block (MIB) , may be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (SSB) . The MIB provides a number of RBs in the system bandwidth and a system frame number (SFN) . The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs) , and paging messages.
[0074] As illustrated in FIG. 2C, some of the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH) . The PUSCH DM-RS may be transmitted in the first one or two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the particular PUCCH format used. The UE may transmit sounding reference signals (SRS) . The SRS may be transmitted in the last symbol of a subframe. The SRS may have a comb structure, and a UE may transmit SRS on one of the combs. The SRS may be used by a base station for channel quality estimation to enable frequency-dependent scheduling on the UL.
[0075] FIG. 2D illustrates an example of various UL channels within a subframe of a frame. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI) , such as scheduling requests, a channel quality indicator (CQI) , a precoding matrix indicator (PMI) , a rank indicator (RI) , and HARQ ACK / NACK feedback. The PUSCH carries data, and may additionally be used to carry a buffer status report (BSR) , a power headroom report (PHR) , or UCI.
[0076] FIG. 3 is a diagram of an example of a base station 310 and a UE 350 in a wireless communication system, such as the wireless communication network 100 of FIG. 1. In an aspect, the base station 310 and / or UE 350 may implement the A-IoT signaling component 126 described herein. In the DL, IP packets from the EPC 160 may be provided to a controller / processor 375. In an aspect, base station 310 may be the same as or similar to base station 102 of FIG. 1, and UE 350 may be the same as or similar to the UE 104 of FIG. 1. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (such as MIB, SIBs) , RRC connection control (such as RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release) , inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification) , and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs) , error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs) , re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs) , demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.
[0077] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding / decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The TX processor 316 handles mapping to signal constellations based on various modulation schemes (such as binary phase-shift keying (BPSK) , quadrature phase-shift keying (QPSK) , M-phase-shift keying (M-PSK) , M-quadrature amplitude modulation (M-QAM) ) . The coded and modulated symbols may be split into parallel streams. Each stream may be mapped to an OFDM subcarrier, multiplexed with a reference signal (such as a pilot) in the time or frequency domain, and combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal or channel condition feedback transmitted by the UE 350. Each spatial stream may be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX may modulate an RF carrier with a respective spatial stream for transmission.
[0078] At the UE 350, each receiver 354RX receives a signal through its respective antenna 352. Each receiver 354RX recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT) . The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on channel estimates computed by the channel estimator 358. The soft decisions are decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel. The data and control signals are provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.
[0079] The controller / processor 359 can be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer-readable medium and may be any of the types of computer-readable mediums discussed herein (e.g., RAM, ROM, EEPROM, optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the aforementioned types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer) . In the UL, the controller / processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using an ACK or NACK protocol to support HARQ operations.
[0080] Similar to the functionality described in connection with the DL transmission by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (such as MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression / decompression, and security (ciphering, deciphering, integrity protection, integrity verification) ; RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.
[0081] Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antenna 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a respective spatial stream for transmission.
[0082] The UL transmission is processed at the base station 310 in a manner similar to that described in connection with the receiver function at the UE 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to a RX processor 370.
[0083] The controller / processor 375 can be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer-readable medium and may be any of the types of computer-readable mediums discussed herein (e.g., RAM, ROM, EEPROM, optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the aforementioned types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer) . In the UL, the controller / processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the UE 350. IP packets from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also responsible for error detection using an ACK or NACK protocol to support HARQ operations.
[0084] At the UE 350, at least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform aspects in connection with the A-IoT signaling component 126 of FIG. 1. For example, the memory 360 may include executable instructions defining the A-IoT signaling component 126. The TX processor 368, the RX processor 356, and / or the controller / processor 359 may be configured to execute the A-IoT signaling component 126.
[0085] Similarly, at the base station 310, at least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform aspects in connection with the A-IoT signaling component 126 of FIG. 1. For example, the memory 376 may include executable instructions defining the A-IoT signaling component 126. The TX processor 316, the RX processor 370, and / or the controller / processor 375 may be configured to execute the A-IoT signaling component 126.
[0086] FIG. 4 is a diagram illustrating an example disaggregated base station 400 architecture. The disaggregated base station 400 architecture may include one or more central units (CUs) 410 that can communicate directly with a core network 420 via a backhaul link, or indirectly with the core network 420 through one or more disaggregated base station units (such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) 425 via an E2 link, or a Non-Real Time (Non-RT) RIC 415 associated with a Service Management and Orchestration (SMO) Framework 405, or both) . A CU 410 may communicate with one or more distributed units (DUs) 430 via respective midhaul links, such as an F1 interface. The DUs 430 may communicate with one or more radio units (RUs) 440 via respective fronthaul links. The RUs 440 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, the UE 104 may be simultaneously served by multiple RUs 440.
[0087] Each of the units, i.e., the CUs 410, the DUs 430, the RUs 440, as well as the Near-RT RICs 425, the Non-RT RICs 415 and the SMO Framework 405, may include one or more interfaces or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more of the other units. Additionally, the units can include a wireless interface, which may include a receiver, a transmitter or transceiver (such as a radio frequency (RF) transceiver) , configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.
[0088] In some aspects, the CU 410 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC) , packet data convergence protocol (PDCP) , service data adaptation protocol (SDAP) , or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 410. The CU 410 may be configured to handle user plane functionality (i.e., Central Unit –User Plane (CU-UP) ) , control plane functionality (i.e., Central Unit –Control Plane (CU-CP) ) , or a combination thereof. In some implementations, the CU 410 can be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as the E1 interface when implemented in an O-RAN configuration. The CU 410 can be implemented to communicate with the DU 430, as necessary, for network control and signaling.
[0089] The DU 430 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 440. In some aspects, the DU 430 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, or the like) depending, at least in part, on a functional split, such as those defined by the 3rd Generation Partnership Project (3GPP) . In some aspects, the DU 430 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 430, or with the control functions hosted by the CU 410.
[0090] Lower-layer functionality can be implemented by one or more RUs 440. In some deployments, an RU 440, controlled by a DU 430, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (such as performing fast Fourier transform (FFT) , inverse FFT (iFFT) , digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like) , or both, based at least in part on the functional split, such as a lower layer functional split. In such an architecture, the RU (s) 440 can be implemented to handle over the air (OTA) communication with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU (s) 440 can be controlled by the corresponding DU 430. In some scenarios, this configuration can enable the DU (s) 430 and the CU 410 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.
[0091] The SMO Framework 405 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 405 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements which may be managed via an operations and maintenance interface (such as an O1 interface) . For virtualized network elements, the SMO Framework 405 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 490) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface) . Such virtualized network elements can include, but are not limited to, CUs 410, DUs 430, RUs 440 and Near-RT RICs 425. In some implementations, the SMO Framework 405 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 411, via an O1 interface. Additionally, in some implementations, the SMO Framework 405 can communicate directly with one or more RUs 440 via an O1 interface. The SMO Framework 405 also may include a Non-RT RIC 415 configured to support functionality of the SMO Framework 405.
[0092] The Non-RT RIC 415 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, Artificial Intelligence / Machine Learning (AI / ML) workflows including model training and updates, or policy-based guidance of applications / features in the Near-RT RIC 425. The Non-RT RIC 415 may be coupled to or communicate with (such as via an A1 interface) the Near-RT RIC 425. The Near-RT RIC 425 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 410, one or more DUs 430, or both, as well as an O-eNB, with the Near-RT RIC 425.
[0093] In some implementations, to generate AI / ML models to be deployed in the Near-RT RIC 425, the Non-RT RIC 415 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 425 and may be received at the SMO Framework 405 or the Non-RT RIC 415 from non-network data sources or from network functions. In some examples, the Non-RT RIC 415 or the Near-RT RIC 425 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 415 may monitor long-term trends and patterns for performance and employ AI / ML models to perform corrective actions through the SMO Framework 405 (such as reconfiguration via O1) or via creation of RAN management policies (such as A1 policies) .
[0094] As noted above, the present disclosure provides a new R2D message 120 designed to trigger Msg1 message 122 transmission, with various options for implementation within the message structure, resources, and procedures in the wireless communication network 100. As will be described below, referring to FIG. 5, in general, the R2D message 120 is defined as including one or any combination of elements such as message type, transaction ID, Q adjust, re-access indication, resource adjustment, reader ID, device ID, and a reserved field. In one aspect, referring to FIG. 6, the R2D message 120 is wholly carried within an R2D MAC PDU, with alternatives exploring different configurations, such as: a first alternative, referring to FIG. 7, that places the R2D message 120 wholly in the MAC header; a second alterative, referring to FIG. 8, that situates the R2D message 120 in a single MAC CE without involving the MAC header; and a third alternative, that utilized multiple MAC CEs to carry all of the information of the R2D message 120. In another option, referring to FIG. 10, the R2D message 120 is distributed between the MAC header and R2D MAC CE. In another aspect, referring to FIG. 11, a split approach is utilized where the R2D message 120 is partially carried in L1 control and a remainder in the R2D MAC PDU. In yet another aspect, referring to FIG. 12, the R2D message 120 is fully integrated into the L1 control, eliminating the use of R2D MAC PDU. These aspects may optimize signaling processes for reader device 114 and A-IoT device 116 communications.
[0095] Referring to FIG. 5, as noted above, the R2D message 120 is defined with one or any combination of one or more of the following elements or fields, which can include one or more bits and / or data to indicate a respective parameter: message type 502, transaction ID 504, number of R2D message adjust indication 506, re-access indication 508, resource adjustment 510, reader ID 512, device ID 514, and a reserved field 516. The message type 502 can be implemented either as a single-entry message type I configuration or as multiple entries, e.g., a message type II, to differentiate between two distinct message types. The single entry, message type I is defined to indicate the initiation of a set of Msg1 resources pre-configured in a paging message without requiring Msg1 resource adjustment. Message Type II, on the other hand, is used for adjusting the number of remaining R2D messages and / or performing Msg1 resource adjustments. Additionally, the R2D message may incorporate the transaction ID 504, which may be indicated explicitly or implicitly, such as through a cyclic redundancy check (CRC) mask embedded with the transaction ID (e.g., the CRC can be decoded using the proper value of the transaction ID 504) . The transaction ID 504 may indicate a specific session or query or command for which a response is desired, e.g., associated with the reader devices 114 gathering data from the A-IoT devices 116. In an aspect, the R2D message 120 facilitates adjustments, such as via the number of R2D message adjust indication 506, which modifies the number of remaining R2D messages by either directly indicating an absolute value or specifying a delta. In an aspect, the R2D message 120 may also support the re-access indication 508, which is configured when a single R2D message is utilized for both initial access and re-access processes. Additionally, in an aspect, the R2D message 120 may include the resource adjustment 510 to enable resource adjustments by modifying TDMed (time-division multiplexed) resources, FDMed (frequency-division multiplexed) resources, or both, and allows changes to the number of resources configured in the paging message 118, such as transitioning from two TDMed resources to one, or indicating a new resource pattern. Also, the resource adjustment 510 may also enable timing parameters, such as TR2D, Toffset1, and Toffset2, to be adjusted. Additionally, in an aspect, the R2D message 120 may include fields for Device ID 512, which is an identifier of one or more A-IoT devices 116 that are intended recipients of the R2D message 120, and the Reader ID 514, which is an identifier of the reader device 114 that transmitted the R2D message 120 and / or the identifier of the reader device 114 to which the A-IoT device 116 is to respond. Additionally, the R2D message 120 may include one or more reserved fields 516 that can be utilized for other purposes, as may be determined in future developments. Any combination, and any number, of these elements is supported, including cases where the R2D message 120 conveys solely the message type 502, or only the message type 502 and the transaction ID 504 as in some aspects these may be considered the most basic fields for the A-IoT device 116 to utilize in order to properly direct the Msg1 message 122.
[0096] Thus, the options provided by this configuration of the R2D message 120 optimizes the flexibility and scalability of signaling operations between the one or more reader devices 114 and the one or more A-IoT devices 116.
[0097] Referring to FIG. 6, as mentioned above, in an aspect, the R2D message 120 is configured to be completely carried within the R2D MAC protocol date unit (PDU) 600. The location of the R2D message 120 within the R2D MAC protocol date unit (PDU) 600 may vary depending on the implementation.
[0098] Referring to FIG. 7, for example, in an aspect, the R2D message 120 is configured to be completely carried within a MAC header 702 of the R2D MAC PDU 600. By providing the R2D message 120 in the MAC header 702, which may be located at a beginning of the PDU, a receiving A-IoT device 116 can quickly decode relevant fields of the message, such as to determine if the message is meant for the respective device or not.
[0099] Referring to FIG. 8, in another alternative aspect, the R2D message 120 is configured to be completely carried within one or more MAC control elements (CEs) 702 of a MAC sub-PDU 802 of the R2D MAC PDU 600 without a MAC header. In one implementation, the R2D message 120 is carried in a single MAC CE 804. Also, in some aspects, the MAC sub-PDU 802 may include padding bits 806.
[0100] Referring to FIG. 9, in a further alternative, multiple MAC CEs 804 in multiple MAC subPDUs, such as MAC subPDUs 902 and 904, are utilized to convey different and / or overlapping information of the R2D message 120. For instance, in one implementation, one MAC CE 804 includes the message type, transaction ID, Q value adjustment, re-access indication, and reserved bits, while another MAC CE 804 incorporates the resource adjustment, device ID, reader ID, as well as more reserve bits. The combination of different fields carried in each of the multiple MAC CEs 804 may vary depending on the implementation.
[0101] Referring to FIG. 10, in another aspect, the R2D message 120 is partially carried in the MAC header 702 in one MAC subPDU 1002 with the remaining components carried in one or more MAC CEs 804 in one or more MAC subPDUs 1004. In this case, the MAC header 702 may include elements such as message type, transaction ID, and the reserve bits for extensibility. One or multiple MAC CEs 804 may incorporate parameters like Q value adjustments, re-access indication (e.g., to signify whether the message pertains to re-access or initial access, which is particularly relevant when a single R2D message serves both purposes) , resource adjustment, device ID, reader ID, and, optionally, one or more reserved bits.
[0102] In other aspects, for all MAC PDU-related designs, the MAC header 702 and MAC CE 804 can support either byte-alignment or non-byte alignment configurations, ensuring adaptability across signaling scenarios.
[0103] Referring to FIG. 11, in yet another aspect, a hybrid approach is utilized where the R2D message 120 is distributed across L1 control 1000 and the R2D MAC PDU 600, such as but not limited to being in one or more MAC CEs 1102. In this case, the L1 control 1100 is distinct from the MAC PDU 600, and the L1 control 1100 may include a separate Cyclic Redundancy Check (CRC) for early indication. In other words, the one or more A-IoT devices 116 more quickly process the L1 control 1100, as compared to other parts of the R2D MAC PDU 600, and access the beginning 1104 of the R2D MAC PDU 600 if the portion of the R2D message 120 in the L1 control 1100 is relevant. The L1 control 1100 may include parameters such as message type, transaction ID, device ID, and the R2D MAC PDU length or duration 1106, e.g., to indicate an end 1108 of the R2D MAC PDU 600, which may not be necessary if the R2D MAC PDU 600 employs a fixed size or postamble. The R2D MAC PDU 600 further incorporates elements including a MAC CE and / or a MAC header, jointly illustrated as “MAC CE or MAC header” 1102, to carry remaining parameters of the R2D message 120, such as Q value adjustment, re-access indication, resource adjustment, Reader ID, and reserve bits. This configuration may conserve resources, as repeated or common parameters of the R2D message 120 may be carried by the L1 control 1100, while parameters having changes may be carried by the one or more MAC CEs 1102.
[0104] Referring to FIG. 12, in a further aspect, the R2D message 120 is wholly carried within the L1 control 1100, without the use of an R2D MAC PDU. This streamlined approach potentially enhances signaling efficiency and enables the scalability and flexibility.
[0105] Referring to FIGS. 13-21, the present disclosure further defines the location and timing of the R2D message 120 within the RACH procedure 124 in a wireless communication protocol of the wireless communication network 100. The proposed solutions improve the efficiency and reliability of communication between the one or more reader devices 114 and the one or more A-IoT devices 116. By defining the timing and location of this new R2D message 120, the implementations of the present disclosure enables better management of Msg1 transmission, even in cases of failed or incomplete transmissions. The proposed solutions may provide enhanced resource allocation, reduced communication delays, and may ensure successful data exchange in IoT networks. In other words, the present disclosure improves the efficiency and performance of low-power, resource-constrained IoT devices operating in dynamic environments.
[0106] Referring to FIGS. 13 and 14, in one or more example messaging timelines 1300 and 1400 that illustrate the teachings herein at a high level, in general, the R2D message 120 follows the paging message 118 and the access occasions 119 configured for Msg1 in the paging message, and may be transmitted either before or after the Msg1 message 122 (e.g., either an initial one based on the paging message or a subsequent one responsive to the R2D message 120) as in FIG. 13, or after one or more Msg2 messages 123 and Msg3 messages 125, as in FIG. 14.
[0107] Referring to FIGS. 15-21, specific examples of such scenarios are described in detail. Referring to FIGS. 15-17, example messaging timelines 1500 and 1600, and messaging diagram 1700 include one alternative scenario (timeline 1500) that includes successful reception of Msg1 120 and transmission of Msg 2 123, but transmitting the R2D message 120 following a NACK indication 127 indicating the transmission or retransmission of the Msg3 125 was not received. Or, in the other alternative scenario (timeline 1600) , if Msg1 122 is not received 129 in response to the paging message 118, then the R2D message 120 is transmitted.
[0108] Referring to FIGS. 18 and 19, example messaging timeline 1800 and messaging diagram 1900 include transmitting the new R2D message 120 after all Msg3 message 125 transmissions are successfully completed.
[0109] Referring to FIGS. 20 and 21, example messaging timeline 2000 and messaging diagram 2100 include the uniform placement of the new R2D message 120 adjacent to one or more access occasion 119a or 119b, such as paging-indicated TDMed resources. For instance, in these aspects, the R2D message 120 facilitates triggering another subgroup of ambient IoT devices 116 using the same Msg1 resources, e.g., one or more access occasion 119a or 119b. For example, in a case where a maximum of two access occasion 119a or 119b, e.g., two sets of TDMed resources, are allocated for Msg1 transmission per paging message 118, the R2D message 120 is defined to be located before the second access occasion 119b for Msg1 transmission, ensuring efficient resource utilization and enhanced communication reliability.
[0110] Referring to FIGS. 22-24, in operation, reader device 114 may perform a method 2300 of wireless communication, such as via execution of A-IoT signaling component 126 by one or more processors 2205 configured, individually or in any combination, to execute instructions to perform the following actions, and / or configured to communicate with one or more memories 2210 to obtain the instructions and perform the actions.
[0111] At block 2302, the method 2300 includes transmitting a reader to device (R2D) message configured to trigger transmission of a message 1 message of a random access procedure at one or more ambient IoT devices, wherein the R2D message includes one or more of a message type, a transaction identifier, a re-access indication, a resource adjustment, a reader identifier, or a device identifier. For example, in an aspect, reader device 114, one or more processors 2205, one or more memories 2210, A-IoT signaling component 126, and / or transmitting component 2220 may be configured to or may comprise means for transmitting a reader to device (R2D) message configured to trigger transmission of a message 1 message of a random access procedure at one or more ambient IoT devices, wherein the R2D message includes one or more of a message type, a transaction identifier, a re-access indication, a resource adjustment, a reader identifier, or a device identifier.
[0112] For example, the transmitting at block 2302 may include the reader device 114 operating a wireless modem to generate the R2D message 120 and wirelessly transmit the R2D message 120 via one or more antennas to one or more A-IoT device 116, and / or performing other signal transmitting functionality as described herein.
[0113] At block 2304, the method 2300 includes monitoring for reception of one or more message 1 messages from the one or more ambient IoT devices.. For example, in an aspect, reader device 114, one or more processors 2205, one or more memories 2210, A-IoT signaling component 126, and / or monitoring component 2225 may be configured to or may comprise means for monitoring for reception of one or more message 1 messages from the one or more ambient IoT devices..
[0114] For example, the monitoring at block 2304 may include the reader device 114 operating a modem device to receive signals over the air via one or more antennas such as the Msg1 message 122 transmitted by the one or more A-IoT devices 116, or to execute other signal monitoring functionality as described herein.
[0115] Further, for example, the monitoring at block 2304 may be performed {insert WHY it is done this way and / or any other principle (s) / advantage (s) of this action} .
[0116] Referring to FIG. 24, multiple alternative aspects may be implemented by method 2300 to perform the transmitting of the R2D message 120 at block 2302.
[0117] For instance, in an alternative or additional aspect, at block 2402, the transmitting at block 2302 of the R2D message further comprises transmitting the R2D message in a medium access control protocol data unit, as described above.
[0118] In another alternative or additional aspect, at block 2404, the transmitting at block 2302 of the R2D message further comprises transmitting the R2D message in a header of a medium access control protocol data unit, as described above.
[0119] In an alternative or additional aspect, at block 2406, the transmitting at block 2302 of the R2D message further comprises transmitting the R2D message in at least one control element of a medium access control protocol data unit without a header, as described above.
[0120] In an alternative or additional aspect, at block 2408, the transmitting at block 2302 of the R2D message further comprises transmitting different portions of the R2D message in different ones of a plurality of control elements of a medium access control protocol data unit, as described above.
[0121] In an alternative or additional aspect, at block 2410, the transmitting at block 2302 of the R2D message further comprises transmitting a first portion of the R2D message in a header of a medium access control protocol data unit and a second portion of the R2D message in at least one control element of the medium access control protocol data unit, as described above.
[0122] In an alternative or additional aspect, at block 2412, the transmitting at block 2302 of the R2D message further comprises transmitting a first portion of the R2D message in a header of a medium access control protocol data unit and additional portions of the R2D message in different ones of a plurality of control elements of the medium access control protocol data unit, as described above.
[0123] In an alternative or additional aspect, at block 2414, the transmitting at block 2302 of the R2D message further comprises transmitting a first portion of the R2D message in an L1 control field and a second portion of the R2D message in a medium access control protocol data unit, as described above.
[0124] In an alternative or additional aspect, at block 2416, the transmitting at block 2302 of the R2D message further comprises transmitting the R2D message in an L1 control field, as described above.
[0125] In an alternative or additional aspect, the message type is selected from a plurality of different message types, and / or the transaction identifier comprises an implicit indicator, as described above.
[0126] Referring to FIGS. 25-27, in operation, A-IoT device 116 may perform a method 2600 of wireless communication, such as via execution of A-IoT signaling component 128 by one or more processors 2506 configured, individually or in any combination, to execute instructions to perform the following actions, and / or configured to communicate with one or more memories 2511 to obtain and perform the instructions.
[0127] At block 2602, the method 2600 includes receiving a reader to device (R2D) message configured to trigger transmission of a message 1 message of a random access procedure at one or more ambient IoT devices, wherein the R2D message includes one or more of a message type, a transaction identifier, a re-access indication, a resource adjustment, a reader identifier, or a device identifier. For example, in an aspect, A-IoT device 116, one or more processors 2506, one or more memories 2511, A-IoT signaling component 128, and / or receiving component 2520 may be configured to or may comprise means for receiving a reader to device (R2D) message configured to trigger transmission of a message 1 message of a random access procedure at one or more ambient IoT devices, wherein the R2D message includes one or more of a message type, a transaction identifier, a re-access indication, a resource adjustment, a reader identifier, or a device identifier.
[0128] For example, the receiving at block 2602 may include the A-IoT device 116 operating a wireless modem to receive the R2D message 120 from the reader device 114 via one or more antennas, and / or performing other signal receiving functionality as described herein..
[0129] At block 2604, the method 2600 includes transmitting the message 1 message based on reception of the R2D message.. For example, in an aspect, A-IoT device 116, one or more processors 2506, one or more memories 2511, A-IoT signaling component 128, and / or transmitting component 2525 may be configured to or may comprise means for transmitting the message 1 message based on reception of the R2D message..
[0130] For example, the transmitting at block 2604 may include the A-IoT device 116 operating a wireless modem to generate the Msg1 message 122 and wirelessly transmit it via one or more antennas to the reader device 114, and / or performing other signal transmitting functionality as described herein.
[0131] Referring to FIG. 27, multiple alternative aspects may be implemented by method 2600 to perform the receiving of the R2D message 120 at block 2602.
[0132] For example, in an alternative or additional aspect, at block 2702, the receiving at block 2602 of the R2D message further comprises receiving the R2D message in a medium access control protocol data unit, as described above.
[0133] In an alternative or additional aspect, at block 2704, the receiving at block 2602 of the R2D message further comprises receiving the R2D message in a header of a medium access control protocol data unit, as described above.
[0134] In an alternative or additional aspect, at block 2706, the receiving at block 2602 of the R2D message further comprises receiving the R2D message in at least one control element of a medium access control protocol data unit without a header, as described above.
[0135] In an alternative or additional aspect, at block 2708, the receiving at block 2602 of the R2D message further comprises receiving different portions of the R2D message in different ones of a plurality of control elements of a medium access control protocol data unit, as described above.
[0136] In an alternative or additional aspect, at block 2710, the receiving at block 2602 of the R2D message further comprises receiving a first portion of the R2D message in a header of a medium access control protocol data unit and a second portion of the R2D message in at least one control element of the medium access control protocol data unit, as described above.
[0137] In an alternative or additional aspect, at block 2712, the receiving at block 2602 of the R2D message further comprises receiving a first portion of the R2D message in a header of a medium access control protocol data unit and additional portions of the R2D message in different ones of a plurality of control elements of the medium access control protocol data unit, as described above.
[0138] In an alternative or additional aspect, at block 2714, the receiving at block 2602 of the R2D message further comprises receiving a first portion of the R2D message in an L1 control field and a second portion of the R2D message in a medium access control protocol data unit, as described above.
[0139] In an alternative or additional aspect, at block 2716, the receiving at block 2602 of the R2D message further comprises receiving the R2D message in an L1 control field, as described above.
[0140] In an alternative or additional aspect, the message type is selected from a plurality of different message types, and / or the transaction identifier comprises an implicit indicator, as described above.
[0141] The present aspects may be implemented in one or any combination of the following clauses.
[0142] Clause 1. An apparatus for wireless communication, comprising: one or more memories; and one or more processors coupled with one or more memories and configured, , individually or in combination, to: transmit a reader to device (R2D) message configured to trigger transmission of a message 1 message of a random access procedure at one or more ambient IoT devices, wherein the R2D message includes one or more of a message type, a transaction identifier, a re-access indication, a resource adjustment, a reader identifier, or a device identifier; and monitor for reception of one or more message 1 messages from the one or more ambient IoT devices.
[0143] Clause 2. The apparatus of clause 1, wherein to transmit the R2D message the one or more processors are further configured to transmit the R2D message in a medium access control protocol data unit.
[0144] Clause 3. The apparatus of any preceding clause, wherein to transmit the R2D message the one or more processors are further configured to transmit the R2D message in a header of a medium access control protocol data unit.
[0145] Clause 4. The apparatus of any preceding clause, wherein to transmit the R2D message the one or more processors are further configured to transmit the R2D message in at least one control element of a medium access control protocol data unit without a header.
[0146] Clause 5. The apparatus of any preceding clause, wherein to transmit the R2D message the one or more processors are further configured to transmit different portions of the R2D message in different ones of a plurality of control elements of a medium access control protocol data unit.
[0147] Clause 6. The apparatus of any preceding clause, wherein to transmit the R2D message the one or more processors are further configured to transmit a first portion of the R2D message in a header of a medium access control protocol data unit and a second portion of the R2D message in at least one control element of the medium access control protocol data unit.
[0148] Clause 7. The apparatus of any preceding clause, wherein to transmit the R2D message the one or more processors are further configured to transmit a first portion of the R2D message in a header of a medium access control protocol data unit and additional portions of the R2D message in different ones of a plurality of control elements of the medium access control protocol data unit.
[0149] Clause 8. The apparatus of any preceding clause, wherein to transmit the R2D message the one or more processors are further configured to transmit a first portion of the R2D message in an L1 control field and a second portion of the R2D message in a medium access control protocol data unit.
[0150] Clause 9. The apparatus of any preceding clause, wherein to transmit the R2D message the one or more processors are further configured to transmit the R2D message in an L1 control field.
[0151] Clause 10. The apparatus of any preceding clause, wherein the message type is selected from a plurality of different message types, and / or wherein the transaction identifier comprises an implicit indicator.
[0152] Clause 11. A method of wireless communication, comprising: transmitting a reader to device (R2D) message configured to trigger transmission of a message 1 message of a random access procedure at one or more ambient IoT devices, wherein the R2D message includes one or more of a message type, a transaction identifier, a re-access indication, a resource adjustment, a reader identifier, or a device identifier; and monitoring for reception of one or more message 1 messages from the one or more ambient IoT devices.
[0153] Clause 12. The method of clause 11, wherein transmitting the R2D message further comprises transmitting the R2D message in a medium access control protocol data unit.
[0154] Clause 13. The method of any preceding clause, wherein transmitting the R2D message further comprises transmitting the R2D message in a header of a medium access control protocol data unit.
[0155] Clause 14. The method of any preceding clause, wherein transmitting the R2D message further comprises transmitting the R2D message in at least one control element of a medium access control protocol data unit without a header.
[0156] Clause 15. The method of any preceding clause, wherein transmitting the R2D message further comprises transmitting different portions of the R2D message in different ones of a plurality of control elements of a medium access control protocol data unit.
[0157] Clause 16. The method of any preceding clause, wherein transmitting the R2D message further comprises transmitting a first portion of the R2D message in a header of a medium access control protocol data unit and a second portion of the R2D message in at least one control element of the medium access control protocol data unit.
[0158] Clause 17. The method of any preceding clause, wherein transmitting the R2D message further comprises transmitting a first portion of the R2D message in a header of a medium access control protocol data unit and additional portions of the R2D message in different ones of a plurality of control elements of the medium access control protocol data unit.
[0159] Clause 18. The method of any preceding clause, wherein transmitting the R2D message further comprises transmitting a first portion of the R2D message in an L1 control field and a second portion of the R2D message in a medium access control protocol data unit.
[0160] Clause 19. The method of any preceding clause, wherein transmitting the R2D message further comprises transmitting the R2D message in an L1 control field.
[0161] Clause 20. The method of any preceding clause, wherein the message type is selected from a plurality of different message types, and / or wherein the transaction identifier comprises an implicit indicator.
[0162] Clause 21. An apparatus for wireless communication, comprising: one or more memories; and one or more processors coupled with one or more memories and configured, , individually or in combination, to: receive a reader to device (R2D) message configured to trigger transmission of a message 1 message of a random access procedure at one or more ambient IoT devices, wherein the R2D message includes one or more of a message type, a transaction identifier, a re-access indication, a resource adjustment, a reader identifier, or a device identifier; and transmit the message 1 message based on reception of the R2D message.
[0163] Clause 22. The apparatus of clause 21, wherein to receive the R2D message the one or more processors are further configured to receive the R2D message in a medium access control protocol data unit.
[0164] Clause 23. The apparatus of any preceding clause, wherein to receive the R2D message the one or more processors are further configured to receive the R2D message in a header of a medium access control protocol data unit.
[0165] Clause 24. The apparatus of any preceding clause, wherein to receive the R2D message the one or more processors are further configured to receive the R2D message in at least one control element of a medium access control protocol data unit without a header.
[0166] Clause 25. The apparatus of any preceding clause, wherein to receive the R2D message the one or more processors are further configured to receive different portions of the R2D message in different ones of a plurality of control elements of a medium access control protocol data unit.
[0167] Clause 26. The apparatus of any preceding clause, wherein to receive the R2D message the one or more processors are further configured to receive a first portion of the R2D message in a header of a medium access control protocol data unit and a second portion of the R2D message in at least one control element of the medium access control protocol data unit.
[0168] Clause 27. The apparatus of any preceding clause, wherein to receive the R2D message the one or more processors are further configured to receive a first portion of the R2D message in a header of a medium access control protocol data unit and additional portions of the R2D message in different ones of a plurality of control elements of the medium access control protocol data unit.
[0169] Clause 28. The apparatus of any preceding clause, wherein to receive the R2D message the one or more processors are further configured to receive a first portion of the R2D message in an L1 control field and a second portion of the R2D message in a medium access control protocol data unit.
[0170] Clause 29. The apparatus of any preceding clause, wherein to receive the R2D message the one or more processors are further configured to receive the R2D message in an L1 control field.
[0171] Clause 30. The apparatus of any preceding clause, wherein the message type is selected from a plurality of different message types, and / or wherein the transaction identifier comprises an implicit indicator.
[0172] Clause 31. A method of wireless communication, comprising: receiving a reader to device (R2D) message configured to trigger transmission of a message 1 message of a random access procedure at one or more ambient IoT devices, wherein the R2D message includes one or more of a message type, a transaction identifier, a re-access indication, a resource adjustment, a reader identifier, or a device identifier; and transmitting the message 1 message based on reception of the R2D message.
[0173] Clause 32. The method of clause 31, wherein receiving the R2D message further comprises receiving the R2D message in a medium access control protocol data unit.
[0174] Clause 33. The method of any preceding clause, wherein receiving the R2D message further comprises receiving the R2D message in a header of a medium access control protocol data unit.
[0175] Clause 34. The method of any preceding clause, wherein receiving the R2D message further comprises receiving the R2D message in at least one control element of a medium access control protocol data unit without a header.
[0176] Clause 35. The method of any preceding clause, wherein receiving the R2D message further comprises receiving different portions of the R2D message in different ones of a plurality of control elements of a medium access control protocol data unit.
[0177] Clause 36. The method of any preceding clause, wherein receiving the R2D message further comprises receiving a first portion of the R2D message in a header of a medium access control protocol data unit and a second portion of the R2D message in at least one control element of the medium access control protocol data unit.
[0178] Clause 37. The method of any preceding clause, wherein receiving the R2D message further comprises receiving a first portion of the R2D message in a header of a medium access control protocol data unit and additional portions of the R2D message in different ones of a plurality of control elements of the medium access control protocol data unit.
[0179] Clause 38. The method of any preceding clause, wherein receiving the R2D message further comprises receiving a first portion of the R2D message in an L1 control field and a second portion of the R2D message in a medium access control protocol data unit.
[0180] Clause 39. The method of any preceding clause, wherein receiving the R2D message further comprises receiving the R2D message in an L1 control field.
[0181] Clause 40. The method of any preceding clause, wherein the message type is selected from a plurality of different message types, and / or wherein the transaction identifier comprises an implicit indicator.
[0182] Clause 41. A computer-readable medium comprising stored instructions for wireless communication, wherein the instructions are executable by one or more processors, individually or in any combination, to perform the method of any of clauses 11 to 20, or the method of any of clauses 31 to 40.
[0183] Clause 42. An apparatus for wireless communication, comprising means for to performing the method of any of clauses 11 to 20, or the method any of clauses 31 to 40.
[0184] The description herein is directed to certain implementations for the purposes of describing the innovative aspects of this disclosure. However, a person having ordinary skill in the art will readily recognize that the teachings herein can be applied in a multitude of different ways. Some of the examples in this disclosure are based on wireless and wired local area network (LAN) communication according to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 wireless standards, the IEEE 802.3 Ethernet standards, and the IEEE 1901 Powerline communication (PLC) standards. However, the described implementations may be implemented in any device, system or network that is capable of transmitting and receiving RF signals according to any of the wireless communication standards, including any of the IEEE 802.11 standards, the standard, code division multiple access (CDMA) , frequency division multiple access (FDMA) , time division multiple access (TDMA) , Global System for Mobile communications (GSM) , GSM / General Packet Radio Service (GPRS) , Enhanced Data GSM Environment (EDGE) , Terrestrial Trunked Radio (TETRA) , Wideband-CDMA (W-CDMA) , Evolution Data Optimized (EV-DO) , 1xEV-DO, EV-DO Rev A, EV-DO Rev B, High Speed Packet Access (HSPA) , High Speed Downlink Packet Access (HSDPA) , High Speed Uplink Packet Access (HSUPA) , Evolved High Speed Packet Access (HSPA+) , Long Term Evolution (LTE) , AMPS, or other known signals that are used to communicate within a wireless, cellular or internet of things (IOT) network, such as a system utilizing 3G, 4G, 5G, 6G, or further implementations thereof, technology.
[0185] Further, several aspects of telecommunication systems has been presented with reference to various apparatus and methods. These apparatus and methods may be described in this detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements” ) . These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software, or a combination thereof, depends upon the particular application and design constraints imposed on the overall system.
[0186] By way of example, an element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs) , central processing units (CPUs) , application processors, digital signal processors (DSPs) , reduced instruction set computing (RISC) processors, systems on a chip (SoC) , baseband processors, field programmable gate arrays (FPGAs) , programmable logic devices (PLDs) , state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. The processor may include an interface or be coupled to an interface that can obtain or output signals. The processor may obtain signals via the interface and output signals via the interface. In some implementations, the interface may be a printed circuit board (PCB) transmission line. In some other implementations, the interface may include a wireless transmitter, a wireless transceiver, or a combination thereof. For example, the interface may include a radio frequency (RF) transceiver which can be implemented to receive or transmit signals, or both. One or more processors in the processing system may execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
[0187] Similarly, in one or more aspects, the functions described may be implemented in hardware, digital electronic circuitry, computer software, firmware, including the structures disclosed in this specification and their structural equivalents thereof, or in any combination thereof. Implementations of the subject matter described in this specification also can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions, encoded on a non-transitory computer readable and / or storage media for execution by, or to control the operation of, a data processing apparatus. Computer-readable media includes computer storage media, which may be referred to as non-transitory computer-readable media. Non-transitory computer-readable media may exclude transitory signals. Storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can include a random-access memory (RAM) , a read-only memory (ROM) , an electrically erasable programmable ROM (EEPROM) , optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the aforementioned types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.
[0188] As used herein, a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover: a, b, c, a-b, a-c, b-c, and a-b-c.
[0189] Certain features that are described in this specification in the context of separate implementations also can be implemented in combination in a single implementation. Conversely, various features that are described in the context of a single implementation also can be implemented in multiple implementations separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.
[0190] Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. Further, the drawings may schematically depict one more example processes in the form of a flow diagram. However, other operations that are not depicted can be incorporated in the example processes that are schematically illustrated. For example, one or more additional operations can be performed before, after, simultaneously, or between any of the illustrated operations. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the implementations described above should not be understood as requiring such separation in all implementations, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products. Additionally, other implementations are within the scope of the following claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results.
[0191] Thus, based on the foregoing, various modifications to the implementations described in this disclosure may be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other implementations without departing from the spirit or scope of this disclosure. Thus, the following claims are not intended to be limited to the implementations shown herein, but are to be accorded the widest scope consistent with this disclosure, and the principles and the novel features described herein.
Claims
1.An apparatus for wireless communication, comprising:one or more memories; andone or more processors coupled with the one or more memories and configured, individually or in combination, to:transmit a reader to device (R2D) message configured to trigger transmission of a message 1 message of a random access procedure at one or more ambient IoT devices, wherein the R2D message includes one or more of a message type, a transaction identifier, a re-access indication, a resource adjustment, a reader identifier, or a device identifier; andmonitor for reception of one or more message 1 messages from the one or more ambient IoT devices.2.The apparatus of claim 1, wherein to transmit the R2D message the one or more processors are further configured to transmit the R2D message in a medium access control protocol data unit.3.The apparatus of claim 1, wherein to transmit the R2D message the one or more processors are further configured to transmit the R2D message in a header of a medium access control protocol data unit.4.The apparatus of claim 1, wherein to transmit the R2D message the one or more processors are further configured to transmit the R2D message in at least one control element of a medium access control protocol data unit without a header.5.The apparatus of claim 1, wherein to transmit the R2D message the one or more processors are further configured to transmit different portions of the R2D message in different ones of a plurality of control elements of a medium access control protocol data unit.6.The apparatus of claim 1, wherein to transmit the R2D message the one or more processors are further configured to transmit a first portion of the R2D message in a header of a medium access control protocol data unit and a second portion of the R2D message in at least one control element of the medium access control protocol data unit.7.The apparatus of claim 1, wherein to transmit the R2D message the one or more processors are further configured to transmit a first portion of the R2D message in a header of a medium access control protocol data unit and additional portions of the R2D message in different ones of a plurality of control elements of the medium access control protocol data unit.8.The apparatus of claim 1, wherein to transmit the R2D message the one or more processors are further configured to transmit a first portion of the R2D message in an L1 control field and a second portion of the R2D message in a medium access control protocol data unit.9.The apparatus of claim 1, wherein to transmit the R2D message the one or more processors are further configured to transmit the R2D message in an L1 control field.10.The apparatus of claim 1, wherein the message type is selected from a plurality of different message types, and / or wherein the transaction identifier comprises an implicit indicator.11.An apparatus for wireless communication, comprising:one or more memories; andone or more processors coupled with the one or more memories and configured, individually or in combination, to:receive a reader to device (R2D) message configured to trigger transmission of a message 1 message of a random access procedure at one or more ambient IoT devices, wherein the R2D message includes one or more of a message type, a transaction identifier, a re-access indication, a resource adjustment, a reader identifier, or a device identifier; andtransmit the message 1 message based on reception of the R2D message.12.The apparatus of claim 11, wherein to receive the R2D message the one or more processors are further configured to receive the R2D message in a medium access control protocol data unit.13.The apparatus of claim 11, wherein to receive the R2D message the one or more processors are further configured to receive the R2D message in a header of a medium access control protocol data unit.14.The apparatus of claim 11, wherein to receive the R2D message the one or more processors are further configured to receive the R2D message in at least one control element of a medium access control protocol data unit without a header.15.The apparatus of claim 11, wherein to receive the R2D message the one or more processors are further configured to receive different portions of the R2D message in different ones of a plurality of control elements of a medium access control protocol data unit.16.The apparatus of claim 11, wherein to receive the R2D message the one or more processors are further configured to receive a first portion of the R2D message in a header of a medium access control protocol data unit and a second portion of the R2D message in at least one control element of the medium access control protocol data unit.17.The apparatus of claim 11, wherein to receive the R2D message the one or more processors are further configured to receive a first portion of the R2D message in a header of a medium access control protocol data unit and additional portions of the R2D message in different ones of a plurality of control elements of the medium access control protocol data unit.18.The apparatus of claim 11, wherein to receive the R2D message the one or more processors are further configured to receive a first portion of the R2D message in an L1 control field and a second portion of the R2D message in a medium access control protocol data unit.19.The apparatus of claim 11, wherein to receive the R2D message the one or more processors are further configured to receive the R2D message in an L1 control field.20.The apparatus of claim 11, wherein the message type is selected from a plurality of different message types, and / or wherein the transaction identifier comprises an implicit indicator..
