Method of user equipment (UE), method of radio access network (RAN) node, method of first core network node, UE, ran node and first core network node

Abstract

An aspect of this disclosure includes a method of a user equipment (UE). The method includes receiving energy supply mix information from a radio access network (RAN) node. The method includes selecting a RAN node with less carbon emission based on the received energy supply mix information.

Description

METHOD OF USER EQUIPMENT (UE), METHOD OF RADIO ACCESS NETWORK (RAN) NODE, METHOD OF FIRST CORE NETWORK NODE, UE, RAN NODE AND FIRST CORE NETWORK NODE

[0001] The present disclosure relates to a method of a user equipment (UE), a method of a radio access network (RAN) node, a method of a first core network node, a UE, a RAN node, a first core network node and etc.

[0002] According to S1-241417

[0010] , based on the condition of the environment (e.g. wind condition, solar power condition, etc.), the energy company may change the energy supply mix for supplying to a 3GPP network on location granularity bases. Such change will result in the energy supply mix to network equipment such as base station, edge computing center, core network nodes and etc. If information associated with the energy supply mix can be shared to PLMN operators, PLMN operators can adjust or optimize the network or service provisioning based on this information for lower carbon emission. For example, PLMN operators may tend to provide the same level of service experience with higher ratio of renewable energy usage with the agreement with 3rd party.

[0003] In addition, according to S1-241407

[0011] , users who are more aware and sensitive toward environment may want to reduce their carbon footprint by choosing renewable energy sources over non-renewable sources for network services, even with compromised service performance. Overall reduction in energy usage and prioritizing usage of renewable energy sources (whenever available) over non-renewable energy sources need to have a coordinated solution at both user and network levels from the perspective of energy saving.

