Communication based on computing resources

Abstract

One disclosure of the present disclosure provides a method. The method may comprise the steps in which: a first network entity receives, from a second network entity, a first configuration update message including information related to a computing resource for the second network entity; the first network entity determines to switch off a second network node on the basis of the information related to the computing resource for a second network; and the first network entity transmits, to the second network entity, a second configuration update message including information related to the switch off.

Description

Communication based on computing resources

[0001] This specification relates to mobile communication.

[0002] 3GPP (3rd Generation Partnership Project) LTE (Long-Term Evolution) is a technology designed to enable high-speed packet communication. Many methods have been proposed to achieve LTE goals, such as reducing costs for users and operators, improving service quality, expanding coverage, and increasing system capacity. As high-level requirements, 3GPP LTE demands reduced cost per bit, improved service availability, flexible use of frequency bands, a simple structure, open interfaces, and appropriate power consumption of terminals.

[0003] Work has begun at the ITU (International Telecommunication Union) and 3GPP to develop requirements and specifications for New Radio (NR) systems. 3GPP must identify and develop the technical components necessary to successfully standardize NR in a timely manner, satisfying both urgent market demands and the longer-term requirements presented by the ITU-R (ITU Radio communication sector) IMT (International Mobile Telecommunications)-2020 process. Furthermore, NR must be able to utilize any spectrum band up to at least 100 GHz so that it can be used for wireless communication even in the distant future.

[0004] NR targets a single technical framework that covers all deployment scenarios, usage scenarios, and requirements, including eMBB (enhanced Mobile Broadband), mMTC (massive Machine Type-Communications), and URLLC (Ultra-Reliable and Low Latency Communications). NR must be forward compatible by nature.

[0005] Discussions regarding 6G mobile communication systems are underway. For example, various services such as sensing services, immersive reality, and / or multi-domal services may be provided based on AI technology. However, according to conventional technology, there is a problem in that the processing and / or computing capabilities required to provide these services are not effectively supported. For example, there is a problem in that the method by which base stations utilize computing resources is not supported.

[0006] In one embodiment, a method is provided. The method may include the steps of: a first network entity receiving a first configuration update message from a second network entity, the first network entity including information regarding computing resources for the second network entity; the first network entity determining to switch off the second network node based on the information regarding computing resources for the second network; and the first network entity transmitting a second configuration update message to the second network entity, the second network entity including information regarding switching off.

[0007] In another aspect, a device for implementing the above method is provided.

[0008] In one embodiment, a method is provided. The method may include the step of a second network entity transmitting to a first network entity a first configuration update message containing information related to computing resources for the second network entity; and the step of the second network entity receiving from the first network entity a second configuration update message containing information related to a switch-off.

[0009] In another aspect, a device for implementing the above method is provided.

[0010] FIG. 1 shows an example of a communication system to which the implementation of the present specification is applied.

[0011] FIG. 2 shows an example of a wireless device to which the implementation of the present specification applies.

[0012] FIG. 3 shows an example of a UE to which the implementation of the present specification applies.

[0013] FIG. 4 shows an example of a 5G system structure to which the implementation of the present specification is applied.

[0014] FIG. 5 illustrates an example of a procedure related to an O-cloud notification according to one embodiment of the disclosure of the present specification.

[0015] FIG. 6 shows an example of a gNB-DU setting update procedure according to one embodiment of the disclosure of the present specification.

[0016] FIG. 7 shows an example of a gNB-CU setting update procedure according to one embodiment of the disclosure of the present specification.

[0017] FIG. 8 illustrates an example of a procedure including operations according to one embodiment of the disclosure of the present specification.

[0018] FIG. 9 illustrates an example of an NG-RAN node configuration update procedure according to one embodiment of the disclosure of the present specification.

[0019] FIG. 10 illustrates an example of a procedure according to one embodiment of the disclosure of the present specification.

[0020] The following techniques, devices, and systems may be applied to various wireless multiple access systems. Examples of multiple access systems include Code Division Multiple Access (CDMA) systems, Frequency Division Multiple Access (FDMA) systems, Time Division Multiple Access (TDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Multi-Carrier Frequency Division Multiple Access (MC-FDMA) systems. CDMA may be implemented through wireless technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA may be implemented through wireless technologies such as Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), or Enhanced Data Rates for GSM Evolution (EDGE). OFDMA can be implemented through wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or E-UTRA (Evolved UTRA). UTRA is part of UMTS (Universal Mobile Telecommunications System). 3GPP (3rd Generation Partnership Project) LTE (Long-Term Evolution) is part of E-UMTS (Evolved UMTS) using E-UTRA.3GPP LTE uses OFDMA in the downlink (DL) and SC-FDMA in the uplink (UL). Evolutions of 3GPP LTE include LTE-A (Advanced), LTE-A Pro, and / or 5G NR (New Radio).

[0021] For convenience of explanation, the implementation of this specification is described primarily in relation to 3GPP-based wireless communication systems. However, the technical characteristics of this specification are not limited thereto. For example, the following detailed description is provided based on a mobile communication system corresponding to a 3GPP-based wireless communication system, but aspects of this specification that are not limited to 3GPP-based wireless communication systems may be applied to other mobile communication systems.

[0022] For terms and technologies used in this specification that are not specifically described, reference may be made to wireless communication standard documents published prior to this specification.

[0023] In this specification, "A or B" may mean "only A," "only B," or "both A and B." Alternatively, in this specification, "A or B" may be interpreted as "A and / or B." For example, in this specification, "A, B or C" may mean "only A," "only B," "only C," or "any combination of A, B and C."

[0024] A slash ( / ) or a comma used in this specification may mean "and / or." For example, "A / B" may mean "A and / or B." Accordingly, "A / B" may mean "only A," "only B," or "both A and B." For example, "A, B, C" may mean "A, B or C."

[0025] In this specification, "at least one of A and B" may mean "only A," "only B," or "both A and B." Additionally, in this specification, the expressions "at least one of A or B" or "at least one of A and / or B" may be interpreted as synonymous with "at least one of A and B."

[0026] Additionally, in this specification, "at least one of A, B and C" may mean "only A," "only B," "only C," or "any combination of A, B and C." Furthermore, "at least one of A, B or C" or "at least one of A, B and / or C" may mean "at least one of A, B and C."

[0027] Additionally, parentheses used in this specification may mean "for example." Specifically, when indicated as "control information (PDCCH)," "PDCCH" may be proposed as an example of "control information." In other words, "control information" in this specification is not limited to "PDCCH," and "PDCCH" may be proposed as an example of "control information." Furthermore, even when indicated as "control information (i.e., PDCCH)," "PDCCH" may be proposed as an example of "control information."

[0028] Technical features described individually within a single drawing in this specification may be implemented individually or simultaneously.

[0029] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification may be applied to various fields where wireless communication and / or connectivity between devices (e.g., 5G) is required.

[0030] The present specification will be described in more detail below with reference to the drawings. In the following drawings and / or description, the same reference numerals may refer to the same or corresponding hardware blocks, software blocks, and / or function blocks unless otherwise indicated.

[0031] FIG. 1 shows an example of a communication system to which the implementation of the present specification is applied.

[0032] The 5G usage scenario shown in FIG. 1 is merely an example, and the technical features of this specification may be applied to other 5G usage scenarios not shown in FIG. 1.

[0033] The three main requirement categories for 5G are (1) enhanced Mobile BroadBand (eMBB) category, (2) massive Machine Type Communication (mMTC) category, and (3) Ultra-Reliable and Low Latency Communications (URLLC) category.

[0034] Referring to FIG. 1, the communication system (1) includes wireless devices (100a to 100f), a base station (BS; 200), and a network (300). FIG. 1 illustrates a 5G network as an example of the network of the communication system (1), but the implementation of the present specification is not limited to a 5G system and may be applied to future communication systems beyond a 5G system.

[0035] The base station (200) and the network (300) can be implemented as wireless devices, and a specific wireless device can operate as a base station / network node in relation to another wireless device.

[0036] Wireless devices (100a to 100f) represent devices that perform communication using Radio Access Technology (RAT) (e.g., 5G NR or LTE) and may also be referred to as communication / wireless / 5G devices. Wireless devices (100a to 100f) may include, but are not limited to, robots (100a), vehicles (100b-1 and 100b-2), eXtended Reality (XR) devices (100c), portable devices (100d), home appliances (100e), Internet-Of-Things (IoT) devices (100f), and Artificial Intelligence (AI) devices / servers (400). For example, vehicles may include vehicles with wireless communication capabilities, autonomous vehicles, and vehicles capable of performing communication between vehicles. Vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices and may be implemented in the form of HMDs (Head-Mounted Devices) and HUDs (Head-Up Displays) mounted on vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signs, vehicles, robots, etc. Portable devices may include smartphones, smart pads, wearable devices (e.g., smartwatches or smart glasses), and computers (e.g., laptops). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters.

