Communication control method and device for energy saving of terminal in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. The 5G or 6G communication system may: receive, from a network entity, configuration information including a threshold value for a battery level of a terminal or a threshold value for an energy usage amount of the terminal; and receive, from the network entity, a response message to a request message on the basis of the threshold value, wherein the response message includes identification information for activating or deactivating a protocol data unit (PDU) session, and the network entity includes a policy control function (PCF) entity or an access and mobility management function (AMF) entity.

Description

Communication control method and device for energy saving of terminals in wireless communication systems

[0001] The present disclosure relates to the field of communications, and particularly to the operation of terminals and base stations. The present disclosure relates to a method and device for controlling communication to conserve energy in a terminal in a wireless communication system.

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

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

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

[0005] In addition, standardization of wireless interface architecture / protocols is in progress 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. Standardization is also in progress for system architecture / services such as 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.

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

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

[0008] The disclosed embodiment is intended to provide a device and method for controlling communication to save energy of a terminal in a wireless communication system.

[0009] The present invention proposes a communication control method and device for saving energy of a terminal.

[0010] More specifically, a method according to one embodiment of the present disclosure includes the steps of receiving a first control signal transmitted from a base station, processing the received first control signal, and transmitting a second control signal generated based on the processing to the base station.

[0011] The present disclosure provides a device and method for effectively providing services in a wireless communication system. Specifically, the present disclosure provides a device and method for controlling communication to conserve energy at a terminal in a wireless communication system.

[0012] FIG. 1 illustrates a communication network including core network entities in a wireless communication system according to one embodiment of the present disclosure.

[0013] FIG. 2 illustrates a method for setting a non-access stratum (NAS) reject mode and deactivating a protocol data unit (PDU) session based on energy-related information of a UE (user equipment) in a registration procedure of a wireless communication system according to one embodiment of the present disclosure.

[0014] FIG. 3 illustrates a method for setting a NAS reject mode and activating a PDU session based on energy-related information of a UE in a registration procedure of a wireless communication system according to one embodiment of the present disclosure.

[0015] FIG. 4 illustrates a method for determining PDU session deactivation based on energy-related information and energy-related policy of a UE in a PDU session-related procedure of a wireless communication system according to one embodiment of the present disclosure.

[0016] FIG. 5 illustrates a method for activating a PDU session based on energy-related information of a UE in a Service Request procedure of a wireless communication system according to one embodiment of the present disclosure.

[0017] FIG. 6 is a block diagram illustrating the structure of a terminal according to one embodiment of the present disclosure.

[0018] FIG. 7 is a block diagram illustrating the structure of a base station according to one embodiment of the present disclosure.

[0019] FIG. 8 is a block diagram illustrating the structure of a network entity according to one embodiment of the present disclosure.

[0020] The operating principles of the present invention will be 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 will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. The terms described below are defined based on their functions in the present invention. These terms may vary depending on the intent or custom of the user or operator, and therefore, their definitions should be determined based on the overall content of this specification.

[0021] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.

[0022] The advantages and features of the present invention, and the methods for achieving them, will become clearer with reference to the embodiments described in detail below together with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided only to ensure that the disclosure of the present invention is complete and to fully inform those skilled in the art of the scope of the invention, and the present invention is defined only by the scope of the claims. Like reference numerals designate like elements throughout the specification.

[0023] At this time, it will be understood that each block of the processing flowchart drawings and combinations of the flowchart drawings can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flowchart block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flowchart block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).

[0024] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.

[0025] Here, the term '~ unit' used in the present embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and the '~ unit' performs certain roles. However, the '~ unit' is not limited to software or hardware. The '~ unit' may be configured to be on an addressable storage medium and may be configured to play one or more processors. Therefore, as an example, the '~ unit' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. Additionally, the components and '~parts' may be implemented to activate one or more CPUs within a device or secure multimedia card. In addition, in an embodiment, the '~parts' may include one or more processors.

[0026] In the following description of the present disclosure, detailed descriptions of related known functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Hereinafter, embodiments of the present disclosure will be described with reference to the attached drawings.

[0027] The terms used in this disclosure to refer to network objects (or network functions) and objects of the Edge Computing system, terms used to refer to messages, terms used to refer to identification information, and the like are provided for convenience of explanation. Therefore, the disclosure is not limited to the terms described below, and other terms that refer to objects with equivalent technical meanings may be used.

[0028] For convenience, the present disclosure uses terms and names defined in the LTE and NR standards, which are the most recent standards defined by the 3rd Generation Partnership Project (3GPP) among the existing communication standards. However, the present invention is not limited to the above terms and names, and can be equally applied to systems conforming to other standards. In particular, the present invention can be applied to 3GPP NR (5th generation mobile communication standard). Furthermore, the embodiments of the present disclosure can be applied to other communication systems with similar technical backgrounds or channel types. Furthermore, the embodiments of the present disclosure can be applied to other communication systems with some modifications as determined by a person having skilled technical knowledge without significantly departing from the scope of the present disclosure.

