Determination of the length of cyclic redundancy check for ambient-iot devices

Abstract

An apparatus configured to process a transport block for a reader-to-device (R2D) or device-to-reader (D2R) communication, determine a size of the transport block or a payload size of the transport block and determine a Cyclic Redundancy Check (CRC) length for the transport block based on the size of the transport block or the payload size, wherein the CRC length is determined to be a first length when the of the transport block or the payload size is greater than a threshold, and a second length when the of the transport block or the payload size is equal to or less than the threshold.

Description

Attorney Docket No. 30164 / 101702Ref. No. P70848WO1Cyclic Redundancy Check Handling for Ambient-IoT Devices Inventors: Ankit Bhamri, Dawei Zhang, Haitong Sun, Hong He, Huaning Niu, Sigen Ye, Wei Zeng and Weidong YangPriority / Incorporation By Reference

[0001] This application claims priority to U. S. Provisional Application Serial No. 63 / 753, 718 filed on February 4, 2025, and entitled " Cyclic Redundancy Check Handling for Ambient-IoT Devices, " the entirety of which is incorporated by reference herein.Background

[0002] A network may support ambient Internet of Things(ambient-IoT) devices. An ambient-IoT device may harvest energy from the ambient environment. A reader (e. g., base station, user equipment (UE), etc. ) may transmit query commands and communicate with ambient-IoT devices. The communications from the reader to the ambient-IoT devices are termed R2D communications. The communications from the device to the ambient-IoT devices may be termed D2R communications. The R2D and D2R communications may or may not include cyclic redundancy checking (CRC). There is a need to define CRC handling for the R2D and D2R communications.Summary

[0003] Some example embodiments are related to an apparatus having memory coupled to processing circuitry, the processing circuitry configured to process a transport block for a reader-to-device (R2D) or device-to-reader (D2R) communication, determine a size of the transport block or a payload size of the transport block and determine a Cyclic Redundancy Check (CRC)Attorney Docket No. 30164 / 101702Ref. No. P70848WO1length for the transport block based on the size of the transport block or the payload size, wherein the CRC length is determined to be a first length when the of the transport block or the payload size is greater than a threshold, and a second length when the of the transport block or the payload size is equal to or less than the threshold.

[0004] Other example embodiments are related to an apparatus having memory coupled to processing circuitry, the processing circuitry configured to process, based on reader signaling, configuration information for a cyclic redundancy check (CRC) of a Physical Reader to Device Channel (PRDCH), process, based on the reader signaling, a PRDCH communication and determine CRC information for the PRDCH communication at least based on the configuration information or the PRDCH, wherein the CRC information comprises whether a CRC is attached to the PRDCH communication or a length of the CRC when it is attached to the PRDCH communication.Brief Description of the Drawings

[0005] Fig. 1 shows a first example deployment scenario according to various example embodiments.

[0006] Fig. 2 shows a second example deployment scenario according to various example embodiments.

[0007] Fig. 3 shows an example wireless device according to various example embodiments.

[0008] Fig. 4 shows an example user equipment (UE) according to various example embodiments.Attorney Docket No. 30164 / 101702Ref. No. P70848WO1

[0009] Fig. 5 shows an example base station according to various example embodiments.

[0010] Fig. 6 shows an example TBS to CRC mapping table according to various example embodiments.

[0011] Fig. 7 shows an example method of determining and using CRC information for R2D communications according to various example embodiments.

[0012] Fig. 8 shows an example method of determining and using CRC information for D2R communications according to various example embodiments.

[0013] Fig. 9 shows an example method of determining and using CRC information for R2D communications where the CRC for a control part and a data part of the R2D communications are different according to various example embodiments.Detailed Description

[0014] The example embodiments may be further understood with reference to the following description and the related appended drawings, wherein like elements are provided with the same reference numerals. The example embodiments disclose manners of handling cyclic redundancy check (CRC) for ambient-IoT devices at both the device side and the reader side.

[0015] The example embodiments are described with regard to ambient-IoT devices. An ambient-IoT device refers to a Third Generation Partnership Project (3GPP) IoT device that is smallerAttorney Docket No. 30164 / 101702Ref. No. P70848WO1than other types of loT devices and provides cost-efficient solutions to various types of use cases such as, but not limited to, tracking and monitoring obj ects. Throughout this description, the terms "wireless device" or "device" may be used to generally refer to an ambient-IoT device or any other type of smaller wireless device that is equipped with similar capabilities and configured with the hardware, software, and / or firmware to exchange information and data with a network.Therefore, the terms "ambient-IoT device, " "wireless device" and "device" as described herein is used to represent any appropriate electronic component.

[0016] The example embodiments may be applied to different device types including device type 1, device type 2a and device type 2b. The term "device type 1" may refer to a wireless device that possesses one or more of the following characteristics: a peak power consumption of approximately 1 microwatt (μW), energy storage capabilities, an initial sampling frequency offset (SFO) up to 10xparts per million (ppm) where x could be as high as 5, neither downlink nor uplink amplification in the wireless device and uplink transmissions that are backscattered on a carrier wave provided externally to the wireless device.

[0017] The term "device type 2a" may refer to a wireless device that possesses one or more of the following characteristics: a peak power consumption equal to or less than ( < ) a few hundred microwatt (μW), energy storage capabilities, an initial SFO up to 10xppm where x could be same or lower than that of device type 1, downlink and / or uplink amplification in the wireless device and uplink transmissions that areAttorney Docket No. 30164 / 101702Ref. No. P70848WO1backscattered on a carrier wave provided externally to the wireless device.

[0018] The term "device type 2b" may refer to a wireless device that possesses one or more of the following characteristics: a peak power consumption of equal to or less than (<) a few hundred microwatt (μW), energy storage capabilities, an initial SFO up to 10xppm where x could be same or lower than that of device type 1, downlink and / or uplink amplification in the wireless device and uplink transmissions that are generated internally by the wireless device. However, any reference to a particular device type (e. g., device type 1, 2a, eb, etc. ) is merely provided for illustrative purposes.Different entities may refer to similar concepts in a different manner.

[0019] The example embodiments are also described with regard to a 5G New Radio (NR) network. However, reference to a 5G NR network is merely provided for illustrative purposes. The example embodiments may be utilized with any network that may establish a connection to a wireless device and exchange information and data with the wireless device (e. g., 5G-Advanced networks, 6G networks, 7G networks, etc. ).

[0020] The example embodiments are further described with regard to a deployment scenario where the wireless devices (e. g., ambient-IoT device) may communicate over the air with a base station of the network. In other examples, the wireless device may communicate over the air with a user equipment (UE) that acts as an intermediate node, under network control, between the wireless device and the base station. ThroughoutAttorney Docket No. 30164 / 101702Ref. No. P70848WO1this description, the term "reader" may refer to the node that is communicating over the air with the ambient-IoT devices.Therefore, a reader may refer to a base station or a UE depending on the applicable deployment scenario. Thus, in the example embodiments, communications may be referred to as reader to device (R2D) communications where the transmitter is the reader and the receiver is the ambient-IoT device. Similarly, device to reader (D2R) communications refer to the scenario where the transmitter is the ambient-IoT device and the receiver is the reader. The R2D and D2R communications each include only one physical channel, a Physical Reader to Device Channel ( PRDCH) and a Physical Device to Reader Channel (PDRCH), e. g., there are no separate uplink and downlink channels, control channels, random access channels, etc.

