Transmission skipping mechanisms for ambient IoT devices

Abstract

Example methods, apparatuses, and non-transitory computer-readable storage media are provided. An example method includes receiving a first transmission (or channel) that indicates a number of transmissions to skip. A device may skip the number of transmissions in circumstances where the device is indicated to skip such transmissions. The device then receives a second transmission after skipping the number of received. A number of preambles may be counted by the device to determine the number of transmissions skipped.

Description

TRANSMISSION SKIPPING MECHANISMS FOR AMBIENT IOT DEVICESPRIORITY CLAIM AND CROSS-REFERENCE[oooi] This patent application claims priority to U.S. Provisional Application No. 63 / 574,731, filed on April 04, 2024, and entitled “Timing Considerations for Ambient loT Devices,” and U.S. Provisional Application No. 63 / 645,021, filed on May 09, 2024, entitled “Timing Considerations for Ambient loT Devices,” which are hereby incorporated by reference herein as if reproduced in their entireties. TECHNICAL FIELD

[0002] The present disclosure relates generally to managing the allocation of resources in a network, and in particular embodiments, to techniques and mechanisms for improved timing considerations for ambient loT devices.BACKGROUND

[0003] Radio frequency identification (RFID) devices, which were introduced over two decades ago, have a low degree of complexity compared to cellular technologies, and can rely on captured RF energy to provide processing power and for transmission. The low degree of complexity enables RFID devices, such as tags, to enter the marketplace for applications including inventory control. There are several standards related to RFID devices to specify waveforms for transmission and reception and message protocol. In part due to the low degree of complexity, there are several drawbacks with RFID devices. Revisiting the communication links and protocols used by RFID devices should be considered given the ubiquity of cellular systems around the world.SUMMARY

[0004] Technical advantages are generally achieved, by embodiments of this disclosure which describe improved timing considerations for ambient loT devices.

[0005] In accordance with an embodiment, an example method is provided. The method maybe a method for wireless communication by a device. The example method includes receiving, by a device, a first transmission comprising scheduling information, the scheduling information indicating a number of transmissions intended for a group of devices. The example method furtherincludes skipping, by the device, reception of a transmission for the number of transmissions. The example method further includes receiving, by the device, a second transmission after skipping the number of transmissions.

[0006] In some embodiments, the first transmission further includes an indicator indicating the group of devices, where the number of transmissions indicating a number of transmissions a device within the group of devices is expected to monitor, and where the device is not the device within the group of devices.

[0007] In some embodiments, the indicator is based on a relationship with a skip time value.

[0008] In some embodiments, the skip time value exceeds or is smaller than a time value that is based on a capability of the device.

[0009] In some embodiments, a second time value related the capability is based on a second device of a skip group.

[0010] In some embodiments, the skipping the reception of a transmission for the number of transmissions includes counting, by the device, each preamble of each received transmission, and skipping, by the device, processing of a nonpreamble portion of each received transmission.

[0011] In some embodiments, the example method further includes entering, by the device, a state, where in the state the device is configured for the counting of each preamble of each received transmission and the skipping of the processing of the non-preamble portion of each received transmission.

[0012] In some embodiments, the example method further includes during, by the device, the skipping of the processing of the non-preamble portion of each received transmission, performing energy harvesting.

[0013] In accordance with another aspect of the disclosure, another example method is provided. The method may be a method for wireless communication by a device. The example method includes receiving, from a reader, a first transmission including an indicator indicating a number of transmissions to skip, for example including a skip group and a number of transmissions for members of the skip group to skip. The example method further includes skipping reception of a transmission for the number of transmissions, for example from the reader in accordance with the indicator indicating the number of transmissions to skip. The example method further includes receiving, from thereader, a second transmission after skipping the reception of the transmission, for example the transmission of the number of transmission from the reader.

[0014] In some embodiments, the number of transmissions to skip is a number of physical reader to device channel (PRDCH) transmissions to skip.

[0015] In some embodiments, the indicator further indicates a skip group, where the number of transmissions to skip corresponds to the skip group.

[0016] In some embodiments, the skipping the reception of the transmission includes counting each preamble of each received transmission, and skipping processing of a non-preamble portion of each received transmission in accordance with the indicator indicating a number of transmissions to skip.

[0017] In some embodiments, the method further includes, during the skipping of the processing of the non-preamble portion of each received transmission, performing energy harvesting.

[0018] In accordance with another aspect of the disclosure, another example method is provided. The method may be a method for wireless communication by a device, for example a reader. The example method includes transmitting, by a reader, a first transmission comprising a first indicator indicating a first number of transmissions to skip. The example method further includes transmitting, by the reader, the first number of transmissions that includes a number of physical reader to device channel (PRDCH) transmissions.

[0019] In some embodiments, the example method further includes transmitting, by the reader, a second transmission including a second indicator indicating a second number of transmissions to skip after transmitting the first number of transmissions.

[0020] In some embodiments, the first number of transmissions to skip is determined based on at least one of a charging rate, a charging capability, or an energy harvesting.

[0021] In some embodiments, the first indicator indicates a skip group, where the first number of transmissions includes a number of transmissions for members of the skip group to skip, and where a device is a member of the skip group.

[0022] In some embodiments, the first indicator is based on a relationship with a skip time value.

[0023] In some embodiments, the skip time value exceeds or is smaller than a time value that is based on a capability is related to the device.

[0024] In some embodiments, a second time value is based on a second device of a skip group.

[0025] In accordance with another aspect of the disclosure, another example method is provided. The method may be a method for wireless communication by a device. The example method includes receiving a first transmission including scheduling information, the scheduling information indicating a number of transmissions intended for a group of devices. The method further includes skipping reception of a transmission of the number of transmissions. The method further includes receiving a second transmission after sipping the number of transmissions.

[0026] In some embodiments, the first transmission further includes an indicator indicating the group of devices, where the number of transmissions is indicated as expected to be monitored by a device within the group of devices, and the device is not the device within the group of devices.

[0027] In some embodiments, the indicator is based on a relationship with a skip time value. In some such embodiments, the skip time value exceeds or is smaller than a time value that is based on a capability of the device. In some other such embodiments, a second time value related to the capability is based on a second device of a skip group.

[0028] In some embodiments, the skipping the reception of the transmission for the number of transmission includes counting each preamble of each received transmission, and skipping processing of a non-preamble portion of each received transmission.

[0029] In some embodiments, the method further includes enabling the device to enter to a state in which the device is configured for the counting each preamble of each received transmission and the skipping the processing of the non-preamble portion of each received transmission.

[0030] In some embodiments, the method further includes, during the skipping of the processing of the pre-amble portion of each received transmission, performing energy harvesting.

[0031] In accordance with another aspect of the disclosure, another example method is provided. The method may be a method for wireless communication bya device. The example method includes receiving scheduling parameters indicating a size of a first window. The size of the first window indicates a number of transmissions from a reader, and the scheduling parameters further indicate one or more selection criteria indicating whether the device is scheduled for communications in the first window. The example method further includes counting a number of received transmissions within the first window. The example method further includes, in response to the one or more selection criteria indicating that the device is scheduled for the communications in the first window, processing one or more received transmissions within the first window. The example method further includes, in response to the counted number of the received transmissions equaling or exceeding the size of the first window, receiving at least one next scheduling parameter.

[0032] In some embodiments, the example method further includes transmitting, by the device, a message to the reader in response to the processing the one or more received transmissions within the first window.

[0033] In some embodiments, at least one transmission of the received transmissions comprises a preamble and a combination of scheduling information and a payload.

[0034] In some embodiments, the counting the number of the received transmissions within the first window includes counting, by the device, a number of preambles.

[0035] In some embodiments, the one or more selection criteria comprise a combination of a first criterion for the device with a low energy level, and a second criterion for the device being unable to process one or more received transmissions within an earlier window.

[0036] In accordance with another aspect of the disclosure, an example apparatus is provided. An example apparatus includes at least one processor and at least one memory having computer instructions stored thereon. The computer instructions, in response to execution of the computer instructions, cause the apparatus to perform the method according to any one of the example methods discussed herein.

[0037] In accordance with another aspect of the disclosure, an example non-transitory computer-readable storage medium is provided. The example non-transitory computer-readable storage medium has computer programinstructions stored thereon. In response to execution by at least one processor, the computer program instructions configure the at least one processor to perform the method according to any one of the example methods discussed herein.BRIEF DESCRIPTION OF THE DRAWINGS

[0038] For a more complete understanding of the present disclosure, and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:

[0039] FIG. 1 illustrates an example topology in which a base station (BS) is communicating with an Ambient loT device;

[0040] FIG. 2 illustrates another example topology in which a base station is communicating with an intermediate node;

[0041] FIG. 3 illustrates an example of channels for communications with an Ambient loT device;

[0042] FIG. 4 illustrates timing for four example communication events;

[0043] FIG. 5 illustrates four example energy levels for a device;

[0044] FIG. 6 illustrates four example energy levels for a device with energy harvesting;

[0045] FIG. 7A illustrates example energy levels for a device for a sequence of transmissions;

[0046] FIG. 7B illustrates an example sequence of commands of an example signaling approach;

[0047] FIG. 7C illustrates an example of R2D transmission that includes a timing acquisition signal and a PRDCH;

[0048] FIG. 7D illustrates an example of inventorying for a number of tags;

[0049] FIG. 8A illustrates a flowchart depicting operations of an example process for skipping of PRDCH at power on;

[0050] FIG. 8B illustrates a flowchart depicting operations of an example process for skipping of PRDCH at power on without using groups;

[0051] FIG. 8C illustrates a flowchart depicting operations of an example process for creating multiple levels of groups;

[0052] FIG. 8D illustrates examples of orderings of multiple windows;

[0053] FIG. 9 illustrates a flowchart depicting operations of an example process for skipping after a device transmits a PDRCH;

[0054] FIG. 10 illustrates a pipelining diagram of group transmission skipping;

[0055] FIG. 11 illustrates a pipelining diagram of device transmission skipping;

[0056] FIG. 12 illustrates example modulations with different waveform formats;

[0057] FIG. 13 illustrates example contents of a PRDCH;

[0058] FIG. 14 illustrates an example layout of fields used to specify transmission information;

[0059] FIG. 15 illustrates example locations of transmission information for a PRDCH;

[0060] FIG. 16 illustrates example waveform formats;

[0061] FIG. 17 illustrates a flowchart depicting operations of an example process for operation of a base station or intermediate node;

[0062] FIG. 18 illustrates a flowchart depicting operations of an example process for operation of an ambient loT device;

[0063] FIG. 19 illustrates example sizes of headers;

[0064] FIG. 20 illustrates example coding schemes with various length and header fields;

[0065] FIG. 21 illustrates an example process where one or more PRDCH are used for transmission;

[0066] FIG. 22 illustrates example fields for use of a different number of PRDCH;

[0067] FIG. 23 illustrates a flowchart depicting operations of receiving and transmitting a continuation field;

[0068] FIG. 24 illustrates a flowchart depicting example operations for skipping transmissions by a device;

[0069] FIG. 25 illustrates a flowchart depicting example operations for skipping transmission by a device group;

[0070] FIG. 26 illustrates a flowchart depicting example operations for transmitting data for skipping by a device or device group;

[0071] FIG. 27 illustrates a flowchart depicting example operations for skipping transmissions based on counting received transmissions;

[0072] FIG. 28 illustrates an example communications system in accordance with at least one embodiment of the present disclosure;

[0073] FIG. 29 illustrates another example communications system in accordance with at least one embodiment of the present disclosure;

[0074] FIG. 30A illustrates a block diagram of an example edge device in accordance with at least one embodiment of the present disclosure;

[0075] FIG. 30B illustrates a block diagram of an example base station in accordance with at least one embodiment of the present disclosure; and

[0076] FIG. 31 illustrates an example computing system in accordance with at least one embodiment of the present disclosure.

[0077] Corresponding numerals and symbols in the different figures generally refer to corresponding parts unless otherwise indicated. The figures are drawn to clearly illustrate the relevant aspects of the embodiments and are not necessarily drawn to scale.DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

[0078] Cellular technology, which is implemented within smartphones, allows user equipments (UEs) to have data rates as low as megabits to as high as gigabits per second depending on UE capability, to support network coverage while UEs traverse cells, operate in both licensed and unlicensed bands, and to coexist with each other. Among the technologies used for cellular technology are tight timing requirements; advanced error correction techniques; multiple-input multipleoutput technology; protocols for medium access control and for configuration; and security protocols for integrity and encryption. In order to support the benefits of cellular technology, the UEs tend to have a high degree of complexity due to high precision crystals / oscillators, memory, tracking loops, multiple receivers, high powered amplifiers, high speed analog-to-digital convertors, support of large bandwidth (BW) and many radio bands, and sophisticated protocols. In addition, these UEs generally have access to energy storage, e.g., batteries that can provide days of service before recharging.

