Enhancements to layer 1 identification of environmental internet of things devices in wireless communication systems

Abstract

Methods, systems, and devices for wireless communication are described. A reader device can communicate a first message via a physical layer channel. The first message can include an indication of a first wireless device identifier associated with a wireless device, such as an ambient Internet of Things (AIoT) device. The first message can also include a request for a second wireless device identifier associated with the wireless device or an indication of a second wireless device identifier associated with the wireless device. The second wireless device identifier can have a bit length selected from a plurality of different bit lengths based on a type of the reader device or an identity of the wireless device. Subsequently, the reader device and the wireless device can communicate one or more messages using the second wireless device identifier having the selected bit length.

Description

Technical Field

[0001] This disclosure relates to wireless communication, including techniques for enhancing Layer 1 (L1) identification of Ambient Internet of Things (AIoT) devices in wireless communication systems. Background Technology

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, and broadcasting. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication for communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0003] The described technology relates to improved methods, systems, apparatuses, and devices for enhancing Layer 1 (L1) identification of Ambient Internet of Things (AIoT) devices in wireless communication systems. For example, the described technology enables one or more network devices in a wireless communication system to help track, locate, or communicate with wireless devices in an surrounding computing environment. Such a surrounding computing environment can use wireless devices (such as AIoT devices) to leverage information from the surrounding environment and provide intelligent services to users. Wireless devices can interact with one or more other devices in the surrounding computing environment to provide services such as location tracking services, communication services, or identification services. For example, a wireless device can interact with a network device (such as a reader device) that can detect or read one of the wireless devices. The reader device can convey a message including first identification information associated with the wireless device. The message may also include a request for a second wireless device identifier associated with the wireless device, or may include an indication of the second wireless device identifier associated with the wireless device. The second wireless device identifier may have a bit length selected from a plurality of different bit lengths based on the type of the reader device or based on the identity of the wireless device. The reader device and the wireless device can then communicate with each other using the second wireless device identifier with the selected bit length.

[0004] A method for wireless communication by a reader device is described. The method may include: conveying, via a physical layer channel, a first message including a first indication of a first wireless device identifier associated with a wireless device, the first message further including a request for or a second indication of a second wireless device identifier associated with the wireless device, the second wireless device identifier including a bit length selected from a set of multiple different bit lengths based on the type of the reader device or the identity of the wireless device; and conveying one or more messages including a second wireless device identifier having the bit length based on at least a partial match between the first wireless device identifier and an identifier associated with the wireless device.

[0005] A reader device for wireless communication is described. The reader device may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code to cause the reader device to: communicate via a physical layer channel a first message including a first indication of a first wireless device identifier associated with a wireless device, the first message further including a request for or a second indication of a second wireless device identifier associated with the wireless device, the second wireless device identifier including a bit length selected from a set of multiple different bit lengths based on the type of the reader device or the identity of the wireless device; and communicate one or more messages including a second wireless device identifier having the bit length based on at least a partial match between the first wireless device identifier and an identifier associated with the wireless device.

[0006] Another reader device for wireless communication is described. The reader device may include: components for conveying, via a physical layer channel, a first message including a first indication of a first wireless device identifier associated with a wireless device, the first message further including a request for or a second indication of a second wireless device identifier associated with the wireless device, the second wireless device identifier including a bit length selected from a set of multiple different bit lengths based on the type of the reader device or the identity of the wireless device; and components for conveying one or more messages including a second wireless device identifier having the bit length based on at least a partial match between the first wireless device identifier and an identifier associated with the wireless device.

[0007] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: convey, via a physical layer channel, a first message including a first indication of a first wireless device identifier associated with a wireless device, the first message further including a request for or a second indication of a second wireless device identifier associated with the wireless device, the second wireless device identifier including a bit length selected from a set of multiple different bit lengths based on the type of reader device or the identity of the wireless device; and convey one or more messages including a second wireless device identifier having the bit length based on at least a partial match between the first wireless device identifier and an identifier associated with the wireless device.

[0008] In some examples of the methods, reader devices, and nontransitory computer-readable media described herein, the first message also includes a third indication of the bit length.

[0009] In some examples of the methods, reader devices, and nontransitory computer-readable media described herein, the bit length of the second wireless device identifier may be further selected based on the broadcast type of at least one of the one or more messages, and the broadcast type includes unicast, broadcast, or multicast.

[0010] In some examples of the methods, reader devices, and nontransitory computer-readable media described herein, the first bit length is selectable based on the type of reader device being a user equipment (UE) reader device, and the second bit length is selectable based on the type of reader device being a base station reader device.

[0011] In some examples of the methods, reader devices, and nontransitory computer-readable media described herein, the first bit length includes fewer bits than the second bit length.

[0012] Some examples of the methods, reader devices, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for establishing a current session with a wireless device based on receiving a second indication for a second wireless device identifier, wherein conveying one or more messages includes conveying one or more messages including a second wireless device identifier having that bit length during the duration of the current session.

[0013] Some examples of the methods, reader devices, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving configuration information from a network entity indicating a lookup table, the lookup table including an association between identification information of a set of multiple wireless devices and a corresponding bit length of each wireless device in the set of multiple wireless devices, wherein the bit length of a second wireless device identifier may be further selected based on the lookup table.

[0014] In some examples of the methods, reader devices, and nontransitory computer-readable media described herein, conveying a first message includes sending a first message that includes a request for a second wireless device identifier, and the first message also includes a third indication of whether to reuse a previous second wireless identifier or to generate a new second wireless identifier.

[0015] In some examples of the methods, reader devices, and nontransitory computer-readable media described herein, conveying a first message includes receiving a first message including a request for a second wireless device identifier, and the method, apparatus, and nontransitory computer-readable media may include additional operations, features, components, or instructions for transmitting a second message via a physical layer channel including an indication of a first wireless device identifier associated with a wireless device, and omitting the indication of a second wireless device identifier associated with a wireless device, wherein conveying one or more messages including a second wireless device identifier includes conveying one or more messages including a previous second wireless device identifier associated with a wireless device.

[0016] In some examples of the methods, reader devices, and nontransitory computer-readable media described herein, the second wireless device identifier may be configured by the wireless device, reader device, or network entity.

[0017] Some examples of the methods, reader devices, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for sending a second message to a wireless device including a session termination command, wherein the session termination command indicates that a second wireless device identifier may no longer be valid.

[0018] In some examples of the methods, reader devices, and nontransitory computer-readable media described herein, a second wireless device identifier associated with a wireless device invalidates a previous second wireless identifier associated with the wireless device.

[0019] Some examples of the methods, reader devices, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: allocating a new second wireless device identifier associated with a wireless device based on performing contention resolution during the inventory process, wherein the new second wireless device identifier includes a contention resolution ID (CRI), a unique wireless device identifier, or a global wireless device identifier; and using the new second wireless device identifier to convey one or more additional messages. Attached Figure Description

[0020] Figure 1 An example of a wireless communication system is shown, which supports enhanced techniques for Layer 1 (L1) identification of Ambient Internet of Things (AIoT) devices in a wireless communication system, according to one or more aspects of this disclosure.

[0021] Figure 2 An example of a part of a wireless communication system is shown, which supports an enhanced technique for L1 identification of AIoT devices in a wireless communication system according to one or more aspects of this disclosure.

[0022] Figure 3A and Figure 3B An example of a signal flow is shown that supports one or more aspects of this disclosure for enhancing the L1 identifier of an AIoT device in a wireless communication system during a selection or unicast query process.

[0023] Figure 4A and Figure 4B An example of a signal flow is shown that supports one or more aspects of this disclosure for enhancing the L1 identifier of an AIoT device in a wireless communication system during the registration process.

[0024] Figure 5 An example of a signal flow is shown that supports an enhanced L1 identifier for AIoT devices in a wireless communication system, according to one or more aspects of this disclosure.

[0025] Figure 6 and Figure 7 A block diagram of a device is shown that supports enhanced techniques for L1 identification of AIoT devices in a wireless communication system, according to one or more aspects of this disclosure.

[0026] Figure 8 A block diagram of a communication manager is shown, which supports enhanced techniques for L1 identification of AIoT devices in wireless communication systems, according to one or more aspects of this disclosure.

[0027] Figure 9A diagram of a system of devices including techniques for enhancing L1 identification for AIoT devices in wireless communication systems, according to one or more aspects of this disclosure, is shown.

[0028] Figure 10 A flowchart illustrating a method for enhancing the L1 identifier of AIoT devices in a wireless communication system, according to one or more aspects of this disclosure, is shown. Detailed Implementation

[0029] Various aspects of this disclosure relate to techniques for querying wireless devices (e.g., Ambient Internet of Things (AIoT) devices) in wireless communication systems. For example, the described techniques provide means for a reader device to query one or more wireless devices (such as AIoT devices) in an surrounding computing environment to trigger the location, identification, or communication of the wireless devices. For instance, the surrounding computing environment may include one or more wireless devices that interact with one or more other devices (such as one or more reader devices capable of reading or detecting the wireless devices) to facilitate the provision of services, such as location tracking services, communication services, or identification services. The reader device may then communicate with one or more network devices (such as base stations) to further facilitate the provision of services. In some cases, it may be necessary to locate, identify, or communicate with wireless devices to provide services.

[0030] The aspects of this disclosure are first described in the context of a wireless communication system. These aspects are further illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to enhanced technologies for Layer 1 (L1) identification of AIoT devices in a wireless communication system.

[0031] Figure 1 An example of a wireless communication system 100 is illustrated, which supports enhanced techniques for L1 identification of AIoT devices in a wireless communication system according to one or more aspects of this disclosure. The wireless communication system 100 may include one or more devices, such as one or more network devices (e.g., network entity 105), one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-APro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein. As described herein, the term "paging" may refer to paging or enhanced paging in LTE, NR, or 6G systems, dedicated paging designed in a wireless system (e.g., an AIoT system), or a paging-like method using other terms (e.g., select, query, or other terms) for similar purposes.

[0032] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via communication link 125 (e.g., a radio frequency (RF) access link). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish communication link 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0033] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Examples of UE 115 are illustrated herein. The UE 115 described herein may be able to support communication with various types of devices in the wireless communication system 100 (e.g., other wireless communication devices, including UE 115 or network entity 105), such as... Figure 1 As shown.

[0034] As described herein, a node in the wireless communication system 100 (which may be referred to as a network node or wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. As another example, a node may be network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0035] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via backhaul communication link 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication link 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. The backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be one or more wired links (e.g., electrical links, fiber optic links) or one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof, or may include one or more wired links (e.g., electrical links, fiber optic links) or one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 may communicate with the core network 130 via communication link 155.

