Energy data from user plane function

By adding UPF IDs and subscribing to gNB ID during PFCP session updates, the method addresses filter overlaps and communication gaps in 5G networks, improving energy consumption data accuracy and reducing SMF processing burden.

WO2026234651A1PCT designated stage Publication Date: 2026-11-12TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/IB2026/054664
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-09
Filing Date
2026-05-11
Publication Date
2026-11-12

Smart Images

  • Figure IB2026054664_12112026_PF_FP_ABST
    Figure IB2026054664_12112026_PF_FP_ABST
Patent Text Reader

Abstract

Embodiments of a method performed by a Session Management Function (SMF) are described. The method includes adding, to a User Plane Function (UPF), during a Packet Forwarding Control Protocol (PFCP) session establishment or update, path information comprising at least one of one or more UPF identifiers and one or more user plane addresses. In some embodiments, the SMF receives, from an Energy Information Function (EIF), a subscription request for volume information and path information from the UPF and forwards the subscription request to the UPF. In other embodiments, a method performed by an Access and Mobility Management Function (AMF) includes maintaining, for one or more User Equipments, one or more of a set of UE access behavior trends and a set of UE location trends and exposing the maintained trends to a consumer network function in response to a subscription. Corresponding network nodes are also disclosed.
Need to check novelty before this filing date? Find Prior Art

Description

ENERGY DATA FROM USER PLANE FUNCTIONCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of priority to U.S. Provisional Patent Application No. 63 / 803083, filed May 9, 2025, the entire contents of which are hereby incorporated by reference.TECHNICAL FIELD

[0002] The present disclosure relates to wireless communication networks, and more particularly to energy consumption information collection in a 5G network.BACKGROUND

[0003] It may be desirable to collect energy consumption data for a User Equipment (UE) from the Session Management Function (SMF). In clause 5.51.2.2.2 of 3GPP TS 23.501 it is described how the Energy Information Function (EIF) collects data for Energy calculations. EIF gets this information from the SMF, i.e. SMF aggregates data that it receives from the Access and Mobility Management Function (AMF) and the User Plane Function (UPF) and reports to EIF. In 3GPP temporary document S2-2503632, the SMF fetches the data volume from UPF using the Usage Reporting Rule (URR) specified in 3GPP TS 29.244.

[0004] There currently exist certain challenges. The SMF utilizes URR in the UPF for reporting traffic volume data. However, this creates a potential for a filter provided by EIF to SMF to overlap the filters already defined in the Packet Detection Rules (PDRs). Additionally, SMF must perform translations of network identifiers, such as converting cell IDs to gNodeB (gNB) IDs. If an Intermediate-SMF (I-SMF) is in the communication path, then changes to the cell ID (and consequently gNB) may not be properly communicated to the SMF. This communication gap may prevent the EIF from correctly performing energy consumption calculations.SUMMARY

[0005] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. In one respect, certain embodiments in keeping with the present disclosure add path information, such as UPF IDs or user plane addresses, to the UPF during PFCP session establishment or update, as discussed in 3GPP TS 29.244. This process could be triggered by the establishment or modification of a PDU session. In this framework, when the EIF collects volume and path information from the UPF, (1) it subscribes to this data via the Session Management Function (SMF), (2) the SMF forwards this subscription request to theUPF, and (3) the UPF reports both 5G Core (5GC) path information and volume data directly to the EIF. In another respect, certain embodiments in keeping with the present disclosure include a mechanism for the EIF to subscribe to the gNB ID from the AMF by utilizing the Namf_EventExposure service.

[0006] Certain embodiments may provide one or more of the following technical advantage(s). During Protocol Data Unit (PDU) session establishment or modification, the Session Management Function (SMF) incorporates path information in the Packet Forwarding Control Protocol (PFCP) communication over the N4 interface during session establishment or update procedures. When later subscription requests are made using the Nupf_EventExposure service, indicators are included to instruct the User Plane Function (UPF) to include path information in its reports and to report according to network-wide default times and intervals. Additionally, the EIF could directly specify the clock times and intervals in its subscription request, rather than relying on indicator-triggered default parameters. Also, the Access and Mobility Management Function (AMF) may offer gNodeB (gNB) ID as available reporting information through the Namf_EventExposure Service. In certain embodiments, signaling traffic through the SMF will be reduced. In certain embodiments, there will be lower overall processing requirements and computational burden on the SMF. In certain embodiments, energy consumption calculations will be more precise, including in cases where an I-SMF is used.

[0007] According to a first aspect of the present disclosure, there is provided a method performed by a Session Management Function, SMF. The method includes adding, to a User Plane Function, UPF, during a Packet Forwarding Control Protocol, PFCP, session establishment or update, path information including at least one of: one or more UPF identifiers and one or more user plane addresses.

[0008] In some embodiments, the method further includes, in response to a change of data path for an ongoing subscription, updating a PFCP session associated with the UPF such that the UPF closes a current measurement report and starts a new measurement report including updated path information.

