Method and apparatus for data transmission

Abstract

Embodiments of the present disclosure provide method and apparatus for data transmission. A method performed by a first network node may comprise obtaining at least one parameter indicating how to handle data intended for a terminal device. The method may comprise handling the data based on the at least one parameter.

Description

METHOD AND APPARATUS FOR DATA TRANSMISSIONTECHNICAL FIELD

[0001] The non-limiting and exemplary embodiments of the present disclosure generally relate to the technical field of communications, and specifically to methods and apparatuses for data transmission.BACKGROUND

[0002] This section introduces aspects that may facilitate a better understanding of the disclosure. Accordingly, the statements of this section are to be read in this light and are not to be understood as admissions about what is in the prior art or what is not in the prior art.

[0003] In communication networks such as fifth generation system (5GS) as defined by 3rd Generation Partnership Project (3GPP), various data may be transmitted in the networks. For example, the data may be transmitted to a terminal device or user equip ment(UE), such as Internet of Things (loT) device, e.g., zero-energy (ZE) loT (ZE-IoT) or ambient-IoT (A-IoT).

[0004] Wireless loT devices are often battery powered. They may need to change battery and the battery lifetime may be concerns for many potential applications such as asset tracking or environmental / industrial sensors. The wireless communications industry has been interested in so-called zero-energy devices. ZE devices may refer to wireless loT devices that do not require battery replacement, and often harvest energy from the environment. In some use cases, such as monitoring a temperature of foodstuffs, the ZE devices may have small batteries that are disposable (e.g., organic, compostable batteries), rechargeable or have very limited capacity.

[0005] These ZE-IoT devices can in addition be of very small form factor and could even be printable and they may target ultra-low power consumption to enable operation based on either energy-harvesting from an ambient source or back-scattering communication (e.g. Radio Frequency Identification (RFID)). That is, instead of relying on energy for communication being provided by a battery, the energy can be instead harvested from an ambient source, such as vibrations, solar power, radio frequency (RF), etc. A charge carrier wave may be provided to the device which is modulated and reflected back to a reader (e.g. in the back-scattering communication case). This may enable energy autonomous operation during the lifetime of the devices without need for either manual replacement or charging of the batteries. Compared to existing radio access technologies this puts new requirements on the radio interface and the protocols.SUMMARY

[0006] This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

[0007] The terminal devices such as ZE-IoT devices may be expected to consume low energy, have a low cost and / or a very small form factor. This means that such terminal devices may be equipped with simpler and cheaper components such as crystal-free radios where the local oscillators (LOs) do not have a stable or accurate time / frequency reference.

[0008] The terminal devices such as ZE-IoT devices may not have enough energy to transmit like legacy UEs’ transmission. For example, the terminal devices such as ZE-IoT devices may transmit, e.g., few transmissions and the energy may deplete (or power off). The terminal devices such as ZE-IoT devices may need to harvest energy to continue with transmissions.

[0009] In downlink (DL) scenario and due to the operation or transmission behavior of the terminal devices such as ZE-IoT device, it may happen that in the midst of DL transmission, the terminal devices may power off due to energy depletion. One issue is particularly interesting if a user pane function sends data to a radio access network (RAN) node to send it to a particular terminal device. However, the terminal device is not responsive, e.g., it may be temporarily shut-off. In this situation, an efficient protocol design is required for the treatment of DL data, given that the user pane function does not keep a copy of the data. This may become particularly relevant in case of ZE-IoT (and / or A-IoT) where a core network (CN) may not associate user plane (UP) packet with a quality of service (QoS) profile or identifier (ID), i.e., RAN node is provided with DL data but without a guideline how to deliver the DL data over air interface, e.g., whether to keep the DL data in a buffer for some time or not.

[0010] The problem may be also applicable to DL control plane (CP) packets (e.g. sent over Non-Access Stratum (NAS)), e.g., when a base station delivers a NAS message carrying DL user data from CN (e.g., Access and Mobility Management Function (AMF) or Session Management Function (SMF)) to the terminal device such as loT device without receiving any feedback.

[0011] To overcome or mitigate at least one of above mentioned problems or other problems, the embodiments of the present disclosure propose a solution for data transmission. For example, the proposed solution may facilitate the DL operation of the terminal device e.g. which may be prone to frequent shutting down e.g. due to energy storage capabilities.

[0012] In a first aspect of the disclosure, there is provided a method performed by a first network node. The method may comprise obtaining at least one parameter indicating how tohandle data intended for a terminal device. The method may comprise handling the data based on the at least one parameter.

[0013] In an embodiment, the at least one parameter may comprise at least one of an indicator indicating whether the first network node needs to buffer the data, a timer indicating the first network node to keep the data in a buffer until the timer is expired, a maximum number of data packets that the first network node needs to store in the buffer, retransmission times that the first network node can try retransmissions to deliver the data to the terminal device, a duration for which the data stored in the buffer is valid, or a maximum volume of the data that the first network node needs to store in the buffer.

[0014] In an embodiment, handling the data based on the at least one parameter may comprise at least one of when the terminal device is not responsive, the first network node keeps the data in the buffer, when the terminal device is able to establish with the first network node, the first network node delivers the data as long as the data is still stored in the buffer, when the timer expires, the first network node clears the data, when the maximum number of stored data packets is reached and a new data packet is received, the first network node clears an oldest data packet in the buffer, when the maximum volume of the data is reached and new data is received, the first network node clears oldest data in the buffer, when the retransmission times is reached, the first network node clears the data, when the duration is invalid, the first network node clears the data, when the first network node successfully delivers the data, the first network node clears the data, during a mobility scenario, the first network node delivers the data to a new access network node, when the terminal device is accessing a network via a new access network node, the first network node delivers the data to the new access network node, when the first network node does not need to buffer the data, the first network node immediately delivers the data, when the first network node does not deliver the data to the terminal device and decides to clear the data, the first network node delivers the data to the core network node for buffering, or when the first network node has not received a feedback from the terminal device for a given or configured period of time, the first network node delivers the stored data to the core network node for buffering.

[0015] In an embodiment, a value of the at least one parameter is set based on at least one of a data type, a terminal device type, an indication of a user plane function, a policy of an access and mobility management function, a terminal device energy-harvesting capability type, or a latency budget of the data.

[0016] In an embodiment, the at least one parameter is applied to at least one of the data intended for all terminal devices, the data intended for a specific terminal device, the data intended for a class of terminal devices, all types of data, a specific type of data, the data for alltypes of services, the data for a specific type of service, a data packet, or the data for a protocol data unit session.

[0017] In an embodiment, the at least one parameter may be determined by at least one of a session management function, a user plane function, an access and mobility management function, or an access network node.

[0018] In an embodiment, the method may comprise, when the terminal device is unable to be paged or connected, sending, to an access and mobility management function, a message for informing about a lost of the terminal device and / or asking the access and mobility management function to re-initiate a registration or connection procedure.

[0019] In an embodiment, the method may comprise sending, to an access and mobility management function, a first message for estimating a reachability timer of the terminal device.

[0020] In an embodiment, the method may comprise receiving, from an access and mobility management function, a second message comprising an estimated maximum wait time for delivering the data to the terminal device.

[0021] In an embodiment, the method may comprise, when the terminal device is considered reachable, receiving, from an access and mobility management function, a third message for paging the terminal device.

[0022] In an embodiment, the method may comprise paging the terminal device.

[0023] In an embodiment, the method may comprise, when the terminal device is considered reachable, receiving, from an access and mobility management function, a fourth message for delivering the data to the terminal device.

[0024] In an embodiment, the method may comprise delivering the data to the terminal device.

[0025] In an embodiment, the obtaining at least one parameter indicating how to handle data intended for a terminal device comprising at least one of obtaining the at least one parameter from a user plane function, obtaining the at least one parameter from an access and mobility management function, obtaining the at least one parameter from another access network node, or determining the at least one parameter by itself.

[0026] In an embodiment, the method may comprise resetting a value of the at least one parameter.

[0027] In an embodiment, the at least one parameter is obtained from at least one of an in-band signaling as part of the data, a message during a PDU session establishment or modification procedure, a message during a handover procedure, or a message during an initial registration procedure.

[0028] In an embodiment, the data may comprise user plane data or control plane based data transmission or data not associated with a quality of service (QoS) profile or identifier.

[0029] In an embodiment, the terminal device may comprise at least one of an ultra-low power device, a zero-energy device, an Internet of Things device, a device requiring Ultra Reliable Low Latency Communication, a device using Enhanced Mobile Broadband service, a device using Massive Machine Type Communication service or a device using Time Sensitive Networking.

[0030] In an embodiment, the first network node may comprise at least one of an access network node, or a user plane function.

[0031] In a second aspect of the disclosure, there is provided a method performed by a second network node. The method may comprise determining at least one parameter indicating how to handle data intended for a terminal device. The method may comprise sending the at least one parameter to a first network node.

[0032] In an embodiment, the second network node may comprise at least one of a session management function, or an access and mobility management function.

[0033] In an embodiment, when the second network node is an access and mobility management function, the method may comprise, when the terminal device is unable to be paged or connected, receiving, from an access network node, a message for informing about a lost of the terminal device and / or asking the access and mobility management function to re-initiate a registration or connection procedure. The method may comprise re-initiating the registration or connection procedure.

[0034] In an embodiment, the method may comprise receiving, from the first network node, a first message for estimating a reachability timer of the terminal device.

[0035] In an embodiment, the method may comprise estimating the reachability timer of the terminal device.

[0036] In an embodiment, the method may comprise sending, to the first network node, a second message comprising an estimated maximum wait time for delivering the data to the terminal device.

[0037] In an embodiment, the method may comprise, when the terminal device is considered reachable, sending, to the access network node, a third message for paging the terminal device.

[0038] In an embodiment, the method may comprise, when the terminal device is considered reachable, sending, to the first network node, a fourth message for delivering the data to the terminal device.

[0039] In an embodiment, the at least one parameter is sent in at least one of an in-band signaling as part of the data, a message during a PDU session establishment or modification procedure, a message during a handover procedure, or a message during an initial registration procedure.

[0040] In a third aspect of the disclosure, there is provided a first network node. The first network node may comprise a processor and a memory coupled to the processor. Said memory contains instructions executable by said processor. Said first network node is operative to obtain at least one parameter indicating how to handle data intended for a terminal device. Said first network node is operative to handle the data based on the at least one parameter.

[0041] In an embodiment, said first network node is operative to perform any of the method of the first aspect of the disclosure.

[0042] In a fourth aspect of the disclosure, there is provided a second network node. The second network node comprises a processor and a memory coupled to the processor. Said memory contains instructions executable by said processor. Said second network node is operative to determine at least one parameter indicating how to handle data intended for a terminal device. Said second network node is operative to send the at least one parameter to a first network node.

[0043] In an embodiment, said first network node is operative to perform any of the method of the second aspect of the disclosure.

[0044] In another aspect of the disclosure, there is provided a computer program product comprising instructions which when executed by at least one processor, cause the at least one processor to perform the method according to any one of the first or second aspect.