[0036] One or more network entities or network equipment described herein as network entity 105 or network equipment may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, node B, eNodeB (eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home node B, home evolution node B, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack physically or logically integrated within a single network entity (e.g., network entity 105 or a single RAN node, such as base station 140).

[0037] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across multiple network entities (e.g., network entity 105) such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a Central Unit (CU) such as CU 160, a Distributed Unit (DU) such as DU 165, a Radio Unit (RU) such as RU 170, a RAN Intelligent Controller (RIC) such as RIC 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a Service Management and Orchestration (SMO) system such as SMO system 180, or any combination thereof. RU 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities in network entity 105 of a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0038] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 (e.g., one or more CUs) can connect to DU 165 (e.g., one or more DUs) or RU 170 (e.g., one or more RUs) or a combination thereof, and DU 165, RU 170, or both can host lower protocol layers, such as L1 (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, media access control (MAC) layer) functionality and signaling, and can each be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can (e.g., via one or more different RUs, such as RU 170) support one or more different cells. In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by a different one of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by corresponding network entities (e.g., one or more network entities in network entity 105) that communicate via such communication links.

[0039] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities of network entity 105 (e.g., network entity 105 or IAB node 104) may be partially controlled by each other. IAB node 104 may be referred to as a donor entity or IAB donor. DU 165 or RU 170 may be partially controlled by CU 160 associated with network entity 105 or base station 140 (such as a donor network entity or donor base station). One or more donor entities (e.g., IAB donors) may communicate with one or more additional devices (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by one or more DUs (e.g., DU 165) of a coupled IAB donor. The IAB-MT may be equipped with a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include one or more DUs (e.g., DU 165) that support communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., IAB node 104, or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0040] When the techniques described herein are applied in the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support the tests described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., components such as IAB node, DU 165, CU 160, RU 170, RIC 175, SMO system 180).

[0041] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in various objects such as appliances, vehicles, or meters.

[0042] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that sometimes operate as repeaters, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0043] UE 115 and network entity 105 can wirelessly communicate with each other via communication link 125 (e.g., one or more access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined PHY layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more PHY layer channels for a given RAT (e.g., LTE, LTE-A, LTE-A Pro, NR). Each PHY layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating operation for the carrier, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 can be configured using multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities, such as one or more network entities in network entity 105).

[0044] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0045] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, in response This can represent the supported subcarrier spacing, while This can represent the supported Discrete Fourier Transform (DFT) size. The time interval for organizing communication resources can be based on radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0046] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems, such as wireless communication system 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0047] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0048] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include a common search space set configured to transmit control information to UE 115 (e.g., one or more UEs), or it may include a UE-specific search space set configured to transmit control information to UE 115 (e.g., a particular UE).

[0049] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas (such as coverage area 110). In some examples, coverage areas 110 associated with different technologies (e.g., different coverage areas) may overlap, but coverage areas 110 (e.g., different coverage areas) may be supported by the same network entity (e.g., network entity 105). In some other examples, overlapping coverage areas (such as coverage area 110) associated with different technologies may be supported by different network entities (e.g., network entity 105). The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different RATs to support communication to coverage areas 110 (e.g., different coverage areas).

[0050] Some UE 115 devices (such as MTC or IoT devices) can be relatively low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices with integrated sensors or instruments to measure or acquire information and relay such information to a central server or application that uses the information or presents it to people interacting with the application. Some UE 115 devices may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.

[0051] Some UE 115s can be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not involve concurrent transmission and reception). In some examples, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for UE 115 may include entering a power-saving deep sleep mode when not engaged in active communication, operating with limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a carrier's guard band, or outside a carrier.

[0052] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communication may include private or group communications and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritizing services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0053] In some examples, UE 115 may be configured to support direct communication with other UEs (e.g., one or more UEs in UE 115) via a device-to-device (D2D) communication link (such as D2D communication link 135) (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in the group performing D2D communication may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UEs 115 in this group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, a group of UEs 115 communicating via D2D communication can support a one-to-many (1:M) system, in which each UE 115 transmits to one or more UEs in the group. In some examples, network entity 105 can facilitate the scheduling of resources used for D2D communication. In some other examples, D2D communication can be performed between UEs 115 without involving network entity 105.

[0054] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), access and mobility management function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be transferred through user plane entities, which provide IP address allocation and other functions. User plane entities can connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0055] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the lower frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than one hundred kilometers).

[0056] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may employ licensed assisted access (LAA), LTE-Unlicensed (LTE-U) RAT, or NR technology using unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed frequency bands may be based on carrier aggregation configurations combined with component carriers operating with licensed frequency bands (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0057] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0058] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0059] Some wireless communication systems may include, operate within, or integrate with an ambient computing environment. Such ambient computing environments can use connected wireless devices (such as AIoT devices) to leverage information from the surrounding environment and provide intelligent services to users. In some cases, the wireless devices included in the ambient computing environment may include devices with energy harvesting (EH) capabilities (e.g., radio frequency identification (RFID) tags), devices without EH capabilities, battery-powered devices, or other wireless devices. Wireless devices may interact with one or more other devices in the ambient computing environment to provide services such as location tracking services, communication services, identification services, or other services. For example, wireless devices may interact with network devices (such as reader devices) that can detect or read wireless devices. In some cases, a reader device may be a UE 115 or a network entity 105 (such as a base station 140). The reader device may communicate with one or more other network devices (such as one or more other network entities 105) to provide services.

[0060] In some cases, the reader device may be instructed by network entity 105 to wake up (e.g., page) one or more wireless devices to trigger a transition from an idle or inactive state to an awake state in order to provide service. Thus, the reader device can communicate with one or more wireless devices. For example, the reader device may convey a message including first identification information associated with the wireless device. This message may also include a request for a second wireless device identifier associated with the wireless device, or may include an indication of a second wireless device identifier associated with the wireless device. The second wireless device identifier may have a bit length selected from a plurality of different bit lengths based on the type of the reader device or based on the identity of the wireless device. The reader device and the wireless device can then communicate with each other using the second wireless device identifier with the selected bit length. In some cases, the second wireless device identifier may have fewer bits than the first wireless device identifier, and communicating using the second wireless device identifier may be more efficient than communicating using the first wireless device identifier.

[0061] Figure 2 An example of a portion of a wireless communication system 200 is shown, illustrating an enhancement technique for L1 identification of AIoT devices in a wireless communication system according to one or more aspects of this disclosure. The wireless communication system 200 may include network entity 130-a, network entity 105-a, one or more reader devices 250 (e.g., UE reader device 250-a and base station reader device 250-b), and one or more wireless devices 215 (e.g., wireless devices 215-a, 215-b, 215-c, and 215-d). Network entity 130-a may be as referenced... Figure 1 The example described is the core network 130 or network entity 105. Network entity 105-a and base station reader device 250-b can be as shown in the reference. Figure 1 The network entity 105 or base station 140 described is an example. The UE reader device 250-a can be as shown in the reference. Figure 1 Example of UE 115 described. Network entity 130-a, network entity 105-a, UE reader device 250-a, base station reader device 250-b and one or more wireless devices 215 may communicate using communication links (such as communication links 125-a, 125-b, 125-c, 125-d and 125-e).

[0062] In some cases, network entity 130-a may provide services such as location tracking services, communication services, identification services, or other services associated with one or more wireless devices 215. In some cases, it may be necessary to locate one or more of the wireless devices 215. For example, wireless device 215 may be a low-power, low-complexity AIoT device, such as a tag (e.g., a radio frequency identifier (RFID) tag) attached to a suitcase, pet, key pair, or other item, and network entity 130-a may facilitate the provision of location tracking services for tracking the location of wireless device 215.

[0063] Wireless device 215 may have the lowest circuitry and processing power compared to other user equipment (such as UE 115), and may be smaller and cheaper than previous generations of IoT devices (such as Narrowband (NB)-IoT, Long Term Machine Type Evolution (LTE-M), and Enhanced Reduced Capability (eRedCap) IoT devices). These devices may also have the lowest energy storage capacity, and in some cases, the primary power source for such devices may be radio waves transmitted from signals (e.g., continuous wave or NR signals) from another device, such as a reader device (e.g., reader device 250). In some cases, wireless device 215 may employ technology similar to passive UHF RFID. Therefore, in some cases, due to low power, low complexity, and limited processing capabilities, wireless device 215 may not support certain standard features or functionalities compared to other user equipment or IoT devices. Furthermore, different wireless devices 215 may have different capabilities or support different functions. For example, in some cases, wireless device 215 may be a first-type wireless device 215 (e.g., device type 1) or a second-type wireless device 215 (e.g., device type 2).

[0064] The first type of wireless device 215 (e.g., device type 1) may be a wireless device with low complexity relative to other wireless devices 215. This type of wireless device may have the ability to store a limited amount of energy, but may not be able to generate signals independently. Alternatively, the first type of wireless device 215 may be an EH-capable device that utilizes backscattering to transmit one or more signals based on a received signal (e.g., an RF signal). For example, the first type of wireless device 215 may collect energy received from radio waves transmitted by a signal transmitted by the reader device 250. The first type of wireless device 215 may use the collected energy to perform backscattering to transmit one or more signals back to the reader device 250 that initially transmitted the signal or back to another device, such as by reflecting the received signal. These wireless devices 215 may have a peak power consumption of about 1 μW and a range of <13 meters (m) to about 33 meters (m).

[0065] The second type of wireless device 215 (e.g., device type 2) may have the ability to store a larger amount of energy compared to the first type of wireless device 215. This type of device can be further classified into various subtypes. For example, a first subtype of the second type of wireless device 215 (e.g., device type 2a) may be a wireless device with moderate complexity relative to other wireless devices 215. This type of wireless device may include energy storage, may have an initial sampling frequency offset (SFO) of up to 10 x (e.g., 10 times) parts per million (ppm), and may communicate based on backscattering of an external carrier. For example, this type of wireless device may have neither downlink amplification nor uplink amplification capabilities, and the device's uplink transmission may be based on backscattering of an externally provided carrier. Therefore, the primary energy source for this type of wireless device may be the received signal (e.g., an RF signal) from the reader device 250. These wireless devices 215 may have a peak power consumption of approximately 10 to 100 times μW and a range of approximately 22 m to 61 m.

[0066] A second subtype (e.g., device type 2b) of the second type of wireless device 215 can be a highly complex wireless device relative to other types of wireless devices 215. This type of wireless device may include energy storage, may have an initial SFO of up to 10 times the ppm, and may communicate based on an internally generated carrier. This type of wireless device may additionally have downlink or uplink amplification capabilities. Therefore, the device's uplink transmission may be generated independently by the device or may be a backscattering of an externally provided carrier. Thus, the primary energy source for this type of wireless device may be the received signal (e.g., an RF signal) from the reader device 250, or it may be solar energy. These wireless devices 215 may have peak power consumption of less than a few hundred μW and a range of approximately <100m to 300m.

[0067] In some cases, network entity 130-a may locate or track wireless device 215 with the assistance of one or more reader devices 250. Reader device 250 may refer to a device associated with network entity 130-a that can be used to detect or read one or more wireless devices in wireless device 215. For example, reader device 250 may be UE reader device 250-a or base station reader device 250-b. Network entity 130-a may communicate with UE reader device 250-a via network entity 105-a (through which UE reader device 250-a is connected). For example, network entity 130-a may transmit control signals (in some cases, these control signals may be paging signals or similar signals) to network entity 105-a, thereby instructing one or more UE reader devices 250-a to track, locate, or register one or more wireless devices in wireless device 215. Additionally or alternatively, network entity 130-a may communicate directly with base station reader device 250-b and may directly transmit control signals (in some cases, the control signals may be paging signals or similar signals) to base station reader device 250-b, thereby instructing base station reader device 250-b to track, locate, or register one or more wireless devices among wireless devices 215.

