Network function apparatus and methods

Abstract

Various aspects of the present disclosure relate to a first network entity for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory. The processor is configured to cause the first network entity to: select a second network entity to compensate at least one service for at least one consumer entity; transfer one or more of a network context or a user context to the selected second network entity prior to the first network entity switching to a power OFF state, wherein the network context or a user context supports the at least one service; and switch from a power ON state to the power OFF state in response to one or more of the network context or the user context being transferred to the selected second network entity.

Description

NETWORK FUNCTION APPARATUS AND METHODSTECHNICAL FIELD

[0001] The present disclosure relates to wireless communications, and more specifically to managing and / or controlling energy of network entities in wireless communication systems.BACKGROUND

[0002] A wireless communications system may include one or multiple network communication devices, which may be otherwise known as network equipment (NE), supporting wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like)). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., 5G-advanced (5G-A), sixth generation (6G)).SUMMARY

[0003] As used herein, including in the claims, an article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’ or “one or both of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, including in the claims, the phrase “based on” shall not be Attorney Docket No. PC934859WO15047176-1construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

[0004] Some implementations of the method and apparatuses described herein may further include a first network entity for wireless communication, comprising at least one memory and at least one processor coupled with the at least one memory. The processor is configured to cause the first network entity to: select a second network entity to compensate at least one service for at least one consumer entity; transfer one or more of a network context or a user context to the selected second network entity prior to the first network entity switching to a power OFF state (which may be an energy saving state), wherein the network context or the user context supports the at least one service; and switch from a power ON state to the power OFF state in response to one or more of the network context or the user context being transferred to the selected second network entity.

[0005] The second network entity may be selected based at least in part on information indicating the second network entity supports one or more of the at least one service or a service scope associated with the at least one service.

[0006] The at least one processor may be further configured to cause the first network entity to process pending traffic prior to switching to the power OFF state.

[0007] To process the pending traffic, the at least one processor may be configured to cause the first network entity to perform at least one of: handover the pending traffic to the second network entity, wherein the first network entity is switched from the power ON state to the power OFF state further in response to the handover of the pending traffic to the second network entity; or monitor for completion of the processing of the pending traffic at the first network entity, wherein the first network entity is switched from the power ON state to the power OFF state further in response to the completion of the processing of the pending traffic at the first network entity.Attorney Docket No. PC934859WO15047176-1

[0008] The at least one processor may be configured to cause the first network entity to synchronize a heartbeat timer with a schedule associated with expected powered ON and powered OFF durations of the first network entity.

[0009] The at least one processor may be configured to cause the first network entity to receive feedback information from the second network entity, wherein the feedback information indicates a successful service compensation by the second network entity, wherein the first network entity is switched from the power ON state to the power OFF state further in response to the received feedback information.

[0010] The at least one processor may be configured to cause the first network entity to instruct a third network entity to retain profile context of the first network entity after switching from the power ON state to the power OFF state by including a status that indicates the power OFF state, wherein the third network entity is configured to support discovery and selection of the first network entity including an indication related to a time it can be reactivated. For example, the third network entity may be configured to output timing information that indicates a time the first network entity is available to switch to the power ON state (i.e. to be reactivated).

[0011] The third network entity may be a network repository function.

[0012] The at least one processor may be configured to cause the first network entity to transmit to the third network entity an indication of the power OFF state of the first network entity.

[0013] The at least one processor may be configured to cause the first network entity to reactivate one or more capabilities associated with the at least one service and corresponding to one or more requirements of the consumer entity during the power OFF state of the first network entity.

[0014] The first network entity may be a network function that is configured to be powered OFF to an energy saving state. The second network entity may be a target network function configured to compensate the operation of the first network entity.Attorney Docket No. PC934859WO15047176-1

[0015] In examples, two subsets of context information can be considered: firstly, NF context, which may for example be termed network function profile context, which is maintained in the third network entity (e.g. network repository function) for discovery (this context characterize the services offered by the NF providing accessibility information). Secondly, network and / or user context that is to be transferred to the second network entity for service compensation (this service is related to user or session related data when using a service in an NF). Examples of network and user context include, for access and mobility function (AMF): UE location, SUPI, PDU session info, etc. For session management function (SMF), network and user context may include: PDU session ID, SUPI, QoS flow info, select UPFs, etc.

[0016] Implementations of the present disclosure provide a first network entity for wireless communication, comprising at least one memory; and at least one processor coupled with the at least one memory. The at least one processor is configured to cause the first network entity to: select a second network entity to compensate at least one service for at least one consumer entity, and to at least one of: process pending traffic prior to switching to a power OFF state; synchronize a heartbeat timer with a schedule associated with expected powered ON and powered OFF durations of the first network entity; and receive feedback information from the second network entity, wherein the feedback information indicates a successful service compensation by the second network entity, wherein the first network entity is switched from the power ON state to the power OFF state further in response to the received feedback information.

[0017] To process the pending traffic, the at least one processor may be configured to cause the first network entity to perform at least one of: handover the pending traffic to the second network entity, wherein the first network entity is switched from the power ON state to the power OFF state further in response to the handover of the pending traffic to the second network entity; or monitor for completion of the processing of the pending traffic at the first network entity, wherein the first network entity is switched from the power ON state to the power OFF state further in response to the completion of the processing of the pending traffic at the first network entity.Attorney Docket No. PC934859WO15047176-1

[0018] The power OFF state may be at least one of: a state in which the first network entity remains powered on with a reduced power level to maintain the one or more of the network context and user context; a state in which the first network entity is configured to process ongoing service requests and to be unable to be selected to support further consumer requests; a state in which the first network entity is operable to return to full operational status following expiry of the power OFF state; and a powered off state.

