WO2025211814A1 - Method and device for energy-based network slice replacement - Google Patents

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. Provided is a method performed by a policy control function (PCF) entity in a wireless communication system. The method may comprise the steps of: transmitting, to a network entity related to energy, a first message for requesting information related to energy of pieces of single-network slice selection assistance information (S-NSSAI); receiving, from the network entity, a second message including the information related to the energy in response to the first message; and transmitting, to an access and mobility management function (AMF) entity, a third message including information about first S-NSSAI to be replaced among the pieces of S-NSSAI on the basis of the information related to the energy.

Description

Method and device for energy-based network slice replacement

The present disclosure relates to a wireless communication system or a mobile communication system. Specifically, it relates to a method and device for energy-based network slice replacement in a wireless communication system.

5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.

In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.

Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.

In addition, standardization of wireless interface architecture/protocols for technologies such as intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) that provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) that simplifies random access procedures is also in progress, and standardization of system architecture/services for 5G baseline architecture (e.g., Service-based Architecture, Service-based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal is also in progress.

Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.

According to one embodiment of the present disclosure, a device and method for effectively providing a service in a mobile communication system are provided.

According to one embodiment of the present disclosure, a method performed by a policy control function (PCF) entity in a wireless communication system is provided. The method may include the steps of transmitting a first message to a network entity related to energy for requesting information related to energy of single-network slice selection assistance information (S-NSSAIs), receiving a second message from the network entity in response to the first message, the second message including the information related to the energy, and transmitting a third message to an access and mobility management function (AMF) entity including information about a first S-NSSAI to be replaced among the S-NSSAIs based on the information related to the energy.

According to one embodiment of the present disclosure, a device and method for effectively providing a service in a wireless communication system can be provided.

The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned can be clearly understood by a person having ordinary skill in the art to which the present disclosure belongs from the description below.

Figure 1 illustrates the structure of a 5G (generation) system according to one embodiment.

FIG. 2 illustrates a method for changing network slices based on energy according to one embodiment.

FIG. 3a illustrates a method for changing network slices based on energy according to one embodiment.

FIG. 3b illustrates a method for changing network slices based on energy according to one embodiment.

Figure 4 illustrates the configuration of an exemplary base station according to one embodiment.

Figure 5 illustrates the configuration of an exemplary terminal according to one embodiment.

Figure 6 illustrates the configuration of a core network object according to one embodiment.

The operating principles of the present disclosure are described in detail below with reference to the attached drawings. In the following description of the present disclosure, detailed descriptions of related known functions or configurations may be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Furthermore, the terms described below are defined based on the functions of the present disclosure and may vary depending on the intent or custom of the user or operator. Therefore, the definitions of terms should be based on the overall content of this specification.

The terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, and terms referring to various identification information are provided as examples for convenience of explanation. Therefore, the present disclosure is not limited to the terms described below, and other terms referring to objects with equivalent technical meanings may be used.

For convenience of explanation, this disclosure uses terms and names defined in the 5GS and NR standards, which are the most recent standards defined by the 3rd Generation Partnership Project (3GPP) among the existing communication standards. However, this disclosure is not limited to the above-described terms and names, and can be equally applied to wireless communication networks conforming to other standards. In particular, this disclosure can be applied to the 3GPP 5GS (5G system)/NR (5th generation mobile communication standard).

Figure 1 illustrates the structure of a 5G system according to one embodiment.

Referring to FIG. 1, a 5G mobile communication network is composed of a 5G UE (user equipment, terminal), a 5G RAN (radio access network, base station), gNB (5g nodeB), eNB (evolved nodeB, etc.), and/or a 5G core network. For example, a 5G core network may be composed of NFs such as an AMF (access and mobility management function) entity that provides a mobility management function of a UE, an SMF (session management function) entity that provides a session management function, an UPF (user plane function) entity that performs a data transfer role, a PCF (policy control function) entity that provides a policy control function, a UDM (unified data management) entity that provides data management functions such as subscriber data and policy control data, and/or a UDR (unified data repository) entity that stores data of various network functions (NFs) such as UDM. For example, a 5G core network may be composed of an NSSF (network slice selection function) entity, a NWDAF (network data analytic It can be composed of NFs such as function) entity, AF (application function) entity, DN (data network) entity, NSACF (network slice admission control function) entity, etc.

In one embodiment, the 3GPP system defines a conceptual link connecting NFs within a 5G system as a reference point. The following is an example of a reference point included in the 5G system architecture depicted in FIG. 1.

- N1: Reference point between UE and AMF

- N2: Reference point between (R)AN and AMF

- N3: Reference point between (R)AN and UPF

- N4: Reference point between SMF and UPF

- N5: Reference point between PCF and AF

- N6: Reference point between UPF and DN

- N7: Reference point between SMF and PCF

- N8: Reference point between UDM and AMF

- N9: Reference point between two core UPFs

- N10: Reference point between UDM and SMF

- N11: Reference point between AMF and SMF

- N12: Reference point between AMF and AUSF

- N13: Reference point between UDM and authentication server function (AUSF)

- N14: Reference point between two AMFs

- N15: Reference point between PCF and AMF for non-roaming scenarios, reference point between PCF and AMF in visited network for roaming scenarios.

In 5G systems, network slicing can be referred to as a technology and architecture that enables multiple virtualized, independent, logical networks within a single physical network. To meet the specialized requirements of services/applications, network operators can configure virtual end-to-end (E2E) networks called network slices to provide services to UEs (or users). For example, a network slice can be identified by an identifier called single-network slice selection assistance information (S-NSSAI). The network can transmit a set of allowed slices (e.g., allowed NSSAI(s)) to the UE during the UE registration procedure. The UE transmits and receives application data (or data) through a protocol data unit (PDU) session created through one of the S-NSSAIs (e.g., network slice) among the allowed slice sets.

Hereinafter, in one embodiment of the present disclosure, the operation of NF may be referred to as the operation of OAM (orchestration and management). However, this is merely an example, and the operation of NF may be referred to as the operation of various entities, various functions, and various components.

Figure 2 illustrates a method for changing network slices based on energy according to one embodiment.

Referring to FIG. 2, in step 200a according to an embodiment, a radio access network (RAN) (110) may receive an access network (AN) message from a UE (100). If the AN message includes an indication for the UE (e.g., energy saving allowed indication) or information associated with the UE, the RAN may store an indication corresponding to the UE context. For example, the indication for the UE or the information associated with the UE may be an indication or information related to energy consumption or energy saving of the UE. (AN message (energy saving allowed indication, UE ID))

According to one embodiment, in step 200b, the RAN may receive an N2 message from an AMF entity (120). If the N2 message includes an energy saving allowed indication for the UE, the RAN may store an indicator corresponding to the UE context. (N2 message (energy saving allowed indication, UE ID))

According to one embodiment, in step 201, the RAN may identify that S-NSSAI is unavailable if: (N2 message (UE ID or PDU Session ID, S-NSSAI, [Alternative S-NSSAI(s)]))

- When energy consumption is high for S-NSSAI (e.g., Energy Consumption (EC) is higher than the threshold stored in the configuration information) (e.g., when energy consumption is higher than the threshold when providing service to UE through S-NSSAI)

- Or, if the energy efficiency is too low for S-NSSAI (e.g., if the Energy Efficiency (EE) is lower than the threshold stored in the configuration information) (e.g., if the energy efficiency is lower than the threshold when providing a service to the UE through S-NSSAI)

- Or, if the usage rate of renewable energy for S-NSSAI is lower than the threshold stored in the configuration information (for example, if the usage rate of renewable energy among the power used when providing service to UE through S-NSSAI is lower than the threshold)

- Alternatively, if an indication that S-NSSAI is unavailable is received from OAM, -information about the ratio of UEs to be transferred (i.e., the number of UEs that need to move from one S-NSSAI to another S-NSSAI) and/or the reason (e.g., EC on S-NSSAI violates the SLA (service level agreement)) may be transmitted together with the indication that S-NSSAI is unavailable.

- Alternatively, if the RAN (110) wants to reduce energy consumption of the network (e.g., if it receives a related message from the OAM (e.g., information indicating that energy consumption of the network should be reduced, or information indicating to reduce energy consumption of the network) or if the energy consumption of the RAN becomes higher than or close to a set threshold), the RAN (110) may determine an S-NSSAI with high energy consumption per unit time as an unusable S-NSSAI. In this case, the RAN (110) may decide to move some or all of the UEs currently using the S-NSSAI with high energy consumption per unit time to an S-NSSAI with lower energy consumption per unit time. For example, the RAN (110) may instruct at least one UE using the first network slice corresponding to the first S-NSSAI with the highest energy consumption per unit time to use the second network slice and/or the third network slice having relatively lower energy consumption per unit time than the first S-NSSAI. In this case, the second network slice may correspond to the second S-NSSAI, and the third network slice may correspond to the third S-NSSAI.

According to one embodiment, the RAN (110) may, conversely, identify (or determine) that S-NSSAI is available. (e.g., when the EC for S-NSSAI is changed to a state lower than the threshold or there is no need to reduce the energy consumption of the RAN) (e.g., when the energy consumption of the RAN is lower than the threshold when providing a service to the UE through S-NSSAI) (e.g., when the energy efficiency of the RAN is higher than the threshold when providing a service to the UE through S-NSSAI) (e.g., when the usage rate of Renewable energy among the power used by the RAN when providing a service to the UE through S-NSSAI is higher than the threshold)

According to one embodiment, the RAN (110) may transmit an N2 message to the AMF entity to move UEs using an S-NSSAI determined to be unavailable to another S-NSSAI. For example, the RAN may transmit a message to the AMF entity instructing UEs using a network slice corresponding to an S-NSSAI identified as unavailable to use another network slice. For example, the message may include information about the reason for changing the network slice (e.g., power efficiency) and/or the S-NSSAI of the network slice being changed. For example, the message may include unavailable S-NSSAI(s) and/or UE ID(s) or ratio of UEs to be transferred.

According to one embodiment, the AMF entity (120) may transmit an N2 message for each UE (or PDU session) or for each S-NSSAI. If the message is transmitted for each UE, the N2 message transmitted to the UE may include the UE ID or PDU Session ID instead of the ratio of UEs to be transferred.

The message may contain at least some of the following information:

- unavailable S-NSSAI: Unavailable S-NSSAI(s) may be included. In this case, S-NSSAI(s) to be used instead of the unavailable S-NSSAI (i.e., Alternative S-NSSAI(s)) may also be included.

- UE ID(s) or ratio of UEs to be transferred: UE ID(s) or ratio (e.g., a value between 0 and 1 or expressed as a percentage) that should be transferred to a different S-NSSAI for each unavailable S-NSSAI may be included. For example, the RAN (110) may include the IDs of UEs that include an energy saving allowed indication in the UE context.

- available S-NSSAI: Available S-NSSAI(s) may be included.

- reason: May contain information indicating whether the slice was replaced due to EC, EE, or renewable energy.

According to one embodiment, in step 201b, the RAN may determine that the S-NSSAI is unavailable (or available) in the same manner as in step 201. The RAN may transmit an N2 SM message to the SMF entity for each PDU session to move the PDU sessions currently using the S-NSSAI determined to be unavailable to another S-NSSAI. For example, the RAN (110) may transmit a message to the SMF entity for each PDU session to allocate the PDU sessions allocated to the network slice determined to be unavailable to another network slice. (N2 message (N2 SM container))

According to one embodiment, the RAN (110) may include an N2 SM message in the N2 message transmitted to the AMF entity. For example, the N2 SM message may include at least some of the following information:

- unavailable S-NSSAI: Unavailable S-NSSAI(s) may be included. In this case, S-NSSAI(s) to be used instead of the unavailable S-NSSAI (i.e., Alternative S-NSSAI(s)) may also be included.

- UE ID(s) or PDU Session ID(s): For example, the RAN may include the IDs of UEs that have an energy saving allowed indication in the UE context or the PDU session ID(s) of those UEs.

- available S-NSSAI: Available S-NSSAI(s) may be included.

- reason: May contain information indicating whether the slice was replaced due to EC, EE, or renewable energy.

According to one embodiment, when the AMF entity receives the N2 message of step 201b from the RAN in step 201c, the AMF entity may transmit a message to the SMF entity for transmitting the N2 SM message included in the N2 message to the SMF entity. (N2 SM container)

According to one embodiment, in step 202b, the UPF entity (130) may determine that the S-NSSAI is unavailable if: (N4 message (S-NSSAI, [Alternative S-NSSAI(s)]))

- When energy consumption is high for S-NSSAI (for example, when Energy Consumption (EC) is higher than the threshold stored in the configuration information)

- Or, if the energy efficiency is too low for S-NSSAI (when the Energy Efficiency (EE) is lower than the threshold stored in the configuration information)

- Or, if the usage rate of renewable energy for S-NSSAI is lower than the threshold stored in the setting information.

- Alternatively, if an indication is received from OAM that S-NSSAI is unavailable, in this case the indication that S-NSSAI is unavailable may be received together with the ratio of UEs to be transferred (i.e., the number of UEs that need to move from one S-NSSAI to another), and/or the reason (e.g., EC on S-NSSAI violates the SLA).

- Alternatively, if the UPF entity (130) wants to reduce energy consumption of the network (e.g., if a related message is received from OAM or if the energy consumption of the UPF becomes higher than or close to a set threshold), the UPF entity may determine an S-NSSAI with high energy consumption per unit time as an unavailable S-NSSAI. In this case, the UPF entity may decide to move some or all of the UEs currently using the S-NSSAI with high energy consumption per unit time to the S-NSSAI with low energy consumption per unit time.

According to one embodiment, the UPF entity (130) may determine, conversely, that the S-NSSAI is available. (For example, when the EC for the S-NSSAI is changed to a state lower than the threshold or there is no need to reduce the energy consumption of the UPF entity) (For example, when the energy consumption of the UPF entity is lower than the threshold when providing a service to the UE through the S-NSSAI) (For example, when the energy efficiency of the UPF entity is higher than the threshold when providing a service to the UE through the S-NSSAI) (For example, when the usage rate of Renewable energy among the power used by the UPF entity is higher than the threshold when providing a service to the UE through the S-NSSAI)

According to one embodiment, the UPF entity (130) may transmit an N4 message per PDU session (or N4 session) to the SMF entity (135) to move UEs using an S-NSSAI that has been determined to be unavailable to another S-NSSAI. For example, the UPF entity (130) may transmit an N4 message per PDU session to the SMF (135) to move UEs using a network slice corresponding to an S-NSSAI that has been determined to be unavailable to another network slice or to assign them to another network slice.

In one embodiment, the N4 message may include at least some of the following information:

- unavailable S-NSSAI: Unavailable S-NSSAI(s) may be included. In this case, S-NSSAI(s) to be used instead of the unavailable S-NSSAI (i.e., Alternative S-NSSAI(s)) may also be included.

- UE ID(s) or PDU Session ID(s): For example, the RAN may include the IDs of UEs that contain an energy saving allowed indication in the UE context or the PDU session ID(s) of the UEs.

- available S-NSSAI: Available S-NSSAI(s) may be included.

- reason: May contain information indicating slice replacement due to EC, slice replacement due to EE, and/or slice replacement due to renewable energy.

According to one embodiment, when the SMF entity (135) receives the message of step 201c or the message of step 202b in step 203, it may transmit a message requesting slice replacement for each UE (or PDU Session) included in the received message to the AMF entity. (request(PDU Session ID or Session Context ID, S-NSSAI, [Alternative S-NSSAI(s)])) The SMF (135) may decide to perform slice replacement only for UEs that have agreed to the energy saving operation (e.g., UEs that include an energy saving allowed indication in the UE subscription information included in the message received by the SMF from the UDM) (or, giving priority to the agreed UEs). The message transmitted to the AMF entity may include at least some of the following information:

- PDU Session ID, S-NSSAI, Alternative S-NSSAI, reason (e.g., S-NSSAI of UPF is not available or S-NSSAI of RAN is not available, etc.)

According to one embodiment, in step 204a, the AMF entity (120) may receive the message of step 201 from the RAN (110), and if the message includes an unavailable S-NSSAI, perform a procedure to move UEs (100) that are using the RAN (110) that transmitted the message of step 201 and are using the unavailable S-NSSAI included in the message of step 201 to an Alternative S-NSSAI. (Network Slice Replacement executed) For example, at least one UE may be connected to the RAN and using a network slice corresponding to an unavailable S-NSSAI, and the AMF entity (120) may perform a procedure to move at least one UE to use a network slice corresponding to an available S-NSSAI.

In one embodiment, the AMF entity (120) may decide to perform slice replacement (or network slice replacement) only for UEs that have agreed to the energy saving operation (e.g., UEs whose UE subscription information includes an energy saving allowed indication) (or giving priority to UEs that have agreed).

According to one embodiment, if the message received from the RAN (110) includes an Alternative S-NSSAI for an unavailable S-NSSAI, the AMF entity (120) may use the Alternative S-NSSAI as it is. If the message received from the RAN does not include the Alternative S-NSSAI, the AMF entity may obtain the Alternative S-NSSAI through configuration information, or obtain the Alternative S-NSSAI for the unavailable S-NSSAI through at least one of the OAM, the NSSF entity, or the PCF entity. For example, the Alternative S-NSSAI may be an available S-NSSAI. For example, the Alternative S-NSSAI may be an S-NSSAI selected from among the available S-NSSAIs. For example, the network slice corresponding to the Alternative S-NSSAI may be a network slice that complies with an energy policy (e.g., energy consumption, energy efficiency).

According to one embodiment, the AMF entity (120) may receive the message of step 203 from the SMF entity (135), and if the received message includes an unavailable S-NSSAI, perform a procedure to move the PDU session corresponding to the unavailable S-NSSAI to an Alternative S-NSSAI. For example, the AMF entity (120) may assign the PDU session corresponding to the unavailable S-NSSAI to a network slice corresponding to the Alternative S-NSSAI.

According to one embodiment, if the Alternative S-NSSAI for the unavailable S-NSSAI is included in the message received from the SMF entity (135), the AMF entity (120) may use the Alternative S-NSSAI as is. If the Alternative S-NSSAI is not included in the received message, the AMF entity (120) may obtain the Alternative S-NSSAI through the configuration information, and may obtain the Alternative S-NSSAI for the unavailable S-NSSAI through at least one of the OAM, the NSSF entity, or the PCF entity.

In the present disclosure, Alternative S-NSSAI may be replaced with at least one term of allowed N-SSAI, available N-SSAI, allowable N-SSAI, acceptable N-SSAI, permitted N-SSAI, or authorized N-SSAI.

According to one embodiment, the AMF entity (120) may transmit configuration information (e.g., mapping from S-NSSAI to Alternative S-NSSAI) indicating that Alternative S-NSSAI will be used instead of S-NSSAI via a non-access stratum (NAS) message to each UE that has decided to replace a slice. For example, if there are UEs among the UEs that have decided to replace a slice that are using a PDU session via an unavailable S-NSSAI, the AMF entity (120) may transmit a message for replacing a slice of the PDU session to the SMF entity (135) that is in charge of the PDU session corresponding to the unavailable S-NSSAI.

For example, a message for replacing a slice of a PDU session may include S-NSSAI, Alternative S-NSSAI, and/or PDU Session ID (or SM Context ID). When the SMF entity (135) receives the message for replacing a slice of a PDU session, it may transmit a message for replacing a slice of the PDU session from S-NSSAI to Alternative S-NSSAI to at least one of the UE (100), the RAN (110), or the UPF entity (130).

According to one embodiment, in step 204b, the AMF entity (120) receives the message of step 201 from the RAN (110), and if the received message includes an unavailable S-NSSAI, upon receiving a new registration request and/or a new PDU session request message for the unavailable S-NSSAI from the UE, the AMF entity (120) may transmit a registration reject message and a PDU session reject message to the UE, respectively. For example, the AMF entity (120) may receive a new registration request for the unavailable S-NSSAI from the UE (100) and transmit a registration reject message to the UE. For example, the AMF entity (120) may receive a new PDU session request message for the unavailable S-NSSAI from the UE and transmit a PDU session reject message to the UE.

For example, a registration rejection message and/or a PDU session rejection message may include a back-off timer. The operations described in FIG. 2 of the present disclosure may be omitted at least in part, and other operations may be added. For example, operations 200a and 200b of FIG. 2 may be optionally performed. For example, the RAN (110) may receive an energy saving allowed indication from the UE (100) or from the AMF entity (120).

FIG. 3a illustrates a method for changing network slices based on energy according to one embodiment.

Referring to FIG. 3a, in step 301, the NSSF entity (or PCF entity) may send a subscription request message to the Energy related NF (350) to obtain energy-related information by S-NSSAI. (Subscribe (analytics ID, S-NSSAI(s), [EE threshold per S-NSSAI], [EC threshold per S-NSSAI]))

For example, the Energy related NF (350) may be included in various entities such as the NWDAF entity, the ECF (Energy Control Function) entity, the EECF (Energy Efficiency Control Function) entity, and/or the OAM.

The request message may contain at least some of the following information:

- A directive requesting energy-related information

- Target S-NSSAI(s) (e.g., S-NSSAI that is the target of a request for energy-related information)

- [EE threshold per S-NSSAI], [EC threshold per S-NSSAI])