[0021] According to some aspects, the example embodiments introduce manners of handling CRC for ambient-IoT devices.Specifically, the example embodiments provide operations for a reader to explicitly or implicitly signal CRC information to ambient-IoT devices for R2D communications and operations for the ambient-IoT device to determine how to handle the CRC information. In addition, the example embodiments provide operations for the ambient-IoT device to determine CRC information for D2R communications and in some cases, signal this CRC information to the reader. These and other example embodiments re described in greater detail below.

[0022] Fig. 1 shows a first example deployment scenario 100 according to various example embodiments. The example deployment scenario 100 includes multiple wireless devices 112A - 112N. The wireless devices 112A - 112N may be ambient-IoT devices or anyAttorney Docket No. 30164 / 101702Ref. No. P70848WO1other appropriate type o f electronic component that i s configured to communicate via a network. An actual deployment scenario may include any number of wireles s devices being used by any number of users.

[0023] The example deployment scenario 100 al so includes a UE 110. The UE 110 may be any type of electronic component that i s configured to communicate via a network, e. g., mobi le phones, tablet computers, desktop computers, smartphones, phablets, embedded devices, wearables, Internet of Things ( loT ) devices, etc. An actual deployment scenario may include any number o f UEs being used by any number o f users. Thus, the example o f a s ingle UE 110 i s merely provided for i llustrative purposes.

[0024] The example deployment scenario 100 al so includes a 5G new radio (NR) radio access network (RAN) 120. However, the example embodiments may apply to other types o f networks ( e. g., s ixth generation ( 6G ) RAN, 5G cloud RAN, a next generation RAN (NG-RAN), a long-term evolution ( LTE ) RAN, a legacy cellular network, a wireles s local area network (WLAN), etc. ).

[0025] The 5G NR RAN 120 may be a portion o f a cel lular network that may be deployed by a network carrier ( e. g., Veri zon, AT & T, T-Mobile, etc. ). The 5G NR RAN 120 may include base stations or acces s nodes (Node Bs, eNodeBs, HeNBs, eNBS, gNBs, gNodeBs, macrocel l s, microcel l s, small cel ls, femtocells, etc. ) that are conf igured to send and receive traf f ic from devices that are equipped with the appropriate cellular chip set. In the example deployment scenario 100, the 5G NR RAN 120 deploys a gNB 120A.Attorney Docket No. 30164 / 101702Ref. No. P70848WO1

[0026] In the example deployment scenario 100, the UE 110 may be configured to operate as an intermediate node between the wireless devices 112A - 112N and the network. Thus, the UE 110 may be configured as a reader and communicate with the wireless devices 112A - 112N over the air. The wireless devices 112A -112N may also send messages directly to the UE 110. The channels between the reader (e. g., UE 110) and the wireless devices 112A - 112N may be referred to as a physical device-to-reader data channel (PDRCH) for uplink (D2R) communication and a physical reader-to-device data channel (PRDCH) for downlink communication and / or control (R2D).

[0027] Fig. 2 shows a second example deployment scenario 200 according to various example embodiments. The example deployment scenario 100 includes multiple wireless devices 112A - 112N, similar to the example deployment scenario 100. The wireless devices 112A - 112N may be ambient-IoT devices or any other appropriate type of electronic component that is configured to communicate via a network.

[0028] The example deployment scenario 200 also includes a 5G new radio (NR) radio access network (RAN) 120 similar to the deployment scenario 100. The 5G NR RAN 120 deploys a gNB 120A. In the example deployment scenario 200, the wireless devices 112A - 112N communicate directly with the gNB 120A, e. g., there is no intermediate UE. Thus, the gNB 120A may be configured as a reader and communicate with the wireless devices 112A - 112N over the air. The wireless devices 112A - 112N may also send messages directly to the gNB 120A. The channels between the reader (e. g., gNB 120A) and the wireless devices 112A - 112N mayAttorney Docket No. 30164 / 101702Ref. No. P70848WO1also be referred to as the PDRCH for uplink communication and PRDCH for downlink communication and / or control.

[0029] Fig. 3 shows an example wireless device 112 according to various example embodiments, e. g., any of the wireless devices 112A - 112N of the example deployments 100 or 200. The wireless device 112 may include a processor 305, a memory arrangement 310, a transceiver 315 and other components 320. The other components may include, for example, an audio output device, a power supply, energy storage, ports to electrically connect the wireless device 112 to other electronic components, etc.

[0030] The processor 305 may be comprised of processing circuitry that is configured to execute a plurality of engines of the wireless device 112. For example, the engines may include a CRC engine 335. The CRC engine 335 may perform various operations related to CRC handling for the device, including, but not limited to processing CRC configuration information, processing R2D communications, determining CRC information for the R2D communications based on the CRC configuration and / or the R2D communications, and determining CRC information for the D2R communications. These and other operations are described in greater detail below.

[0031] The above referenced engine 335 being an application ( e. g., a program) executed by the processor 305 is merely provided for illustrative purposes. The functionality associated with the processor 305 and / or engine 335 may also be represented as a separate incorporated component of the wireless device 112 or may be a modular component coupled to the wireless deviceAttorney Docket No. 30164 / 101702Ref. No. P70848WO1112, e. g., an integrated circuit with or without firmware. For example, the integrated circuit may include input circuitry to receive s ignal s and processing circuitry to process the s ignal s and other information. The engine may al so be embodied as one application or separate appl ications. In addition, in some devices, the functional ity described for the proces sor 305 is spl it among two or more proces sors such as a baseband processor and an appl ications processor. The example embodiments may be implemented in any o f these or other conf igurations o f a wireles s device.

[0032] The memory arrangement 310 may be a hardware component configured to store data related to operations performed by the wireles s device 112. In some examples, the memory arrangement 310 may include non-volatile memory (NVM) that i s used to permanently store certain types of information ( e. g., device ID, etc. ) and regi sters for temporarily storing information whi le energy i s avai lable in energy storage. However, reference to NVM and regi sters is merely provided for il lustrative purposes. The example embodiments may be implemented in any o f these or other configurations of a memory arrangement.

