Techniques for querying environmental internet of things devices in a wireless communication system

Abstract

Methods, systems, and devices for wireless communication are described. A reader device can transmit a first message via a physical layer channel. The first message can include a command for a wireless device, such as an ambient Internet of Things (AIoT) device. The command can indicate a first wireless device identifier, such as a network identifier, associated with the wireless device. Based on at least a portion of the first wireless device identifier matching an identifier associated with the wireless device, the reader device can receive a response message from the wireless device that includes a second wireless device identifier. The second wireless device identifier can be composed of fewer bits than the first wireless device identifier. Subsequently, the reader device and the wireless device can use the second wireless device identifier to communicate one or more messages.

Description

Technical Field

[0001] This disclosure relates to wireless communication, including techniques for querying environmental Internet of Things (AIoT) devices in a wireless communication system. 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, devices, and apparatuses for supporting techniques for querying wireless devices (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 send messages including commands intended for use with the wireless device (such as select, query, read, write, lock, sleep, terminate, or other commands). In some cases, the commands may be transmitted along with first identification information associated with the wireless device, enabling the wireless device to detect that the message is intended for use with the wireless device. In some cases, in response to receiving and detecting that the message is intended for use with the wireless device, the wireless device can send a response message to the reader device indicating second identification information associated with the wireless device. The second identification information may consist of fewer bits than the first identification information (e.g., it may be shorter than the first identification information). The second identification information can be used for subsequent communication between the reader device and the wireless device over a period of time. The fewer bits in the second identification information compared to the first identification information facilitates efficient use of computing resources during communication between the devices.

[0004] A method for wireless communication by a reader device is described. The method may include: transmitting a first message including a wireless device command via a physical layer channel, the wireless device command including a first wireless device identifier having a first number of bits, wherein at least a portion of the first wireless device identifier is transmitted in a data portion, header portion, or control portion of the first message; receiving a response message from the wireless device and based on a match between the first wireless device identifier and at least a portion of an identifier associated with the wireless device, the response message including a second wireless device identifier having a second number of bits, the second number of bits being fewer than the first number of bits; and communicating one or more messages with the wireless device using the second wireless device identifier.

[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 are operable individually or jointly to execute the code to cause the reader device to: transmit a first message including a wireless device command via a physical layer channel, the wireless device command including a first wireless device identifier having a first number of bits, wherein at least a portion of the first wireless device identifier is transmitted in a data portion, header portion, or control portion of the first message; receive a response message from a wireless device and based on a match between the first wireless device identifier and at least a portion of an identifier associated with the wireless device, the response message including a second wireless device identifier having a second number of bits, the second number of bits being fewer than the first number of bits; and communicate one or more messages to the wireless device using the second wireless device identifier.

[0006] Another reader device for wireless communication is described. The reader device may include: components for transmitting a first message including a wireless device command via a physical layer channel, the wireless device command including a first wireless device identifier having a first number of bits, wherein at least a portion of the first wireless device identifier is transmitted in a data portion, header portion, or control portion of the first message; components for receiving a response message from the wireless device and based on a match between the first wireless device identifier and at least a portion of an identifier associated with the wireless device, the response message including a second wireless device identifier having a second number of bits, the second number of bits being fewer than the first number of bits; and components for communicating one or more messages with the wireless device using the second wireless device identifier.

[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: transmit a first message including a wireless device command via a physical layer channel, the wireless device command including a first wireless device identifier having a first number of bits, wherein at least a portion of the first wireless device identifier is transmitted in a data portion, header portion, or control portion of the first message; receive a response message from the wireless device and based on a match between the first wireless device identifier and at least a portion of an identifier associated with the wireless device, the response message including a second wireless device identifier having a second number of bits, the second number of bits being fewer than the first number of bits; and communicate one or more messages to the wireless device using the second wireless device identifier.

[0008] 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 wireless device identifier, wherein communicating one or more messages with the wireless device using the second wireless device identifier includes communicating one or more messages with the wireless device using the second wireless device identifier during the duration of the current session.

[0009] In some examples of the methods, reader devices, and nontransitory computer-readable media described herein, the at least portion of the first wireless device identifier includes the entire portion of the first wireless device identifier.

[0010] In some examples of the methods, reader devices, and nontransitory computer-readable media described herein, the remainder of the first wireless device identifier may be sent in the control portion or header portion of the first message.

[0011] In some examples of the methods, reader devices, and nontransitory computer-readable media described herein, the remainder of the first wireless device identifier may be a second wireless device identifier.

[0012] In some examples of the methods, reader devices, and nontransitory computer-readable media described herein, at least a portion of the first wireless device identifier includes a number of masked bits and a number of unmasked bits, and the second wireless device identifier includes the remainder of the first wireless device identifier associated with that number of masked bits.

[0013] In some examples of the methods, reader devices, and nontransitory computer-readable media described herein, wireless device commands indicate scheduling information for one or more access opportunities used to communicate response messages.

[0014] In some examples of the methods, reader devices, and nontransitory computer-readable media described herein, a wireless device command includes a set of multiple wireless device identifiers and an indication of the number of such multiple wireless device identifiers in the set, and a first wireless device identifier may be one of the multiple wireless device identifiers in the set.

[0015] In some examples of the methods, reader devices, and nontransitory computer-readable media described herein, the first wireless device identifier includes an application layer identifier, a device hardware identifier, or a device network identifier.

[0016] In some examples of the methods, reader devices, and nontransitory computer-readable media described herein, the second wireless device identifier includes a hash version of the first wireless device identifier or a truncated portion of the first wireless device identifier.

[0017] In some examples of the methods, reader devices, and nontransitory computer-readable media described herein, wireless device commands include instructions for rules associated with at least a portion or the remainder of a first wireless device identifier.

[0018] Some examples of the methods, reader devices, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for transmitting a second message including a second wireless device identifier after the transmission of a first message, wherein the second wireless device identifier may be indicated in the header portion of the second message, or in the data portion of the second message, or by scrambling a cyclic redundancy check (CRC), or by scrambling the data portion of the second message. Attached Figure Description

[0019] Figure 1 An example of a wireless communication system is shown that supports a technique for querying environmental Internet of Things (AIoT) devices in a wireless communication system, according to one or more aspects of this disclosure.

[0020] Figure 2 An example of a portion of a wireless communication system is shown, which supports techniques for querying AIoT devices in a wireless communication system according to one or more aspects of this disclosure.

[0021] Figure 3 An example of a signal flow supporting a technique for querying AIoT devices in a wireless communication system, according to one or more aspects of this disclosure, is shown.

[0022] Figure 4 An example of a signal flow supporting a technique for querying AIoT devices in a wireless communication system, according to one or more aspects of this disclosure, is shown.

[0023] Figure 5 An example of a signal flow supporting a technique for querying AIoT devices in a wireless communication system, according to one or more aspects of this disclosure, is shown.

[0024] Figure 6 An example of a signal flow supporting a technique for querying AIoT devices in a wireless communication system, according to one or more aspects of this disclosure, is shown.

[0025] Figure 7 An example of a signal flow supporting a technique for querying an environmental Internet of Things (IoT) device in a wireless communication system, according to one or more aspects of this disclosure, is shown.

[0026] Figure 8 and Figure 9A block diagram of an apparatus for querying AIoT devices in a wireless communication system is shown, according to one or more aspects of this disclosure.

[0027] Figure 10 A block diagram of a communication manager supporting technologies for querying AIoT devices in a wireless communication system, according to one or more aspects of this disclosure, is shown.

[0028] Figure 11 A diagram of a system including a device supporting technology for querying AIoT devices in a wireless communication system is shown, according to one or more aspects of this disclosure.

[0029] Figure 12 A flowchart illustrating a method for querying AIoT devices in a wireless communication system, according to one or more aspects of this disclosure, is shown. Detailed Implementation

[0030] Various aspects of this disclosure relate to techniques for querying wireless devices (e.g., Ambient Internet of Things (AIoT) devices) in a wireless communication system. 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 wireless device to locate or communicate with the wireless device. For example, the surrounding computing environment may include one or more wireless devices (e.g., AIoT devices) that interact with one or more other devices (such as one or more reader devices capable of reading 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 or communicate with wireless devices to provide services.

[0031] 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 the technology used for querying Ambient Internet of Things (AIoT) devices in a wireless communication system.

[0032] Figure 1An example of a wireless communication system 100 supporting techniques for querying AIoT devices in a wireless communication system, according to one or more aspects of this disclosure, is shown. 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-A Pro 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.

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

[0034] 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, such as other wireless communication devices, including UE 115 or network entity 105. Figure 1 As shown in the figure.

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

[0036] 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. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or 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 can communicate with core network 130 via communication link 155.

[0037] One or more of the network entities 105 or network equipment described herein 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 that is physically or logically integrated within a single network entity (e.g., network entity 105 or a single RAN node, such as base station 140).

[0038] 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 a protocol stack that is physically or logically distributed among multiple network entities (e.g., network entity 105) such as an integrated access and 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 RTRIC), 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)).

[0039] 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 upper protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionality 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 Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium 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 another 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 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.

[0040] 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 in network entity 105 (e.g., network entity 105 or IAB node 104) can be partially controlled by each other. IAB node 104 can be referred to as a donor entity or IAB donor. DU 165 or RU 170 can 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) can 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 (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) supporting communication links with relay chains or additional entities (e.g., IAB node 104, UE 115) within the access network (e.g., downstream). 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.