[0019] The expiry of the power OFF state may be based on a time period associated with an energy saving schedule.

[0020] The at least one processor may be configured to cause the first network entity to: store the at least one of network context and user context into a data repository entity; and provide to the second network entity a context identity to be able to retrieve and use the at least one of network context and user context.

[0021] The at least one processor may be configured to determine that the first network entity can be switched to the power OFF state based on at least one of: a service scope of the first network entity; a geographical coverage area of the first network entity; whether the first network entity performs an aggregated role by serving one or more other network entities; and whether the first network entity supports one or more functionalities not available in at least one other network function of a same type.

[0022] Implementations of the present disclosure provide a second network entity for wireless communication, comprising at least one memory; and at least one processor coupled with the at least one memory. The at least one processor is configured to cause the second network entity to: receive at least one of a network context and a user context from a first network entity according to any preceding claim; and provide service compensation for the first network entity.

[0023] The at least one processor may be configured to cause the second network entity to adjust an associated profile to facilitate discovery, based on one or more of: a scope of services being compensated, one or more service features, a service priority, and one or more expected load conditions.Attorney Docket No. PC934859WO15047176-1

[0024] The at least one processor may be configured to cause the second network entity to perform service compensation in response to at least one of an authentication and authorization process from the first network entity to act on its behalf.

[0025] The at least one processor may be configured to cause the second network entity to signal successful configuration of the service compensation, to the first network entity, prior to the first network entity being switched to the power OFF state.

[0026] Implementations of the present disclosure provide a method, performed by a first network entity in a telecommunications network, the method comprising: selecting a second network entity to compensate at least one service for at least one consumer entity; transferring one or more of a network context or a user context to the selected second network entity prior to the first network entity switching to a power OFF state, wherein the network context or a user context supports the at least one service; and switching from a power ON state to the power OFF state in response to one or more of the network context or the user context being transferred to the selected second network entity.BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.

[0028] Figure 2 illustrates an architecture according to an example.

[0029] Figures 3a and 3b illustrate energy cost of a NF according to an example and a comparative example.

[0030] Figure 4 depicts a method according to an example.

[0031] Figure 5 depicts a communication flow according to an example.

[0032] Figure 6 illustrates an example of a network equipment (NE) in accordance with aspects of the present disclosure.

[0033] Figure 7 illustrate a flowchart of a method performed by a NE in accordance with aspects of the present disclosure.Attorney Docket No. PC934859WO15047176-1DETAILED DESCRIPTION

[0034] Some wireless communication systems may support a service-based architecture (SB A). The SBA may be based on a consumer-producer model in which network entities (e.g., network functions (NFs)) may be configured to select, request, and receive (e.g., obtain) a service, and additionally or alternatively may be configured to provide a service in response to a condition or event (e.g. when the NF load surpasses a threshold, or when a UE starts moving). Each network entity (e.g., NF) may be registered with a repository (e.g., a network repository function (NRF)). The NRF may be configured to assist other network entities (e.g., NFs) in identifying and selecting a service provided by another NF.

[0035] The present disclosure relates to methods, apparatuses, and systems for compensating NF and / or NF services when an NF is powered OFF, thereby enabling service continuity without disruption. Additionally, the present disclosure relates to methods, apparatuses, and systems addressing the problem of maintaining a profile of a power ed-OFF NF within the repository (e.g., the NRF), such that a consumer NF may select the power-OFF NF when needed, considering the availability conditions (for example a time needed until the NF becomes fully operational) and respective cost (for example in terms of required resources).

[0036] NF and / or NF service compensation may be achieved when an NF is in an energy saving state (e.g., power-OFF state) by transferring network context information and / or user context information to another NF that is related from a geographical and operational perspective. Additionally, or alternatively, in some examples, the present disclosure relates to methods, apparatuses, and systems for avoiding service disruptions by enabling smooth context transfer and corresponding registration adjustments in the NRF for the NFs involved, considering both conventional and stateless SBA paradigms. A powered-OFF NF may remain visible in the NRF, thereby allowing consumer NFs to discover and select it, subject to certain limitations associated with its availability conditions.

[0037] In some wireless communication systems, no mechanism exists for providing service compensation when an NF is powered OFF. Similarly, such wireless communication systems do not allow the selection of a powered-OFF NF based on its availability conditions. By contrast, the present disclosure relates to methods, apparatuses, Attorney Docket No. PC934859WO15047176-1and systems that enable handling the power-OFF NF state, including maintaining network context and / or user context through modifications and / or enhancements to NF status within the NF profile.

[0038] Aspects of the present disclosure are described in the context of a wireless communications system. Aspects of the present disclosure are further set forth in the accompanying drawings and the description below. The description set forth herein, in connection with the accompanying drawings, describes example implementations and does not represent all the implementations that may be implemented or that are within the scope of the claims. The detailed description includes specific details for the purpose of providing an understanding of the described implementations. These implementations, however, may be practiced without these specific details. Additionally, the description set forth herein, in connection with the accompanying drawings is provided to enable a person having ordinary skill in the art to make or use the present disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and implementations described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

[0039] Figure 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more NE 102, one or more UE 104, and a core network (CN) 106. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE- Advanced (LIE- A) network. In some other implementations, the wireless communications system 100 may be a NR network, such as a 5G network, a 5G- Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 may support radioAttorney Docket No. PC934859WO15047176-1access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.

[0040] The one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a network function, a network entity, a radio access network (RAN), a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, an NE 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.

[0041] An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example, an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.