According to one embodiment, in step 302, the Energy related NF may send a notification message or response message to the NSSF entity (or, PCF entity) that includes at least some of the following information:

- EE for a list of S-NSSAIs

- EC for a list of S-NSSAIs

- Renewable energy for a list of S-NSSAIs,

- UE ID(s) using the renewable energy within a S-NSSAI

- [S-NSSAI(s) whose EC exceeded the threshold], AMF ID(s) for S-NSSAI, UE ID(s)

- [S-NSSAI(s) whose EE becomes lower than the threshold], AMF ID(s) for S-NSSAI, UE ID(s))

(Notify (EE for a list of S-NSSAIs, EC for a list of S-NSSAIs, Renewable energy for a list of S-NSSAIs, UE ID(s) using the renewable energy within a S-NSSAI, [S-NSSAI(s) whose EC exceeded the threshold], AMF ID(s) for S-NSSAI, UE ID(s) [S-NSSAI(s) whose EE becomes lower than the threshold], AMF ID(s) for S-NSSAI, UE ID(s)))

According to one embodiment, in step 303, the NSSF entity (160) (or PCF entity (140)) may determine unavailable S-NSSAI(s) (or available S-NSSAI(s)) based on the information included in the message received in step 302. For example, the NSSF entity may determine Alternative S-NSSAI(s) for each unavailable S-NSSAI. (Nnssf_NSSAIAvailability_Notify (S-NSSAI(s), [Alt S-NSSAI(s)], [ratio of UEs to be replaced or UE ID(s)], reason=energy related))