[0041] When the techniques described herein are applied in a decomposed RAN architecture environment, 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) can be additionally or alternatively 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).

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

[0043] The UE 115 described herein can communicate with various types of devices, such as the UE 115 which can sometimes operate as a relay, as well as network entity 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, relay base stations, etc. Figure 1 As shown in the figure.

[0044] UE 115 and network entity 105 can communicate wirelessly 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., 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 may support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured using multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may 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).

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

[0046] 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 The supported Discrete Fourier Transform (DFT) size can be represented. Time intervals for communication resources can be organized according to 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).

[0047] 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. In addition to 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.

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

[0049] 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 for transmitting control information to UE 115 (e.g., a specific UE).

[0050] In some examples, network entity 105 (e.g., base station 140, RU 170) can 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) can overlap, but coverage areas 110 (e.g., different coverage areas) can be supported by the same network entity (e.g., network entity 105). In some other examples, different network entities (e.g., network entity 105) can support overlapping coverage areas associated with different technologies, such as coverage area 110. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 support communication in coverage areas 110 (e.g., different coverage areas) using the same or different RATs.

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

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

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

[0054] 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) according to peer-to-peer (P2P), D2D, or sidelink protocols. 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.

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

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

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

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

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

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

[0061] 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. The reader device may send commands intended for use with the wireless devices (such as select, query, read, write, lock, sleep, terminate, or other commands). In some cases, the commands may be transmitted along with first identification information associated with the wireless device, enabling the wireless device to detect that the message is intended for use with the wireless device. In some cases, in response to receiving and detecting that the message is intended for use with the wireless device, the wireless device may send a response message to the reader device indicating second identification information associated with the wireless device. The second identification information may consist of fewer bits than the first identification information (e.g., it may be shorter than the first identification information). The second identification information can then be used for communication between the reader device and the wireless device for a period of time.

[0062] Figure 2 An example of a portion of a wireless communication system 200 supporting technologies for querying AIoT devices in a wireless communication system, according to one or more aspects of this disclosure, is shown. 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 An example of the 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, 125-e, 125-f, and 125-g).

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

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

[0065] 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 transmitted the initial 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 less than 13 m to about 33 m.

