Communication network, network node, UE and method for communication of downlink data attempt message

Abstract

Embodiments of present disclosure provide communication network 200 for communication of downlink data attempt message relating to a communication attempt from server 202 to User equipment, UE, 102. Communication network 200 comprises a plurality of network functions, each network function being implemented at least partly in corresponding network node 104. First network function 502 is arranged to communicate with UE 102. Second network function 504 is arranged to receive data notification message originating from server 202, send downlink data attempt message to first network function 502. First network function 502 is further arranged to identify operating mode for UE 102. First network function 502 stores downlink data attempt message when the operating mode is identified as a first operating mode and transmit downlink data attempt message to UE 102, in second operating mode.

Description

[0001] COMMUNICATION NETWORK, NETWORK NODE, UE AND METHOD FOR COMMUNICATION

[0002] OF DOWNLINK DATA ATTEMPT MESSAGE

[0003] TECHNICAL FIELD

[0004] The present disclosure relates generally to a field of wireless communication. More particularly, it relates to first network node, second network node, User Equipment, UE, method implemented in UE and computer program products for communication of downlink data attempt message in a communication network.

[0005] BACKGROUND

[0006] In Third Generation Partnership Project, 3GPP networks, handling downlink data for unreachable devices due to power saving modes may cause a challenge to manage the downlink data. A solution using Extended buffering support feature may address the challenge by allowing User Plane Function, UPF to temporarily store data based on instructions from Session Management Function, SMF. When the downlink data arrives at the UPF, the UPF consults the SMF for handling the unreachable devices (devices may be hereinafter referred to User Equipment, UE). The UPF then either buffers or drops the downlink data as instructed by the SMF and this applies to the UEs not reachable. Due to the power saving modes of the UEs, it may not be possible to reach the UEs by paging as well. The SMF notifies an Access and Mobility Management Function, AMF when UE is reachable again. Once the UE is reachable, the AMF may initiate a network-triggered service request, potentially involving paging for delivering the buffered data to the UE.

[0007] Across mobile generations, various User Equipment, UE power saving methods have been developed to conserve battery of the UE and to optimize radio resources. Some examples of power saving methods for the UE are Discontinuous Reception, DRX, Extended Discontinuous Reception, eDRX, Mobile Initiated Connection Only) and UE power saving mode. The DRX and eDRX features apply across generations, i.e., from second-generation cellular network, 2G to fifth-generation cellular network, 5G. The DRX and eDRX features allow UE to periodically "sleep" and reduce its radio activity. DRX offers shorter sleep periods while eDRX may extend the sleep periods to several hours, potentially leading to longer periods of unavailability of the UE. Introduced in 5G, MICO allows the UE to initiate data transfers and For MICO it is typically the granularity of hour / hours when periodic registration update in 5GC (Tracking area updates in legacy) applies. The UE power saving mode is applicable in fourth-generation cellular network, 4G.

[0008] Optimizing power consumption through UE power saving is not only beneficial for smartphones; but also essential for various types of Internet of Things, loT devices.

[0009] Further, in mobile broadband, MBB networks, paging method is used to either send downlink data or downlink signaling from the network to change the UE to Connected state. In contrast to MBB UEs, RedCap devices utilizing the power saving methods like eDRX are only reachable for a small time period and most of the time may not be reachable to save battery in the UE.

[0010] RedCap is added in 3GPP for 5G networks and is in short "loT for New Radio, NR. The RedCap UE has reduced capability in terms of radio impact and the RedCap was introduced to limit UE complexity as well as UE cost. For the RedCap devices, UE power saving is of importance. The RedCap devices addresses many areas such as: wearables, video surveillance, industrial wireless sensors. Examples of wearables are smart watches, Extended Reality, XR, Virtual Reality, VR, Augmented Reality, AR.

[0011] In an example, power saving strategies for the UEs with different network connections are described now. There are two types of connectivity use-cases such as: internet connected UEs and private network connected UEs.

[0012] In internet connected UEs:

[0013] - Traffic from the external network requires a firewall with a timeout and outbound traffic is prohibited, i.e traffic can not be initiated by network.

[0014] - For battery saving, Operating System, OS vendors keeps only one "notification flow" open to minimize signalling and battery drain.

[0015] - With a power saving activated UE, e.g. eDRX, power saving strategies such as paging may work well if firewall updates wake up the UE, i.e. if the firewall update frequency (detected) is used to trigger wakeup in the UE side.

[0016] In private network connected UEs:

[0017] - Traffic from external networks may arrive at any time as the network often is protected. Paging typically wakes up the UE, so coordination with the network is not needed.

[0018] - With a power saving activated UE, e.g. eDRX, power saving strategies such as paging may not work well. Polling is required for payload retrieval, similar to Internet connected UEs.

[0019] SUMMARY

[0020] The solution as discussed above involves multiple 5GC network functions for coordination.

[0021] Further, with the existing 3GPP solution, the UE is not notified of any missed any payload attempts while unreachable.

[0022] Furthermore, the buffered data may be discarded if the UE remains unreachable for extended periods.

[0023] Thus, there is a need for an improved communication network, first network node, second network node, User equipment, UE and method for communication of downlink data attempt message relating to a communication attempt from a server to the UE, which alleviates at least some of the above-cited problems.

[0024] It is therefore an object of the present disclosure to provide a communication network, a first network node, a second network node, User equipment, UE and method for communication of the downlink data attempt message relating to a communication attempt from the server to the UE to mitigate, alleviate, or eliminate all or at least some of the above-discussed drawbacks of presently known solutions.