[0009] In some embodiments, the method further includes receiving, from an Energy Information Function, EIF, a subscription request for volume information and path information from the UPF, and forwarding, to the UPF, the subscription request, the path information added to the UPF enabling the UPF to establish a direct reporting channel between the UPF and the EIF and to report, to the EIF, 5G Core, 5GC, path information and volume data associated with a Protocol Data Unit, PDU, session.

[0010] In some embodiments, the subscription request received from the EIF includes an indicator instructing the UPF to include path information in reports sent on the direct reporting channel. In some embodiments, the subscription request received from the EIF specifies a clock time and an interval for reporting by the UPF. In some embodiments, the subscription request received from the EIF includes an indicator instructing the UPF to report according to a network-wide default starting time and default interval. In some embodiments, the subscription request forwarded to the UPF further includes an event filter, the event filter including at least one of: a packet filter and an application identifier. In some embodiments, adding the path information to the UPF is performed in response to establishment or modification of the PDU session. In some embodiments, the EIF is configured to obtain a gNodeB, gNB, identifier from an Access and Mobility Management Function, AMF, and to correlate the gNB identifier with the path information and volume data reported by the UPF.

[0011] According to a second aspect of the present disclosure, there is provided a method performed by an Access and Mobility Management Function, AMF. The method includes maintaining, for one or more User Equipments, UEs, one or more of: a set of UE access behavior trends and a set of UE location trends. The method further includes, in response to a subscription, exposing, to a consumer network function, one or more of: the set of UE access behavior trends and the set of UE location trends.

[0012] In some embodiments, the set of UE access behavior trends includes, for each of one or more state transitions, one or more of: an indication of the state transition, a spacing between consecutive occurrences of the state transition, and a duration in a resulting state. In some embodiments, the set of UE location trends includes, for each of one or more locations, one or more of: an indication of the location, a spacing between consecutive arrivals at the location, a duration of stay in the location, and a timestamp of a last arrival in the location. In some embodiments, the set of UE access behavior trends, or the set of UE location trends, or both, is maintained using an exponential moving average.

[0013] According to a third aspect of the present disclosure, there is provided a system for energy consumption reporting in a 5G network. The system includes a Session Management Function, SMF; a User Plane Function, UPF; and an Energy Information Function, EIF. The SMF is configured to add, to the UPF, during a Packet Forwarding Control Protocol, PFCP, session establishment or update, path information including at least one of: one or more UPF identifiers and one or more user plane addresses. The SMF is further configured to forward, to the UPF, a subscription request received from the EIF. By virtue of the path information added by the SMF, the UPF is configured to establish a direct reporting channel between the UPF andthe EIF, and to report, to the EIF over the direct reporting channel and without traversing the SMF, 5G Core, 5GC, path information and volume data associated with a Protocol Data Unit, PDU, session.

[0014] According to further aspects of the present disclosure, corresponding network nodes, computer programs, computer program products, and computer-readable media are also provided. In some such embodiments, a network node configured to operate as the SMF includes processing circuitry configured to perform operations of any of the foregoing method aspects. In some such embodiments, a network node configured to operate as the AMF includes processing circuitry configured to perform operations of any of the foregoing method aspects.BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 is a signaling diagram illustrating an exchange of signals in an example procedure for energy consumption information collection in a wireless network, in accordance with some embodiments;

[0016] Figure 2 is a flowchart illustrating an example method performed by a Session Management Function, in accordance with some embodiments;

[0017] Figure 3 is a block diagram illustrating an example cellular communication system, in accordance with some embodiments;

[0018] Figure 4 is a block diagram illustrating an example wireless local area network communication system, in accordance with some embodiments;

[0019] Figure 5 is a block diagram illustrating an example wireless device, in accordance with some embodiments;

[0020] Figure 6 is a block diagram illustrating an example network node, in accordance with some embodiments;

[0021] Figure 7 is a block diagram illustrating an example virtualization environment, in accordance with some embodiments; and

[0022] Figure 8 is a flowchart illustrating an example method performed by an Access and Mobility Management Function, in accordance with some embodiments.DETAILED DESCRIPTION

[0023] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0024] Figure 3 shows an example of a communication system 300 in accordance with some embodiments.

[0025] In the example, the communication system 300 includes a telecommunications network 302 that includes an access network 304, such as a radio access network (RAN), and a core network 306, which includes one or more core network nodes 308. The access network 304 includes one or more access network nodes or base stations of various types, access network nodes 310A and 310B are depicted (which may be collectively referred to as network nodes 310), or any other similar 3rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 304 may include more than one access network technology. The network nodes 310 of access network 304 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs 312A, 312B, 312C, and 312D (one or more of which may be generally referred to as UEs 312) to the core network 306 over one or more wireless connections.

[0026] Moreover, 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 telecommunications network 302 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 302 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 network nodes to implement one or more functionalities of any network node in the telecommunications network 302, including one or more access network nodes 310 and / or core network nodes 308.

[0027] 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 (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective "open" designating support of an ORAN specification). An ORAN 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 network 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 mayinclude an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the 0-RAN Alliance or comparable technologies.