[0066] The second type of wireless device 215 (e.g., device type 2) may have the ability to store more 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 10X (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 22m to 61m.

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

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

[0069] 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 wireless device 215, reader device 250 may collect information associated with the located wireless device 215 (such as identification and location 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 manner, when it is necessary to locate a specific wireless device 215, network entity 130-a can query registration records 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 instances, network entity 130-a may additionally or alternatively target other reader devices 250 to locate the specific wireless device 215.

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

[0071] Upon receiving a signal from network entity 130-a or network entity 105-a, reader device 250 may transmit a signal (such as a reader-to-device (R2D) paging signal) via forward communication link 125-c (e.g., a forward link) or forward communication link 125-e (e.g., a forward link). This signal may include a first message 220 (e.g., first message 220-a or first message 220-b) containing a command (such as select, query, read, write, lock, sleep, terminate, or other command) intended for use with one or more wireless devices (such as target wireless device 215) in wireless device 215. In some cases, this command may be transmitted along with first identification information associated with target wireless device 215, such that target wireless device 215 can detect that the first message 220 is intended for target wireless device 215. As an example, the command could be a selection command for selecting or identifying one or more specific wireless devices 215 for communication, or a query command (e.g., unicast, multicast, or multicast query) for initiating a registration process to identify wireless devices 215 within the range of reader device 250.

[0072] In response to receiving and detecting that the message is intended for use by the target wireless device 215, the target wireless device 215 may send a signal to the reader device 250 via reverse communication link 125-d (e.g., reverse link) or reverse communication link 125-f (e.g., reverse link). This signal may include a response message, such as a response message 230 (e.g., response message 230-a or response message 230-b) indicating second identification information associated with the target wireless device 215. The second identification information may consist of fewer bits than the first identification information. For example, the second identification information may be shorter than the first identification information. In some cases, the first identification information (e.g., a first wireless device identifier) ​​may be referred to as a long identifier (ID), and the second identification information may be referred to as a short ID. For example, the first identification information may be an application layer ID assigned by an application, such as an Electronic Product Code (EPC) ID; a hardware ID assigned by the manufacturer of the wireless device 215, such as a tag ID (TID) or serial number; a network ID such as one assigned by a 3GPP network; or other unique identifier associated with the wireless device 215. The second identification information may be a Layer 1 (L1)-ID used for communication between the reader device 250 and the wireless device over a period of time (such as a temporary period of time, for example, during the duration of a session between the reader device 250 and the target wireless device 215). In some cases, the second identification information may be a random or pseudo-random value, such as RN16 (e.g., a 16-bit random or 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; or other identification information used for temporary communication between the reader device 250 and the wireless device 215.

[0073] Figure 3 An example of a signal flow 300 supporting a technique for querying AIoT devices in a wireless communication system, according to one or more aspects of this disclosure, is shown. In some aspects, the signal flow 300 may implement as described in reference respectively. Figure 1 and Figure 2 The described wireless communication system 100 or 200 may be implemented by or be comprised of aspects thereof. Signal flow 300 may exemplify the signal flow between wireless device 315 and reader device 350. Wireless device 315 may be as described in reference... Figure 2 An example of a wireless device in the described wireless device 215. Reader device 350 may be as shown in the reference. Figure 2 Examples of the described UE reader device 250-a or base station reader device 250-b.

[0074] In some implementations, in response to a signal received from a network entity by reader device 350 to locate, identify, or otherwise communicate with wireless device 315, reader device 350 may send a signal including a first message 320 addressing wireless device 315. The first message 320 may be a Physical Reader to Device Channel (PRDCH) message including a wireless device command (e.g., a tag command) (or in some cases may be included in a MAC control element (MAC-CE)). The first message 320 may consist of a preamble portion 320-a, a header or control portion 320-b (referred to herein as header portion 320-b), and a data portion 320-c. The first message 320 may additionally or alternatively include one or more other portions not mentioned herein.

[0075] One or more bits of the first message 320 may be used to indicate a wireless device command (e.g., select, query, read, write, etc.) or the purpose of the first message 320. For example, the header portion 320-b or data portion 320-c of the first message 320 may include one or more bits indicating a wireless device command or the purpose of the first message 320. As discussed in reference signal flow 300, the command may be a select command for selecting or identifying one or more specific wireless devices (such as wireless device 315) for communication, or a query command (such as a unicast query command) for initiating a registration process to identify wireless devices (which may include wireless device 315) within the range of reader device 350. However, the type of wireless device command included in the first message 320 is not necessarily limited to select or query commands, and may instead include other types of wireless device commands, such as read, write, terminate, lock, sleep, or other wireless device commands.

[0076] In some cases, the wireless device command may be transmitted along with identification information associated with wireless device 315, enabling the target wireless device 315 to detect that the first message 320 is intended for wireless device 315. For example, the first message 320 may include a selection command with identification information associated with wireless device 315, or it may include a query (e.g., unicast query) command with identification information associated with wireless device 315. The identification information may be a first wireless device ID 340. The first wireless device ID 340 may be a reference... Figure 2The long ID described. The first wireless device ID 340 may be included in the header portion 320-b or the data portion 320-c of the first message 320, or in some cases, in both portions of the first message 320. For example, in some cases, the first portion (e.g., any portion) 340-a of the first wireless device ID may be included in the header portion 320-b of the first message 320, while the second portion (e.g., the remaining portion or a portion not included in the first portion) 340-b of the first wireless device ID may be included in the data portion 320-c of the first message 320. In other cases, the entire portion of the wireless device ID 340 may be included in the header portion 320-b of the first message 320. In this case, the first portion 340-a of the first wireless device ID may be the entire first wireless device ID 340. In other cases, the entire portion of the wireless device ID 340 may be included in the data portion 320-c of the first message 320. In this case, the second part 340-b of the first wireless device ID can be the entire first wireless device ID 340.

[0077] The inclusion of the first wireless device ID 340 in any part of the first message 320 may be at least partially based on characteristics of the first wireless device ID 340, such as its type or size. For example, for privacy purposes, when the first wireless device ID 340 is a hardware ID or application ID, it may be included in a data portion 320-c, which may be encrypted or otherwise encoded to ensure the security of the data carried therein. As another example, when the first wireless device ID 340 exceeds a threshold size or length (e.g., too large / too heavy to be contained in the header portion 320-b), it may be divided into a first portion 340-a and a second portion 340-b, and carried in the corresponding header portion 320-b and data portion 320-c of the first message 320. In some cases, the first message 320 may also include information indicating one or more rules that represent the location or manner in which the first wireless device ID 340 is carried in the first message 320 (e.g., whether it is segmented into different parts of the first message 320, how it is segmented, etc.). In some cases, one or more rules associated with the first wireless device ID 340 may be pre-configured at one or both of the reader device 350 (such as by signaling notification from a network entity (e.g., a base station)) and the wireless device 315.

[0078] A first wireless device ID 340 may be included in the first message 320 such that when the wireless device 315 initially detects the first message 320 sent by the reader device 350, the wireless device 315 can recognize that the first message 320 is intended for use by the wireless device 315. For example, the wireless device 315 may compare the first wireless device ID 340 included in the first message 320 with its own identification information to determine whether there is at least a partial match between the first wireless device ID 340 and the identification information of the wireless device 315. Upon determining that there is at least a partial match (e.g., such that the first message 320 is intended for use by the wireless device 315), the reader device 350 and the wireless device 315 may establish a session (such as a connection for a period of time) for further communication.

[0079] However, in some cases, due to the size of the first wireless device ID 340 (e.g., a long ID, which may be long to ensure uniqueness within a group of wireless devices), reader device 350 and wireless device 315 (after initially establishing a connection or session) may communicate with each other using a relatively small or short wireless device ID (such as a wireless device ID containing fewer bits than the first wireless device ID 340). Therefore, in some cases, reader device 350 and wireless device 315 may negotiate to use a second wireless device ID 345, which may have fewer bits than the first wireless device ID 340, for communication during the current session or for a limited (e.g., temporary) time period. For example, the second wireless device ID 345 may be a reference... Figure 2 The described short ID, and in some cases, can be an identifier that is unique among at least those wireless devices currently within the range of reader device 350. In some cases, the second wireless device ID 345 may be assigned (e.g., generated, configured, determined) by reader device 350 or by a network device (via reader device 350) and indicated to wireless device 315. In other cases, wireless device 315 itself may assign (e.g., generate, configure, determine) the second wireless device ID 345.

[0080] When assigned by reader device 350, the second wireless device ID 345 may be included in the first message 320, such as in the header portion 320-b or data portion 320-c of the first message 320. For example, the first wireless device ID 340 may be included in the header portion 320-b of the first message 320, while the second wireless device ID 345 may be included in the data portion 320-c of the first message 320. Alternatively, the second wireless device ID 345 may be included in the header portion 320-b of the first message 320, while the first wireless device ID 340 may be included in the data portion 320-c of the first message 320. Alternatively, both the first wireless device ID 340 and the second wireless device ID 345 may be included in either the header portion 320-b or the data portion 320-c of the first message 320.

[0081] In some cases, the second wireless device ID 345 may be a random or pseudo-random value, a value derived from the first wireless device ID 340 (such as a hash version of the first wireless device ID 340 or another decoding scheme); or other identification information used for temporary communication between the reader device 350 and the wireless device 315. In some cases, the reader device 350 may dynamically assign unused values ​​to the second wireless device ID 345 via the first message 320 to avoid ID conflicts at the wireless device. For example, the reader device 350 may know the second wireless device ID associated with a wireless device within the coverage area of ​​the reader device 350.

[0082] In some cases, such as when the first wireless device ID 340 is divided into a first portion 340-a and a second portion 340-b of the wireless device ID, one portion of the first wireless device ID 340 (e.g., the first portion 340-a or the second portion 340-b of the first wireless device ID) may be used as the second wireless device ID 345. In some examples, the first message 320 may include both the first wireless device ID 340-a and the second wireless device ID 345 to notify the wireless device 315, which has the first wireless device ID 340-a, that the second wireless device ID 345 has been assigned to the wireless device 315.

[0083] When the wireless device command is a unicast or multicast query and the reader device 350 and wireless device 315 have previously negotiated or assigned a second wireless device ID 345, the reader device 350 may determine to include the second wireless device ID 345 in the first message 320 while the second wireless device ID 345 is still valid (e.g., the duration of use of the second wireless device ID 345 has not yet expired). In this case, the first wireless device ID 340 may be omitted from the first message 320. Otherwise, if the second wireless device ID 345 is no longer valid, the first wireless device ID 340 may be used in the first message 320. Furthermore, in some cases, the reader device 350 may indicate in the first message 320 whether subsequent communication between the reader device 350 and wireless device 315 should use either the second wireless device ID 345 or the first wireless device ID 340 (and which first wireless device ID 340 should be used, such as a hardware ID, application ID, network ID, or other identification information).

[0084] In some cases, when the wireless device command is a multicast query, the command can function similarly to multicast msg 2 or msg B (e.g., registration process), except that the wireless device 315 can provide feedback (such as response message 330).

[0085] For example, in response to detecting the first message 320 and determining that the first message 320 is intended for use by the wireless device 315, the wireless device 315 may send a response message 330 back to the reader device 350. For example, in some cases, the wireless device 315 may be an EH-capable device capable of harvesting or storing energy from received signals output by the reader device 350 (e.g., the signal including the first message 320). The wireless device 315 may use the energy from the received signal to send one or more backscattered signals (or in some cases, non-backscattered signals) including the response message 330 back to the reader device 350 (or in some cases, to a different reader device).

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

[0087] In some instances, the second wireless device ID 345 indicated in response message 330 may be the same second wireless device ID 345 assigned by reader device 350 and indicated in the first message 320 received by wireless device 315. In this case, the inclusion of the second wireless device ID 345 in response message 330 can serve as an indication that the first message 320 and the included second wireless device ID 345 have been received by wireless device 315.

[0088] In other instances, the second wireless device ID 345 indicated in response message 330 may be a wireless device ID assigned by the wireless device 315 itself. That is, in some cases, the wireless device 315 may generate, configure, or determine the second wireless device ID 345. For example, in some cases, the wireless device 315 may generate a random or pseudo-random value to be used as the second wireless device ID 345. In other cases, the wireless device 315 may generate or derive the second wireless device ID 345 from the first wireless device ID 340. For example, the wireless device 315 may use a truncated version of the first wireless device ID 340 as the second wireless device ID 345. As another example, the wireless device 315 may perform a hash function or other decoding scheme on the first wireless device ID 340, and a hashed or truncated hashed version of the first wireless device ID 340 may be used as the second wireless device ID 345.

[0089] In some cases, the first message 320 sent by reader device 350 may include information indicating how the second wireless device ID 345 should be generated by wireless device 315 (e.g., rules indicating the hash function or decoding scheme to be used, rules indicating the truncation method to be used, or other rules). In some cases, one or more rules associated with the second wireless device ID 345 may be pre-configured at one or both of reader device 350 (e.g., signaled by a network entity, such as a base station) and wireless device 315.

[0090] In some cases, the bit sequence used in feedback 355 to indicate the ACK message may be scrambled by the second radio device ID 345 (e.g., the second radio device ID 345 may be implicitly carried in the response message 330 (e.g., carried in the reverse link), such as Radio Network Temporary Identifier (RNTI), Cyclic Redundancy Check (CRC) scrambling, and / or data scrambling). For example, the CRC and / or data of the response message 330 may be scrambled by the second radio device ID 445.

[0091] Reader device 350 may receive a response message 330 that includes a second wireless device ID 345. Subsequent communication between reader device 350 and wireless device 315 (such as sending or receiving one or more messages) may then use or include the second wireless device ID 345. However, in some cases, such as when a first message 320 indicates that subsequent communication should use the first wireless device ID 340, reader device 350 and wireless device 315 may alternatively use the first wireless device ID 340 for communication.

[0092] Figure 4 An example of a signal flow 400 supporting a technique for querying AIoT devices in a wireless communication system, according to one or more aspects of this disclosure, is shown. In some aspects, the signal flow 400 may implement as described in reference respectively. Figure 1 , Figure 2 and Figure 3 The described wireless communication system 100 or 200 or signal flow 300 may be implemented by or be a combination of these aspects. Signal flow 400 may exemplify the signal flow between wireless device 415 and reader device 450. Wireless device 415 may be as described in reference to... Figure 2 and Figure 3 An example of one of the wireless devices described in wireless device 215 or wireless device 315. Reader device 450 may be as shown in the reference. Figure 2 and Figure 3 Examples of the described UE reader device 250-a, base station reader device 250-b, or reader device 350.

[0093] In some implementations, reader device 450 may transmit a signal including a first message 420 addressing to wireless device 415. The first message 420 may be a PRDCH message including a preamble portion 420-a, a header or control portion 420-b (referred to herein as header portion 420-b), and a data portion 420-c (or in some cases may be included in MAC-CE). The first message 420 may additionally or alternatively include one or more other portions not mentioned. In example signal flow 400, the first message 420 may include a select command or a unicast query command (however, the first message 420 is not limited to select and unicast query commands and may additionally include other wireless device commands). One or more bits of the first message 420 may be used to indicate the purpose of the wireless device command or the first message 420. For example, the header portion 420-b or the data portion 420-c of the first message 420 may include one or more bits indicating the purpose of the wireless device command or the first message 420.

[0094] The reader device 450 may transmit a first message 420 to confirm whether the previously queried wireless device (or the wireless device with which the reader device 450 previously communicated) is still within the coverage area of ​​the reader device 450. In such cases, the first message 420 may include a second wireless device ID 445 (e.g., such as regarding...). Figure 2 The short ID or description about Figure 3 The second wireless device ID described is 345), and the first wireless device ID may be omitted (e.g., such as regarding...). Figure 2 Long ID or description about Figure 3 The first wireless device ID 340 is described. For example, reader device 450 and wireless device 415 may have previously connected and may have previously negotiated (e.g., previously assigned by reader device 450 or wireless device 415) a second wireless device ID 445. Therefore, in some cases, the second wireless device ID 445 may remain valid after the initial communication between reader device 450 and wireless device 415 (e.g., when the session between reader device 450 and wireless device 415 has not ended or the validity period of the second wireless device ID 445 has not otherwise expired). In such cases, while wireless device 415 remains within the coverage area of ​​reader device 450, reader device 450 and wireless device 415 can resume communication using the previously assigned second wireless device ID 445 and avoid assigning a new second wireless ID.

[0095] The second radio device ID 445 may be carried in the header portion 420-b of the first message 420. Alternatively, the second radio device ID 445 may be carried in the MAC header or the data portion 420-c of the first message 420. In some cases, the second radio device ID 445 may be implicitly carried in the first message 420 (e.g., in the forward link), such as RNTI, CRC scrambling, and / or data scrambling (e.g., CRC and / or data scrambling by the second radio device ID 445).

[0096] If wireless device 415 is within the coverage area of ​​reader device 450, wireless device 415 can detect the first message 420 and determine, based on the included second wireless device ID 445, that the first message 420 is intended for wireless device 415. In response, wireless device 415 can send a response message 430 back to reader device 450 (or, in some cases, to a different reader device).

[0097] The response message 430 may include a preamble portion 430-a and a data portion 430-b. The data portion 430-b may include feedback 455, such as an ACK message acknowledging that the first message 420 was successfully received by the wireless device 415. In some cases, the feedback 455 may include an indication of a second wireless device ID 445, and the indication of the second wireless device ID 445 itself can serve as an ACK message. The inclusion of the second wireless device ID 445 in the response message 430 can serve as an indication that the first message 420 and the included second wireless device ID 445 were received by the wireless device 415.

[0098] Reader device 450 may receive a response message 430 that includes a second wireless device ID 445. Subsequent communication between reader device 450 and wireless device 415 (such as sending or receiving one or more messages) may use or include the second wireless device ID 445.

[0099] Figure 5 An example of a signal flow 500 supporting a technology for querying AIoT devices, according to one or more aspects of this disclosure, is shown. In some aspects, the signal flow 500 may implement as described in reference respectively. Figure 1 , Figure 2 , Figure 3 and Figure 4 The described wireless communication system 100 or 200, or signal flow 300 or 400, may be implemented by or be an aspect of these aspects. Signal flow 500 may exemplify the signal flow between wireless device 515 and reader device 550. Wireless device 515 may be as described in references to... Figure 2 , Figure 3 and Figure 4 An example of one of the described wireless devices, wireless device 215, wireless device 315, or wireless device 415. Reader device 550 may be as described in reference respectively. Figure 2 , Figure 3 and Figure 4 Examples of the described UE reader device 250-a, base station reader device 250-b, reader device 350, or reader device 450.

[0100] In some implementations, reader device 550 may transmit a signal including a first message 520 addressing to wireless device 515. The first message 520 may be a PRDCH message including a preamble portion 520-a, a header or control portion 520-b (referred to herein as header portion 520-b), and a data portion 520-c (or in some cases may be included in MAC-CE). The first message 520 may additionally or alternatively include one or more other portions not mentioned. In example signal flow 500, the first message 520 may include a select command or a unicast query command (however, the first message 520 is not limited to select and unicast query commands and may additionally include other wireless device commands). One or more bits of the first message 520 may be used to indicate the purpose of the wireless device command or the first message 520. For example, the header portion 520-b or the data portion 520-c of the first message 520 may include one or more bits indicating the purpose of the wireless device command or the first message 520.

[0101] In some cases, to resolve contention between wireless devices responding to select or unicast query commands, instead of indicating the complete first wireless device ID in the first message 520 (e.g., refer to...), Figure 2 Long ID or description about Figure 3 The reader device 550 may indicate mask bits to partially indicate the first wireless device ID (described as a first wireless device ID 340). For example, the first message 520 may include mask bits of the first wireless device ID 540, which may be a portion of the bits associated with the first wireless device ID. As an example, if the first wireless device ID is 96 bits, the first message 520 may carry only a portion of the bits associated with the first wireless device ID, such as bits 1 through 48. The mask bits of the first wireless device ID 540 may be included in the header portion 520-b or data portion 520-c of the first message 520 (or in some cases, the MAC header). The first message 520 may also indicate mask information, such as a start mask bit (e.g., bit 1), an end mask bit (e.g., bit 48), a bit length (e.g., 48 bits), or other information that may indicate the mask bits carried in the first message 520.

[0102] In some cases, the mask bits of the first wireless device ID 540 may not be unique among the wireless devices within the coverage area of ​​the reader device 550. Therefore, multiple wireless devices 515 may potentially respond to the first message. Consequently, the first message 520 may additionally schedule multiple access opportunities, which may be resources for reverse link communication from the wireless device to the reader device 550. In some cases, the longer the mask bits of the first wireless device ID 540, the fewer the number of scheduled access opportunities, because fewer wireless devices 515 with matching identification information may exist, and therefore fewer wireless devices 515 responding to the first message 520. Similarly, the shorter the mask bits of the first wireless device ID 540, the greater the number of scheduled access opportunities, because a larger number of wireless devices 515 with matching identification information may exist, and therefore a larger number of wireless devices 515 responding to the first message 520. In some cases, the reader device 550 may be pre-configured (or may be signaled by a network entity (e.g., a base station) with a table or one or more mapping rules indicating the association between the mask length and the corresponding number of access opportunities to be allocated.

[0103] When the wireless device 515 detects the first message 520 sent by the reader device 550, the wireless device 515 can use the mask information included in the first message 520 to compare the mask bits of the first wireless device ID 540 included in the first message 520 with the indicated bits of its own identification information (e.g., indicated by the mask information) to determine whether there is at least a partial match between the mask bits of the first wireless device ID 540 included in the first message 520 and the identification information of the wireless device 515 (e.g., the wireless device 515 can compare bits 1 to 48 of its own identification information with the mask bits of the first wireless device ID 540 included in the first message 520).

[0104] In response to determining that the identification information at least partially matches and that the first message 520 is intended for use by the wireless device 515, the wireless device 515 may send a response message 530 back to the reader device 550. The response message 530 may include a preamble portion 530-a and a data portion 530-b. The data portion 530-b may include feedback 555, such as an ACK message acknowledging that the first message 520 was successfully received by the wireless device 515. The feedback 555 may include remaining bits of the first wireless device ID 545 (e.g., unmasked bits, bits of the first wireless device ID not included in the masked bits of the first wireless device ID 540). In this case, the remaining bits of the first wireless device ID 545 may be used as a second wireless device ID. The indication of the remaining bits of the first wireless device ID 545 in the feedback 555 may be used as an ACK message.

[0105] Reader device 550 may receive a response message 530 that includes the remaining bits of a first wireless device ID (which may serve as a second wireless device ID). Subsequent communication between reader device 550 and wireless device 515 (such as sending or receiving one or more messages) may use or include the second wireless device ID.

[0106] Figure 6 An example of a signal flow 600 supporting a technique for querying AIoT devices in a wireless communication system, according to one or more aspects of this disclosure, is shown. In some aspects, the signal flow 600 may implement as described in reference respectively. Figure 1 , Figure 2 , Figure 3 , Figure 4 and Figure 5 The described wireless communication system 100 or 200, or signal flow 300, 400, or 500, may be implemented by or be a manifestation of these aspects. Signal flow 600 may exemplify the signal flow between wireless device 615 and reader device 650. Wireless device 615 may be as described in reference to... Figure 2 , Figure 3 , Figure 4 and Figure 5 An example of one of the described wireless devices 215, 315, 415, or 515. Reader device 650 may be as described in the reference. Figure 2 , Figure 3 , Figure 4 and Figure 5 Examples of the described UE reader device 250-a, base station reader device 250-b, reader device 350, reader device 450, or reader device 550.

[0107] In some implementations, reader device 650 may receive signals from a network entity that locate, identify, or otherwise communicate with multiple wireless devices 615. In such cases, reader device 650 may send multiple separate first messages addressing the multiple wireless devices 615 to attempt to locate each of the wireless devices 615 one by one. These separate first messages may be addressable to reference... Figure 3 , Figure 4 and Figure 5 The first messages 320, 420, and 520 are sent in a similar manner to those described.

[0108] In other cases, reader device 650 may transmit a single first message including an indication to each of the plurality of wireless devices 615. For example, reader device 650 may transmit a signal including a first message 620. The first message 620 may be a PRDCH message including a preamble portion 620-a, a header or control portion 620-b (referred to herein as header portion 620-b), and a data portion 620-c (or in some cases may be included in a MAC-CE). The first message 620 may additionally or alternatively include one or more other portions not mentioned. In example signal flow 600, the first message 620 may include a multicast or multicast select or query command (but the first message 620 is not limited to such commands and may additionally include other wireless device commands). One or more bits of the first message 620 may be used to indicate a wireless device command or the purpose of the first message 620.

[0109] The first message 620 may also indicate identification information (e.g., a long ID for each of the plurality of wireless devices 615) associated with each of the plurality of wireless devices 615. For example, the first message 620 may include a plurality of first wireless device IDs 640 corresponding to a respective wireless device among the plurality of wireless devices 615 (e.g., first wireless device ID 1640-a, first wireless device ID 2640-b, and first wireless device ID 3640-c, such as a long ID for each wireless device). Each of the first wireless device IDs 640 may be indicated in a separate segment of the data portion 620-c of the first message 620 (e.g., with mid-amble between segments). In some cases, each of the first wireless device IDs 640 may be indicated in a separate segment of the control portion 620-b of the first message 620. The first message 620 may additionally include information indicating the number of first wireless device IDs 640 included in the first message 620.

[0110] Additionally, in some cases, the first message 620 may include a group ID, and the group ID may serve as a second wireless device ID 645 assigned by the reader device 650. In other cases, the reader device 650 may assign a different value to the second wireless device ID. For example, the reader device 650 may assign a different value to the second wireless device ID based on... Figure 2 , Figure 3 , Figure 4 or Figure 5 The method described is used to assign a second wireless device ID.

[0111] The first message 620 may additionally schedule resources for reverse link communication from multiple wireless devices 615 to reader device 650, such as multiple access times 660 (e.g., access time 1 660-a, access time 2 660-b, and access time 3 660-c). In some cases, resource allocation for access times 660 may be contention-free, such that a one-to-one mapping may exist between each first wireless device ID 640 and each access time 660.

[0112] In response to receiving the first message 620, each of the wireless devices 615 may determine whether any of the first wireless device IDs in the first wireless device IDs 640 at least partially matches its own identification information. If the wireless device 615 determines that there is at least a partial match, the wireless device 615 may recognize that the first message 620 is intended for the wireless device 615 and may send a response message 630 back to the reader device 650. The response message 630 may include a preamble portion 630-a and a data portion 630-b. The data portion 630-b may include feedback 655, such as an ACK message acknowledging that the first message 620 was successfully received by the wireless device 615. In some cases, the feedback 655 may include an indication of a second wireless device ID 645, and the indication of the second wireless device ID 645 itself may serve as an ACK message. The second wireless device ID 645 indicated in response message 630 may be a second wireless device ID assigned by reader device 650 and included in the first message 620, or it may be a second wireless device ID 645 assigned by wireless device 615 itself, such as regarding Figure 2 , Figure 3 , Figure 4 and Figure 5 As described.

[0113] Reader device 650 can receive a corresponding response message 630, including a corresponding second wireless device ID 645, from one or more of a plurality of wireless devices 615. Subsequent communication between reader device 650 and responding wireless device 615 (such as sending or receiving one or more messages) may use or include the second wireless device ID 645 associated with a particular wireless device 615.

[0114] Figure 7 An example of a signal flow 700 supporting a technique for querying AIoT devices in a wireless communication system, according to one or more aspects of this disclosure, is shown. In some aspects, the signal flow 700 may implement as described in reference respectively. Figure 1 , Figure 2 , Figure 3 , Figure 4 , Figure 5 and Figure 6The described wireless communication system 100 or 200, or signal flow 300, 400, 500, or 600, may be implemented by or be a manifestation of these aspects. Signal flow 700 may exemplify the signal flow between wireless device 715 and reader device 750. Wireless device 715 may be as described in reference to... Figure 2 , Figure 3 , Figure 4 , Figure 5 and Figure 6 The example is one of the wireless devices described, namely wireless device 215, wireless device 315, wireless device 415, wireless device 515, or wireless device 615. The reader device 750 may be as described in the reference. Figure 2 , Figure 3 , Figure 4 , Figure 5 and Figure 6 Examples of the described UE reader device 250-a, base station reader device 250-b, reader device 350, reader device 450, reader device 550, or reader device 650.

[0115] In some specific implementations, this is achieved by sending a single first message (such as a message about) to the wireless device 715, which includes commands such as a select command or a unicast query command (or other wireless commands). Figure 3 , Figure 4 , Figure 5 and Figure 6 Instead of using a first message (320, 420, 520, or 620) to locate the wireless device 715, the reader device 750 may alternatively transmit multiple messages to locate the wireless device 715. For example, the reader device 750 may send a first message 720 and a second message 722. The first message 720 and the second message 722 may be used to transmit different wireless device commands and, additionally or alternatively, transmit information that would otherwise be sent in a single first message (such as in the context of...). Figure 3 , Figure 4 , Figure 5 and Figure 6 The different parts of the first message (320, 420, 520, or 620) described.

[0116] The first message 720 may be a PRDCH message including a preamble portion 720-a, a header or control portion 720-b (referred to herein as header portion 720-b), and a data portion 720-c (or in some cases may be included in a MAC-CE). The first message 720 may additionally or alternatively include one or more other portions not mentioned. In example signal flow 700, the first message 720 may include a first radio device ID 740 associated with radio device 715 (e.g., such as regarding...). Figure 2The first message 720 may alternatively include a wake-up signal command having a first wireless device ID 740, a group ID associated with wireless device 715, and a second wireless device ID 745. One or more bits of the first message 720 may be used to indicate a wireless device command or the purpose of the first message 720. The first wireless device ID 740 may be carried in the data portion 720-c or the header portion 720-b of the first message 720. In some cases, the first wireless device ID 740 may be similar to the one described above. Figure 3 The first wireless device ID 340 described, or about Figure 5 The mask bits for the first wireless device ID 540 as described.

[0117] In some cases, different types of wireless devices (e.g., device types 2a and 2b) can TDM each other. For example, different discontinuous reception (DRX) cycles can be configured for different types of wireless devices. This can trigger different types of wireless devices to wake up during different TDM times. Furthermore, in some cases, different TDM times can be mapped to different second wireless device IDs 745.

[0118] The second message 722 may be a PRDCH message including a preamble portion 722-a, a header or control portion 722-b (referred to herein as header portion 722-b), and a data portion 722-c (or in some cases may be included in the MAC-CE). The second message 722 may additionally or alternatively include one or more other portions not mentioned. In example signal flow 700, the second message 722 may include a second wireless device ID 745 associated with wireless device 715 (e.g., such as regarding...). Figure 2 The described short ID indicates a query command (e.g., a unicast or multicast query command). One or more bits of the second message 722 can be used to indicate the purpose of a wireless device command or the second message 722. The second wireless device ID 745 may be carried in the data portion 722-c or the header portion 722-b of the second message 722. The second wireless device ID 745 may be assigned by the reader device 750, such as in relation to... Figure 3 , Figure 5 or Figure 6 The manner of description. In some cases, the second wireless device ID 745 may additionally or alternatively be indicated in the first message 720, and the second message 722 may be used to indicate one or more portions of the first wireless device ID 740.

[0119] In response to detecting the first message 720 and determining that the first message 720 is intended for use with the wireless device 715 (such as regarding...), Figure 3 , Figure 5 and Figure 6 (As described), wireless device 715 can further detect the second message 722 and determine that the second message is intended for use by wireless device 715 (such as regarding...). Figure 3 , Figure 4 , Figure 5 and Figure 6 (Description method). On the other hand, if the wireless device 715 detects the first message 720 and determines that the first message 720 is not intended for use by the wireless device 715, the wireless device 715 may ignore or disregard the second message 722.

[0120] Based on the determination that the first message 720 and the second message 722 are intended for use by the wireless device 715, the wireless device 715 may send a response message 730 back to the reader device 750. The response message 730 may include a preamble portion 730-a and a data portion 730-b. The data portion 730-b may include feedback 755, such as an ACK message acknowledging that the first message 720 was successfully received by the wireless device 715. In some cases, the feedback 755 may include an indication of a second wireless device ID 745, and the indication of the second wireless device ID 745 itself can serve as an ACK message. The second wireless device ID 745 indicated in the response message 730 may be a second wireless device ID assigned by the reader device 750 and included in the first message 720 or the second message 722, or it may be a second wireless device ID 745 assigned by the wireless device 715 itself, such as regarding... Figure 2 , Figure 3 , Figure 4 , Figure 5 and Figure 6 As described.

[0121] The reader device 750 may receive a response message 730 that includes a second wireless device ID 745. Subsequent communication between the reader device 750 and the wireless device 715 (such as sending or receiving one or more messages) may use or include the second wireless device ID 745.

[0122] Figure 8A block diagram 800 of a device 805 supporting techniques for querying AIoT devices in a wireless communication system, according to one or more aspects of this disclosure, is shown. Device 805 may be an example of aspects of network entity 105 or UE 115 as described herein. Device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. Device 805 or one or more components of device 805 (e.g., receiver 810, transmitter 815, and communication manager 820) may include one or more processors, memory coupled to one or more processors, and instructions stored in the memory executable by one or more processors to enable one or more processors to perform the technical features discussed herein for querying AIoT devices. Each of these components may communicate with each other (e.g., via one or more buses).

[0123] Receiver 810 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 related to technologies used for querying AIoT devices in a wireless communication system). The information may be passed to other components of device 805. Receiver 810 may utilize a single antenna or a collection of multiple antennas.

[0124] Transmitter 815 may provide components for transmitting signals generated by other components of device 805. For example, transmitter 815 may transmit information associated with various information channels, such as control channels, data channels, and information channels related to technologies used for querying AIoT devices in a wireless communication system, including packets, user data, control information, or any combination thereof. In some examples, transmitter 815 may be co-located with receiver 810 in a transceiver module. Transmitter 815 may utilize a single antenna or a collection of multiple antennas.

[0125] The communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be examples of components used to perform various aspects of the techniques described herein for querying AIoT devices in a wireless communication system. For example, the communication manager 820, receiver 810, transmitter 815, or various combinations or components thereof may be able to perform one or more of the functions described herein.

[0126] In some examples, the communication manager 820, receiver 810, transmitter 815, 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).

[0127] Additionally or alternatively, the communication manager 820, receiver 810, transmitter 815, 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 820, receiver 810, transmitter 815, 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 in this disclosure).

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