[0068] In some cases, network entity 130-a may wish to track or locate a specific wireless device 215, for example, to locate a wireless device 215-a attached to a lost suitcase. In other cases, network entity 130-a may wish to track or locate multiple wireless devices 215, for example, to receive location or other contextual information about multiple wireless devices 215. Locating multiple wireless devices 215 allows those wireless devices to be registered by the reader device 250 that locates them. This facilitates tracking and locating a specific wireless device 215 at a later time. For example, when reader device 250 locates a wireless device 215, reader device 250 may collect information associated with the located wireless device 215 (such as identification, location information, or other contextual information associated with reader device 250 or wireless device 215) and send that information to network entity 130-a or an AIoT server. Network entity 130-a or the AIoT server may store registration records from each reader device 250. In this way, when a specific wireless device 215 needs to be located at a later time, network entity 130-a can query the registration record to identify the last known reader device 250 that located (or registered) the specific wireless device 215. Network entity 130-a can then target one or more of the last known reader devices 250 that located the specific wireless device 215 to guide those one or more reader devices to locate the specific wireless device 215 again. In some cases, network entity 130-a may additionally or alternatively target other reader devices 250 to locate the specific wireless device 215.

[0069] When identifying a specific reader device 250 to be used in one or more wireless devices among tracking or locating wireless devices 215, network entity 130-a may transmit signals (such as control signals) to reader device 250 to instruct reader device 250 to page one or more wireless devices 215 to trigger one or more wireless devices 215 to wake up and send their identification information or other contextual information (such as location information). In some cases, such as when the reader device is a UE reader device 250-a, signals may be transmitted from network entity 130-a to reader device 250 via an intermediate network entity (such as network entity 105-a associated with UE reader device 250-a). For example, network entity 130-a may send signals to network entity 105-a to instruct network entity 105-a to instruct the managed UE reader device 250-a to page one or more wireless devices 215 to trigger wake-up.

[0070] Upon receiving a signal from network entity 130-a or network entity 105-a, reader device 250 may send a signal (such as a reader-to-device (R2D) paging signal). This signal may include an initial message 210 (e.g., initial message 210-a or initial message 210-b) that includes a command intended for one or more wireless devices among wireless devices 215. As an example, the command may be a selection command (or unicast query command) for selecting or identifying one or more specific wireless devices 215 (such as a target wireless device 215) for communication, or a query command (e.g., multicast, multicast, or broadcast query command) for initiating a registration process to identify wireless devices 215 within the range or coverage area of ​​reader device 250. However, initial message 210 may not be limited to including selection or query commands and may include other commands intended for one or more wireless devices among wireless devices 215, such as read, write, lock, sleep, terminate, or other wireless device commands.

[0071] For example, when reader device 250 wants to select a specific wireless device (such as target wireless device 215) (e.g., when the command included in initial message 210 includes a selection command or unicast query command for target wireless device 215), initial message 210 may be transmitted together with a first message 220 (e.g., first message 220-a or first message 220-b) that includes first identification information associated with target wireless device 215, such that target wireless device 215 can detect that first message 220 is intended for target wireless device 215. Initial message 210 and first message 220 may be a single message and may be referred to herein as first message 220. That is, reader device 250 may initially communicate with target wireless device 215 (e.g., to establish an initial connection or session) by addressing the initial communication (such as a first message 220) with first identification information associated with wireless device 215, such that target wireless device 215 can recognize that the first message 220 is intended for target wireless device 215, and that other wireless devices 215 not associated with the first identification information will recognize that the first message 220 is not intended for those wireless devices 215. In some cases, the first identification information may be referred to as a long identifier (ID). For example, the first identification information (e.g., a long ID) could be an application layer ID assigned by the application, such as an Electronic Product Code (EPC) identifier (e.g., a 96-bit identifier that can be used to uniquely identify a product within a product set); a hardware ID assigned by the manufacturer of wireless device 215, such as a tag ID (TID) or serial number; a network ID assigned by a 3GPP network; a prior identifier used to communicate with the target wireless device 215; a contention resolution ID (CRI); a global identifier for wireless device 215; an identifier that can uniquely identify wireless device 215; or other identifiers associated with the target wireless device 215.

[0072] In some cases, reader device 250 and target wireless device 215 may negotiate second identification information for further communication between reader device 250 and target wireless device 215. The second identification information may be temporary identification information with fewer bits than the first identification information, and communication using the second identification information may be more efficient than communication using the first identification information. In some cases, the second identification information may be referred to as a short ID. For example, the second identification information (e.g., a short ID) may be a Layer 1 identifier (L1-ID) used for communication (e.g., unicast communication) between reader device 250 and target wireless device 215 over a period of time (e.g., during the duration of a session between reader device 250 and target wireless device 215). In some cases, reader device 250 may signal to wireless device 215 that the second identification information is valid for a duration (e.g., the session duration) in the communication between reader device 250 and wireless device 215. In some cases, the second identification information may remain valid for communication until explicitly or implicitly released or invalidated by the reader device 250. For example, the reader device 250 may lock the tag's L1-ID for a certain period of time, a certain clock count, or a certain communication session (e.g., configured to the tag or predefined in the wireless specification) until the reader device 250 releases the tag's L1-ID. This locking mechanism may be an example of the validity and invalidation techniques described herein.

[0073] In some cases, the second identification information may be a group ID used for communication (e.g., multicast communication) between the reader device 250 and a group of wireless devices. In some cases, the second identification information may be a random or pseudo-random value, such as RN16 (e.g., a 16-bit random number or a 16-bit pseudo-random number); identification information derived from the first identification information, such as a portion of the first identification information, a hash version of the first identification information, or other decoding schemes; a group ID; or other identification information used for temporary communication between the reader device 250 and the target wireless device 215 (or a group of target wireless devices).

[0074] In some cases, the second identification information may be assigned by the reader device 250 (e.g., generated, configured, determined, selected, or provided), and in other cases, the second identification information may be assigned by the target wireless device 215.

[0075] Therefore, when the second identification information is allocated by the target wireless device 215, the first message 220 from the reader device 250 to the target wireless device 215 (e.g., first message 220a or first message 220-b) may additionally include a request for the allocation of the second identification information associated with the target wireless device 215. In some cases, this request may indicate a specific length to be associated with the second identification information, for example, a specific bit length. That is, the reader device 250 may request an L1-ID with a specific number of bits from the target wireless device 215. The specific bit length requested for the second identification information may be selected from a plurality of different bit lengths, such as 8 bits, 16 bits, 24 bits, or another number of bits, and this specific bit length is indicated in the first message 220. Upon receiving the first message 220, the target wireless device 215 may determine whether the first message 220 is intended for the target wireless device 215 by comparing the first identification information with its own identification information. If there is at least a partial match between the identification information, the target wireless device 215 can determine that the first message 220 is intended for the target wireless device 215 and can allocate second identification information having the requested bit length. The target wireless device 215 can send a second message 230 (e.g., second message 230-a or second message 230-b) to the reader device 250, including an indication of the second identification information having the requested bit length. After the reader device 250 receives the second message 230, the reader device 250 and the target wireless device 215 can communicate with each other using the second identification information (such as including the second identification information in one or more messages) for at least a period of time, such as the duration of a session between the reader device 250 and the target wireless device 215 or some other period of time.

[0076] When the second identification information is assigned by reader device 250 (rather than target wireless device 215), the first message 220 from reader device 250 to target wireless device 215 (e.g., first message 220a or first message 220-b) may include the second identification information assigned by reader device 250. In this case, the second identification information may also have a bit length selected from a plurality of different bit lengths. Upon receiving the first message 220 and determining that the first message is intended for target wireless device 215 (e.g., based on comparing the first identification information included in the first message 220 with the identification information of target wireless device 215), target wireless device 215 may send a second message 230 to reader device 250 including the second identification information assigned by reader device 250. In some cases, the second message 230 may be used as feedback or acknowledgment (e.g., an ACK message) indicating that target wireless device 215 has successfully received the first message 220. After the reader device 250 receives the second message 230, the reader device 250 and the target wireless device 215 may communicate with each other for at least a period of time, such as the duration of the session between the reader device 250 and the target wireless device 215 or some other period of time, using the second identification information (such as including the second identification information in one or more messages).

[0077] In some cases, such as when reader device 250 wants to register wireless devices 215 within its range or coverage area (e.g., when the command included in initial message 210 includes a query command (e.g., a multicast, broadcast, or broadcast query command)), initial message 210 may be transmitted without first identification information associated with a specific wireless device 215. That is, in some cases, initial message 210 may not target a specific wireless device 215, but can be used to identify those wireless devices 215 within the coverage area of ​​reader device 250 (or those wireless devices 215 that meet other criteria articulated by one or more parameters associated with the query command). In such cases, one or more wireless devices 215 within the coverage area of ​​reader device 250 can detect initial message 210 and recognize (based on the omission of first identification information) that initial message 210 is intended to register one or more wireless devices 215. In this case, initial message 210 and first message 220 (including the identification associated with the target wireless device 215) may not be a single message. Based on the determination by one or more wireless devices 215 that the initial message 210 is intended to register one or more wireless devices 215, each of the one or more wireless devices 215 may respond by sending a first message 220 to the reader device 250 (in this example, the first message 220 is sent from the wireless device 215 to the reader device 250). In this case, the first message 220 may include first identification information associated with the responding wireless device 215 (e.g., an EPC ID or other first identification information as described above). Upon receiving the first message 220 from the wireless device 215, the reader device 250 may assign second identification information to be associated with the wireless device 215 (e.g., an L1-ID or other second identification information as described above). That is, the reader device 250 may assign second identification information to each wireless device 215 responding to the initial message 210 (e.g., a query command). The reader device 250 may assign second identification information with a specific bit length selected from a plurality of different bit lengths. In some cases, the second identification information assigned to different wireless devices may have different bit lengths. Reader device 250 may send a second message 230 to each of the wireless devices 215, including an indication of second identification information associated with that wireless device 215 and having a selected bit length (in this example, the second message 230 is sent from reader device 250 to wireless device 215). In some cases, the second message 230 may also include an indication of the first identification information, such that wireless device 215 can recognize upon receiving the second message 230 that the second message 230 is intended for wireless device 215. In some cases, the second message 230 may serve as feedback or acknowledgment (e.g., an ACK message) that reader device 250 has successfully received the first message 220 from wireless device 215.After receiving the second message 230, the reader device 250 and the wireless device 215 may communicate with each other for at least a period of time, such as the duration of the session between the reader device 250 and the wireless device 215, or some other period of time, using the second identification information (such as including the second identification information in one or more messages).