[0028] The network nodes 310 facilitate direct or indirect connection of one or more UEs 312 to the core network 306 over one or more wireless connections. 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 300 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 300 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0029] The UEs 312 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 310 and other communication devices. Similarly, the network nodes 308, 310 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 302) with the UEs 312 and / or with other network nodes or equipment in the telecommunications network 302 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 302. More specifically, UEs 312 may send messages, data, and / or other signals to network nodes 308, 310 or other elements of the telecommunications network 302 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 308, 310 may send messages, data, and other signals to UEs 312, other network nodes 308, 310, and other devices in telecommunications network 302 directly or indirectly. As one specific example, a core network node 308 may transmit a particular message to a UE 312 by transmitting the message to an access network node 310 that will then transmit the message to the intended UE 312. Similarly, a core network node 308 may receive a particular message from a UE 312 by receiving the message from an access network node 310 that itself received the message from the UE 312.

[0030] In the depicted example, the core network 306 connects elements of the access network 304 (e.g., one or more of the network nodes 310) to one or more host computing systems, such as host 316. 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 306 includes one or more core network nodes (e.g., core network node 308) of various types, one or more of which may be generally referred to as network nodes 308. Network nodes 308 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 308. Example core network nodes provide 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 (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0031] The host 316 may be under the ownership or control of a service provider other than an operator or provider of the access network 304 and / or the telecommunications network 302. The host 316 may be operated by the service provider or on behalf of the service provider. The host 316 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.

[0032] As a whole, the communication system 300 of Figure 3 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 300 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 (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 300 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 300 supporting different standards, protocols, or rule sets.

[0033] As one example, in certain embodiments, access network 304 may contain some access network nodes 310 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 310 support (or the same access network nodes 310 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 302 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP communication standards) and, as a result, may include an access network 304 and / or a core network 306 that supports multiple different standard generations or may include multiple access networks 304 and / or multiple core networks 306 with individual networks 304, 306 supporting different standard generations.

[0034] Telecommunications network 302 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 302. For example, the telecommunications network 302 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.

[0035] In some examples, one or more of the UEs 312 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 304 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 304. 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).

[0036] In the example, the hub 314 communicates with the access network 304 to facilitate indirect communication between one or more UEs (e.g., UE 312C and / or 312D) and network nodes (e.g., network node 310B). In some examples, the hub 314 may be a controller, router, content source and analytics, or any of the other communication devices described hereinregarding UEs. For example, the hub 314 may be a broadband router enabling access to the core network 306 for the UEs. As another example, the hub 314 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 310, or by executable code, script, process, or other instructions in the hub 314.

[0037] As another example, the hub 314 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 314 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 314 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 314 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 314 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0038] The hub 314 may have a constant / persistent or intermittent connection to the network node 310B. The hub 314 may also allow for a different communication scheme and / or schedule between the hub 314 and UEs (e.g., UE 312C and / or 312D), and between the hub 314 and the core network 306. In other examples, the hub 314 is connected to the core network 306 and / or one or more UEs via a wired connection. Moreover, the hub 314 may be configured to connect to an M2M service provider over the access network 304 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 310 while still connected via the hub 314 via a wired or wireless connection. In some embodiments, the hub 314 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 310B. In other embodiments, the hub 314 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 310B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0039] Figure 4 is another example of a communication system 400 according to some embodiments. As used herein, the communication system 400 includes multiple access points (APs) 410 (with four exemplary APs 410A, 410B, 410C, and 410D being depicted) and multiple wireless devices, referred to in the context of communication system 400 as stations (STAs) 412 (referred to individually as STA 412A, STA 412B, STA 412C, STA 412D, and STA 412E). STA 412A is served by AP 410A in a first basic service set (BSS) 420A. STA412B and STA 412C are served by AP 410B in a second BSS, BSS 420B. STA 412D is served by AP 410C in a third BSS, BSS 420C. STA 412E is served by AP 410D in a fourth BSS, BSS 420D. Stations 412 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations 412 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

[0040] Each AP 410 may provide data connectivity to STAs 412 connected to a particular AP 410. As illustrated, APs 410 may be connected to a data network 430. In this way, APs 410 may also provide data connectivity between STAs 412 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, the radio link established between a given STA 412 and its serving AP 410 may be used for providing various kinds of services to STA 412, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 412 and / or on a device linked to STA 412. By way of example, Figure 4 illustrates an application service platform 432 provided in data network 430. The application(s) executed on STA 412 and / or on one or more other devices linked to STA 412 may use the radio link for data communication with one or more other STA 412 and / or the application service platform 432, thereby enabling utilization of the corresponding service(s) at STA 412.

[0041] Figure 5 shows a wireless device 500, which may be configured to operate in communication system 300 of Figure 3 or in communication system 400 of Figure 4. The wireless device 500 may be alternatively referred to as a UE 500, like a UE 312 within the context of communication system 300, or as a station (STA) 500 or as a non-access-point station (non-AP STA) 500, like a STA 412 within the context of the communication system 400, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Examples of a wireless device 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, mobile station, 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, and wireless terminal. Otherexamples include any type of 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.

[0042] A wireless device 500 may support device-to-device (D2D) communication, for example by implementing a 3GPP 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, wireless device 500 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 500 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, wireless device 500 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).

