Network slice configuration method and device for utilizing edge computing resources in wireless communication system

Abstract

The present specification proposes specific methods for implementing a network slicing technology, which can be supported in a next-generation wireless communication system. For example, the present specification proposes a network slice configuration method and device for utilizing edge computing resources in a wireless communication system.

Description

Method and device for configuring network slices for utilizing edge computing resources in a wireless communication system

[0001] This specification relates to wireless communications, and more particularly, to a method and device for configuring a network slice for utilizing edge computing resources in a wireless communications system.

[0002] 3GPP has paved the way for commercial deployment of 5G by completing the first global 5G New Radio (NR) standard in Release (Rel)-15. NR is a radio access technology that offers improved data rates compared to LTE and can satisfy various QoS requirements for specific, segmented usage scenarios. Representative NR usage scenarios include enhanced Mobile Broadband (eMBB), massive Mobile Telecommunications (mMTC), and Ultra Reliable and Low Latency Communications (URLLC). A flexible frame structure, compared to LTE, is provided to meet the requirements of each scenario. Additionally, network slicing technology is being considered. Network slicing technology is a new concept applied to 5G mobile communications that can apply properties such as network isolation, customization, and independent management and orchestration to the radio access network (RAN) and core network of mobile communications by providing network resources and network functions as an independent slice of E2E (End-to-End) resources from the radio access network (RAN) to the core network for each service.

[0003] Communication technology is evolving to form network slices optimized for the characteristics of each application within a single, large network, in conjunction with the advancement of technologies such as Network Function Virtualization (NFV) and Software Defined Network (SDN).

[0004] Network slicing creates logically separate, end-to-end (E2E) networks, including wireless access, transmission, and 5G core equipment, from a single physical network. This allows for dedicated, specialized networks for various services with different characteristics. In other words, network slicing is a technology that provides network resources and network functions required for a service requested by a terminal as a single, independent slice.

[0005] This specification proposes specific implementation methods of network slicing technology that can be supported in next-generation wireless communication systems.

[0006] According to one embodiment, a method for use by a base station in a wireless communication system is proposed. The method comprises: determining whether a base station computing network slice is configured; and configuring the base station computing network slice based on the determination, wherein the base station computing network slice is a network slice that provides a service in which data of at least one of an IP layer and an application layer is processed by the base station or an edge server connected to the base station.

[0007] Here, the base station receives network slice request information from a terminal connected to the base station, and the base station can determine whether to configure the base station computing network slice based on the network slice request information.

[0008] Here, the network slice request information may include an identifier for the base station computing network slice.

[0009] Here, the network slice request information can be transmitted via an AS (Access Stratum) message.

[0010] Here, the base station transmits slice request information to 5GC based on the judgment, and the slice request information may include information identifying the base station computing network slice.

[0011] Here, the base station can determine whether to configure the base station computing network slice based on at least one of available computing resources, mobility of the terminal, and support for service applications.

[0012] Here, the base station receives availability request information from 5GC (5G Core), and the base station can determine whether to configure the base station computing network slice based on the availability request information.

[0013] Here, the availability request information may include at least one of information for identifying the requested base station computing network slice, information about the requested computing resource, and information about the requested service function.

[0014] Here, in response to the availability request information, the base station can transmit availability response information to the 5GC.

[0015] Here, the availability response information may include at least one of information on the presence or absence of available computing resources of the base station, information identifying one or more available slices, and information on the availability of computing resources.

[0016] According to another embodiment, a proposed base station includes one or more memories storing commands; one or more transceivers; and one or more processors connecting the one or more memories and the one or more transceivers, wherein the one or more processors execute the commands to determine whether a base station computing network slice is configured; and configure the base station computing network slice based on the determination, wherein the base station computing network slice is a network slice that provides a service in which data of at least one of an IP layer and an application layer is processed by the base station or an edge server connected to the base station.

[0017] Here, the base station receives network slice request information from a terminal connected to the base station, and the base station can determine whether to configure the base station computing network slice based on the network slice request information.

[0018] Here, the network slice request information may include an identifier for the base station computing network slice.

[0019] Here, the network slice request information can be transmitted via an AS (Access Stratum) message.

[0020] Here, the base station transmits slice request information to 5GC based on the judgment, and the slice request information may include information identifying the base station computing network slice.

[0021] Here, the base station can determine whether to configure the base station computing network slice based on at least one of available computing resources, mobility of the terminal, and support for service applications.

[0022] Here, the base station receives availability request information from 5GC (5G Core), and the base station can determine whether to configure the base station computing network slice based on the availability request information.

[0023] Here, the availability request information may include at least one of information for identifying the requested base station computing network slice, information about the requested computing resource, and information about the requested service function.

[0024] Here, in response to the availability request information, the base station can transmit availability response information to the 5GC.

[0025] Here, the availability response information may include at least one of information on the presence or absence of available computing resources of the base station, information identifying one or more available slices, and information on the availability of computing resources.

[0026] According to this specification, more efficient and low-latency wireless communication service provision and network operation are possible by providing network slices that process computing at base stations or edge servers adjacent to base stations, depending on the type of service. Furthermore, application data processing for providing RAN computing services in open wireless communication networks, various types of computing processing, resource pooling across multiple base stations, and guaranteed low data mobility can be provided. Furthermore, the setup procedures and signaling configurations for providing RAN computing services in open wireless communication networks can be clarified.

[0027] The effects that can be achieved through specific examples of this specification are not limited to the effects listed above. For example, a person with ordinary skill in the relevant technical field may understand or derive various technical effects 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.

[0028] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0029] FIG. 1 is a drawing illustrating a wireless communication system to which the present disclosure can be applied.

[0030] Figure 2 is a block diagram showing a radio protocol architecture for a user plane.

[0031] Figure 3 is a block diagram showing the wireless protocol structure for the control plane.

[0032] FIG. 4 is a drawing illustrating another example of a wireless communication system to which the technical features of the present disclosure can be applied.

[0033] Figure 5 is a diagram illustrating the functional division between NG-RAN and 5GC.

[0034] Figure 6 shows an example of a 5G system architecture to which the implementation of this specification is applied.

[0035] FIG. 7 is a diagram for explaining the network slice concept according to one embodiment of the present specification.

[0036] Figure 8 illustrates an example of processing rendering on an edge server.

[0037] Figure 9 illustrates an example in which a virtualization device function is implemented.

[0038] Figure 10 illustrates an example of semantic communication data processing.

[0039] FIG. 11 illustrates an example of a base station computing slice protocol layer structure according to one embodiment of the present specification.

[0040] Figure 12 illustrates an example of a case where DL data changes according to UL data.

[0041] FIG. 13 illustrates an example of a slice establishment procedure related to AS message-based base station computing according to one embodiment of the present specification.

[0042] FIG. 14 illustrates an example of the configuration of information for a base station computing slice according to one embodiment of the present specification.

[0043] FIG. 15 illustrates an example of a NAS message-based base station computing-related slice establishment procedure according to one embodiment of the present specification.

[0044] FIG. 16 is a flowchart of an example of a method for configuring a network slice of a base station according to one embodiment of the present specification.

[0045] Figure 17 is an example of an open radio access network that provides RAN computing services.

[0046] Figure 18 shows the functional separation of O-DU and O-RU.

[0047] Figure 19 illustrates a protocol stack including a RAN computing module.

[0048] FIG. 20 is a flowchart illustrating an O-RAN resource configuration (or formation) procedure for providing RAN computing services according to one embodiment.

[0049] FIG. 21 is a diagram illustrating a communication device according to some embodiments of the present specification.

[0050] Figure 22 illustrates a communication system (1) applied to the present invention.

[0051] Figure 23 illustrates a wireless device applicable to the present invention.

[0052] Figure 24 illustrates a process for generating a transmission signal in a transmitter.

[0053] Fig. 25 shows another example of a wireless device applied to the present invention.

[0054] The present invention is susceptible to various modifications and embodiments. Specific embodiments are illustrated in the drawings and described in detail in the detailed description. However, this is not intended to limit the present invention to specific embodiments, but rather to encompass all modifications, equivalents, and alternatives falling within the spirit and technical scope of the present invention. Throughout the description of each drawing, similar reference numerals have been used to designate similar components.

[0055] Although the terms "first," "second," "A," "B," etc. may be used herein to describe various components, the components should not be limited by these terms. These terms are used solely to distinguish one component from another. For example, without departing from the scope of the present invention, the first component could be referred to as the second component, and similarly, the second component could also be referred to as the first component. Furthermore, the term "and / or" includes any combination of multiple related listed items or any one of multiple related listed items.

[0056] When a component is referred to as being "connected" or "connected" to another component, it should be understood that it may be directly connected or connected to that other component, but that there may be other components intervening. Conversely, when a component is referred to as being "directly connected" or "connected" to another component, it should be understood that there are no other components intervening.

[0057] The terminology used herein is for the purpose of describing specific embodiments only and is not intended to limit the present invention. The singular expression includes the plural expression unless the context clearly indicates otherwise. In this specification, it should be understood that the terms "comprises" or "has" indicate the presence of a feature, number, step, operation, component, part, or combination thereof described in the specification, but do not exclude in advance the possibility of the presence or addition of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.

[0058] Unless otherwise defined, the terms used herein, including technical or scientific terms, have the same meanings commonly understood by those of ordinary skill in the art to which the present invention pertains. Terms defined in commonly used dictionaries should be interpreted as having meanings consistent with their meanings within the context of the relevant technology, and will not be interpreted in an idealized or overly formal sense unless explicitly defined herein.

[0059] Before proceeding with a detailed description of the drawings, it should be clarified that the division of components in this specification is merely based on the primary function each component is responsible for. In other words, two or more components described below may be combined into a single component, or a single component may be further subdivided into two or more components with more specific functions.

[0060] Furthermore, each component described below may, in addition to its primary function, perform some or all of the functions assigned to other components. Furthermore, some of the primary functions assigned to each component may be dedicated to other components. Therefore, the existence of each component described herein should be interpreted functionally.

[0061] In this specification, “A or B” can mean “only A,” “only B,” or “both A and B.” In other words, “A or B” in this specification can be interpreted as “A and / or B.” For example, “A, B or C” in this specification can mean “only A,” “only B,” “only C,” or “any combination of A, B, and C.”

[0062] As used herein, a slash ( / ) or a comma can mean "and / or." For example, "A / B" can mean "A and / or B." Accordingly, "A / B" can mean "only A," "only B," or "both A and B." For example, "A, B, C" can mean "A, B, or C."

[0063] 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 identically to “at least one of A and B.”

[0064] Additionally, in this specification, “at least one of A, B and C” can mean “only A,” “only B,” “only C,” or “any combination of A, B and C.” Additionally, “at least one of A, B or C” or “at least one of A, B and / or C” can mean “at least one of A, B and C.”

[0065] Hereinafter, a preferred embodiment according to the present invention will be described in detail with reference to the attached drawings.

[0066] Below, a communication system applicable to the present disclosure is described.

[0067] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods and / or operational flowcharts of the present disclosure disclosed in this document may be applied to various fields requiring wireless communication / connectivity (e.g., 5G) between devices.

[0068] Hereinafter, more specific examples will be provided with reference to the drawings. In the drawings / descriptions below, the same drawing reference numerals may represent identical or corresponding hardware blocks, software blocks, or functional blocks, unless otherwise described.

[0069] The following techniques, devices, and systems can 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 can be implemented using wireless technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented using 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 using wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or Evolved UTRA (E-UTRA). UTRA is part of the Universal Mobile Telecommunications System (UMTS). 3GPP (3rd Generation Partnership Project) Long-Term Evolution (LTE) is part of E-UMTS (Evolved UMTS) that utilizes E-UTRA.3GPP LTE uses OFDMA in the downlink (DL) and SC-FDMA in the uplink (UL). Evolution of 3GPP LTE includes LTE-A (Advanced), LTE-A Pro, and / or 5G NR (New Radio).