[0037] In this specification, wireless devices (100a to 100f) may be referred to as User Equipment (UE). The UE may include, for example, a mobile phone, a smartphone, a laptop computer, a digital broadcasting terminal, a PDA (Personal Digital Assistant), a PMP (Portable Multimedia Player), a navigation system, a slate PC, a tablet PC, an ultrabook, a vehicle, a vehicle with autonomous driving capabilities, a connected car, a UAV, an AI module, a robot, an AR device, a VR device, an MR device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a fintech device (or financial device), a security device, a weather / environment device, a 5G service-related device, or a device related to the Fourth Industrial Revolution.

[0038] Wireless devices (100a to 100f) can be connected to a network (300) through a base station (200). AI technology may be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) through the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, and a network after 5G. The wireless devices (100a to 100f) may communicate with each other through the base station (200) / network (300), but they may also communicate directly (e.g., sidelink communication) without going through the base station (200) / network (300). For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (Vehicle-to-Vehicle) / V2X (Vehicle-to-everything) communication). Also, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0039] Wireless communication / connections (150a, 150b, 150c) can be established between wireless devices (100a to 100f) and / or between wireless devices (100a to 100f) and base station (200) and / or between base station (200). Here, the wireless communication / connections can be established through various RATs (e.g., 5G NR), such as uplink / downlink communication (150a), sidelink communication (150b) (or D2D (Device-To-Device) communication), and communication between base stations (150c) (e.g., relay, IAB (Integrated Access and Backhaul)). Through the wireless communication / connections (150a, 150b, 150c), wireless devices (100a to 100f) and base station (200) can transmit / receive wireless signals to / from each other. For example, wireless communication / connection (150a, 150b, 150c) may transmit / receive signals through various physical channels. To this end, based on various proposals in this specification, at least some of the following may be performed: a process for setting various configuration information for transmitting / receiving wireless signals, a process for various signal processing (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and a resource allocation process.

[0040] NR supports multiple numerologies or subcarrier spacings (SCS) to support various 5G services. For example, when the SCS is 15 kHz, it supports a wide area in traditional cellular bands; when the SCS is 30 kHz / 60 kHz, it supports dense-urban areas, lower latency, and wider carrier bandwidth; and when the SCS is 60 kHz or higher, it supports a bandwidth greater than 24.25 GHz to overcome phase noise.

[0041] The NR frequency band can be defined by two types of frequency ranges (FR1, FR2). The numerical values ​​of the frequency ranges may change. For example, the two types of frequency ranges (FR1, FR2) may be as shown in Table 1 below. For convenience of explanation, among the frequency ranges used in the NR system, FR1 may mean "sub 6GHz range" and FR2 may mean "above 6GHz range" and may be referred to as Millimeter Wave (mmW).

[0042] Frequency Range Definition Frequency Range Subcarrier Spacing FR1 450 MHz - 6000 MHz 15, 30, 60 kHz FR2 24 250 MHz - 52600 MHz 60, 120, 240 kHz

[0043] As described above, the numerical values ​​of the frequency range of the NR system may change. For example, FR1 may include a band of 410 MHz to 7125 MHz as shown in Table 2 below. That is, FR1 may include a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher. For example, the frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher included within FR1 may include an unlicensed band. The unlicensed band may be used for various purposes, for example, for communication for vehicles (e.g., autonomous driving).

[0044] Frequency Range Definition Frequency Range Subcarrier Spacing FR1 4 10 MHz - 7 125 MHz 15, 30, 60 kHz FR2 24 250 MHz - 5 2600 MHz 60, 120, 240 kHz

[0045] Here, the wireless communication technology implemented in the wireless device of this specification may include LTE, NR, and 6G, as well as NarrowBand IoT (NB-IoT) for low-power communication. For example, NB-IoT technology may be an example of Low Power Wide Area Network (LPWAN) technology and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, but is not limited to the names mentioned above. Additionally, or generally, the wireless communication technology implemented in the wireless device of this specification may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as eMTC (enhanced MTC). For example, LTE-M technology may be implemented in at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (Non-Bandwidth Limited), 5) LTE-MTC, 6) LTE MTC, and / or 7) LTE M, and is not limited to the names mentioned above. Additionally or generally, wireless communication technology implemented in the wireless device of this specification may include at least one of ZigBee, Bluetooth, and / or LPWAN for low-power communication, and is not limited to the names mentioned above. For example, ZigBee technology can create Personal Area Networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be referred to by various names.

[0046] FIG. 2 shows an example of a wireless device to which the implementation of the present specification applies.

[0047] In FIG. 2, the first wireless device (100) and / or the second wireless device (200) may be implemented in various forms depending on the use example / service. For example, {the first wireless device (100) and the second wireless device (200)} may correspond to at least one of {wireless devices (100a–100f) and base station (200)}, {wireless devices (100a–100f) and wireless devices (100a–100f)} and / or {base station (200) and base station (200)} of FIG. 1. The first wireless device (100) and / or the second wireless device (200) may be composed of various components, devices / parts and / or modules.

[0048] The first wireless device (100) may include at least one transceiver such as a transceiver (106), at least one processing chip such as a processing chip (101), and / or one or more antennas (108).

[0049] The processing chip (101) may include at least one processor, such as a processor (102), and at least one memory, such as a memory (104). Additionally and / or generally, the memory (104) may be placed outside the processing chip (101).

[0050] The processor (102) can control the memory (104) and / or the transceiver (106) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein. For example, the processor (102) may process information within the memory (104) to generate a first information / signal and transmit a wireless signal containing the first information / signal through the transceiver (106). The processor (102) may receive a wireless signal containing a second information / signal through the transceiver (106) and process the second information / signal to store the obtained information in the memory (104).

[0051] Memory (104) may be connected to the processor (102) so as to be operable. Memory (104) may store various types of information and / or instructions. Memory (104) may store firmware and / or software code (105) that implements code, instructions, and / or a set of instructions that perform the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification when executed by the processor (102). For example, firmware and / or software code (105) may implement instructions that perform the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification when executed by the processor (102). For example, firmware and / or software code (105) may control the processor (102) to perform one or more protocols. For example, firmware and / or software code (105) may control the processor (102) to perform one or more wireless interface protocol layers.

[0052] Here, the processor (102) and memory (104) may be part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). A transceiver (106) may be connected to the processor (102) and may transmit and / or receive a wireless signal through one or more antennas (108). Each transceiver (106) may include a transmitter and / or receiver. The transceiver (106) may be interchangeably used with an RF (Radio Frequency) unit. In this specification, the first wireless device (100) may represent a communication modem / circuit / chip.

[0053] The second wireless device (200) may include at least one transceiver such as a transceiver (206), at least one processing chip such as a processing chip (201), and / or one or more antennas (208).

[0054] The processing chip (201) may include at least one processor, such as a processor (202), and at least one memory, such as a memory (204). Additionally and / or generally, the memory (204) may be placed outside the processing chip (201).

[0055] The processor (202) can control the memory (204) and / or the transceiver (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein. For example, the processor (202) may process information within the memory (204) to generate a third information / signal and transmit a wireless signal containing the third information / signal through the transceiver (206). The processor (202) may receive a wireless signal containing a fourth information / signal through the transceiver (206) and process the fourth information / signal to store the obtained information in the memory (204).

[0056] Memory (204) may be connected to the processor (202) so as to be operable. Memory (204) may store various types of information and / or instructions. Memory (204) may store firmware and / or software code (205) that implements code, instructions, and / or sets of instructions that perform descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this specification when executed by the processor (202). For example, firmware and / or software code (205) may implement instructions that perform descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this specification when executed by the processor (202). For example, firmware and / or software code (205) may control the processor (202) to perform one or more protocols. For example, firmware and / or software code (205) may control the processor (202) to perform one or more wireless interface protocol layers.

[0057] Here, the processor (202) and memory (204) may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). A transceiver (206) may be connected to the processor (202) and transmit and / or receive a wireless signal through one or more antennas (208). Each transceiver (206) may include a transmitter and / or receiver. The transceiver (206) may be interchangeably used with an RF unit. In this specification, the second wireless device (200) may represent a communication modem / circuit / chip.