According to one embodiment, if the message received in step 302 includes UE ID(s), the NSSF entity (160) (or PCF entity (140)) may obtain the addresses of the AMF entities (120) responsible for the corresponding UE(s) from the UDM (not shown), and then transmit a message to the corresponding AMF entity (120)(s) to move UEs (e.g., UE (100)) using the unavailable S-NSSAI to another S-NSSAI (or a message to notify the unavailable S-NSSAI(s)).

According to one embodiment, the NSSF entity (160) (or PCF entity (140)) may, if the message received in step 302 includes AMF ID(s) or addresses, send a message to the corresponding AMF entities (120) to move UEs (e.g., UEs (100)) using an unavailable S-NSSAI to another S-NSSAI (or to notify of an unavailable S-NSSAI(s)).

According to one embodiment, the NSSF entity (160) (or PCF entity (140)) may send a message to the AMF entity (120) to move UEs (e.g., UEs (100)) that are using an unavailable S-NSSAI to another S-NSSAI (or to notify the unavailable S-NSSAI(s)). For example, the message to move UEs to another S-NSSAI may include at least some of the following information:

- S-NSSAI(s),

- Alt S-NSSAI(s)

- [ratio of UEs to be replaced or UE ID(s)]

- reason: May contain information indicating that the slice is unavailable due to EC, EE, or renewable energy.