[0078] In some cases, when reader device 250 wants to register wireless devices 215 within its range or coverage area, instead of reader device 250 assigning second identification information to one or more wireless devices 215 in response to initial message 210 (e.g., a query command), one or more wireless devices 215 may assign their own second identification information and signal the second identification information to reader device 250. In such cases, the first message 220 from wireless device 215 to reader device 250 may include the second identification information assigned by wireless device 215. In this case, the second identification information may also have a bit length selected from a plurality of different bit lengths. Upon receiving the first message 220, reader device 250 may send a second message 230 to wireless device 215 including the second identification information assigned by wireless device 215. In some cases, the second message 230 may serve as feedback or acknowledgment (e.g., an ACK message) that reader device 250 has successfully received the first message 220 from wireless device 215. After receiving the second message 230, the reader device 250 and the wireless device 215 may communicate with each other for at least a period of time, such as the duration of a session between the reader device 250 and the target wireless device 215, or some other period of time, using the second identification information (such as including the second identification information in one or more messages).

[0079] Figure 3A and Figure 3B Examples of signal flows 300a and 300b, respectively, are shown, according to one or more aspects of this disclosure, supporting techniques for enhancing the L1 identifier of AIoT devices in a wireless communication system during a selection or unicast query process. In some aspects, signal flows 300a and 300b may implement as described in references to... Figure 1 and Figure 2 The described aspects of the wireless communication system 100 or 200 may be implemented by or by aspects of these wireless communication systems. Signal flow 300a may exemplify the signal flow between wireless device 315a and reader device 350a. Signal flow 300b may exemplify the signal flow between wireless device 315b and reader device 350b. Wireless devices 315a and 315b may be as described in the reference... Figure 2 An example of a wireless device in the described wireless device 215. Reader devices 350a and 350b may be as shown in the reference. Figure 2Examples of the described UE reader device 250-a or base station reader device 250-b.

[0080] refer to Figure 3A In some implementations, in response to a signal received from a network entity by reader device 350a indicating the location of a specific wireless device (such as wireless device 315a) or otherwise communicating with a specific wireless device, reader device 350a may send a signal including a first message 320a addressing wireless device 315a. The first message 320a may be sent via a physical reader to a device channel (PRDCH) (or in some cases may be included in a MAC control element (MAC-CE)). The first message 320a may include a preamble portion 320a-a, a broadcast type portion 320a-b, a control portion 320a-c, and a data portion 320a-c. The first message 320a may additionally or alternatively include one or more other portions not mentioned. In some cases, the first message 320a may be a reference. Figure 2 Examples of the described initial message 210, first message 220, or combinations thereof.

[0081] The first message 320a may include wireless device commands (e.g., tag commands). For example, the first message 320a may include a selection command or a unicast query command for selecting wireless device 315a for communication (the type of wireless device command included in the first message 320a is not limited to selection or unicast query commands, but may include other types of wireless device commands, such as read, write, terminate, lock, sleep, or other wireless device commands). One or more bits of the first message 320a (e.g., a forward link packet) may be used to indicate the wireless device commands in the first message 320a. Additionally, the broadcast portions 320a-b may include one or more bits indicating the broadcast type of the first message (e.g., unicast, multicast, or broadcast). For example, an indication of whether the first message 320a is a broadcast message may include one bit, and an indication of whether the first message 320a is unicast, multicast, or multicast may include multiple bits. In some cases, broadcast portions 320a-b may be included before or within the control portions 320a-c of the first message 320a (such as when the control portions 320a-c and data portions 320a-d are separate channels (such as a control channel and a PRDCH)). In some cases, different preambles (e.g., different delimiters) may be present to indicate the broadcast type. For example, a preamble with a single bit set to a first value (e.g., "0") may indicate that the first message 320a is a broadcast message, and a preamble with a single bit set to a second value (e.g., "1") may indicate that the first message 320a is not a broadcast message. In another example, a preamble with multiple bits may indicate that the first message 320a is a broadcast, unicast, or multicast message. For example, a preamble with multiple bits set to a first value (e.g., "00") can indicate that the first message 320a is a broadcast message, a preamble with multiple bits set to a second value (e.g., "10") can indicate that the first message 320a is a unicast message, and a preamble with multiple bits set to a third value (e.g., "01") can indicate that the first message 320a is a multicast message. The preamble may precede the control portion of the first message 320a.

[0082] The first message 320a may additionally include identification information associated with the wireless device 315a, enabling the wireless device 315a to detect that the first message 320a is intended for the wireless device 315a. The identification information may be a first wireless device ID 340a. The first wireless device ID 340a may be a reference... Figure 2The long ID described. The first wireless device ID 340a may be included in the data portions 320a-d of the first message 320a, or alternatively in the control portions 320a-c of the first message 320a. In some cases, different portions of the first wireless device ID 340a may be included in different portions of the first message 320a (e.g., the first portion of the first wireless device ID 340a may be included in the control portions 320a-c, and the remaining portions of the first wireless device ID 340a may be included in the data portions 320a-d, or vice versa).

[0083] In some cases, the first message 320 may additionally include a request for allocating or instructing a second wireless device ID 345a for subsequent communication between the reader device 350a and the wireless device 315a. The second wireless device ID 345a may be a temporary wireless device ID that may have fewer bits than the first wireless device ID 340a. The second wireless device ID 345a may be a reference... Figure 2 The described short ID (e.g., L1-ID). Communicating using the second wireless device ID 345a is more efficient than communicating using the longer first wireless device ID 340a.

[0084] The request may also indicate a specific length to be associated with the second wireless device ID 345a, for example, a specific bit length 360. That is, the reader device 350a may request the second wireless device ID 345a with a specific number of bits from the wireless device 315a. The bit length 360 requested for the second wireless device ID 345a may be selected from a plurality of candidate bit lengths, such as 8 bits, 16 bits, 24 bits, or another number of bits. The reader device 350a may select the bit length 360 based on: the type of the reader device 350a, the number of wireless devices in the coverage area of ​​the reader device 350a, the broadcast type associated with one or more messages to be transmitted between the reader device 350a and the wireless device 315a, the identity of the wireless device 315a, or a combination thereof.

[0085] For example, in some cases, different types of reader devices 350a may be able to support a second radio device ID 345a with a different bit length 360 (e.g., different length L1-ID). For example, in a UE reader device 350a (such as reference...) Figure 2 In the case of the described reader device 250-a), because the UE reader device 350a may have a relatively small coverage area (such as with the base station reader device 350a (such as reference) Figure 2Compared to the coverage area of ​​the described reader device 250-b), the UE reader device 350a can support a second radio device ID 345a with a relatively short bit length 360 (e.g., 8 bits or 16 bits). Similarly, when the reader device 350a is a base station reader device 350a, because the base station reader device 350a can have a relatively large coverage area, the base station reader device 350a can support a second radio device ID 345a with a longer bit length 360 (e.g., 8 bits, 16 bits, or 24 bits) than the bit length supported by the UE reader device 350a. This may be because the base station reader device 350a may have more radio devices in the coverage area (e.g., relative to the UE reader device 350a), and to ensure that the second radio device ID 345a is unique among those radio devices in the coverage area, a relatively long second radio device ID 345a may be needed to avoid ID conflicts.

[0086] Additionally or alternatively, reader device 350a may determine or select the bit length 360 of the second wireless device ID 345a based on the broadcast type (e.g., unicast, multicast, or broadcast) associated with one or more messages to be transmitted between reader device 350a and wireless device 315a. Different bit lengths 360 may be associated with different broadcast types. For example, the bit length 360 selected for multicast communication may be relatively shorter (e.g., 8 bits or 16 bits) compared to the bit length 360 selected for unicast communication (e.g., 8 bits, 16 bits, or 24 bits). This may be because the number of groups used for multicast communication may be relatively small (compared to the number of individual wireless devices used for unicast communication), and therefore, the second wireless device ID 345a may require fewer bits to ensure uniqueness among those groups.

[0087] Additionally or alternatively, the reader device 350a may determine or select the bit length 360 of the second wireless device ID 345a based on the number of wireless devices in the coverage area of ​​the reader device 350a. For example, different numbers of wireless devices in the coverage area of ​​the reader device 350a may be mapped to different bit lengths 360. For example, if the number of wireless devices in the coverage area of ​​the reader device 350a meets a first threshold (e.g., less than or equal to a first number of wireless devices), a first bit length 360 may be selected, and if the number of wireless devices in the coverage area of ​​the reader device 350a meets a second threshold (e.g., greater than the first number of wireless devices), a second bit length 360 may be selected. In one example, the selected bit length may correspond to the number of wireless devices, wherein a longer bit length may be used when the number of wireless devices exceeds the threshold, and a shorter bit length may be used when the number of wireless devices is less than or equal to the threshold.

[0088] Additionally or alternatively, reader device 350a may determine or select the bit length 360 of the second wireless device ID 340a based on the identity of wireless device 315a (e.g., based on a first wireless device ID 345a or other identification information associated with wireless device 315a). For example, different wireless devices may be associated with different bit lengths 360. Reader device 350a may signal which bit length 360 of the second wireless device ID 345a to use, generate, or use and generate based on the identity or type of wireless device 315a.

[0089] In some cases, reader device 350a may use one or more lookup tables to determine or select the bit length 360 of the second wireless device ID 345a. One or more lookup tables may include an association between the bit length 360 and the type of reader device 350a, the threshold number of wireless devices in the coverage area, the broadcast type, or the wireless device identity.

[0090] The selected bit length 360 may be indicated in the data portions 320a-d of the first message 320a, or alternatively, in the control portions 320a-c of the first message 320a. In some cases, the inclusion of the selected bit length 360 may be an implicit indication of a request to assign a second wireless device ID 345a to the wireless device 315a.

[0091] Upon receiving a first message 320a from reader device 350a, wireless device 315a can determine whether the first message 320a is intended for wireless device 315a by comparing the first wireless device ID 340a included in the first message 320a with its own identification information. If at least a partial match exists, wireless device 315a can determine that the first message 320a is intended for wireless device 315a and can assign a second wireless device ID 345a having a bit length of 360 indicated in the first message 320a.

[0092] In some cases, signaling may implicitly indicate whether a previously assigned second wireless device ID is valid or no longer valid. In one example, the omission of the second wireless device ID in the first message 320a (e.g., a selection command or unicast query message) could be an indication that wireless device 315a is reusing a previously assigned second wireless device ID. For example, in some cases, reader device 350a and wireless device 315a may have previously negotiated or assigned a second wireless device ID for temporary communication between reader device 350a and wireless device 315a, and wireless device 315a may use the previously assigned second wireless device ID as the second wireless device ID 345a.

[0093] Wireless device 315a may send a second message 330a to reader device 350a, the second message including an indication of a second wireless device ID 345a having a bit length of 360 (e.g., a random or pseudo-random number having a bit length of 360 used as the second wireless device ID 345a). For example, in some cases, wireless device 315a may be an EH-capable device capable of collecting or storing energy from received signals transmitted by reader device 350a (e.g., a signal including the first message 320a). Wireless device 315a may use the energy from the received signals to send one or more backscattered signals (or in some cases, non-backscattered signals) including the second message 330a back to reader device 350a (or in some cases, to different reader devices). For example, in response to detecting the first message 320a and determining that the first message 320a is intended for wireless device 315a, wireless device 315a may send the second message 330a back to reader device 350a.

[0094] The second message 330a may include a preamble portion 330a-a and a data portion 330a-b. The data portion 330a-b may include feedback 355a, such as an ACK message acknowledging that the first message 320a was successfully received by the wireless device 315a. For example, one or more bits of the feedback 355a (such as a predefined bit sequence) may be used to indicate an ACK message. The feedback 355a may also include an indication of a second wireless device ID 345a, and the indication of the second wireless device ID 345a itself may serve as an ACK message.