[0058] Hereinafter, hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as a PHY (physical) layer, a MAC (Media Access Control) layer, an RLC (Radio Link Control) layer, a PDCP (Packet Data Convergence Protocol) layer, an RRC (Radio Resource Control) layer, and an SDAP (Service Data Adaptation Protocol) layer). One or more processors (102, 202) may generate one or more PDUs (Protocol Data Units), one or more SDUs (Service Data Units), messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification. One or more processors (102, 202) may generate a signal (e.g., baseband signal) including a PDU, SDU, message, control information, data, or information according to the description, function, procedure, proposal, method, and / or operation flowchart disclosed in this specification and provide it to one or more transceivers (106, 206). One or more processors (102, 202) may receive a signal (e.g., baseband signal) from one or more transceivers (106, 206) and may obtain a PDU, SDU, message, control information, data, or information according to the description, function, procedure, proposal, method, and / or operation flowchart disclosed in this specification.

[0059] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, and / or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, and / or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), and / or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). For example, one or more processors (102, 202) may be composed of a set of communication control processors, application processors (APs), electronic control units (ECUs), central processing units (CPUs), graphic processing units (GPUs), and memory control processors. One or more memories (104, 204) may be connected to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. One or more memories (104, 204) may be composed of Random Access Memory (RAM), Dynamic RAM (DRAM), Read-Only Memory (ROM), Erasable Programmable ROM (EPROM), flash memory, volatile memory, non-volatile memory, hard drive, register, cache memory, computer read storage media, and / or combinations thereof.One or more memories (104, 204) may be located inside and / or outside of one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) through various technologies such as wired or wireless connections.

[0060] One or more transceivers (106, 206) may transmit user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification to one or more other devices. One or more transceivers (106, 206) may receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification from one or more other devices. For example, one or more transceivers (106, 206) may be connected to one or more processors (102, 202) and may transmit and receive wireless signals. For example, one or more processors (102, 202) may control one or more transceivers (106, 206) to transmit user data, control information, wireless signals, etc., to one or more other devices. Additionally, one or more processors (102, 202) can control one or more transceivers (106, 206) to receive user data, control information, wireless signals, etc. from one or more other devices.

[0061] One or more transceivers (106, 206) may be connected to one or more antennas (108, 208). Additionally and / or generally, one or more transceivers (106, 206) may include one or more antennas (108, 208). One or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, etc., mentioned in the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein through one or more antennas (108, 208). In this specification, one or more antennas (108, 208) may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports).

[0062] One or more transceivers (106, 206) can convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202). One or more transceivers (106, 206) can convert processed user data, control information, wireless signals / channels, etc. from baseband signals to RF band signals using one or more processors (102, 202). To this end, one or more transceivers (106, 206) may include (analog) oscillators and / or filters. For example, one or more transceivers (106, 206) can up-convert an OFDM baseband signal into an OFDM signal through an (analog) oscillator and / or filter under the control of one or more processors (102, 202) and transmit the up-converted OFDM signal at a carrier frequency. One or more transceivers (106, 206) can receive an OFDM signal at a carrier frequency and down-convert the OFDM signal into an OFDM baseband signal through an (analog) oscillator and / or filter under the control of one or more processors (102, 202).

[0063] Although not illustrated in FIG. 2, the wireless device (100, 200) may include additional components. The additional components (140) may be configured in various ways depending on the type of the wireless device (100, 200). For example, the additional components (140) may include at least one of a power unit / battery, an input / output (I / O) device (e.g., audio I / O port, video I / O port), a driving unit, and a computing unit. The additional components (140) may be connected to one or more processors (102, 202) through various technologies, such as wired or wireless connections.

[0064] In an implementation of the present specification, the UE may operate as a transmitting device in the uplink and as a receiving device in the downlink. In an implementation of the present specification, the base station may operate as a receiving device in the UL and as a transmitting device in the DL. For technical convenience, it is generally assumed that the first wireless device (100) operates as a UE and the second wireless device (200) operates as a base station. For example, a processor (102) connected to, mounted on, or released to the first wireless device (100) may be configured to perform UE operations according to an implementation of the present specification or to control a transceiver (106) to perform UE operations according to an implementation of the present specification. A processor (202) connected to, mounted on, or released to the second wireless device (200) may be configured to perform base station operations according to an implementation of the present specification or to control a transceiver (206) to perform base station operations according to an implementation of the present specification.

[0065] In this specification, the base station may be referred to as Node B, eNode B, or gNB.

[0066] FIG. 3 shows an example of a UE to which the implementation of the present specification applies.

[0067] Referring to FIG. 3, the UE (100) can correspond to the first wireless device (100) of FIG. 2.

[0068] The UE (100) includes a processor (102), memory (104), transceiver (106), one or more antennas (108), a power management module (141), a battery (142), a display (143), a keypad (144), a SIM (Subscriber Identification Module) card (145), a speaker (146), and a microphone (147).

[0069] The processor (102) may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein. The processor (102) may be configured to control one or more other components of the UE (100) to implement the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein. Layers of a wireless interface protocol may be implemented in the processor (102). The processor (102) may include an ASIC, other chipsets, logic circuits, and / or data processing devices. The processor (102) may be an application processor. The processor (102) may include at least one of a DSP, a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), and a modem (modulator and demodulator). An example of the processor (102) is the SNAPDRAGON manufactured by Qualcomm®. TM Series processor, EXYNOS made by Samsung® TM Series processors, A Series processors made by Apple®, HELIO made by MediaTek® TM Series processors, ATOM made by Intel® TM It can be found in series processors or corresponding next-generation processors.

[0070] Memory (104) is coupled to the processor (102) so as to be operable and stores various information for operating the processor (102). Memory (104) may include ROM, RAM, flash memory, memory card, storage medium and / or other storage device. When the implementation is implemented in software, the technology described herein may be implemented using modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, proposals, methods and / or operation flowcharts disclosed herein. Modules may be stored in memory (104) and executed by the processor (102). Memory (104) may be implemented within the processor (102) or outside the processor (102), in which case it may be communicatively coupled to the processor (102) through various methods known in the technology.

[0071] A transceiver (106) is coupled to operate with a processor (102) and transmits and / or receives a wireless signal. The transceiver (106) includes a transmitter and a receiver. The transceiver (106) may include a baseband circuit for processing a wireless frequency signal. The transceiver (106) controls one or more antennas (108) to transmit and / or receive a wireless signal.

[0072] The power management module (141) manages the power of the processor (102) and / or the transceiver (106). The battery (142) supplies power to the power management module (141).

[0073] The display (143) outputs the result processed by the processor (102). The keypad (144) receives input to be used by the processor (102). The keypad (144) can be displayed on the display (143).

[0074] A SIM card (145) is an integrated circuit for securely storing an International Mobile Subscriber Identity (IMSI) and associated keys, and is used to identify and authenticate a subscriber in a mobile device such as a mobile phone or computer. Additionally, contact information can be stored on many SIM cards.

[0075] The speaker (146) outputs sound-related results processed by the processor (102). The microphone (147) receives sound-related input to be used by the processor (102).

[0076] FIG. 4 shows an example of a 5G system structure to which the implementation of the present specification is applied.

[0077] The 5G system (5GS) structure consists of the following network functions (NF).

[0078] - AUSF (Authentication Server Function)

[0079] -AMF (Access and Mobility Management Function)

[0080] - DN (Data Network), for example, operator services, internet access, or third-party services

[0081] - USDF (Unstructured Data Storage Function)

[0082] - NEF (Network Exposure Function)

[0083] - I-NEF (Intermediate NEF)

[0084] - NRF (Network Repository Function)

[0085] - NSSF (Network Slice Selection Function)

[0086] - PCF (Policy Control Function)

[0087] - SMF (Session Management Function)

[0088] - UDM (Unified Data Management)

[0089] - UDR (Unified Data Repository)

[0090] - UPF (User Plane Function)

[0091] - UCMF (UE radio Capability Management Function)

[0092] - AF (Application Function)

[0093] - UE (User Equipment)

[0094] - (R)AN ((Radio) Access Network)

[0095] - 5G-EIR (5G-Equipment Identity Register)

[0096] - NWDAF (Network Data Analytics Function)

[0097] - CHF (CHarging Function)

[0098] 또한, 다음과 같은 네트워크 기능이 고려될 수 있다.

[0099] - N3IWF (Non-3GPP InterWorking Function)

[0100] - TNGF (Trusted Non-3GPP Gateway Function)

[0101] - W-AGF (Wireline Access Gateway Function)

[0102] Figure 4 shows the 5G system structure in a non-roaming case using a reference point representation showing how various network functions interact with each other.

[0103] In Figure 4, UDSF, NEF, and NRF are not described for clarity of the point-to-point diagram. However, all network functions shown can interact with UDSF, UDR, NEF, and NRF as needed.

[0104] For clarity, the connection between UDR and other NFs (e.g., PCF) is not shown in FIG. 4. For clarity, the connection between NWDAF and other NFs (e.g., PCF) is not shown in FIG. 4.