According to one embodiment, in step 304a, the AMF entity (120) may receive the message of step 303 from the NSSF entity (160) (or the PCF entity (140)), and if the received message includes an unavailable S-NSSAI, the AMF entity (120) may perform a procedure to move UEs (e.g., UEs (100)) that are using the RAN (110) and are using the unavailable S-NSSAI included in the message of step 301 to an Alternative S-NSSAI. The AMF entity (120) may decide to perform slice replacement only for UEs that have agreed to the energy saving operation (e.g., UEs that include an energy saving allowed indication in their UE subscription information) (or, giving priority to UEs that have agreed). (Network Slice Replacement executed)

According to one embodiment, if an AMF entity (120) receives a message from an NSSF entity (or a PCF entity) and includes an Alternative S-NSSAI for an unavailable S-NSSAI, the AMF entity (120) may use the Alternative S-NSSAI included in the message as is. If the received message does not include an Alternative S-NSSAI, the AMF entity may obtain the Alternative S-NSSAI through configuration information, or the AMF entity may obtain the Alternative S-NSSAI for the unavailable S-NSSAI through at least one of an OAM, an NSSF entity, or a PCF entity.

According to one embodiment, the AMF entity (120) may transmit configuration information (e.g., mapping from S-NSSAI to Alternative S-NSSAI) indicating that Alternative S-NSSAI will be used instead of S-NSSAI via a non-access stratum (NAS) message to each UE that has decided to replace a slice. In addition, if there are UEs among the UEs that have decided to replace a slice that are using a PDU session via unavailable S-NSSAI, the AMF entity (120) may transmit a message for replacing a slice of the PDU session to the SMF entity (135) responsible for the PDU session corresponding to the unavailable S-NSSAI. For example, the message for replacing a slice of the PDU session may include S-NSSAI, Alternative S-NSSAI, and/or PDU Session ID (or SM Context ID).