[0079] Comparatively, a RFID device is significantly less complex. In part due to the low degree of complexity, a RFID device suffers from drawbacks including limited range, operation in unlicensed bands where interference from other devices can impact reliability, reader complexity, and network connectivity. Basedon improvements in technology over the past decade, the communication links and protocols used by RFID devices can be improved.

[0080] 3GPP recently completed a study of ambient internet of things (loT) devices with a technical report and started another study within working groups to perform evaluations for several deployment scenarios and system topologies for different power classes, with objectives to study feasibility solutions including frame structure, synchronization and timing, random access; numerologies, bandwidths, and multiple access; waveforms and modulations; channel coding; downlink channel / signal aspects; uplink channel / signal aspects; scheduling and timing relationships; and necessary characteristics of carrier-wave waveform for a carrier wave provided externally to the ambient loT device, including for interference handling at ambient loT receiver, and at NR base station. Other objectives included studying a compact protocol stack and lightweight signaling procedure for, for instance, paging, random access, and data transmission. Embodiments of the present disclosure address these considerations.

[0081] FIG. 1 depicts a first topology (e.g., Topology 1) in which a base station is communicating with an ambient loT device. The ambient loT device is in coverage of the base station. In this regard, the base station may directly communicate with the ambient loT device. In some embodiments, the ambient loT device communicates bi-directionally with the base station. In some embodiments, the communication between the base station and the ambient loT device includes ambient loT data communication and / or signaling.

[0082] FIG. 2 depicts a second topology (e.g., Topology 2) in which a base station is communicating with an intermediate node, such as a UE. The intermediate node is within coverage of the base station. The ambient loT device is in coverage of the intermediate node. The ambient loT device may or may not be in coverage of the base station. In this regard, the ambient loT device may communicate to a base station via the intermediate node. In some embodiments, the ambient loT device communicates bi-directionally with the intermediate node between the device and the base station. The intermediate node may transfer ambient loT data and / or signaling between the base station and the ambient loT device.

[0083] The communication link to an ambient loT device can be called a reader to device (R2D) link while the communication link from an ambient loTdevice can be called a device to reader (D2R) link. In FIG. 1, the Un downlink (e.g., from the base station to the ambient loT device) can be the same frequency as the R2D link. The base station acts as a reader. A reader can perform both transmit and receive functions. The functionality of a reader can be split where one reader just transmits while another reader receives. Likewise, the Uu uplink can be the same frequency as the D2R link. In FIG. 2, the Uu downlink (e.g., from the base station to the intermediate node) can be on a different frequency as the R2D link (e.g., from the intermediate node to the ambient loT device). Likewise, the Uu uplink (e.g., from the intermediate node to the base station) can be on a different frequency as the D2R link (e.g., from the ambient loT device to the intermediate node). The reader in this example is the intermediate node. In some embodiments, the transmission from the ambient loT device occurs at least in the UL spectrum.

[0084] The physical layer design may be the same for both topologies. There may be two types of ambient loT devices. The first type of ambient loT devices is a low power (LP) device with approximately 1 qW power consumption. The second type of ambient loT devices is a high power (HP) device with hundreds of qW power consumption. In some contexts, a HP device may have more capabilities than a LP device, such as better radio performance and additional processing capacity. The first type of devices, e.g., low power device, may have one or more attributes, including one or more of: a ~1 qW peak power consumption, has energy storage, initial sampling frequency offset (SFO) up to ioxppm (the exponent, X, maybe determined by a standard or other agreement determined), neither downlink (DL) nor uplink (UL) amplification in the device. The device’s UL transmission may be backscattered on a carrier wave provided externally.

[0085] The second type of devices, e.g., the high power device, can be further classified by transmission capability and can have one or more other attributes, in some embodiments including one or more of less than or equal to a few hundred zzW peak power consumption, has energy storage, initial sampling frequency offset (SFO) up to iovppm, DL and / or UL amplification in the device. In another implementation, the other attributes may include one or more of less than or equal to a few hundred zzW peak power consumption, has energy storage, initial sampling frequency offset (SFO) up to iovppm, DL and / or UL amplification inthe device. In any such implementation, the device’s UL transmission may be generated internally by the device.

[0086] In some other embodiments, additional types of ambient loT devices may be introduced. In some embodiments, there may be capabilities (or features) associated with each device type. For example, a basic feature is a device supporting the some of the characteristics of Device 1 (backscattering, modulation(s) supported, etc.). Additional features can introduce energy consumption levels, amplification, and / or the like.

[0087] With a harmonized design, there is a compatibility introduced into the system where all ambient loT devices can support a basic operation, interface, and / or protocol, while also allowing differentiation. There maybe deployments with only LP devices (e.g., Device 1), only HP devices (e.g., Devices 2a and 2b), or combinations of LP and HP devices. A LP device can have a substantially lower data rate than a HP device and can have a smaller coverage area than a HP device. The quality of service for LP devices may be lower than for HP devices. As a result of these limitations for an LP device, it may be beneficial to introduce means to have a harmonized design to allow additional capabilities of a HP device to be enabled in a seamless manner. Additional capabilities can include better receiver (e.g., improved data rate), error correction resulting in fewer retransmissions (e.g., avoid a retransmission due a single (multiple) bit error(s), reduced latency). These additional capabilities can further improve system capacity.

[0088] The transmission of data from a reader (R), such as a base station or intermediate node, to an ambient loT device or tag (D) occurs on the R2D link and uses the physical reader to device channel (PRDCH). Similarly, the transmission of data from a device to a reader occurs on the D2Rlink and uses the physical device to reader channel (PDRCH). Both channels are shown in FIG. 3-

[0089] Details about channel coding and cyclic redundancy check (CRC) codes are related to these channels. In some embodiments, a payload received from upper layers maybe received at the lower layer. Additionally or alternatively, the CRC may be computed over the payload. A channel encoding, where defined, may be applied to both the payload and CRC to create a PxxCH (e.g., PDRCH and / or PRDCH) that may be mapped to the physical layer. In this regard, the detailsabout mapping the channels to the physical layer, e.g., placement of timing symbols, modulation, and delimiters, may also be provided.

[0090] In some embodiments, a reader may utilize transmissions for more than just data transmission. For example, in some embodiments, a reader may utilize received signals for device location. In some implementations, a reader may utilize signal energy of a transmission at one or more locations to determine a proximity of a device to a reader. Additionally or alternatively, in some embodiments the reader may vary transmit energy of transmissions to determine proximity of a reader when it is unable to receive a response.

[0091] Due to energy consumption constraints, ambient loT devices have limitations on what processing can be supported. For example, approaches used in cellular systems for scheduling may not be applicable to ambient loT devices. For example, although devices have energy storage, the amount of storage can vary based on device type. Since a device has finite energy capacity, any act of communication depletes the energy of the device. Consideration of the energy aspect can impact protocol and scheduling. A protocol and / or scheduling may accommodate energy harvesting (EH) in a seamless manner. In addition, there maybe different implementations for EH. Some devices can harvest RF energy, while others can have solar and / or light, piezoelectric (e.g., kinetic and / or vibration), electromagnetic, electrostatic, heat / thermal, thermoelectric, magnetic, wind / water, acoustic, and / or the like. In some embodiments, combinations of EH can be supported. These different implementations for EH may be transparent to the protocol and scheduling.

[0092] Latency may be defined as: The time for charging the ambient loT device storage (if present) is not included in the latency defined above. Time for energy harvesting, charging (e.g., a charging capability), etc. is regarded as an implementation issue only. It is noted that EH does not impact the latency definition.

[0093] A device may be unavailable for up to several tens of seconds. Solutions are provided to support timing for devices to have sufficient energy for communications while considering protocol and / or scheduling aspects. Additionally, appropriate signaling elements are proposed to support the various device types, capabilities, and limitations of ambient loT devices.

[0094] Certain minimum processing times maybe considered. For example:

[0095] TR2D_min: Minimum Time (e.g., a minimum processing time) between a R2D transmission and the corresponding D2R transmission following it.

[0096] TD2R_min: Minimum Time (e.g., a minimum processing time) between a D2R transmission and the corresponding R2D transmission following it.

[0097] TR2D_ _R2D_min I Minimum Time (e.g., a minimum processing time) between two different consecutive R2D transmissions to the same A-IoT device.

[0098] TD2R_D2R_min: Minimum Time (e.g., a minimum processing time) between two different consecutive D2R transmissions from the same A-IoT device.

[0099] A maximum timing may not be necessary, since the maximum time may impact device availability and not be utilized in some embodiments given that clock-based timing may be avoided. Thus, in some such embodiments, a maximum time may not be provided.

[0100] FIG. 4 depicts the four communication events described above.Specifically, example (a) in FIG. 4 shows consecutive PRDCH transmissions with a time ti between them. From a device perspective, ti can represent the minimum processing time for PRDCH 1 (TR2D_ _R2D_min ). The time ti can also include factors related to device capability. Example (b) in FIG. 4 shows PRDCH transmission followed by a PDRCH with a time t2between them. From a device perspective, t2can represent the minimum processing time for PRDCH and a minimum time (e.g., a minimum processing time) to prepare the transmission of PDRCH, corresponding to TR2D_min. The time t2can also include factors related to device capability. Example (c) in FIG. 4 shows PDRCH transmission followed by a PRDCH with a time t3between them. From a device perspective, t3can represent the minimum processing time for PDRCH, corresponding to TD2R_min. In some circumstances, the processing time maybe small. The time t3can also include factors related to device capability. Example (d) in FIG. 4 shows consecutive PDRCH transmissions with a time t4between them. From a device perspective, t4can represent the minimum processing time for PDRCH 1, corresponding to TD2R_ _D2R_min. Note that the processing time may be small. The time t4can also include factors related to device capability. For example, if one or more capabilities of a device is known to a reader, the minimum time (e.g., a minimum processing time) may be determined to be sufficient to allow the device of suchcapabilities to process the transmission. In other embodiments, all devices may be assumed to have the same processing time.

[0101] In some embodiments, the value of TR2D_min for a particular device is large enough that the particular device that is an intended recipient of a first PRDCH can complete processing before receiving the next PRDCH intended for that device. The minimum processing time may be measured from the end of the first PRDCH to the beginning of the next PRDCH intended for that recipient. In a circumstance where the minimum processing time is sufficiently large, another PRDCH intended for a different recipient may be scheduled between the two PRDCH transmissions.MINIMUM PROCESSING TIMING DETAILS

[0102] There are several considerations about the minimum processing time. The minimum processing time may vary based on factors, including: message length; device capability; whether the reader knows the device capability; and / or the type of message and associated processing with the type of message. For the following embodiments, the description can be applicable to ti, t2, t3, and t4.

[0103] If the message length is presented by I, there can be a threshold rule. As an example, when the length I is smaller than a certain length IT (e.g., a length threshold), a first processing time tmin,i is used, otherwise a second processing time tmin, 2 is used.

[0104] Alternatively, the minimum processing time is proportional to the message length tmin= t0+ kl, where to is a minimum time (e.g., a minimum processing time) offset and A: is a constant, even a power of 2 (for implementation by a shifter). The values of to and k can be dependent on device capability. A combination of a threshold and linear equation can be also used.

[0105] Certain messages can require additional processing time. For example, a message that updates EEPROM in a device may require more time than a message reading the EEPROM. The equation tmin= tm+ t(msg) captures a minimum processing time tm and t(msg) can be a time value associated with the message, t(msg) can be a function. This can be stored in a table or based on capability.

[0106] For the D2R link, when channel coding is used, additional processing time may be needed for the device to generate the encoded sequence. A device capable of supporting a specific channel coding scheme may require additional timing.

[0107] Alternatively, the reader can signal a time value or and an index to a table of time values. For example, if a table of 8 values is used, a three-bit index idx can be provided to generate the minimum processing time, as shown in Table 1- tmin = to + table idx]. A signaled time value can be a multiplier m. tmin= t0+ mbt, where At can represent a unit of time such as 50 microseconds. Table 1. Table of additional times