[0129] The communication manager 820 may support wireless communications according to examples disclosed herein. For example, the communication manager 820 may be capable of, configured to, or operable to support components for transmitting a first message including a wireless device command via a physical layer channel, the wireless device command including a first wireless device identifier having a first number of bits, wherein at least a portion of the first wireless device identifier is transmitted in a data portion, header portion, or control portion of the first message. The communication manager 820 may be capable of, configured to, or operable to support components for receiving a response message from a wireless device and based on a match between the first wireless device identifier and at least a portion of an identifier associated with the wireless device, the response message including a second wireless device identifier having a second number of bits, the second number of bits being fewer than the first number of bits. The communication manager 820 may be capable of, configured to, or operable to support components for communicating one or more messages with a wireless device using the second wireless device identifier.

[0130] By including or configuring a communication manager 820 according to an example as described herein, device 805 (e.g., controlling receiver 810, transmitter 815, communication manager 820 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.

[0131] Figure 9 A block diagram 900 illustrates a device 905 supporting techniques for querying AIoT devices in a wireless communication system, according to one or more aspects of this disclosure. Device 905 may be an example of aspects of device 805 or UE 115 as described herein. Device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. Device 905 or one or more components of device 905 (e.g., receiver 910, transmitter 915, communication manager 920) 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).

