Wireless access node apparatus and interface method performed by wireless access node apparatus

Abstract

This invention proposes a method for unified conversion of the functions of all devices (RAN and core) from 5G core to RAN by implementing specific technologies to evolve the functions of RAN devices into a 5G architecture and implement functions for NF communication.

Description

Technical Field

[0001] This disclosure relates to Radio Access Network (RAN) technology.

[0002] This application is based on and claims priority to Korean Patent Application No. 10-2020-0135271, filed with the Korean Intellectual Property Office on October 19, 2020, the disclosure of which is incorporated herein by reference in its entirety. Background Technology

[0003] 5G defines a network architecture for supporting user equipment (UE), base stations (access), core and servers in an end-to-end manner.

[0004] Furthermore, 5G defines a network architecture that separates the control plane for control signaling functions and the user plane for data transmission / reception functions by separating the control signaling functions and data transmission / reception functions that have been complexly performed by individual nodes (e.g., S-GW, P-GW, etc.) in traditional LTE (4G).

[0005] In this context, the control node of the control plane (CP) in 5G can be defined as follows: Access and Mobility Management Function (AMF) that controls the radio part of user equipment (UE); Policy Control Function (PCF) that manages and controls policies such as subscription service information and payments for each UE and UE information; Session Management Function (SMF) that controls / manages sessions for using data services for each UE; Network Open Function (NEF) that is responsible for sharing information with external networks; Unified Data Management / Authentication Function (UDM / AUSF) that manages / controls user subscriber databases and authentication; Network Repository Function (NRF) that performs management / control of information associated with each network function (NF) in the network; and Billing Function (CHF) that processes subscriber payments.

[0006] In 5G, a data node in the user plane (UP) can be defined as a user plane function (UPF), which performs data transmission or reception between the UE and a server in an external service network (e.g., the Internet) via a session with the UE, based on the control of the SMF (interoperable with the SMF).

[0007] The 5G core can define NFs that perform predetermined functions, and NFs are defined to interoperate with each other using service-based interfaces (SBIs).

[0008] The 5G core uses SBIs between NF services to perform communication, so the core NF can be installed, distributed, and upgraded very easily. Additionally, virtualization (VNF, CNF) can be configured, and system resources can be used efficiently.

[0009] In the case of radio access network (RAN) in 5G, the standard focuses on the radio communication of the RAN, so the RAN cannot evolve into the new 5G architecture and still uses legacy interfaces (e.g., N2, etc.).

[0010] Based on the current level of 5G technology, the implementation of evolution to 5G architecture and NF is only enabled in the core, but the implementation of evolution to 5G architecture and NF has not yet been applied in RAN.

[0011] Therefore, this disclosure proposes a detailed technique that allows the functionality of RAN equipment to evolve to a 5G architecture and be implemented as NF, so as to unify the functionality of all equipment (RAN, core) including RAN and 5G core as NF. Summary of the Invention

[0012] Technical issues

[0013] This disclosure presents a detailed technique that allows the functionality of RAN equipment to evolve to a 5G architecture and be implemented as NF, so as to unify the functionality of all equipment (RAN, core) including RAN and 5G core as NF.

[0014] Technical solution

[0015] The radio access node apparatus according to embodiments of the present disclosure can be configured as a service-based architecture (SBA) that performs communication using messages via a service-based interface (SBI) between network functions (NFs).

[0016] A radio access node apparatus according to an embodiment of the present disclosure may include: an NF communication unit configured to perform necessary communications associated with providing services to an accessed user equipment (UE), and the NF communication unit may perform communications using SBI messages via an inter-NF service-based interface (SBI).

[0017] Specifically, the NF that communicates with the NF communication unit is at least one of the following: NF service in another node device that forms a base station with the radio access node device, another radio access node device, another radio access node device, the control plane NF, and the user plane NF.

[0018] Specifically, the NF communication unit may include an SBI module that processes SBI messages.

[0019] Specifically, the SBI module can be configured to operate according to at least one of a request / response based message sending or receiving scheme and a subscription / notification based message sending or receiving scheme.

[0020] Specifically, the SBI module can be configured to perform a conversion between messages sent via another interface and SBI messages sent via SBI when performing message sending or receiving.

[0021] Specifically, the NF communication unit can be configured to use SBI messages when sending or receiving messages related to the radio part handover of the UE.

[0022] Specifically, the NF communication unit can be configured to use SBI messages when a notification is sent upon detection of a specific event pre-subscribed (or subscribed) by the Access and Mobility Management Function (AMF).

[0023] Specifically, the NF communication unit can be configured to use SBI messages when sending or receiving messages related to the UE context associated with the UE.

[0024] Specifically, the NF communication unit can be configured to communicate directly with the Session Management Function (SMF) that manages / controls the UE session without going through the Access and Mobility Management Function (AMF) when processing the UE's session management, using SBI messages.