[0025] According to a first aspect of the present disclosure, a communication network for communication of downlink data attempt message relating to a communication attempt from a server to a User equipment, UE is provided. The communication network comprises a plurality of network functions, each network function being implemented at least partly in a corresponding network node. A first network function from the plurality of network functions is arranged to communicate with the UE. A second network function from the plurality of network functions is arranged to receive a data notification message. The second network function is further arranged to send the downlink data attempt message relating to the communication attempt from the server in the communication network, to the first network function. The first network function in the communication network is further arranged to identify an operating mode for the UE. The first network function is further arranged to store the downlink data attempt message when the operating mode is identified as a first operating mode for transmission in a second operating mode.

[0026] Optionally, when the operating mode is identified as the second operating mode, the first network function is arranged to perform the transmission of the downlink data attempt message to the UE.

[0027] Optionally, the UE being arranged to obtain the downlink data attempt message originating from the server through the first network function.

[0028] Optionally, the UE comprises a controlling circuitry. The controlling circuitry is configured to transmit a registration request to the first network function after the UE enters the second operating mode. If the registration request is transmitted then the first network function transmits the down link data attempt message relating to the communication attempt from the server if such information is available, from when the UE was in the first operating mode.

[0029] Optionally, the UE is arranged to receive, a registration accept message from the first network function in response the transmission of the registration request.

[0030] Optionally, the communication network further comprising a third network function among the plurality network function. The third network function is arranged to receive a data notification message from the server containing the downlink data attempt message originating from the server to the UE. The third network function is further arranged to send, the data notification message to the second network function from the plurality of network function.

[0031] Optionally, the first network function comprises an Access and Mobility Management Function, AMF, and wherein the second network function comprises a session management function, SMF and wherein the third network function comprises a user plane function, UPF.

[0032] Optionally, the first operating mode comprises a power saving mode. Optionally, the second operating mode comprises a normal operating mode.

[0033] Optionally, the second network function from the plurality of network function is arranged to send the downlink data attempt message to the first network function, upon receipt of the data notification message from the third network function in the communication network.

[0034] Optionally, the third network function is arranged to send the data notification message to the second network function per each Quality of Service, QoS flow for establishing a protocol data unit, PDU session between the UE and the server.

[0035] Optionally, the first network function is arranged to store the downlink data attempt message when the UE remains in the first operating mode.

[0036] Optionally, the server is connected with a plurality of application server and the server collects notifications of plurality of applications through the plurality application server.

[0037] Optionally, the downlink data attempt message comprises at least one of:

[0038] -information related to receipt of a downlink data packet per QoS flow and a PDU session;

[0039] - information related to receipt of the downlink data packet per the PDU session; or

[0040] - information related to receipt of the downlink data packet from any of the PDU session.

[0041] According to a second aspect of the present disclosure, there is provided a UE for obtaining downlink data attempt message relating to a communication attempt from a server in a communication network. The UE comprises a controlling circuitry. The controlling circuitry is configured to cause transmitting a registration request to a first network function after the UE enters a second operating mode. If The registration request is transmitted after the UE is entering a first operating mode, the first network function will include in registration accept message to the UE down link data attempt message relating to the communication attempt from the server, if such information is available.

[0042] Optionally, the UE is further arranged to transmit a service request to the first network function after the UE enters a second operating mode. The service request is transmitted to cause the first network function for transmitting down link data attempt message originating from the server, until the UE entered in a second operating mode. Optionally, the UE is arranged to receive a registration accept message from the first network function in response the transmission of the registration request.

[0043] Optionally, the UE is arranged to receive a configuration update command message from the first network function in response the transmission of the network triggered service request or UE triggered Service Request.

[0044] Optionally, the first operating mode comprises a power saving mode.

[0045] Optionally, the second operating mode comprises a normal operating mode.

[0046] According to a third aspect of the present disclosure, a method implemented in the UE for obtaining downlink data attempt message relating to a communication attempt from a server in a communication network is provided. The method comprises transmitting, a registration request or a service request to the first network function after the UE enters a second operating mode. The method further comprises causing the first network function for transmitting down link data attempt message relating to the communication attempt from the server, after the UE is in a first operating mode. The registration request or service request is transmitted to cause the first network function for transmitting down link data attempt message, after the UE is in a first operating mode.

[0047] Optionally, the UE is arranged to receive a registration accept message from the first network function in response the transmission of the registration request.

[0048] Optionally, the UE is arranged to receive a configuration update command message from the first network function as a result of the transmission of the service request.

[0049] Optionally, the first operating mode comprises a power saving mode.

[0050] Optionally, the second operating mode comprises a normal operating mode.

[0051] According to a fourth aspect of the present disclosure, there is provided a first network node for communication of downlink data attempt message relating to a communication attempt from the server to the UE. The first network node comprises a first network function arranged to communicate with the UE. The first network function is further arranged to receive from a second network function, a downlink data attempt message related to a communication attempt from the server in the communication network. The first network function is further arranged to identify the operating mode for the UE. The first network function is further arranged to store the downlink data attempt message after the operating mode is identified as a first operating mode. The first network function is further arranged to transmit the downlink data attempt message is to the UE, after identification that the UE is in the second operating mode.

[0052] Optionally, the first network function comprises an Access and Mobility Management Function, AMF.

[0053] Optionally, the second network function comprises a session management function, SMF.

[0054] Optionally, the first operating mode comprises a power saving mode.

[0055] Optionally, the second operating mode comprises a normal operating mode.

[0056] Optionally, the first network node is arranged to send the downlink data attempt message to the UE as a configuration update message or as a registration accept message.

[0057] Optionally, the first network function is arranged to receive the downlink data attempt message from the second network function, upon receipt of a data notification message from the third network function in the communication network.

[0058] Optionally, the first network function is arranged to store the downlink data attempt message when the UE remains in the first operating mode.

[0059] Optionally, the downlink data attempt message comprises at least one of

[0060] -information related to receipt of a downlink data packet per QoS flow and a PDU session;