According to one embodiment, upon receiving the message, the SMF entity (135) may transmit a message to at least one of the UE (100), the RAN (110), or the UPF entity to replace the slice of the PDU Session from the S-NSSAI to the Alternative S-NSSAI.

According to one embodiment, in step 304b, the AMF entity (120) may receive the message of step 303 from the NSSF entity (160) (or the PCF entity (140)). When the received message includes an unavailable S-NSSAI, the AMF entity (120) may transmit a registration rejection message and a PDU session rejection message to the UE in response to each of the new registration request and/or new PDU session request messages for the unavailable S-NSSAI received from the UE. For example, the AMF entity (120) may transmit a registration rejection message to the UE (100) in response to a registration request for the unavailable S-NSSAI. For example, the AMF entity (120) may transmit a PDU session rejection message to the UE in response to a request message for a PDU session corresponding to the unavailable S-NSSAI. (ES or EE behavior activated for the Network Slice OR Deregister some or all of the UEs from the S-NSSAI)

For example, a registration rejection message and/or a PDU session rejection message may include a back-off timer.

FIG. 3b illustrates a method for replacing network slices based on energy according to one embodiment.

Referring to FIG. 3b, in step 311 according to one embodiment, the PCF entity (140) may transmit a subscription request message to the Energy related NF (350) (or, NWDAF entity, OAM) to obtain energy-related information per S-NSSAI. (Subscribe (analytics ID, S-NSSAI(s), [EE threshold per S-NSSAI], [EC threshold per S-NSSAI]))