[0025] Specifically, the NF communication unit can be configured to communicate directly with the Policy Control Function (PCF), which manages and controls multiple policies (including QoS policies), without going through the Access and Mobility Management Function (AMF), when performing processing related to the UE's quality of service (QoS policy).

[0026] Specifically, the NF communication unit can be configured to perform direct communication without going through the Access and Mobility Management Function (AMF) by using SBI messages when processing the registration of the NF of the radio access node device to the Network Repository Function (NRF), wherein the NRF manages / controls information associated with each NF in the network.

[0027] An interface method performed by a radio access node device according to one embodiment of the present disclosure may include performing communication operations related to the provision of services to an accessed user equipment (UE), and the communication operations may be performed using SBI messages via an inter-NF service-based interface (SBI).

[0028] Beneficial effects

[0029] According to one embodiment of the present disclosure, a radio access node apparatus and an interface method performed by the apparatus allow the functionality of RAN equipment to evolve to a 5G architecture and be implemented as NF. Detailed techniques enable the unified implementation of the functionality of all equipment (RAN, core) including RAN and 5G core as NF. Attached Figure Description

[0030] Figure 1 This is a diagram illustrating the structure of a 5G system.

[0031] Figure 2 and Figure 3 This is a diagram illustrating the concept of configuring the RAN device as an SBA in this disclosure.

[0032] Figure 4 This diagram illustrates one implementation of the RAN device functionality as an NF in this disclosure.

[0033] Figure 5 This is a block diagram illustrating the configuration of a radio access node (RANF) device according to one embodiment of the present disclosure.

[0034] Figure 6 This is a diagram illustrating the process of processing SBI messages in a Radio Access Node (RANF) device according to one embodiment of the present disclosure.

[0035] Figure 7 This is a diagram illustrating an example of an SBI message used by a Radio Access Node (RANF) according to one embodiment of this disclosure.

[0036] Figure 8 This is a diagram illustrating an example of an SBI message value managed by a Radio Access Node (RANF) according to one embodiment of this disclosure.

[0037] Figures 9 to 12 This is a flowchart illustrating a communication scenario based on an interface method performed by a radio access node device (RANF) according to one embodiment of the present disclosure. Detailed Implementation

[0038] In the following description, embodiments of the present disclosure are illustrated with reference to the accompanying drawings.

[0039] This disclosure relates to a technique for implementing the functions of RAN devices as network functions (NF) so as to unify the implementation of the functions of all devices (RAN, core) as NF.

[0040] In 5G, the network architecture is defined as supporting user equipment (UE), base stations (access), core, and servers in an end-to-end manner.

[0041] In addition, in 5G, the network architecture is defined as a structure that separates the control signaling functions (control plane) and the data transmission / reception functions (user plane) by separating the control signaling functions and data transmission / reception functions that are complexly performed by individual nodes (e.g., S-GW, P-GW, etc.) in traditional LTE (4G).

[0042] In this context, the control node of the control plane (CP) in 5G can be defined as follows: Access and Mobility Management Function (AMF) that controls the radio part of user equipment (UE); Policy Control Function (PCF) that manages and controls policies such as subscription service information and payments for each UE and UE information; Session Management Function (SMF) that controls / manages sessions for using data services for each UE; Network Open Function (NEF) that is responsible for sharing information with external networks; Unified Data Management / Authentication Function (UDM / AUSF) that manages / controls user subscriber databases and authentication; Network Repository Function (NRF) that performs management / control of information associated with each network function (NF) in the network; and Billing Function (CHF) that processes subscriber payments.

[0043] In 5G, a data node in the user plane (UP) can be defined as a user plane function (UPF), which performs data transmission or reception between the UE and a server in an external service network (e.g., the Internet) via a session with the UE, based on the control of the SMF (interoperable with the SMF).

[0044] In addition, a new Service Communication Proxy (SCP) is defined in 5G to facilitate the handling of various inter-NF service communications via a mesh structure. The NFs are usually referred to as the control nodes of the CP (AMF, PCF, SMF, etc.) and the control nodes of the UP (UPF) as described above. The Service Communication Proxy (SCP) uses a service-based interface (SBI) to perform communication.

[0045] Therefore, in 5G, when SCP is introduced, communication based on SBI messages can be established between NFs via SCP. SBI messages are messages provided in a common shape / structure.

[0046] The 5G core can define Functional Levels (NFs) that perform predetermined functions, and these NFs are defined to interoperate with each other using Service-Based Interfaces (SBIs). Therefore, the 5G core uses SBIs between NF services to perform communication, allowing the core NFs to be easily installed, distributed, and upgraded, configured with virtualization (VNFs, CNFs), and efficiently utilizing system resources.