[0033] The transceiver 315 may be a hardware component configured to communicate with the 5G NR-RAN 120, an LTE-RAN ( not pictured), a legacy RAN ( not pictured), a WLAN ( not pictured), etc. Accordingly, the transceiver 315 may operate on a variety o f di f ferent frequencies or channel s ( e. g., set o f consecutive frequencies ). The transceiver 315 includes circuitry configured to transmit and / or receive s ignals ( e. g., control s ignal s, data signal s ). Such s ignal s may be encoded with information implementing any one o f the methods describedAttorney Docket No. 30164 / 101702Ref. No. P70848WO1herein. The processor 305 may be operably coupled to the transceiver 315 and configured to receive from and / or transmit signals to the transceiver 315. The processor 305 may be configured to encode, decode and / or process signals (e. g., signaling from a base station of a network) for implementing any one of the techniques described herein.

[0034] Fig. 4 shows an example UE 110 according to various example embodiments. The UE 110 will be described with regard to the example deployment 100 of Fig. 1. The UE 110 may include a processor 405, a memory arrangement 410, a display device 415, an input / output ( I / O) device 420, a transceiver 425 and other components 430. The other components 430 may include, for example, an audio input device, an audio output device, a power supply, a data acquisition device, ports to electrically connect the UE 110 to other electronic devices, etc.

[0035] The processor 405 may be comprised of processing circuitry that is configured to execute a plurality of engines for the UE 110. For example, the engines may include a CRC engine 435. The CRC engine 435 may perform various operations related to CRC handling for ambient-IoT devices including, but not limited to configuring an ambient-IoT device with CRC configuration information, generating R2D communications with CRC information in accordance with the CRC configuration information and processing D2R communications with CRC information. These and other operations are described in greater detail below.

[0036] The above referenced engine 435 being an application (e. g., a program) executed by the processor 405 is merelyAttorney Docket No. 30164 / 101702Ref. No. P70848WO1provided for illustrative purposes. The functionality associated with the engine 435 may also be represented as a separate incorporated component of the UE 110 or may be a modular component coupled to the UE 110, e. g., an integrated circuit with or without firmware. For example, the integrated circuit may include input circuitry to receive signals and processing circuitry to process the signals and other information. The engine may also be embodied as one application or separate applications. In addition, in some UEs, the functionality described for the processor 405 is split among two or more processors such as a baseband processor and an applications processor. The example embodiments may be implemented in any of these or other configurations of a UE.

[0037] The memory arrangement 410 may be a hardware component configured to store data related to operations performed by the UE 110. The display device 415 may be a hardware component configured to show data to a user while the I / O device 420 may be a hardware component that enables the user to enterinputs. The display device 415 and the I / O device 420 may be separate components or integrated together such as a touchscreen.

[0038] The transceiver 425 may be a hardware component configured to exchange data with the wireless device 112, the 5G NR RAN 120 and / or any other appropriate type of network.Accordingly, the transceiver 425 may operate on a variety of different frequencies or channels (e. g., set of consecutive frequencies). The transceiver 425 includes circuitry configured to transmit and / or receive signals (e. g., control signals, data signals). Such signals may be encoded with informationAttorney Docket No. 30164 / 101702Ref. No. P70848WO1implementing any one of the methods described herein. The processor 405 may be operably coupled to the transceiver 425 and configured to receive from and / or transmit signals to the transceiver 425. The processor 405 may be configured to encode, decode and / or process signals ( e. g., signaling from a base station of a network) for implementing any one of the techniques described herein.

[0039] Fig. 5 shows an example base station 500 according to various example embodiments. The base station 500 may represent the gNB 120A of the deployment scenario 100 or 200 or any other type of access node.

[0040] The base station 500 may include a processor 505, a memory arrangement 510, an input / output ( I / O) device 515, a transceiver 520, and other components 525. The other components 525 may include, for example, an audio input device, an audio output device, a battery, a data acquisition device, ports to electrically connect the base station 500 to other electronic devices and / or power sources, transceiver chains, antenna elements, antenna panels, etc.

[0041] The processor 505 may be comprised of processing circuitry that is configured to execute a plurality of engines for the base station 500. For example, the engines may include a CRC engine 535. The CRC engine 535 may perform various operations related to CRC handling for ambient-IoT devices including, but not limited to configuring an ambient-IoT device with CRC configuration information, generating R2D communications with CRC information in accordance with the CRC configuration information and processing D2R communications withAttorney Docket No. 30164 / 101702Ref. No. P70848WO1CRC information. These and other operations are described in greater detail below.

[0042] The above noted engine 535 being an application ( e. g., a program) executed by the processor 505 is only an example. The functionality associated with the engine 535 may also be represented as a separate incorporated component of the base station 500 or may be a modular component coupled to the base station 500, e. g., an integrated circuit with or without firmware. For example, the integrated circuit may include input circuitry to receive signals and processing circuitry to process the signals and other information. In addition, in some base stations, the functionality described for the processor 505 is split among a plurality of processors (e.g., a baseband processor, an applications processor, etc. ). The example embodiments may be implemented in any of these or other configurations of a base station.

[0043] The memory arrangement 510 may be a hardware component configured to store data related to operations performed by the base station 500. The I / O device 515 may be a hardware component or ports that enable a user to interact with the base station 500.

[0044] The transceiver 520 may be a hardware component configured to exchange data with the UE 110 and / or the wireless devices 112A – 112N. The transceiver 520 may operate on a variety of different frequencies or channels (e.g., set of consecutive frequencies). Therefore, the transceiver 520 may include one or more components to enable the data exchange with the various networks, UEs and wireless devices. The transceiverAttorney Docket No. 30164 / 101702Ref. No. P70848WO1520 includes circuitry configured to transmit and / or receive signals (e. g., control signals, data signals). Such signals may be encoded with information implementing any one of the methods described herein. The processor 505 may be operably coupled to the transceiver 520 and configured to receive from and / or transmit signals to the transceiver 520. The processor 505 may be configured to encode, decode and / or process signals (e. g., signaling from a UE, a wireless device, etc. ) for implementing any one of the methods described herein.

[0045] As described above, the example embodiments are relate to CRC handling for R2D or D2R communications. Some example CRC use cases may include no CRC being attached, a CRC-6 attachment, or a CRC-16 attachment. The example embodiments are not limited to these CRC use cases as the example embodiments may also be implemented with other types of CRC. In general, smaller or no CRC may provide lower overhead and better resource utilization. Higher CRC may provide better detection performance. The example embodiments provide manners of signaling (e. g. explicit or implicit) to determine both at the device and the reader the CRC that is attached to communications and the length of the CRC.

[0046] In addition, various example embodiments of CRC handling are described below. These example embodiments are not exclusive, e. g., the principles of some example embodiments may be implemented in other example embodiments. To provide a nonlimiting example, some example embodiments use an explicit indication of whether a CRC is attached to a R2D communication. Other example embodiments describe that a length of the CRC may be implicitly determined based on the type of the R2D communication. These two embodiments may be combined to allow aAttorney Docket No. 30164 / 101702Ref. No. P70848WO1device to determine a CRC is attached based on the explicit indication and the length of that CRC based on the implicit determination of the type of the R2D communication. Other combinations of example embodiments will be apparent from the below description of the example embodiments.