[0070] For convenience of explanation, the implementation of this specification is primarily described in relation to a 3GPP-based wireless communication system. However, the technical features 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. However, aspects of this specification that are not limited to a 3GPP-based wireless communication system can be applied to other mobile communication systems.

[0071] FIG. 1 is a diagram illustrating a wireless communication system to which the present disclosure can be applied. This may also be referred to as an Evolved-UMTS Terrestrial Radio Access Network (E-UTRAN) or a Long Term Evolution (LTE) / LTE-A system.

[0072] E-UTRAN includes a base station (BS) 20 that provides a control plane and a user plane to a user equipment (UE) 10. The UE 10 may be fixed or mobile, and may be referred to by other terms such as a mobile station (MS), a user terminal (UT), a subscriber station (SS), a mobile terminal (MT), or a wireless device. The base station (20) refers to a fixed station that communicates with the UE 10, and may be referred to by other terms such as an evolved-NodeB (eNB), a base transceiver system (BTS), or an access point.

[0073] Base stations (20) can be connected to each other via the X2 interface. The base station (20) is connected to an EPC (Evolved Packet Core, 30) via the S1 interface, more specifically, to an MME (Mobility Management Entity) via the S1-MME, and to an S-GW (Serving Gateway) via the S1-U.

[0074] The EPC (30) consists of an MME, an S-GW, and a P-GW (Packet Data Network-Gateway). The MME holds information about terminal access and capabilities, and this information is primarily used for terminal mobility management. The S-GW is a gateway with the E-UTRAN as its endpoint, and the P-GW is a gateway with the PDN as its endpoint.

[0075] The layers of the radio interface protocol between the terminal and the network can be divided into L1 (layer 1), L2 (layer 2), and L3 (layer 3) based on the three lower layers of the Open System Interconnection (OSI) standard model, which is widely known in communication systems. Among these, the physical layer belonging to layer 1 provides an information transfer service using a physical channel, and the RRC (Radio Resource Control) layer located in layer 3 controls radio resources between the terminal and the network. To this end, the RRC layer exchanges RRC messages between the terminal and the base station.

[0076] Figure 2 is a block diagram illustrating the radio protocol architecture for the user plane. Figure 3 is a block diagram illustrating the radio protocol architecture for the control plane. The user plane is a protocol stack for transmitting user data, and the control plane is a protocol stack for transmitting control signals.

[0077] Referring to Figures 2 and 3, the physical layer (PHY layer) provides information transfer services to upper layers using physical channels. The PHY layer is connected to its upper layer, the Medium Access Control (MAC) layer, through a transport channel. Data is transferred between the MAC layer and the PHY layer via the transport channel. Transport channels are classified based on how and with what characteristics data is transmitted over the wireless interface.

[0078] Data travels between different physical layers, i.e., between the physical layers of a transmitter and receiver, via a physical channel. This physical channel can be modulated using Orthogonal Frequency Division Multiplexing (OFDM) and utilizes time and frequency as radio resources.

[0079] The MAC layer's functions include mapping between logical channels and transmission channels, and multiplexing / demultiplexing MAC service data units (SDUs) belonging to a logical channel onto the transmission channel into transport blocks provided as physical channels. The MAC layer provides services to the RLC (Radio Link Control) layer via logical channels.

[0080] The functions of the RLC layer include concatenation, segmentation, and reassembly of RLC SDUs. To guarantee the various Quality of Service (QoS) required by radio bearers (RBs), the RLC layer provides three operating modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). AM RLC provides error correction through automatic repeat request (ARQ).

[0081] The RRC (Radio Resource Control) layer is defined only in the control plane. The RRC layer is responsible for controlling logical channels, transmission channels, and physical channels, related to the configuration, reconfiguration, and release of radio bearers. An RB is a logical path provided by Layer 1 (PHY layer) and Layer 2 (MAC layer, RLC layer, PDCP layer) for data transmission between a terminal and the network.

[0082] The functions of the Packet Data Convergence Protocol (PDCP) layer in the user plane include the transmission of user data, header compression, and ciphering. The functions of the Packet Data Convergence Protocol (PDCP) layer in the control plane include the transmission of control plane data and encryption / integrity protection.

[0083] Establishing an RB refers to the process of defining the characteristics of the radio protocol layer and channel to provide a specific service, and setting specific parameters and operating methods for each. RBs can be further divided into two types: signaling RBs (SRBs) and data RBs (DRBs). SRBs are used as a channel to transmit RRC messages in the control plane, while DRBs are used as a channel to transmit user data in the user plane.

[0084] When an RRC connection is established between the RRC layer of the terminal and the RRC layer of the E-UTRAN, the terminal is in an RRC connected state, otherwise it is in an RRC idle state.

[0085] Downlink transmission channels that transmit data from the network to the terminal include the Broadcast Channel (BCH), which transmits system information, and the downlink Shared Channel (SCH), which transmits user traffic or control messages. Traffic or control messages for downlink multicast or broadcast services may be transmitted through the downlink SCH, or may be transmitted through a separate downlink Multicast Channel (MCH). Meanwhile, uplink transmission channels that transmit data from the terminal to the network include the Random Access Channel (RACH), which transmits initial control messages, and the uplink Shared Channel (SCH), which transmits user traffic or control messages.

[0086] Logical channels that are located above the transmission channel and are mapped to the transmission channel include BCCH (Broadcast Control Channel), PCCH (Paging Control Channel), CCCH (Common Control Channel), MCCH (Multicast Control Channel), and MTCH (Multicast Traffic Channel).

[0087] A physical channel (PCH) consists of multiple OFDM symbols in the time domain and multiple subcarriers in the frequency domain. A single subframe consists of multiple OFDM symbols in the time domain. A resource block (RB) is a resource allocation unit and consists of multiple OFDM symbols and multiple subcarriers. Additionally, each subframe can use specific subcarriers of specific OFDM symbols (e.g., the first OFDM symbol) of the subframe for the Physical Downlink Control Channel (PDCCH), i.e., the L1 / L2 control channel. A Transmission Time Interval (TTI) is a unit time for transmission and can be, for example, a subframe or a slot.

[0088] Below, we describe new radio access technology (new RAT, NR).

[0089] FIG. 4 is a drawing illustrating another example of a wireless communication system to which an embodiment of the present disclosure can be applied.

[0090] Specifically, FIG. 4 illustrates a system architecture based on a 5G NR (new radio access technology) system. Entities used in a 5G NR system (hereinafter simply referred to as "NR") may incorporate some or all of the functions of the entities introduced in FIG. 1 (e.g., eNB, MME, S-GW). Entities used in an NR system may be identified as "NG" to distinguish them from LTE.

[0091] Referring to FIG. 4, the wireless communication system includes one or more UEs (11), a next-generation RAN (NG-RAN), and a fifth-generation core network (5GC). The NG-RAN is composed of at least one NG-RAN node. The NG-RAN node is an entity corresponding to the BS (20) illustrated in FIG. 1. The NG-RAN node is composed of at least one gNB (21) and / or at least one ng-eNB (22). The gNB (21) provides termination of NR user plane and control plane protocols toward the UE (11). The ng-eNB (22) provides termination of E-UTRA user plane and control plane protocols toward the UE (11).

[0092] The 5GC includes the access and mobility management function (AMF), the user plane function (UPF), and the session management function (SMF). The AMF hosts functions such as NAS security and idle state mobility handling. The AMF is an entity that includes the functions of a conventional MME. The UPF hosts functions such as mobility anchoring and protocol data unit (PDU) processing. The UPF is an entity that includes the functions of a conventional S-GW. The SMF hosts functions such as UE IP address allocation and PDU session control.

[0093] The gNB and ng-eNB are interconnected via the Xn interface. The gNB and ng-eNB are also connected to the 5GC via the NG interface. More specifically, they are connected to the AMF via the NG-C interface and to the UPF via the NG-U interface.

[0094] Figure 5 is a diagram illustrating the functional division between NG-RAN and 5GC.

[0095] Referring to FIG. 5, the gNB can provide functions such as inter-cell radio resource management (Inter Cell RRM), radio bearer management (RB control), connection mobility control (Connection Mobility Control), radio admission control (Radio Admission Control), measurement configuration and provision, and dynamic resource allocation. The AMF can provide functions such as NAS security and idle state mobility processing. The UPF can provide functions such as mobility anchoring and PDU processing. The SMF (Session Management Function) can provide functions such as terminal IP address allocation and PDU session control.

[0096] Figure 6 shows an example of a 5G system architecture to which the implementation of this specification is applied.

[0097] The 5G system (5GS; 5G System) structure consists of the following network functions (NF; Network Function).

[0098] - AUSF (Authentication Server Function)

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

[0100] - DN (Data Network), 예를 들어 사업자 서비스, 인터넷 접속 또는 타사 서비스

[0101] - USDF (Unstructured Data Storage Function)

[0102] - NEF (Network Exposure Function)

[0103] - I-NEF (Intermediate NEF)

[0104] - NRF (Network Repository Function)

[0105] - NSSF (Network Slice Selection Function)

[0106] - PCF (Policy Control Function)

[0107] - SMF (Session Management Function)

[0108] - UDM (Unified Data Management)

[0109] - UDR (Unified Data Repository)

[0110] - UPF (User Plane Function)

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

[0112] - AF (Application Function)

[0113] - UE (User Equipment)

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

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

[0116] - NWDAF (Network Data Analytics Function)

[0117] - CHF (CHarging Function)

[0118] Additionally, the following network features may be considered:

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

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

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

[0122] Figure 6 illustrates the 5G system architecture for a non-roaming case using a reference point representation showing how various network functions interact with each other.

[0123] For clarity of the point-to-point diagram in Figure 6, UDSF, NEF, and NRF are not illustrated. However, all network functions shown can interact with UDSF, UDR, NEF, and NRF as needed.

[0124] For clarity, the connection between UDR and other NFs (e.g., PCF) is not shown in Fig. 6. For clarity, the connection between NWDAF and other NFs (e.g., PCF) is not shown in Fig. 6.

[0125] The 5G system architecture includes the following benchmarks:

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

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

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

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

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

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

[0132] The following benchmarks illustrate the interactions that exist between NF services in NF.

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

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

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

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

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

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

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

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

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

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

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

[0144] In some cases, two NFs may need to be interconnected to serve a UE.

[0145] Additionally, network functions may be implemented as network elements on dedicated hardware, as software instances running on dedicated hardware, or as virtualized functions instantiated on a suitable platform (e.g., cloud infrastructure).

[0146] Below, network slicing is explained.

[0147] Network slicing is a new concept applied to 5G mobile communications that allows for the application of properties such as network isolation, customization, and independent management and orchestration to the radio access network (RAN) and core network of mobile communications by providing network resources and network functions as an independent slice of E2E (End-to-End) resources from the radio access network (RAN) to the core network by service.

[0148] Communication technology is evolving by combining advancements in technologies such as Network Function Virtualization (NFV) and Software Defined Networks (SDN) to create network slices optimized for the characteristics of each application within a single, large network. Network slicing can mean creating a logically separated E2E (End-to-End) network that includes wireless access, transmission, and 5G core equipment from a single physical network, thereby providing a dedicated network specialized for various services with different characteristics. In other words, network slicing is a technology that provides the network resources and network functions required for a service requested by a terminal as a single, independent slice.

[0149] When a network slice is deployed, AMF interacts with NSSF to select a network slice instance. Each network slice instance may include one or more network function instances to provide the network services required by that network slice instance. For example, a network slice instance may be for multimedia services, and a network slice instance may be for Internet of Things (IoT) services.

[0150] Here, network slicing technology can refer to a technology that applies network isolation and customization properties to the mobile communication core network structure by bundling network resources and network functions into a single, independent slice according to service. Network slicing technology is a new concept for 5G core networks that has not been used in existing mobile communication network technologies. It is a technology that bundles the network resources and network functions required for a service requested by a mobile terminal into a single, independent slice and provides them.