[0045] In another aspect of the disclosure, there is provided a computer-readable storage medium storing instructions which when executed by at least one processor, cause the at least one processor to perform the method according to any one of the first or second aspect.

[0046] Embodiments herein may provide many advantages, of which a non-exhaustive list of examples follows. In some embodiments herein, the proposed solution specifies behavior to handle DL data at a network node such as RAN node when the terminal device is unable to respond e.g. in scenarios like RRC connectionless. In some embodiments herein, the proposed solution may increase DL transmission reliability by providing an opportunity at the network node such as RAN node to hold the DL data e.g. until certain timer and / or wait for the terminal device to respond e.g. before the timer expires and / or allows the network node such as RAN node to deliver the data successfully. The embodiments herein are not limited to the features and advantages mentioned above. A person skilled in the art will recognize additional features and advantages upon reading the following detailed description.BRIEF DESCRIPTION OF THE DRAWINGS

[0047] The above and other aspects, features, and benefits of various embodiments of the present disclosure will become more fully apparent, by way of example, from the following detailed description with reference to the accompanying drawings, in which like reference numerals or letters are used to designate like or equivalent elements. The drawings are illustrated for facilitating better understanding of the embodiments of the disclosure and not necessarily drawn to scale, in which:

[0048] FIG.l schematically shows a high level architecture in a 5G network according to an embodiment of the present disclosure;

[0049] FIG.2 schematically shows system architecture in a 4G network according to an embodiment of the present disclosure;

[0050] FIGs.3, 4, 5a, 5b, 5c, 5d, 5e, 6a, 6b, 6c, 6d, 6e and 7 show flowcharts of methods according to embodiments of the present disclosure;

[0051] FIG.8 is a block diagram showing an apparatus suitable for practicing some embodiments of the disclosure;

[0052] FIG.9 shows an example of a communication system according to an embodiment of the disclosure;

[0053] FIG.10 shows a UE in accordance with some embodiments;

[0054] FIG.l 1 shows a network node in accordance with some embodiments;

[0055] FIG.12 is a block diagram of a host according to an embodiment of the disclosure;

[0056] FIG.13 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized; and

[0057] FIG.14 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection according to an embodiment of the disclosure.DETAILED DESCRIPTION

[0058] The embodiments of the present disclosure are described in detail with reference to the accompanying drawings. It should be understood that these embodiments are discussed only for the purpose of enabling those skilled persons in the art to better understand and thus implement the present disclosure, rather than suggesting any limitations on the scope of the present disclosure. Reference throughout this specification to features, advantages, or similar language does not imply that all of the features and advantages that may be realized with the present disclosure should be or are in any single embodiment of the disclosure. Rather, language referring to the features and advantages is understood to mean that a specific feature, advantage, or characteristic described in connection with an embodiment is included in at least oneembodiment of the present disclosure. Furthermore, the described features, advantages, and characteristics of the disclosure may be combined in any suitable manner in one or more embodiments. One skilled in the relevant art will recognize that the disclosure may be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of the disclosure.

[0059] As used herein, the term “network” refers to a network following any suitable communication standards such as new radio (NR), long term evolution (LTE), LTE-Advanced, wideband code division multiple access (WCDMA), high-speed packet access (HSPA), Code Division Multiple Access (CDMA), Time Division Multiple Address (TDM A), Frequency Division Multiple Access (FDMA), Orthogonal Frequency-Division Multiple Access (OFDMA), Single carrier frequency division multiple access (SC-FDMA) and other wireless networks. A CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA), etc. UTRA includes WCDMA and other variants of CDMA. A TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM). An OFDMA network may implement a radio technology such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, Ad-hoc network, wireless sensor network, etc. In the following description, the terms “network” and “system” can be used interchangeably. Furthermore, the communications between two devices in the network may be performed according to any suitable communication protocols, including, but not limited to, the communication protocols as defined by a standard organization such as 3 GPP. For example, the communication protocols may comprise the first generation (1G), 2G, 3G, 4G, 4.5G, 5G, 6G communication protocols, and / or any other protocols either currently known or to be developed in the future.

[0060] The term “network device” or “network node” or “network function” refers to any suitable function which can be implemented in a network entity (physical or virtual) of a communication network. For example, the network function can be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g. on a cloud infrastructure. For example, the 5G system (5GS) may comprise a plurality of NFs such as Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Service Function (AUSF), Unified Data Management (UDM), Policy Control Function (PCF), Application Function (AF), Network Exposure Function (NEF), User plane Function (UPF) and Network Repository Function (NRF), radio access network (RAN), service communication proxy (SCP), network data analytics function (NWDAF), network sliceSelection Function (NSSF), network slice-Specific Authentication and Authorization Function (NSSAAF), etc. In other embodiments, the network function may comprise different types of NFs for example depending on a specific network. For example, the 4G system (such as Long Term Evolution (LTE)) may include Mobile Management Entity (MME), home subscriber server (HSS), PCRF (Policy and Charging Rules Function), PGW (Packet Data Network Gateway), PGW control plane (PGW-C), PGW user plane (PGW-U) Serving gateway (SGW), SGW control plane (SGW-C), SGW user plane (SGW-U), E-UTRAN Node B (eNB), etc. In other embodiments, the network function may comprise different types of NFs for example depending on a specific network.

[0061] The network device may be an access network device with accessing function in a communication network via which a terminal device accesses to the network and receives services therefrom. The access network device may include a base station (BS), an access point (AP), a multi-cell / multicast coordination entity (MCE), a controller or any other suitable device in a wireless communication network. The BS may be, for example, a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), a next generation NodeB (gNodeB or gNB), a remote radio unit (RRU), a radio header (RH), an Integrated Access and Backhaul (IAB) node, a remote radio head (RRH), a relay, a low power node such as a femto, a pico, and so forth.

[0062] Yet further examples of the access network device comprise multi- standard radio (MSR) radio equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, positioning nodes and / or the like. More generally, however, the network node may represent any suitable device (or group of devices) capable, configured, arranged, and / or operable to enable and / or provide a terminal device access to a wireless communication network or to provide some service to a terminal device that has accessed to the wireless communication network.

[0063] Virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to a provider edge node and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).

[0064] In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments hosted by one or more of hardware nodes. Further, in embodiments in which the virtual node is not a radio access node or does not require radioconnectivity (e.g., a core network node), then the provider edge node or PE may be entirely virtualized.

[0065] The functions may be implemented by one or more applications (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein. Applications are run in virtualization environment which provides hardware comprising processing circuitry and memory. Memory contains instructions executable by processing circuitry whereby application is operative to provide one or more of the features, benefits, and / or functions disclosed herein.

[0066] Virtualization environment, comprises general-purpose or special-purpose network hardware devices comprising a set of one or more processors or processing circuitry, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory which may be non-persistent memory for temporarily storing instructions or software executed by processing circuitry. Each hardware device may comprise one or more network interface controllers (NICs), also known as network interface cards, which include physical network interface. Each hardware device may also include non-transitory, persistent, machine-readable storage media - having stored therein software and / or instructions executable by processing circuitry. Software may include any type of software including software for instantiating one or more virtualization layers (also referred to as hypervisors), software to execute virtual machines as well as software allowing it to execute functions, features and / or benefits described in relation with some embodiments described herein.

[0067] Virtual machines, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer or hypervisor. Different embodiments of the instance of virtual appliance may be implemented on one or more of virtual machines, and the implementations may be made in different ways.

[0068] During operation, processing circuitry executes software to instantiate the hypervisor or virtualization layer, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer may present a virtual operating platform that appears like networking hardware to virtual machine.

[0069] The term “terminal device” refers to any end device that can access a communication network and receive services therefrom. By way of example and not limitation, the terminal device refers to a mobile terminal, user equipment (UE), or other suitable devices. The UE may be, for example, a Subscriber Station (SS), a Portable Subscriber Station, a Mobile Station (MS),or an Access Terminal (AT). The terminal device may include, but not limited to, a portable computer, an image capture terminal device such as a digital camera, a gaming terminal device, a music storage and a playback appliance, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet, a wearable device, a personal digital assistant (PDA), a portable computer, a desktop computer, a wearable terminal device, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, a laptop-embedded equipment (LEE), a laptop -mounted equipment (LME), a USB dongle, a smart device, a wireless customer-premises equipment (CPE) and the like. In the following description, the terms “terminal device”, “terminal”, “user equipment” and “UE” may be used interchangeably. As one example, a terminal device may represent a UE configured for communication in accordance with one or more communication standards promulgated by the 3GPP (3rd Generation Partnership Project), such as 3GPP LTE standard or NR standard. As used herein, a “user equipment” or “UE” may not necessarily have a “user” in the sense of a human user who owns and / or operates the relevant device. In some embodiments, a terminal device may be configured to transmit and / or receive information without direct human interaction. For instance, a terminal device may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the communication network. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but that may not initially be associated with a specific human user.

[0070] As yet another example, in an Internet of Things (loT) scenario, a terminal device may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another terminal device and / or network equipment. The terminal device may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as a machine-type communication (MTC) device. As one particular example, the terminal device may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances, for example refrigerators, televisions, personal wearables such as watches etc. In other scenarios, a terminal device may represent a vehicle or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0071] References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes theparticular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

[0072] It shall be understood that although the terms “first” and “second” etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term “and / or” includes any and all combinations of one or more of the associated listed terms.

[0073] As used herein unless expressly stated to the contrary, the phrase “at least one of A and B” or “at least one of A or B” should be understood to mean any of the following “only A, only B, or both A and B.” The phrase “A and / or B” should be understood to mean any of the following “only A, only B, or both A and B”.

[0074] As used herein unless expressly stated to the contrary, the phrase “a plurality of’ followed by a conjunctive list of enumerated items (e.g., “A and B”, “A, B, and C”) is intended to mean “multiple items, with each item selected from the list consisting of’ the enumerated items. For example, “a plurality of A and B” is intended to mean any of the following: more than one A; more than one B; or at least one A and at least one B.

[0075] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. 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. It will be further understood that the terms “comprises”, “comprising”, “has”, “having”, “includes” and / or “including”, when used herein, specify the presence of stated features, elements, and / or components etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof.

[0076] It is noted that these terms as used in this document are used only for ease of description and differentiation among nodes, devices or networks etc. With the development of the technology, other terms with the similar / same meanings may also be used.

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

[0078] Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are describedin relation to a communication system complied with the exemplary system architecture illustrated in FIGs.l and 2. For simplicity, the system architecture of FIGs.l and 2 only depict some exemplary elements. In practice, a communication system may further include any additional elements suitable to support communication between terminal devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or terminal device. The communication system may provide communication and various types of services to one or more terminal devices to facilitate the terminal devices’ access to and / or use of the services provided by, or via, the communication system.