[0043] In particular embodiments, wireless device 500 includes processing circuitry 502 that is operatively coupled via a bus 504 to an input / output interface 506, a power source 508, a memory 510, a communication interface 512, and / or any other component, or any combination thereof. Certain embodiments of wireless device 500 may include all or a subset of the components shown in Figure 5. The level of integration between the components may vary from one embodiment of wireless device 500 to another. In general, in a particular embodiment of wireless device 500, processing circuitry 502, input / output interface 506, power source 508, memory 510, and communication interface 512 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device 500. Further, certain embodiments of wireless devices 500 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0044] The processing circuitry 502 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 510. The processing circuitry 502 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 502 may include multiple central processing units (CPUs).

[0045] In the example, the input / output interface 506 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 any combination thereof. An input device may allow a user to capture information into wireless device 500. 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.

[0046] In some embodiments, the power source 508 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 to supply power to circuitry or to charge an associated battery. The power source 508 may further include power circuitry for delivering power from the power source 508 itself, and / or an external power source, to the various parts of wireless device 500 via input circuitry or an interface such as an electrical power cable. Power source 508 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 500 to which power is supplied.

[0047] The memory 510 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 510 includes one or more programs 514, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 516. The memory 510 may store, for use by wireless device 500, any of a variety of various operating systems or combinations of operating systems.

[0048] The memory 510 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, externalhard 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 circuit card (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 510 may allow wireless device 500 to access instructions, 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 510, which may be or include a device-readable storage medium.

[0049] The processing circuitry 502 may be configured to communicate with an access network or other network via or using the communication interface 512. The communication interface 512 may include one or more communication subsystems and may include or be communicatively coupled to an antenna 522. The communication interface 512 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 wireless device or a network node in an access network). Each transceiver may include a transmitter 518 and / or a receiver 520 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 518 and receiver 520 may be coupled to one or more antennas (e.g., antenna 522) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0050] In the illustrated embodiment, communication functions of the communication interface 512 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), 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 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.

[0051] In particular embodiments, wireless device 500 may provide an output of data captured via a sensor, through its communication interface 512, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device 500 can be communicated through a wireless connection to a network node via another wireless device 500. In particular embodiments, such 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 several sensors), 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).

[0052] As another example, wireless device 500 includes 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, wireless device 500 may include 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.

[0053] Wireless device 500, 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 includeing, but not limited to, 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 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. In particular embodiments, wireless device 500 represents an loT device that includes 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 example embodiment of wireless device 500 shown in Figure 5.

[0054] As yet another specific example, in an loT scenario, wireless device 500 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 wireless device and / or a network node. Wireless device 500 may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, wireless device 500 may implement the 3GPP NB-IoT standard. In other scenarios, wireless device 500 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.

[0055] In practice, any number of wireless devices 500 may be used together with respect to a single use case. For example, a first wireless device 500 might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second wireless device 500 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device 500 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 wireless device 500 can also include more than one of the functionalities described above. For example, wireless device 500 might include the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0056] Figure 6 shows a network node 600 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 telecommunications network. In accordance with respective embodiments, network node 600 may be configured to operate in communication system 300 of Figure 3, like network nodes 308 or 310, or in communication system 400 of Figure 4, like an AP 410 or a station 412. 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).

[0057] Network nodes 600 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. Network node 600 may be a relay node or a relay donor node controlling a relay. Network nodes 600 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).

[0058] Other examples of network nodes 600 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).

[0059] In particular embodiments, network node 600 includes a processing circuitry 602, a memory 604, a communication interface 606, and a power source 608. In general, in a particular embodiment of network node 600, processing circuitry 602, memory 604, communication interface 606, and power source 608 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 600.

[0060] The network node 600 may be composed of multiple distinct network entities (e.g., a NodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 600 includes multiple such entities (e.g., BTS and BSC), one or more of the separate entities 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 600 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 604 or portions of memory 604 for different RATs) and some components may be reused (e.g., a same antenna 610 may be shared by different RATs). The network node 600 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 600, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), 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 600.

[0061] The processing circuitry 602 may include 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 components, such as the memory 604, to provide network node 600 functionality.

[0062] In some embodiments, the processing circuitry 602 includes a system on a chip (SOC). In some embodiments, the processing circuitry 602 includes one or more of radio frequency (RF) transceiver circuitry 612 and baseband processing circuitry 614. In some embodiments, the RF transceiver circuitry 612 and the baseband processing circuitry 614 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 612 and baseband processing circuitry 614 may be on the same chip or set of chips, boards, or units.

[0063] The memory 604 may include 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 computerexecutable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 602. The memory 604 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 602 and utilized by the network node 600. The memory 604 may be used to store any calculations made by the processing circuitry 602 and / or any data received via the communication interface 606. In some embodiments, the processing circuitry 602 and memory 604 is integrated.