[0047] In some example embodiments, a PRDCH may include an explicit indication related to CRC. As described above, the PRDCH (or PDRCH) may be a single channel that may carry control information, data, etc. Thus, a first part of a PRDCH communication may include Layer 1 (L1) R2D control information that may indicate ( e. g., via a bitfield) whether and / or what length CRC may be attached to the data part of the same PRDCH and / or follow-up PRDCH transmissions. In one option, one bit of a bitfield may indicate whether a CRC is attached, e. g., a value of "1" in bitfield indicates a CRC is attached and a value of " 0" indicates no CRC is attached.

[0048] I f the bitfield indicates there is a CRC attachment, then the length of the CRC may be indicated in various manners. In some examples, the indication of the exact length may be implicitly indicated. For example, the length of the CRC may depend on the length of the PRDCH. In this example, the length may be determined based on, for example, a transport block size ( TBS ) indication, a postamble following the PRDCH or any other manner of determining the size of the PRDCH. The device may be configured with information that indicates the length of the CRC that is attached to a PRDCH data portion based on the length of the PRDCH. Thus, once the device determines the length of the PRDCH, the device may determine the length of the CRC that is attached to a PRDCH data portion based on the configuration.Attorney Docket No. 30164 / 101702Ref. No. P70848WO1

[0049] In other examples, if the bitfield indicates there is a CRC attachment, then the length of the CRC may be indicated implicitly based on the type of the PRDCH transmission, e. g., the device may be configured with information relating a CRC length to a PRDCH transmission type. When the device determines the PRDCH transmission type, the device then may determine the CRC length based on the configuration. Additional details of these two examples of implicit indication of CRC length are provided below.

[0050] In further examples, if the bitfield indicates there is a CRC attachment, then the length of the CRC may be explicitly indicated. For example, the bitfield may be a two bit bitfield where the value of the two bits indicates both whether there is a CRC and the CRC length (if a CRC is attached). To provide one example of a two bit bitfield explicitly indicating the length of the CRC. A bitfield value of "00" may indicate no CRC, a bitfield value of "01" may indicate a CRC-6 attachment, and a bitfield value of "11" may indicate a CRC-16 attachment. This is only an example and other bitfield values or combinations may be used to signal whether the CEC is attached and the CRC length.

[0051] In the above examples, the information provided by the LI R2D control part is related to the CRC information for the data part of the R2D communication. Whether the LI R2D control part in the PRDCH also has a CRC may be defined in standards (e. g., 3GPP Technical Specifications (TS) ) as to whether there is a CRC and the type / length of the CRC for the control part of the PRDCH.Attorney Docket No. 30164 / 101702Ref. No. P70848WO1

[0052] In some example embodiments, whether there is a CRC and the type / length of the CRC may be implicitly signaled to the device. In these example embodiments, whether and what length of the CRC is to be attached to PRDCH may be determined based on the R2D time acquisition signal (TAS ) length and / or pattern of the R2D communication. The TAS of the R2D communication may include a start-indicator part (SIP) and a clock acquisition part (CAP). The SIP and the CAP may be received prior to the data portion of the R2D communication. The SIP and the CAP may include ON durations and OFF durations. The ON durations comprise a high voltage portion of a waveform of the SIP and CAP and the OFF durations comprise a low voltage portion of a waveform of the SIP and CAP. These properties of the TAS may be used to implicitly indicate information about the CRC of the data portion of the R2D communication as described in greater detail below.

[0053] In some example embodiments, a length of an OFF duration of the R2D SIP may be used to determine the length of the CRC. For example, the device may be configured with information that correlates a length of the OFF duration of the SIP to a CRC length. For example, a first length of the OFF duration may correspond to CRC- 6 and a second length of the OFF duration may correspond to CRC-16. In some examples, the first length may be shorter than the second length but there is no requirement that the correlation be defined in this manner. When the device determines the length of the OFF duration of the SIP, the device may then determine the length of the CRC based on the configuration.Attorney Docket No. 30164 / 101702Ref. No. P70848WO1

[0054] These examples assume that a CRC is attached. However, in these examples, the device may also determine that no CRC is attached and in that case, the length of the OFF duration of the SIP is irrelevant for the purposes of CRC handling. For example, the device may determine that no CRC is attached based on the length of the PRDCH, e. g., based on the TBS indication, a postamble following the PRDCH, etc. as described above. Again, the device may be configured with information that relates a length of the PRDCH to whether a CRC is attached. When the device determines that the length of the PRDCH relates to no CRC, the device may ignore the length of the OFF duration of the SIP for the purposes of CRC handling. The length of the OFF duration of the SIP may be used for other purposes by the device.

[0055] In other examples of implicit indication of the CRC information, a pattern or sequence of the CAP of the TAS may be used to determine CRC information. The pattern or sequence may refer to a pattern or sequence of ON and OFF durations, e. g., a pattern may be a number of ON-OFF sequences, a number of ON-OFF-ON sequences, etc. that are included in the CAP.

[0056] For example, the device may be configured with information that relates two sequences of the CAP to CRC information. To provide a specific example, the first sequence may correspond to CRC-6 and the second sequence may correspond to CRC-16. When the device determines the sequence of the CAP, the device may then determine the length of the CRC based on the configuration. In one option, the configuration may include a third sequence that corresponds to no CRC. Thus, if the device determines the CAP includes the third sequence, the device mayAttorney Docket No. 30164 / 101702Ref. No. P70848WO1determine that no CRC is attached to the data portion of the PRDCH. In another option, if the third sequence is not specified, then no CRC may be determined based on the length of PRDCH, e. g., based on the TBS indication, a postamble following the PRDCH, etc. as described above.

[0057] In further examples of implicit indication of the CRC information, a length of the CAP of the TAS may be used to determine CRC information. For example, the CAP may have a single sequence but this single sequence may have different lengths. For example, the device may be configured with information that relates two lengths of the one sequence of the CAP to CRC information. To provide a specific example, the first length may correspond to CRC-6 and the second length may correspond to CRC-16. When the device determines the length of sequence of the CAP, the device may then determine the length of the CRC based on the configuration. In one option, the configuration may include a third length of the CAP sequence that corresponds to no CRC. Thus, if the device determines the CAP includes the sequence of the third length, the device may determine that no CRC is attached to the data portion of the PRDCH. In another option, if the third length is not specified, then no CRC may be determined based on the length of PRDCH, e. g., based on the TBS indication, a postamble following the PRDCH, etc. as described above. In some examples, the first length may be shorter than the second length and the third length may be shorter than both the first and second lengths. However, this is just an example and other configurations and lengths may be used.Attorney Docket No. 30164 / 101702Ref. No. P70848WO1

[0058] In some example embodiments, the device may determine whether a CRC is attached and the length of the CRC based on the type of the R2D communication. For example, the device may be configured with information that relates types of the R2D communications with CRC information. This configuration may be based on information included in standards (e.g., 3GPP TSs) or may be a per device configuration (e.g., via Radio Resource Control (RRC) configuration).