[0004] NPL 1: [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". V17.1.0 (2021-12) NPL 2: [2] 3GPP TS 23.501: "System architecture for the 5G System (5GS)". V18.5.0 (2024-03) NPL 3: [3] 3GPP TS 23.502: "Procedures for the 5G System (5GS)". V18.5.0 (2024-03) NPL 4: [4] 3GPP TS 23.503: "Policy and charging control framework for the 5G System (5GS) Stage 2". V18.5.0 (2024-03) NPL 5: [5] 3GPP TS 23.003: "Numbering, addressing and identification". V18.5.0 (2024-03) NPL 6: [6] 3GPP TS 23.032: "Universal Geographical Area Description (GAD) ". V18.1.0 (2023-09) NPL 7: [7] IETF RFC 5139: https: / / www.rfc-editor.org / rfc / rfc5139 NPL 8: [8] IETF RFC 5580: https: / / www.rfc-editor.org / rfc / rfc5580 NPL 9: [9] 3GPP TS 37.340: "Evolved Universal Terrestrial Radio Access (E-UTRA) and NR Multi-connectivity Stage 2". V18.1.0 (2024-03) NPL 10:

[0010] S1-241417: 3GPP TSG-SA WG1 Meeting #106 Jeju, Korea, 27-31 May 2024 NPL 11:

[0011] S1-241407: 3GPP TSG-SA WG1 Meeting #106 Jeju, Korea, 27-31 May 2024

[0005] However, there are no mechanisms in 3GPP specifications for achieving the following potential service requirement: how to 5G system obtain the information associated with the energy supply mix.

[0006] For example, in some scenarios: 　　 - 3GPP system needs to have a mechanism to select a better network element based on the obtained information associated with the energy supply mix.

[0007] The disclosure has a method of a user equipment (UE), the method comprising receiving energy supply mix information from a radio access network (RAN) node; and selecting a RAN node with less carbon emission based on the received energy supply mix information.

[0008] The disclosure has a method of radio access network (RAN) node, the method comprising receiving energy supply mix information from a core network node; and selecting a core network node with less carbon emission based on the received energy supply mix information.

[0009] The disclosure has a method of a first core network node, the method comprising receiving energy supply mix information from a second core network node; and selecting a second core network node with less carbon emission based on the received energy supply mix information.

[0010] The disclosure has a user equipment (UE) comprising means for receiving energy supply mix information from a radio access network (RAN) node; and means for selecting a RAN node with less carbon emission based on the received energy supply mix information.

[0011] The disclosure has a radio access network (RAN) node comprising means for receiving energy supply mix information from a core network node; and means for selecting a core network node with less carbon emission based on the received energy supply mix information.

[0012] The disclosure has a first core network node comprising means for receiving energy supply mix information from a second core network node; and means for selecting a second core network node with less carbon emission based on the received energy supply mix information.

[0013] Fig. 1 is an overall architecture of a First scenario in a First example of a First Aspect.Fig. 2 is a data structure of a Second scenario in the First example of the First Aspect.Fig. 3 is a data structure of a Third scenario in the First example of the First Aspect.Fig. 4 is a data structure of a Fourth scenario in the First example of the First Aspect.Fig. 5 is a Signaling diagram of a Fifth scenario in the First example of the First Aspect.Fig. 6 is an overall architecture of a First scenario in a Second example of the First Aspect.Fig. 7 is a Signaling diagram of a Fourth scenario in the Second example of the First Aspect.Fig. 8 is a Signaling diagram of a Fifth scenario in the Second example of the First Aspect.Fig. 9 is a Signaling diagram of a Sixth example of the First Aspect.Fig. 10 is a Signaling diagram of a Seventh scenario in the Second example of the First Aspect.Fig. 11 is a Signaling diagram of a Eighth scenario in the Second example of the First Aspect.Fig. 12 is a Signaling diagram of a Nineth scenario in the Second example of the First Aspect.Fig. 13 is a Signaling diagram of a First example of a Second Aspect.Fig. 14 is a Signaling diagram of a Second example of the Second Aspect.Fig. 15 is a Signaling diagram of a Third example of the Second Aspect.Fig. 16 is a Signaling diagram of a Fourth example of the Second Aspect.Fig. 17 is a Signaling diagram of a Fifth example of the Second Aspect.Fig. 18 is a Signaling diagram of a First example of a Third Aspect.Fig. 19 is a Signaling diagram of a Second example of the Third Aspect.Fig. 20 is a Signaling diagram of a Third example of the Third Aspect.Fig. 21 is a diagram illustrating a system overview.Fig. 22 is a block diagram illustrating a UE.Fig. 23 is a block diagram illustrating an (R)AN node.Fig. 24 is a diagram illustrating System overview of (R)AN node based on O-RAN architecture.Fig. 25 is a block diagram illustrating an RU.Fig. 26 is a block diagram illustrating a DU.Fig. 27 is a block diagram illustrating a CU.Fig. 28 is a block diagram illustrating an AMF.Fig. 29 is a block diagram illustrating an SMF.Fig. 30 is a block diagram illustrating a UPF.Fig. 31 is a block diagram illustrating a PCF.Fig. 32 is a block diagram illustrating an NWDAF.Fig. 33 is a block diagram illustrating a UDM.Fig. 34 is a block diagram illustrating an AUSF.Fig. 35 is a block diagram illustrating an AAnF.Fig. 36 is a block diagram illustrating an NRF.Fig. 37 is a block diagram illustrating an NEF.Fig. 38 is a block diagram illustrating a UDR.Fig. 39 is a block diagram illustrating an OAM.Fig. 40 is a block diagram illustrating an AF.

[0014] First Aspect 　　This aspect discloses an architecture and mechanisms to support the energy supply mix information handling in 3GPP network.

[0015] First example of the First Aspect: 　　This example discloses an architecture to support the energy supply mix information handling in 3GPP network by interworking with OAM 8.

[0016] First scenario in First example of the First Aspect: 　　The First scenario in the First example of the First Aspect includes an overall architecture for handling the energy supply mix information by interworking with OAM 8.

[0017] Fig. 1 explains an example of the overall architecture for handling the energy supply mix information by interworking with the OAM 8.

[0018] The overall architecture for handling the energy supply mix information by interworking with OAM 8 as illustrated in Fig. 1 has the following features.

[0019] The Energy supply AF 20101 　　 - The Energy supply AF 20101 in the data network 20 is an Application Function that manages the energy supply mix information per geographical location basis. 　　 - One example, the energy supply mix information may be managed by the energy supply mix information as disclosed in Fig. 2. 　　 - One example, the Energy supply AF 20101 may be located in a power company and has a contract with a PLMN A for energy supply. 　　 - The Energy supply AF 20101 has an interface with the OAM 8 in the PLMN A.

[0020] The Energy monitor AF 20102 　　 - The Energy monitor AF 20102 in the data network 20 is an Application Function that monitors the energy consumption in the PLMN A taking energy supply mix information into account. 　　 - The Energy monitor AF 20102 corrects a consumed energy from the OAM 8 using the Energy fed factor as disclosed in Fig. 3. 　　 - One example, the Energy monitor AF 20102 may be located in a power company and has a contract with a PLMN A for energy supply. 　　 - The Energy monitor AF 20102 has an interface with the OAM 8 in the PLMN A.

[0021] The Energy related architecture in the PLMN A as an example 　　 - The OAM 8 in the PLMN A has interfaces with RAN 5, Core Network nodes in the Core Network 7 and an Energy supply AF 20101 and an Energy monitor AF 20102. 　　 - The PLMN A may have multiple contracts with multiple power company for energy supply to the 3GPP network in the PLMN A. In this case, the OAM 8 has interfaces with multiple Energy supply AF 20101s and multiple Energy monitor AF 20102s.

[0022] Second scenario in First example of the First Aspect: 　　The Second scenario in the First example of the First Aspect includes a list of data elements and a structure of the energy supply mix information as an example.

[0023] The energy supply mix information provides information on the used sources for the supplied energy and their ratio in total generated energy. The information may also include other attributes, such as time or location.

[0024] For example, the energy supply mix information may be provided by the Energy supply AF 20101 to the OAM 8 or the NEF 79.

[0025] For example, the energy supply mix information may be provided by the OAM 8 to the RAN 5 and core network nodes in PLMN A.

[0026] For example, the energy supply mix information may be provided by the NEF 79 to core network nodes in PLMN A.

[0027] For example, the energy supply mix information may be provided by the AMF 70 to the RAN 5.

[0028] The energy supply mix information may comprise at least one of the following data elements: 　　 - Energy supplier ID: The Energy supplier ID identifies the Energy supplier. The Energy supplier ID may be a company name of the Energy supplier, an identifier of the Energy supplier company by the Energy supplier association or the Energy related standard body, or an identifier of the Energy supplier company by 3GPP or cellular network community (Example, GSMA). 　　 - Source of energy: The Source of energy indicates how the supplied energy is generated or how the fed energy is generated from. For example, the Source of energy may be a list of an energy source with a percentage indicating a ratio of an energy out of total fed energy. For example, the Source of energy may be followings (but not limited in the followings): 　　 - Thermal power, A% 　　 - Nuclear power, B% 　　 - Solar power, C% 　　 - Hydroelectric power, D% 　　 - Wind power, E% 　　 - Attributions of Energy source: The Attributions of Energy source indicate attributions of each Energy source in the energy supply mix information. This is an additional parameter for Energy source. For example, The Attributions of Energy source may be one or a combination of the followings: 　　 - Period: The Period indicates the period that the Energy source is available. For example, the Energy source Solar power is available in a period from 10 am to 5 pm in a day. 　　 - Location: The Location indicates a geographical area where the Source of energy is fed. The Location may be expressed with the following form. The Location may be a combination of the following forms. 　　 - Universal Geographical Area Description (GAD) as defined in 3GPP TS 23.032 [6]. 　　 - NMEA format as used by the GPS system. 　　 - A general City name, zip-code. 　　 - Revised Civic Location Format for Presence Information Data Format Location Object as defined in IETF RFC 5139 [7]. 　　 - A location expressed with civic and geospatial location formats as defined in IETF RFC 5580 [8]. 　　 - A list of Tracking Area Identity (TAI), a list of NR Cell Global Identity (NCGI) as defined in the 3GPP TS 23.003 [5]. 　　 - A list of E-UTRAN Cell Global Identifier (ECGI) as defined in the 3GPP TS 23.003 [5]. 　　 - A list of Global Cable Identifier (GCI) as defined in the 3GPP TS 23.003 [5].

[0029] Fig. 2 explains an example of the structure of the energy supply mix information that is used by the Energy supply AF 20101, the OAM 8, Core Network Nodes in the PLMN A and RAN 5.

[0030] Third scenario in First example of the First Aspect: 　　The Third scenario in the First example of the First Aspect includes a list of data elements and a structure of the energy fed factor as an example. The energy fed factor may be expressed with different way. For example, energy fed information, energy consumption factor, energy consumption information, energy consumption, etc.

[0031] The energy fed factor provides a detailed information on which a fed energy has been consumed by a node.

[0032] For example, the energy fed factor may be used by the RAN 5, core network nodes in EPC, core network nodes in 5GC, core network nodes in 6GC to report a consumed energy to the OAM 8.

[0033] For example, the energy fed factor may be used by the OAM 8 to report a consumed energy to the Energy monitor AF 20102.

[0034] For example, the energy fed factor may be used by the RAN 5 to report a consumed energy to the AMF 70.

[0035] For example, the energy fed factor may be used by the core network nodes in EPC, core network nodes in 5GC, core network nodes in 6GC to report a consumed energy to the NEF 79.

[0036] For example, the energy fed factor may be used by the NEF 79 to report a consumed energy to the Energy monitor AF 20102.

[0037] The energy fed factor may be reported per Node, per UE, per Network Slice (S-NSSAI), per PDU Session, per PLMN, per location.

[0038] One example, multiple energy fed factors are used to express a total energy fed to a particular target. For example, if the UE 3 activated a PDU Session with an initial RAN 5 and moved to next RAN 5 due to movement of the UE 3, total energy fed to the UE 3 for the PDU Session may be, at least, a sum of an energy fed factor reported by the initial RAN 5 and another energy fed factor reported by the next RAN 5 for an energy fed by RAN.

[0039] The energy fed factor may comprise at least one of the following data elements: 　　 - Total Energy fed: The Total Energy fed indicates a total energy that has been fed. It may be expressed by a Joule or a Watt, but not limited to them. 　　 - Location: The Location indicate a geographical area where a fed energy was consumed. Refer to the Second scenario in First example of the First Aspect for a possible form of the Location. 　　 - Energy Supplier ID: Refer to the Second scenario in First example of the First Aspect. In addition, if energy being fed is generated by a node itself (For example, solar panels are equipped at the RAN 5 and used for an energy to the RAN 5.), a predefined Energy Supplier ID value may be used. 　　 - Fed energy ratio: The Fed energy ratio indicates a percentage of a fed energy by an Energy Supplier ID out of a total energy been fed. This is an associated data for the Energy Supplier ID. One example, The Fed energy radio may be expressed with a Joule instead of a ratio. Further, the Fed energy ratio has an associated data such as energy source with a percentage. The associated data is detail information on how the fed energy is made of by an energy company indicated by the Energy Supplier ID. For example, the associated data may be followings: 　　 - Thermal power, A% 　　 - Nuclear power, B% 　　 - Solar power, C% 　　 - Hydroelectric power, D% 　　 - Wind power, E%

[0040] Fig. 3 explains an example of the structure of the energy fed factor that is used by the Energy monitor AF 20102, the OAM 8, Core Network Nodes in the PLMN A, the RAN 5 and the UE 3.

[0041] Fourth scenario in First example of the First Aspect: 　　The Fourth scenario in the First example of the First Aspect includes a list of data elements and a structure of the fed energy ratio as an example. The fed energy ratio may be expressed with different way. For example, the fed energy ratio may be expressed with energy fed information, energy consumption factor, energy consumption information, energy consumption, etc.

[0042] The fed energy ratio implies a simplified energy information on which a fed energy to a node. The fed energy ratio is used by the RAN 5, core network nodes in EPC, core network nodes in 5GC, core network nodes in 6GC to indicate a ratio of fed energy to nodes.

[0043] For example, the fed energy ratio may be broadcasted to the UE 3 by the RAN 5 to inform an energy supply mix information that the RAN 5 is fed. Based on this information, the UE 3 may select the best or better cell for less carbon emission.

[0044] For example, the fed energy ratio may be informed from the AMF 70 to the RAN 5 to inform an energy supply mix information that the AMF 70 is fed. Based on this information, the RAN 5 may select the best or better AMF 70 for less carbon emission.

[0045] For example, the fed energy ratio may be informed from a candidate RAN 5 to a source RAN 5 to inform an energy supply mix information that the candidate RAN 5 is fed. Based on this information, the source RAN 5 may select the best or better target RAN 5 for less carbon emission during the Handover.

[0046] The fed energy ratio may comprise at least a list of energy source with a ratio. The fed energy ratio may comprise at least one energy source with a ratio. For example, the fed energy ratio can be as follows: 　　 - Thermal power, A% 　　 - Nuclear power, B% 　　 - Solar power, C% 　　 - Hydroelectric power, D% 　　 - Wind power, E%

[0047] Fig. 4 explains an example of the structure of the fed energy ratio that is used by the UE 3, the RAN 5 and Core Network Nodes in the PLMN A.

[0048] Fifth scenario in First example of the First Aspect: 　　The Fifth scenario in the First example of the First Aspect includes call flows for the following procedures. 　　 - A call flow that the energy supply mix information is distributed from the Energy supply AF 20101 to the RAN 5 and core network nodes in the PLMN A via the OAM 8. 　　 - A call flow that the RAN 5 and core network nodes in the PLMN A report the energy fed factors to the Energy monitor AF 20102 via the OAM 8 after the RAN 5 and core network nodes have monitored an Energy consumption taking the energy supply mix information into account.

[0049] Fig. 5 illustrates an example of call flows for both distribution of the energy supply mix information and reporting of the energy fed factors via the OAM 8.

[0050] The detailed processes of the Fifth scenario in First example of the First Aspect are described below with reference to Fig. 5.

[0051] Step 1. The Energy supply AF 20101 in a data network 20 provides the latest energy supply mix information to the OAM 8. The energy supply mix information is disclosed in the Second scenario in First example of the First Aspect.

[0052] In addition, the Energy supply AF 20101 may also provide at least one of the following pieces of information to the OAM 8: 　　 - Energy monitor AF address: The Energy monitor AF address is the address of the AF that measured energy fed factors are reported to. The Energy monitor AF address may be represented in the form of a FQDN, IPv4 address with a port number or IPv6 address with a port number. 　　 - Reporting condition: The Reporting condition indicates when measured energy fed factors are reported. For example, the Reported condition may be set as every hour, every day, or every time after the PDU Session is released.

[0053] Step 2-1. The latest energy supply mix information is provided to the RAN 5. In addition to the energy supply mix information, the OAM 8 might provide the Reporting condition to the RAN 5. 　　Refer to Step 1 for the Reporting condition in detail.

[0054] Step 2-2. The latest energy supply mix information is provided to the core network node(s). In addition to the energy supply mix information, the OAM 8 might provide the Reporting condition to the core network nodes. 　　Refer to Step 1 for the Reporting condition in detail.

[0055] Note that the UPF 72 in Fig. 5 represents any of core network node(s) in the PLMN including, AMF, SMF, PCF, NEF, NWDAF, UDM, AUSF, AAnF, NRF, NEF, UDR, MME, SGW, PGW, PCRF, IMS nodes, etc. In Fig. 5, core network node(s) is depicted as UPF 72, but it may be AMF, SMF, PCF, NEF, NWDAF, UDM, AUSF, AAnF, NRF, NEF, UDR, MME, SGW, PGW, PCRF, IMS nodes, etc in the PLMN instead of or in addition to UPF 72.

[0056] Step 3. The RAN 5 and core network node(s) monitor an energy consumption taking the energy supply mix information into account. The RAN 5 and core network node(s) monitor an energy consumption based on the energy supply mix information. The energy consumption may be referred to as an energy fed factor, energy fed information, energy consumption factor energy consumption information, etc.

[0057] Step 4. The Reporting condition is met in the RAN 5 or / and core network node(s).

[0058] Step 5-1. The RAN 5 sends the Energy fed report to the OAM 8 including at least a list of Energy fed factors per Node, per UE, per PDU Session, per S-NSSAI, or any combination thereof.

[0059] Step 5-2. The core network node(s) sends the Energy fed report to the OAM 8 including at least a list of Energy fed factors per Node, per UE, per PDU Session, per S-NSSAI, or any combination thereof.

[0060] Step 6. The OAM 8 compiles the received reports in Steps 5-1 and 5-2.

[0061] Step 7. The OAM 8 sends a compiled Energy fed report to the Energy monitor AF 20102 including at least a list of Energy fed factors per Node, per UE, per PDU Session, per S-NSSAI, or any combination thereof.

[0062] Variant 1 of Fifth scenario in First example of the First Aspect: 　　In case that the energy supply mix information is changed, for example a percentage of the Solar power is reduced from 30% to 5% due to a bad weather, the Energy supply AF 20101 sends an updated energy supply mix information to the OAM 8. Then, the Steps 2-1 and 2-2 take place for updating the installed energy supply mix information in both the RAN 5 and core network nodes and the updated energy supply mix information is reflected for the monitoring in Step 3.

[0063] First scenario in Second example of the First Aspect: 　　The First scenario in the Second example of the First Aspect includes an overall architecture for handling the energy supply mix information by interworking with the NEF 79.

[0064] Fig. 6 explains an example of overall architecture for handling the energy supply mix information by interworking with the NEF 79.

[0065] The overall architecture for handling the energy supply mix information by interworking with NEF as illustrated in Fig. 6 has the following features.

[0066] The Energy supply AF 20101 　　 - The Energy supply AF 20101 in the data network 20 is an Application Function that manages the energy supply mix information per geographical location basis. 　　 - One example, the energy supply mix information may be managed by the energy supply mix information as disclosed in Fig. 2. 　　 - One example, the Energy supply AF 20101 may be located in a power company and has a contract with a PLMN A for energy supply. 　　 - The Energy supply AF 20101 has an interface with the NEF 79 in the PLMN A.

[0067] The Energy monitor AF 20102 　　 - The Energy monitor AF 20102 in the data network 20 is an Application Function that monitors the energy consumption in the PLMN A taking energy supply mix information into account. 　　 - The Energy monitor AF 20102 corrects a consumed energy from the NEF 79 using the Energy fed factor as disclosed in Fig. 3. 　　 - One example, the Energy monitor AF 20102 may be located in a power company and has a contract with a PLMN A for energy supply. 　　 - The Energy monitor AF 20102 has an interface with the NEF 79 in the PLMN A.

[0068] The Energy related architecture in the PLMN A as an example 　　 - The NEF 79 in the PLMN A is an interworking node to the Energy supply AF 20101 and the Energy monitor AF 20102 from the Core Network nodes in the PLMN A. 　　 - The NEF 79 in the PLMN A is an interworking node to the Core Network nodes in the PLMN A from the Energy supply AF 20101 and the Energy monitor AF 20102. 　　 - The PLMN A may have multiple contracts with multiple power company for energy supply to the 3GPP network in the PLMN A. In this case, the NEF 79 has interfaces with multiple Energy supply AF 20101s and multiple Energy monitor AF 20102s.

[0069] Second scenario in Second example of the First Aspect: 　　The Second scenario in the Second example of the First Aspect includes the list of data elements and a structure of the energy supply mix information as an example. 　　Refer to Second scenario in First example of the First Aspect for the list of data elements and a structure of the energy supply mix information as an example.

[0070] Third scenario in Second example of the First Aspect: 　　The Third scenario in the Second example of the First Aspect includes the list of data elements and a structure of the energy fed factor as an example. 　　Refer to the Third scenario in First example of the First Aspect for the list of data elements and a structure of the energy fed factor as an example.

[0071] Fourth scenario in Second example of the First Aspect: 　　The Fourth scenario in the Second example of the First Aspect includes a call flow depicting the energy supply mix information distribution from the Energy supply AF 20101 to the UE 3, the RAN 5 and core network nodes in the PLMN A via the NEF 79.

[0072] Note that the AMF 70 in Fig. 7 represents any network node in EPC, any core network node in 5GC and any core network node in 6GC.

[0073] Fig. 7 illustrates an example of call flows for distribution of the energy supply mix information to UE 3, RAN 5 and core network nodes via the NEF 79.

[0074] The detailed processes of the Fourth scenario in the Second example of the First Aspect are described below with reference to Fig. 7.

[0075] Step 1. The NEF 79 sends the Naf_EventExposure_Subscribe message to the Energy supply AF 20101 including Energy source request and location. 　　The following bullets explain each parameter in detail. 　　 - Energy source request: The Energy source request indicates that this service subscription invocation is requesting the Energy sources fed to the PLMN A. 　　 - Location: The Location indicates that a service consumer (e.g. NEF 79) may designate geographical area where the service consumer asks for the energy supply mix information. 　　For example, the NEF 79 may designate the geographical area where the PLMN A covers.

[0076] Step 2. The Energy supply AF 20101 sends the Naf_EventExposure_Subscribe response message to the NEF 79 including the latest energy supply mix information. Refer to the First scenario in the First example of the First Aspect for details of the energy supply mix information.

[0077] Step 3. The core network nodes (represented as the AMF 70 in Fig. 7) send the Nnef_EventExposure_Subscribe message to the NEF 79 including Energy source request and location.

[0078] See Step 1 for each parameter in detail.

[0079] For example, the core network nodes (represented as the AMF 70 in Fig. 7) may designate geographical area where the core network nodes (represented as the AMF 70 in Fig. 7) cover.

[0080] Step 4. The NEF 79 sends the Nnef_EventExposure_Subscribe response message to the core network nodes (represented as the AMF 70 in Fig. 7) including the latest energy supply mix information. Refer to the First scenario in the First example of the First Aspect for details of the energy supply mix information.

[0081] Step 5. The AMF 70 sends the latest energy supply mix information to the RAN 5 in order to install the latest energy supply mix information in RAN 5 using the NGAP Interface management procedures. Refer to the Fig. 8 for details of the procedures.

[0082] Step 6. The RAN 5 and core network nodes monitor an Energy consumption taking the energy supply mix information into account. The RAN 5 and core network nodes monitor an Energy consumption based on the energy supply mix information.

[0083] Variant 1 of Fourth scenario in Second example of the First Aspect: 　　After the Step 2, the Energy supply AF 20101 may at any time send the Naf_EventExposure_notify message to the NEF 79 including the latest energy supply mix information in order to update the energy supply mix information in the RAN 5 and core network nodes in PLMN A. In this case, Steps 3 to 7 may take place when the NEF 79 receives the Naf_EventExposure_notify message from the Energy supply AF 20101.

[0084] Variant 2 of Fourth scenario in Second example of the First Aspect: 　　After the Step 4, the NEF 79 may at any time send the Nnef_EventExposure_notify message to core network nodes in PLMN A including the latest energy supply mix information in order to update the energy supply mix information in the RAN 5 and core network nodes in PLMN A. In this case, Steps 5 to 7 may take place when core network nodes receive the Naf_EventExposure_notify message from the NEF 79.

[0085] Fifth scenario in Second example of the First Aspect: 　　The Fifth scenario in Second example of the First Aspect includes a call flow that the RAN 5 in the PLMN A reports the energy fed factors to the Energy monitor AF 20102 via the NEF 79 after the RAN 5 have monitored an Energy consumption taking the energy supply mix information into account.

[0086] Fig. 8 illustrates an example of call flow that the RAN 5 reports the energy fed factors to the Energy monitor AF 20102 via the NEF 79.

[0087] The detailed processes of the Fifth scenario in Second example of the First Aspect are described below with reference to Fig. 8.

[0088] Step 0. The RAN 5 monitors an Energy consumption taking the energy supply mix information into account based on the procedure in Fig. 7.

[0089] Step 1. The Energy monitor AF 20102 sends a Nnef_EventExposure_Subscribe message to the NEF 79 including at least one of Energy fed report request, Location and Reporting condition.

[0090] The following bullets explain each parameter in detail. 　　 - Energy fed report request: The Energy fed report request indicates that this service subscription invocation is requesting the Energy fed report from all nodes or at least one node in the PLMN A. 　　 - Location: The Location indicates that a service consumer (ex. Energy monitor AF 20102) may designate geographical area where the service consumer asks for the Energy fed report. 　　 - Reporting condition: Refer to Step 1 in Fig. 5.

[0091] Step 2. The NEF 7 sends the Nnef_EventExposure_Subscribe response message to the Energy monitor AF 20102.

[0092] Refer to the First scenario in the First example of the First Aspect for details of the energy supply mix information.

[0093] Step 3. The NEF 79 sends a Namf_EventExposure_Subscribe message to the AMF 70 including at least one of Energy fed report request, Location and Reporting condition. 　　See Step 1 for each parameter in detail.

[0094] Although the Step 3 indicates the Namf_EventExposure_Subscribe message to the AMF 70, the NEF 79 sends any core network nodes with a service that a service producer provides. For example, if the NEF 79 sends this message to the SMF 71, then service invocation may be a Nsmf_EventExposure_Subscribe.

[0095] Step 4. The AMF 70 sends the Namf_EventExposure_Subscribe response message to the NEF 79.

[0096] Although the Step 4 indicates the Namf_EventExposure_Subscribe response message to the NEF 79, any core network nodes, as a service producer, that the service is invoked in Step 3 sends this message to the NEF 79. For example, if the SMF 71 sends this message to the NEF 79, then service invocation response may be a Nsmf_EventExposure_Subscribe response.

[0097] Step 5. The AMF 70 sends an Energy fed report control message to the RAN 5 including at least one of Location and Reporting condition. 　　See Step 1 for each parameter in detail.

[0098] Step 6. The Reporting condition is met in the RAN 5.

[0099] Step 7. The RAN 5 sends an Energy fed report message to the AMF 70 including at least a list of Energy fed factors per Node, per UE, per PDU Session, per S-NSSAI, or any combination thereof.

[0100] Step 8. The AMF 70 sends an Namf_EventExposure_Notify message to the NEF 79 including at least a list of Energy fed factors per Node, per UE, per PDU Session, per S-NSSAI, or any combination thereof.

[0101] Step 9. The NEF 79 sends an Nnef_EventExposure_Notify message to the Energy monitor AF 20102 including at least a list of Energy fed factors per Node, per UE, per PDU Session, per S-NSSAI, or any combination thereof.

[0102] Sixth scenario in Second example of the First Aspect: 　　The Sixth scenario in the Second example of the First Aspect includes a call flow where core network nodes in the PLMN A report the energy fed factors to the Energy monitor AF 20102 via the NEF 79 after the core network nodes have monitored an Energy consumption taking the energy supply mix information into account.

[0103] Note that the AMF 70 in Fig. 9 represents any network node in EPC, any core network nodes in 5GC and any core network nodes in 6GC.

[0104] Fig. 9 illustrates an example of a call flow that core network nodes report the energy fed factors to the Energy monitor AF 20102 via the NEF 79.

[0105] The detailed processes of the Sixth scenario in Second example of the First Aspect are described below with reference to Fig. 9.

[0106] Step 1. Steps 0 to 4 in Fig. 8 take place.

[0107] Step 2. The Reporting condition is met in core network nodes.

[0108] Step 3. Steps 8 to 9 in Fig. 8 take place. 　　Although the Step 8 in Fig. 8 indicates the Namf_EventExposure_Notify message to the NEF 79, any core network node, as a service producer, that the service is invoked in Step 3 in Fig. 8 sends this message to the NEF 79. For example, if the SMF 71 sends this message to the NEF 79, then service invocation response may be a Nsmf_EventExposure_Notify.

[0109] Seventh scenario in Second example of the First Aspect: 　　The Seventh scenario in the Second example of the First Aspect includes call flows between AMF 70 and RAN 5 for exchanging energy supply mix information.

[0110] Fig. 10 illustrates an example of call flow for the NG Setup procedure that support energy supply mix handling.

[0111] The detailed processes of the Seventh scenario in Second example of the First Aspect are described below with reference to Fig. 10.

[0112] Step 0-1. The energy fed factor is installed in RAN 5.

[0113] Step 0-2. The energy fed factor is installed in AMF 70. In addition, AMF 70 may have new energy fed factor for the RAN 5. For example, new energy fed factor for the RAN 5 is received from the NEF 79 by the call flow disclosed in Fig. 7.

[0114] Step 1. The RAN 5 sends the NG Setup Request message to the AMF 70 including Supported TA List, energy supply mix supported by RAN and Current energy fed factor in RAN.

[0115] The following bullets explain each parameter in detail. 　　 - Supported TA List: The Supported TA List indicates the TA(s) that the RAN 5 supports. This information may be digested by the AMF to know geographical area where the RAN 5 covers. The AMF 70 may find that an energy fed factor for RAN 5 based on the received Supported TA List. 　　 - Energy supply mix supported by RAN: The Energy supply mix supported by RAN indicates that the RAN 5 supports the energy supply mix feature. 　　 - Current energy fed factor in RAN: The Current energy fed factor in RAN indicates that the current energy fed factor being installed in the RAN 5.

[0116] Step 2. Upon reception of the NG Setup Request message from the RAN 5 in Step 1, the AMF 70 performs the following processes: 　　 - If the AMF 70 receives the supply mix supported by RAN from the RAN 5 in Step 1, the AMF 70 performs for Energy supply mix handling below. 　　 - Based on the received Supported TA List, the AMF find necessary energy fed factor in RAN for the RAN 5. 　　 - If updating an energy fed factor is needed in the RAN 5 by comparing to the received Current energy fed factor in RAN, the AMF 70 sets the New energy fed factor in RAN in the NG Setup Request message.

[0117] The AMF 70 sends the NG Setup Response message to the RAN 5 including energy supply mix supported by AMF, Current energy fed factor in AMF and New energy fed factor in RAN.

[0118] The following bullets explain each parameter in detail. 　　 - Energy supply mix supported by AMF: The Energy supply mix supported by AMF indicates that the AMF 70 supports the energy supply mix feature. 　　 - Current energy fed factor in AMF: The Current energy fed factor in AMF indicates that the current energy fed factor being installed in the AMF 70. 　　 - New energy fed factor in RAN: the New energy fed factor in RAN indicates new energy fed factor needs to be installed in RAN 5.

[0119] The RAN 5 installs the received New energy fed factor in RAN in the RAN 5.

[0120] Variant 1 of Seventh scenario in Second example of the First Aspect: 　　In Step 1 in Fig. 10, the NG Setup Request message may be a RAN Configuration Update message or an existing NGAP message or a new NGAP message.

[0121] In Step 2 in Fig. 10, the NG Setup Response message may be a RAN Configuration Update Acknowledge message or an existing NGAP message or a new NGAP message.

[0122] Variant 2 of Seventh scenario in Second example of the First Aspect: 　　In one example, at step 1 in Fig. 10 the RAN 5 may include in the NG Setup Request message or in the RAN Configuration Update message to the AMF 70 a simple parameter to indicate that the RAN 5 is partially or fully powered by a renewable energy, e.g. wind energy, hydroelectric energy, solar energy or any other kind of green energy or a combination of them. This parameter may be called 'renewable energy powered' or any other notation for a parameter to indicate that the RAN 5 is partially or fully powered by a renewable energy. It is possible that the RAN 5 includes such an optional indication in the NG Setup Request or RAN Configuration Update messages when the share of the renewable energy used to power the RAN 5 reaches or exceeds certain threshold value (in percentage of the whole energy used to power the RAN 5 for example), which threshold value can be configured in the RAN 5 by the operator or be provided to the RAN 5 by the OAM 8 or by the AMF 70 in a N2 message.

[0123] Similarly, at step 2 in Fig. 10 the AMF 70 may include in the NG Setup Response message to the RAN 5 a simple parameter to indicate that the AMF 70 is partially or fully powered by a renewable energy, e.g. wind energy, hydroelectric energy, solar energy or any other kind of green energy or a combination of them. This parameter may be called 'renewable energy powered' or any other notation for a parameter to indicate that the AMF 70 is partially or fully powered by a renewable energy. It is possible that the AMF 70 includes such an optional indication in the NG Setup Response message when the share of the renewable energy used to power the AMF 70 reaches or exceeds certain threshold value (in percentage of the whole energy used to power the AMF 70 for example), which threshold value can be configured in the AMF 70 by the operator or be provided to the AMF 70 by the OAM 8 or by the AF via the NEF 79.

[0124] Eighth scenario in Second example of the First Aspect: 　　The Eighth scenario in Second example of the First Aspect includes call flows between AMF 70 and RAN 5 for exchanging energy supply mix information.

[0125] Fig. 11 illustrates an example of call flow for the AMF Configuration Update procedure that support energy supply mix handling.

[0126] The detailed processes of the Eighth scenario in Second example of the First Aspect are described below with reference to Fig. 11.

[0127] Step 0. Steps 0-1 and 0-2 in Fig. 10 take place.

[0128] Step 1. The AMF 70 sends the AMF Configuration Update message to the RAN 5 including energy supply mix supported by the AMF 70, Current energy fed factor in the AMF 70 and New energy fed factor in RAN 5.

[0129] Refer to the Step 2 in Fig. 10 for parameter details.

[0130] The RAN 5 installs the received New energy fed factor in the RAN 5.

[0131] Step 2. Upon reception of the AMF Configuration Update message from the AMF 70 in Step 1, The RAN 5 sends the AMF Configuration Update Acknowledge message to the AMF 70 including Supported TA List, energy supply mix supported by the RAN 5 and Current energy fed factor in RAN. Refer to Step 1 in Fig. 3 for parameter details.

[0132] Variant 1 of Eight scenario in Second example of the First Aspect: 　　In one example, at step 2 in Fig. 11 the AMF 70 may include in the AMF Configuration Update message to the RAN 5 a simple parameter to indicate that the AMF 70 is partially or fully powered by a renewable energy, e.g. wind energy, hydroelectric energy, solar energy or any other kind of green energy or a combination of them. This parameter may be called 'renewable energy powered' or any other notation for a parameter to indicate that the AMF 70 is partially or fully powered by a renewable energy. It is possible that the AMF 70 includes such an optional indication in the AMF Configuration Update message when the share of the renewable energy used to power the AMF 70 reaches or exceeds certain threshold value (in percentage of the whole energy used to power the AMF 70 for example), which threshold value can be configured in the AMF 70 by the operator or be provided to the AMF 70 by the OAM 8 or by the AF via the NEF 79.

[0133] Nineth scenario in Second example of the First Aspect: 　　The Nineth scenario in Second example of the First Aspect includes call flows between RAN 5s (RAN 501 and RAN 502) for exchanging energy supply mix information.

[0134] Fig. 12 illustrates an example of call flow for the NG Setup procedure that support energy supply mix handling.

[0135] The detailed processes of the Ninth scenario in Second example of the First Aspect are described below with reference to Fig. 12.

[0136] Step 0-1. The energy fed factor is installed in RAN 501.

[0137] Step 0-2. The energy fed factor is installed in RAN 502.

[0138] Step 1. The RAN 501 sends the XN Setup Request message to the RAN 502 including energy supply mix supported by RAN and Current energy fed factor in RAN.

[0139] Refer to the Step 1 in Fig. 10 for parameter details.

[0140] The RAN 502 stores the received Current energy fed factor in RAN as an energy fed factor for the RAN 501 and may use this information when the RAN 502 selects a target RAN for handover taking a carbon emission into account.

[0141] Step 2. Upon reception of the XN Setup Request message from the RAN 501 in Step 1, the RAN 502 sends the XN Setup Response message to the RAN 501 including energy supply mix supported by RAN and Current energy fed factor in RAN.

[0142] Refer to the Step 1 in Fig. 10 for parameter details.

[0143] The RAN 501 stores the received Current energy fed factor in RAN as an energy fed factor for the RAN 502.

[0144] And may use this information when the RAN 501 selects a target RAN for handover taking a carbon emission into account.

[0145] Variant 1 of Nineth scenario in Second example of the First Aspect: 　　In Step 1 in Fig. 12, the XN Setup Request message may be a NG-RAN Node Configuration Update message or an existing XNAP message or a new XNAP message.

[0146] In Step 2 in Fig. 12, the XN Setup Response message may be a NG-RAN Node Configuration Update Acknowledge message or an existing XNAP message or a new XNAP message.

[0147] Variant 2 of Nineth scenario in Second example of the First Aspect: 　　After Step 2, RAN 501 may use the Current energy fed factor in RAN 502 when the RAN 501 selects a target RAN for handover taking a carbon emission into account.

[0148] Variant 3 of Nineth scenario in Second example of the First Aspect: 　　After Step 1, RAN 502 may use the Current energy fed factor in RAN 501 when the RAN 502 selects a target RAN for handover taking a carbon emission into account.

[0149] Variant 4 of Nineth scenario in Second example of the First Aspect: 　　In one example, at step 1 in Fig. 12 the RAN 501 may include in the Xn Setup Request message to the RAN 502 a simple parameter to indicate that the RAN 501 is partially or fully powered by a renewable energy, e.g. wind energy, hydroelectric energy, solar energy or any other kind of green energy or a combination of them. This parameter may be called 'renewable energy powered' or any other notation for a parameter to indicate that the RAN 501 is partially or fully powered by a renewable energy. It is possible that the RAN 501 includes such an optional indication in the Xn Setup Request message when the share of the renewable energy used to power the RAN 501 reaches or exceeds certain threshold value (in percentage of the whole energy used to power the RAN 501 for example), which threshold value can be configured in the RAN 501 by the operator or be provided to the RAN 501 by the OAM 8 or by the AMF 70 in a N2 message.

[0150] Similarly, at step 2 in Fig. 12 the RAN 502 may include in the Xn Setup Response message to the RAN 501 a simple parameter to indicate that the RAN 502 is partially or fully powered by a renewable energy, e.g. wind energy, hydroelectric energy, solar energy or any other kind of green energy or a combination of them. This parameter may be called 'renewable energy powered' or any other notation for a parameter to indicate that the RAN 502 is partially or fully powered by a renewable energy. It is possible that the RAN 502 includes such an optional indication in the Xn Setup Response message when the share of the renewable energy used to power the RAN 502 reaches or exceeds certain threshold value (in percentage of the whole energy used to power the RAN 502 for example), which threshold value can be configured in the RAN 502 by the operator or be provided to the RAN 502 by the OAM 8 or by the AF via the NEF 79.

[0151] Second Aspect 　　This aspect discloses mechanisms for energy aware cell selection / re-selection by the UE and / or energy aware UE handover between RAN nodes and / or energy aware core network nodes selection in order to reduce the carbon emission in the PLMN for cellular mobile communication. This aspect also discloses mechanisms for energy-aware secondary cell addition / change in case of Carrier Aggregation or Secondary Node addition / modification / change in case of Dual Connectivity.

[0152] First example of the Second Aspect: 　　The First example of the Second Aspect includes a mechanism for the UE 3 to select or re-select a RAN 5 taking an energy fed factor in RAN 5 into account.

[0153] Fig. 13 illustrates an example of call flow for broadcasting the energy fed factor in RAN 5 to the UE 3.

[0154] The detailed processes of the First example of the Second Aspect are described below with reference to Fig. 13.

[0155] Step 0. The energy fed factor is installed in RAN 5.

[0156] The RAN 5 calculates a Fed energy ratio taking energy fed factor into account. The RAN 5 may calculate a Fed energy ratio based on the energy fed factor.

[0157] Refer to the Fourth scenario in the First example of the First Aspect for details of the Fed energy ratio.

[0158] One example, the RAN 5 scores multiple energy fed factors in case where the RAN 5 has multiple energy sources.

[0159] One example, the RAN 5 has an energy fed factor in core network.

[0160] Step 1. The RAN 5 broadcasts a Fed energy ratio over the System Information Block (SIB). The SIB may be referred to as a SIB message, a system information message, etc.

[0161] One example, the RAN 5 may broadcast the Fed energy ratio in RAN 5 and another Fed energy ratio in core network (including AMF 70).

[0162] Step 2. The UE 3 may receive the SIB and consider the Fed energy ratio during the cell selection and cell reselection and the UE 3 may give a priority to a cell powered with less carbon emission(s). The UE 3 may select and / or re-select a RAN 5 providing a cell powered with less carbon emission(s) based on the energy fed factor in the RAN 5 and / or the Fed energy ratio. The UE 3 may select and / or re-select a RAN 5 providing a cell powered with less carbon emission(s) taking an energy fed factor in the RAN 5 into account. The UE 3 may select and / or re-select a RAN 5 providing a cell powered with less carbon emission(s) based on the energy supply mix information. The less carbon emission(s) may be referred to as lower carbon emission(s), low carbon emission(s), etc.

[0163] Variant 1 of the First Example of the Second Aspect: 　　In one example, at step 1 in Fig. 13, the RAN 5 may include in the SIB message a simple parameter (true / false flag or 1 / 0 flag) to indicate that the RAN 5 is partially or fully powered by a renewable energy, e.g. wind energy, hydroelectric energy, solar energy or any other kind of green energy or a combination of them. This parameter may be called 'renewable energy powered' or any other notation for a parameter to indicate that the RAN 5 is partially or fully powered by a renewable energy. It is possible that the RAN 5 includes such an optional indication in the SIB message when the share of the renewable energy used to power the RAN 5 reaches or exceeds certain threshold value (in percentage of the whole energy used to power the RAN 5 for example), which threshold value can be configured in the RAN 5 by the operator or be provided to the RAN 5 by the OAM 8 or by the AMF 70 in a N2 message. Then at step 2, if the 'renewable energy powered' indication is present in the SIB by the RAN 5, the UE may consider that cell with priority for cell selection and reselection.

[0164] Variant 2 of the First Example of the Second Aspect: 　　In one example, in step 1 in Fig. 13, the network also broadcasts attributions of energy sources as defined in Fig. 2. These attributes tell the timing information about the energy sources that will power the cell on a particular day. For example, SIBx will broadcast that a cell is powered from 10 am to 5 pm from solar power, from 5 pm to 10 pm from wind power and from 10 pm to 10 am from thermal power. The SIBx may be referred to as an SIB, a SIB message, a system information message, etc. The network may be RAN 5. The attributions of energy sources may be referred to as information about the attributions of energy sources, information related to the attributions of energy sources, etc.

[0165] When a UE 3 reads and / or receives the information about attributions of energy sources, the UE 3 may show this information to the user of the UE 3 by displaying the information on its screen and the user will be aware about the source of energy of a serving cell through the day. When a UE 3 reads and / or receives the information about attributions of energy sources, the UE 3 may display this information on its screen. This information can also be applicable to a TAI, RAI or PLMN wide. Based on this information, the UE 3 will plan to access the serving cell depending on the source of energy which powered the cell. UE 3 may schedule a time to download movie when the cell is supposed to power by renewable energy resource e.g., solar energy resource. The display of the UE 3 may be referred to as a user interface of the UE 3.

[0166] The user interface of the UE 3 will show energy source icon specific to each power type which is currently powering the serving cell.

[0167] In one example when UE 3 performs manual PLMN selection procedure or manual Closed Subscriber Group (CSG) selection procedure, the UE 3 may show the user a list of PLMNs by displaying it on its screen. For each entry in the list, the UE 3 may display the type of energy powering the cell of the PLMN, along with PLMN ID. In case of CAG cell, the UE 3 may display CAG ID and type of power source powering the CAG cell.

[0168] Variant 3 of the First Example of the Third Aspect: 　　In one example, UE 3 may also support energy-aware cell selection and may indicate support for energy-aware cell selection as UE MM Core Network capability or as a part of UE radio capability (as shown in the Third Aspect).

[0169] In one example, UE 3 is provided with a list of energy-efficient cells for energy-aware cell reselection. Energy-efficient cell for energy-aware cell reselection may be a cell that operates on the same or different frequency, on the same or a different RAN node compared to the initially selected cell. Energy-efficient cell can be configured as a part of a group of cells.

[0170] In one example, Energy-Efficient Cell Group (eeCG) may be configured by O&M 8, based on the energy rating for RAN 5 and other RAN, and a number of cell-specific parameters, such as (predicted) load and RAN sleep modes, system bandwidth, antenna configurations etc. The energy rating for RAN 5 and other RAN may be determined by the energy supply mix explained in the First Aspect.

[0171] UE 3 may, after receiving minimum system information, receive eeCG information in a separate System Information Block (SIB) from RAN 5. This SIB may contain at least one or more the following parameters: 　　 - Id of energy-efficient cell group. 　　 - Carrier frequency, which can be indicated explicitly as ARFCN or implicitly (value 0 corresponds to serving frequency, value 1 indicates the first frequency in SIB4, value 2 corresponds to the second frequency in SIB4, and so on). 　　 - List of cells belonging to the group with the corresponding cell reselection priority value.

[0172] The energy-efficient cell group information may also be provided using dedicated signaling, i.e., (RRC).

[0173] The UE may also derive reselection priorities for energy-aware cell reselection by using NAS provided eeCG information, ensuring energy efficient selection of network elements across RAN and core.

[0174] When energy-aware-based cell reselection information is provided to or received by UE 3, UE 3 derives the appropriate cell information for cell reselection.

[0175] Second example of the Second Aspect: 　　The Second example of the Second Aspect includes a mechanism for renewable energy aware handover.

[0176] Fig. 14 illustrates an example of renewable energy aware target RAN selection in N2 Handover. The target RAN may be expressed as T-RAN, target RAN node, T-RAN node, etc.

[0177] Step 1 to 2. The T-AMF 7002 is reported by the connected RAN nodes which of them is powered (partly or fully) with renewable energy as per Fig. 11 of the Eights scenario in the Second example of the First Aspect. The UE 3 is assumed to be in connected mode via S-RAN 501. The S-RAN may be expressed as source RAN, S-RAN node, source RAN node, etc.

[0178] Step 3. At some stage the S-RAN 501 decides that Handover is required.

[0179] Step 4. The S-RAN 501 sends Handover Request message to the serving S-AMF 7001. The S-AMF may be expressed as source AMF, S-AMF node, source AMF node, etc.

[0180] Step 5. When the S-AMF 7001 cannot serve the UE any longer, the S-AMF 7001 selects the target T-AMF 7002. The T-AMF may be expressed as target AMF, T-AMF node, target AMF node, etc. When the S-AMF 7001 selects the T-AMF 7002, the S-AMF 7001 may request the NRF to give a priority for a target AMF which is partially or fully powered by renewable energy, if available. The source AMF sends Forward Relocation Request message to the target AMF selected by NRF.

[0181] Step 6, The T-AMF 7002 selects a target RAN, e.g. T-RAN 502 as per the requirement in TS23.502 Section 4.9.1.3.3. In selecting the T-RAN 502, the T-AMF 7002 may also consider the power mix of the target RAN, i.e. whether the target RAN is partially or fully powered with renewable energy.

[0182] Step 7. When the T-RAN 502 is selected, the T-AMF 7002 sends the Handover Request message to the T-RAN 502.

[0183] Step 8. The Handover process continues as per 3GPP TS 23.502 [3], Section 4.9.1.3.3.

[0184] Variant 1 of the Second Example of the Second Aspect: 　　In one example in step 5, the source S-AMF 7001 sends the forward relocation request message to a target T-AMF 7002 selected as per the existing procedure or to a default AMF. After the target T-AMF 7002 or the default AMF receives the forward relocation request message, the target T-AMF 7002 or the default AMF may select another target AMF depending on the type of energy powered by the target from the pool of AMFs serving the target NG RAN. For example, the target T-AMF 7002 or the default AMF may choose an AMF which is powered by a renewable energy resource (e.g. solar power or wind power). The T-AMF 7002 or default AMF then forward the Forward Relocation Request message to the selected AMF which then sends Handover Request message to the target T-RAN 502.

[0185] Third example of the Second Aspect: 　　The Third example of the Second Aspect includes a mechanism for the RAN 5 to select or re-select an AMF 70 taking an energy fed factor in AMF 70 into account, i.e., energy aware AMF selection.

[0186] Fig. 15 illustrates an example of call flow for selecting or re-selecting an AMF 70 taking an energy fed factor into account.

[0187] The detailed processes of the Second example of the Second Aspect are described below with reference to Fig. 15.

[0188] Step 0. The energy fed factor in AMF 70 is transferred to RAN 5 based on procedures disclosed by Figs. 10 and 11.

[0189] Note that the RAN 5 may receive multiple energy fed factors from multiple AMFs 70 if the RAN 5 is associated with multiple AMFs 70.

[0190] Step 1. The RAN 5 may receive the energy fed factor in AMF 70 and consider the Fed energy ratio in AMF 70 based on the received energy fed factor in AMF 70 during the AMF selection or re-selection procedure and the RAN 5 may give a priority to AMF 70 powered with less carbon emission(s). The RAN 5 may select and / or re-select a AMF 70 powered with less carbon emission(s) based on the received energy fed factor and / or the Fed energy ratio. The RAN 5 may select and / or re-select a AMF 70 powered with less carbon emission(s) taking an energy fed factor in the AMF 70 into account. The RAN 5 may select and / or re-select a AMF 70 powered with less carbon emission(s) based on the energy supply mix information. The less carbon emission may be referred to as lower carbon emission(s), low carbon emission(s), etc.

[0191] Variant 1 of the Second Example of the Second Aspect: 　　In one example, at step 0 in Fig. 15 the AMF 70 may include in the N2 message to the RAN 5 a simple parameter (true / false flag or 1 / 0 flag) to indicate that the RAN 5 is partially or fully powered by a renewable energy, e.g., wind energy, hydroelectric energy, solar energy or any other kind of green energy or a combination of them. This parameter may be called 'renewable energy powered' or any other notation for a parameter to indicate that the AMF 70 is partially or fully powered by a renewable energy. It is possible that the AMF 70 includes such an optional indication in the N2 message to the RAN 5 when the share of the renewable energy used to power the AMF 70 reaches or exceeds certain threshold value (in percentage of the whole energy used to power the AMF 70 for example), which threshold value can be configured in the AMF 70 by the operator or be provided to the AMF 70 by the OAM 8 or by the AF via the NEF 79. Then at step 1, if the 'renewable energy powered' indication was present in the N2 message to RAN 5, the RAN 5 would consider that information in the AMF selection process giving some level of priority to AMF partly or fully powered by renewable energy.

[0192] Variant 2 of the Second Example of the Second Aspect: 　　In another example, at step 0 in Fig. 15 the AMF 70 may consider the share of the renewable energy used to power the AMF 70 and modify the Weight Factor (e.g. increase the Weight Factor for this AMF 70 if a renewable energy is used to power the AMF 70) so that, as at step 2, AMF 70 is more often selected by the RAN 5 in AMF selection procedure. The increase to the Weight Factor may be proportional to the share of the renewable energy used to power AMF 70, for example.

[0193] Fourth example of the Second Aspect: 　　The Fourth example of the Second Aspect includes a mechanism for the AMF 70 to select or re-select core network nodes, including SMF 71, UPF 72, taking an energy fed factor in a candidate core network node into account.

[0194] Note that the SMF 71 in the Fig. 16 represents any network nodes in EPC, any core network nodes in 5GC and any core network nodes in 6GC.

[0195] Fig. 16 illustrates an example of call flow for selecting or re-selecting a core network node taking an energy fed factor in a candidate core network node into account.

[0196] The detailed processes of the Third example of the Second Aspect are described below with reference to Fig. 16.

[0197] Step 1. The SMF 71 sends an Nnrf_NFManagement_NFRegister message to the NRF 78 including NF type and energy fed factor.

[0198] The following bullets explain each parameter in detail. 　　 - NF type: The NF type indicates a Network Function type. For example, the NF Type may be an SMF. 　　 - energy fed factor: The Current energy fed factor in a service consumer (For example, the SMF 71).

[0199] Although the Fig. 16 illustrates the SMF 71 as the service consumer of the Nnrf_NFManagement_NFRegister service, the service consumer may be any core network entities.

[0200] Step 2. The NRF 78 sends the Nnrf_NFManagement_NFRegister response message to the SMF 71 or any service consumer.

[0201] Step 3. The SMF selection procedure is triggered in the AMF 70. 　　For example, the PDU Session establishment procedure as described in section 4.3.2.2.1 in 3GPP TS 23.502 [3] is triggered.

[0202] Step 4. The AMF 70 sends an Nnrf_NFDiscovery_Request message to the NRF 78 including NF type and Less Carbon emission requested. 　　The following bullets explain each parameter in detail. 　　 - NF type: Refer to Step 1. 　　 - Less Carbon emission requested: The Less Carbon emission requested indicates to the NEF 78 that a network function with Less Carbon emission is requested.

[0203] Step 5. Upon reception of the Nnrf_NFDiscovery_Request message from the AMF 70 including the Less Carbon emission requested, the NRF 78 selects NF instances that has less carbon emission.

[0204] The NEF 78 sends an Nnrf_NFDiscovery_Response message to the AMF 70 including a set of NF instances and energy fed factor per NF instance.

[0205] The following bullets explain each parameter in detail. 　　 - A set of NF instances: A set of NF instances that the AMF 70 can select a NF instance. 　　 - Energy fed factor per NF instance: Energy fed factor per NF instance is an Energy fed factor in a NF instance that are indicated in a set of NF instances.

[0206] When the AMF 70 receives the Nnrf_NFDiscovery_Response message from the NRF 78 including a set of NF instances and energy fed factor per NF instance, the AMF 70 may select and / or re-select a core network entity (an SMF in this example) with less carbon emission based on the energy fed factor per NF instance. The AMF 70 may select and / or re-select a core network entity (an SMF in this example) with less carbon emission based on the energy supply mix information. The less carbon emission(s) may be referred to as lower carbon emission(s), low carbon emission(s), etc.

[0207] Fifth example of the Second Aspect 　　The Fifth example of the Second Aspect includes mechanisms for energy-aware Secondary Node addition / modification / change in case of Dual Connectivity.

[0208] Note that the Dual Connectivity in this example is equally applicable to the multi-connectivity as defined in 3GPP TS 37.340 [9].

[0209] The detailed processes of the Fifth example of the Second Aspect are described below with reference to Fig. 17.

[0210] Step 0. One or more UE 3s may be registered and dual-connected to M-RAN 501 and Secondary RAN - Source (S-RAN-S 502). M-RAN 501 acts as a Master Node for one or more UE 3s. M-RAN may be expressed as Master RAN, M-RAN node, Master RAN node, etc. S-RAN-S 502 acts as a Secondary Node for one or more UE 3s. S-RAN-S may be expressed as Secondary RAN-S, S-RAN-S node, Secondary RAN-S node, Secondary RAN-Source node, etc.

[0211] Step 1. AMF 70, triggered by OAM 8 or some other core network node, may send RAN Configuration Update to M-RAN 501, containing energy efficiency information and energy efficiency configuration regarding the S-RAN-S 502 energy efficiency status (e.g., due to a change in the energy supply mix of S-RAN-S 502). The configuration transfer may also include a list of potential S-RAN-Ts in the area, related to one or more Tracking Areas (TAs). The configuration transfer information may be a completely new IE or may be a new IE that is a part of the existing IE, such as SON Configuration transfer. S-RAN-T acts as a Secondary Node for one or more UE 3s. S-RAN-T may be expressed as Secondary RAN-Target, Secondary RAN-T, S-RAN-T node, Secondary RAN-T node, Secondary RAN-Target node, etc.

[0212] Step 2. The M-RAN 501 sends RAN Configuration Update Acknowledge to the AMF 70.

[0213] Step 3. Triggered by RAN configuration transfer, M-RAN 501 initiates Secondary Node change procedure for each UE 3. If required, before initiating S-RAN-S change, M-RAN 501 may request measurement report on one or more S-RAN-Ts (not depicted in Fig. 17).

[0214] Step 4. The M-RAN 501 sends SN Addition Request to the S-RAN-T 503 including energy supply mix change. The energy supply mix change indicates that this Secondary Node change procedure is trigged due to a change in the energy supply mix for the S-RAN-S 502.

[0215] Step 5. The S-RAN-T 503 sends SN Addition Request acknowledge to the M-RAN 501.

[0216] Step 6. The M-RAN 501 sends SN Release Request to the S-RAN-S 502 including energy supply mix change. The energy supply mix change indicates that this Secondary Node change procedure is trigged due to a change in the energy supply mix for the S-RAN-S 502.

[0217] Step 7. The S-RAN-S 502 sends SN Release Request acknowledge to the M-RAN 501.

[0218] Step 8. Steps 4-16 in 3GPP TS 37.340 [9], Figure 10.5.2-1 take place.

[0219] Variant 1 of Fifth example of the Second Aspect: 　　In Step 3, the M-RAN 501 may initiate the Secondary Node change procedure when the M-RAN 501 receives the energy efficiency information and energy efficiency configuration regarding the S-RAN-S 502 energy efficiency status (e.g. due to a change in the energy supply mix of S-RAN-S 502) from the OAM 8.

[0220] Variant 2 of Fifth example of the Second Aspect: 　　 - In case that S-RAN 502 receives the energy efficiency information and energy efficiency configuration regarding the S-RAN-S 502 energy efficiency status (e.g. due to a change in the energy supply mix of S-RAN-S 502) from the OAM 8, the Secondary Node change procedure may take place with the following changes: 　　 - Steps 1 and 2 are replaced with a RAN Change required message from the S-RAN-S to the M-RAN 501 including energy efficiency information and energy efficiency configuration regarding the S-RAN-S 502 energy efficiency status (e.g. due to a change in the energy supply mix of S-RAN-S 502). 　　 - Steps 6 and 7 are omitted. 　　 - In Step 8, when the M-RAN 501 receives the RRCConnectionReconfigurationComplete message from the UE 3, the M-RAN 501 sends a RAN Change Confirm message to the S-RAN-S 502 to stop user data handling.

[0221] Third Aspect 　　This aspect discloses mechanism of an Energy-aware service.

[0222] The Energy-aware service provides end uses an opportunity to use the best or better energy supply mix for their cellular communication. Once, the end user activates the Energy-aware service, 3GPP system performs dynamic service adjustments at flow level based on energy information with user consent.

[0223] First example of the Third Aspect: 　　The First example of the Third Aspect includes a Registration procedure that supports Energy-aware service.

[0224] Fig. 18 illustrates an example of call flow of the Registration procedure supporting Energy-aware service.

[0225] The detailed processes of the First example of the Third Aspect are described below with reference to Fig. 18.

[0226] Step 0. The UDM 75 holds, in the subscription data, an Energy-aware service profile for UE 3.

[0227] The Energy-aware service profile defines a user profile for the Energy-aware service.

[0228] The Energy-aware service profile may include at least one of the following parameters: 　　 - Energy-aware service status: The Energy-aware service status indicates a status of the Energy-aware service. The Energy-aware service status may have one of the following statuses: 　　 - Subscribed. 　　 - Not subscribed. 　　 - Suspended. 　　 - Applicable only to 4G only, 5G only, 6G only, 4G+5G only or 5G+6G only. 　　 - UE work in a renewal energy resource only (e.g. Solar power, Wind power, etc.) or non-renewable energy resource only (Thermal power, nuclear power) or both renewable and non-renewable energy resource, non-renewable preferred or renewable preferred. If the energy aware service status is set to 'renewable energy resource only', the UDM may contain a validity parameter as well which would define after how long the UE 3 can fall back to a renewable energy resources or mix energy resource. This would allow the operator to consider the time(s) (or period(s)) when the renewable energy is usually not available (e.g. solar energy is not available at nights (or between 7:00PM to 5:00AM) ). 　　 - List of DNNs: The List of DNNs indicates that listed DNNs are subject for the Energy-aware service. If the Energy-aware service profile does not include this parameter, the Energy-aware service is available for any DNNs. 　　 - List of APNs: The List of APNs indicates that listed APNs are subject for the Energy-aware service. If the Energy-aware service profile does not include this parameter, the Energy-aware service is available for any APNs. 　　 - List of S-NSSAIs: The List of S-NSSAIs indicates that listed S-NSSAIs are subject for the Energy-aware service. If the Energy-aware service profile does not include this parameter, the Energy-aware service is available for any S-NSSAIs. 　　 - List of PLMNs: The List of PLMNs indicates that the Energy-aware service is available only in the listed PLMNs. If the Energy-aware service profile does not include this parameter, the Energy-aware service is available in any PLMNs.

[0229] Step 1. A Cell belonging to the RAN 5 (or the RAN 5 in the Cell) broadcasts an Energy-aware service support and the Fed energy ratio over the System Information.

[0230] The following bullets explain each parameter in detail. 　　 - Energy-aware service support: The Energy-aware service support indicates that the RAN 5 or RAN 5 with core network nodes in the core network 7 or the PLMN A supports the Energy-aware service. 　　 - Fed energy ratio: Refer to the Fourth scenario in the First example of the First Aspect for details.

[0231] Step 2. The UE 3 sends the RRC Setup Request message to the RAN 5 including Energy-aware service support. The Energy-aware service support indicates that the UE 3 supports the Energy-aware service.

[0232] Step 3. Upon the reception of the RRC Setup Request message in Step 3, the RAN 5 sends the RRC Setup message, to the UE 3, including the Energy-aware service support and the Fed energy ratio. Refer to Step 1 for parameter details.

[0233] One example, the RAN 5 includes the Energy-aware service support and the Fed energy ratio only if the UE 3 sends the Energy-aware service support in Step 2.

[0234] Step 4. The UE 3 sends the RRC Message number 3 message to the RAN 5 including Energy-aware service support and Dedicated NAS. For Energy-aware service support, refer to Step 1.

[0235] The RAN 5 may refer to the Fed energy ratio for candidate AMFs to select an AMF 70 if not yet selected.

[0236] The Dedicated NAS includes the Registration Request message. The Registration Request message to the AMF 70 includes at least one of User ID, Energy-aware service support and Energy-aware operation requested.

[0237] The following bullets explain each parameter in detail. 　　 - User ID: User ID (e.g., the User ID may be expressed as User Identity) may be a 5G-GUTI, SUCI or SUPI. 　　 - Energy-aware service support: Refer to Step 2. 　　 - Energy-aware operation requested: The Energy-aware operation requested indicates that the UE 3 is requesting the Energy-aware service in PLMN A.

[0238] Step 5. Upon reception of the RRC Message number 3 message from the UE 3, the RAN 5 sends the Initial UE message to the AMF 70 including Energy-aware service support and NAS-PDU. The NAS-PDU includes the Registration Request message that is received in the Dedicated NAS in Step 4.

[0239] Step 6. Upon reception of the Registration Request message in step 5, the AMF 70 sends an Nudm_UECM_Registration Request message to a UDM 75 including at least one of the SUPI, Energy-aware service support, Energy-aware operation requested.

[0240] The following bullets explain each parameter in detail. 　　 - SUPI: Subscription Permanent Identifier, Refer to 3GPP TS 23.003 [5] for details. 　　 - Energy-aware service support: The Energy-aware service support indicates that UE 3 and AMF 70 and core network nodes in the core network 7 or PLMN A support the Energy-aware service. 　　 - Energy-aware operation requested: Refer to Step 4.

[0241] Step 7. Upon reception of the Nudm_UECM_Registration Request message in Step 6, the UDM 75 sends an Nudm_UECM_Registration Response message to the AMF 70. The UDM also sends type of energy subscription allowed (or available) (e.g. renewable energy allowed (or available) or only non-renewable energy allowed (or available) or both renewable and non-renewable energy allowed (or available)) and the validity time related to the 'only a renewable energy allowed (or available)' instruction if available.

[0242] Step 8. After the completion of the Nudm_UECM_Registration service in Steps 6 and 7, the AMF 70 sends an Nudm_SDM_Get Request message to the UDM 75 including at least one of the SUPI, Energy-aware service support, Energy-aware operation requested. Refer to Step 6 for parameter details.

[0243] Step 9. The UDM 75 finds Subscriber data for the UE 3 and sends an Nudm_SDM_Get Response message to the AMF 70 including the Subscriber data for the UE 3. The Subscriber data may include the Energy-aware service profile. Refer to Step 1 for details of the Energy-aware service profile. The UDM also sends type of energy subscription allowed (or available) (e.g. renewable energy allowed (or available) or only non-renewable energy allowed (or available) or both renewable and non-renewable energy allowed (or available)) and the validity time related to the 'only a renewable energy allowed (or available)' instruction if available.

[0244] Step 10. The AMF 70 sends the Registration Accept message to the UE 3 including 5G-GUTI, Energy-aware service allowed (or available). The AMF 70 may send the validity time to the UE 3.

[0245] The following bullets explain each parameter in detail. 　　 - 5G-GUTI: The 5G-GUTI is a temporary user identifier for the UE 3, Refer to 3GPP TS 23.003 [5] for details. 　　 - Energy-aware service allowed: The Energy-aware service allowed (or available) indicates to the UE 3 that requested Energy-aware service in Step 4 is accepted by the PLMN A.

[0246] Step 11. Upon reception of the Registration Accept message, the UE 3 stores the received data in the Registration Accept message in step 10 into non-volatile memory in the UE 3.

[0247] The UE 3 sends the Registration Complete message to the AMF 70.

[0248] Step 12. The UE 3 recognizes (or considers or determines) that Energy-aware service is available (or allowed) in PLMN A since (or based on that) the UE 3 received the Energy-aware service allowed from the AMF 70 in Step 10.

[0249] If the UE receives energy subscription information in the Registration Accept message, then the UE can perform one of the following actions: 　　i) if the energy subscription information indicates renewable energy only or indicates that only renewable energy is allowed (available), then the UE can only access the cell which indicates that it is powered by a renewable resource only. If validity time was included, after expiry of the validity time, the UE 3 may fall-back to non-renewable energy resource.