[0064] The communication interface 606 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface 606 includes port(s) / terminal(s) 616 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 600 may be capable of wireless communication and communication interface 606 may also include radio front-end circuitry 618 that may be coupled to, or in certain embodiments a part of, an antenna 610. Particular embodiments ofradio front-end circuitry 618 include filter(s) 620 and amplifier(s) 622. The radio front-end circuitry 618 may be connected to an antenna 610 and processing circuitry 602. The radio frontend circuitry may be configured to condition signals communicated between antenna 610 and processing circuitry 602. The radio front-end circuitry 618 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 618 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 620 and / or amplifiers 622. The radio signal(s) may then be transmitted via the antenna 610. Similarly, when receiving data, the antenna 610 may collect radio signals which are then converted into digital data by the radio front-end circuitry 618. The digital data may be passed to the processing circuitry 602. In other embodiments, the communication interface may include different components and / or different combinations of components.

[0065] In certain alternative embodiments, network node 600 may be capable of wireless communication but does not include separate radio front-end circuitry 618, instead, the processing circuitry 602 includes radio front-end circuitry and is connected to the antenna 610. Similarly, in some embodiments, all or some of the RF transceiver circuitry 612 is part of the communication interface 606. In still other embodiments, the communication interface 606 includes one or more ports or terminals 616, the radio front-end circuitry 618, and the RF transceiver circuitry 612, as part of a radio unit (not shown), and the communication interface 606 communicates with the baseband processing circuitry 614, which is part of a digital unit (not shown).

[0066] The antenna 610 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 610 may be coupled to the radio front-end circuitry 618 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 610 is separate from the network node 600 and connectable to the network node 600 through one or more interfaces or ports.

[0067] The antenna 610, communication interface 606, and / or the processing circuitry 602 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the network node 600. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 610, the communication interface 606, and / or the processing circuitry 602 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 600. Any information,data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0068] The power source 608 provides power to the various components of network node 600 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 608 may further include, or be coupled to, power management circuitry to supply the components of the network node 600 with power for performing the functionality described herein. For example, the network node 600 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 608. As a further example, the power source 608 may include 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.

[0069] Embodiments of the network node 600 may include additional components beyond those shown in Figure 6 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 600 may include user interface equipment to allow input of information into the network node 600 and to allow output of information from the network node 600. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 600.

[0070] Figure 7 is a block diagram illustrating a virtualization environment 700 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 700 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host. Further, in embodiments in which a 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 700 includes components defined by the O-RAN Alliance, suchas an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

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

[0072] Hardware 704 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 706 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 708A and VM 708B (which may be collectively referred to as VMs 708), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 706 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 708.

[0073] The VMs 708 include virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 706. Different embodiments of the instance of a virtual appliance 702 may be implemented on one or more of VMs 708, 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.

[0074] In the context of NFV, each of the VMs 708 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 708, and that part of hardware 704 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 of the VMs 708 on top of the hardware 704 and corresponds to an application 702.

[0075] Hardware 704 may be implemented in a standalone network node with generic or specific components. Hardware 704 may implement some functions via virtualization. Alternatively, hardware 704 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 managementand orchestration 710, which, among others, oversees lifecycle management of applications 702. In some embodiments, hardware 704 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 712 which may alternatively be used for communication between hardware nodes and radio units.

[0076] Figure 1 illustrates an example procedure for energy consumption information collection in a wireless network in accordance with some embodiments.

[0077] In some embodiments, EIF 112 retrieves information about the serving AMF 108 and SMFs 106 for a specific UE by querying the Unified Data Management (UDM) 110. Such query may include parameters such as the UE identifier and network slice information (S-NSSAI and Data Network Name).

[0078] In some embodiments, the EIF 112 invokes the Namf_EventExposure_Subscribe service to obtain the gNB ID from the AMF 108.

[0079] In some embodiments, the EIF 112 subsequently invokes the Nsmf_EventExposure_Subscribe service. For example, in certain embodiments, the EIF 112 may invoke the Nsmf_EventExposure_Subscribe service as specified in Technical Specification 23.502. This request includes required granularity parameters such as, for example, UE ID, DNN / S-NSSAI (i.e., network slice information), and application- specific information (i.e., application identifiers or packet filters). This process enables the EIF 112 to retrieve detailed information from the UPF 104, with the specific parameters as further described below in connection with the information provided to the SMF 106.

[0080] In particular, in some embodiments, the information provided from the EIF 112 to the SMF 106 for user-plane energy consumption calculation may include one or more of: a UE identifier (e.g., SUPI); slice and data network name information applicable to a PDU session (e.g., S-NSSAI combined with the DNN); application information (e.g., packet filters or an application identifier); a UPF event identifier indicating an event identifier of the UPF 104 for getting path information and volume information; a path identifier indicator that indicates that 5GC path information is wanted for the measurement; and a default timer identifier indicating that the information reporting interval is the PLMN-wide configurable starting times and interval T.

[0081] In some embodiments, the set of information from SMF 106 to the UPF 104 for user-plane energy consumption may include one or more of: the UE identifier (e.g., SUPI); a UE IP address; slice and data network name information applicable to a PDU session (e.g., S-NSSAI combined with the DNN); application information (e.g., packet filters or an application identifier); a UPF event identifier indicating an event identifier of the UPF 104 for getting volume information; a path identifier indicator that indicates that 5GC path information is wanted; and a default timer identifier indicating that the information reporting interval is the PLMN-wide configurable starting times and interval T.