[0047] In the case of radio access network (RAN) in 5G, the standard focuses on the radio communication of the RAN, so the RAN cannot evolve into the new 5G architecture and still uses legacy interfaces (e.g., N2, etc.).

[0048] Therefore, in current 5G systems, RAN equipment such as CU, DU, and RU remains functionally intensive and very costly from a price / TCO perspective. Decomposition may be limited due to the need to modify default legacy interfaces. Because of these drawbacks, it will be difficult to meet the high quality of service requirements of customers in future 5G SA or 6G communication environments.

[0049] Based on the current level of 5G technology, the implementation of evolution to 5G architecture and NF is only implemented in the core, but the implementation of evolution to 5G architecture and NF has not yet been applied in the RAN.

[0050] Therefore, this disclosure proposes a detailed technology that allows the functionality of RAN devices to evolve to the 5G architecture and be implemented as NF, thereby unifying the functionality of all devices (RAN, core) including RAN and 5G core as NF.

[0051] In other words, the subject of this disclosure is to implement the functionality of RAN devices as NF and configure the same service-based architecture (SBA).

[0052] Therefore, this disclosure proposes a radio access network node device (Radio Access Network Function (RANF)) that implements / deploys the functions of a RAN device as an NF.

[0053] Therefore, the Radio Access Node (RANF) device proposed in this disclosure is characterized as a service-based architecture (SBA) that performs communication using messages via the service-based interface (SBI) between network functions (NFs).

[0054] In this context, the radio access node device (RANF) implemented as NF and configured as SBA in this disclosure may correspond to each RAN device (e.g., CU, DU, RU, etc.) included in a 5G base station (gNB), and may correspond to a portion of the RAN devices (e.g., CU, DU, RU, etc.).

[0055] In other words, RANF in this disclosure can be CU-CP, CU_UP, DU_high, DU_low, etc.

[0056] Therefore, RAN devices implemented as RANFs (e.g., CU, DU, RU, etc.) can implement the functions (features) provided by the device into the SBI of each NF service unit, and can contain an SBI module responsible for such processing (described later).

[0057] Therefore, as Figure 2 As shown, a RANF implemented as an NF and configured as an SBA according to this disclosure can be implemented via SBI messages in the same way as the core NF of the control node (AMF, SMF, CHF, etc.) commonly referred to as CP and the control node (UPF) of UP, and can even communicate directly with another NF (e.g., SMF, CHF, etc.) (e.g., when a service mesh-based SCP is introduced).

[0058] Therefore, according to this disclosure, the RANF can perform direct communication with another core NF (e.g., SMF, CHF, etc.), thereby making the interworking AMF lightweight. Furthermore, various performance improvements can be made (e.g., processes can be simplified by separating session management and mobility management, changes in NF information can be immediately identified, and telecom company networks can be configured to provide seamless service even in the case of RM by enhancing the stateless 5G characteristics).

[0059] In the following description, for ease of description, a detailed description will be provided with reference to an implementation of a RAN device (e.g., CU, DU, RU, etc.) that can be implemented as a RANF and performs short-range communication with the core network (e.g., AMF).

[0060] Figure 3 This is a diagram illustrating the concept of configuring a CU, which is used as an example of a RAN device, as an SBA.

[0061] like Figure 3 As shown in this disclosure, a CU (CU-CP / CU-UP) based on CP / UP classification can be configured as an SBA to perform communication using SBI messages.

[0062] In this manner, the CU-CP configured as SBA according to this disclosure can communicate directly with the AMF and other NFs such as SMF, CHF, etc. (including the CU-UP configured as SBA) via SBI messages (protocol), and the CU-UP configured as SBA according to this disclosure can communicate directly with other NFs such as UPF (including the CU-CP configured as SBA) via SBI messages (protocol).

[0063] In this case, such as Figure 3 As described, RAN devices (e.g., CU, DU, RU, etc.) that are implemented as RANF and configured as SBA can indicate SBI messages (protocols) (e.g., Nran in the case of CU-CP, Ncu in the case of CU-UP, etc.) via API-based unit classification "Nxxx" (here, xxx = NF) based on NF services provided by the device and implemented as SBI.

[0064] In the following description, reference is made to an implementation of the CU-CP that first communicates with the core network (e.g., AMF) in a RAN device (e.g., CU, DU, RU, etc.) that can be implemented as a RANF.

[0065] That is to say, in the following text, such as Figure 4 As shown in the description provided below, the CU-CP configured as SBA according to this disclosure is referred to as RANF (or CU-CP NF).

[0066] exist Figure 4 In the embodiments shown, the RANF (or CU-CP NF) can communicate directly with the core NF using Nran (SBI message), and the CU-UP not configured as RANF according to this disclosure can communicate with the RANF (or CU-CP NF) and UPF via conventional interfaces (E1, N3, etc.).