[0108] Alternatively, there are scenarios where a reader is unaware of a device capability. For example, in an inventory scenario where there can be a mixture of device 1, device 2a, and / or device 2b devices, a reader may assume the worst-case timing (or a reasonably large time value) and signal a timing value to use. An example is for a reader to send an index (idx) to a table (e.g., Table 2 herein).Table 2. Table of absolute times

[0109] Alternatively, when a reader is addressing a device with an unknown identity, an absolute timing can be used. Once the reader is aware of the device (e.g., capabilities), a second minimum processing timing is used. In such a case, the destination of the PRDCH can be used to determine the minimum processing timing.

[0110] In this regard, the minimum processing time can be a function of message type, a function of message length, and / or an amount of processing needed. There can be a signaled indicator or multiplier, as an example. For the 4 different combinations of PDRCH and PRDCH in FIG. 4, a different relationship is used for each combination, as shown below:

[0111] h = ti ,min + ki *( or ti = table2[zdx]

[0112] t2= t2,min + t msg) + tablei[zdx]

[0113] t3— t3,min + t(msg)

[0114] t4= t4,min + t^msg)RECHARGING DETAILS

[0115] A device consumes energy when receiving any PRDCH. A device does not consume, or consumes a small amount of energy, when it is not transmitting. An example of such energy consumption is depicted in FIG. 5.

[0116] In example (a) of FIG. 5, the energy storage is represented on a relative scale with 100% being the maximum energy. In some contexts, the standards may specify a minimum requirement of energy storage. Normally an upper limit for energy storage is not specified. There may be capabilities to specify different levels of energy storage (e.g., a charging capability). Alternatively, the minimum requirement may be measured relative to the peak power consumption of the device. Also shown are three levels, a minimum level to receive PRDCH and transmit PDRCH, a minimum level to transmit PDRCH, and a minimum level to receive PRDCH. In the example, assume a sequence of receive and transmit operations is performed. At a certain time in example (b) of FIG. 5, a device hasenough energy to receive and transmit. Assuming no EH is performed after receiving, a device has enough energy to transmit in example (c) of FIG. 5. Assuming no EH is performed after transmitting, a device does not have enough energy to receive in example (d) of FIG. 5.

[0117] FIG. 6 depicts an updated figure assuming that a device can perform energy harvesting for at least the duration of the minimum processing time, where the “harvest” box represents the energy harvesting during at least the minimum processing time (t2, t3) shown in FIG. 4. The device has an opportunity to replenish its energy during energy harvesting. However, the amount of replenishment may be insufficient for further communication in some circumstances, for example in the receive transmit sequence example.

[0118] It is possible to extend the time after receiving PRDCH or transmitting PDRCH. For example, assume the sequence of transmissions and / or receptions at the device is receive PRDCH 1, receive PRDCH 2, transmit PDRCH 1, receive PRDCH 3, and transmit PDRCH 2, as shown in FIG. 7. This may represent a sequence of operations for contention-based access.

[0119] At the start of sequence of transmissions and / or receptions, the device has a certain percentage of energy storage to perform a sequence of receive PRDCH 1, receive PRDCH 2, and transmit PDRCH 1 as shown in example (a) of FIG. 7. A relative percentage PD2R,min is the energy for transmitting PDRCH while a relative percentage PR2D,min is the energy for receiving PRDCH. As discussed herein, the same percentage PR2D,min is used for receiving PRDCH. Each message may use a different energy percentage. When a device has energy exceeding the threshold PD2R,min+ 2*PR2D,min, it can start a sequence of receive PRDCH 1, receive PRDCH 2, and transmit PDRCH 1. However, the reader may be unaware of the device’s energy status. There maybe a requirement (e.g., a threshold) for a minimum energy storage in a device before communications can begin. In some circumstances, the standards specify a minimum requirement of storage (e.g., relative to the peak energy consumption of the device) before any communication sequence can begin. After the device receives PRDCH 1, the device’s energy level drops by PR2D,min. However, the duration ti' between successive PRDCH may allow the device to perform energy harvesting. Time t can be the sum of ti and any additional time a reader allows after the transmission of PRDCH 1. A device may be unaware of this additional time.

[0120] Example (b) of FIG. 7 shows the energy level at the onset of receiving PRDCH 2. The amount of energy harvesting or harvesting efficiency (which is likely not to be specified) may vary according to device capability. In example (c) of FIG. 7, the device harvested some energy during time t2. Regardless of the amount of energy the device harvested, it has enough energy to transmit PDRCH 1. The device may not have enough energy to perform a receive and / or transmit sequence unless t3' is sufficiently long enough in example (d) of FIG. Time t3' can be the sum of t3and any additional time a reader uses after the reception of PDRCH 1. Once the device has enough energy, it can receive PRDCH 3 and then transmit PDRCH 2 as depicted in example (e) of FIG. 7A.

[0121] Additional factors for a reader to consider when scheduling. At the onset of communications to one or many devices, a reader should allow a device to have enough energy to start a round of communications (e.g., ramp up). For example, for devices that support RF energy harvesting, the reader can enable an energy source (e.g., carrier wave (CW) emitter to be on for a sufficient duration of time). This ramp up time (e.g., to) may vary across device types and type of session (e.g., inventory, command, and the like). In one or more circumstances, one or more devices may not have enough energy at the onset of communications even with a reasonable time for ramp-up. For example, in some embodiments, scheduling is based on a message or other transmission type, such that different types of messages, commands, and / or the like are provided additional processing time.

[0122] For an inventory session, a reader may or may not know the types of devices at a start of inventory. The reader may allow a time to for devices to charge to a sufficient level. For a command session, a reader knows the device type and can allow a time to' to let that specific device to charge, where time to' can be based on the specific device’s capabilities.

[0123] While the approach in FIG. 7A can be utilized for a simple device, when multiple devices are involved, enhancements are needed because receiving a PRDCH consumes energy at a device, regardless of whether the device is not the intended destination of the PRDCH. Having transmission information early in the R2D transmission allows a device to minimize its energy consumption. For example, a destination ID may allow a device to stop receiving when the destination ID does not match the device ID, and other IDs may similarly beutilized when early within a received channel and / or transmission. The transmission information may not be sufficient for a device to charge, however. In addition, from a standards perspective, whether a device discontinues receiving a R2D transmission when the device is not the intended destination is usually a device implementation decision. In general, the reader may assume that the device received the transmission and schedule accordingly.

[0124] Ambient loT devices generally have imprecise timing. For example, implementing a discontinuous receive (DRX) procedure in which a device is informed a period of time when not to expect PRDCH can allow a device to charge. Due to timing drift, however, a device may attempt to receive PRDCH too early or too late. When a device monitors a PRDCH too early, it may not have enough energy when its intended PRDCH is transmitted. When the device monitors a PRDCH too late, it may miss receiving its intended PRDCH. In addition, the timing between a reader and multiple devices can be variable. For example, one device may require more time to transmit or process.

[0125] DRX operations are generally time-based; a device is informed when to start monitoring R2D transmissions after some time. However, due to poor timing (e.g., large SFO) and limited support of tracking loops from energy considerations, a device may monitor for R2D transmissions starting from 9 ms up to 11 ms (or another range) when it was scheduled to monitor at 10 ms. One approach is to have a periodic (or quasi-periodic) signal that contains a clock value. A device can monitor the clock value to adjust its timing. In FIG. 7B, a reader commands a device to start DRX for 5 ms as an example. A device starts DRX for 5 ms but due to timing accuracy, the device begins to monitor R2D transmissions 5.3 ms later. One approach is for a reader to transmit a quasi- periodic signal starting at 4.5 ms after issuing the command to start DRX. There are 3 signals (A, B, C) sent by the reader at 4.5, 5, and 5.5 ms, respectively, after the reader issues the command to start DRX. A device can start monitoring R2D transmissions and receive one of the three signals, in this example C. The device can readjust its timing. During the 5.3 ms, a device can perform energy harvesting. One of the drawbacks is that the act of receiving the signals A / B / C consumes energy of the device. Secondly, a reader may not be able to use the time between A and B and between B and C for any other communications.

[0126] An embodiment considers a signaling approach to allow a device to skip processing PRDCH. The skipping may be independent of a clock associated with a device, thus avoiding limitations by timing accuracy of a given device. A PRDCH is generally preceded by a preamble and / or timing indicator. A device can count the number of preamble and / or timing indicator it received but not process the following PRDCH. Although counting is subject to errors, including those resulting from channel impairments (e.g., impairments such as noise and fading can cause a miscount) or the device losing power, counting is advantageous for an asynchronous system. By skipping, in some embodiments, one or more channels, transmissions, and / or the like, such embodiments reduce energy consumption by the device, for example by reducing the speed at which data processing is necessary by the device.

[0127] FIG. 7C shows examples of an R2D transmission that includes a timing acquisition signal and a PRDCH. The depicted R2D transmission provides a generalized frame structure for an example transmission, for example the R2D transmission, including multiple data portions. In some embodiments, data portions may be indicated using a length field, a delimiter, and / or another indication mechanism. The timing acquisition signal can include a start-indicator part and a clock-acquisition part. A timing acquisition signal can be considered a preamble (e.g., a R2D preamble that precedes other R2D information). Both example (a) in FIG. 7C and example (b) in FIG. 7C show that the PRDCH can carry D2R scheduling information. D2R scheduling information can include modulation / coding scheme, transport block size, and / or skip count. Example (b) of FIG. 7C shows that the PRDCH can carry control information about the PRDCH. Control information can indicate whether a PRDCH is a broadcast, multicast, or unicast message, and / or the destination id for the transmission. It should be appreciated that D2R transmissions, as discussed herein, may similarly include data representing a D2R preamble processable in accordance with at least some embodiments of the present disclosure.

[0128] When information about the future transmissions is provided to a device, the device in some circumstances may elect to save energy by not receiving the full transmission. For example, the reader can provide a window (e.g., based on a number of transmissions when a device or a group of devices) isnot expected to receive a transmission. A device can count the number of received transmissions. In the meantime, the device can continue charging.

[0129] If a device received a PRDCH and was scheduled to transmit a PDRCH, the scheduling for the PDRCH can include a count until the next scheduled PRDCH. This count can be based on device capability. In case the reader is unaware of the capability, the reader may schedule the largest value suitable for all devices.

[0130] For inventory, there are several observations. First, a number of devices, possibly with different capabilities, may have all powered on at once. Secondly, a reader is unaware of the number of devices and may be unaware of their capabilities. If all the devices start receiving any PRDCH, some devices may not have enough energy to receive the PRDCH when the PRDCH is intended for such a device. One approach is to partition devices into groups. A group can then be informed when to monitor a PRDCH. For example, assume a device has a unique M bit ID. A group can be based on the N least significant bits (LSBs) of the ID, where M>N. Consider M=q6 and N=3. Eight groups (2N) can be created with a first group (e.g., group o) corresponding to devices whose N LSBs are o. Another approach is a device generates an N-bit random integer (e.g., to represent values between o to 2N-i). Signaling can indicate when that group should expect PRDCH. For instance, an N-bit mask can indicate whether group i, i=o, ..., 2N-I, should wait and / or how much to wait. Alternatively, group i is scheduled for PRDCH (in some embodiments, with a count value), and the other groups use a counter.

[0131] FIG. 7D depicts an example with 80 tags (e.g., devices) to be inventoried. The tags are split and / or otherwise partitioned into 8 groups (e.g., groups o, 1, ..., 7). There can be an unequal number of tags (e.g., devices) in each group. As an example, assuming a device has a number (e.g., its identifier, a random number), the device can belong to a certain group if the number is within a range. For instance, a modulo function applied to the number results in a value between o and 127. If the quotient of the value divided by 16 is k, the device is associated with group k, where k=o, 1 ..., 7.

[0132] FIG. 8A depicts a flowchart at a device to implement skipping of PRDCH at power on. The device may receive a PRDCH indicating the device should form a group. In the same PRDCH or in a different PRDCH, the device canreceive an indicator of the group and a number of PRDCHs to skip. If the indicator indicates that the group skips PRDCH, the device will skip the number of PRDCH as indicated. The flow can resume with receiving another PRDCH. The PRDCH may indicate further skipping for the group. Otherwise, the device can process the PRDCH (or a following PRDCH). Alternatively, if the group of the device is not scheduled to receive any PRDCH within the indicated number of PRDCH, the device can skip receiving the indicated number of PRDCH transmissions.