[0105] The 5G system structure includes the following reference points.

[0106] - N1: Reference point between UE and AMF.

[0107] - N2: Reference point between (R)AN and AMF.

[0108] - N3: Reference point between (R)AN and UPF.

[0109] - N4: Reference point between SMF and UPF.

[0110] - N6: Reference point between the UPF and the data network.

[0111] - N9: Reference point between two UPFs.

[0112] The following reference points show the interactions that exist between the NF services of NF.

[0113] - N5: Reference point between PCF and AF.

[0114] - N7: Reference point between SMF and PCF.

[0115] - N8: Reference point between UDM and AMF.

[0116] - N10: Reference point between UDM and SMF.

[0117] - N11: Reference point between AMF and SMF.

[0118] - N12: Reference point between AMF and AUSF.

[0119] - N13: Reference point between UDM and AUSF.

[0120] - N14: Reference point between two AMFs.

[0121] - N15: Reference point between PCF and AMF for non-roaming scenarios, reference point between PCF and AMF of the visited network for roaming scenarios.

[0122] - N16: Reference point between two SMFs (in the case of roaming, between the SMF of the visited network and the SMF of the home network)

[0123] - N22: Reference point between AMF and NSSF.

[0124] In some cases, two NFs may need to be connected to each other to service the UE.

[0125] Discussions regarding 6G mobile communication systems are underway. For example, various services such as sensing services, immersive reality, and / or multi-domal services may be provided based on AI technology. These services can provide users with more effective and / or high-quality services and / or Quality of Experience (QoE).

[0126] However, according to the prior art, there is a problem in that the technology for implementing these actual services is not defined. For example, according to the prior art, there is a problem in that the processing and / or computing capabilities for providing these services are not effectively supported. For example, there is a problem in that the method by which a base station utilizes computing resources is not supported.

[0127] A study on 6G mobile communication systems, Release 20 / [FS_6G-REQ] Study on 6G Use Cases and Service Requirements (SP-241391), has been initiated in SA1. Agreed candidate scenarios are scheduled to be added to TR 22.870.

[0128] However, the discussion is limited to basic requirements, and the definitions of functional structures, procedures, and detailed protocols (e.g., stage 2 / stage 3) are still at a stage where studies have not yet begun. In other words, there is a problem in that the technologies for implementing actual 6G-related services have not been defined.

[0129] In particular, various 6G-related services, such as sensing services and immersive reality / multi-dominal services, are expected to provide users with more effective and higher-quality services / QoE by utilizing AI technology. Therefore, processing and computing capabilities are critical. Network nodes, high-performance on-device AI terminals, and / or high-performance base stations of 6G systems are highly likely to be equipped with exceptionally high processing capabilities, such as Neural Processing Units (NPUs) and Graphics Processing Units (GPUs).

[0130] In the disclosure of this specification, examples of system functions and procedures capable of effectively controlling the computing capabilities of a mobile communication system are described, targeting 5G evolution / 6G systems in a zero-touch configuration / operation environment where network automation is extended. For example, examples of base station control functions and procedures for maximizing the utilization of computing resources of base station nodes, such as a Central Unit (CU) (e.g., gNodeB CU (gNB-CU)) and / or a Distributed Unit (DU) (e.g., gNB-DU) deployed in the cloud, are described.

[0131] This allows the efficiency of computing resource usage to be maximized from the perspective of the entire system. From the operator's perspective, certain resources of the data centers and / or servers built by the operator 3 rd Business profits can be pursued by renting it to a party or making it available for use for other services.

[0132] According to one embodiment of the disclosure of this specification, a base station or RAN-level management function can monitor information related to computing resources and switch off (deactivate) a specific base station module based on pre-configured criteria. Accordingly, the operator can utilize cloud resources for other purposes.

[0133] This specification proposes the following methods to solve the above problems. The methods presented below may be performed or used selectively, in combination, or complementarily.

[0134] In addition, although the present specification specifies embodiments based on the structure, procedures, messages, etc. of a 5G mobile communication system, the scope of the specification is not limited thereto, and the contents described in the disclosure of the present specification can be extended to an evolved form of a 6G mobile communication system.

[0135] [1] Explains an example of a cloud notification.

[0136] Cloud infrastructure can inform base station function nodes (e.g., CU, DU and orchestration / management function nodes, OAM, and / or RAN management function, etc.) deployed in the cloud about information that can be identified by the infrastructure.

[0137] In this specification, the procedure for O-cloud notification of the Open Radio Access Network (O-RAN) standard may be used as follows.

[0138] The following drawings are made to illustrate a specific example of the present specification. The names of specific devices or specific signals / messages / fields described in the drawings are presented as examples, and therefore the technical features of the present specification are not limited to the specific names used in the following drawings.

[0139] FIG. 5 illustrates an example of a procedure related to an O-cloud notification according to one embodiment of the disclosure of the present specification.

[0140] Referring to the example in FIG. 5, the cloud infrastructure may include an Application Programming Interface (API) producer and an Event Framework o-cloud Implementation. The API producer may be a helper. The helper may be provided by the cloud vendor.

[0141] An Event Consumer or API Consumer is illustrated in the example of Fig. 5. The Event Consumer or API Consumer can act as a workload. The Event Consumer or API Consumer and the API Producer can use the application context.

[0142] In the example of Fig. 5, a precondition (e.g., API consumer has subscribed to address previously) can be satisfied.

[0143] An event matching the API consumer's subscription may occur. Then, the event framework o-cloud implementation can send notifications related to the event to the API producer.

[0144] 1. The API producer sends a message containing notifications related to the event (e.g., POST <<endpoint URI> > (XyzNotification)) can be sent to event consumers or API consumers. The above message (e.g., POST <<endpoint URI> (XyzNotification)) performs the role of announcing the unique network address of a specific function node installed in o-cloud when a pre-configured event (e.g., an event for a fault notification) occurs.

[0145] 2. An event consumer or API consumer can send a 204 No Content message to an API producer. The 204 No Content message in the example above serves as a response indicating that the message was successfully received.

[0146] CUs and / or DUs corresponding to Event consumers (or API consumers) can register (or subscribe) to event notifications for computing resources in advance. CUs and / or DUs corresponding to Event consumers (or API consumers) can receive notifications from the cloud.

[0147] In this specification, a CU and / or DU corresponding to an Event consumer (or API consumer) may periodically receive information related to one or more of the following cloud computing resources, or receive it when an event occurs.

[0148] - Information / status regarding currently available computing resources (e.g., xPU type and processing capability, storage, and / or power consumption, etc.);

[0149] - Information / status related to currently used computing resources (e.g., xPU type and processing capability, storage, and / or power consumption, etc.); and / or

[0150] - Whether the threshold set during pre-configuration for specific resources or event subscription is exceeded, etc.

[0151] For reference, the xPU type can refer to the type of processing unit used for computing. For example, the xPU type can be one or more of an NPU, Central Processing Unit (CPU), GPU, or Tensor Processing Unit (TPU).

[0152] In addition, this specification includes cases where the base station function node corresponding to the Event consumer and the base station function node corresponding to the API consumer that performs event notification registration in the cloud are different from each other.

[0153] For example, if there are DUs and CUs hosted in the cloud for base station functions, the DU can register (or subscribe) to event notifications for DU-related computing resources as an API consumer. In this case, the DU may also designate a CU associated with the DU as an event consumer. The CU can perform the network control functions described below based on information related to the computing resources associated with the DU that it receives directly. For example, the CU can receive event notifications from the cloud that include information related to the computing resources associated with the DU.

[0154] [2] This describes an example of the operation of a base station node that has received a notification from the Cloud. For example, the base station node here may be a CU or a DU. In the case where the CU and DU of the base station node are not separated, the base station node here may refer to a base station node that includes both the functions of the CU and the DU.

[0155] [2]-1 The gNB-DU can transmit service status and switching off related information to the gNB-CU through the DU Configuration Update procedure.

[0156] The following drawings are made to illustrate a specific example of the present specification. The names of specific devices or specific signals / messages / fields described in the drawings are presented as examples, and therefore the technical features of the present specification are not limited to the specific names used in the following drawings.

[0157] FIG. 6 shows an example of a gNB-DU setting update procedure according to one embodiment of the disclosure of the present specification.

[0158] Figure 6 is an example of the successful operation of the gNB-DU configuration update procedure. In this regard, TS 38.473 V18.4.0 Figure 8.2.4.2-1 may be referenced.

[0159] gNB-DU can send GNB-DU configuration update messages to gNB-CU.

[0160] gNB-CU can send an ACKNOWLEDGE message to gNB-DU to update the GNB-DU settings.

