Method of a network node, method of a core network node, network node, and core network node

Abstract

An aspect of this disclosure includes a method of a network node. The method includes communicating with a NF with Energy Saving State Change. The method includes controlling the NF with Energy Saving State Change based on an event rule to detect an event relating to Energy Saving State.

Description

METHOD OF A NETWORK NODE, METHOD OF A CORE NETWORK NODE, NETWORK NODE, AND CORE NETWORK NODE

[0001] The present disclosure relates to a method of a network node, a method of a core network node, a network node, and a core network node, etc.

[0002] Edge Computing enables network operators and 3rdparty service providers to host application servers close to the UE's access point of attachment, so as to achieve a service delivery through reduced end-to-end latency and load on the transport network.

[0003] Fig. 1 shows an architectural view of an edge computing system specified in TS 23.548 [9]. In the context of the present application, a Data Network (DN) can be categorized as a central DN or a local part of a DN.

[0004] The central DN attached to a User Plane Function (UPF) in a 5G core (5GC) via an N6 reference point is located at a far side of the 5G system relative to UEs. On the other hand, the local part of the DN attached to another UPF in 5GC via the N6 reference point is located at a location closer to UEs. The local part of the DN can be deployed in a distributed way.

[0005] On the local part of the DN, Edge Application Servers (EASs) are application servers that are deployed close to the UE's access point of attachment to provide edge application services for UEs.

[0006] It is described in TR 22.882 [1] that climate change and global energy shortage are issues that requires international cooperation and coordinated solutions at all levels. Whereas the existing studies concentrate more on how to satisfy user experience and try to achieve energy efficiency within the network at the same time, verticals and customers have no approach for energy efficiency related information from the network.

[0007] 5GC Energy Efficiency (EE) related KPIs are introduced in TS28.554

[0012] , where the KPI is expressed as a fraction of Useful Output of 5GC and Energy Consumption of 5GC. An example of the numerator is the sum of the UL and DL data volumes at a certain interface, and the denominator is the sum of the energy consumptions of physical and virtualized network functions. In a case where the 5GC is able to reduce the energy consumptions while maintaining the required level of data volumes handled by 5GC (e.g., UPF), then the energy efficiency is improved.

[0008] A use case on supporting different energy-related SLAs in industrial campus is introduced in TR 22.882 [1]. The use case is introduced for an energy saving between a factory F and a 5GC in an operator T. The 5G MEC system at the factory F is expected to be able to: - Monitor the workload in the local MEC environment in relation to the current energy consumptions, - specify threshold to classify the energy consumption. The threshold for example, separates the two states such as lower or higher energy consumption states, - evaluate a status change, which may be referred to as an event, to identify when the dynamic energy control should be started. For example, an event can be set as a status change from a lower to a higher energy consumption state, and vice versa. It is important to note a terminology variant that for example, in case of lower energy consumption, while maintaining required optimum level of load maps to "High Energy Efficiency status" as compared to "Low Energy Efficiency status" which maps to relatively high(er) energy consumption for the same, or lower level of traffic load handled by the network or by a specific NF, - issue / trigger notifications to inform operator T to kick off energy saving procedures in the 5GC.

[0009] Besides, the 5GC (managed / owned by the operator T), is expected to be able to: - manage dedicated network functions with energy saving state change capability - route notifications from the 5G MEC to the appropriate 5GC NF to convey the request(s) from 5G MEC and vice versa, - change energy state of the dedicated network function(s), if notified, to react to the request from the 5G MEC, - define policies for managing energy state of the dedicated network functions to describe how energy state is controlled.

[0010] NF energy state is sometimes referred to using the term status (i.e., NF energy status).

[0011] NPL 1: [1] 3GPP TR 22.882 V19.0.0 (2023-06) Study on Energy Efficiency as a service criteria NPL 2: [2] 3GPP TS 23.501 V18.2.2 (2023-07) System architecture for the 5G System (5GS); Stage 2 NPL 3: [3] 3GPP TS 23.502 V18.2.0 (2023-06) Procedures for the 5G System (5GS);Stage 2 NPL 4: [4] 3GPP TS 23.503 V18.2.0 (2023-06) Policy and charging control framework for the 5G System (5GS);Stage 2 NPL 5: [5] 3GPP TS 23.548 V18.2.0 (2023-06) 5G System Enhancements for Edge Computing; Stage 2 NPL 6: [6] 3GPP TS 23.558 V18.3.0 (2023-06) Architecture for enabling Edge Applications; NPL 7: [7] 3GPP TS 28.104 V18.0.1 (2023-06) Management Data Analytics (MDA) NPL 8: [8] 3GPP TS 28.310 V18.2.0 (2023-06) Energy efficiency of 5G NPL 9: [9] 3GPP TS 28.538 V18.3.0 (2023-06) Edge Computing Management (ECM) NPL 10:

[0010] 3GPP TS 28.550 V18.2.0 (2023-09) Performance assurance NPL 11:

[0011] 3GPP TS 28.552 V18.3.0 (2023-06) 5G performance measurements NPL 12:

[0012] 3GPP TS 28.554 V18.2.0 (2023-06) 5G end to end Key Performance Indicators (KPI) NPL 13:

[0013] 3GPP TS 28.622 V18.4.0 (2023-09) Integration Reference Point (IRP);Information Service (IS) NPL 14:

[0014] 3GPP TS 29.564 V18.1.0 (2023-06) 5G System; User Plane Function Services; Stage 3

[0012] There are limitations in the current 3GPP specification in the 5G MEC system for the factory F and 5GC for the operator T.

[0013] TS28.550

[0010] describes threshold crossing notifications triggering process but the aspects are limited to performance assurance.

[0014] TS23.501 [2] describes 5GC NFs in 5GC but the aspect of the energy efficiency is not covered.

[0015] TS23.502 [3] describes procedures in 5GC but the aspect of how energy efficiency information is handled between 5G MEC in factory F and 5GC in operator T is not described yet.

[0016] TS23.503 [4] describes policies in 5GC but the aspect of policies for energy state of the dedicated network functions is not described yet.

[0017] The problem to solve is that there is no disclosure in the above 3GPP specifications to achieve the energy efficiency or energy saving mentioned in the background.

[0018] The objective of this disclosure is to solve the above problem.

[0019] Abbreviations 　　For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. 4G-GUTI　　4G Globally Unique Temporary UE Identity 5GC　　5G Core Network 5GLAN　　5G Local Area Network 5GS　　5G System 5G-AN　　5G Access Network 5G-AN PDB　　5G Access Network Packet Delay Budget 5G-EIR　　5G-Equipment Identity Register 5G-GUTI　　5G Globally Unique Temporary Identifier 5G-BRG　　5G Broadband Residential Gateway 5G-CRG　　5G Cable Residential Gateway 5G GM　　5G Grand Master 5G-RG　　5G Residential Gateway 5G-S-TMSI　　5G S-Temporary Mobile Subscription Identifier 5G VN　　5G Virtual Network 5QI　　5G QoS Identifier ABBA　　Anti-Bidding-down Between Architectures AF　　Application Function AMF　　Access and Mobility Management Function API　　Application Programming Interface AS　　Access Stratum ATSSS　　Access Traffic Steering, Switching, Splitting ATSSS-LL　　ATSSS Low-Layer AUSF　　Authentication Server Function AUTN　　Authentication token BBF　　Broadband Forum BMCA　　Best Master Clock Algorithm BSF　　Binding Support Function CAG　　Closed Access Group CAPIF　　Common API Framework for 3GPP northbound APIs CHF　　Charging Function CN PDB　　Core Network Packet Delay Budget CP　　Control Plane CU　　Centralized Unit DAPS　　Dual Active Protocol Stacks DL　　Downlink DN　　Data Network DNAI　　DN Access Identifier DNN　　Data Network Name DRX　　Discontinuous Reception DS-TT　　Device-side TSN translator DU　　Distributed Unit ePDG　　evolved Packet Data Gateway EAP　　Extensible Authentication Protocol EBI　　EPS Bearer Identity EPS　　Evolved Packet System EUI　　Extended Unique Identifier FAR　　Forwarding Action Rule FN-BRG　　Fixed Network Broadband RG FN-CRG　　Fixed Network Cable RG FN-RG　　Fixed Network RG FQDN　　Fully Qualified Domain Name GFBR　　Guaranteed Flow Bit Rate GMLC　　Gateway Mobile Location Centre GPSI　　Generic Public Subscription Identifier GUAMI　　Globally Unique AMF Identifier GUTI　　Globally Unique Temporary UE Identity HR　　Home Routed (roaming) IAB　　Integrated access and backhaul IMEI　　International Mobile Equipment Identity IMEI / TAC　　IMEI Type Allocation Code IMS　　IP Multimedia Subsystem IOWN　　Innovative Optical and Wireless Network IPUPS　　Inter PLMN UP Security I-SMF　　Intermediate SMF I-UPF　　Intermediate UPF LADN　　Local Area Data Network LBO　　Local Break Out (roaming) LMF　　Location Management Function LoA　　Level of Automation LPP　　LTE Positioning Protocol LRF　　Location Retrieval Function LTE　　Long Term Evolution MAC　　Medium Access Control MCC　　Mobile country code MCX　　Mission Critical Service MDBV　　Maximum Data Burst Volume MFBR　　Maximum Flow Bit Rate MICO　　Mobile Initiated Connection Only MNC　　Mobile Network Code MO　　Mobile Originated MPS　　Multimedia Priority Service MPTCP　　Multi-Path TCP Protocol MT　　Mobile Terminated MT　　Mobile Termination N3IWF　　Non-3GPP InterWorking Function N5CW　　Non-5G-Capable over WLAN NAI　　Network Access Identifier NAS　　Non-Access Stratum NEF　　Network Exposure Function NF　　Network Function NGAP　　Next Generation Application Protocol ngKSI　　Next Generation Key Set Identifier NID　　Network identifier NPN　　Non-Public Network NR　　New Radio NRF　　Network Repository Function NSI ID　　Network Slice Instance Identifier NSSAA　　Network Slice-Specific Authentication and Authorization NSSAAF　　Network Slice-Specific Authentication and Authorization Function NSSAI　　Network Slice Selection Assistance Information NSSF　　Network Slice Selection Function NSSP　　Network Slice Selection Policy NW-TT　　Network-side TSN translator NWDAF　　Network Data Analytics Function O-RAN　　Open RAN Alliance O-DU　　O-RAN Distributed Unit O-CU　　O-RAN Centralized Unit O-RU　　O-RAN Radio Unit PCF　　Policy Control Function PDB　　Packet Delay Budget PDCP　　Packet Data Convergence Protocol PDR　　Packet Detection Rule PDU　　Protocol Data Unit PEI　　Permanent Equipment Identifier PER　　Packet Error Rate PFD　　Packet Flow Description PLMN　　Public Land Mobile Network PNI-NPN　　Public Network Integrated Non-Public Network PPD　　Paging Policy Differentiation PPF　　Paging Proceed Flag PPI　　Paging Policy Indicator PSA　　PDU Session Anchor PTP　　Precision Time Protocol QFI　　QoS Flow Identifier QoE　　Quality of Experience QoS　　Quality of Service RACS　　Radio Capabilities Signalling optimisation (R)AN　　(Radio) Access Network RG　　Residential Gateway RU　　Radio Unit RIM　　Remote Interference Management RLC　　Radio Link Control RQA　　Reflective QoS Attribute RQI　　Reflective QoS Indication RRC　　Radio Resource Control RSN　　Redundancy Sequence Number SA NR　　Standalone New Radio SBA　　Service Based Architecture SBI　　Service Based Interface SCP　　Service Communication Proxy SD　　Slice Differentiator SDAP　　Service Data Adaptation Protocol SEAF　　Security Anchor Functionality SEPP　　Security Edge Protection Proxy SMF　　Session Management Function SMS　　Short Message Service SMSF　　Short Message Service Function SN　　Sequence Number SN name　　Serving Network Name. SNPN　　Stand-alone Non-Public Network S-NSSAI　　Single Network Slice Selection Assistance Information SOR　　Steering Of Roaming SSC　　Session and Service Continuity SSCMSP　　Session and Service Continuity Mode Selection Policy SST　　Slice / Service Type SUCI　　Subscription Concealed Identifier SUPI　　Subscription Permanent Identifier SV　　Software Version TAI　　Tracking Area Identity TCP　　Transmission Control Protocol TNAN　　Trusted Non-3GPP Access Network TNAP　　Trusted Non-3GPP Access Point TNGF　　Trusted Non-3GPP Gateway Function TNL　　Transport Network Layer TNLA　　Transport Network Layer Association TSC　　Time Sensitive Communication TSCAI　　TSC Assistance Information TSN　　Time Sensitive Networking TSN GM　　TSN Grand Master TSP　　Traffic Steering Policy TT　　TSN Translator TWIF　　Trusted WLAN Interworking Function UCMF　　UE radio Capability Management Function UDM　　Unified Data Management UDR　　Unified Data Repository UDSF　　Unstructured Data Storage Function UE　　User Equipment UL　　Uplink UL CL　　Uplink Classifier UP　　User Plane UPF　　User Plane Function URLLC　　Ultra Reliable Low Latency Communication URRP-AMF　　UE Reachability Request Parameter for AMF URSP　　UE Route Selection Policy UU　　Interface between User Equipment and Radio Access Network VID　　VLAN Identifier VLAN　　Virtual Local Area Network W-5GAN　　Wireline 5G Access Network W-5GBAN　　Wireline BBF Access Network W-5GCAN　　Wireline 5G Cable Access Network W-AGF　　Wireline Access Gateway Function WLAN　　Wireless Local Area Network WUS　　Wake Up Signal

