Techniques for data transmission in ambient devices

Abstract

A method for data transmission in a wireless network includes encoding a first preamble for a sequence of data packets by an Ambient Internet of Things (A-IoT) device, generating a data packet for the sequence of data packets, and encoding multiple repetitions of the data packet for the sequence of data packets according to a number of repetitions in the sequence of data packets to a reader.

Description

TECHNIQUES FOR DATA TRANSMISSION IN AMBIENT DEVICESCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of and priority to previously filed U.S. Provisional Application 63 / 554,816, filed February 16, 2024 entitled - REPETITION OF DATA TRANSMISSION FOR AMBIENT - INTERNET OF THINGS (A-IOT) APPLICATIONS” and U.S. Provisional Application 63 / 676,795. filed July 29, 2024 entitled ‘REPETITION OF DATA TRANSMISSION FOR AMBIENT - INTERNET OF THINGS (A-IOT) APPLICATIONS”, the contents of both which are herein incorporated by reference in their entirety.BACKGROUND

[0002] Internet of Thing (loT) devices have evolved to encompass a diverse range of applications, such as smart homes, smart cities, and healthcare monitoring. Ambient Internet of Things (A-IoT) devices typically have limited size with limited energy storage that do not need to be replaced or recharged manually. In this case, the output power of energy' harvester is ty pically from IpW to a few hundreds of pW. Existing cellular devices may not work well with energy harvesting due to their peak power consumption of higher than lOmW. Communication issues arise due to extremely low cost and low complexity transceiver architecture of A-IoT devices. There is a need for an improved process of data transmission to and from A-IoT devices to reduce communication failures.BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

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

[0004] FIG 1 illustrates a wireless net^vork in accordance with one embodiment.

[0005] FIG. 2 illustrates data transmission in accordance with one embodiment.

[0006] FIG. 3 illustrates data transmission in accordance with one embodiment.

[0007] FIG. 4 illustrates data transmission in accordance with one embodiment.

[0008] FIG. 5 illustrates data transmission in accordance with one embodiment.

[0009] FIG. 6 illustrates data transmission in accordance with one embodiment.

[0010] FIG. 7 illustrates data transmission in accordance with one embodiment.

[0011] FIG. 8 illustrates modulation signal durations of chip rates in accordance with one embodiment.

[0012] FIG. 9 illustrates modulation signal durations of chip rates in accordance with one embodiment.

[0013] FIG. 10 illustrates a data signal frame format that supports variable chip rates in accordance with one embodiment.

[0014] FIG. 11 illustrates a data signal frame format that supports variable chip rates in accordance with one embodiment.

[0015] FIG. 12 illustrates a logic flow in accordance with one embodiment.

[0016] FIG. 13 illustrates a logic flow in accordance with one embodiment.

[0017] FIG. 14 illustrates a network architecture in accordance with one embodiment.

[0018] FIG. 15 illustrates wireless network in accordance with one embodiment.

[0019] FIG. 16 illustrates an apparatus in accordance with one embodiment.

[0020] FIG. 17 illustrates a computer readable storage medium in accordance with one embodiment.DETAILED DESCRIPTION

[0021] Embodiments are generally directed to data transmission in ambient devices. Some embodiments are particularly directed to improving the success rate of data transmission involving ambient devices by encoding multiple copies of a data packet in a transmission. The data transmissions can include bidirectional communication between a base station and an ambient device, such as an A-IoT device. The data transmissions can also be between the base station and ambient device via an intermediate node, where the intermediate node passes the messages between the base station and ambient device. The transmitter, which can be the base station, intermediate node, or ambient device, encodes a preamble for a sequence of data packets, generates a data packet for the sequence of data packets, and encodes multiple copies of the data packet according to a defined number of repetitions. Each copy of the data packet is self-decodable so that only one copy of the data packet needs to be successfully decoded by the receiver for the transmission to be successful. The data transmission can optionally include a control message between the preamble and the first copy of the data packet, and / or a copy of the preamble and / or control message preceding each copy of the data packet. The defined number of repetitions of the data packet can be identified in the preamble and / or control message. The data transmission can include a postamble encoded after the last copy of the data packet to indicate the end of the data transmission.

[0022] Ambient devices may be limited to half-duplex constraints, e.g.. they may not be able to transmit and receive simultaneously, even on different frequencies that may be separated by a duplex gap. To address this limitation and reduce the number of excess copies of data packets transmitted after the data packet has been successfully decoded, pauses may be taken between the encoding of the data packet copies. For example, after a group of a defined number of copies of the data packet are encoded, the encoding may be paused for a defined period of time to open the communication channel to receive an acknowledgment message confirming that the data packet has been successfully decoded. If an acknowledgment message is received, then the encoding is terminated. Otherwise, following the pause, another group of a defined number of data packet copies is encoded followed by another pause, and so on until the total number of encoded copies reaches the defined number of copies or an acknowledgment message is decoded.

[0023] In some embodiments, the transmitter may decode a received message that includes an indication of a chip rate of a receiver. The transmitter can determine the chip rate using the indication and subsequently encode messages based on the chip rate.

[0024] In Third Generation Partnership Project (3GPP), various connectivity technologies tailored to loT requirements were introduced. In particular, Low Power, Wide-Area (LPWA) Technologies such as Narrowband loT (NB-IoT) and LTE-M were specified to address the specific needs of low-power devices, extending the battery life of loT devices and enabling their use in remote or hard-to-reach locations. Given that existing technologies cannot meet all the requirements of target use cases such as asset identification, inventory, sensing, etc., A-IoT technology is recommended in the 3 GPP Release 19 (Rel-19) to open new markets within 3GPP systems, whose number of connections and / or device density can be orders of magnitude higher than existing 3GPP loT technologies. The new loT technology will provide complexity and power consumption orders of magnitude lower than the existing 3GPP LPWA technologies and shall address use cases and scenarios that cannot otherwise be fulfilled based on existing 3GPP LPWA loT technologies.

[0025] Various 3GPP documents define A-IoT technology and physical layer procedures, including 3GPP Technical Standards (TS), Technical Reports (TR), Change Requests (CR), and / or Work Items (WI). Various embodiments discussed herein may implement the physical layer standards as defined by the 3GPP TS 38.212 standard titled “NR; Multiplexing and Channel Coding,’7Release 18, Version 18.4.0 (September 2024). and including future versions or variants (collectively referred to as “3GPP TS 38.212 Standards”). The 3GPP TS 38.212 specifies defines uplink and downlink transport channels and control information. Various embodiments discussed herein may implement the physical layer standards as definedby the 3GPP TS 38.214 standard titled "NR; Physical Layer Procedures for Data,” Release 18, Version 18.4.0 (September 2024), and including future versions or variants (collectively referred to as “3GPP TS 38.214 Standards”). The 3GPP TS 38.214 specifies procedures for physical uplink and downlink shared channels. It may be appreciated that the embodiments may be implemented in accordance with other 3 GPP TS, TR. CR, and WI as well as other wireless standards released by other standards entities. Embodiments are not limited in this context.

[0026] The present disclosure will now be described with reference to the attached drawing figures, wherein like reference numerals are used to refer to like elements throughout, and wherein the illustrated structures and devices are not necessarily drawn to scale. As utilized herein, terms "component." “system,” “interface,” and the like are intended to refer to a computer-related entity, hardware, software (e.g., in execution), and / or firmware. For example, a component can be a processor (e.g., a microprocessor, a controller, or other processing device), a process running on a processor, a controller, an object, an executable, a program, a storage device, a computer, a tablet PC and / or a user equipment (e.g., mobile phone, etc.) with a processing device. By way of illustration, an application running on a server and the server can also be a component. One or more components can reside within a process, and a component can be localized on one computer and / or distributed between two or more computers. A set of elements or a set of other components can be described herein, in which the term “set” can be interpreted as “one or more.”

[0027] Further, these components can execute from various computer readable storage media having various data structures stored thereon such as with a module, for example. The components can communicate via local and / or remote processes such as in accordance with a signal having one or more data packets (e.g.. data from one component interacting with another component in a local system, distributed system, and / or across a network, such as, the Internet, a local area netw ork, a wide area network, or similar network with other systems via the signal).

[0028] As another example, a component can be an apparatus with specific functionality provided by mechanical parts operated by electric or electronic circuitry, in which the electric or electronic circuitry can be operated by a software application or a firmw are application executed by one or more processors. The one or more processors can be internal or external to the apparatus and can execute at least a part of the software or firmware application. As yet another example, a component can be an apparatus that provides specific functionality through electronic components without mechanical parts; the electronic components caninclude one or more processors therein to execute software and / or firmware that confer(s). at least in part, the functionality of the electronic components.

[0029] Use of the word exemplary is intended to present concepts in a concrete fashion. As used in this application, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or”. That is, unless specified otherwise, or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then “X employs A or B” is satisfied under any of the foregoing instances. In addition, the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form. Furthermore, to the extent that the terms “including”, “includes”, “having”, “has”, “with”, or variants thereof are used in either the detailed description and the claims, such terms are intended to be inclusive in a manner similar to the term “comprising.” Additionally, in situations wherein one or more numbered items are discussed (e.g., a “first X”, a “second X”, etc.), in general the one or more numbered items may be distinct or they may be the same, although in some situations the context may indicate that they are distinct or that they are the same.

[0030] As used herein, the term “circuitry” may refer to, be part of, or include a circuit, an integrated circuit (IC), a monolithic IC, a discrete circuit, a hybrid integrated circuit (HIC), an Application Specific Integrated Circuit (ASIC), an electronic circuit, a logic circuit, a microcircuit, a hybrid circuit, a microchip, a chip, a chiplet, a chipset. a multi-chip module (MCM), a semiconductor die, a system on a chip (SoC), a processor (shared, dedicated, or group), a processor circuit, a processing circuit, or associated memory (shared, dedicated, or group) operably coupled to the circuitry that execute one or more software or firmware programs, a combinational logic circuit, or other suitable hardware components that provide the described functionality. In some embodiments, the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules. In some embodiments, circuitry' may include logic, at least partially operable in hardware.

[0031] FIG. 1 illustrates example topologies of a wireless network 100, namely a first topology 102 and a second topology 104, utilized by at least one ambient device for data communication. For purposes of convenience and without limitation, the example wireless network 100 is described in the context of the long-term evolution (LTE), fifth generation (5G) new radio (NR) (5G NR), and sixth generation (6G) cellular networks communication standards as defined by one or more 3GPP TS 38.133 Standards, 3GPP 38.330 Standards,3GPP 38.331 Standards, or other 3GPP standards or specifications. It is understood that the wireless network 100 can adhere to other types of wireless standards as well.