[0061] -information related to receipt of the downlink data packet per the PDU session; or

[0062] -information related to receipt of the downlink data packet from any of the PDU session.

[0063] According to a fifth aspect of the present disclosure, there is provided a second network node for communication of downlink data attempt message from the server to the UE. The second network node comprises a second network function arranged to send a downlink data attempt message relating to a communication attempt from the server in the communication network, to a first network function, after receiving a data notification message originating from the server. Optionally, the second network function is further arranged to: collect and store information provided by the third network function during a Network triggered Service Request procedure per PDU session.

[0064] Optionally, the second network function is further arranged to: transmit the information provided by the third network function to the first network function when the first network function notifies the second operating mode of the UE.

[0065] Optionally, the second network function is arranged to send the downlink data attempt message to the first network function, after receipt of a data notification message from a third network function.

[0066] According to a sixth aspect of the present disclosure, there is provided a computer program product comprising a non-transitory computer readable medium, having thereon a computer program comprising program instructions. The computer program is loadable into a data processing unit and configured to cause execution of the method according to the first and second aspects when the computer program is run by the data processing unit.

[0067] Some embodiments disclosed herein have one or more of the following advantages:

[0068] - Eliminates unnecessary polling between the UE and server, saving battery life.

[0069] - Minimized unnecessary communication between the UE and the server, significantly reducing power consumption of the server.

[0070] - Providing a power efficient solution to UE as, the UE only requests server notifications as registration request, when the server has actually tried to reach it, not just after waking from every power saving mode. As the UE receives information about downlink data attempt through the downlink data attempt message, the UE knows when the server has actually tried to reach it.

[0071] - Providing a straightforward approach by communicating the downlink data attempt message between a first network function and the UE, avoiding complex solutions like extended buffering. Hence, easy to implement.

[0072] - Simpler and more efficient than 3GPP extended buffering support solutions, as in the extended buffering support solutions, the UE may not be available for longer periods of time. - Since the UE has limited availability for notifications for short time, it leverages "Downlink Data Attempts" information to efficiently exchange downlink data with the server.

[0073] Other advantages may be readily apparent to one having skill in the art. Certain embodiments may have none, some, or all of the recited advantages.

[0074] BRIEF DESCRIPTION OF THE DRAWINGS

[0075] The foregoing will be apparent from the following more particular description of the example embodiments, as illustrated in the accompanying drawings in which like reference characters refer to the same parts throughout the different views. The drawings are not necessarily to scale, emphasis instead being placed upon illustrating the example embodiments.

[0076] FIG. 1 discloses a wireless communication system according to some examples;

[0077] FIG. 2 is an example communication network for communication of downlink data attempt message from a server (202) to a User equipment, UE (204), according to some embodiments of the present disclosure;

[0078] FIG. 3 is a schematic block diagram illustrating an example UE according to some embodiments of the present disclosure;

[0079] FIG. 4 is a is a flowchart illustrating example method steps of a method implemented in the UE for obtaining downlink data attempt message relating to a communication attempt from a server in a communication network, according to some embodiments of the present disclosure;

[0080] FIG. 5A-5C are schematic block diagrams of different example network nodes according to some embodiments of the present disclosure;

[0081] FIG. 6 is signalling diagram illustrating example signalling communication between the UE and the plurality of network functions, according to some embodiments of the present disclosure;

[0082] FIG. 7 discloses an example computing environment according to some embodiments.

[0083] DETAILED DESCRIPTION

[0084] Aspects of the present disclosure will be described more fully hereinafter with reference to the accompanying drawings. The systems and methods disclosed herein can, however, be realized in many different forms and should not be construed as being limited to the aspects set forth herein. Like numbers in the drawings refer to like elements throughout.

[0085] The terminology used herein is for the purpose of describing particular aspects of the disclosure only and is not intended to limit the invention. It should be emphasized that the term "comprises / comprising" when used in this specification is taken to specify the presence of stated features, integers, steps, or components, but does not preclude the presence or addition of one or more other features, integers, steps, components, or groups thereof. 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.

[0086] Embodiments of the present disclosure will be described and exemplified more fully hereinafter with reference to the accompanying drawings. The solutions disclosed herein can, however, be realized in many different forms and should not be construed as being limited to the embodiments set forth herein.

[0087] It will be appreciated that when the present disclosure is described in terms of a system and a method, it may also be embodied in one or more processors and one or more memories coupled to the one or more processors, wherein the one or more memories store one or more programs that perform the steps, services and functions disclosed herein when executed by the one or more processors.

[0088] FIG. 1 discloses an example wireless communication system 100. Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the examples disclosed herein are described in related to a wireless communication system / wireless network, such as the example wireless communication system 100 described in FIG. 1.

[0089] The wireless communication system 100 may comprise and / or interface with any type of communication, telecommunication, data, cellular, and / or radio network or other similar type of system. The wireless communication system 100 may be configured to operate according to specific standards or other types of predefined rules of procedures. Thus, the wireless communication system 100 may implement communication standards, such as, 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, or 5G standards, or future generation network technology e.g. sixth generation network technology and / or subsequently developed network technology, wireless local area network, WLAN, standards such as, IEEE 802.11 standards, and / or any other appropriate wireless communication standards, such as, worldwide interoperability for microwave access, WiMax, Bluetooth, Z-Wave and / or ZigBee standards.

[0090] For simplicity, as depicted in FIG. 1, the wireless communication system 100 comprises a User Equipment, UE 102, a network node 104, and a communication network 200 (communication network may be alternatively referred as network). The UE 102 and the network node 104 operate together in order to provide wireless connections in the wireless communication system 100. The network 200 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks, PSTNs, packet data networks, optical networks, wide-area networks, WANs, local area networks, LANs, wireless local area networks, WLANs, wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices (for example, wireless devices and network node).