[0132] Receiver 910 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 related to technologies used for querying AIoT devices in a wireless communication system). The information may be passed to other components of device 905. Receiver 910 may utilize a single antenna or a collection of multiple antennas.

[0133] Transmitter 915 may provide components for transmitting signals generated by other components of device 905. For example, transmitter 915 may transmit information associated with various information channels, such as control channels, data channels, and information channels related to technologies used for querying AIoT devices in a wireless communication system, including packets, user data, control information, or any combination thereof. In some examples, transmitter 915 may be co-located with receiver 910 in a transceiver module. Transmitter 915 may utilize a single antenna or a collection of multiple antennas.

[0134] Device 905 or its various components may be examples of various aspects of the techniques for querying AIoT devices in a wireless communication system as described herein. For example, communication manager 920 may include wireless device identification manager 925, message manager 930, or any combination thereof. Communication manager 920 may be examples of aspects of communication manager 820 as described herein. In some examples, communication manager 920 or its various components may be configured to use receiver 910, transmitter 915, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 920 may receive information from receiver 910, transmit information to transmitter 915, or integrate in combination with receiver 910, transmitter 915, or both to acquire information, output information, or perform various other operations as described herein.

[0135] Communication manager 920 can support wireless communication according to examples disclosed herein. Wireless device identifier manager 925 is capable of, configured to, or operable to support components for transmitting a first message including a wireless device command via a physical layer channel, the wireless device command including a first wireless device identifier having a first number of bits, wherein at least a portion of the first wireless device identifier is transmitted in a data portion, header portion, or control portion of the first message. Wireless device identifier manager 925 is capable of, configured to, or operable to support components for receiving a response message from a wireless device and based on a match between the first wireless device identifier and at least a portion of an identifier associated with the wireless device, the response message including a second wireless device identifier having a second number of bits, the second number of bits being fewer than the first number of bits. Message manager 930 is capable of, configured to, or operable to support components for communicating one or more messages with a wireless device using the second wireless device identifier.