[0032] Both illustrated topology examples of the wireless network 100 includes a base station 106 and an ambient device 108. In the first topology 102. the ambient device 106 directly and bidirectionally communicates with the base station 106. The communication between the base station 106 and the ambient device 108 includes ambient loT data and / or signaling. The base station 106 can include a component functioning as a base station in a wireless network, such as a gNodeB (gNB) in a 5G wireless network. The ambient device 108 is a device with energy storage capabilities that is configured for wireless connection to one or more networks. The ambient device 108 can be limited to low power consumption, such as less than or equal to IpW or lOpW during transmitting or receiving. Ambient devices 108 include A-IoT devices. Some ambient devices 108 can harvest ambient energy from radio waves, light, motion, heat, or any other viable energy source, such as A-IoT device types 1 and 2a. Some ambient devices 108, such as A-IoT device type 2b, may or may not harvest energy. Accordingly, the ambient device 108 operates on a limited amount of energy' and has a low complexity transceiver architecture that limits its ability to successfully encode and transmit or decode data in data transmissions. Ambient devices 108 can include, for example and without limitation, sensors, controls, wearable devices, and other simple electronic devices. The A-IoT device can include an A-IoT ty pe 1 device, an A-IoT type 2a device, or an A-IoT ty pe 2b device. An A-IoT type 1 device has about 1 pW peak power consumption, energy storage, initial sampling frequency offset (SFO) up to 10xppm, and neither downlink (DL) nor uplink (UL) amplification in the device. An A-IoT type 1 device’s UL transmission is backscattered on a carrier wave provided externally. An A-IoT type 2a device has less than or equal to a few hundred pW peak power consumption, has energy storage, initial sampling frequency offset (SFO) up to 10xppm, both DL and / or UL amplification in the device. An A- loT type 2a device’s UL transmission is backscattered on a carrier wave provided externally. An A-IoT type 2b device has less than or equal to a few hundred pW peak power consumption, has energy' storage, initial sampling frequency offset (SFO) up to 10xppm, both DL and / or UL amplification in the device. An A-IoT ty pe 2b device's UL transmission is generated internally by the device.

[0033] In the second topology 104, the ambient device 108 communicates bidirectionally with an intermediate node 110 between the ambient device 106 and base station 106. The intermediate node 110 can be, for example, a relay, Integrated Access and Backhaul (I AB) node, user equipment (UE), repeater, or another device known in the art that is capable of A- loT. UE can include, without limitation, a personal computer, a network appliance, aworkstation, a phone, a handheld PC. a personal digital assistant, a thin client, a fat client, smartphone, tablet, or like wearable mobile device. The intermediate node 110 transfers ambient loT data and / or signaling between the base station 106 and the ambient device 108. Specifically, the intermediate node 110 decodes data communications from the base station 106 or ambient device 108 and encodes the decoded data communications for transmission to the ambient device 108 or base station 106, respectively.

[0034] Due to extremely low cost and low complexity transceiver architecture of ambient devices 108. the communication range between base station 106 and ambient device 108 as deployed according to the first topology 102 and the communication range between the intermediate node 110 and the ambient device 108 as deployed in the second topology 104 can be limited. However, for certain A-IoT applications, including inventory' use case, it is envisioned that the maximum distance of 10-50 meters for ambient devices 108 operating indoors needs to be designed. To ensure that A-IoT system can meet the coverage target, certain mechanisms may need to be considered for the transmission of a data channel for A- loT applications.

[0035] Various embodiments herein include systems and methods for repetition of data transmission for ambient devices 108 including A-IoT applications. For example, aspects of various embodiments include repetition of data transmission in ambient devices and data transmission based on a chip rate indication of ambient devices.

[0036] In this disclosure, unless mentioned explicitly, the disclosed embodiments and examples may apply to data communications in the first topology7102 and the second topology7104. The following discussion of embodiments and examples of data transmission will be described primarily as data encoded and transmitted by base station 106, as shown in FIG. 1, and decoded by' ambient device 108. However, it is understood that the described data transmissions can be encoded and transmitted by ambient device 108 and decoded by base station 106 and / or that the data transmissions can transmitted via intermediate node 110, as shown in the first topology 102 of FIG. 1, without diverting from the described subject matter. Specifically, as the described embodiments and examples can be deployed in the second topology' 104, the data transmissions can be encoded by the base station 106 or ambient device 108, decoded and encoded by the intermediate node 110, and then decoded by the ambient device 108 or base station 106, respectively. Accordingly, although the following descriptions are primarily presented in terms of the base station 1 6 to ambient device 108 link, they can be applicable to the intermediate node 110 to ambient device 108 link. It is understood that, unless otherwise stated, all data transmissions described herein can be data exchanged between ambient device 108 and a reader, which can be the base station 106 or theintermediate node 110. For example, ambient device 108 can encode data that is transmitted to another ambient device that decodes the received data, ambient device 108 can encode data that is transmitted to a reader that decodes the received data, or a reader can encode data that is transmitted to ambient device 108 that decodes the received data. Unless otherwise stated, features described in different embodiments and examples can be combined. For example, it is understood that descriptions of an embodiment of a data transmission with a control message, an embodiment with a postamble, and an embodiment with a preamble before each repetition of a data packet discloses that a data transmission can include a control message, a postamble, and / or preamble before each repetition of a data packet.

[0037] Consecutive repetitions of a data packet can be transmitted after a preamble. The number of repetitions or maximum number of repetitions and / or the length of each repetition of data packet can be indicated by the associated preamble. For each repetition, the same modulated data with equal length is transmitted.

[0038] The data field that is repeated can be a minimum self-decodable unit of information with defined coding and modulation. For example, each copy of the data field can include a Cyclic Redundancy Check (CRC) attachment, which the receiver can use to determine if the decoded data packet includes errors. As the data field is self-decodable, any received copy of the data field can be interpreted and decoded regardless of whether any other portions of the data transmission were successfully received. In favorable transmission environments, e.g. good receive signal to noise ratio (SNR), the receiver may be able to perform decoding based on a single instance of the data field without leveraging the data field repetitions. Tn non- favorable transmission environments, the receiver may need multiple instances of the data field repetition to correctly decode the data packet.

[0039] Because the data field is set to a defined coding and modulation, the data payload size that can be sent in the data field will be fixed. Variable information payload could be supported by using padding bits to the information payload to create the data payload that will be sent over the data field of the transmission, thus including the padding bits in each of the repeated data packets.

[0040] FIG. 2 illustrates a data transmission in a wireless network involving one or more ambient devices, such as ambient device 108 shown in FIG. 1. FIG. 2 shows blocks representing a preamble 202 and repetitions of a data packet 204 on a timeline increasing from left to right representing the order of generation and transmission. In other words, blocks on the left are generated and transmitted before blocks to the right. A defined number ‘N’ of repetitions of data packet 204, also referred to herein as data field, in the sequence of datapackets 204 are included in the payload, which are identified in FIG. 2 as repetition #0 data packet 204, repetition #1 data packet 204, and so on through repetition #N-1 data packet 204. ‘N’ for data communications with a specific ambient device can be defined based on the link performance of device to reader (D2R) transmission from the ambient device and reader to device (R2D) transmission to the ambient device. The value of ‘N’ can be defined as any integer, such as 2, 4, 6, or 8. In some embodiments, ‘N’ may be adjusted based on the link performance of device to reader (D2R) transmission from ambient device 108 and reader to device (R2D) transmission to ambient device 108. For example, if ambient device 108 is encodingCN’ copies of data packet 204 and none of the copies are successfully decoded or if 'N’ copies of the data packet 204 are transmitted to the ambient device 108 and the ambient device does not successfully decode any of the copies, then the reader, such as base station 106, and / or intermediate node 110 may increase the value of ‘N’.

[0041] The preamble 202 can include a unique sequence that is easily discernable to identify the preamble 202. Preamble 202 can carry information on ‘N’, the defined number of repetitions of data packet 204 that will follow the preamble 202. Preamble 202 can also include a maximum number of repetitions of the data packet 204, the length of each repetition of the data packet 204. the total length of the data packets 204 combined, and / or the total length of the data transmission. The data packet 204 contains the information payload and can include up to a maximum of 1,000 bits. Each encoded repetition of the data packet 204 can include the same modulated data and have equal length. Encoding copies of data packet 204 provides redundant transmission of the information pay load to ensure at least one copy of the data packet 204 was successfully transmitted and decoded. The reader, which can include the base station 106, encodes the preamble 202 for a sequence of data packets 204.

[0042] The reader, which can include the base station 106. then generates data packet 204 and encodes multiple copies of the data packet 204 for the sequence of data packets 204 according to ‘N’. Further, the repetitions of data packet 204 can be mapped to consecutively occurring time resources available for transmission to ambient device 108.

[0043] Because each copy of the data packet 204 is self-decodable, only one copy of the data packet 204 needs to be decoded for the data transmission to be successful. In some embodiments, the receiver may be successful in encoding a first portion of one copy and a second portion of another copy of the data packet 204 that the receiver can combine to generate a complete decoded copy of the data packet 204. In this aspect, the data transmission can still be successful even if the receiver was unable to decode the data field from a single copy of the data packet 204.

[0044] FIG. 3 illustrates a data transmission including a preamble 202 and a control 302, also referred to as a control message. The reader including base station 106 can generate the control 302 directly following the preamble 202 and before the first repetition of the data packet 204, identified in FIG. 3 as repetition #0. No gap is inserted between repetitions of the data packet 204. There may also be no gaps inserted between the preamble 202 and the control 302 and between the control 302 and the first repetition of the data packet 204. In some embodiments, information that would otherwise be included in the preamble 202 can instead or additionally be included in the control 302, such as the number of repetitions of the data packet 204, a maximum number of repetitions of the data packet 204, the length of each repetition of the data packet 204, the total length of the data packets 204 combined, and / or the total length of the data transmission.

[0045] FIG. 3 illustrates one example of repetition of data transmission. As shown. ‘N’ repetitions are applied for the data transmission, where ‘N’ is indicated in the control 302 before the first repetition of the data packet 204, identified in FIG. 3 as repetition #0.

[0046] FIG. 4 illustrates an example of data transmission including a postamble 402 at the end of the transmission. Consecutive repetitions of data packet 204 are transmitted after the preamble 202 and before the postamble 402. The length of each repetition of data packet 204 can be indicated by the preamble 202. In some embodiments, the preamble 202 may not include an indication of the number of repetitions of the data packet 204. The postamble 402 may be used to indicate the termination of the repetition of data packets 204. In embodiments, the data transmission can also include the control 302, as shown in FIG. 3, and consecutive repetitions of the data packet 204 are transmitted after the control 302 and the preamble 202 and before the postamble 402. In this example, the length of each repetition of the data packet 204 can be indicated by the associated control 302 and / or preamble 202. For each repetition, the same modulated data with equal length is transmitted.