[0151] Through this, network operators can independently allocate network resources specialized for each service and user, and secure network flexibility through resource virtualization based on SDN (Software Defined Networking) / NFV (Network Function Virtualization) technology, thereby securing scalability and reliability of service and network resource operation.

[0152] A network slice can be a complete logical network, comprising a set of network functions and corresponding resources required to provide specific network performance and characteristics. Network slices can exist on the Radio Access Network (RAN) and the Core Network (CN). A network slice instance can be an instantiation of a network slice, i.e., a deployed set of network functions that deliver intended network slice services according to a network slice template.

[0153] Network slices can be configured differently depending on the supported features and network function optimizations. Operators can deploy multiple Network Slice Instances (NSIs) dedicated to different groups of UEs, each delivering the exact same optimizations and characteristics.

[0154] The NSSF may be a network function having knowledge and overview of the NSI topology for a given Public Land Mobile Network (PLMN) (e.g., recognizing the availability of the set of active NSI(s) corresponding to the registration areas and for which entry point (i.e., AMF (260)) that is accessible to the specific NSI). In addition, the NSSF may support slice-level service mapping for a given Single-Network Slice Selection Assistance Information (S-NSSAI) to select a target NSI based on at least one of a serving Mobile Virtual Network Operator (MVNO), a service or Over The Top (OTT) provider, a location of the UE, and a time window. Here, a network slice instance can be selected from a pool of network slice instances for a particular S-NSSAI for load balancing and redundancy.

[0155] NSSF allows operators to configure slice-level control rules. For example, to provide mission-critical services such as autonomous driving or remote industrial robot control, it is necessary to acquire network slice instances with guaranteed low-latency access.

[0156] NSSF can support statistical collection for slice selection for the management system of the serving PLMN.

[0157] Additionally, the input parameters of NSSF may include an Accepted S-NSSAI. Additionally, in some cases, at least one of the UE's past associated NSI list and the UE's serving registration area may be further considered as input parameters of NSSF.

[0158] The output parameters of NSSF may include information about the newly selected serving network slice instance corresponding to the approved S-NSSAI (e.g., the NSI ID). Additionally, in some cases, at least one of the IP address or fully qualified domain name (FQDN) of the newly selected serving AMF and the IP address or FQDN of the selected serving NRF (NF Repository Function) for the selected NSI may be further considered as output parameters of NSSF.

[0159] FIG. 7 is a diagram for explaining the network slice concept according to one embodiment of the present specification.

[0160] Referring to Fig. 7, a network slice is composed of an E2E logical network including a terminal and a counterpart node (a counterpart terminal or a counterpart application server). A user can receive services by accessing a network slice specialized for the application he or she uses (eMBB, URLLC, MIoT, V2X, etc.). That is, a user's terminal can access one or more network slices simultaneously. Each slice can be identified by a slice / service type (SST) that is mapped to the expected network behavior in terms of services and characteristics.

[0161] Mobile operators can allocate network resources appropriate for a given service, either on a slice-by-slice basis or on a set of specific slices. These network resources may refer to network functions (NFs), logical resources provided by the NFs, or radio resource allocations. A network slice instance (NSI) can be defined as a set of network function instances and required resources that form a deployed network slice.

[0162] In describing embodiments of the present disclosure, the terms slice, service, network slice, network service, application slice, application service, network slice instance, etc. may be used interchangeably.

[0163] Meanwhile, next-generation wireless communication networks, such as 5G networks, are developing a split network architecture in which Radio Access Network (RAN) functionality is split between a central unit (CU) and multiple distributed units (DUs). For example, RAN functionality may be split at the point between the Packet Data Convergence Protocol (PDCP) layer and the Radio Link Control (RLC) layer of the 5G protocol stack. The DU will perform layer functions up to and including the RLC layer, while the CU will perform PDCP layer and upper layer functions prior to the core network. By separating the stack from the PDCP layer and upper layers, the CU can function as a cloud-based convergence point between networks using multiple heterogeneous technologies, thereby serving multiple heterogeneous DUs.

[0164] Below, the next-generation communication system beyond 5G or 5G-Advanced is described. For convenience, the next-generation communication system is referred to as the 6G system.

[0165] The 6G (wireless communication) system aims to provide (i) very high data rates per device, (ii) a very large number of connected devices, (iii) global connectivity, (iv) very low latency, (v) reduced energy consumption of battery-free IoT devices, (vi) ultra-reliable connectivity, and (vii) connected intelligence with machine learning capabilities. The user scenarios of the 6G system can be divided into six aspects: immersive communication, hyper reliable & low-latency communication, massive communication, ubiquitous connectivity, integrated AI and communication, and integrated sensing and communication. Although the requirements or key performance indicators (KPIs) for the 6G system have not been determined yet, it is expected to have the requirements shown in Table 1 below. In other words, Table 1 is a table showing an example of the requirements of a 6G system.

[0166] peak data rate1 TbpsE2E latency1 msMaximum spectral efficiency100bps / HzMobility supportUp to 1000km / hrSatellite integrationFullyAIFullyAutonomous vehicleFullyXRFullyHaptic CommunicationFully

[0167] 6G systems can have key factors such as enhanced mobile broadband (eMBB), ultra-reliable low latency communications (URLLC), massive machine-type communication (mMTC), AI integrated communication, tactile internet, high throughput, high network capacity, high energy efficiency, low backhaul and access network congestion, and enhanced data security.

[0168] Below, Artificial Intelligence (AI) is explained.

[0169] The most crucial and newly introduced technology for 6G systems is AI. 4G systems did not involve AI. 5G systems will support partial or very limited AI. However, 6G systems will fully support AI for automation. Advances in machine learning will create more intelligent networks for real-time communications in 6G. Incorporating AI into communications can streamline and improve real-time data transmission. AI can use numerous analyses to determine how complex target tasks should be performed. In other words, AI can increase efficiency and reduce processing delays.

[0170] Time-consuming tasks such as handover, network selection, and resource scheduling can be performed instantly using AI. AI can also play a crucial role in machine-to-machine (M2M), machine-to-human, and human-to-machine communications. Furthermore, AI can facilitate rapid communication in brain-computer interfaces (BCIs). AI-based communication systems can be supported by metamaterials, intelligent structures, intelligent networks, intelligent devices, intelligent cognitive radios, self-sustaining wireless networks, and machine learning.

[0171] Recent attempts to integrate AI into wireless communication systems have focused on the application layer, network layer, and especially deep learning in wireless resource management and allocation. However, this research is increasingly evolving to the MAC layer and physical layer, with attempts to combine deep learning with wireless transmission, particularly at the physical layer. AI-based physical layer transmission refers to the application of AI-based signal processing and communication mechanisms, rather than traditional communication frameworks, in the fundamental signal processing and communication mechanisms. For example, this may include deep learning-based channel coding and decoding, deep learning-based signal estimation and detection, deep learning-based MIMO mechanisms, and AI-based resource scheduling and allocation.

[0172] Machine learning can be used for channel estimation and channel tracking, as well as for power allocation and interference cancellation in the physical layer of the downlink (DL). Furthermore, machine learning can be used for antenna selection, power control, and symbol detection in MIMO systems.

[0173] However, the application of DNN for transmission at the physical layer may have the following problems.

[0174] Deep learning-based AI algorithms require a large amount of training data to optimize training parameters. However, due to limitations in obtaining training data from specific channel environments, a large amount of training data is used offline. This means that static training on training data in specific channel environments can lead to conflicts with the dynamic characteristics and diversity of the wireless channel.

[0175] Furthermore, current deep learning primarily targets real-world signals. However, signals at the physical layer of wireless communications are complex signals. Further research is needed on neural networks that detect complex-domain signals to match the characteristics of wireless communication signals.

[0176] Below, we will look at machine learning in more detail.

[0177] Machine learning refers to a series of operations that train machines to perform tasks that humans can or cannot perform. Machine learning requires data and a learning model. Data learning methods in machine learning can be broadly categorized into three types: supervised learning, unsupervised learning, and reinforcement learning.

[0178] Neural network training aims to minimize output errors. It involves repeatedly inputting training data into a neural network, calculating the neural network output and target error for the training data, and backpropagating the neural network error from the output layer to the input layer to update the weights of each node in the neural network to reduce the error.

[0179] Supervised learning uses labeled training data, while unsupervised learning may not have labeled training data. For example, in the case of supervised learning for data classification, the training data may be data in which each training data category is labeled. Labeled training data is input to a neural network, and the error can be calculated by comparing the output (categories) of the neural network with the training data labels. The calculated error is backpropagated through the neural network in the backward direction (i.e., from the output layer to the input layer), and the connection weights of each node in each layer of the neural network can be updated through backpropagation. The amount of change in the connection weights of each updated node can be determined by the learning rate. The neural network's calculation of the input data and the backpropagation of the error can constitute a learning cycle (epoch). The learning rate can be applied differently depending on the number of iterations of the neural network's learning cycle. For example, in the early stages of training a neural network, a high learning rate can be used to quickly allow the network to reach a certain level of performance, thereby improving efficiency. In the later stages of training, a low learning rate can be used to improve accuracy.

[0180] Learning methods may vary depending on the characteristics of the data. For example, if the goal is to accurately predict data transmitted by a transmitter in a communication system, supervised learning is preferable to unsupervised learning or reinforcement learning.

[0181] The learning model corresponds to the human brain, and the most basic linear model can be thought of, but the machine learning paradigm that uses highly complex neural network structures, such as artificial neural networks, as learning models is called deep learning.

[0182] The neural network cores used in learning methods are mainly divided into deep neural networks (DNN), convolutional deep neural networks (CNN), and recurrent boltzmann machines (RNN).

[0183] An artificial neural network is an example of a network of multiple perceptrons.

[0184] Below, THz (Tera-Hertz) communication is described.

[0185] Data transmission rates can be increased by increasing the channel bandwidth. To easily secure a wide channel bandwidth, high-frequency bands must be used. Therefore, communication methods using the sub-THz band, a frequency band higher than 100 GHz, and even the THz band, which is higher than that, are being considered. Communication methods using higher frequency bands allow for the application of advanced massive MIMO technology, as the antenna sizes and spacing between them are smaller. THz waves, also known as sub-millimeter radiation, generally refer to the frequency range between 0.1 THz and 10 THz, with corresponding wavelengths ranging from 0.03 mm to 3 mm. The 100 GHz to 300 GHz band (the sub-THz band) is considered the main portion of the THz band for cellular communications. Frequency bands up to 100 GHz have been considered for 5G mobile communications, and the sub-THz and THz bands are expected to be used in 6G mobile communications.

[0186] 6G mobile communications will utilize sub-THz and THz bands in addition to the existing mmWave band. Adding the sub-THz band to the mmWave band significantly increases channel bandwidth due to the increased use of frequency resources, resulting in increased data transmission rates and cell throughput. Among the defined THz bands, 300 GHz to 3 THz lies in the far infrared (IR) frequency band. While part of the optical band, the 300 GHz to 3 THz band lies at the boundary of the optical band, immediately following the RF band. Therefore, this 300 GHz to 3 THz band exhibits similarities to RF.

[0187] Key characteristics of THz communications include (i) a relatively wide channel bandwidth, widely available to support very high data rates, and (ii) high path loss at high frequencies (requiring highly directional antennas). The short wavelength allows for small antenna sizes and very close spacing between antennas, allowing a significant number of antennas to be deployed in a small area. The narrow beams generated by beamforming across these numerous antennas can reduce interference. In other words, the small wavelength of THz signals allows for a significantly larger number of antenna elements to be integrated into devices and base stations operating in this band. This enables the use of advanced adaptive array technologies to overcome range limitations.