[0136] In some cases, the wireless device identifier manager 925 and the message manager 930 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 925 and the message manager 930 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.

[0137] Figure 10 A block diagram 1000 of a communication manager 1020 supporting techniques for querying AIoT devices in a wireless communication system, according to one or more aspects of this disclosure, is shown. The communication manager 1020 may be an example of a communication manager 820, a communication manager 920, or aspects thereof as described herein. The communication manager 1020 or its various components may be examples of components for performing various aspects of techniques for querying AIoT devices in a wireless communication system as described herein. For example, the communication manager 1020 may include a wireless device identification manager 1025, a message manager 1030, a session manager 1035, 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).

[0138] Communication manager 1020 can support wireless communication according to examples disclosed herein. Wireless device identifier manager 1025 is capable of, configured to, or operable to support components for transmitting a first message including a wireless device command via a physical layer channel, the wireless device command including a first wireless device identifier having a first number of bits, wherein at least a portion of the first wireless device identifier is transmitted in a data portion, header portion, or control portion of the first message. In some examples, wireless device identifier manager 1025 is capable of, configured to, or operable to support components for receiving a response message from a wireless device and based on a match between the first wireless device identifier and at least a portion of an identifier associated with the wireless device, the response message including a second wireless device identifier having a second number of bits, the second number of bits being fewer than the first number of bits. Message manager 1030 is capable of, configured to, or operable to support components for communicating one or more messages with a wireless device using the second wireless device identifier.

