WO2025235720A1 - Methods and apparatus for low-complexity sequence design - Google Patents

Abstract

Systems and methods for low-complexity sequence design are discussed herein. Additionally, low-complexity transceiver scheme design is discussed herein. For example, a reader determines a duration of a data packet to be transmitted to a device in a PRDCH data transmission, selects a postamble sequence for a Physical Reader-to-Device Channel (PRDCH) data transmission, wherein the postamble sequence is selected based the duration of the data packet of the PRDCH data transmission, and transmits, to the device, the PRDCH data transmission with the postamble sequence, wherein the postamble sequence corresponds to the duration of the data packet. In some cases, the device receives, from the reader, a PRDCH data transmission with a postamble sequence, determines a duration of a data packet of the PRDCH data transmission, based on the postamble sequence, and decodes the data packet based on the duration as determined based on the postamble sequence.

Description

METHODS AND APPARATUS FOR LOW-COMPLEXITY SEQUENCE DESIGN

TECHNICAL FIELD

[0001] This application relates generally to wireless communication systems, including the implementation of reader-to-device (R2D) and device-to-reader (D2R) communication.

BACKGROUND

[0002] Wireless mobile communication technology uses various standards and protocols to transmit data between a base station and a wireless communication device. Wireless communication system standards and protocols can include, for example. 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) (e.g., 4G), 3GPP New Radio (NR) (e.g., 5G), and Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard for Wireless Local Area Networks (WLAN) (commonly known to industry groups as Wi-Fi®).

[0003] As contemplated by the 3GPP, different wireless communication systems' standards and protocols can use various radio access networks (RANs) for communicating between a base station of the RAN (which may also sometimes be referred to generally as a RAN node, a network node, or simply a node) and a wireless communication device known as a user equipment (UE). 3GPP RANs can include, for example, Global System for Mobile communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN). Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and/or Next-Generation Radio Access Network (NG-RAN).

[0004] Each RAN may use one or more radio access technologies (RATs) to perform communication between the base station and the UE. For example, the GERAN implements GSM and/or EDGE RAT, the UTRAN implements Universal Mobile Telecommunication System (UMTS) RAT or other 3GPP RAT, the E-UTRAN implements LTE RAT (sometimes simply referred to as LTE), and NG-RAN implements NR RAT (sometimes referred to herein as 5G RAT, 5G NR RAT, or simply NR). In certain deployments, the E-UTRAN may also implement NR RAT. In certain deployments, NG-RAN may also implement LTE RAT. [0005] A base station used by a RAN may correspond to that RAN. One example of an E-UTRAN base station is an Evolved Universal Terrestrial Radio Access Network (E- UTRAN) Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB). One example of an NG-RAN base station is a next generation Node B (also sometimes referred to as a g Node B or gNB).

[0006] A RAN provides its communication services with external entities through its connection to a core network (CN). For example, E-UTRAN may utilize an Evolved Packet Core (EPC) while NG-RAN may utilize a 5G Core Network (5GC).

[0007] Frequency bands for 5G NR may be separated into two or more different frequency ranges. For example, Frequency Range 1 (FR1) may include frequency bands operating in sub-6 gigahertz (GHz) frequencies, some of which are bands that may be used by previous standards, and may potentially be extended to cover new spectrum offerings from 410 megahertz (MHz) to 7125 MHz. Frequency Range 2 (FR2) may include frequency bands from 24.25 GHz to 52.6 GHz. Note that in some systems, FR2 may also include frequency bands from 52.6 GHz to 71 GHz (or beyond). Bands in the millimeter wave (mmWave) range of FR2 may have smaller coverage but potentially higher available bandwidth than bands in FR1. Skilled persons will recognize these frequency ranges, which are provided by way of example, may change from time to time or from region to region.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS [0008] To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure number in which that element is first introduced.

[0009] FIG. 1 illustrates an example of physical reader-to-device channel (PRDCH) generation in accordance with some embodiments.

[0010] FIG. 2 illustrates an example of physical device-to-reader channel (PDRCH) generation in accordance with some embodiments.

[0011] FIG. 3 illustrates examples of the transmission modes for receiving and/or transmitting a physical channel, according to embodiments herein.

[0012] FIG. 4 illustrates examples of the transmission modes for receiving and/or transmitting a PDRCH and/or a PRDCH, according to embodiments herein. [0013] FIG. 5 illustrates an example of PRDCH generation where the same coding may be applied, according to embodiments herein.

[0014] FIG. 6 illustrates an example of PDRCH generation where the same coding may be applied, according to embodiments herein.

[0015] FIG. 7 illustrates an example of PRDCH generation where a separate coding may be applied, according to embodiments herein.

[0016] FIG. 8 illustrates an example of PDRCH generation where a separate coding may be applied, according to embodiments herein.

[0017] FIG. 9 illustrates a method for a reader, according to embodiments herein.

[0018] FIG. 10 illustrates a method for a device, according to embodiments herein.

[0019] FIG. 11 illustrates an example architecture of a wireless communication system, according to embodiments disclosed herein.

[0020] FIG. 12 illustrates a sy stem for performing signaling between a wireless device and a network device, according to embodiments disclosed herein.

DETAILED DESCRIPTION

[0021] Various embodiments are described with regard to a UE. However, reference to a UE is merely provided for illustrative purposes. The example embodiments may be utilized with any electronic component that may establish a connection to a network and is configured with the hardware, software, and/or firmware to exchange information and data with the network. Therefore, the UE as described herein is used to represent any appropriate electronic component.

[0022] In some wireless communication systems, various device definitions have been agreed upon. For example, a first device, "‘Device I ". may have around one microwatt (pW) peak power consumption, may have energy storage, an initial sampling frequency offset (SFO) of up to 10X parts per million (ppm) where X is a multiplier (e.g., in a range of 4-5), with neither downlink (DL) nor uplink (UL) amplification in the device. Further, the device's UL transmission may be backscattered on a carrier wave provided externally.

[0023] A second device, “Device 2a” may have less than or equal to a few hundred pW peak power consumption, may have energy storage, may have an initial SFO of up to 10X ppm where X is a multiplier (e.g., in a range of 3-4), and both downlink (DL) and/or UL amplification may be in the device. Further, the device’s UL transmission may be backscattered on a carrier wave provided externally.

[0024] A third device, “Device 2b” may have less than or equal to a few hundred pW peak power consumption, may have energy storage, may have an initial SFO of up to 10X ppm where X is a multiplier (e.g., in a range of 3-4), and both DL and/or UL amplification in the device. Further, the device’s UL transmission may be generated internally by the device.