[0161] For example, gNB-DU can receive an event notification containing information related to a computing resource from the cloud in [1]. gNB-DU can forward the information related to the computing resource received from the cloud as is to gNB-CU. Alternatively, gNB-DU can process the information related to the computing resource received from the cloud and send the processed information to gNB-CU.

[0162] For example, gNB-DU can send a GNB-DU configuration update message containing information related to computing resources or processed information related to computing resources to gNB-CU.

[0163] In some implementations, a gNB-DU hosted on O-Cloud may determine, based on information regarding computing resources received from the cloud, that the currently available computing resources do not satisfy the Quality of Service (QoS) of traffic for the active cells that the gNB-DU must handle. In this case, the gNB-DU may send a GNB-DU configuration update message to the gNB-CU that includes information regarding computing resources, along with the information that the currently available computing resources do not satisfy the QoS of traffic for the active cells that the gNB-DU must handle.

[0164] In some implementations, the gNB-DU may receive information from the cloud that a preset threshold for the computing resources allocated to each active cell has been exceeded. In this case, the gNB-DU may propose to the gNB-CU the deactivation of the cell handling the least traffic to secure computing resources. For example, the gNB-DU may send a GNB-DU configuration update message to the gNB-CU containing information regarding the deactivation of the cell handling the least traffic to secure computing resources.

[0165] In some implementations, based on [1] operation, gNB-CU may directly receive information regarding computing resources related to the DU from the cloud. Based on the previously performed gNB-DU configuration update procedure, gNB-CU may also perform [3]-1 operation by utilizing information regarding the service status of each cell and / or information regarding computing resources related to the DU received from the DU.

[0166] [2]-2 In the disclosure of this specification, a gNB-CU may update configuration-related information (e.g., ID information of the gNB-CU or network topology information connected to the gNB-CU, and / or supported slice information and status information regarding current network resources, etc.) to an OAM or RAN management function node. For example, the gNB-CU may forward information related to computing resources received from the cloud as is to an OAM or RAN management function node. Alternatively, the gNB-CU may process information related to computing resources and then transmit the processed information to an OAM or RAN management function node. For example, the gNB-CU may process information related to computing resources to generate processed information. The processed information may be, for example, a list of gNB-DUs among the connected gNB-DUs that require adjustment of computing resources because their computing resources exceed an arbitrary threshold.

[0167] [3] Based on information related to computing resources, base station functions can be deactivated.

[0168] [3]-1 The gNB-CU can decide to switch off (deactivate) a specific cell based on information related to the collected computing resources. The gNB-CU can instruct the gNB-DU managing the cell that has decided to switch off the specific cell to switch off (deactivate). For example, the gNB-CU can instruct the gNB-DU managing the cell that has decided to switch off the specific cell to switch off (deactivate) based on the gNB-CU configuration update procedure.

[0169] The following drawings are made to illustrate a specific example of the present specification. The names of specific devices or specific signals / messages / fields described in the drawings are presented as examples, and therefore the technical features of the present specification are not limited to the specific names used in the following drawings.

[0170] FIG. 7 shows an example of a gNB-CU setting update procedure according to one embodiment of the disclosure of the present specification.

[0171] Figure 7 is an example of the successful operation of the gNB-CU configuration update procedure. In this regard, TS 38.473 V18.4.0 Figure 8.2.5.2-1 may be referenced.

[0172] gNB-CU can send GNB-CU configuration update messages to gNB-DU.

[0173] For example, the gNB-CU can send a GNB-CU configuration update message containing information related to the switch-off (deactivation) of a specific cell to the gNB-DU managing the cell that decided to switch off.

[0174] gNB-DU can send an ACKNOWLEDGE message to the gNB-CU to update the GNB-CU settings.

[0175] [3]-2 In some implementations, the OAM and / or RAN management function may decide to switch off (deactivate) some or all base station function modules based on information related to the collected computing resources.

[0176] In performing the above [3] operation (e.g., [3]-1, and / or [3]-2), the following description may apply. For example, an operation to hand over terminals that were being served by the said base station function module and / or base station to another base station function module / base station may be performed before or after i) deciding to switch off (deactivate) the base station function module and / or base station, or ii) before or after executing the switch off (deactivation) of the base station function module and / or base station. Accordingly, it is assumed that a procedure to ensure the continuity of service received by the terminal is performed.

[0177] Assuming a system equipped with / operated with AI functions, data collection for information related to computing resources may be performed through the process [1] [2] above for a certain period of time and / or in a specific region. In this case, during the process of deciding switch off (deactivation) in [3] above, the gNB-CU, OAM and / or RAN management function may obtain inference results for the decision through an analytics (analysis of statistical and predicted values) procedure or an AIML model. Based on the results, the gNB-CU, OAM and / or RAN management function performs the most optimized decision and subsequent procedure.

[0178] [4] Changed status information is notified to surrounding base stations. A base station node (e.g., CU or RAN-level management function of FIG. 8) periodically updates the changed status information to other connected base station nodes when there is a change in the active cell of the base station or a change in capability, etc. By utilizing this procedure, the base station node (e.g., CU or RAN-level management function of FIG. 8) can notify other connected base station nodes that the status information of the cell has changed according to computing resources.

[0179] The following drawings are made to illustrate a specific example of the present specification. The names of specific devices or specific signals / messages / fields described in the drawings are presented as examples, and therefore the technical features of the present specification are not limited to the specific names used in the following drawings.

[0180] FIG. 8 illustrates an example of a procedure including operations according to one embodiment of the disclosure of the present specification.

[0181] For reference, the O-cloud of FIG. 8 may include the API producer and event framework o-cloud implementation of FIG. 5. The CU, DU, and RAN-level management functions of FIG. 8 may be the event consumers of FIG. 5.

[0182] 1. O-cloud can send cloud event notification messages to DUs deployed in the cloud, or CUs or RAN-level management functions deployed in the cloud. For example, cloud event notification messages may include information related to computing resources.

[0183] For example, O-Cloud can periodically or immediately notify base station function nodes (e.g., DU and / or CU) installed in the cloud, Non-real time RAN Intelligent Controller (RIC), Near-real time RIC, etc., that a predefined event related to computing resources has occurred. Here, the content described in [1] Cloud notification above may apply to the event. For example, O-Cloud can send a cloud notification based on what is described in [1] above.

[0184] In some implementations, a network node, such as a DU that receives a notification directly from O-cloud, may forward the information contained in the notification (e.g., information related to computing resources) as is to other network nodes, CUs, and / or RAN-level management functions. Alternatively, a network node, such as a DU that receives a notification directly from O-cloud, may transform the information contained in the notification (e.g., information related to computing resources) into a processed form (e.g., a message in a form that 3GPP function nodes can understand) and send it to other network nodes, CUs, and / or RAN-level management functions. As another example, a network node, such as a DU that receives a notification directly from O-cloud, may send new information extracted based on the information contained in the notification (e.g., information related to computing resources) and event information (e.g., event information such as computing resources exceeding a preset threshold) to other network nodes, CUs, and / or RAN-level management functions. For example, the new information here may include statistical values ​​regarding how many times the corresponding event has occurred over a certain period, and / or prediction values ​​regarding when the corresponding event will occur based on the statistical values. As an example of processed information, the contents of [2]-1 described above may be referenced.

[0185] 2. 3GPP base station functional nodes may transmit, exchange, and / or update information related to computing resources. For example, a DU may transmit information related to computing resources to a CU or RAN-level management function. As another example, a CU or RAN-level management function may transmit information related to computing resources to a DU.

[0186] For example, 3GPP base station functional nodes (e.g., DU, CU, RAN-level management function, etc.) can exchange capability and status information with each other through the gNB-CU configuration update, gNB-DU configuration update procedures of the prior art TS 38.473 V18.4.0. In the disclosure of this specification, while performing these processes, the DU and CU (or RAN-level management function) may additionally exchange information related to computing resources (e.g., status information of computing resources).

[0187] For example, the DU may send a message (e.g., GNB-DU CONFIGURATION UPDATE message) containing information related to the DU's computing resource event received from the O-cloud (e.g., information related to computing resources) to the CU. In addition, the CU may also send a message (e.g., GNB-CU CONFIGURATION UPDATE message) containing information related to the CU's computing resource event received from the O-cloud (e.g., information related to computing resources) to the DU.

[0188] In another embodiment, the GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE and GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE transmitted as a response to the GNB-DU CONFIGURATION UPDATE or GNB-CU CONFIGURATION UPDATE message may each include information related to computing resource events (e.g., information related to computing resources).