[0091] In an example, the network node 104 refer to equipment capable, configured, arranged, and / or operable to communicate directly or indirectly with the UE 102 and / or with other network nodes or equipment in the wireless communication system 100 to enable and / or provide wireless access to the UE 102 and / or to perform other functions (for example, administration) in the wireless communication system 100. Examples of the network node 104 may include, but are not limited to, access points, APs (for example, radio access points), base stations, BSs (for example, radio base stations, nodeBs, evolved NodeBs, eNBs, new radio, NR, nodes (gNBs), or the like). The BSs may be categorized based on an amount of coverage the BSs provide (or, stated different, their transmit power level) and may then also be referred to as femto BSs, pico BSs, micro BSs, macro BSs. The BS may be a relay node or a relay donor node controlling a relay.

[0092] The UE 102 refers to a device capable, configured, arranged and / or operable to communicate wirelessly with the network node 104 and / or other wireless devices.

[0093] In some examples, the UE 102 may include one or more of: computing devices, wireless devices, ultra-low power wireless devices, Internet of Things, loT, devices, and so on. Examples of the computing devices may include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over Internet Protocol, IP, VoIP, phone, a wireless local loop phone, a desktop computer, a personal digital assistant, PDA, a wireless camera, a gaming console or device, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment, LEE, a laptop-mounted equipment, LME, a smart device, a wireless customer-premise equipment, CPE, a vehicle- mounted wireless terminal device, and so on.

[0094] It should be understood that the UE 102 may not be limited to the above-described wireless devices. The communication may be extended to other wireless devices of different classes or categories providing different services while supporting, for example, Enhanced Mobile Broadband, eMBB, massive Machine-Type Communication, MTC, Ultra-Reliable Low Latency Communication, URLLC, Time Sensitive Networking, TSN, or the like.

[0095] In the wireless communication system 100, the network node 104 and the UE 102 are connected through 3GPP 5G core network where specific network services and operations are provided through software components called network functions (NFs). The wireless communication system 100 hosts large scale applications.

[0096] FIG. 2 discloses an example communication network architecture 200 or simply referred as communication network 200 for communication of downlink data attempt message from a server 202 to the UE 102. The downlink data attempt message is related to a communication attempt from the server 202 in the communication network 200. In some examples, there may be a plurality of UEs 102 in a communication network 200 arranged to be served by at least one mobile network operator (not shown in FIG. 2).

[0097] The communication network 200 comprises a plurality of network functions (502, 504, 506 which are later shown in FIG. 5). Each network function being implemented at least partly in a corresponding network node from a plurality of network nodes 104a, 104b...104n. A first network function 502 (later shown in FIG. 5) from the plurality of network functions is arranged to communicate with the UE 102. The UE 102 is arranged to obtain the downlink data attempt message relating to a communication attempt from the server 202 through the first network function 502. A second network function 504 (later shown in FIG. 5) from the plurality of network functions is arranged to receive a data notification message. The second network function 504 is further arranged to send a downlink data attempt message to the first network function 502. The downlink data attempt message is related to the communication attempt from the server 202 in the communication network 200. The first network function 502 is further arranged to identify, an operating mode forthe UE 102. When the operating mode is identified as a first operating mode, the first network function 502 stores the downlink data attempt message, for transmission in a second operating mode.

[0098] Optionally, after the operating mode is identified as the second operating mode, the first network function 502 is arranged to perform the transmission of the downlink data attempt message to the UE 102.

[0099] Optionally, the UE 102 being arranged to obtain the downlink data attempt message originating from the server 202 through the first network function 502.

[0100] Optionally, the UE 102 comprises a controlling circuitry 306. The controlling circuitry is configured to transmit, a registration request or a service request to the first network function after the UE 102 enters the second operating mode. If registration request is transmitted after the UE 102 enters the first operating mode, then the first network function 502 may transmit the down link data attempt message relating to the communication attempt from the server 202 if such information is available. If service request is transmitted after the UE 102 enters the first operating mode, then the first network function 502 may transmit the down link data attempt message relating to the communication attempt from the server 202 if such information is available

[0101] Optionally, the UE 102 is arranged to receive, a registration accept message from the first network function 502 in response the transmission of the registration request. Optionally, the UE is arranged to receive a configuration update command message from the first network function as a result of the transmission of the service request.

[0102] Optionally, the communication network 200 further comprising a third network function 506 among the plurality network function. The third network function 506 is arranged to receive a data notification message from the server 202 containing the downlink data attempt message originating from the server 202 to the UE 102. The third network function 506 is further arranged to send, the data notification message to the second network function 504 from the plurality of network function.

[0103] Optionally, the first network function 502 comprises an Access and Mobility Management Function, AMF, and wherein the second network function 504 comprises a session management function, SMF and wherein the third network function 506 comprises a user plane function, UPF.

[0104] Optionally, the first operating mode comprises a power saving mode.

[0105] Optionally, the second operating mode comprises a normal operating mode.

[0106] Optionally, the second network function 504 from the plurality of network function is arranged to send the downlink data attempt message to the first network function 502, upon receipt of the data notification message from the third network function 506 in the communication network.

[0107] Optionally, the third network function 506 is arranged to send the data notification message to the second network function 504 per each Quality of Service, QoS flow for establishing a protocol data unit, PDU session between the UE 102 and the server 202. In an example, the data notification message is sent on application level which gives some information to the UE for the applications 204 used. In an example, the data notification message is usually sent on a payload path. In some examples, the data notification message may comprise Non-Access Stratum, NAS messages. In an example, the data notification message may contain information and the UE 102 has updated information in the server 202 to fetch.

[0108] Optionally, the first network function 502 is arranged to store the downlink data attempt message when the UE 102 remains in the first operating mode.