[0025] FIG. 1 illustrates an example of physical reader-to-device channel (PRDCH) generation in accordance with some embodiments. In some wireless communication systems, various agreements related to the physical channel design for reader-to-device (R2D) and device-to-reader (D2R) are made. For ambient loT devices, a dedicated physical broadcast channel for R2D (e.g., physical broadcast channel (PBCH)-like) may not be considered. For ambient loT devices, at least for R2D data transmission, a physical channel (e.g., PRDCH) may be considered. Note that system information (if defined) may be transmitted on the PRDCH, however whether/how control information is transmitted on the PRDCH may be further contemplated. For the R2D timing acquisition signal immediately preceding the transmission of a physical channel, a preamble with at least two parts may be considered which includes a start-indicator part and a clock-acquisition part, where the start-indicator part immediately precedes the clock-acquisition part. The preamble may be considered as not to be part of a physical channel.

[0026] Additionally, various blocks may be considered as the baseline for PRDCH generation at the reader. For example, cyclic redundancy checksum (CRC) bits may be appended to R2D information bits if there is non-zero length CRC at a CRC attachment block 102. Then, the resultant of the CRC attachment block 102 may be passed to a line coding block 104 and then passed to a 00K-1/00K-4 generation with orthogonal frequency -division multiplexing (OFDM) waveform generation block such as the OOK- l/OOK-4 generation with OFDM waveform generation block 106. The 00K-1/00K-4 generation with OFDM waveform generation block 106 may include resource mapping. Further blocks may also be considered for PRDCH generation.

[0027] FIG. 2 illustrates an example of physical device-to-reader channel (PDRCH) generation in accordance with some embodiments. In some wireless communication mechanisms, for ambient loT devices, at least for D2R data transmission, a physical channel (e.g., PDRCH) may be considered along with various other aspects. A response transmitted, from the device to the reader during contention-based access procedure, on the PDRCH may be considered, however whether/how/what D2R control information (if defined) may be transmitted on the PDRCH may be further contemplated. For D2R, a preamble preceding each PDRCH transmission may be considered as the baseline at least for the D2R timing acquisition signal, but the preamble is not part of the PDRCH.

[0028] Additionally, various blocks may be contemplated for PDRCH generation at the device. For example, as a baseline, CRC bits may be appended to D2R information bits if there is non-zero length CRC at a CRC attachment block 202. The resultant of the CRC attachment block 202 is passed to a coding block 204. Various coding procedures performed in the coding block 204 may include, for example, with/without line coding and/or forward error correction (FEC). If no line coding is used at the line coding block 204, there may be an additional block (e.g. square wave generator) before and/or after the modulation block 206. Modulation of the resultant of the coding block 204 may be considered at the modulation block 206. Note that further blocks may additionally be considered.

[0029] In some wireless communication systems, for D2R transmission, a midamble may be considered at least for the purpose of performing timing/frequency tracking or channel estimation or interference estimation. Various information may considered for the midamble such as modulation and coding schemes (e.g., data modulation, line/channel coding), receiving procedures (e.g., coherent or non-coherent), D2R transmission length and/or packet size, midamble overhead, timing/frequency accuracy, and/or phase accuracy.

[0030] Additionally, in some wireless communication mechanisms, a R2D transmission without a midamble may be used as the baseline if Manchester encoding is used. Further considerations for the R2D transmission with a midamble if pulse-interval encoding (PIE) is used may be contemplated.

[0031] For the R2D timing acquisition signal immediately preceding the transmission of a physical channel, a preamble with at least two parts which includes a start-indicator part and a clock-acquisition part may be contemplated, where the start-indicator part immediately precedes the clock-acquisition part. The start-indicator part may be a fixed length (e.g., one OFDM symbol duration) and may provide the start of the R2D transmission, however further details of start-indicator part (e.g., the pattern) may be considered. The clock-acquisition part may provide at least the chip duration of the subsequent physical channel transmission. Details of the clock-acquisition part (e.g.. structure, encoding, length), procedures to determine chip duration of the subsequent physical channel transmission, and other functionalities may be further considered. The preamble may not be considered to be part of a physical channel. In some instances, other part(s) of the preamble, (if any), whether the above clock acquisition is sufficient for all devices, and how to make the preamble compact may be further considered.

[0032] For D2R, a preamble preceding each PDRCH transmission is considered as the baseline at least for the D2R timing acquisition signal. The preamble may not be part of the PDRCH. Additionally, other functionalities of the preamble may be contemplated (e.g., channel estimation, time acquisition, time/frequency tracking etc.).

[0033] Embodiments discussed herein may mitigate issues related to aspects of and the design of the preamble for R2D and D2R transmissions. For example, it may not be clear how to support variable size of preamble including a delimiter part and/or a clock acquisition part, how to associate different preamble sizes to different PRDCH and/or PDRCH transmissions during an inventory' round, or how to utilize postamble and/or explicit indication to signal the end of PRDCH and/or PDRCH transmission may be discussed herein. Embodiments herein may be related to several design aspects of different sequences including the preamble and the postamble that may be considered for ambient internet of things (loT) device communication.

[0034] In various embodiments, a different size of the preamble may be transmitted to the device or transmitted from the device, where the length of the first part of the preamble may be used to indicate the length of the second part of the preamble, thus indicating the total size of the preamble from the different variable lengths supported by the device. Additionally, in some embodiments, during an inventory round, the length of the preamble may be associated with the duration of the gap between the two R2D transmissions and/or two D2R transmissions. In various embodiments, the reader may explicitly indicate the size of the preamble to be applied at the start of the PDRCH. Further, in some embodiments, if the other ambles (e.g., postamble, midamble) are applied to indicate the end of R2D and/or D2R transmissions, multiple lengths and/or ty pes of the postamble may be configured and one of the configured postamble sequences may be applied based on the length of the data packet transmission. In various embodiments, the length of all of the ambles (e.g., preamble, midamble, postamble) are indicated to be the same by the reader for a given PDRCH transmission.

[0035] In some embodiments, for preamble length determination, a minimum and a maximum length of the delimiter part of the preamble may be configured depending on the range of length within the minimum and maximum length. Further, the succeeding clock-acquisition part of the preamble’s length may be determined.

[0036] In some cases, a mapping table (e.g., provided in Table 1) may be configured for the device, where the corresponding pairing of lengths between the delimiter part and clock-acquisition part may be provided. As a result, this may allow for support of a variable length of the preamble, without having an explicit indicator of the length.