[0067] Figure 5 This is a diagram illustrating the configuration of a radio access node device (RANF) that implements the functions of a RAN device as an NF according to this disclosure.

[0068] As described above, the RANF in this disclosure can be CU-CP, CU_UP, DU_high, DU_low, RU, etc. However, for ease of description, detailed implementations will be described with reference to the CU-CP, which first communicates with the core network (e.g., AMF).

[0069] like Figure 5As shown, according to one embodiment of this disclosure, RANF 100 (e.g., CU-CP NF) may be a function of a RAN device implemented as an NF, which provides services to accessed user equipment (UE).

[0070] The RANF 100 of this disclosure (e.g., CU-CP NF) may include an NF communication unit 110, which performs the communication required by the NF in connection with providing services to the UE.

[0071] Here, the NF communication unit 110 can perform communication using SBI messages via the service-based interface (SBI) between NFs.

[0072] The NF communication unit 110 may include an SBI module for processing SBI messages.

[0073] In other words, the RANF 100 of this disclosure (e.g., CU-CP-NF) may include an NF communication unit 110 (specifically, an SBI module that performs communication with the NF by using SBI messages), and may be configured as SBA by implementing the functionality of the RAN device (CU-CP) as an NF.

[0074] In this case, the NF communicating with the NF communication unit 110 (specifically, the SBI module) can be at least one of the following: another node device (e.g., a CU-UP, DU_high, DU_low, or RU configured as SBA) configured for the same base station (gNB) for which the RANF 100 (e.g., a CU-CP NF) is configured; another radio access node device (e.g., another CU-CP NF); another radio access node device (e.g., another CU-CP NF); NF services in the CP (e.g., AMF, SMF, PCF, etc.); and NFs in the UP (e.g., UPF).

[0075] The SBI module included / prepared in the RANF 100 of this disclosure (e.g., CU-CP NF) can operate on at least one of a request / response based message sending or receiving scheme and a subscription / notification based message sending or receiving scheme.

[0076] Specifically, the SBI module included / prepared in the RANF 100 of this disclosure (e.g., CU-CP NF) may be a message interface associated with the processing (procedure) of each NF service corresponding to the function (feature) of the CU-CP implemented in the SBI of each NF service unit.

[0077] The SBI module can be an interface that handles the receive (input, receive, enter) / send (output, send, exit) processes associated with the processing (disposal) of each NF service.

[0078] Such an SBI module can operate as a messaging interface associated with requests / responses and subscriptions / notifications.

[0079] Furthermore, when performing message sending or receiving, the SBI module included / prepared in the RANF 100 of this disclosure (e.g., CU-CP NF) can convert between messages via another interface and SBI messages via the SBI.

[0080] In other words, the SBI module included / prepared in the RANF 100 of this disclosure (e.g., CU-CP NF) can process / convert received (input, receive, enter) conventional protocols (e.g., GTP-C, GTPP, SCTP, etc.) and can send (output, transmit, exit) the same protocol as SBI messages (SBI protocol), and can process / convert received (input, receive, enter) SBI messages (SBI protocol) and can send (output, transmit, exit) the same protocol as conventional protocols (e.g., GTP-C, GTPP, SCTP).

[0081] According to one implementation, the SBI module included / prepared in the RANF 100 (e.g., CU-CP NF) of this disclosure can convert legacy messages of RAN devices (e.g., CU-UP) into SBIs for RAN NF inter-service communication (or RANF inter-service communication), and this conversion function can be internalized as a process, or legacy messages can be converted into SBIs.

[0082] As described above, based on the SBI module, the RANF 100 of this disclosure (e.g., CU-CP NF) can perform direct communication between each NF service (inter-RAN, intra-RAN, RAN core) corresponding to the CU-CP function (feature) implemented as SBI (when using a service mesh-based SCP).

[0083] In the following text, reference will be made to Figure 6 This describes the process of processing SBI messages in RANF 100 (e.g., CU NF) of this disclosure.

[0084] like Figure 6 As shown, the RANF 100 of this disclosure (e.g., CU NF) (specifically, which includes / prepares an SBI module) can essentially perform receive (input, receive, enter) / process (dispose) / transmit (output, transmit, exit).

[0085] Here, the message (SBI Msg.) that the SBI module interacts with can be a data packet that includes application layer headers such as HTTP, HTTP / 2, and QUIC defined in the SBI.

[0086] The messages exchanged by the SBI module can be understood as "data," "packets," "payloads," "content," and "header information." Additionally, the types of headers included in the messages can include GTP-C, GTP-U, TCP, IP, and version information.

[0087] Additionally, the header information in a message can include source address, destination address, port number, etc., to enable sending / receiving. Furthermore, multiple (N) headers corresponding to a single header can be included in a message.