[0020] Definitions 　　For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].

[0021] Fig. 1 is 5GS providing access to EAS with UL CL / BP for non-roaming scenario.Fig. 2 is an example of a signaling diagram of this disclosure.Fig. 3 is an example of a data structure of this disclosure.Fig. 4 is an example of a signaling diagram of this disclosure.Fig. 5 is an example of a data structure of this disclosure.Fig. 6 is an example of a data structure of this disclosure.Fig. 7 is an example of a signaling diagram of this disclosure.Fig. 8 is an example of a signaling diagram of this disclosure.Fig. 9 is an example of a data structure of this disclosure.Fig. 10 is an example of a signaling diagram of this disclosure.Fig. 11 is an example of a data structure of this disclosure.Fig. 12 is an example of a signaling diagram of this disclosure.Fig. 13 is an example of a signaling diagram of this disclosure.Fig. 14 is an example of a data structure of this disclosure.Fig. 15 is an example of a data structure of this disclosure.Fig. 16 is an example of a data structure of this disclosure.Fig. 17 is an example of a data structure of this disclosure.Fig. 18 is a diagram illustrating a system overview.Fig. 19 is a block diagram illustrating a UE.Fig. 20 is a block diagram illustrating an (R)AN node.Fig. 21 is a diagram illustrating System overview of (R)AN node based on O-RAN architecture.Fig. 22 is a block diagram illustrating an RU.Fig. 23 is a block diagram illustrating a DU.Fig. 24 is a block diagram illustrating a CU.Fig. 25 is a block diagram illustrating an AMF.Fig. 26 is a block diagram illustrating an SMF.Fig. 27 is a block diagram illustrating a UPF.Fig. 28 is a block diagram illustrating a PCF.Fig. 29 is a block diagram illustrating a NEF.Fig. 30 is a block diagram illustrating an UDM.Fig. 31 is a block diagram illustrating an NWDAF.Fig. 32 is a block diagram illustrating an AF.Fig. 33 is a block diagram illustrating an OAM.Fig. 34 is a block diagram illustrating an NRF.

[0022] For example, the objective of this application is to disclose at least one of the following aspects in the 5G MEC. - How to specify threshold to classify the energy consumption. The threshold level for example, separates the two states (or status) such as lower or higher energy consumption states, - How to evaluate a status change, which may be referred to as an event, to identify when the dynamic energy control should be started. For example, an event can be set as a status change from lower to higher energy consumption state, and vice versa, - How to issue / activate notifications to inform the operator T to kick off energy saving procedures / workflows in the 5GC.

[0023] In addition, for example, the application discloses at least one of the following aspects in the 5GC: - How to manage dedicated network functions with energy saving state change capability to function / operate in an energy-efficient manner, - How to route notification from the 5G MEC to appropriate 5GC NF to inform the request(s) from 5G MEC and vice versa, - How to change energy state of the dedicated network functions, if notified, to react to the request from the 5G MEC, - How to define / describe policies for energy state of the dedicated network functions to describe how energy state is controlled.

[0024] According to this disclosure, for example, at least one of, or all the following new requirements to be addressed. - 1. The 5G system supports different energy states of network elements and network functions. - 2. The 5G system supports dynamic changes of energy states of network elements and network functions, based on pre-configured policy with authorised 3rd party. - 3. Pre-configured policy may include: the time of day, date or a threshold level of changing energy states, which energy state map to which level of load, etc.

[0025] According to this disclosure, for example, at least one of followings are defined to achieve the energy efficiency or energy saving mentioned in the background: - A new service as EnergySaving Management service in OAM, - A new capability in PCF for EnergySaving, - A new capability in PCF and NEF to subscribe for EnergySaving, - A new capability in AF for EnergySaving, - Different energy states in NF referred, but not limited to, e.g., -- Compute-optimized, Energy-optimized, etc. - A new service in Provisioning management service in OAM is introduced, - Scheduled workflows for dynamic changes of energy states, - Subscription workflow for notification service about energy states, - Notification workflow to deliver events about energy states, - Energy Saving and Provisioning management service in OAM management objects for Energy Saving, - Following the workflow by Energy Saving in 5GC and Provisioning management service in OAM Energy Saving state change capability in NF changes different energy states of network elements and network functions, - Pre-configured policy based on a schedule, - Pre-configured policy based on energy state classified by threshold, - Pre-configured policy based on energy state predicted by level of load.

[0026] Those skilled in the art will appreciate that elements in the figures are illustrated for simplicity and may not have necessarily been drawn to scale. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the figures by conventional symbols, and the figures may show only those specific details that are pertinent to understanding the Aspects of the present disclosure so as not to obscure the figures with details that will be readily apparent to those skilled in the art having the benefit of the description herein.

[0027] For the purpose of promoting an understanding of the principles of the disclosure, reference will now be made to the Aspect illustrated in the figures and specific language will be used to describe them. It will nevertheless be understood that no limitation of the scope of the disclosure is thereby intended. Such alterations and further modifications in the illustrated system, and such further applications of the principles of the disclosure as would normally occur to those skilled in the art are to be construed as being within the scope of the present disclosure.

[0028] The terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method that comprises a list of steps does not include only those steps but may include other steps not expressly listed or inherent to such a process or method. Similarly, one or more devices or entities or sub-systems or elements or structures or components preceded by "comprises... a" does not, without more constraints, preclude the existence of other devices, sub-systems, elements, structures, components, additional devices, additional sub-systems, additional elements, additional structures or additional components. Appearances of the phrase "in an Aspect", "in another Aspect" and similar language throughout this specification may, but not necessarily do, all refer to the same Aspect.

[0029] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this disclosure belongs. The system, methods, and examples provided herein are only illustrative and not intended to be limiting.

[0030] In the following specification and the claims, reference will be made to a number of terms, which may be defined to have the following meanings. The singular forms "a", "an", and "the" include plural references unless the context clearly dictates otherwise.

[0031] As used herein, information is associated with data and knowledge, as data is meaningful information and represents the values attributed to parameters. Further knowledge signifies understanding of an abstract or concrete concept. Note that this example system is simplified to facilitate description of the disclosed subject matter and is not intended to limit the scope of this disclosure. Other devices, systems, and configurations may be used to implement the Aspects disclosed herein in addition to, or instead of, a system, and all such Aspects are contemplated as within the scope of the present disclosure.

[0032] Each of Aspects and elements included in the each of Aspects described below may be implemented independently or in combination with any other. These Aspects include novel characteristics different from one another. Accordingly, these Aspects contribute to achieving objects or solving problems different from one another and contribute to obtaining advantages different from one another.

[0033] Any lists described in following aspects include at least one parameter or multiple parameters.

[0034] An example object of this disclosure is to provide a method and apparatus that can solve the above-mentioned problem.

[0035] In this disclosure, regarding listed parameters in the certain message, at least one of the listed parameters may be included in the certain message. For example, "the message including parameter A and parameter B" may mean "the message including at least one of parameter A and parameter B". In addition, for example, "A including (or containing, or similar wording etc.) B and C" may mean "A including at least one of B and C".

[0036] A method of a network node according to example aspect of this disclosure includes communicating with a NF with Energy Saving State Change. The method includes controlling the NF with Energy Saving State Change based on an event rule to detect an event relating to Energy Saving State.

[0037] A method of a core network node according to example aspect of this disclosure includes sending, to a NEF, a parameter for subscribing to receive energy saving information indicating that an observed or a predicted energy saving metric exceeds or falls below a threshold level. The method includes receiving, from the NEF, the energy saving information. The Energy Saving information is generated by NF.

[0038] A method of a core network node according to example aspect of this disclosure includes communicating with a NF. The method includes switching an energy state of the NF between Energy-optimized state and Compute-optimized state, in a case where an attribute of Energy Saving switch to manage or control the energy saving state of the NF is changed.

[0039] A method of a core network node according to example aspect of this disclosure includes receiving, from a NEF, AF available data including a first parameter relating to Event ID indicating ENERGY_SAVIING. The method includes storing the received AF available data including a first parameter relating to Event ID indicating ENERGY_SAVIING. The method includes receiving, from a PCF, a second parameter relating to Event ID indicating ENERGY_SAVIING. The method includes determining that the first parameter is stored, based on the second parameter. The method includes sending, to the PCF, the stored AF available data.

[0040] A network node according to example aspect of this disclosure includes at least one memory, and at least one hardware processor coupled to the at least one memory. The at least one hardware processor is configured to communicate with a NF with Energy Saving State Change. The at least one hardware processor is configured to control the NF with Energy Saving State Change based on an event rule to detect an event relating to Energy Saving State.

[0041] A core network node according to example aspect of this disclosure includes at least one memory, and at least one hardware processor coupled to the at least one memory. The at least one hardware processor is configured to send, to a NEF, a parameter for subscribing to receive energy saving information indicating that an observed or a predicted energy saving metric exceeds or falls below a threshold. The at least one hardware processor is configured to receive, from the NEF, the energy saving information. The Energy Saving information is generated by NF.

[0042] A core network node according to example aspect of this disclosure includes at least one memory, and at least one hardware processor coupled to the at least one memory. The at least one hardware processor is configured to communicate with a NF. The at least one hardware processor is configured to switch an energy state of the NF between Energy-optimized state and Compute-optimized state, in a case where an attribute of Energy Saving switch to manage or control the energy saving state of the NF is changed.

