Devices and methods for communication
AIoT devices utilize ambient energy sources for data transmission and processing, addressing the challenge of battery-less devices in IoT systems by improving communication efficiency.
Patent Information
- Application Number
- PCT/CN2025/094060
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-09
- Publication Date
- 2026-11-12
AI Technical Summary
Existing IoT technologies face challenges in supporting battery-less devices that require energy harvesting from ambient sources, particularly in communication systems like 5G NR, as they lack efficient methods for data transmission and processing.
The implementation of AIoT devices that can receive, store, and process data using ambient energy sources, including backscattering transmission, and communicate effectively with RAN nodes through specific message handling and segmentation techniques.
Enables efficient data transmission and processing for battery-less devices by leveraging ambient energy sources, enhancing communication capabilities in IoT systems.
Smart Images

Figure CN2025094060_12112026_PF_FP_ABST
Abstract
Description
DEVICES AND METHODS FOR COMMUNICATIONFIELDS
[0001] Example embodiments of the present disclosure generally relate to the field of communication techniques and in particular, to devices and methods for data transmission associated with ambient Internet of Things (AIoT or A-IoT) device.BACKGROUND
[0002] In recent years, Internet of Things (IoT) has attracted much attention in the wireless communication world. IoT technologies are expected to drastically change the landscape of various industries. The automation and digitalization of various industries open numbers of new markets requiring new IoT technologies of supporting battery-less devices with no energy storage capability or devices with energy storage that do not need to be replaced or recharged manually. Thus, AIoT is proposed, which is a promising field in some communication systems such as the 5th generation mobile communication technology (5G) new radio (NR) . The ambient IoT refers to IoT without power and energy sources. Specifically, the ambient IoT terminal node, which is also referred to as an ambient IoT device or tag, obtains energy from the environment. For example, an ambient IoT device may capture and collect energy by collecting radio waves to complete data collection, transmission and distributed computing, etc.SUMMARY
[0003] In general, embodiments of the present disclosure provide methods, devices and computer storage medium for data transmission associated with AIoT device.
[0004] In a first aspect, there is provided an ambient Internet of things (AIoT) device. The AIoT device comprises: a processor configured to cause the AIoT device to: receive, from a radio access network (RAN) node, a first message comprising at least one of: a first data service data unit (SDU) , or a first identifier associated with the first message; store, by at least one of an upper layer of the AIoT device or a medium access control (MAC) layer of the AIoT device, at least one of: the first identifier, the first data SDU, a response message to the first message, or second data SDU to be included in the response message; and in response to receiving a second message from the RAN node, determine whether the second message matches with the first message based on the stored at least one of: the first identifier, the response message, or the second data SDU.
[0005] In a second aspect, there is provided an AIoT device. The AIoT device comprises: a processor configured to cause the AIoT device to: receive, from a RAN node, a reader to device (R2D) message comprising scheduling information of a device to reader (D2R) message; determine the D2R message based on the R2D message, where the D2R message comprises at least one of: a data SDU, a field of length information associated with the D2R message, a first indication indicating whether the field of length information is included in the D2R message, a second indication indicating whether a field of padding is included in the D2R message, or a third indication indicating whether a data SDU is included in the D2R message; and transmit the D2R message to the RAN node.
[0006] In a third aspect, there is provided an AIoT device. The AIoT device comprises: a processor configured to cause the AIoT device to: receive, from a RAN node, at least one R2D message, the at least one R2D message comprising at least one segment of original upper layer data and at least one of: at least one indication associated with the at least one segment, or at least one offset information associated with the at least one segment; and reassemble the at least one segment to obtain the original upper layer data based on at least one of the at least one indication or the at least one offset information, where an indication associated with a segment of the original upper layer data indicates at least one of: whether the segment is a last segment, whether the original upper layer data is segmented, whether the segment is a first segment, whether a further segment is after the segment, or an end of R2D transmission, and where offset information associated with a segment of the original upper layer data indicates at least one of: a type of a previous segment, a starting point of the segment in original upper layer data, or a location of the segment in original upper layer data.
[0007] In a fourth aspect, there is provided a RAN node. The RAN node comprises: a processor configured to cause the RAN node to: transmit, to an AIoT device, a first message comprising at least one of: a first data SDU, or a first identifier associated with the first message; transmit a second message to the AIoT device; and receive, from the AIoT device, one of: an indication of mismatching between the first message and the second message to the RAN node, or a response message to the first message or the second message.
[0008] In a fifth aspect, there is provided a RAN node. The RAN node comprises: a processor configured to cause the RAN node to: transmit, to an AIoT device, a reader to device (R2D) message comprising scheduling information of a device to reader (D2R) message; and receive, from the AIoT device, the D2R message comprising at least one of: a data SDU, a field of length information associated with the D2R message, a first indication indicating whether the field of length information is included in the D2Rmessage, a second indication indicating whether a field of padding is included in the D2R message, or a third indication indicating whether a data SDU is included in the D2R message.
[0009] In a sixth aspect, there is provided a RAN node. The RAN node comprises: a processor configured to cause the RAN node to: transmit, to an AIoT device, at least one R2D message, the at least one R2D message comprising at least one segment of original upper layer data and at least one of: at least one indication associated with the at least one segment, or at least one offset information associated with the at least one segment, where an indication associated with a segment of the original upper layer data indicates at least one of: whether the segment is a last segment, whether the original upper layer data is segmented, whether the segment is a first segment, whether a further segment is after the segment, or an end of R2D transmission, and where offset information associated with a segment of the original upper layer data indicates at least one of: a type of a previous segment, a starting point of the segment in original upper layer data, or a location of the segment in original upper layer data.
[0010] In a seventh aspect, there is provided a communication method performed by an AIoT device. The method comprises: receiving, from a RAN node, a first message comprising at least one of: a first data SDU, or a first identifier associated with the first message; storing, by at least one of an upper layer of the AIoT device or a MAC layer of the AIoT device, at least one of: the first identifier, the first data SDU, a response message to the first message, or second data SDU to be included in the response message; and in response to receiving a second message from the RAN node, determining whether the second message matches with the first message based on the stored at least one of: the first identifier, the response message, or the second data SDU.
[0011] In an eighth aspect, there is provided a communication method performed by an AIoT device. The method comprises: receiving, from a RAN node, a R2D message comprising scheduling information of a D2R message; determining the D2R message based on the R2D message, where the D2R message comprises at least one of: a data SDU, a field of length information associated with the D2R message, a first indication indicating whether the field of length information is included in the D2R message, a second indication indicating whether a field of padding is included in the D2R message, or a third indication indicating whether a data SDU is included in the D2R message; and transmitting the D2R message to the RAN node.
[0012] In a ninth aspect, there is provided a communication method performed by an AIoT device. The method comprises: receiving, from a RAN node, at least one R2D message, the at least one R2D message comprising at least one segment of original upper layer data and at least one of: at least one indication associated with the at least one segment, or at least one offset information associated with the at least one segment; and reassembling the at least one segment to obtain the original upper layer data based on at least one of the at least one indication or the at least one offset information, where an indication associated with a segment of the original upper layer data indicates at least one of: whether the segment is a last segment, whether the original upper layer data is segmented, whether the segment is a first segment, whether a further segment is after the segment, or an end of R2D transmission, and where offset information associated with a segment of the original upper layer data indicates at least one of: a type of a previous segment, a starting point of the segment in original upper layer data, or a location of the segment in original upper layer data.
[0013] In a tenth aspect, there is provided a communication method performed by a RAN node. The method comprises: transmitting, to an AIoT device, a first message comprising at least one of: a first data SDU, or a first identifier associated with the first message; transmitting a second message to the AIoT device; and receiving, from the AIoT device, one of: an indication of mismatching between the first message and the second message to the RAN node, or a response message to the first message or the second message.
[0014] In an eleventh aspect, there is provided a communication method performed by a RAN node. The method comprises: transmitting, to an AIoT device, a R2D message comprising scheduling information of a D2R message; and receiving, from the AIoT device, the D2R message comprising at least one of: a data SDU, a field of length information associated with the D2R message, a first indication indicating whether the field of length information is included in the D2Rmessage, a second indication indicating whether a field of padding is included in the D2R message, or a third indication indicating whether a data SDU is included in the D2R message.
[0015] In a twelfth aspect, there is provided a communication method performed by a RAN node. The method comprises: transmitting, to an AIoT device, at least one R2D message, the at least one R2D message comprising at least one segment of original upper layer data and at least one of: at least one indication associated with the at least one segment, or at least one offset information associated with the at least one segment, where an indication associated with a segment of the original upper layer data indicates at least one of: whether the segment is a last segment, whether the original upper layer data is segmented, whether the segment is a first segment, whether a further segment is after the segment, or an end of R2D transmission, and where offset information associated with a segment of the original upper layer data indicates at least one of: a type of a previous segment, a starting point of the segment in original upper layer data, or a location of the segment in original upper layer data.
[0016] In a thirteenth aspect, there is provided a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to carry out the method according to the seventh, eighth, ninth, tenth, eleventh, or twelfth aspect.
[0017] Other features of the present disclosure will become easily comprehensible through the following description.BRIEF DESCRIPTION OF THE DRAWINGS
[0018] Through the more detailed description of some example embodiments of the present disclosure in the accompanying drawings, the above and other objects, features and advantages of the present disclosure will become more apparent, wherein:
[0019] FIG. 1A illustrates an example communication environment in which example embodiments of the present disclosure can be implemented;
[0020] FIG. 1B illustrates another example communication environment in which example embodiments of the present disclosure can be implemented;
[0021] FIG. 1C illustrates an example format for a random ID message;
[0022] FIG. 2A illustrates an example signaling flow of data transmission procedure for AIoT device;
[0023] FIG. 2B illustrates another example signaling flow of data transmission procedure for AIoT device;
[0024] FIG. 3 illustrates a signaling flow of data transmission associated with AIoT device in accordance with some embodiments of the present disclosure;
[0025] FIG. 4 illustrates another signaling flow of data transmission associated with AIoT device in accordance with some embodiments of the present disclosure;
[0026] FIG. 5A to FIG. 5C illustrate example formats of MAC protocol data unit (PDU) in accordance with some example embodiments of the present disclosure, respectively;
[0027] FIG. 6A to FIG. 6C illustrate example formats of MAC protocol data unit (PDU) in accordance with some example embodiments of the present disclosure, respectively;
[0028] FIG. 7 illustrates another signaling flow of data transmission associated with AIoT device in accordance with some embodiments of the present disclosure;
[0029] FIG. 8A to FIG. 8C illustrate example formats of MAC protocol data unit (PDU) in accordance with some example embodiments of the present disclosure, respectively;
[0030] FIG. 9 illustrates another signaling flow for data transmission associated with AIoT device in accordance with some embodiments of the present disclosure;
[0031] FIG. 10 illustrates a signaling flow for message segmentation transmission for AIoT device in accordance with some embodiments of the present disclosure;
[0032] FIG. 11 illustrates another signaling flow for message segmentation transmission for AIoT device in accordance with some embodiments of the present disclosure;
[0033] FIG. 12 illustrates a flowchart of a communication method implemented at an AIoT device according to some example embodiments of the present disclosure;
[0034] FIG. 13 illustrates a flowchart of a communication method implemented at an AIoT device according to some example embodiments of the present disclosure;
[0035] FIG. 14 illustrates a flowchart of a communication method implemented at an AIoT device according to some example embodiments of the present disclosure;
[0036] FIG. 15 illustrates a flowchart of a communication method implemented at a RAN node according to some example embodiments of the present disclosure;
[0037] FIG. 16 illustrates a flowchart of a communication method implemented at a RAN node according to some example embodiments of the present disclosure;
[0038] FIG. 17 illustrates a flowchart of a communication method implemented at a RAN node according to some example embodiments of the present disclosure; and
[0039] FIG. 18 illustrates a simplified block diagram of an apparatus that is suitable for implementing example embodiments of the present disclosure.
[0040] Throughout the drawings, the same or similar reference numerals represent the same or similar element.DETAILED DESCRIPTION
[0041] Principle of the present disclosure will now be described with reference to some example embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. Embodiments described herein can be implemented in various manners other than the ones described below.
[0042] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.
[0043] As used herein, the term ‘terminal device’ refers to any device having wireless or wired communication capabilities. Examples of the terminal device include, but not limited to, user equipment (UE) , personal computers, desktops, mobile phones, cellular phones, smart phones, personal digital assistants (PDAs) , portable computers, tablets, wearable devices, internet of things (IoT) devices, Ultra-reliable and Low Latency Communications (URLLC) devices, Internet of Everything (IoE) devices, machine type communication (MTC) devices, devices on vehicle for V2X communication where X means pedestrian, vehicle, or infrastructure / network, devices for Integrated Access and Backhaul (IAB) , Space borne vehicles or Air borne vehicles in Non-terrestrial networks (NTN) including Satellites and High Altitude Platforms (HAPs) encompassing Unmanned Aircraft Systems (UAS) , eXtended Reality (XR) devices including different types of realities such as Augmented Reality (AR) , Mixed Reality (MR) and Virtual Reality (VR) , the unmanned aerial vehicle (UAV) commonly known as a drone which is an aircraft without any human pilot, devices on high speed train (HST) , or image capture devices such as digital cameras, sensors, gaming devices, music storage and playback appliances, or Internet appliances enabling wireless or wired Internet access and browsing and the like. The ‘terminal device’ may further have ‘multicast / broadcast’ feature, to support public safety and mission critical, V2X applications, transparent IPv4 / IPv6 multicast delivery, IPTV, smart TV, radio services, software delivery over wireless, group communications and IoT applications. It may also incorporate one or multiple Subscriber Identity Module (SIM) as known as Multi-SIM. The term “terminal device” can be used interchangeably with a UE, a mobile station, a subscriber station, a mobile terminal, a user terminal or a wireless device.
[0044] The term “network device” refers to a device which is capable of providing or hosting a cell or coverage where terminal devices can communicate. Examples of a network device include, but not limited to, a Node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a next generation NodeB (gNB) , a transmission reception point (TRP) , a remote radio unit (RRU) , a radio head (RH) , a remote radio head (RRH) , an IAB node, a low power node such as a femto node, a pico node, a reconfigurable intelligent surface (RIS) , and the like.
[0045] The terminal device or the network device may have Artificial intelligence (AI) or Machine learning capability. It generally includes a model which has been trained from numerous collected data for a specific function, and can be used to predict some information.
[0046] The terminal or the network device may work on several frequency ranges, e.g., FR1 (e.g., 450 MHz to 6000 MHz) , FR2 (e.g., 24.25GHz to 52.6GHz) , frequency band larger than 100 GHz as well as Tera Hertz (THz) . It can further work on licensed / unlicensed / shared spectrum. The terminal device may have more than one connection with the network devices under Multi-Radio Dual Connectivity (MR-DC) application scenario. The terminal device or the network device can work on full duplex, flexible duplex and cross division duplex modes.
[0047] A network function as described herein may be implemented by a device or an entity or a node, which is also referred to as a device / entity / node implementing the network function. Such device / entity / node is sometimes called as a core network device / entity / node that may include a combination of hardware processing circuit and software and / or firmware comprising machine-readable instructions, or software comprising machine-readable instructions that are executable by at least one processor of hardware processing circuit of an apparatus. A hardware processing circuit includes at least one processor and at least one memory storing machine-readable instructions that are executable by the at least one processor of the hardware processing circuit. A processor includes any or some combination of an accelerator, a microprocessor, a core of a multi-core microprocessor, a microcontroller, a programmable integrated circuit, a programmable gate array, a digital signal processor, a central processing unit, a graphic processing unit, a tensor processing unit. Memory includes any or some combination of volatile or non-volatile memory (e.g., a flash memory, cache, a random-access memory (RAM) , and / or a read-only memory (ROM) ) . The memory stores the machine-readable instructions of the software and / or firmware for execution by the at least one processor of the hardware processing circuit. The machine-readable instructions are executable by the at least one processor of the hardware processing circuit cause the hardware processing circuit to perform the actions or operations of the methods described herein. For example, the session management function described herein may be implemented as a session management entity and the session management policy control function described herein may be implemented as a session management policy control entity, respectively.
[0048] Embodiments of the present disclosure may be performed in test equipment, e.g., signal generator, signal analyzer, spectrum analyzer, network analyzer, test terminal device, test network device, channel emulator. In some embodiments, the terminal device may be connected with a first network device and a second network device. One of the first network device and the second network device may be a master node and the other one may be a secondary node. The first network device and the second network device may use different radio access technologies (RATs) . In some embodiments, the first network device may be a first RAT device and the second network device may be a second RAT device. In some embodiments, the first RAT device is eNB and the second RAT device is gNB. Information related with different RATs may be transmitted to the terminal device from at least one of the first network device or the second network device. In some embodiments, first information may be transmitted to the terminal device from the first network device and second information may be transmitted to the terminal device from the second network device directly or via the first network device. In some embodiments, information related with configuration for the terminal device configured by the second network device may be transmitted from the second network device via the first network device. Information related with reconfiguration for the terminal device configured by the second network device may be transmitted to the terminal device from the second network device directly or via the first network device.
[0049] As used herein, the singular forms ‘a’ , ‘an’ and ‘the’ are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term ‘includes’ and its variants are to be read as open terms that mean ‘includes, but is not limited to. ’ The term ‘based on’ is to be read as ‘at least in part based on. ’ The term ‘one embodiment’ and ‘an embodiment’ are to be read as ‘at least one embodiment. ’ The term ‘another embodiment’ is to be read as ‘at least one other embodiment. ’ The terms ‘first, ’ ‘second, ’ and the like may refer to different or same objects. Other definitions, explicit and implicit, may be included below.
[0050] In some examples, values, procedures, or apparatus are referred to as ‘best, ’ ‘lowest, ’ ‘highest, ’ ‘minimum, ’ ‘maximum, ’ or the like. It will be appreciated that such descriptions are intended to indicate that a selection among many used functional alternatives can be made, and such selections need not be better, smaller, higher, or otherwise preferable to other selections.
[0051] As used herein, the term “resource, ” “transmission resource, ” “uplink resource, ” or “downlink resource” may refer to any resource for performing a communication, such as a resource in time domain, a resource in frequency domain, a resource in space domain, a resource in code domain, or any other resource enabling a communication, and the like. In the following, unless explicitly stated, a resource in both frequency domain and time domain will be used as an example of a transmission resource for describing some example embodiments of the present disclosure. It is noted that example embodiments of the present disclosure are equally applicable to other resources in other domains.
[0052] As used herein, the term “ambient IoT device” may refer to a device that may not necessarily be able to generate signals independently, and may have very low or even no energy storage capacity. The energy for the ambient IoT device may be provided through the harvesting of radio waves, light, motion, heat, or any other power source that could be seen suitable. The term “ambient IoT device” may also be referred to as a “passive device” , “passive IoT” , “IoT device” , “AIoT device” , “A-IoT device” , “AIoT device” or the like. Examples of the ambient IoT device may include but not limited to tags, sensors, radio frequency (RF) components, or the like. The energy for the ambient IoT device may be provided through the harvesting of radio waves, light, motion, heat, or any other power source that could be seen suitable.
[0053] As used herein, the term “medium access control (MAC) control information” and “medium access control control element (MAC CE) ” may be used interchangeably.
[0054] Principles and implementations of the present disclosure will be described in detail below with reference to the figures.
[0055] FIG. 1A illustrates a schematic diagram of an example communication environment 100 in which example embodiments of the present disclosure can be implemented. In the communication environment 100, an AIoT device 110 communicates with an RAN node 120 or an RAN device. The AIoT device 110 may be a battery-less device, an energy storage disabled device, or a device with limited energy storage capability. The AIoT device 110 may directly and bidirectionally communicate with the RAN node 120 such as a network device or other suitable device. The RAN node 120 may be referred to as a reader for the AIoT device 110.
[0056] In some embodiments, the AIoT device 110 may have no energy storage energy storage, no independent signal generation or amplification. The AIoT device 110 may support a backscattering transmission. Such AIoT device 110 may be referred to as “Device A” or “Device type A” . Alternatively, in some embodiments, the AIoT device 110 supporting the backscattering transmission may have some energy storage, but with no independent signal generation. For such AIoT device 110, using of stored energy may include an amplification for reflected signals. Such AIoT device 110 may be referred to as “Device B” or “Device type B” . Alternatively, in some embodiments, the AIoT device 110 has some energy storage and has independent signal generation, that is, the AIoT device 110 has active RF components for transmission. Such AIoT device 110 may be referred to as “Device C” or “Device type C” . In some following embodiments, the AIoT device 110 may be a Device A or a Device B or a Device C.
[0057] In some embodiments, the AIoT device 110 may be of different device types. A first device type of the AIoT device 110 (referred to as Device 1 or device type 1) may support about 1 μW peak power consumption, have energy storage, initial sampling frequency offset (SFO) up to 10X ppm, neither DL nor UL amplification in the device. The device’s UL transmission is backscattered on a carrier wave provided externally.
[0058] A second device type of the AIoT device 110 (referred to as Device 2a or device type 2a) may support less than or equal to a few hundred μW peak power consumption, have energy storage, initial SFO up to 10X ppm, both DL and / or UL amplification in the device. The device’s UL transmission is backscattered on a carrier wave provided externally.
[0059] A third device type of the AIoT device 110 (referred to as Device 2b or device type 2b) may support less than or equal to a few hundred μW peak power consumption, harvest energy storage, initial SFO up to 10X ppm, both DL and / or UL amplification in the device. The device’s UL transmission is generated internally by the device.
[0060] In some embodiments, the RAN node 120 may be a network device such as a base station, a gNB (also referred to as an AIoT enabled gNB) , a relay, or an IAB device, a terminal device such as UE, or any other suitable device. The RAN node 120 supports AIoT, and may be referred to as an “AIoT enabled RAN node” or “AIoT RAN node” . The RAN node 120 may transmit a signal (also referred to as “ambient IoT signal” ) to the AIoT device 110. As used herein, a device such as the RAN node 120 transmitting the ambient IoT signal to the AIoT device 110 may be referred to as an “ambient IoT device reader” or “reader” . The AIoT device 110 receives the ambient IoT signal and may perform a backscattering transmission based on the ambient IoT signal. For example, the AIoT device 110 may collect or harvest energy from the ambient IoT signal and use the collected energy to transmit the backscattering transmission. As used herein, the term “signal” may be referred to as a “waveform” . The term “ambient IoT signal” may be referred to as an “ambient IoT data” , “ambient IoT signaling” , “ambient IoT waveform” , “harvesting signal” , “carrier wave (CW) ” , “inventory signal” , or “command” . The ambient IoT signal may be a physical layer (PHY) signal.
[0061] In embodiments where the RAN node 120 being a network device such as a base station, the AIoT device 110 may directly and bidirectionally communicate with the base station. If the RAN node 120 is a network device, the topology of the AIoT device 110 and the RAN node 120 shown in FIG. 1A may be referred to as a “Topology 1” . The RAN node 120 in FIG. 1A may be referred to as a gNB reader for the AIoT device 110, or a gNB with AIoT reader function.
[0062] FIG. 1B illustrates a schematic diagram of another example communication environment 150 in which example embodiments of the present disclosure can be implemented. Different with FIG. 1A, in the communication environment 150, the AIoT device 110 communicates bidirectionally with an intermediate node such bas the RAN node 120 between the AIoT device 110 and a network device 160 such as a base station. The RAN node 120 between the AIoT device 110 and the network device 160 may be referred to as an “intermediate node” or “intermediate device” . Examples of the intermediate node may include but be not limited to a terminal device such as UE (also referred to as a UE reader, and AIoT enabled UE, an AIoT node or an AIoT enabled transmission reception point (TRP) ) , a relay, an IAB node, a repeater, a distributed unit (DU) or any other suitable device supporting AIoT. The intermediate node (that is, the RAN node 120 in FIG. 1B) may transmit an ambient IoT signal to the AIoT device 110, and receive a backscattering transmission from the AIoT device 110. The RAN node 120 may be implemented as a terminal device such as UE via which the AIoT device and the network device 160 may communicate. In some embodiments, the RAN node 120 may be a UE reader of the ambient IoT device. The network device 160 may be implemented as the network device serving the UE reader.
[0063] The RAN node 120 such as the intermediate node communicates with the AIoT device 110 for example via Uu interface. The RAN node 120 may transmit the ambient IoT signal to the AIoT device 110 based on the signal from the RAN node 120. The RAN node 120 may receive a backscattering transmission from the AIoT device 110 and forward information derived from the backscattering transmission, to the network device 160. The topology of the AIoT device 110, the RAN node 120 (the intermediate node) and the network device 160 (such as the network device) shown in FIG. 1B may be referred to as a “Topology 2” .
[0064] As used herein, the RAN node 120 in FIG. 1A and FIG. 1B may be referred to as an “ambient IoT device reader” , “A-IoT device reader” , “passive device reader” , “IoT device reader” , “reader” , “reader for the AIoT device 110” , “UE reader” , “BS reader” , “the serving RAN node of reader” , “AIoT RAN node” , “gNB with AIoT reader function” , or the like. The RAN node 120 may support one or more ambient IoT device (s) . The RAN node 120 may operate as a UE and be referred to as “UE reader” , or may operate as a network node and be referred to as “base station (BS) reader” . The RAN node 120 may be referred to as an ambient RAN (A-RAN) , a RAN reader or an A-RAN reader. The network device 160 in FIG. 1B may also be referred to as an A-RAN node or an A-RAN node serving the reader.
[0065] In some embodiments, the communication environment 100 or 150 may include one or more CN nodes or functions (not shown) , such as AIoT function (AIoTF) or AIoT CN, or the like. The AIoTF may support AIoT related function. As used herein, the terms “AIoTF” , “application function (AF) ” , “access and mobility management function (AMF) ” , “AIoT controller” , “AIoT capable AMF” , “AIoT device management” , “AIoT reader management” may be used interchangeably. It is to be understood that there may be more or less CN nodes or functions in the communication environment 100 or 150.
[0066] In some embodiments, the network device 160 may be an AIoT enabled gNB. The RAN node 120 may be an AIoT enabled UE. As used herein, the AIoT enabled gNB refers to a gNB supporting AIoT random access network (RAN) function, which is able to communicate with the AIoT enabled UE via NR Uu interface. The AIoT enabled UE may refer to a UE supporting common reader function, which is able to communicate with the AIoT device via the AIoT radio interface.
[0067] It is to be understood that the number of devices, nodes and their connections as shown in FIG. 1A and FIG. 1B are merely for purpose of illustration without any limitation. In embodiments of the present disclosure, there may be more or less devices.
[0068] A functionality procedure of the AIoT device 110 may involve the AIoT device 110, the RAN node 120, the network device 160 (for Topology 2) and optionally one or more CN nodes or functions, or the like. As used herein, the term “functionality” of the AIoT device 110 may also be referred to as an “application” or “service” of the AIoT device 110, or an “ambient IoT functionality” , “ambient IoT application” , or “ambient IoT service” . The functionality may be an inventory service, a command service, and the like. During the procedure of the functionality or service of the AIoT device 110, different types of traffic may be involved, such as a device-originated (DO) traffic, device-terminated (DT) traffic, DO device-terminated triggered (DO-DTT) traffic. The DO traffic may be autonomously initiated by the AIoT device 110 itself. Such autonomously initiated DO traffic may be referred to as DO-A traffic. As used herein, the terms “DO-A traffic” and “DO-A service” may be used interchangeably.
[0069] In some example embodiments, a transmission direction from the RAN node 120 to the AIoT device 110 is referred to as a downlink (DL) or reader to device (R2D) link, while a transmission direction from the AIoT device 110 to the RAN node 120 is referred to as an uplink (UL) or device to reader (D2R) link. In DL, the RAN node 120 is a transmitting (TX) device (or a transmitter) and the AIoT device 110 is a receiving (RX) device (or a receiver) . In UL, the AIoT device 110 is a TX device (or a transmitter) and the RAN node 120 is a RX device (or a receiver) .
[0070] The message communicated between the AIoT device 110 and the RAN node 120 may be a message via MAC layer, which may be referred to as an AIoT MAC message. A message (such as an AIoT MAC message) transmitted from the RAN node 120 to the AIoT device 110 may be referred to as a “R2D message” . A message (such as an AIoT MAC message) from the AIoT device 110 to the RAN node 120 may be referred to as “D2R message” . The R2D message may be an A-IoT paging message, access occasion trigger message, random ID response message or R2D upper layer data transfer message. The D2R message may be random ID message or D2R upper layer data transfer message.
[0071] For the AIoT paging message, the fields in this message are defined as follows: -R2D Message Type: this field indicates the message type. -RA Type: this field indicates contention based random access (CBRA) or contention free random access (CFRA) . -Indication of Paging ID presence: this field indicates whether Paging ID and Length of Paging ID are present (when set to 1) or absent (when set to 0) . -Length of Paging ID: this field indicates the Paging ID length information when Paging ID field is present. -Paging ID. -Transaction ID. -Number of Access Occasions: this field indicates the number of access occasions. -D2R Scheduling Information (Info) : this field indicates the physical layer parameters used for D2R scheduling.
[0072] For the access occasion trigger message, the field in this message is defined as follows: -R2D Message Type: this field indicates the message type.
[0073] For the random ID response message (such as Msg2 in CBRA) , the fields in this message are defined as follows: -R2D Message Type: this field indicates the message type. -Echoed Random ID: 16 bits. -Assigned AS ID: This field provides the value of AS ID which is 16 bits. -D2R Scheduling Info: this field indicates the physical layer parameters used for D2R scheduling.
[0074] For the R2D Upper Layer Data Transfer message, the fields in this message are defined as follows: -R2D Message Type: this field indicates the message type. -AS ID: This field provides / indicates the value of AS ID. -Length. -Data service data unit (SDU) . -Received Data Size: this field is to indicate the number of bytes successfully received by the reader. -D2R Scheduling Info: this field indicates the physical layer parameters used for D2R scheduling.
[0075] For D2R message, the Random ID message (such as Msg1 in CBRA) may use a format 180 shown in FIG. 1C. For example, the Random ID message may include two octets (OCTs) , each OCT may include a random ID. The random ID may be a 16-bit random number.
[0076] For the D2R Upper Layer Data Transfer message, the fields in this message are defined as follows: -More Data Indication. -Length. -Data SDU. -MAC Padding: this field includes padding bits.
[0077] As described above, in some R2D messages or D2R messages, there may be a field of message type, such as R2D Message Type field in R2D message or D2R Message Type field in D2R message. Table 1 below illustrates example values of the R2D Message Type field, and Table 2 below illustrates example values of the D2R Message Type field. It is to be understood that these values and message names are only for the purpose of illustration, without suggesting any limitation. Table 1 Table 2
[0078] Several example formats for R2D message and D2R message have been described. These formats may be varied or updated in some embodiments. For example, the length field, and / or the MAC Padding field in the D2R upper layer data transfer message may be further specified or varied. The Length field and / or the Data SDU field for the R2D upper layer data transfer message may be further specified, varied, or removed. Details of one or more fields in R2D message or D2R message may be described with respect to FIG. 5A to FIG. 6C and FIG. 8A to FIG. 8C.
[0079] For the purpose of discussion, unless being explicitly states, a R2D message used herein may refer to a R2D upper layer data transfer message. and a D2R message used herein may refer to a D2R upper layer data transfer message.
[0080] As used herein, the upper layer of the AIoT device 110 may be referred to as “upper layer of MAC layer” , “AIoT non-access stratum (NAS) layer” , “application layer” , and / or the like. The message via the upper layer may be referred to as “NAS message” , “AIoT NAS message” , “AIoTF information” , and / or the like.
[0081] As used herein, the term “data SDU” may refer to a MAC protocol data unit (PDU) or MAC message including a data SDU. The data SDU may be included in a R2D message or D2R message. The MAC PDU or AIoT MAC PDU is a data unit format in which the (AIoT) MAC message is encapsulated for transmission through the lower layer (such as MAC layer) of the AIoT protocol stack. An AIoT MAC SDU is a bit string that is byte aligned (i.e., multiple of 8 bits) in length. A MAC SDU is included into a MAC PDU from the first bit onward. A transmission failure of data SDU may be a transmission failure of MAC PDU or MAC message.
[0082] As used herein, the term “service” or “service associated with AIoT” may be a “command (service) ” , “ (inventory service) ” , “combined inventory and command (service) ” or the like. A configuration of a service may include information such as a service area, a reader list, a reader ID list, a time offset or time point associated with the service, a transaction ID, or the like.
[0083] The communications in the communication environment 100 and / or the communication environment 150 may conform to any suitable standards including, but not limited to, Global System for Mobile Communications (GSM) , Long Term Evolution (LTE) , LTE-Evolution, LTE-Advanced (LTE-A) , New Radio (NR) , Wideband Code Division Multiple Access (WCDMA) , Code Division Multiple Access (CDMA) , GSM EDGE Radio Access Network (GERAN) , Machine Type Communication (MTC) and the like. The embodiments of the present disclosure may be performed according to any generation communication protocols either currently known or to be developed in the future. Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, 5.5G, 5G-Advanced networks, or the sixth generation (6G) networks.
[0084] In some mechanisms, necessary functions and procedures for an Ambient IoT compact protocol stack and lightweight signalling procedure to enable DO-DTT and DT data transmission are discussed. A-IoT Paging, including subsequent paging for the same service, is specified. The options that a paging message contains one identifier, and that a paging message contains no identifier are supported. Temporary identifier is not supported, unless being required. It aims to design a paging message format such that multiple identifiers may be contained in one paging message, for forward compatibility purposes.
[0085] In some mechanisms, AIoT random access, including re-access for failure handling is proposed. Contention-based and contention-free cases are supported. For the contention-based random access, only 3-step only (solution 1) is included. The AIoT data transmission may include data (re-) transmission for failure handling.
[0086] Segmentation is supported at least in D2R transmission. In some mechanisms, only MAC layer is included. To support segmentation, a 1 bit indication may be introduced to indicate whether there is more data or not, if CN may provide an estimated expected D2R message size. For segment retransmission, reader explicitly indicates an offset in the MAC layer, for example, the number of bits successfully received so far (from the start) . For the retransmission of the first segment or unsegmented D2R message, the reader sends the R2D message by including the upper layer command again. In some cases, 1-bit indication is sufficient to indicate whether more D2R data will be sent. In case where MAC PDU includes both MAC SDU and padding, for D2R a field to indicate how many SDU bits are present is required. However, how this is provided (i.e. SDU length field or padding length field) and the size of length field need to be considered.
[0087] For R2D message for the command, the R2D message may include D2R scheduling information and a received data size field. The D2R scheduling information may indicate a resource size for the D2R message. For the D2R message for the response of the command, the D2R message transmission may include a MAC PDU. Original upper layer data SDU may be segmented. Data SDU field includes a segment which starts from (x+1) th byte, x being an offset of the segment.
[0088] FIG. 2A illustrates an example signaling flow 200 of data transmission procedure for AIoT device. The signaling flow 200 involves an AIoT device 201 and a reader 202. The reader 202 transmits a first R2D message including a command to the AIoT device 201. In response to receiving the R2D message, the AIoT device 201 may decide that a corresponding D2R message (that is, a response message to the first R2D message) may be unsegmented or may be a first segment. The AIoT device 201 then transmits a data SDU#1, comprising the response message to the first R2D message, to the reader 202. The reader 202 may transmit a second R2D message including the command to the AIoT device 201. The AIoT device 201 may determine whether the corresponding D2R message (that is, a response message to the second R2D message) is unsegmented or first segment or subsequent segment. The AIoT device 201 may transmit a data SDU#2, comprising the response message to the second R2D message, to the reader 202. However, during the data transmission procedure, failure transmission may happen. For example, in some cases, the first R2D message transmission may fail. For another example, the data SDU#1 transmission may fail. In such failure cases, the reader 202 may not know whether the first R2D message transmission fails or the data SDU#1 transmission fails. Therefore, the reader 202 may transmit a second R2D message including a command, may be the same as that in the first R2D message, to the AIoT device 201. In response to receiving the second R2D message, the AIoT device 201 may transmit the data SDU#2 to the reader.
[0089] FIG. 2B illustrates another example signaling flow 250 of data transmission procedure for AIoT device. The signaling flow 250 involves the AIoT device 201 and the reader 202. The reader 202 may transmit a first R2D message including a command to the AIoT device 201. The AIoT device 201 may generate a first segment, e.g., the initial segment, of a response (that is, an original data SDU) of the command and transmit a data SDU#1, comprising the first segment, to the reader 202. The data SDU#1 is successfully received by the reader 202. The reader 202 may transmit a second R2D message including an offset#1 and optionally the command to the AIoT device 201. The AIoT device 201 may generate a second segment starting from the offset#1 plus one of the response and transmit a data SDU#2, comprising the second segment, to the reader 202.
[0090] A data SDU such as the data SDU#1 or data SDU#2 may be a MAC PDU or MAC message including the data SDU. The data SDU#1 is included in the D2R message or transmission. The data SDU#2 may be included in a D2R message or transmission. However, the transmission of the second R2D message or the transmission of the data SDU#2 may fail. A transmission failure of data SDU or R2D message or D2R message may be a transmission failure of the MAC PDU or MAC message. The reader may transmit a third R2D message including the offset#1 and optionally the command to the AIoT device 201. The AIoT device 201 may derive the third segment starting from the offset#1 plus one of the response and transmit a data SDU#3, comprising the third segment to the reader 202. For example, the third segment may be the same as the second segment, such as with the same starting point of the response and with the same length or size. As another example, the third segment may be different from the second segment, such as with the same start point of the response but with different length or size.
[0091] However, for subsequent D2R transmission (e.g., the second segment and the third segment as shown in FIG. 2B) , how to get the command or the original data SDU for (re) transmission of segments needs to be considered. In addition, whether and how to use the offset for the initial segment or unsegmented SDU is a concerning problem.
[0092] In some cases, padding may be supported. How to indicate the length of padding and whether the length field is always included need to be considered. In addition, how to enable the R2D segment and reassemble is another concerning problem.
[0093] Embodiments of the present disclosure provide a solution for AIoT related data transmission. In the solution, a RAN node transmits, to an AIoT device, a first message (such as first R2D message) including at least one of a first data SDU or a first identifier associated with the first message. The AIoT device stores, by upper layer and / or MAC layer, the first identifier, a response message (such as a D2R message) to the first message, and / or second data SDU to be included in the response message. The RAN node further transmits a second message (such as a second R2D message or subsequent R2D message) to the AIoT device. In response to receiving the second message, the AIoT device determines whether the second message matches with the first message based on the stored first identifier, the stored response message and / or the stored second data SDU. For example, the AIoT device may determine whether the first and second messages correspond to a same identifier or a same command. Based on the determining, the AIoT device may transmit a subsequent message, for the response or failure indication, to the RAN node. In this manner, the D2R message / transmission upon subsequent R2D message (s) without command may be enabled.
[0094] Principles and implementations of the present disclosure will be described in detail below with reference to the figures. FIG. 3 illustrates a signaling flow 300 of data transmission of AIoT device in accordance with some embodiments of the present disclosure. The signaling flow 300 involves the AIoT device 110 and the RAN node 120 in FIG. 1A or FIG. 1B. It is to be understood that although a single AIoT device and a single RAN node are illustrated in the signaling flow 300 and other following signaling flows, there may be more than one AIoT device and more than one RAN node in the signaling flow 300 and other following signaling flows. Embodiments of the present disclosure are not limited here.
[0095] In operation, the RAN node 120 transmits (3010) , to the AIoT device 110, a first message including a first data SDU, and / or a first identifier (ID) associated with the first message. Alternatively, or in addition, the first data SDU may include the first ID or a second ID corresponding to the first ID. The MAC layer of the AIoT device 110 may forward or indicate the first ID to the upper layer. Correspondingly, the AIoT device 110 receives (3015) the first message. For example, the first message may be a first R2D message. The first identifier associated with the first message may be a transaction ID or any other suitable ID. For the purpose of discussion, some example embodiments will be described with the first identifier being a transaction ID. The first data SDU may include a command. That is, the first message may include the command. As used herein, the term “data SDU” , “SDU of upper layer data” , “upper layer data SDU” and “SDU” may be used interchangeably. The data SDU may be included in a field of data SDU in the corresponding message. The terms “field of data SDU” , “data SDU field” , “field of command” , “data SDU field including command” , “data SDU field including upper layer data SDU” , “data SDU field including a segment of upper layer data SDU” may be used interchangeably. The AIoT device 110 may transmit a response message (e.g. a D2R message) of the first message to the RAN node 120. The response message may include a second data SDU (e.g., the upper layer data) or a segment of the second data SDU.
[0096] An upper layer (or upper layers) and / or MAC layer of the AIoT device 110 stores (3020) the first identifier, the first data SDU, a response message to the first message, and / or the second data SDU (to be) included in the (subsequent) response message. For example, the second data SDU will be included in the subsequent response message. As used herein, the terms “store” , “record” , “keep” may be used interchangeably. It is to be understood that there may be one or more upper layers. Embodiments described with respect to an upper layer may also be applied to multiple upper layers. For example, indicating or forwarding information (such as ID, data SDU, or the like) to an upper layer may be regarded as indicating or forwarding information to upper layers.
[0097] The RAN node 120 transmits (3030) a second message such as a second R2D message to the AIoT device 110. In response to receiving (3035) the second message from the RAN node 120, the AIoT device 110 determines (3040) whether the second message matches with the first message based on the stored at least one of: the first identifier, the response message, or the second data SDU. Based on the determination (3040) , the AIoT device 110 may perform (3050) a corresponding operation. In an example, if the second message carries the first identifier or a second identifier being partially same with the first identifier, the second message matches with the first message. There may be one or more rules or conditions for determining (3040) whether the second message matches with the first message. Details of the matching determination will be described with respect to FIG. 4.
[0098] The second message may not include the data SDU (field) or the command. In this manner, a following D2R transmission may be enabled upon the subsequent R2D message (s) such as the second message without command. The D2R message such as MAC PDU or segment may be formed using the stored information of the AIoT device 110 such as the stored data SDU (the command) or stored response.
[0099] In some embodiments, the first message includes a first R2D message including at least one of the first identifier or the first data SDU. The MAC layer of the AIoT device 110 may indicate, to the upper layer, the first data SDU and / or the first identifier. Alternatively, or in addition, the MAC layer may store the first data SDU and / or the first identifier. For example, if the first identifier is not stored by the AIoT device 110 or no identifier is stored by the AIoT device 110, the AIoT device 110 such as the MAC layer may store the first data SDU and / or the first identifier. In some examples, the first data SDU may include the first identifier such as the transaction ID or a second identifier associated with the first identifier. The second identifier may be a service ID, or any other suitable ID. For example, the second identifier may include a part of the first identifier, or the other way around. The first identifier and the second identifier may share a same part.
[0100] Further embodiments with the first message being a first R2D message will be described with respect to FIG. 4. FIG. 4 illustrates another signaling flow 400 of data transmission associated with AIoT device in accordance with some embodiments of the present disclosure. The signaling flow 400 involves the AIoT device 110 and the RAN node 120 such as reader.
[0101] As shown, the RAN node 120 may transmit (4010) , to the AIoT device 110, a paging message such as AIoT paging. The paging message includes the first identifier such as transaction ID#1. The AIoT device 110 may perform (4020) a MAC layer operation. For example, if the first identifier is not stored by the AIoT device 110 (such as MAC layer or upper layer of the AIoT device 110) or no identifier is stored by the AIoT device 110, the MAC layer may store the first identifier and / or indicate the first identifier to the upper layer. Alternatively, or in addition, the AIoT device 110 may perform (4030) an upper layer operation. For example, if the MAC layer indicates the first identifier to the upper layer, the upper layer may store the first identifier. That is, after inventory procedure, or after A-IoT random access procedure, the AIoT device 110 may record the transaction ID and the access stratum (AS) ID. Thus, the upper layer may record the received transaction ID.
[0102] The RAN node 120 transmits (4110) the first R2D message including a first data SDU (that is, data SDU#1) and / or the first identifier (that is, transaction ID#1) to the AIoT device 110. The data SDU#1 may include a command#1. Alternatively, or in addition, the data SDU#1 may include the first identifier (for example, transaction ID#1) or a second identifier (for example, service ID#1) corresponding to the first identifier. The AIoT device 110 may perform (4120) corresponding MAC layer operation and / or perform (4130) upper layer operation. For example, the MAC layer may store the data SDU#1 and / or indicate or forward the data SDU#1 to the upper layer. If the data SDU#1 is indicated to the upper layer, the upper layer may store the data SDU#1. These operations may be performed if the upper layer data SDU#1 is included in the first R2D message. In addition, the MAC layer may indicate or forward the first identifier to the upper layer, or store the first identifier. The upper layer may store the first identifier from the MAC layer. The MAC layer and / or the upper layer may store the first identifier if the AIoT device 110 has no stored transaction ID (at MAC layer) or if the first identifier is not stored.
[0103] The upper layer of the AIoT device 110 may read or derive a second data SDU (that is, the upper layer data SDU#2) to form the response message (referred to as response#1) based on the received upper layer data SDU#1 (the command) . The upper layer may indicate data SDU#2 or response#1 to the lower layer such as MAC layer. Therefore, the upper layer data, such as data SDU#2 or response#1, is available at the MAC layer. The MAC layer and / or the upper layer may store the response message to the first R2D message and / or data SDU (s) of the response message. The first identifier (transaction ID#1) is associated to or corresponds to the received upper layer data SDU#1. Upon the (upper layer) data SDU#2 or response#1 indicated by the upper layer, the lower layer (e.g., MAC layer) may form the MAC PDU based on the transport block size (TBS) , resource size or message size (e.g., given / indicated by the D2R Scheduling Info) indicated by the RAN node 120. In addition, the MAC layer may store the upper layer data SDU#2 or response#1 (from the upper layer) and / or the transaction ID#1. The AIoT device 110 may transmit (4140) the response message including the data SDU#2 or a segment of the data SDU#2 to the RAN node 120.
[0104] In some embodiments, the AIoT device 110 may determine whether the response message is to be segmented based on size information of at least one of the response message or the second data SDU. For example, before deriving the second data SDU, the AIoT device 110 may determine whether the response message is to be segmented. If the response message is to be segmented, the AIoT device 110 may perform (4120) , at the MAC layer, at least one of: indicating the first identifier to the upper layer, storing the first data SDU, storing the second data SDU, or storing the response message (from the upper layer) . That is, the MAC layer of the AIoT device 110 may determine that there will be subsequent D2R transmission for the same command.
[0105] In some embodiments, the AIoT device 110 may transmit, to the RAN node 120 such as gNB, a capability report of the AIoT device 110. The capability report may indicate that the AIoT device 110 has a storage capability, such as a capability of storing the first data SDU and / or the command and / or the second data SDU or the response message. The capability report may further indicate that the storage of the above information may be at the MAC layer or upper layer (s) . The capability report may be included in the response message, or included in a further D2R message. Alternatively, the RAN node 120 may obtain the storage capability of the AIoT device 110 from a further device such as a CN node associated with the AIoT device 110. The CN node may be AIoTF, AMF, or the like. In this manner, the RAN node 120 may know about the storage capability of the AIoT device 110. Based on such storage capability, the RAN node 120 may not include the command in the second R2D message or subsequent R2D message. If an AIoT device does not have such capability, the RAN node 120 may still need to include the command in the second or subsequent R2D message.
[0106] The RAN node 120 may transmit (4210) a second R2D message including a data SDU#3 to the AIoT device 110. The AIoT device 110 may perform (4220) corresponding MAC layer operation and / or perform (4230) corresponding upper layer operation. If the second R2D message matches with the first R2D message, the AIoT device 110 may derive, at the upper layer, fourth data SDU (data SDU#4) based on the third identifier associated with the second R2D message. The second R2D message may match with the first R2D message based on the third identifier being same as the first identifier, or being at least part of a second identifier associated with the first identifier. In case the second R2D message matches with the first R2D message, the AIoT device 110 may derive, at the upper layer, fourth data SDU (data SDU#4) based on the store second data SDU (the command) of the first R2D message. The AIoT device 110 may transmit (4240) the data SDU#4 or a segment of the data SDU#4 to the RAN node 120.
[0107] In an example, the second R2D message includes a third data SDU (data SDU#3, which may include a command#2) , and / or the third data SDU includes a third identifier. The MAC layer of the AIoT device 110 may forward or indicate the data SDU#3 to the upper layer. The data SDU#3 may include a command#2. Alternatively, the data SDU#3 may include a third identifier such as transaction ID#2 or service ID#2.
[0108] In some examples, the second (R2D) message excludes a data SDU. That is, the second R2D message does not include a command. That is, the field of command is optional, and the subsequent R2D message (for data SDU or upper layer data) may not include the command. In an option, the upper layer of A-IoT device 110 may store the data SDU (e.g., command, from the RAN node 120) . The first identifier or index (e.g., transaction ID) of command may be provided by the upper layer or MAC layer. In another option, the MAC layer of A-IoT device 110 may store the data SDU (e.g., command, form the reader) , corresponding to the transaction ID. In a further option, the MAC layer of A-IoT device 110 may store the original upper layer SDU (e.g., response, form its own upper layer) . Based on the stored information, the D2R transmission upon the second R2D message (that is, subsequent R2D messages of the first R2D message) without command can be enabled.
[0109] In some examples, the response message to the first message may include a MAC PDU. The AIoT device 110 may generate the MAC PDU based on stored second data SDU or stored response message and further based on the offset information related to D2R message. As used herein, the offset information may indicate a received data size, or an offset bit or offset byte related to the received data size, or the like. The offset of a data SDU may be based on at least one data SDU previously transmitted before the data SDU.
[0110] In some examples, the second message may include a second R2D message, and the second R2D message includes a third identifier (for example, transaction ID#2) without including a third data SDU or data SDU field. The AIoT device 110 may perform (4220) , at the MAC layer, at least one of: indicating the third identifier to the upper layer, indicating stored first data SDU associated with the third identifier to the upper layer, generating an MAC PDU based on stored second data SDU or stored response message associated with the third identifier, or updating, based on offset information related to D2R message, the stored second data SDU, or the stored response message. In an option, the MAC layer of the AIoT device 110 may indicate the transaction ID#2 to the upper layer. In another option, the MAC layer of the AIoT device 110 may indicate the stored SDU (e.g. SDU#1 of the upper layer data#1) associated to the transaction ID#2 to the upper layer. The MAC layer may derive the stored data SDU#1 / command according to the transaction ID#2 first. In a further option, the MAC layer may form MAC PDU based on the stored data SDU#2 or response#1 (from the upper layer) . These options may be performed if the transaction ID#2 is same as at least one of the stored transaction ID, and the data / response is corresponding to the transaction ID#2 or the matched transaction ID. In addition, the MAC layer may update the store data SDU after receiving the offset. That is, the bits or bytes till the offset-th bit or byte of the store data SDU / upper layer data may be deleted. For D2R transmission, an indication on the updating or deletion of the bits or bytes may be added.
[0111] In some examples, the second R2D message may include an indication on at least one D2R resource, such as the D2R scheduling information. The second R2D message may exclude the upper layer data SDU or data SDU field. Alternatively or in addition, the second R2D message may exclude the identifier such as transaction ID. The AIoT device 110 may perform (4220) , at the MAC layer, at least one of: indicating a stored identifier (such as transaction ID#1) to the upper layer, indicating stored first data SDU to the upper layer, generating an MAC PDU or data SDU based on stored second data SDU or stored response message, or updating, based on offset information related to D2R message, the stored second data SDU, or the stored response message. These operations may be performed if there is the D2R resource in the R2D message. In addition, the second R2D message may include offset information related to the D2R message, such as an offset for the D2R transmission. The MAC layer may form the data SDU or MAC PDU based on the stored data SDU#2 or response#1 (from the upper layer) further based on the offset information.
[0112] In some examples, a third identifier associated with the second R2D message may be provided by a physical layer. The second R2D message may exclude the data SDU or data SDU field. The RAN node 120 may mask the cyclic redundancy check (CRC) with the third identifier such as transaction ID for the (R2D) physical layer signal. The AIoT device 110 may perform (4220) , at the MAC layer, at least one of: indicating the third identifier to the upper layer, indicating stored first data SDU associated with the third identifier to the upper layer, generating an MAC PDU based on stored second data SDU or stored response message associated with the third identifier, or updating, based on offset information related to D2R message, the stored second data SDU, or the stored response message.
[0113] In some embodiments, the AIoT device 110 may perform (4220) the MAC layer operation if the second message matches with the first message. The AIoT device 110 may determine that the second message matches with the first message based on at least one condition being satisfied. A condition may be that a third identifier in the second (R2D) message is stored at the MAC layer, or stored at the upper layer. Another condition may be that at least part of an identifier (such as service ID) stored at the MAC layer or the upper layer matches with the third identifier, or the other way around. That is, the stored identifier and the third identifier may share a same part. A further condition may be a data SDU associated with the first (R2D) message being stored at the MAC layer or the upper layer. The data SDU associated with the first message may be the data SDU#1 (the command, received data SDU from the RAN node) or the data SDU#2 which corresponds to the response message.
[0114] The upper layer of the AIoT device 110 may, according to the upper layer data SDU#3 or the stored upper layer data SDU#1, read or derive upper layer data SDU#4 or form response#2. Then the upper layer of the AIoT device 110 may indicate upper layer data SDU#4 or response#2 to the lower layer (e.g., MAC layer) .
[0115] The upper layer may derive the upper layer data (e.g. command) according to the transactionID#2 or service ID#2, upon at least one of: ·the transaction ID#2 is the same as the transaction ID in the (at least one) stored command, ·the transaction ID#2 matches part of the service ID, such as most significant bit (MSB) or least significant bit (LSB) X bits, in the (at least one) stored command, X being an integer, ·the transaction ID#2 is the same as the transaction ID corresponding to the (at least one) stored command, or ·the service ID#2 is the same as the service ID corresponding to the (at least one) stored command.
[0116] Several MAC layer operations and upper layer operations in response to the second message matching the first message have been described. In some cases, the AIoT device 110 may determine that the second message mismatches with the first message based on at least one condition being satisfied. For example, if no data SDU from the RAN node 120 is stored at the MAC layer, or the upper layer, the second message mismatches with the first message. If there is no stored data SDU from the upper layer, the second message mismatches with the first message. If no identifier is stored at the MAC layer or the upper layer, the second message mismatches with the first message. If an identifier in the second message mismatches with a stored identifier at the MAC layer or the upper layer, the second message mismatches with the first message.
[0117] If the second message mismatches with the first message, the AIoT device 110 such as MAC layer and / or upper layer may perform corresponding operation (s) . For example, the AIoT device 110 may transmit an indication of the mismatching (or failure) to the RAN node 120, which may be generated at the MAC layer or the upper layer. For another example, the AIoT device 110 may refrain, at the MAC layer, from indicating to the upper layer, at least one of: third data SDU in the second message, third identifier in the second message, or stored data SDU. For a further example, the AIoT device 110 may indicate, by the upper layer to the MAC layer, at least one of: an indication of indicating the mismatching to the RAN node, and / or an identifier of the RAN node. As a result, the AIoT device 110 may generate, at the MAC layer, a response to indicating the mismatching, and transmit the response to the RAN node 120. In addition, the AIoT device 110 may generate, at the upper layer, a response to indicating the mismatching, and transmit the response to the RAN node 120.
[0118] If there is the transaction ID (transaction ID#2) or command (the upper layer data SDU#3) in the second or subsequent R2D message, if there is no matched transaction ID at MAC layer, the MAC layer may perform at least one of the following: not forwarding or indicating the upper layer data SDU#3, transaction ID#2 or the stored upper layer data SDU#1 to the upper layer, or sending an indication on failure to the RAN node 120, via MAC layer information.
[0119] If there is the D2R resource in the second or subsequent R2D message, the AIoT device 110 may determine failure based on at least one of the following conditions: ·there isn’t any stored SDU from the reader (e.g., command) in the MAC layer; ·there isn’t any stored SDU from the upper layer (e.g., response) ; ·there isn’t any stored transaction ID in the MAC layer; ·there isn’t any stored SDU from the reader (e.g., command) in the upper layer; or ·there isn’t any stored transaction ID in the upper layer.
[0120] Upon matching failure, the MAC layer may perform at least one of the following: not forwarding or indicating the upper layer data SDU#3, transaction ID#2 or the stored upper layer data SDU#1 to the upper layer, or sending an indication on failure to the RAN node 120 via MAC layer information.
[0121] Alternatively, or in addition, if there is no matched transaction ID or service ID at the upper layer, the upper layer may form a response to indicate failure, and send it to the reader, or indicate the MAC layer to send a failure indication to the RAN node 120. In addition, the upper layer may indicate the reader ID to MAC layer.
[0122] In some examples of FIG. 4, in a first option, the upper layer of A-IoT device 110 may store the data SDU (e.g., command, form the reader) . The index (e.g., transaction ID) of command may be provided by the upper layer or MAC layer. The subsequent R2D message may not provide command or only provide the index of command. Then, the upper layer may use the stored command to form the original upper layer data SDU.
[0123] In a second option, the MAC layer of A-IoT device 110 may store the data SDU (e.g., command, form the reader) , corresponding to the transaction ID. The subsequent R2D message may not provide command or only provide the index of command. Then, the MAC layer may forward the command to the upper layer, and the upper layer may use this command to form the original upper layer data SDU.
[0124] In a third option, the MAC layer of A-IoT device 110 may store the original upper layer SDU (e.g., response, form its own upper layer) . The MAC layer may use this stored original upper layer SDU to form MAC PDU.
[0125] In addition, the transaction ID#1 may be the same as transaction ID#2. The content of the upper layer data SDU#2 may be the same as that of SDU#1. The upper layer data SDU#1, SDU#3 may be command or command for reading. The upper layer data SDU#2, data SDU#4 may be data read according to the command. For example, data SDU#2 is an un-segmented SDU (e.g., the original upper layer data SDU) , and data SDU#4 is an un-segmented SDU (e.g., the original upper layer data SDU) . For another example, data SDU#2 is an un-segmented SDU (e.g., the original upper layer data SDU) , and data SDU#4 is a segment of the original upper layer data SDU. For a further example, data SDU#2 is a segment of the original upper layer data SDU, and data SDU#4 is another segment of the original upper layer data SDU.
[0126] Alternatively, these two SDUs may be associated to two original upper layer data SDUs, such as data SDU#2 is an un-segmented SDU (e.g., the original upper layer data SDU#1) , and data SDU#4 is an un-segmented SDU (e.g., the original upper layer data SDU#2) ; or data SDU#2 is an un-segmented SDU (e.g., the original upper layer data SDU#1) , and data SDU#4 is a segment of the original upper layer data SDU#2; or data SDU#2 is a segment of the original upper layer data SDU#1, and data SDU#4 is another segment of the original upper layer data SDU#2. In other words, for the case, the R2D message always provides command.
[0127] In some example embodiments, a R2D message such as the first message or the second message comprises a MAC PDU. At least one type of MAC PDU may be supported. IN an example, the R2D message may include MAC PDU of a single type (referred to as a fourth type of MAC PDU) . The fourth type of MAC PDU includes one or more of: a field of data SDU, a field of identifier, format information of the first type of MAC PDU, and / or the like.
[0128] The format information may include an indication of a format of the MAC PDU, an indication indicating whether the field of data SDU (which may include a command) is included, an indication indicating whether the field of identifier (which may include a transaction ID) is included, an indication indicating whether the field of data SDU and the field of identifier are included, and / or the like. That is, The format information may include an indication indicating whether the field of data SDU (which may include a command) is present or absence, an indication indicating whether the field of identifier (which may include a transaction ID) is present or absence, an indication indicating whether the field of data SDU and the field of identifier are present or absence, and / or the like. As used herein, the terms “included” , “present” and “existing” are used interchangeably. The terms “not included” , “excluded” and “absent” are used interchangeably.
[0129] FIG. 5A illustrates an example of the fourth format of MAC PDU 500 in accordance with some example embodiments of the present disclosure. As shown, the MAC PDU 500 includes control information 510 and optionally a field of data SDU 520. The control information 510 includes a field of indication 512. The control information 510 may optionally include a field of ID 514. In an example, the control information 510 may optionally include an indication (not shown) indicating whether the field of ID 514 is included. The field of data SDU 520 may include a command. In some examples, the field of data SDU may also be referred to as a field of command, or a field of upper layer data.
[0130] Alternatively, in some examples, the R2D message such as the first message or the second message is of a fifth type of MAC PDU or a sixth type of MAC PDU. The fifth type of MAC PDU at least includes a field of data SDU (which may include a command) , and the sixth type of MAC PDU excludes the field of data SDU. The fifth type of MAC PDU and / or the sixth type of MAC PDU may include a field of identifier such as transaction ID.
[0131] FIG. 5B illustrates an example of the fifth format of MAC PDU 530 in accordance with some example embodiments of the present disclosure. The MAC PDU 530 includes control information / part 530. The control information 530 may include a field of indication 542. The MAC PDU 530 may optionally include the field of data SDU 520, which may include a command. For example, the field of indication 542 may indicate the corresponding format includes the field of data SDU 520.
[0132] FIG. 5C illustrates an example of the sixth format of MAC PDU 550 in accordance with some example embodiments of the present disclosure. The MAC PDU 55-may include control information 560. The control information may include a field of indication 562. For example, the field of indication 542 may indicate the corresponding format excludes the field of data SDU 520.
[0133] In an option, the MAC PDU for upper layer data SDU (e.g. the R2D Upper Layer Data Transfer message) may always include the field for data SDU 520 (which may include a command) , and the field for data SDU 520may include full command or index of command, such as transaction ID or service ID. In another option, the field for data SDU 520is optional.
[0134] The MAC PDU may include an indication on the appearance / present for the field of data SDU; or an indication on the format of MAC PDU or the format of control information / part of the MAC PDU, for example, one format with the field of data SDU and another format without the field of data SDU.
[0135] Alternatively, or in addition, in some examples, the MAC PDU for upper layer data (SDU) may always comprise the field for transaction ID. Alternatively, the field for transaction ID is optional. Alternatively or in addition, the appearance / present of the field for transaction ID means the appearance / present of the field of data SDU 520. The field of data SDU may carry upper layer data, such as command. This MAC PDU may comprise one indication on at least one of: ·an indication#1 on whether the field of data SDU 520is included. For example, 1 bit indication or other bit-length indication. The indication#1 being 0 means that the message is without the field of data SDU 520, and the indication#1 being 1 means that the message is with the field of data SDU 520. ·an indication#2 on whether the field of command is included. For example, 1 bit indication or other bit-length indication. The indication#2 being 0 means that the message is without the field of data SDU 520and the field of transaction ID, and the indication#2 being 1 means that the message is with the field of data SDU 520and the field of transaction ID. ·an indication#3 on whether the field of transaction ID is included. The indication#3 being 0 means that the message is without the field for transaction ID, and the indication#2 being 1 means that the message is with the field for transaction ID.
[0136] Alternatively, the MAC PDU may comprise one indication on a combined code on the appearance of these fields, for example: ·1 bit indication, where the indication being 1 indicates that both the field of data SDU 520and the field of transaction ID are included and the indication being 0 indicates that the field of transaction ID is included without the command, or ·1 bit indication, where the indication being 1 indicates that only the field of data SDU 520is included and the indication being 0 indicates that only the field of transaction ID is included, or ·a 2 bits indication or combined indication, where the indication being “00” indicates that both the field of data SDU 520and the field of transaction ID are included, the indication being “01” indicates that only the field of transaction ID is included and the indication being “10” indicates that only the field of data SDU 520is included.
[0137] It is to be understood that these example indications and values are only for the purpose of discussion, without suggesting any limitation. Any suitable indication or value may be used to indicate the existence of the field of data SDU 520 and / or the field of transaction ID. The field of indication 512, the field of indication 542 and the field of indication 562 may use the above examples of indication, or any other suitable indication. Scope of the present disclosure is not limited here. The formats shown in FIG. 5A to FIG. 5C may be used for the R2D Upper Layer Data Transfer message. For example, the field of data SDU may be omitted in some R2D Upper Layer Data Transfer message. It is to be understood that these example formats are only for the purpose of discussion, without suggesting any limitation. These formats may include further fields, such as R2D Message Type field, AS ID field, Length field, Received Data Size field, D2R Scheduling Info field, and / or the like. One or more of these fields may be omitted, and one or more further fields may be added. Scope of the present disclosure is not limited here.
[0138] In an example, the first R2D message for upper layer data, may comprise the field of data SDU 520. The subsequent R2D message for upper layer data may not comprise the field of data SDU 520. In another example, the first R2D message for upper layer data may comprise the field of data SDU 520, and the field of transaction ID. The subsequent R2D message for upper layer data may comprise transaction ID, and the field of data SDU 520. In a further example, the first R2D message for upper layer data may comprise the field of data SDU 520, and without the field of transaction ID. The subsequent R2D message for upper layer data may comprise the field of transaction ID, and without the field of data SDU 520. In a still further example, the first R2D message for upper layer data may comprise the field of data SDU 520, and the field of transaction ID. The subsequent R2D message for upper layer data may comprise the field of transaction ID, and without the field of data SDU 520.
[0139] By indicating the format of the MAC PDU, the MAC layer of the AIoT device 110 may derive the corresponding fields of data SDU and / or transaction ID.
[0140] As mentioned, an R2D message such as the first R2D message and / or the second R2D message may include offset information (e.g., the field of offset information, such as the field of received message size) related to D2R message / transmission. The offset information may be used to determine an offset or starting point of (original) upper layer data in a MAC PDU for a D2R message. In an example, the offset may be set as zero for the initial D2R transmission. The MAC layer of the AIoT device 110 may form or generate the MAC PDU or data SDU, which starts from a bit or byte indicated by the offset plus one of the original upper layer data SDU.
[0141] In an example, if the offset information indicating zero or a predefined value, the AIoT device 110 may generate, at the MAC layer, a MAC PDU or data SDU (e.g., the upper layer data) from one of: a beginning bit or byte of original data SDU, a bit or byte of original data SDU (e.g., the upper layer data) indicated by the offset information, or a bit or byte of original data SDU indicated by the offset information plus one. That is, the data SDU field may be set to include data which starts from 1) the first bit / byte or 2) the bit / byte indicated by the offset plus one or 3) the bit / byte indicated by the offset of the original upper layer data SDU. The MAC PDU or data SDU may be generated till the end of the original data SDU, if the size of the original upper layer data SDU is smaller than or equal to the indicated D2R resources, or till the D2R resource is fully occupied. If the offset information indicates a value different from zero and the predefined value, the AIoT device 110 may generate, at the MAC layer, a MAC PDU or data SDU from a bit or byte of original data SDU indicated by the value plus one.
[0142] Alternatively, in some examples, the offset information of the R2D message for upper layer data may present optionally. For example, the offset information may be for the retransmission of segment only. The AIoT device 110 may make decision for generating MAC PDU or data SDU for D2R transmission based on the presence of the offset information.
[0143] Upon receiving an R2D message such as command, in response to the offset information being included in an R2D message, the AIoT device 110 may generate, at the MAC layer, a MAC PDU or data SDU from a bit or byte of original data SDU indicated by the offset information plus one. If the offset information is not included in the R2D message, the AIoT device 110 may generate, at the MAC layer, a MAC PDU or data SDU from a beginning bit or byte of the original data SDU.
[0144] If no identifier is stored or no identifier (e.g., transaction ID) associated with the R2D message is stored by the MAC layer and / or upper layer, the AIoT device 110 may generate, at the MAC layer, a MAC PDU or data SDU from a beginning bit or byte of original data SDU. In addition, the R2D message may not include the field of offset information in such cases. Alternatively, the R2D message may include the field of offset information but this field will not be interpreted / used. If an identifier associated with the R2D message is stored by the MAC layer and / or upper layer, the AIoT device 110 may generate, at the MAC layer, a MAC PDU or data SDU based on the offset information. The MAC layer may process the field of offset information.
[0145] The RAN node 120 may change the transaction ID for the retransmission of a command / upper layer data to trigger the retransmission of the first segment / unsegmented D2R message. The transmission ID may be provided by the MAC layer, physical layer, and the upper layer.
[0146] If a subsequent R2D message is with an old command, for example, with a stored transaction ID, but the subsequent R2D message is without offset information, the AIoT device 110 may not response to the R2D message. Alternatively, the AIoT device 110 may form the MAC PDU starting from the first bit or byte.
[0147] As mentioned, the R2D message such as R2D upper layer data transfer message may be a MAC PDU with offset information. The MAC PDU format or an indication may indicate the presence of the field of offset information.
[0148] In some examples, the R2D message is of a first type of MAC PDU. The first type of MAC PDU includes a field of offset information.
[0149] In an example, the R2D message may include an indication indicating whether the field of offset information is included. The indication may be a 1-bit indication or other bit-length indication. For example, the indication being “0” indicates the R2D message without the field of offset, and the indication being “1” indicates the R2D message with the field of offset. FIG. 6A illustrates an example format of MAC PDU 600 of the first type in accordance with some example embodiments of the present disclosure. As shown, the MAC PDU 600 includes control information 610. The control information 610 may include a field of indication 612, which indicates whether the field of offset information 614 is included.
[0150] In another example, an indication on a format of control information / part in the MAC layer indicates whether the field of offset information is included. For example, the indication being “0” indicates a format without the field of offset, and the indication being “1” indicates a format with the field of offset.
[0151] In a further example, an identifier in the R2D message may indicate whether the field of offset information is included. A new transaction ID means without the field of offset, or no need to interpret / use the field of offset to form data SDU. A stored transaction ID means with the field of offset, need to interpret / use the field of offset to form data SDU.
[0152] Alternatively, or in addition, in some examples, the R2D message is of a second type of MAC PDU or a third type of MAC PDU. The second type of MAC PDU at least includes a field of offset information, and the third type of MAC PDU excludes the field of offset information.
[0153] FIG. 6B illustrates an example format of MAC PDU 620 of the second type in accordance with some example embodiments of the present disclosure. The MAC PDU 620 includes control information 630. The control information / part 630 may include a field of offset information 632. FIG. 6C illustrates an example format of MAC PDU 640 of the third type in accordance with some example embodiments of the present disclosure. The MAC PDU includes control information 650. No field of offset information is included in the control information 650.
[0154] By using these MAC PDU formats, the MAC layer of the AIoT device 110 may determine the presence of the offset information based on the indication of the field of offset information, and / or a specific message type or MAC PDU type. There may be two types of message or MAC PDU. One type of message or MAC PDU includes the field of data SDU but excludes the field of offset information. That is, the message includes a command without an offset. Another type of message or MAC PDU includes the field of offset information but excludes the field of data SDU. For example, the message includes an offset but does not include a command.
[0155] In some examples, the MAC PDU such as control information or control part of the MAC PDU may include at least one indication related to the offset information and the data SDU (which may include the command) . The at least one indication may include an indication (for example, 1 bit or any bit length) for the field of offset information and an indication (for example, 1 bit or any bit length) for the field of data SDU. The indication being set to “1” may indicate a presence of the corresponding field, and the indication being set to “0” may indicate an absence of the corresponding field. Alternatively, the at least one indication may be a combined indication for both the field of offset information and the field of data SDU. The combined indication may include 1 bit, 2 bits or more bits. For example, if a 1-bit combined indication being set to “0” , it may mean that the field of data SDU is included, if the 1-bit combined indication being set to “1” , it may mean that the field of offset information is included, or the other way around. Examples of 2 bits combined indication will be shown in Table 3 and Table 4 below. It is to be understood that the values, bit lengths and meanings shown in Table 3 and Table 4 are only for the purpose of illustration, without suggesting any limitation. In addition, for the value “11” in Table 4, it may be reserved. Any suitable values or indications may be applied. Scope of the present disclosure is not limited in this regard. Table 3 Table 4
[0156] By using these MAC PDU types where the data SDU (the command) and offset information are optional, the overhead of subsequent R2D message (s) may be saved.
[0157] In some cases, padding may be supported. How to indicate the length of padding and whether the length field is always included need to be considered.
[0158] The formats shown in FIG. 6A to FIG. 6C may be used for the R2D Upper Layer Data Transfer message. It is to be understood that these example formats are only for the purpose of discussion, without suggesting any limitation. These formats may include further fields, such as Data SDU field, R2D Message Type field, AS ID field, Length field, Received Data Size field, D2R Scheduling Info field, and / or the like. One or more of these fields may be omitted, and one or more further fields may be added. The formats shown in FIG. 6A, FIG. 6B or FIG. 6C may be applied at least partially in combination with those formats shown in FIG. 5A to FIG. 5C. Scope of the present disclosure is not limited here.
[0159] Embodiments of the present disclosure provide a solution for management of AS ID of AIoT device. In the solution, a RAN node transmits, to an AIoT device, a R2D message including scheduling information of a D2R message. The AIoT device determines or generates the D2R message based on the R2D message. The D2R message includes a data SDU, a field of length information associated with the D2R message, a first indication indicating whether the field of length information is included in the D2R message, a second indication indicating whether a field of padding is included in the D2R message, or a third indication indicating whether a data SDU is included in the D2R message. The AIoT device transmits the D2R message to the RAN node. In this manner, the indication of padding may be enabled.
[0160] FIG. 7 illustrates a signaling flow 700 of data transmission of AIoT device in accordance with some embodiments of the present disclosure. The signaling flow 700 involves the AIoT device 110 and the RAN node 120 in FIG. 1A or FIG. 1B. It is to be understood that although a single AIoT device and a single RAN node are illustrated in the signaling flow 700 and other following signaling flows, there may be more than one AIoT device and more than one RAN node in the signaling flow 700 and other following signaling flows. Embodiments of the present disclosure are not limited here.
[0161] In operation, the RAN node transmits (7010) , to the AIoT device, a R2D message including scheduling information of a D2R message such as D2R scheduling information. Correspondingly, the AIoT device 110 receives (7015) the R2D message. Based on the D2R scheduling information, the D2R message size may be determined.
[0162] The AIoT device 110 determines (7020) or generates the D2R message based on the R2D message, such as the D2R scheduling information. The D2R message includes at least one of: a data SDU such as a field of data SDU, a field of length information associated with the D2R message, a field of padding, a first indication (e.g., may be named as padding indication) indicating whether the field of length information is included in the D2R message, a second indication indicating whether a field of padding is included in the D2R message, or a third indication indicating whether a data SDU is included in the D2R message. In an example, the D2R message may include the field of length and the field of padding. For example, if no data is at the AIoT device 110 or the AIoT device 110 has not generated a response or read data in response to the D2R resource arrives, there may be no data SDU in the D2R message. In addition, the D2R message may include the field of padding. The field of length may indicate a length of the padding field. Alternatively, the D2R may include the field of data SDU. The AIoT device 110 transmits (7030) the D2R message to the RAN node 120. Correspondingly, the RAN node 120 receives (7035) the D2R message. The RAN node 120 may determine whether there is a field of data SDU in the D2R message based on the D2R message size and the length of padding. Alternatively, the RAN node 120 may determine whether there is a field of data SDU in the D2R message based on the third indication.
[0163] In some examples, the field of length information indicates one or more of: a length (also referred to as size) of the data SDU, a length of MAC PDU excluding the field of padding, a length of the field of padding, or the like.
[0164] FIG. 8A illustrates an example format of MAC PDU 800 in accordance with some example embodiments of the present disclosure. The MAC PDU 800 includes control information / part 810, a field of data SDU 820 and optionally a field of padding 830. The control information 810 may include a field of length 812. In the example of FIG. 8A, the field of length 812 indicates a length for MAC PDU excluding the field of padding. The RAN node 120 may determine the appearance or length of the field of padding based on the scheduled D2R message size minus the length for MAC PDU. Alternative, the D2R message may include one indication to indicate whether the field of padding appears / present.
[0165] FIG. 8B illustrates an example format of MAC PDU 840 in accordance with some example embodiments of the present disclosure. The MAC PDU 840 includes control information / part 850, a field of data SDU 820 and optionally a field of padding 830. The control information 850 may include a field of length 852. The field of length 852 indicates a length for the field of data SDU 820. The RAN node 120 may determine the appearance or length of the field of padding based on the scheduled D2R message size minus (the length for the field of Data SDU plus the size of control information in the MAC PDU) .
[0166] Alternatively, or in addition, the D2R message may include one indication to indicate whether the field of padding appears. Alternatively, or in addition, the D2R message may include one indication to indicate whether the field of length appears.
[0167] Alternatively, or in addition, if there is no field of padding or the field of padding is absent, the field of length may not appear or may absent. No padding means the size of the resulting MAC PDU including the total upper layer data is larger than or equal to the resource size given by the D2R scheduling information. No padding means the size of the resulting MAC PDU including the segment of upper layer data is larger than or equal to the resource size given by the D2R scheduling information. That is, if the field of padding appears, it means the field of length appears. That is, if the field of length appears, it means that the field of padding appears. In other words, if the field of length absent or not appears, it means there is not the field of padding or the field of padding absent. In other words, if there is not the field of padding or the field of padding absent, it means the field of length absent or not appears. For example, the MAC PDU may comprise control information and the field of data SDU. The RAN node 120 may determine the appearance or length of the field of data SDU based on the scheduled D2R message size minus the length of control information in the MAC PDU (e.g., the size of control information may be fixed or predefined) . Alternatively, or in addition, if no field of data SDU is included or the field of data SDU is absent, the field of length may not appear or may be absent. That is, if the field of data SDU appears, it means the field of length appears. That is, if the field of length appears, it means that the field of data SDU appears. In other words, if the field of length is absent or not appears, it means there is no field of data SDU or the field of data SDU is absent. In other words, if there is not the field of data SDU or the field of data SDU is absent, it means the field of length is absent or not appears. For example, the MAC PDU may comprise control information and the field of padding. The RAN node 120 may determine the appearance or length of the field of padding based on the scheduled D2R message size minus the length of control information in the MAC PDU (e.g., the size of control information may be fixed or predefined) . Alternatively, or in addition, if there is no field of data SDU or the field of data SDU is absent, the field of length may appear and may indicate the size of data SDU as zero (e.g., set as all-bits-zero) . Alternatively, or in addition, if there is no field of padding or the field of padding is absent, the field of length may appear and may indicate the size of padding as zero (e.g., set as all-bits-zero) .
[0168] The D2R message may include only one field on length, such as the length for MAC PDU excluding the field of padding, or the length for the field of data SDU. Alternatively, or in addition, if D2R message needs the padding with one byte (or less than 1 byte) , the field of length for MAC PDU / data SDU may appear. Alternatively, or in addition, if D2R message needs the padding with more than one byte, both the field of length for PDU / data SDU and the field of padding may appear. In an example, the field of length may be 7 bits or any other length of bits. Alternatively, the field of length may be byte-aligned, such as 8 bits / 1 byte, 16 bits / 2 bytes; or 7 bits for the length and 1bit for R (reserved bit) . The MAC PDU may also include a field of More Data indication (may be 1 bit) . In addition, if the field of More Data indication indicates that there is no more data to be transmitted, the field of length may be present or may become effective. That is, the RAN node may interpret or process the field of length. Alternative, indicate that there is more data to be transmitted, the field of length may be absent, may become invalid or may be treated as reserved bits. That is, the RAN node may not interpret or process the field of length.
[0169] Alternatively, the D2R may include the field of length indicating a length for padding. FIG. 8C illustrates an example format of MAC PDU 860 in accordance with some example embodiments of the present disclosure. The MAC PDU 860 includes control information / part 870, a field of data SDU 820 and optionally a field of padding 830. The control information 870 may include a field of length 872. The field of length 872 indicates a length for the field of padding 830.
[0170] The D2R message may always comprising the field of length, if there isn’t the field of padding, the length is set to all-bits-zero. Alternatively, or in addition, the D2R message may include one indication to indicate whether the field of padding appears. Alternatively, or in addition, if no padding, the field of length for padding may not appear. Alternatively, or in addition, if D2R message needs the padding with one byte, the field of length for padding may appear. Alternatively, or in addition, if D2R message needs the padding with more than one byte, both the field of length for padding and the field of padding may appear.
[0171] The field of length may be 7 bits or any other length of bits. Alternatively, the field of length may be byte-aligned, such as 8 bits, 16 bits; or 7bits for the length and 1bit for R (reserved bit) .
[0172] The formats shown in FIG. 8A to FIG. 8C may be used for the D2R Upper Layer Data Transfer message. For example, the field of Padding may be included or omitted. The length field may indicate the length of Data SDU field, the length of Padding field, or the length of MAC PDU excluding the Padding field. It is to be understood that these example formats are only for the purpose of discussion, without suggesting any limitation. These formats may include further fields, such as D2R Message Type field, More Data Indication field, and / or the like. One or more of these fields may be omitted, and one or more further fields may be added. Scope of the present disclosure is not limited here.
[0173] The AIoT device 110 may determine whether at least one condition is satisfied. The at least one condition may include the D2R message / data SDU / upper layer data being to be segmented, and / or further segmentation of the D2R message / data SDU / upper layer data being to be transmitted. If the at least one condition is satisfied, the AIoT device 110 may exclude at least one of the field of length information or the field of padding from a MAC PDU of the D2R message. In addition, if there is more data to be transmitted (and there are no more resources) , the MAC PDU will not comprise the field of padding and / or the field of length. That is, the A-IoT device 110 will not transmit the field of padding and / or the field of length.
[0174] If a length of the field of padding is less than or equal to a threshold, the field of length information may be included and the field of padding may be excluded from the D2R message. That is, if the length of the field of padding is less than or equal to a threshold such as 1 byte, the field of padding may not be included in the D2R message. For example, the length field may be set as all-bits-zero. In this case, RAN node 120 may determine the absence of the field of padding.
[0175] In some examples, the control information / part of the MAC PDU may include an indication on the appearance of the field for padding (e.g., the second indication) . The indication may be set as ‘1’ to indicate appearance of the field for padding, and set as ‘0’ to indicate absence of the field for padding.
[0176] The control information / part of the MAC PDU may include an indication on the appearance of the field for length or length information (e.g., the first indication) . The indication may be set as ‘1’ to indicate appearance of the field for length, and set as ‘0’ to indicate absence of the field for length. If the field for length is present, the field of padding may also present. That is, the first indication may also indicate the presence or absence of the field of padding. Alternatively, or in addition, the first indication may also indicate the presence or absence of the field of data SDU.
[0177] Several examples of the MAC PDU for D2R message have been described. With these MAC PDU formats, a field of length may be defined or included. The indication of padding thus be enabled.
[0178] In some cases, padding may be supported. How to enable the R2D segment and reassemble is another concerning problem. Embodiments of the present disclosure provide another solution for data transmission of AIoT device. In the solution, a RAN node transmits, to an AIoT device, at least one R2D message. The at least one R2D message includes at least one segment of original upper layer data and at least one of: at least one indication associated with the at least one segment, or at least one offset information associated with the at least one segment. The AIoT device reassembles the at least one segment to obtain the (original) upper layer data such as original data SDU based on at least one of the at least one indication or the at least one offset information. In this manner, the original upper layer data may be reassembled.
[0179] FIG. 9 illustrates another signaling flow 900 for data transmission associated with AIoT device in accordance with some embodiments of the present disclosure. The signaling flow 900 involves the AIoT device 110 and the RAN node 120 in FIG. 1A or FIG. 1B.
[0180] In operation, the RAN node 120 transmits (9010) , to the AIoT device 110, at least one R2D message. The at least one R2D message includes at least one segment of original upper layer data and at least one indication. The original upper layer data may be an original data SDU. The original data SDU may include a command. Each segment of the original upper layer data is included in a data SDU (field) , which may be part or segment of the original upper layer data such as the original data SDU. In the following description, the original data SDU corresponding to the original upper layer data may be referred to as “original data SDU” , and the data SDU including a segment may be referred to as a segmented data SDU, a transmitted data SDU, a received data SDU, a data SDU in a segment, a stored SDU or a stored data SDU.
[0181] The at least one indication may be at least one indication associated with the at least one segment, or at least one offset information associated with the at least one segment. The AIoT device receives (9015) the at least one segment correspondingly. The AIoT device 110 reassembles (9020) the at least one segment to obtain the (original) data SDU (e.g., original upper layer data) based on at least one of the at least one indication or the at least one offset information. In this manner, the R2D message or the (original) data SDU may be reassembled.
[0182] In some examples, an indication associated with a segment of the (original) data SDU indicates at least one of: whether the segment is a last segment, whether the (original) data SDU is segmented, whether the segment is a first segment, whether a further segment is after the first segment (e.g., the subsequent segment or a second segment) , or an end of R2D transmission (e.g., the end of the transmission for the original data SDU / upper layer data) .
[0183] The indication may be an indication type#1, an indication type#2, an indication type#3, or an indication type#4. For example, the indication type#1 being set to “0” may indicate a last segment or un-segmented, and the indication type#1 being set to “1” may indicate there may be further segment or more data. The indication type#2 being set to “00” may indicate un-segmented or non-segment, the indication type#2 being set to “01” may indicate a first or subsequent segment, and the indication type#2 being set to “10” may indicate a last segment. The indication type#3 being set to “00” may indicate un-segmented or non-segment, the indication type#3 being set to “01” may indicate the first segment, the indication type#3 being set to “10” may indicate the subsequent segment, and the indication type#3 being set to “11” may indicate a last segment. The indication type#4 being set to “1” may indicate the end of the R2D transmission. It is to be understood that these indication types, values and meanings are only for the purpose of illustration, without suggesting any limitation.
[0184] The offset information associated with a segment of the original data SDU (also referred to as the offset information associated with the R2D message) indicates at least one of: a type of offset, transmitted bytes of a previous segment, a starting point of the segment in original data SDU, or a location of the segment in original data SDU. For example, an offset type#1 may indicate transmitted byte (s) of previous segment (s) . An offset type#2 may indicate the starting point of the current segment (s) or the location of the segment in the original upper layer data SDU. The offset information may indicate the type of offset, such as the offset type#1 or offset type#2. Based on the indicated type of offset, the AIoT device 110 may determine what exactly information is included in the offset information.
[0185] The R2D message may include the field of upper layer data SDU, the field of indication on segment and the field on offset. The MAC layer may re-assemble the segments to form original data SDU (e.g., upper layer data) . In an option, once a segment of the original data SDU is received, the MAC layer may re-assemble the segment. For example, the MAC layer may reassemble the segmented data SDU in the received R2D message to obtain partial of the original data SDU. In another option, the MAC layer may store and re-assemble SDUs (e.g., segments of the original data SDU) upon the end of R2D transmission or the last segment.
[0186] In some examples, in response to receiving a R2D message of the at least one R2D message, the MAC layer of the AIoT device 110 may store a received data SDU (e.g., a segment of original data SDU) in the R2D message and offset information associated with the R2D message. Alternatively, the MAC layer may forward or indicate the received data SDU and the offset information to an upper layer. Alternatively, the MAC layer may reassemble the original upper layer data based on the received data SDU (e.g., a segment of the original data SDU / upper layer data) in the R2D message and based on the offset information. The MAC layer may forward the reassembled (original) data SDU to the upper layer.
[0187] In some examples, the at least one R2D message comprises a plurality of R2D messages. In response to receiving a R2D message of the plurality of R2D messages, the R2D message being not the last R2D message (the R2D message does not include data SDU with the last segment of original upper layer data) , the MAC layer of the AIoT device 110 may store a segment of (original) data SDU in the R2D message.
[0188] In response to an indication of an R2D message indicating a last segment or an end of R2D transmission, the MAC layer of the AIoT device 110 may forward the received data SDU (segment of original upper layer data) and the offset information to the upper layer, or forward the received data SDU and at least one stored SDU and offset information of the received data SDU and the at least one stored SDU to the upper layer. Alternatively, the MAC layer may reassemble the original upper layer data based on the data SDU in the R2D message and based on offset information associated with the R2D message, or reassemble the original upper layer data based on the data SDU in the R2D message with at least one stored data SDU.
[0189] In some embodiments, in response to an indication of an R2D message indicating no segment, the AIoT device 110 may forward data SDU in the R2D message from a MAC layer to an upper layer. In such case, the AIoT device 110 may not store the received data SDU.
[0190] Further example embodiments will be described with respect to FIG. 10, which illustrates a signaling flow 1000 of data transmission related to AIoT device in accordance with some embodiments of the present disclosure. The signaling flow 1000 involves the AIoT device 110 and the RAN node 120 in FIG. 1A or FIG. 1B. The signaling flow 1000 is an example implementation of the signaling flow 900.
[0191] As shown, the RAN node 120 transmits (1010) a first R2D message including a segment#1 of data SDU#1 / upper layer data#1 (in data SDU field) to the AIoT device 110. The data SDU#1 is the original upper layer data#1. In an option, the MAC layer of the AIoT device 110 may reassemble (1020) partial of the data SDU#1 based on the segment#1. Alternatively, the MAC layer may store the segment#1 of data SDU#1 or forward the segment#1 of data SDU#1 to the upper layer. If the indication indicates no segment or is set as ’00’ for the indication type#2, (the MAC layer) may forward the segment#1 of data SDU#1 to upper layer. If the indication indicates the first or subsequent segment or is set as “01” for the indication type#2, the MAC layer may store the received data SDU#1 or segment#1 of data SDU#1 and store the offset corresponding to this data SDU or the segment of data SDU. Alternatively, if the data SDU is the subsequent segment or if there is a stored or previous segment of data SDU#1 or reassembled (partial) data SDU#1, the MAC layer may reassemble the original data SDU#1 based on the received data SDU according to the start point or location as its offset plus one. That is, the MAC layer may attempt to reassemble the original data SDU once it receives a segment of the original data SDU.
[0192] The RAN node 120 transmits (1030) a second R2D message including a segment#2 of the data SDU#1 to the AIoT device 110. If the indication indicates the last segment or the indication type#2 is set as “10” , the MAC layer may reassemble the original data SDU based on the store segment (s) or the reassembled (partial) data SDU#1. After that, the MAC layer may forward the reassembled data SDU or the original upper layer data SDU to the upper layer.
[0193] If the MAC layer has reassembled partial of the data SDU#1 based on segment#1, the MAC layer may further reassemble the data SDU#1 based on segment #2 and based on the offset information. That is, the MAC layer may process segment once received. The MAC layer may reassemble the received data SDU based on the start point or location as offset plus one.
[0194] If the MAC layer has not reassembled partial of the data SDU#1 based on the segment#1 and / or has stored the segment#1 of data SDU#1, the MAC layer may determine whether the second segment#2 is the last segment. If the segment#2 is the last segment, the MAC layer may reassemble the data SDU#1 based on the received segment#2 and the stored segment#1 or stored data SDU including segment#1. Otherwise, the MAC layer may store the segment#2 (or data SDU in the segment#2) or forward the segment #2 (or data SDU including the segment#2) to the upper layer.
[0195] If all segments are received, the AIoT device 110 may reassemble or obtain or reform the original upper layer data, the original data SDU or original message. The AIoT device 110 may transmit (1050) a data SDU or response, corresponding to the original upper layer data (e.g., data SDU#1) , to the RAN node 120. That is the MAC layer may not process segment till the last segment is received. For example, the MAC layer may reassemble the stored and received data SDUs (e.g., segments of the original data SDU) to form the original upper layer data according to the start point / location of each data SDU as its own offset plus one.
[0196] Alternatively, in some embodiments, the R2D message may include the field of upper layer data / data SDU and at least the field of offset information. The MAC layer may forward the received data SDU and offset information to the upper layer. The offset information may include offset type#1 to indicate the transmitted bytes of previous segment (s) , or offset type#2 to indicate the start point of the current segment (s) / the location of the segment in the original upper layer data SDU.
[0197] The upper layer may reform the original data SDU / the original upper layer data based on the received data SDU (s) (e.g., segments of the original data SDU) and offset information in R2D message. In an example, the upper layer of the AIoT device 110 may reassemble at least one segment of (original) data SDU forwarded from a MAC layer. In an example, in response to receiving a segment of (original) data SDU and offset information of the segment of (original) data SDU from the MAC layer, the upper layer may reassemble the (original) data SDU based on the offset information. That is, the upper layer may reassemble the received data SDU to form the (original) data SDU / the original upper layer data based on the offset information directly.
[0198] In another example, in response to receiving a last segment of (original) data SDU / the original upper layer data and offset information of the last segment of (original) data SDU from the MAC layer, the upper layer may reassemble the last data SDU with at least one stored data SDU based on the offset information of the last segment and stored offset information of the at least one stored SDU. That is, the upper layer may store the received data SDU (s) and reassemble the stored data SDU (s) if the last segment of data SDU is received. In addition, the MAC layer may indicate to the upper layer that one segment or one data SDU is the last segment of the original upper layer data. Alternatively or in addition, the MAC layer may indicate to the upper layer that the end of R2D transmission for the original upper layer data or the segments of the original upper layer data, or the end of R2D transmission. In addition, one timer may be used for the reassemble of segments to form the original upper layer data. For another example, if the first segment of the original upper layer data is received, the MAC layer or the upper layer of the AIoT device may start the timer or set the timer to an initial value. For another example, if the timer expires, the MAC layer or the upper layer of the AIoT device may drop all segments. In addition, if the original upper layer data is reformed, the timer may be stopped. The initial value of the timer may be configured by RAN node, such as gNB, or the CN node, such as AIoTF. In addition, the initial value of the timer may be predefined, preconfigured or may be set as a default value.
[0199] Further example embodiments will be described with respect to FIG. 11, which illustrates a signaling flow 1100 of data transmission related to AIoT device in accordance with some embodiments of the present disclosure. The signaling flow 1100 involves the AIoT device 110 and the RAN node 120 in FIG. 1A or FIG. 1B. The signaling flow 1100 is an example implementation of the signaling flow 900.
[0200] As shown, the RAN node 120 transmits (1110) a first R2D message including a segment#1 of original upper layer data (such as, data SDU#1) to the AIoT device 110. If the data SDU#1 is not the last segment or not an un-segmented data SDU / upper layer data, the AIoT device 110 may perform (1120) MAC layer operation. For example, the MAC layer may forward the segment once received. The MAC layer may forward the segment#1 of the data SDU#1 and its offset to the upper layer (s) . Alternatively, the MAC layer may not forward the segment till the last segment is received. If the segment#1 is not the last segment or not an un-segmented SDU / upper layer data, the MAC layer may store the received data SDU#1 or the segment#1 of the data SDU#1 and store the offset corresponding to this data SDU or segment. If the MAC layer may forward the segment#1 of the data SDU#1 to the upper layer, the upper layer may reassemble (1130) the data SDU#1 based on the segment of data SDU#1, or may store the segment#1 of data SDU#1.
[0201] The RAN node 120 transmits (1140) a second R2D message including a segment#2 of data SDU#1 to the AIoT device 110. If the segment#2 is not the last segment or un-segmented SDU, the MAC layer and upper layer may perform similar operations as described above. If the segment#2 is the last segment or an un-segmented SDU, the AIoT device 110 may perform (1150) a MAC layer operation. For example, the MAC layer may forward the segment once received to the upper layer (s) . The MAC layer may forward the data SDU#2 and its offset to the upper layer (s) . Alternatively, the MAC layer may not forward the segment (s) till the last segment is received. The MAC layer may forward all data SUDs or segments and corresponding offsets of these data SDUs / segments to the upper layer (s) .
[0202] In some embodiments, no matter the segment is the last segment or not, the MAC layer may forward the received segment once received. The MAC layer may forward the received data SDU (segment of the original upper layer data) and its offset to upper layer (s) .
[0203] The upper layer 1160 may reassemble (1160) the data SDU#1 based on the offset of segment#2 of data SDU#1, or may reassemble (1160) the segment#1 of data SDU#1 together with the segment#2 of data SDU#1 based on respective offsets.
[0204] In this manner, the original data SDU / the original upper layer data may be reassembled by the upper layer. The upper layer may generate a response message or data SDU of the response message corresponding to the original upper layer data. The AIoT device 110 may transmit (1170) the data SDU or response message to the RAN node 120.
[0205] Several embodiments regarding reassembling the segments of data SDUs based on the offsets have been described. With these embodiments, an indication of last segment or an indication of an end of R2D transmission may be used for the reassembling. The R2D segment and reassembling can thus be enabled.
[0206] Several embodiments regarding the data transmission associated with the AIoT have been described with respect to FIG. 3 to FIG. 12. It would be appreciated that some example specifications, signaling flows and embodiments are provided above, and the detailed description may be varied. It is to be understood that these signaling flows 300, 400, 500, 800, 1000, 1100 and / or 1200 may be used separately, or in any suitable combination. It is to be understood that these signaling flows 300, 400, 500, 800, 1000, 1100 and / or 1200 may involve any other suitable operations or signaling not shown. With these signaling flows and similar signaling flows, the data transmission associated with AIoT service can be managed and enhanced.
[0207] FIG. 13 illustrates a flowchart of a communication method 1300 implemented at an AIoT device in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 1300 will be described from the perspective of the AIoT device 110 in FIG. 1A or FIG. 1B.
[0208] FIG. 12 illustrates a flowchart of a communication method 1200 implemented at an AIoT device in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 1200 will be described from the perspective of the AIoT device 110 in FIG. 1A or FIG. 1B.
[0209] At block 1210, the AIoT device 110 receives, from a RAN node, a first message comprising at least one of: a first data SDU, or a first identifier associated with the first message.
[0210] At block 1220, the AIoT device 110 stores, by at least one of an upper layer of the AIoT device or a MAC layer of the AIoT device, at least one of: the first identifier, the first data SDU, a response message to the first message, or second data SDU to be included in the response message.
[0211] At block 1230, in response to receiving a second message from the RAN node, the AIoT device 110 determines whether the second message matches with the first message based on the stored at least one of: the first identifier, the response message, or the second data SDU.
[0212] In some example embodiments, the first message comprises a first R2D message comprising at least one of the first identifier or the first data SDU, and where the processor is further configured to cause the AIoT device to: perform, at the MAC layer, at least one of: indicating, to the upper layer, at least one of the first data SDU, or the first identifier, or storing at least one of the first data SDU or the first identifier.
[0213] In some example embodiments, in response to the first identifier being not stored by the AIoT device or no identifier being stored by the AIoT device, the AIoT device 110 may store at least one of the first data SDU or the first identifier.
[0214] In some example embodiments, the first data SDU comprises the first identifier or a second identifier associated with the first identifier.
[0215] In some example embodiments, the method 1200 further comprises: receiving, from the RAN node, a paging message comprising the first identifier; and in response to the first identifier being not stored by the AIoT device or no identifier being stored by the AIoT device, performing, at the MAC layer, at least one of: storing the first identifier; and indicating to the upper layer, the first identifier.
[0216] In some example embodiments, the method 1200 further comprises: determining whether the response message is to be segmented based on size information of at least one of the response message or the second data SDU; and in accordance with a determination that the response message is to be segmented, performing, at the MAC layer, at least one of: indicating the first identifier to the upper layer, storing the first data SDU, storing the second data SDU, or storing the response message.
[0217] In some example embodiments, the second message comprises a second R2D message comprising a third data SDU, and the third data SDU comprises a third identifier.
[0218] In some example embodiments, the second message comprises a second R2D message comprising a third identifier. The AIoT device 110 may perform, at the MAC layer, an operation comprising at least one of: indicating the third identifier to the upper layer, indicating stored first data SDU associated with the third identifier to the upper layer, generating an MAC PDU based on stored second data SDU or stored response message associated with the third identifier, or updating, based on offset information related to D2R message, the stored second data SDU, or the stored response message.
[0219] In some example embodiments, the second message comprises a second R2D message comprising an indication on at least one D2R resource. The AIoT device 110 may perform, at the MAC layer, an operation comprising at least one of: indicating a stored identifier to the upper layer, indicating stored first data SDU to the upper layer, generating an MAC PDU based on stored second data SDU or stored response message, or updating, based on offset information related to D2R message, the stored second data SDU, or the stored response message.
[0220] In some example embodiments, the second message comprises a second R2D message, and a third identifier associated with the second message is provided by a physical layer. The AIoT device 110 may perform, at the MAC layer, an operation comprising at least one of: indicating the third identifier to the upper layer, indicating stored first data SDU associated with the third identifier to the upper layer, generating an MAC PDU based on stored second data SDU or stored response message associated with the third identifier, or updating, based on offset information related to D2R message, the stored second data SDU, or the stored response message.
[0221] In some example embodiments, the method 1200 further comprises: in accordance with a determination that the second message matches with the first message, performing the operation at the MAC layer.
[0222] In some example embodiments, the AIoT device 110 may determine that the second message matches with the first message based on at least one of: a third identifier in the second message being stored at the MAC layer, at least part of an identifier stored at the MAC layer matching the third identifier, the third identifier being stored at the upper layer, at least part of an identifier stored at the upper layer matching the third identifier in the second message, a data SDU associated with the first message being stored at the MAC layer, or a data SDU associated with the first message being stored at the upper layer.
[0223] In some example embodiments, the second message excludes a data SDU, and / or where the MAC PDU is generated further based on the offset information.
[0224] In some example embodiments, an R2D message comprises offset information related to D2R message. In response to the offset information indicating zero or a predefined value, the AIoT device 110 may generate, at the MAC layer, a MAC PDU or data SDU from one of: a beginning bit or byte of original data SDU, a bit or byte of original data SDU indicated by the offset information, or a bit or byte of original data SDU indicated by the offset information plus one. In response to the offset information indicating a value different from zero and the predefined value, the AIoT device 110 may generate, at the MAC layer, a MAC PDU or data SDU from a bit or byte of original data SDU indicated by the value plus one.
[0225] In some example embodiments, the method 1200 further comprises: in response to offset information being included in an R2D message, generating, at the MAC layer, a MAC PDU or data SDU from a bit or byte of original data SDU indicated by the offset information plus one; and in response to the offset information being excluded from the R2D message, generating, at the MAC layer, a MAC PDU or data SDU from a beginning bit or byte of original data SDU.
[0226] In some example embodiments, the method 1200 further comprises: in response to no identifier being stored or no identifier associated with the R2D message being stored, generating, at the MAC layer, a MAC PDU or data SDU from a beginning bit or byte of original data SDU; and in response to an identifier associated with the R2D message being stored, generating, at the MAC layer, a MAC PDU or data SDU based on the offset information.
[0227] In some example embodiments, the R2D message is of a first type of MAC PDU, the first type of MAC PDU comprising at least one of: a field of offset information.
[0228] In some example embodiments, the R2D message comprises an indication indicating whether the field of offset information is included, or where an indication on a format of control information in the MAC layer indicates whether the field of offset information is included, or where an identifier in the R2D message indicates whether the field of offset information is included.
[0229] In some example embodiments, R2D message is of a second type of MAC PDU or a third type of MAC PDU, where the second type of MAC PDU at least comprises a field of offset information, and the third type of MAC PDU excludes the field of offset information.
[0230] In some example embodiments, the method further comprises: determining that the second message mismatches with the first message based on at least one of: no data SDU from the RAN node stored at the MAC layer, no stored data SDU from the upper layer, no stored identifier at the MAC layer, no data SDU from the RAN node stored at the upper layer, no stored identifier at the upper layer, an identifier in the second message mismatch with a stored identifier at the MAC layer, or an identifier in the second message mismatch with a stored identifier at the upper layer.
[0231] In some example embodiments, the method 1200 further comprises: in accordance with a determination that the second message mismatches with the first message, performing at least one of: transmitting an indication of the mismatching to the RAN node, refraining, at the MAC layer, from indicating to the upper layer, at least one of: third data SDU in the second message, third identifier in the second message, or stored data SDU; indicating, by the upper layer to the MAC layer, at least one of: an indication of indicating the mismatching to the RAN node, or an identifier of the RAN node, or generating, at the upper layer, a response to indicating the mismatching, and transmitting the response to the RAN node.
[0232] In some example embodiments, the method 1200 further comprises: in accordance with a determination that the second message matches with the first message, deriving, at the upper layer, fourth data SDU based on the third identifier associated with the second message, where the second message matches with the first message based on the third identifier being same as the first identifier, or being at least part of a second identifier associated with the first identifier.
[0233] In some example embodiments, at least one of the first message or the second message is of a fourth type of MAC PDU, the fourth type of MAC PDU comprising at least one of: a field of data SDU, a field of identifier, or format information of the first type of MAC PDU.
[0234] In some example embodiments, the format information comprises at least one of: an indication of a format of the MAC PDU, an indication indicating whether the field of data SDU is included, an indication indicating whether the field of identifier is included, or an indication indicating whether the field of data SDU and the field of identifier are included.
[0235] In some example embodiments, at least one of the first message or the second message is of a fifth type of MAC PDU or a sixth type of MAC PDU, where the fifth type of MAC PDU at least comprises a field of data SDU, and the sixth type of MAC PDU excludes the field of data SDU.
[0236] In some example embodiments, at least one of the fifth type of MAC PDU or the sixth type of MAC PDU comprises a field of identifier.
[0237] FIG. 13 illustrates a flowchart of a communication method 1300 implemented at an AIoT device in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 1300 will be described from the perspective of the AIoT device 110 in FIG. 1A or FIG. 1B.
[0238] At block 1310, the AIoT device 110 receives, from a RAN node, a R2D message comprising scheduling information of a D2R message.
[0239] At block 1320, the AIoT device 110 determines the D2R message based on the R2D message. The D2R message comprises at least one of: a data SDU, a field of length information associated with the D2R message, a first indication indicating whether the field of length information is included in the D2R message, a second indication indicating whether a field of padding is included in the D2R message, or a third indication indicating whether a data SDU is included in the D2R message.
[0240] At block 1330, the AIoT device 110 transmits the D2R message to the RAN node.
[0241] In some example embodiments, the field of length information indicates at least one of: a length of the data SDU, a length of MAC PDU excluding the field of padding, or a length of the field of padding.
[0242] In some example embodiments, the method 1300 further comprises: determining whether at least one condition is satisfied, the at least one condition comprising at least one of: the D2R message being to be segmented or further segmentation of the D2R message being to be transmitted; and in accordance with a determination that the at least one condition is satisfied, excluding at least one of the field of length information or the field of padding from a MAC PDU of the D2R message.
[0243] In some example embodiments, a length of the field of padding is less than or equal to a threshold, the field of length information is included and the field of padding is excluded from the D2R message.
[0244] FIG. 14 illustrates a flowchart of a communication method 1400 implemented at an AIoT device in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 1400 will be described from the perspective of the AIoT device 110 in FIG. 1A or FIG. 1B.
[0245] At block 1410, the AIoT device 110 receives, from a RAN node, at least one R2D message, the at least one R2D message comprising at least one segment of original upper layer and at least one of: at least one indication associated with the at least one segment, or at least one offset information associated with the at least one segment.
[0246] At block 1420, the AIoT device 110 reassembles the at least one segment to obtain the original upper layer based on at least one of the at least one indication or the at least one offset information. An indication associated with a segment of the data SDU indicates at least one of: whether the segment is a last segment, whether the original upper layer is segmented, whether the segment is a first segment, whether a further segment is after the segment, or an end of R2D transmission. Offset information associated with a segment of the original upper layer indicates at least one of: a type of a previous segment, a starting point of the segment in original upper layer, or a location of the segment in original upper layer.
[0247] In some example embodiments, in response to receiving a R2D message of the at least one R2D message, the AIoT device 110 may perform, at the MAC layer, at least one of: storing at least one of: a segment of original upper layer in the R2D message and offset information associated with the R2D message, forwarding the original upper layer and the offset information to an upper layer, or reassembling the original upper layer in the R2D message based on the offset information.
[0248] In some example embodiments, the at least one R2D message comprises a plurality of R2D messages, and in response to receiving a R2D message of the plurality of R2D messages, the R2D message being not the last R2D message, the AIoT device 110 may store a segment of original upper layer in the R2D message. In response to an indication of an R2D message indicating a last segment or an end of R2D transmission, the AIoT device 110 may perform, at the MAC layer, at least one of: forwarding the segment and the offset information to an upper layer, forwarding the segment and at least one stored segment and offset information of the segment and the at least one stored segment to the upper layer, reassembling the segment in the R2D message based on offset information associated with the R2D message, or reassembling the segment in the R2D message with at least one stored segment.
[0249] In some example embodiments, the method 1400 further comprises: in response to an indication of an R2D message indicating no segment, forwarding data SDU in the R2D message from a MAC layer to an upper layer.
[0250] In some example embodiments, the AIoT device 110 may reassemble, at an upper layer, at least one segment of original upper layer from a MAC layer.
[0251] In some example embodiments, in response to receiving a segment of original upper layer and offset information of the segment of original upper layer from the MAC layer, the AIoT device 110 may reassemble the original upper layer based on the offset information.
[0252] In some example embodiments, in response to receiving a last segment of data SDU and offset information of the last segment of original upper layer from the MAC layer, the AIoT device 110 may reassemble the last segment with at least one stored segment based on the offset information of the last segment and stored offset information of the at least one stored segment.
[0253] FIG. 15 illustrates a flowchart of a communication method 1500 implemented at a RAN node in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 1500 will be described from the perspective of the RAN node 120 in FIG. 1A or FIG. 1B.
[0254] At block 1510, the RAN node 120 transmits, to an AIoT device, a first message comprising at least one of: a first data SDU, or a first identifier associated with the first message.
[0255] At block 1520, the RAN node 120 transmits a second message to the AIoT device.
[0256] At block 1530, the RAN node 120 receives, from the AIoT device, one of: an indication of mismatching between the first message and the second message to the RAN node, or a response message to the first message or the second message.
[0257] In some example embodiments, the first message comprises a first R2D message comprising at least one of the first identifier or the first data SDU.
[0258] In some example embodiments, the first data SDU comprises the first identifier or a second identifier associated with the first identifier.
[0259] In some example embodiments, the method 1500 further comprises: transmitting, to the AIoT device, a paging message comprising the first identifier.
[0260] FIG. 16 illustrates a flowchart of a communication method 1600 implemented at a RAN node in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 1600 will be described from the perspective of the RAN node 120 in FIG. 1A or FIG. 1B.
[0261] At block 1610, the RAN node 120 transmits, to an AIoT device, a R2D message comprising scheduling information of a D2R message.
[0262] At block 1620, the RAN node 120 receive, from the AIoT device, the D2R message comprising at least one of: a data SDU, a field of length information associated with the D2R message, a first indication indicating whether the field of length information is included in the D2Rmessage, a second indication indicating whether a field of padding is included in the D2R message, or a third indication indicating whether a data SDU is included in the D2R message.
[0263] In some example embodiments, the field of length information indicates at least one of: a length of the data SDU, a length of MAC PDU excluding the field of padding, or a length of the field of padding.
[0264] In some example embodiments, a length of the field of padding is less than or equal to a threshold, and the field of length information is excluded from the D2R message.
[0265] FIG. 17 illustrates a flowchart of a communication method 1700 implemented at a RAN node in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 1700 will be described from the perspective of the RAN node 120 in FIG. 1A or FIG. 1B.
[0266] At block 1710, the RAN node 120 transmit, to an AIoT device, at least one R2D message, the at least one R2D message comprising at least one segment of original upper layer data and at least one of: at least one indication associated with the at least one segment, or at least one offset information associated with the at least one segment. An indication associated with a segment of the original upper layer data indicates at least one of: whether the segment is a last segment, whether the original upper layer data is segmented, whether the segment is a first segment, whether a further segment is after the segment, or an end of R2D transmission. Offset information associated with a segment of the original upper layer data indicates at least one of: a type of a previous segment, a starting point of the segment in original upper layer data, or a location of the segment in original upper layer data.
[0267] FIG. 18 is a simplified block diagram of a device 1800 that is suitable for implementing embodiments of the present disclosure. The device 1800 can be considered as a further example implementation of any of the devices as shown in FIG. 1 A or FIG. 1B. Accordingly, the device 1800 can be implemented at or as at least a part of the AIoT device 110 or the RAN node 120.
[0268] As shown, the device 1800 includes a processor 1810, a memory 1820 coupled to the processor 1810, a suitable transceiver 1840 coupled to the processor 1810, and a communication interface coupled to the transceiver 1840. The memory 1820 stores at least a part of a program 1830. The transceiver 1840 may be for bidirectional communications or a unidirectional communication based on requirements. The transceiver 1840 may include at least one of a transmitter 1842 and a receiver 1844. The transmitter 1842 and the receiver 1844 may be functional modules or physical entities. The transceiver 1840 has at least one antenna to facilitate communication, though in practice an Access Node mentioned in this application may have several ones. The communication interface may represent any interface that is necessary for communication with other network elements, such as X2 / Xn interface for bidirectional communications between eNBs / gNBs, S1 / NG interface for communication between a Mobility Management Entity (MME) / Access and Mobility Management Function (AMF) / SGW / UPF and the eNB / gNB, Un interface for communication between the eNB / gNB and a relay node (RN) , or Uu interface for communication between the eNB / gNB and a terminal device.
[0269] The program 1830 is assumed to include program instructions that, when executed by the associated processor 1810, enable the device 1800 to operate in accordance with the embodiments of the present disclosure, as discussed herein with reference to FIGS. 1 A to 17. The embodiments herein may be implemented by computer software executable by the processor 1810 of the device 1800, or by hardware, or by a combination of software and hardware. The processor 1810 may be configured to implement various embodiments of the present disclosure. Furthermore, a combination of the processor 1810 and memory 1820 may form processing means 1850 adapted to implement various embodiments of the present disclosure.
[0270] The memory 1820 may be of any type suitable to the local technical network and may be implemented using any suitable data storage technology, such as a non-transitory computer readable storage medium, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples. While only one memory 1820 is shown in the device 1800, there may be several physically distinct memory modules in the device 1800. The processor 1810 may be of any type suitable to the local technical network, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 1800 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
[0271] According to embodiments of the present disclosure, an AIoT device comprising a circuitry is provided. The circuitry is configured to: receive, from a RAN node, a first message comprising at least one of: a first data SDU, or a first identifier associated with the first message; store, by at least one of an upper layer of the AIoT device or a MAC layer of the AIoT device, at least one of: the first identifier, a response message to the first message, or second data SDU to be included in the response message; and in response to receiving a second message from the RAN node, determine whether the second message matches with the first message based on the stored at least one of: the first identifier, the response message, or the second data SDU. According to embodiments of the present disclosure, the circuitry may be configured to perform any method implemented by the AIoT device as discussed above.
[0272] According to embodiments of the present disclosure, an AIoT device comprising a circuitry is provided. The circuitry is configured to: receive, from a RAN node, a R2D message comprising scheduling information of a D2R message; determine the D2R message based on the R2D message, where the D2R message comprises at least one of: a data SDU, a field of length information associated with the D2R message, a first indication indicating whether the field of length information is included in the D2R message, a second indication indicating whether a field of padding is included in the D2R message, or a third indication indicating whether a data SDU is included in the D2R message; and transmit the D2R message to the RAN node. According to embodiments of the present disclosure, the circuitry may be configured to perform any method implemented by the AIoT device as discussed above.
[0273] According to embodiments of the present disclosure, an AIoT device comprising a circuitry is provided. The circuitry is configured to: receive, from a RAN node, at least one R2D message, the at least one R2D message comprising at least one segment of original upper layer data and at least one of: at least one indication associated with the at least one segment, or at least one offset information associated with the at least one segment; and reassemble the at least one segment to obtain the original upper layer data based on at least one of the at least one indication or the at least one offset information, where an indication associated with a segment of the original upper layer data indicates at least one of: whether the segment is a last segment, whether the original upper layer data is segmented, whether the segment is a first segment, whether a further segment is after the segment, or an end of R2D transmission, and where offset information associated with a segment of the original upper layer data indicates at least one of: a type of a previous segment, a starting point of the segment in original upper layer data, or a location of the segment in original upper layer data. According to embodiments of the present disclosure, the circuitry may be configured to perform any method implemented by the AIoT device as discussed above.
[0274] According to embodiments of the present disclosure, a RAN node comprising a circuitry is provided. The circuitry is configured to: transmit, to an AIoT device, a first message comprising at least one of: a first data SDU, or a first identifier associated with the first message; transmit a second message to the AIoT device; and receive, from the AIoT device, one of: an indication of mismatching between the first message and the second message to the RAN node, or a response message to the first message or the second message. According to embodiments of the present disclosure, the circuitry may be configured to perform any method implemented by the RAN node as discussed above.
[0275] According to embodiments of the present disclosure, a RAN node comprising a circuitry is provided. The circuitry is configured to: transmit, to an AIoT device, a R2D message comprising scheduling information of a D2R message; and receive, from the AIoT device, the D2R message comprising at least one of: a data SDU, a field of length information associated with the D2R message, a first indication indicating whether the field of length information is included in the D2Rmessage, a second indication indicating whether a field of padding is included in the D2R message, or a third indication indicating whether a data SDU is included in the D2R message. According to embodiments of the present disclosure, the circuitry may be configured to perform any method implemented by the RAN node as discussed above.
[0276] According to embodiments of the present disclosure, a RAN node comprising a circuitry is provided. The circuitry is configured to: transmit, to an AIoT device, at least one R2D message, the at least one R2D message comprising at least one segment of original upper layer data and at least one of: at least one indication associated with the at least one segment, or at least one offset information associated with the at least one segment, where an indication associated with a segment of the original upper layer data indicates at least one of: whether the segment is a last segment, whether the original upper layer data is segmented, whether the segment is a first segment, whether a further segment is after the segment, or an end of R2D transmission, and where offset information associated with a segment of the original upper layer data indicates at least one of: a type of a previous segment, a starting point of the segment in original upper layer data, or a location of the segment in original upper layer data. According to embodiments of the present disclosure, the circuitry may be configured to perform any method implemented by the RAN node as discussed above.
[0277] The term “circuitry” used herein may refer to hardware circuits and / or combinations of hardware circuits and software. For example, the circuitry may be a combination of analog and / or digital hardware circuits with software / firmware. As a further example, the circuitry may be any portions of hardware processors with software including digital signal processor (s) , software, and memory (ies) that work together to cause an apparatus, such as a terminal device or a network device, to perform various functions. In a still further example, the circuitry may be hardware circuits and or processors, such as a microprocessor or a portion of a microprocessor, that requires software / firmware for operation, but the software may not be present when it is not needed for operation. As used herein, the term circuitry also covers an implementation of merely a hardware circuit or processor (s) or a portion of a hardware circuit or processor (s) and its (or their) accompanying software and / or firmware.
[0278] According to embodiments of the present disclosure, a first apparatus is provided. The first apparatus comprises means for receiving, from a RAN node, a first message comprising at least one of: a first data SDU, or a first identifier associated with the first message; means for storing, by at least one of an upper layer of the AIoT device or a MAC layer of the AIoT device, at least one of: the first identifier, a response message to the first message, or second data SDU to be included in the response message; and means for in response to receiving a second message from the RAN node, determining whether the second message matches with the first message based on the stored at least one of: the first identifier, the response message, or the second data SDU. In some embodiments, the first apparatus may comprise means for performing the respective operations of the method 1200. In some example embodiments, the first apparatus may further comprise means for performing other operations in some example embodiments of the method 1200. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.
[0279] According to embodiments of the present disclosure, a second apparatus is provided. The second apparatus comprises means for receiving, from a RAN node, a R2D message comprising scheduling information of a D2R message; means for determining the D2R message based on the R2D message, where the D2R message comprises at least one of: a data SDU, a field of length information associated with the D2R message, a first indication indicating whether the field of length information is included in the D2R message, a second indication indicating whether a field of padding is included in the D2R message, or a third indication indicating whether a data SDU is included in the D2R message; and means for transmitting the D2R message to the RAN node. In some embodiments, the second apparatus may comprise means for performing the respective operations of the method 1300. In some example embodiments, the second apparatus may further comprise means for performing other operations in some example embodiments of the method 1300. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.
[0280] According to embodiments of the present disclosure, a third apparatus is provided. The third apparatus comprises means for receiving, from a RAN node, at least one R2D message, the at least one R2D message comprising at least one segment of original upper layer data and at least one of: at least one indication associated with the at least one segment, or at least one offset information associated with the at least one segment; and means for reassembling the at least one segment to obtain the original upper layer data based on at least one of the at least one indication or the at least one offset information, where an indication associated with a segment of the original upper layer data indicates at least one of: whether the segment is a last segment, whether the original upper layer data is segmented, whether the segment is a first segment, whether a further segment is after the segment, or an end of R2D transmission, and where offset information associated with a segment of the original upper layer data indicates at least one of: a type of a previous segment, a starting point of the segment in original upper layer data, or a location of the segment in original upper layer data. In some embodiments, the third apparatus may comprise means for performing the respective operations of the method 1400. In some example embodiments, the third apparatus may further comprise means for performing other operations in some example embodiments of the method 1400. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.
[0281] According to embodiments of the present disclosure, a fourth apparatus is provided. The fourth apparatus comprises means for transmitting, to an AIoT device, a first message comprising at least one of: a first data SDU, or a first identifier associated with the first message; means for transmitting a second message to the AIoT device; and means for receiving, from the AIoT device, one of: an indication of mismatching between the first message and the second message to the RAN node, or a response message to the first message or the second message. In some embodiments, the fourth apparatus may comprise means for performing the respective operations of the method 1500. In some example embodiments, the fourth apparatus may further comprise means for performing other operations in some example embodiments of the method 1500. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.
[0282] According to embodiments of the present disclosure, a fifth apparatus is provided. The fifth apparatus comprises means for transmitting, to an AIoT device, a R2D message comprising scheduling information of a D2R message; and means for receiving, from the AIoT device, the D2R message comprising at least one of: a data SDU, a field of length information associated with the D2R message, a first indication indicating whether the field of length information is included in the D2Rmessage, a second indication indicating whether a field of padding is included in the D2R message, or a third indication indicating whether a data SDU is included in the D2R message. In some embodiments, the fifth apparatus may comprise means for performing the respective operations of the method 1600. In some example embodiments, the fifth apparatus may further comprise means for performing other operations in some example embodiments of the method 1600. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.
[0283] According to embodiments of the present disclosure, a sixth apparatus is provided. The sixth apparatus comprises means for transmitting, to an AIoT device, at least one R2D message, the at least one R2D message comprising at least one segment of original upper layer data and at least one of: at least one indication associated with the at least one segment, or at least one offset information associated with the at least one segment, where an indication associated with a segment of the original upper layer data indicates at least one of: whether the segment is a last segment, whether the original upper layer data is segmented, whether the segment is a first segment, whether a further segment is after the segment, or an end of R2D transmission, and where offset information associated with a segment of the original upper layer data indicates at least one of: a type of a previous segment, a starting point of the segment in original upper layer data, or a location of the segment in original upper layer data. In some embodiments, the sixth apparatus may comprise means for performing the respective operations of the method 1700. In some example embodiments, the sixth apparatus may further comprise means for performing other operations in some example embodiments of the method 1700. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.
[0284] In summary, embodiments of the present disclosure provide the following aspects.
[0285] In an aspect, it is proposed an AIoT device comprising: a processor configured to cause the AIoT device to: receive, from a RAN node, a first message comprising at least one of: a first data SDU, or a first identifier associated with the first message; store, by at least one of an upper layer of the AIoT device or a MAC layer of the AIoT device, at least one of: the first identifier, a response message to the first message, or second data SDU to be included in the response message; and in response to receiving a second message from the RAN node, determine whether the second message matches with the first message based on the stored at least one of: the first identifier, the response message, or the second data SDU.
[0286] In some embodiments, the first message comprises a first R2D message comprising at least one of the first identifier or the first data SDU, and where the processor is further configured to cause the AIoT device to: perform, at the MAC layer, at least one of: indicating, to the upper layer, at least one of the first data SDU, or the first identifier, or storing at least one of the first data SDU or the first identifier.
[0287] In some embodiments, the processor is further configured to cause the AIoT device to: in response to the first identifier being not stored by the AIoT device or no identifier being stored by the AIoT device, store at least one of the first data SDU or the first identifier.
[0288] In some embodiments, the first data SDU comprises the first identifier or a second identifier associated with the first identifier.
[0289] In some embodiments, the processor is further configured to cause the AIoT device to: receive, from the RAN node, a paging message comprising the first identifier; and in response to the first identifier being not stored by the AIoT device or no identifier being stored by the AIoT device, perform, at the MAC layer, at least one of: storing the first identifier; and indicating to the upper layer, the first identifier.
[0290] In some embodiments, the processor is further configured to cause the AIoT device to: determine whether the response message is to be segmented based on size information of at least one of the response message or the second data SDU; and in accordance with a determination that the response message is to be segmented, perform, at the MAC layer, at least one of: indicating the first identifier to the upper layer, storing the first data SDU, storing the second data SDU, or storing the response message.
[0291] In some embodiments, the second message comprises a second R2D message comprising a third data SDU, and the third data SDU comprises a third identifier.
[0292] In some embodiments, the second message comprises a second R2D message comprising a third identifier, and where the processor is further configured to cause the AIoT device to: perform, at the MAC layer, an operation comprising at least one of: indicating the third identifier to the upper layer, indicating stored first data SDU associated with the third identifier to the upper layer, generating an MAC PDU based on stored second data SDU or stored response message associated with the third identifier, or updating, based on offset information related to D2R message, the stored second data SDU, or the stored response message.
[0293] In some embodiments, the second message comprises a second R2D message comprising an indication on at least one D2R resource, where the processor is further configured to cause the AIoT device to: perform, at the MAC layer, an operation comprising at least one of: indicating a stored identifier to the upper layer, indicating stored first data SDU to the upper layer, generating an MAC PDU based on stored second data SDU or stored response message, or updating, based on offset information related to D2R message, the stored second data SDU, or the stored response message.
[0294] In some embodiments, the second message comprises a second R2D message, and a third identifier associated with the second message is provided by a physical layer, and where the processor is further configured to cause the AIoT device to: perform, at the MAC layer, an operation comprising at least one of: indicating the third identifier to the upper layer, indicating stored first data SDU associated with the third identifier to the upper layer, generating an MAC PDU based on stored second data SDU or stored response message associated with the third identifier, or updating, based on offset information related to D2R message, the stored second data SDU, or the stored response message.
[0295] In some embodiments, the processor is further configured to cause the AIoT device to: in accordance with a determination that the second message matches with the first message, perform the operation at the MAC layer.
[0296] In some embodiments, the processor is further configured to cause the AIoT device to: determine that the second message matches with the first message based on at least one of: a third identifier in the second message being stored at the MAC layer, at least part of an identifier stored at the MAC layer matching the third identifier, the third identifier being stored at the upper layer, at least part of an identifier stored at the upper layer matching the third identifier in the second message, a data SDU associated with the first message being stored at the MAC layer, or a data SDU associated with the first message being stored at the upper layer.
[0297] In some embodiments, the second message excludes a data SDU, and / or where the MAC PDU is generated further based on the offset information.
[0298] In some embodiments, an R2D message comprises offset information related to D2R message, and where the processor is further configured to cause the AIoT device to: in response to the offset information indicating zero or a predefined value, generate, at the MAC layer, a MAC PDU or data SDU from one of: a beginning bit or byte of original data SDU, a bit or byte of original data SDU indicated by the offset information, or a bit or byte of original data SDU indicated by the offset information plus one; and in response to the offset information indicating a value different from zero and the predefined value, generate, at the MAC layer, a MAC PDU or data SDU from a bit or byte of original data SDU indicated by the value plus one.
[0299] In some embodiments, the processor is further configured to cause the AIoT device to: in response to offset information being included in an R2D message, generate, at the MAC layer, a MAC PDU or data SDU from a bit or byte of original data SDU indicated by the offset information plus one; and in response to the offset information being excluded from the R2D message, generate, at the MAC layer, a MAC PDU or data SDU from a beginning bit or byte of original data SDU.
[0300] In some embodiments, the processor is further configured to cause the AIoT device to: in response to no identifier being stored or no identifier associated with the R2D message being stored, generate, at the MAC layer, a MAC PDU or data SDU from a beginning bit or byte of original data SDU; and in response to an identifier associated with the R2D message being stored, generate, at the MAC layer, a MAC PDU or data SDU based on the offset information.
[0301] In some embodiments, the R2D message is of a first type of MAC PDU, the first type of MAC PDU comprising at least one of: a field of offset information.
[0302] In some embodiments, the R2D message comprises an indication indicating whether the field of offset information is included, or where an indication on a format of control information in the MAC layer indicates whether the field of offset information is included, or where an identifier in the R2D message indicates whether the field of offset information is included.
[0303] In some embodiments, R2D message is of a second type of MAC PDU or a third type of MAC PDU, where the second type of MAC PDU at least comprises a field of offset information, and the third type of MAC PDU excludes the field of offset information.
[0304] In some embodiments, the processor is further configured to cause the AIoT device to: determine that the second message mismatches with the first message based on at least one of: no data SDU from the RAN node stored at the MAC layer, no stored data SDU from the upper layer, no stored identifier at the MAC layer, no data SDU from the RAN node stored at the upper layer, no stored identifier at the upper layer, an identifier in the second message mismatch with a stored identifier at the MAC layer, or an identifier in the second message mismatch with a stored identifier at the upper layer.
[0305] In some embodiments, the processor is further configured to cause the AIoT device to: in accordance with a determination that the second message mismatches with the first message, perform at least one of: transmitting an indication of the mismatching to the RAN node, refraining, at the MAC layer, from indicating to the upper layer, at least one of: third data SDU in the second message, third identifier in the second message, or stored data SDU; indicating, by the upper layer to the MAC layer, at least one of: an indication of indicating the mismatching to the RAN node, or an identifier of the RAN node, or generating, at the upper layer, a response to indicating the mismatching, and transmitting the response to the RAN node.
[0306] In some embodiments, the processor is further configured to cause the AIoT device to: in accordance with a determination that the second message matches with the first message, derive, at the upper layer, fourth data SDU based on the third identifier associated with the second message, where the second message matches with the first message based on the third identifier being same as the first identifier, or being at least part of a second identifier associated with the first identifier.
[0307] In some embodiments, at least one of the first message or the second message is of a fourth type of MAC PDU, the fourth type of MAC PDU comprising at least one of: a field of data SDU, a field of identifier, or format information of the first type of MAC PDU.
[0308] In some embodiments, the format information comprises at least one of: an indication of a format of the MAC PDU, an indication indicating whether the field of data SDU is included, an indication indicating whether the field of identifier is included, or an indication indicating whether the field of data SDU and the field of identifier are included.
[0309] In some embodiments, at least one of the first message or the second message is of a fifth type of MAC PDU or a sixth type of MAC PDU, where the fifth type of MAC PDU at least comprises a field of data SDU, and the sixth type of MAC PDU excludes the field of data SDU.
[0310] In some embodiments, at least one of the fifth type of MAC PDU or the sixth type of MAC PDU comprises a field of identifier.
[0311] In an aspect, it is proposed an AIoT device comprising: a processor configured to cause the AIoT device to: receive, from a RAN node, a R2D message comprising scheduling information of a D2R message; determine the D2R message based on the R2D message, where the D2R message comprises at least one of: a data SDU, a field of length information associated with the D2R message, a first indication indicating whether the field of length information is included in the D2R message, a second indication indicating whether a field of padding is included in the D2R message, or a third indication indicating whether a data SDU is included in the D2R message; and transmit the D2R message to the RAN node.
[0312] In some embodiments, the field of length information indicates at least one of: a length of the data SDU, a length of MAC PDU excluding the field of padding, or a length of the field of padding.
[0313] In some embodiments, the processor is further configured to cause the AIoT device to: determine whether at least one condition is satisfied, the at least one condition comprising at least one of: the D2R message being to be segmented or further segmentation of the D2R message being to be transmitted; and in accordance with a determination that the at least one condition is satisfied, exclude at least one of the field of length information or the field of padding from a MAC PDU of the D2R message.
[0314] In some embodiments, a length of the field of padding is less than or equal to a threshold, the field of length information is included and the field of padding is excluded from the D2R message.
[0315] In an aspect, it is proposed an AIoT device comprising: a processor configured to cause the AIoT device to: receive, from a RAN node, at least one R2D message, the at least one R2D message comprising at least one segment of original upper layer data and at least one of: at least one indication associated with the at least one segment, or at least one offset information associated with the at least one segment; and reassemble the at least one segment to obtain the original upper layer data based on at least one of the at least one indication or the at least one offset information, where an indication associated with a segment of the original upper layer data indicates at least one of: whether the segment is a last segment, whether the original upper layer data is segmented, whether the segment is a first segment, whether a further segment is after the segment, or an end of R2D transmission, and where offset information associated with a segment of the data SDU indicates at least one of: a type of a previous segment, a starting point of the segment in original upper layer data, or a location of the segment in original upper layer data.
[0316] In some embodiments, the processor is further configured to cause the AIoT device to: in response to receiving a R2D message of the at least one R2D message, perform, at the MAC layer, at least one of: storing at least one of: a segment of data SDU in the R2D message and offset information associated with the R2D message, forwarding the data SDU and the offset information to an upper layer, or reassembling the data SDU in the R2D message based on the offset information.
[0317] In some embodiments, the at least one R2D message comprises a plurality of R2D messages, and where the processor is further configured to cause the AIoT device to: in response to receiving a R2D message of the plurality of R2D messages, the R2D message being not the last R2D message, store a segment of data SDU in the R2D message; and in response to an indication of an R2D message indicating a last segment or an end of R2D transmission, perform, at the MAC layer, at least one of: forwarding the data SDU and the offset information to an upper layer, forwarding the data SDU and at least one stored SDU and offset information of the data SDU and the at least one stored SDU to the upper layer, reassembling data SDU in the R2D message based on offset information associated with the R2D message, or reassembling the data SDU in the R2D message with at least one stored data SDU.
[0318] In some embodiments, the processor is further configured to cause the AIoT device to: in response to an indication of an R2D message indicating no segment, forward data SDU in the R2D message from a MAC layer to an upper layer.
[0319] In some embodiments, the processor is further configured to cause the AIoT device to: reassemble, at an upper layer, at least one segment of data SDU from a MAC layer.
[0320] In some embodiments, the processor is further configured to cause the AIoT device to: in response to receiving a segment of data SDU and offset information of the segment of data SDU from the MAC layer, reassemble the data SDU based on the offset information.
[0321] In some embodiments, the processor is further configured to cause the AIoT device to: in response to receiving a last segment of data SDU and offset information of the last segment of data SDU from the MAC layer, reassemble the last data SDU with at least one stored data SDU based on the offset information of the last segment and stored offset information of the at least one stored SDU.
[0322] In an aspect, it is proposed a RAN node comprising: a processor configured to cause the RAN node to: transmit, to an AIoT device, a first message comprising at least one of: a first data SDU, or a first identifier associated with the first message; transmit a second message to the AIoT device; and receive, from the AIoT device, one of: an indication of mismatching between the first message and the second message to the RAN node, or a response message to the first message or the second message.
[0323] In some embodiments, the first message comprises a first R2D message comprising at least one of the first identifier or the first data SDU.
[0324] In some embodiments, the first data SDU comprises the first identifier or a second identifier associated with the first identifier.
[0325] In some embodiments, the processor is further configured to cause the RAN node to: transmit, to the AIoT device, a paging message comprising the first identifier.
[0326] In an aspect, it is proposed a RAN node comprising: a processor configured to cause the RAN node to: transmit, to an AIoT device, a R2D message comprising scheduling information of a D2R message; and receive, from the AIoT device, the D2R message comprising at least one of: a data SDU, a field of length information associated with the D2R message, a first indication indicating whether the field of length information is included in the D2Rmessage, a second indication indicating whether a field of padding is included in the D2R message, or a third indication indicating whether a data SDU is included in the D2R message.
[0327] In some embodiments, the field of length information indicates at least one of: a length of the data SDU, a length of MAC PDU excluding the field of padding, or a length of the field of padding.
[0328] In some embodiments, a length of the field of padding is less than or equal to a threshold, and the field of length information is excluded from the D2R message.
[0329] In an aspect, it is proposed a RAN node comprising: a processor configured to cause the RAN node to: transmit, to an AIoT device, at least one R2D message, the at least one R2D message comprising at least one segment of original upper layer data and at least one of: at least one indication associated with the at least one segment, or at least one offset information associated with the at least one segment, where an indication associated with a segment of the original upper layer data indicates at least one of: whether the segment is a last segment, whether the original upper layer data is segmented, whether the segment is a first segment, whether a further segment is after the segment, or an end of R2D transmission, and where offset information associated with a segment of the original upper layer data indicates at least one of: a type of a previous segment, a starting point of the segment in original upper layer data, or a location of the segment in original upper layer data.
[0330] In an aspect, an AIoT device comprises: at least one processor; and at least one memory coupled to the at least one processor and storing instructions thereon, the instructions, when executed by the at least one processor, causing the device to perform the method implemented by the AIoT device discussed above.
[0331] In an aspect, an AIoT device comprises: at least one processor; and at least one memory coupled to the at least one processor and storing instructions thereon, the instructions, when executed by the at least one processor, causing the device to perform the method implemented by the AIoT device discussed above.
[0332] In an aspect, an AIoT device comprises: at least one processor; and at least one memory coupled to the at least one processor and storing instructions thereon, the instructions, when executed by the at least one processor, causing the device to perform the method implemented by the AIoT device discussed above.
[0333] In an aspect, a RAN node comprises: at least one processor; and at least one memory coupled to the at least one processor and storing instructions thereon, the instructions, when executed by the at least one processor, causing the device to perform the method implemented by the RAN node discussed above.
[0334] In an aspect, a RAN node comprises: at least one processor; and at least one memory coupled to the at least one processor and storing instructions thereon, the instructions, when executed by the at least one processor, causing the device to perform the method implemented by the RAN node discussed above.
[0335] In an aspect, a RAN node comprises: at least one processor; and at least one memory coupled to the at least one processor and storing instructions thereon, the instructions, when executed by the at least one processor, causing the device to perform the method implemented by the RAN node discussed above.
[0336] In an aspect, a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the AIoT device discussed above.
[0337] In an aspect, a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the AIoT device discussed above.
[0338] In an aspect, a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the AIoT device discussed above.
[0339] In an aspect, a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the RAN node discussed above.
[0340] In an aspect, a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the RAN node discussed above.
[0341] In an aspect, a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the RAN node discussed above.
[0342] In an aspect, a computer program comprising instructions, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the AIoT device discussed above.
[0343] In an aspect, a computer program comprising instructions, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the AIoT device discussed above.
[0344] In an aspect, a computer program comprising instructions, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the AIoT device discussed above.
[0345] In an aspect, a computer program comprising instructions, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the RAN node discussed above.
[0346] In an aspect, a computer program comprising instructions, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the RAN node discussed above.
[0347] In an aspect, a computer program comprising instructions, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the RAN node discussed above.
[0348] Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representation, it will be appreciated that the blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
[0349] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the process or method as described above with reference to FIGS. 1 to 18. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
[0350] Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
[0351] The above program code may be embodied on a machine readable medium, which may be any tangible medium that may contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine readable medium may be a machine readable signal medium or a machine readable storage medium. A machine readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the machine readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0352] Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable sub-combination.
[0353] Although the present disclosure has been described in language specific to structural features and / or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Claims
1.An ambient Internet of things (AIoT) device comprising:a processor configured to cause the AIoT device to:receive, from a radio access network (RAN) node, a first message comprising at least one of: a first data service data unit (SDU) , or a first identifier associated with the first message;store, by at least one of an upper layer of the AIoT device or a medium access control (MAC) layer of the AIoT device, at least one of: the first identifier, the first data SDU, a response message to the first message, or second data SDU to be included in the response message; andin response to receiving a second message from the RAN node, determine whether the second message matches with the first message based on the stored at least one of: the first identifier, the response message, or the second data SDU.2.The AIoT device of claim 1, wherein the first message comprises a first reader to device (R2D) message comprising at least one of the first identifier or the first data SDU, and wherein the processor is further configured to cause the AIoT device to:perform, at the MAC layer, at least one of:indicating, to the upper layer, at least one of the first data SDU, or the first identifier, orstoring at least one of the first data SDU or the first identifier.3.The AIoT device of claim 2, wherein the processor is further configured to cause the AIoT device to:in response to the first identifier being not stored by the AIoT device or no identifier being stored by the AIoT device, store at least one of the first data SDU or the first identifier.4.The AIoT device of claim 2, wherein the first data SDU comprises the first identifier or a second identifier associated with the first identifier.5.The AIoT device of any of claims 1-4, wherein the processor is further configured to cause the AIoT device to:receive, from the RAN node, a paging message comprising the first identifier; andin response to the first identifier being not stored by the AIoT device or no identifier being stored by the AIoT device, perform, at the MAC layer, at least one of:storing the first identifier; orindicating to the upper layer, the first identifier.6.The AIoT device of any of claims 1-5, wherein the processor is further configured to cause the AIoT device to:determine whether the response message is to be segmented based on size information of at least one of the response message or the second data SDU; andin accordance with a determination that the response message is to be segmented, perform, at the MAC layer, at least one of:indicating the first identifier to the upper layer,storing the first data SDU,storing the second data SDU, orstoring the response message.7.The AIoT device of any of claims 1-6, wherein the second message comprises a second R2D message comprising a third data SDU, and the third data SDU comprises a third identifier.8.The AIoT device of any of claims 1-6, wherein the second message comprises a second R2D message comprising a third identifier, andwherein the processor is further configured to cause the AIoT device to: perform, at the MAC layer, an operation comprising at least one of:indicating the third identifier to the upper layer,indicating stored first data SDU associated with the third identifier to the upper layer,generating an MAC protocol data unit (PDU) based on stored second data SDU or stored response message associated with the third identifier, orupdating, based on offset information related to device to reader (D2R) message, the stored second data SDU, or the stored response message.9.The AIoT device of any of claims 1-6, wherein the second message comprises a second R2D message comprising an indication on at least one device to reader (D2R) resource,wherein the processor is further configured to cause the AIoT device to: perform, at the MAC layer, an operation comprising at least one of:indicating a stored identifier to the upper layer,indicating stored first data SDU to the upper layer,generating an MAC protocol data unit (PDU) based on stored second data SDU or stored response message, orupdating, based on offset information related to device to reader (D2R) message, the stored second data SDU, or the stored response message.10.The AIoT device of any of claims 1-6, wherein the second message comprises a second R2D message, and a third identifier associated with the second message is provided by a physical layer, andwherein the processor is further configured to cause the AIoT device to: perform, at the MAC layer, an operation comprising at least one of:indicating the third identifier to the upper layer,indicating stored first data SDU associated with the third identifier to the upper layer,generating an MAC protocol data unit (PDU) based on stored second data SDU or stored response message associated with the third identifier, orupdating, based on offset information related to device to reader (D2R) message, the stored second data SDU, or the stored response message.11.The AIoT device of any of claims 8-10, wherein the processor is further configured to cause the AIoT device to:in accordance with a determination that the second message matches with the first message, perform the operation at the MAC layer.12.The AIoT device of claim 11, wherein the processor is further configured to cause the AIoT device to: determine that the second message matches with the first message based on at least one of:a third identifier in the second message being stored at the MAC layer,at least part of an identifier stored at the MAC layer matching the third identifier,the third identifier being stored at the upper layer,at least part of an identifier stored at the upper layer matching the third identifier in the second message,a data SDU associated with the first message being stored at the MAC layer, ora data SDU associated with the first message being stored at the upper layer.13.The AIoT device of any of claims 1-12, wherein the processor is further configured to cause the AIoT device to:in response to offset information being included in an R2D message, generate, at the MAC layer, a MAC PDU or data SDU from a bit or byte of original data SDU indicated by the offset information plus one; andin response to the offset information being excluded from the R2D message, generate, at the MAC layer, a MAC PDU or data SDU from a beginning bit or byte of original data SDU.14.The AIoT device of claim 13, wherein the processor is further configured to cause the AIoT device to:in response to no identifier being stored or no identifier associated with the R2D message being stored, generate, at the MAC layer, a MAC PDU or data SDU from a beginning bit or byte of original data SDU; andin response to an identifier associated with the R2D message being stored, generate, at the MAC layer, a MAC PDU or data SDU based on the offset information.15.The AIoT device of any of claims 13-14, wherein the R2D message is of a first type of MAC protocol data unit (PDU) , the first type of MAC PDU comprising a field of offset information.16.The AIoT device of claim 15, wherein the R2D message comprises an indication indicating whether the field of offset information is included, orwherein an indication on a format of control information in the MAC layer indicates whether the field of offset information is included, orwherein an identifier in the R2D message indicates whether the field of offset information is included.17.The AIoT device of any of claims 1-16, wherein the processor is further configured to cause the AIoT device to: determine that the second message mismatches with the first message based on at least one of:no data SDU from the RAN node stored at the MAC layer,no stored data SDU from the upper layer,no stored identifier at the MAC layer,no data SDU from the RAN node stored at the upper layer,no stored identifier at the upper layer,an identifier in the second message mismatch with a stored identifier at the MAC layer, oran identifier in the second message mismatch with a stored identifier at the upper layer.18.The AIoT device of any of claims 1-17, wherein the processor is further configured to cause the AIoT device to:in accordance with a determination that the second message mismatches with the first message, perform at least one of:transmitting an indication of the mismatching to the RAN node,refraining, at the MAC layer, from indicating to the upper layer, at least one of: third data SDU in the second message, third identifier in the second message, or stored data SDU,indicating, by the upper layer to the MAC layer, at least one of: an indication of indicating the mismatching to the RAN node, or an identifier of the RAN node, orgenerating, at the upper layer, a response to indicating the mismatching, and transmitting the response to the RAN node.19.The AIoT device of any of claims 1-18, wherein at least one of the first message or the second message is of a fourth type of MAC protocol data unit (PDU) , the fourth type of MAC PDU comprising at least one of: a field of data SDU, a field of identifier, or format information of the first type of MAC PDU.20.The AIoT device of claim 19, wherein the format information comprises at least one of:an indication of a format of the MAC PDU,an indication indicating whether the field of data SDU is included,an indication indicating whether the field of identifier is included, oran indication indicating whether the field of data SDU and the field of identifier are included.21.An ambient Internet of things (AIoT) device comprising:a processor configured to cause the AIoT device to:receive, from a radio access network (RAN) node, a reader to device (R2D) message comprising scheduling information of a device to reader (D2R) message;determine the D2R message based on the R2D message, wherein the D2R message comprises at least one of: a data service data unit (SDU) , a field of length information associated with the D2R message, a first indication indicating whether the field of length information is included in the D2R message, a second indication indicating whether a field of padding is included in the D2R message, or a third indication indicating whether a data SDU is included in the D2R message; andtransmit the D2R message to the RAN node.22.The AIoT device of claim 21, wherein the field of length information indicates at least one of: a length of the data SDU, a length of medium access control (MAC) protocol data unit (PDU) excluding the field of padding, or a length of the field of padding.23.The AIoT device of claim 21 or 22, wherein the processor is further configured to cause the AIoT device to:determine whether at least one condition is satisfied, the at least one condition comprising at least one of: the D2R message being to be segmented or further segmentation of the D2R message being to be transmitted; andin accordance with a determination that the at least one condition is satisfied, exclude at least one of the field of length information or the field of padding from a MAC PDU of the D2R message.24.The AIoT device of any of claims 21-23, wherein a length of the field of padding is less than or equal to a threshold, the field of length information is included and the field of padding is excluded from the D2R message.25.An ambient Internet of things (AIoT) device comprising:a processor configured to cause the AIoT device to:receive, from a radio access network (RAN) node, at least one reader to device (R2D) message, the at least one R2D message comprising at least one segment of original upper layer data and at least one of: at least one indication associated with the at least one segment, or at least one offset information associated with the at least one segment; andreassemble the at least one segment to obtain the original upper layer data based on at least one of the at least one indication or the at least one offset information,wherein an indication associated with a segment of the original upper layer data indicates at least one of:whether the segment is a last segment,whether the original upper layer data is segmented,whether the segment is a first segment,whether a further segment is after the segment, oran end of R2D transmission, andwherein offset information associated with a segment of the original upper layer data indicates at least one of:a type of a previous segment,a starting point of the segment in the original upper layer data, ora location of the segment in the original upper layer data.26.The AIoT device of claim 25, wherein the processor is further configured to cause the AIoT device to:in response to receiving a R2D message of the at least one R2D message, perform, at the MAC layer, at least one of:storing at least one of: a segment of the original upper layer data in the R2D message and offset information associated with the R2D message,forwarding the segment and the offset information to an upper layer,reassembling the segment in the R2D message based on the offset information to obtain reassembled data, orforwarding the reassembled data to the upper layer.27.The AIoT device of claim 25, wherein the at least one R2D message comprises a plurality of R2D messages, and wherein the processor is further configured to cause the AIoT device to:in response to receiving a R2D message of the plurality of R2D messages, the R2D message being not the last R2D message, store a segment of the original upper layer data in the R2D message; andin response to an indication of an R2D message indicating a last segment or an end of R2D transmission, perform, at the MAC layer, at least one of:forwarding the segment and the offset information to an upper layer,forwarding the segment and at least one stored segment and offset information of the segment and the at least one stored segment to the upper layer,reassembling the segment based on offset information associated with the R2D message to obtain reassembled data,reassembling the segment with at least one stored segment to obtain reassembled original upper layer data, orforwarding the reassembled data or reassembled original upper layer data to the upper layer.28.The AIoT device of any of claims 25-27, wherein the processor is further configured to cause the AIoT device to:in response to an indication of an R2D message indicating no segment, forward data SDU in the R2D message from a MAC layer to an upper layer.