[0079] FIG.l schematically shows a high level architecture in a 5G network according to an embodiment of the present disclosure. The architecture of FIG.l may be similar to Figure 4.2.3-1 of 3GPP TS 23.501 V18.4.0, the disclosure of which is incorporated by reference herein in its entirety. The system architecture of FIG.l may comprise a plurality of network functions (NFs) such as Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Service Function (AUSF), Unified Data Management (UDM), Policy Control Function (PCF), Application Function (AF), Network Exposure Function (NEF), User plane Function (UPF) and Network Repository Function (NRF), (radio) access network ((R)AN), service communication proxy (SCP), Network Slice Selection Function (NSSF), network slice-Specific Authentication and Authorization Function (NSSAAF), Edge Application Server Discovery Function (EASDF), NSACF (network slice Admission Control Function), NWDAF, etc.

[0080] In accordance with an exemplary embodiment, the UE can establish a signaling connection with the AMF over the reference point Nl, as illustrated in FIG.l. This signaling connection may enable NAS (Non-access stratum) signaling exchange between the UE and the core network, comprising a signaling connection between the UE and the (R)AN and the N2 connection for this UE between the (R)AN and the AMF. The (R)AN can communicate with the UPF over the reference point N3. The UE can establish a protocol data unit (PDU) session to the DN (data network, e.g. an operator network or Internet) through the UPF over the reference point N6.

[0081] As further illustrated in FIG.l, the exemplary system architecture also contains the service-based interfaces such as Nnrf, Nnef, Nausf, Nudm, Npcf, Namf, Nnsacf, Neasdf, Nnssf, Nnwdaf and Nsmf exhibited by NFs such as the NRF, the NEF, the AUSF, the UDM, the PCF, the AMF, the NSACF, the EASDF, the NSSF, the NWDAF and the SMF. In addition, FIG.l also shows some reference points such as Nl, N2, N3, N4, N6 and N9, which can support the interactions between NF services in the NFs. For example, these reference points may berealized through corresponding NF service-based interfaces and by specifying some NF service consumers and providers as well as their interactions in order to perform a particular system procedure.

[0082] Various NFs shown in FIG.l may be responsible for functions such as session management, mobility management, authentication, security, etc. The AUSF, AMF, DN, NEF, NRF, NSSF, PCF, SMF, UDM, UPF, AF, UE, (R)AN, SCP, NSACF, NSSAAF, EASDF may include the functionality for example as defined in clause 6.2 of 3 GPP TS 23.501 VI 8.4.0.

[0083] FIG.2 schematically shows system architecture in a 4G network according to an embodiment of the present disclosure, which is the same as Figure 4.2-la of 3GPP TS 23.682 VI 8.0.0, the disclosure of which is incorporated by reference herein in its entirety. The system architecture of FIG.2 may comprise some exemplary elements such as Services Capability Server (SCS), Application Server (AS), SCEF (Service Capability Exposure Function), HSS, UE, RAN(Radio Access Network), SGSN (Serving GPRS(General Packet Radio Service) Support Node), MME, MSC(Mobile Switching Centre), S-GW(Serving Gateway), GGSN / P-GW(Gateway GPRS Support Node / PDN(Packet Data Network) Gateway), MTC-IWF(Machine Type Communications-InterWorking Function) CDF / CGF(Charging Data Function / Charging Gateway Function), MTC-AAA(Machine Type Communications-authentication, authorization and accounting), SMS-SC / GMSC / IWMSC(Short Message Service- Service Centre / Gateway MSC / InterWorking MSC) IP-SM-GW(Internet protocol Short Message Gateway). The network elements and interfaces as shown in FIG.2 may be same as the corresponding network elements and interfaces as described in 3 GPP TS 23.682 V18.0.0.

[0084] The system architecture shows the architecture for a UE used for MTC connecting to the 3GPP network (UTRAN (Universal Terrestrial Radio Access Network), E-UTRAN (Evolved UTRAN), GERAN (GSM EDGE (Enhanced Data rates for GSM Evolution) Radio Access Network), etc.) via the Um / Uu / LTE-Uu interfaces. The system architecture also shows the 3 GPP network service capability exposure to SCS and AS.

[0085] As further illustrated in FIG.2, the exemplary system architecture also contains various reference points.

[0086] Tsms: Reference point used by an entity outside the 3 GPP network to communicate with UEs used for MTC via SMS (Short Message Service).

[0087] Tsp: Reference point used by a SCS to communicate with the MTC-IWF related control plane signaling.

[0088] T4: Reference point used between MTC-IWF and the SMS-SC in the HPLMN (home Public Land Mobile Network).

[0089] T6a: Reference point used between SCEF and serving MME.

[0090] T6b: Reference point used between SCEF and serving SGSN.

[0091] T8: Reference point used between the SCEF and the SCS / AS.

[0092] S6m: Reference point used by MTC-IWF to interrogate HSS / HLR (Home Location Register).

[0093] S6n: Reference point used by MTC-AAA to interrogate HSS / HLR.

[0094] S6t: Reference point used between SCEF and HSS.

[0095] SGs: Reference point used between MSC and MME.

[0096] Gi / SGi: Reference point used between GGSN / P-GW and application server and between GGSN / P-GW and SCS.

[0097] Rf / Ga: Reference point used between MTC-IWF and CDF / CGF.

[0098] Gd: Reference point used between SMS-SC / GMSC / IWMSC and SGSN.

[0099] SGd: Reference point used between SMS-SC / GMSC / IWMSC and MME.

[0100] E: Reference point used between SMS-SC / GMSC / IWMSC and MSC.

[0101] A non-terrestrial network refers to a network, or segment of networks using RF resources on board a satellite (or Uncrewed Aerial System (UAS) platform).

[0102] A recent work of 3GPP is “New SID: Study on Ambient loT”, RP-222685, 3GPP TSG RAN#97e Electronic Meeting, September 12 - 16, 2022. This study targets at a new 3GPP loT technology, suitable for deployment in a 3 GPP system, which relies on ultra-low complexity devices with ultra- low power consumption for the very-low end loT applications. The study shall provide clear differentiation, i.e. addressing use cases and scenarios that cannot otherwise be fulfilled based on existing 3GPP Low-Power Wide-Area Network (LPWA) loT technology e.g. NB-IoT including with reduced peak transmit (Tx) power.

[0103] In terms of energy storage, the study will consider the following device characteristics:

[0104] • Pure batteryless devices with no energy storage capability at all, and completely dependent on the availability of an external source of energy

[0105] • Devices with limited energy storage capability that do not need to be replaced or recharged manually.

[0106] Device categorization based on corresponding characteristics (e.g. energy source, energy storage capability, passive / active transmission, etc.) may be discussed during the study, in relation with the relevant use cases. The device’ s peak power consumption shall be limited by its practical form factor for the intended use cases, and shall consider its energy source.

[0107] • Identify the suitable deployment scenarios and their characteristics, at least for the use cases / services agreed in SAl ’s “Study on Ambient power-enabled internet of Things”, comprising among at least the following aspects:• Indoor / outdoor environment• Basestation characteristics, e.g. macro / micro / pico cells-based deployments• Connectivity topologies, including which node(s) , e.g. basestation, UE, relay, repeater, etc. can communicate with target devices• Time Division Duplex (TDD) / Frequency Division Duplex (FDD), and frequency bands in licensed or unlicensed spectrum• Coexistence with UEs and infrastructure in frequency bands for existing 3 GPP technologies• Device originated and / or device terminated traffic assumption

[0108] NOTE: There can be more than one deployment scenario identified for a use case, and a deployment scenario may be common to more than one use case.

[0109] NOTE: Where more than one deployment scenario is identified for a use case, the trade-offs between them should also be studied.

[0110] NOTE: The study shall not prioritize deployment aspects that should be coordinated with SA, e.g. public or private network, with or without core network (CN) connection.

[0111] NOTE: A representative use case can be studied for a group of use cases that have similar requirements.

[0112] • Formulate a set of RAN design targets based on the identified deployment scenarios and their characteristics for the relevant use cases, at least including• Power consumption• Complexity• Coverage• Data rate• Positioning accuracy

[0113] NOTE: The requirements from SAI on the relevant use cases shall be taken into consideration.

[0114] NOTE: The study shall aim to provide better coverage compared to existing non-3GPP technologies for the relevant use cases.

[0115] NOTE: Other RAN design targets in relation to connection density, mobility, security, latency, reliability etc. may be discussed, if necessary for the relevant use cases.

[0116] NOTE: Detailed definitions of the RAN design targets should be discussed during the study.

[0117] • Compare and assess the feasibility of meeting the design targets for relevant use case on the basis of the deployment scenario(s) appropriate to it, and identify assumptions on required functionality to be supported.

[0118] NOTE: This is not to require a detailed Working Group (WG)-level of analysis.

[0119] Note: This study shall target for an loT segment well below the existing 3 GPP loT technologies, e.g. NB-IoT, enhanced MTC (eMTC), New Radio (NR) support for reduced capability (RedCap), etc. The study shall not aim to replace existing 3GPP LPWA technologies.

[0120] Handling of DL data in legacy 5G networks

[0121] User plane (UP) traffic of a protocol data unit (PDU) session is assigned with a quality of service (QoS) flow identifier (ID) (QFI), so packets with same QFI may have same forwarding treatment. Any UP packet over N3 tunnel has a QFI in the header of the packet. In the downlink (DL), for a given packet, what RAN receives from CN is QFI in the header and from this value RAN can associate with the QoS profile defined by CN, which consists of QoS parameters and QoS characteristics that help instruct RAN how to deliver the UP packet. Based on that information, RAN can bind / link QoS flows to radio bearers (RBs) to deliver to the device over air interface.

[0122] Regarding UP data buffer management, as detailed in clause 5.8 of 3GPP TS 23.501 V18.4.0, when the UP connection of the PDU Session is activated, the SMF updates the UPF of the change in buffering state. That is, in case of RRC_INACTIVE, the buffered downlink packets, if any, are then forwarded to the RAN by the UPF. Thus, RAN may have a responsibility to deliver the DL packets to the UE.

[0123] In the control plane (CP), the CN assistance information for RAN optimization (see clause 5.4.6 of 3 GPP TS 23.501 VI 8.4.0) currently is provided to RAN via N2 interface (CP signaling) for RAN parameters regarding expected UE behavior to optimize UE state transition (both Connection Management (CM) and Radio Resource Control (RRC) levels) steering or RAN paging strategy. For example, for the RAN paging strategy, the assistance information consists of a service priority (e.g. values 1 o 256) that helps RAN understand how important the downlink signaling is. But this is only applicable for the RAN paging.

[0124] In below embodiments, we have considered or assumed use case with ultra-low power devices, zero-energy devices (such as backscattering and / or energy harvesting based devices), or loT devices. However, the embodiments should not be limited to such devices, and can be extended to other service / device classes or categories, e.g., related to Enhanced Mobile Broadband (eMBB), massive-Machine-Type Communications (MTC), Ultra Reliable Low Latency Communication (URLLC), Time-Sensitive Networking (TSN), etc.

[0125] FIG.3 shows a flowchart of a method according to an embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a first network node or communicatively coupled to the first network node. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 300 as well asmeans or modules or circuits for accomplishing other processes in conjunction with other components.