[0043] A core network node according to example aspect of this disclosure includes at least one memory, and at least one hardware processor coupled to the at least one memory. The at least one hardware processor is configured to receive, from a NEF, AF available data including a first parameter relating to Event ID indicating ENERGY_SAVIING. The at least one hardware processor is configured to store the received AF available data including a first parameter relating to Event ID indicating ENERGY_SAVIING. The at least one hardware processor is configured to receive, from a PCF, a second parameter relating to Event ID indicating ENERGY_SAVIING. The at least one hardware processor is configured to determine that the first parameter is stored, based on the second parameter. The at least one hardware processor is configured to send, to the PCF, the stored AF available data.

[0044] First aspect (Solution 1) 　　This solution discloses methods about how to manage dedicated network functions with energy saving state change capability to be executed energy-efficiently.

[0045] Fig. 2 shows a method that an energy saving state change happens at a scheduled time.

[0046] Energy Saving Management is a role conducted by a network function or a management function in Operation, Administration and Maintenance (OAM).

[0047] NF with Energy Saving State Change is a network function in the 5GC (including 5G MEC).

[0048] Energy Saving State Change is a capability in the NF and the Energy Saving State Change capability changes the current energy saving state or the current energy saving mode.

[0049] For example, Energy Saving State Change may be a capability in the NF and the Energy Saving State Change capability may change between Energy-optimized state and Compute-optimized state as defined below.

[0050] Energy saving state may be Energy-optimized state.

[0051] The Energy Saving State Change capability is further introduced in Solution 3.

[0052] An event rule describes criteria to detect a certain event.

[0053] Fig. 3 shows an example of the event rule to detect a scheduled event.

[0054] The event rule includes attributes, for example, name, timestamp, schedule and activatedRule, and so on.

[0055] The attribute, name, maps to, or indicates the name of the event rule.

[0056] The attribute, timestamp, maps to, or indicates the time when the eventRule is created.

[0057] The attribute, schedule, maps to, or indicates the time when the eventRule is evaluated.

[0058] The attribute, schedule, may include, for example, min, hour, date, month date, day of the week and year.

[0059] Each attribute maps to, or indicates minute, hour, date of the month, month , day of the week, and year respectively of the schedule.

[0060] The attribute, activatedRule, maps to or indicates the rule that initiate a workflow to change the energy saving state of a NF.

[0061] The detailed processes of the aspect are described as below, with reference to Fig. 2.

[0062] Step1-1: 　　An event rule is created or generated in Energy Saving Management.

[0063] An event rule may be created or generated in Energy Saving Management based on the input by a network operator.

[0064] If a scheduled time comes, then the event rule is evaluated by Energy Saving Management function or Energy Saving Management function node (for example, OAM with the Energy Saving Management function).

[0065] Step1-2: 　　If the schedule event is detected by Energy Saving Management function or Energy Saving Management function node (for example, OAM with the Energy Saving Management function), then a workflow is activated to change an energy saving state change in a dedicated network function.

[0066] For example, if the schedule event is detected by Energy Saving Management function in the 5GC or Energy Saving Management function node (for example, OAM with the Energy Saving Management function), then the NF with Energy Saving State Change may activate a workflow to change an energy saving state.

[0067] For example, if the schedule event is detected by Energy Saving Management function in the 5GC or Energy Saving Management function node (for example, OAM with the Energy Saving Management function), then the Energy Saving Management function may activate the workflow for the NF with Energy Saving State Change. The NF with Energy Saving State Change may change an energy saving state based on the workflow.

[0068] The corresponding workflow is further disclosed in Solution 3.

[0069] For example, a method of a network node according to this aspect of this disclosure may include communicating with a NF with Energy Saving State Change. The method may include controlling the NF with Energy Saving State Change based on an event rule to detect an event relating to Energy Saving State.

[0070] Variant 1 of the solution 1 　　Fig. 4 shows the variant 1 of the solution 1.

[0071] In this variant 1, another event rule is introduced to detect patterned events at more or finer granularities.

[0072] Fig. 5 shows an example of an event rule to detect a patterned event.

[0073] A new attribute, event, is a list of events to be detected.

[0074] In the example, an event named as "CpuUsageIsHigh" is listed in the event[0].

[0075] The event[0] is named as "CpuUsageIsHigh" to describe that the current CPU usage is high.

[0076] Fig. 6 shows another example of an event rule to detect another patterned event.

[0077] There are two elements, event[0] and event[1], in the list of events.

[0078] The event[0] is named as "CpuUsageIsLow" to describe that the current CPU usage is low.

[0079] The event[1] is named as "PowerConsumptionIsLow" to describe that the current power consumption is low.

[0080] A new attribute, rule, describes a criteria to detect the patterned event.

[0081] In Fig. 6, the criteria is described as event[0] and event[1].

[0082] Step1-1-1: 　　An event rule is created or generated in PCF.

[0083] Step1-1-2: 　　If "Energy Saving event #1" is detected by PCF, then PCF activates switchToCompute-optimized workflow.

[0084] For example, if the event "CpuUsageIsHigh" is detected, then PCF may activate switchToCompute-optimized workflow.

[0085] If "Energy Saving event #2" is detected by PCF, then PCF activates switchToEnergy-optimized workflow.

[0086] For example, if the event "CpuUsageIsLow" or "PowerConsumptionIsLow" is detected, then PCF may activate switchToCompute-optimized workflow.

[0087] In the switchToCompute-optimized or switchToEnergy-optimized workflow, PCF notifies energySavingInfos with Npcf_EventExposure service.

[0088] The detail of the energySavingInfos is introduced in Solution2.

[0089] For example, PCF may detect "Energy Saving event #1" or "Energy Saving event #1" based on the energySavingInfos.

[0090] Step1-1-3: 　　If energySavingInfos is notified to Energy Saving Management, then a workflow is activated to change an energy saving state change in a dedicated network function.

[0091] The workflow is disclosed in Solution 3.

[0092] Second aspect (Solution 2) 　　Solution 2 discloses methods about how PCF is notified by Application Function.

[0093] Policy Control Function (PCF) is a network function in the following system overview.

[0094] Network Exposure Function (NEF) is a network function in the following system overview.

[0095] Application Function (AF) is a network function in the following system overview.

[0096] The AF has a new feature that generates energySavingInfos.

[0097] OAM is a management function that manages AF.

[0098] The detailed processes of the aspect are described as below with reference to Fig. 7.

[0099] Step2-1: 　　PCF initiates Nnef_EventExposure_subscribe service to subscribe to have events from NEF.

[0100] In addition to existing specifications in TS23.502 [3], PCF may indicate to subscribe a new event, ENERGY_SAVING, to have energy savings information in the subscription parameter.

[0101] PCF may send, to NEF, the energy savings information including the subscription parameter indicating ENERGY_SAVING event.

[0102] The subscription parameter can also include an event filter that is used to filter the type of ENERGY_SAVING event: -- OBSERVED_ENERGY_SAVING -- PREDICTED_ENERGY_SAVING

[0103] Step2-2: 　　NEF receives the parameters about ENERGY_SAVING event, and then NEF initiates Naf_EventExposure_subscribe service to subscribe to have events from AF.

[0104] The parameter described in Step2-1 is reused in the parameter of Naf_EventExposure_subscribe service.

[0105] NEF may send, to AF with Energy Saving, the received subscription parameter indicating ENERGY_SAVING event.

[0106] Step2-3: 　　AF receives the parameters about ENERGY_SAVING event, and then AF activates a feature of Energy Saving.

[0107] If OBSERVED_ENERGY_SAVING is specified in the event filter, then AF activates an OAM workflow for Threshold Crossing

[0013] .

[0108] The following variant 1 describes the workflow in detail.

[0109] Step2-4: 　　If PREDICTED_ENERGY_SAVING is specified in the event filter, then AF activates a workflow for PerfMetricJob

[0013] .

[0110] The following variant 2 describes the workflows in detail.

[0111] Step2-5: 　　Based on the report from OAM, AF creates or generates energySavingInfos.

[0112] The energySavingInfos is an event notification that describes that the target energy saving metric has crossed the threshold.

[0113] For example, the energySavingInfos may be an event notification that describes that the target energy saving metric exceeds or falls below the threshold.

[0114] AF activates Naf_EventExposure service to notify energySavingInfos to PCF.

[0115] Step2-6: 　　NEF is notified with energySavingInfos, and then NEF activates Nnef_EventExposure service to notify energySavingInfos to PCF.

[0116] For example, a method of a core network node according to this aspect of this disclosure may include sending, to a NEF, a parameter for subscribing to receive energy saving information indicating that an observed or a predicted energy saving metric exceeds or falls below a threshold. The method may include receiving, from the NEF, the energy saving information. The Energy Saving information may be generated by NF.

[0117] Variant 1 of the solution 2 　　The following variant 1 describes the workflow in detail to determine a workload status based on Threshold Crossing specified in Performance assurance service in the OAM.

[0118] The detailed processes of the variant 1 are described as below, with reference to Fig. 8.

[0119] Step2-1-1: 　　This step is the same as the step 2-2 in the solution 2.

[0120] Step2-1-2: 　　This step details the step 2-3 in the solution 2.

[0121] If the event filter includes OBSERVED_ENERGY_SAVING and a list of names of observedEnergySaving discussed in the solution 4, for example: - PEE.AvgPower.PNF1 - VR.VCpuUsageMean.VNF1

[0122] then AF creates a Management Object Instance (MOI) for ThresholdMonitor IOC specified in Performance assurance service.

[0123] If the target NF is instantiated as VNF (e.g. containers, virtual machines), then Performance assurance service collects notifications for Threshold Crossing from the VNF which executes the NF as well as PNF which executes the VNF.

[0124] If the NF is instantiated as PNF, then Performance assurance service collects notifications for Threshold Crossing from PNF which executes the NF.

[0125] The target NF is not limited and could be such as UPF, Edge Application Server as a type of AF. 　　Appropriate names of performanceMetrics are given.

[0126] Step2-1-3: 　　With VR.VCpuUsageMean.VNF1 in Fig. 15, an event of VCpuUsageMean.VNF1.Low is created when the measurement is below the value of thresholdValue.

[0127] VR.VDiskUsageMean.VNF1 in Fig. 15, OAM may collect measurements about virtual CPU usage, virtual memory usage and virtual disk usage of the VNF1.

[0128] OAM may observe a value of a target energy saving metric. The target energy saving metric may include virtual CPU usage, virtual memory usage and virtual disk usage of the VNF1.

[0129] OAM may create or generate the event of VCpuUsageMean.VNF1.Low in a case where the measurement or the energy saving metric is below the value of thresholdValue.

[0130] OAM may send the event of VCpuUsageMean.VNF1.Low.

[0131] Another event of VR.VCpuUsageMean.VNF1.High is created when the measurement is above the value of thresholdValue.

[0132] Step2-1-4: 　　With PEE.AvgPower.PNF1 in Fig. 14, an event of PEE.AvgPower.PNF1.Low is created when the measurement is below the value of thresholdValue.

[0133] PEE.AvgPower.PNF1 in Fig. 14, OAM may collect measurements about average power consumption, minimum power consumption, and maximum power consumption of the PNF1.

[0134] OAM may observe a value of a target energy saving metric. The target energy saving metric may include average power consumption, minimum power consumption, and maximum power consumption of the PNF1.