[0188] THz wireless communication is a wireless communication using THz waves with a frequency of approximately 0.1 to 10 THz (1 THz = 1000 GHz). It can refer to terahertz (THz) band wireless communication using a very high carrier frequency of 100 GHz or higher. THz waves are located between the RF (Radio Frequency) / millimeter (mm) and infrared bands, and (i) compared to visible light / infrared light, they penetrate non-metallic / non-polarizable materials well, and compared to RF / millimeter waves, they have a shorter wavelength, so they have high linearity and can focus beams. In addition, since the photon energy of THz waves is only a few meV, they have the characteristic of being harmless to the human body. The frequency bands expected to be used for THz wireless communication may be the D-band (110 GHz to 170 GHz) or H-band (220 GHz to 325 GHz), which have low propagation loss due to molecular absorption in the air. Discussions on standardization of THz wireless communication are being centered around the IEEE 802.15 THz working group in addition to 3GPP, and standard documents issued by the IEEE 802.15 Task Groups (TG3d, TG3e) may elaborate or supplement the contents described in this specification. THz wireless communication can be applied to wireless cognition, sensing, imaging, wireless communication, and THz navigation.

[0189] THz wireless communication scenarios can be categorized into macro networks, micro networks, and nanoscale networks. In macro networks, THz wireless communication can be applied to vehicle-to-vehicle (V2V) communications and backhaul / fronthaul connections. In micro networks, THz wireless communication can be applied to fixed point-to-point or multi-point connections, such as indoor small cells, wireless connections in data centers, and near-field communications, such as kiosk downloads.

[0190] Below, the proposed methods of this specification are described. The proposed methods, embodiments, and other elements described herein may be combined and used within a range of non-interference. Furthermore, some steps, operations, procedures, and configurations of the proposed methods and embodiments described herein may be omitted for implementation.

[0191] Edge computing, which transmits data using edge servers, has recently been discussed. Edge computing may include, for example, multi-access edge computing (MEC) or fog computing. Edge computing can refer to a technology that provides data to electronic devices through a separate server (hereinafter, an edge server or MEC server) installed geographically close to the electronic device, such as within or near a base station. For example, at least one application installed on an electronic device that requires low latency can transmit and receive data through an edge server installed geographically close to the device, rather than through an external data network (DN), such as a server located on the Internet.

[0192] There is ongoing discussion about the architecture for implementing edge computing services in next-generation communication systems. Edge computing can be referred to as mobile edge computing or multi-access edge computing. In various embodiments of the present disclosure, edge computing will be referred to as MEC for convenience. MEC is a technology that alleviates mobile core network congestion, achieves low-latency data communication with terminals, and creates new services based on this by installing a wireless base station or a gateway (or UPF) near the wireless base station and applying distributed cloud computing technology thereon to deploy various services and caching content close to user terminals.

[0193] MEC provides application developers and content providers with cloud computing capabilities and an IT (information technology) service environment at the mobile network edge. Specifically, MEC enables applications to provide ultra-low latency, high-capacity bandwidth, and real-time network information access. Therefore, applications offering MEC services can provide MEC services to terminals via the 5G system (5GS). Furthermore, the 5G system can provide functionality for terminals using MEC services to access the MEC system. In addition to the 5G system, next-generation wireless communication systems, such as 6G and / or 4G systems following the 5G system, can also provide functionality for MEC services.

[0194] Demand for extended reality (XR) services is growing. XR encompasses virtual reality (VR), augmented reality (AR), and mixed reality (MR). VR technology provides real-world objects and backgrounds as CG images only, AR technology provides virtual CG images overlayed on top of real-world images, and MR technology is a computer graphics technology that blends and combines virtual objects with the real world.

[0195] MR technology is similar to AR in that it presents both real and virtual objects simultaneously. However, while AR uses virtual objects to complement real objects, MR uses virtual and real objects on an equal footing.

[0196] XR technology can be applied to HMD (Head-Mount Display), HUD (Head-Up Display), mobile phones, tablet PCs, laptops, desktops, TVs, digital signage, etc., and devices to which XR technology is applied can be called XR devices.

[0197] In relation to XR technology / XR services, since a lot of computing resources are required for rendering video streaming, etc., the ability to process rendering on an edge server is being discussed for complex rendering, as shown in Fig. 8. Fig. 8 illustrates an example of processing rendering on an edge server.

[0198] Similar to XR services, the concept of processing computing on edge servers is also being discussed, including virtualization device functions. A virtual device can be a service where a virtual device is displayed within a specific device, similar to a computer's virtual machine. In this case, the virtual device or virtualization device function is processed in the cloud, which possesses massive computing power or capabilities, resulting in relatively low power consumption and, in B2B applications, preventing the leakage of secure data. Figure 9 illustrates an example of how the virtualization device function is implemented.

[0199] Edge computing for these services may require low latency and high reliability. Therefore, if processing for these computations is performed within a mobile system, it may be advantageous to process them at the base station closest to the terminal. However, current mobile systems process IP (Internet Protocol) layer and application layer data not at the base station, but through a dedicated core device called the User Plane Function (UPF). Therefore, considering the current mobile system architecture, delays in computational processing may occur.

[0200] Meanwhile, a technology called semantic communication is being researched. Figure 10 illustrates an example of semantic communication data processing. Specifically, Figure 10 (a) illustrates an example of data processing in a conventional communication system, and Figure 10 (b) illustrates an example of data processing in a semantic communication system. According to this technology, source data is interpreted and encoded as data with intent based on AI, and the receiving end decodes and reinterprets the data based on the same AI model, thereby transmitting information. According to this technology, when data for a service requiring a large transmission capacity is transmitted, it is reduced to a very small form and transmitted, which can increase communication capacity. In this case, since source coding of the actual data may be required, the transmitting and receiving entities on the communication channel may need to process the data at the IP layer or application layer. In addition, for the implementation of the technology, the semantic communication data must be closely linked cross-layer with channel coding information, etc., so close processing within the base station may be required.

[0201] To perform the above technologies / services, data processing for the IP or application layers may need to be performed at the base station. However, if data processing for the IP or application layers is typically performed at the base station, delays can occur and significant computing power is required, potentially degrading communication system performance.

[0202] Therefore, a base station may need a method for processing services that require the integration of computing and communication and services that only require communication separately. This specification proposes a method for processing such services separately and a method for processing such separated services through separate protocol structures. For example, this specification defines a new protocol stack that enables a base station to perform data processing for the IP layer or application layer, defines a new slice to designate a service for the protocol stack, defines an SLA (Service-Level Agreement) required for configuring the slice (e.g., available computing resources, service function availability, etc.), and presents a setup process required for establishing the SLA. Meanwhile, in this specification, a method and / or technology for a base station to process / perform computing is referred to as base station computing or RAN computing. Here, the base station may include a base station of a next-generation wireless communication system such as a gNB, an eNB, and / or a 6G. Furthermore, the method and / or technology described herein based on base station computing may be performed by a base station and / or an edge server close to the base station. Meanwhile, a service that is a convergence of computing and communication, or a service that provides (or requires) computing of a RAN, or a service that provides (or requires) computing of a base station, or a service that provides (or requires) computing of an edge server may be called a base station computing service or a RAN computing service.

[0203] As an example, a base station computing-related slice protocol structure is proposed. Fig. 11 illustrates an example of a base station computing slice protocol layer structure according to one embodiment of the present specification.

[0204] Referring to Fig. 11, the current wireless communication protocol can be configured with IP lower layers (e.g., PDCP, RLC, MAC, PHY layers, etc.) between the base station and the terminal, such as slice #2. For UL (uplink), the terminal can perform necessary encoding on data generated in the application layer / IP layer while passing through the PDCP, RLC, MAC, and PHY layers. The encoded data is received by the base station and then decoded in reverse across the PHY, MAC, RLC, and PDCP layers, and can be generally transmitted to the UPF (or P-GW (PDN gateway)) that processes the IP layer to the service server. For DL ​​(downlink), data received from the UPF can be encoded for the wireless protocol layers. The encoded data is transmitted to the terminal, and the terminal can obtain the final application data by decoding the data.

[0205] This specification proposes a configuration of a slice, such as slice #1 of FIG. 11. For this slice, the base station can receive data for both the IP layer and the application layer, and perform computing processes on the service data. The processing performed by the base station can include compression processing, AI processing, and selective processing of certain data, for data above the IP layer, i.e., data from the IP layer and the application layer.

[0206] For UL, the base station can transmit the application layer data or application data received from the terminal to the UPF through an encoding process from the IP layer to the transport L1. Through this processing, the service data transmitted from the terminal can be transformed / modified through a computing process. For example, the service data can be compressed through this processing, reducing its volume. For another example, for XR services, a portion of the service data to be transmitted to the DL can be determined and transmitted.

[0207] For DL, the base station can encode the application layer data received from the UPF through an encoding process from the IP layer to the physical layer and then transmit it to the terminal. Through this processing, the service data transmitted from the UPF can be transformed / modified through a computing process. For example, the service data can be compressed through this processing, reducing its volume. For another example, for XR services, some of the service data can be determined and transmitted to the DL.

[0208] Figure 12 illustrates an example of a case where DL data changes according to UL data. Referring to Figure 12, for 360-degree VR service DL data including HQ tiles, which are ultra-high definition tiles, and LQ tiles, which are low definition tiles, the HQ data actually transmitted may be a portion of the entire HQ data depending on the user's focal point. In order to perform the above technologies / services, it may be necessary for the base station to perform data processing for the IP layer or application layer.

[0209] As an example, a base station computing-related slice establishment procedure based on an Access Stratum (AS) message is proposed. Fig. 13 illustrates an example of a base station computing-related slice establishment procedure based on an AS message according to one embodiment of the present specification.

[0210] Slices related to base station computing can be set up / established based on AS messages. Here, base station computing can also be performed based on the computing resources of an edge server near the base station. In this case, the computing resources actually available at the base station can be a key indicator of whether a slice is established / allowed. To this end, a request / response procedure for available computing resources and a procedure for determining available computing resources can be performed between the base station and the edge server. Furthermore, in addition to computing resources, if the mobility of a terminal is excessively high, frequent handovers can lead to live migration or live application migration, which can cause time delays. Therefore, terminal mobility can be a key indicator of whether a slice is allowed. Furthermore, the support / readiness of the corresponding service application can be a key indicator of whether a slice is allowed.

[0211] Referring to FIG. 13, a terminal may transmit network slice-related information to a base station (S1310). Here, the network slice-related information may be transmitted as part of AS information or AS messages (e.g., terminal capability information, terminal assistance information, mobility-related information, setup information, etc.). Alternatively, the network slice-related information may be included in newly defined information (e.g., network slicing initiation information, base station computing-related information, etc.).

[0212] The above network slice-related information may include information about a base station computing slice. Here, slice information about a service for which the base station performs computing may be included in the network slice-related information. At this time, when a terminal transmits service requirement information requested by the terminal to the network / system in order to receive a service from a specific network slice instance, the core network may select an appropriate network slice instance. To this end, a Network Slice Selection Function (NSSF) and Network Slice Selection Assistance Information (NSSAI) may be used, and the information may include SST (Slice / Service Type) information that distinguishes a service type and SD (Slice Differentiator) information that distinguishes an attribute of a network slice instance. For example, the information about the base station computing slice may be SST information defined for base station computing. In addition, the NSSAI may be composed of one or more S-NSSAI (Single-Network Slice Selection Assistance Information), and the S-NSSAI may include SST information and SD information. Here, as an example, information about the base station computing slice may be specific information included in the S-NSSAI in addition to SST information and SD information (in this specification, the specific information is referred to as SSST (subsidiary SST) information). The SSST information may be combined with the SST information to indicate a slice / service. Fig. 14 illustrates an example of a configuration of information about a base station computing slice according to an embodiment of the present specification. Specifically, Fig. 14 (a) illustrates an example of a configuration of SST information about a base station computing slice, and Fig. 14 (b) illustrates an example of a configuration of SSST information about a base station computing slice.For example, referring to (a) of FIG. 14, an SST related to RAN computing (or base station computing) may be newly defined. As another example, referring to (b) of FIG. 14, an SSST related to RAN computing (or base station computing) may be newly defined.