[0126] At block 302, the first network node may obtain at least one parameter indicating how to handle data intended for a terminal device.

[0127] The first network node may be deployed in any suitable network. In an embodiment, the first network node may be deployed in a fifth generation system (5GS) or a sixth generation system (6GS) as defined by 3GPP.

[0128] The first network node may be any suitable network device or network node or network function which may need to obtain at least one parameter indicating how to handle the data intended for the terminal device. For example, the first network node may implement radio access network function or user plane function, etc.

[0129] In an embodiment, the first network node may comprise at least one of an access network node or a user plane function. For example, the access network node may be same as or similar to radio access network (such as eNB or gNB) as described in various 3 GPP specifications such as 3GPP TS 23.501 V18.4.0 or 3GPP TS 23.682 V18.0.0 or 3GPP 6G specification. The user plane function may be same as or similar to the user plane function (such as UPF or PGW-U or SGW-U) as described in various 3 GPP specifications such as such as 3GPP TS 23.501 V18.4.0 or 3GPP TS 23.682 V18.0.0 or 3GPP 6G specification.

[0130] The terminal devices node may be any suitable terminal device. In an embodiment, the terminal device may comprise at least one of an ultra-low power device, a zero-energy device, an Internet of Things device, a device requiring Ultra Reliable Low Latency Communication, a device using Enhanced Mobile Broadband service, a device using Massive Machine Type Communication service or a device using Time Sensitive Networking.

[0131] The data may be any suitable data such as user data or signaling data, etc., which is to be transmitted to the terminal device. In an embodiment, the data may comprise user plane data, control plane data, or user data which is transmitted based on a control plane. In an embodiment, the data may be downlink data. The downlink may refer to the link from the network to the terminal device.

[0132] The at least one parameter may comprise any suitable parameter related to handling the data intended for the terminal device.

[0133] In an embodiment, the at least one parameter may comprise at least one of:• an indicator indicating whether the first network node needs to buffer the data,• a timer indicating the first network node to keep the data in a buffer until the timer is expired,• a maximum number of data packets that the first network node needs to store in the buffer,• retransmission times that the first network node can try retransmissions to deliver the data to the terminal device,• a duration for which the data stored in the buffer is valid, or• a maximum volume of the data that the first network node needs to store in the buffer.

[0134] For example, the indicator may indicate whether the radio access network node or the user plane function needs to buffer the data. Based on the indicator, the radio access network node or the user plane function may buffer the data if the data can not be transmitted to the terminal device currently due to various reasons e.g., the terminal device may power off due to energy depletion, the terminal device may be temporarily shut-off, the terminal device is not responsive, the radio access network node or the user plane function is overloaded, etc.

[0135] For example, the timer / number of packets / volume of stored data based handling of DL data may be used at the RAN node.

[0136] In an embodiment, the first network node such as UPF may send the data to a RAN node, e.g., gNB or eNB. The first network node may add or tag or include or modify or append the data with additional information indicating whether / how the RAN node shall handle (e.g. buffer) the data.

[0137] For example, the timer may be used by the first network node such as UPF or RAN node to keep the data until the timer is expired.

[0138] For example, the maximum number of data packets may be used by the first network node such as UPF or RAN node to store the data in its buffer. For example, suppose at most N data packets need to be kept in the buffer, and there are already N data packets stored in the RAN node’s buffer, when a new data packet is received from a core network node (e.g., UPF), the RAN node may discard the oldest data packet in its buffer.

[0139] For example, the core network node such as UPF / AMF can forward each data packet to the gNB along with the associated age of information (Aol) i.e. duration for which the information is valid. When the UE is available, the data packet is forwarded by the RAN node such as gNB if the Aol is still valid, otherwise the data packet is discarded if the Aol expires.

[0140] For example, the CN node (e.g., SMF / UPF / AMF) my associate DL data sent to a RAN node, e.g., gNB or eNB, with information / indication related to reliability such as up to how many times the RAN node can try retransmissions to deliver a DL data packet. In case the terminal device such as loT device is not responsive, the RAN node may keep trying retransmissions until reaching the maximum retransmission number. In case the RAN node still does not receive any feedback from the terminal device such as loT device after the maximum allowable attempts, the RAN node may clear the data in the buffer with or without sending the data back to the CN node for further possible forwarding to another RAN node when theterminal device is accessing the network again. With this, for example, the network can differentiate the treatment of different types of UP data with the assistance information from CN. In an example, the network can configure zero retransmission for data traffic of some application with very low reliability that allows the RAN node to clear DL data packet in the buffer after the respective DL transmission.

[0141] For example, similar to the timer-based mechanism above, the maximum number of DL retransmissions can either be per DL data packet, or per PDU session, per loT device, or per category of loT devices.

[0142] For example, the indicated maximum number of retransmissions of DL data can be used in separation or in combination with the other parameter such as timer / number mechanism above. In an example of combination, the first network node such as RAN node can clear data in the buffer when either the configured timer associated to the data expires, or the maximum number of stored data is reached and the data is the oldest data, or the maximum retransmission attempts of the data has reached, or the data is successfully delivered. In another example, when the data is transmitted for the first time, the associated timer is stopped or the data is moved to another buffer, and the data is only discarded when the maximum retransmission attempts of the data is reached or the data is successfully delivered.

[0143] For example, depending on the granularity of configuration, the signaling of the parameter value can be in-band signaling as part of the DL data packet itself, or during the PDU session estab lishment / modification, or during the initial registration procedure with device capability exchanged between the terminal device and the network, etc.

[0144] This embodiment may be useful. For example, in case the UE is not responsive, then the RAN node keeps the data e.g. in the buffer and once the UE is able to establish with the RAN node, it can deliver the data as long as the data is still stored in the buffer (e.g., before the timer expires). In case the UE is unable to establish a link with the RAN node before the expiration of timer or the maximum number of stored data packets is reached, then the RAN node may clear the data once the timer expires or clear the oldest data in its buffer. This timer or maximum number of stored data packets can be a common timer / value or default timer / value which the RAN node can select or utilize.

[0145] The value of the at least one parameter can be determined in various ways, such as based on service type, data type, machine learning, an operator configuration, a local policy, a policy from a core network node, an indication of a core network node, a type of terminal device, QoS, etc.

[0146] In an embodiment, the value of the at least one parameter may be set based on at least one of:• a data type,• a terminal device type,• an indication of a user plane function,• a policy of an access and mobility management function,• a terminal device energy-harvesting capability type, or• a latency budget of the data.

[0147] For example, the value of the timer may be set or selected or determined in various ways. For example, it can be determined based on machine learning, an operator configuration, a local policy, a policy from core network, etc.

[0148] For example, the selection of the timer / number value can depend on non-limiting conditions, e.g., Data type, UPF indication, AMF policies, UE harvesting capabilities, latency budget of the data, etc.

[0149] In an embodiment, the first network node such as RAN node may select the at least one parameter such as timer / number value based on UE type or UE’s harvesting capability type. In one option, the UEs may report their harvesting capabilities and the first network node such as RAN node keeps the record containing which UE has which UE harvesting capability. A UE with efficient harvesting capability (e.g., recharges fast / sooner) may require smaller timer / number of data packets to be stored at the first network node such as RAN node compared to the UE with poor harvesting capability.

[0150] For example, the different values of the at least one parameter may be set for different data type. Different values of the at least one parameter may be set for different terminal device types. The indication of the user plane function may indicate the value of the at least one parameter. The policy of an access and mobility management function may be used to determine the value of the at least one parameter. Different values of the at least one parameter may be set for different terminal device energy-harvesting capability types. Different values of the at least one parameter may be set for different latency budgets of the data.

[0151] In an embodiment, the at least one parameter such as timer can either be per DL data packet or per PDU session. In the former case, the at least one parameter such as timer can be included as part of the DL data packet itself, e.g., as a field in the packet header. In the latter case, the same parameter value can be used for all the data packets of the same PDU session or all the data packets for the terminal device. The at least one parameter value can be decided by the network and signaled to the first network node such as RAN node when the PDU session is established or modified, or via other messages(e.g. N2 messages). In this case, there is no need to include the at least one parameter in every DL data packet.

[0152] In an alternative embodiment, the at least one parameter such as timer / number can be per device category (e.g. loT). In this case, the CN can determine the at least one parameter such as timer / number value once it gets to know category of the device and signals the value of the at least one parameter to the first network node such as RAN node.

[0153] In an alternative embodiment, the at least one parameter such as timer / number can be per data / service type. In this case, the CN can determine the at least one parameter value based on the data / service type and signals the value of the at least one parameter to the first network node such as RAN node.

[0154] The at least one parameter may be applied to various data. In an embodiment, the at least one parameter may be applied to at least one of: the data intended for all terminal devices, the data intended for a specific terminal device, the data intended for a class of terminal devices, all types of data, a specific type of data, the data for all types of services, the data for a specific type of service, a data packet, or the data for a protocol data unit session.

[0155] For example, the first network node such as UPF may apply the same parameter such as same timer to all UEs or a class of UEs (e.g., ZE-IoT class). Different data types may be configured with different parameters such as timers. The first network node such as UPF may apply the same parameter such as same timer to all data types to all UEs or a class of UEs (e.g. ZE-IoT class).

[0156] In an embodiment, the timer can either be per DL data packet or per PDU session. As detailed earlier, in the former case, the timer can be included as part of the DL data packet itself, e.g., as a field in the packet header. In the latter case, the same timer value can be used for all the data packets of the same PDU session or all the data packets for the device.

[0157] The at least one parameter may be determined by various network node. In an embodiment, the at least one parameter may be determined by at least one of:• a session management function,• a user plane function,• an access and mobility management function, or• an access network node.

[0158] The session management function may be any suitable network device or network node or network function which can implement session management function. For example, the session management function may be same as or similar to the session management function (such as SMF) as described in various 3GPP specifications such as 3GPP TS 23.501 V18.4.0 or 3 GPP TS 23.682 VI 8.0.0 or 3 GPP 6G specification. When the at least one parameter is determined by the session management function, the session management function may send it to the first network node.

[0159] The access and mobility management function may be any suitable network device or network node or network function which can implement access and mobility management function. For example, the access and mobility management function may be same as or similar to the access and mobility management function (such as AMF) as described in various 3GPP specifications such as 3GPP TS 23.501 V18.4.0 or 3GPP TS 23.682 V18.0.0 or 3GPP 6G specification. When the at least one parameter is determined by the access and mobility management function, the access and mobility management function may send it to the first network node.

[0160] For example, when the first network node is the user plane function, the first network node may determine the at least one parameter by itself or receive it from the session management function or the access and mobility management function. In addition, the first network node may send the at least one parameter to the access network node.

[0161] For example, when the first network node is the access network node, the first network node may determine the at least one parameter by itself or receive it from the session management function or the access and mobility management function or the user plane function.

[0162] For example, the at least one parameter such as timer / number values or function can be set by SMF when instructing UPF for handling DL data. The at least one parameter can be set by UPF in the data. The RAN node can set the at least one parameter based on a policy indicated by AMF / network or a local policy. The above parameter setting methods can be combined in any suitable ways.