Table 1: Determination of Variable Length Preamble(s)

[0037] In some embodiments, a preamble length association with transmission gaps duration may be introduced. For example, a device may transmit according to variable lengths of preamble, wherein the length of the transmitted preamble may be associated with the gap duration with the proceeding transmission in the same direction and/or in the opposite direction. In some cases, a mapping table (e.g., provided in Table 2) may be configured for the device, where the length of preamble may be associated with the a gap duration of the succeeding transmission (e.g., R2D) from the previous transmission in the same direction (e.g., R2D) and with the gap duration of succeeding transmission (e.g., R2D) from the previous transmission in the opposite direction (e.g., D2R).

Table 2: Association between the Preamble Length and the Gap Duration

Between Transmissions

[0038] In various embodiments, a postamble design may be introduced for indicating the end of the transmission. For example, if a PRDCH is used to indicate the control information to the device, then it may be followed by a postamble sequence, regardless of the size of the control information. In the control information, at least a transmit block size (TBS) for the next PRDCH and/or PDRCH may be included, where, in some cases, a common TBS table (e.g., provided in Table 3) for PRDCH and PDRCH may be configured. In some other cases, a dedicated/separate TBS table for PRDCH and PDRCH may be configured, respectively. If the TBS field is not included as part of the control information, then the device may assume that the packet size is longer than the size supported in the configured table and therefore, may (implicitly) determine that a postamble may be associated at the end of the packet transmission to identify the end of the transmission.

Table 3: TBS Size(s) Configuration

[0039] In various embodiments of postamble design for indicating the end of a transmission, if a TBS is not indicated/included in the control information, then the postamble may be applied, where multiple lengths/types of the postamble may be configured for data transmission and one of the configured postamble sequences may be applied based on the length of the data packet transmission. In some examples, if the postamble is applied for both the PRDCH and the PDRCH, then the same configuration may be applied for the postamble sequence. In some other examples, if the postamble is applied for both the PRDCH and the PDRCH, then different configurations may be applied for the postamble sequence (a separate/dedicated postamble sequence for each of PRDCH and PDRCH data transmissions). An example of a postamble sequence type/length for different data transmission packet sizes is provided in Table 4.

Table 4: Packet Size and Corresponding Postamble Sequence

[0040] In various embodiments of postamble design for indicating the end of a transmission, if multiple data packet transmissions (e.g., a PRDCH data transmission) are contiguously scheduled (e.g.. with a minimum gap of between each PRDCH transmission), then one or more options may be applied to determine the size of each PRDCH data transmission. In a first option, the control information may provide a single TBS for each of the PRDCH data transmissions for a burst and no postamble may be applied to any of the PRDCHs. In a second option, the control information may provide multiple TBSs for each of the PRDCH data transmissions for a burst and no postamble may be applied to any of the PRDCHs. In a third option, the control information may provide a single TBS for the entire burst and may additionally indicate the number of PRDCH data transmissions, where the TBS for each PRDCH data transmission may be determined by the device based on the total TBS/number of PRDCH data transmissions. Note that no postamble may be applied to any of the PRDCHs. In a fourth option, no TBS may be provided and the postamble may be attached at the end of each of the PRDCHs. In a fifth option, no TBS may be provided and the postamble may be attached at the end of the last PRDCH. In such option, the end of PRDCH (with exception of the last PRDCH) may be determined based on the gap between the current and next PRDCH and the preamble associated with the next PRDCH. In a sixth option, a postamble may always be attached to each PRDCH. It should be understood that similar options may be applicable for the PDRCH transmission. Additionally, it should be understood that various combinations of the discussed options may be used for postamble design.

[0041] By way of example embodiments, a first example (Example 1) is a method at device, wherein the device is configured with a mapping of length of delimiter and the corresponding length for preamble and based on the configuration, the device determines the duration of the preamble based on the duration of the delimiter-part of the preamble at the start of preamble.

[0042] Example 2 includes the method of Example 1, wherein the preamble duration is associated with the gap duration between the succeeding transmission and the preceding transmission.

[0043] Example 3 includes the method of Example 2, wherein the preamble duration may be different depending on the type of succeeding transmission and the proceeding transmission

[0044] Example 4 is a method at a device, wherein the duration and the ty pe of postamble sequence is associated with one or more of the duration of the preceding transmission, the presence of explicit signaling for indicating the preceding transmission duration, and/or the type of information in the preceding transmission [0045] Low- Complexity Transceiver Schemes

[0046] In some wireless communication mechanisms, various issues related to the transmission schemes of the physical channels for R2D information, (i.e., the design details of PRDCH) have been considered. Note that additional issues have been identified and are mitigated by embodiments discussed herein. For example, various encountered undefined issues may include how to schedule/multiplex control information, system information from the reader to device along with data transmission from reader to device using PRDCH, how to handle encoding (CRC attachment) of different types of information for PRDCH, what transmission modes are supported for PRDCH and their corresponding identification at the ambient loT device, how to schedule/multiplex control information from the device to reader along with data transmission from device to reader using PDRCH, how to handle encoding (CRC attachment) of different ty pes of information for PDRCH and what transmission modes are supported for PDRCH and their corresponding identification at the ambient loT device.

[0047] In various embodiments, a device may be able to receive and/or transmit a physical channel using at least one of multiple transmission modes, wherein the transmission mode may be used to determine one or more of: information types that may be mapped to the physical channel, encoding of the different types (if present) of information for the physical channel generation, and/or a length of each of the information types. The length of preamble(s), midamble(s), and/or postamble(s) may still be present within such embodiments.

[0048] FIG. 3 illustrates examples of the transmission modes for receiving and/or transmitting over a PRDCH, according to embodiments herein.

[0049] In various embodiments, transmission modes (TMs) (e.g., TM0, TM1, TM2, TM3) for PRDCH and PDRCH may be introduced. For example, the transmission modes may include a PRDCH-TM0 302 mode where the R2D data 304 may be mapped. The PRDCH-TM0 302 mode may have a variable length, which may be separately indicated (e.g., via resource allocation and/or TBS signaling). The PRDCH-TM0 302 mode may be a unicast type mode.

[0050] The transmission modes for the PRDCH may further include a PRDCH-TM1 306 mode where the system information 308 may be mapped. The PRDCH-TM1 306 mode may have a fixed length. The PRDCH-TM1 306 mode may be a broadcast type mode.