According to one embodiment, in step 312, the Energy related NF (350) may transmit a notification message or response message to the PCF entity (140) that includes at least some of the following information:

- EE for a list of S-NSSAIs

- EC for a list of S-NSSAIs

- Renewable energy for a list of S-NSSAIs,

- UE ID(s) using the renewable energy within a S-NSSAI

- [S-NSSAI(s) whose EC exceeded the threshold], AMF ID(s) for S-NSSAI, UE ID(s)

- [S-NSSAI(s) whose EE becomes lower than the threshold], AMF ID(s) for S-NSSAI, UE ID(s))

According to one embodiment, in step 313, the PCF (140) may determine to update parameters (e.g., UE-Slice-MBR, Slice-MBR) related to energy consumption per S-NSSAI based on information (e.g., EE list, EC list) included in the received response message. For example, for an S-NSSAI, it may be determined that energy should be reduced in the following cases: EC above the threshold, EE lower than the threshold, renewable energy lower than the threshold for an S-NSSAI.

For example, an S-NSSAI requiring a reduction in Slice-MBR or UE-Slice-MBR can correspond to a network slice having an EC (energy consumption) above a threshold value, and can correspond to a network slice having an EE (energy efficiency) below a threshold value. An S-NSSAI requiring a reduction in Slice-MBR or UE-Slice-MBR can correspond to a network slice having a renewable energy ratio among the energy consumed to produce power when the network slice provides a service below a threshold value.

According to one embodiment, at step 313b, the PCF (140) may send a message to the AMF entity (120) to update the UE-Slice-MBR for the S-NSSAI(s) that are intended to reduce energy consumption. For example, the message to update the UE-Slice-MRB may include at least some of the following information:

- Policy association ID

- Authorized UE-Slice-MRR(maximum bit rate)

According to one embodiment, the AMF entity (120) may apply an access and mobility (AM) policy at step 314b. (AM policy applied) Upon receiving a message including an Authorized UE-Slice-MBR from the PCF at step 313b, the AMF entity (120) may transmit an N2 message including the UE-Slice-MBR to the RAN.

According to one embodiment, the PCF entity (140) may adjust the Slice-MBR at step 314c. (Adjust Slice-MBR) The PCF entity (140) may determine session parameters for the S-NSSAI based on the updated Slice-MBR for each S-NSSAI. For example, if the uplink (UL) (or downlink (DL)) data rate for the S-NSSAI reaches the Slice-MBR, the allowed bit rate of the quality of service (QoS) flow generated by the S-NSSAI may be set lower or rejected.

According to one embodiment, the SMF entity (135) may apply a session management (SM) policy at step 314c. (SM policy applied).

In step 313a of the present disclosure, the PCF (140) may send a message (e.g., an AM policy notification) to the AMF (120). For example, the message may include a UE ID, a Policy Association ID, an S-NSSAI to be replaced, and an Alt S-NSSAI. In step 314a of the present disclosure, a network slice replacement may be performed. Step 314a may correspond to step 304a of FIG. 3a.

FIG. 4 illustrates a configuration of an exemplary base station according to one embodiment of the present disclosure.

Referring to FIG. 4, the configuration illustrated in FIG. 7 according to one embodiment may be understood as the configuration of the gNB and/or eNB of FIG. 1. Terms such as “… unit”, “… unit”, etc. used hereinafter refer to a unit that processes at least one function or operation, which may be implemented by hardware, software, or a combination of hardware and software.

According to one embodiment, the base station includes a communication unit (405), a storage unit (410), and/or a control unit (415).

The communication unit (405) performs functions for transmitting and receiving signals via a wireless channel. For example, the communication unit (405) performs a conversion function between a baseband signal and a bit stream according to the physical layer specifications of the system. For example, when transmitting data, the communication unit (405) generates complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the communication unit (405) restores a reception bit stream by demodulating and decoding the baseband signal. In addition, the communication unit (405) upconverts a baseband signal into an RF band signal and transmits it through an antenna, and downconverts an RF band signal received through the antenna into a baseband signal. For example, the communication unit (405) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc.

In addition, the communication unit (405) may include a plurality of transmit/receive paths. Furthermore, the communication unit (405) may include at least one antenna array composed of a plurality of antenna elements. In terms of hardware, the communication unit (405) may be composed of digital circuits and analog circuits (e.g., radio frequency integrated circuits (RFIC)). Here, the digital circuits and analog circuits may be implemented in a single package. In addition, the communication unit (405) may include a plurality of RF chains. Furthermore, the communication unit (405) may perform beamforming.