[0250] ii) if the energy subscription information indicates non-renewable energy only or indicates that only non-renewable energy is allowed (available), then the UE can access the cell which indicates it is powered by non-renewable energy only.

[0251] iii) if the energy subscription information indicates both renewable and non-renewable or indicates that both renewable and non-renewable are allowed (available), then the UE can access cell which indicates that it is powered by either renewable or non-renewable.

[0252] iv) if the energy subscription information indicates renewable energy preferred, then the UE first tries to select a suitable cell which indicates that it is powered by renewable energy resources. If no suitable cell powered by renewable energy resource is found, then the UE selects a suitable cell powered by non-renewable energy sources.

[0253] iv) if the energy subscription information indicates non-renewable energy preferred then the UE first tries to select a suitable cell which indicates that it is powered by non-renewable energy resources. If no suitable cell powered by non-renewable energy resource is found, then the UE selects a suitable cell powered by non-renewable energy sources.

[0254] Variant 1 of First example of the Third Aspect: 　　In one example, the UE can be configured in one of the following energy consumption modes: 　　 - renewable energy resource only: In this energy consumption mode, the UE can access only the cell which indicated that it is powered by renewable energy resource. 　　 - non renewable energy resource only: In this energy consumption mode, the UE can access only the cell which indicated that it is powered by non-renewable energy resource. 　　 - both renewable energy resource and non-renewable energy resource: In this energy consumption state mode the UE can access the cell which indicates the cell is powered either renewable or non-renewable energy resource.