[0051] The transmission modes for the PRDCH may further include a PRDCH-TM2 310 mode where only R2D Layer 1 (LI) control information 312 may be mapped. The PRDCH-TM2 310 mode may either be a broadcast type, a groupcast type or a unicast type mode. The length of the PRDCH-TM2 310 mode may be fixed or may be a variable length, where the end of transmission may be signaled via a postamble.

[0052] The transmission modes for the PRDCH may further include a PRDCH-TM3 314 mode where R2D LI control information 312 and R2D data 304 may be mapped. Note this mode may be a unicast mode. In some cases, the LI control information 312 portion may precede the R2D data 304 portion in the PRDCH and the length of LI control information 312 portion may be fixed, while the length of R2D data 304 may be variable. Additionally, the length of the R2D data 304 may be signaled in the R2D LI control information 312 portion.

[0053] FIG. 4 illustrates examples of the transmission modes for receiving and/or transmitting over a PDRCH according to embodiments herein.

[0054] In various embodiments, multiple transmission modes for PDRCH may be introduced including, for example, a PDRCH-TM0 402 mode where D2R data 408 is mapped. The PDRCH-TM0 402 mode may have a variable length, which may be separately indicated (e g., via resource allocation and/or TBS signaling). The PDRCH- TM0 402 mode may be a unicast type mode.

[0055] The transmission modes for the PDRCH may further include a PDRCH-TM1 404 mode where the D2R LI control information 410 may be mapped. This mode may be a unicast mode and the length may be fixed or may be of variable length, where the end of transmission may be signaled via postamble.

[0056] The transmission modes for the PDRCH may further include a PDRCH-TM2 406 mode where D2R LI control information 410 and D2R data 408 may be mapped. This mode may be a unicast mode. In the PDRCH-TM2 406 mode, a LI control information 410 portion may precede a D2R data 408 portion in the PDRCH. Additionally, the length of the LI control information 410 portion may be fixed while the length of D2R data 408 portion may be variable. Further, the length of D2R data 408 may be signaled within the R2D LI control information 410 portion. [0057] In various embodiments, separate or joint encoding of different information types for PRDCH and PDRCH may be introduced. In some cases, various procedures may be introduced for the encoding of PRDCH and PDRCH when more than one type of information is mapped to the same channel. In some examples, separate encoding via a separate CRC attached to each type of information bits may be introduced, where the CRC length and/or type may depend on the type of information. Further, following the separate CRC attachment, the same coding may be applied and a single codeword may be generated. In some examples, for the PRDCH-TM3 and PDRCH-TM2 modes discussed herein, the CRC attached to the LI control information portion may be a shorter length as compared to the CRC attached to the data information portion.

[0058] FIG. 5 illustrates an example of PRDCH generation where the same coding may be applied, according to embodiments herein. For example, R2D data information bits may be passed through a first CRC attachment block 502 and R2D control information bits may be passed through a second CRC attachment block 504. Then, both the resultant of the first CRC attachment block 502 and the second CRC attachment block 504 are passed together to the same line coding block 506 which passes its resultant through an 00K-1/00K-4 generation with OFDM waveform generation block 508, thus generating a PRDCH.

[0059] FIG. 6 illustrates an example of PDRCH generation where the same coding may be applied, according to embodiments herein. For example, D2R data information bits may be passed through a first CRC attachment block 602 and D2R control information bits may be passed through a second CRC attachment block 604. Then, both the resultant of the first CRC attachment block 602 and the second CRC attachment block 604 are passed together to the same coding block 606 which passes its resultant through a modulation block 608, thus generating a PDRCH.

[0060] In various embodiments, separate encoding via separate CRC attached to each type of information bits may be introduced, where the CRC length and/or ty pe may depend on the type of information. Further, following the separate CRC attachment, a separate coding may be applied and two codewords may be generated.

[0061] FIG. 7 illustrates an example of PRDCH generation where a separate coding may be applied, according to embodiments herein. For example. R2D data information bits may be passed through a first CRC attachment block 702 and R2D control information bits may be passed through a second CRC attachment block 704. Then, the resultant of the first CRC attachment block 702 is passed to first line coding block 706 and the resultant of the second CRC attachment block 704 is passed to the second line coding block 708. The resultant of the first line coding block 706 and the second line coding block 708 are together passed to the same 00K-1/00K-4 generation with OFDM waveform generation block 710, thus generating a PRDCH.

[0062] FIG. 8 illustrates an example of PDRCH generation where a separate coding may be applied, according to embodiments herein. For example, D2R data information bits may be passed through a first CRC attachment block 802 and D2R control information bits may be passed through a second CRC attachment block 804. The resultant of the first CRC attachment block 802 is passed to a first coding block 806 and the resultant of the second CRC attachment block 804 is passed to a second coding block 808. Then, the resultant of the first coding block 806 and the second coding block 808 are together passed to the same modulation block 810, thus generating a PDRCH.

[0063] In various embodiments, joint encoding via the same CRC attached to the joint block of the information bits may be introduced, where the CRC length and/or type may depend on the total length of the information block. For example, the PRDCH generation and PDRCH generation may be similar to that of the physical channel generation discussed in FIG. 1, and FIG. 2, respectively, but, in such cases, the R2D and the D2R information bits inputted at the start may include the combined information bits.

[0064] In various embodiments, signaling of the transmission modes for PRDCH and PDRCH may be introduced. For example, various options may be introduced to signal which transmission mode the ambient loT device may need to apply for the PRDCH and for the PDRCH.

[0065] In a first option, the length and or voltage pattern of a delimiter may be used to signal which transmission mode the ambient loT device is to be applied. Different lengths/ranges for the delimiter may be used to determine which transmission mode is applied for a physical channel. For example, for the PRDCH, a PRDCH-TM0 may be applied if the delimiter value is less than X0 us. The PRDCH-TM1 mode may be applied if the delimiter value is greater than X0 us, but less than XI us. The PRDCH-TM2 mode may be applied if the delimiter value is greater than XI us, but less than X2 us. The PRDCH-TM3 mode may be applied if the delimiter value is greater than X2 us, but less than X3 us. Alternatively or in addition, a different voltage pattern may be applied for the delimiter to indicate the transmission mode for the physical channel (e g., a low voltage throughout may indicate one transmission mode and a high voltage throughout may indicate a second transmission mode). Further, in some examples, a combination of different lengths and voltage patterns may also be applied