[0139] In some examples, the session manager 1035 is capable of, configured to, or able to operate to support components for establishing a current session with a wireless device based on the received second wireless device identifier, wherein communicating one or more messages with the wireless device using the second wireless device identifier includes: communicating one or more messages with the wireless device using the second wireless device identifier during the duration of the current session.

[0140] In some examples, at least a portion of the first wireless device identifier includes the entire first wireless device identifier.

[0141] In some examples, the remainder of the first wireless device identifier is sent in the control section or header section of the first message.

[0142] In some examples, the remainder of the first wireless device identifier is the second wireless device identifier.

[0143] In some examples, at least a portion of the first wireless device identifier includes a number of masked bits and a number of unmasked bits. In some examples, the second wireless device identifier includes the remaining portion of the first wireless device identifier associated with that number of masked bits.

[0144] In some examples, the wireless device command indicates scheduling information for one or more access opportunities used to communicate a response message.

[0145] In some examples, a wireless device command includes a set of multiple wireless device identifiers and an indication of the number of such identifiers in the set. In some examples, the first wireless device identifier is one of the multiple wireless device identifiers in the set.

[0146] In some examples, the first wireless device identifier includes an application layer identifier, a device hardware identifier, or a device network identifier.

[0147] In some examples, the second wireless device identifier includes a hash version of the first wireless device identifier or a truncated portion of the first wireless device identifier.

[0148] In some examples, the wireless device command includes instructions on rules associated with at least a portion or the remainder of the first wireless device identifier.

[0149] In some examples, the wireless device identifier manager 1025 is capable of, configured to, or operable to support components for sending a second message including a second wireless device identifier after the transmission of the first message, wherein the second wireless device identifier is indicated in the header portion of the second message, or in the data portion of the second message, or by scrambling a CRC, or by scrambling the data portion of the second message.

[0150] In some cases, the wireless device identifier manager 1025, message manager 1030, and session manager 1035 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 memory that enable the processor to perform or facilitate the features of the wireless device identifier manager 1025, message manager 1030, and session manager 1035 discussed herein.

[0151] Figure 11 A diagram of a system 1100 including a device 1105 supporting technology for querying AIoT devices in a wireless communication system, according to one or more aspects of this disclosure, is shown. Device 1105 may be an example of device 805, device 905, network entity 105, or UE 115 as described herein, or a component including such devices. Device 1105 may communicate with one or more other devices (e.g., network entity 105, UE 115, or a combination thereof) (e.g., wirelessly). Device 1105 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 1120, an input / output (I / O) controller (e.g., I / O controller 1110), a transceiver 1115, one or more antennas 1125, at least one memory 1130, code 1135, and at least one processor 1140. These components may communicate electronically or be coupled in other ways (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1145).

[0152] I / O controller 1110 manages the input and output signals of device 1105. I / O controller 1110 can also manage peripheral devices not integrated into device 1105. In some cases, I / O controller 1110 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1110 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 1110 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 1110 may be implemented as part of one or more processors, such as at least one processor 1140. In some cases, a user may interact with the device 1105 via the I / O controller 1110 or via hardware components controlled by the I / O controller 1110.

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

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

[0155] At least one processor 1140 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 units, one or more discrete hardware components, or any combination thereof). In some cases, at least one processor 1140 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 1140. At least one processor 1140 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 1130) to cause device 1105 to perform various functions (e.g., functions or tasks supporting technologies for querying AIoT devices in a wireless communication system). For example, device 1105 or components thereof may include at least one processor 1140 and at least one memory 1130 coupled to or coupled to the at least one processor 1140, the at least one processor 1140 and the at least one memory 1130 being configured to perform the various functions described herein.

[0156] In some examples, at least one processor 1140 may include multiple processors, and at least one memory 1130 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 1140 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 1140) and memory circuitry (which may include at least one memory 1130)) 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 1140 or a processing system including at least one processor 1140 may be configured, configured to, or operable to cause device 1105 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” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code 1135 (e.g., processor-executable code) stored in at least one memory 1130 or otherwise.

[0157] Communication manager 1120 may support wireless communications according to examples disclosed herein. For example, communication manager 1120 may be capable of, configured to, or operable to support components for transmitting a first message including a wireless device command via a physical layer channel, the wireless device command including a first wireless device identifier having a first number of bits, wherein at least a portion of the first wireless device identifier is transmitted in a data portion, header portion, or control portion of the first message. Communication manager 1120 may be capable of, configured to, or operable to support components for receiving a response message from a wireless device and based on a match between the first wireless device identifier and at least a portion of an identifier associated with the wireless device, the response message including a second wireless device identifier having a second number of bits, the second number of bits being fewer than the first number of bits. Communication manager 1120 may be capable of, configured to, or operable to support components for communicating one or more messages with a wireless device using the second wireless device identifier.

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

[0159] In some examples, the communication manager 1120 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using a transceiver 1115, one or more antennas 1125, or any combination thereof, or otherwise cooperating with them. Although the communication manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1120 may be supported or executed by at least one processor 1140, at least one memory 1130, code 1135, or any combination thereof. For example, code 1135 may include instructions that can be executed by at least one processor 1140 to cause device 1105 to perform various aspects of the techniques described herein for querying AIoT devices in a wireless communication system, or at least one processor 1140 and at least one memory 1130 may be otherwise configured to perform or support such operations individually or jointly.

[0160] Figure 12 A flowchart illustrating a method 1200 for querying AIoT devices in a wireless communication system, according to one or more aspects of this disclosure, is shown. Operation of method 1200 may be implemented by a UE or its components as described herein. For example, operation of method 1200 may be performed by, as referenced... Figures 1 to 11 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.

[0161] At 1205, the method may include: transmitting a first message including a wireless device command via a physical layer channel, the wireless device command including a first wireless device identifier having a first number of bits, wherein at least a portion of the first wireless device identifier is transmitted in a data portion, a header portion, or a control portion of the first message. Operation of 1205 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1205 may be provided by reference to [reference]. Figure 10 The described wireless device identification manager 1025 is used to perform this.

[0162] At 1210, the method may include: receiving a response message from a wireless device and based on a first wireless device identifier matching at least partially with an identifier associated with the wireless device, the response message including a second wireless device identifier having a second number of bits, the second number of bits being fewer than the first number of bits. The operation of 1210 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1210 may be provided by reference to [reference]. Figure 10 The described wireless device identification manager 1025 is used to perform this.

[0163] At 1215, the method may include: communicating one or more messages with the wireless device using a second wireless device identifier. The operation of 1215 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1215 may be derived from references... Figure 10 The message manager 1030 described is used to execute this.

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