[0255] The sends energy power consumption modes in the registration request message to the AMF 70 which in terms sends it to the UDM 75 as defined above. The UDM 75 based on the energy consumption state value and energy subscription information decides whether the UE is allowed to register on the cell or not. For example, if the UE 3 indicates energy consumption state is renewable energy resource and energy subscription information state indicates the UE 3 is subscribed to only non-renewable energy resource then the UDM 75 will reject the registration procedure. In step 7, the UDM 75 will send Nudm_UECM_Registration Response message or an existing message between the AMF 70 and UDM 75, including an existing Information Element (IE) or a new IE indicating registration failed and further including another information element indicating non-renewable energy resource only allowed. Optionally the UDM 75 includes energy subscription information in the Nudm_UECM_Registration Response message or an existing message between the AMF 70 and UDM 75. When the AMF 70 receives the Nudm_UECM_Registration Request message or the existing message between AMF 70 and the UDM 75, the AMF 70 rejects the Registration procedure indicating in 5GMM cause or in a new IE that registration is allowed for non-renewable energy resource only. If the AMF 70 received the energy subscription information element from the UDM 75, it includes the energy subscription information element in the Registration Reject message. In one example the registration request message is sent security protected (ciphering or integrity or both) after the security procedure is executed between the UE 3 and the network.