[0088] As described above, the header of the message that interfaces with the SBI module of this disclosure may include information for identifying the type of data and for identifying the actual content of the data, how the data is processed, etc.

[0089] Therefore, the NF receiving the message can identify the data based on the message header and know how to process the data.

[0090] In this case, such as Figure 6 As shown, messages managed by RANF 100 (e.g., CU NF) can be classified as CP messages and UP messages in the same way that CU NF is classified as CU-CP NF and CU-UP NF, as shown below.

[0091] CPP: Control Plane Grouping (including header information)

[0092] UPP: User Plane Packet (including header information)

[0093] Therefore, specifically, the SBI module included / prepared in the RANF 100 (e.g., CU NF) of this disclosure knows how to classify the payload of each type of RANF based on the header in the message when performing reception (input, receive, enter).

[0094] For example, upon receiving a pre-defined CPP, RANF 100 (e.g., CU NF) (specifically, the SBI module) can perform a process of interpreting / classifying the message and forwarding it to the appropriate processing (disposal) resource. In this case, the SBI module can perform decapsulation, etc., on the header.

[0095] When performing processing (disposal), the RANF 100 of this disclosure (e.g., CU NF) (specifically, containing / prepared SBI modules) can process the payload of each type of RANF based on the message header and the message content. The processing scheme is the same as the operation defined in the standard, therefore its detailed description is omitted.

[0096] In the case of performing transmission (output, transmission, de-output), the RANF 100 of this disclosure (e.g., CU NF) (specifically, the included / prepared SBI module) can perform processing (disposal) for each type of RANF and can determine the NF to which the processing is to be performed. As described above, generally, CP NFs (including CU-CP NFs) can perform transmission / transmission for CP NFs, and UP NFs (CU-UP NFs) can perform transmission / transmission for UP NFs.

[0097] In this scenario, the SBI module can input the destination address into the header to execute message sending, and can also additionally generate and correct the header before performing encapsulation / decapsulation.

[0098] The RANF 100 of this disclosure (e.g., CU NF) (specifically, including / prepared with an SBI module) can classify received (input, receive, incoming) messages, perform basic header processing (encapsulation / decapsulation) on messages (data packets), and perform CP or UP functions (actual processing) based on the header-processed packets. When the DU / CU NF corresponding to the DU / CU is configured as a single SBA, the single SBA can have the capability to commonly handle CP and UP (common plane I / F).

[0099] Furthermore, the RANF 100 of this disclosure (e.g., CU NF) (specifically, which contains / prepares an SBI module) can, depending on the state and progress of the RANF, directly forward messages (data packets) to another NF when needed.

[0100] Figure 7 This is a diagram illustrating an example of an SBI message defined by the RANF of this disclosure (specifically, the RANF (CU-CP NF) that implements the function of the CU-CP that first communicates with the core network (e.g., AMF) as described above).

[0101] In this disclosure, the SBI message (protocol) of each NF service unit can be defined according to the function / role of the RAN device itself implemented as a RANF (e.g., Nran, Ncu, Ncucp, Ndu, Nduhigh, Ndulow, etc.).

[0102] Therefore, the SBI messages used by the RANF (CU-CP NF) that implements the CU-CP functionality (e.g., the service name used to communicate with the AMF) can be configured as follows: Figure 7 The example is shown in the table.

[0103] In other words, SBI messages used by RANF (CU-CP NF) (e.g., service names used to communicate with AMF) can be classified into the following four types:

[0104] Nran_PDUSession: PDU session association processing

[0105] Nran_UEContext: Management of UE management information

[0106] Nran_UEMobility: Management of UE mobility

[0107] Nran_EventExposure: Subscriber / Notifications configured for the RAN

[0108] For reference, message names and types can be categorized primarily based on "service names," and further categorized based on the service operations for each service name.

[0109] Each service operation is a type of message exchanged between NFs, and can basically include create / update / delete / subscribe / unsubscribe, etc.

[0110] Each service operation can be organized based on various attribute names (for example, SMF can be organized based on SUPI, S-NSSAI, DNN, etc.).

[0111] The processing (disposal) logic for each RANF can vary depending on the functionality and characteristics of the implemented RAN device (e.g., CU, DU, RU, etc.).

[0112] For example, each NF including AMF can be classified based on four types of service names, associated service operations, associated attribute names, etc., and the corresponding NF (e.g., AMF) can perform operations based on them.

[0113] In other words, the processing (disposal) for each RANF can determine whether to execute a call processing procedure, or which call processing procedure to execute, based on the service name, service operation, and attribute name, and can determine whether to process the scheduled service and message (yes / no) based on its own loading status (e.g., CPU load, memory utilization, etc.).