[0109] Optionally, the server 202 is connected with a plurality of application server 206 and wherein the server 202 collects notifications of the plurality of applications 204 through the plurality application server 206.

[0110] Optionally, the downlink data attempt message comprises at least one of:

[0111] -information related to receipt of a downlink data packet per QoS flow and a PDU session; - information related to receipt of the downlink data packet per the PDU session; or

[0112] - information related to receipt of the downlink data packet from any of the PDU session.

[0113] In an example, as shown in FIG. 2, the UE 102 hosts a first application 204 which may perform registration through Operating System, OS of the UE 102 in the server 202. In an example, as shown in Figure 2, there may be other applications 204a, 204b hosted in the UE 102.

[0114] In some examples, as shown in FIG. 2, there may be a plurality of application servers 206a, 206b, 206c (collectively may referred as application server 206). The application server 206 may arranged to receive key from the applications 202 hosted in the UE 102 after a concluded Protocol Data Unit, PDU session establishment between applications 204 on the UE and a Data Network 210. In some examples, the data network 210 can be Internet or private corporate networks. By sending the key to the application server 206, the application server 206 will come to know about the availability of the application 204 hosted on the UE 102 and then the application server may be aware of the server 202 to perform any notification request further on for the application 204.

[0115] In some examples, as shown in FIG. 2, the plurality of network nodes 104a, 104b...l04n are connected to a 5GC network 212.

[0116] In some examples, the server 202 can be e.g. an Apple server operated by Apple Inc. to provide various online services to Apple customers. In some examples, the server 202 can be e.g. a Google server operated by Google Inc. to provide various online services to Google customers etc.

[0117] In some examples, as shown in FIG. 2, there may be a Firewall, FW which allows for Uplink / Downlink data based on a timer. In an example, FW may have a timer typically e.g. 5 - 10 minutes.

[0118] In some examples, the communication network 200, for example, may be an informational technology network, an operational technology network, a cloud infrastructure, a software as a service, SaaS, infrastructure, or any combination thereof, connected to each of the computing devices. In FIG. 3, an example UE 102 is illustrated comprising one or more modules. The one or more modules may comprise a memory 302, a processor 304, a controlling circuitry 306, and a driver 308. The controlling circuitry 306, may be adapted to control the other modules.

[0119] The memory 302, the processor 304 and the driver 308 as well as the controlling circuitry 306, may be operatively connected to each other.

[0120] The memory 302 may be adapted to store the downlink data attempt message relating to a communication attempt from the server 202. In an example, the memory 302 may be adapted to store the downlink data originated at the server 202.

[0121] The processor 304 may be adapted to identify that the server may be tried to establish communication for transmitting downlink data or for establishing the PDU session. The processor 304 may be adapted to transmit the registration request to the first network function 502, after UE on the second operating mode.

[0122] The controlling circuitry 306 may be adapted to control the steps as executed by the UE 102. For example, the controlling circuitry 306 may be adapted to transmit the registration request or a service request to the first network function 502 when the UE enters the second operating mode. In an example, the service request comprises a UE triggered Service request. The registration request or the service request is transmitted to cause the first function to transmit downlink data attempt message relating to the communication attempt from the server 202, when the UE 102 is in the first operating mode.

[0123] The UE 102 sends the registration request message (due to trigger condition fulfilled). Further, the UE 102 may send a Service Request message (due to trigger condition fulfilled), which will cause the first network function 502 to send the configuration update command message to the UE 102 including the down link data attempt message. A network triggered Service Request where the first network function 502 in addition will send the configuration update command to the UE 102 including the down link data attempt message. The driver 308 may be adapted to process the downlink data attempt message received and transmitted by the UE 102.

[0124] The UE 102 of FIG. 3 is provided for obtaining downlink data attempt message relating to the communication attempt from the server 202 in a communication network 200. Optionally, the UE 102 is arranged to receive a registration accept message or a configuration update command message from the first network function 502 in response the transmission of the registration request or as a result of the transmission of the service request (which may be part of a UE triggered service request or a network triggered service request).

[0125] Optionally, the first operating mode comprises a power saving mode.

[0126] Optionally, the second operating mode comprises a normal operating mode.

[0127] FIG. 4 is a is a flowchart illustrating example method steps of a method 400 implemented in the UE 102 for obtaining downlink data attempt message relating to the communication attempt from the server 202 in the communication network 200.

[0128] The order in which the method 400 is described is not intended to be construed as a limitation, and any number of the described method blocks may be combined in any order to implement the method 400 or alternate methods. Additionally, individual blocks may be deleted from the method 400 without departing from the spirit and scope of the embodiments described herein.

[0129] At step 402, the method 400 comprises transmitting the registration request to the first network function 502, after the UE 102 enters the second operating mode. The transmission may be performed through the controlling circuitry 306.

[0130] At step 404, the method 400 comprises causing the first function 502 to transmit downlink data attempt message relating to the communication attempt from the server 202, when the UE 102 is in the first operating mode.

[0131] Optionally, the UE 102 is arranged to receive a registration accept message from the first network function 502 in response the transmission of the registration request.

[0132] Optionally, the first operating mode comprises a power saving mode.

[0133] Optionally, the second operating mode comprises a normal operating mode.

[0134] FIG. 5A-5C are schematic block diagrams of different example network nodes according to some examples. The network nodes may be in a core network equipment of a 5G network, a Long Term Evolution, LTE system or other wireless communication systems which, which may include one or more network functions. In an example, as shown in FIG. 5A, the first network functions 502, the second network function 504, and the third network function 506 are being implemented in the first network node 104a. In an example, as shown in FIG. 5B, the first network functions 502, the second network function 504 are being implemented in the second network node 104b. In an example, as shown in FIG. 5B, the first network functions 502 is being implemented in a third network node 104c to communicate with the UE 102.