[0135] OAM may create or generate the event of PEE.AvgPower.PNF1.Low in a case where the measurement or the energy saving metric is below the value of thresholdValue.

[0136] OAM may send the event of PEE.AvgPower.PNF1.Low.

[0137] Another event of PEE.AvgPower.PNF1.High is created when the measurement is above the value of thresholdValue.

[0138] Step2-1-5: 　　Based on the collections of the notifications, AF determines the current workload.

[0139] In this case, the workloads of VNF and PNF are below the threshold, so this case is, for example, classified as the workload is low.

[0140] Step2-1-6: 　　AF creates energySavingInfos.

[0141] The energySavingInfos includes a list of events that describes the target energy saving metric has crossed the threshold.

[0142] For example, the energySavingInfos may include a list of events that describes the target metric for energy saving exceeds or falls below the threshold.

[0143] As shown in Fig. 9, energySavingInfos may, for example, include: or be structured as below: - observedMeasurement providing a name of the energy saving metric that has crossed the threshold. - observedValue providing a Value of the energy saving metric, that has crossed the threshold, when the threshold crossing was observed. - observedDirection providing a direction ("UP" or "DOWN"("e.g., DN")) of the energy saving metric, when the threshold crossing was observed. "UP" may indicate that the energy saving metric which was below the threshold exceeds the threshold now, and "DN" may indicate that the energy saving metric which exceeded the threshold becomes below the threshold now.

[0144] AF notifies the energySavingInfos with Naf_EventExposure service.

[0145] Variant 2 of the solution 2 　　The following variant 2 describes the workflow in detail to determine a workload status based on PerfMetricJob specified in Performance assurance service in the OAM.

[0146] AF with Energy Saving function may predict energy consumption (for example, energy consumption of EAS or NF) in the future, and determine the workload (for example, workload of EAS or NF).

[0147] The detailed processes of the variant 2 are described as below, with reference to Fig. 10.

[0148] Step2-2-1: 　　This step is the same as the step 2-2 in the solution 2.

[0149] Step2-2-2: 　　If the event filter includes PREDICTED_ENERGY_SAVING and a list of names of predictedEnergySaving discussed in the solution 4, for example: - PEE.AvgPower.PNF1 - VR.VCpuUsageMean.VNF1

[0150] then AF creates a Management Object Instance (MOI) for PerfMetricJob IOC specified in Streaming data reporting service.

[0151] If the target NF is instantiated as VNF (e.g. containers, virtual machines), then Streaming data reporting service in OAM collects performance metrics for PerfMetricJob from the VNF which executes the NF as well as PNF which executes the VNF.

[0152] If the NF is instantiated as PNF, then Streaming data reporting service collects n metrics for PerfMetricJob from PNF which executes the VNF, then Streaming data reporting service in OAM collects performance metrics for PerfMetricJob from the PNF.

[0153] The target NF is not limited and could be such as UPF, Edge Application Server as a type of AF.

[0154] Appropriate names of performanceMetrics are given.

[0155] Step2-2-3: 　　The performance of the monitored VNF is measured at every time of period (e.g., second, minute, hour, etc) and then the measured data is reported to AF in a stream manner.

[0156] Depending on performanceMetrics: - If the name is VR.VCpuUsageMean.VNF1, VR.VMemoryUsageMean.VNF1, VR.VDiskUsageMean.VNF1 in Fig. 17, OAM collects measurements about virtual CPU usage, virtuam memory usage and virtual disk usage of the VNF1.

[0157] Step2-2-4: 　　The performance of the monitored PNF is measured at every time of period (e.g., second, minute, hour, etc) and then the measured data is reported to AF in a stream manner.

[0158] Depending on performanceMetrics: - If the name is PEE.AvgPower.PNF1, PEE.MinPower.PNF1, PEE.MaxPower.PNF1 in Fig. 16, OAM collects measurements about average power consumption, minimum power consumption, and maximum power consumption respectively.

[0159] Step2-2-5: 　　Based on the collections of the notified report, the AF predicts workload in the future.

[0160] Step2-2-6: 　　AF creates energySavingInfos.

[0161] The energySavingInfos includes a list of energySavingInfo elements that describes that the workload is low.

[0162] As shown in Fig. 11, energySavingInfos may, for example, be structured as below. - predictedMeasurement providing a name of the predicted energy saving metric that would cross the threshold. - predictedValue providing a value of the energy saving metric, that would cross the threshold, when the threshold crossing is predicted. - predictedDirection providing a direction ("UP" or "DOWN" (e.g., "DN")) of the energy saving metric, when the threshold crossing is predicted. "UP" may indicate that the energy saving metric which is below now the threshold will exceed the threshold in the future, and "DN" may indicate that the energy saving metric which exceeds the threshold now will become below the threshold in the future.

[0163] AF notifies the energySavingInfos with Naf_EventExposure service.

[0164] Third aspect (Solution 3) 　　This solution discloses methods about how NF with Energy Saving state can be changed.

[0165] Provisioning management service in OAM manages management objects related to resource provisioning.

[0166] A management object includes an attribute of Energy Saving switch that manages or controls or switches the state of NF Energy Saving.

[0167] In case where an NF is instantiated as a VNF with two different groups of instances.

[0168] A group consists of energy efficient instances and the other group consists of high-performance instances.

[0169] The former group can be used when the NF is in a state of "Energy-optimized".

[0170] "Energy-optimized" is an energy state where the NF is executed while keeping lower power consumptions.

[0171] For example, "Energy-optimized" Group may be Energy Efficiency prioritized Group.

[0172] For example, "Energy-optimized" may be an energy state where the NF operating with energy efficiency or energy saving.

[0173] "Energy-optimized" may be an energy state which is not "Compute-optimized" state.

[0174] The latter group can be used when the NF is in a state of "Compute-optimized".

[0175] "Compute-optimized" is an energy state where the NF is executed while keeping better performance.

[0176] For example, "Compute-optimized" group may be computation prioritized group.

[0177] "Compute-optimized" may be an energy state where the NF is executed while keeping power consumptions as usual.

[0178] "Compute-optimized" may be an energy state which is not "Energy-optimized" state.

[0179] Traffic can, for example, be steered with a load balancer that is placed in front of the two groups.

[0180] For example, Traffic may be allocated by the load balancer.

[0181] For simplicity, the attribute of Energy Saving switch in this Solution 3 expects to have two energy saving state: "Energy-optimized" and "Compute-optimized".

[0182] The detailed processes of the aspect are described as below, with reference to Fig. 12.

[0183] The detail steps start with a certain condition where an attribute of Energy Saving switch for NF has been set to "Compute-optimized".

[0184] The detail steps from step3-1 to step3-4 describe about how to activate Energy Saving behavior.

[0185] Step3-1: 　　If Energy Saving management is notified with scheduled or patterned event, then Energy Saving management modifies an attribute of Energy Saving switch from "Compute-optimized" to "Energy-optimized".

[0186] Step3-2: 　　Provisioning management service in OAM connect to the target NF and modify the attribute of Energy Saving switch from "Compute-optimized" to "Energy-optimized".

[0187] Step3-3:

[0188] Energy Saving state change capability in the NF changes the direction of the traffic steering from for the group of Compute-optimized to for the group of Energy-optimized.

[0189] After the NF changes the behavior from "Compute-optimized" to "Energy-optimized", the NF informs Provisioning management service in OAM that energySaving state has been changed to Energy-optimized.

[0190] Step3-4: 　　Provisioning management service in OAM notifies Energy Saving management that energySaving state has been changed to Energy-optimized.

[0191] The output of energySaving may include the following attributes.

[0192] An attribute of old value maps onto or indicates a value of previous state, "Compute-optimized". 　　Another attribute of new value maps onto or indicates a value of current or new state, "Energy-optimized".

[0193] The detail steps from step3-5 to step3-8 describes about how to deactivate Energy Saving behavior.

[0194] Step3-5: 　　The behavior is the same as step3-1 but the modified attribute to be set is "Compute -optimized".

[0195] Step3-6: 　　The behavior is the same as step3-2 but the modified attribute to be set is "Compute -optimized".

[0196] Step3-7: 　　The behavior is the same as step3-3 but energySaving state in the NF has been changed to "Compute-optimized".

[0197] Energy Saving state change capability in the NF changes the direction of the traffic steering from for the group of Energy-optimized to for the group of Compute-optimized.

[0198] The NF informs Provisioning management service in OAM that energySaving state has been changed to "Compute-optimized".

[0199] Step3-8: 　　The behavior is the same as step3-4 but the informed energySaving state in the NF is "Compute-optimized".

[0200] The output of energySaving may consists of the following attributes.

[0201] An attribute of old value maps onto or indicates a value of previous state, "Energy-optimized". 　　Another attribute of new value maps onto or indicates a value of current or new state, "Compute-optimized".

[0202] A method of a core network node according to this aspect of this disclosure may include communicating with a N. The method may include switching an energy state of the NF between Energy-optimized state and Compute-optimized state, in a case where an attribute of Energy Saving switch to manage or control the energy saving state of the NF is changed.

[0203] Variant 1 of the solution 3 　　The attribute of Energy Saving switch can be represented more flexibly.

[0204] In a case where an NF is instantiated as a VNF with multiple instances (e.g., containers or virtual machines), the power consumptions can be reduced if the number of the running instances is decreased.

[0205] In this case, Energy Saving state can, for example, be represented as 25%, 50%, 75% or 100%. 　　The meaning of 25% is that a quarter of the instances are running.

[0206] If Energy Saving state change capability increases the number of the percentage, the Energy Saving state is shifted to "Compute-optimized".

[0207] When Energy Saving state change capability decreases the number of the percentage, the Energy Saving state is shifted to "Energy-efficient".

[0208] Fourth aspect (Solution 4) 　　This solution discloses methods about how AF notification service is available in 5GC.

[0209] The detailed processes of the aspect are described as below, with reference to Fig. 13.

[0210] Step4-1:

[0211] Common performance measurements for NFs in TS28.552

[0011] is a collection of measured data for virtual resources.

[0212] The Common performance measurements may include further performance measurement related to Power, Energy and Environment for physical network functions.

[0213] The physical network function may execute network functions specified in 5GC or execute virtual resources providing network functions.

[0214] Based on the Common performance measurements, AF available data can be structured and registered on NEF via OAM.

[0215] Depending on the AF available data: - if the AF available data is "observedEnergySaving", -- Fig. 14 shows an example related to average power consumption of a physical network function that executes virtual network function for PNF1. -- Fig. 15 shows another example of observedEnergySaving related to average virtual cpu usage of a virtual network function of VNF1. - if the AF available data is "predictedEnergySaving", -- Fig. 16 shows an example of predictedEnergySaving providing performance measurement data related to Power, Energy and Environment for physical network functions. -- Fig. 17 shows another example of predictedEnergySaving providing performance measurement data related to virtual network functions.

[0216] An AF available data specified as observedEnergySaving may, for example, include: - id providing a name of the event (e.g, PEE.AvgPower.PNF1, VR.VCpuUsageMean.VNF1) - ThresholdMonitor providing a threshold monitor for performance metrics specified in TS28.622

[0013]

[0217] Each element of the ThresholdMonitor may include: - performanceMetrics providing a list of names the observed measurement (e.g., PEE.AvgPower.PNF1, VR.VCpuUsageMean.VNF1.Low) - thresholdInfoList providing a list of thresholdInfo elements specified in TS28.622

[0013]