[0133] FIG. 8B shows an alternate embodiment without using groups. A device receives parameters to begin inventory in X70. After a device receives scheduling parameters in X71, the device can count preambles in X72. The device can examine whether it should receive PRDCH in X73. For example, the scheduling parameters in X71 can include a range (e.g., 0-15). Any device with a number in the range would be expected to receive PRDCH in X75 in the next opportunity, for example a particular window. The scheduling parameters in X71 can include a skip count. Once the count of preambles equals or exceeds the skip count in X74, the device can resume to monitor R2D transmissions for a PRDCH containing scheduling parameters in X71.

[0134] FIG. 8C depicts an example process of how to create multiple levels of groups (xgo) and skip counts. In x8o, a device receives parameters to form a first group. The first group can be the group o, 1, ..., 7 as described before. If the value, as described in FIG. 7D, is a number between o and 127, the first group can be devices with values between 16 and 31. In x82, a device receives scheduling parameters and begins to count preambles in X84. If the first group is scheduled for receiving in x86, the first group receives parameters how to establish a second group in X91. In one example, the second group is for a device whose remainder for the value divided by 16 is 9. After the device receives scheduling parameters within the group in X92, the device can count preambles in X93. The device checks in X94 to see if the second group is scheduled to receive PRDCH in xg6. The same approach may also be utilized to processing without using groups. In some embodiments, the skip count can be used to indicate when a device should receive a PRDCH. If the device is not among the first group scheduled to receive in x86, the device examines to see whether the skip count is reached in x88.

[0135] For ambient loT devices, channel coding (e.g., forward error correction) may not be used. It is possible that a device is unable to receive a PRDCH correctly. It is also possible that a device misses a PRDCH due to not having enough energy. It is also possible that a device erroneously counts preambles. FIG. 8D shows an example of a process utilized to improve reliability. A reader transmits scheduling parameter i message (e.g., x02, X04, xo6) three times. The skip count allows a device to skip PRDCH until the second of the three scheduling parameter 2 X24 messages. While a device is counting preambles, it may miss one preamble or mistakenly count an extra preamble. By indexing to the second of the three messages (e.g., X24), such embodiments allow for an error in one preamble count. In this example, the first scheduling parameter 1 message xo2 has a skip count of 21, the second scheduling parameter 1 message X04 has a skip count of 20, and the third scheduling parameter 1 message xo6 has a skip count of 19. If a device determines it is to receive (e.g., process) first group xio, there maybe an alternate skip count to let a device skip until it receives scheduling parameter A message xi2. Again, there can be three scheduling parameter A messages (e.g., xii, xi2, X13). The scheduling parameter A message (e.g., xi2) can indicate the skip count for the PRDCH message o (e.g., X14) to N-i (e.g., X15).

[0136] This example uses linearly increasing ordering, but in other embodiments the ordering can be linearly decreasing, an even numbered ordering, or an odd numbered ordering. If a device received scheduling parameter A message xi2 and is expected to receive PRDCH message o (xi4), it may get a skip count of 1. As an example, if a device is expected to receive PRDCH message n (where o < n < N), the skip count can be n+i for when the device receives scheduling parameter A message xi2. FIG. 8D allows including a catchall PRDCH message xi6. A device may be informed when catchall PRDCH message xi6 is to be transmitted (e.g., using a skip count). The catchall PRDCH can allow a device to start inventory in case it missed an opportunity to receive its scheduled PRDCH message (e.g., X14 to XI5). The process PRDCH o message (X14) may include a skip count to the scheduling parameter 2 message X24.

[0137] Instead of providing a count (e.g., a skip) value to scheduling parameter 2 message X24, scheduling parameter 1 messages xo2, X04, and xo6can provide a count (e.g., skip) value for the message xi6. This approach can be used to handle one or more mistakes of preamble detection.

[0138] FIG. 8D also depicts two examples of the ordering of multiple windows X30 and X50. In the first example, there are n groups (or partitions), with one or more scheduling parameters messages (e.g., X32, X36, X40, and X44) before each window (e.g., X34, X38, andx42). The catchall scheduling parameter message (X40) and catchall window (X42) can be for devices which were not serviced in windows X34, X38. Scheduling parameter message X44 can be for a second round of messages, or to service more devices. A different window ordering is presented in X50. The catchall scheduling parameter message (X52) and catchall window (X54) are first followed by the scheduling parameter message 1 (X56), window 1 X58 up to scheduling parameter message n (x6o), window n x62. Scheduling parameter message X64 can be for another round of messages, or to service more devices.

[0139] In at least one embodiment, a device receives a first delay (e.g., a skip count) value where only preamble counting is expected. After the device counts the first delay value of preambles, the device is expected to perform reception and decoding of R2D transmissions. In some embodiments, a device can start performing reception and decoding of R2D transmissions before the count reaches the first delay value. There may be a window of the R2D transmissions (e.g., X32 in FIG. 8D). A window can be defined as a number of preambles that a device can perform reception and decoding of R2D transmissions. Within that window and after that window, the counts (e.g., skips) are already defined. The reception of the scheduling parameters (X32) is similar to an initial broadcast group. Time can be given to perform an initial charging before that and (if needed) after it before the first dedicated window (X34). Windows (X34, X38, and / or X42) need not be the same size. There can be special windows, in some embodiments, such as a catchall window (e.g. X42, X54) (which could be last X42, or first X54, for example). The first window after the initial scheduling message could also be used for devices / tags that may not have enough energy if they wait, for example. With these partitioning mechanisms (including the possible around group / delay), it maybe assumed that within a window the tag and / or device will have enough energy.

[0140] In at least one embodiment, a PRDCH can indicate when the next PRDCH containing the indicator for group skipping is to be sent. Utilizing such implementations, embodiments of the present disclosure may provide a fallback mechanism is if a device loses count.

[0141] FIG. 9 depicts a flowchart for skipping after a device transmits a PDRCH. A device receives a PRDCH, which can indicate a skip value. The flowchart includes a transmit PDRCH step, which may be optional in some embodiments. After the device transmits, it skips the indicated number of PRDCHs before it can resume receiving PRDCH. FIG. 10 depicts an example of how groups can perform skipping.

[0142] As depicted, the skipping is a form of pipelining, as shown in FIG. 11. It is possible that the reader informs a device of a number of PRDCH (e.g., n-i) to skip as part of the scheduling information for the PDRCH. From a reader perspective, there are n parallel communication sessions, one for each of the N devices.

[0143] From a standards perspective, a simple scheduling is desirable to support a variety of device capabilities. The number of transmissions to skip can be in the range o to M-i. If a reader knows a charging rate capability (of a device, the reader can select the number of transmissions to skip based on the charging rate. If a reader is unaware of the device capability, in some embodiments it utilizes M-i.

[0144] In some embodiments, the amount to skip corresponds to a time value or skip time value. Determining the amount to skip can be conservative in some embodiments, for example it can be larger than the energy harvesting time. Balancing the amount to skip may be considered, as there may be one or more drawbacks to being conservative. First, the reader does not know the device energy state. It is possible that a device is fully charged before the end of skipping. In such a case, a device is not precluded from monitoring the PRDCH. Second, the amount of time to charge can be very long, and unreasonable for a scenario and / or use case. A device can still operate even if it is not fully charged. In such a case, the amount to skip can be much shorter than the worst-case time. Third, when two devices are scheduled to skip at the same time, the amount to skip may be too large for one device and / or too small for the other device. It is possible to set the amount to skip based on the larger or smaller time of the devices.

[0145] The amount, or maximum amount, of PRDCHs (or time interval) to skip is indicated to the device(s) to allow the device(s) to skip, but the device(s) can start receiving / transmitting once it is sufficiently charged. Such implementations can avoid unnecessary long delay for devices and spread out the transmissions from the devices in time. These implementations also ease the burden for the reader to have knowledge of the UE capability (e.g., a charging capability) and actual charging rate, which depends on many factors.

[0146] For a harmonized design of multiple device types, a scheduling scheme may support one or more of the following:

[0147] For the R2D link, at least one or more of: multiple modulations, different device capabilities, and / or different cast types. For the D2R link, at least one or more of: scheduling information (e.g., modulation, transmission length, coding), and / or different device capabilities. It should be appreciated that another scheduling scheme may support one or more additional and / or alternative features. Embodiments with a harmonized design of multiple device types further ensure that energy consumption does not exceed the limits for the device types and its other limitations (e.g., timing accuracy).

[0148] The two power classes of devices have different capabilities in terms of processing, and a goal of the embodiments is to have a harmonized physical layer design. For ambient loT devices, the low power device may be able to support one modulation (e.g., waveform format 1). An example can be on-off keying (OOK), or OOKi, as shown in example (a) of FIG. 12. OOKi may be able to convey one bit per symbol. The FIG. 12 also includes a preamble (Prei), which can mark the beginning of a transmission and can provide timing information. With waveform format 1, PRDCH 1 has a duration of ti and occupies a bandwidth of bwi. Prei also uses waveform format 1.

[0149] A high-power device may be able to support waveform format 1 as well as a second modulation (e.g., waveform format 2), such as OOK4 where multiple bits may be conveyed per symbol. Example (b) of FIG. 12 also shows a preamble (Pre2), which can mark the beginning of a transmission and can provide timing information. With waveform format 2, PRDCH B has a duration of ta and occupies a bandwidth of bwa. Pre2 also uses waveform format 2. For the same sized payload, the duration of PRDCH 2 may be shorter than the duration of PRDCH 1. One drawback of an approach shown in FIG. 12 is that a high-powerdevice may have to perform hypothesis testing (e.g., blind testing) on the preamble to determine whether waveform format 1 or waveform format 2 was received. If additional waveform formats are introduced, additional hypothesis testing may be necessary. Another drawback of having two different preambles is that it leads away from a harmonized design. It is possible that a low power device is unable to process waveform format 2. For instance, when it receives Pre2, a low power device may waste energy attempting to process the received transmission. A third drawback is there may be a limited number of preambles with desirable qualities. A possible issue with the approach is that a HP device may have to perform blind detection to determine whether waveform format 1 or waveform format was used during transmission.

[0150] FIG. 13 depicts a general example of the contents of the PRDCH. The example can be applied to the PDRCH. In example (a) of FIG. 13, a reader may have data 1 to data n to transmit to a device. Each data k, k=i, ... , n can be for example, a command, information, control, configuration, or link control. In example (b) of FIG. 13, each data k, k=i, ..., n can be processed at the MAC layer. Each data can be prepended by a MAC header. Additional fields can be included by the MAC. In example (c) of FIG. 13, all the MAC headers and data can be concatenated (aggregated / multiplexed) to create a payload. In example (d) of FIG. 13, an information field (e.g., Info 1) can be multiplexed with the payload. Although the figure shows the information field preceding the payload, the information field can follow the payload. In example (e) of FIG. 16, a cyclic redundancy check (CRC) code is computed and appended to Info 1 + Payload fields. In example (f) of FIG. 13, if channel coding is supported, the fields Info 1 + Payload + CRC are encoded. Examples of channel codes can include, but not limited to, repetition, BCH codes, Reed-Mueller codes, convolutional codes. In example (g) of FIG. 16, another information field (Info 2) is multiplexed. In this step, in some embodiments the CRC does not cover Info 2. In example (h) of FIG. 16, the contents of the previous step are provided to the PRDCH before transmission. In other embodiments, one or more steps may not be included. For example, there may be no channel coding in step g. The channel coding can be viewed as a pass through (no coding applied).

[0151] One issue facing ambient loT devices is limited available energy. For example, receiving a transmission when the device is not an intended destinationof the transmission consumes energy when limited energy is available. Having a protocol and / or signaling (e.g., at the physical layer and / or MAC layer) enables a device to stop receiving has benefits for device energy. The protocol and / or signal can include:

[0152] Device capability [2 bits]: ‘00’ can indicate basic device capability and / or all devices: this has a benefit for a harmonized design, ‘01’ can indicate devices with an additional set of capabilities, To’ can indicate devices with a further set of capabilities, and TT can be reserved. If ‘11’ is set, it may indicate an additional device type field is used.

[0153] In some embodiments, devices a higher capability can support other features not available for less capable devices.

[0154] In other embodiments, a device capability is 1 bit, where ‘o’ can indicate all devices, T indicates additional device capabilities. Then there can be several bits for the additional device types. For example, a casting [2 bits] may represent the following: ‘00’ can indicate broadcast, ‘01’ can multicast, To’ can indicate unicast, and ‘11’ reserved

[0155] For the following, it is assumed that an ID is 16 bits. In other embodiments, the ID can be longer or shorter. Alternatively, it can be considered as the RNTI (radio network temporary identifier). In some embodiments, an example ID [fixed or variable] includes:

[0156] A Broadcast id: A known pattern, such as ‘0000 0000 00000000’, could be used. If the transmission is broadcast. Sending no bits can reduce the length of the transmission (and system overhead).

[0157] A Group ID: Can be 16 bit id or a smaller set (e.g., 4 most significant bits of the device id). Alternatively, a Group ID can be an n-bit number independent of the device ID.

[0158] A Device ID: A unique number assigned to the device by the network associated with the reader. If a device moves to different reader, it may be possible a new device ID is provided.

[0159] In some embodiments, a field for skipping can be included.

[0160] Other fields can include a modulation type, for example if the PRDCH can have a different modulation compared to the prefix. For example, a modulation type (fixed assuming 2 bits as an example, or a variable number of bits): o bits if device capability is ‘00’, or 2 bits if device capability is not ‘00’. Themodulation type can be ‘oo’ for a default modulation (e.g., OOKi), ‘of for e.g., OOK4 with m bits), and the like. In some embodiments, ‘11’ can be reserved