[0213] In addition, here, the terminal can determine whether base station computing is necessary and perform operation S1310 based on the determination that base station computing is necessary. Alternatively, the base station, 5GC, and / or DN (Data Network) (or service server) can determine whether base station computing is necessary and instruct the terminal to perform operation S1310 based on the determination that base station computing is necessary. The terminal can perform operation S1310 based on the instruction.

[0214] The base station may transmit slice request information to the 5GC based on the network slice-related information (S1320). Here, the base station may calculate the computing resources that it can use for the corresponding service and determine whether it can provide the corresponding slice. At this time, the base station may use the aforementioned indicators (e.g., availability of computing resources, mobility of the terminal, support for the corresponding service application, etc.) when determining whether it can provide the corresponding slice. For example, whether to provide an edge computing slice or a base station computing slice may be determined based on speed information / mobility information reported by the terminal. At this time, the base station may also determine whether to provide the corresponding slice based on whether the application function of the corresponding service can be provided. If the base station determines / judges that it can provide the corresponding slice, the base station may transmit the slice request information. Here, for example, the slice request information may include request NSSAI information. The request NSSAI information may be slice information for a service for which base station computing is performed. As another example, the slice request information may include information about available computing resources. The information about available computing resources may indicate the computing resources currently available for the service. Here, the computing resources may be indicated using a percentage indicator based on the computational load of a single reference CPU. In this case, if the slice request information indicates multiple slices, the information about available computing resources may be configured by mapping the information about the multiple computing resources to the slice IDs for the multiple slices.

[0215] The base station may receive slice response information from the 5GC based on the slice request information (S1330). Here, the slice response information may include information on whether the slice is permitted. The base station may transmit information on whether the slice is permitted to the terminal based on the slice response information.

[0216] The terminal may perform an activation operation of the base station, 5GC, and / or DN and the base station computing slice (S1340). Here, the activation operation may include transmitting and receiving communication and service-related information based on the base station computing slice protocol layer proposed in this specification.

[0217] As an example, a base station computing-related slice establishment procedure based on a Non-Access Stratum (NAS) message is proposed. Fig. 15 illustrates an example of a base station computing-related slice establishment procedure based on a NAS message according to one embodiment of the present specification.

[0218] Base station computing-related slices can be set up / established based on AS messages. Here, a procedure may be considered in which a terminal requests slice setup via an NAS message sent to the 5GC, and the 5GC requests the base station to review / judge computing resources for slice operation. At this time, the computing resources available at the base station for slice establishment can be a key indicator of whether or not to allow slicing. To this end, a request / response procedure for available computing resources and a procedure for judging available computing resources can be performed between the base station and the edge server. Furthermore, in addition to computing resources, if the mobility of the terminal is excessively high, frequent handovers can lead to live migration or live application migration, which can cause time delays. Therefore, terminal mobility can be a key indicator of whether or not to allow slicing. Furthermore, the readiness of the corresponding service application can be a key indicator of whether or not to allow slicing.

[0219] Referring to FIG. 15, the terminal may transmit network slice related information to the 5GC (S1510). Here, the network slice related information may be transmitted via a NAS message. For example, the NAS message may be a registration request message. Here, the NAS message may include information on a base station computing slice. At this time, slice information on a service for which the base station performs computing may be included in the network slice related information. For example, the information on the base station computing slice may be SST information defined for base station computing. In addition, the NSSAI may be composed of one or more S-NSSAI (Single-Network Slice Selection Assistance Information), and the S-NSSAI may include SST information and SD information. Here, for example, the information on the base station computing slice may be specific information included in the S-NSSAI in addition to the SST information and SD information (in this specification, the specific information is referred to as SSST (subsidiary SST) information). The SSST information may be combined with the SST information to indicate a slice / service. For example, information about the base station computing slice can be configured as in FIG. 14.

[0220] 5GC can transmit slice request information to the base station (S1520). The slice request information can include request information for determining available computing resources to confirm whether the slice is in operation. Before performing step S1520, the 5GC can check / determine whether the terminal and the base station can support the slice through subscription, policy, etc. For example, if it is determined that slice support is possible for the remaining parts excluding the presence of available computing resources of the base station, the 5GC can perform step S1520. Here, the determination request information can include at least one of the following information.

[0221] - Information about the requested NSSAI: Information identifying the corresponding slice may be included in the judgment request information. For example, information in the same form / format as the information used in step S1510 may be included in the judgment request information.

[0222] - Information on requested computing resources: Information on computing resources required for the service may be included in the judgment request information. For example, the information on requested computing resources may indicate a percentage indicator based on the computational load of a single reference CPU.

[0223] - Information about the requested service function: The judgment request information may include information requesting the availability of the service function required for the service. For example, the information about the requested service function may include information such as the name of the service function and the manufacturer's name.

[0224] The base station may transmit slice response information to the 5GC (S1530). Here, the slice response information may include information on whether the base station has available computing resources. In addition, the slice response information may include information that can identify one or more available slices. Here, the information that can identify the slices may be information in the same form / format as the information used in step S1510. In addition, the slice response information may include information on the availability of computing resources. The information on the availability of computing resources may be information on computing resources available for a corresponding service. For example, the information on the availability of computing resources may indicate a percentage indicator based on the computational load of one reference CPU. In another example, the information on the availability of computing resources may indicate whether they are available (i.e., available or unavailable). Here, for a plurality of slices, the information on the availability of computing resources may be mapped to each of the plurality of slice identifiers and transmitted.

[0225] 5GC can transmit network slice usage information to the terminal (S1540). The network slice usage information can indicate whether to allow the slice. Here, before performing step S1540, 5GC can determine whether to allow the slice based on at least one of network slice-related information and slice response information. In this case, step S1540 can be performed based on the 5GC's determination of whether to allow the slice.

[0226] The terminal may perform an activation operation of the base station, 5GC, and / or DN and the base station computing slice (S1550). Here, the activation operation may include transmitting and receiving communication and service-related information based on the base station computing slice protocol layer proposed in this specification.

[0227] FIG. 16 is a flowchart illustrating an example of a method for configuring a network slice of a base station according to one embodiment of the present disclosure. The example of FIG. 16 can be implemented in combination with various embodiments, proposed methods, and configurations described in the present disclosure, including FIGS. 1 to 15 .

[0228] Referring to Figure 16, the base station determines whether a base station computing network slice is configured (S1610). Here, the base station computing network slice may be a network slice that provides a service that performs computing at the base station or an edge server adjacent to the base station.

[0229] For example, the base station may receive network slice-related information from the terminal. At this time, the network slice-related information may be transmitted as included in AS information or an AS message (e.g., terminal capability information, terminal assistance information, mobility-related information, setup information, etc.). Alternatively, the network slice-related information may be included in newly defined information (e.g., network slicing initiation information, base station computing-related information, etc.). In addition, the network slice-related information may include information for identifying a base station computing network slice.

[0230] For example, the base station may transmit slice request information to the 5GC based on the network slice-related information. Here, the base station may calculate the computing resources that it can use for the corresponding service and determine whether it can provide the corresponding slice. At this time, the base station may use the aforementioned indicators (e.g., availability of computing resources, mobility of the terminal, support for the corresponding service application, etc.) when determining whether it can provide the corresponding slice. For example, whether to configure an edge computing slice or a base station computing slice may be determined based on speed information / mobility information reported by the terminal. At this time, the base station may also determine whether to configure the corresponding slice based on whether the application function of the corresponding service can be provided. If the base station decides / determines to configure the corresponding slice, the base station may transmit the slice request information. Here, for example, the slice request information may include request NSSAI information. The request NSSAI information may be slice information for a service for which base station computing is performed. As another example, the slice request information may include information on available computing resources. The information on available computing resources may indicate computing resources currently available for a corresponding service. Here, the computing resources may be indicated using a percentage indicator based on the computational load of a single reference CPU. In this case, if the slice request information indicates multiple slices, the information on available computing resources may be configured by mapping information on multiple computing resources to slice IDs for the multiple slices. In addition, the base station may receive slice response information from the 5GC based on the slice request information. Here, the slice response information may include information on whether or not a slice is permitted.

[0231] As another example, the base station may receive availability request information for a base station computing network slice from the 5GC, and determine whether the slice is configured based on the availability request information. Here, the availability request information may include request information for determining available computing resources to confirm whether the slice is operating. The 5GC may confirm / determine whether the terminal and the base station can support the slice through subscription, policy, etc. For example, if the base station determines that slice support is possible for the remaining part excluding the presence of available computing resources of the base station, the base station may receive availability request information from the 5GC. Here, the availability request information may include at least one of the following information.

[0232] - Information about the requested NSSAI: Information identifying the slice may be included in the availability request information.

[0233] Information about requested computing resources: Information about the computing resources required for the service may be included in the availability request information. For example, the information about the requested computing resources may indicate a percentage indicator based on the computational load of a single reference CPU.

[0234] - Information about the requested service function: Information requesting the availability of the service function required for the service may be included in the availability request information. For example, the information about the requested service function may include information such as the name of the service function and the manufacturer's name.

[0235] If the base station determines to configure the slice, the base station may transmit availability response information to the 5GC. Here, the availability response information may include information on whether the base station has available computing resources. In addition, the availability response information may include information that can identify one or more available slices. In addition, the availability response information may include information on the availability of computing resources. The information on the availability of computing resources may be information on computing resources available for a corresponding service. For example, the information on the availability of computing resources may indicate a percentage indicator based on the computational load of one reference CPU. In another example, the information on the availability of computing resources may indicate whether they are available (i.e., available or unavailable). Here, for a plurality of slices, the information on the availability of computing resources may be mapped to each of the plurality of slice identifiers and transmitted.

[0236] Based on the above judgment, the base station configures the base station computing network slice (S1620). Here, the base station can communicate data for services that use base station computing based on the base station computing network slice. For example, based on the base station computing network slice, the base station can process data at the IP layer and application layer.

[0237] Meanwhile, if data processing for the IP or application layer is typically performed by a base station, delays can occur and significant computing power is required, potentially degrading communication system performance. Therefore, base stations may need to differentiate between services that require a convergence of computing and communications and those that only require communication.

[0238] RAN computing services can be implemented in open radio access networks, such as the Open-RAN (O-RAN) standard. According to the present invention, the open radio access network may include a logical central unit (CU) component that provides RAN computing services. Here, the logical CU component provides application data processing, various types of computing processing, resource pooling across multiple base stations, and ensuring low data mobility, etc., for providing RAN (radio access network) computing services. At this time, the open radio access network requires a setup procedure and signaling configuration to provide RAN computing services.

[0239] Meanwhile, the embodiments of the present specification can be applied not only to O-RAN but also to various radio access networks (RAN). For example, the RRC, PDCP, RLC, MAC, and PHY layers can be subdivided into RRC, PDCP, High RLC, Low RLC, High MAC, Low MAC, High PHY, and Low PHY layers. Here, for example, the RRC and PDCP layers can be included in an O-CU (O-RAN Central Unit), the High RLC, Low RLC, High MAC, Low MAC, and High PHY layers can be included in an O-DU (O-RAN Distributed Unit), and the Low PHY (and RF) can be included in an O-RU (O-RAN Radio Unit). In this case, an open fronthaul interface can exist between the O-DU and the O-RU, in which case, a multi-vendor RAN model can be implemented. Alternatively, the above interface may not be applied to the RAN. In this case, the embodiments of the present specification may be implemented on an existing RAN or a RAN without such an interface, as long as they are not mutually collocated.

[0240] Figure 17 is an example of an open radio access network that provides RAN computing services.