[0218] Each element of the thresholdInfoList may include: - thresholdDirection providing a direction of the measured data (e.g., UP, DN) - thresholdValue providing a value of the measured data (e.g., 50, 100)

[0219] An AF available data specified as predictedEnergySaving may, for example, include: - jobId providing a name of the mesurement (e.g, PEE.PNF1, VR.VNF1) - perfMetricJob providing a performance metric production job specified in TS28.622

[0013]

[0220] PerfMetricJob may include: - performanceMetrics providing a name the observed measurement (e.g., PEE.AvgPower.PNF1, VR.VCpuUsageMean.VNF1)

[0221] Step4-2: 　　NEF utilizes Nnrf_Nfmanagement_Register service to register the AF available data.

[0222] In this case, an event whose event id is ENERGY_SAVING is registered.

[0223] For example, NEF may send, to NRF, AF available data including a first parameter relating to Event ID indicating ENERGY_SAVIING.

[0224] For example, NEF may send, to NRF, AF available data including a first parameter for using energy saving.

[0225] For example, NEF may send, to NRF, AF available data including a first parameter for changing between Energy-optimized state and Compute-optimized state.

[0226] The AF available data or the first parameter relating to Event ID indicating ENERGY_SAVIING may be used for energy saving or for changing between Energy-optimized state and Compute-optimized state.

[0227] The AF available data may be related to Event ID indicating ENERGY_SAVIING.

[0228] Step4-3: 　　NRF stores the new event whose event id is ENERGY_SAVING.

[0229] NRF may store the received AF available data from NEF.

[0230] Then NRF responds to NEF.

[0231] Step4-4: 　　If PCF needs to be notified with ENERGY_SAVING, then PCF initiates Nnrf_NfDiscovery_Request service to discover AF available data.

[0232] The target AF available data is explicitly requested with the event id, "ENERGY_SAVING".

[0233] For example, NRF may receive, from PCF, a second parameter relating to Event ID indicating ENERGY_SAVIING.

[0234] Step4-5: 　　NRF discovers the AF available data with the event id, "ENERGY_SAVING".

[0235] For example, NRF may discover or detect or determine or consider that the first parameter and the second parameter indicate the same Event ID "ENERGY_SAVIING".

[0236] For example, NRF may discover or detect or determine or consider the first parameter corresponding to the second parameter.

[0237] For example, NRF may send the first parameter corresponding to the second parameter.

[0238] If discovered, then NRF responds to PCF with the event id, "ENERGY_SAVING".

[0239] For example, if discovered, then NRF responds to PCF the stored AF available data with the event id, "ENERGY_SAVING".

[0240] A method of a core network node according to this aspect of this disclosure may include receiving, from a NEF, AF available data including a first parameter relating to Event ID indicating ENERGY_SAVIING. The method may include storing the received AF available data including a first parameter relating to Event ID indicating ENERGY_SAVIING. The method may include receiving, from a PCF, a second parameter relating to Event ID indicating ENERGY_SAVIING. The method may include determining that the first parameter is stored, based on the second parameter. The method may include sending, to the PCF, the stored AF available data.

[0241] System overview 　　Fig. 18 schematically illustrates a telecommunication system 1 for a mobile (cellular or wireless) device (known as a user equipment (UE)) to which the above aspects are applicable.

[0242] The telecommunication system 1 represents a system overview in which an end to end communication is possible. For example, UE 3 (or user equipment, 'mobile device' 3) communicates with other UEs 3 or service servers in the data network 20 via respective (R)AN nodes 5 and a core network 7.

[0243] The (R)AN node 5 supports any radio accesses including a 5G radio access technology (RAT), an E-UTRA radio access technology, a beyond 5G RAT, a 6G RAT and non-3GPP RAT including wireless local area network (WLAN) technology as defined by the Institute of Electrical and Electronics Engineers (IEEE).

[0244] The (R)AN node 5 may split into a Radio Unit (RU), Distributed Unit (DU) and Centralized Unit (CU). In some aspects, each of the units may be connected to each other and structure the (R)AN node 5 by adopting an architecture as defined by the Open RAN (O-RAN) Alliance, where the units above are referred to as O-RU, O-DU and O-CU respectively.

[0245] The (R)AN node 5 may be split into one or more control plane functions and one or more user plane functions. Further, multiple user plane functions can be allocated to support a communication. In some aspects, user traffic may be distributed to multiple user plane functions and user traffic over each user plane function is aggregated in both the UE 3 and the (R)AN node 5. This split architecture may be called 'dual connectivity' or 'Multi connectivity'.

[0246] The (R)AN node 5 can also support a communication using the satellite access. In some aspects, the (R)AN node 5 may support a satellite access and a terrestrial access.

[0247] In addition, the (R)AN node 5 can also be referred as an access node for a non-wireless.

[0248] access. The non-wireless access includes a fixed line access as defined by the Broadband Forum (BBF) and an optical access as defined by the Innovative Optical and Wireless Network (IOWN).

[0249] The core network 7 may include logical nodes (or 'functions') for supporting a communication in the telecommunication system 1. For example, the core network 7 may be 5G Core Network (5GC) that includes, amongst other functions, control plane functions and user plane functions. Each function in a logical node can be considered as a network function. The network function may be provided to another node by adapting the Service Based Architecture (SBA).

[0250] A Network Function can be deployed as distributed, redundant, stateless, and scalable that provides the services from several locations and several execution instances in each location by adapting the network virtualization technology as defined by the European Telecommunications Standards Institute, Network Functions Virtualization (ETSI NFV).

[0251] The core network 7 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0252] As is well known, a UE 3 may enter and leave the areas (i.e. radio cells) served by the (R)AN node 5 as the UE 3 is moving around in the geographical area covered by the telecommunication system 1. In order to keep track of the UE 3 and to facilitate movement between the different (R)AN nodes 5, the core network 7 comprises at least one access and mobility management function (AMF) 70. The AMF 70 is in communication with the (R)AN node 5 coupled to the core network 7. In some core networks, a mobility management entity (MME) or a mobility management node for beyond 5G or a mobility management node for 6G may be used instead of the AMF 70.

[0253] The core network 7 also includes, amongst others, a Session Management Function (SMF) 71, a User Plane Function (UPF) 72, a Policy Control Function (PCF) 73, a Network Exposure Function (NEF) 74, a Unified Data Management (UDM) 75, and a Network Data Analytics Function (NWDAF) 76 etc. When the UE 3 is roaming to a visited Public Land Mobile Network (VPLMN), a home Public Land Mobile Network (HPLMN) of the UE 3 provides the UDM 75 and at least some of the functionalities of the SMF 71, UPF 72, and PCF 73 for the roaming-out UE 3.

[0254] The UE 3 and a respective serving (R)AN node 5 are connected via an appropriate air interface (for example the so-called "Uu" interface and / or the like). Neighboring (R)AN nodes 5 are connected to each other via an appropriate (R)AN node 5 to (R)AN node interface (such as the so-called "Xn" interface and / or the like). Each (R)AN node 5 is also connected to nodes in the core network 7 (such as the so-called core network nodes) via an appropriate interface (such as the so-called "N2" / "N3" interface(s) and / or the like). From the core network 7, connection to a data network 20 is also provided. The data network 20 can be an internet, a public network, an external network, a private network or an internal network of the PLMN. In case that the data network 20 is provided by a PLMN operator or Mobile Virtual Network Operator (MVNO), the IP Multimedia Subsystem (IMS) service may be provided by that data network 20. The UE 3 can be connected to the data network 20 using IPv4, IPv6, IPv4v6, Ethernet or unstructured data type.

[0255] The "Uu" interface may include a Control plane and User plane.

[0256] The User plane of the Uu interface is responsible to convey user traffic between the UE 3 and a serving (R)AN node 5. The User plane of the Uu interface may have a layered structure with SDAP, PDCP, RLC and MAC sublayer over the physical connection.

[0257] The Control plane of the Uu interface is responsible to establish, modify and release a connection between the UE 3 and a serving (R)AN node 5. The Control plane of the Uu interface may have a layered structure with RRC, PDCP, RLC and MAC sublayers over the physical connection.

[0258] For example, the following messages are communicated over the RRC layer to support AS signaling. - RRC Setup Request message: This message is sent from the UE 3 to the (R)AN node 5. In addition to the parameters that are disclosed by embodiments in this disclosure, any of the following parameters may be included together in the RRC Setup Request message. -- establishmentCause and ue-Identity. The ue-Identity may have a value of ng-5G-S-TMSI-Part1 or randomValue. - RRC Setup message: This message is sent from the (R)AN node 5 to the UE 3. In addition to the parameters that are disclosed by embodiments in this disclosure, any of the following parameters may be included together in the RRC Setup message. -- masterCellGroup and radioBearerConfig. - RRC Setup Complete message: This message is sent from the UE 3 to the (R)AN node 5. In addition to the parameters that are disclosed by embodiments in this disclosure, any of the following parameters may be included together in the RRC Setup Complete message. -- guami-Type, iab-NodeIndication, idleMeasAvailable, mobilityState, ng-5G-S-TMSI-Part2, registeredAMF, selectedPLMN-Identity.

[0259] The UE 3 and the AMF 70 are connected via an appropriate interface (for example the so-called N1 interface and / or the like). The N1 interface is responsible for providing a communication between the UE 3 and the AMF 70 to support NAS signaling. The N1 interface may be established over a 3GPP access and over a non-3GPP access. For example, the following messages are communicated over the N1 interface. - Registration Request message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by embodiments in this disclosure, any of the following parameters may be included together in the Registration Request message. -- 5GS registration type, ngKSI, 5GS mobile identity, Non-current native NAS key set identifier, 5GMM capability, UE security capability, Requested NSSAI, Last visited registered TAI, S1 UE network capability, Uplink data status, PDU session status, MICO indication, UE status, Additional GUTI, Allowed PDU session status, UE's usage setting, Requested DRX parameters, EPS NAS message container, LADN indication, Payload container type, Payload container, Network slicing indication, 5GS update type, Mobile station classmark 2, Supported codecs, NAS message container, EPS bearer context status, Requested extended DRX parameters, T3324 value, UE radio capability ID, Requested mapped NSSAI, Additional information requested, Requested WUS assistance information, N5GC indication and Requested NB-N1 mode DRX parameters. - Registration Accept message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by embodiments in this disclosure, any of the following parameters may be included together in the Registration Accept message. -- 5GS registration result, 5G-GUTI, Equivalent PLMNs, TAI list, Allowed NSSAI, Rejected NSSAI, Configured NSSAI, 5GS network feature support, PDU session status, PDU session reactivation result, PDU session reactivation result error cause, LADN information, MICO indication, Network slicing indication, Service area list, T3512 value, Non-3GPP de-registration timer value, T3502 value, Emergency number list, Extended emergency number list, SOR transparent container, EAP message, NSSAI inclusion mode, Operator-defined access category definitions, Negotiated DRX parameters, Non-3GPP NW policies, EPS bearer context status, Negotiated extended DRX parameters, T3447 value, T3448 value, T3324 value, UE radio capability ID, UE radio capability ID deletion indication, Pending NSSAI, Ciphering key data, CAG information list, Truncated 5G-S-TMSI configuration, Negotiated WUS assistance information, Negotiated NB-N1 mode DRX parameters and Extended rejected NSSAI. - Registration Complete message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by embodiments in this disclosure, the following parameter may be included together in the Registration Complete message. -- SOR transparent container. - Authentication Request message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by embodiments in this disclosure, any of the following parameters may be included together in the Authentication Request message. -- ngKSI,ABBA, Authentication parameter RAND (5G authentication challenge), Authentication parameter AUTN (5G authentication challenge) and EAP message. - Authentication Response message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by embodiments in this disclosure, any of the following parameters may be populated together in the Authentication Response message. -- Authentication response message identity, Authentication response parameter and EAP message. - Authentication Result message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by embodiments in this disclosure, any of the following parameters may be populated together in the Authentication Result message. -- ngKSI, EAP message and ABBA. - Authentication Failure message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by embodiments in this disclosure, any of the following parameters may be populated together in the Authentication Failure message. -- Authentication failure message identity, 5GMM cause and Authentication failure parameter. - Authentication Reject message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by embodiments in this disclosure, the following parameter may be populated together in the Authentication Reject message. -- EAP message. - Service Request message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by embodiments in this disclosure, any of the following parameters may be populated together in the Service Request message. -- ngKSI,Service type, 5G-S-TMSI, Uplink data status, PDU session status, Allowed PDU session status, NAS message container. - Service Accept message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by embodiments in this disclosure, any of the following parameters may be populated together in the Service Accept message. -- PDU session status, PDU session reactivation result, PDU session reactivation result error cause, EAP message and T3448 value. - Service Reject message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by embodiments in this disclosure, any of the following parameters may be populated together in the Service Reject message. -- 5GMM cause, PDU session status, T3346 value, EAP message, T3448 value and CAG information list. - Configuration Update Command message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by embodiments in this disclosure, any of the following parameters may be populated together in the Configuration Update Command message. -- Configuration update indication,5G-GUTI, TAI list, Allowed NSSAI, Service area list, Full name for network, Short name for network, Local time zone, Universal time and local time zone, Network daylight saving time, LADN information, MICO indication, Network slicing indication, Configured NSSAI, Rejected NSSAI, Operator-defined access category definitions, SMS indication, T3447 value, CAG information list, UE radio capability ID, UE radio capability ID deletion indication, 5GS registration result, Truncated 5G-S-TMSI configuration, Additional configuration indication and Extended rejected NSSAI. - Configuration Update Complete message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by embodiments in this disclosure, the following parameter may be populated together in the Configuration Update Complete message. -- Configuration update complete message identity.