[0066] In a second option, the preamble sequence’s clock acquisition portion may be used to signal which transmission mode the ambient loT device is to be applied. Alternatively or in addition, the transmission mode may be determined based on information associated with preamble. For example, different types of sequences may indicate different transmission modes and/or different lengths of sequences may indicate different transmission modes.

[0067] In a third option, an explicit indication in the R2D control information part may be used to signal which transmission mode the ambient loT device is to be applied. For example, the explicit information field (e.g., included as part of the R2D control information) may indicate which transmission mode is applied for the next PRDCH and/or PDRCH transmission.

[0068] It should be understood that, in some cases, various combinations of the discussed options may be used to signal which transmission mode the ambient loT device is to be applied for the PRDCH and for the PDRCH.

[0069] A first example embodiment (Example A) includes a method at a first device that can be configured with multiple modes of transmission for the physical channel to transmit and receive from other device(s), wherein the transmission mode for a physical channel is used to determined one or more of information types that are mapped to the physical channel, encoding of the different types of information for the physical channel generation, length of each of the information types, and/or presence of sequence in the middle and/or end of the physical channel.

[0070] Example B includes the method of Example A, wherein the first device is indicated with one of the transmission modes from the multiple configured transmission modes for the physical channel for transmitting to the other device.

[0071] Example C includes the method of Example A, wherein the first device is indicated with one of the transmission modes from the multiple configured transmission modes for the physical channel for receiving from the other device.

[0072] Example D includes the method of Example A, wherein the cast type of the physical channel may be implicitly determined based on the indicated transmission mode. [0073] Example E includes the method of Example A, wherein for mapping different types of information to the same physical channel, a separate CRC of different lengths could be applied to each information part.

[0074] Example F includes the method of Example E, wherein after the separate CRC attached to each information part, single coding is applied to multiple information parts, by concatenating the CRC attached information parts.

[0075] Example, G includes the method of Example E. wherein after the separate CRC attached to each information part, separate coding is applied to multiple information parts and separate codewords are generated, which are then concatenated for further processing.

[0076] Example H includes the method of Example A, wherein for mapping different types of information to the same physical channel, a single CRC is applied to the concatenated information bits of different types.

[0077] Example I includes the method of Example H, wherein depending on which types of information bits are mapped together to the same physical channel, different CRC length may be added accordingly.

[0078] Example J includes the method of Example A, wherein different lengths of the delimiter are used to indicate the type of transmission mode for the succeeding physical channel.

[0079] Example K includes the method of Example A, wherein different voltage pattern of the delimiter are used to indicate the type of transmission mode for the succeeding physical channel.

[0080] Example L includes the method of Example A, wherein different sequence lengths of the clock-acquisition part of the preamble are used to indicate the type of transmission mode for the succeeding physical channel.

[0081] Example M includes the method of Example A, wherein different sequence types of the clock-acquisition part of the preamble are used to indicate the type of transmission mode for the succeeding physical channel.

[0082] Example N includes the method of Example A, wherein R2D control information includes a field to indicate the transmission mode for the physical channels for PRDCH and/or PDRCH.

[0083] FIG. 9 illustrates a method 900 for a reader, according to embodiments herein. The illustrated method 900 includes determining 902 a duration of a data packet to be transmitted to a device in a PRDCH data transmission. The method 900 further includes selecting 904 a postamble sequence for a PRDCH data transmission, wherein the postamble sequence is selected based the duration of the data packet of the PRDCH data transmission. The method 900 further includes transmitting 906, to the device, the PRDCH data transmission with the postamble sequence, wherein the postamble sequence corresponds to the duration of the data packet.

[0084] In some embodiments of the method 900, a first type or a first length of the postamble sequence corresponds to a first duration, and a second type or a second length of the postamble sequence corresponds to a second duration.

[0085] In some embodiments of the method 900, the postamble sequence is attached at an end of each of a series of PRDCH transmissions sent by the reader.

[0086] In some embodiments of the method 900, the postamble sequence is attached at an end of each of a series of PRDCH transmissions sent by the reader, wherein the end of each of the series of PRDCH transmissions align with a boundary of a last orthogonal frequency-division multiplexing (OFDM) symbol.

[0087] In some embodiments of the method 900, the postamble sequence is attached only at an end of a last PRDCH transmission of a series of PRDCH transmissions sent by the reader.

[0088] In some embodiments, the method 900 further comprises determining a postamble configuration and applying the postamble configuration to the postamble sequence. In some such embodiments, the postamble configuration is applied to both PRDCH transmissions from the reader and PDRCH transmissions from the device. In some other such embodiments, the postamble configuration is applied to PRDCH transmissions from the reader and a different configuration is applied for PDRCH transmissions from the device.

[0089] In some embodiments, the method 900 further comprises generating a preamble for the PRDCH data transmission, wherein the preamble comprises a delimiter part and a clock-acquisition part, wherein a length of the delimiter part corresponds to a length of the clock-acquisition part, such that the length of the delimiter part indicates to the device a length of the clock acquisition part, and transmitting the preamble prior to the PRDCH data transmission. In some such embodiments, a preamble length is associated with a duration of a gap between transmissions. [0090] FIG. 10 illustrates a method 1000 for a device, according to embodiments herein. The illustrated method 1000 includes receiving 1002, from a reader, a PRDCH data transmission with a postamble sequence. The method 1000 further includes determining 1004 a duration of a data packet of the PRDCH data transmission, based on the postamble sequence. The method 1000 further includes decoding 1006 the data packet based on the duration as determined based on the postamble sequence.

[0091] In some embodiments of the method 1000, a first type or a first length of the postamble sequence corresponds to a first duration, and a second type or a second length of the postamble sequence corresponds to a second duration.

[0092] In some embodiments of the method 1000, the postamble sequence is attached at an end of each of a series of PRDCH transmissions sent by the reader.

[0093] In some embodiments of the method 1000, the postamble sequence is attached only at an end of a last PRDCH transmission of a series of PRDCH transmissions sent by the reader.

[0094] In some embodiments of the method 1000, a postamble configuration is applied to both PRDCH transmissions from the reader and PDRCH transmissions from the device.

[0095] In some embodiments of the method 1000, a postamble configuration is applied to PRDCH transmissions from the reader and a different configuration is applied for PDRCH transmissions from the device.

[0096] In some embodiments, the method 1000 further comprises receiving a preamble associated with the PRDCH data transmission, wherein the preamble comprises a delimiter part and a clock-acquisition part, and wherein a length of the delimiter part corresponds to a length of the clock-acquisition part, such that the length of the delimiter part indicates to the device a length of the clock acquisition part. In some such embodiments, a preamble length is associated with a duration of a gap between transmissions.