[0095] Reader device 350a may receive a second message 330a including a second wireless device ID 345a. After reader device 350a receives the second message 330a, reader device 350a and wireless device 315a may communicate with each other (e.g., send or receive one or more messages) using the second wireless device ID 345a (such as including the second wireless device ID 345a in one or more messages) for at least a period of time, such as the duration of a session between reader device 350a and wireless device 315a or some other period of time.

[0096] refer to Figure 3BIn some specific implementations, in response to a signal received from a network entity by reader device 350b indicating the location of a specific wireless device (such as wireless device 315b) or otherwise communicating with a specific wireless device, reader device 350a may send a first message 320b including a select or unicast query command and addressing wireless device 315b. (The type of wireless device command included in the first message 320b is not limited to a select or unicast query command, but may include other types of wireless device commands, such as read, write, terminate, lock, sleep, or other wireless device commands.) However, in this example, instead of reader device 350b requesting wireless device 315b to allocate second identification information, reader device 350b may allocate the second identification information itself. For example, reader device 350b may allocate a second wireless device ID 345b for temporary communication with wireless device 315b, and may indicate the second wireless device ID 345b to wireless device 315b. In some cases, the second wireless device ID 345b assigned by the reader device 350b may be a previously negotiated or assigned second wireless device ID used for communication between the reader device 350b and the wireless device 315b. For example, in some cases, such as when the second wireless device ID 345b remains valid (e.g., the usage period of the second wireless device ID 345b has not yet expired), the reader device 350b may assign a previous second wireless device ID 345b. In other cases, the reader device 350b may assign a new second wireless device ID 345b.

[0097] Reader device 350b may indicate second wireless device ID 345b in first message 320a. First message 320b may include a preamble portion 320b-a, a broadcast type portion 320b-b, a control portion 320b-c, and a data portion 320b-c. First message 320b may additionally or alternatively include one or more other portions not mentioned. First message 320b may otherwise be similar to... Figure 3A The first message 320a, but instead of including an indication of a request for second identification information associated with the wireless device 315b, may alternatively include a second wireless ID 345b assigned by the reader device 350b.

[0098] The second wireless device ID 345b assigned by reader device 350b may have a bit length selected by reader device 350b. (See reference...) Figure 3AAs described, the bit length 360 of the second wireless device ID 345b can be selected from a plurality of candidate bit lengths based on: the type of reader device 350b, the number of wireless devices in the coverage area of ​​reader device 350b, the broadcast type associated with one or more messages to be transmitted between reader device 350b and wireless device 315b, the identity of wireless device 315b, or a combination thereof. The second wireless device ID 345b with the selected bit length may be indicated in the data portion 320b-d of the first message 320b, or alternatively, in the control portion 320b-c of the first message 320b. In some cases, the bit length may be additionally included in the first message 320b.

[0099] Upon receiving a first message 320b from reader device 350b, wireless device 315b can determine whether the first message 320b is intended for wireless device 315b by comparing the first wireless device ID 340a included in the first message 320b with its own identification information. If at least a partial match exists, wireless device 315b can determine that the first message 320b is intended for wireless device 315b and can further detect a second wireless device ID 345b with a selected bit length. In some cases, such as when wireless device 315b is capable of supporting at most a single second wireless device ID, reception of the first message 320b including the second wireless device ID 345b assigned by reader device 350b can invalidate any previously assigned second wireless device IDs used in previous communications between reader device 350b and wireless device 315b. In some examples, the reader can send a control message to configure the tag with a new L1-ID, which can also explicitly or implicitly indicate that the tag's previous L1-ID is invalid.

[0100] Wireless device 315b can send a second message 330b to reader device 350b, the second message including an indication of a second wireless device ID 345b assigned by reader device 350b and included in a first message 320b. The second message 330b may include a preamble portion 330b-a and a data portion 330b-b. The second message 330b may be similar to... Figure 3A The second message 330a, but the second wireless device ID 345b included in the feedback 355b can be the second wireless device ID 345b assigned by the reader device 350b.

[0101] Reader device 350b may receive a second message 330b including a second wireless device ID 345b. Receipt of the second message 330b by reader device 350b may be an indication that the first message 320b and the second wireless device ID 345b included in the first message have been successfully received by wireless device 315b. After reader device 350b receives the second message 330b, reader device 350b and wireless device 315b may communicate with each other (e.g., send or receive one or more messages) using the second wireless device ID 345b (such as by including the second wireless device ID 345b in one or more messages) for at least a period of time, such as the duration of a session between reader device 350b and target wireless device 315b or some other period of time.

[0102] Figure 4A and Figure 4B Examples of signal flows 400a and 400b, according to one or more aspects of this disclosure, are illustrated, which support techniques for enhancing the L1 identifier of AIoT devices in a wireless communication system during the registration process. In some aspects, signal flows 400a and 400b may implement, as described in references respectively... Figure 1 and Figure 2 The described aspects of the wireless communication system 100 or 200, or aspects thereof, can be implemented by these wireless communication systems. Signal flow 400a may exemplify the signal flow between wireless device 415a and reader device 450a. Signal flow 400b may exemplify the signal flow between wireless device 415b and reader device 450b. Wireless devices 415a and 415b may be as described in the reference... Figure 2 , Figure 3A and Figure 3B Examples of one of the described wireless devices 215, 315a, or 315b. Reader devices 450a and 450b may be as described in the reference. Figure 2 , Figure 3A or Figure 3B Examples of the described UE reader device 250-a, base station reader device 250-b, reader device 350a, or reader device 350b.

[0103] refer to Figure 4A In some specific implementations, in response to reader device 450a receiving a signal from a network entity that registers (e.g., identifies) a wireless device in the coverage area of ​​reader device 450a, reader device 450a may send an initial message (such as a registration message including a query command, e.g., a reference). Figure 2The described initial message 210) signals to notify wireless devices within the coverage area of ​​reader device 450a to respond to the message. In some cases, one or more wireless devices (such as wireless device 415a) may respond to the registration message by transmitting a first message 420a back to reader device 450a.

[0104] The first message 420a may include a preamble portion 420a-a and a data portion 420a-c. The first message 420a may additionally or alternatively include one or more other portions not mentioned. In some cases, the first message 420a may be a reference. Figure 2 An example of the first message 220 described. To identify the wireless device 415a responding to the registration message, the first message 420a may include an indication of a first wireless device ID 440a associated with the wireless device 415a. The first wireless device ID 440a may be a reference... Figure 2 The described long ID (e.g., an EPC ID with, for example, 96 bits to uniquely identify wireless device 315b within a group of wireless devices). In response to receiving a registration message from reader device 450a, wireless device 415a may send a first message 420a to reader device 450a including a first wireless device ID 440a, such that reader device 450a can identify the responding wireless device 415a.

[0105] Upon receiving the first message 420a, the reader device 450a may assign a second wireless device ID 445a for further communication between the reader device 450a and the wireless device 415a. The second wireless device ID 445a may be a reference... Figure 2 The described short ID (e.g., L1-ID). In some cases, the second wireless device ID 445a assigned by reader device 450b may be a wireless device ID previously negotiated or assigned for communication between reader device 450a and wireless device 415a. For example, in some cases, such as when the second wireless device ID 445a remains valid (e.g., the usage time of the second wireless device ID 445a has not yet expired), reader device 450a may assign a previous second wireless device ID 445a. In other cases, reader device 450a may assign a new second wireless device ID 445a. For example, reader device 450a may determine the bit length of the second wireless device ID 445a, such as by referring to... Figure 3A and Figure 3B The described, and assignable, second wireless device ID 445a with a defined bit length.

[0106] The reader device 450a may send a second message 430a to the wireless device 415a, the second message including an indication of a first wireless device ID 440a and an indication of a second wireless device ID 445a having a determined bit length. In some cases, such as during registration contention resolution, the first wireless device ID 440a sent along with the assigned second wireless device ID 445a may be a CRI, a globally unique identifier of the wireless device identifier, or other identifier that uniquely identifies the wireless device 415a (such as a reference criterion). Figure 2 The long ID described herein. Including the first wireless device ID 440a in this way can mitigate ID contention when the second message 430a is received at one or more wireless devices within the coverage area of ​​the reader device 450a by ensuring that the second message 430a is uniquely addressed to the target wireless device (such as wireless device 415a).

[0107] In some cases, reader device 450a may send a second message 430a that includes an indication of the first wireless device ID 440a, but omits the indication of the second wireless device ID 445a. The omission of the second wireless device ID 445a may be an indication that wireless device 415a reuses a previously assigned second wireless device ID.

[0108] The second message 430a can be similar to Figure 3B The second message 330b. The second message 430a may be transmitted via PRDCH (or may be included in MAC-CE in some cases). The second message 430a may include a preamble portion 430a-a, a broadcast type portion 430a-b, a control portion 430a-c, and a data portion 430a-c. The second message 430a may additionally or alternatively include one or more other portions not mentioned. The first radio device ID 440a or the second radio device ID 445a may be included in one or more portions of the second message 430a (e.g., the data portion 430a-c or the control portion 430a-c), such as references. Figure 3B As described. In some cases, the bit length associated with the second wireless device ID 445a may also be included in the second message 430a.

[0109] Wireless device 415a can receive second message 430a and can determine that second message 430a is intended for wireless device 415a based on at least a partial match between the first wireless device ID 440a included in the second message and the identification information of wireless device 415a. Then, reader device 450a and wireless device 415a can communicate with each other (e.g., send or receive one or more messages) using the second wireless device ID 445a (such as including the second wireless device ID 445a in one or more messages) for at least a period of time, such as the duration of a session between reader device 450a and wireless device 415a or some other period of time.

[0110] refer to Figure 4B In some implementations, in response to reader device 450b receiving a signal from a network entity indicating that a wireless device in its coverage area is registered, reader device 450b may send an initial message (such as a registration message) to signal that the wireless devices in its coverage area should respond to the message. In some cases, one or more wireless devices (such as wireless device 415b) may respond to the registration message by transmitting a first message 420b back to reader device 450b. However, in this example, instead of reader device 450b assigning second identification information, wireless device 415b may assign the second identification information itself after receiving the registration message from reader device 450b.

[0111] For example, wireless device 415b may, in response to registration, assign a second wireless device ID 445b for temporary communication with reader device 450b and may indicate the second wireless device ID 445b to reader device 450b. For example, in response to receiving a registration message (such as a reference message) from reader device 450b... Figure 2 The described initial message 210 (which signals a wireless device in the coverage area of ​​reader device 450b to respond to the registration message) allows wireless device 415b to transmit a first message 420b back to reader device 450b to identify itself as being in the coverage area of ​​reader device 450b.

[0112] The first message 420b may include a preamble portion 420b-a and a data portion 420b-c. The first message 420b may additionally or alternatively include one or more other portions not mentioned. In some cases, the first message 420b may be a reference. Figure 2 An example of the first message 220 described. To identify the wireless device 415b responding to the registration message, the first message 420b may include an indication of a first wireless device ID 440b associated with the wireless device 415b. The first wireless device ID 440b may be a reference... Figure 2The described long ID (e.g., EPC ID). The first message 420b may also include an indication of a second wireless device ID 445b for further temporary communication between the wireless device 415b and the reader device 450b. The second wireless device ID 445b may be a reference... Figure 2 The short ID described (e.g., L1-ID).