[0260] User equipment (UE) 　　Fig. 19is a block diagram illustrating the main components of the UE 3 (mobile device 3). As shown, the UE 3 includes a transceiver circuit 31 which is operable to transmit signals to and to receive signals from the connected node(s) via one or more antennas 32. Further, the UE 3 may include a user interface 34 for inputting information from outside or outputting information to outside. Although not necessarily shown in the Figure, the UE 3 may have all the usual functionality of a conventional mobile device and this may be provided by any one or any combination of hardware, software and firmware, as appropriate. Software may be pre-installed in the memory and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. A controller 33 controls the operation of the UE 3 in accordance with software stored in a memory 36. The software includes, among other things, an operating system 361 and a communications control module 362 having at least a transceiver control module 3621. The communications control module 362 (using its transceiver control module 3621) is responsible for handling (generating / sending / receiving) signalling and uplink / downlink data packets between the UE 3 and other nodes, such as the (R)AN node 5 and the AMF 10. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a registration request message and associated response messages) relating to access and mobility management procedures (for the UE 3). The controller 33 interworks with one or more Universal Subscriber Identity Module (USIM) 35. If there are multiple USIMs 35 equipped, the controller 33 may activate only one USIM 35 or may activate multiple USIMs 35 at the same time.

[0261] The UE 3 may, for example, support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0262] The UE 3 may, for example, be an item of equipment for production or manufacture and / or an item of energy related machinery (for example equipment or machinery such as: boilers; engines; turbines; solar panels; wind turbines; hydroelectric generators; thermal power generators; nuclear electricity generators; batteries; nuclear systems and / or associated equipment; heavy electrical machinery; pumps including vacuum pumps; compressors; fans; blowers; oil hydraulic equipment; pneumatic equipment; metal working machinery; manipulators; robots and / or their application systems; tools; molds or dies; rolls; conveying equipment; elevating equipment; materials handling equipment; textile machinery; sewing machines; printing and / or related machinery; paper converting machinery; chemical machinery; mining and / or construction machinery and / or related equipment; machinery and / or implements for agriculture, forestry and / or fisheries; safety and / or environment preservation equipment; tractors; precision bearings; chains; gears; power transmission equipment; lubricating equipment; valves; pipe fittings; and / or application systems for any of the previously mentioned equipment or machinery etc.).

[0263] The UE 3 may, for example, be an item of transport equipment (for example transport equipment such as: rolling stocks; motor vehicles; motor cycles; bicycles; trains; buses; carts; rickshaws; ships and other watercraft; aircraft; rockets; satellites; drones; balloons etc.).

[0264] The UE 3 may, for example, be an item of information and communication equipment (for example information and communication equipment such as: electronic computer and related equipment; communication and related equipment; electronic components etc.).

[0265] the UE 3 may, for example, be a refrigerating machine, a refrigerating machine applied product, an item of trade and / or service industry equipment, a vending machine, an automatic service machine, an office machine or equipment, a consumer electronic and electronic appliance (for example a consumer electronic appliance such as: audio equipment; video equipment; a loud speaker; a radio; a television; a microwave oven; a rice cooker; a coffee machine; a dishwasher; a washing machine; a dryer; an electronic fan or related appliance; a cleaner etc.).

[0266] the UE 3 may, for example, be an electrical application system or equipment (for example an electrical application system or equipment such as: an x-ray system; a particle accelerator; radio isotope equipment; sonic equipment; electromagnetic application equipment; electronic power application equipment etc.).

[0267] The UE 3 may, for example, be an electronic lamp, a luminaire, a measuring instrument, an analyzer, a tester, or a surveying or sensing instrument (for example a surveying or sensing instrument such as: a smoke alarm; a human alarm sensor; a motion sensor; a wireless tag etc.), a watch or clock, a laboratory instrument, optical apparatus, medical equipment and / or system, a weapon, an item of cutlery, a hand tool, or the like.

[0268] The UE 3 may, for example, be a wireless-equipped personal digital assistant or related equipment (such as a wireless card or module designed for attachment to or for insertion into another electronic device (for example a personal computer, electrical measuring machine)).

[0269] The UE 3 may be a device or a part of a system that provides applications, services, and solutions described below, as to "internet of things (IoT)", using a variety of wired and / or wireless communication technologies.

[0270] Internet of Things devices (or "things") may be equipped with appropriate electronics, software, sensors, network connectivity, and / or the like, which enable these devices to collect and exchange data with each other and with other communication devices. IoT devices may comprise automated equipment that follow software instructions stored in an internal memory. IoT devices may operate without requiring human supervision or interaction. IoT devices might also remain stationary and / or inactive for a long period of time. IoT devices may be implemented as a part of a (generally) stationary apparatus. IoT devices may also be embedded in non-stationary apparatus (e.g. vehicles) or attached to animals or persons to be monitored / tracked.

[0271] It will be appreciated that IoT technology can be implemented on any communication devices that can connect to a communications network for sending / receiving data, regardless of whether such communication devices are controlled by human input or software instructions stored in memory.

[0272] It will be appreciated that IoT devices are sometimes also referred to as Machine-Type Communication (MTC) devices or Machine-to-Machine (M2M) communication devices or Narrow Band-IoT UE (NB-IoT UE). It will be appreciated that a UE 3 may support one or more IoT or MTC applications.

[0273] The UE 3 may be a smart phone or a wearable device (e.g. smart glasses, a smart watch, a smart ring, or a hearable device).

[0274] The UE 3 may be a car, or a connected car, or an autonomous car, or a vehicle device, or a motorcycle or V2X (Vehicle to Everything) communication module (e.g. Vehicle to Vehicle communication module, Vehicle to Infrastructure communication module, Vehicle to People communication module and Vehicle to Network communication module).

[0275] (R)AN node 　　Fig. 20 is a block diagram illustrating the main components of an exemplary (R)AN node 5, for example a base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G). As shown, the (R)AN node 5 includes a transceiver circuit 51 which is operable to transmit signals to and to receive signals from connected UE(s) 3 via one or more antennas 52 and to transmit signals to and to receive signals from other network nodes (either directly or indirectly) via a network interface 53. A controller 54 controls the operation of the (R)AN node 5 in accordance with software stored in a memory 55. Software may be pre-installed in the memory and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g an RMD), for example. The software includes, among other things, an operating system 551 and a communications control module 552 having at least a transceiver control module 5521.

[0276] The communications control module 552 (using its transceiver control sub-module) is responsible for handling (generating / sending / receiving) signalling between the (R)AN node 5 and other nodes, such as the UE 3, another (R)AN node 5, the AMF 70 and the UPF 72 (e.g. directly or indirectly). The signalling may include, for example, appropriately formatted signalling messages relating to a radio connection and a connection with the core network 7 (for a particular UE 3), and in particular, relating to connection establishment and maintenance (e.g. RRC connection establishment and other RRC messages), NG Application Protocol (NGAP) messages (i.e. messages by N2 reference point) and Xn application protocol (XnAP) messages (i.e. messages by Xn reference point), etc. Such signalling may also include, for example, broadcast information (e.g. Master Information and System information) in a sending case.

[0277] The controller 54 is also configured (by software or hardware) to handle related tasks such as, when implemented, UE mobility estimation and / or moving trajectory estimation.

[0278] The (R)AN node 5 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0279] System overview of (R)AN node 5 based on O-RAN architecture 　　Fig. 21 schematically illustrates a (R)AN node 5 based on O-RAN architecture to which the (R)AN node 5 aspects are applicable.

[0280] The (R)AN node 5 based on O-RAN architecture represents a system overview in which the (R)AN node is split into a Radio Unit (RU) 60, Distributed Unit (DU) 61 and Centralized Unit (CU) 62. In some aspects, each unit may be combined. For example, the RU 60 can be integrated / combined with the DU 61 as an integrated / combined unit, the DU 61 can be integrated / combined with the CU 62 as another integrated / combined unit. Any functionality in the description for a unit (e.g. one of RU 60, DU 61 and CU 62) can be implemented in the integrated / combined unit above. Further, CU 62 can separate into two functional units such as CU Control plane (CP) and CU User plane (UP). The CU CP has a control plane functionality in the (R)AN node 5. The CU UP has a user plane functionality in the (R)AN node 5. Each CU CP is connected to the CU UP via an appropriate interface (such as the so-called "E1" interface and / or the like).

[0281] The UE 3 and a respective serving RU 60 are connected via an appropriate air interface (for example the so-called "Uu" interface and / or the like). Each RU 60 is connected to the DU 61 via an appropriate interface (such as the so-called "Front haul", "Open Front haul", "F1" interface and / or the like). Each DU 61 is connected to the CU 62 via an appropriate interface (such as the so-called "Mid haul", "Open Mid haul", "E2" interface and / or the like). Each CU 62 is also connected to nodes in the core network 7 (such as the so-called core network nodes) via an appropriate interface (such as the so-called "Back haul", "Open Back haul", "N2" / "N3" interface(s) and / or the like). In addition, a user plane part of the DU 61 can also be connected to the core network nodes 7 via an appropriate interface (such as the so-called "N3" interface(s) and / or the like).

[0282] Depending on functionality split among the RU 60, DU 61 and CU 62, each unit provides some of the functionality that is provided by the (R)AN node 5. For example, the RU 60 may provide a functionality to communicate with a UE 3 over air interface, the DU 61 may provide functionalities to support MAC layer and RLC layer, the CU 62 may provide functionalities to support PDCP layer, SDAP layer and RRC layer.