[0135] In some examples, the first network functions 502 comprises an access and management function, AMF. The second network function 504 comprises the session management function, SMF. The third network function 506 comprises the user plane function, UPF. In some examples, the first network functions 502 in the network nodes 104a, 104b, 104c may be utilized for managing the access and mobility of the UE 102. The second network function 504 may be utilized for managing the PDU sessions, e.g. establishing, modifying or releasing PDU sessions and the third network function 506 may be utilized for receiving the downlink data.

[0136] The first network node 104a is arranged for communication of downlink data attempt message relating to a communication attempt from the server 202 to the UE 102. The network node 104a comprises the first network function 502. The first network function 502 is arranged to communicate with the UE 102. The first network function 502 is arranged to receive the downlink data attempt message from the second network function 504. The downlink data attempt message is related to the communication attempt from the server 202 in the communication network 200. The first network function 502 is further arranged to identify the operating mode for the UE 102. The first network function 502 is further arranged to store the downlink data attempt message after the operating mode is identified as the first operating mode. The first network function 502 is further arranged to transmit the downlink data attempt message is to the UE 102, upon identification that the UE 102 is in the second operating mode.

[0137] Optionally, the first network function 502 comprises the Access and Mobility Management Function, AMF.

[0138] Optionally, the second network function 504 comprises a session management function, SMF.

[0139] Optionally, the first operating mode comprises a power saving mode. Optionally, the second operating mode comprises a normal operating mode.

[0140] Optionally, the first network node is arranged to send the downlink data attempt message to the UE 102 as a configuration update command message or as a registration accept message.

[0141] In an example, the configuration update command message is sent to the UE 102 as part of a UE triggered Service Request or a Network triggered Service Request procedure.

[0142] In an example, the configuration update command message is sent to the UE 102 after a concluded or together with UE triggered Service Request or a Network triggered Service Request procedure. In other words, the configuration update command message can be sent either (1) after concluded UE initiated Service request or network initiated service request or (2) in the end of UE triggered Service request or networked initiated service request.

[0143] Optionally, the first network function (502) is arranged to receive the downlink data attempt message from the second network function (504), upon receipt of a data notification message from the third network function in the communication network.

[0144] Optionally, the first network function is arranged to store the downlink data attempt message when the UE remains in the first operating mode. In an example, the first network function 502 will perform paging when network triggered service request applies and when the first network function 502 detects that the UE 102 can be reachable. A successful network triggered service request means that UE change to second operating mode (also may refer as connected state). If the first network function 502 detects that UE 102 can not be reachable as it is in deep sleep, no paging message will be sent by the first network function 502 in network triggered service request. Optionally, the server 202 is connected with a plurality of application server 206 and the server collects notifications from a plurality of applications 204 through the plurality application server 206.

[0145] Optionally, the downlink data attempt message comprises at least one of

[0146] -information related to receipt of a downlink data packet per QoS flow and a PDU session;

[0147] -information related to receipt of the downlink data packet per the PDU session; or

[0148] -information related to receipt of the downlink data packet from any of the PDU session. The second network node 104b is arranged for communication of downlink data attempt message from the server 202 to the UE 102. The second network node 104b comprises the second network function 504 arranged to send the downlink data attempt message to the first network function 502 upon receiving the data notification message relating to the communication attempt from the server 202. The downlink data attempt message is related to the communication attempt from the server 202 in the communication network 200.

[0149] Optionally, the second network function 504 is arranged to send the downlink data attempt message the first network function 502, upon receipt of a data notification message from a third network function 506.