[0047] FIG. 5 illustrates a data transmission with multiple preambles, where a preamble is inserted before each repetition of the data packet 204. The length of each repetition of the data packet 204 can be indicated in the first preamble 202. In this embodiment, the first repetition of the data packet 204, namely repetition #0, follows the first preamble 202 and all subsequent repetitions of the data packet 204, namely repetition #1 data packet 204 through repetition #N-1 data packet 204, are each preceded by a preamble 502, which is also referred to herein is a midamble.

[0048] The subsequent preambles 502 can be copies of the first preamble 202, in w hich case each repetition includes both a copy of preamble 202 and data packet 204. Further, no gap isinserted between repetitions. In other embodiments, the subsequent preambles 502, or midambles, may not be identical to the first preamble 202.

[0049] The number of repetitions or maximum number of repetitions and / or the length of each repetition of data packet 204 can be indicated by the associated preamble or the first preamble 202. For each repetition, the same modulated data with equal length is transmitted. Further, the preamble in each repetition may be used to indicate the repetition index for the respective data packet 204. The repetition may indicate which copy the respective data packet 204 is, such as first, second, third, etc. A control message, such as control 302 shown in FIG. 3, may be inserted between the preamble 202 and the first data packet 204 or between each preamble 202, 502 and respective data packet 204. The number of repetitions or maximum number of repetitions and / or the length of each repetition of data packet can be indicated by the associated preamble and / or control 302 and / or the first associated preamble or control 302. Further, the preamble 202, 502 and / or control 302 in each repetition may be used to indicate the repetition index for the data packet.

[0050] In some embodiments, a postamble, such as postamble 402 shown in FIG. 4. may be transmitted after each repetition of the data packet 204 or the last repetition of data packets 204. The postamble 402 may be used to indicate the termination of repetition of data transmission.

[0051] FIG. 6 illustrates an example of data transmission with non-consecutive repetitions of data packets 204 separated by pauses. ‘N’ repetitions are applied for the data transmission, where each repetition includes a copy of the preamble 202 followed by a copy of the data packet 204. Copies of the preamble 202 after the initial copy are shown in FIG. 6 as preambles 502, which may be identical to the first preamble 202. As described herein, the preamble in each repetition may be used to indicate the repetition index for the respective data packet 204. Encoding copies of the preamble 202 and the data packet 204 are paused after a number of copies for a defined period of time, and so on until the earlier of ‘N’ repetitions have been encoded or an acknowledgement (ACK) message 604 is decoded. A preamble 602 may precede the ACK message 604.

[0052] In some embodiments, a control message, such as control 302 shown in FIG. 3, may be included between the preamble 202 (or preamble 502) and data packet 204 for each repetition or only the first repetition. The number of repetitions or maximum number of repetitions and / or the length of each repetition of the data packet 204 can be indicated by the associated preamble and / or control message and / or the first associated preamble or control message. A postamble, such as postamble 402 shown in FIG. 4, may be inserted after eachrepetition or only the last repetition. Further, the postamble may be used to indicate the termination of each repetition or the last repetition of data transmission.

[0053] Ambient devices, such as A-IoT devices, may be limited to half-duplex constraints, e.g., they may not be able to transmit and receive simultaneously, even on different frequencies that may be separated by a duplex gap. To address such cases, time gaps may be inserted after every ‘R’ repetitions to pause encoding by the ambient device and provide an opportunity' for the ambient device to encode and transmit an acknowledgement in case of successful decoding. The value ofLR?can be defined as one, two, three, or more. In the example illustrated in FIG. 6, the value of 'R’ is defined as one, where there is a time gap after every repetition. In an example, the value of ‘R’ may be specified, configured via higher layers, indicated in the preamble 202 or control message (if present), determined as a function of the maximum number of repetitions, or determined as a function of the indicated number of repetitions 'N’ in the preamble or control message (if present) at the start of the first repetition of the data packet 204. In a further example, the duration of the time gap includes the transmission time for the acknowledgment message as well as guard times for downlink / uplink (DL / UL) switching for the ambient device to provide sufficient time for the encoding and transmission of the acknowledgment message to avoid overlapping or interference or signals.

[0054] When the receiver, which may include reader including the base station 106 deployed in a wireless network according to the first topology 102 or including the intermediate node 110 deployed according to the second topology 104 or the ambient device 108 as shown in FIG. 1, receives and successfully decodes the first ‘K’ repetitions of the data packet 204, where (K < N), the receiver may respond with the ACK based control message to the transmitter. In this case, the transmitter, which may include the base station 106 in the first topology 102 or the intermediate node 110 in the second topology 104 or the ambient device 108, may cancel the remaining (N-K) repetitions of the data packet 204.

[0055] Further, the receiver, which may be the ambient device 108, may successfully decode the data packet after 2 repetitions and responds with ACK response to the transmitter. In this case, the transmitter, which may be the base station 106, may cancel the remaining (N-2) repetitions to save resource for system operation.

[0056] A maximum number of repetitions may be specified or configured by higher layers and the actual number of repetitions used for transmission of a data packet may be less than or equal to the maximum value.

[0057] Preambles serving as mid-ambles, such as preambles 502 shown in FIG. 5. may be inserted after ‘K’ consecutive repetitions to indicate one or more of: termination of repetitions, start of a new packet transmission, or that repetitions of the current data packet follow. In an example, the value of ‘K’ may be specified, or configured via higher layers, or indicated in the preamble or control message (if present), or determined as a function of the maximum number of repetitions, or determined as a function of the indicated number of repetitions in the preamble or control message (if present) at the start of the first repetition of the data packet.

[0058] In some embodiments, for a given (known) modulation and coding scheme, the length of a repetition of the data packet 204 may be defined in terms of a configured or indicated code rate and size of the data packet. In another example, the length of a repetition of a data packet may be defined in terms of a configured or indicated number of symbols and / or slots to which a single repetition of the data packet 204 is mapped. A repetition code may be applied to the data transmission on a bit level. In this case, the length of repetition code may be indicated in the preamble and / or control message. In some embodiments, a combination of repetition code and repetition of data packet can be jointly applied. In this case, for each repetition of data packet, repetition code may be applied. In some aspects, the repetition code may be applied before a Cyclic Redundancy Check (CRC) or after CRC appendment.

[0059] FIG. 7 illustrates one example of repetitions of preamble associated with physical device to reader channel (PDRCH), control information and data transmission for physical reader to device channel (PRDCH). In the example, two repetitions of the preamble 202 associated with the PDRCH, two repetitions of the control 302, and four repetitions of the data packet 204 are included in the PDRCH transmission. Further, the number of repetitions for the preamble associated with PDRCH. control information and data packet are indicated in the control information for the PRDCH transmission that is used to trigger the PDRCH transmission.

[0060] In another embodiment, a number of repetitions can be used for the transmission of preambles and / or control information that is associated with the PDRCH or PRDCH transmission.

[0061] In one option, the number of repetitions for the preamble 202 can be indicated in the control information that is included in the PDRCH or PRDCH transmission. As a further extension, when the number of repetitions is applied to the preamble associated with the PDRCH transmission, the number of repetitions for preamble can be indicated in the controlinformation that is included in the PRDCH transmission, where the PRDCH transmission is used to trigger the corresponding PDRCH transmission.

[0062] In one option, the number of repetitions for the control information may be determined in accordance with the number of repetitions for the preamble 202 associated with the data packet 204. In another option, the number of repetitions for the control information in the PDRCH transmission may be indicated in the control information in the PRDCH that is used to trigger the PDRCH transmission.

[0063] In another embodiment, the number of repetitions for the data packet 204 may be determined in accordance with the number of repetitions for the associated preambles 202, the number of repetitions for the associated control information, or a combination thereof.

[0064] In one option, a field in the control 302 in the PRDCH transmission may be used to indicate a set of repetitions for the preamble 202, control information and / or data packet of PDRCH transmission in response to the PRDCH transmission. The set of repetitions may be predefined in the specification or indicated by paging, trigger or query message. In one example, one codepoint may be used to indicate the number of repetitions for preambles 202, the number of repetitions for control 302 and / or the number of repetitions for data packet 204 of the PDRCH transmission.

[0065] In another option, a field in the control information in the PRDCH transmission may be used to indicate a number of repetitions for the preamble 202 associated with the PDRCH transmission in response to the PRDCH transmission. Further, the number of repetitions for the control 302 and / or data packet 204 may be determined in accordance with the number of repetitions for the preamble 202 associated with the PDRCH transmission. In some aspects, the above embodiments may be applied to the PDRCH or PRDCH. In some aspects, in the above embodiments, the control message or control information may be included in the PDRCH or PRDCH.

[0066] FIG. 8 and FIG. 9 illustrate modulation signal durations of different chip rates. Ambient devices may be configured to utilize one or more chip rates. Ambient devices that can use multiple chip rates can select a chip rate and generate and encode a data packet according to the selected chip rate. When more than one chip rate may be applied for the transmission of a data packet, a chip rate indication may be carried by a preamble or explicitly included in a control message associated with the data packet. In some embodiments, the chip rate is not explicitly carried by the transmission signal. The transmitter can select a specific chip rate and the receiver detects the chip rate based on the duration of the modulated signal. The receiver may include the reader such as the base station 106 deployed in a wirelessnetwork according to the first topology 102 or the intermediate node 110 deployed according to the second topology 104 or the ambient device 108 as shown in FIG. 1. The transmitter may include the reader such as the base station 106 in the first topology7102 or the intermediate node 110 in the second topology 104 or the ambient device 108. When data is transmitted, the receiver decodes the received message that includes an indication of the chip rate, which may have been selected by the transmitter. The receiver determines the chip rate based on the indication and can, now acting as the transmitter, generate a data packet based on the determined chip rate. For example, the ambient device 108 can transmit a data packet to the reader including base station 106 or intermediate node 110 including an indication of the chip rate. The reader including base station 106 or intermediate node 110 decodes the data packet and determines the chip rate using the chip rate indication. The base station 106 or intermediate node 110 can determine the chip rate by identifying an indication carried by the preamble or control message or by detecting the chip rate based on the duration of the modulated signal. The base station 106 or intermediate node 110 then generates and encodes data packets, such as the repeated data packets described herein, based on the chip rate. FIG. 8 shows an example comparison between a low chip rate and a high chip rate with Manchester encoded signals.

[0067] FIG. 9 shows an example comparison between a low chip rate and a high chip rate with pulse-interval encoded signals. When a chip rate is increased, whether the signals generated are Manchester encoded signals, pulse-interval encoded signals, or another type of encoded signals, the time duration corresponding to the 0 and 1 encoded signals are proportionally decreased. Therefore, an increase in chip rate allows more information to be transmitted and received for the same given time duration. Accordingly, a data transmission with a high chip rate will be shorter than a data transmission carry ing the same information with a low chip rate.