[0042] The one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (loT) device, an Internet-of-Everything (loE) device, or machine-type communication (MTC) device, among other examples.Attorney Docket No. PC934859WO15047176-1

[0043] A UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

[0044] An NE 102 may support communications with the CN 106, or with another NE 102, or both. For example, an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., SI, N2, N2, or network interface). In some implementations, the NE 102 may communicate with each other directly. In some other implementations, the NE 102 may communicate with each other or indirectly (e.g., via the CN 106. In some implementations, one or more NE 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs).

[0045] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.

[0046] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an SI, N2, N2, or another network interface). The packet data network may include an application server. In some implementations, one or more UEs 104Attorney Docket No. PC934859WO15047176-1may communicate with the application server. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102. The CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106).

[0047] In the wireless communications system 100, the NEs 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, the NEs 102 and the UEs 104 may support different resource structures. For example, the NEs 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the NEs 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5 G and among other suitable radio access technologies, the NEs 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures). The NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies.

[0048] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., / r=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., / r=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., / r=l) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., / r=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., / r=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., / r=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0049] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, forAttorney Docket No. PC934859WO15047176-1example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0050] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., / r=0, jU=l , / r=2, jU=3, / r=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., / r=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0051] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. InAttorney Docket No. PC934859WO15047176-1some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data). In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

[0052] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., / r=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., / r=l), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., / r=2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., / r=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., / r=3), which includes 120 kHz subcarrier spacing.

[0053] Figure 2 illustrates an example of a system architecture in accordance with aspects of the present disclosure. Communication is shown between a NF service producer 205, NRF 210 and NF service consumer (which may for example be termed a consumer entity) 215. This communication allows for the NRF 210 to assist the NF service consumer 215 to identify and select a service from the NF service producer 205.

[0054] Each NF service producer 205 initially registers its available services when activated in the NRF 215 (step 1 in Figure 2). An NF consumer 210 may discover a service (step 2 in Figure 1) when needed by issuing a query to the NRF 215, which responds with the available service(s) that match the desired requirements and the corresponding NF address(es). The NF consumer 215 selects an NF producer 205 that matches best its requirements from the ones provided by the NRF 215 and issues a service request to receive a service response (step 3 in Figure 1).

[0055] The NF discovery process is based on at least one of: NF capabilities, i.e., offered NF services (for example offered services or functionalities for use by consumer entities), NF allocated priority relative to other NFs of the same type, NF static capacity and NF dynamic load information, NF serving scope (geographical operation scope of a NF), locality related to the location of the NF (geographic location, data center, etc.), NF slice related information (single network slice selection assistance information (S -NS SAI), Attorney Docket No. PC934859WO15047176-1network slice instance (NSI)), NF access permissions (e.g., type of NF(s) or public land mobile networks (PLMNs) identity allowed to access), NF vendor specific information, and NF serving scope (geographical operation scope of a NF).

[0056] Each NF maintains an NF status in the NRF, which can take values as set out in 3GPP TS 29.510.

[0057] A change of the NF Status value can be notified as a "NF PROFILE CHANGED" event, which may also include the a"NF DEREGISTERED" event that notifies subscribed NF(s) that an NF is no longer available. An NF that is no longer available is powered OFF, which may for example be not because of energy saving but for other operational issues.

[0058] In comparative examples, energy related information may be considered in the NF discovery and selection process as set out in 3 GPP TR 23.700-67 by enhancing the NF profile in the NRF. This information may include an indication of an energy saving state, an energy saving schedule, i.e., the time when an NF is scheduled to be powered OFF and be powered on again, an energy priority parameter that provides information related to the priority in selecting an NF with respect to a combination of energy metrics, e.g., energy cost and energy efficiency and an indication related to the usage of renewable energy information. Energy priority can be configured by the operator so the way that the individual metrics are combined is based on the operator policy.

[0059] In TR 23.700-66 more energy metrics are considered including the energy cost, the energy efficiency and the carbon footprint related to an NF. In comparative methods, the focus for NF discovery and selection considering energy related metric concentrates on the user plane considering only the user plane function (UPF).

[0060] However, in comparative systems there is no process that would allow any NF in the mobile core network to be powered OFF, not only UPFs, whilst allowing handling of ongoing traffic. There is no process that deals with what happens to the network and / or user context when powered OFF or how an NF profile context shall appear in the NRF to let other NFs know that it can potentially be back in the NF status REGISTERED when needed. Also, there is no process that would allow an NF in the control plane toAttorney Docket No. PC934859WO15047176-1compensate for another NF of the same type. Finally, there is no process that would allow an NF to discover and select an NF that is powered OFF having knowledge of the respective cost, e.g., additional energy cost, and the time that is needed for a powered OFF NF to be fully operational, i.e., in NF status REGISTERED.

[0061] The following definitions relating to energy saving states may be used, with reference to clause 3 of 3GPP TS 28.310: “energySaving” state in which some functions of a cell or network function are powered down; “notEnergySaving” state when no energy saving in progress; and “compensatingForEnergySaving” state in an off-peak traffic situation, a network element is remaining powered on, e.g., taking over the coverage areas of a neighbour base station in the “energySaving” state.

[0062] In the energy saving state, the cell or network function is still controllable (i.e., from a management function).

[0063] The present disclosure provides a method for managing (which may refer to e.g. controlling) to power OFF and reactivate (i.e. power ON) an NF within a mobile core network. The method comprises procedures for: (i) powering-off of a selected NF and handling its associated context information; (ii) transferring the context information to another NF instance to re-use, enabling operational continuity and service compensation; and (iii) managing the corresponding NF registration and status entries within the NRF. Examples utilize a Service-Based Interface (SBI) architecture, and others use a stateless SBA model.