[0059] To provide some non- l imiting examples, the device may be conf igured with information indicating that ambient- IoT paging messages from a reader to one or multiple devices include an attached CRC- 1 6. Simi larly, ambient- IoT random access mes sages, e. g., mes sage from reader to one or multiple devices for signaling time-frequency resources for access occasions may also include an attached CRC-16. These are only example configurations and other CRC configurations for these messages may be used.

[0060] For ambient-IoT R2D data transmissions, there may be various configurations. For example, in a first option a CRC-6 is always attached. In a second option, the CRC information (e.g., length of CRC) may be based on the length of the R2D data transmission, e.g., based on the TBS indication or a postamble. This second option may also include a length that corresponds to no CRC. In a third option, the CRC information for the R2D data transmissions may be based on any of the various explicit or implicit signaling example embodiments described above.

[0061] The above example embodiments described various manner of determining the CRC information for R2D communications. EachAttorney Docket No. 30164 / 101702Ref. No. P70848WO1of these example embodiments may also be applied to D2R communications, e. g., the communications from an ambient-IoT device to a reader via the PDRCH. The following example embodiments provide additional manners of determining CRC information for D2R communications, e. g., how the ambient-IoT device is to attach CRC to D2R communications and how the reader is to perform CRC handling.

[0062] In some example embodiments, R2D control information may be used to explicitly indicate to the device whether CRC is used and the CRC length for D2R communications (e. g., PDRCH transmissions) in response to the PRDCH. For example, in one option, LI R2D control information may be used. In one example of this option, if the LI R2D control information is used for CRC attachment determination for PRDCH (e. g., as described in the above example embodiments), then the same indicated value may also be applied for PDRCH. For example, if the LI R2D control information indicates that CRC-6 is used for the PRDCH, any response to this R2D communication on the PDRCH should also use CRC-6.

[0063] In another example of this option, dedicated LI R2D control information may be used to explicitly indicate the CRC information to be used for the PDRCH, e. g., a bitfield may be included in the LI R2D control information that is dedicated to the PDRCH. This bitfield may be designed in a manner similar to the example bitfields described in the above example embodiments.

[0064] In another option, the control information may be signaled via Medium Access Control Control Element (MAC CE). ForAttorney Docket No. 30164 / 101702Ref. No. P70848WO1example, the reader may signal the device the CRC information for PDRCH via a MAC CE. The MAC CE may include the bitfield as described above or any other manner of indicating whether a CRC is to be used on the PDRCH and the length of the CRC, if used.

[0065] In some example embodiments, the device may implicitly determine the CRC information for the PDRCH. For example, the device may determine the CRC information for D2R communications based on TBS information signaled to the device from the reader. As described above, the device may be configured with information that relates CRC information to the TBS information, e. g., the CRC information is related to the size of the TBs in the PDRCH. The above examples described this correlation for the PRDCH. The same principles may be used for the PDRCH.

[0066] In one option, the same TBS to CRC attachment mapping may be specified for both D2R and R2D communications. In another option, separate TBS to CRC attachment mapping may specified for D2R communications and R2D communications. An example of TBS to CRC mapping is described with reference to Fig. 6.

[0067] Fig. 6 shows an example TBS to CRC mapping table 600 according to various example embodiments. In this example, the mapping table 600 has an index column and a TBS range column. In this example, a TBS of less than 20 bits corresponds to index 0, a TBS of 20-100 bits corresponds to index 1 and a TBS of greater than 100 bits corresponds to an index of 2. The indices may be defined, for example, as follows: Index 0 indicates no CRC, Index 1 indicates CRC-6 and Index 2 indicates CRC-16. Thus, once the device knows the TBS for the D2R communication (or R2D communication), the device may determine the CRC that is appliedAttorney Docket No. 30164 / 101702Ref. No. P70848WO1to the communication. As described above, the device maybe configured with a single table that applies to both R2D communications and D2R communications or there may be a separate table for each of the R2D communications and D2R communications. In addition, the R2D communications and D2R communications do not need to both apply the TBS manner of determining CRC information. For example, the device may determine the CRC information for the D2R communications using the TBS examples provided herein, while the CRC information for the R2D communications may be determined using one of the other examples provided herein, e. g., explicit signaling of CRC information.

[0068] While the above examples of the TBS being used to determine CRC information used multiple indices, in other example embodiments, only a single index may apply to when a CRC is to be attached. For example, table 600 may be modified such that Index 1 corresponds to a TBS range of greater than 20 bits and Index 1 may still correlate to CRC-6. Thus, any PDRCH that includes a CRC (e. g., those with a TBS > 20 bits ) will use CRC-6, e. g., a single length CRC is used for all PDRCH that have CRC.

[0069] In the above example embodiments of the D2R communications, the reader was aware of the size of the PDRCH. However, there may be cases where the reader is not aware of the size of the PDRCH. In some example embodiments, when the reader is not aware of the exact message size of the D2R communication, then the device may explicitly or implicitly indicate the CRC information, TBS or length of the PDRCH to the reader.Attorney Docket No. 30164 / 101702Ref. No. P70848WO1

[0070] For example, in one option, the device may indicate the CRC information, TBS or length of the PDRCH to the reader using a preamble, mid-amble or postamble of the PDRCH. In the above examples of R2D communications, it was described that a postamble may be used to indicate a length of the PRDCH.Similarly, in the PDRCH a preamble, mid-amble or postamble may be used. In another option, the PDRCH may include D2R control information that may indicate the CRC information, TBS or length of the PDRCH to the reader.

[0071] In some example embodiments, whether a CRC is attached to the D2R communications is based on whether repetitions are applied to the D2R communications. For example, in one option, if repetitions are not applied, then a CRC is attached to the PDRCH. Otherwise if repetitions are applied, then a CRC is not attached to the PDRCH. The length of the CRC may be determined based, for example, on any of the example embodiments described above.

[0072] In another option, the number of repetitions may be used to determine the CRC information for the PDRCH. For example, if up to 4 repetitions are applied, then the CRC is attached. Otherwise, for more than 4 repetitions, there is no CRC attachment. Again, the length of the CRC may be determined based, for example, on any of the example embodiments described above.

[0073] Fig. 7 shows an example method 700 of determining and using CRC information for R2D communications according to various example embodiments. The method 700 is described fromAttorney Docket No. 30164 / 101702Ref. No. P70848WO1the viewpoint of the ambient-IoT device, e. g., wireless device 112.

[0074] In 710, the ambient-IoT device receives CRC configuration information from the reader, e. g., base station 500, UE 110. Numerous examples of CRC configuration information were described above. These examples, include, but are not limited to configuration information that indicates the length of the CRC that is attached to a PRDCH data portion based on the length of the PRDCH, configuration information relating a CRC length to a PRDCH transmission type, configuration information that correlates a length of an OFF duration of a SIP to a CRC length, configuration information that relates two sequences of a CAP to CRC information, etc.