[0150] FIG. 6 is a signalling diagram illustrating example signalling communication between the UE 102 and the plurality of network functions 502, 504, 506, according to some examples. In the communication network 200, when the server 202 wants to transmit the downlink data or downlink data attempt message related to the communication attempt to the UE 102, the signaling communication established between the plurality of network functions. FIG. 6, shows a Network triggered Service Request procedure (3GPP TS 23.502 §4.2.3.3) where the triggering happened due to receipt of the downlink data 602 at the third network function 506. Upon receipt of the downlink data 602, the third network function 506 sends a Data Notification message 604 to the second network function 504. By receiving the data notification message 604, the second network function 504 may send an acknowledgement through a data notification ack message 606. After receiving the data notification ack message 606, the third network function 506 sends the downlink data 602 to the second network function 504 and then the second network function 504 sends the downlink data attempt message 608 to the first network function 502. In an example, the data attempt message 608 may send as a "Namf_Communication_NlN2Message Transfer Request" message. Optionally, the first network function 502 may send an acknowledgement message to the second network function 504. In an example, the acknowledgement message may comprise a "Namf_Communication_NlN2Message Transfer Response" message 612. If the first network function 502 is not able to page due to the first operating mode, e.g, power saving mode of the UE 102, the first network function 502 stores the downlink data attempt message 608. In an example, the first network function 502 may store all information received per each QoS flow and PDU session (the PDU sessions can be from several second network function 504). Once, the UE 102 is in the second operating mode, e. g, when the UE 102 is in Connected state, the first network function 502 provides the downlink data attempt message 608 to the UE 102. In an example, the downlink data attempt message 608 is sent either as the registration accept message (as part of a registration procedure (3GPP TS 23.502 §4.2.2)) or as the configuration update message (also may referred as, configuration update command (as part of a Configuration Update Command procedure (3GPP TS 23.502 §4.2.4.2)). In an example, the Configuration Update Command can e.g., be sent as part of or after a concluded UE triggered Service Request (3GPP TS 23.502 §4.2.3.2) or a Network triggered Service Request procedure (3GPP TS 23.502 §4.2.3.3). The downlink data attempt message 608 may be provided to the UE e.g. either as part of registration procedure (in registration accept message), UE triggered Service Request (in Configuration Update Command message) or network triggered Service Request (in Configuration Update Command message) and can e.g. be provided in the first procedure that occurs after the UE enters second operation mode.

[0151] In some examples, the downlink data attempt message 608 includes information related to the communication attempts (also may referred as downlink data attempt or downlink data attempt message), e.g., if any communication for transmitting downlink data are made or not. The UE 102 may use the downlink data attempt message 608 information to identify the application 204 hosted in the UE 102, and the information can be seen as UE implementation specific. If there has been any downlink data attempt(s), the UE 102 may use the information to notify the server 202 or service providers (not shown in the FIGS.). The server 202 may then provide the information which are needed to the UE 102. In an example, the information may be related to any client application.

[0152] In some examples, the second network function 504 may collect and store the downlink data attempt message 608 during a Network triggered Service Request procedure (3GPP TS 23.502 §4.2.3.3) per PDU session and provide the information or the downlink data attempt message 608 to the first network function 502 when the first network function 502 notifies that the UE 102 is reachable. The second network function 504 may then send the downlink data attempt message 608 to the first network function 502. In an example, the first network function 502 may capture collected information of the second network function 502 per PDU session. The first network function 502 may provide the collected information to the UE 102 either as the registration accept message or as the configuration update command. In some examples, the downlink data attempt message may include any of the information:

[0153] -information related to receipt of a downlink data packet per QoS flow and a PDU session;

[0154] - information related to receipt of the downlink data packet per the PDU session; or

[0155] - information related to receipt of the downlink data packet from any of the PDU session.

[0156] FIG. 7 illustrates an example-computing environment 700 implementing the UE 102, as described in FIG. 3, and method as described in FIG. 4. As depicted in FIG. 7, the computing environment 700 comprises at least one data processing module 706 that is equipped with a control module 702 and an Arithmetic Logic Unit (ALU) 704, a plurality of networking devices 708 and a plurality Input output, I / O devices 710, a memory 712, a storage 714. The data processing module 706 may be responsible for implementing the UE and method described in FIGS 3 and 4 respectively. For example, the data processing module 706 in some embodiments be equivalent to the controlling circuitry of the platform described above in conjunction with FIGS. 3 and 4. The data processing module 706 is capable of executing software instructions stored in memory 712. The data processing module 706 receives commands from the control module 702 in order to perform its processing. Further, any logical and arithmetic operations involved in the execution of the instructions are computed with the help of the ALU 704.

[0157] The computer program is loadable into the data processing module 706, which may, for example, be comprised in an electronic apparatus (such as the platform). When loaded into the data processing module 706, the computer program may be stored in the memory 712 associated with or comprised in the data processing module 706. According to some embodiments, the computer program may, when loaded into and run by the data processing module 606, cause execution of method steps according to, for example, any of the methods illustrated in FIGS. 3 and 4, or otherwise described herein.

[0158] The overall computing environment 700 may be composed of multiple homogeneous and / or heterogeneous cores, multiple CPUs of different kinds, special media and other accelerators. Further, the plurality of data processing modules 606 may be located on a single chip or over multiple chips.

[0159] The algorithm comprising of instructions and codes required for the implementation are stored in either the memory 712 or the storage 714 or both. At the time of execution, the instructions may be fetched from the corresponding memory 712 and / or storage 714, and executed by the data processing module 706.

[0160] In case of any hardware implementations various networking devices 708 or external I / O devices 710 may be connected to the computing environment to support the implementation through the networking devices 708 and the I / O devices 710. The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the elements. The elements shown in FIG. 7 include blocks which can be at least one of a hardware device, or a combination of hardware device and software module.

Claims

CLAIMS1. A communication network (200) for communication of a downlink data attempt message relating to a communication attempt from a server (202) in the communication network (200) to a User equipment, UE (102), the communication network (200) comprising: a plurality of network functions (502, 504, 506), each network function being implemented at least partly in a corresponding network node (104), wherein a first network function (502) from the plurality of network functions (502, 504, 506) is arranged to communicate with the UE (102); wherein, a second network function (504) from the plurality of network functions is arranged to: receive a data notification message originating from the server (202); send the downlink data attempt message relating to the communication attempt from the server (202) in the communication network (200), to the first network function (502); wherein, the first network function (502) is arranged to: identify, an operating mode for the UE (102), and after the operating mode is identified as a first operating mode, store, the downlink data for transmission in a second operating mode.

2. The communication network (200) according to claim 1, wherein after the operating mode is identified as the second operating mode, the first network function (502) is arranged to perform the transmission of the downlink data attempt message to the UE (102).

3. The communication network (200) according to any of the preceding claims, further comprising the UE, said UE being arranged to obtain the downlink data attempt message originating from the server (202) through the first network function (502).

4. The communication network (200) according to any of the preceding claims, wherein the UE (102) comprises: a controlling circuitry (306) configured to:transmit a registration request to the first network function (502) after the UE (102) enters the second operating mode; wherein the registration request is transmitted to cause the first network function (502) to transmit the down link data attempt message relating to the communication attempt from the server (202), while the UE (102) was in the first operating mode.

5. The communication network (200) according to any of the preceding claims, wherein the UE (102) is further arranged to: transmit a Service Request to the first network function (502) after the UE (102) enters the second operating mode; wherein the Service Request is transmitted to cause the first network function (502) to transmit the down link data attempt message relating to the communication attempt from the server (202), while the UE (102) was in the first operating mode.

6. The communication network (200) according to any of the preceding claims, wherein the UE (102) is arranged to receive a registration accept message or a configuration update command message from the first network function (502) in response the transmission of the registration request or as a result of the transmission of the service request.

7. The communication network (200) according to any of the preceding claims, wherein the first network function (502) comprises an Access and Mobility Management Function, AMF.

8. The communication network (200) according to any of the preceding claims, wherein the second network function (504) comprises a session management function, SMF.

9. The communication network (200) according to any of the preceding claims, wherein the first operating mode comprises a power saving mode.

10. The communication network (200) according to any of the preceding claims, wherein the second operating mode comprises a normal operating mode.

11. The communication network (200) according to any of the preceding claims, wherein the second network function (504) from the plurality of network function is arranged to send the downlink data attempt message to the first network function (502), after receipt of the data notification message from the third network function (506) in the communication network (200).

12. The communication network (200) according to any of the preceding claims, wherein the first network function (502) is arranged to store the downlink data attempt message when the UE (102) remains in the first operating mode.

13. The communication network (200) according to any of the preceding claims, wherein the downlink data attempt message comprises at least one of:-information related to receipt of a downlink data packet per QoS flow and a PDU session;- information related to receipt of the downlink data packet per the PDU session; or- information related to receipt of the downlink data packet from any of the PDU session.

14. A User Equipment, UE (102) configured for obtaining downlink data attempt message originating from a server (202) in a communication network (200), the UE (102) comprising a controlling circuitry (306) configured to cause: transmitting a registration request to a first network function (502) after the UE (102) enters a second operating mode, wherein the registration request is transmitted to cause the first network function (502) for transmitting down link data attempt message originating from the server (202), until the UE entered in a second operating mode.

15. The UE (102) according to claim 14, wherein the UE (102) is further arranged to: transmit a service request to the first network function (502) after the UE (102) enters a second operating mode, wherein the service request is transmitted to cause the first network function (502) for transmitting down link data attempt message originating from the server (202), until after the UE entered in a second operating mode.

16. The UE (102) according to any claim 14-15 wherein the UE (102) is arranged to receive a registration accept message or configuration update command message from the first network function (502) in response the transmission of the registration request.

17. The UE (102) according to any claim 14-16, wherein the first operating mode comprises a power saving mode.

18. The UE (102) according to any claim 14-16, and wherein the second operating mode comprises a normal operating mode.

19. A method implemented in a User Equipment, UE (102), for obtaining downlink data attempt message originating from a server (202) in a communication network (200), the method comprising: transmitting, a registration request to the first network function (502) after the UE enters a second operating mode; wherein registration request is transmitted to cause the first network function (502) for transmitting down link data attempt message relating to the communication attempt from the server (202), after the UE (102) is in a first operating mode.

20. The method according to claim 19, wherein the method further comprises: transmitting a service request to the first network function (502) when the UE (102) enters a second operating mode, wherein the service request is transmitted to cause the first network function (502) for transmitting down link data attempt message originating from the server (202), until after the UE entered in a second operating mode.

21. The method according to claim any claim 19-20, wherein the UE (102) is arranged to receive a registration accept message from the first network function (502) in response the transmission of the registration request or a configuration update command message from the first network node (502) as a result of the transmission of the service request.

22. The method according to any claim 19-21, wherein the first operating mode comprises a power saving mode.

23. The method according to any claim 19-21, wherein the second operating mode comprises a power saving mode comprises a normal operating mode.

24. A first network node (104a) for communication of downlink data attempt message relating to a communication attempt from a server (202) to a User Equipment, UE, (102), the first network node (104a) comprising: a first network function (502) arranged to communicate with the UE (102), wherein the first network function (502) is further arranged to: receive from a second network function (504) a downlink data attempt message related to a communication attempt from the server (202) in the communication network (200); identify, an operating mode for the UE (102), after the operating mode is identified as a first operating mode, store the downlink data attempt message; and upon identification that the UE (102) is in a second operating mode, transmitting the downlink data attempt message is to the UE (102).

25. The first network node (104a) according to claim 24, wherein the first network function (502) comprises an Access and Mobility Management Function, AMF.

26. The first network node (104a) according to claim 24, wherein the second network function (504) comprises a session management function, SMF.

27. The first network node (104a) according to any of claims 24-26, wherein the first network node is arranged to send the downlink data attempt message to the UE (102) as a configuration update command message or as a registration accept message.

28. The first network node (104a) according to any of claims 24-27, wherein the first network function (502) is arranged to receive the downlink data attempt message from the second network function (504)).