[0161] Another field may include channel coding. The channel coding may include one or more other information. For example, channel coding may include a channel type (fixed assuming 2 bits for example, or a variable number of bits). Example channel types identifiers may include o bits if the device capability is ‘00’, or 2 bits if device capability is not ‘00’. The channel type can be ‘00’ for no coding, ‘01’ repetition coding as an example, To’ for convolutional coding as an example. In some embodiments, Ti’ can be reserved.

[0162] Additionally or alternatively, channel coding may include a channel rate (fixed assuming 2 bits for example, or variable number of bits). An example channel coding may include o bits if device capability is ‘00’, or 2 bits if device capability is not ‘00’. Some examples include, when channel type is ‘01’ or To’, an identifier can be ‘00’ for rate 1 / 2, ‘01’ for rate 1 / 3, To’ for rate IT. In some embodiments, Ti’ can be reserved.

[0163] Another field can be length (in bits or symbols or payload size or payload size with CRC). In some embodiments, length is related to modulation type and channel coding. If there is an end of transmission delimiter, the length field may not be present. Assuming the maximum payload is N bits, e.g., N=iooo. In such a case, [log2Al bits may be used to represent the size. For example. 10 bits are used for N=iooo. It may be possible to reduce the number of bits to indicate the size. For example, if there are fewer than T bits, then [log2T] are used to indicate the size, otherwise in some embodiments [log2N / Q] represents the size in multiples of Q. For example, let T = 64. In some such implementations, 6 bits can represent the size for 63 or fewer bits. Between 64 and 1000, if Q=8 and N=iooo, then, seven bits can represent lengths of 64, 72, 80, ..., and 1016. In other embodiments, more efficient representations maybe utilized to convey the length using fewer bits.

[0164] One or more other fields may be considered for control. FIG. 14 depicts an example possible layout of the fields used to specify transmissions (Tx Info). Example (a) of FIG. 14 depicts an example with the seven fields described above. Example (b) of FIG. 14 depicts possible fields for a broadcast to all devices, assuming the broadcast size is known and / or specified.

[0165] There can be several ways to convey the transmission information in the R2D link in various embodiments. Example (a) of FIG. 15 can represent no transmission (tx) information sent or the tx information is within the payload. The PRDCH may include a CRC over the data (e.g., a baseline). If the tx information is in the payload (for example as a MAC field), a device may have to parse the payload in order to find if tx information is transmitted. Example (b) of FIG. 15 can represent tx information sent within PRDCH. The tx information can precede the payload (as shown) or can follow the payload. When tx information precedes the payload, a device can process the tx information to determine whether to process the payload (e.g., a possible energy savings). A CRC may cover both the transmission information and payload. Example (c) of FIG. 15 can represent tx information sent before the PRDCH, for example as a header that precedes the PRDCH. One benefit is the device process the tx information before processing the payload. For example, in example (a) of FIG. 16, if the tx information does not indicate a change in modulation, the PRDCH is received with the same modulation as the tx information. In example (b) with FIG. 16, if the tx information does indicate a change in modulation, the PRDCH is received with a different modulation from the tx header. In some embodiments, a device with additional capabilities supports a different modulation.

[0166] In example (d) of FIG. 15, the tx information is divided into two parts, tx info B, which precedes the PRDCH, and tx info A, which is within the PRDCH. In example (e) of FIG. 15, a control channel precedes the PRDCH. The control channel can have the tx information, which has a CRC for integrity detection. Example (f) of FIG. 15 is similar to example (e) of FIG. 15 except that the tx information is divided into two parts, tx info B, which is located within the control channel, and tx info A, which is within the PRDCH.

[0167] The physical layer may provide different types of transmission information. For example, in NR, a first sidelink control information (SCI) may include fields for link management, MCS / TBS for the PSSCH, resource reservation as well as an indicator of the format for the second SCI, for example. The second SCI may include fields for the cast type, destination ID, source ID, and HARQ management. The first SCI in some embodiments has its own channel while the second SCI is part of the PSSCH.

[0168] Different transmission information locations may provide different advantages and disadvantages, for example:Table 3. Advantages and Disadvantages of Transmission InformationLocations

[0169] Device complexity may be a primary consideration for location of transmission information. For low device complexity, no support of ARQ / HARQ maybe provided. The reliability of control information (i.e., control information) is not expected to be higher than the data. Thus, having a dedicated channel, as depicted in example (d) in FIG. 15, may provide only a small benefit.

[0170] In example (b) of FIG. 15, since a CRC covers the payload, the integrity of the payload, which includes the commands and application information, is ensured. If the device type or cast type is incorrectly received, the intended device may stop receive the payload, or may receive the payload but fail the packet integrity check. If a length field is included and if any bits are in error, the number of bits processed by the CRC will be incorrect, resulting in an incorrect CRC calculation. Thus, a CRC over the tx info field may not be needed.

[0171] For improved energy conservation and in view of the considerations above, transmission information may be added within the PRDCH and before the PRDCH in accordance with example (e) of FIG. 15.

[0172] In some embodiments, D2R control information, if present, may be presented in accordance with one or more of the examples depicted and described with respect to FIG. 15. For example, in some embodiments, a PDRCH is structured in accordance with the structure in example (a) of FIG. 15. In other embodiments, a PDRCH is structured in accordance with examples (b), (c), or (d) in FIG. 15, with the payload information representing D2R control information specifically. In some circumstances, however, D2R control information may not be needed.SCHEDULING D2R

[0173] In some embodiments, a PDRCH is generated in response to a PRDCH. This is unlike NR where the uplink traffic can be generated autonomously from the downlink traffic. A control channel (e.g., a physical downlink control channel,or PDCCH) is used to schedule uplink transmissions at a future time after the control channel was received. Alternatively, with configured grants, uplink transmissions occur at scheduled times.

[0174] For an ambient loT system, the devices in some circumstances operate asynchronous to the reader timing. A device obtains timing after receiving the PRDCH. The device can use that timing for subsequent operations. However, the device may lack a tracking loop to keep accurate timing due to factors such as energy. As such, the timing of the device drifts with respect to the reader’s timing. One consequence is the D2R transmissions based on periodic timing or scheduled timing is not expected. Assuming that PDRCH is generated in response to a PRDCH, the PRDCH transmission should provide D2R scheduling information.

[0175] The scheduling information that is conveyed may include one or more of the following modulation types. If the device can support several modulation formats, the PDRCH can have a different modulation:

[0176] Modulation type (fixed assuming 2 bits or variable number of bits), for example o bits if device capability is ‘00’, 2 bits if device capability is not ‘00’. Can be ‘00’ for default modulation (e.g., BPSK), ‘01’ for e.g. OOK4 with m bits). ‘11’ can be reserved

[0177] Small frequency shift (fixed assuming 2 bits or variable number of bits), ‘00’ for no offset, ‘01’ for offset 1 (e.g., for Miller coding), ‘10’ for offset 2 (e.g., for Miller coding), and / or ‘11’ for reserved.

[0178] Large frequency shift (assuming a device supports large frequency shift), for example in some embodiments 1 bit: D2R frequency higher than R2D frequency, and / or N bits: amount of offset, in units of MHz, RBs, and / or the like.

[0179] Power level, for example ‘00’: max, ‘01’: 3 dB less than max, and / or ’10’: 6 dB less than max.

[0180] Another field can be channel coding, in some embodiments. For example, other fields may include one or more of:

[0181] Channel coding type (fixed assuming 2 bits or variable number of bits), for example o bits if device capability is ‘00’, and / or 2 bits if device capability is not ‘00’. In some embodiments, the channel coding type can be ‘00’ for no coding, ‘01’ for example repetition coding, To’ for convolutional coding for example, and ‘11’ can be reserved.

[0182] Channel coding rate (fixed assuming 2 bits or variable number of bits), for example o bits if device capability is ‘oo’, 2 bits if device capability is not ‘00’. One example is when channel coding type is ‘01’ or ‘10’, the channel coding rate can be ‘00’ for rate 1 / 2, ‘01’ for rate 1 / 3, ‘10’ for rate 1 / 4, and ‘11’ can be reserved.

[0183] Another field can be the length (in bits, symbols, payload size, payload size with CRC) and can be similar to the length field for PRDCH. Another field can be timing delay, for example an additive term to time t2, for example where N bits represent a time adjustment (e.g., index to a table or multiples of time unit (e.g., too microseconds)). Another field can be skipping, for example where N bits represent a number of transmissions of PRDCH to skip.

[0184] The scheduling information for the PDRCH should be integrity protected in the PRDCH to ensure if no errors are present in the scheduling information. There maybe several ways to provide the scheduling information. One example is a MAC CE, as shown in examples of FIG. 13). The MAC can provide a container of M bits. The fields from above can be used to specify the contents of the container. Note that this slightly different than the NR MAC CE providing Msg3 scheduling in that this MAC CE is used for most PDRCH transmissions while the MAC CE providing Msg3 scheduling also provides contention access information.

[0185] Alternatively, the scheduling information can be provided as part of the info 1 field in example (d) of FIG. 13. The info 1 field can be split to precede the MAC CE and follow the MAC CE(s) in example (d) of FIG. 13.ALTERNATIVE WAVEFORM FORMAT IMPLEMENTATIONS

[0186] To support for waveform format 2 and other capabilities for HP devices, a header field for tx information maybe introduced in some embodiments. There are values / flags that both LP and HP devices can understand.

[0187] Examples (a), (b), (c), and (d) of FIG. 16 depict a first embodiment, where a preamble and header (e.g., containing the tx information) precede the payload modulated by waveform format 1 (PRDCH A). In example (a) of FIG. 16, the header is modulated according to waveform format 1. Waveform format 1 has a bandwidth bwi. In some embodiments, the waveform format used for the preamble has the same bandwidth as waveform format 1. In some embodiments,the waveform format used for the preamble may be different from waveform format 1.

[0188] In example (b) of FIG. 16, the header is modulated according to waveform format 1. PRDCH B is modulated with waveform format 2. In this example, the duration of the header and preamble is the same as example (a) in FIG. 16. Example (c) in FIG. 16 is similar to example (b) in FIG. 16, except that support for an error correction (EC) code is included. Some examples of codes include, but are not limited to, systematic codes such as binary BCH codes (e.g., Hamming codes). Such codes generally have low implementation complexity. The systematic portion can include the payload and CRC. Example (d) in FIG. 16 is similar to example (a) in FIG. 16, however support for an error correction (EC) code is included.

[0189] Table 3 shows an example of the mapping of the fields.Table 3

[0190] FIG. 17 depicts the operation at a base station and / or intermediate node in accordance with at least one embodiment of the present disclosure. For example, the operation is for transmission in accordance with embodiments of the present disclosure. The flowchart includes receiving (e.g., obtaining) a payload transmission from, for example, higher layers. The flowchart furtherincludes determining a transmission format based on capabilities, operating mode, and / or the like. The flowchart further includes using a first waveform format for a header. The flowchart further includes determining whether the header indicates using a second waveform. In a circumstance where the operation determines that the header does indicate using a second waveform, the flowchart further includes using the second waveform format for the payload. In a circumstance where the operation determines that the header does not indicate using a second waveform, the flowchart further includes using a first waveform format for the payload. The flowchart further includes ending transmission.