[0075] In 720, the ambient-IoT device receives the PRDCH. In 730, the ambient-IoT device determines the CRC information for the PRDCH based on the configuration information and / or the PRDCH. This CRC information may include whether a CRC is attached to the PRDCH and, if attached, the length of the CRC. As described above, the CRC information may be indicated to the ambient-IoT device explicitly or implicitly using various techniques as were described above in the example embodiments.

[0076] In 740, the ambient-IoT device may process the PRDCH based on the CRC information, e. g., if the CRC information is attached, the ambient-IoT device may use the CRC information to error check and correct the PRDCH.

[0077] Fig. 8 shows an example method 800 of determining and using CRC information for D2R communications according toAttorney Docket No. 30164 / 101702Ref. No. P70848WO1various example embodiments. The method 800 is described from the viewpoint of the ambient-IoT device, e. g., wireless device 112.

[0078] In 810, the ambient-IoT device receives CRC configuration information from the reader, e. g., base station 500, UE 110. Again, numerous examples of CRC configuration information were described above. As also described above, in some examples the CRC configuration information is the same for both R2D communications and D2R communications but in other examples the CRC configuration information is different for R2D communications and D2R communications.

[0079] In 820, the ambient-IoT device receives the PRDCH. As described above, in some example embodiments, the PRDCH may include information related to the CRC information for the PDRCH. In other example embodiments, for the purposes of CRC information of the PDRCH, the PRDCH may merely be a trigger for the ambient-IoT device to transmit the PDRCH.

[0080] In 830, the ambient-IoT device may determine the CRC information for the PDRCH. This determination may be based on the CRC configuration information, the PRDCH and / or the PDRCH. Again, the CRC information for the PDRCH may include whether a CRC is attached to the PDRCH and, if attached, the length of the CRC.

[0081] In 840, the ambient-IoT device may generate the PDRCH using the CRC information, e. g., if CRC is to be attached to the PDRCH. In 850, the ambient-IoT device may transmit the PDRCH to the reader.Attorney Docket No. 30164 / 101702Ref. No. P70848WO1

[0082] Fig. 9 shows an example method 900 of determining and using CRC information for R2D communications where the CRC for a control part and a data part of the R2D communications are different according to various example embodiments. The method 900 is described from the viewpoint of the ambient-IoT device, e. g., wireless device 112.

[0083] In 910, the ambient-IoT device receives CRC configuration information from the reader, e. g., base station 500, UE 110. Numerous examples of CRC configuration information were described above. These examples, include, but are not limited to configuration information that indicates the length of the CRC that is attached to a PRDCH data portion based on the length of the PRDCH, configuration information relating a CRC length to a PRDCH transmission type, configuration information that correlates a length of an OFF duration of a SIP to a CRC length, configuration information that relates two sequences of a CAP to CRC information, etc. In these example embodiments, the CRC configuration information may include configurations for two ( 2 ) CRCs. A first CRC that may be applied to the LI R2D control part of the PRDCH and a second CRC that may be applied to the data part of the PRDCH.

[0084] In 920, the ambient-IoT device receives the PRDCH. In 930, the ambient-IoT device determines the CRC information for the LI R2D control part of the PRDCH based on the first configuration information. This CRC information may be used to decode the LI R2D control part of the PRDCH. In some example embodiments, the CRC attached to the LI R2D control part of the PRDCH may have a fixed size, e. g. CRC-6, CRC-16, etc. In someAttorney Docket No. 30164 / 101702Ref. No. P70848WO1example embodiments, the CRC attached to LI R2D control part of the PRDCH may be determined based on, for example, the TAS as described above.

[0085] In 940, the ambient-IoT device determines the CRC information for the data part of the PRDCH based on the second configuration information and / or the information included in the LI R2D control part of the PRDCH. This CRC information may be used to decode the data part of the PRDCH. The CRC information may include whether a CRC is attached to the data part of the PRDCH and, if attached, the length of the CRC. In some example embodiments, the CRC information for the data part of the PRDCH may be indicated to the ambient-IoT device explicitly or implicitly using various techniques as were described above in the example embodiments. In other example embodiments, the CRC information for the data part of the PRDCH may be indicated to the ambient-IoT device in the LI R2D control part of the PRDCH.Examples

[0086] In a first example, a method, comprising processing, based on reader signaling, configuration information for a cyclic redundancy check (CRC) of a Physical Reader to Device Channel (PRDCH), processing, based on the reader signaling, a PRDCH communication and determining CRC information for the PRDCH communication at least based on the configuration information or the PRDCH, wherein the CRC information comprises whether a CRC is attached to the PRDCH communication or a length of the CRC when it is attached to the PRDCH communication.Attorney Docket No. 30164 / 101702Ref. No. P70848WO1

[0087] In a second example, the method of the first example, wherein the PRDCH communication comprises Layer 1 reader to device (L1 R2D) control information.

[0088] In a third example, the method of the second example, wherein the CRC information comprises information for a first CRC attached to the L1 R2D control information of the PRDCH and a second CRC attached to a data part of the PRDCH.

[0089] In a fourth example, the method of the third example, wherein the first CRC has a fixed length that is included in the configuration information.

[0090] In a fifth example, the method of the third example, wherein an R2D communication preceding the PRDCH comprises a time acquisition signal (TAS), wherein the first CRC is determined based on the TAS.

[0091] In a sixth example, the method of the second example, wherein the L1 R2D control information comprises a bitfield indicating whether the CRC is attached to the PRDCH communication.

[0092] In a seventh example, the method of the sixth example, wherein, when the bitfield indicates the CRC is attached to the PRDCH communication, the method further comprising determining the length of the CRC based on a transport block size (TBS) indicator associated with the PRDCH communication, a size indicator in a postamble of the PRDCH communication or a type of transmission of the PRDCH communication.Attorney Docket No. 30164 / 101702Ref. No. P70848WO1

[0093] In an eighth example, the method of the sixth example, wherein the bitfield further indicates the length of the CRC attached to the PRDCH communication.

[0094] In a ninth example, the method of the first example, wherein an R2D communication preceding the PRDCH comprises a time acquisition signal (TAS), wherein the CRC information is determined based on the TAS.

[0095] In a tenth example, the method of the ninth example, wherein the TAS comprises a start indicator part (SIP), wherein the length of the CRC attached to the PRDCH communication is based on a length of an OFF duration of the SIP.

[0096] In an eleventh example, the method of the tenth example, wherein whether the CRC is attached to the PRDCH communication is based on a size of the PRDCH that is determined based on a transport block size (TBS) indicator associated with the PRDCH or a postamble attached to an end of the PRDCH.

[0097] In a twelfth example, the method of the ninth example, wherein the TAS comprises a clock acquisition part (CAP).

[0098] In a thirteenth example, the method of the twelfth example, wherein the length of the CRC attached to the PRDCH communication is based on a sequence included in the CAP.

[0099] In a fourteenth example, the method of the thirteenth example, wherein whether the CRC is attached to the PRDCH communication is also based on the sequence included in the CAP.Attorney Docket No. 30164 / 101702Ref. No. P70848WO1