[0241] Referring to FIG. 17, the open radio access network (1100) includes a service management and orchestration framework (1110) including a non-real time RIC (RAN Intelligent Controller) layer (1111), a real-time RIC (1120) layer, an open gNB (O-gNB, 1130), an open eNB (O-eNB, 1140), an open cloud (O-Cloud, 1150), and a RAN computing module (O-CU-ComP, 1160).

[0242] The non-real-time RIC layer (1111) is a controller of an intelligent radio access network, and is a controller that requires more than 1 second in terms of control latency. The non-real-time RIC layer (1111) performs big data analysis and artificial intelligence-based management through machine learning, such as RAN policy management, network traffic patterns, terminal mobility patterns, service types, and quality of service (QoS) prediction patterns. The trained model generated in the non-real-time RIC layer (1111) is distributed to the real-time RIC layer (1120) via the A1 interface.

[0243] The real-time RIC layer (1120) is a controller of an intelligent radio access network and provides a radio resource management function with a control latency of approximately 0.01 to 1 second. The real-time RIC layer (1120) is responsible for functions such as terminal-level load balancing, resource block management, as well as service quality and terminal mobility management. The real-time RIC layer (1120) transmits control commands (handover, resource allocation, etc.) to the O-CU (O-RAN Central Unit, 1131-1, 1131-2) and the O-DU (O-RAN Distributed Unit, 1132) via the E2 interface, and collects measured data and provides it to the non-real-time RIC layer (1111). Through this interaction, control algorithms related to load balancing, mobility management, etc. are optimized.

[0244] When looking at the configuration of one open gNB (1130) within the open wireless access network (1100) architecture, the open gNB (1130) includes an O-CU (1131-1, 1131-2), an O-DU (1132), and an O-RU (Radio Unit, 1133). The O-CU (1131-1, 1131-2) may be logically functionally divided into an O-CU-UP (User Plane, 1131-1) that transmits control plane information and an O-CU-CP (Control Plane, 1131-2) that transmits user plane data.

[0245] The O-DU (1132) is responsible for real-time L2 (Layer 2) functions of the Radio Link Control and Medium Access Control layers and baseband signal processing, while the O-RU (1133) performs radio signal processing. An open fronthaul interface is defined between the O-DU and O-RU.

[0246] In the case of O-RU (1133), the physical layer is divided into two and communication protocol processing is performed for the lower physical layer.

[0247] Figure 18 shows the functional separation of O-DU and O-RU.

[0248] Referring to FIG. 18, the physical layer process below the MAC layer (1200) includes channel coding (1210), scrambling (1220), modulation (1230), layer mapping (1240), precoding (1250), digital beamforming (1260), FFT / IFFT cyclic prefix (CP) (1270), DAC / ADC (1280), and analog beamforming (1290).

[0249] Each element of the above physical layer process can be performed separately by an O-DU (1132) or an O-RU (1133), and depending on the point at which the separation occurs, various cases (Split 6, Split 7-3, Alternative 7-2 Splits, Split 7-1, Split 8) may exist.

[0250] For example, based on the 7-2 Split, the O-RU (1133) can perform processing for layer mapping (Layer Mapping, 1240), precoding (Pre-coding, 1250), digital beamforming (Digital Beamforming, 1260), FFT / IFFT CP (Cyclic Prefix, 1270), DAC / ADC (1280), and analog beamforming (Analog Beamforming, 1290). In addition, the O-DU (1132) performs processing for the remaining physical layer processes, MAC layer (1200) processes, and RLC layer protocols that are not performed in the O-RU (1133).

[0251] Referring back to FIG. 17, the O-CU-UP (1131-2) performs processing for the PDCP layer for a data session. The O-CU-CP (1131-1) performs processing for a control session, and thus performs processing for the PDCP layer and the RRC layer. An E1 interface is designed for control between the O-CU-CP (1131-1) and the O-CU-UP (1131-2). An X2-c interface is designed for control signaling communication between the O-CU-CPs (1131-1) of different base stations. In addition, an X2-u interface is designed for communication of data packets between the O-CU-UPs (1131-2) of different base stations.

[0252] If the O-CU (1131-1, 1131-2) only performs protocol processing for the PDCP layer, it cannot process application data, and thus cannot be equipped with application functions for processing application data. To achieve this, a suitable logical function capable of performing services requiring various computing resources is required, and this can be implemented by the RAN computing module (O-CU-ComP, 1160).

[0253] The RAN computing module (1160) is a logical component required to provide RAN computing services. It may be named O-CU-ComP, but this is only an example, and other terms that provide the same function may be used. Here, ComP refers to a computing plane, a plane dedicated to computing services. In Fig. 17, the RAN computing module (1160) is shown as a separate functional element from the gNB (1130), but this is only an example for the convenience of explanation, and it may be included within the gNB (1130) as a logical functional element.

[0254] In situations where the type of computing unit required varies depending on the service type that requires computing resources of various types of processing units (e.g., CPU, GPU, NPU, etc.), the RAN computing module (O-CU-ComP, 1160) provides selective processing or selection of processing units. Service types that require specific computing resources may not always be required and may require less mobility guarantee across multiple base stations. In other words, the RAN computing module (O-CU-ComP, 1160) can function as a new structure that can satisfy the above requirements, i.e., a logical CU component. The RAN computing module (O-CU-ComP, 1160) is as shown in FIG. 19 when viewed from a protocol stack perspective.

[0255] Figure 19 illustrates a protocol stack including a RAN computing module.

[0256] Referring to FIG. 19, the protocol stack (1300) according to the present embodiment includes a RAN computing module (1160) as a logical component, and may be located at a level corresponding to the IP / APP layer (1310). The RAN computing module (1160) may have at least one of the following characteristics.

[0257] 1) The RAN computing module (1160) may be connected to the O-CU-UP (1131-2). The O-CU-UP (1131-2) may perform processing from the physical layer to the PDCP layer, and the RAN computing module (1160) may perform processing for IP / App. That is, in the RAN computing service according to the present embodiment, protocol processing of all layers may be performed through the RAN computing module (1160) connected to the O-CU-UP (1131-2). At this time, the RAN computing module (1160) may require an interface for connection with the O-CU-UP (1131-2), which may be named C1-u. IP packets may be exchanged through the C1-u interface.

[0258] 2) The RAN computing module (1160) can process user data sessions.

[0259] 3) The RAN computing module (1160) may be connected to multiple O-CU-UPs and / or multiple O-CU-CPs. In this case, each O-CU-UP and O-CU-CP may be a node having connectivity via E1.

[0260] 4) The RAN computing module (1160) can perform processing on application data. Processing of application data may include the following embodiments.

[0261] - From the UL (uplink) perspective, the RAN computing module (1160) can send the application data received from the terminal back to the UPF through an encoding process from the IP layer to the transport L1. In this processing, service data can be generated as data that has been changed through a computing process from the data initially received from the terminal. That is, the RAN computing module (1160) can generate changed data by applying computing processing to the application data received from the terminal. As a result, the data can be compressed and the amount of data can be reduced. In the case of XR, some of the data to be transmitted in the downlink can be selectively determined and transmitted based on the service data.

[0262] - From a DL (uplink) perspective, the RAN computing module (1160) can transmit application data received from the UPF to the terminal after going through an encoding process from the IP layer to the physical layer. In this processing, service data can be generated as data that has been transformed through a computing process from the data initially transmitted from the UPF. That is, the RAN computing module (1160) can generate transformed data by applying computing processing to the application data received from the UPF. As a result, the data can be compressed and the amount of data can be reduced. In the case of XR, some of the data to be transmitted in the downlink can be selectively determined and transmitted based on the uplink service data.

[0263] 5) The RAN computing module (1160) may provide application functions for processing application data. For example, data may be compressed to reduce the amount of data. As another example, in the case of XR, the RAN computing module (1160) may determine a portion of the large amount of data to be transmitted via downlink based on service data. As another example, an AI inferencing service may be provided for providing federated AI services.

[0264] 6) The RAN computing module (1160) may require an interface for connection with the O-CU-CP (1131-1). In this embodiment, the interface is referred to as C1-c. The C1-C interface may provide at least one of the following functions or information.

[0265] - Service functions to be performed in the RAN computing module (1160)

[0266] - Life Cycle Management (LCM) function for the above service functions. LCM includes activation, deactivation, and deployment.

[0267] 7) The RAN computing module (1160) may require an interface for connection with the O-CU-UP (1131-2), which may be referred to as C1-u. IP packets may be exchanged through the C1-u interface.

[0268] 8) The RAN computing module (1160) may require an interface for connection with other RAN computing modules. In the present embodiment, the interface may be named X2-u_com. In the X2-u_com interface, delivery in the form of service live migration rather than general packets may occur. As an example, the delivery in the form of service live migration may include delivery in the form of moving a container for an ongoing service. As another example, the delivery in the form of service live migration may include delivery in the form of moving a docker for an ongoing service. As yet another example, the delivery in the form of moving a virtual machine for an ongoing service. As yet another example, the delivery in the form of moving a service metadata for an ongoing service may include delivery in the form of moving a service metadata.

[0269] FIG. 20 is a flowchart illustrating an O-RAN resource configuration (or formation) procedure for providing RAN computing services according to one embodiment. FIG. 20 may also be referred to as a PDU session configuration (or formation) procedure for providing RAN computing services.

[0270] In one aspect, a separate network slice for providing RAN computing services may be defined or used. Here, the separate network slice for providing RAN computing services may be referred to as a RAN computing slice. The embodiment of FIG. 20 relates to a process for reconfiguring O-RAN resources (including, for example, reconfiguring O-Cloud and VNFs) for providing RAN computing services, assuming that a RAN computing slice is used, and discloses a process for configuring O-CU-ComP VNFs by considering the computing resources required in the O-Cloud and preferred computing types when configuring (or forming) the RAN computing slice.

[0271] Referring to FIG. 20, the terminal transmits a registration request message to 5GC (S2010). The registration request message may be an NAS message. The registration request message may include RAN computing slice-related information or indicators. Here, the RAN computing slice-related information is slice information for services that perform computing in the gNB or RAN.

[0272] As an example of information related to a RAN computing slice, a slice / service type (Slice Service Type: SST) indicating RAN computing can be newly defined, as shown in (a) of Fig. 14. That is, the terminal can set the slice / service type to "RAN computing" and transmit a registration request message including the set slice / service type to 5GC. At this time, the 5GC receives a registration request message including the slice / service type indicating RAN computing from the terminal.

[0273] As another example of RAN computing slice-related information, an S-NSSAI including a Subsidiary SST (SSST) field indicating RAN computing may be defined, as in (b) of FIG. 14. That is, a terminal may include an S-NSSAI including a Subsidiary SST field indicating RAN computing in a registration request message and transmit it to 5GC. At this time, the 5GC may receive an S-NSSAI including a Subsidiary SST field indicating RAN computing from the terminal through the registration request message. Meanwhile, the Subsidiary Slice / Service Type may also indicate a RAN computing service in the form of a combination with a service specified by the Slice / Service Type.

[0274] Upon receiving a registration request message, the 5GC can check whether the terminal and base station (gNB or O-CU-CP) can support the RAN computing slice. The check procedure can be based on subscription or policy. If the terminal and base station determine that they can support the RAN computing slice, the 5GC transmits a Slice Resource Status Request message to the base station to request a check of the actually available computing resources to confirm whether the final slice is operating (S2020). The Slice Resource Status Request message may be named a status check request message or may be named by another name. The Slice Resource Status Request message is an NG-C control plane message and may include at least one or more of the following information.

[0275] 1) Requested NSSAI

[0276] Slice information about the service for which the base station performs computing may be included in the slice resource status request message. In this case, the slice information may include information about the slice ID (e.g., SST or SSST indicating RAN computing) used in step S2010.

[0277] 2) Required computing resource

[0278] Computing resource information required for RAN computing services may be included in a slice resource status request message. For example, the computing resource information required for RAN computing services may indicate a percentage indicator based on the computational capacity of a single reference CPU.