[0283] Radio Unit (RU) 　　Fig. 22 is a block diagram illustrating the main components of an exemplary RU 60, for example a RU part of base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G). As shown, the RU 60 includes a transceiver circuit 601 which is operable to transmit signals to and to receive signals from connected UE(s) 3 via one or more antennas 602 and to transmit signals to and to receive signals from other network nodes or network unit (either directly or indirectly) via a network interface 603. A controller 604 controls the operation of the RU 60 in accordance with software stored in a memory 605. Software may be pre-installed in the memory and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 6051 and a communications control module 6052 having at least a transceiver control module 60521.

[0284] The communications control module 6052 (using its transceiver control sub-module) is responsible for handling (generating / sending / receiving) signalling between the RU 60 and other nodes or units, such as the UE 3, another RU 60 and DU 61 (e.g. directly or indirectly). The signalling may include, for example, appropriately formatted signalling messages relating to a radio connection and a connection with the RU 60 (for a particular UE 3), and in particular, relating to MAC layer and RLC layer.

[0285] The controller 604 is also configured (by software or hardware) to handle related tasks such as, when implemented, UE mobility estimate and / or moving trajectory estimation.

[0286] The RU 60 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0287] As described above, the RU 60 can be integrated / combined with the DU 61 as an integrated / combined unit. Any functionality in the description for the RU 60 can be implemented in the integrated / combined unit above.

[0288] Distributed Unit (DU) 　　Fig. 23 is a block diagram illustrating the main components of an exemplary DU 61, for example a DU part of a base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G). As shown, the apparatus includes a transceiver circuit 611 which is operable to transmit signals to and to receive signals from other nodes or units (including the RU 60) via a network interface 612. A controller 613 controls the operation of the DU 61 in accordance with software stored in a memory 614. Software may be pre-installed in the memory 614 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 6141 and a communications control module 6142 having at least a transceiver control module 61421. The communications control module 6142 (using its transceiver control module 61421 is responsible for handling (generating / sending / receiving) signalling between the DU 61 and other nodes or units, such as the RU 60 and other nodes and units.

[0289] The DU 61 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0290] As described above, the DU 61 can be integrated / combined with the RU 60 or CU 62 as an integrated / combined unit. Any functionality in the description for DU 61 can be implemented in one of the integrated / combined unit above.

[0291] Centralized Unit (CU) 　　Fig. 24 is a block diagram illustrating the main components of an exemplary CU 62, for example a CU part of base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G). As shown, the apparatus includes a transceiver circuit 621 which is operable to transmit signals to and to receive signals from other nodes or units (including the DU 61) via a network interface 622. A controller 623 controls the operation of the CU 62 in accordance with software stored in a memory 624. Software may be pre-installed in the memory 624 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 6241 and a communications control module 6242 having at least a transceiver control module 62421. The communications control module 6242 (using its transceiver control module 62421 is responsible for handling (generating / sending / receiving) signalling between the CU 62 and other nodes or units, such as the DU 61 and other nodes and units.

[0292] The CU 62 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0293] As described above, the CU 62 can be integrated / combined with the DU 61 as an integrated / combined unit. Any functionality in the description for the CU 62 can be implemented in the integrated / combined unit above.

[0294] AMF 　　Fig. 25 is a block diagram illustrating the main components of the AMF 70. As shown, the apparatus includes a transceiver circuit 701 which is operable to transmit signals to and to receive signals from other nodes (including the UE 3) via a network interface 702. A controller 703 controls the operation of the AMF 70 in accordance with software stored in a memory 704. Software may be pre-installed in the memory 704 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7041 and a communications control module 7042 having at least a transceiver control module 70421. The communications control module 7042 (using its transceiver control module 70421 is responsible for handling (generating / sending / receiving) signalling between the AMF 70 and other nodes, such as the UE 3 (e.g. via the (R)AN node 5) and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a registration request message and associated response messages) relating to access and mobility management procedures (for the UE 3).

[0295] The AMF 70 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0296] SMF 　　Fig. 26 is a block diagram illustrating the main components of the SMF 71. As shown, the apparatus includes a transceiver circuit 711 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 712. A controller 713 controls the operation of the SMF 71 in accordance with software stored in a memory 714. Software may be pre-installed in the memory 714 and / or may be downloaded via the telecommunication network or from a removable memory device (RMD), for example. The software includes, among other things, an operating system 7141 and a communications control module 7142 having at least a transceiver control module 71421. The communications control module 7142 (using its transceiver control module 71421 is responsible for handling (generating / sending / receiving) signalling between the SMF 71 and other nodes, such as the UPF 72 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a Hypertext Transfer Protocol (HTTP) restful methods based on the service based interfaces) relating to session management procedures (for the UE 3).

[0297] The SMF 71 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0298] UPF 　　Fig. 27 is a block diagram illustrating the main components of the UPF 72. As shown, the apparatus includes a transceiver circuit 721 which is operable to transmit signals to and to receive signals from other nodes (including the SMF 71) via a network interface 722. A controller 723 controls the operation of the UPF 72 in accordance with software stored in a memory 724. Software may be pre-installed in the memory 724 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7241 and a communications control module 7242 having at least a transceiver control module 72421. The communications control module 7242 (using its transceiver control module 72421 is responsible for handling (generating / sending / receiving) signalling between the UPF 72 and other nodes, such as the SMF 71 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a GPRS Tunneling Protocol (GTP) for User plane) relating to User data handling (for the UE 3).

[0299] The UPF 72 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0300] PCF 　　Fig. 28 is a block diagram illustrating the main components of the PCF 73. As shown, the apparatus includes a transceiver circuit 731 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 732. A controller 733 controls the operation of the PCF 73 in accordance with software stored in a memory 734. Software may be pre-installed in the memory 734 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7341 and a communications control module 7342 having at least a transceiver control module 73421. The communications control module 7342 (using its transceiver control module 73421 is responsible for handling (generating / sending / receiving) signalling between the PCF 73 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to policy management procedures (for the UE 3).

[0301] The PCF 73 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0302] NEF 　　Fig. 29 is a block diagram illustrating the main components of the NEF 74. As shown, the apparatus includes a transceiver circuit 741 which is operable to transmit signals to and to receive signals from other nodes (including the UDM 75) via a network interface 742. A controller 743 controls the operation of the NEF 74 in accordance with software stored in a memory 744. Software may be pre-installed in the memory 744 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7441 and a communications control module 7442 having at least a transceiver control module 74421. The communications control module 7442 (using its transceiver control module 74421 is responsible for handling (generating / sending / receiving) signalling between the NEF 74 and other nodes, such as the UDM 75 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to network exposure function procedures (for the UE 3). 　　The NEF 74 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0303] UDM 　　Fig. 30 is a block diagram illustrating the main components of the UDM 75. As shown, the apparatus includes a transceiver circuit 751 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 752. A controller 753 controls the operation of the UDM 75 in accordance with software stored in a memory 754. Software may be pre-installed in the memory 754 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7541 and a communications control module 7542 having at least a transceiver control module 75421. The communications control module 7542 (using its transceiver control module 75421 is responsible for handling (generating / sending / receiving) signalling between the UDM 75 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the VPLMN of the UE 3 when the UE 3 is roaming-out. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to mobility management procedures (for the UE 3).

[0304] The UDM 75 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0305] NWDAF 　　Fig. 31 is a block diagram illustrating the main components of the NWDAF 76. As shown, the apparatus includes a transceiver circuit 761 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 762. A controller 763 controls the operation of the NWDAF 76 in accordance with the software stored in a memory 764. The Software may be pre-installed in the memory 764 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7641 and a communications control module 7642 having at least a transceiver control module 76421. The communications control module 7642 (using its transceiver control module 76421 is responsible for handling (generating / sending / receiving) signalling between the NWDAF 76 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to network data analytics function procedures (for the UE 3).

[0306] The NWDAF 76 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0307] Application Function (AF) 　　Fig. 32 is a block diagram illustrating the main components of the AF 201. As shown, the apparatus includes a transceiver circuit 2011 which is operable to transmit signals to and to receive signals from other nodes (including the UE 3) via a network interface 2012. A controller 2013 controls the operation of the AF 201 in accordance with software stored in a memory 2014. Software may be pre-installed in the memory 2014 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 20141 and a communications control module 20142 having at least a transceiver control module 201421. The communications control module 20142 (using its transceiver control module 201421 is responsible for handling (generating / sending / receiving) signalling between the AF 201 and other nodes, such as the UE 3 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to policy management procedures (for the UE 3). For example, the AF_EES and the AF_EAS may have same components to the AF 201.

[0308] The AF 201 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0309] OAM 　　Fig. 33 is a block diagram illustrating the main components of the OAM 80. As shown, the apparatus includes a transceiver circuit 801 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 802. A controller 803 controls the operation of the OAM 80 in accordance with the software stored in a memory 804. The Software may be pre-installed in the memory 804 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 8041 and a communications control module 8042 having at least a transceiver control module 80421. The communications control module 8042 (using its transceiver control module 80421 is responsible for handling (generating / sending / receiving) signalling between the OAM 80 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to network data analytics function procedures (for the UE 3).

[0310] The OAM 80 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0311] NRF 　　Fig. 34 is a block diagram illustrating the main components of the NRF 81. As shown, the apparatus includes a transceiver circuit 811 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 812. A controller 813 controls the operation of the NRF 81 in accordance with the software stored in a memory 814. The Software may be pre-installed in the memory 814 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 8141 and a communications control module 8142 having at least a transceiver control module 81421. The communications control module 8142 (using its transceiver control module 81421 is responsible for handling (generating / sending / receiving) signalling between the NRF 81 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to network data analytics function procedures (for the UE 3).

[0312] The NRF 81 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0313] Modifications and Alternatives 　　Detailed aspects have been described above. As those skilled in the art will appreciate, a number of modifications and alternatives can be made to the above aspects whilst still benefiting from the disclosures embodied therein. By way of illustration only a number of these alternatives and modifications will now be described.

[0314] In the above description, the UE 3 and the network apparatus are described for ease of understanding as having a number of discrete modules (such as the communication control modules). Whilst these modules may be provided in this way for certain applications, for example where an existing system has been modified to implement the disclosure, in other applications, for example in systems designed with the inventive features in mind from the outset, these modules may be built into the overall operating system or code and so these modules may not be discernible as discrete entities. These modules may also be implemented in software, hardware, firmware or a mix of these.

[0315] Each controller may comprise any suitable form of processing circuitry including (but not limited to), for example: one or more hardware implemented computer processors; microprocessors; central processing units (CPUs); arithmetic logic units (ALUs); input / output (IO) circuits; internal memories / caches (program and / or data); processing registers; communication buses (e.g. control, data and / or address buses); direct memory access (DMA) functions; hardware or software implemented counters, pointers and / or timers; and / or the like.

[0316] In the above aspects, a number of software modules were described. As those skilled in the art will appreciate, the software modules may be provided in compiled or un-compiled form and may be supplied to the UE 3 and the network apparatus as a signal over a computer network, or on a recording medium. Further, the functionality performed by part or all of this software may be performed using one or more dedicated hardware circuits. However, the use of software modules is preferred as it facilitates the updating of the UE 3 and the network apparatus in order to update their functionalities.