[0163] In an embodiment, the first network node may obtain the at least one parameter by at least one of:• obtaining the at least one parameter from a user plane function,• obtaining the at least one parameter from an access and mobility management function,• obtaining the at least one parameter from another access network node, or• determining the at least one parameter by itself.

[0164] For example, when the at least one parameter is obtained from another network node, the at least one parameter may be carried in any suitable message or data. In an embodiment, the at least one parameter may be obtained from at least one of:• an in-band signaling as part of the data,• a message during a PDU session establishment or modification procedure,• a message during a handover procedure, or• a message during an initial registration procedure.

[0165] The part of the data may be any suitable part of the data such as a packet header.

[0166] The PDU session establishment or modification procedure may be same as or similar to that as described in various 3GPP specifications such as 3GPP TS 23.502 V18.4.0 or 3GPP 6G specification. For example, during the PDU session establishment or modification procedure, the UPF / AMF may send the at least one parameter to the RAN. The SMF may send the at least one parameter to UPF.

[0167] The initial registration procedure may be same as or similar to that as described in various 3 GPP specifications such as 3 GPP TS 23.502 VI 8.4.0 or 3 GPP 6G specification. For example, during the initial registration procedure, the AMF may send the at least one parameter to RAN.

[0168] The handover procedure may be same as or similar to that as described in various 3 GPP specifications such as 3 GPP TS 23.502 VI 8.4.0 or 3 GPP 6G specification. For example, during the handover procedure, the old RAN node may send the at least one parameter to the new RAN node.

[0169] For example, the core network node such as UPF / SMF / AMF can indicate if the timer is needed or not for the data transmission. In case there is no need for the timer (i.e., no need to buffer the data), the core network node can set the timer value to zero (or any other suitable value) or the field is not included (or optional) in the data, and the first network node such as RAN node can immediately deliver the data received from UPF in DL. Alternatively, the core network node such as UPF can explicitly include one-bit flag in header of DL data packet, and says, the timer is needed, then the first network node such as RAN node applies the timer value appropriately and keeps the data until the timer expires or delivers the data in DL successfully to UE before the expiration of the timer.

[0170] For example, the core network node such as UPF / SMF / AMF can indicate if the maximum number is need or not for data transmission with specific data types and / or to specific UE categories. In case there is no need for the maximum number (i.e., no need to buffer the data), the core network node can set the maximum number value to zero. Alternatively, the core network node such as UPF can explicitly include one-bit flag in the header of DL data packet toindicate whether or not buffering is needed for that data packet, such indicator may override the maximum number associated with the data, e.g., it could be that according to the data type or the target UE category, the data should be buffered, while the indicator associated with the data indicates that the data needs not to be buffered, in this case the RAN node immediately delivers the data received from UPF in DL and then discards the data.

[0171] At block 304, the first network node may handle the data based on the at least one parameter. For example, the first network node may handle the data according to the at least one parameter and / or a local policy and / or a policy from a core network node.

[0172] In an embodiment, when the indicator indicates that the first network node needs to buffer the data, the first network node may store the data in the buffer e.g. if the data cannot be delivered to the terminal device.

[0173] In an embodiment, when the indicator indicates that the first network node does not need to buffer the data, the first network node may not store the data in the buffer and the first network node will try to deliver the data to the terminal device. If the data cannot be delivered to the terminal device, the data may be discarded or forwarded to another network node.

[0174] In an embodiment, when the terminal device is not responsive (e.g. temporarily shut-off, energy depletion, etc.), the first network node keeps the data in the buffer.

[0175] In an embodiment, when the terminal device is able to establish (or has established) with the first network node, the first network node may deliver the data as long as the data is still stored in the buffer.

[0176] In an embodiment, when the timer expires, the first network node may clear the data.

[0177] In an embodiment, when the maximum number of stored data packets is reached and a new data packet is received, the first network node may clear the oldest data packet in the buffer.

[0178] In an embodiment, when the maximum volume of the data is reached and new data is received, the first network node clears the oldest data in the buffer.

[0179] In an embodiment, when the retransmission times is reached, the first network node may clear the data.

[0180] In an embodiment, when the duration is invalid, the first network node may clear the data.

[0181] In an embodiment, when the first network node successfully delivers the data, the first network node may clear the data.

[0182] In an embodiment, during a mobility scenario, the first network node may deliver the data to a new access network node.

[0183] In an embodiment, when the terminal device is accessing a network via a new access network node, the first network node delivers the data to the new access network node.

[0184] For example, the proposed method can be used in a mobility scenario. The RAN node (old RAN node) keeps the data until the timer expires or keeps the oldest data until the maximum volume / number of stored data / packets is reached, during which another RAN node (new RAN node, where the UE is camped or linked) can query either the old RAN node or CN (e.g., SMF / AMF / UPF) for UE’s data and the old RAN node or CN can deliver the stored data to the new RAN node. The old RAN node can deliver data over inter RAN node inference (e.g., X2, Xn or some new interface). And, once the old RAN node has delivered the stored data to the new RAN node, the old RAN node can clear the stored data from its buffer as per policy, e.g., if feedback is implemented, then after ACK, the old RAN node can clear the data.

[0185] In an embodiment, when the first network node does not need to buffer the data, the first network node may immediately deliver the data after receiving the data. Alternatively, the first network node may discard the data if the terminal device is not connected to the RAN.

[0186] In an embodiment, when the first network node does not deliver the data to the terminal device and decides to clear the data, the first network node may deliver the data to the core network node (such as AMF or UPF) for buffering.

[0187] In an embodiment, when the first network node has not received a feedback from the terminal device for a given or configured period of time, the first network node may deliver the stored data to the core network node (such as AMF or UPF) for buffering.

[0188] For example, if the first network node such as RAN node has not received the feedback from the terminal device for a given / configured period of time, the first network node such as RAN node can send stored DL data back to CN (e.g., AMF or UPF) for buffering and / or possible forwarding to the new RAN node when the device is accessing network again.

[0189] FIG.4 shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a first network node or communicatively coupled to the first network node. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 400 as well as means or modules or circuits for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.

[0190] At block 402, when the terminal device is unable to be paged or connected, the first network node may send, to an access and mobility management function, a message for informing about a lost of the terminal device and / or ask the access and mobility management function to re-initiate a registration or connection procedure.

[0191] For example, if the first network node such as RAN node has received the data from the core network node such as UPF / AMF, but the terminal device is unable to be paged / connected,then the first network node such as RAN node can inform about the lost UE situation and / or can ask the access and mobility management function to re-initiate a registration or connection procedure.

[0192] FIG.5a shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a first network node or communicatively coupled to the first network node. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 500 as well as means or modules or circuits for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.

[0193] At block 502, the first network node may send, to an access and mobility management function, a first message for estimating a reachability timer (or time) of the terminal device. The first message may be a new message or a modified existing message. For example, when the terminal device is unable to be paged or connected, the first network node may send the first message to the access and mobility management function.

[0194] FIG.5b shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a first network node or communicatively coupled to the first network node. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 510 as well as means or modules or circuits for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.

[0195] At block 512, the first network node may receive, from an access and mobility management function, a second message comprising an estimated maximum wait time for delivering the data to the terminal device.

[0196] The estimated maximum wait time may be used for various purposes. For example, it may be used to determine or adjust the value of the at least one parameter. The first network node may wait the estimated maximum wait time to deliver the data. The first network node may discard the data or forward the data to another network node if the estimated maximum wait time is larger than the value of the timer. The first network node may try to deliver the data after the estimated maximum wait time.

[0197] FIG.5c shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a first network node or communicatively coupled to the first network node. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 520 as well asmeans or modules or circuits for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.

[0198] At block 522, when the terminal device is considered reachable, the first network node may receive, from an access and mobility management function, a third message for paging the terminal device. The third message may be a new message or a modified existing message. For example, the access and mobility management function may estimate at which time the terminal device is considered reachable, and then it may send the third message to the first network node.

[0199] At block 524, the first network node may page the terminal device.

[0200] FIG.5d shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a first network node or communicatively coupled to the first network node. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 530 as well as means or modules or circuits for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.

[0201] At block 532, when the terminal device is considered reachable, the first network node may receive, from an access and mobility management function, a fourth message for delivering the data to the terminal device. The fourth message may be a new message or a modified existing message. In an embodiment, block 532 and block 522 may be combined.

[0202] At block 534, the first network node may deliver the data to the terminal device.

[0203] For example, the first network node such as UPF or RAN node may buffer the data packets intended for the UE and ask the access and mobility management function such as AMF (e.g. via the session management function such as SMF if the first network node is UPF) to estimate the UE reachability timer e.g. based on the UE characteristics e.g., past transmissions, energy availability stats, or Extended Discontinuous Reception(eDRX), or based on machine learning. The access and mobility management function such as AMF may calculate the UE reachability e.g. based on the characteristics provided by the RAN node or based on machine learning and trigger RAN node paging via a message if the UE is considered reachable. The access and mobility management function such as AMF may inform other network functions of an Estimated Maximum Wait Time. Once the UE is considered reachable, the access and mobility management function such as AMF then informs other NFs that the data and / or signaling can be delivered to the UE.

[0204] FIG.5e shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a first networknode or communicatively coupled to the first network node. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 540 as well as means or modules or circuits for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.

[0205] At block 542, the first network node may reset a value of the at least one parameter. The first network node may reset the value of the at least one parameter due to various reasons.

[0206] For example, if a parameter can be obtained from another network node such as UPF / SMF / SMF and determined by the first network node, the first network node may replace the value of the at least one parameter obtained from other network node with the value of the at least one parameter determined by itself. The first network node may reset the value of the at least one parameter based on the value of the at least one parameter obtained from other network node and the value of the at least one parameter determined by itself.

[0207] For example, when the at least one parameter is obtained from another access network node, the first network node may reset the value of the at least one parameter.

[0208] In an embodiment, in case of mobility from one RAN node to another RAN node, the CN assisted information (including the at least one parameter such as timer / number value and max number of retransmissions, etc.) can be reset at the new RAN node so that undelivered DL data in the RAN buffer can be kept e.g. for possible retransmissions, if needed.

[0209] The embodiments of the present disclosure can be applied to control plane based transmissions, where DL data is sent over NAS signaling, and there is no user plane function involvement. For example, this DL data (i.e., NAS PDU from AMF) has an associated timer, and the RAN node can keep or deliver the data to the intended terminal device or core network node or another RAN node e.g. until the expiration of timer.

[0210] FIG.6a shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a second network node or communicatively coupled to the second network node. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 600 as well as means or modules or circuits for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.

[0211] At block 602, the second network node may determine at least one parameter indicating how to handle data intended for a terminal device.

[0212] For example, the second network node may determine the at least one parameter based on a data type, a terminal device type, an indication of a core network node, a policy of a corenetwork node, a local policy, a terminal device energy-harvesting capability type, or QoS requirement of the data.