[0189] For example, the DU can transmit information about the cell related to the switch-off (deactivation) to the CU. The information about the cell related to the switch-off (deactivation) may include, for example, information about the cell to be switched off (deactivated) (e.g., information about the cell that the DU has decided to switch off (deactivate)) or information about candidate cells to be switched off (deactivated).

[0190] Information regarding the cell related to switch-off (deactivation) can be transmitted based on the contents of the conventional technical specifications below or newly defined / extended parameters.

[0191] For example, the DU may transmit information about the cell related to Switch-off (deactivation) to the CU based on the service state of the following TS 38.473 V18.4.0 S9.2.1.7 GNB-DU CONFIGURATION UPDATE and / or Switching Off Ongoing of TS 38.473 V18.4.0 9.3.1.68 Service Status.

[0192] TS 38.473 V18.4.0 9.2.1.7 GNB-DU CONFIGURATION UPDATE is explained.

[0193] The gNB-DU can send a GNB-DU CONFIGURATION UPDATE message to transmit updated information related to the F1-C (e.g., F1 Control Plane) interface instance.

[0194] Direction: gNB-DU -> gNB-CU

[0195] IE / Group Name Scope IE Type and Reference Semantic description Criticality Assigned Criticality Message Type MTS 38.473 V18.4.0 9.3.1.1 YESrejectTransaction IDMTS 38.473 V18.4.0 9.3.1.23 YESreject Cells Status List 0..1 Full list of active cells YESreject>Cells Status Item 0 .. <maxcellingnbdu>EACHreject>>NR CGIMTS 38.473 V18.4.0 9.3.1.12 Reference->>Service StatusMTS 38.473 V18.4.0 9.3.1.68 Reference-

[0196] Table 3 is an example of the information included in the GNB-DU CONFIGURATION UPDATE message. The GNB-DU CONFIGURATION UPDATE message may include information such as the Message Type, Transaction ID, and Cells Status List. The Cells Status List may include Cells Status Items. Cells Status Items may include NR CGI and / or Service Status.

[0197] For service status, TS 38.473 9.3.1.68 Service Status may be referenced.

[0198] The Service Status Information Element (IE) is used by gNB-DU to indicate the service status of a cell.

[0199] IE / Group Name Existence Range IE Type and Reference Semantic description Service State MENUMERATED (In-Service, Out-Of-Service, ...) Indicates the service status of the cell. In-Service and Out-of-Service service states are defined in TS 38.401 V18.4.0. Switching Off Ongoing OENUMERATED (True, ...) This IE indicates that gNB-DU will delete the cell after a certain period of time using the new gNB-DU configuration update procedure.

[0200] According to the example in Table 4, the Service Status in Table 3 may include Service State and / or Switching Off Ongoing.

[0201] Table 4 shows examples of service statuses. For example, the DU may send a GNB-DU CONFIGURATION UPDATE message to the CU that includes Switching Off Ongoing. Switching Off Ongoing may be an example of cell information related to switch-off (deactivation).

[0202] 3. CU or RAN-level management functions can perform operations related to AI functions.

[0203] For reference, the CU may be a base station node with control functions for the DU when base station functions are implemented by being separated into CU / DU. The RAN-level management function may be a network node capable of collecting and integrating information from multiple base station function nodes, similar to an OAM server or a core network node. In this specification, a CU capable of managing multiple DUs or a RAN-level management function capable of managing multiple base stations may perform the management and control of computing resources. In this specification, operations performed by the CU may also be performed by the RAN-level management function, and operations performed by the RAN-level management function may also be performed by the CU.

[0204] For example, a system in which AI functions are installed and / or operated on network nodes may be assumed. For example, assume a case where AI functions are installed and operated on a CU. In this case, the CU may collect information related to computing resources through steps 1 and 2 above for a certain period of time and / or in a specific region. Based on the collected information related to computing resources, the CU may perform analysis and / or AI model training processes. For example, the analysis may be performed in the same manner as the analysis performed by the NWDAF. Based on the analysis and / or AI model training processes, the CU may infer (or derive) statistical values ​​and / or predicted values ​​regarding how much computing resource will be used at a given time, etc.

[0205] 4. CU or RAN-level management functions can determine cell switch-off (or deactivation).

[0206] Based on statistical and / or predicted values ​​regarding how much computing resource will be used at a given time, the CU may determine the switch-off (deactivation) of a specific base station functional node (e.g., a specific DU). Examples of how switch-off (deactivation) is determined are listed below, but these are merely examples. The scope of this specification is not limited by the examples below. For instance, various embodiments are possible depending on configurations and thresholds set in advance by the operator. Additionally, the conditions listed below may be used by the CU or RAN-level management function to determine switch-off (deactivation), either individually or in combination of one or more:

[0207] A. If the computing resource utilization of a specific cell is below a first threshold (e.g., 10%), or if such a situation is anticipated, a CU or RAN-level management function may decide to switch off the cell;

[0208] B. If the computing resource utilization of a specific cell differs from the utilization of surrounding cells by more than a second threshold (e.g., 30%), or if such a situation is anticipated, a CU or RAN-level management function may decide to switch off the cell; and / or

[0209] C. Regardless of computing resource usage, if any condition (e.g., specific time, specific region, etc.) is satisfied, the CU or RAN-level management function can decide to switch off the cell.

[0210] In this way, even after the CU or RAN-level management function has decided to switch-off (deactivation), the CU or RAN-level management function may perform continuous monitoring according to configuration conditions. For example, if the cell satisfies the switch-on (activation) condition again, the CU or RAN-level management function may change the cell back to its previous operational state. For example, the action of the CU or RAN-level management function switching the cell on (activating) may be performed automatically based on an explicit request or configuration information.

[0211] 5. Preliminary work before cell switch-off, such as handover procedures, may be performed.

[0212] For example, before a CU or RAN-level management function performs a cell switch-off, it may perform preliminary operations, such as HandOver (HO) a terminal served through the cell to another cell. For the actions and / or messages used in Step 5, procedures of the prior art may be utilized. For example, conventional actions and / or messages related to handover may be used. In some implementations, the HO cause value may be newly defined or expanded. For example, the CU or RAN-level management function may notify the target DU (or target CU) that the handover procedure is being performed due to a computing resource issue based on the newly defined HO cause value or the expanded HO cause value. For example, a description related to the newly defined HO cause value or the expanded HO cause value may be applied to TS 38.300 15.4.2.1 Intra-system energy saving.

[0213] TS 38.300 15.4.2.1 Explains intra-system energy saving.

[0214] This solution is based on the possibility that an NG-RAN node equipped with a capacity booster cell may decide to automatically switch off that cell to reduce energy consumption (inactive state). This decision is typically made based on configured information and cell load information. The switch-off decision may also be performed by O&M.

[0215] An NG-RAN node can initiate a handover operation to offload a switched-off cell. To support target nodes involved in subsequent operations, such as selecting a target cell during a subsequent handover, the NG-RAN node can indicate the reason for the handover with an appropriate cause value.

[0216] The NG-RAN node that owns the relevant cell notifies all adjacent NG-RAN nodes of the switch-off operation through the Xn interface via the NG-RAN node configuration update procedure.

[0217] For example, an inter-DU handover may be performed. In this case, the CU may send a UE context setup request message to the target DU. To inform the target DU that the handover procedure is being performed due to a computing resource issue, the UE context setup request message may include a newly defined HO cause value or an extended HO cause value.

[0218] For example, an inter-CU handover may be performed. In this case, a CU or RAN-level management function may send a handover request message to the target CU. To inform the target DU (or target CU) that the handover procedure is being performed due to a computing resource issue, the handover request message may include a newly defined HO cause value or an extended HO cause value.

[0219] Alternatively, the RAN-level management function may send a control message containing configuration information to a specific CU or specific DU for management purposes, and the control message may include information that it is related to a computing resource issue.

[0220] 6. The CU or RAN-level management function can update information related to computing resources by sending a configuration update message (e.g., gNB-CU configuration update message) containing information related to computing resources to the DU.

[0221] For example, a CU or RAN-level management function can update information related to computing resources to the DU. For example, a CU or RAN-level management function can send a message to the DU containing information related to cell switch-off (or deactivation).

[0222] For example, the CU may command / request the DU managing the cell that has decided to switch off to switch off (deactivation) the cell. Procedures of the prior art may be utilized for such operations and messages, etc.

[0223] For example, the CU may use the gNB-CU configuration update procedure according to the example of FIG. 7. For example, the CU may send a gNB-CU configuration update message to the DU that includes a Cells to be Deactivated List Item IE. The Cells to be Deactivated List Item IE may include an NG CGI IE. The DU deactivates (or switches off) the cells indicated by the NG CGI IE.