[0064] In the process of selecting an NF to be powered OFF or taken out of service for energy-saving purposes, additional criteria beyond conventional considerations such as network and / or user related context, or network load may be taken into account. Network and / or user context refers any stateful data the NF holds related to UEs, sessions, or other operations. Examples of network and / or user context may include for i) AMF, UE registration or NAS context, ii) SMF PDU session state, QoS rules, UPF forwarding rules, PCF policy rules, UDM subscription data for UEs.

[0065] Other criteria for selecting an NF to be powered OFF may include at least one of the NF’s service scope or geographical coverage area, i.e., whether the NF performs anAttorney Docket No. PC934859WO15047176-1aggregated role by serving multiple other NFs, or whether it supports specialized functionalities not available in other NFs of the same type, such as features dedicated to premium users or specific services. This information can be considered by the OAM when taking the decision to save energy for a specific NF.

[0066] Figures 3a and 3b illustrate use of an UNDIS COVERABLE NF status as per 3GPP TS 29.510, compared to a modified version of the UNDIS COVERABLE NF status that can follow the energy saving time schedule. Both of these figures depict change of NF energy cost with time.

[0067] With reference to Figure 3a, an NF may remain powered on with an UNDIS COVERABLE NF status as specified in TS 29.510 having the capability to process ongoing traffic to avoid service disruption. In this way the NF can maintain its network and / or user context as well as its profile context in the NRF, while at the same time it can save energy by limiting the usage of computing resources with respect to packet processing. The UNDIS COVERABLE NF status is a temporary status, which is controlled by a shutdown time. The shutdown time indicates the time window before the NF status is updated to powered OFF.

[0068] In this comparative example, a power ed-OFF NF may lose its network and / or user related context. It also needs to deregister from NRF, with the NRF notifying all subscribed NFs about the NF DEREGISTERED status update. A powered-OFF NF avoids spending a fixed amount of energy just to maintain basic network and / or user context and operations powered on as in UNDISCOVERABLE NF status, but it increases the latency of re-powering on an NF. Once an NF is re-powered on, i.e., with NF status REGISTERED, it needs to re-register and re-establish its network and / or user context as well as its profile context in NRF from scratch. To achieve this, it consumes network resources, e.g., due to signaling related to UE re-registrations, and it is prone to errors, e.g., when resetting a policy or handling charging operations.

[0069] In an approach according to the present disclosure, the NF status can remain UNDISCOVERABLE if the shutdown timer follows the energy saving time schedule as illustrated in Figure 2b. In this example, the NF consumes limited energy when in the energy saving status, but then when time elapses instead of being powered OFF the NF Attorney Docket No. PC934859WO15047176-1updates its status to REGISTERED. To achieve this a new parameter can be introduced when the UNDISCOVERABLE NF status is selected. This parameter can be an energy related flag to indicate if the UNDISCOVERABLE NF status shall remain, or be updated into REGISTERED once the shutdown timer elapses. However, in this case a fixed amount of energy is supplied to maintain the minimum NF functionality powered on handling no traffic. This fixed amount of energy, which is implementation specific, i.e., depends on the computing facilities and how an NF is realized, e.g., as virtualized NF using a container or virtual machine or alternatively as a physical NF. A similar solution, according to the present disclosure, could be achieved by introducing an ENERGY_SAVING NF status, which allows the NF to continue processing ongoing traffic to prevent service disruption before partially powering OFF. In this state, the NF maintains a minimal power level to preserve network and / or user context, as well as its profile information in the NRF. In this case the ENERGY SAVING NF status can be updated into REGISTERED once the shutdown timer elapses without the need of an energy related flag

[0070] An alternative solution, according to the present disclosure, is to conserve the NF / NF service context of an NF either by compressing and storing it locally or transferring it to another NF for storage and / or for further usage. The NF / NF service context refers to network and / or user related context associated with a NF. These two terms may be used interchangeably in this disclosure. When the NF / NF service context is maintained, it is beneficial to keep the NF entry in the NRF, since the NF profile context in NRF can be reused or partially updated. Storing NF / NF service context locally there is the benefit of reusing it when the NF is re-powered on, but in the meantime the same context is actively needed if traffic is shifted in another NF and that NF / NF service context it may also evolve depending on usage. On the other hand, storing locally charging context can be useful for completing charging records.

[0071] Bigger benefits can be realized when NF / NF service context is stored outside an NF and especially when it can be used directly by another NF, which takes over to compensate for a powered OFF NF of the same type, e.g., an AMF or SMF. NF / NF service context transfer towards another NF of the same type can assist in, e.g., transferring ongoing session or UE connectivity whilst being transparent to the mobile user.Attorney Docket No. PC934859WO15047176-1

[0072] In a conventional SB A, when an NF is powered OFF or taken out of service, its context can be transferred to another NF to ensure service continuity, while remaining transparent to the end user. The selection of the target NF for NF / NF service context transfer can be carried out either by the NF that is about to be powered OFF by querying the NRF or by the 0AM, in conjunction with the decision to power OFF a specific NF, considering the relationships between the involved NFs. The selection of the target NF for context transfer may take load balancing into account, aiming to avoid overloading the receiving NF. Analytics, e.g., “Analytics ID = NF load” as per 3GPP TS 23.288, can also be used to predict the NF's load over the expected duration related with this context transfer.

[0073] In certain cases, a hierarchical relation may exist, wherein an NF lower in hierarchy can transfer, i.e., push, the NF / NF service context via SB A Interfaces to an NF higher in the hierarchy, e.g., that has an NF aggregation role. In some other cases, a NF may transfer its NF / NF service context to another NF that operates within a neighbouring serving scope. When this happens, the receiving NF may be required to update its serving scope in the NRF to inform NF consumers that it is now capable of serving a broader scope as well as update its load indication considering the received context.