[0191] FIG. 18 depicts the operation at an ambient loT device in accordance with at least one embodiment of the present disclosure. For example, the operation is for processing a payload in accordance with at least one embodiment of the present disclosure. The flowchart includes receiving a preamble. The flowchart further includes receiving a header while processing a received signal with a first waveform format. The flowchart further includes determining whether the header indicates using a second waveform. In a circumstance where the operation determines that the header does indicate using a second waveform, the flowchart further includes receiving the payload while processing the received signal with the second waveform format. In a circumstance where the operation determines that the header does not indicate that the header does not include a second waveform, the flowchart includes receiving the payload while processing the received signal with the first waveform format. The flowchart further includes processing the payload.

[0192] In some other example embodiments, the size of the header is fixed. In another example, a single header bit can indicate whether additional bits are present in the header. FIG. 19 shows one such example. If the first header bit ho is ‘o’, then there are no other header bits following the first header bit (example (a) of FIG. 19)). If the first header bit ho is T, then there are header bits following the first header bit (example (b) of FIG. 19 and example (c) of FIG. 19)). If the second and third header bits (hi, h2) have certain values, then there are additional header bits, as shown in example (c) of FIG. 19).

[0193] The following table shows an example of a coding scheme, “n / a” indicates the particular header bit is not transmitted.Table 4. possible header fields

[0194] In another embodiment, the transmission can include simple error detection scheme on header. For example, even / odd parity can be used. The following example assumes three bits (ho, hi, hz) are the bits in the header, and p is the parity sum.

[0195] With even parity, the exclusive-or (XOR) sum of the header bits can be the parity bit. If there are 3 bits in the header, the exclusive-or sum of ‘o’, T, and ‘1’ is ‘o’; resulting in the parity bit p value of ‘o’. The exclusive-or sum of ‘o’, T’, and ‘o’ is T; resulting in the parity bit p value of T’.

[0196] With odd parity, the parity bit is the logical complement of the exclusive-or sum of the header bits. If there are 3 bits in the header, the exclusive- or sum of ‘o’, T, and T is ‘o’; resulting in the parity bit p value of ‘1’. The exclusive-or sum of ‘o’, T, and ‘o’ is T; resulting in the parity bit p value of ‘o’.

[0197] An ambient loT device can assume the header is in error if the exclusive-or sum of the header bits and parity bit is not ‘o’ for even parity or T for odd parity. While the error detection of even / odd parity is weak, because there is no error correction on the link, the link must be error free for successful packettransmission. The ambient loT device can then disregard the processing the packet.

[0198] In some embodiments, it may not be necessary to employ error detection on the header. For example, it may not be necessary to employ error detection on the header if the error detection on the packet is reliable.

[0199] In another embodiment, there may be additional fields after the header. In one example, a length field or multiple length fields may follow the header. One possible benefit is a receiver can determine the size of the PRDCH before receiving the PRDCH. As shown in FIG. 13, there can be a MAC protocol encapsulating the ambient loT command. The protocol can include a MAC header, where one field is a MAC length. That MAC length can be related to the payload length. While an ambient loT device knows howto process the MAC protocol, some embodiments benefit from an implementation perspective of the receiver to limit its knowledge of the MAC protocol, for example where the receiver knows the size of the PRDCH before receiving the PRDCH.

[0200] FIG. 20 depicts various possible schemes with / without a header and with / without a length field. Example (a) in FIG. 20 has neither a header field nor a length field. The transmitter (e.g., base station) transmits a preamble followed by the PRDCH. The ambient loT device determines the number of bits in the PRDCH by examining the MAC protocol. In example (b) of FIG. 20 there is a header preceding the PRDCH. In some embodiments, the header can indicate short and long length payload. The ambient loT device determines the number of bits in the PRDCH by examining the MAC protocol. In example (c) of FIG. 20 there is a length field preceding the PRDCH. There is no header field. The length field can indicate the PRDCH length in bytes, number of 16-bit words, number of bits, number of symbols. For example, if the number of bits per modulation symbol is s and the length field indicates the number of modulation symbols is I, the number of bits is the PRDCH is s*Z. In another example, if the minimum size of the MAC header is m bits and CRC is c bits, the length field can be l*s - m / s - c / s.

[0201] In another embodiment, assume that the size of the PRDCH is fixed, example q symbols or bits. If the size of a payload exceeds the size of the PRDCH, then one or more additional PRDCH are used. Example (a) of FIG. 21 depicts the process when one PRDCH is used. The MAC may ensure that padding is added sothat the length of the payload fits into exactly one PRDCH. Example (b) of FIG. 21 shows the process when three PRDCH are used. The MAC may ensure that padding is added so that the length of the payload fits into exactly three PRDCH. Some such embodiments may be similar to NR where PRDCH is transmitted over several physical resource blocks (PRBs).

[0202] In some embodiment, example (a) of FIG. 22 depicts that a length field indicates the number of PRDCH that follows. For example, if the length field is o, then one PRDCH follows. If the length field is 2, then three PRDCH follow. Example (b) of FIG. 22 depicts a continuation field k that precedes a PRDCH k, k=l, ..., n. For example, if the continuation field k is one bit, which can indicate whether another continuation + PRDCH (continuation k+1 and PRDCH k+1) follows PRDCH k. Assume the continuation field is represented by x and xbar (logical complement), x can be either “o” or “1”, while xbar is “1” or “o”, respectively. In this example when continuation field k is x, then the PRDCH k, continuation k+1 field, and PRDCH k+1 follow. If continuation field k is xbar, then only PRDCH k+1 follows. Example (c) of FIG. 22 extends the concept for a midamble n. In this example when continuation field k is x, then the PRDCH k, midamble k+1, continuation k+1 field, and PRDCH k+1 follow. If continuation field k is xbar, then only PRDCH k+i follows. The midamble can be the same signal as the preamble. It can also be different. This provides a receiver the opportunity to re-synchronize the timing. In some embodiments, all midambles are the same or each can be different.

[0203] Example (a) of FIG. 23 shows a possible flowchart for receiving a continuation field (referring to examples (b) and / or (c) of FIG. 22) while example (b) of FIG. 23 shows a possible flowchart for transmitting a continuation field.

[0204] As depicted in example (a) of FIG. 23, a process in some embodiments includes receiving a field after a preamble. The process further includes receiving a current field. The process further includes storing a current PRDCH. The process further includes determining whether an additional field follows the current PRDCH. The process further includes determining whether a current field indicates additional field follows the current PRDCH. In a circumstance where the current field indicates that the additional field does follow the current PRDCH, the flow returns to receiving the current field. In a circumstance where the current field indicates that the additional field does not follow the currentPRDCH, the flow proceeds to processing the PRDCH. As depicted in example (b) of FIG. 23, a process in some embodiments includes determining a number of PRDCH n, k=i. The process further includes transmitting a preamble. The process further includes setting a field k to indicate a field k+i will be transmitted k=l, ... n. The process further includes transmitting field k and PRDCH k. The process further includes determining if k is less than N. In a circumstance where k is less than N, the flow returns to setting a field k to indicate a field k+i will be transmitted k=i, ... n. In a circumstance where k is not less than N, the flow proceeds to ending transmission.

[0205] FIG. 24 illustrates a flowchart depicting example operations of a method in accordance with at least one embodiment of the present disclosure. Specifically, FIG. 24 depicts a process 2400 including operations for skipping transmissions by a device in accordance with at least one embodiment of the present disclosure. The example process maybe performed by one or more device(s) in accordance with embodiments of the present disclosure, for example a wireless device, tag, terminal, or the like, as depicted and described herein. Optional steps may be depicted in broken (e.g., dashed) lines. The device(s) may include computer-readable code or instructions executing on one or more processors of the device(s). Coding of the software for carrying out or performing the process 2400 is well within the scope of a person of ordinary skill in the art having regard to the present disclosure. The process 2400 may include additional or fewer operations than those shown and described and may be carried out or performed in a different order. Computer-readable code or instructions of the software executable by the one or more processors may be stored on a non- transitory computer-readable medium, such as for example, the memory of the device(s). In some embodiments, the process 2400 maybe performed by one or more of units or modules (e.g., an integrated circuit) of the device(s), such as field programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs).

[0206] The process 2400 includes a step 2402 of receiving, by a device, a first transmission including scheduling information. The scheduling information indicates a number of received transmissions for a group of devices.

[0207] In some embodiments, the first transmission further includes an indicator indicating the group of devices for the device. The number oftransmissions may indicate the number of transmissions that a device within the group of devices is expected to monitor. The device may not be the device within the group of devices to skip.

[0208] In some embodiments, the indicator is based on a relationship with a skip time value. For example, the relationship may define a number of transmissions to be skipped by a device (or device group) that is sufficient to satisfy the amount of time indicated by the skip time value. Additionally or alternatively, in some embodiments, the skip time value exceeds or is smaller than a time value that is based on one or more capabilities of the device. Additionally or alternatively still, in some embodiments the skip time value or a second time value related to the one or more capabilities is based on a second device in the skip group.

[0209] The process 2400 further includes a step 2404 of skipping, by the device, reception of a transmission for the number of transmissions. In this regard, the step 2404 skips reception of transmissions for the number of transmissions, in total. To skip a transmission, a device may process only a portion of the received data of the transmission. In some embodiments, the device counts a number of received preambles, and skips the remaining information in a received transmission. The device may enter a state in which the device is configured for the counting of each preamble of each received transmission and the skipping of the processing of the non-preamble portion of each received transmission.

[0210] Additionally or alternatively, in some embodiments, the device may, during the skipping of the processing of the non-preamble portion of each received transmission, perform energy harvesting. In this regard, the device may perform the energy harvesting based on the remaining data portions of a transmission.

[0211] The process 2400 further includes a step 2406 of receiving, by the device, a second transmission after skipping the number of received transmissions. In some embodiments, the second transmission is processed in full. In other embodiments, the second transmission configures the device to skip one or more additional transmissions for a second number of transmissions.

[0212] FIG. 25 illustrates a flowchart depicting additional example operations of a method in accordance with some embodiments of the present disclosure.Specifically, FIG. 25 depicts a process 2500 including operations for skipping transmission by a device group. The example process may be performed by one or more device(s) in accordance with embodiments of the present disclosure, for example a wireless device, tag, terminal, or the like, as depicted and described herein. Optional steps may be depicted in broken (e.g., dashed) lines. The device(s) may include computer-readable code or instructions executing on one or more processors of the device(s). Coding of the software for carrying out or performing the process 2500 is well within the scope of a person of ordinary skill in the art having regard to the present disclosure. The process 2500 may include additional or fewer operations than those shown and described and may be carried out or performed in a different order. Computer-readable code or instructions of the software executable by the one or more processors may be stored on a non-transitory computer-readable medium, such as for example, the memory of the device(s). In some embodiments, the process 2500 may be performed by one or more of units or modules (e.g., an integrated circuit) of the device(s), such as field programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs).

[0213] The process 2500 includes a step 2502 of receiving, by a device, a first transmission comprising an indicator. The indicator indicates a skip group and a number of transmissions for members of the skip group to skip. The device may be associated with one or more skip groups, for example based on an identifier of the device, and / or the like.

[0214] The process 2500 further includes a step 2504 of skipping, by the device, reception of a transmission for the number of transmissions. In this regard, the number of transmissions is indicated as expected to be monitored by the device, or a device within a group of devices (e.g., a skip group). In some embodiments, the device skips transmissions for the number of transmissions in a circumstance where the device is a member of the skip group. In a circumstance where the device is not a member of the skip group, the device may not skip processing data portions of the received transmissions. In response to the indicator indicating the number of transmissions as expected to be monitored by a device within the group of devices, a particular device that is within the group of devices may continue to skip a transmission as transmissions are received until the number of transmissions is reached (e.g., skipping reception of a transmissionfor the number of transmissions). A device that is not within the group of devices may not skip reception of a transmission, or otherwise may ignore the indicator.

[0215] The process 2500 further includes a step 2506 of receiving, by the device, a second transmission after skipping the number of transmissions in accordance with the indicator of the skip group and whether the device is a member of the skip group. In some embodiments, the second transmission is processed in full. In other embodiments, the second transmission configures the device to skip one or more additional transmissions, for example based on a skip group, or return to processing one or more additional transmissions.