[0068] FIG. 10 illustrates data signal frame format that supports variable chip rates. In an embodiment, data is transmitted with a transmission signal format that consists of preamble 202, control field or (control 302), and data field (or data packet). The chip rate for the data field can vary depending on configuration. The chip rate of the data field can be indicated by the information carried in control 302. If the data field can support variable chip rates, the data field 1002 with a modulated signal duration reflective of a low chip rate will have a longer duration of transmission that the data field 1004 with a modulated signal duration reflective of a high chip rate.

[0069] FIG. 11 illustrates data signal frame format without a control field that supports variable chip rates. Data can be transmitted with a transmission signal format that consists ofpreamble 202 and data field 1002, 1004. The chip rate for the data field can vary depending on configuration. The chip rate of the data field is not explicitly carried by the transmission signal. The transmitter can select a specific chip rate and the receiver can detect the chip rate based on the duration of the modulated signal.

[0070] Operations for the disclosed embodiments may be further described with reference to the following figures. Some of the figures may include a logic flow. Although such figures presented herein may include a particular logic flow, it can be appreciated that the logic flow merely provides an example of how the general functionality as described herein can be implemented. Further, a given logic flow does not necessarily have to be executed in the order presented unless otherwise indicated. Moreover, not all acts illustrated in a logic flow may be required in some embodiments. In addition, the given logic flow may be implemented by a hardware element, a software element executed by a processor, or any combination thereof. The embodiments are not limited in this context.

[0071] FIG. 12 illustrates an embodiment of a logic flow 1200. The logic flow 1200 may be representative of some or all of the operations executed by one or more embodiments described herein. For example, the logic flow 1200 may include some or all of the operations performed by devices or entities within the wireless network 100, including the base station 106, ambient device 108, and intermediate node 110. More particularly, the logic flow 1200 illustrates a use case where the device or entity acting as the transmitter can encode a data transmission with repetitions of a data packet. Embodiments are not limited in this context.

[0072] In block 1202, logic flow 1200 encodes a first preamble for a sequence of data packets by an Ambient Internet of Things (A-IoT) device. The first preamble can indicate the number of repetitions in the sequence of the data packets.

[0073] In block 1204, logic flow 1200 generates a data packet for the sequence of data packets. Prior to generating the first preamble and the data packets, logic flow 1200 can decode a message including an indication of a chip rate and generate the data packet for the sequence of data packets based on the chip rate.

[0074] In block 1206, logic flow 1200 encodes multiple repetitions of the data packet for the sequence of data packets according to a number of repetitions in the sequence of data packets to a reader. In some embodiments, a preamble can be encoded before each repetition of the data packet.

[0075] In block 808, logic flow 1200 can optionally encode a postamble indicating completion of the sequence of data packets.

[0076] FIG. 13 illustrates an embodiment of a logic flow 1300. The logic flow 1300 may be representative of some or all of the operations executed by one or more embodiments described herein. For example, the logic flow71300 may include some or all of the operations performed by devices or entities within the wireless network 100, including the base station 106, ambient device 108, and intermediate node 110. More particularly, the logic flow 1300 illustrates a use case where the device or entity acting as the transmitter can encode a data transmission with repetitions of a data packet. Embodiments are not limited in this context. In some embodiments, logic flow 1300 can include logic flow 1200.

[0077] In block 1302, logic flow 1300 encodes a first preamble for a sequence of data packets by an Ambient Internet of Things (A-IoT) device. In block 1304, logic flow 1300 generates a data packet for the sequence of data packets. In block 1306, logic flow 1300 encodes multiple repetitions of the data packet for the sequence of data packets according to a number of repetitions in the sequence of data packets to a reader.

[0078] In block 1308, logic flow f300 encodes a first repetition of the data packet for the sequence of data packets. In block 1310. logic flow 1300 pauses encoding of the sequence of data packets for a defined time period. In block 1312, logic flow 1300 encodes a second repetition of the data packet for the sequence of data packets. In block 1314, logic flow 1300 pauses encoding of the sequence of data packet for the defined time period. In block 1316, logic flow 1300 decodes an acknowledgement message from the reader of the first repetition or the second repetition of the data packet during the defined time period.

[0079] In block 1318, logic flow 1300 terminates encoding of the sequence of data packets in response to the acknowledgement message.