The communication unit (405) transmits and receives signals as described above. Accordingly, all or part of the communication unit (405) may be referred to as a "transmitter," a "receiver," or a "transmitting and receiving unit." Furthermore, in the following description, transmission and reception performed via a wireless channel are used to mean that the communication unit (405) performs the processing described above.

The storage unit (410) stores data such as basic programs, application programs, and setting information for the operation of the base station. The storage unit (410) may be composed of volatile memory, non-volatile memory, or a combination of volatile and non-volatile memory. In addition, the storage unit (410) provides stored data upon request from the control unit (415).

The control unit (415) controls the overall operations of the base station. For example, the control unit (415) transmits and receives signals through the communication unit (405). In addition, the control unit (415) records and reads data in the storage unit (410). In addition, the control unit (415) can perform the functions of the protocol stack required by the communication standard. To this end, the control unit (415) may include at least one processor or microprocessor, or may be a part of a processor. In addition, a part of the communication unit (405) and the control unit (415) may be referred to as a CP (communication processor). According to various embodiments, the control unit (415) may control to perform synchronization using a wireless communication network. For example, the control unit (415) may control the base station to perform operations according to the various embodiments described above.

FIG. 5 illustrates the configuration of an exemplary terminal according to one embodiment of the present disclosure. The configuration illustrated in FIG. 8 may be understood as the configuration of the UE (or NR UE) of FIG. 1. Terms such as "unit" and "unit" used hereinafter refer to a unit that processes at least one function or operation, and may be implemented by hardware, software, or a combination of hardware and software.

Referring to FIG. 5, the terminal includes a communication unit (505), a storage unit (510), and/or a control unit (515).

The communication unit (505) performs functions for transmitting and receiving signals via a wireless channel. For example, the communication unit (505) performs a conversion function between a baseband signal and a bit stream according to the physical layer specifications of the system. For example, when transmitting data, the communication unit (505) generates complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the communication unit (505) restores a reception bit stream by demodulating and decoding the baseband signal. In addition, the communication unit (505) upconverts a baseband signal to an RF band signal and then transmits it through an antenna, and downconverts an RF band signal received through the antenna to a baseband signal. For example, the communication unit (505) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc.

In addition, the communication unit (505) may include a plurality of transmit/receive paths. Furthermore, the communication unit (505) may include at least one antenna array composed of a plurality of antenna elements. In terms of hardware, the communication unit (505) may be composed of digital circuits and analog circuits (e.g., a radio frequency integrated circuit (RFIC)). Here, the digital circuits and analog circuits may be implemented in a single package. In addition, the communication unit (505) may include a plurality of RF chains. Furthermore, the communication unit (505) may perform beamforming.

The communication unit (505) transmits and receives signals as described above. Accordingly, all or part of the communication unit (505) may be referred to as a "transmitter," a "receiver," or a "transmitting and receiving unit." Furthermore, in the following description, transmission and reception performed via a wireless channel are used to mean that the communication unit (505) performs the processing described above.

The storage unit (510) stores data such as basic programs, application programs, and setting information for the operation of the terminal. The storage unit (510) may be composed of volatile memory, non-volatile memory, or a combination of volatile and non-volatile memory. In addition, the storage unit (510) provides stored data upon request from the control unit (515).

The control unit (515) controls the overall operations of the terminal. For example, the control unit (515) transmits and receives signals through the communication unit (505). In addition, the control unit (515) records and reads data in the storage unit (510). In addition, the control unit (515) can perform the functions of the protocol stack required by the communication standard. To this end, the control unit (515) may include at least one processor or microprocessor, or may be a part of a processor. In addition, a part of the communication unit (505) and the control unit (515) may be referred to as a CP (communication processor). According to various embodiments, the control unit (515) may control to perform synchronization using a wireless communication network. For example, the control unit (515) may control the terminal to perform operations according to various embodiments described below.

FIG. 6 illustrates a configuration of a core network object according to an embodiment of the present disclosure. It illustrates a configuration of a core network object in a wireless communication system according to various embodiments of the present disclosure. The configuration illustrated in FIG. 6 may be understood to correspond to at least one of the network entities of FIGS. 1 to 5 . Terms such as “… unit” and “… unit” used hereinafter mean a unit that processes at least one function or operation, and this may be implemented by hardware, software, or a combination of hardware and software.

Referring to FIG. 6, the core network object may include a communication unit (640), a storage unit (645), and/or a control unit (650).

The communication unit (640) provides an interface for communicating with other devices within the network. That is, the communication unit (640) converts a bit string transmitted from the core network object to another device into a physical signal, and converts a physical signal received from another device into a bit string. That is, the communication unit (640) can transmit and receive signals. Accordingly, the communication unit (640) may be referred to as a modem, a transmitter, a receiver, or a transceiver. In this case, the communication unit (640) enables the core network object to communicate with other devices or systems via a backhaul connection (e.g., a wired backhaul or a wireless backhaul) or via a network.

The storage unit (645) stores data such as basic programs, application programs, and configuration information for the operation of the core network object. The storage unit (645) may be composed of volatile memory, non-volatile memory, or a combination of volatile and non-volatile memory. In addition, the storage unit (645) provides the stored data upon request from the control unit (650).

The control unit (650) controls the overall operations of the core network object. For example, the control unit (650) transmits and receives signals through the communication unit (640). In addition, the control unit (650) records and reads data from the storage unit (645). For this purpose, the control unit (650) may include at least one processor. According to various embodiments of the present disclosure, the control unit (650) may control synchronization using a wireless communication network. For example, the control unit (650) may control the core network object to perform operations according to various embodiments described below.