[0029] The 5G mobile communication network is composed of 5G UE (user equipment, terminal), 5G RAN (radio access network, base station, base station, gNB (5g nodeB), eNB (evolved nodeB, etc.), and 5G core network. The 5G core network is composed of network functions (NF) such as AMF (access and mobility management function) (150) that provides UE mobility management function, SMF (session management function) (160) that provides session management function, UPF (user plane function) (170) that performs data transfer role, PCF (policy control function) (180) that provides policy control function, UDM (unified data management) (153) that provides data management function such as subscriber data and policy control data, and UDR (unified data repository) that stores data of various network functions.

[0030] Referring to FIG. 1, the AMF (150) provides a function for access and mobility management per terminal (110), and basically, one AMF (150) can be connected to one terminal (110). Specifically, the AMF (150) can perform at least one of signaling between core network nodes for mobility between 3GPP access networks, an interface (N2 interface) between wireless access networks (e.g., 5G RAN) (120), NAS signaling with the terminal (110), identification of the SMF (160), and provision of transmission of session management (SM) messages between the terminal (110) and the SMF (160). Some or all of the functions of the AMF (150) can be supported within a single instance of one AMF (150).

[0031] Referring to FIG. 1, the SMF (160) provides a session management function, and when the terminal (110) has multiple sessions, each session can be managed by a different SMF (160). Specifically, the SMF (160) can perform at least one of the following functions: session management (e.g., session establishment, modification, and release, including tunnel maintenance between the UPF (170) and the access network node), selection and control of UP (user plane) functions, traffic steering setup for routing traffic to an appropriate destination in the UPF (170), termination of the SM portion of NAS messages, downlink data notification (DDN), and initiation of AN-specific SM information (e.g., delivery to the access network via the N2 interface via the AMF (150)). Some or all of the functions of the SMF (160) can be supported within a single instance of one SMF (160).

[0032] In the 3GPP system, a conceptual link connecting NFs within a 5G system is defined as a reference point. A reference point may also be referred to as an interface. The following examples illustrate reference points (hereafter, interchangeably referred to as interfaces) included in the 5G system architecture represented across various embodiments of the present disclosure.

[0033] - N1: Reference point between UE (110) and AMF (150)

[0034] - N2: Reference point between (R)AN(120) and AMF(150)

[0035] - N3: Reference point between (R)AN(120) and UPF(170)

[0036] - N4: Reference point between SMF (160) and UPF (170)

[0037] - N5: Reference point between PCF (180) and AF (130)

[0038] - N6: Reference point between UPF (170) and DN (140)

[0039] - N7: Reference point between SMF (160) and PCF (180)

[0040] - N8: Reference point between UDM (153) and AMF (150)

[0041] - N9: Reference point between two core UPFs (170)

[0042] - N10: Reference point between UDM (153) and SMF (160)

[0043] - N11: Reference point between AMF (150) and SMF (160)

[0044] - N12: Reference point between AMF (150) and AUSF (151)

[0045] - N13: Reference point between UDM (153) and authentication server function (AUSF) (151).

[0046] - N14: Reference point between two AMFs (150)

[0047] - N15: For non-roaming scenarios, reference point between PCF (180) and AMF (150), for roaming scenarios, reference point between PCF (180) and AMF (150) within the visited network.

[0048] FIG. 2 illustrates a method for setting an NAS reject mode and deactivating a PDU (protocol data unit) session based on energy-related information of a UE in a registration procedure of a wireless communication system according to one embodiment of the present disclosure.

[0049] Step 0. A preference for energy usage of the UE may be set. The preference for energy usage of the UE may be set by the user, or may be set by configuration information (e.g., a UE Route Selection Policy (URSP) rule or an energy profile) received by the UE from the network (e.g., a PCF or AMF). For example, the preference for energy usage may include at least one of a threshold for the battery level of the UE and a threshold for energy usage of the UE. The threshold for energy usage of the UE may be measured at the UE or at the network. Alternatively, the threshold for energy usage of the UE may be measured by the amount of energy consumed for communication with the UE. In one embodiment, the preference for energy usage may be set per application (e.g., app ID or Single Network Slice Selection Assistance Information (S-NSSAI), data network name (DNN), or Connection Capability) or per UE (e.g., for multiple applications).

[0050] Step 1. In one embodiment, when the UE battery level falls below a set threshold, the UE may include energy related information (e.g., at least one of a UE battery level, a UE energy exceeded threshold indication, and an energy saving request indicator) in a Non-Access-Stratum (NAS) message (e.g., a registration request message) transmitted to the AMF via the NG-RAN.

[0051] In one embodiment, if a threshold related to energy usage (e.g., power consumption) of a UE is set (e.g., including at least one of a threshold for energy usage of the UE, a transmit bit rate per unit time of the UE, and a receive bit rate per unit time of the UE), and a parameter of the UE (e.g., including at least one of energy usage, power consumption, and bit rate) increases above the threshold, the UE may include energy related information (e.g., including at least one of energy usage of the UE, a UE energy usage exceeded threshold indication, and an energy saving request indicator) in a NAS message (e.g., a registration request message) transmitted to the AMF.

[0052] In one embodiment, the UE's battery level and energy saving request indicators included in the energy-related information may be included for each application or service. In this case, the energy-related information may include application identification information (e.g., at least one of application ID, application traffic category information (e.g., low latency, high bandwidth, enterprise), S-NSSAI, and DNN).

[0053] Step 2. When the AMF receives an NAS message from the UE, it can check whether there is UE subscription information. Alternatively, when the AMF receives a message from an NF (e.g., OAM, Energy Control Function, or SMF) that the energy consumption of the UE has exceeded a threshold for communication, it can check whether there is UE subscription information stored in the AMF.

[0054] If there is no UE subscription information stored in the AMF, the AMF can request subscription information for the UE from the UDM. The UDM can include the subscription information in the response message sent to the AMF. The subscription information can include at least one of the following: UE ID, whether energy saving is allowed for the UE, whether energy saving is allowed for app ID(s), S-NSSAI, or whether energy saving is allowed for the DNN.

[0055] Step 3. In one embodiment, if the NAS message received from the UE includes energy-related information, or the energy-related information includes a battery level or energy saving request indicator for the UE, the AMF may update the energy state (e.g., energy saving state #n, normal state) for the UE to a value indicating the energy saving state and determine the NAS reject mode. The AMF may also update the energy state and / or NAS reject mode only if the UE is allowed to save energy based on the UE subscription information.

[0056] In one embodiment, if the AMF receives an NAS message from the UE that includes energy-related information and the energy-related information includes a battery level or energy saving request indicator for the UE, the AMF may update the energy state (e.g., energy saving state #n, normal state) for the UE to a value indicating the energy saving state. The AMF may update the energy state only if the UE is permitted to save energy according to the UE subscription information.

[0057] In one embodiment, if an NAS message received from a UE includes energy-related information and the energy-related information includes application identification information, the AMF may decide to deactivate the PDU session(s) corresponding to the application identification information. The AMF may also deactivate only the PDU session(s) for the allowed app (or network slice) or service based on the UE subscription information.

[0058] Step 4. The AMF may include an active PDU session list (e.g., a list containing activated PDU session IDs) in the registration response (e.g., registration accept or registration reject) message sent to the UE. At this time, the AMF may not include the PDU session ID(s) for which deactivation was determined in Step 3 in the active PDU session list.

[0059] Step 5. AMF may send a message (e.g., SM Context Update message) to SMF requesting deactivation on a per-PDU session basis for the PDU session(s) for which deactivation was decided in Step 3.

[0060] Step 6. SMF can send N4 message to UPF to release AN tunnel (RAN tunnel).

[0061] Step 7. SMF can send a message to AMF to perform resource release for the PDU session.

[0062] Step 8. The AMF may send an N2 Resource Release Request message to the NG-RAN. The N2 Resource Release Request message may include information contained in the N2 SM Information message received from the SMF, and a Registration Accept message (or Registration Reject message). The Registration Accept message (or Registration Reject message) may include the PDU session status for the PDU session(s), which may indicate, for example, activated or deactivated.

[0063] In one embodiment, if the AMF determines to set the NAS reject mode for the UE in step 3, the AMF may transmit a registration accept message (or registration reject message) to the UE to set a back-off timer. For example, the AMF may include information including the back-off timer in the registration accept message (or registration reject message) transmitted to the UE. The AMF may include the PDU session status for the PDU sessions for which deactivation or deactivation reject has been determined in step 3 in the registration accept message (or registration reject message). The AMF may mark the PDU session status as deactivated for the PDU sessions for which deactivation has been determined in step 3. The AMF may mark the PDU session status as deactivation failed for the PDU sessions for which deactivation reject has been determined in step 3.

[0064] Step 8a. The NG-RAN may send a registration accept message (or registration reject message) to the UE. The UE may receive the registration accept message (or registration reject message) from the NG-RAN and store the status of the PDU session according to the PDU session status for each PDU session ID(s) included in the message. When the NG-RAN receives a registration reject message from the AMF, the NG-RAN may release the resource for the PDU session ID included in the registration reject message. If the received registration accept message (or registration reject message) includes a back-off timer and a cause (NAS reject due to energy), the UE may not transmit the NAS message until the back-off timer expires.

[0065] Step 9. The UE can send a NAS request to the AMF.

[0066] Step 10. If the UE's NAS reject mode is set, the AMF may send a reject message to the UE. The reject message may include at least one of a cause code indicating UE energy saving or a back-off timer. Upon receiving the back-off timer, the UE may transmit a NAS request only after the back-off timer expires.

[0067] FIG. 3 illustrates a method for performing NAS reject mode setting and PDU session activation based on energy-related information of a UE in a registration procedure of a wireless communication system according to one embodiment of the present disclosure.

[0068] Step 0. A UE's energy usage preference can be set. The UE's energy usage preference can be set by the user or by configuration information (e.g., a URSP rule or energy profile) received by the UE from the network (e.g., a PCF). For example, the energy usage preference can include at least one of a threshold for the UE's battery level or a threshold for the UE's energy usage. In one embodiment, the energy usage preference can be set per application (e.g., app ID or S-NSSAI, DNN, or Connection Capability) or per UE (e.g., for multiple applications).

[0069] Step 1. When the UE battery level rises above a configured threshold, the UE may include energy-related information (e.g., at least one of a UE battery level, a UE energy below the threshold indication, or an energy saving release request indicator) in an NAS message (e.g., a registration request message) transmitted to the AMF via the NG-RAN. The UE battery level, UE energy below the threshold indication, or energy saving request indicator included in the energy-related information may be included for each application or service. In this case, the energy-related information may include application identification information (e.g., at least one of an application ID, application traffic category information (e.g., low latency, high bandwidth, or enterprise), S-NSSAI, and DNN). If the AMF receives a NAS message from the UE that includes energy-related information (e.g., a UE battery level, a UE energy below the threshold indication, or an energy saving release request indicator), the AMF may decide to release the NAS reject mode for the UE and / or perform PDU session activation for one or more PDU sessions.

[0070] Step 2. If the NAS message received from the UE includes energy related information (e.g., at least one of a UE battery level, a UE energy below the threshold indication, or an energy saving release request indicator), the AMF may update the energy state (e.g., an energy saving state or a normal state) for the UE to a value indicating a normal state and release the NAS reject mode. If the NAS message received from the UE includes energy related information (e.g., at least one of a UE battery level, a UE energy below the threshold indication, or an energy saving release request indicator), and the energy related information includes application identification information, the AMF may decide to activate the PDU session(s) corresponding to the application identification information.

[0071] Step 3. AMF may send a message (e.g., a registration response message) to SMF requesting activation for each PDU session(s) for which deactivation was decided in Step 3.

[0072] Step 4. SMF can send an N4 message (e.g., SM Context Update message) to UPF to establish an AN tunnel.

[0073] Step 5. The SMF can send an N4 message to the UPF, including the PDU session ID (or N4 session ID), the RAN Tunnel Endpoint Identifier (TEID), and an activation indication. The UPF can establish an N3 tunnel for the PDU session based on the RAN TEID.

[0074] Step 6. The SMF may include a result indication indicating success or acceptance in the SM Context update response message it sends to the AMF. The SMF may then perform PDU session activation.

[0075] Step 7. The SMF may transmit information to the RAN via the AMF to establish resources for the PDU session. For example, the AMF may include the information contained in the N2 SM Information message received from the SMF, the Registration Accept message (or Registration Reject message), in the N2 request message and transmit it to the NG-RAN. The Registration Accept message (or Registration Reject message) may include the PDU session status (e.g., activated or deactivated) for the PDU session(s).

[0076] In one embodiment, if the AMF decides to release the NAS reject mode for the UE in step 2, the AMF may release the back-off timer by sending a registration accept message (or registration reject message) to the UE. For example, the AMF may include information including a back-off timer reset indicator (or a back-off timer set to 0) in the registration accept message (or registration reject message) sent to the UE.

[0077] In one embodiment, if the AMF decides to release the NAS reject mode in step 2, the AMF may not include a back-off timer in the Registration accept message (or the registration reject message). The AMF may include the PDU session status for the PDU Sessions for which the AMF decides to activate or reject the activation in step 2 in the Registration accept message (or the registration reject message). The AMF may mark the PDU session status as activated for the PDU session for which the AMF decides to activate in step 2. The AMF may mark the PDU session status as deactivated (or reactivation failed) for the PDU session for which the AMF decides to reject the activation in step 2. The AMF may include the cause and the back-off timer in the Registration accept message (or the registration reject message) for the PDU Session for which the PDU session (re)activation failed in step 2.

[0078] Step 7a. The NG-RAN may send a registration accept message (or registration reject message) to the UE. The UE may receive the registration accept message (or registration reject message) from the NG-RAN. The UE may then store the status of the PDU session based on the PDU session status for each PDU session ID(s) included in the registration accept message (or registration reject message).

[0079] In one embodiment, if there is a PDU session for which PDU session reactivation has failed and the cause indicates that the failure is due to energy, the UE may retransmit a request message for PDU session activation (e.g., a Service request message or a Registration request message) to the AMF after the received back-off timer has expired.

[0080] FIG. 4 illustrates a method for determining PDU session deactivation based on energy-related information and energy-related policy of a UE in a PDU session-related procedure of a wireless communication system according to one embodiment of the present disclosure.

[0081] Step 0. A preference for energy usage of the UE may be set. The preference for energy usage of the UE may be set by the user or by configuration information (e.g., a URSP rule or an energy profile, etc.) received by the UE from a network (e.g., a PCF). For example, the preference for energy usage may include at least one of a threshold for the battery level of the UE or a threshold for the energy usage of the UE. In one embodiment, the preference for energy usage may be set per application (e.g., an app ID or S-NSSAI, a DNN, or a Connection Capability) or per UE (e.g., for multiple applications).

[0082] Step 1. When the UE battery level falls below a configured threshold, the UE may include energy related information (e.g., at least one of the UE battery level, the UE energy exceeded threshold indication, or an energy saving request indicator) or at least one of the PDU session ID(s) (or DNN(s), S-NSSAI(s)) in an NAS message (e.g., a PDU session modification request message) transmitted to the AMF via the NG-RAN. The UE battery level and the energy saving request indicator included in the energy related information may be included for each application or service. In this case, the energy related information may include application identification information (e.g., one or more of the application ID, application traffic category information (e.g., low latency, high bandwidth, or enterprise), S-NSSAI, and DNN).

[0083] Step 2. The AMF may send an SM Context update request message to the SMF for the PDU session(s) corresponding to the information included in the PDU session modification request message received from the UE (e.g., PDU session ID(s), app ID(s), S-NSSAI(s), or DNN(s)).

[0084] In one embodiment, the AMF may include energy related information in the SM context update request message if the message received from the UE includes energy related information.

[0085] In one embodiment, the AMF may include an indicator requesting PDU session deactivation in the SM context update request message if the message received from the UE includes an indicator requesting PDU session deactivation.

[0086] Step 3. If the message received from the AMF includes energy-related information, the SMF may send a Policy Association Update message to the PCF, including the UE ID and / or energy-related information. Based on the received energy-related information, the PCF may determine an energy policy, including whether to apply energy saving to the PDU session. The PCF may then include the energy policy in the SM Policy Association Update Response message sent to the SMF.

[0087] Step 4. SMF can decide whether to deactivate the PDU session based on energy policy information received from PCF or its own judgment.

[0088] Step 4a. If the SMF decides to perform deactivation, the SMF may include a result indicating failure or rejection in the SM Context update response message sent to the AMF. At this time, the SMF may include information indicating that the UE's request failed in the PDU session modification response message sent to the UE through the AMF and may not perform PDU session deactivation.

[0089] Step 5. The SMF can send an N4 message to the UPF to release the AN tunnel. For example, the SMF can send the UPF an N4 message containing the PDU session ID and a deactivation indication. The UPF can then release or deactivate the N3 tunnel for the PDU session.

[0090] Step 6. If the SMF decides to perform deactivation, the SMF may include a message (e.g., N2 Resource Release request (PDU Session ID)) that it wants to send to the NG-RAN for PDU Session deactivation in the SM Context update response message or Namf_Communication_N1N2MessageTransfer message that it sends to the AMF.

[0091] Step 7. AMF may transmit a message (e.g., an N2 Resource Release Request message) containing information included in N2 SM Information or an N1 message included in a message received from SMF to NG-RAN.

[0092] Step 8. If the NG-RAN receives an N1 message from the AMF, it can send a PDU Session Modification Response message to the UE. If the NG-RAN receives an N2 resource release request (PDU Session ID) from the AMF, it can deactivate or release resources for the PDU session corresponding to the PDU Session ID.

[0093] FIG. 5 illustrates a method for activating a PDU session based on energy-related information of a UE in a Service Request procedure of a wireless communication system according to one embodiment of the present disclosure.

[0094] Step 0. A UE's energy usage preference can be configured. The UE's energy usage preference can be configured by the user or by configuration information (e.g., URSP rules or energy profiles) received by the UE from the network (e.g., PCF). For example, the energy usage preference can include at least one of a threshold for the UE's battery level or a threshold for the UE's energy usage.

[0095] In one embodiment, preferences for energy usage may be set per application (e.g., app ID, S-NSSAI, DNN, or Connection Capability) or per UE (e.g., for multiple applications).

[0096] Step 1. When the UE battery level rises above a configured threshold, the UE may include energy-related information (e.g., at least one of a UE battery level, a UE energy below the threshold indication, or an energy saving release request indicator) in a Service Request message transmitted to the AMF via the NG-RAN. The UE battery level, the UE energy below the threshold indication, or the energy saving request indicator included in the energy-related information may be included for each application or service. In this case, the energy-related information may include application identification information (e.g., at least one of an application ID, application traffic category information (e.g., low latency, high bandwidth, or enterprise), S-NSSAI, or DNN).

[0097] Step 2. AMF may send an SM Context update request message for the PDU session(s) corresponding to the information contained in the message received from the UE (e.g., PDU session ID(s), app ID(s), S-NSSAI(s), or DNN(s)).

[0098] In one embodiment, the AMF may include energy related information in the SM context update request message if the message received from the UE includes energy related information.

[0099] In one embodiment, the AMF may request PDU session activation by sending an SM context update request message for each PDU session if the message received from the UE includes PDU session ID(s) requesting PDU session activation.

[0100] Step 3. SMF can decide whether to activate the PDU session based on energy policy information received from PCF or its own judgment.

[0101] Step 4. If the SMF decides to perform activation, the SMF may send an N4 message to the UPF to establish an AN tunnel. More specifically, the SMF may send the UPF an N4 message containing at least one of a PDU session ID (or N4 session ID), a RAN Tunnel Endpoint Identifier (TEID), or an activation indication.

[0102] Step 5. If the SMF decides to perform activation, the UPF can establish an N3 tunnel for the PDU session based on the RAN TEID.

[0103] Step 6. If the SMF decides not to perform the activation, the SMF may include a result indicating failure or rejection and / or PDU session ID(s) in the SM Context update response message that it sends to the AMF. At this time, the SMF may include information indicating that the UE's request failed in the Service response message that it sends to the UE through the AMF, and may not perform the PDU session activation. More specifically, if the SMF decides to perform the activation, the SMF may include a result indication indicating success or acceptance in the SM Context update response message that it sends to the AMF, and perform the PDU session activation through steps 5-8.

[0104] Additionally, the SMF can pass information to the RAN via the AMF to establish resources for a PDU session.

[0105] Step 7. The AMF may transmit to the NG-RAN or the UE at least one of the information contained in the N2 SM Information received from the SMF or the MM NAS Service Accept. The MM NAS Service Accept may include the PDU session status for the PDU session(s), which may indicate, for example, whether activated or reactivation failed.

[0106] In one embodiment, the AMF may mark the PDU session status as activation for the PDU sessions that indicate success among the PDU session ID(s) included in the message received from the SMF in step 6.

[0107] In one embodiment, the AMF may mark the PDU session status as PDU session reactivation failed for the PDU session ID(s) included in the message received from the SMF in step 6 that indicate a failure.

[0108] In one embodiment, the AMF may include a cause and / or back-off timer in the MM NAS service Accept for PDU Sessions where PDU session (re)activation failed due to energy policy in step 6.

[0109] The UE can receive NAS service Accept from the NG-RAN and store the status of the PDU session according to the PDU session status by PDU session ID(s) included in the NAS service Accept message.

[0110] In one embodiment, if there is a PDU session for which PDU session reactivation has failed and the cause indicates that the failure is due to energy policy, the UE may retransmit a request message for PDU session activation (e.g., a Service request message or a Registration request message) to the AMF after the received back-off timer has expired.

[0111] FIG. 6 is a block diagram illustrating the structure of a terminal (UE) according to one embodiment of the present disclosure.

[0112] Referring to FIG. 6, the terminal of the present disclosure may include a processor (620), a transceiver (600), and a memory (610). However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more or fewer components than the components described above. Furthermore, the processor (620), the transceiver (600), and the memory (610) may be implemented in the form of a single chip.

[0113] According to one embodiment of the present disclosure, the processor (620) can control a series of processes by which the terminal can operate according to the above-described embodiments of the present disclosure. For example, the processor (620) can control components of the terminal to perform the network slice change support method according to the above-described embodiments. The processor (620) can control components of the terminal to perform the above-described embodiments of the present disclosure by executing a program stored in the memory (610). In addition, the processor (620) can be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor.

[0114] According to one embodiment of the present disclosure, the transceiver (600) can transmit and receive signals with a network entity, another terminal, or a base station. The signals transmitted and received with the network entity, another terminal, or a base station can include control information and data. The transceiver (600) can be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and frequency-converts a received signal. However, the transceiver (600) is only one embodiment, and the components of the transceiver (600) are not limited to the RF transmitter and RF receiver. In addition, the transceiver (600) can receive a signal through a wireless channel, output it to the processor (620), and transmit the signal output from the processor (620) through the wireless channel.

[0115] According to one embodiment of the present disclosure, the memory (610) can store programs and data necessary for the operation of the terminal. In addition, the memory (610) can store control information or data included in signals transmitted and received by the terminal. The memory (610) can be configured as a storage medium or a combination of storage media, such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there can be a plurality of memories (610). In addition, according to one embodiment, the memory (610) can also store a program for performing the aforementioned network slice change support method.

[0116] FIG. 7 is a block diagram illustrating the structure of a base station according to one embodiment of the present disclosure.

[0117] Referring to FIG. 7, the base station of the present disclosure may include a processor (720), a transceiver (700), and a memory (710). However, the components of the base station are not limited to the examples described above. For example, the base station may include more or fewer components than the components described above. Furthermore, the processor (720), the transceiver (700), and the memory (710) may be implemented in the form of a single chip.

[0118] According to one embodiment of the present disclosure, the processor (720) may control a series of processes by which the base station may operate according to the embodiments of the present disclosure described above. For example, the processor (720) may control components of the base station to perform the network slice change support method according to the embodiments described above. The processor (720) may control components of the base station to perform the embodiments of the present disclosure described above by executing a program stored in the memory (710). In addition, the processor (720) may be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor.

[0119] According to one embodiment of the present disclosure, the transceiver (700) can transmit and receive signals with a network entity, another base station, or a terminal. The signals transmitted and received with the network entity, another base station, or a terminal may include control information and data. The transceiver (700) may be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and frequency-downconverts a received signal. However, the transceiver (700) is only one embodiment, and the components of the transceiver (700) are not limited to the RF transmitter and RF receiver. In addition, the transceiver (700) may receive a signal through a wireless channel, output it to the processor (720), and transmit the signal output from the processor (720) through the wireless channel.

[0120] According to one embodiment of the present disclosure, the memory (710) can store programs and data necessary for the operation of the base station. In addition, the memory (710) can store control information or data included in signals transmitted and received by the base station. The memory (710) can be configured as a storage medium or a combination of storage media, such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there can be a plurality of memories (710). In addition, according to one embodiment, the memory (710) can store a program for performing the aforementioned network slice change support method.

[0121] FIG. 8 is a block diagram illustrating the structure of a network entity according to one embodiment of the present disclosure.

[0122] Referring to FIG. 8, the network entity of the present disclosure may include a processor (820), a transceiver (800), and a memory (810). However, the components of the network entity are not limited to the examples described above. For example, the network entity may include more or fewer components than the components described above. In addition, the processor (820), the transceiver (800), and the memory (810) may be implemented in the form of a single chip. In addition, according to one embodiment of the present disclosure, the network entity may refer to a network function (NF), and the NF may include a RAN, an AMF, a PCF, an UDM, an AF, a NEF, and a UTM.

[0123] According to one embodiment of the present disclosure, the processor (820) can control a series of processes by which the NF can operate according to the above-described embodiments of the present disclosure. For example, the processor (820) can control components of a network entity to perform a network slice change support method according to the above-described embodiments. The processor (820) can control components of the network entity to perform the above-described embodiments of the present disclosure by executing a program stored in the memory (810). In addition, the processor (820) can be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor.

[0124] According to one embodiment of the present disclosure, the transceiver (800) can transmit and receive signals with other network entities, base stations, or terminals. The signals transmitted and received with other network entities or terminals can include control information and data. The transceiver (800) can be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and frequency-converts a received signal. However, the transceiver (800) is only one embodiment, and the components of the transceiver (800) are not limited to the RF transmitter and RF receiver. In addition, the transceiver (800) can receive a signal through a wireless channel, output it to the processor (820), and transmit the signal output from the processor (820) through the wireless channel.

[0125] According to one embodiment of the present disclosure, the memory (810) may store programs and data necessary for the operation of the network entity. Furthermore, the memory (810) may store control information or data included in signals transmitted and received by the network entity. The memory (810) may be configured as a storage medium or a combination of storage media, such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. Furthermore, there may be a plurality of memories (810). Furthermore, according to one embodiment, the memory (810) may store a program for performing the aforementioned network slice change support method.

[0126] It should be noted that the configuration diagrams, exemplary diagrams of control / data signal transmission / reception methods, and exemplary diagrams of operating procedures illustrated in FIGS. 1 to 8 are not intended to limit the scope of the embodiments of the present disclosure. That is, not all components, entities, or operational steps described in FIGS. 1 to 8 should be construed as essential components for the implementation of the disclosure, and implementation may be performed within a scope that does not detract from the essence of the disclosure even if only some components are included.

[0127] The operations of the embodiments described above can be realized by providing a memory device storing the corresponding program code in any component within the device. That is, the control unit within the device can execute the operations described above by reading and executing the program code stored in the memory device through a processor or a CPU (Central Processing Unit).

[0128] The various components and modules of the entity or terminal device described in the present disclosure may be operated using hardware circuits, such as logic circuits based on complementary metal oxide semiconductors, firmware, software, and / or hardware and firmware and / or software embedded in a machine-readable medium. For example, various electrical structures and methods may be implemented using electrical circuits such as transistors, logic gates, and application-specific semiconductors.

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

[0130] 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 embodiments described in the claims or specification of the present disclosure.

[0131] 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 devices, compact disc-ROMs (CD-ROMs), digital versatile discs (DVDs) or other forms of optical storage devices, magnetic cassettes, or may be stored in memories formed by a combination of some or all of these. In addition, each configuration memory may include multiple copies.

[0132] Additionally, the program may be stored on an attachable storage device that is accessible via a communication network, such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), 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 disclosure 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 disclosure.

[0133] In the specific embodiments of the present disclosure described above, components included in the disclosure are expressed singularly or plurally, 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 disclosure is not limited to singular or plural components. Components expressed in plural may be composed of singular elements, or components expressed in singular may be composed of plural elements.

[0134] While the detailed description of this disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the described embodiments, but should be defined not only by the scope of the claims described below, but also by equivalents thereof.

Claims

1. In a method performed by a terminal of a wireless communication system, A step of receiving, from a network entity, configuration information including a threshold value regarding a battery level of the terminal or a threshold value regarding energy usage of the terminal; a step of transmitting a request message including energy-related information based on the threshold value to the network entity; and A step of receiving a response message to the request message based on the energy-related information, The above response message contains identification information for activating or deactivating a PDU (protocol data unit) session, A method wherein the above network entity includes a PCF (policy control function) entity or an AMF (access and mobility management function) entity.

2. In paragraph 1, If the battery level of the terminal is less than or equal to the threshold value, the response message includes at least one of identification information for deactivating the PDU session or an indicator for resetting a back-off timer, A method wherein resources for at least one PDU session are disabled based on the above identification information.

3. In paragraph 1, If the battery level of the terminal is greater than or equal to the threshold value, the response message includes at least one of identification information for the activation of the PDU session or information for setting a back-off timer, A method wherein resources for at least one PDU session are activated based on the above identification information.

4. In paragraph 1, The above threshold value is set for each application, S-NSSAI (single network slice selection assistance information), DNN (data network name), or terminal. A method wherein the energy-related information includes at least one of information for indicating a battery level of the terminal or instruction information for requesting or releasing energy saving.

5. A method performed by a network entity of a wireless communication system, A step of transmitting setting information including a threshold value regarding a battery level of the terminal or a threshold value regarding energy usage of the terminal to the terminal; A step of receiving a request message including energy-related information based on the threshold value from the terminal; and A step of transmitting a response message to the request message based on the energy-related information, The above response message contains identification information for activating or deactivating a PDU (protocol data unit) session, A method wherein the above network entity includes a PCF (policy control function) entity or an AMF (access and mobility management function) entity.

6. In paragraph 5, If the battery level of the terminal is less than or equal to the threshold value, the response message includes at least one of identification information for deactivating the PDU session or an indicator for resetting a back-off timer, A method wherein resources for at least one PDU session are disabled based on the above identification information.

7. In paragraph 5, If the battery level of the terminal is greater than or equal to the threshold value, the response message includes at least one of identification information for the activation of the PDU session or information for setting a back-off timer, A method wherein resources for at least one PDU session are activated based on the above identification information.

8. In paragraph 5, The above threshold value is set for each application, S-NSSAI (single network slice selection assistance information), DNN (data network name), or terminal. A method wherein the energy-related information includes at least one of information for indicating a battery level of the terminal or instruction information for requesting or releasing energy saving.

9. In the terminal of a wireless communication system, Transmitter and receiver; and At least one control unit connected to the above transceiver unit, At least one control unit: Receive configuration information from a network entity, including a threshold value regarding the battery level of the terminal or a threshold value regarding the energy usage of the terminal; To the above network entity, a request message containing energy-related information is transmitted based on the above threshold value, and Based on the above energy-related information, a response message to the request message is set to be received, The above response message contains identification information for activating or deactivating a PDU (protocol data unit) session, A terminal in which the above network entity includes a PCF (policy control function) entity or an AMF (access and mobility management function) entity.

10. In paragraph 9, If the battery level of the terminal is less than or equal to the threshold value, the response message includes at least one of identification information for deactivating the PDU session or an indicator for resetting a back-off timer, A terminal in which resources for at least one PDU session are disabled based on the above identification information.

11. In paragraph 9, If the battery level of the terminal is greater than or equal to the threshold value, the response message includes at least one of identification information for the activation of the PDU session or information for setting a back-off timer, A terminal in which resources for at least one PDU session are activated based on the above identification information.

12. In paragraph 9, The above threshold value is set for each application, S-NSSAI (single network slice selection assistance information), DNN (data network name), or terminal. A terminal, wherein the energy-related information includes at least one of information for indicating a battery level of the terminal or instruction information for requesting or releasing energy saving.

13. In the network entity of a wireless communication system, Transmitter and receiver; and At least one control unit connected to the above transceiver unit, At least one control unit: Transmitting setting information including a threshold value regarding the battery level of the terminal or a threshold value regarding the energy usage of the terminal to the terminal, Receive a request message including energy-related information based on the threshold value from the terminal, and Based on the above energy-related information, a response message to the request message is set to be transmitted, The above response message contains identification information for activating or deactivating a PDU (protocol data unit) session, The above network entity is a network entity that includes a PCF (policy control function) entity or an AMF (access and mobility management function) entity.

14. In paragraph 13, If the battery level of the terminal is less than or equal to the threshold value, the response message includes at least one of identification information for deactivating the PDU session or an indicator for resetting a back-off timer, A network entity, wherein resources for at least one PDU session are disabled based on the above identification information.

15. In paragraph 13, If the battery level of the terminal is greater than or equal to the threshold value, the response message includes at least one of identification information for the activation of the PDU session or information for setting a back-off timer, A network entity for which resources for at least one PDU session are activated based on the above identification information.

Images