[0082] The EIF 112 receives the data volume of the required granularities from the PDU Session Anchor (PSA) UPF 104. In some embodiments, the set of information collected from the UPF 104 by the EIF 112 may include one or more of: a UE IP address; a UE identifier (e.g., SUPI); network slice information applicable to a UE (e.g., S-NSSAI); slice and data network name information applicable to a PDU session (e.g., S-NSSAI combined with the DNN); packet filters (e.g., packet filters as in clause 5.7.6 for IP or Ethernet traffic); an application identifier identifying traffic of the service data flow; a list of data volume information representing the data volume and the associated UPF(s) and gNB(s) serving the UE within the time interval; and a reference to a time interval indicating the time interval of the collected information (e.g., one or more time stamps). In some embodiments, the list of data volume information further indicates, for one or more entries: an uplink and / or downlink data volume of a PDU Session identified by a (UE-ID, S-NSSAI / DNN) tuple, or of a service data flow identified by a (UE ID, S-NSSAI, DNN, Packet Filters / Application Identifier) tuple; and one or more (I-)UPF identifiers (e.g., NF identifier(s) of UPF(s) or user plane address(es)) associated with a reported data volume used by a PDU Session identified by UE-ID, S-NSSAI / DNN and, optionally, packet filters or application identifier. In some embodiments, each entry of the list of data volume information represents the serving UPF(s) corresponding to the same data volume regarding the required granularities. In some embodiments, a new entry is added when the UPF(s) changes. In some embodiments, the EIF 112 correlates the gNB ID received from the AMF 108 with the information received from the UPF 104.

[0083] Figure 1 shows the procedure for the EIF 112 to collect the energy consumption information. Initially, the EIF 112 subscribes to the energy consumption per node and total data volume per node from the 0AM 102.

[0084] The Consumer NF 114 (i.e. trusted AF or 5GC NF) subscribes to the energy consumption event with the EIF 112 by using Neif_EventExposure_Subscribe service for therequired granularities (UE, PDU Session and / or QoS flow) 116. For example, in some embodiments this may be done as described in clause 5.51.2.3 of TS 23.501.

[0085] If the Consumer is untrusted AF, the subscription is sent via NEF. If the event subscription is authorized by the NEF, then the NEF sends the event subscription to the EIF 112 via Neif_EventExposure_Subscribe 116.

[0086] The EIF 112 invokes Nudm_UECM_Get 118 service operation to retrieve the SMF IDs and AMF ID for the required granularity.

[0087] The EIF 112 invokes the Namf_EventExposure_Subscribe 120 request to the AMF 108 to request the information of the user location in terms of gNB.

[0088] The EIF 112 invokes the Nsmf_EventExposure_Subscribe 122 request to the SMF 106 to request the information by subscribing the UPF 104 userDataUsage event and requesting volume measurements. For example, in some embodiments this may be done as defined in clause 5.51.2 of TS 23.501. Per Data path reporting is requested. An indication that configurable starting time with interval T should be used for the measurements is also included. Note that the SMF 106 is assumed to provide the data path in the PFCP session when this solution is deployed in the network.

[0089] The SMF 106 invokes the Nupf_EventExposure_Subscribe 124 request to the UPF 104 for User data Usage Measures requesting the PSA UPF 104 to report data volume optionally with an event filter for the target traffic (packet filter or application ID). SMF 106 indicates that Per Data path reporting is requested. The subscription also indicates that configurable starting time with interval T should be used for the measurements.

[0090] In some embodiments, the Nupf_EventExposure_Subscribe service operation is used by an NF to subscribe or modify a subscription to UPF event exposure notifications, e.g., for the purpose of UPF data collection on a specified PDU Session or for all PDU Sessions of one UE or any UE. In some embodiments, the inputs to the Nupf_EventExposure_Subscribe service operation may include one or more of an NF identifier; a target of event reporting (e.g., "any UE" or, when a specific UE is targeted, an identifier of the specific UE); a set of one or more event identifiers; a notification target address (and optionally a notification correlation identifier); and event reporting information. In some embodiments, additional optional inputs to the Nupf_EventExposure_Subscribe service operation may include one or more of: a subscription correlation identifier (e.g., used in the case of modification of the event subscription); an expiry time; a DNN; an S-NSSAI; either one or more application identifiers or traffic filtering information; a type of measurement; a granularity of measurement; reporting suggestion information; a subscription termination reporting indication; a remaining datareporting indication; an IP domain; an IP address of a remote end; a port number of a remote end; an indication of data path in reporting; and an indication that network-wide measurement time and period should be used. In some embodiments, the output of the Nupf_EventExposure_Subscribe service operation, where the subscription is accepted, may include one or more of a subscription correlation identifier and an expiry time. In some embodiments, the output may further optionally include a first corresponding event report (e.g., where available) and / or a notification target address (and optionally a notification correlation identifier) used to correlate notifications sent by the UPF 104 with the subscription.