[0114] Figure 8This is a diagram illustrating an example of an SBI message value managed by a Radio Access Node (RANF) according to one embodiment of this disclosure.

[0115] In other words, it can be a table that defines SBI message values ​​managed by an SBI module included / prepared in RANF 100 (e.g., CU NF) of this disclosure.

[0116] like Figure 8 As shown, the message address and message attribute value can be matched for each process (disposal) (e.g., process ID) performed by the SBI module.

[0117] In other words, when an SBI message (i.e., a data group) is input, the SBI module can extract the relevant content, allocate it to the resource mapped to each process (process ID), and process it.

[0118] For reference, the message address can be based on a minimum 5-tuple stream ID value, and the message attribute can be based on a minimum 3-tuple attribute ID. For reference, the tuple can also be a wildcard*. Furthermore, such N-tuple-based IDs can be managed essentially as a single integrated ID via hashing.

[0119] The following describes an implementation of the RANF 100 of this disclosure (e.g., CU-CP NF) using SBI messages to perform communication.

[0120] According to one implementation, the NF communication unit 110 (SBI module) can use SBI messages when sending or receiving messages related to radio part handover of the UE.

[0121] In other words, the RANF 100 of this disclosure (e.g., CU-CP NF) can even use SBI messages (e.g., Xn H / O -> Nxn H / O SBI message) in operations between RANFs (e.g., Xn H / O -> Nxn H / O).

[0122] According to another embodiment, the NF communication unit 110 (SBI module) can use SBI messages to send a notification when it detects a pre-subscribed (reserved) scheduled event by the AMF.

[0123] In other words, in this disclosure, other NFs, including AMF, subscribe to (reserve) the RANF 100 of this disclosure (e.g., CU-CP NF) and can receive immediate notifications when a reserved RAN (e.g., RAN instance, RAN set, etc.) or an event associated with a reserved RB (e.g., information, load, value higher than or equal to / less than or equal to a threshold, H / O, reserved subscriber, area, etc.) is detected.

[0124] According to another embodiment, the NF communication unit 110 (SBI module) can use SBI messages when sending or receiving messages related to the UE context associated with the UE.

[0125] In other words, even when communicating with the AMF associated with the UE context, the RANF 100 of this disclosure (e.g., CU-CP NF) can use SBI messages to perform communication.

[0126] According to another embodiment, in the case of handling UE session management, the NF communication unit 110 (e.g., SBI module) can communicate directly with the SMF that manages / controls the UE session by using SBI messages without going through the AMF.

[0127] In other words, when performing PDU session control related processes (e.g., creation, update, deletion, etc.), the RANF 100 of this disclosure (e.g., CU-CP NF) can directly perform SBI communication with the SMF without going through the AMF.

[0128] According to another embodiment, when performing quality (QoS) policy-related processing on the UE, the NF communication unit 110 (e.g., the SBI module) can communicate directly with the PCF that manages / controls multiple policies including QoS policies by using SBI messages without going through the AMF.

[0129] In other words, when performing quality of service (QoS) related processing on the UE and when performing PDU session control processing (e.g., creation, update, deletion, etc.) on the UE, the RANF 100 of this disclosure (e.g., CU-CP NF) can directly perform SBI communication with the PCF without going through the AMF.

[0130] As described above, the PCF and SMF can also subscribe to the RANF 100 disclosed herein (e.g., CU-CP NF) and can immediately receive information associated with radio blocks (RBs) (e.g., QoS scheduling information, QoS priority, NW slice information, etc.) via notification upon detection of an event. In this case, direct communication from the RANF 100 (e.g., CU-CP NF) can be performed via the SBI without going through the AMF.

[0131] According to another implementation, when performing the registration of the NF of RANF 100 (e.g., CU-CP NF) to the NRF that manages / controls information associated with each NF in the network, the NF communication unit 110 (SBI module) can perform direct communication using SBI messages without going through the AMF.

[0132] In other words, the RANF 100 of this disclosure (e.g., CU-CP NF) can directly perform SBI communication with the PCF without going through the AMF when performing registration related to the NF of the RANF 100.

[0133] In addition to the above-described embodiments, the RANF 100 of this disclosure (e.g., CU-CP NF) can directly perform various types / categories of communication that are conventionally performed via AMF in order to communicate with the core NF, via SBI communication without going through AMF.

[0134] As described above, this disclosure defines / implements the SBI module in detail to allow the functionality of RAN devices to evolve to the 5G architecture and be implemented as NF, thereby unifying the functionality of all devices (RAN, core) including RAN and 5G core as NF.

[0135] Furthermore, in this disclosure, since the Radio Access Node (RANF) device containing / preparing the SBI module as described above is implemented, detailed communication between RAN instances and RAN sets can be freely performed, and from a standards perspective, the development, installation, and distribution of communication configurations (migration, pkg upgrades, duplication / multiplication) can be evolved very easily.