[0074] In addition, the receiving target NF may be required to update information related to access and authorization, i.e., which NFs are allowed to consume selected services, to assure that the accessibility is maintained for the services offered by the original NF, or alternatively that the target NF is selected considering compatibility in the access and authorization. The target NF may also need to adapt the prioritization related to the obtained the new services or in relation with a certain usage, e.g., UEs or slice or DNN.

[0075] A different solution, according to the present disclosure, can be realized considering a stateless SB A, in where an NF does not maintain locally NF / NF service context information but instead the NF / NF service context is stored in another repository, e.g., the Context Storage Repository Function (CSRF). In this case when an NF is powered OFF it needs to pass the identifier or ID of the NF / NF service context to the NF that takes over. The identifier of the NF / NF service context may contain a timestamp and a version to be able to distinguish different versions as well as the last NF or a list of NFs that have usedAttorney Docket No. PC934859WO15047176-1it or modified it. The target NF can also be based on the criteria discussed for the case of the conventional SB A, but instead of transferring the NF / NF service context between the involved NFs, it will obtain, i.e., pull, it from the CSRF.

[0076] A related issue when powering OFF an NF is how to deal with the NF entry in the NRF. An approach according to comparative examples is to allow an NF that is powered OFF to deregister from the NRF. Alternatively, an NF may appear in the NRF with an UNDISCOVERABLE NF status as elaborated above. This means that while its context information is present in the NRF, other NFs cannot discover or select it for using it. The NF status UNDISCOVERABLE is temporary but can be used to represent a powered OFF state under certain conditions and modifications as discussed above.

[0077] Another option is to adopt the SUSPENDED NF status to represent a powered-OFF NF. This status is non-temporary but may trigger NF recovery procedures as it typically indicates failures, e.g., a heartbeat failure. To avoid triggering recovery procedures a new parameter, e.g., an energy related flag, can be introduced when SUSPENDED NF status is selected, to indicate that the NF is SUSPENDED for energy saving purposes.

[0078] Alternatively, when maintaining an NF entry in the NRF, there may be a requirement to indicate that such an NF is on energy saving state. To achieve this a new NF status can be introduced related to energy saving, i.e., ENERGY SAVING NF status. An NF with an ENERGY SAVING NF status can then appear in the NRF to indicate that an NF is powered OFF to save energy but can potentially be re-powered on again. An NF with an ENERGY SAVING NF status may also include a time schedule indicating when it is expected to be powered back on and how long the reactivation will take.

[0079] An NF can maintain its registration in the NRF by regularly exchanging heartbeat (i.e., keep-alive) messages. When the NF is powered OFF and deregistered from the NRF, heartbeat messages may be deemed to no longer be needed. An NF powered on with an undiscoverable NF status that handles limited traffic may still exchange keep-alive messages regularly but with a time window equal to the scheduled re-empower time (i.e., the time that it will be powered back with a REGISTERED NF status). Otherwise, the NRF can deregister the NF entry.Attorney Docket No. PC934859WO15047176-1

[0080] An NF with an ENERGY SAVING NF status may be considered powered OFF but may still need to maintain its profile context in the NRF. In this case, keep-alive messages can be adjusted to align with the time schedule indicating when the NF is expected to power back on. If the NRF is informed of this schedule through heartbeat messages, it can retain the NF’s entry without requiring regular message exchanges.

[0081] In a stateless SB A, an NF can be powered OFF more easily, since its context is stored in a separate repository, e.g., the CSRF. The NF's entry can remain registered in the NRF with an ENERGY SAVING NF status, allowing it to be powered back on with minimal delay when needed. This status can also include a time schedule indicating the expected to be powered back on and the duration required for the NF to be reactivated, i.e. become fully operational.

[0082] When an NF is re-powered on it can then retrieve the latest NF / NF service context from the respective acting NF that compensates in terms of the offered services or from the user data context NF in case of stateless SB A.

[0083] Some specific procedures according to the present disclosure will now be described.

[0084] Figure 4 depicts a method for powering OFF an NF in the mobile core network according to an example of the present disclosure. The steps of the method may be performed in the order shown, or in another order. Certain steps may be omitted, or new steps may be added.

[0085] At 405, the 0AM selects the NF in the mobile core to be powered OFF and notifies it accordingly. The specific method for powering OFF the NF can vary (as mentioned above), but in this example the powering OFF process is be controlled by the NF itself, as it is responsible for handling ongoing traffic and ensuring service continuity.

[0086] At 410, once notified by the 0 AM that it will be powered OFF, the NF shall ensure that it can no longer be selected and used by other consumer NFs or AFs within the mobile core network. To achieve this while handling ongoing traffic, the NF updates its status in the NRF to UNDISCOVERABLE. The NF with an UNDIS COVERABLE NF status can manage ongoing sessions either by offloading traffic, triggering a network Attorney Docket No. PC934859WO15047176-1handover to enforce a change in serving NF, or by waiting for the session to be finalized, especially in case where a session duration is deterministic and known to the NF.

[0087] The 0AM may provide to the NF a shut down time to indicate by when the UNDIS COVERABLE NF status that is temporary needs to be updated. In other words, the shut down time indicates to the NF the time window by which it needs to handle the ongoing traffic.

[0088] At 415, the NF adjusts the heartbeat time according to the schedule that is expected to be powered OFF. By ensuring that the heartbeat time and the powered OFF schedule are aligned, i.e., adopt the same time window, the powered OFF NF can be prevented from experience a heartbeat failure since the next keep alive message is scheduled when the NF is re-powered back again.