[0113] In some cases, the second wireless device ID 445b assigned by wireless device 415b may be a wireless device ID previously negotiated or assigned for communication between reader device 450b and wireless device 415b. For example, in some cases, such as when the second wireless device ID 445b remains valid (e.g., the usage period of the second wireless device ID 445b has not yet expired), wireless device 415b may assign a previous second wireless device ID 445b. Additionally or alternatively, in some cases, registration messages (such as references) Figure 2 The described initial message 210 (or another forward link control message) may include an indication of whether the wireless device 415 should reuse a previously assigned second wireless device ID (e.g., one or more bits in the control portion of the registration message), or may include a time-lapse indication of the validity of the previously assigned second wireless device ID. In some cases, the registration message may include a dedicated command indicating the validity of the previously assigned second wireless device ID (e.g., the validity of reuse).

[0114] In other cases, wireless device 415b may assign a new second wireless device ID 445b. For example, in some cases, the registration message may include a dedicated command indicating that the previously assigned second wireless device ID is invalid and not to be reused. For example, if the previously assigned second wireless device ID was valid for at most one session, the registration message may include a "session end" command to signal the end of the session and to signal that the previously assigned second wireless device ID is no longer valid. In some cases, the dedicated command may be a unicast command, a multicast command, a multicast command instructing multiple unicast wireless devices, or a broadcast command. In some cases, the reception of a registration message triggers the invalidation of the previously assigned second wireless device ID. For example, when a new reader device sends a registration message, a command, or both to the tag, the previously assigned second wireless device ID (e.g., the previous L1-ID) may become invalid.

[0115] For example, wireless device 415b can determine the bit length of the second wireless device ID 445b (such as a reference). Figure 3A and Figure 3BAs described above, a second wireless device ID 445b with a defined bit length can be assigned. In some cases, the bit length associated with the second wireless device ID 445a may also be included in the first message 420b.

[0116] Therefore, in response to receiving a registration message from reader device 450b, wireless device 415b may send a first message 420b to reader device 450b, including a first wireless device ID 440b and a second wireless device ID 445b, so that reader device 450b can identify the responding wireless device 415b.

[0117] Upon receiving the first message 420b, the reader device 450b may send a second message 430b, which includes an indication of the first wireless device ID 440b, a second wireless device ID 445b assigned by the wireless device 415b and included in the first message 420b, or both. The second message 430b may be an acknowledgment that the reader device 450b has successfully received the first message 420b and the second wireless device ID 445b in the first message. The second message 430b may be similar to... Figure 3B The second message 430b. The second message 430b may be transmitted via PRDCH (or may be included in MAC-CE in some cases). The second message 430a may include a preamble portion 430b-a, a broadcast type portion 430b-b, a control portion 430b-c, and a data portion 430b-c. The second message 430b may additionally or alternatively include one or more other portions not mentioned. The first radio device ID 440b and the second radio device ID 445b may be included in one or more portions of the second message 430b (e.g., the data portion 430b-c or the control portion 430b-c), such as references. Figure 3B As described.

[0118] Wireless device 415b can receive the second message 430b and can determine that the second message 430b is intended for wireless device 415b based on at least a partial match between the first wireless device ID 440b included in the second message and the identification information of wireless device 415b. Then, reader device 450b and wireless device 415b can communicate with each other (e.g., send or receive one or more messages) using the second wireless device ID 445b (such as by including the second wireless device ID 445b in one or more messages) for at least a period of time, such as the duration of a session between reader device 450b and wireless device 415b or some other period of time.

[0119] Figure 5Examples of signal flow 500 supporting techniques for enhancing L1 identification of AIoT devices in wireless communication systems, according to one or more aspects of this disclosure, are shown. In some examples, process flow 500 may be implemented as described in reference 1. Figure 1 , Figure 2 , Figure 3A , Figure 3B , Figure 4A and Figure 4B The described wireless communication systems 100 and 200 and signal flows 300a, 300b, 400a and 400b are aspects of, or implemented by, these aspects. Process flow 500 may exemplify the signal flow between reader device 550 and wireless device 515. In the following description of process flow 500, communication between reader device 550 and wireless device 515 may be transmitted in a different order than the example order shown, or operations performed by reader device 550 and wireless device 515 may be performed in a different order or at different times. Some operations may also be omitted from process flow 500, and other operations may be added to process flow 500. In some examples, the operations exemplified in process flow 500 may be performed by hardware (e.g., including circuits, processing blocks, logic components and other components), code executed by a processor (e.g., software or firmware), or any combination thereof. Alternative examples are possible, in which some steps are performed in a different order than described or not at all. In some cases, steps may include additional features not mentioned below, or other steps may be added.

[0120] At step 510, reader device 550 may assign a second wireless device ID to wireless device 515 for temporary communication between devices. For example, see reference... Figure 3B and Figure 4A As described, reader device 550 can locate or register (e.g., select or query) wireless device 515 and send a message including an indication of a second wireless device ID having a bit length selected from a plurality of different bit lengths (e.g., Figure 3B First message 320b or Figure 4A The second message 430a). The second wireless device ID can be a reference. Figure 2 Examples of short IDs (e.g., L1-IDs) as described.

[0121] At step 520, after the second wireless device ID is assigned, the wireless device 515 and the reader device 550 may communicate with each other (e.g., send or receive one or more messages) using the second wireless device ID (such as including the second wireless device ID in one or more messages) for at least a period of time, such as the duration of the session between the reader device 550 and the wireless device 515 or some other period of time.

[0122] At step 530, the wireless device 515 may move to a new location. For example, the wireless device 515 may move to a new location outside the coverage area of ​​the reader device 550. In such a case, the reader device 550 may not be aware that the wireless device 515 has moved outside the coverage area of ​​the reader device.

[0123] At step 540, reader device 550 may attempt to communicate with wireless device 515 after wireless device 515 has moved (e.g., sending commands to wireless device 515, such as read, query, write, allo_req_new_L1_ID, or other commands), and may not receive a response from wireless device 515, or in some cases may receive a NACK message from wireless device 515. A timer or counter may be configured at reader device 550, and reader device 550 may attempt to communicate a threshold number of times (e.g., a first threshold number of times) or a threshold amount of time (e.g., a first threshold amount of time). In some cases, reader device 550 may receive one or more signals from wireless device 515 (such as one or more reverse link signals), and reader device 550 may measure one or more received signals. For example, reader device 550 may measure a reference signal received power (RSRP), reference signal received quality (RSRQ), received signal strength indicator (RRSI), or another signal metric associated with the strength or quality of one or more received signals from wireless device 515 (e.g., measuring one or more reverse link signals, one or more forward link signals, or both). Reader device 550 may determine whether the signal metric has fallen below a signal quality threshold for a number of times (e.g., consecutive times) (e.g., a second threshold number) or for a certain amount of time (e.g., a second threshold time).

[0124] At step 550, if the communication attempts made at step 540 fail for a first threshold number of times or for a first threshold amount of time, or if one or more signal metrics associated with one or more received signals from wireless device 515 fall below a second threshold number of times or for a second threshold amount of time, then reader device 550 may determine that the session has ended or the session cannot be maintained, and therefore the second wireless device ID is no longer valid. Reader device 550 may then reclaim the second wireless device ID (e.g., for use by another wireless device).

[0125] In some implementations, the steps and operations of signal flow 500 described above may be additionally or alternatively performed by different devices. For example, in some implementations, at step 510, wireless device 515 may assign a second device ID (such as a reference ID) to reader device 550. Figure 3A and Figure 4B(As described). In such a specific implementation, timers and counters may be configured at wireless device 515, and at step 540, wireless device 515 may determine whether attempted communication to reader device 550 has failed for a first threshold number of times or a second threshold amount of time, or whether one or more signal metrics associated with one or more signals (e.g., forward link signals) from reader device 550 have fallen below a second threshold number of times or a second threshold amount of time. If so, at step 550, wireless device 515 may determine that the session has ended or cannot be maintained, and the second wireless device ID is therefore no longer valid. Wireless device 515 may therefore reclaim the second wireless device ID.

[0126] Figure 6 A block diagram 600 illustrates a device 605 supporting enhanced techniques for L1 identification of AIoT devices in a wireless communication system, according to one or more aspects of this disclosure. Device 605 may be an example of aspects of a UE 115 or network entity 105 as described herein. Device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. Device 605 or one or more components of device 605 (e.g., receiver 610, transmitter 615, communication manager 620) may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0127] Receiver 610 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels, etc., related to technologies that enhance L1 identification for AIoT devices in wireless communication systems). The information may be passed to other components of device 605. Receiver 610 may utilize a single antenna or a collection of antennas.

[0128] Transmitter 615 may provide components for transmitting signals generated by other components of device 605. For example, transmitter 615 may transmit information associated with various information channels, such as control channels, data channels, and information channels (e.g., control channels, data channels, and information channels associated with techniques enhancing L1 identification for AIoT devices in wireless communication systems), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 615 may be co-located with receiver 610 in a transceiver module. Transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0129] The communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be examples of components for performing various aspects of the techniques for enhancing L1 identification of AIoT devices in wireless communication systems as described herein. For example, the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be able to perform one or more of the functions described herein.

[0130] In some examples, the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic component, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0131] Additionally or alternatively, the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be implemented in code (e.g., as communication management software or firmware) (e.g., referred to as processor executable code) executed by at least one processor. If implemented in code executed by at least one processor, the functionality of the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be performed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured, either individually or collectively, as components for performing the functions described herein).

[0132] In some examples, the communication manager 620 may be configured to use the receiver 610, the transmitter 615, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 620 may receive information from the receiver 610, transmit information to the transmitter 615, or be integrated with the receiver 610, the transmitter 615, or both to acquire information, output information, or perform various other operations as described herein.

[0133] Communication manager 620 may support wireless communications according to examples disclosed herein. For example, communication manager 620 may be capable of, configured to, or operable to support components for conveying, via a physical layer channel, a first message including a first indication of a first wireless device identifier associated with a wireless device, the first message further including a request for or a second indication of a second wireless device identifier associated with the wireless device, the second wireless device identifier including a bit length selected from a set of multiple different bit lengths based on the type of reader device or the identity of the wireless device. Communication manager 620 may be capable of, configured to, or operable to support components for conveying one or more messages including a second wireless device identifier having that bit length based on at least a partial match between the first wireless device identifier and an identifier associated with the wireless device.

[0134] By including or configuring a communication manager 620 according to an example as described herein, device 605 (e.g., controlling receiver 610, transmitter 615, communication manager 620 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for reducing processing, lowering power consumption and utilizing communication resources more efficiently.

[0135] Figure 7 A block diagram 700 illustrates a device 705 supporting enhanced techniques for L1 identification of AIoT devices in a wireless communication system, according to one or more aspects of this disclosure. Device 705 may be an example of aspects of device 605, UE 115, or network entity 105 as described herein. Device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. Device 705 or one or more components of device 705 (e.g., receiver 710, transmitter 715, communication manager 720) may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0136] Receiver 710 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels, etc., related to technologies that enhance L1 identification for AIoT devices in wireless communication systems). The information may be passed to other components of device 705. Receiver 710 may utilize a single antenna or a collection of multiple antennas.