[0080] FIG. 14 illustrates a network architecture 1400. FIG. 14 illustrates block diagrams of NF components (NFs) and interfaces in connection with embodiments / aspects described herein. In the 5G network architecture of FIG. 14. a next generation (NG) radio access network (RAN) (NG-RAN) comprises a functional split feature that splits a gNodeB (gNB) (also referred to as an '‘NG RAN,” '‘NG RAN node,” or the like) into a gNB-Centralized Unit (CU) (gNB-CU) that implements the upper layer of gNB function and gNB-Distributed Unit (DU) (gNB-DU) that implements the lower layer gNB function. The 5G core NFs and gNB- CU can be implemented as Virtualized Network Functions (VNFs). and the gNB-CU and / or gNB-DU can be implemented as Physical Network Function(s) (PNF(s). An Operator can create a virtualized 5G networks by using the European Telecommunications Standards Institute (ETSI) network functions virtualization (NFV) lifecycle management function toinstantiate a Network Service (NS) in the cloud that includes various VNFs (e.g., 5G core NFs, gNB-CU), PNFs (e.g. gNB-DU), and VNF Forwarding Graph(s) (VNFFG(s)).

[0081] FIG. 14 illustrates an architecture of a network architecture 1400 including a second CN 1402 in accordance with various embodiments. As depicted in FIG. 14, the network architecture 1400 includes a user equipment (UE) 1328, a RAN 1430 or access node (AN); and a DN 1434, which can all be the same or similar to similarly named elements as discussed herein. The DN 1434 can implement, for example, operator services, Internet access or 3rd party services, as discussed further below. The CN 1402 may be implemented as a 5GC or 5GS, and it can include an Authentication Server Function (AUSF) 1320; an AMF 1422; an SMF 1424; a NEF 1408; a PCF 1412; an NRF 1410; a Unified Data Management (UDM) 1414; an application function (AF) 1416; an LMF 1426; a user plane function (UPF) 1432; Network Slice-Specific Authentication and Authorization Function (NSSAAF) 1418; and an NSSF 1406, each with respective components for processing corresponding 5GC network functions (NFs).

[0082] The UPF 1432 can act as an anchor point for intra- RAT and inter-RAT mobility, an external protocol data unit (PDU) session point of interconnect to DN 203, and a branching point to support multi-homed PDU session. The UPF 1432 can also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g.. packet filtering, gating, uplink (UL)Zdownlink (DL) rate enforcement), perform Uplink Traffic verification (e.g.. Service Data Flow (SDF) to Quality of Service (QoS) flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 1432 can include an uplink classifier to support routing traffic flows to a data network. The DN 1434 can represent various network operator services, Internet access, or third party services. DN 1434 can include, or be similar to, application server XQ30 discussed previously. The UPF 1432 can interact with the SMF 1424 via an N4 reference point between the SMF 1424 and the UPF 1432.

[0083] The AUSF 1420 can store data for authentication of UE 1428 and handle authentication-related functionality . The AUSF 1420 can facilitate a common authentication framework for various access types. The AUSF 1420 can communicate with the AMF 1422 via an N12 reference point between the AMF 1422 and the AUSF 1420; and can communicate with the UDM 1414 via an N13 reference point between the UDM 1414 and the AUSF 1420. Additionally, the AUSF 1420 can exhibit an Nausf service-based interface.

[0084] The AMF 1422 can be responsible for registration management (e.g., for registering UE 1428, etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, and access authentication and authorization. The AMF 1422 can be a termination point for the an Ni l reference point between the AMF 1422 and the SMF 1424. The AMF 1422 can provide transport for SM messages between the UE 1428 and the SMF 1424, and act as a transparent proxy for routing SM messages. AMF 1422 can also provide transport for SMS messages between UE 1428 and a Short Message Service (SMS) function (SMSF) (not shown by FIG. 14). AMF 1422 can act as Security' Anchor Function (SEAF), which can include interaction with the AUSF 1420 and the UE 1428, receipt of an intermediate key that was established as a result of the UE 1428 authentication process. Where Universal Subscriber Identity Module (USIM) based authentication is used, the AMF 1422 can retrieve the security material from the AUSF 1420. AMF 1422 can also include a Security Context Management (SCM) function, which receives a key from the SEAF that it uses to derive access-network specific keys. Furthermore, AMF 1422 can be a termination point of a RAN CP interface or RAN connection point interface, which can include or be an N2 reference point between the RAN 1430 and the AMF 1422; and the AMF 1422 can be a termination point of Non Access Stratum (NAS) layer (Nl) signaling, and perform NAS ciphering and integrity protection.

[0085] AMF 1422 can also support NAS signaling with a UE 1428 over an N3 Interworking Function (IWF) interface. The N3 IWF can be used to provide access to untrusted entities. N3IWF can be a termination point for the N2 interface between the RAN 1430 and the AMF 1422 for the control plane, and can be a termination point for the N3 reference point between the RAN 1430 and the UPF for the user plane. As such, the AMF 1422 can handle N2 signaling from the SMF 1424 and the AMF 1422 for PDU sessions and QoS, encapsulate / de-encapsulate packets for IPSec and N3 tunneling, mark N3 user-plane packets in the uplink, and enforce QoS corresponding to N3 packet marking taking into account QoS requirements associated with such marking received over N2. N3IWF can also relay uplink and downlink controlplane NAS signaling between the UE 1428 and AMF 1422 via an Nl reference point between the UE 1428 and the AMF 1422, and relay uplink and downlink user-plane packets between the UE 1428 and UPF 1432. The N3IWF also provides mechanisms for IPsec tunnel establishment with the UE 1428. The AMF 1422 can exhibit an Namf service-based interface, and can be a termination point for an N14 reference point between two AMFs and an N17 reference point between the AMF 1422 and a 5G-Equipment Identity Register (EIR) (not shown by FIG. 14).

[0086] The UE 1428 can need to register with the AMF 1422 in order to receive network services. Registration Management (RM) is used to register or deregister the UE 1428 with the network (e.g., AMF 1422), and establish a UE context in the network (e.g., AMF 1422). The UE 1428 can operate in an RM-REGISTERED state or an RM-DEREGISTERED state. In the RM-DEREGISTERED state, the UE 1428 is not registered with the network, and the UE context in AMF 1422 holds no valid location or routing information for the UE 1428 so the UE 1428 is not reachable by the AMF 1422. In the RM-REGISTERED state, the UE 1428 is registered with the network, and the UE context in AMF 1422 can hold a valid location or routing information for the UE 1428 so the UE 1428 is reachable by the AMF 1422. In the RM-REGISTERED state, the UE 1428 can perform mobility Registration Update procedures, perform periodic Registration Update procedures triggered by expiration of the periodic update timer (e.g., to notify the network that the UE 1428 is still active), and perform a Registration Update procedure to update UE capability information or to re-negotiate protocol parameters with the network, among others.

[0087] The AMF 1422 can store one or more RM contexts for the UE 1428, where each RM context is associated with a specific access to the network. The RM context can be a data structure, database object, etc. that indicates or stores, inter alia, a registration state per access type and the periodic update timer. The AMF 1422 can also store a 5GC MM context that can be the same or similar to the (E)MM context discussed previously. In various embodiments, the AMF 1422 can store a CE mode B Restriction parameter of the UE 1428 in an associated MM context or RM context. The AMF 1422 can also derive the value, when needed, from the UE's usage setting parameter already stored in the UE context (and / or MM / RM context).

[0088] Connection Management (CM) can be used to establish and release a signaling connection between the UE 1428 and the AMF 1422 over the N1 interface. The signaling connection is used to enable NAS signaling exchange between the UE 1428 and the CN 1402, and comprises both the signaling connection between the UE and the Access Network (AN) (e.g., Radio Resource Control (RRC) connection or UE-N3IWF connection for non-3GPP access) and the N2 connection for the UE 1428 between the AN (e.g.. RAN 1430) and the AMF 1422. The UE 1428 can operate in one of two CM states. CM-IDLE mode or CM- CONNECTED mode. When the UE 1428 is operating in the CM-IDLE state / mode, the UE 1428 can have no NAS signaling connection established with the AMF 221 over the N1 interface, and there can be RAN 1430 signaling connection (e.g., N2 and / or N3 connections) for the UE 1428. When the UE 1428 is operating in the CM-CONNECTED state / mode, the UE 1428 can have an established NAS signaling connection with the AMF 1422 over the N1 interface, and there can be a RAN 1430 signaling connection (e.g., N2 and / or N3 connections)for the UE 1428. Establishment of an N2 connection between the RAN 1430 and the AMF 142222 can cause the UE 1428 to transition from CM-IDLE mode to CM-CONNECTED mode, and the UE 1428 can transition from the CM-CONNECTED mode to the CM-IDLE mode when N2 signaling between the RAN 1430 and the AMF 1422 is released.

[0089] The SMF 1424 can be responsible for SM (e g., session establishment, modify and release, including tunnel maintain between UPF and an node); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating an specific SM information, sent via AMF over N2 to AN; and determining SSC mode of a session. SM can refer to management of a PDU session, and a PDU session or “session7’ can refer to a PDU connectivity service that provides or enables the exchange of PDUs between a UE 1428 and a DN 1434 identified by a Data Network Name (DNN). PDU sessions can be established upon UE 1428 request, modified upon UE 1428 and 5GC CN 1402 request, and released upon UE 1428 and 5GC CN 1402 request using NAS SM signaling exchanged over the N1 reference point between the UE 1428 and the SMF 1424. Upon request from an application server, the 5GC CN 1402 can trigger a specific application in the UE 1428. In response to receipt of the trigger message, the UE 1428 can pass the trigger message (or relevant parts / information of the trigger message) to one or more identified applications in the UE 1428. The identified application(s) in the UE 1428 can establish a PDU session to a specific DNN. The SMF 1424 can check whether the UE 1428 requests are compliant with user subscription information associated with the UE 1428. In this regard, the SMF 1424 can retrieve and / or request to receive update notifications on SMF 1424 level subscription data from the UDM 1414.

[0090] The SMF 1424 can include the following roaming functionality: handling local enforcement to apply QoS SLAs (VPLMN); charging data collection and charging interface (VPLMN); lawful intercept (in VPLMN for SM events and interface to LI system); and support for interaction with external DN 1434 for transport of signaling for PDU session authorization / authentication by external DN 1434. an N16 reference point between two SMFs 1424 can be included in the network architecture 1400, which can be between another SMF 1424 in a visited network and the SMF 1424 in the home network in roaming scenarios. Additionally, the SMF 1424 can exhibit the Nsmf service-based interface.

[0091] The NEF 1408 can provide means for securely exposing the services and capabilities provided by 3GPP network functions for third party, internal exposure / re-exposure,Application Functions (e.g., AF 1416). edge computing or fog computing systems, etc. In such embodiments, the NEF 1408 can authenticate, authorize, and / or throttle the AFs 1416. NEF 1408 can also translate information exchanged with the AF 1416 and information exchanged with internal network functions. For example, the NEF 1408 can translate between an AF-Service-Identifier and an internal 5GC information. NEF 1408 can also receive information from other network functions (NFs) based on exposed capabilities of other network functions. This information can be stored at the NEF 1408 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 1408 to other NFs and AFs, and / or used for other purposes such as analytics. Additionally, the NEF 1408 can exhibit an Nnef service-based interface.

[0092] The NRF 1410 can support service discover ' functions, receive NF discover}' requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 1410 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” and the like can refer to the creation of an instance, and an “instance” can refer to a concrete occurrence of an object, which can occur, for example, during execution of program code. Additionally, the NRF 1410 can exhibit the Nnrf service-based interface.

[0093] The PCF 1412 can provide policy rules to control plane function(s) to enforce them, and can also support unified policy framework to govern network behavior. The PCF 1412 can also implement a front end (FE) to access subscription information relevant for policy decisions in a Uniform Data Repository (UDR) or user datagram protocol of the UDM 1414. The PCF 1412 can communicate with the AMF 1422 via an N15 reference point between the PCF 1412 and the AMF 1422, which can include a PCF 1412 in a visited network and the AMF 1422 in case of roaming scenarios. The PCF 1412 can communicate with the application function AF 1416 via an N5 reference point between the PCF 1412 and the AF 1416; and with the SMF 1424 via an N7 reference point between the PCF 1412 and the SMF 1424. The network architecture 1400 and / or CN 1402 can also include an N24 reference point between the PCF 1412 (in the home network) and a PCF 1412 in a visited network. Additionally, the PCF 1412 can exhibit an Npcf service-based interface.

[0094] The UDM 1414 can handle subscription-related information to support the network entities' handling of communication sessions, and can store subscription data of UE 1428. For example, subscription data can be communicated between the UDM 1414 and the AMF 1422 via an N8 reference point between the UDM 1414 and the AMF 1422. The UDM 1414 can include two parts, an application FE and a Uniform Data Repositor}' (UDR) (the FE and UDR are not shown by FIG. 14). The UDR can store subscription data and policy data for the UDM1414 and the PCF 1412, and / or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs UE 1428) for the NEF 1408. The Nudr service-based interface can be exhibited by the UDR to allow the UDM 1414, PCF 1412, and NEF 1408 to access a particular set of the stored data, as well as to read, update (e.g.. add, modify), delete, and subscribe to notification of relevant data changes in the UDR. The UDM 1414 can include a UDM-FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends can serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration / mobility management, and subscription management. The UDR can interact with the SMF 1424 via an N10 reference point between the UDM 1414 and the SMF 1424. UDM 1414 can also support SMS management, wherein an SMS-FE implements the similar application logic as discussed previously. Additionally, the UDM 1414 can exhibit the Nudm service-based interface.

[0095] The AF 1416 can provide application influence on traffic routing, provide access to the NCE, and interact with the policy framework for policy control. The NCE can be a mechanism that allows the 5GC CN 1402 and AF 1416 to provide information to each other via NEF 1408, which can be used for edge computing implementations. In such implementations, the network operator and third party services can be hosted close to the UE 1428 access point of attachment to achieve an efficient service delivery through the reduced end-to-end latency and load on the transport network. For edge computing implementations, the 5GC can select a UPF 1432 close to the UE 1428 and execute traffic steering from the UPF 1432 to DN 1434 via the N6 interface. This can be based on the UE subscription data, UE location, and information provided by the AF 1416. In this way, the AF 1416 can influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 1416 is considered to be a trusted entity, the network operator can permit AF 1416 to interact directly with relevant NFs. Additionally, the AF 1416 can exhibit an Naf service-based interface.

[0096] The NSSF 1406 can select a set of network slice instances serving the UE 1428. The NSSF 1406 can also determine allowed NSSA1 and the mapping to the subscribed single Network Slice Selection Assistance Information (S-NSSAIs), if needed. The NSSF 1406 can also determine the AMF 1422 set to be used to serve the UE 1428, or a list of candidate AMF 1422 based on a suitable configuration and possibly by querying the NRF 1410. The selection of a set of network slice instances for the UE 1428 can be triggered by the AMF 1422 with which the UE 1428 is registered by interacting with the NSSF 1406, which can lead to a change of AMF 1422. The NSSF 1406 can interact with the AMF 1422 via an N22 referencepoint between AMF 1422 and NSSF 1406; and can communicate with another NSSF 1406 in a visited network via an N31 reference point (not shown by FIG. 14). Additionally, the NSSF 1406 can exhibit an Nnssf service-based interface.

[0097] The CN 1402 can include an SMSF, which can be responsible for SMS subscription checking and verification, and relaying SM messages to / from the UE 1428 to / from other entities, such as an SMS-GMSC / IWMSC / SMS-router. The SMS can also interact with AMF 1422 and UDM 1414 for a notification procedure that the UE 1428 is available for SMS transfer (e.g., set a UE not reachable flag, and notifying UDM 1414 when UE 1428 is available for SMS).

[0098] The CN 1402 can also include other elements that are not shown by FIG. 14. such as a Data Storage system / architecture, a 5G-EIR. a SEPP, and the like. The Data Storage system can include a SDSF, an UDSF, and / or the like. Any NF can store and retrieve unstructured data into / from the UDSF (e.g., UE contexts), via N18 reference point between any NF and the UDSF (not shown by FIG. 14. Individual NFs can share a UDSF for storing their respective unstructured data or individual NFs can each have their own UDSF located at or near the individual NFs. Additionally, the UDSF can exhibit an Nudsf service-based interface (not shown by FIG. 14. The 5G-EIR can be an NF that checks the status of PEI for determining whether particular equipment / entities are blacklisted from the network; and the SEPP can be a non-transparent proxy that performs topology hiding, message filtering, and policing on inter-PLMN control plane interfaces.

[0099] Additionally, there can be many more reference points and / or service-based interfaces between the NF services in the NFs: however, these interfaces and reference points have been omitted from FIG. 14 for clarity. In one example, the CN 1402 can include an Nx interface, which is an inter-CN interface between the Mobility Management Entity (MME) and the AMF 1422 in order to enable interworking between CN 1402 and other CN. Other example interfaces / reference points can include an N5g-Equipment Identity Register (EIR) service-based interface exhibited by a 5G-EIR, an N27 reference point between the Network Repository Function (NRF) in the visited network and the NRF in the home network; and an N31 reference point between the NSSF in the visited network and the NSSF in the home network. Further, any of the above functions, entities, etc. can include or be comprised by a component as referred to herein.

[0100] The LMF 1426 (or individual instances of the LMF 1426) is a core network component responsible for determining and managing the geographical location of user equipment (UE). The LMF collects data from the radio network and various other sources tocalculate the position of the UE using techniques like triangulation, time of arrival (TOA), and observed time difference of arrival (OTDOA). It supports both network-based and UE- based positioning methods, with the network or the UE itself calculating the location based on available signals. The LMF interacts with the 5G base stations (gNodeB) to gather necessary’ measurements, and it can also leverage Global Navigation Satellite Systems (GNSS) for more accurate positioning when necessary. In addition to its role in determining device location, the LMF is responsible for sharing this information with authorized entities, such as location-based services or emergency responders. The LMF is vital for enabling services like emergency calls, where precise location information is required, and for supporting Internet of Things (loT) applications where location tracking is necessary. It interfaces with other core network functions, like the Access and Mobility Management Function (AMF), and integrates seamlessly into the 5G service-based architecture to provide secure and reliable location services across various use cases. The LMF 1426 may be deployed in a distributed manner. More than one LMF 1426 can be present in the communication path between various NF Services. The LMF 1426, although not an NF instance, can also be deployed distributed, redundant, and scalable.

[0101] The DN 1434 may represent various network operator services. Internet access, or third party services that may be provided by one or more servers, such as an application server. In some implementations, the DN 1434 may be, or include, one or more edge compute nodes. Additionally or alternatively, the DN 1434 may be an Edge DN 1434, which is a (local) Data Network that supports the architecture for enabling edge applications. In these embodiments, the application server may represent the physical hardware systems / devices providing app server functionality and / or the application software resident in the cloud or at an edge compute node that performs server function(s). In some embodiments, the application server provides an edge hosting environment that provides support required for Edge Application Server's execution.

[0102] The Access Stratum (AS) layer in a 3GPP system is responsible for the radio communication between the user equipment (UE) and the radio access network (RAN). It handles tasks related to the physical transmission of data over the air interface, including managing the establishment, maintenance, and release of radio connections. The AS layer oversees the radio resource control (RRC), which handles signaling between the UE and the base station (gNodeB in 5G or eNodeB in 4G), and it ensures that data is transmitted efficiently and reliably over the wireless link. This layer is involved in functions such as scheduling, handovers, and ensuring quality of service (QoS) for different types of data traffic.

[0103] In contrast, the Non-Access Stratum (NAS) layer operates between the UE and the core network, managing higher-level signaling that is not directly tied to the radio access network. The NAS layer is responsible for tasks such as mobility management, session management, and security between the UE and the core network (like AMF in 5G or MME in 4G). It handles authentication, network registration, location tracking, and the establishment of IP sessions, ensuring secure communication. While the AS layer manages the radio connection, the NAS layer oversees the broader network functions, allowing the device to communicate securely and move seamlessly across different network areas.

[0104] FIG. 15 schematically illustrates a wireless network 1500 in accordance with various embodiments. The wireless network 1500 may include a UE 1502 in wireless communication with an AN 1524. The UE 1502 and AN 1524 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein.

[0105] The UE 1502 may be communicatively coupled with the AN 1524 via connection 1546. The connection 1546 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol, a 5G NR, or a 6G protocol operating at mmWave or sub-6GHz frequencies.

[0106] The UE 1502 may include a host platform 1504 coupled with a modem platform 1508. The host platform 1504 may include application processing circuitry 1506. which maybe coupled with protocol processing circuitry 1510 of the modem platform 1508. The application processing circuitry 1506 may run various applications for the UE 1502 that source / sink application data. The application processing circuitry- 1506 may further implement one or more layer operations to transmit / receive application data to / from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations

[0107] The protocol processing circuitry 1510 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 1546. The layer operations implemented by the protocol processing circuitry 1510 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.

[0108] The modem platform 1508 may further include digital baseband circuitry 1512 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry- 1510 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling / descrambling. encoding / decoding. layer mapping / de-mapping. modulation symbol mapping, received symbol / bit metric determination, multi-antenna portprecoding / decoding. which may include one or more of space-time, space-frequency or spatial coding, reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, control channel signal blind decoding, and other related functions.

[0109] The modem platform 1508 may further include transmit circuitry 1514, receive circuitry 1516, RF circuitry 1518, and RF front end RFFE 1520, which may include or connect to one or more antenna panels 1522. Briefly, the transmit circuitry' 1514 may include a digital- to-analog converter, mixer, intermediate frequency (IF) components, etc.; the receive circuitry 1516 may include an analog-to-digital converter, mixer, IF components, etc.; the RF circuitry 1518 may include a low-noise amplifier, a power amplifier, power tracking components, etc.; RFFE 1520 may include filters (for example, surface / bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc. The selection and arrangement of the components of the transmit circuitry 1514, receive circuitry 1516, RF circuitry 1518, RFFE 1520, and antenna panels 1522 (referred generically as “transmit / receive components’") may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mmWave or sub-6 gHz frequencies, etc. In some embodiments, the transmit / receive components may be arranged in multiple parallel transmit / receive chains, may be disposed in the same or different chips / modules, etc.

[0110] In some embodiments, the protocol processing circuitry 1510 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit / receive components.

[0111] A UE reception may be established by and via the antenna panels 1522, RFFE 1520, RF circuitry 1518, receive circuitry 1516, digital baseband circuitry 1512, and protocol protocol processing circuitry' 1510. In some embodiments, the antenna panels 1522 may receive a transmission from the AN 1524 by receive-beamforming signals received by a plurality of antennas / antenna elements of the one or more antenna panels 1522.

[0112] A UE transmission may be established by and via the protocol processing circuitry' 1510, digital baseband circuitry 1512, transmit circuitry 1514, RF circuitry 1518, RFFE 1520, and antenna panels 1522. In some embodiments, the transmit components of the UE 1502 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 1522.

[0113] Similar to the UE 1502, the AN 1524 may include a host platform 1526 coupled with a modem platform 1530. The host platform 1526 may include application processing circuitry1528 coupled with protocol processing circuitry 1532 of the modem platform 1530. The modem platform 1530 may further include digital baseband circuitry 1534, transmit circuitry 1536, receive circuitry 1538, RF circuitry 1540, RFFE circuitry 1542, and antenna panels 1544. The components of the AN 1524 may be similar to and substantially interchangeable with like-named components of the UE 1502. In addition to performing data transmission / reception as described above, the components of the host platform 150404 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

[0114] FIG. 16 is a block diagram illustrating an apparatus 1600 with various components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, FIG. 16 shows a diagrammatic representation of hardware resources 1630 including one or more processors (or processor cores) 1610, one or more memory' devices 1622, and one or more communication resources 1626, each of which may be communicatively coupled via a bus 1620 or other interface circuitry. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 1602 may be executed to provide an execution environment for one or more netw ork slices / sub-slices to utilize the hardware resources 1630.

[0115] The processors 1610 may include, for example, a processor 1612 and a processor 1612. The processors 1610 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, AN ASIC, AN FPGA, a radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

[0116] The memory devices 1622 (or storage devices) may include main memory , disk storage, or any suitable combination thereof. The memory devices 1622 may include, but are not limited to, any type of volatile, non-volatile, or semi-volatile memory such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.

[0117] The communication resources 1626 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 1604 or one or more databases 1606 or other network elements via anetwork 2008. For example, the communication resources 1626 may include wired communication components (e g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.

[0118] The instructions 1616, instructions 1618, instructions 1624, instructions 1628, and / or instructions 1632 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 2010 to perform any one or more of the methodologies discussed herein. The instructions 1616, instructions 1618, instructions 1624, instructions 1628, and / or instructions 1632 may reside, completely or partially, within at least one of the processors 1610 (e.g., within the processor’s cache memory ), the memory' devices 1 22, or any suitable combination thereof. Furthermore, any portion of the instructions 1616, instructions 1618, instructions 1624, instructions 1628, and / or instructions 1632 may be transferred to the hardware resources 1630 from any combination of the peripheral devices 1604 or the databases 1606. Accordingly, the memory of processors 1610, the memory' devices 1622, the peripheral devices 1604, and the databases 1606 are examples of computer-readable and machine-readable media.

[0119] 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 in the example section below. For example, the baseband circuitry 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 below. 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 below in the example section.

[0120] FIG. 17 illustrates computer readable storage medium 1700. Computer readable storage medium 1700 may comprise any non-transitory computer-readable storage medium or machine-readable storage medium, such as an optical, magnetic or semiconductor storage medium. In various embodiments, computer readable storage medium 1700 may comprise an article of manufacture. In some embodiments, computer readable storage medium 1700 may store computer executable instructions 1702 with which circuitry can execute. For example, computer executable instructions 1702 can include computer executable instructions 1702 to implement operations described with respect to logic flow 1100 and / or logic flow 1200. Examples of computer readable storage medium 1700 or machine-readable storage medium 1700 may include any tangible media capable of storing electronic data, includingvolatile memory or non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writeable or re-writeable memory, and so forth. Examples of computer executable instructions 1702 may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, object-oriented code, visual code, and the like.

[0121] The components and features of the devices described above may be implemented using any combination of discrete circuitry, application specific integrated circuits (ASICs), logic gates and / or single chip architectures. Further, the features of the devices may be implemented using microcontrollers, programmable logic arrays and / or microprocessors or any combination of the foregoing where suitably appropriate. It is noted that hardware, firmware and / or software elements may be collectively or individually referred to herein as ’ logic" or "‘circuit.’'

[0122] It will be appreciated that the exemplary devices shown in the block diagrams described above may represent one functionally descriptive example of many potential implementations. Accordingly, division, omission or inclusion of block functions depicted in the accompanying figures does not infer that the hardware components, circuits, software and / or elements for implementing these functions would necessarily be divided, omitted, or included in embodiments.

[0123] At least one computer-readable storage medium may include instructions that, when executed, cause a system to perform any of the computer-implemented methods described herein.

[0124] Some embodiments may be described using the expression “one embodiment” or “an embodiment” along with their derivatives. These terms mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment. Moreover, unless otherwise noted the features described above are recognized to be usable together in any combination. Thus, any features discussed separately may be employed in combination with each other unless it is noted that the features are incompatible with each other.

[0125] With general reference to notations and nomenclature used herein, the detailed descriptions herein may be presented in terms of program procedures executed on a computer or network of computers. These procedural descriptions and representations are used by those skilled in the art to most effectively convey the substance of their work to others skilled in the art.

[0126] A procedure is here, and generally, conceived to be a self-consistent sequence of operations leading to a desired result. These operations are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical, magnetic or optical signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It proves convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like. It should be noted, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to those quantities.

[0127] Further, the manipulations performed are often referred to in terms, such as adding or comparing, which are commonly associated with mental operations performed by a human operator. No such capability of a human operator is necessary, or desirable in most cases, in any of the operations described herein, which form part of one or more embodiments. Rather, the operations are machine operations. Useful machines for performing operations of various embodiments include general purpose digital computers or similar devices.

[0128] Some embodiments may be described using the expression "coupled" and "connected" along with their derivatives. These terms are not necessarily intended as synonyms for each other. For example, some embodiments may be described using the terms “connected” and / or “coupled” to indicate that two or more elements are in direct physical or electrical contact with each other. The term "coupled,” however, may also mean that two or more elements are not in direct contact with each other, but yet still co-operate or interact with each other.

[0129] Various embodiments also relate to apparatus or systems for performing these operations. This apparatus may be specially constructed for the required purpose or it may comprise a general purpose computer as selectively activated or reconfigured by a computer program stored in the computer. The procedures presented herein are not inherently related to a particular computer or other apparatus. Various general purpose machines may be used with programs written in accordance with the teachings herein, or it may prove convenient to construct more specialized apparatus to perform the required processes. The required structure for a variety of these machines will appear from the description given.

[0130] What has been described above includes examples of the disclosed architecture. It is, of course, not possible to describe every conceivable combination of components and / or methodologies, but one of ordinary skill in the art may recognize that many further combinations and permutations are possible. Accordingly, the novel architecture is intendedto embrace all such alterations, modifications and variations that fall within the spirit and scope of the appended claims.

[0131] The various elements of the devices as previously described with reference to FIGS. 1-17 may include various hardware elements, software elements, or a combination of both. Examples of hardware elements may include devices, logic devices, components, processors, microprocessors, circuits, processors, circuit elements (e.g., transistors, resistors, capacitors, inductors, and so forth), integrated circuits, application specific integrated circuits (ASIC), programmable logic devices (PLD), digital signal processors (DSP), field programmable gate array (FPGA), memory units, logic gates, registers, semiconductor device, chips, microchips, chip sets, and so forth. Examples of software elements may include software components, programs, applications, computer programs, application programs, sy stem programs, software development programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, procedures, software interfaces, application program interfaces (API), instruction sets, computing code, computer code, code segments, computer code segments, words, values, symbols, or any combination thereof. However, determining whether an embodiment is implemented using hardware elements and / or software elements may van’ in accordance with any number of factors, such as desired computational rate, power levels, heat tolerances, processing cycle budget, input data rates, output data rates, memory’ resources, data bus speeds and other design or performance constraints, as desired for a given implementation.

[0132] One or more aspects of at least one embodiment may be implemented by representative instructions stored on a machine-readable medium which represents various logic within the processor, which when read by a machine causes the machine to fabricate logic to perform the techniques described herein. Such representations, known as "TP cores’" may be stored on a tangible, machine readable medium and supplied to various customers or manufacturing facilities to load into the fabrication machines that make the logic or processor. Some embodiments may be implemented, for example, using a machine-readable medium or article which may store an instruction or a set of instructions that, if executed by a machine, may cause the machine to perform a method and / or operations in accordance with the embodiments. Such a machine may include, for example, any suitable processing platform, computing platform, computing device, processing device, computing system, processing system, computer, processor, or the like, and may be implemented using any suitable combination of hardware and / or software. The machine-readable medium or article may include, for example, any suitable type of memory unit, memory device, memory article, memory medium, storage device, storage article, storage medium and / or storage unit, forexample, memory, removable or non-removable media, erasable or non-erasable media, writeable or re-writeable media, digital or analog media, hard disk, floppy disk, Compact Disk Read Only Memory' (CD-ROM), Compact Disk Recordable (CD-R), Compact Disk Rewriteable (CD-RW), optical disk, magnetic media, magneto-optical media, removable memory cards or disks, various types of Digital Versatile Disk (DVD), a tape, a cassette, or the like. The instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, encrypted code, and the like, implemented using any suitable high-level, low-level, object-oriented, visual, compiled and / or interpreted programming language.

[0133] It will be appreciated that the exemplary devices shown in the block diagrams described above may represent one functionally descriptive example of many potential implementations. Accordingly, division, omission or inclusion of block functions depicted in the accompanying figures does not infer that the hardware components, circuits, software and / or elements for implementing these functions would necessarily be divided, omitted, or included in embodiments.

[0134] At least one computer-readable storage medium may include instructions that, when executed, cause a system to perform any of the computer-implemented methods described herein.

[0135] Some embodiments may be described using the expression “one embodiment” or “an embodiment” along with their derivatives. These terms mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment. Moreover, unless otherwise noted the features described above are recognized to be usable together in any combination. Thus, any features discussed separately may be employed in combination with each other unless it is noted that the features are incompatible with each other.

[0136] Examples

[0137] Example 1. A method for data transmission in a wireless network, the method comprising: encoding a first preamble for a sequence of data packets by an Ambient Internet of Things (A-IoT) device; generating a data packet for the sequence of data packets; and encoding multiple repetitions of the data packet for the sequence of data packets according to a number of repetitions in the sequence of data packets to a reader.

[0138] Example 2. The method of example 1 and any preceding example, wherein the first preamble indicates the number of repetitions in the sequence of the data packets.

[0139] Example 3. The method of example 1 and any preceding example, further comprising encoding a postamble indicating completion of the sequence of data packets.

[0140] Example 4. The method of example 1 and any preceding example, further comprising encoding a preamble before each repetition of the data packet.

[0141] Example 5. The method of example 1 and any preceding example, comprising: decoding a message comprising an indication of a chip rate by the A-IoT device; and generating the data packet for the sequence of data packets based on the chip rate.

[0142] Example 6. The method of example 1 and any preceding example, comprising: encoding a first repetition of the data packet for the sequence of data packets; pausing encoding of the sequence of data packets for a defined time period; encoding a second repetition of the data packet for the sequence of data packets; pausing encoding of the sequence of data packet for the defined time period; decoding an acknowledgement message from the reader of the first repetition or the second repetition of the data packet during the defined time period; and terminating encoding of the sequence of data packets in response to the acknowledgement message.

[0143] Example 7. The method of example 1 and any preceding example, wherein the reader comprises a gNodeB, intermediate node, relay, Integrated Access and Backhaul (IAB) node, or user equipment (UE).

[0144] Example 8. A user equipment (UE) device for data transmission in a wireless network, the UE device comprising: a memory interface to communicate information via the wireless network; and processor circuitry operably coupled to the memory interface to: encode a first preamble for a sequence of data packets by the apparatus; generate a data packet for the sequence of data packets; and encode multiple repetitions of the data packet for the sequence of data packets according to a number of repetitions in the sequence of data packets to a reader.

[0145] Example 9. The UE device of example 8 and any preceding example, wherein the first preamble indicates the number of repetitions in the sequence of the data packets.

[0146] Example 10. The UE device of example 8 and any preceding example, wherein the processor circuity is coupled to the memory interface to encode a postamble indicating completion of the sequence of data packets.

[0147] Example 11. The UE device of example 8 and any preceding example, wherein the processor circuity is coupled to the memory interface to encode a preamble before each repetition of the data packet.

[0148] Example 12. The UE device of example 8 and any preceding example, wherein the processor circuity is coupled to the memory interface to: decode a message comprising an indication of a chip rate; and generate the data packet for the sequence of data packets based on the chip rate.

[0149] Example 13. The UE device of example 8 and any preceding example, wherein the processor circuity is coupled to the memory' interface to: encode a first repetition of the data packet for the sequence of data packets; pause encoding of the sequence of data packets for a defined time period; encode a second repetition of the data packet for the sequence of data packets; pause encoding of the sequence of data packet for the defined time period; decode an acknowledgement message from the reader of the first repetition or the second repetition of the data packet during the defined time period; and terminate encoding of the sequence of data packets in response to the acknowledgement message.

[0150] Example 14. The UE device of example 8 and any preceding example, wherein the UE device comprises an Ambient Internet of Things (A-IoT) device.

[0151] Example 15. A computing device for data transmission in a wireless network, the computing device comprising: a memory interface to communicate information via the wireless network; and processor circuitry operably coupled to the memory' interface to: encode a first preamble for a sequence of data packets by an Ambient Internet of Things (A-IoT) device; generate a data packet for the sequence of data packets; and encode multiple repetitions of the data packet for the sequence of data packets according to a number of repetitions in the sequence of data packets to a reader.

[0152] Example 16. The computing device of example 15 and any preceding example, wherein the first preamble indicates the number of repetitions in the sequence of the data packets.

[0153] Example 17. The computing device of example 15 and any preceding example, wherein the processor circuity is coupled to the memory interface to encode a postamble indicating completion of the sequence of data packets.

[0154] Example 18. The computing device of example 15 and any preceding example, wherein the processor circuity' is coupled to the memory' interface to encode a preamble before each repetition of the data packet.

[0155] Example 19. The computing device of example 15 and any preceding example, wherein the processor circuity' is coupled to the memory interface to: decode a message comprising an indication of a chip rate; and generate the data packet for the sequence of data packets based on the chip rate.

[0156] Example 20. The computing device of example 15 and any preceding example, wherein the processor circuity is coupled to the memory interface to: encode a first repetition of the data packet for the sequence of data packets; pause encoding of the sequence of data packets for a defined time period; encode a second repetition of the data packet for the sequence of data packets; pause encoding of the sequence of data packet for the defined time period; decode an acknowledgement message from the reader of the first copy or the second copy of the data packet during the defined time period; and terminate encoding of the sequence of data packets in response to the acknowledgement message.

[0157] Example 21. An apparatus for data transmission in a wireless network, the apparatus comprising: means for encoding a first preamble for a sequence of data packets by an Ambient Internet of Things (A-IoT) device; means for generating a data packet for the sequence of data packets; and means for encoding multiple repetitions of the data packet for the sequence of data packets according to a number of repetitions in the sequence of data packets to a reader.

[0158] Example 22. The apparatus of example 21 and any preceding example, wherein the first preamble indicates the number of repetitions in the sequence of the data packets.

[0159] Example 23. The apparatus of example 21 and any preceding example, further comprising means for encoding a postamble indicating completion of the sequence of data packets.

[0160] Example 24. The apparatus of example 21 and any preceding example, further comprising means for encoding a preamble before each repetition of the data packet.

[0161] Example 25. The apparatus of example 21 and any preceding example, comprising: means for decoding a message comprising an indication of a chip rate by the A-IoT device; and means for generating the data packet for the sequence of data packets based on the chip rate.

[0162] Example 26. The apparatus of example 21 and any preceding example, comprising: means for encoding a first repetition of the data packet for the sequence of data packets; means for pausing encoding of the sequence of data packets for a defined time period; means for encoding a second repetition of the data packet for the sequence of data packets; means for pausing encoding of the sequence of data packet for the defined time period; means for decoding an acknowledgement message from the reader of the first repetition or the second repetition of the data packet during the defined time period; and means for terminating encoding of the sequence of data packets in response to the acknowledgement message.

[0163] Example 27. The apparatus of example 21 and any preceding example, wherein the reader comprises a gNodeB, intermediate node, relay. Integrated Access and Backhaul (IAB) node, or user equipment (UE).

[0164] Example 28. Machine-readable storage including machine-readable instructions, when executed, causes circuitry for user equipment (UE) to communicate information via the wireless network; encode a first preamble for a sequence of data packets by the apparatus; generate a data packet for the sequence of data packets; and encode multiple repetitions of the data packet for the sequence of data packets according to a number of repetitions in the sequence of data packets to a reader.

[0165] Example 29. The machine-readable of example 28 and any preceding example, wherein the first preamble indicates the number of repetitions in the sequence of the data packets.

[0166] Example 30. The machine-readable of example 28 and any preceding example, wherein the processor circuity is coupled to the memory interface to encode a postamble indicating completion of the sequence of data packets.

[0167] Example 31. The machine-readable of example 28 and any preceding example, wherein the processor circuity is coupled to the memory interface to encode a preamble before each repetition of the data packet.

[0168] Example 32. The machine-readable of example 28 and any preceding example, wherein the processor circuity is coupled to the memory interface to: decode a message comprising an indication of a chip rate; and generate the data packet for the sequence of data packets based on the chip rate.

[0169] Example 33. The machine-readable of example 28 and any preceding example, wherein the processor circuity is coupled to the memory interface to: encode a first repetition of the data packet for the sequence of data packets; pause encoding of the sequence of data packets for a defined time period; encode a second repetition of the data packet for the sequence of data packets; pause encoding of the sequence of data packet for the defined time period; decode an acknowledgement message from the reader of the first repetition or the second repetition of the data packet during the defined time period; and terminate encoding of the sequence of data packets in response to the acknowledgement message.

[0170] Example 34. The machine-readable of example 28 and any preceding example, wherein the UE device comprises an Ambient Internet of Things (A-IoT) device.

[0171] Example 35. An apparatus comprising means to perform a method as provided in any- preceding example.

[0172] Example 36. Machine-readable storage including machine-readable instructions, when executed, to implement a method or realize an apparatus as provided in any preceding example.

[0173] Terminology

[0174] For the purposes of the present document, the following terms and definitions are applicable to the examples and embodiments discussed herein.

[0175] The term ‘‘circuitry’’ as used herein refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and / or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g.. a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality. In some embodiments, the circuitry' may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

[0176] The term “processor circuitry ” as used herein refers to, is part of, or includes circuitry' capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and / or transferring digital data. Processing circuitry may include one or more processing cores to execute instructions and one or more memory structures to store program and data information. The term “processor circuitry ” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and / or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and / or functional processes. Processing circuitry' may include more hardware accelerators, which may be microprocessors, programmable processing devices, or the like. The one or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. The terms “application circuitry” and / or “baseband circuitry” may be considered synonymous to, and may be referred to as, “processor circuitry.”

[0177] The term “interface circuitry” as used herein refers to. is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term “interface circuitry'” may refer to one or more hardware interfaces, for example, buses, I / O interfaces, peripheral component interfaces, network interface cards, and / or the like.

[0178] The term “user equipment” or “UE” as used herein refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network. The term “user equipment” or “UE” may be considered synonymous to, and may be referred to as. client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term “user equipment” or “UE” may include any type of wireless / wired device or any computing device including a wireless communications interface.

[0179] The term “network element” as used herein refers to physical or virtualized equipment and / or infrastructure used to provide wired or wireless communication network services. The term “network element” may be considered synonymous to and / or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI. and / or the like.

[0180] The term “computer system” as used herein refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” and / or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” and / or “system” may refer to multiple computer devices and / or multiple computing systems that are communicatively coupled with one another and configured to share computing and / or networking resources.

[0181] The term “appliance,” “computer appliance,” or the like, as used herein refers to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide a specific computing resource. A “virtual appliance” is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or otherwise is dedicated to provide a specific computing resource.

[0182] The term “resource” as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, and / or a physical or virtual componentwithin a particular device, such as computer devices, mechanical devices, memory space, processor / CPU time, processor / CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory usage, storage, network, database and applications, workload units, and / or the like. A "hardw are resource" may refer to compute, storage, and / or network resources provided by physical hardware element(s). A '‘virtualized resource" may refer to compute, storage, and / or network resources provided by virtualization infrastructure to an application, device, system, etc. The term “network resource” or “communication resource” may refer to resources that are accessible by computer devices / systems via a communications network. The term “system resources” may refer to any kind of shared entities to provide services, and may include computing and / or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.

[0183] The term “channel” as used herein refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream. The term “channel” maybe synonymous with and / or equivalent to “communications channel,” “data communications channel,” “transmission channel,” '‘data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and / or any other like term denoting a pathway or medium through which data is communicated. Additionally, the term “link” as used herein refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.

[0184] The terms “instantiate,” “instantiation,” and the like as used herein refers to the creation of an instance. An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.

[0185] The terms “coupled,” “communicatively coupled,” along with derivatives thereof are used herein. The term “coupled” may mean two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements indirectly contact each other but still cooperate or interact with each other, and / or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other. The term “directly coupled” may mean that two or more elements are in direct contact with one another. The term “communicatively coupled” may mean that two or more elements may be in contact with one another by a means of communication including through a wire or other interconnect connection, through a wireless communication channel or link, and / or the like.

[0186] The term “information element” refers to a structural element containing one or more fields. The term “field” refers to individual contents of an information element, or a data element that contains content.

[0187] The term “SMTC” refers to an SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.

[0188] The term “SSB” refers to an SS / PBCH block.

[0189] The term “a “Primary Cell” refers to the MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure.

[0190] The term “Primary SCG Cell” refers to the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure for DC operation.

[0191] The term “Secondary Cell” refers to a cell providing additional radio resources on top of a Special Cell for a UE configured with CA.

[0192] The term “Secondary Cell Group” refers to the subset of serving cells comprising the PSCell and zero or more secondary’ cells for a UE configured with DC.

[0193] The term “Serving Cell” refers to the primary cell for a UE in RRC CONNECTED not configured with CA / DC there is only one serving cell comprising of the primary cell.

[0194] The term “serving cell” or “serving cells” refers to the set of cells comprising the Special Cell(s) and all secondary cells for a UE in RRC_CONNECTED configured with CA / .

[0195] The term “Special Cell” refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term “Special Cell” refers to the Pcell.

Claims

CLAIMSWhat is claimed is:

1. A method for data transmission in a wireless network, the method comprising: encoding a first preamble for a sequence of data packets by an Ambient Internet of Things (A-IoT) device; generating a data packet for the sequence of data packets; and encoding multiple repetitions of the data packet for the sequence of data packets according to a number of repetitions in the sequence of data packets to a reader.

2. The method of claim 1. wherein the first preamble indicates the number of repetitions in the sequence of the data packets.

3. The method of claim 1, further comprising encoding a postamble indicating completion of the sequence of data packets.

4. The method of claim 1 , further comprising encoding a preamble before each repetition of the data packet.

5. The method of claim 1. comprising: decoding a message comprising an indication of a chip rate by the A-IoT device; and generating the data packet for the sequence of data packets based on the chip rate.

6. The method of claim 1. comprising: encoding a first repetition of the data packet for the sequence of data packets; pausing encoding of the sequence of data packets for a defined time period; encoding a second repetition of the data packet for the sequence of data packets; pausing encoding of the sequence of data packet for the defined time period; decoding an acknowledgement message from the reader of the first repetition or the second repetition of the data packet during the defined time period; and terminating encoding of the sequence of data packets in response to the ackno ledgement message.

7. The method of claim 1, wherein the reader comprises a gNodeB, intermediate node, relay. Integrated Access and Backhaul (IAB) node, or user equipment (UE).

8. A user equipment (UE) device for data transmission in a wireless network, the UE device comprising:a memory interface to communicate information via the wireless network: and processor circuitry operably coupled to the memory interface to: encode a first preamble for a sequence of data packets by the apparatus; generate a data packet for the sequence of data packets; and encode multiple repetitions of the data packet for the sequence of data packets according to a number of repetitions in the sequence of data packets to a reader.

9. The UE device of claim 8, wherein the first preamble indicates the number of repetitions in the sequence of the data packets.

10. The UE device of claim 8, wherein the processor circuity is coupled to the memory interface to encode a postamble indicating completion of the sequence of data packets.

11. The UE device of claim 8, wherein the processor circuity is coupled to the memory interface to encode a preamble before each repetition of the data packet.

12. The UE device of claim 8, wherein the processor circuity is coupled to the memory’ interface to: decode a message comprising an indication of a chip rate; and generate the data packet for the sequence of data packets based on the chip rate.

13. The UE device of claim 8, wherein the processor circuity is coupled to the memory interface to: encode a first repetition of the data packet for the sequence of data packets; pause encoding of the sequence of data packets for a defined time period; encode a second repetition of the data packet for the sequence of data packets; pause encoding of the sequence of data packet for the defined time period; decode an acknowledgement message from the reader of the first repetition or the second repetition of the data packet during the defined time period; and terminate encoding of the sequence of data packets in response to the acknowledgement message.

14. The UE device of claim 8, wherein the UE device comprises an Ambient Internet of Things (A-IoT) device.

15. A computing device for data transmission in a wireless network, the computing device comprising: a memory’ interface to communicate information via the wireless network: andprocessor circuitry operably coupled to the memory interface to: encode a first preamble for a sequence of data packets by an Ambient Internet of Things (A-IoT) device; generate a data packet for the sequence of data packets; and encode multiple repetitions of the data packet for the sequence of data packets according to a number of repetitions in the sequence of data packets to a reader.

16. The computing device of claim 15, wherein the first preamble indicates the number of repetitions in the sequence of the data packets.

17. The computing device of claim 15, wherein the processor circuity is coupled to the memory' interface to encode a postamble indicating completion of the sequence of data packets.

18. The computing device of claim 15, wherein the processor circuity is coupled to the memory' interface to encode a preamble before each repetition of the data packet.

19. The computing device of claim 15, wherein the processor circuity is coupled to the memory interface to: decode a message comprising an indication of a chip rate; and generate the data packet for the sequence of data packets based on the chip rate.

20. The computing device of claim 15, wherein the processor circuity is coupled to the memory7interface to: encode a first repetition of the data packet for the sequence of data packets; pause encoding of the sequence of data packets for a defined time period; encode a second repetition of the data packet for the sequence of data packets; pause encoding of the sequence of data packet for the defined time period; decode an acknowledgement message from the reader of the first copy or the second copy of the data packet during the defined time period; and terminate encoding of the sequence of data packets in response to the acknowledgement message.

Images