[0089] At 420, the NF packages the contained NF / NF service context information to transfer it towards the respect NF, i.e., either a target NF that compensates its services or a context repository, i.e., CSRF, in a stateless SB A from where a target NF can obtain that NF / NF service context information.

[0090] The NF that is about to be powered OFF can either select the target NF to transfer its NF / NF service context information or if the NF / NF service context is stored in a separate context repository, e.g., CSRF, update such context associated with a reference ID instead. Alternatively, the 0AM can select the target NF and notify either one or both involved NFs accordingly. The selected target NF updates its NF profile in the NRF to reflect changes in the service scope, accessibility, load, and prioritization in accordance with the new services, which compensate for the powered OFF NF.

[0091] At 425, the NF designated for power-OFF updates its NF profile status to remain visible in the NRF. This can be achieved by adopting one of the following NF statuses including ENERGY SAVING, a modified UNDISCOVERABLE status, or a modified SUSPENDED status. Additionally, the NF shall include the scheduled power-OFF time along with the anticipated reactivation time including also the expected cost.

[0092] In certain cases, a reactivated NF depending on the timing and conditions of its reactivation, e.g., if reactivated to support a special service during an ongoing energy - Attomey Docket No. PC934859WO15047176-1saving period, may only enable a subset of its full-service capabilities to provide the desired support. For instance, a consumer request may target a specific service, or a specific subarea within the original serving scope, or may require a specified level computing, which may be communicated through a complexity indicator or implicitly associated with a specific feature, task, or requested service.

[0093] The NF can then be powered OFF in accordance with the selected procedure.

[0094] Figure 5 depicts a communication flow according to an example of respective procedures for adjusting the NF profile in the NRF for both the powered-OFF NF and the target NF. Communication is shown between a powered-OFF NF 505, a target NF 510, a context storage repository function 515, and a NRF 520, for example as described above. The steps may be performed in the order shown, or alternatively one or more steps may be performed in a different order. One or more of the depicted steps may be omitted, and / or one or more steps may be added.

[0095] At 1, the 0AM determines to power OFF a specific NF 505 based on network load conditions and operator defined polices and indicates this decision to the selected NF 505.

[0096] In addition, the 0 AM may designate a target NF 510 being responsible to compensate the services of the NF 505 that was selected to be powered OFF and communicate this to that target NF 510.

[0097] At 2a, the NF 505 designated to be powered OFF sends a PATCH request to the resource URI representing the NF Instance in the NRF 520. The payload body of the PATCH request contains the list of operations (i.e., add / delete / replace operations) to be applied to the NF Profile of the NF Instance; these operations may be directed to individual parameters related to the NF status, i.e., replace NF status = REGISTERED with UNDIS COVERABLE, as well as adding a new relevant parameters referred to as powered OFF time schedule = “value indicated by 0AM’ (considering the NF expected powered OFF and repowered on times). In order to leave the NF Profile in a consistent state, all the operations specified by the PATCH request body shall be executed atomically.Attorney Docket No. PC934859WO15047176-1

[0098] At 2b, on success, if the update operation is accepted by the NRF, "204 No Content" should be returned; the NRF may instead return "200 OK" with the payload body of the PATCH response containing the representation of the replaced resource following the operations specified in 3GPP TS 29.510. On failure the NRF 520 can provide the problem details.

[0099] At 3, the NF 505 designated to be powered OFF packages the contained NF / NF service context information or respective updates and context ID, and performs the transfer before it enters an ENERGY SAVING NF status using the procedure as per clause 4.26 TS 23.502. Two different options may be used to achieve this, one based on a push and another on a pull procedure.

[0100] Option 1 : In the push procedure, at 3a the NF 505 designated to be powered OFF exchanges authorization and synchronization information. Then, at 3b, the NF 505 transfers or sends NF / NF service context to the target NF 510 acting as NF Service producer relying on the conventional SBA paradigm. The target NF 510 as a service consumer receives the context and provides a response indicating a successful or not successful (e.g., due to authorization failure) operation.

[0101] Option 2: In the pull procedure, the NF / NF service context is maintained in the Context Storage Repository Function (CSRF) 515 following the stateless SBA paradigm. At 3a’, the NF 505 designated to be powered OFF transfers or sends the respective context updates to the CSRF 515. At 3b’ the NF 505 triggers the target NF 510 to retrieve the respective context providing also optionally the context ID, authentication and access information to assist the context retrieval from the CSRF 515. At 3c’ the target NF 510 as an NF Service Consumer then obtains or pulls the NF / NF service context from CSRF.

[0102] When all procedures have been executed successfully the target NF 510 can continue to serve the original NF Service Consumers, allowing the NF 505 to be powered OFF.

[0103] The target NF 510 in a stateless SBA can also provide further NF / NF service context updates directly to CSRF 515. Hence, when the powered OFF NF 505 re-powers on with a REGISTERED NF status it can retrieve an up-to-date version of the respectiveAttorney Docket No. PC934859WO15047176-1NF / NF Service context information, by using the context ID from CSRF 515 or directly from the target NF 510.

[0104] At 4, upon receiving the NF / NF service context from the NF 505 designated to be powered OFF, the target NF 510 updates its NF profile in the NRF 520 accordingly. To achieve this, at 4a it sends a PATCH request to the resource URI representing the NF Instance in the NRF 520. The payload body of the PATCH request contains the list of operations (e.g., add or replace) to be applied to the NF Profile of the NF Instance; these operations may target individual parameters including adjustments to the serving scope, access information related to specific services previously offered by the NF designated to be powered OFF and the corresponding service priorities.