[0097] FIG. 11 illustrates an example architecture of a wireless communication system 1100, according to embodiments disclosed herein. The following description is provided for an example wireless communication system 1100 that operates in conjunction with the LTE sy stem standards and/or 5G or NR system standards as provided by 3GPP technical specifications. [0098] As shown by FIG. 11, the wireless communication system 1100 includes UE 1102 and UE 1104 (although any number of UEs may be used). In this example, the UE 1102 and the UE 1104 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device configured for wireless communication.

[0099] The UE 1102 and UE 1104 may be configured to communicatively couple with a RAN 1106. In embodiments, the RAN 1106 may be NG-RAN, E-UTRAN, etc. The UE 1102 and UE 1104 utilize connections (or channels) (shown as connection 1108 and connection 1110, respectively) with the RAN 1106, each of which comprises a physical communications interface. The RAN 1106 can include one or more base stations (such as base station 1112 and base station 1114) that enable the connection 1108 and connection 1110.

[0100] In this example, the connection 1108 and connection 1110 are air interfaces to enable such communicative coupling, and may be consistent with RAT(s) used by the RAN 1106, such as, for example, an LTE and/or NR.

[0101] In some embodiments, the UE 1102 and UE 1104 may also directly exchange communication data via a sidelink interface 1116. The UE 1104 is shown to be configured to access an access point (shown as AP 1118) via connection 1120. By way of example, the connection 1120 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 1118 may comprise a Wi-Fi® router. In this example, the AP 1118 may be connected to another network (for example, the Internet) without going through a CN 1124.

[0102] In embodiments, the UE 1102 and UE 1104 can be configured to communicate using orthogonal frequency division multiplexing (OFDM) communication signals with each other or with the base station 1112 and/or the base station 1114 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to. an orthogonal frequency division multiple access (OFDMA) communication technique (e.g., for downlink communications) or a single carrier frequency division multiple access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers. [0103] In some embodiments, all or parts of the base station 1112 or base station 1114 may be implemented as one or more software entities running on server computers as part of a virtual network. In addition, or in other embodiments, the base station 1112 or base station 1114 may be configured to communicate with one another via interface 1122. In embodiments where the wireless communication system 1100 is an LTE system (e.g., when the CN 1124 is an EPC), the interface 1122 may be an X2 interface. The X2 interface may be defined between two or more base stations (e.g.. two or more eNBs and the like) that connect to an EPC, and/or between two eNBs connecting to the EPC. In embodiments where the wireless communication system 1100 is an NR system (e.g., when CN 1124 is a 5GC), the interface 1122 may be an Xn interface. The Xn interface is defined between two or more base stations (e.g., two or more gNBs and the like) that connect to 5GC, between a base station 1112 (e.g., a gNB) connecting to 5GC and an eNB, and/or between two eNBs connecting to 5GC (e.g., CN 1124).

[0104] The RAN 1106 is shown to be communicatively coupled to the CN 1124. The CN 1124 may comprise one or more network elements 1126, which are configured to offer various data and telecommunications services to customers/subscribers (e.g., users of UE 1102 and UE 1104) who are connected to the CN 1124 via the RAN 1106. The components of the CN 1124 may be implemented in one physical device or separate physical devices including components to read and execute instructions from a machine- readable or computer-readable medium (e g., a non-transitory machine-readable storage medium).

[0105] In embodiments, the CN 1124 may be an EPC, and the RAN 1106 may be connected with the CN 1124 via an SI interface 1128. In embodiments, the SI interface 1128 may be split into two parts, an SI user plane (Sl-U) interface, which carries traffic data between the base station 1112 or base station 1114 and a serving gateway (S-GW), and the SI -MME interface, which is a signaling interface between the base station 1112 or base station 1114 and mobility management entities (MMEs).

[0106] In embodiments, the CN 1124 may be a 5GC, and the RAN 1106 may be connected with the CN 1124 via an NG interface 1128. In embodiments, the NG interface 1 128 may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the base station 1112 or base station 1114 and a user plane function (UPF), and the SI control plane (NG-C) interface, which is a signaling interface between the base station 1112 or base station 1114 and access and mobility management functions (AMFs).

[0107] Generally, an application server 1130 may be an element offering applications that use internet protocol (IP) bearer resources with the CN 1124 (e.g., packet switched data services). The application server 1130 can also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc.) for the UE 1102 and UE 1104 via the CN 1124. The application server 1130 may communicate with the CN 1124 through an IP communications interface 1132.

[0108] FIG. 12 illustrates a system 1200 for performing signaling 1234 between a wireless device 1202 and a network device 1218, according to embodiments disclosed herein. The system 1200 may be a portion of a wireless communications system as herein described. The wireless device 1202 may be, for example, a UE of a wireless communication system. The network device 1218 may be, for example, a base station (e g., an eNB or a gNB) of a wireless communication system.

[0109] The wireless device 1202 may include one or more processor(s) 1204. The processor(s) 1204 may execute instructions such that various operations of the wireless device 1202 are performed, as described herein. The processor(s) 1204 may include one or more baseband processors implemented using, for example, a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0110] The wireless device 1202 may include a memory 1206. The memory 1206 may be a non-transitory computer-readable storage medium that stores instructions 1208 (which may include, for example, the instructions being executed by the processor(s) 1204). The instructions 1208 may also be referred to as program code or a computer program. The memory’ 1206 may also store data used by. and results computed by, the processor(s) 1204.

[OHl] The wireless device 1202 may include one or more transceiver(s) 1210 that may include radio frequency (RF) transmitter circuitry and/or receiver circuitry that use the antenna(s) 1212 of the wireless device 1202 to facilitate signaling (e.g., the signaling 1234) to and/or from the wireless device 1202 with other devices (e.g., the network device 1218) according to corresponding RATs. [0112] The wireless device 1202 may include one or more antenna(s) 1212 (e.g., one, two, four, or more). For embodiments with multiple antenna(s) 1212, the wireless device 1202 may leverage the spatial diversity of such multiple antenna(s) 1212 to send and/or receive multiple different data streams on the same time and frequency resources. This behavior may be referred to as, for example, multiple input multiple output (MIMO) behavior (referring to the multiple antennas used at each of a transmitting device and a receiving device that enable this aspect). MIMO transmissions by the wireless device 1202 may be accomplished according to precoding (or digital beamforming) that is applied at the wireless device 1202 that multiplexes the data streams across the antenna(s) 1212 according to known or assumed channel characteristics such that each data stream is received with an appropriate signal strength relative to other streams and at a desired location in the spatial domain (e.g., the location of a receiver associated with that data stream). Certain embodiments may use single user MIMO (SU-MIMO) methods (where the data streams are all directed to a single receiver) and/or multi user MIMO (MU-MIMO) methods (where individual data streams may be directed to individual (different) receivers in different locations in the spatial domain).