[0165] Aspect 1: A method for wireless communication by a reader device, the method comprising: transmitting a first message including a wireless device command via a physical layer channel, the wireless device command including a first wireless device identifier having a first number of bits, wherein at least a portion of the first wireless device identifier is transmitted in a data portion, a header portion, or a control portion of the first message; receiving a response message from the wireless device and at least in part based on a match between the first wireless device identifier and at least a partial match with an identifier associated with the wireless device, the response message including a second wireless device identifier having a second number of bits, the second number of bits being fewer than the first number of bits; and communicating one or more messages with the wireless device using the second wireless device identifier.

[0166] Aspect 2: According to the method of aspect 1, the method further includes: establishing a current session with the wireless device based at least in part on receiving the second wireless device identifier, wherein communicating the one or more messages with the wireless device using the second wireless device identifier includes: communicating the one or more messages with the wireless device using the second wireless device identifier during the duration of the current session.

[0167] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the at least portion of the first wireless device identifier comprises the entire portion of the first wireless device identifier.

[0168] Aspect 4: The method according to any one of Aspects 1 to 3, wherein the remainder of the first wireless device identifier is transmitted in the control portion or the header portion of the first message.

[0169] Aspect 5: According to the method of aspect 4, the remaining portion of the first wireless device identifier is the second wireless device identifier.

[0170] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the at least portion of the first wireless device identifier includes a number of mask bits and a number of unmasked bits, and the second wireless device identifier includes the remaining portion of the first wireless device identifier associated with the number of mask bits.

[0171] Aspect 7: The method according to any one of Aspects 1 to 6, wherein the wireless device command indicates scheduling information for one or more access opportunities for conveying the response message.

[0172] Aspect 8: The method according to any one of Aspects 1 to 7, wherein the wireless device command includes a plurality of wireless device identifiers and an indication of the number of the plurality of wireless device identifiers, wherein the first wireless device identifier is one of the plurality of wireless device identifiers.

[0173] Aspect 9: The method according to any one of Aspects 1 to 8, wherein the first wireless device identifier includes an application layer identifier, a device hardware identifier, or a device network identifier.

[0174] Aspect 10: The method according to any one of Aspects 1 to 9, wherein the second wireless device identifier includes a hash version of the first wireless device identifier or a truncated portion of the first wireless device identifier.

[0175] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the wireless device command includes an indication of a rule associated with at least a portion or the remainder of the first wireless device identifier.

[0176] Aspect 12: The method according to any one of Aspects 1 to 11, the method further comprising: sending a second message including the second wireless device identifier after the transmission of the first message, wherein the second wireless device identifier is indicated in the header portion of the second message, or in the data portion of the second message, or by scrambling a CRC, or by scrambling the data portion of the second message.

[0177] Aspect 13: 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 12.

[0178] Aspect 14: 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 12.

[0179] Aspect 15: A non-transitory computer-readable medium storing code for wireless communication, said code comprising instructions executable by one or more processors to perform the method according to any one of Aspects 1 to 12. It should be noted that the methods described herein describe possible specific implementations. Operations and steps can be rearranged or otherwise modified, and other specific implementations are possible. Furthermore, aspects from two or more of these methods can be combined.

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

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

[0182] The various exemplary blocks and components described herein can be implemented or performed using general-purpose processors, DSPs, ASICs, CPUs, graphics processing units (GPUs), neural processing units (NPUs), FPGAs or other programmable logic devices, discrete gate or transistor logic units, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternatives, 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 functions or operations individually or jointly.

[0183] 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 various portions distributed such that the functions are implemented in different physical locations.

[0184] Computer-readable media include 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 that can be accessed 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.

[0185] 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".

[0186] 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 those 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".

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

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

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

[0190] 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 including a wireless device command is transmitted via a physical layer channel. The wireless device command includes a first wireless device identifier having a first number of bits, wherein at least a portion of the first wireless device identifier is transmitted in the data portion, header portion, or control portion of the first message. A response message is received from a wireless device and at least in part based on a partial match between the first wireless device identifier and an identifier associated with the wireless device, the response message including a second wireless device identifier having a second number of bits, the second number of bits being fewer than the first number of bits; and One or more messages are communicated with the wireless device, at least in part, based on the second wireless device identifier.

2. The reader device of claim 1, wherein the one or more processors are further configured individually or collectively to cause the reader device to: A current session with the wireless device is established at least in part based on receiving the second wireless device identifier, wherein one or more messages are conveyed using the second wireless device identifier during the duration of the current session.

3. The reader device of claim 1, wherein the at least portion of the first wireless device identifier comprises the entire portion of the first wireless device identifier.

4. The reader device of claim 1, wherein the remainder of the first wireless device identifier is transmitted in the control portion or the header portion of the first message.

5. The reader device of claim 4, wherein the remaining portion of the first wireless device identifier is the second wireless device identifier.

6. The reader device of claim 1, wherein the at least portion of the first wireless device identifier comprises a number of masked bits and a number of unmasked bits. The second wireless device identifier includes the remaining portion of the first wireless device identifier associated with the number of mask bits.

7. The reader device of claim 1, wherein the wireless device command indicates scheduling information for one or more access opportunities for sending the response message.

8. The reader device of claim 1, wherein the wireless device command includes a plurality of wireless device identifiers and an indication of the number of the plurality of wireless device identifiers, and The first wireless device identifier is one of the plurality of wireless device identifiers.

9. The reader device according to claim 1, wherein the first wireless device identifier includes an application layer identifier, a device hardware identifier, or a device network identifier.

10. The reader device of claim 1, wherein the second wireless device identifier includes a hash version of the first wireless device identifier or a truncated portion of the first wireless device identifier.

11. The reader device of claim 1, wherein the wireless device command includes an indication of a rule associated with at least a portion or the remainder of the first wireless device identifier.

12. The reader device of claim 1, wherein the one or more processors are individually or jointly further configured to cause the reader device to: A second message including the second wireless device identifier is sent after the first message is sent, wherein the second wireless device identifier is indicated in the header portion of the second message, or in the data portion of the second message, or by scrambling the cyclic redundancy check (CRC) or by scrambling the data portion of the second message.

13. A method for wireless communication by a reader device, the method comprising: A first message including a wireless device command is transmitted via a physical layer channel. The wireless device command includes a first wireless device identifier having a first number of bits, wherein at least a portion of the first wireless device identifier is transmitted in the data portion, header portion, or control portion of the first message. A response message is received from a wireless device and at least in part based on a partial match between the first wireless device identifier and an identifier associated with the wireless device, the response message including a second wireless device identifier having a second number of bits, the second number of bits being fewer than the first number of bits; and One or more messages are communicated with the wireless device, at least in part, based on the second wireless device identifier.

14. The method according to claim 13, further comprising: Establishing a current session with the wireless device is based at least in part on receiving the second wireless device identifier, wherein communicating the one or more messages with the wireless device using the second wireless device identifier includes: communicating the one or more messages with the wireless device using the second wireless device identifier during the duration of the current session.

15. The method of claim 13, wherein the at least portion of the first wireless device identifier comprises the entire portion of the first wireless device identifier.

16. The method of claim 13, wherein the remainder of the first wireless device identifier is transmitted in the control portion or the header portion of the first message.

17. The method of claim 16, wherein the remaining portion of the first wireless device identifier is the second wireless device identifier.

18. The method of claim 13, wherein the at least portion of the first wireless device identifier comprises a number of mask bits and a number of unmasked bits. The second wireless device identifier includes the remaining portion of the first wireless device identifier associated with the number of mask bits.

19. A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to: A first message including a wireless device command is transmitted via a physical layer channel. The wireless device command includes a first wireless device identifier having a first number of bits, wherein at least a portion of the first wireless device identifier is transmitted in the data portion, header portion, or control portion of the first message. A response message is received from a wireless device and at least in part based on a partial match between the first wireless device identifier and an identifier associated with the wireless device, the response message including a second wireless device identifier having a second number of bits, the second number of bits being fewer than the first number of bits; and One or more messages are communicated with the wireless device, at least in part, based on the second wireless device identifier.

20. The non-transitory computer-readable medium of claim 19, wherein the instructions are further executable by the one or more processors to: A current session with the wireless device is established at least in part based on receiving the second wireless device identifier, wherein one or more messages are conveyed using the second wireless device identifier during the duration of the current session.

Images