[0091] The UPF 104 provides the data volume information for energy consumption calculation to EIF 112 by invoking Nupf_EventExposure_Notify 126 service operation for the required granularity. For example, in some embodiments providing the data volume information for energy consumption calculation may be done as described in 5.51.2 of TS 23.501. In order to avoid simultaneous reporting at end of the period causing signaling storms, mechanisms to differ delay tolerant reporting may be used. For example, in certain embodiments the mechanisms specified in 4.15.4.5.1 may be used to differ delay tolerant reporting may be used. The gNB ID information has been obtained by EIF 112 from AMF 108 directly. Note that when the data path changes for an ongoing subscription, SMF 106 updates the PFCP session which triggers UPF 104 to close the measurement report and start a new one. The UPF 104 reporting includes the data path information. Further note that it is left for EIF 112 implementation how the reported data volume is split between gNBs when gNB is changed in the middle of the measurement period.

[0092] The EIF 112 performs the energy consumption information calculation and then reports the energy consumption information of the required granularity to the Consumer NF 114 via Neif_EventExposure_Notify 128. For example, in some embodiments the EIF 112 performs this calculation as described in clause 5.51.2.3 of TS 23.501.

[0093] In some embodiments, an example method 200 performed by an SMF 106 may be carried out as illustrated in Figure 2. In some embodiments, the method 200 may include adding 202, to a UPF 104, during a PFCP session establishment or update, path information including at least one of: one or more UPF identifiers and one or more user plane addresses. In some embodiments, the method 200 may further include receiving 204, from an EIF 112, a subscription request for volume information and path information from the UPF 104. In some embodiments, the method 200 may further include forwarding 206, to the UPF 104, the subscription request. In some embodiments, by virtue of the path information added by the SMF 106, the UPF 104 may establish 208 a direct reporting channel between the UPF 104 andthe EIF 112 and report 210, to the EIF 112, 5G Core (5GC) path information and volume data associated with a PDU session.

[0094] In some embodiments in keeping with the present disclosure, during Connection, Registration and Mobility Management procedures, the AMF 108 may store and update UE access behavior trends and UE location trends. Each metric is updated incrementally, e.g. using exponential moving average. This information is exposed to consumer NFs (e.g. NWDAF) that subscribe for the event ID "UE access behavior trends" and / or "UE location trends", respectively, by invoking Namf_EventExposure_Subscribe.

[0095] In some embodiments, the UE access behavior trends exposed by the AMF 108 may include, for each of a list of state transitions: a UE identity (e.g., SUPI); a state transition type identifier (e.g., "Access Type change to 3GPP access", "Access Type change to non-3GPP access", "RM state change to RM-DEREGISTERED", "RM state change to RM-REGISTERED", "CM state change to CM-IDLE", "CM state change to CM-CONNECTED", "Handover", or "Mobility Registration Update"); a spacing including an average and variance of the time interval separating two consecutive occurrences of the state transition; and a duration including an average and variance of duration in the resulting state.

[0096] In some embodiments, the UE location trends exposed by the AMF 108 may include, for each of a list of one or more location information entries: a UE identity (e.g., SUPI); a UE location (e.g., TAI, Cell-ID where available, gNB ID where applicable, and / or non-3GPP access identity); a spacing including an average and variance of the time interval separating two consecutive arrivals at this location; a duration including an average and variance of duration of stay in the location; and a timestamp including the timestamp of a last arrival in the location. In some embodiments, a maximum size N of the list of location information entries is defined per configuration, and only the N entries with the highest average value of the duration are kept in the list. In some embodiments, the list of location information entries is ordered by descending order of the duration.

[0097] In some embodiments, an example method 800 performed by an AMF 108 may be carried out as illustrated in Figure 8. In some embodiments, the method 800 may include maintaining 802, for one or more UEs, one or more of: a set of UE access behavior trends and a set of UE location trends. In some embodiments, the method 800 may further include, in response to a subscription, exposing 804, to a consumer network function, one or more of: the set of UE access behavior trends and the set of UE location trends.

[0098] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments mayinclude computing devices with different combinations of components. It is to be understood that these computing devices may include 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 include 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.

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

Claims

CLAIMS1. A method (200), performed by a Session Management Function, SMF (106), the method comprising:adding (202), to a User Plane Function, UPF (104), during a Packet Forwarding Control Protocol, PFCP, session establishment or update, path information comprising at least one of: one or more UPF identifiers and one or more user plane addresses.

2. The method of claim 1, further comprising, in response to a change of data path for an ongoing subscription, updating a PFCP session associated with the UPF (104) such that the UPF (104) closes a current measurement report and starts a new measurement report including updated path information.

3. The method of any of claims 1-2, further comprising:receiving (204), from an Energy Information Function, EIF (112), a subscription request for volume information and path information from the UPF (104); and forwarding (206), to the UPF (104), the subscription request, the path information added to the UPF (104) enabling the UPF (104) to establish (208) a direct reporting channel between the UPF (104) and the EIF (112) and to report (210), to the EIF (112), 5G Core, 5GC, path information and volume data associated with a Protocol Data Unit, PDU, session.