[0113] In certain embodiments having multiple antennas, the wireless device 1202 may implement analog beamforming techniques, whereby phases of the signals sent by the antenna(s) 1212 are relatively adjusted such that the (joint) transmission of the antenna(s) 1212 can be directed (this is sometimes referred to as beam steering).

[0114] The wireless device 1202 may include one or more interface(s) 1214. The interface(s) 1214 may be used to provide input to or output from the wireless device 1202. For example, a wireless device 1202 that is a UE may include interface(s) 1214 such as microphones, speakers, a touchscreen, buttons, and the like in order to allow for input and/or output to the UE by a user of the UE. Other interfaces of such a UE may be made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver(s) 1210/antenna(s) 1212 already described) that allow for communication between the UE and other devices and may operate according to known protocols (e.g., Wi-Fi®, Bluetooth®, and the like).

[0115] The wireless device 1202 may include a D2R and R2D transmission module 1216. The D2R and R2D transmission module 1216 may be implemented via hardware, software, or combinations thereof. For example, the D2R and R2D transmission module 1216 may be implemented as a processor, circuit, and/or instructions 1208 stored in the memory 1206 and executed by the processor(s) 1204. In some examples, the D2R and R2D transmission module 1216 may be integrated within the processor(s) 1204 and/or the transceiver(s) 1210. For example, the D2R and R2D transmission module 1216 may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the processor(s) 1204 or the transceiver(s) 1210.

[0116] The D2R and R2D transmission module 1216 may be used for various aspects of the present disclosure. For example, the D2R and R2D transmission module 1216 may be configured to perform any of the UE-based methods, reader-based methods, and/or device-based methods disclosed herein.

[0117] The network device 1218 may include one or more processor(s) 1220. The processor(s) 1220 may execute instructions such that various operations of the network device 1218 are performed, as described herein. The processor(s) 1220 may include one or more baseband processors implemented using, for example, a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0118] The network device 1218 may include a memory 1222. The memory 1222 may be a non-transitory computer-readable storage medium that stores instructions 1224 (which may include, for example, the instructions being executed by the processor(s) 1220). The instructions 1224 may also be referred to as program code or a computer program. The memory 1222 may also store data used by, and results computed by, the processor(s) 1220.

[0119] The network device 1218 may include one or more transceiver(s) 1226 that may include RF transmitter circuitry and/or receiver circuitry that use the antenna(s) 1228 of the network device 1218 to facilitate signaling (e.g., the signaling 1234) to and/or from the network device 1218 with other devices (e.g., the wireless device 1202) according to corresponding RATs.

[0120] The network device 1218 may include one or more antenna(s) 1228 (e.g., one, two, four, or more). In embodiments having multiple antenna(s) 1228, the network device 1218 may perform MIMO, digital beamforming, analog beamforming, beam steering, etc., as has been described.

[0121] The network device 1218 may include one or more interface(s) 1230. The interface(s) 1230 may be used to provide input to or output from the network device 1218. For example, a network device 1218 that is a base station may include interface(s) 1230 made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver(s) 1226/antenna(s) 1228 already described) that enables the base station to communicate with other equipment in a core network, and/or that enables the base station to communicate with external networks, computers, databases, and the like for purposes of operations, administration, and maintenance of the base station or other equipment operably connected thereto.

[0122] The network device 1218 may include a D2R and R2D transmission module 1232. The D2R and R2D transmission module 1232 may be implemented via hardware, software, or combinations thereof. For example, the D2R and R2D transmission module 1232 may be implemented as a processor, circuit, and/or instructions 1224 stored in the memor 1222 and executed by the processor(s) 1220. In some examples, the D2R and R2D transmission module 1232 may be integrated within the processor(s) 1220 and/or the transceiver(s) 1226. For example, the D2R and R2D transmission module 1232 may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the processor(s) 1220 or the transceiver(s) 1226.

[0123] The D2R and R2D transmission module 1232 may be used for various aspects of the present disclosure. For example, the D2R and R2D transmission module 1232 may be configured to perform any of the network-based methods, reader-based methods, and/or device-based methods disclosed herein.

[0124] Embodiments contemplated herein include an apparatus comprising means to perform one or more elements of any of the UE-based methods disclosed herein. This apparatus may be. for example, an apparatus of a UE (such as a wireless device 1202 that is a UE, as described herein).

[0125] Embodiments contemplated herein include one or more non -transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of any of the UE-based methods disclosed herein. This non-transitory computer-readable media may be, for example, a memory of a UE (such as a memory 1206 of a wireless device 1202 that is a UE, as described herein).

[0126] Embodiments contemplated herein include an apparatus comprising logic, modules, or circuitry to perform one or more elements of any of the UE-based methods disclosed herein. This apparatus may be, for example, an apparatus of a UE (such as a wireless device 1202 that is a UE, as described herein).

[0127] Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of any of the UE-based methods disclosed herein. This apparatus may be, for example, an apparatus of a UE (such as a wireless device 1202 that is a UE, as described herein).

[0128] Embodiments contemplated herein include a signal as described in or related to one or more elements of any of the UE-based methods disclosed herein.

[0129] Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processor is to cause the processor to carry out one or more elements of any of the UE- based methods disclosed herein. The processor may be a processor of a UE (such as a processor(s) 1204 of a wireless device 1202 that is a UE. as described herein). These instructions may be, for example, located in the processor and/or on a memory of the UE (such as a memory 1206 of a wireless device 1202 that is a UE, as described herein).

[0130] Embodiments contemplated herein include an apparatus comprising means to perform one or more elements of any of the network-based methods disclosed herein. This apparatus may be, for example, an apparatus of a base station (such as a network device 1218 that is a base station, as described herein).

[0131] Embodiments contemplated herein include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of any of the network-based methods disclosed herein. This non-transitory computer-readable media may be, for example, a memory of a base station (such as a memory 1222 of a network device 1218 that is a base station, as described herein).