[0256] For example, if the UE 3 indicates energy consumption state is renewable energy resource and energy subscription information state indicates the UE 3 is subscribed to renewable energy resource, then the UDM 75 will accept the registration procedure and executes the registration procedure as defined above.

[0257] The UE 3 also includes power consumption mode or UE energy subscription information in an RRC message in an existing IE or as a new IE during an RRC procedure e.g., in the RRC connection request message or RRC setup complete message. Based on the value of the power consumption mode the RAN 5 selects an AMF. If the UE power consumption mode indicates renewable energy resource only then the NG RAN selects the AMF 70 which is powered by renewable energy resource.

[0258] Variant 2 of First example of the Third Aspect: 　　In one example, during an RRC procedure if RAN 5 determines that the serving cell capacity or all cell of the RAN 5 powered by renewable energy resource is running full capacity or getting congested (or full), then the RAN 5 may release the existing RRC connection or reject a RRC connection establishment procedure by sending an existing including an existing information element or a new IE indicating congestion on renewable energy resource and optionally a back off timer. When the UE 3 receives the RRC message the UE 3 does not access a cell powered by renewable energy resources. If the UE 3 receives a back off timer, then the UE 3 start the back off timer with value received in the back off timer. The UE 3 may not retry to access the cell powered by renewable energy resource till the back off timer expires until the access is for an emergency service, or a Mission Priority service or a Mission Critical Service.