[0224] Subsequently, by utilizing the procedures of the prior art (e.g., NG-RAN node configuration update procedures), the CU can notify adjacent base stations of the switched-off cell. At this time, in the disclosure of this specification, the CU may additionally transmit cause value information to adjacent base stations indicating that the cell-switch issue was caused by a computing resource issue. Furthermore, the CU may transmit information related to the switched-off cell and / or cause value information indicating that the cell-switch issue was caused by a computing resource issue to DU and RAN-level management functions.

[0225] Information related to cell switch-off transmitted between adjacent base stations may be based on the following NG-RAN node configuration update procedure. Some message fields may be newly defined or expanded so that additionally necessary information (e.g., information related to the switched-off cell and / or cause value information indicating that the cell-switch issue was caused by a computing resource issue) can be included.

[0226] The CU can transmit an NG-RAN node configuration update message to an adjacent base station that includes a Deactivation Indication IE containing information related to the switch-off of a specific cell. The Deactivation Indication IE may be included in the Served Cells To Update NR IE.

[0227] CU can use TS 38.423 9.1.3.4 NG-RAN NODE CONFIGURATION UPDATE.

[0228] To convey updated information about the Xn-C interface instance, the NG-RAN node sends an NG-RAN node configuration update message to an adjacent NG-RAN node.

[0229] The direction in which the NG-RAN NODE CONFIGURATION UPDATE message is transmitted is NG-RAN node1 -> NG-RAN node2.

[0230] IE / Group Name Scope IE Types and References Semantic Description Criticality Assigned Criticality Message Type MTS 38.423 9.2.3.1 YES reject TAI Support List OTS 38.423 9.2.3.20 List of supported TAs and associated attributes. GLOBAL reject CHOICE Initiating NodeType M YES ignore >gNB>>Served Cells To Update N OTS 38.423 9.2.2.15 YES ignore

[0231] According to one embodiment, the CU of NG-RAN node1 can send an NG-RAN NODE CONFIGURATION UPDATE message containing Served Cells To Update NR to NG-RAN node2.

[0232] The details regarding the above Served Cells To Update NR IE are as follows.

[0233] TS 38.423 9.2.2.15 Served Cells To Update NR is described.

[0234] Served Cells To Update NR IE includes updated configuration information of serving cells exchanged between NG-RAN nodes.

[0235] IE / Group Name Scope IE Type and Reference Semantic Description Criticality Assigned Criticality Served Cells To Modify NR0 .. < maxnoofCells in NG-RAN node> List of modified cells served by the NG-RAN node -> Old NR CGIM NR CGI 9.2.2.7 -> Served Cell Information NRM 9.2.2.11 -> Neighbor Information NRO 9.2.2.13 -> Neighbor Information E-UTRA 9.2.2.14 -> Deactivation Indication OE NUMERATED (deactivated, ...) Indicates that the associated cell is switched off for energy saving reasons.

[0236] Served Cells To Update NR IE may include Served Cells To Modify NR of the example in Table 6. Served Cells To Modify NR may include a Deactivation Indication.

[0237] For reference, the following description may apply to the Deactivation Indication IE of the NG-RAN node Configuration Update procedure.

[0238] TS 38.423 8.4.2 NG-RAN node Configuration Update is described.

[0239] The purpose of the NG-RAN node configuration update procedure is to update the necessary application-level configuration data so that two NG-RAN nodes can properly interoperate through the Xn-C interface. The NG-RAN node Configuration Update uses non-UE-associated signaling.

[0240] Referring to Fig. 9, an example of the successful operation of the NG-RAN node configuration update procedure is described.

[0241] The following drawings are made to illustrate a specific example of the present specification. The names of specific devices or specific signals / messages / fields described in the drawings are presented as examples, and therefore the technical features of the present specification are not limited to the specific names used in the following drawings.

[0242] FIG. 9 illustrates an example of an NG-RAN node configuration update procedure according to one embodiment of the disclosure of the present specification.

[0243] NG-RAN node1 can send an NG-RAN mode setting update message to NG-RAN node2. NG-RAN node2 can send an NG-RAN mode setting update ACKNOWLEDGE message to NG-RAN node1.

[0244] NG-RAN Node 1 initiates the procedure by sending an NG-RAN NODE configuration UPDATE message to peer NG-RAN Node 2.

[0245] The NG-RAN node configuration update message may include Served Cells NR To Modify IE according to the example in Table 6. In this case, NG-RAN node2 can modify the cell information indicated by Old NR-CGI IE according to Served Cell InformationNRIE.

[0246] According to one embodiment, a CU (e.g., a CU of NG-RAN node 1) may send an NG-RAN NODE configuration UPDATE message to NG-RAN node 2 that includes a Deactivation Indication IE. For example, the NG-RAN NODE configuration UPDATE message may include Served Cells NR To Modify IE, and Served Cells NR To Modify IE may include a Deactivation Indication IE. If the Deactivation Indication IE is set to "deactivated," this may indicate that the associated cell has been switched off to reduce energy consumption.

[0247] According to one embodiment, a first network node (e.g., gNB-CU) may receive information related to a computing resource from a second network node (e.g., gNB-DU). Alternatively, the first network node (e.g., gNB-CU) may receive information related to a computing resource associated with the second network node from a cloud on which the second network node (e.g., gNB-DU) is installed. Based on information related to the computing resource and / or pre-configured reference information, the first network node (e.g., gNB-CU) may determine the switch-off (deactivation) of a specific base station module. The first network node (e.g., gNB-CU) may transmit a message instructing the switch-off (deactivation) to the second network node (e.g., gNB-DU). The first network node (e.g., gNB-CU) may notify a third network node (e.g., adjacent base station or gNB-CU) of the changed status information of the first network node (e.g., gNB-CU).

[0248] According to one embodiment, a fourth network node (e.g., OAM or RAN management function) may receive information related to computing resources from a first network node (e.g., gNB-CU). Based on information related to computing resources and / or pre-configured reference information, the fourth network node (e.g., OAM or RAN management function) may determine the switch-off (deactivation) of a specific base station module. The fourth network node (e.g., OAM or RAN management function) may transmit a message instructing the switch-off (deactivation) to the first network node (e.g., gNB-CU). The fourth network node (e.g., OAM or RAN management function) may notify the third network node (e.g., adjacent base station or gNB-CU) of the changed status information of the first network node (e.g., gNB-CU).

[0249] The following drawings are made to illustrate a specific example of the present specification. The names of specific devices or specific signals / messages / fields described in the drawings are presented as examples, and therefore the technical features of the present specification are not limited to the specific names used in the following drawings.

[0250] FIG. 10 illustrates an example of a procedure according to one embodiment of the disclosure of the present specification.

[0251] For reference, the procedure illustrated in FIG. 10 is merely an example, and the scope of disclosure of this specification is not limited by the example of FIG. 10.

[0252] For example, regarding the example of FIG. 10, the operations described in the examples of FIG. 1 through 9 may also be applied. For example, even if the operations, contents, etc. are not directly described in the example of FIG. 10, the operations, contents, etc. described in various examples of the disclosure of this specification may be applied.

[0253] In the example of FIG. 10, the first network entity may be a gNB-CU, CU, or RAN-level management function described in various examples of the disclosure of this specification.

[0254] The second network entity may be a gNB-DU or DU deployed in the cloud.

[0255] In step (S1001), the second network entity can send a first configuration update message to the first network entity.

[0256] For example, a first network entity may receive a first configuration update message from a second network entity that includes information related to computing resources for said second network entity.

[0257] In some implementations, information regarding computing resources may include at least one of: information regarding computing resources currently available to the second network entity; information regarding computing resources currently in use by the second network entity; or information regarding settings regarding computing resources of the second network entity or whether computing resources of the second network entity exceed a threshold value.

[0258] In some implementations, the cloud (e.g., an API producer included in the cloud) can transmit information related to computing resources for the second network to the second network entity.

[0259] In some implementations, based on information related to computing resources for the second network entity, the first network entity may derive a predicted value for computing resources.

[0260] In step (S1002), the first network entity can decide to switch off (or disable).

[0261] For example, the first network entity may decide to switch off the second network node based on information related to the computing resources for the second network.

[0262] For example, the first network entity may decide to switch off (or disable) the second network entity, or decide to switch off (or disable) the first cell of the second network entity.

[0263] In some implementations, the first network entity may decide to switch off (or disable) the second network node based on at least one of the following: when the computing resource utilization of the second network node or the first cell of the second network node is less than a first threshold; when the computing resource utilization of the second network node or the first cell of the second network node differs from the computing resource utilization of a neighboring network node or the computing resource utilization of a neighboring cell by more than a second threshold; or when the second network node or the first cell of the second network node satisfies conditions related to switch-off.

[0264] In step (S1003), the first network entity can send a second configuration update message to the second network entity.