[0100] In a fifteenth example, the method of the thirteenth example, wherein whether the CRC is attached to the PRDCH communication is based on a transport block size (TBS) indicator associated with the PRDCH communication or a size indicator in a postamble of the PRDCH communication.

[0101] In a sixteenth example, the method of the twelfth example, wherein the length of the CRC attached to the PRDCH communication is based on a length of a sequence included in the CAP.

[0102] In a seventeenth example, the method of the thirteenth example, wherein whether the CRC is attached to the PRDCH communication is also based on the length of the sequence included in the CAP.

[0103] In an eighteenth example, the method of the seventeenth example, wherein whether the CRC is attached to the PRDCH communication is based on a transport block size (TBS) indicator associated with the PRDCH communication or a size indicator in a postamble of the PRDCH communication.

[0104] In a nineteenth example, the method of the first example, wherein the CRC configuration information comprises a correlation between a PRDCH type and CRC information for each PRDCH type included in the CRC configuration, wherein the CRC information for the PRDCH communication is determined based on the CRC configuration information and a type of the PRDCH communication.Attorney Docket No. 30164 / 101702Ref. No. P70848WO1

[0105] In a twentieth example, the method of the nineteenth example, wherein, when the PRDCH type of the PRDCH communication comprises a paging message from the reader or a random access message from the reader signaling resources for a random access occasion, the CRC information comprises that the CRC is attached to the PRDCH communication and the length of the CRC.

[0106] In a twenty first example, the method of the nineteenth example, wherein, when the PRDCH type of the PRDCH communication comprises a data message from the reader, the CRC information comprises that the CRC is attached to the PRDCH communication and the length of the CRC.

[0107] In a twenty second example, the method of the nineteenth example, wherein, when the PRDCH type of the PRDCH communication comprises a data message from the reader, the CRC information is based on a transport block size ( TBS ) indicator associated with the PRDCH communication or a size indicator in a postamble of the PRDCH communication.

[0108] In a twenty third example, the method of the first example, further comprising determining second CRC information for a Physical Device to Reader Channel ( PDRCH) communication sent in response to the PRDCH communication and generating, for transmission to the reader, the PRDCH communication based on the CRC information.

[0109] In a twenty fourth example, the method of the twenty third example, wherein the PRDCH communication comprises Layer 1 reader to device (L1 R2D) control information, wherein theAttorney Docket No. 30164 / 101702Ref. No. P70848WO1second CRC information is determined based on the L1 R2D control information.

[0110] In a twenty fifth example, the method of the twenty fourth example, wherein the L1 R2D control information comprises a bitfield indicating whether a CRC is attached to the PDRCH communication.

[0111] In a twenty sixth example, the method of the twenty fifth example, wherein, when the bitfield indicates the CRC is attached to the PDRCH communication, the method further comprising determining the length of the CRC based on a transport block size (TBS) indicator associated with the PDRCH communication, a size indicator in a postamble of the PDRCH communication or a type of transmission of the PDRCH communication.

[0112] In a twenty seventh example, the method of the twenty fifth example, wherein the bitfield further indicates the length of the CRC attached to the PDRCH communication.

[0113] In a twenty eighth example, the method of the twenty fourth example, wherein the L1 R2D control information of the PRDCH comprises common CRC information for the PRDCH communication and the PDRCH communication.

[0114] In a twenty ninth example, the method of the twenty fourth example, wherein the L1 R2D control information of the PRDCH comprises dedicated CRC information for the PRDCH communication and dedicated second CRC information for the PDRCH communication.Attorney Docket No. 30164 / 101702Ref. No. P70848WO1

[0115] In a thirteith example, the method of the twenty third example, wherein the PRDCH communication comprises a Medium Access Control Control Element (MAC CE), wherein the second CRC information is determined based on the MAC CE.

[0116] In a thirty first example, the method of the thirtieth example, wherein the MAC CE comprises a bitfield indicating whether a CRC is attached to the PDRCH communication.

[0117] In a thirty second example, the method of the thirty first example, wherein, when the bitfield indicates the CRC is attached to the PDRCH communication, the method further comprising determining the length of the CRC based on a transport block size (TBS) indicator associated with the PDRCH communication, a size indicator in a postamble of the PDRCH communication or a type of transmission of the PDRCH communication.

[0118] In a thirty third example, the method of the thirty first example, wherein the bitfield further indicates the length of the CRC attached to the PDRCH communication.

[0119] In a thirty fourth example, the method of the twenty third example, wherein the second CRC information is determine based on a transport block size (TBS) indicator associated with the PDRCH communication.

[0120] In a thirty fifth example, the method of the thirty fourth example, wherein a mapping between the TBS indicator and the second CRC information for the PDRCH is the same as aAttorney Docket No. 30164 / 101702Ref. No. P70848WO1mapping between the TBS indicator and the CRC information for the PRDCH.

[0121] In a thirty sixth example, the method of the thirty fourth example, wherein a mapping between the TBS indicator and the second CRC information for the PDRCH is different from a mapping between the TBS indicator and the CRC information for the PRDCH.

[0122] In a thirty seventh example, the method of the twenty third example, wherein the PDRCH communication further comprises the second CRC information, a size of the PDRCH communication or a transport block size ( TBS ) indicator associated with the PDRCH communication.

[0123] In a thirty eighth example, the method of the thirty seventh example, wherein the second CRC information, the size of the PDRCH communication or the TBS indicator is included in one of a preamble, a mid-amble or a postamble of the PDRCH communication.

[0124] In a thirty ninth example, the method of the thirty seventh example, wherein the second CRC information, the size of the PDRCH communication or the TBS indicator is included in D2R control information.

[0125] In a fortieth example, the method of the twenty third example, wherein the second CRC information is based on repetitions applied to the PDRCH communication.Attorney Docket No. 30164 / 101702Ref. No. P70848WO1

[0126] In a forty first example, the method of the fortieth example, wherein, when repetitions are applied, a CRC is not attached to the PDRCH communication and, when repetitions are not applied a CRC is attached to the PDRCH communication.

[0127] In a forty second example, the method of the fortieth example, wherein whether a CRC is attached to the PDRCH communication is based on a number of repetitions applied to the PDRCH communication.

[0128] In a forty third example, a processor configured to perform any of the methods of the first through forty second examples.

[0129] In a forty fourth example, a wireless device configured to perform any of the methods of the first through forty second examples.

[0130] In a forty fifth example, a method comprising processing a transport block for a reader-to-device (R2D) or device-to-reader (D2R) communication, determining a size of the transport block or a payload size of the transport block; and determining a Cyclic Redundancy Check (CRC) length for the transport block based on the size of the transport block or the payload size, wherein the CRC length is determined to be a first length when the of the transport block or the payload size is greater than a threshold, and a second length when the of the transport block or the payload size is equal to or less than the threshold.Attorney Docket No. 30164 / 101702Ref. No. P70848WO1