[0213] At block 604, the second network node may send the at least one parameter to a first network node.

[0214] In an embodiment, the at least one parameter may comprise at least one of an indicator indicating whether the first network node needs to buffer the data, a timer indicating the first network node to keep the data in a buffer until the timer is expired, a maximum number of data packets that the first network node needs to store in the buffer, retransmission times that the first network node can try retransmissions to deliver the data to the terminal device, a duration for which the data stored in the buffer is valid, or a maximum volume of the data that the first network node needs to store in the buffer.

[0215] In an embodiment, a value of the at least one parameter may be determined based on at least one of a data type, a terminal device type, an indication of a user plane function, a policy of an access and mobility management function, a terminal device energy-harvesting capability type, or a latency budget of the data.

[0216] In an embodiment, the at least one parameter may be applied to at least one of the data intended for all terminal devices, the data intended for a specific terminal device, the data intended for a class of terminal devices, all types of data, a specific type of data, the data for all types of services, the data for a specific type of service, a data packet, or the data for a protocol data unit session.

[0217] In an embodiment, the second network node may comprise at least one of a session management function, or an access and mobility management function.

[0218] In an embodiment, the at least one parameter may be sent in at least one of an in-band signaling as part of the data, a message during a PDU session establishment or modification procedure, a message during a handover procedure, or a message during an initial registration procedure.

[0219] In an embodiment, the data may comprise user plane data or control plane based data transmission or data not associated with a quality of service (QoS) profile or identifier.

[0220] In an embodiment, the terminal device may comprise at least one of an ultra-low power device, a zero-energy device, an Internet of Things device, a device requiring Ultra Reliable Low Latency Communication, a device using Enhanced Mobile Broadband service, a device using Massive Machine Type Communication service or a device using Time Sensitive Networking.

[0221] In an embodiment, the first network node may comprise at least one of an access network node, or a user plane function.

[0222] FIG.6b shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a second network node or communicatively coupled to the second network node. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 610 as well as means or modules or circuits for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.

[0223] In an embodiment, the second network node may be an access and mobility management function such as AMF.

[0224] At block 612, when the terminal device is unable to be paged or connected, the second network node may receive, from an access network node, a message for informing about a lost of the terminal device and / or asking the access and mobility management function to re -initiate a registration or connection procedure.

[0225] At block 614, the second network node may re-initiate the registration or connection procedure.

[0226] FIG.6c shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a second network node or communicatively coupled to the second network node. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 620 as well as means or modules or circuits for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.

[0227] In an embodiment, the second network node may be an access and mobility management function such as AMF.

[0228] At block 622, the second network node may receive, from the first network node, a first message for estimating a reachability timer of the terminal device.

[0229] At block 624, the second network node may estimate the reachability timer (or time) of the terminal device.

[0230] FIG.6d shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a second network node or communicatively coupled to the second network node. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 630 as well as means or modules or circuits for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.

[0231] In an embodiment, the second network node may be an access and mobility management function such as AMF.

[0232] At block 632, the second network node may send, to the first network node, a second message comprising an estimated maximum wait time for delivering the data to the terminal device.

[0233] FIG.6e shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a second network node or communicatively coupled to the second network node. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 640 as well as means or modules or circuits for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.

[0234] In an embodiment, the second network node may be an access and mobility management function such as AMF.

[0235] At block 642, when the terminal device is considered reachable, the second network node may send, to the access network node, a third message for paging the terminal device.

[0236] FIG.7 shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a second network node or communicatively coupled to the second network node. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 700 as well as means or modules or circuits for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.

[0237] In an embodiment, the second network node may be an access and mobility management function such as AMF.

[0238] At block 702, when the terminal device is considered reachable, the second network node may send, to the first network node, a fourth message for delivering the data to the terminal device.

[0239] In an embodiment, it proposes that the user plane node such as UPF sends the data intended for a terminal device such as ZE device to a radio access network (RAN) node (e.g., gNB or eNB) where the data is associated with CN assisted information instructing how to handle the data over the air interface.

[0240] As an example of such assistance information, the data can be associated with a timer. In case the terminal device is not responsive, e.g., the terminal device does not respond to the (connected or camped) RAN node. This case could happen, e.g., the terminal device is drainedof energy, then the RAN node may keep the data until the timer expires, or until the data is delivered successfully to intended node / device or another node before the expiration of timer. For example, the intended node / device or another node can be an intended terminal device such as ZE device / UE which can be in the form of initial transmissions or retransmissions, or a new RAN node (gNB or eNB) where the terminal device is now camped, or some master terminal device which it can transmit the data to the terminal device, e.g., via sidelink (SL) or UE-2-UE interface, or a CN node that handles the data for the terminal device such as ZE / A-IoT devices. The CN node may be UPF or AMF or SMF where the CN node has no copy of the data as it had forwarded the data to the RAN node earlier.

[0241] As another example of CN assisted information, the data can be associated with a maximum number of retransmissions attempt in case the terminal device is not responsive. This information can be used in separation or in combination with the timer above.

[0242] In an embodiment, it may associate the CN assisted information to the data delivered to the RAN node. The CN assisted information can be as an instruction for the RAN node to handle the data. For example, the RAN node may keep the data until the expiration of timer or data is delivered successfully to the terminal device (before the expiration of timer) or after an allowable retransmissions of the data.

[0243] In an embodiment, in scenarios like RRC connectionless, the proposed method specifies behavior to handle the data at the RAN node when the terminal device is unable to respond.

[0244] In an embodiment, it can increase DL transmission reliability by providing an opportunity at the RAN node to hold the data until a certain timer and wait for the terminal device to respond before the timer expires and allows the RAN node to deliver the data successfully.

[0245] Embodiments herein may provide many advantages, of which a non-exhaustive list of examples follows. In some embodiments herein, the proposed solution specifies behavior to handle DL data at a network node such as RAN node when the terminal device is unable to respond e.g. in scenarios like RRC connectionless. In some embodiments herein, the proposed solution may increase DL transmission reliability by providing an opportunity at the network node such as RAN node to hold the DL data e.g. until certain timer and / or wait for the terminal device to respond e.g. before the timer expires and / or allows the network node such as RAN node to deliver the data successfully. The embodiments herein are not limited to the features and advantages mentioned above. A person skilled in the art will recognize additional features and advantages upon reading the following detailed description.

[0246] FIG.8 is a block diagram showing an apparatus suitable for practicing some embodiments of the disclosure. For example, the first network node or the second network node described above may be implemented as or through the apparatus 800.

[0247] The apparatus 800 comprises at least one processor 821, such as a digital processor (DP), and at least one memory (MEM) 822 coupled to the processor 821. The apparatus 800 may comprise a transmitter TX and receiver RX 823 coupled to the processor 821. The MEM 822 stores a program (PROG) 824. The PROG 824 may include instructions that, when executed on the associated processor 821, enable the apparatus 800 to operate in accordance with the embodiments of the present disclosure. A combination of the at least one processor 821 and the at least one MEM 822 may form processing means 825 adapted to implement various embodiments of the present disclosure.

[0248] Various embodiments of the present disclosure may be implemented by computer program executable by one or more of the processor 821, software, firmware, hardware or in a combination thereof.

[0249] The MEM 822 may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memories and removable memories, as non-limiting examples.

[0250] The processor 821 may be of any type suitable to the local technical environment, 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.

[0251] In an embodiment where the apparatus is implemented as or at the first network node, the memory 822 contains instructions executable by the processor 821, whereby the first network node operates according to any of the methods performed by the first network node as described above.

[0252] In an embodiment where the apparatus is implemented as or at the second network node, the memory 822 contains instructions executable by the processor 821, whereby the second network node operates according to any of the methods performed by the second network node as described above.

[0253] With function units, the first network node or the second network node may not need a fixed processor or memory, any computing resource and storage resource may be arranged from the first network node or the second network node in the communication system. The introduction of virtualization technology and network computing technology may improve the usage efficiency of the network resources and the flexibility of the network.

[0254] Further, the exemplary overall commutation system including the terminal device and the network node (such as the first network node or the second network node) will be introduced as below.

[0255] FIG.9 shows an example of a communication system 9100 in accordance with some embodiments.

[0256] In the example, the communication system 9100 includes a telecommunication network 9102 that includes an access network 9104, such as a radio access network (RAN), and a core network 9106, which includes one or more core network nodes 9108. The access network 9104 includes one or more access network nodes, such as network nodes 9110a and 9110b (one or more of which may be generally referred to as network nodes 9110), or any other similar 3rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 9102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 9102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 9102, including one or more network nodes 9110 and / or core network nodes 9108.

[0257] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application or a non-real time control application, or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O -Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes 9110 facilitatedirect or indirect connection of user equipment (UE), such as by connecting UEs 9111a, 9112, 9111c, and 91 l id (one or more of which may be generally referred to as UEs 9112) to the core network 9106 over one or more wireless connections.

[0258] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 9100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 9100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0259] The UEs 9112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 9110 and other communication devices. Similarly, the network nodes 9110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 9112 and / or with other network nodes or equipment in the telecommunication network 9102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 9102.

[0260] In the depicted example, the core network 9106 connects the network nodes 9110 to one or more hosts, such as host 9116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 9106 includes one more core network nodes (e.g., core network node 9108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 9108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDE), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0261] The host 9116 may be under the ownership or control of a service provider other than an operator or provider of the access network 9104 and / or the telecommunication network 9102,and may be operated by the service provider or on behalf of the service provider. The host 9116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0262] As a whole, the communication system 9100 of FIG.9 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0263] In some examples, the telecommunication network 9102 is a cellular network that implements 3 GPP standardized features. Accordingly, the telecommunications network 9102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 9102. For example, the telecommunications network 9102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0264] In some examples, the UEs 9112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 9104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 9104. Additionally, a UE may be configured for operating in single- or multi-RAT or multi- standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0265] In the example, the hub 9114 communicates with the access network 9104 to facilitate indirect communication between one or more UEs (e.g., UE 9111c and / or 91 l id) and networknodes (e.g., network node 9110b). In some examples, the hub 9114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 9114 may be a broadband router enabling access to the core network 9106 for the UEs. As another example, the hub 9114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 9110, or by executable code, script, process, or other instructions in the hub 9114. As another example, the hub 9114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 9114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 9114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 9114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 9114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0266] The hub 9114 may have a constant / persistent or intermittent connection to the network node 9110b. The hub 9114 may also allow for a different communication scheme and / or schedule between the hub 9114 and UEs (e.g., UE 9111c and / or 91 l id), and between the hub 9114 and the core network 9106. In other examples, the hub 9114 is connected to the core network 9106 and / or one or more UEs via a wired connection. Moreover, the hub 9114 may be configured to connect to an M2M service provider over the access network 9104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 9110 while still connected via the hub 9114 via a wired or wireless connection. In some embodiments, the hub 9114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 9110b. In other embodiments, the hub 9114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 9110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0267] FIG.10 shows a UE 10200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobilestation, tablet, laptop, laptop-embedded equipment (LEE), laptop -mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle -mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0268] A UE may support device-to-device (Did) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0269] The UE 10200 includes processing circuitry 10202 that is operatively coupled via a bus 10204 to an input / output interface 10206, a power source 10208, a memory 10210, a communication interface 10212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIG.10. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0270] The processing circuitry 10202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 10210. The processing circuitry 10202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 10202 may include multiple central processing units (CPUs).