[0259] Variant 3 of First example of the Third Aspect: 　　In one example, when a UE 3 wants to disable the energy aware service support, then the UE 3 will initiate registration procedure by sending registration request message which doesn't contain energy aware service support indicator or contains energy aware service support indicator, but energy aware service operation request is set to not requested. On receiving the Registration Request message, the AMF 70 disables the energy aware service support and sends Registration accept message. The AMF 70 also informs the UDM 75 by sending an existing message between the AMF 70 and the UDM 75 and containing IE indicating UE 3 has disabled the energy aware service operation. The AMF 70 may also indicate this to other NF using existing message between the UDM 75 and the NF.

[0260] In case network wants to disable the energy aware service for the UE 3 due to expiry of the subscription related to energy aware service, the UDM 75 sends an existing message to the AMF 70 including an IE or existing IE indicating that the UE energy aware service is disabled or sending a new message between the UDM 75 and the AMF 70. When the AMF 70 receives the message the AMF 70 sends UE Configuration Update message including an IE or in existing IE indicating the UE energy aware service is disabled.

[0261] Second example of the Third Aspect: 　　The Second example of the Third Aspect includes a PDU Session Establishment procedure and Service Request procedure that supports Energy-aware service.

[0262] Fig. 19 illustrates an example of call flow of the PDU Session Establishment procedure and Service Request procedure supporting Energy-aware service.

[0263] The detailed processes of the Second example of the Third Aspect are described below with reference to Fig. 19.

[0264] Step 0. The UE 3 has been registered to the AMF 70.

[0265] Step 1. The UE 3 sends a UL NAS Transport message to the AMF 70 via the RAN 5 including at least one of PDU Session ID, DNN, S-NSSAI, Energy-aware service request, Service level, NAS.

[0266] The following bullets explain each parameter in detail. 　　 - PDU Session ID: The PDU Session ID is an identifier of the PDU Session. 　　 - DNN: The DNN is a Data Network Name that is equivalent to an APN in EPS. The DNN is a reference to a data network. 　　 - S-NSSAI: The S-NSSAI is a Single NSSAI that indicates a network slice. 　　 - Energy-aware service request: The Energy-aware service request indicates that the UE 3 is requesting to adapt Energy-aware service to the PDU Session being requested. In addition, Energy-aware service request may indicate to deactivate Energy-aware service in case the Energy-aware service has been activated on the PDU Session. 　　 - Service level: The Service level indicates a Service level for the Energy-aware service that the UE 3 is requesting to apply to the PDU Session being requested. The Service level may form as ones in the followings as examples: 　　 - Level 0-10, where Level 0 is light contribution for less carbon emission with a little QoS down grade while Level 10 is the highest contribution for less carbon emission with minimum QoS support. 　　 - A list of Compromise-able 5QI: The list of Compromise-able 5QI indicates that the UE 3 can accept down grading QoS for the sake of less carbon emission. 　　 - NAS: The NAS contains the SM NAS message. The SM NAS may be a PDU Session Establishment Request message or Service Request message or any other existing or new SM messages.

[0267] Note that although the Step 1 indicates the PDU Session Establishment Request message in the NAS parameter, Service Request message or any other existing or new SM message may be embedded in the NAS parameter.

[0268] Step 2. The AMF 70 sends an Nsmf_PDUSession_Create Request message to the SMF 71 including at least one of PDU Session ID, DNN, S-NSSAI, Energy-aware service request and PDU Session Establishment Request message.

[0269] Refer to Step 1 for parameter details.

[0270] Step 3. Upon reception of the Nsmf_PDUSession_Create Request message from the AMF 70, the SMF 71 sends the Nsmf_PDUSession_Create response message to the AMF 70.

[0271] Step 4. If the SMF 71 does not have Session Management Subscription data for the UE 3, the SMF 71 may send the Nudm_SDM_Get message to the UDM 75 including SUPI, DNN, S-NSSAI, Energy-aware service request.

[0272] Refer to Step 1 for parameter details.

[0273] Note that Energy-aware service request is set in this message only in case where the UE 3 requested and the AMF 70 and ather core network nodes in the core network 7 support the Energy-aware service.

[0274] Step 5. Upon reception of the Nudm_SDM_Get message from the SMF 71, the UDM 75 sends the Nudm_SDM_Get response message to the SMF 71 including the Session Management Subscription data. The Session Management Subscription data may include the Energy-aware service profile for the UE 3. Refer to Step 0 of Fig. 16 for details of the Energy-aware service profile.

[0275] One example, the UDM 75 provides a part of the Energy-aware service profile effective only to the indicated DNN and S-NSSAI in Step 4.

[0276] Step 6. If the SMF 71 does not have a PCF association, the SMF 71 establishes the PCF association with the PCF 73. The SMF 71 sends an Npcf_SMPolicyControl_Create message to the PCF 73 including at least one of the User ID, DNN, S-NSSAI, Energy-aware service request, Service level. 　　A SUPI of UE 3 is set to the User ID. 　　For detail of DNN, S-NSSAI, Energy-aware service request and Service level, refer to Step 1.

[0277] Step 7. Upon reception of the Npcf_SMPolicyControl_Create message from the SMF 71, the PCF 73 generates a PCC Rule and Energy-aware service policy for the UE 3 and sends an Npcf_SMPolicyControl_Create Response message to the SMF 71 including a generated PCC Rule and a generated Energy-aware service policy. The PCF 73 generates the Energy-aware service policy based on the received Service level in Step 6 and the generated PCC rule in Step 7.

[0278] One example, the PCC rule may include the Energy-aware service policy.

[0279] Step 8. The SMF 71 sends an N4 Session Establishment Request message to the UPF 72 including at least one of the PDU Session ID, DNN, S-NSSAI, QoS Flow, Energy-aware service policy. Upon reception of the N4 Session Establishment Request message, the UPF 72 may install the Energy-aware service policy rule.

[0280] The following bullets explain each parameter in detail. 　　 - PDU Session ID: Refer to Step 1. 　　 - DNN: Refer to Step 1. 　　 - S-NSSAI: Refer to Step 1. 　　 - QoS Flow: The QoS Flow indicates a requested QoS flow for the PDU Session together with Packet detection, enforcement and reporting rules. 　　 - Energy-aware service policy rule: The Energy-aware service policy rule is a poly rule applied to the PDU Session based on the Service level indicated by the UE 3. Depending on the Energy fed factor or Fed energy ratio in the UPF 71 or core network 7, the QoS level vary.

[0281] The UPF 72 uses the received QoS Flow and Energy-aware service policy rule to enforce the Energy-aware service. For example, the UPF 71 decides to execute the Network initiated QoS modification based on Energy-aware service as disclosed in Fig. 19.

[0282] Step 9. After successful resource reservation for the PDU Session and successful installation of the Energy-aware service policy in step 11, the UPF 72 sends an N4 Session Establishment Response message to the SMF 71 including Energy-aware service policy accepted (or available). The Energy-aware service policy accepted (or available) indicates that the Energy-aware service policy has been successfully installed and ready for Energy-aware service is under operation to the PDU Session.

[0283] Step 10. The SMF 71 sends an Namf_Communication_N1N2MessageTransfer message to the AMF 70 including at least one of Energy-aware service accepted, Service level accepted, N1 SM container.