[0279] 3) Required service function

[0280] Information querying the availability of service functions required for RAN computing services may be included in the slice resource status request message. For example, the information querying the availability of service functions required for RAN computing services may include information such as the name of the service function and the manufacturer's name.

[0281] Next, the base station (or O-CU-CP) transmits a RAN computing slicing allocation / change / delete request message to the Service Management & Orchestrator (SMO) (including rAPP) (S2030). The RAN computing slicing allocation / change / delete request message is transmitted via the O1 interface. The RAN computing slicing allocation / change / delete request message provides the function to create, modify, or remove a slice for providing RAN computing services and may be named differently. The RAN computing slicing allocation / change / delete request message may include at least one of the following information:

[0282] 1) Requested NSSAI

[0283] The RAN Computing Slicing Assignment / Change / Delete Request message may include slice information for a service for which the base station performs computing. The slice information may include at least one of the following information elements.

[0284] - Information about the slice ID used in the S2010 phase (e.g. SST or SSST indicating RAN computing)

[0285] 2) Requested computing resources

[0286] The RAN Computing Slicing Allocation / Change / Delete Request message may include computing resource information required for RAN computing services. For example, the computing resource information required for RAN computing services may indicate a percentage indicator based on the computational capacity of a single reference CPU.

[0287] 3) Preferred computing type

[0288] The preferred type of computing resource may vary depending on the service. For example, AI-related service computing may benefit from processing by a Neural Processing Unit (NPU), video streaming services like XR may benefit from processing by a Graphics Processing Unit (GPU), and general services like virtual devices may benefit from processing by a Central Processing Unit (CPU).

[0289] 4) Requested service function

[0290] The RAN Computing Slicing Allocation / Change / Deletion Request message may include information querying the availability of service functions required for RAN computing services. For example, the information querying the availability of service functions required for RAN computing services may include information such as the name of the service function and the manufacturer's name.

[0291] Next, the SMO transmits a RAN Computing Slicing Allocation / Change / Delete Request message to the Open Cloud (O-Cloud) (S2040). The RAN Computing Slicing Allocation / Change / Delete Request message is transmitted via the O2 interface. The RAN Computing Slicing Allocation / Change / Delete Request message provides the function to create, modify, or delete slices for providing RAN computing services and may be named differently. The RAN Computing Slicing Allocation / Change / Delete Request message may include at least one of the following pieces of information:

[0292] 1) Requested NSSAI

[0293] The RAN Computing Slicing Assignment / Change / Delete Request message may include slice information for a service for which the base station performs computing. The slice information may include at least one of the following information elements.

[0294] - Information about the slice ID used in the S2010 phase (e.g. SST or SSST indicating RAN computing)

[0295] 2) Requested computing resources

[0296] The RAN Computing Slicing Allocation / Change / Delete Request message may include computing resource information required for RAN computing services. For example, the computing resource information required for RAN computing services may indicate a percentage indicator based on the computational capacity of a single reference CPU.

[0297] 3) Preferred computing type

[0298] The preferred type of computing resource may vary depending on the service. For example, AI-related service computing may benefit from processing by a Neural Processing Unit (NPU), video streaming services like XR may benefit from processing by a Graphics Processing Unit (GPU), and general services like virtual devices may benefit from processing by a Central Processing Unit (CPU).

[0299] 4) Requested service function

[0300] The RAN Computing Slicing Allocation / Change / Deletion Request message may include information querying the availability of service functions required for RAN computing services. For example, the information querying the availability of service functions required for RAN computing services may include information such as the name of the service function and the manufacturer's name.

[0301] Next, the open cloud can allocate virtual resources (O-CU-ComP virtual resources) for the RAN computing module and, when the virtual resources are ready, can notify the base station (O-CU-CP) of this (S2050). That is, the open cloud allocates O-CU-Comp virtual resources based on the request received in step S2040 and allows the O-CU-CP to know about the prepared resources. As an example, information regarding whether the virtual resource allocation is ready can be transmitted to the O-CU-CP via the SMO. As another example, information regarding whether the virtual resource allocation is ready can be transmitted to the O-CU-CP via the C1-c interface. Information regarding whether the virtual resource allocation is ready can include at least one of computing resource status information, computing type information, or computing type status information.

[0302] Next, the base station determines available resources based on steps S2020 to S2050 and transmits a Slice Resource Status Response message to 5GC (S2060). The Slice Resource Status Response message is an NG-C control plane message and may include at least one of the following pieces of information:

[0303] 1) Available NSSAI

[0304] The slicing resource status response message may include one or more slice ID information that is available according to the request message of step S2010. In this case, the slice information may include at least one of the following information elements.

[0305] - Information about the slice ID used in the S2010 phase (e.g. SST or SSST indicating RAN computing)

[0306] 2) Computing resource availability

[0307] The slicing resource status response message may include information about available computing resources for the RAN computing service. For example, the information about available computing resources for the RAN computing service may indicate a percentage indicator based on the computational capacity of a single reference CPU. As another example, the information about available computing resources for the RAN computing service may include an indication of "Yes" or "No." As another example, for multiple slices, multiple resource information may be configured to match the slice ID.

[0308] 3) Computing type

[0309] Depending on the service, the preferred type of computing resource may vary. For example, AI-related service computing may benefit from processing by a Neural Processing Unit (NPU), video streaming services like XR may benefit from processing by a Graphics Processing Unit (GPU), and general services like virtual devices may benefit from processing by a Central Processing Unit (CPU).

[0310] 4) Service function availability

[0311] The Slicing Resource Status Response message may include information indicating that a service function required (or possible) for a RAN computing service is ready. As an example, the information indicating that a service function required (or possible) for a RAN computing service is ready may include information such as the name of the service function and the manufacturer's name.

[0312] Next, the 5GC transmits a registration response message to the terminal via the base station based on the slicing resource status response message (S2070). The registration response message may ultimately indicate whether or not to allow the RAN computing slice. If the registration response message indicates that the RAN computing slice is allowed, the base station may provide RAN computing services to the terminal based on the protocol stack of the RAN computing module (e.g., FIG. 19).

[0313] The combination or combination of the embodiments and technical features described through FIGS. 1 to 20 are directly and unambiguously possible. Therefore, the various combinations or combinations are included in the embodiments proposed in the present specification. In addition, as described above, the embodiments of the present specification can be applied not only to O-RAN but also to various radio access networks (RANs). For example, the RRC, PDCP, RLC, MAC, and PHY layers can be subdivided into RRC, PDCP, High RLC, Low RLC, High MAC, Low MAC, High PHY, and Low PHY layers. Here, for example, the RRC and PDCP layers can be included in an O-RAN Central Unit (O-CU), the High RLC, Low RLC, High MAC, Low MAC, and High PHY layers can be included in an O-RAN Distributed Unit (O-DU), and the Low PHY (and RF) can be included in an O-RAN Radio Unit (O-RU). At this time, an open fronthaul interface may exist between the O-DU and O-RU, in which case a multi-vendor RAN model can be implemented. Alternatively, such an interface may not be applicable to the RAN. In this case, the embodiments of this specification can be implemented on existing RANs or RANs without such an interface, as long as they are not inter-coordinated.

[0314] FIG. 21 is a diagram illustrating a communication device according to some embodiments of the present specification.

[0315] Referring to FIG. 21, a communication device (1700) may include a memory (1710) and a processor (1720). The memory (1710) and the processor (1720) may communicate with each other via a bus (1730).

[0316] The memory (1710) may contain computer-readable instructions. The processor (1720) may perform the aforementioned operations as the instructions stored in the memory (1710) are executed by the processor (1720). The memory (1710) may be volatile memory or non-volatile memory.

[0317] The processor (1720) may execute instructions or programs, or control the communication device (1700). The communication device (1700) may be implemented as part of various computing devices. In addition, the communication device (1700) may process the operations described above.

[0318] For example, when a UE registers, the processor (1720) may receive a registration request from a user terminal, select a network slice instance to be assigned to the user terminal from among multiple network slice instances within the communication device based on the registration request, and transmit a registration approval message to the user terminal in response to the selection of the network slice instance. Here, the network slice instance may be an instantiated form of a network slice that includes one or more network functions and resources for providing a network service with certain performance and characteristics to the user terminal.

[0319] As another example, when establishing a PDU session, the processor (1720) may receive a PDU session establishment request from a user terminal, select a network slice instance to be allocated to the user terminal from among a plurality of network slice instances (NSIs; Network Slice Instances) within the communication device based on the PDU session establishment request, and select a network function instance to be allocated to the user terminal from among a plurality of network function instances included in the selected network slice instance. Here, the network slice instance may be an instantiated form of a network slice including one or more network functions and resources for providing a network service with certain performance and characteristics to the user terminal.

[0320] Below, an example of a communication system to which the present invention is applied is described.

[0321] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods and / or operational flowcharts of the present invention disclosed in this document may be applied to various fields requiring wireless communication / connection (e.g., 5G) between devices.

[0322] Hereinafter, more specific examples will be provided with reference to the drawings. In the drawings / descriptions below, the same drawing reference numerals may represent identical or corresponding hardware blocks, software blocks, or functional blocks, unless otherwise described.

[0323] Figure 22 illustrates a communication system (1) applied to the present invention.

[0324] Referring to FIG. 22, a communication system (1) applied to the present invention includes a wireless device, a base station, and a network. Here, the wireless device refers to a device that performs communication using a wireless access technology (e.g., 5G NR (New RAT), LTE (Long Term Evolution)) and may be referred to as a communication / wireless / 5G device. Although not limited thereto, the wireless device may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (eXtended Reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Things) device (100f), and an AI device / server (400). For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of performing vehicle-to-vehicle communication, etc. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone). XR devices include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices, and can be implemented in the form of HMD (Head-Mounted Device), HUD (Head-Up Display) installed in a vehicle, television, smartphone, computer, wearable device, home appliance, digital signage, vehicle, robot, etc. Mobile devices can include smartphone, smart pad, wearable device (e.g., smart watch, smart glass), computer (e.g., laptop, etc.), etc. Home appliances can include TV, refrigerator, washing machine, etc. IoT devices can include sensors, smart meters, etc. For example, base stations and networks can also be implemented as wireless devices, and a specific wireless device (200a) can act as a base station / network node to other wireless devices.

[0325] Here, the wireless communication technology implemented in the wireless device of the present specification may include not only LTE, NR, and 6G, but also Narrowband Internet of Things for low-power communication. At this time, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, and may be implemented with standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device of the present specification may perform communication based on LTE-M technology. At this time, for example, LTE-M technology may be an example of LPWAN technology, and may be called by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology can be implemented by 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 Machine Type Communication, and / or 7) LTE M, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device of the present specification can include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low-power communication, and is not limited to the above-described names. 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 can be called by various names.

[0326] Wireless devices (100a to 100f) can be connected to a network (300) via a base station (200). Artificial Intelligence (AI) technology can be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) via 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, etc. The wireless devices (100a to 100f) can communicate with each other via the base station (200) / network (300), but can also communicate directly (e.g., sidelink communication) without going through the base station / network. For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to Everything) communication). In addition, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

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

[0328] Figure 23 illustrates a wireless device applicable to the present invention.

[0329] Referring to FIG. 23, the first wireless device (100) and the second wireless device (200) can transmit and receive wireless signals through various wireless access technologies (e.g., LTE, NR). Here, {the first wireless device (100), the second wireless device (200)} can correspond to {the wireless device (100x), the base station (200)} and / or {the wireless device (100x), the wireless device (100x)} of FIG. 22.

[0330] A first wireless device (100) includes one or more processors (102) and one or more memories (104), and may further include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memories (104) and / or the transceivers (106), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein. For example, the processor (102) may process information in the memory (104) to generate first information / signals, and then transmit a wireless signal including the first information / signals via the transceivers (106). Furthermore, the processor (102) may receive a wireless signal including second information / signals via the transceivers (106), and then store information obtained from signal processing of the second information / signals in the memory (104). The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may perform some or all of the processes controlled by the processor (102), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals via one or more antennas (108). The transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit. In the present invention, a wireless device may also mean a communication modem / circuit / chip.