[0271] In the example, the input / output interface 10206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or anycombination thereof. An input device may allow a user to capture information into the UE 10200. Examples of an input device include a touch- sensitive or presence- sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence- sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0272] In some embodiments, the power source 10208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 10208 may further include power circuitry for delivering power from the power source 10208 itself, and / or an external power source, to the various parts of the UE 10200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 10208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 10208 to make the power suitable for the respective components of the UE 10200 to which power is supplied.

[0273] The memory 10210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 10210 includes one or more application programs 10214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 10216. The memory 10210 may store, for use by the UE 10200, any of a variety of various operating systems or combinations of operating systems.

[0274] The memory 10210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuitcard (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 10210 may allow the UE 10200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 10210, which may be or comprise a device-readable storage medium.

[0275] The processing circuitry 10202 may be configured to communicate with an access network or other network using the communication interface 10212. The communication interface 10212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 10222. The communication interface 10212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 10218 and / or a receiver 10220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 10218 and receiver 10220 may be coupled to one or more antennas (e.g., antenna 10222) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0276] In the illustrated embodiment, communication functions of the communication interface 10212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0277] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 10212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from severalsensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0278] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0279] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 10200 shown in FIG.10.

[0280] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3 GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3 GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0281] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speedinformation (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0282] FIG.11 shows a network node 11300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0283] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0284] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi- standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self- Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0285] The network node 11300 includes a processing circuitry 11302, a memory 11304, a communication interface 11306, and a power source 11308. The network node 11300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 11300 comprisesmultiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 11300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 11304 for different RATs) and some components may be reused (e.g., a same antenna 11310 may be shared by different RATs). The network node 11300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 11300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 11300.

[0286] The processing circuitry 11302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application- specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 11300 components, such as the memory 11304, to provide network node 11300 functionality.

[0287] In some embodiments, the processing circuitry 11302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 11302 includes one or more of radio frequency (RF) transceiver circuitry 11312 and baseband processing circuitry 11314. In some embodiments, the radio frequency (RF) transceiver circuitry 11312 and the baseband processing circuitry 11314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 11312 and baseband processing circuitry 11314 may be on the same chip or set of chips, boards, or units.

[0288] The memory 11304 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 11302. The memory 11304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more oflogic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 11302 and utilized by the network node 11300. The memory 11304 may be used to store any calculations made by the processing circuitry 11302 and / or any data received via the communication interface 11306. In some embodiments, the processing circuitry 11302 and memory 11304 is integrated.

[0289] The communication interface 11306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 11306 comprises port(s) / terminal(s) 11316 to send and receive data, for example to and from a network over a wired connection. The communication interface 11306 also includes radio front-end circuitry 11318 that may be coupled to, or in certain embodiments a part of, the antenna 11310. Radio front-end circuitry 11318 comprises filters 11320 and amplifiers 11322. The radio front-end circuitry 11318 may be connected to an antenna 11310 and processing circuitry 11302. The radio front-end circuitry may be configured to condition signals communicated between antenna 11310 and processing circuitry 11302. The radio front-end circuitry 11318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 11318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 11320 and / or amplifiers 11322. The radio signal may then be transmitted via the antenna 11310. Similarly, when receiving data, the antenna 11310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 11318. The digital data may be passed to the processing circuitry 11302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0290] In certain alternative embodiments, the network node 11300 does not include separate radio front-end circuitry 11318, instead, the processing circuitry 11302 includes radio front-end circuitry and is connected to the antenna 11310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 11312 is part of the communication interface 11306. In still other embodiments, the communication interface 11306 includes one or more ports or terminals 11316, the radio front-end circuitry 11318, and the RF transceiver circuitry 11312, as part of a radio unit (not shown), and the communication interface 11306 communicates with the baseband processing circuitry 11314, which is part of a digital unit (not shown).

[0291] The antenna 11310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 11310 may be coupled to the radio front-end circuitry 11318 and may be any type of antenna capable of transmitting and receiving dataand / or signals wirelessly. In certain embodiments, the antenna 11310 is separate from the network node 11300 and connectable to the network node 11300 through an interface or port.

[0292] The antenna 11310, communication interface 11306, and / or the processing circuitry 11302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 11310, the communication interface 11306, and / or the processing circuitry 11302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0293] The power source 11308 provides power to the various components of network node 11300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 11308 may comprise, or be coupled to, power management circuitry to supply the components of the network node 11300 with power for performing the functionality described herein. For example, the network node 11300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 11308. As a further example, the power source 11308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0294] Embodiments of the network node 11300 may include additional components beyond those shown in FIG.11 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 11300 may include user interface equipment to allow input of information into the network node 11300 and to allow output of information from the network node 11300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 11300.

[0295] FIG.12 is a block diagram of a host 12400, which may be an embodiment of the host 9116 of FIG.9, in accordance with various aspects described herein. As used herein, the host 12400 may be or comprise various combinations hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 12400 may provide one or more services to one or more UEs.

[0296] The host 12400 includes processing circuitry 12402 that is operatively coupled via a bus 12404 to an input / output interface 12406, a network interface 12408, a power source 12410, and a memory 12412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the terminal devices, such that the descriptions thereof are generally applicable to the corresponding components of host 12400.

[0297] The memory 12412 may include one or more computer programs including one or more host application programs 12414 and data 12416, which may include user data, e.g., data generated by a UE for the host 12400 or data generated by the host 12400 for a UE. Embodiments of the host 12400 may utilize only a subset or all of the components shown. The host application programs 12414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 12414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 12400 may select and / or indicate a different host for over-the-top services for a UE. The host application programs 12414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0298] FIG.13 is a block diagram illustrating a virtualization environment 13500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 13500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 13500 includes components defined by the O-RAN Alliance, such as an O-Cloudenvironment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

[0299] Applications 13502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 13500 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0300] Hardware 13504 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 13506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 13508 A and 13508B (one or more of which may be generally referred to as VMs 13508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 13506 may present a virtual operating platform that appears like networking hardware to the VMs 13508.

[0301] The VMs 13508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 13506. Different embodiments of the instance of a virtual appliance 13502 may be implemented on one or more of VMs 13508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0302] In the context of NFV, a VM 13508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 13508, and that part of hardware 13504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 13508 on top of the hardware 13504 and corresponds to the application 13502.

[0303] Hardware 13504 may be implemented in a standalone network node with generic or specific components. Hardware 13504 may implement some functions via virtualization. Alternatively, hardware 13504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 13510, which, among others, oversees lifecycle management of applications13502. In some embodiments, hardware 13504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 13512 which may alternatively be used for communication between hardware nodes and radio units.

[0304] FIG.14 shows a communication diagram of a host 14602 communicating via a network node 14604 with a UE 14606 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 9111a of FIG.9), network node (such as network node 9110a of FIG.9), and host (such as host 9116 of FIG.9 and / or host 12400 of FIG.12) discussed in the preceding paragraphs will now be described with reference to FIG.14.

[0305] Like host 12400, embodiments of host 14602 include hardware, such as a communication interface, processing circuitry, and memory. The host 14602 also includes software, which is stored in or accessible by the host 14602 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 14606 connecting via an over-the-top (OTT) connection 14650 extending between the UE 14606 and host 14602. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 14650.

[0306] The network node 14604 includes hardware enabling it to communicate with the host 14602 and UE 14606. The connection 14660 may be direct or pass through a core network (like core network 9106 of FIG.9) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

[0307] The UE 14606 includes hardware and software, which is stored in or accessible by UE 14606 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 14606 with the support of the host 14602. In the host 14602, an executing host application may communicate with the executing client application via the OTT connection 14650 terminating at the UE 14606 and host 14602. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 14650 may transfer both the request data and the user data. The UE's clientapplication may interact with the user to generate the user data that it provides to the host application through the OTT connection 14650.

[0308] The OTT connection 14650 may extend via a connection 14660 between the host 14602 and the network node 14604 and via a wireless connection 14670 between the network node 14604 and the UE 14606 to provide the connection between the host 14602 and the UE 14606. The connection 14660 and wireless connection 14670, over which the OTT connection 14650 may be provided, have been drawn abstractly to illustrate the communication between the host 14602 and the UE 14606 via the network node 14604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0309] As an example of transmitting data via the OTT connection 14650, in step 14608, the host 14602 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 14606. In other embodiments, the user data is associated with a UE 14606 that shares data with the host 14602 without explicit human interaction. In step 14610, the host 14602 initiates a transmission carrying the user data towards the UE 14606. The host 14602 may initiate the transmission responsive to a request transmitted by the UE 14606. The request may be caused by human interaction with the UE 14606 or by operation of the client application executing on the UE 14606. The transmission may pass via the network node 14604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 14612, the network node 14604 transmits to the UE 14606 the user data that was carried in the transmission that the host 14602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 14614, the UE 14606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 14606 associated with the host application executed by the host 14602.

[0310] In some examples, the UE 14606 executes a client application which provides user data to the host 14602. The user data may be provided in reaction or response to the data received from the host 14602. Accordingly, in step 14616, the UE 14606 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE 14606. Regardless of the specific manner in which the user data was provided, the UE 14606 initiates, in step 14618, transmission of the user data towards the host 14602 via the network node 14604. In step 14620, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 14604 receives user data from the UE 14606 and initiates transmission of the received user data towards the host 14602. In step 14622, the host 14602 receives the user data carried in the transmission initiated by the UE 14606.

[0311] One or more of the various embodiments improve the performance of OTT services provided to the UE 14606 using the OTT connection 14650, in which the wireless connection 14670 forms the last segment. More precisely, in some embodiments herein, the proposed solution specifies behavior to handle DL data at a network node such as RAN node when the terminal device is unable to respond e.g. in scenarios like RRC connectionless. In some embodiments herein, the proposed solution may increase DL transmission reliability by providing an opportunity at the network node such as RAN node to hold the DL data e.g. until certain timer and / or wait for the terminal device to respond e.g. before the timer expires and / or allows the network node such as RAN node to deliver the data successfully.

[0312] In an example scenario, factory status information may be collected and analyzed by the host 14602. As another example, the host 14602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 14602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 14602 may store surveillance video uploaded by a UE. As another example, the host 14602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 14602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and / or transmitting data.

[0313] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 14650 between the host 14602 and UE 14606, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 14602 and / or UE 14606. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 14650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 14650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 14604. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, bythe host 14602. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 14650 while monitoring propagation times, errors, etc.

[0314] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0315] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0316] The term unit or module may have conventional meaning in the field of electronics, electrical devices and / or electronic devices and may include, for example, electrical and / orelectronic circuitry, devices, modules, processors, memories, logic solid state and / or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and / or displaying functions, and so on, as such as those that are described herein.