[0216] FIG. 26 illustrates a flowchart depicting additional example operations of a method in accordance with some embodiments of the present disclosure. Specifically, FIG. 26 depicts a process 2600 including operations for transmitting data for skipping by a device or device group The example process may be performed by one or more device(s) in accordance with embodiments of the present disclosure, for example a wireless device, reader, core network device, intermediary network device, , or the like, as depicted and described herein. Optional steps may be depicted in broken (e.g., dashed) lines. The device(s) may include computer-readable code or instructions executing on one or more processors of the device(s). Coding of the software for carrying out or performing the process 2600 is well within the scope of a person of ordinary skill in the art having regard to the present disclosure. The process 2600 may include additional or fewer operations than those shown and described and may be carried out or performed in a different order. Computer-readable code or instructions of the software executable by the one or more processors may be stored on a non- transitory computer-readable medium, such as for example, the memory of the device(s). In some embodiments, the process 2600 maybe performed by one or more of units or modules (e.g., an integrated circuit) of the device(s), such as field programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs).

[0217] The process 2600 includes a step 2602 of transmitting, by a reader, a first transmission comprising an indicator indicating a number of transmissions to skip. In this regard, the number of transmissions is indicated as expected to be monitored by the device, or a device within a group of devices (e.g., a skip group). In some embodiments, the indicator indicates a number of transmissions for aparticular device to skip. In some embodiments, the indicator indicates a number of transmissions for a skip group (e.g., representing a group of devices) to skip. For example, in some embodiments, the first transmission includes an indicator associated with a device or a skip group. In response to the indicator indicating the number of transmissions as expected to be monitored by a device within the group of devices, a particular device that is within the group of devices may continue to skip a transmission as transmissions are received until the number of transmissions is reached (e.g., skipping reception of a transmission for the number of transmissions). A device that is not within the group of devices may not skip reception of a transmission, or otherwise may ignore the indicator.

[0218] In some embodiments, the indicator is based on a relationship with a skip time value. Additionally or alternatively, in some embodiments, the skip time value exceeds or is smaller than a time value that is based on a capability related to a device. Additionally or alternatively still, in some embodiments a second time value is based on a second device of the skip group.

[0219] The process 2600 further includes a step 2604 of transmitting, by the reader, a second transmission after skipping the number of received transmissions in accordance with the indicator. In some embodiments, the second transmission is configured to be received by a device that skipped the number of received transmissions.

[0220] FIG. 27 illustrates a flowchart depicting additional example operations of a method in accordance with some embodiments of the present disclosure. Specifically, FIG. 27 depicts a process 2700 including operations for skipping transmissions based on counting received transmissions. The example process may be performed by one or more device(s) in accordance with embodiments of the present disclosure, for example a wireless device, tag, terminal, or the like, as depicted and described herein. Optional steps maybe depicted in broken (e.g., dashed) lines. The device(s) may include computer-readable code or instructions executing on one or more processors of the device(s). Coding of the software for carrying out or performing the process 2700 is well within the scope of a person of ordinary skill in the art having regard to the present disclosure. The process 2700 may include additional or fewer operations than those shown and described and may be carried out or performed in a different order. Computer-readable code or instructions of the software executable by the one or more processors maybe stored on a non-transitoiy computer-readable medium, such as for example, the memory of the device(s). In some embodiments, the process 2700 may be performed by one or more of units or modules (e.g., an integrated circuit) of the device(s), such as field programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs).

[0221] The process 2700 includes a step 2702 of receiving, by a device, scheduling parameters indicating a size of a first window. The size of the first window indicates a number of transmissions from a reader. The scheduling parameters further indicate one or more selection criteria. The one or more selection criteria indicate whether the device is scheduled for one or more communications in the first window.

[0222] The process 2700 further includes a step 2704 of counting, by the device, a number of received transmissions within the first window. In some embodiments, the device counts the number of received transmissions by counting a number of received portions of data. For example, in some embodiments, the device counts a number of received preambles for received transmissions. The device may count transmissions without having processed a complete payload of the transmission. In some embodiments, at least one transmission of the number of received transmissions includes a preamble and a combination of scheduling information and a payload.

[0223] The process 2700 further includes a step 2706 of, in response to the one or more selection criteria indicating that the device is scheduled for communications in the first window, processing, by the device, the one or more received transmissions within the first window. In some embodiments, the device processes each payload of a received transmission, for example rather than skipping the one or more received transmissions during the first window. In some embodiments, the selection criteria includes a combination of a first criterion for the device with a low energy level, and a second criterion for the device being unable to process one or more received transmissions within an earlier window.

[0224] The process 2700 further includes a step 2708 of, in response to the counted number of received transmissions equaling or exceeding the size of the first window, receiving, by the device, at least one next scheduling parameter. In some embodiments, the at least one next scheduling parameter indicates a next window and / or number of transmissions from the reader. The at least one nextscheduling parameter in some embodiments further includes an indication of whether the device is scheduled for communications during the next window, and / or whether the device should skip one or more transmissions during the next window.

[0225] In some embodiments, the process 2700 further includes transmitting, by the device, a message to the reader in response to the processing of the one or more received transmissions within the first window. The message sent to the reader may be a reply transmission.

[0226] FIG. 28 illustrates an example communications system 2800. Communications system 2800 includes an access node 2810 serving user equipments (UEs) with coverage 2801, such as UEs 2820. In a first operating mode, communications to and from a UE passes through access node 2810 with a coverage area 2801. The access node 2810 is connected to a backhaul network 2815 for connecting to the internet, operations and management, and so forth. In a second operating mode, communications to and from a UE do not pass through access node 2810, however, access node 2810 typically allocates resources used by the UE to communicate when specific conditions are met. Communications between a pair of UEs 2820 can use a sidelink (SL) connection (shown as two separate one-way connections 2825). In FIG. 28, the sideline communication is occurring between two UEs operating inside of coverage area 2801. However, sidelink communications, in general, can occur when UEs 2820 are both outside coverage area 2801, both inside coverage area 2801, or one inside and the other outside coverage area 2801. Communication between a UE and access node pair occur over uni-directional communication links, where the communication links between the UE and the access node are referred to as uplinks 2830, and the communication links between the access node and UE is referred to as downlinks 2835-

[0227] Access nodes may also be commonly referred to as Node Bs, evolved Node Bs (eNBs), next generation (NG) Node Bs (gNBs), master eNBs (MeNBs), secondary eNBs (SeNBs), master gNBs (MgNBs), secondary gNBs (SgNBs), network controllers, control nodes, base stations, access points, transmission points (TPs), transmission-reception points (TRPs), cells, carriers, macro cells, femtocells, pico cells, and so on, while UEs may also be commonly referred to as mobile stations, mobiles, terminals, users, subscribers, stations, and the like.Access nodes may provide wireless access in accordance with one or more wireless communication protocols, e.g., the Third Generation Partnership Project (3GPP) long term evolution (LTE), LTE advanced (LTE-A), 5G, 5G LTE, 5G NR, sixth generation (6G), High Speed Packet Access (HSPA), the IEEE 802.11 family of standards, such as 802.na / b / g / n / ac / ad / ax / ay / be, etc. While it is understood that communications systems may employ multiple access nodes capable of communicating with a number of UEs, only one access node and two UEs are illustrated for simplicity.

[0228] FIG. 29 illustrates an example communication system 2900. In general, the system 2900 enables multiple wireless or wired users to transmit and receive data and other content. The system 2900 may implement one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), or non- orthogonal multiple access (NOMA).

[0229] In this example, the communication system 2900 includes electronic devices (ED) 29103-29100, radio access networks (RANs) 292oa-292ob, a core network 2930, a public switched telephone network (PSTN) 2940, the Internet 2950, and other networks 2960. While certain numbers of these components or elements are shown in FIG. 29, any number of these components or elements may be included in the system 2900.

[0230] The EDs 29103-29100 are configured to operate or communicate in the system 2900. For example, the EDs 28ioa-28ioc are configured to transmit or receive via wireless or wired communication channels. Each ED 29103-29100 represents any suitable end user device and may include such devices (or may be referred to) as a user equipment or device (UE), wireless transmit or receive unit (WTRU), mobile station, fixed or mobile subscriber unit, cellular telephone, personal digital assistant (PDA), smartphone, laptop, computer, touchpad, wireless sensor, or consumer electronics device.

[0231] The RANs 292oa-292ob here include base stations 297oa-297ob, respectively. Each base station 297oa-297ob is configured to wirelessly interface with one or more of the EDs 29103-29100 to enable access to the core network 2930, the PSTN 2940, the Internet 2950, or the other networks 2960. For example, the base stations 297oa-297ob may include (or be) one or more ofseveral well-known devices, such as a base transceiver station (BTS), a Node-B (NodeB), an evolved NodeB (eNB), a Next Generation (NG) NodeB (gNB), a gNB centralized unit (gNB-CU), a gNB distributed unit (gNB-DU), a Home NodeB, a Home eNodeB, a site controller, an access point (AP), or a wireless router. The EDs 29103-29100 are configured to interface and communicate with the Internet 2950 and may access the core network 2930, the PSTN 2940, or the other networks 2960.

[0232] In the embodiment shown in FIG. 29, the base station 2970a forms part of the RAN 2920a, which may include other base stations, elements, or devices. Also, the base station 2970b forms part of the RAN 2920b, which may include other base stations, elements, or devices. Each base station 297oa-297ob operates to transmit or receive wireless signals within a particular geographic region or area, sometimes referred to as a “cell.” In some embodiments, multipleinput multiple-output (MIMO) technology maybe employed having multiple transceivers for each cell.

[0233] The base stations 297oa-297ob communicate with one or more of the EDs 29103-29100 over one or more air interfaces 2990 using wireless communication links. The air interfaces 2990 may utilize any suitable radio access technology.

[0234] It is contemplated that the system 2900 may use multiple channel access functionality, including such schemes as described above. In particular embodiments, the base stations and EDs implement 5G New Radio (NR), LTE, LTE-A, or LTE-B. Of course, other multiple access schemes and wireless protocols may be utilized.

[0235] The RANs 292oa-292ob are in communication with the core network 2930 to provide the EDs 29100-29100 with voice, data, application, Voice over Internet Protocol (VoIP), or other services. Understandably, the RANs 2920a- 2920b or the core network 2930 may be in direct or indirect communication with one or more other RANs (not shown). The core network 2930 may also serve as a gateway access for other networks (such as the PSTN 2940, the Internet 2950, and the other networks 2960). In addition, some or all of the EDs 29103-29100 may include functionality for communicating with different wireless networks over different wireless links using different wireless technologies or protocols. Instead of wireless communication (or in addition thereto), the EDs maycommunicate via wired communication channels to a service provider or switch (not shown), and to the Internet 2950.

[0236] Although FIG. 29 illustrates one example of a communication system, various changes maybe made to FIG. 29. For example, the communication system 2900 could include any number of EDs, base stations, networks, or other components in any suitable configuration.

[0237] FIGs. 30A and 30B illustrate example devices that may implement the methods and teachings according to this disclosure. In particular, FIG. 30A illustrates an example ED 3010, and FIG. 30B illustrates an example base station 3070. These components could be used in the system 2900 or in any other suitable system.

[0238] As shown in FIG. 30A, the ED 3010 includes at least one processing unit 3000. The processing unit 3000 implements various processing operations of the ED 3010. For example, the processing unit 3000 could perform signal coding, data processing, power control, input / output processing, or any other functionality enabling the ED 3010 to operate in the system 2900. The processing unit 3000 also supports the methods and teachings described in more detail above. Each processing unit 3000 includes any suitable processing or computing device configured to perform one or more operations. Each processing unit 3000 could, for example, include a microprocessor, microcontroller, digital signal processor, field programmable gate array, or application specific integrated circuit.

[0239] The ED 3010 also includes at least one transceiver 3002. The transceiver 3002 is configured to modulate data or other content for transmission by at least one antenna or NIC (Network Interface Controller) 3004. The transceiver 3002 is also configured to demodulate data or other content received by the at least one antenna 3004. Each transceiver 3002 includes any suitable structure for generating signals for wireless or wired transmission or processing signals received wirelessly or by wire. Each antenna 3004 includes any suitable structure for transmitting or receiving wireless or wired signals. One or multiple transceivers 3002 could be used in the ED 3010, and one or multiple antennas 3004 could be used in the ED 3010. Although shown as a single functional unit, a transceiver 3002 could also be implemented using at least one transmitter and at least one separate receiver.

[0240] The ED 3010 further includes one or more input / output devices 3006 or interfaces (such as a wired interface to the Internet 2850). The input / output devices 3006 facilitate interaction with a user or other devices (network communications) in the network. Each input / output device 3006 includes any suitable structure for providing information to or receiving information from a user, such as a speaker, microphone, keypad, keyboard, display, or touch screen, including network interface communications.