[0137] Transmitter 715 may provide components for transmitting signals generated by other components of device 705. For example, transmitter 715 may transmit information associated with various information channels, such as control channels, data channels, and information channels (e.g., control channels, data channels, and information channels associated with techniques enhancing L1 identification for AIoT devices in wireless communication systems), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 715 may be co-located with receiver 710 in a transceiver module. Transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0138] Device 705 or its various components may be examples of various aspects of components used to perform enhanced techniques for L1 identification of AIoT devices in wireless communication systems as described herein. For example, communication manager 720 may include wireless device identification manager 725, message manager 730, or any combination thereof. Communication manager 720 may be examples of aspects of communication manager 620 as described herein. In some examples, communication manager 720 or its various components may be configured to use receiver 710, transmitter 715, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 720 may receive information from receiver 710, transmit information to transmitter 715, or be integrated in combination with receiver 710, transmitter 715, or both to acquire information, output information, or perform various other operations as described herein.

[0139] Communication manager 720 can support wireless communication according to examples disclosed herein. Wireless device identifier manager 725 is capable of, configured to, or operable to support components for conveying, via a physical layer channel, a first message including a first indication of a first wireless device identifier associated with a wireless device, the first message also including a request for or a second indication of a second wireless device identifier associated with the wireless device, the second wireless device identifier including a bit length selected from a set of multiple different bit lengths based on the type of reader device or the identity of the wireless device. Message manager 730 is capable of, configured to, or operable to support components for conveying one or more messages including a second wireless device identifier having the bit length based on at least a partial match between the first wireless device identifier and an identifier associated with the wireless device.

[0140] In some cases, the wireless device identifier manager 725 and the message manager 730 may each be a processor (e.g., a transceiver processor, a radio processor, a transmitter processor, or a receiver processor) or at least a portion thereof. The processor may be coupled to memory and execute instructions stored in the memory that enable the processor to perform or facilitate the features of the wireless device identifier manager 725 and the message manager 730 discussed herein. The transceiver processor may co-locate with and / or communicate with (e.g., instruct its operation) the transceiver of the device. The radio processor may co-locate with and / or communicate with (e.g., instruct its operation) the radio components of the device (e.g., NR radio components, LTE radio components, Wi-Fi radio components). The transmitter processor may co-locate with and / or communicate with (e.g., instruct its operation) the transmitter of the device. The receiver processor may co-locate with and / or communicate with (e.g., instruct its operation) the receiver of the device.

[0141] Figure 8 A block diagram 800 illustrates a communication manager 820 supporting enhanced techniques for L1 identification of AIoT devices in a wireless communication system, according to one or more aspects of this disclosure. The communication manager 820 may be an example of aspects of the communication manager 620, communication manager 720, or both as described herein. The communication manager 820 or its various components may be examples of components for implementing various aspects of enhanced techniques for L1 identification of AIoT devices in a wireless communication system as described herein. For example, the communication manager 820 may include a wireless device identification manager 825, a message manager 830, a session manager 835, a configuration manager 840, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0142] Communication manager 820 can support wireless communication according to examples disclosed herein. Wireless device identifier manager 825 is capable of, configured to, or operable to support components for conveying, via a physical layer channel, a first message including a first indication of a first wireless device identifier associated with a wireless device, the first message also including a request for or a second indication of a second wireless device identifier associated with the wireless device, the second wireless device identifier including a bit length selected from a set of multiple different bit lengths based on the type of reader device or the identity of the wireless device. Message manager 830 is capable of, configured to, or operable to support components for conveying one or more messages including a second wireless device identifier having the bit length based on at least a partial match between the first wireless device identifier and an identifier associated with the wireless device.

[0143] In some examples, the first message also includes a third indication of the bit length.

[0144] In some examples, the bit length of the second wireless device identifier is further selected based on the broadcast type of at least one of the messages. In some examples, the broadcast type includes unicast, broadcast, or multicast.

[0145] In some examples, the first length is selected based on the type of the reader device, which is a UE reader device. In other examples, the second length is selected based on the type of the reader device, which is a base station reader device.

[0146] In some examples, the first bit length includes fewer bits than the second bit length.

[0147] In some examples, the session manager 835 is capable of, configured to, or able to operate to support components for establishing a current session with a wireless device based on a second indication received for a second wireless device identifier, wherein conveying one or more messages includes conveying one or more messages including a second wireless device identifier having that bit length during the duration of the current session.

[0148] In some examples, configuration manager 840 is capable of, configured to, or able to operate to support components for receiving configuration information from a network entity that indicates a lookup table, the lookup table including an association between identification information of a set of multiple wireless devices and a corresponding bit length of each wireless device in the set of multiple wireless devices, wherein the bit length of a second wireless device identifier is further selected based on the lookup table.

[0149] In some examples, conveying the first message includes sending a first message that includes a request for a second wireless device identifier. In some examples, the first message also includes a third indication of whether to reuse a previous second wireless identifier or generate a new second wireless identifier.

[0150] In some examples, conveying the first message includes receiving a first message that includes a request for a second wireless device identifier. In some examples, the wireless device identifier manager 825 is capable, configured, or operable to support components for transmitting a second message via a physical layer channel, the second message including an indication of a first wireless device identifier associated with the wireless device and omitting an indication of a second wireless device identifier associated with the wireless device. In some examples, the second wireless device identifier included in one or more messages includes a previously associated second wireless device identifier.

[0151] In some examples, the second wireless device identifier is configured by the wireless device, reader device, or network entity.

[0152] In some examples, the wireless device identifier manager 825 is capable of, configured to, or able to operate to support components for sending a second message to a wireless device, including a session termination command, wherein the session termination command indicates that a second wireless device identifier is no longer valid.

[0153] In some examples, a second wireless device identifier associated with a wireless device invalidates a previous second wireless identifier associated with the wireless device.

[0154] In some examples, the wireless device identifier manager 825 is capable of, configured to, or operable to support components for allocating a new second wireless device identifier associated with a wireless device based on a contention resolution performed during the registration process, wherein the new second wireless device identifier includes a CRI, a unique wireless device identifier, or a global wireless device identifier. In some examples, the message manager 830 is capable of, configured to, or operable to support components for conveying one or more additional messages including the new second wireless device identifier.

[0155] In some cases, the wireless device identification manager 825, message manager 830, session manager 835, and configuration manager 840 may each be a processor (e.g., a transceiver processor, a radio processor, a transmitter processor, or a receiver processor) or at least a portion thereof. The processor may be coupled to memory and execute instructions stored in the memory that enable the processor to perform or facilitate the features of the wireless device identification manager 825, message manager 830, session manager 835, and configuration manager 840 discussed herein.

[0156] Figure 9 A diagram illustrating a system 900 including a device 905 supporting enhanced techniques for L1 identification of AIoT devices in a wireless communication system, according to one or more aspects of this disclosure. Device 905 may be an example of device 605, device 705, or UE 115 as described herein, or a component including such devices. Device 905 may communicate with one or more other devices (e.g., network entity 105, UE 115, or a combination thereof) (e.g., wirelessly). Device 905 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 920, an input / output (I / O) controller (e.g., I / O controller 910), a transceiver 915, one or more antennas 925, at least one memory 930, code 935, and at least one processor 940. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 945).

[0157] I / O controller 910 manages the input and output signals of device 905. I / O controller 910 can also manage peripheral devices not integrated into device 905. In some cases, I / O controller 910 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 910 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Or another known operating system. Additionally or alternatively, the I / O controller 910 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 910 may be implemented as part of one or more processors, such as at least one processor 940. In some cases, a user may interact with the device 905 via the I / O controller 910 or via hardware components controlled by the I / O controller 910.

[0158] In some cases, device 905 may include a single antenna. However, in other cases, device 905 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 915 may communicate bidirectionally via one or more antennas 925 using a wired or wireless link as described herein. For example, transceiver 915 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 915 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 925 for transmission; and demodulating packets received from one or more antennas 925. Transceiver 915, or transceiver 915 and one or more antennas 925, may be an example of transmitter 615, transmitter 715, receiver 610, receiver 710, or any combination thereof or components thereof as described herein.

[0159] At least one memory 930 may include random access memory (RAM) and read-only memory (ROM). At least one memory 930 may store computer-readable code, computer-executable code, or processor-executable code, such as code 935. Code 935 may include instructions that, when executed by at least one processor 940, cause device 905 to perform the various functions described herein. Code 935 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 935 may not be directly executable by at least one processor 940, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, in addition, at least one memory 930 may also include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0160] At least one processor 940 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof). In some cases, at least one processor 940 may be configured to use a memory controller to operate a memory array. In some other cases, the memory controller may be integrated into at least one processor 940. At least one processor 940 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 930) to cause device 905 to perform various functions (e.g., functions or tasks that support enhancements to L1 identification for AIoT devices in wireless communication systems). For example, device 905 or components of device 905 may include at least one processor 940 and at least one memory 930 coupled to or coupled to at least one processor 940, wherein at least one processor 940 and at least one memory 930 are configured to perform the various functions described herein.

[0161] In some examples, at least one processor 940 may include multiple processors, and at least one memory 930 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 940 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 940) and memory circuitry (which may include at least one memory 930)) or components that receive or receive input and process the input to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 940 or a processing system including at least one processor 940 may be configured, capable of being configured, or operable to cause device 905 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” can be used interchangeably and can be associated with the ability to perform one or more of the functions described herein when executing code 935 (e.g., processor-executable code) stored in at least one memory 930 or otherwise.

[0162] The communication manager 920 may support wireless communications according to examples disclosed herein. For example, the communication manager 920 may be capable of, configured to, or operable to support components for conveying, via a physical layer channel, a first message including a first indication of a first wireless device identifier associated with a wireless device, the first message further including a request for or a second indication of a second wireless device identifier associated with the wireless device, the second wireless device identifier including a bit length selected from a set of multiple different bit lengths based on the type of reader device or the identity of the wireless device. The communication manager 920 may be capable of, configured to, or operable to support components for conveying one or more messages including a second wireless device identifier having that bit length based on at least a partial match between the first wireless device identifier and an identifier associated with the wireless device.

[0163] By including or configuring a communication manager 920 according to an example as described herein, device 905 can support techniques for improving communication reliability, reducing latency, utilizing communication resources more efficiently, and improving coordination between devices.

[0164] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using a transceiver 915, one or more antennas 925, or any combination thereof, or otherwise cooperating with them. Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 may be supported or executed by at least one processor 940, at least one memory 930, code 935, or any combination thereof. For example, code 935 may include instructions that can be executed by at least one processor 940 to cause device 905 to perform various aspects of the techniques for enhancing L1 identification of AIoT devices in wireless communication systems as described herein, or at least one processor 940 and at least one memory 930 may be otherwise configured to perform or support such operations individually or jointly.