[0105] At 4b, on success, if the update operation is accepted by the NRF 520, "204 No Content" is returned; the NRF 520 may instead return "200 OK" with the payload body of the PATCH response containing the representation of the replaced resource following the operations specified in TS 29.510. On failure the NRF 520 can provide the problem details.

[0106] At 5a. the target NF 510 may then notify the NF 505 designated for power-OFF that service compensation has been successfully completed, and that it may proceed with the power-OFF operation without impacting service continuity.

[0107] At 5b, the NF 505 designated for power-OFF updates its NF profile in the NRF 520 accordingly. To achieve this, it sends a PATCH request to the resource URI representing the NF Instance in the NRF 520. Three different variations may exist for powering OFF the NF 505 (as already mentioned) wherein the payload body of the PATCH request may contain one or more of:a replace operation be applied to the NF Profile of the NF Instance targeting the individual parameter NF status, i.e., replace NF status =UNDISCO VERABLE with ENERGY SAVING.an add operation be applied to the NF Profile of the NF Instance targeting the individual parameter NF status, e.g., keep NF status =UNDIS COVERABLE and add a positive energy related flag = 1.Attorney Docket No. PC934859WO15047176-1an add and replace operations be applied to the NF Profile of the NF Instance targeting the individual parameter NF status, e.g., replace NF status = UNDISCOVERABLE with SUSPENDED and add a positive energy related flag = 1.An alternative variation can be to adopt the ENERGY SAVING NF status directly instead of UNDISCOVERABLE with the condition that it can continue processing ongoing traffic to prevent service disruption before partially powering OFF at 2a.

[0108] In addition, a new associated parameter referred to as re-empower time may be implemented to indicate the time required for an NF 505 to be repowered and become fully operational with a REGISTERED NF status. This parameter may assist potential consumers in evaluating and selecting an NF even when powered OFF by providing an estimate of the time needed for it to become fully available.

[0109] At 5c, on success, "204 No Content" should be returned; the NRF 520 may instead return "200 OK" with the payload body of the PATCH response containing the representation of the replaced resource following the operations specified in TS 29.510. On failure the NRF 520 can provide the problem details.

[0110] At 5d, once the NF 505 receives a confirmation that the power-OFF preparation process was successfully completed, it can switch into an energy saving state if applicable, i.e., when the NF status becomes ENERGY SAVING or SUSPENDED. Alternatively, the NF may notify the 0AM, which can then initiate the transition to the energy-saving state in accordance with the predefined power-OFF schedule. It should be noted that this step may be omitted if the NF status is set to UNDISCOVERABLE.

[0111] The method thus provides an effective way for allowing a NF 505 to be powered down and compensated by a target NF 510.

[0112] Figure 6 illustrates an example of a NE 600 in accordance with aspects of the present disclosure. The NE 600 may include a processor 602, a memory 604, a controller 606, and a transceiver 608. The processor 602, the memory 604, the controller 606, or the transceiver 608, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described Attorney Docket No. PC934859WO15047176-1herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0113] The processor 602, the memory 604, the controller 606, or the transceiver 608, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0114] The processor 602 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 602 may be configured to operate the memory 604. In some other implementations, the memory 604 may be integrated into the processor 602. The processor 602 may be configured to execute computer-readable instructions stored in the memory 604 to cause the NE 600 to perform various functions of the present disclosure.

[0115] The memory 604 may include volatile or non-volatile memory. The memory 604 may store computer-readable, computer-executable code including instructions when executed by the processor 602 cause the NE 600 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 604 or another type of memory. Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0116] In some implementations, the processor 602 and the memory 604 coupled with the processor 602 may be configured to cause the NE 600 to perform one or more of the functions described herein (e.g., executing, by the processor 602, instructions stored in the memory 604). For example, the processor 602 may support wireless communication at the NE 600 in accordance with examples as disclosed herein. The NE 600 may be configured to implement a source and / or target NF as described elsewhere herein.Attorney Docket No. PC934859WO15047176-1

[0117] The controller 606 may manage input and output signals for the NE 600. The controller 606 may also manage peripherals not integrated into the NE 600. In some implementations, the controller 606 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 606 may be implemented as part of the processor 602.

[0118] In some implementations, the NE 600 may include at least one transceiver 608. In some other implementations, the NE 600 may have more than one transceiver 608. The transceiver 608 may represent a wireless transceiver. The transceiver 608 may include one or more receiver chains 610, one or more transmitter chains 612, or a combination thereof.

[0119] A receiver chain 610 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 610 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 610 may include at least one amplifier (e.g., a low-noise amplifier (LN A)) configured to amplify the received signal. The receiver chain 610 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 610 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0120] A transmitter chain 612 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 612 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 612 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 612 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0121] Figure 7 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a NE as described Attorney Docket No. PC934859WO15047176-1herein, for example an NE implementing a NF as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.

[0122] It will be understood that the method described herein describes A possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0123] At 705, the NE selects a second network entity to compensate at least one service for at least one consumer entity.

[0124] At 710 the NE transfers one or more of a network context or a user context to the selected second network entity prior to the first network entity switching to a power OFF state, wherein the network context or a user context supports the at least one service.

[0125] At 715 the NE switches from a power ON state to the power OFF state in response to one or more of the network context or the user context being transferred to the selected second network entity..

[0126] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.Attorney Docket No. PC934859WO15047176-1

Claims

29CLAIMSWhat is claimed is:

1. A first network entity for wireless communication, comprising:at least one memory; andat least one processor coupled with the at least one memory and configured to cause the first network entity to:select a second network entity to compensate at least one service for at least one consumer entity;transfer one or more of a network context or a user context to the selected second network entity prior to the first network entity switching to a power OFF state, wherein the network context or the user context supports the at least one service; andswitch from a power ON state to the power OFF state in response to one or more of the network context or the user context being transferred to the selected second network entity.

2. The first network entity of claim 1 , wherein the second network entity is selected based at least in part on information indicating the second network entity supports one or more of the at least one service or a service scope associated with the at least one service.

3. The first network entity of any preceding claim, wherein the at least one processor is further configured to cause the first network entity to:process pending traffic prior to switching to the power OFF state.

4. The first network entity of claim 3, wherein, to process the pending traffic, the at least one processor is configured to cause the first network entity to:handover the pending traffic to the second network entity, wherein the first network entity is switched from the power ON state to the power OFF state further in response to the handover of the pending traffic to the second network entity; orAttorney Docket No. PC934859WO15047176-130monitor for completion of the processing of the pending traffic at the first network entity, wherein the first network entity is switched from the power ON state to the power OFF state further in response to the completion of the processing of the pending traffic at the first network entity.

5. The first network entity of any preceding claim, wherein the at least one processor is configured to cause the first network entity to:synchronize a heartbeat timer with a schedule associated with expected powered ON and powered OFF durations of the first network entity.

6. The first network entity of any preceding claim, wherein the at least one processor is configured to cause the first network entity to:receive feedback information from the second network entity, wherein the feedback information indicates a successful service compensation by the second network entity, wherein the first network entity is switched from the power ON state to the power OFF state further in response to the received feedback information.

7. The first network entity of any preceding claim, wherein the at least one processor is configured to cause the first network entity to:instruct a third network entity to retain profile context of the first network entity, after switching from the power ON state to the power OFF state, by including a status that indicates the power OFF state,wherein the third network entity is configured to support discovery and selection of the first network entity, and wherein the third network entity is configured to output timing information that indicates a time the first network entity is available to switch to the power ON state / for reactivation.

8. The first network entity of claim 7, wherein the at least one processor is configured to cause the first network entity to:transmit to the third network entity an indication of the power OFF state of the first network entity.Attorney Docket No. PC934859WO15047176-19. The first network entity of any preceding claim, wherein the at least one processor is configured to cause the first network entity to:reactivate one or more capabilities associated with the at least one service and corresponding to one or more requirements of the consumer entity during the power OFF state of the first network entity.

10. The first network entity of any preceding claim, wherein at least one of:the first network entity is a network function that is configured to be powered OFF to an energy saving state; andthe second network entity is a target network function configured to compensate the operation of the first network entity.

11. A first network entity for wireless communication, comprising:at least one memory; andat least one processor coupled with the at least one memory and configured to cause the first network entity to:select a second network entity to compensate at least one service for at least one consumer entity, and to at least one of:process pending traffic prior to switching to a power OFF state;synchronize a heartbeat timer with a schedule associated with expected powered ON and powered OFF durations of the first network entity; andreceive feedback information from the second network entity, wherein the feedback information indicates a successful service compensation by the second network entity, wherein the first network entity is switched from the power ON state to the power OFF state further in response to the received feedback information.

12. The first network entity of any preceding claim, wherein the power OFF state is at least one of:a state in which the first network entity remains powered on with a reduced power level to maintain the one or more of the network context and user context;Attorney Docket No. PC934859WO15047176-1a state in which the first network entity is configured to process ongoing service requests and to be unable to be selected to support further consumer requests;a state in which the first network entity is operable to return to full operational status following expiry of the power OFF state; anda powered off state.

13. The first network entity of claim 12, wherein the expiry of the power OFF state is based on a time period associated with an energy saving schedule.

14. The first network entity of any preceding claim, wherein the at least one processor is configured to cause the first network entity to:store the at least one of network context and user context into a data repository entity; andprovide to the second network entity a context identity to be able to retrieve and use the at least one of network context and user context.

15. The first network entity of any preceding claim, wherein the at least one processor is configured to determine that the first network entity can be switched to the power OFF state based on at least one of:a service scope of the first network entity;a geographical coverage area of the first network entity;whether the first network entity performs an aggregated role by serving one or more other network entities; andwhether the first network entity supports one or more functionalities not available in at least one other network function of a same type.

16. A second network entity for wireless communication, comprising:at least one memory; andat least one processor coupled with the at least one memory and configured to cause the second network entity to:receive at least one of a network context and a user context from a first network entity according to any preceding claim; andAttorney Docket No. PC934859WO15047176-1provide service compensation for the first network entity.

17. The second network entity of claim 16, wherein the at least one processor is configured to cause the second network entity to adjust an associated profile to facilitate discovery, based on one or more of:a scope of services being compensated,one or more service features,a service priority, andone or more expected load conditions.

18. The second network entity of claim 16 or claim 17, wherein the at least one processor is configured to cause the second network entity to perform service compensation in response to at least one of an authentication and authorization process from the first network entity to act on its behalf.

19. The second network entity of any of claims 16 to 18, wherein the at least one processor is configured to cause the second network entity to:signal successful configuration of the service compensation, to the first network entity, prior to the first network entity being switched to the power OFF state.

20. A method, performed by a first network entity in a telecommunications network, the method comprising:selecting a second network entity to compensate at least one service for at least one consumer entity;transferring one or more of a network context or a user context to the selected second network entity prior to the first network entity switching to a power OFF state, wherein the network context or a user context supports the at least one service; and switching from a power ON state to the power OFF state in response to one or more of the network context or the user context being transferred to the selected second network entity.Attorney Docket No. PC934859WO15047176-1

Images