[0136] Furthermore, in this disclosure, due to the implementation of the Radio Access Node (RANF) device containing / embodying the SBI module as described above, inter-RAN and intra-RAN communication can be implemented significantly and efficiently, and can be accomplished as a cloud-native architecture. More freely, functions can be decomposed (fragmented), and services can be efficiently and rapidly prepared for each "function, feature, pkg, patch" in a container / VM virtualization environment.

[0137] In addition, in this disclosure, latency / performance-sensitive data processing schemes and signaling can also use SBIs suitable for Telco IT (e.g., new protocols for HTTP and HTTP / 2 schemes), and thus can further increase agility with flexibility, quickly improve functional qualifications and operational efficiency, and rapidly deliver new product services.

[0138] In the following text, refer to Figures 9 to 12This describes the interface methods performed by the RANF proposed in this disclosure.

[0139] As described above, the RANF proposed in this disclosure can directly perform various types / categories of communication that are normally performed via the AMF by using SBI communication without going through the AMF, so as to communicate with the core NF, can use SBI communication to communicate with the AMF, and can perform communication by applying SBI to inter-RAN communication, intra-RAN communication, etc.

[0140] In the following description, for ease of description, several implementations of various call flows that can be executed by the RANF of this disclosure via SBI are described.

[0141] First, refer to Figure 9 As one implementation of the call flow that the RANF can execute via SBI in this disclosure, a UE context-dependent call flow associated with communication with the AMF is described.

[0142] like Figure 9 As shown, in the case of a conventional RAN, when communication with the AMF is performed in operations 1b, 2 and 4, a conventional interface (e.g., the N2 interface) has been used.

[0143] Conversely, according to this disclosure, such as Figure 9 As shown, the RANF of this disclosure, implemented as an NF by including the above-described SBI module, can perform communication operations 1b, 2, and 4 (wherein, conventional RAN uses the N2 interface) by using the SBI.

[0144] • UE context release request (UE CONTEXT RELEASE REQUEST) -> e.g., Namf_UEContext_Release

[0145] • UE context release command (UE CONTEXT RELEASE COMMAND) -> for example, Nran_UEContext_Release

[0146] • UE context release complete (UE CONTEXT RELEASE COMPLETE) -> e.g., Nran_UEContext_Release confirmation: 204 No context

[0147] Subsequently, referring to Figure 10 As one implementation of the call flow that the RANF of this disclosure can execute via SBI, a call flow related to PDU session control (e.g., creation, update, deletion, etc.) associated with direct communication with the SMF is described.

[0148] like Figure 10 As shown, the traditional RAN uses a traditional interface (e.g., the N2 interface) and therefore can have a structure that performs communication with the SMF via the AMF.

[0149] Conversely, according to this disclosure, such as Figure 10 As shown, the RANF of this disclosure, which is implemented as NF by including the above-mentioned SBI module, can directly perform SBI communication with SMF without going through AMF (e.g., ①, ②), so the signaling that needs to go through AMF (the box drawn with dark gray line) can be unnecessary and can be omitted.

[0150] In this scenario, call flow between RANF and SMF can be shortened / simplified, AMF functions can be optimized, and overall signaling can be reduced.

[0151] Subsequently, referring to Figure 11 As one implementation of the call flow that the RANF can execute via SBI according to this disclosure, a QoS policy-related call flow associated with direct communication with the PCF is described.

[0152] like Figure 11 As shown, the traditional RAN uses a traditional interface (e.g., the N2 interface) and therefore can have a structure that performs communication with the PCF via the AMF.

[0153] Conversely, according to this disclosure, such as Figure 11 As shown, the RANF implemented as NF by including the above-mentioned SBI module can directly perform SBI communication with PCF without going through AMF (①, ②, ③), so the signaling that needs to go through AMF (the box drawn with dark gray line) can be unnecessary and can be omitted.

[0154] Therefore, the call flow between RANF and PCF can be shortened / simplified, AMF functions can be optimized, and overall signaling can be reduced. Furthermore, PCF can immediately receive information from RANF (e.g., QoS scheduling information, QoS priority, NW slicing information, etc.).

[0155] Subsequently, referring to Figure 12 As one implementation of the call flow that the RANF can execute via SBI according to this disclosure, a call flow related to NF registration processing associated with direct communication with the NRF is described.

[0156] like Figure 12As shown, according to this disclosure, the RANF implemented as an NF by including the above-described SBI module can directly perform SBI communication with the NRF by using SBI messages (e.g., NRF registration) without going through the AMF, in the same manner as the core NF (e.g., AMF, SMF, etc.).