[0132] Embodiments contemplated herein include an apparatus comprising logic, modules, or circuitry to perform one or more elements of any of the network-based methods disclosed herein. This apparatus may be, for example, an apparatus of a base station (such as a network device 1218 that is a base station, as described herein). [0133] Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of any of the network-based methods disclosed herein. This apparatus may be, for example, an apparatus of a base station (such as a network device 1218 that is a base station, as described herein).

[0134] Embodiments contemplated herein include a signal as described in or related to one or more elements of any of the network-based methods disclosed herein.

[0135] Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out one or more elements of any of the network-based methods disclosed herein. The processor may be a processor of a base station (such as a processor(s) 1220 of a network device 1218 that is a base station, as described herein). These instructions may be, for example, located in the processor and/or on a memory of the base station (such as a memory 1222 of a netw ork device 1218 that is a base station, as described herein).

[0136] For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth herein. For example, a baseband processor as described herein in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein.

[0137] Any of the above described embodiments may be combined with any other embodiment (or combination of embodiments), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0138] Embodiments and implementations of the systems and methods described herein may include various operations, which may be embodied in machine-executable instructions to be executed by a computer system. A computer system may include one or more general-purpose or special-purpose computers (or other electronic devices). The computer system may include hardware components that include specific logic for performing the operations or may include a combination of hardware, software, and/or firmware.

[0139] It should be recognized that the systems described herein include descriptions of specific embodiments. These embodiments can be combined into single systems, partially combined into other systems, split into multiple systems or divided or combined in other ways. In addition, it is contemplated that parameters, attributes, aspects, etc. of one embodiment can be used in another embodiment. The parameters, attributes, aspects, etc. are merely described in one or more embodiments for clarity, and it is recognized that the parameters, attributes, aspects, etc. can be combined with or substituted for parameters, attributes, aspects, etc. of another embodiment unless specifically disclaimed herein.

[0140] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

[0141] Although the foregoing has been described in some detail for purposes of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles thereof. It should be noted that there are many alternative ways of implementing both the processes and apparatuses described herein. Accordingly, the present embodiments are to be considered illustrative and not restrictive, and the description is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.

Claims

1. A method for a reader, comprising: determining a duration of a data packet to be transmitted to a device in a PRDCH data transmission; selecting a postamble sequence for a Physical Reader-to-Device Channel (PRDCH) data transmission, wherein the postamble sequence is selected based the duration of the data packet of the PRDCH data transmission; and transmitting, to the device, the PRDCH data transmission with the postamble sequence, wherein the postamble sequence corresponds to the duration of the data packet.

2. The method of claim 1, wherein a first type or a first length of the postamble sequence corresponds to a first duration, and a second type or a second length of the postamble sequence corresponds to a second duration.

3. The method of claim 1, wherein the postamble sequence is attached at an end of each of a series of PRDCH transmissions sent by the reader.

4. The method of claim 1 , wherein the postamble sequence is attached at an end of each of a series of PRDCH transmissions sent by the reader, wherein the end of each of the series of PRDCH transmissions align with a boundary' of a last orthogonal frequencydivision multiplexing (OFDM) symbol.

5. The method of claim 1, wherein the postamble sequence is attached only at an end of a last PRDCH transmission of a series of PRDCH transmissions sent by the reader.

6. The method of claim 1, further comprising: determining a postamble configuration; and applying the postamble configuration to the postamble sequence.

7. The method of claim 6, wherein the postamble configuration is applied to both PRDCH transmissions from the reader and PDRCH transmissions from the device.

8. The method of claim 6, wherein the postamble configuration is applied to PRDCH transmissions from the reader and a different configuration is applied for PDRCH transmissions from the device.

9. The method of claim 1, further comprising: generating a preamble for the PRDCH data transmission, wherein the preamble comprises a delimiter part and a clock-acquisition part, wherein a length of the delimiter part corresponds to a length of the clockacquisition part, such that the length of the delimiter part indicates to the device the length of the clock-acquisition part; and transmitting the preamble prior to the PRDCH data transmission.

10. The method of claim 9, wherein a preamble length is associated with a duration of a gap between transmissions.

11. A method for a device, comprising: receiving, from a reader, a Physical Reader-to-Device Channel (PRDCH) data transmission with a postamble sequence; determining a duration of a data packet of the PRDCH data transmission, based on detection of the postamble sequence; and decoding the data packet based on the duration as determined based on detection of the postamble sequence.

12. The method of claim 11, wherein a first ty pe or a first length of the postamble sequence corresponds to a first duration, and a second type or a second length of the postamble sequence corresponds to a second duration.

13. The method of claim 11, wherein the postamble sequence is attached at an end of each of a series of PRDCH transmissions sent by the reader.

14. The method of claim 11, wherein the postamble sequence is attached only at an end of a last PRDCH transmission of a series of PRDCH transmissions sent by the reader.

15. The method of claim 11, wherein a postamble configuration is applied to both PRDCH transmissions from the reader and PDRCH transmissions from the device.

16. The method of claim 11, wherein a postamble configuration is applied to PRDCH transmissions from the reader and a different configuration is applied for PDRCH transmissions from the device.

17. The method of claim 11, further comprising receiving a preamble associated with the PRDCH data transmission, wherein the preamble comprises a delimiter part and a clockacquisition part, and wherein a length of the delimiter part corresponds to a length of the clock-acquisition part, such that the length of the delimiter part indicates to the device the length of the clock-acquisition part.

18. The method of claim 17, wherein a preamble length is associated with a duration of a gap between transmissions.

19. A reader apparatus comprising: a processor; and a memory storing instructions that when executed by the processor, configure the apparatus to: determine a duration of a data packet to be transmitted to a device in a PRDCH data transmission; select a postamble sequence for a Physical Reader-to-Device Channel (PRDCH) data transmission, wherein the postamble sequence is selected based the duration of the data packet of the PRDCH data transmission; and transmit, to the device, the PRDCH data transmission with the postamble sequence, wherein the postamble sequence corresponds to the duration of the data packet.

20. The reader apparatus of claim 19, wherein a first type or a first length of the postamble sequence corresponds to a first duration, and a second type or a second length of the postamble sequence corresponds to a second duration.

21. An apparatus comprising means to perform the method of any of claim 1 to claim 18.

22. A computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform the method of any of claim 1 to claim 18.

23. An apparatus comprising logic, modules, or circuitry to perform the method of any of claim 1 to claim 18.

24. A baseband processor for a user equipment (UE) configured to perform the method of any of claim 11 to claim 18.