[0284] The following bullets explain each parameter in detail. 　　 - Energy-aware service accepted (or available): The Energy-aware service accepted (or available) indicates that the requested Energy-aware service is accepted (or available) and under the operation. In addition, Energy-aware service accepted (or available) may indicate to deactivate Energy-aware service in case the Energy-aware service has been activated on the PDU Session. 　　 - Service level accepted (or available): The Service level accepted indicates that the Service level indicated by the UE 3 has accepted (or available) and under the operation. 　　 - N2 SM container: The N2 SM container contains an N2 SM message. the N2 SM container may include Energy-aware service policy accepted and Service level accepted. 　　 - N1 SM container: The N1 SM container contains N1 SM message. In this example, the N1 SM container contains a PDU Session Establishment Accept message. One another example, the N1 SM container may contain a Service Request Accept message or any existing or new N1 SM message. Further the PDU Session Establishment Accept message in the N1 SM container may include Energy-aware service policy accepted and Service level accepted.

[0285] Step 11. Upon reception of the Namf_Communication_N1N2MessageTransfer message from the SMF 71, the AMF 70 sends the Downlink NAS Transport message to the UE 3 including NAS. The NAS includes the PDU Session Establishment Accept message.

[0286] The Downlink NAS Transport message is carried by the N2 PDU Session Request message from the AMF 70 to the RAN 5. The N2 PDU Session Request may include an N2 SM information and Energy-aware service policy accepted and Service level accepted. One example, The N2 SM information may contain the Energy-aware service policy accepted and Service level accepted (or available).

[0287] When the RAN 5 receives the Energy-aware service policy accepted and Service level accepted, this information may be used by the RAN 5 for supporting the Energy-aware service.

[0288] One example, the NAS may include a Service Request Accept message or any existing or new N1 SM message.

[0289] The PDU Session Establishment Accept message may include Energy-aware service policy accepted and Service level accepted. Refer to Step 10 for parameter details.

[0290] Upon reception of the PDU Session Establishment Accept message in the UE 3 from the AMF 70, the UE 3 recognizes that the Energy-aware service is accepted and under operational with the designated Service level in Step 1.

[0291] Variant 1 of Second example of the Third Aspect: 　　In Step 11, upon reception of the PDU Session Establishment Accept message in the UE 3 from the AMF 70, the UE 3 in NAS later inform to upper layer in the UE 3 that the requested Energy-aware service is accepted (or available) with the designated Service level. Then the upper layer of the UE 3 may display the requested Energy-aware service is accepted (or available) with the designated Service level to a display of a smart phone so that end user can understand it.

[0292] End user may deactivate the Energy-aware service or change the Service level of the Energy-aware service if a service quality of the PDU Session is lower than expected. In this case, end user can initiate the Energy-aware service control procedure as disclosed in Fig. 19.

[0293] Third example of the Third Aspect: 　　The Third example of the Third Aspect includes a PDU Session modification procedure for the activated Energy-aware service. 　　The PDU Session modification procedure may be activated by end user or by the core network 7 based on the Energy-aware service policy rule installed in the UPF 72.

[0294] Fig. 20 illustrates an example of call flow of the PDU Session modification procedure for the activated Energy-aware service.

[0295] The detailed processes of the Third example of the Third Aspect are described below with reference to Fig. 20.

[0296] Step 0. The UE 3 has been registered to the AMF 70 and the PDU Session has been established with SMF and UPF with Energy-aware service activated.

[0297] UE initiated Energy-aware service control 　　Step 1. UE 3 decides (or considers or determines) to deactivate the Energy-aware service or change the Service level of the Energy-aware service.

[0298] Step 2. The UE 3 sends a UL NAS Transport message to the AMF 70 via the RAN 5 including at least one of PDU Session ID, DNN, S-NSSAI, Energy-aware service request, Service level, NAS.

[0299] The NAS includes the PDU Session modification message.

[0300] Refer to Step 1 in Fig. 19 for parameter details.

[0301] Step 3. The AMF 70 sends an Nsmf_PDUSession_Update message to the SMF 71 including at least one of PDU Session ID, DNN, S-NSSAI, Energy-aware service request and PDU Session modification message.

[0302] Refer to Step 1 in Fig. 19 for parameter details.

[0303] Step 4. Upon reception of the Nsmf_PDUSession_Create Request message from the AMF 70, the SMF 71 sends the Nsmf_PDUSession_Create response message to the AMF 70.

[0304] After Step 4, Step 6 and following steps will follow.

[0305] Network initiated QoS modification based on Energy-aware service.

[0306] Step 5. UPF decides to change a QoS for the PDU Session based on the Energy-aware service policy and inform it to the SMF.

[0307] After Step 5, Step 6 and following steps will follow.

[0308] Step 6. Steps 2 to 2b in section 4.3.3.2 in 3GPP TS 23.502 [3] take place.

[0309] Step 7. The AMF 70 sends the Downlink NAS Transport message to the UE 3 including NAS. The NAS includes the PDU Session modification command message.

[0310] The PDU Session modification command message may include Energy-aware service accepted and Service level accepted. Refer to Step 10 in Fig. 19 for parameter details.

[0311] Step 8. The UE 3 sends the UL NAS Transport message to the AMF 70 including NAS. 　　The NAS includes the PDU Session modification complete message.

[0312] Step 9. Steps 7a to 13 in section 4.3.3.2 in 3GPP TS 23.502 [3] take place.

[0313] Variant 1 of Third example of the Third Aspect: 　　After the Step 9, the UE 3 in NAS later inform to upper layer in the UE 3 that the requested Energy-aware service is deactivated or modified with the designated Service level. Then the upper layer of the UE 3 may display the requested Energy-aware service is accepted with the designated Service level to a display of a smart phone so that end user can understand it.

[0314] System overview 　　Fig. 21 schematically illustrates a telecommunication system 1 for a mobile (cellular or wireless) to which the above aspects are applicable.

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

[0316] 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).

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

[0318] The (R)AN node 5 may be split into control plane function and user plane function. 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 functions are aggregated in both the UE 3 and the (R)AN node 5. This split architecture may be called as 'dual connectivity' or 'Multi connectivity'.

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

[0320] In addition, the (R)AN node 5 can also be referred as an access node for a non-wireless 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).

[0321] 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 logical nodes can be considered as a network function. The network function may be provided to another node by adapting the Service Based Architecture (SBA).

[0322] 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).

[0323] 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).

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

[0325] 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 Data Analytics Function (NWDAF) 74, a Unified Data Management (UDM) 75, a Authentication Server Function (AUSF) 76, a AKMA Anchor Function (AAnF) 77, a Network Repository Function (NRF) 78, a Network Exposure Function (NEF) 79 and a Unified Data Repository (UDR) 7100. 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, PCF 73, AAnF 77, NRF 78, NEF 79 and UDR 7100 for the roaming-out UE 3.

[0326] The OAM 8 includes, amongst others, Operational functions, Administrational functions and Maintenance related functions. The OAM 8 has interfaces with RAN 5, logical nodes in the core network 7 in a PLMN. In addition, the OAM 8 has interfaces to the AF 201 and other entities that are located in the data network 20.

[0327] 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, PCF 73, AAnF 77, NRF 78, NEF 79 and UDR 7100 for the roaming-out UE 3.

[0328] 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 node 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. The data network may include an Application Function (AF) 201.

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

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

[0331] The Control plane of 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 Uu interface may have a layered structure with RRC, PDCP, RLC and MAC sublayers over the physical connection.

[0332] 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 Aspects in this disclosure, 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 Aspects in this disclosure, 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 Aspects in this disclosure, following parameters may be included together in the RRC setup complete message. 　　 -- guami-Type, iab-NodeIndication, idleMeasAvailable, ue-MeasurementsAvailable, mobilityState, ng-5G-S-TMSI-Part2, registeredAMF, selectedPLMN-Identity, s-NSSAI-List , onboardingRequest.

[0333] 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 to provide 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 Aspects in this disclosure, 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 Aspects in this disclosure, 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 Aspects in this disclosure, following parameters 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 Aspects in this disclosure, 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 Aspects in this disclosure, 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 Aspects in this disclosure, 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 Aspects in this disclosure, 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 Aspects in this disclosure, following parameters 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 Aspects in this disclosure, 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 Aspects in this disclosure, 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 Aspects in this disclosure, 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 Aspects in this disclosure, 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 Aspects in this disclosure, following parameters may be populated together in the Configuration Update Complete message. 　　 -- Configuration update complete message identity.

[0334] User equipment (UE) 　　Fig. 22 is 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 (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 70. 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.

[0335] 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).

[0336] 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.).

[0337] 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.).

[0338] 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.).

[0339] 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.).

[0340] 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.).

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

[0342] 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)).

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

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

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

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

[0347] 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). For a wearable device, the UE 3 may be a reduced capability device (RedCap).

[0348] 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).

[0349] (R)AN node 　　Fig. 23 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 (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.

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

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

[0352] 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).

[0353] The RAN 501, the RAN 502, M-RAN 501, T-RAN 502, S-RAN-S 502 and S-RAN-T 503 may have same components to the (R)AN node 5. The (R)AN node 5 may be expressed as a RAN node, RAN, (R)AN etc.

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

[0355] 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).

[0356] 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 via an appropriate interface (such as the so-called "N3" interface(s) and / or the like).

[0357] 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 functionalities to communicate with a UE 3 (e.g., the Network Relay UE 300) 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.

[0358] Radio Unit (RU) 　　Fig. 25 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 (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.

[0359] 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 (e.g., the Network Relay UE 300)), and in particular, relating to MAC layer and RLC layer.

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

[0361] 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).

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

[0363] Distributed Unit (DU) 　　Fig. 26 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 (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.

[0364] 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).

[0365] As described above, the RU 60 can be integrated / combined with the DU 61 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.

[0366] Centralized Unit (CU) 　　Fig. 27 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 (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.

[0367] 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).

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

[0369] AMF 　　Fig. 28 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 (e.g., the Network Relay UE 300 and the UE 3), the NSSF 76) 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 (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).

[0370] 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). The S-AMF 7001 and T-AMF 7002 may have same components to the AMF 70.

[0371] SMF 　　Fig. 29 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 data storage device (e.g. 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 AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 (e.g., the Network Relay UE 300 and 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).

[0372] 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).

[0373] UPF 　　Fig. 30 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 (e.g., the Network Relay UE 300 and 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).

[0374] 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).

[0375] PCF 　　Fig. 31 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 (e.g., the Network Relay UE 300 and 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).

[0376] 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).

[0377] NWDAF 　　Fig. 32 is a block diagram illustrating the main components of the NWDAF 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 AMF 70 and the UDM 75) via a network interface 742. A controller 743 controls the operation of the NWDAF 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 NWDAF 74 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).

[0378] The NWDAF 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).

[0379] UDM 　　Fig. 33 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 (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 (e.g., the Network Relay UE 300 and 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).

[0380] 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).

[0381] AUSF 　　Fig. 34 is a block diagram illustrating the main components of the AUSF 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 AUSF 76 in accordance with software stored in a memory 764. 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 (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 AUSF 76 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).

[0382] The AUSF 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).

[0383] AAnF 　　Fig. 35 is a block diagram illustrating the main components of the AAnF 77. As shown, the apparatus includes a transceiver circuit 771 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 772. A controller 773 controls the operation of the AAnF 77 in accordance with the software stored in a memory 774. The Software may be pre-installed in the memory 774 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 7741 and a communications control module 7742 having at least a transceiver control module 77421. The communications control module 7742 (using its transceiver control module 77421 is responsible for handling (generating / sending / receiving) signalling between the AAnF 77 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).

[0384] The AAnF 77 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).

[0385] NRF 　　Fig. 36 is a block diagram illustrating the main components of the NRF 78. As shown, the apparatus includes a transceiver circuit 781 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 782. A controller 783 controls the operation of the NRF 78 in accordance with the software stored in a memory 784. The Software may be pre-installed in the memory 784 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 7841 and a communications control module 7842 having at least a transceiver control module 78421. The communications control module 7842 (using its transceiver control module 78421 is responsible for handling (generating / sending / receiving) signalling between the NRF 78 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).

[0386] The NRF 78 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).

[0387] NEF 　　Fig. 37 is a block diagram illustrating the main components of the NEF 79. As shown, the apparatus includes a transceiver circuit 791 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 792. A controller 793 controls the operation of the NEF 79 in accordance with the software stored in a memory 794. The Software may be pre-installed in the memory 794 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 7941 and a communications control module 7942 having at least a transceiver control module 79421. The communications control module 7942 (using its transceiver control module 79421 is responsible for handling (generating / sending / receiving) signalling between the NEF 79 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).

[0388] The NEF 79 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).

[0389] UDR 　　Fig. 38 is a block diagram illustrating the main components of the UDR 7100. As shown, the apparatus includes a transceiver circuit 7101 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 7102. A controller 7103 controls the operation of the UDR 7100 in accordance with the software stored in a memory 7104. The Software may be pre-installed in the memory 7104 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 71041 and a communications control module 71042 having at least a transceiver control module 710421. The communications control module 71042 (using its transceiver control module 710421 is responsible for handling (generating / sending / receiving) signalling between the UDR 7100 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).

[0390] The UDR 7100 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).

[0391] OAM 　　Fig. 39 is a block diagram illustrating the main components of the OAM 8. As shown, the apparatus includes a transceiver circuit 811 which is operable to transmit signals to and to receive signals from other nodes via a network interface 8012. A controller 813 controls the operation of the OAM 8 in accordance with software stored in a memory 814. 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 OAM 8 and other nodes. 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).

[0392] The OAM 8 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).

[0393] AF 　　Fig. 40 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 (e.g., the Network Relay UE 300 and 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).