[0157] Furthermore, the RANF of this disclosure can perform SBI communication with the NRF directly without going through the AMF, in the same manner as the core NF (e.g., AMF, SMF, etc.), thereby enabling various direct communication / interoperability (e.g., discovery of NFs (e.g., AMF, SMF, etc.) for handling service requests, etc.).

[0158] As described above, this disclosure defines / implements the SBI module in detail to allow the functionality of RAN devices to evolve to the 5G architecture and be implemented as NF, thereby unifying the functionality of all devices (RAN, core) including RAN and 5G core as NF.

[0159] An interface method according to one embodiment of this disclosure can be embodied in the form of program commands executable via various computer devices and can be recorded in a computer-readable medium. The computer-readable medium can include program commands, data files, data structures, etc., independently or in combination. The program commands recorded in the medium may be specifically designed or configured for this disclosure, or may be known to those skilled in the art of computer software and may be permitted for use. Examples of computer-readable recording media may include magnetic media such as hard disks, floppy disks, and magnetic tapes; optical media such as CD-ROMs and DVDs; magneto-optical media such as floppy disks; and hardware devices specifically configured to store and implement program commands such as ROMs, RAMs, flash memory, etc. Furthermore, program commands may include, for example, high-level language code executable in a computer using an interpreter, and machine code produced by a compiler. The aforementioned hardware devices may be configured to operate as one or more software modules to perform the operations of this disclosure, and vice versa.

[0160] Although this disclosure has been described in detail with reference to various embodiments, this disclosure is not limited to the above embodiments, and the technical concept of this disclosure can be modified or corrected by those skilled in the art without departing from the subject matter of this disclosure as claimed in the appended claims.

Claims

1. A radio access node apparatus, the radio access node apparatus being configured to provide services to an accessing user equipment (UE), the radio access node apparatus comprising: An NF communication unit, configured to perform the necessary communications associated with the provision of the service. The NF communication unit communicates using SBI messages based on the Service-Based Interface (SBI) between NFs. The SBI message includes a packet with a header, and The NF communication unit classifies the packet into at least one of a control plane (CP) packet or a user plane (UP) packet based on the header, and modifies the header to include the destination address corresponding to the NF of the CP when the packet is a CP packet, and to include the destination address corresponding to the NF of the UP when the packet is a UP packet. The NF communication unit is configured to communicate with the NF of the CP using the SBI message without going through the Access and Mobility Management Function (AMF).

2. The radio access node device according to claim 1, wherein, The NF communicating with the NF communication unit is at least one of the following: another node device that forms a base station with the radio access node device, another radio access node device, the NF service in another radio access node device, the NF of the CP, and the NF of the UP.

3. The radio access node device according to claim 1, wherein, The NF communication unit includes an SBI module that processes the SBI messages.

4. The radio access node device according to claim 3, wherein, The SBI module is configured to operate according to at least one of a request / response based message sending or receiving scheme and a subscription / notification based message sending or receiving scheme.

5. The radio access node apparatus according to claim 3, wherein, The SBI module is configured to perform a conversion between messages based on another interface and SBI messages based on the SBI to send or receive messages.

6. The radio access node apparatus according to claim 1, wherein, The NF communication unit is configured to use the SBI message when sending or receiving messages related to the radio part handover of the UE.

7. The radio access node apparatus according to claim 1, wherein, The NF communication unit is configured to use the SBI message when a notification is sent based on the detection of a specific event subscribed to by the AMF.

8. The radio access node apparatus according to claim 1, wherein, The NF communication unit is configured to use the SBI message when sending or receiving messages related to the UE context of the UE.

9. The radio access node apparatus according to claim 1, wherein, The NF communication unit is configured to communicate with the Session Management Function (SMF) used for managing and controlling UE sessions using the SBI message without going through the AMF when processing the UE's session management.

10. The radio access node apparatus according to claim 1, wherein, The NF communication unit is configured to communicate with the Policy Control Function (PCF), which manages and controls multiple policies including QoS policies, without going through the AMF, using the SBI message when performing quality-related processing of the UE.

11. The radio access node apparatus according to claim 1, wherein, The NF communication unit is configured to communicate using the SBI message without going through the AMF when processing the registration of the radio access node device's NF to the network repository function NRF, wherein the NRF is used to manage and control information associated with each NF in the network.

12. An interface method performed by a radio access node device, the interface method comprising the following steps: Communication is achieved using messages from the Service-Based Interface (SBI) between Network Functions (NFs). The message includes a packet with a header, and The steps involved in communication include: Based on the header, the packets are classified as at least one of control plane (CP) packets or user plane (UP) packets; Modify the header to include the destination address corresponding to the NF of the CP when the packet is the CP packet, and to include the destination address corresponding to the NF of the UP when the packet is the UP packet; and Without going through the Access and Mobility Management Function (AMF), the NF of the CP is communicated using SBI messages.

Images