29. The first network node (104a) according to any of claims 24-28, wherein the first network function (502) is arranged to store the downlink data attempt message when the UE (102) remains in the first operating mode.

30. The first network node (104a) according to any of claims 24-29, wherein the downlink data attempt message comprises at least one of:-information related to receipt of a downlink data packet per QoS flow and aPDU session;-information related to receipt of the downlink data packet per the PDU session; or-information related to receipt of the downlink data packet from any of the PDU session.

31. A second network node (104b) for communication of downlink data attempt message relating to a communication attempt from a server to a User Equipment, UE, (102), the second network node (104b) comprising: a second network function (504), said network function is arranged to: send a downlink data attempt message relating to a communication attempt from the server (202) in the communication network (200), to a first network function (502), upon receiving a data notification message relating to the communication attempt from the server (202).

32. The second network node (104b) according to claim 30, wherein, the second network function (504) is further arranged to: collect and store information provided by the third network function (506) during a Network triggered Service Request procedure per PDU session.

33. The second network node (104b) according to claim 30-31, wherein, the second network function (504) is further arranged to: transmit the information provided by the third network function (506) to the first network function (502) after the first network function (502) notifies the second operating mode of the UE (102).

34. The second network node (104b) according to any claims 30-32, wherein, the second network function (504) is arranged to send the downlink data attempt message to the first network function (502), after receipt of a data notification message from a third network function (506).

35. A computer program product comprising a non-transitory computer readable medium, having thereon a computer program comprising program instructions, the computer program is loadable into a data processing unit and configured to cause execution of the method according to any of claims 20 through 23 when the computer program is run by the data processing unit.

Images