[0131] In a forty sixth example, the method of the forty fifth example, wherein the D2R communication is a Physical Device to Reader Channel (PDRCH), and the CRC is attached to the transport block prior to block repetition.

[0132] In a forty seventh example, the method of the forty fifth example, wherein the R2D communication is a Physical Reader to Device Channel (PRDCH).

[0133] In a forty eighth example, the method of the forty fifth example, wherein determining the CRC length is based on a mapping table where different ranges of the of the transport block or the payload size correspond to different CRC types.

[0134] In a forty ninth example, a processor configured to perform any of the methods of the forty fifth through forty eighth examples.

[0135] In a fiftieth example, a wireless device configured to perform any of the methods of the forty fifth through forty eighth examples.

[0136] In a fifty first example, a reader device configured to perform any of the methods of the forty fifth through forty eighth examples.

[0137] Those skilled in the art will understand that the above-described example embodiments may be implemented in any suitable software or hardware configuration or combination thereof. An example hardware platform for implementing the example embodiments may include, for example, an Intel x86 basedAttorney Docket No. 30164 / 101702Ref. No. P70848WO1platform with compatible operating system, a Windows OS, a Mac platform and MAC OS, a mobile device having an operating system such as iOS, Android, etc. The example embodiments of the above described method may be embodied as a program containing lines of code stored on a non-transitory computer readable storage medium that, when compiled, may be executed on a processor or microprocessor.

[0138] Although this application described various embodiments each having different features in various combinations, those skilled in the art will understand that any of the features of one embodiment may be combined with the features of the other embodiments in any manner not specifically disclaimed or which is not functionally or logically inconsistent with the operation of the device or the stated functions of the disclosed embodiments.

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

[0140] It will be apparent to those skilled in the art that various modifications may be made in the present disclosure, without departing from the spirit or the scope of the disclosure. Thus, it is intended that the present disclosure cover modifications and variations of this disclosure providedAttorney Docket No. 30164 / 101702Ref. No. P70848WO1they come within the scope of the appended claims and their equivalent.

Claims

Attorney Docket No. 30164 / 101702Ref. No. P70848WO1What is claimed:

1. An apparatus comprising memory coupled to processing circuitry, the processing circuitry configured to:process a transport block for a reader-to-device (R2D) or device- to-reader (D2R) communication;determine a size of the transport block or a payload size of the transport block; anddetermine a Cyclic Redundancy Check (CRC) length for the transport block based on the size of the transport block or the payload size, wherein the CRC length is determined to be a first length when the of the transport block or the payload size is greater than a threshold, and a second length when the of the transport block or the payload size is equal to or less than the threshold.

2. The apparatus of claim 1, wherein the D2R communication is a Physical Device to Reader Channel (PDRCH), and the CRC is attached to the transport block prior to block repetition.

3. The apparatus of claim 1, wherein the R2D communication is a Physical Reader to Device Channel (PRDCH).

4. The apparatus of claim 1, wherein determining the CRC length is based on a mapping table where different ranges of the of the transport block or the payload size correspond to different CRC types.

5. An apparatus comprising memory coupled to processing circuitry, the processing circuitry configured to:Attorney Docket No. 30164 / 101702Ref. No. P70848WO1process, based on reader signaling, configuration information for a cyclic redundancy check (CRC) of a Physical Reader to Device Channel (PRDCH);process, based on the reader signaling, a PRDCH communication; anddetermine CRC information for the PRDCH communication at least based on the configuration information or the PRDCH, wherein the CRC information comprises whether a CRC is attached to the PRDCH communication or a length of the CRC when it is attached to the PRDCH communication.

6. The apparatus of claim 5, wherein the PRDCH communication comprises Layer 1 reader to device (L1 R2D) control information.

7. The apparatus of claim 6, wherein the CRC information comprises information for a first CRC attached to the L1 R2D control information of the PRDCH and a second CRC attached to a data part of the PRDCH.

8. The apparatus of claim 6, wherein the L1 R2D control information comprises a bitfield indicating whether the CRC is attached to the PRDCH communication.

9. The apparatus of claim 8, wherein, when the bitfield indicates the CRC is attached to the PRDCH communication, the processing circuitry is further configured to:determine the length of the CRC based on a transport block size (TBS) indicator associated with the PRDCH communication, a size indicator in a postamble of the PRDCH communication or a type of transmission of the PRDCH communication.Attorney Docket No. 30164 / 101702Ref. No. P70848WO110. The apparatus of claim 5, wherein an R2D communication preceding the PRDCH comprises a time acquisition signal ( TAS ), wherein the CRC information is determined based on the TAS.

11. The apparatus of claim 10, wherein the TAS comprises a start indicator part ( SIP), wherein the length of the CRC attached to the PRDCH communication is based on a length of an OFF duration of the SIP.

12. The apparatus of claim 10, wherein the TAS comprises a clock acquisition part (CAP), wherein the length of the CRC attached to the PRDCH communication is based on a sequence included in the CAP.

13. The apparatus of claim 5, wherein the CRC configuration information comprises a correlation between a PRDCH type and CRC information for each PRDCH type included in the CRC configuration, wherein the CRC information for the PRDCH communication is determined based on the CRC configuration information and a type of the PRDCH communication.

14. The apparatus of claim 13, wherein, when the PRDCH type of the PRDCH communication comprises a paging message from the reader or a random access message from the reader signaling resources for a random access occasion, the CRC information comprises that the CRC is attached to the PRDCH communication and the length of the CRC.

15. The apparatus of claim 13, wherein, when the PRDCH type of the PRDCH communication comprises a data message from theAttorney Docket No. 30164 / 101702Ref. No. P70848WO1reader, the CRC information comprises that the CRC is attached to the PRDCH communication and the length of the CRC.

16. The apparatus of claim 13, wherein, when the PRDCH type of the PRDCH communication comprises a data message from the reader, the CRC information is based on a transport block size ( TBS ) indicator associated with the PRDCH communication or a size indicator in a postamble of the PRDCH communication.

17. The apparatus of claim 5, wherein the processing circuitry is further configured to:determine second CRC information for a Physical Device to Reader Channel (PDRCH) communication sent in response to the PRDCH communication; andgenerate, for transmission to the reader, the PRDCH communication based on the CRC information.

18. The apparatus of claim 23, wherein the PRDCH communication comprises Layer 1 reader to device (L1 R2D) control information, wherein the second CRC information is determined based on the L1 R2D control information.

19. The apparatus of claim 18, wherein the L1 R2D control information comprises a bitfield indicating whether a CRC is attached to the PDRCH communication.

20. The apparatus of claim 19, wherein, when the bitfield indicates the CRC is attached to the PDRCH communication, the processing circuitry is further configured to:determine the length of the CRC based on a transport block size ( TBS ) indicator associated with the PDRCH communication, aAttorney Docket No. 30164 / 101702Ref. No. P70848WO1size indicator in a postamble of the PDRCH communication or a type of transmission of the PDRCH communication.

Images