[0241] In addition, the ED 3010 includes at least one memory 3008. The memory 3008 stores instructions and data used, generated, or collected by the ED 3010. For example, the memory 3008 could store software or firmware instructions executed by the processing unit(s) 3000 and data used to reduce or eliminate interference in incoming signals. Each memory 3008 includes any suitable volatile or non-volatile storage and retrieval device(s). Any suitable type of memory may be used, such as random access memory (RAM), read only memory (ROM), hard disk, optical disc, subscriber identity module (SIM) card, memory stick, secure digital (SD) memory card, and the like.

[0242] As shown in FIG. 30B, the base station 3070 includes at least one processing unit 3050, at least one transceiver 3052, which includes functionality for a transmitter and a receiver, one or more antennas 3056, at least one memory 3058, and one or more input / output devices or interfaces 3066. A scheduler, which would be understood by one skilled in the art, is coupled to the processing unit 3050. The scheduler could be included within or operated separately from the base station 3070. The processing unit 3050 implements various processing operations of the base station 3070, such as signal coding, data processing, power control, input / output processing, or any other functionality. The processing unit 3050 can also support the methods and teachings described in more detail above. Each processing unit 3050 includes any suitable processing or computing device configured to perform one or more operations. Each processing unit 3050 could, for example, include a microprocessor, microcontroller, digital signal processor, field programmable gate array, or application specific integrated circuit.

[0243] Each transceiver 3052 includes any suitable structure for generating signals for wireless or wired transmission to one or more EDs or other devices. Each transceiver 3052 further includes any suitable structure for processing signals received wirelessly or by wire from one or more EDs or other devices.Although shown combined as a transceiver 3052, a transmitter and a receiver could be separate components. Each antenna 3056 includes any suitable structure for transmitting or receiving wireless or wired signals. While a common antenna 3056 is shown here as being coupled to the transceiver 3052, one or more antennas 3056 could be coupled to the transceiver(s) 3052, allowing separate antennas 3056 to be coupled to the transmitter and the receiver if equipped as separate components. Each memory 3058 includes any suitable volatile or non-volatile storage and retrieval device(s). Each input / output device 3066 facilitates interaction with a user or other devices (network communications) in the network. Each input / output device 3066 includes any suitable structure for providing information to or receiving / providing information from a user, including network interface communications.

[0244] FIG. 31 is a block diagram of a computing system 3100 that may be used for implementing the devices and methods disclosed herein. For example, the computing system can be any entity of UE, access network (AN), mobility management (MM), session management (SM), user plane gateway (UPGW), or access stratum (AS). Specific devices may utilize all of the components shown or only a subset of the components, and levels of integration may vary from device to device. Furthermore, a device may contain multiple instances of a component, such as multiple processing units, processors, memories, transmitters, receivers, etc. The computing system 3100 includes a processing unit 3102. The processing unit includes a central processing unit (CPU) 3114, memory 3108, and may further include a mass storage device 3104, a video adapter 3110, and an I / O interface 3112 connected to a bus 3120.

[0245] The bus 3120 may be one or more of any type of several bus architectures including a memory bus or memory controller, a peripheral bus, or a video bus. The CPU 3114 may comprise any type of electronic data processor. The memory 3108 may comprise any type of non-transitory system memory such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM), or a combination thereof. In an embodiment, the memory 3108 may include ROM for use at boot-up, and DRAM for program and data storage for use while executing programs.

[0246] The mass storage 3104 may comprise any type of non-transitory storage device configured to store data, programs, and other information and to make the data, programs, and other information accessible via the bus 3120. The mass storage 3104 may comprise, for example, one or more of a solid state drive, hard disk drive, a magnetic disk drive, or an optical disk drive.

[0247] The video adapter 3110 and the I / O interface 3112 provide interfaces to couple external input and output devices to the processing unit 3102. As illustrated, examples of input and output devices include a display 3118 coupled to the video adapter 3110 and a mouse, keyboard, or printer 3116 coupled to the I / O interface 3112. Other devices may be coupled to the processing unit 3102, and additional or fewer interface cards may be utilized. For example, a serial interface such as Universal Serial Bus (USB) (not shown) maybe used to provide an interface for an external device.

[0248] The processing unit 3102 also includes one or more network interfaces 3106, which may comprise wired links, such as an Ethernet cable, or wireless links to access nodes or different networks. The network interfaces 3106 allow the processing unit 3102 to communicate with remote units via the networks. For example, the network interfaces 3106 may provide wireless communication via one or more transmitters / transmit antennas and one or more receivers / receive antennas. In an embodiment, the processing unit 3102 is coupled to a local-area network 3122 or a wide-area network for data processing and communications with remote devices, such as other processing units, the Internet, or remote storage facilities.

[0249] It should be appreciated that one or more steps of the embodiment methods provided herein may be performed by corresponding units or modules. For example, a signal may be transmitted by a transmitting unit or a transmitting module. A signal may be received by a receiving unit or a receiving module. A signal may be processed by a processing unit or a processing module. Other steps may be performed by a performing unit or module, a generating unit or module, an obtaining unit or module, a setting unit or module, an adjusting unit or module, an increasing unit or module, a decreasing unit or module, a determining unit or module, a modifying unit or module, a reducing unit or module, a removing unit or module, or a selecting unit or module. The respective units or modules maybe hardware, software, or a combination thereof. For instance, oneor more of the units or modules maybe an integrated circuit, such as field programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs).

[0250] Although the description has been described in detail, it should be understood that various changes, substitutions and alterations can be made without departing from the spirit and scope of this disclosure as defined by the appended claims. Moreover, the scope of the disclosure is not intended to be limited to the particular embodiments described herein, as one of ordinary skill in the art will readily appreciate from this disclosure that processes, machines, manufacture, compositions of matter, means, methods, or steps, presently existing or later to be developed, may perform substantially the same function or achieve substantially the same result as the corresponding embodiments described herein. Accordingly, the appended claims are intended to include within their scope such processes, machines, manufacture, compositions of matter, means, methods, or steps.

[0251] It should be appreciated that one or more steps of the embodiment methods provided herein may be performed by corresponding units or modules. For example, a signal may be transmitted by a transmitting unit or a transmitting module. A signal may be received by a receiving unit or a receiving module. A signal may be processed by a processing unit or a processing module. Other steps may be performed by a scheduling information receiving unit / module, a transmission reception skipping unit / module, a transmission receiving unit / module, a transmission counting unit / module, an energy harvesting unit / module, transmitting unit / module, a transmission configuring unit / module, a counting unit / module, and / or a selection criteria processing unit / module. The respective units / modules may be hardware, software, or a combination thereof. For instance, one or more of the units / modules may be an integrated circuit, such as field programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs).

[0252] Although the description has been described in detail, it should be understood that various changes, substitutions and alterations can be made without departing from the spirit and scope of this disclosure as defined by the appended claims. Moreover, the scope of the disclosure is not intended to be limited to the particular embodiments described herein, as one of ordinary skill inthe art will readily appreciate from this disclosure that processes, machines, manufacture, compositions of matter, means, methods, or steps, presently existing or later to be developed, may perform substantially the same functions or achieve substantially the same result as the corresponding embodiments described herein. Accordingly, the appended claims are intended to include within their scope such processes, machines, manufacture, composition the description has been described in detail, it should be understood that various changes, substitutions and alterations can be made without departing from the spirit and scope of this disclosure as defined by the appended claims. Moreover, the scope of the disclosure is not intended to be limited to the particular embodiments described herein, as one of ordinary skill in the art will readily appreciate from this disclosure that processes, machines, manufacture, compositions of matter, means, methods, or steps, presently existing or later to be developed, may perform substantially the same function or achieve substantially the same result as the corresponding embodiments described herein. Accordingly, the appended claims are intended to include within their scope such processes, machines, manufacture, compositions of matter, means, methods, or steps.

Claims

CLAIMSWhat is Claimed:

1. A method for wireless communication by a device, comprising: receiving, from a reader, a first transmission comprising an indicator indicating a number of transmissions to skip; skipping reception of a transmission of the number of transmissions from the reader in accordance with the indicator indicating the number of transmissions to skip; and receiving, from the reader, a second transmission after skipping the reception of the transmission.

2. The method according to claim 1, wherein the number of transmissions to skip is a number of physical reader to device channel (PRDCH) transmissions to skip.

3. The method according to claim 1 or claim 2, wherein the indicator further indicates s a skip group, wherein the number of transmissions to skip corresponds to the skip group.

4. The method according to any one of claims 1-3, wherein the skipping the reception of the transmission comprises: counting each preamble of each received transmission; and skipping processing of a non-preamble portion of each received transmission in accordance with the indicator indicating the number of transmissions to skip.

5. The method according to claim 4, further comprising: during the skipping of the processing of the non-preamble portion of each received transmission, performing energy harvesting.

6. A method comprising: transmitting, by a reader, a first transmission comprising a first indicator indicating a first number of transmissions to skip; and transmitting, by the reader, the first number of transmissions that comprise a number of physical reader to device channel (PRDCH) transmissions.

7. The method according to claim 6, the method further comprising: transmitting, by the reader, a second transmission comprising a second indicator indicating a second number of transmissions to skip after transmitting the first number of transmissions.

8. The method according to claim 6 or 7, wherein the first number of transmissions to skip is determined based on at least one of a charging rate, a charging capability, or an energy harvesting time.

9. The method according to any one of claims 6-8, wherein the first indicator indicating a skip group, wherein the first number of transmissions comprises a number of transmissions for members of the skip group to skip, and wherein a device is a member of the skip group.

10. The method according to any one of claims 6-9, wherein the first indicator is based on a relationship with a skip time value.

11. The method according to claim 10, wherein the skip time value exceeds or is smaller than a time value that is based on a capability is related to the device.

12. The method according to claim 11, a second time value is based on a second device of a skip group.

13. A method for a wireless communication by a device, comprising: receiving a first transmission comprising scheduling information, the scheduling information indicating a number of transmissions intended for a group of devices; skipping reception of a transmission of the number of transmissions; and receiving a second transmission after skipping the number of transmissions.

14. The method according to claim 13, wherein the first transmission further comprises an indicator indicating the group of devices, wherein the number of transmissions is indicated as expected to be monitored by a device within the group of devices, and wherein the device is not the device within the group of devices.

15. The method according to any one of claims 13-14, wherein the indicator is based on a relationship with a skip time value.

16. The method according to claim 15, wherein the skip time value exceeds or is smaller than a time value that is based on a capability of the device.

17. The method according to claim 16, wherein a second time value related to the capability is based on a second device of a skip group.

18. The method according to any one of claims 13-17, wherein the skipping the reception of the transmission for the number of transmissions comprises: counting each preamble of each received transmission; and skipping processing of a non-preamble portion of each received transmission.19- The method according to claim 18, further comprising: enabling the device to enter to a state in which the device is configured for the counting each preamble of each received transmission and the skipping the processing of the non-preamble portion of each received transmission.

20. The method according to any one of claims 18-19, further comprising: during the skipping of the processing of the non-preamble portion of each received transmission, performing energy harvesting.

21. A method for wireless communication by a device, comprising: receiving scheduling parameters indicating a size of a first window, wherein the size of the first window indicates a number of transmissions from a reader, and wherein the scheduling parameters further indicate one or more selection criteria indicating whether the device is scheduled for communications in the first window; counting a number of received transmissions within the first window; in response to the one or more selection criteria indicating that the device is scheduled for the communications in the first window, processing one or more received transmissions within the first window; and in response to the counted number of the received transmissions equaling or exceeding the size of the first window, receiving at least one next scheduling parameter.

22. The method according to claim 21, further comprising: transmitting, by the device, a message to the reader in response to the processing the one or more received transmissions within the first window.

23. The method according to any one of claims 21-22, wherein at least one transmission of the received transmissions comprises a preamble and a combination of scheduling information and a payload.

24. The method according to any one of claims 21-23, wherein the counting the number of the received transmissions within the first window comprises: counting, by the device, a number of preambles.

25. The method according to any one of claims 21-24, wherein the one or more selection criteria comprise a combination of a first criterion for the device with a low energy level, and a second criterion for the device being unable to process one or more received transmissions within an earlier window.

26. An apparatus comprising at least one processor and at least one memory having computer instructions stored thereon, wherein the computer instructions, inresponse to execution of the computer instructions, cause the apparatus to perform the method according to any one of claims 1-25.

27. A non-transitory computer-readable storage medium having computer program instructions stored thereon that, in response to execution by at least one processor, configure the at least one processor to perform the method according to any one of claims 1-25.

Images