[0165] Figure 10 A flowchart illustrating a method 1000 for enhancing the L1 identifier of an AIoT device in a wireless communication system, according to one or more aspects of this disclosure, is shown. Operation of method 1000 may be implemented by a UE or its components as described herein. For example, operation of method 1000 may be performed by, as referenced... Figures 1 to 9 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0166] At 1005, the method may include: conveying via a physical layer channel a first message including a first indication of a first wireless device identifier associated with a wireless device, the first message further including a request for or a second indication of a second wireless device identifier associated with the wireless device, the second wireless device identifier including a bit length selected from a set of multiple different bit lengths based on the type of reader device or the identity of the wireless device. The operation of 1005 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1005 may be provided by reference to [reference needed]. Figure 8 The described Wireless Device Identifier Manager 825 is used to perform this.

[0167] At 1010, the method may include: conveying one or more messages including a second wireless device identifier having the bit length based on at least a partial match between a first wireless device identifier and an identifier associated with the wireless device. The operation of 1010 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1010 may be provided by reference to [reference]. Figure 8 The message manager 830 described is used to execute this.

[0168] The following provides an overview of the various aspects of this disclosure:

[0169] Aspect 1: A method for wireless communication by a reader device, the method comprising: conveying via a physical layer channel a first message including a first indication of a first wireless device identifier associated with a wireless device, the first message further including a request for a second wireless device identifier associated with the wireless device or a second indication of the second wireless device identifier associated with the wireless device, the second wireless device identifier including a bit length selected from a plurality of different bit lengths based at least in part on the type of the reader device or the identity of the wireless device; and conveying one or more messages including the second wireless device identifier having the bit length based at least in part on a match at least partially between the first wireless device identifier and an identifier associated with the wireless device.

[0170] Aspect 2: According to the method of aspect 1, the first message further includes a third indication of the bit length.

[0171] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the bit length of the second wireless device identifier is further selected at least in part based on the broadcast type of at least one of the one or more messages, and the broadcast type includes unicast, broadcast, or multicast.

[0172] Aspect 4: The method according to any one of Aspects 1 to 3, wherein the first length is selected at least in part based on the type of the reader device being a UE reader device, or the second length is selected at least in part based on the type of the reader device being a base station reader device.

[0173] Aspect 5: According to the method of aspect 4, the first bit length includes fewer bits than the second bit length.

[0174] Aspect 6: The method according to any one of Aspects 1 to 5, the method further comprising: establishing a current session with the wireless device based at least in part on receiving the second indication for the second wireless device identifier, wherein conveying the one or more messages comprises: conveying the one or more messages including the second wireless device identifier having the bit length during the duration of the current session.

[0175] Aspect 7: The method according to any one of Aspects 1 to 6, the method further comprising: receiving configuration information from a network entity indicating a lookup table, the lookup table including an association between identification information of a plurality of wireless devices and a corresponding bit length of each of the plurality of wireless devices, wherein the bit length of the second wireless device identifier is further selected at least in part based on the lookup table.

[0176] Aspect 8: The method according to any one of Aspects 1 to 7, wherein conveying the first message comprises: sending the first message including the request for the second wireless device identifier, and the first message further includes a third indication of whether to reuse a previous second wireless identifier or to generate a new second wireless identifier.

[0177] Aspect 9: The method according to any one of Aspects 1 to 8, wherein conveying the first message comprises: receiving the first message including the request for the second wireless device identifier, the method further comprising: transmitting a second message via the physical layer channel, the second message including an indication of the first wireless device identifier associated with the wireless device and omitting an indication of the second wireless device identifier associated with the wireless device, wherein conveying the one or more messages including the second wireless device identifier includes conveying the one or more messages including a previous second wireless device identifier associated with the wireless device.

[0178] Aspect 10: The method according to any one of Aspects 1 to 9, wherein the second wireless device identifier is configured by the wireless device, the reader device, or the network entity.

[0179] Aspect 11: The method according to any one of Aspects 1 to 10, the method further comprising: sending a second message to the wireless device including a session end command, wherein the session end command indicates that the second wireless device identifier is no longer valid.

[0180] Aspect 12: The method according to any one of Aspects 1 to 11, wherein the second wireless device identifier associated with the wireless device invalidates a previous second wireless identifier associated with the wireless device.

[0181] Aspect 13: The method according to any one of Aspects 1 to 12, the method further comprising: allocating a new second wireless device identifier associated with the wireless device based at least in part on performing contention resolution during the registration process, wherein the new second wireless device identifier includes a contention resolution ID (CRI), a unique wireless device identifier, or a global wireless device identifier; and using the new second wireless device identifier to convey one or more additional messages.

[0182] Aspect 14: A reader device for wireless communication, the reader device comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the reader device to perform a method according to any one of Aspects 1 to 13.

[0183] Aspect 15: A reader device for wireless communication, the reader device comprising at least one component for performing the method according to any one of aspects 1 to 13.

[0184] Aspect 16: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the method according to any one of aspects 1 to 13.

[0185] It should be noted that the methods described herein describe possible specific implementations. Operations and steps may be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods may be combined.

[0186] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0187] The information and signals described herein can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0188] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, GPU, NPU, FPGA, or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described function or operation individually or jointly.

[0189] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in various locations, including portions distributed such that the functions are implemented in different physical locations.

[0190] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0191] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0192] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0193] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, searching (such as by searching in a table, database, or other data structure), ascertainment, etc. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, acquiring, selecting, choosing, creating, and other similar actions.

[0194] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second reference numeral to differentiate between similar components. If only the first reference numeral is used in the description, the description applies to any of the similar components having the same first reference numeral, regardless of the second reference numeral or other subsequent reference numerals.

[0195] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some of the drawings, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0196] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A reader device, the reader device comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors coupled to one or more memories, wherein the one or more processors are individually or collectively configured to enable the reader device to: A first message is transmitted via a physical layer channel, including a first indication of a first wireless device identifier associated with a wireless device. The first message further includes a request for or a second indication of a second wireless device identifier associated with the wireless device, wherein the second wireless device identifier includes a bit length selected from a plurality of different bit lengths based at least in part on the type of the reader device or the identity of the wireless device. One or more messages, including the second wireless device identifier having the stated bit length, are conveyed based at least in part on a match between the first wireless device identifier and an identifier associated with the wireless device.

2. The reader device of claim 1, wherein the first message further includes a third indication of the bit length.

3. The reader device of claim 1, wherein the bit length of the second wireless device identifier is further selected, at least in part, based on the broadcast type of at least one of the one or more messages, and The broadcast type mentioned includes unicast, broadcast, or multicast.

4. The reader device of claim 1, wherein the first bit length is selected based at least in part on the fact that the type of the reader device is a user equipment (UE) reader device, or The second bit length is selected based at least in part on the fact that the type of the reader device is a base station reader device.

5. The reader device of claim 4, wherein the first bit length comprises fewer bits than the second bit length.

6. The reader device of claim 1, wherein the one or more processors are individually or jointly further configured to cause the reader device to: The current session with the wireless device is established at least in part based on receiving the second indication for the second wireless device identifier, including that one or more messages of the second wireless device identifier having the bit length are communicated during the duration of the current session.

7. The reader device of claim 1, wherein the one or more processors are individually or jointly further configured to cause the reader device to: Configuration information indicating a lookup table is received from a network entity. The lookup table includes an association between identification information of a plurality of wireless devices and a corresponding bit length of each of the plurality of wireless devices, wherein the bit length of the second wireless device identifier is further selected at least in part based on the lookup table.

8. The reader device of claim 1, wherein the one or more processors are individually or jointly configured to cause the reader device to convey the first message by individually or jointly causing the reader device to perform the following: Send a first message including the request for the second wireless device identifier, wherein the first message further includes a third indication of whether to reuse the previous second wireless identifier or generate a new second wireless identifier.

9. The reader device of claim 1, wherein the one or more processors are individually or jointly configured to cause the reader device to convey the first message by individually or jointly causing the reader device to perform the following: Receive the first message including the request for the second wireless device identifier. The one or more processors are also configured individually or collectively to enable the reader device to: A second message is transmitted via the physical layer channel, including an indication of the first wireless device identifier associated with the wireless device, wherein the indication of the second wireless device identifier associated with the wireless device is omitted in the second message. The second wireless device identifier included in one or more of the messages includes a previous second wireless device identifier associated with the wireless device.

10. The reader device of claim 1, wherein the second wireless device identifier is configured by the wireless device, the reader device, or a network entity.

11. The reader device of claim 1, wherein the one or more processors are individually or jointly further configured to cause the reader device to: Send a second message to the wireless device including a session termination command, wherein the session termination command indicates that the second wireless device identifier is no longer valid.

12. The reader device of claim 1, wherein the second wireless device identifier associated with the wireless device invalidates a previous second wireless identifier associated with the wireless device.

13. The reader device of claim 1, wherein the one or more processors are individually or jointly further configured to cause the reader device to: At least in part, a new second wireless device identifier is assigned to the wireless device based on contention resolution performed during the registration process, wherein the new second wireless device identifier includes a Contention Resolution ID (CRI), a unique wireless device identifier, or a global wireless device identifier; and It conveys one or more additional messages, including the new second wireless device identifier.

14. A method for wireless communication by a reader device, the method comprising: A first message is transmitted via a physical layer channel, including a first indication of a first wireless device identifier associated with a wireless device. The first message also includes a request for or a second indication of a second wireless device identifier associated with the wireless device, the second wireless device identifier comprising a bit length selected from a plurality of different bit lengths based at least in part on the type of the reader device or the identity of the wireless device. One or more messages, including the second wireless device identifier having the stated bit length, are conveyed based at least in part on a match between the first wireless device identifier and an identifier associated with the wireless device.

15. The method of claim 14, wherein the first message further includes a third indication of the bit length.

16. The method of claim 14, wherein the bit length of the second wireless device identifier is further selected, at least in part, based on the broadcast type of at least one of the one or more messages, and The broadcast type mentioned includes unicast, broadcast, or multicast.

17. The method of claim 14, wherein the first bit length is selected based at least in part on the fact that the type of the reader device is a user equipment (UE) reader device, or The second bit length is selected based at least in part on the fact that the type of the reader device is a base station reader device, wherein the first bit length includes fewer bits than the second bit length.

18. The method according to claim 14, further comprising: The current session with the wireless device is established at least in part based on receiving the second indication for the second wireless device identifier, wherein conveying the one or more messages includes conveying the one or more messages including the second wireless device identifier having the bit length during the duration of the current session.

19. The method of claim 14, further comprising: Configuration information indicating a lookup table is received from a network entity. The lookup table includes an association between identification information of a plurality of wireless devices and a corresponding bit length of each of the plurality of wireless devices, wherein the bit length of the second wireless device identifier is further selected at least in part based on the lookup table.

20. A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors of a reader device to: A first message is transmitted via a physical layer channel, including a first indication of a first wireless device identifier associated with a wireless device. The first message also includes a request for or a second indication of a second wireless device identifier associated with the wireless device, the second wireless device identifier comprising a bit length selected from a plurality of different bit lengths based at least in part on the type of the reader device or the identity of the wireless device. One or more messages, including the second wireless device identifier having the stated bit length, are conveyed based at least in part on a match between the first wireless device identifier and an identifier associated with the wireless device.

Images