The methods according to the embodiments described in the claims or specification of the present invention may be implemented in the form of hardware, software, or a combination of hardware and software.

When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to the embodiments described in the claims or specification of the present invention.

These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage device, compact disc ROM (CD-ROM), digital versatile discs (DVDs) or other forms of optical storage device, magnetic cassette. Or, they may be stored in a memory configured as a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.

Additionally, the program may be stored in an attachable storage device that is accessible via a communication network such as the Internet, an intranet, a local area network (LAN), a wide local area network (WLAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device implementing an embodiment of the present invention via an external port. Additionally, a separate storage device on the communication network may be connected to a device implementing an embodiment of the present invention.

In the specific embodiments of the present invention described above, components included in the invention are expressed in the singular or plural form depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present invention is not limited to singular or plural components. Even components expressed in the plural form may be composed of singular elements, or even components expressed in the singular form may be composed of plural elements.

While the detailed description of the present invention has described specific embodiments, it is clear that various modifications are possible without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined not only by the scope of the following claims but also by equivalents thereof.

Claims (15)

In a method performed by a PCF (policy control function) entity in a wireless communication system, A step of transmitting a first message to a network entity related to energy to request information related to energy of single-network slice selection assistance information (S-NSSAI); receiving, from the network entity, a second message including the information related to the energy in response to the first message; and A method comprising the step of transmitting, to an AMF (access and mobility management function) entity, a third message including information about a first S-NSSAI to be replaced among the S-NSSAIs based on the information related to the energy. In claim 1, Further comprising a step of determining a second S-NSSAI corresponding to the first S-NSSAI based on the information related to the energy, A method wherein information about the second S-NSSAI is included in the third message. In claim 1, A method further comprising the step of transmitting a fourth message to the AMF entity requesting an update of an energy parameter of at least one S-NSSAI among the S-NSSAIs. In claim 1, The information related to the energy includes information on the EE (energy efficiency) of the S-NSSAIs, information on the EC (energy consumption) of the S-NSSAIs, or information on renewable energy associated with the S-NSSAIs. A method according to claim 1, wherein the third message further includes information about the ratio of UEs associated with the first S-NSSAI, or information about the cause of the replacement of the first S-NSSAI. In a method performed by an AMF (access and mobility management function) entity in a wireless communication system, A step of receiving a message including information about a first S-NSSAI to be replaced among S-NSSAIs (single-network slice selection assistance information) from a PCF (policy control function) entity; and Including a step of changing UEs (user equipment) associated with the first S-NSSAI to the second S-NSSAI, The method wherein the first S-NSSAI is based on information related to the energy of the S-NSSAIs. In claim 5, The second S-NSSAI corresponding to the first S-NSSAI is based on the information related to the energy, A method in which information about the second S-NSSAI is included in the message. In claim 5, A method further comprising the step of receiving, from the PCF entity, a message requesting an update of an energy parameter of at least one S-NSSAI among the S-NSSAIs. In claim 5, The information related to the energy includes information on the EE (energy efficiency) of the S-NSSAIs, information on the EC (energy consumption) of the S-NSSAIs, or information on renewable energy associated with the S-NSSAIs. A method wherein the message further includes information about the ratio of UEs associated with the first S-NSSAI, or information about the cause of the replacement of the first S-NSSAI. In the PCF (policy control function) entity of a wireless communication system, transceiver; and A controller coupled with the above transceiver, The above controller: Transmitting a first message to a network entity related to energy to request information related to energy of single-network slice selection assistance information (S-NSSAI), Receive from the network entity a second message including the information related to the energy in response to the first message; A PCF entity configured to transmit a third message to an AMF (access and mobility management function) entity, the third message including information about a first S-NSSAI to be replaced among the S-NSSAIs based on the information related to the energy. In claim 9, The above controller: Based on the above information related to the above energy, it is set to determine the second S-NSSAI corresponding to the first S-NSSAI, Information about the above second S-NSSAI is included in the above third message, PCF entity. In claim 9, The above controller: A PCF entity configured to transmit a fourth message to the AMF entity requesting an update of an energy parameter of at least one S-NSSAI among the S-NSSAIs. In claim 9, The information related to the energy includes information on the EE (energy efficiency) of the S-NSSAIs, information on the EC (energy consumption) of the S-NSSAIs, or information on renewable energy associated with the S-NSSAIs. The PCF entity, wherein the third message further includes information about the ratio of UEs associated with the first S-NSSAI, or information about the reason why the first S-NSSAI is replaced. In a method performed by an AMF (access and mobility management function) entity in a wireless communication system, transceiver; and A controller coupled with the above transceiver, The above controller: Receive a message from a PCF (policy control function) entity, including information about a first S-NSSAI to be replaced among S-NSSAIs (single-network slice selection assistance information), It is set to change the UEs (user equipment) associated with the first S-NSSAI to the second S-NSSAI, The above first S-NSSAI is an AMF entity based on information related to the energy of the above S-NSSAIs. In claim 13, The second S-NSSAI corresponding to the first S-NSSAI is based on the information related to the energy, Information about the above second S-NSSAI is included in the above message, AMF entity. In claim 13, The above controller: An AMF entity configured to receive, from the PCF entity, a message requesting an update of an energy parameter of at least one of the S-NSSAIs.