[0317] According to an aspect of the disclosure it is provided a computer program product being tangibly stored on a computer readable storage medium and including instructions which, when executed on at least one processor, cause the at least one processor to carry out any of the methods as described above.

[0318] According to an aspect of the disclosure it is provided a computer-readable storage medium storing instructions which when executed by at least one processor, cause the at least one processor to carry out any of the methods as described above.

[0319] In addition, the present disclosure may also provide a carrier containing the computer program as mentioned above, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium. The computer readable storage medium can be, for example, an optical compact disk or an electronic memory device like a RAM (random access memory), a ROM (read only memory), Flash memory, magnetic tape, CD-ROM, DVD, Blue-ray disc and the like.

[0320] The techniques described herein may be implemented by various means so that an apparatus implementing one or more functions of a corresponding apparatus described with an embodiment comprises not only prior art means, but also means for implementing the one or more functions of the corresponding apparatus described with the embodiment and it may comprise separate means for each separate function, or means that may be configured to perform two or more functions. For example, these techniques may be implemented in hardware (one or more apparatuses), firmware (one or more apparatuses), software (one or more modules), or combinations thereof. For a firmware or software, implementation may be made through modules (e.g., procedures, functions, and so on) that perform the functions described herein.

[0321] Exemplary embodiments herein have been described above with reference to block diagrams and flowchart illustrations of methods and apparatuses. It will be understood that each block of the block diagrams and flowchart illustrations, and combinations of blocks in the block diagrams and flowchart illustrations, respectively, can be implemented by various means including computer program instructions. These computer program instructions may be loaded onto a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions which execute on the computer or other programmable data processing apparatus create means for implementing the functions specified in the flowchart block or blocks.

[0322] 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 subject matter described herein, 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.

[0323] While this specification contains many specific implementation details, these should not be construed as limitations on the scope of any implementation or of what may be claimed, but rather as descriptions of features that may be specific to particular embodiments of particular implementations. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable sub -combination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a sub -combination or variation of a sub-combination.

[0324] It will be obvious to a person skilled in the art that, as the technology advances, the inventive concept can be implemented in various ways. The above described embodiments are given for describing rather than limiting the disclosure, and it is to be understood that modifications and variations may be resorted to without departing from the spirit and scope of the disclosure as those skilled in the art readily understand. Such modifications and variations are considered to be within the scope of the disclosure and the appended claims. The protection scope of the disclosure is defined by the accompanying claims.

Claims

WHAT IS CLAIMED IS:

1. A method (300) performed by a first network node, comprising: obtaining (302) at least one parameter indicating how to handle data intended for a terminal device; and handling (304) the data based on the at least one parameter.

2. The method according to claim 1, wherein the at least one parameter comprises at least one of: an indicator indicating whether the first network node needs to buffer the data, a timer indicating the first network node to keep the data in a buffer until the timer is expired, a maximum number of data packets that the first network node needs to store in the buffer, retransmission times that the first network node can try retransmissions to deliver the data to the terminal device, a duration for which the data stored in the buffer is valid, or a maximum volume of the data that the first network node needs to store in the buffer.

3. The method according to claim 2, wherein handling the data based on the at least one parameter comprises at least one of: when the terminal device is not responsive, the first network node keeps the data in the buffer, when the terminal device is able to establish with the first network node, the first network node delivers the data as long as the data is still stored in the buffer, when the timer expires, the first network node clears the data, when the maximum number of stored data packets is reached and a new data packet is received, the first network node clears an oldest data packet in the buffer, when the maximum volume of the data is reached and new data is received, the first network node clears oldest data in the buffer, when the retransmission times is reached, the first network node clears the data, when the duration is invalid, the first network node clears the data, when the first network node successfully delivers the data, the first network node clears the data, during a mobility scenario, the first network node delivers the data to a new access network node, when the terminal device is accessing a network via a new access network node, the first network node delivers the data to the new access network node,when the first network node does not need to buffer the data, the first network node immediately delivers the data, when the first network node does not deliver the data to the terminal device and decides to clear the data, the first network node delivers the data to the core network node for buffering, or when the first network node has not received a feedback from the terminal device for a given or configured period of time, the first network node delivers the stored data to the core network node for buffering.

4. The method according to any of claims 1-3, wherein a value of the at least one parameter is set based on at least one of: a data type, a terminal device type, an indication of a user plane function, a policy of an access and mobility management function, a terminal device energy-harvesting capability type, or a latency budget of the data.

5. The method according to any of claims 1-4, wherein the at least one parameter is applied to at least one of: the data intended for all terminal devices, the data intended for a specific terminal device, the data intended for a class of terminal devices, all types of data, a specific type of data, the data for all types of services, the data for a specific type of service, a data packet, or the data for a protocol data unit session.

6. The method according to any of claims 1-5, wherein the at least one parameter is determined by at least one of: a session management function, a user plane function, an access and mobility management function, or an access network node.

7. The method according to any of claims 1-6, further comprising: when the terminal device is unable to be paged or connected, sending (402), to an access and mobility management function, a message for informing about a lost of the terminal deviceand / or asking the access and mobility management function to re-initiate a registration or connection procedure.

8. The method according to any of claims 1-7, further comprising: sending (502), to an access and mobility management function, a first message for estimating a reachability timer of the terminal device.

9. The method according to claim 8, further comprising: receiving (512), from an access and mobility management function, a second message comprising an estimated maximum wait time for delivering the data to the terminal device.

10. The method according to any of claims 8-9, further comprising: when the terminal device is considered reachable, receiving (522), from an access and mobility management function, a third message for paging the terminal device; and paging (524) the terminal device.

11. The method according to any of claims 8-10, further comprising: when the terminal device is considered reachable, receiving (532), from an access and mobility management function, a fourth message for delivering the data to the terminal device; and delivering (534) the data to the terminal device.

12. The method according to any of claims 1-11, wherein the obtaining at least one parameter indicating how to handle data intended for a terminal device comprising at least one of: obtaining the at least one parameter from a user plane function, obtaining the at least one parameter from an access and mobility management function, obtaining the at least one parameter from another access network node, or determining the at least one parameter by itself.

13. The method according to claim 12, further comprising: resetting (542) a value of the at least one parameter.

14. The method according to any of claims 1-13, wherein the at least one parameter is obtained from at least one of: an in-band signaling as part of the data, a message during a PDU session establishment or modification procedure, a message during a handover procedure, or a message during an initial registration procedure.

15. The method according to any of claims 1-14, wherein the data comprises user plane data or control plane based data transmission or data not associated with a quality of service profile or identifier.

16. The method according to any of claims 1-15, wherein the terminal device comprises at least one of: an ultra- low power device, a zero-energy device, an Internet of Things device, a device requiring Ultra Reliable Low Latency Communication, a device using Enhanced Mobile Broadband service, a device using Massive Machine Type Communication service or a device using Time Sensitive Networking.

17. The method according to any of claims 1-16, wherein the first network node comprises at least one of: an access network node, or a user plane function.

18. A method (600) performed by a second network node, comprising: determining (602) at least one parameter indicating how to handle data intended for a terminal device; and sending (604) the at least one parameter to a first network node.

19. The method according to claim 18, wherein the at least one parameter comprises at least one of: an indicator indicating whether the first network node needs to buffer the data, a timer indicating the first network node to keep the data in a buffer until the timer is expired, a maximum number of data packets that the first network node needs to store in the buffer, retransmission times that the first network node can try retransmissions to deliver the data to the terminal device, a duration for which the data stored in the buffer is valid, or a maximum volume of the data that the first network node needs to store in the buffer.

20. The method according to any of claims 18-19, wherein a value of the at least one parameter is determined based on at least one of: a data type, a terminal device type, an indication of a user plane function, a policy of an access and mobility management function, a terminal device energy-harvesting capability type, or a latency budget of the data.

21. The method according to any of claims 18-20, wherein the at least one parameter is applied to at least one of: the data intended for all terminal devices, the data intended for a specific terminal device, the data intended for a class of terminal devices, all types of data, a specific type of data, the data for all types of services, the data for a specific type of service, a data packet, or the data for a protocol data unit session.

22. The method according to any of claims 18-21, wherein the second network node comprises at least one of: a session management function, or an access and mobility management function.

23. The method according to any of claims 18-22, wherein when the second network node is an access and mobility management function, the method further comprises: when the terminal device is unable to be paged or connected, receiving (612), from an access network node, a message for informing about a lost of the terminal device and / or asking the access and mobility management function to re-initiate a registration or connection procedure; and re-initiating (614) the registration or connection procedure.

24. The method according to any of claims 18-23, further comprising: receiving (622), from the first network node, a first message for estimating a reachability timer of the terminal device; and estimating (624) the reachability timer of the terminal device.

25. The method according to claim 24, further comprising: sending (632), to the first network node, a second message comprising an estimated maximum wait time for delivering the data to the terminal device.

26. The method according to any of claims 24-25, further comprising: when the terminal device is considered reachable, sending (642), to the access network node, a third message for paging the terminal device.

27. The method according to any of claims 24-26, further comprising: when the terminal device is considered reachable, sending (652), to the first network node, a fourth message for delivering the data to the terminal device.

28. The method according to any of claims 18-27, wherein the at least one parameter is sent in at least one of: an in-band signaling as part of the data, a message during a PDU session establishment or modification procedure, a message during a handover procedure, or a message during an initial registration procedure.

29. The method according to any of claims 18-28, wherein the data comprises user plane data or control plane based data transmission or data not associated with a quality of service profile or identifier.

30. The method according to any of claims 18-29, wherein the terminal device comprises at least one of: an ultra- low power device, a zero-energy device, an Internet of Things device, a device requiring Ultra Reliable Low Latency Communication, a device using Enhanced Mobile Broadband service, a device using Massive Machine Type Communication service or a device using Time Sensitive Networking.

31. The method according to any of claims 18-30, wherein the first network node comprises at least one of: an access network node, or a user plane function.

32. A first network node (800), comprising: a processor (821); and a memory (822) coupled to the processor (821), said memory (822) containing instructions executable by said processor (821), whereby said first network node (800) is operative to: obtain at least one parameter indicating how to handle data intended for a terminal device; and handle the data based on the at least one parameter.

33. The first network node according to claim 32, wherein the first network node is further operative to perform the method of any one of claims 2 to 17.

34. A second network node (800), comprising: a processor (821); and a memory (822) coupled to the processor (821), said memory (822) containing instructions executable by said processor (821), whereby said second network node (800) is operative to:determine at least one parameter indicating how to handle data intended for a terminal device; and send the at least one parameter to a first network node.

35. The second network node according to claim 34, wherein the second network node is further operative to perform the method of any one of claims 19 to 31.

36. A computer-readable storage medium storing instructions which when executed by at least one processor, cause the at least one processor to perform the method according to any one of claims 1 to 31.

37. A computer program product comprising instructions which when executed by at least one processor, cause the at least one processor to perform the method according to any one of claims 1 to 31.

Images