[0317] In the above aspects, a 3GPP radio communications (radio access) technology is used. However, any other radio communications technology (e.g. WLAN, Wi-Fi, WiMAX, Bluetooth, etc.) and other fix line communications technology (e.g. BBF Access, Cable Access, optical access, etc.) may also be used in accordance with the above aspects.

[0318] Items of user equipment might include, for example, communication devices such as mobile telephones, smartphones, user equipment, personal digital assistants, laptop / tablet computers, web browsers, e-book readers and / or the like. Such mobile (or even generally stationary) devices are typically operated by a user, although it is also possible to connect so-called 'Internet of Things' (IoT) devices and similar machine-type communication (MTC) devices to the network. For simplicity, the present application refers to mobile devices (or UEs) in the description but it will be appreciated that the technology described can be implemented on any communication devices (mobile and / or generally stationary) that can connect to a communications network for sending / receiving data, regardless of whether such communication devices are controlled by human input or software instructions stored in memory.

[0319] Various other modifications will be apparent to those skilled in the art and will not be described in further detail here.

[0320] Supplementary notes 　　The whole or part of the example Aspects disclosed above can be described as, but not limited to, the following supplementary notes. (Supplementary note 1) 　　A method of a network node comprising: 　　　　communicating with a NF with Energy Saving State Change; and 　　　　controlling the NF with Energy Saving State Change based on an event rule to detect an event relating to Energy Saving State. (Supplementary note 2) 　　A method of a core network node comprising: 　　sending, to a NEF, a parameter for subscribing to receive energy saving information indicating that an observed or a predicted energy saving metric exceeds or falls below a threshold; and 　　receiving, from the NEF, the energy saving information, 　　wherein the Energy Saving information is generated by NF. (Supplementary note 3) 　　A method of a core network node comprising: 　　communicating with a NF; 　　switching an energy state of the NF between Energy-optimized state and Compute-optimized state, in a case where an attribute of Energy Saving switch to manage or control the energy saving state of the NF is changed. (Supplementary note 4) 　　A method of a core network node comprising: 　　receiving, from a NEF, AF available data including a first parameter relating to Event ID indicating ENERGY_SAVIING; 　　storing the received AF available data including a first parameter relating to Event ID indicating ENERGY_SAVIING; 　　receiving, from a PCF, a second parameter relating to Event ID indicating ENERGY_SAVIING; 　　determining that the first parameter is stored, based on the second parameter; and 　　sending, to the PCF, the stored AF available data. (Supplementary note 5) 　　A network node comprising: 　　　　means for communicating with a NF with Energy Saving State Change; and 　　　　means for controlling the NF with Energy Saving State Change based on an event rule to detect an event relating to Energy Saving State. (Supplementary note 6) 　　A core network node comprising: 　　means for sending, to a NEF, a parameter for subscribing to receive energy saving information indicating that an observed or a predicted energy saving metric exceeds or falls below a threshold; and 　　means for receiving, from the NEF, the energy saving information, 　　wherein the Energy Saving information is generated by NF. (Supplementary note 7) 　　A core network node comprising: 　　means for communicating with a NF; 　　means for switching an energy state of the NF between Energy-optimized state and Compute-optimized state, in a case where an attribute of Energy Saving switch to manage or control the energy saving state of the NF is changed. (Supplementary note 8) 　　A core network node comprising: 　　means for receiving, from a NEF, AF available data including a first parameter relating to Event ID indicating ENERGY_SAVIING; 　　means for storing the received AF available data including a first parameter relating to Event ID indicating ENERGY_SAVIING; 　　means for receiving, from a PCF, a second parameter relating to Event ID indicating ENERGY_SAVIING; 　　means for determining that the first parameter is stored, based on the second parameter; and 　　means for sending, to the PCF, the stored AF available data.

[0321] This application is based upon and claims the benefit of priority from India Patent Application No. 202311074544 filed on November 1, 2023, the disclosure of which is incorporated herein in its entirety by reference.

[0322] 20　　DATA NETWORK 201　　APPLICATION FUNCTION(AF) 2011　　TRANSCEIVER CIRCUIT 2012　　NETWORK INTERFACE 2013　　CONTROLLER 2014　　MEMORY 20141　　OPERATING SYSTEM 20142　　COMMUNICATIONS CONTROL MODULE 201421　　TRANSCEIVER CONTROL MODULE 3　　USER EQUIPMENT(UE) 31　　TRANSCEIVER CIRCUIT 32　　ANTENNA 33　　CONTROLLER 34　　USER INTERFACE 35　　USIM 36　　MEMORY 361　　OPERATING SYSTEM 362　　COMMUNICATIONS CONTROL MODULE 3621　　TRANSCEIVER CONTROL MODULE 5　　gNB 51　　TRANSCEIVER CIRCUIT 52　　ANTENNA 53　　NETWORK INTERFACE 54　　CONTROLLER 55　　MEMORY 551　　OPERATING SYSTEM 552　　COMMUNICATIONS CONTROL MODULE 5521　　TRANSCEIVER CONTROL MODULE 60　　RADIO UNIT(RU) 601　　TRANSCEIVER CIRCUIT 602　　ANTENNA 603　　NETWORK INTERFACE 604　　CONTROLLER 605　　MEMORY 6051　　OPERATING SYSTEM 6052　　COMMUNICATIONS CONTROL MODULE 60521　　TRANSCEIVER CONTROL MODULE 61　　DISTRIBUTED UNIT(DU) 611　　TRANSCEIVER CIRCUIT 612　　NETWORK INTERFACE 613　　CONTROLLER 614　　MEMORY 6141　　OPERATING SYSTEM 6142　　COMMUNICATIONS CONTROL MODULE 61421　　TRANSCEIVER CONTROL MODULE 62　　CENTRALIZED UNIT(CU) 621　　TRANSCEIVER CIRCUIT 622　　NETWORK INTERFACE 623　　CONTROLLER 624　　MEMORY 6241　　OPERATING SYSTEM 6242　　COMMUNICATIONS CONTROL MODULE 62421　　TRANSCEIVER CONTROL MODULE 7　　CORE NETWORK 70　　ACCESS AND MOBILITY FUNCTION(AMF) 701　　TRANSCEIVER CIRCUIT 702　　NETWORK INTERFACE 703　　CONTROLLER 704　　MEMORY 7041　　OPERATING SYSTEM 7042　　COMMUNICATIONS CONTROL MODULE 70421　　TRANSCEIVER CONTROL MODULE 71　　SESSION MANAGEMENT FUNCTION(SMF) 711　　TRANSCEIVER CIRCUIT 712　　NETWORK INTERFACE 713　　CONTROLLER 714　　MEMORY 7141　　OPERATING SYSTEM 7142　　COMMUNICATIONS CONTROL MODULE 71421　　TRANSCEIVER CONTROL MODULE 72　　USER PLANE FUNCTION(UPF) 721　　TRANSCEIVER CIRCUIT 722　　NETWORK INTERFACE 723　　CONTROLLER 724　　MEMORY 7241　　OPERATING SYSTEM 7242　　COMMUNICATIONS CONTROL MODULE 72421　　TRANSCEIVER CONTROL MODULE 73　　POLICY CONTROL FUNCTION(PCF) 731　　TRANSCEIVER CIRCUIT 732　　NETWORK INTERFACE 733　　CONTROLLER 734　　MEMORY 7341　　OPERATING SYSTEM 7342　　COMMUNICATIONS CONTROL MODULE 73421　　TRANSCEIVER CONTROL MODULE 74　　NETWORK DATA ANALYTICS FUNCTION(NWDAF) 741　　TRANSCEIVER CIRCUIT 742　　NETWORK INTERFACE 743　　CONTROLLER 744　　MEMORY 7441　　OPERATING SYSTEM 7442　　COMMUNICATIONS CONTROL MODULE 74421　　TRANSCEIVER CONTROL MODULE 75　　UNIFIED DATA MANAGEMENT FUNCTION(UDM) 751　　TRANSCEIVER CIRCUIT 752　　NETWORK INTERFACE 753　　CONTROLLER 754　　MEMORY 7541　　OPERATING SYSTEM 7542　　COMMUNICATIONS CONTROL MODULE 75421　　TRANSCEIVER CONTROL MODULE 76　　NETWORK DATA ANALYTICS FUNCTION (NWDAF) 761　　TRANSCEIVER CIRCUIT 762　　NETWORK INTERFACE 763　　CONTROLLER 764　　MEMORY 7641　　OPERATING SYSTEM 7642　　COMMUNICATIONS CONTROL MODULE 76421　　TRANSCEIVER CONTROL MODULE 80　　OAM 801　　TRANSCEIVER CIRCUIT 802　　NETWORK INTERFACE 803　　CONTROLLER 804　　MEMORY 8041　　OPERATING SYSTEM 8042　　COMMUNICATIONS CONTROL MODULE 80421　　TRANSCEIVER CONTROL MODULE 81　　NETWORK REPOSITORY FUNCTION(NRF) 801　　TRANSCEIVER CIRCUIT 802　　NETWORK INTERFACE 803　　CONTROLLER 804　　MEMORY 8041　　OPERATING SYSTEM 8042　　COMMUNICATIONS CONTROL MODULE 80421　　TRANSCEIVER CONTROL MODULE

Claims

1. A method of a network node comprising: 　　　　communicating with a NF with Energy Saving State Change; and 　　　　controlling the NF with Energy Saving State Change based on an event rule to detect an event relating to Energy Saving State.

2. A method of a core network node comprising: 　　sending, to a NEF, a parameter for subscribing to receive energy saving information indicating that an observed or a predicted energy saving metric exceeds or falls below a threshold; and 　　receiving, from the NEF, the energy saving information, 　　wherein the Energy Saving information is generated by NF.

3. A method of a core network node comprising: 　　communicating with a NF; 　　switching an energy state of the NF between Energy-optimized state and Compute-optimized state, in a case where an attribute of Energy Saving switch to manage or control the energy saving state of the NF is changed.

4. A method of a core network node comprising: 　　receiving, from a NEF, AF available data including a first parameter relating to Event ID indicating ENERGY_SAVIING; 　　storing the received AF available data including a first parameter relating to Event ID indicating ENERGY_SAVIING; 　　receiving, from a PCF, a second parameter relating to Event ID indicating ENERGY_SAVIING; 　　determining that the first parameter is stored, based on the second parameter; and 　　sending, to the PCF, the stored AF available data.

5. A network node comprising: 　　　　means for communicating with a NF with Energy Saving State Change; and 　　　　means for controlling the NF with Energy Saving State Change based on an event rule to detect an event relating to Energy Saving State.

6. A core network node comprising: 　　means for sending, to a NEF, a parameter for subscribing to receive energy saving information indicating that an observed or a predicted energy saving metric exceeds or falls below a threshold; and 　　means for receiving, from the NEF, the energy saving information, 　　wherein the Energy Saving information is generated by NF.

7. A core network node comprising: 　　means for communicating with a NF; 　　means for switching an energy state of the NF between Energy-optimized state and Compute-optimized state, in a case where an attribute of Energy Saving switch to manage or control the energy saving state of the NF is changed.

8. A core network node comprising: 　　means for receiving, from a NEF, AF available data including a first parameter relating to Event ID indicating ENERGY_SAVIING; 　　means for storing the received AF available data including a first parameter relating to Event ID indicating ENERGY_SAVIING; 　　means for receiving, from a PCF, a second parameter relating to Event ID indicating ENERGY_SAVIING; 　　means for determining that the first parameter is stored, based on the second parameter; and 　　means for sending, to the PCF, the stored AF available data.

Images