4. The method of claim 3, wherein the subscription request received from the EIF (112) comprises an indicator instructing the UPF (104) to include path information in reports sent on the direct reporting channel.

5. The method of any of claims 3-4, wherein the subscription request received from the EIF (112) specifies a clock time and an interval for reporting by the UPF (104).

6. The method of any of claims 3-4, wherein the subscription request received from the EIF (112) comprises an indicator instructing the UPF (104) to report according to a network- wide default starting time and default interval.

7. The method of any of claims 3-6, wherein the subscription request forwarded to the UPF (104) further comprises an event filter, the event filter comprising at least one of: a packet filter and an application identifier.

8. The method of any of claims 1-7, wherein adding (202) the path information to the UPF (104) is performed in response to establishment or modification of the PDU session.

9. The method of any of claims 3-8, wherein the subscription request received from the EIF (112) is associated with one or more granularities, the one or more granularities comprising at least one of: a User Equipment, UE, identifier, network slice information comprising a Single Network Slice Selection Assistance Information, S-NSSAI, and a Data Network Name, DNN, and application-specific information comprising at least one of an application identifier and one or more packet filters.

10. The method of any of claims 3-9, wherein the Energy Information Function, EIF (112), is configured to obtain a gNodeB, gNB, identifier from an Access and Mobility Management Function, AMF (108), and to correlate the gNB identifier with the path information and volume data reported by the UPF (104).

11. A method (800), performed by an Access and Mobility Management Function, AMF (108), the method comprising:maintaining (802), for one or more User Equipments, UEs, one or more of: a set of UE access behavior trends and a set of UE location trends; andin response to a subscription, exposing (804), to a consumer network function, one or more of: the set of UE access behavior trends and the set of UE location trends.

12. The method of claim 11, wherein the set of UE access behavior trends comprises, for each of one or more state transitions, one or more of: an indication of the state transition, a spacing between consecutive occurrences of the state transition, and a duration in a resulting state.

13. The method of any of claims 11-12, wherein the set of UE location trends comprises, for each of one or more locations, one or more of: an indication of the location, a spacing between consecutive arrivals at the location, a duration of stay in the location, and a timestamp of a last arrival in the location.

14. The method of any of claims 11-13, wherein the set of UE access behavior trends, or the set of UE location trends, or both, is maintained using an exponential moving average.

15. The method of any of claims 11-14, wherein the subscription identifies the consumer network function and a Network Data Analytics Function, NWDAF.

16. A network node (600) configured to operate as a Session Management Function, SMF (106), the network node (600) comprising processing circuitry (602) configured to perform operations comprising:adding, to a User Plane Function, UPF (104), during a Packet Forwarding Control Protocol, PFCP, session establishment or update, path information comprising at least one of: one or more UPF identifiers and one or more user plane addresses.

17. The network node of claim 16, wherein the processing circuitry (602) is further configured to perform operations corresponding to any of the operations of any of claims 2-10.

18. A network node (600) configured to operate as a Session Management Function, SMF (106), the network node (600) comprising:processing circuitry (602); andmemory (604) coupled to the processing circuitry (602), the memory (604) storing instructions that, when executed by the processing circuitry (602), cause the network node (600) to add, to a User Plane Function, UPF (104), during a Packet Forwarding Control Protocol, PFCP, session establishment or update, path information comprising at least one of: one or more UPF identifiers and one or more user plane addresses.

19. The network node of claim 18, wherein the memory (604) further stores instructions that, when executed by the processing circuitry (602), cause the network node (600) to perform operations corresponding to any of the operations of any of claims 2-10.

20. A network node (600) configured to operate as an Access and Mobility Management Function, AMF (108), the network node (600) comprising processing circuitry (602) configured to perform operations corresponding to the operations of any of claims 11-15.

21. A computer program comprising instructions which, when executed by processing circuitry (602) of a network node (600), cause the network node (600) to perform the method of any of claims 1-15.

22. A computer program product comprising a computer-readable medium (604) storing a computer program, the computer program comprising instructions which, when executed by processing circuitry (602) of a network node (600), cause the network node (600) to perform the method of any of claims 1-15.

23. A computer-readable medium (604) storing instructions which, when executed by processing circuitry (602) of a network node (600), cause the network node (600) to perform the method of any of claims 1-15.

24. A system for energy consumption reporting in a 5G network, the system comprising a Session Management Function, SMF (106); a User Plane Function, UPF (104); and an Energy Information Function, EIF (112);wherein the SMF (106) is configured to add (202), to the UPF (104), during a Packet Forwarding Control Protocol, PFCP, session establishment or update, path information comprising at least one of: one or more UPF identifiers and one or more user plane addresses; and to forward (206), to the UPF (104), a subscription request received from the EIF (112);wherein, by virtue of the path information added by the SMF (106), the UPF (104) is configured to establish (208) a direct reporting channel between the UPF (104) and the EIF (112), and to report (210), to the EIF (112) over the direct reporting channel and without traversing the SMF (106), 5G Core, 5GC, path information and volume data associated with a Protocol Data Unit, PDU, session.