[0331] The second wireless device (200) includes one or more processors (202), one or more memories (204), and may further include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memories (204) and / or the transceivers (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein. For example, the processor (202) may process information in the memory (204) to generate third information / signals, and then transmit a wireless signal including the third information / signals via the transceivers (206). In addition, the processor (202) may receive a wireless signal including fourth information / signals via the transceivers (206), and then store information obtained from signal processing of the fourth information / signals in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may perform some or all of the processes controlled by the processor (202), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed herein. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF unit. In the present invention, a wireless device may also mean a communication modem / circuit / chip.

[0332] Hereinafter, the 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 PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed herein, and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) can receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein.

[0333] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, 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), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts invented in this document may be implemented using firmware or software configured to perform one or more processors (102, 202) or stored in one or more memories (104, 204) and driven by one or more processors (102, 202). The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts invented in this document may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions.

[0334] One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be configured as ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0335] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or flowcharts of this document, to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts of this document, from one or more other devices. For example, one or more transceivers (106, 206) can be connected to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be coupled to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, or the like, as referred to in the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts of the present document, via one or more antennas (108, 208). In the present document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). 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 the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202).One or more transceivers (106, 206) may convert user data, control information, wireless signals / channels, etc. processed by one or more processors (102, 202) from baseband signals to RF band signals. For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or filter.

[0336] Figure 24 illustrates a process for generating a transmission signal in a transmitter.

[0337] Referring to FIG. 24, the signal processing circuit (1000) may include a scrambler (1010), a modulator (1020), a layer mapper (1030), a precoder (1040), a resource mapper (1050), and a signal generator (1060). Although not limited thereto, the operations / functions of FIG. 24 may be performed in the processor (102, 202) and / or the transceiver (106, 206) of FIG. 23. The hardware elements of FIG. 24 may be implemented in the processor (102, 202) and / or the transceiver (106, 206) of FIG. 23. For example, blocks 1010 to 1060 may be implemented in the processor (102, 202) of FIG. 19. Additionally, blocks 1010 to 1050 may be implemented in the processor (102, 202) of FIG. 23, and block 1060 may be implemented in the transceiver (106, 206) of FIG. 23.

[0338] The codeword can be converted into a wireless signal through the signal processing circuit (1000) of FIG. 24. Here, the codeword is an encoded bit sequence of an information block. The information block may include a transport block (e.g., an UL-SCH transport block, a DL-SCH transport block). The wireless signal may be transmitted through various physical channels (e.g., a PUSCH or a PDSCH).

[0339] Specifically, the codeword can be converted into a bit sequence scrambled by a scrambler (1010). The scramble sequence used for scrambling is generated based on an initialization value, and the initialization value may include ID information of the wireless device, etc. The scrambled bit sequence can be modulated into a modulation symbol sequence by a modulator (1020). The modulation method may include pi / 2-BPSK (pi / 2-Binary Phase Shift Keying), m-PSK (m-Phase Shift Keying), m-QAM (m-Quadrature Amplitude Modulation), etc. The complex modulation symbol sequence can be mapped to one or more transmission layers by a layer mapper (1030). The modulation symbols of each transmission layer can be mapped to the corresponding antenna port(s) by a precoder (1040) (precoding). The output z of the precoder (1040) can be obtained by multiplying the output y of the layer mapper (1030) by a precoding matrix W of N*M. Here, N is the number of antenna ports, and M is the number of transmission layers. Here, the precoder (1040) can perform precoding after performing transform precoding (e.g., DFT transform) on complex modulation symbols. In addition, the precoder (1040) can perform precoding without performing transform precoding.

[0340] The resource mapper (1050) can map modulation symbols of each antenna port to time-frequency resources. The time-frequency resources can include multiple symbols (e.g., CP-OFDM symbols, DFT-s-OFDM symbols) in the time domain and multiple subcarriers in the frequency domain. The signal generator (1060) generates a wireless signal from the mapped modulation symbols, and the generated wireless signal can be transmitted to another device through each antenna. To this end, the signal generator (1060) can include an Inverse Fast Fourier Transform (IFFT) module, a Cyclic Prefix (CP) inserter, a Digital-to-Analog Converter (DAC), a frequency uplink converter, etc.

[0341] The signal processing process for receiving signals in a wireless device can be configured in reverse order of the signal processing process (1010 to 1060) of FIG. 24. For example, a wireless device (e.g., 100, 200 of FIG. 23) can receive wireless signals from the outside through an antenna port / transceiver. The received wireless signals can be converted into baseband signals through a signal restorer. For this purpose, the signal restorer can include a frequency downlink converter, an analog-to-digital converter (ADC), a CP remover, and a fast Fourier transform (FFT) module. Thereafter, the baseband signal can be restored to a codeword through a resource demapper process, a postcoding process, a demodulation process, and a descrambling process. The codewords can be restored to the original information blocks through decoding. Accordingly, a signal processing circuit (not shown) for a received signal may include a signal restorer, a resource de-mapper, a postcoder, a demodulator, a de-scrambler, and a decoder.

[0342] Figure 25 illustrates another example of a wireless device applicable to the present invention. The wireless device may be implemented in various forms depending on the use case / service.

[0343] Referring to FIG. 25, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 23 and may be composed of various elements, components, units, and / or modules. For example, the wireless device (100, 200) may include a communication unit (110), a control unit (120), a memory unit (130), and an additional element (140). The communication unit may include a communication circuit (112) and a transceiver(s) (114). For example, the communication circuit (112) may include one or more processors (102, 202) and / or one or more memories (104, 204) of FIG. 23. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 23. The control unit (120) is electrically connected to the communication unit (110), the memory unit (130), and the additional elements (140) and controls the overall operation of the wireless device. For example, the control unit (120) may control the electrical / mechanical operation of the wireless device based on the program / code / command / information stored in the memory unit (130). In addition, the control unit (120) may transmit information stored in the memory unit (130) to an external device (e.g., another communication device) via a wireless / wired interface through the communication unit (110), or store information received from an external device (e.g., another communication device) via a wireless / wired interface in the memory unit (130).

[0344] The additional element (140) may be configured in various ways depending on the type of the wireless device. For example, the additional element (140) may include at least one of a power unit / battery, an input / output (I / O) unit, a driving unit, and a computing unit. Although not limited thereto, the wireless device may be implemented in the form of a robot (Fig. 22, 100a), a vehicle (Fig. 22, 100b-1, 100b-2), an XR device (Fig. 22, 100c), a portable device (Fig. 22, 100d), a home appliance (Fig. 22, 100e), an IoT device (Fig. 22, 100f), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or a financial device), a security device, a climate / environmental device, an AI server / device (Fig. 22, 400), a base station (Fig. 22, 200), a network node, etc. Wireless devices may be mobile or stationary depending on the use / service.

[0345] In FIG. 25, various elements, components, units / parts, and / or modules within the wireless device (100, 200) may be entirely interconnected via a wired interface, or at least some may be wirelessly connected via a communication unit (110). For example, within the wireless device (100, 200), the control unit (120) and the communication unit (110) may be wired, and the control unit (120) and a first unit (e.g., 130, 140) may be wirelessly connected via the communication unit (110). In addition, each element, component, unit / part, and / or module within the wireless device (100, 200) may further include one or more elements. For example, the control unit (120) may be composed of a set of one or more processors. For example, the control unit (120) may be composed of a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing processor, a memory control processor, etc. As another example, the memory unit (130) may be composed of RAM (Random Access Memory), DRAM (Dynamic RAM), ROM (Read Only Memory), flash memory, volatile memory, non-volatile memory, and / or a combination thereof.

[0346] The methods proposed in this specification may also be performed by an apparatus configured to control the communication device, which comprises, in addition to the communication device, at least one computer-readable recording medium containing instructions based on being executed by at least one processor, and one or more processors and one or more memories executable by the one or more processors and storing the instructions, wherein the one or more processors execute the instructions to perform the methods proposed in this specification.

[0347] The claims set forth in this specification may be combined in various ways. For example, the technical features of the method claims of this specification may be combined and implemented as a device, and the technical features of the device claims of this specification may be combined and implemented as a method. Furthermore, the technical features of the method claims and the technical features of the device claims of this specification may be combined and implemented as a device, and the technical features of the method claims and the technical features of the device claims of this specification may be combined and implemented as a method.

Claims

1. In a method used by a base station in a wireless communication system, Determine whether a base station computing network slice is configured; and Based on the above judgment, the base station computing network slice is configured, A method characterized in that the base station computing network slice is a network slice that provides a service in which data of at least one of an IP layer and an application layer is processed by the base station or an edge server connected to the base station.

2. In paragraph 1, The base station receives network slice request information from a terminal connected to the base station, A method characterized in that the base station determines whether to configure the base station computing network slice based on the network slice request information.

3. In paragraph 2, A method characterized in that the above network slice request information includes an identifier for the base station computing network slice.

4. In paragraph 2, A method characterized in that the above network slice request information is transmitted via an AS (Access Stratum) message.

5. In paragraph 2, The base station transmits slice request information to 5GC based on the above judgment, A method characterized in that the slice request information includes information identifying the base station computing network slice.

6. In paragraph 1, A method characterized in that the base station determines whether to configure the base station computing network slice based on at least one of available computing resources, mobility of the terminal, and support for service applications.

7. In paragraph 1, The above base station receives availability request information from 5GC (5G Core), A method characterized in that the base station determines whether to configure the base station computing network slice based on the availability request information.

8. In paragraph 7, A method characterized in that the above availability request information includes at least one of information for identifying the requested base station computing network slice, information about the requested computing resource, and information about the requested service function.

9. In paragraph 7, A method characterized in that, in response to the availability request information, the base station transmits availability response information to the 5GC.

10. In paragraph 9, A method characterized in that the availability response information includes at least one of information on the presence or absence of available computing resources of the base station, information identifying one or more available slices, and information on the availability of computing resources.

11. The base station; One or more memories that store instructions; one or more transmitters and receivers; and One or more processors connecting the one or more memories and the one or more transceivers, wherein the one or more processors execute the instructions, Determine whether a base station computing network slice is configured; and Based on the above judgment, the base station computing network slice is configured, A device characterized in that the base station computing network slice is a network slice that provides a service in which data of at least one of the IP layer and the application layer is processed by the base station or an edge server connected to the base station.

12. In paragraph 11, The base station receives network slice request information from a terminal connected to the base station, A device characterized in that the base station determines whether to configure the base station computing network slice based on the network slice request information.

13. In paragraph 12, A device characterized in that the above network slice request information includes an identifier for the base station computing network slice.

14. In paragraph 12, A device characterized in that the above network slice request information is transmitted via an AS (Access Stratum) message.

15. In paragraph 12, The base station transmits slice request information to 5GC based on the above judgment, A device characterized in that the slice request information includes information identifying the base station computing network slice.

16. In paragraph 11, A device characterized in that the base station determines whether to configure the base station computing network slice based on at least one of available computing resources, mobility of the terminal, and support for service applications.

17. In paragraph 11, The above base station receives availability request information from 5GC (5G Core), A device characterized in that the base station determines whether to configure the base station computing network slice based on the availability request information.

18. In paragraph 17, A device characterized in that the above availability request information includes at least one of information for identifying the requested base station computing network slice, information about the requested computing resource, and information about the requested service function.

19. In paragraph 17, A device characterized in that, in response to the availability request information, the base station transmits availability response information to the 5GC.

20. In paragraph 19, A device characterized in that the above availability response information includes at least one of information on the presence or absence of available computing resources of the base station, information identifying one or more available slices, and information on the availability of computing resources.

Images