[0265] For example, the first network entity may send a second configuration update message containing information related to switch-off to the second network entity.

[0266] In some implementations, the first network entity may transmit to a third network entity (e.g., a neighboring base station or cell) information regarding the second network entity being in a switched-off state and information regarding the switched-off state being in a computing resource.

[0267] In some implementations, the first network entity may send a message containing information related to the handover to the target cell or target network entity before the second configuration update message is sent.

[0268] This specification may have various effects.

[0269] Services based on 6G mobile communication systems can be effectively supported. For example, various services such as sensing services, immersive reality, and / or multi-domal services can be effectively provided based on AI technology.

[0270] For example, processing and / or computing capabilities for providing various services can be effectively supported. For example, a base station can effectively utilize computing resources.

[0271] For example, targeting 5G evolution / 6G systems in a zero-touch configuration / operation environment with extended network automation, the computing capabilities of mobile communication systems can be effectively controlled. For example, the utilization of computing resources of base station nodes, such as CUs and DUs, deployed in the cloud can be maximized. For example, operators can utilize cloud resources for business purposes other than providing transmission systems for communication services.

[0272] The effects obtainable through the specific examples of this specification are not limited to those listed above. For example, there may be various technical effects that a person with ordinary skill in the related art can understand or derive from this specification. Accordingly, the specific effects of this specification are not limited to those explicitly described herein, but may include various effects that can be understood or derived from the technical features of this specification.

[0273] For reference, the operation of the terminal (e.g., UE) described in this specification may be implemented by the device of FIGS. 1 to 3 described above. For example, the terminal may be the first device (100) or the second device (200) of FIG. 2. For example, the operation of the terminal (e.g., UE) described in this specification may be processed by one or more processors (102 or 202). The operation of the terminal described in this specification may be stored in one or more memories (104 or 204) in the form of an instruction / program (e.g., instruction, executable code) executable by one or more processors (102 or 202). One or more processors (102 or 202) may control one or more memories (104 or 204) and one or more transceivers (105 or 206) and execute the instruction / program stored in one or more memories (104 or 204) to perform the operation of the terminal (e.g., UE) described in the disclosure of this specification.

[0274] Additionally, instructions for performing the operation of the terminal described in the disclosure of this specification may be stored in a non-volatile computer-readable storage medium. The storage medium may be included in one or more memories (104 or 204). And, the instructions recorded in the storage medium may perform the operation of the terminal (e.g., UE) described in the disclosure of this specification by being executed by one or more processors (102 or 202).

[0275] For reference, the operation of a network node (e.g., AMF, SMF, UPF, PCF, UDM, NWDAF, OAM, cloud, RAN-level management function, etc.) or a base station (e.g., NG-RAN, NG-RAN node 1, NG-RAN node 2, RAN, AN, gNB, CU, DU, gNB-CU, gNB-DU, etc.) described in this specification may be implemented by the device of FIGS. 1 to 3, which will be described below. For example, the network node or base station may be the first device (100) or the second device (200) of FIG. 2. For example, the operation of the network node or base station described in this specification may be processed by one or more processors (102 or 202). The operation of the terminal described in this specification may be stored in one or more memories (104 or 204) in the form of an instruction / program (e.g., instruction, executable code) executable by one or more processors (102 or 202). One or more processors (102 or 202) can control one or more memories (104 or 204) and one or more transceivers (106 or 206) and execute instructions / programs stored in one or more memories (104 or 204) to perform the operation of a network node or base station as described in the disclosure of this specification.

[0276] Additionally, instructions for performing the operation of a network node or base station described in the disclosure of this specification may be stored in a non-volatile (or non-transient) computer-readable storage medium. The storage medium may be contained in one or more memories (104 or 204). And, the instructions recorded in the storage medium may perform the operation of a network node or base station described in the disclosure of this specification by being executed by one or more processors (102 or 202).

[0277] Although preferred embodiments have been described by way of example above, the disclosure of this specification is not limited to such specific embodiments, and may be modified, changed, or improved in various forms within the scope of the spirit and claims of this specification.

[0278] In the exemplary system described above, methods are described based on a flowchart as a series of steps or blocks, but are not limited to the order of the described steps, and some steps may occur in a different order or simultaneously with other steps as described above. Furthermore, a person skilled in the art will understand that the steps shown in the flowchart are not exclusive, and that other steps may be included, or that one or more steps of the flowchart may be omitted without affecting the scope of rights.

[0279] The claims described in this specification may be combined in various ways. For example, the technical features of the method claims in this specification may be combined to be implemented as a device, and the technical features of the device claims in this specification may be combined to be implemented as a method. Furthermore, the technical features of the method claims and the technical features of the device claims in this specification may be combined to be implemented as a device, and the technical features of the method claims and the technical features of the device claims in this specification may be combined to be implemented as a method. Other implementations are within the scope of the following claims.< / maxcellingnbdu>

Claims

1. A first network entity receiving a first configuration update message from a second network entity, the message including information related to computing resources for the second network entity, The second network entity is a Distributed Unit (DU) of a base station installed in the cloud; The first network entity determines to switch off the second network node based on information related to the computing resources for the second network; and A method comprising the step of the first network entity transmitting to the second network entity a second configuration update message containing information related to switch-off.

2. In Paragraph 1, A method in which information related to computing resources for the second network is provided to the second network entity by the cloud.

3. In Paragraph 1 or 2, A method further comprising the step of the first network entity transmitting to the third network entity information related to the second network entity being in a switch-off state and information related to the switch-off state being a computing resource.

4. In any one of paragraphs 1 through 3, Information related to the above computing resources is, Information on currently available computing resources of the above-mentioned second network entity; Information on computing resources currently in use by the above-mentioned second network entity; or A method comprising at least one of a setting related to the computing resources of the second network entity or information related to whether the computing resources of the second network entity exceed a threshold.

5. In any one of paragraphs 1 through 4, If the computing resource utilization rate of the second network node or the first cell of the second network node is less than a first threshold; If the computing resource utilization of the second network node or the first cell of the second network node differs from the computing resource utilization of a neighboring network node or the computing resource utilization of a neighboring cell by more than a second threshold; or A method in which it is determined to switch off the second network node based on at least one of the cases where the second network node or the first cell of the second network node satisfies conditions related to switch-off.

6. In any one of paragraphs 1 through 5, A method comprising the step of the first network entity deriving a predicted value for a computing resource based on information related to a computing resource for the second network entity.

7. In any one of paragraphs 1 through 6, A method further comprising the step of the first network entity transmitting a message containing information related to a handover to a target cell or target network entity before the second setting update message is transmitted.

8. At least one transmitter / receiver; At least one processor; and It includes one or more memories that store instructions and can be connected to operate with one or more processors, and The above-mentioned at least one processor is a device adapted to perform a method according to any one of claims 1 to 8.

9. At least one processor; and It includes at least one memory that stores instructions and is operablely electrically connected to at least one processor, and The above-mentioned at least one processor is an apparatus adapted to perform a method according to any one of claims 1 to 8.

10. As a non-transitory computer-readable medium (CRM) recording instructions, The above instructions, when executed by one or more processors, cause the one or more processors to: perform a method according to any one of claims 1 through 8, CRM.

11. A second network entity transmitting to a first network entity a first configuration update message containing information related to computing resources for said second network entity, The second network entity is a Distributed Unit (DU) of a base station installed in the cloud, and Information related to the computing resources for the second network is used to determine whether the first network entity switches off the second network node; and A method comprising the step of the second network entity receiving a second configuration update message from the first network entity, the second network entity including information related to switch-off.

12. In Paragraph 11, A method further comprising the step of the second network entity receiving information related to computing resources for the second network from the cloud.

13. In paragraphs 11 and 12, Information related to the above computing resources is, Information on currently available computing resources of the above-mentioned second network entity; Information on computing resources currently in use by the above-mentioned second network entity; or A method comprising at least one of a setting related to the computing resources of the second network entity or information related to whether the computing resources of the second network entity exceed a threshold.

14. In any one of paragraphs 11 through 13, If the computing resource utilization rate of the second network node or the first cell of the second network node is less than a first threshold; If the computing resource utilization of the second network node or the first cell of the second network node differs from the computing resource utilization of a neighboring network node or the computing resource utilization of a neighboring cell by more than a second threshold; or A method in which it is determined to switch off the second network node based on at least one of the cases where the second network node or the first cell of the second network node satisfies conditions related to switch-off.

15. One or more transmitters / receivers; One or more processors; and It includes one or more memories that store instructions and can be connected to operate with one or more processors, and The above-mentioned at least one processor is a device adapted to perform a method according to any one of claims 11 to 13.

Images