[0394] 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).

[0395] The Energy monitor AF 20102 and Energy supply AF 20101 may have same components to the AF 201.

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

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

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

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

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

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

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

[0403] As will be appreciated by one of skill in the art, the present disclosure may be embodied as a method, and system. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, a software embodiment or an embodiment combining software and hardware aspects.

[0404] It will be understood that each block of the block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general-purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a plurality of microprocessors, one or more microprocessors, or any other such configuration.

[0405] The methods or algorithms described in connection with the examples disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC.

[0406] The previous description of the disclosed examples is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to these examples will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other examples without departing from the spirit or scope of the disclosure. Thus, the present disclosure is not intended to be limited to the examples shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0407] While the disclosure has been particularly shown and described with reference to exemplary Aspects thereof, the disclosure is not limited to these Aspects. It will be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present disclosure as defined by this document. For example, the Aspects above are not limited to 5GS, and the Aspects are also applicable to communication system other than 5GS (e.g., 6G system, 5G beyond system).

[0408] Supplementary notes 　　The whole or part of the example Aspects disclosed above can be described as, but not limited to, the following supplementary notes. 　　<First Supplementary notes> 　　(Supplementary Note A1) 　　A method of a network node, the method comprising: 　　receiving, from a data network via a communication node, energy supply mix information; and 　　sending, to the data network via the communication node, energy fed factors based on monitoring energy consumption based on the energy supply mix information. 　　(Supplementary Note A2) 　　The method according to supplementary note A1, the method comprising: 　　monitoring the energy consumption based on the energy supply mix information. 　　(Supplementary Note A3) 　　The method according to supplementary note A1 or A2, wherein the communication node is an Operations, Administration, and Maintenance (OAM) node. 　　(Supplementary Note A4) 　　The method according to any one of supplementary notes A1-A3, wherein the network node is a radio access network (RAN) node or a core network node. 　　(Supplementary Note A5) 　　A method of a network node, the method comprising: 　　receiving, from a data network via a communication node, energy supply mix information; and 　　monitoring energy consumption based on the energy supply mix information. 　　(Supplementary Note A6) 　　The method according to supplementary note A5, comprising:　　 　　sending, to the data network via the communication node, energy fed factors based on the monitoring the energy consumption based on the energy supply mix information. 　　(Supplementary Note A7) 　　The method according to supplementary note A5 or A6, wherein the communication node is a Network Exposure Function (NEF) node. 　　(Supplementary Note A8) 　　The method according to any one of supplementary notes A5-A7, wherein the network node is a radio access network (RAN) node or a core network node. 　　(Supplementary Note A9) 　　A network node comprising: 　　means for receiving, from a data network via a communication node, energy supply mix information; and 　　means for sending, to the data network via the communication node, energy fed factors based on monitoring energy consumption based on the energy supply mix information. 　　(Supplementary Note A10) 　　The network node according to supplementary note A9, comprising: 　　means for monitoring the energy consumption based on the energy supply mix information. 　　(Supplementary Note A11) 　　The network node according to supplementary note A9 or A10, wherein the communication node is an Operations, Administration, and Maintenance (OAM) node. 　　(Supplementary Note A12) 　　The network node according to any one of supplementary notes A9-A11, wherein the network node is a radio access network (RAN) node or a core network node. 　　(Supplementary Note A13) 　　A network node comprising: 　　means for receiving, from a data network via a communication node, energy supply mix information; and 　　means for monitoring energy consumption based on the energy supply mix information. 　　(Supplementary Note A14) 　　The network node according to supplementary note A13, comprising: 　　means for sending, to the data network via the communication node, energy fed factors based on the monitored energy consumption based on the energy supply mix information. 　　(Supplementary Note A15) 　　The network node according to supplementary note A13 or A14, wherein the communication node is a Network Exposure Function (NEF) node. 　　(Supplementary Note A16) 　　The network node according to any one of supplementary notes A13-A15, wherein the network node is a radio access network (RAN) node or a core network node. 　　　　<Second Supplementary notes> 　　(Supplementary Note B1) 　　A method of a user equipment (UE), the method comprising: 　　receiving energy supply mix information from a radio access network (RAN) node; and 　　selecting a RAN node with less carbon emission based on the received energy supply mix information. 　　(Supplementary Note B2) 　　A method of radio access network (RAN) node, the method comprising: 　　receiving energy supply mix information from a core network node; and 　　selecting a core network node with less carbon emission based on the received energy supply mix information. 　　(Supplementary Note B3) 　　The method according to supplementary note B2, wherein the core network node is a Access and Mobility Management Function (AMF) node. 　　(Supplementary Note B4) 　　A method of a first core network node, the method comprising: 　　receiving energy supply mix information from a second core network node; and 　　selecting a second core network node with less carbon emission based on the received energy supply mix information. 　　(Supplementary Note B5) 　　The method according to supplementary note B4, wherein the first core network node is a Access and Mobility Management Function (AMF) node. 　　(Supplementary Note B6) 　　The method according to supplementary note B5, wherein the second core network node is a Session Management Function (SMF) node. 　　(Supplementary Note B7) 　　A user equipment (UE) comprising: 　　means for receiving energy supply mix information from a radio access network (RAN) node; and 　　means for selecting a RAN node with less carbon emission based on the received energy supply mix information. 　　(Supplementary Note B8) 　　A radio access network (RAN) node comprising: 　　means for receiving energy supply mix information from a core network node; and 　　means for selecting a core network node with less carbon emission based on the received energy supply mix information. 　　(Supplementary Note B9) 　　The RAN node according to supplementary note B8, wherein the core network node is a Access and Mobility Management Function (AMF) node. 　　(Supplementary Note B10) 　　A first core network node comprising: 　　means for receiving energy supply mix information from a second core network node; and 　　means for selecting a second core network node with less carbon emission based on the received energy supply mix information. 　　(Supplementary Note B11) 　　The first core network node according to supplementary note B10, wherein the first core network node is a Access and Mobility Management Function (AMF) node. 　　(Supplementary Note B12) 　　The first core network node according to supplementary note B11, wherein the second core network node is a Session Management Function (SMF) node. 　　<Third Supplementary notes> 　　(Supplementary Note C1) A method of a User Equipment (UE) comprising: 　　sending, to a core network node, first information and second information, 　　wherein the first information indicates that the UE supports the Energy-aware service, and 　　wherein the second information indicates that an Energy-aware operation is requested; 　　receiving, from the core network node, third information in a case where the UE send the first information and the second information to the core network node, 　　wherein the third information indicates that the Energy-aware operation for the UE is accepted. 　　(Supplementary Note C2) The method of the UE according to supplementary note C1, further comprising: 　　receiving, from the core network node, fourth information in a case where the UE send the first information and the second information to the core network node, 　　wherein the fourth information indicates energy resource information of the Energy-aware service that is applied to the UE. 　　(Supplementary Note C3) The method of the UE according to supplementary note C1, further comprising: 　　receiving, from the core network node, fifth information in a case where the UE send the first information and the second information to the core network node, 　　wherein the fifth information indicates a validity time when the Energy-aware service is applied to the UE. 　　(Supplementary Note C4) A method of a core network node comprising: 　　receiving, from a user equipment (UE), first information and second information, 　　wherein the first information indicates that the UE supports the Energy-aware service, and 　　wherein the second information indicates that an Energy-aware operation is requested; 　　sending, to an UDM, the first information and the second information; 　　receiving, from the UDM, third information, 　　wherein the third information indicates a status of the Energy-aware service of the UE; and 　　sending, to the UE, fourth information in a case where the status of the third information is subscribed, 　　wherein the fourth information indicates that the Energy-aware operation for the UE is accepted. 　　(Supplementary Note C5) The method of the core network node according to supplementary note C4 further comprising: 　　sending, to the UE, fifth information in a case where the UE send the first information and the second information to the core network node, 　　wherein the fifth information indicates energy resource information of the Energy-aware service that is applied to the UE. 　　(Supplementary Note C6) The method of the core network node according to Supplementary note C4 further comprising: 　　sending, to the UE, sixth information in a case where the UE send the first information and the second information to the core network node, 　　wherein the sixth information indicates a validity time when the Energy-aware service is applied to the UE.

[0409] This application claims priority based on Indian patent application No. 202411053482 filed on July 12, 2024, the entire disclosure of which is incorporated herein.

[0410] 20　　DATA NETWORK 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　　RADIO ACCESS NETWORK (RAN) 501　　S-RAN 502　　T-RAN 503　　S-RAN-T 51　　TRANSCEIVER CIRCUIT 52　　ANTENNA 53　　NETWORK INTERFACE 54　　CONTROLLER 55　　MEMORY 551　　OPERATING SYSTEM 552　　COMMUNICATIONS CONTROL MODULE 5521　　TRANSCEIVER CONTROL MODULE 60　　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　　DU 611　　TRANSCEIVER CIRCUIT 612　　NETWORK INTERFACE 613　　CONTROLLER 614　　MEMORY 6141　　OPERATING SYSTEM 6142　　COMMUNICATIONS CONTROL MODULE 61421　　TRANSCEIVER CONTROL MODULE 62　　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 MANAGEMENT FUNCTION (AMF) 7001　　S-AMF 7002　　T-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 (UDM) 751　　TRANSCEIVER CIRCUIT 752　　NETWORK INTERFACE 753　　CONTROLLER 754　　MEMORY 7541　　OPERATING SYSTEM 7542　　COMMUNICATIONS CONTROL MODULE 75421　　TRANSCEIVER CONTROL MODULE 76　　AUTHENTICATION SERVER FUNCTION (AUSF) 761　　TRANSCEIVER CIRCUIT 762　　NETWORK INTERFACE 763　　CONTROLLER 764　　MEMORY 7641　　OPERATING SYSTEM 7642　　COMMUNICATIONS CONTROL MODULE 76421　　TRANSCEIVER CONTROL MODULE 77　　AKMA ANCHOR FUNCTION (AAnF) 771　　TRANSCEIVER CIRCUIT 772　　NETWORK INTERFACE 773　　CONTROLLER 774　　MEMORY 7741　　OPERATING SYSTEM 7742　　COMMUNICATIONS CONTROL MODULE 77421　　TRANSCEIVER CONTROL MODULE 78　　NETWORK REPOSITORY FUNCTION (NRF) 781　　TRANSCEIVER CIRCUIT 782　　NETWORK INTERFACE 783　　CONTROLLER 784　　MEMORY 7841　　OPERATING SYSTEM 7842　　COMMUNICATIONS CONTROL MODULE 78421　　TRANSCEIVER CONTROL MODULE 79　　NETWORK EXPOSURE FUNCTION (NEF) 791　　TRANSCEIVER CIRCUIT 792　　NETWORK INTERFACE 793　　CONTROLLER 794　　MEMORY 7941　　OPERATING SYSTEM 7942　　COMMUNICATIONS CONTROL MODULE 79421　　TRANSCEIVER CONTROL MODULE 7100　　UNIFIED DATA REPOSITORY (UDR) 7101　　TRANSCEIVER CIRCUIT 7102　　NETWORK INTERFACE 7103　　CONTROLLER 7104　　MEMORY 71041　　OPERATING SYSTEM 71042　　COMMUNICATIONS CONTROL MODULE 710421　　TRANSCEIVER CONTROL MODULE 8　　OPERATIONS, ADMINISTRATION, AND MAINTENANCE (OAM) 811　　TRANSCEIVER CIRCUIT 812　　NETWORK INTERFACE 813　　CONTROLLER 814　　MEMORY 8141　　OPERATING SYSTEM 8142　　COMMUNICATIONS CONTROL MODULE 81421　　TRANSCEIVER CONTROL MODULE 201　　APPLICATION FUNCTION (AF) 20101 ENERGY SUPPLY AF 20102 ENERGY MONITOR AF 2011　　TRANSCEIVER CIRCUIT 2012　　NETWORK INTERFACE 2013　　CONTROLLER 2014　　MEMORY 20141　　OPERATING SYSTEM 20142　　COMMUNICATIONS CONTROL MODULE 201421　　TRANSCEIVER CONTROL MODULE

Claims

A method of a user equipment (UE), the method comprising:　　receiving energy supply mix information from a radio access network (RAN) node; and　　selecting a RAN node with less carbon emission based on the received energy supply mix information.A method of radio access network (RAN) node, the method comprising:　　receiving energy supply mix information from a core network node; and　　selecting a core network node with less carbon emission based on the received energy supply mix information.The method according to claim 2, wherein the core network node is a Access and Mobility Management Function (AMF) node.A method of a first core network node, the method comprising:　　receiving energy supply mix information from a second core network node; and　　selecting a second core network node with less carbon emission based on the received energy supply mix information.The method according to claim 4, wherein the first core network node is a Access and Mobility Management Function (AMF) node.The method according to claim 5, wherein the second core network node is a Session Management Function (SMF) node.A user equipment (UE) comprising:　　means for receiving energy supply mix information from a radio access network (RAN) node; and　　means for selecting a RAN node with less carbon emission based on the received energy supply mix information.A radio access network (RAN) node comprising:　　means for receiving energy supply mix information from a core network node; and　　means for selecting a core network node with less carbon emission based on the received energy supply mix information.The RAN node according to claim 8, wherein the core network node is a Access and Mobility Management Function (AMF) node.A first core network node comprising:　　means for receiving energy supply mix information from a second core network node; and　　means for selecting a second core network node with less carbon emission based on the received energy supply mix information.The first core network node according to claim 10, wherein the first core network node is a Access and Mobility Management Function (AMF) node.The first core network node according to claim 11, wherein the second core network node is a Session Management Function (SMF) node.

Images