KR20210007794A - Apparatus and method for user equipment identification in radio access network communication system - Google Patents

Abstract

An objective of the invention of the present disclosure is to provide a method and an apparatus for identifying a user in a radio access network (RAN). To this end, the method, which is performed by a first node in a wireless communication system, includes: identifying a unique identifier of a terminal; identifying a RAN terminal identifier of the terminal; and transmitting information related to a mapping relation between the RAN terminal identifier and the unique identifier of the terminal to a second node based on the unique identifier of the terminal. Accordingly, a user-specific service or a user-demanded service is efficiently provided through radio resource monitoring for a specific user.

Description

User identification method and device in RAN communication system {APPARATUS AND METHOD FOR USER EQUIPMENT IDENTIFICATION IN RADIO ACCESS NETWORK COMMUNICATION SYSTEM}

The present invention relates to a method and apparatus for classifying users, generating and transmitting identifiers for a base station in a wireless communication system.

In order to meet the demands of wireless data traffic, 5G communication systems (hereinafter, 5G systems, which can be mixed with NR (new radio or next radio) systems, etc.) have been commercialized, and services with high data rates through 5G systems such as 4G It is expected that wireless communication services with various purposes, such as Internet of Things and services that require high reliability for specific purposes, can be provided to users.

Open Radio Access Network (O-RAN), established by companies and equipment providers in a system mixed with the current 4G communication system and 5G system, defines new Network Element (NE) and Interface standards based on the existing 3GPP standards. , O-RAN (Open Radio Access Network) structure emerged.

As the 4G/5G communication system (hereinafter referred to as 4G/5G system, NR (new radio or next radio)) is commercialized, differentiated service support is required for users in a virtualized network, but in RAN or O-RAN. There is a problem that it is impossible to specify a user from the collected cell-related information. We propose a method to solve this problem.

The present invention for solving the above problem is a method of a first node of a wireless communication system, the method comprising the steps of: checking a unique identifier of a terminal; Checking a radio access network (RAN) terminal identifier of the terminal; And transmitting information related to a mapping relationship between the radio access network (RAN) terminal identifier and the unique identifier of the terminal to a second node based on the unique identifier of the terminal.

In addition, the unique identifier of the terminal may be identified based on the first information transmitted from the terminal and the second information transmitted from the network entity, and information related to the mapping relationship between the RAN terminal identifier and the unique identifier of the terminal May include at least one of RAN terminal identifier information set based on the unique identifier of the terminal, the RAN terminal identifier and a unique identifier pair of the terminal.

In addition, the unique identifier of the terminal is 5G-GUTI, the first information is 5G-S-TMSI, the network entity is AMF, the second information may be GUAMI, or the unique identifier of the terminal is GUTI, the first information may be S-TMSI, the network entity may be MME, and the second information may be GUMMEI.

In addition, measurement information about the terminal may be transmitted from the first node to the second node together with information related to the mapping relationship between the RAN terminal identifier and the unique identifier of the terminal.

In addition, a method of a second node of a wireless communication system, the method comprising: receiving information related to a mapping relationship between a radio access network (RAN) terminal identifier for a terminal and a unique identifier of the terminal from a first node; Checking the unique identifier of the terminal and the RAN terminal identifier; And processing information related to the terminal received from a third node and/or a fourth node based on the RAN terminal identifier of the terminal.

In addition, the information related to the mapping relationship between the RAN terminal identifier and the unique identifier of the terminal includes RAN terminal identifier information set based on the unique identifier of the terminal, the RAN terminal identifier and the unique identifier pair of the terminal. It may include at least one of, and the unique identifier of the terminal may be 5G-GUTI or GUTI.

In addition, measurement information on the terminal may be received from the first node to the second node together with information related to the mapping relationship between the RAN terminal identifier and the unique identifier of the terminal. At this time, the second node may receive the RAN terminal identifier and measurement-related information on the terminal from the third node and/or the fourth node, and the first node, the third node, and the fourth node Information on the terminal received from at least one of the nodes may be transmitted to the fifth node, and the information on the terminal may be transmitted together with a unique identifier of the terminal.

In addition, an apparatus for controlling a first node of a wireless communication system, comprising: a communication unit; And a unique identifier of the terminal, a radio access network (RAN) terminal identifier of the terminal, and a radio access network (RAN) terminal identifier and a unique identifier of the terminal based on the unique identifier of the terminal. And a control unit connected to the communication unit for controlling to transmit information related to the mapping relationship of to the second node.

An apparatus for controlling a second node of a wireless communication system, comprising: a communication unit; And receiving information related to a mapping relationship between a radio access network (RAN) terminal identifier for a terminal and a unique identifier of the terminal from the first node, and confirming the unique identifier of the terminal and the RAN terminal identifier, and the And a control unit connected to the communication unit for controlling to process information related to the terminal received from a third node and/or a fourth node based on the RAN terminal identifier of the terminal.

Through the invention of the present disclosure, it is possible to efficiently provide a user-specific service or a user requested service through radio resource monitoring for a specific user.

1A is a diagram illustrating an example of a 4G LTE core system.
1B is a diagram illustrating an example of a 3GPP 5G Non-Standard Alone (NSA) system.
2 is a diagram showing the configuration of IMSI, which is a unique identifier of a terminal commonly used in 3G, 4G, and 5G systems defined by ITU-T.
3 is a diagram showing the configuration of a GUTI used by an MME of an LTE core network defined in 3GPP standards.
4 is a diagram illustrating an example of a 5G NR core system.
5 is a diagram showing a configuration of a 5G-GUTI used in a 5G core system.
6 is a diagram illustrating an example of an O-RAN network system.
7 is a diagram illustrating an example of a connection between an O-RAN RIC and a plurality of O-CU-CP, O-CU-UP, and O-DU.
FIG. 8 is a diagram illustrating a procedure for obtaining 5G-GUTI by CU-CP of 5G RAN defined in 3GPP.
9 is a diagram illustrating a procedure for obtaining a 5G-GUTI by an O-CU-CP of a 5G RAN defined in an O-RAN.
10 is a diagram illustrating a procedure for obtaining a GUTI by an eNB of a 4G RAN defined in 3GPP.
11 is a diagram illustrating a procedure for obtaining a GUTI by an eNB of a 4G O-RAN defined in O-RAN.
12 is a diagram illustrating a procedure for generating a GUTI by an eNB of a 4G RAN defined in 3GPP.
13 is a diagram illustrating a procedure for generating 5G-GUTI by CU-CP of 5G RAN defined in 3GPP.
14 is a diagram showing a procedure for receiving information classified as a specific terminal from an O-DU and an O-CU-CP by an RIC defined in an O-RAN.
FIG. 15 is a diagram illustrating a procedure for an NRT-RIC defined in O-RAN to receive information classified as a specific terminal from an O-DU, an O-CU-CP, and RIC.
16 is a diagram illustrating a procedure for a collection server to receive information classified as a specific terminal from DU, CU-UP and CU-CP defined in 3GPP.
17 is a diagram illustrating a procedure for a RIC to receive information classified as a specific terminal from O-DU, O-CU-UP and O-CU-CP defined in O-RAN.
18 is a diagram illustrating an example of using a 5G-GUTI-based UE identifier proposed by the present invention in an O-RAN.
19 is a diagram showing an apparatus for carrying out the present invention.
20 is a diagram illustrating an example of a 5G Non-Standard Alone (NSA) system defined by O-RAN.
FIG. 21 is a diagram illustrating a procedure for obtaining a GUTI by an eNB to which a UE accesses a call in the case of an NSA EN-DC defined in O-RAN.
FIG. 22 is a diagram illustrating a procedure for obtaining a GUAMI by a CU-CP of a 5G RAN defined in 3GPP in case of an initial attach of a terminal.
FIG. 23 is a diagram illustrating a procedure for an eNB of a 4G RAN defined in 3GPP to acquire a GUMMEI in case of an Initial Attach of a UE.
24 is a diagram illustrating an example of a procedure for allocating a globally unique RAN UE ID in a core network in case of an initial attach of a terminal by an O-CU-CP of a 5G RAN defined by an O-RAN.
25 is a diagram illustrating a procedure for allocating a globally unique RAN UE ID in a core network in case of an initial attach of a terminal by an eNB in the case of LTE/NSA defined in O-RAN.
FIG. 26 is a diagram showing an example of a procedure for allocating a RAN UE NGAP ID used for configuring a core network and NGAP as a RAN UE ID in case of an initial attach of a terminal by an O-CU-CP of a 5G RAN defined in an O-RAN.
27 is a diagram showing RAN UE NGAP ID specified in 3GPP standard.
FIG. 28 is a diagram illustrating an example of a procedure for allocating an AMF UE NGAP ID used for configuring a core network and NGAP as a RAN UE ID in case of an initial attach of a terminal by an O-CU-CP of a 5G RAN defined by an O-RAN.
29 is a diagram showing a detailed configuration of AMF UE NGAP ID.
30 is a diagram showing the configuration of an MME UE S1AP ID.
31 is a diagram showing an example of generating a 64-bit terminal identifier using a hash function.

Hereinafter, embodiments of the present invention will be described in detail together with the accompanying drawings. In addition, when it is determined that detailed descriptions of known functions or configurations related to the present invention may unnecessarily obscure the subject matter of the present invention, detailed descriptions thereof will be omitted. In addition, terms to be described later are terms defined in consideration of functions in the present invention, which may vary according to the intention or custom of users and operators. Therefore, the definition should be made based on the contents throughout this specification.

In addition, in describing the embodiments of the present invention in detail, the main subject matter of the present invention can be applied to other communication systems having similar technical backgrounds and channel types with slight modifications within the scope of the present invention. And, this will be possible by the judgment of a person skilled in the technical field of the present invention.

Advantages and features of the present invention, and a method of achieving them will become apparent with reference to the embodiments described below in detail together with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but may be implemented in a variety of different forms, only the present embodiments are intended to complete the disclosure of the present invention, and the general knowledge in the art It is provided to completely inform the scope of the invention to those who have it, and the invention is only defined by the scope of the claims. The same reference numerals refer to the same components throughout the specification.

At this time, it will be appreciated that each block of the flowchart diagrams and combinations of the flowchart diagrams may be executed by computer program instructions. Since these computer program instructions can be mounted on the processor of a general purpose computer, special purpose computer or other programmable data processing equipment, the instructions executed by the processor of the computer or other programmable data processing equipment are described in the flowchart block(s). It creates a means to perform functions. These computer program instructions can also be stored in computer-usable or computer-readable memory that can be directed to a computer or other programmable data processing equipment to implement a function in a particular way, so that the computer-usable or computer-readable memory It is also possible to produce an article of manufacture containing instruction means for performing the functions described in the flowchart block(s). Computer program instructions can also be mounted on a computer or other programmable data processing equipment, so that a series of operating steps are performed on a computer or other programmable data processing equipment to create a computer-executable process to create a computer or other programmable data processing equipment. It is also possible for instructions to perform processing equipment to provide steps for executing the functions described in the flowchart block(s).

In addition, each block may represent a module, segment, or part of code that contains one or more executable instructions for executing the specified logical function(s). In addition, it should be noted that in some alternative execution examples, functions mentioned in blocks may occur out of order. For example, two blocks shown in succession may in fact be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order depending on the corresponding function.

In this case, the term'~ unit' used in the present embodiment means software or hardware components such as FPGA or ASIC, and'~ unit' performs certain roles. However,'~ part' is not limited to software or hardware. The'~ unit' may be configured to be in an addressable storage medium or may be configured to reproduce one or more processors. Thus, as an example,'~ unit' refers to components such as software components, object-oriented software components, class components and task components, processes, functions, properties, and procedures. , Subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, database, data structures, tables, arrays, and variables. The components and functions provided in the'~ units' may be combined into a smaller number of elements and'~ units', or may be further divided into additional elements and'~ units'. In addition, components and'~ units' may be implemented to play one or more CPUs in a device or a security multimedia card.

Hereinafter, in the present invention, the uplink refers to a radio link through which a terminal (User Equipment, UE or Mobile Station, MS) transmits data or control signals to a base station (eNode B, or base station, BS), and downlink (Downlink) Denotes a radio link through which the base station transmits data or control signals to the terminal. In addition, the base station may be at least one of an eNode B, a Node B, a base station (BS), a generation Node B (gNB) radio access unit, a base station controller, or a node on a network as a subject performing resource allocation of the terminal. The terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing a communication function.

In order to meet the demands of wireless data traffic, 5G communication systems (hereinafter, 5G systems, which can be mixed with NR (new radio or next radio) systems, etc.) have been commercialized, and services with high data rates through 5G systems such as 4G It is expected that wireless communication services with various purposes, such as Internet of Things and services that require high reliability for specific purposes, can be provided to users.

Open Radio Access Network (O-RAN) established by companies and equipment providers in a system mixed with the current 4th generation communication system and 5th generation system, defines new network elements (NE) and interface standards based on the existing 3GPP standards. , O-RAN (Open Radio Access Network) structure emerged. O-RAN newly defines the existing 3GPP NE, RU, DU, CU-CP, and CU-UP as O-RU, O-DU, O-CU-CP, and O-CU-UP respectively (integrating O- RAN base station), and in addition, the near-real-time RAN Intelligent Controller (RIC) and the non-real-time RAN Intelligent Controller (NRT-RIC) were standardized. The newly defined RIC deploys servers intensively in one physical location to transmit information to the actual terminal and the cell site where O-DU, O-CU-CP, and O-CU-UP (O-RAN base station) transmit and receive. It is a logical node that can be collected. Each of the O-DU and RIC, O-CU-CP and RIC, and O-CU-UP and RIC can be connected by Ethernet. In addition, interface standards for communication between O-DU and RIC, between O-CU-CP and RIC, and between O-CU-UP and RIC were required. Currently, E2-DU, E2-CU-CP, E2-CU-UP Standards such as O-DU, O-CU-CP, O-CU-UP and RIC are used.

As the 4th and/or 5th generation communication systems (hereinafter 4G/5G systems, LTE and/or NR (new radio or next radio)) are commercialized, differentiated service support from users is required in a virtualized network. There is a problem that it is impossible to specify which user the information related to the cell collected by the RAN or O-RAN is for a user. The reason is that according to the 3GPP standard, in the Radio Access Network (RAN), the identifiers of the terminals used in O-DU, O-CU-CP and O-CU-UP (hereinafter referred to as RAN terminal identifiers) exist, but (uniquely) users This is because information about (or information that can specify a user, user identifier, user identifier, for example, IMSI (International Mobile Subscriber Identity), SUPI (SUbscription Permanent Identifier), SUCI (SUbscription Concealed Identifier)) is not known.

Specifically, when the RIC receives measurement information and call-related information for each terminal based on the RAN terminal identifier from O-DU, O-CU-CP, and O-CU-UP, the RIC includes a plurality of O-CU- Since the CP can be connected, the RAN terminal identifier may be duplicated, and when the O-CU-CP to which the terminal is connected is changed, the RAN terminal identifier may be changed. Therefore, in the case of the 3GPP standard, in order to specify which user the information collected by the RAN or O-RAN is for the user, it is possible to distinguish between the RAN and the core network, and the user identifier (ID) that can be used on the RAN side. (Or it can be mixed with a user identifier, a terminal identifier, a terminal identifier, etc.) is required.

Based on the user identifier, it may be identified that the information collected by the RAN or O-RAN is for a specific user in the Collection server, RIC, or/and NRT-RIC. The collected information may be transmitted from at least one of (O-)CU-CP, (O-)CU-UP, and (O-)DU, and the collection server, RIC or/and NRT-RIC is the user identifier. Based on, it is possible to confirm that the information collected from different subjects is for one specific user, and determine a Key Performance Indicator (KPI) of a service provided to each user based on the collected information.

Previously, since it was not possible to confirm that the collected information was for a specific user, radio resource monitoring for each user was not possible, but through the present invention, resource optimization for users and user-specific services or It is possible to efficiently provide user-requested services. For example, the RIC (or NRT-RIC or collection server) efficiently divides network slices or sets additional carriers so that a specific terminal can receive services through carrier aggregation for resource optimization, or a specific terminal has dual access. An additional cell to perform dual connectivity can be set so that service can be received through (dual connectivity). In addition, the RIC (or NRT-RIC or collection server) can be configured to connect to a specific cell while avoiding connection with a specific cell when a specific terminal moves between cells. In addition, the RIC (or NRT-RIC or collection server) can efficiently perform resource optimization through machine learning through analysis based on the collected information. In addition, resource optimization of the present invention is not limited to the above description. In addition, according to the present invention, it is possible not only to collect information for each terminal, but also to collect and analyze information for each bearer.

In addition, the collected information for a specific user may be used in the collection server, RIC or NRT-RIC, but is also provided to OSS (Operations Support System) or/and BSS (Business Support System) to provide specialized services to users. .

1A is a diagram illustrating a 4G LTE core system. The eNB (evolved Node B, 100), which is a 4G base station, is connected to a mobility management entity (MME) 120 of a 4G core system through an S1-MME interface. The eNB is a device that performs scheduling by collecting state information such as buffer status, available transmission power, and channel status of the terminal 110. The MME is responsible for mobility management and various control functions for the terminal. The serving gateway 130 provides a data bearer, and creates or controls a data bearer under the control of the MME. The MME can internally identify the UE with a Globally Unique Temporary Identifier (GUTI).

Carrier aggregation (CA) technology combines a plurality of component carriers, and one terminal transmits and receives a signal using such a plurality of component carriers at the same time, thereby improving frequency use efficiency from the viewpoint of the terminal or the base station. It is a technology that increases. Specifically, according to the CA technology, the UE and the base station can transmit and receive signals using a broadband using a plurality of component carriers, respectively, in an uplink (uplink, hereinafter referred to as UL) and a downlink (hereinafter, hereinafter referred to as DL). Component carriers are located in different frequency bands. Hereinafter, the uplink refers to a communication link through which the UE transmits signals to the base station, and the downlink refers to a communication link through which the base station transmits signals to the UE. In this case, the number of uplink component carriers and downlink component carriers may be different.

In dual connectivity or multi connectivity, one terminal is connected to a plurality of different base stations to transmit and receive signals simultaneously using carriers in each of a plurality of base stations located in different frequency bands. It is a technology to increase the frequency use efficiency of The terminal is a first base station (for example, this may be a base station that provides a service using LTE (Long Term Evolution) technology or 4G mobile communication technology) and a second base station (for example, this is NR (New Radio) technology or 5G It may be a base station that provides a service using mobile communication technology) and can transmit and receive traffic simultaneously, and at this time, frequency resources used by each base station may be located in different bands. In this way, a method that operates based on the dual connection method of LTE and NR may be referred to as 5G non-standalone (NSA).

1B shows an example of a 5G NSA system. The 5G NSA system is composed of EPC 150, LTE (or can be mixed with LTE base station, eNB, etc., 160), NR (or NR base station, can be mixed with gNB, 170) and terminal 180 shown in FIG. 1A The LTE base station and the NR base station 160 and 170 are connected to the EPC 150, and the terminal 180 can receive services from the LTE base station and the NR base station 160 and 170 at the same time.

In this case, the UE can perform RRC access through the first base station and receive services provided by the control plane (for example, connection management, mobility management, etc.), and additional radio resources for transmitting and receiving data through the second base station. Can be provided. In this case, this dual connection technology may be referred to as EN-DC (Evolved Universal Terrestrial Radio Access (E-UTRA)-NR Dual Connectivity). The present invention is not limited to these EN-DCs, and the first base station uses NR technology and the second base station uses LTE technology, and can be applied to both NE-DC (NR-E-UTRA Dual Connectivity) and various types of multiple connections. I can. It can also be applied in the case of carrier aggregation.

In addition, the present invention can be applied to a case where a first system using a first communication technology and a second system using a second communication technology are implemented in one device, or when the first base station and the second base station are located in the same geographic location. .

FIG. 2 is a diagram illustrating an International Mobile Subscription Identity (IMSI) that is a unique identifier of a terminal commonly used in all systems of 3G, 4G and 5G defined by ITU-T. Using the IMSI 200, terminals can be uniquely classified worldwide. IMSI is composed of Mobile Country Code (MCC, 210), Mobile Network Code (MNC, 220) and Mobile Subscriber Identification Number (MSIN, 230). MCC is an identifier that allows countries around the world to be identified, and MNC is an identifier that allows public land mobile networks (PLMNs, which can be used interchangeably with operators) to be identified. MSIN is an identifier that allows the terminal to be identified within the PLMN.

3 is a diagram showing a GUTI used in a 4G LTE core system. The GUTI 300 is an identifier that enables identification of a specific terminal in a core network composed of a plurality of MMEs (core network, or can be mixed with a network or a core network). GUTI is composed of GUMMEI (Globally Unique MME Identifier, 310) and M-TMSI (Temporary Mobile Subscription Identifier, 320). GUMMEI is composed of an MCC 330, an MNC 340, and an MME identifier (350). The MME Identifier is composed of an MME Group ID 360 and an MME code 370. The MME Group ID represents an MME group (group) composed of multiple MMEs, and the MME Code indicates a specific MME. The M-TMSI 320 means MME-TMSI, and the M-TMSI allows the UE to be uniquely identified only inside the MME. When the MME code and M-TMSI are combined, it becomes S-TMSI (SAE-Temporary Mobile Subscriber Identity, 380), which is a temporary terminal identifier that allows the MME to identify the user within the MME group.

4 is a diagram of a 5G NR core system. The 5G core network 460 may include a network function such as an Access and Mobility Management Function (AMF) 430, a Session Management Function (SMF) 440, and a User Plane Function (UPF) 450). AMF provides a function for UE-level access and mobility management, which may be similar to the role of the MME in the LTE core network. SMF provides a session management function, and UPF delivers downlink data received from a data network (not shown) to the UE via the gNB 400, and transfers the uplink data received from the UE via the gNB to the data network. Deliver.

In addition, the 5G base station (gNB (generation Node B), 400) has a radio unit (RU), a medium access control (MAC), and a radio link control (RLC) function that performs a physical layer function as a logical function. CU-CP (central unit-control plane, 404), CU-UP (central unit) in charge of higher functions such as DU (digital unit) 402 and RRC (radio resource control) and PDCP (Packet Data Convergence Protocol) -user plane, 406). The CU-CP is a function related to a control plane and may specifically perform connection setup, mobility, and security related functions. CU-UP is a function related to a user plane and can perform a function related to data transmission/reception of a user. gNB is connected to AMF, and multiple AMFs of 5G core network exist in the operator network.

5 is a diagram showing a structure of a 5G-Globally Unique Temporary Identifier (5G-GUTI) used in a 5G core system. 5G-GUTI 500 is an identifier that enables specific terminal identification in a 5G core network composed of a plurality of AMFs, and 5G-GUTI is a GUAMI (Globally Unique AMF Identifier, 510) and 5G-TMSI (5G-Temporary Mobile Subscription Identifier). , 520). GUAMI is composed of MCC (530), MNC (540), AMF Identifier (560). The AMF Identifier is composed of AMF Region ID 560, AMF Set ID 570, and AMF Pointer 580. The AMF Region ID indicates an AMF group composed of multiple AMFs, the AMF Set ID indicates a specific AMF set within the AMF region, and the AMF Pointer indicates a specific AMF within the AMF set. 5G-TMSI is an identifier that uniquely identifies a terminal only in a specific AMF pointer. 5G-S-TMSI (5G SAE-Temporary Mobile Subscriber Identity, 590) can be composed of AMF set ID, AMF pointer, and 5G-TMSI junction, and can be used for wireless signaling in a shortened form of 5G-GUTI. It can be used to perform efficiently.

6 is a diagram of an O-RAN network system. The O-RAN network is a standard that logically separates the functions of the existing 4G, 5G eNB, and gNB, and the O-RAN standard newly introduces NRT-RIC (non-real time RAN intelligent controller, 600) and RIC (near-real- time) RAN intelligent controller, 610), O-CU-CP 620, O-CU-UP 630, O-DU 640, and the like have been defined. O-CU, including O-CU-CP and O-CU-UP, is a logical node that provides functions of RRC, SDAP (Service Data Adaptation Protocol), and PDCP protocol, and O-CU-CP is RRC And a logical node that provides the function of the control plane part of the PDCP, O-CU-UP is a logical node that provides the function of the user plane part of SDAP and PDCP, and the O-DU is RLC, MAC, upper physical layer (high -PHY, which is a logical node that provides the function of a 7-2x fronthaul split, and although not shown, the O-RU connected to the O-DU is a lower physical layer (low-PHY). , Which is based on a 7-2x fronthaul split) is a logical node that provides functionality and RF processing.

NRT-RIC is a logical node that enables non-real-time control, optimization of RAN elements and resources, model training, and updating, and RIC is a logical node that enables O-DU, O-CU- It is a logical node that enables near-real-time control and optimization of RAN elements and resources based on data collected from CP and O-CU-UP.

The present invention is not limited by the name of each node described above, and the configuration of the present invention may be applied in the case of a logical node or entity that performs the above-described functions. In addition, the logical node may be physically located in the same location or different location, and the function may be provided by the same physical device (for example, a processor, a control unit, etc.) or the function may be provided by another physical device. As an example, the function of at least one logical node described above may be provided through virtualization in one physical device.

7 is a diagram illustrating an example of a connection between an O-RAN RIC and a plurality of O-CU-CP, O-CU-UP, and O-DU. As shown, one RIC (700) can be connected to a plurality of O-CU-CP (720), O-CU-UP (710), O-DU (730), each node and each E2-CP ( 750), E2-UP (760), E2-DU (740) interface can be connected. In addition, an interface between O-CU-CP and DU and between O-CU-UP and DU may be referred to as an F1 770 interface. In the present invention, DU and O-DU, CU-CP and O-CU-CP, CU-UP and O-CU-UP may be used interchangeably. Also, eNB and O-RAN eNB, gNB and O-RAN gNB may be mixed. In addition, although one RIC 700 is shown in FIG. 7, a plurality of RICs may exist, which may be implemented by a plurality of hardware located in the same physical location or through virtualization using one hardware.

FIG. 8 is a diagram illustrating a procedure for obtaining 5G-GUTI by CU-CP of 5G RAN defined in 3GPP.

In step 800, according to the call access procedure defined in the 3GPP standard, the terminal 801 includes the upper 39 bits of the 5G SAE-Temporary Mobile Subscriber Identity (5G-S-TMSI) value allocated from the 5G core network in the initial configuration in the RRCSetupRequest message. It is transmitted to DU 802. According to the call access procedure defined in the 3GPP standard in step 810, the DU transmits the upper 39 bits value of the 5G-S-TMSI value received in step 800 to the CU-CP 803 in the F1 Initial UL RRC Message Transfer message. In step 820, the CU-CP stores the upper 39 bits of the 5G-S-TMSI value transmitted by the DU included in the F1 message. Thereafter, the CU-CP performs a DL RRC message transfer to the DU, and the DU transmits an RRCSetup message (or RRCReject message) to the terminal.

When the DU transmits the RRCSetup message, the UE includes the lower 9 bits of the 5G-S-TMSI value allocated from the core network in the initial configuration in the RRCSetupComplete message according to the call access procedure defined in the 3GPP standard in step 830 and transmits it to the DU. . In step 840, according to the call access procedure defined in the 3GPP standard, the DU transmits the lower 9 bits value of the 5G-S-TMSI value received in step 4 to the CU-CP in the F1 UL RRC Message Transfer message. In step 850, the CU-CP stores the lower 9 bits of the 5G-S-TMSI value transmitted by the DU in the F1 message. Thereafter, the CU-CP transmits an Initial UE message to the AMF 805.

In step 860, the CU-CP stores the GUAMI value transmitted by the AMF in the NGAP INITIAL CONTEXT SETUP REQUEST message according to the call connection procedure defined in the 3GPP standard. In step 870, CU-CP checks 5G-TMSI based on the upper 39 bits and lower 9 bits of 5G-S-TMSI stored in steps 820 and 850, and attaches 5G-TMSI to the lower part of the GUAMI received in step 860. Create 5G-GUTI.

The above-described procedure is not necessarily performed in sequence or all steps are performed, and may be performed by changing the order or omitting specific steps. In addition, another configuration illustrated in FIG. 8 may be performed in addition to the above-described procedure, and a procedure described in another drawing may be performed in combination with the procedure illustrated in FIG. 8.

9 is a diagram illustrating a procedure for obtaining a 5G-GUTI by an O-CU-CP of a 5G RAN defined in an O-RAN.

In step 900, according to the call access procedure defined in the 3GPP standard, the terminal 901 includes the upper 39 bits of the 5G-S-TMSI value allocated from the core network in the initial configuration in the RRCSetupRequest message and transmits it to the O-DU 902. In step 910, according to the call access procedure defined in the 3GPP standard, the O-DU contains the upper 39 bits of the 5G-S-TMSI value received in step 900 as O-CU-CP (903) in the F1 Initial UL RRC Message Transfer message. And send it. In step 920, the O-CU-CP stores the upper 39 bits of the 5G-S-TMSI value transmitted by the O-DU in the F1 message. Thereafter, the O-CU-CP performs a DL RRC message transfer to the O-DU, and the O-DU transmits an RRCSetup message (or RRCReject) message to the terminal.

When the O-DU transmits the RRCSetup message, the UE includes the lower 9 bits of the 5G-S-TMSI value allocated from the core network in the initial configuration according to the call access procedure defined in the 3GPP standard in step 930 in the RRCSetupComplete message. It is transmitted as DU. In step 940, according to the call access procedure defined in the 3GPP standard, the O-DU transmits the lower 9 bits of the 5G-S-TMSI value received in step 4 to the O-CU-CP in the F1 UL RRC Message Transfer message. . In step 950, the O-CU-CP stores the lower 9 bits of the 5G-S-TMSI value transmitted by the O-DU in the F1 message.

Thereafter, the O-CU-CP transmits the Initial UE message to the AMF (905), and in step 960, the O-CU-CP is transmitted by including the AMF in the NGAP INITIAL CONTEXT SETUP REQUEST message according to the call connection procedure defined in the 3GPP standard. Save the GUAMI value. In step 970, O-CU-CP checks 5G-TMSI based on the upper 39 bits and lower 9 bits of 5G-S-TMSI stored in steps 920 and 950, and adds 5G-TMSI to the lower part of the GUAMI received in step 960. Conjugation to create 5G-GUTI.

The above-described procedure is not necessarily performed in sequence or all steps are performed, and may be performed by changing the order or omitting specific steps. In addition, another configuration illustrated in FIG. 9 may be performed in addition to the above-described procedure, and a procedure described in another drawing may be performed in combination with the procedure illustrated in FIG. 9.

10 is a diagram illustrating a procedure for obtaining a GUTI by an eNB of a 4G RAN defined in 3GPP.

In step 1000, according to the call access procedure defined in the 3GPP standard, the terminal 1001 includes 40 bits of the S-TMSI value allocated from the core network in the initial configuration in the RRC Connection Request message and transmits it to the eNB 1002. In step 1010, the eNB stores the S-TMSI value transmitted by the UE. Thereafter, the eNB transmits an RRCConnectionSetup message to the UE, and the UE transmits an RRCConnectionSetupComplete message to the eNB in response thereto. Thereafter, the eNB transmits an Initial UE message to the MME 1003. Thereafter, in step 1020, the eNB stores the GUMMEI value transmitted by including it in the S1AP INITIAL CONTEXT SETUP REQUEST message by the MME according to the call access procedure defined in the 3GPP standard. In step 1030, the eNB checks the MME Temporary Mobile Subscriber Identity (M-TMSI) based on the S-TMSI stored in step 1010, and creates a GUTI by joining the M-TMSI under the GUMMEI received in step 1020.

The above-described procedure is not necessarily performed in sequence or all steps are performed, and may be performed by changing the order or omitting specific steps. In addition, another configuration illustrated in FIG. 10 may be performed in addition to the above-described procedure, and a procedure described in another drawing may be performed in combination with the procedure illustrated in FIG. 10.

11 is a diagram illustrating a procedure for obtaining a GUTI by an eNB of a 4G O-RAN defined in an O-RAN.

In step 1100, according to the call access procedure defined in the 3GPP standard, the terminal 1101 includes 40 bits of the S-TMSI value allocated from the core network in the initial configuration in the RRC Connection Request message and transmits it to the eNB 1102 of the O-RAN. In step 1110, the eNB stores the S-TMSI value transmitted by the UE. Thereafter, the eNB transmits an RRCConnectionSetup message to the UE, and the UE transmits an RRCConnectionSetupComplete message to the eNB in response thereto. Thereafter, the eNB transmits an Initial UE message to the MME 1103. In step 1120, the eNB of the O-RAN stores the GUMMEI value transmitted by the MME in the S1AP INITIAL CONTEXT SETUP REQUEST message according to the call access procedure defined in the 3GPP standard. In step 1130, the O-RAN eNB checks the M-TMSI based on the S-TMSI stored in step 1110, and generates a GUTI by concatenating the M-TMSI under the GUMMEI received in step 1120.

The above-described procedure is not necessarily performed in sequence or all steps are performed, and may be performed by changing the order or omitting specific steps. In addition, another configuration illustrated in FIG. 11 may be performed in addition to the above-described procedure, and a procedure described in another drawing may be performed in combination with the procedure illustrated in FIG. 11.

12 is a diagram illustrating a configuration in which an eNB of a 4G RAN defined in 3GPP generates a GUTI using S-TMSI received from a terminal and GUMMEI received from an MME. The eNB confirms the M-TMSI 1220 by applying the lower 32bits Mask to the S-TMSI 1200. The eNB creates a GUTI 1230 by joining the GUMMEI 1210 in front of the identified M-TMSI. In this case, the method of generating the GUTI is not limited to the above-described masking, and the GUTI may be generated through various methods based on S-TMSI and GUMMEI.

13 is a diagram illustrating a configuration in which a CU-CP of a 5G RAN defined in 3GPP generates a 5G-GUTI using 5G-S-TMSI received from a terminal and GUAMI received from an AMF. CU-CP confirms 5G-TMSI 1320 by applying the lower 32bits Mask to 5G-S-TMSI 1300. CU-CP creates 5G-GUTI 1330 by joining GUAMI 1310 in front of 5G-TMSI. In this case, the method of generating the 5G-GUTI is not limited to the above-described masking, and the GUTI may be generated through various methods based on 5G-S-TMSI and GUAMI.

14 is a diagram showing a procedure for receiving information classified as for a specific terminal from an O-DU and an O-CU-CP by an RIC defined in an O-RAN.

In step 1400, the O-CU-CP 1402 communicates with the terminal and AMF to generate a 5G-GUTI. 5G-GUTI can be created by the method described above. In step 1410, the RIC 1403 transmits the E2-CP RIC SUBSCRIPTION REQUEST message defined in the O-RAN standard to the O-CU-CP, and when a specific event occurs, the RIC 1403 is configured to transmit a report classified for each specific terminal. In step 1420, the O-CU-CP performs the request set by step 1410 to the RIC, and in step 1400, the RAN UE ID defined in 3GPP and the RAN UE ID are mapped to the E2 E2-CP RIC SUBSCRIPTION RESPONSE message to the RIC. Transmits with a preset 5G-GUTI included.

Based on the mapping relationship between the RAN UE ID and 5G-GUTI, the RIC can determine which terminal the collected information is for (ie, which 5G-GUTI is for the terminal). Details will be described later. The RAN UE ID is a temporary terminal identifier defined in 3GPP, and is a terminal identifier used between CU-CP, CU-UP, and DU. This can be set between each node during the F1 interface setup, and is used to identify a specific terminal between each node and report call related information and measurement related information for a specific terminal, and is defined as 64 bits. The RAN UE ID is a terminal identifier temporarily determined within the O-RAN base station, and can be set by an operator as OAM (operation administration maintenance). As a specific example, the RAN UE ID may be used to report call summary log (CSL) information to the call log collection server. O-CU-CP can set the RAN UE ID by any number. For example, the RAN UE ID may be included in the UE context setup request and UE context setup response messages transmitted and received between the DU and the CU, and the bearer context modification request and bearer context modification failure messages transmitted and received between the CU-CP and CU-UP. Can be included. In addition, as an example, the RAN UE ID may be included in the Handover request message and Handover request acknowledge message transmitted and received by the source gNB and the target gNB, and may be included in the Retrieve UE context request and Retrieve UE context response message of the old gNG and the new gNB. It may be included in the Handover required message between the gNB and the AMF and the Handover command message, and may be included in the S-node addition request and S-node request acknowledge message between the master gNB and the secondary gNB, and the initial UE message transmitted by the gNB to the AMF It may be included in, and may be included in the Handover request and Handover request acknowledge messages between the target gNB and the AMF.

In the present invention, an example in which the RAN UE ID and 5G GUTI are included and transmitted in the E2 E2-CP RIC SUBSCRIPTION RESPONSE message is described, but the O-CU-CP is the only terminal shared with the 5G-GUTI or the core network. It may be set based on a value for unique identification or a combination of a value for identifying a terminal shared with the GUAMI and the core network. In 5G networks, User Data Management (UDM) stores the user's permanent ID, SUPI (Subscription Permanent ID), subscription data, policy data, etc., and AMF maps between SUPI and 5G-GUTI or RAN UE ID and 5G-GUTI. , It stores mapping information between SUPIs. A value for identifying a terminal shared with the core network may be based on the mapping information. The AMF may store a value for identifying the UE and mapping information of an identifier capable of globally uniquely identifying the UE such as 5G GUTI or SUPI.

In this case, the RAN UE ID is 5G-GUTI (or a value for uniquely identifying a terminal shared with the core network or a combination of a value for identifying a terminal shared with the GUAMI and the core network, hereinafter 5G-GUTI is 5G -GUTI, a value for uniquely identifying a terminal shared with the core network, or a combination of values for identifying a terminal shared with the GUAMI and the core network) It may be determined by a function (or rule) to be, and such a function may be predetermined or set. In this case, the RIC may obtain the 5G-GUTI value of the specific terminal according to a predetermined or set function (or rule) based on the received RAN UE ID of the specific terminal. In this case, the O-CU-CP transmits only the RAN UE ID or/and 5G-GUTI to the RIC, or adds a parameter applied to generate the RAN UE ID from the 5G-GUTI with the RAN UE ID or/and 5G-GUTI. Can be transmitted. Alternatively, since the maximum length of the currently defined RAN UE ID is 64 bits and the length of 5G-GUTI is 62 bits, the O-CU-CP can set the contents of the RAN UE ID to be the same as 5G-GUTI. In the case described above or when a value for identifying a terminal shared with the core network including the GUAMI is used as the RAN UE ID, the O-CU-CP may transmit only the RAN UE ID to the RIC. This method is not limited to the example of FIG. 14 and may be applied to the entire contents of the present invention.

In addition, the O-CU-CP can transmit the RAN UE ID (and 5G-GUTI) through another message even if it is not an E2 E2-CP RIC SUBSCRIPTION RESPONSE message to the RIC, and the present invention can be applied to this case.

In step 1430, the RIC transmits the E2-DU RIC SUBSCRIPTION REQUEST message defined in the O-RAN standard to the O-DU 1401, and when a specific event occurs, the RIC configures to transmit a report classified for each specific terminal. In step 1440, the O-DU performs the RIC's request according to step 1430, and transmits the E2-DU RIC SUBSCRIPTION RESPONSE to the RIC, including the RAN UE ID and the report for each RAN ID. Such a report may include terminal-related information, specifically, terminal-related measurement information, and may include at least one of DU resource state information and terminal KPI-related information (this is information related to throughput and latency. The report) The content of is not limited to the example of FIG. 14 and may be applied to the entire content of the present invention.

When a preset event occurs in step 1410 in step 1450, the O-CU-CP transmits information classified by RAN UE ID to the RIC using the E2-CP INDICATION message defined in O-RAN. The information may include one or more RAN UE IDs and information for each RAN UE ID. The information may be related to at least one of KPI-related information for each terminal and UE context information in the CU-CP, and the content of the information is not limited to the example of FIG. 14 and may be applied to the entire contents of the present invention.

When a preset event occurs in step 1410 in step 1460, the O-DU transmits information classified by RAN UE ID to the RIC using the E2-DU INDICATION message defined in O-RAN. The information may include one or more RAN UE IDs and information for each RAN UE ID.

The RIC checks the 5G-GUTI associated with the RAN UE ID and stores the information per RAN UE ID transmitted by the O-CU-CP and O-DU in steps 1450 and 1460 so as to be associated with each 5G-GUTI. That is, information on a specific user transmitted by each of the O-CU-CP and O-DU for one 5G-GUTI may be stored. At this time, since a plurality of O-CU-CPs and a plurality of O-DUs may be connected to the RIC, there is a fear that the RAN UE ID transmitted by each O-CU-CP and O-DU may overlap. At this time, the RIC identifies 5G-GUTI or identifies 5G-GUTI based on the port information and RAN UE ID of the O-CU-CP and/or O-DU that transmitted the RAN UE ID (and information related thereto). Alternatively, 5G-GUTI may be identified based on the RAN function ID and RAN UE ID of the O-DU.

In addition, the RAN UE ID described above is only an example of an O-RAN specific user identifier, and a user identifier (or terminal identifier) specific to the O-RAN may be used in this method, and 5G-GUTI is the terminal (or user) This is only an example of a globally unique identifier, and a globally unique identifier of a terminal (or user) may be used in the present method.

The above-described procedure is not necessarily performed in sequence or all steps are performed, and may be performed by changing the order or omitting specific steps. In addition, another configuration illustrated in FIG. 14 may be performed in addition to the above-described procedure, and a procedure described in another drawing may be performed in combination with the procedure illustrated in FIG. 14. The name of the message described in FIG. 14 is only an example, and the configuration of the present invention may be applied to a method and message similar to that disclosed in the present invention.

FIG. 15 is a diagram illustrating a procedure for an NRT-RIC defined in O-RAN to receive information classified as a specific terminal from an O-DU, an O-CU-CP, and RIC. O-DU (1501), O-CU-UP (1502), O-CU-CP (1503), and RIC (1504) use the O1 message defined in O-RAN for each UE separated by each RAN UE ID. Information, cell-specific information is transmitted to the NRT-RIC (1500). In addition to the RAN UE ID, the RIC transmits 5G-GUTI information in a mapping relationship with the RAN UE ID together. In this case, the information transmitted by the RIC (although not shown) may be measurement information for each terminal received from the O-DU, O-CU-CP, and O-CU-UP together with the RAN UE ID. RIC's xApps can process the received information for each terminal and transmit the processed information for each terminal to the NRT-RIC together with the RAN UE ID and/or 5G-GUTI.

NRT-RIC collects the information transmitted by O-DU, O-CU-UP, O-CU-CP, and RIC through each O-1 interface for each RAN UE ID, and the 5G-GUTI transmitted by the RIC Connect and save. That is, the NRT-RIC can also store information corresponding to each user transmitted by O-DU, O-CU-UP, O-CU-CP, and RIC based on 5G-GUTI. In addition, the NRT-RIC may provide the collected information to OSS or/and BSS.

The RAN UE ID is set based on 5G-GUTI (in this case, the NRT-RIC may be determined in advance based on the RAN UE ID or may acquire 5G-GUTI according to a set rule) or the maximum of the currently defined RAN UE ID. Since the length is 64 bits and the length of 5G-GUTI is 62 bits, the contents of the RAN UE ID can be set equal to the 5G-GUTI. In this case, the RIC can transmit only the RAN UE ID to the RIC.

In addition, the RAN UE ID described above is only an example of an O-RAN specific user identifier, and a user identifier (or terminal identifier) specific to the O-RAN may be used in this method, and 5G-GUTI is the terminal (or user) This is only an example of a globally unique identifier, and a globally unique identifier of a terminal (or user) may be used in the present method.

The above-described procedure is not necessarily performed in sequence or all steps are performed, and may be performed by changing the order or omitting specific steps. In addition, other configurations shown in FIG. 15 may be performed in addition to the above-described procedure, and procedures described in other drawings may be performed in combination with the procedure described in FIG. 15. The name of the message described in FIG. 15 is only an example, and the configuration of the present invention may be applied to a method and message similar to that disclosed in the present invention.

16 is a procedure for a collection server to receive information classified as a specific terminal from DU, CU-UP and CU-CP defined in 3GPP.

In step 1600, the CU-CP 1601 communicates with the terminal and the AMF to generate 5G-GUTI. This method can be carried out in the manner described above. In step 1610, the collection server 1604 transmits a SUBSCRIPTION REQUEST message provided by the collection server to CU-CP, and configures to transmit a report classified for each specific terminal when a specific event occurs. In step 1620, the CU-CP performs the request set by step 1610 to the Collection Server (SUBSCRIPTION RESPONSE message), and at this time, the RAN UE ID defined in 3GPP and the RAN UE ID are mapped to the Collection Server in step 1600. It transmits with a 5G-GUTI included.

Based on the mapping relationship between the RAN UE ID and 5G-GUTI, the Collection Server can check which terminal the collected information is for (ie, which 5G-GUTI is for the terminal). Details will be described later. The RAN UE ID is a unique value within the 3GPP 5G NR base station and can be set by the operator as OAM.

In the present invention, an example in which the RAN UE ID and 5G GUTI are transmitted in the SUBSCRIPTION RESPONSE message is described, but the CU-CP sets the RAN UE ID based on 5G-GUTI (in this case, based on the RAN UE ID received by the RIC 5G-GUTI can be obtained according to a predetermined or set rule) or the maximum length of the currently defined RAN UE ID is 64 bits and the length of 5G-GUTI is 62 bits, so CU-CP sets the contents of the RAN UE ID to 5G-GUTI. It can be set as In this case, the CU-CP can transmit only the RAN UE ID to the RIC.

In addition, the CU-CP can transmit the RAN UE ID (and 5G-GUTI) through another message even if it is not a SUBSCRIPTION RESPONSE message to the Collection Server, and the present invention can be applied even in this case.

In step 1630, the collection server transmits the SUBSCRIPTION REQUEST message provided by the collection server to the CU-UP 1602, and when a specific event occurs, the collection server configures to transmit the report classified by specific terminal to the collection server. In step 1640, the CU-UP performs the request according to step 1630, and transmits the SUBSCRPTION RESPONSE message to the collection server by including the RAN UE ID defined in 3GPP and the report (terminal related information) for each RAN UE ID.

In step 1650, the collection server transmits a SUBSCRIPTION REQUEST message provided by the collection server to the DU 1601, and when a specific event occurs, the collection server is configured to transmit a report classified for each specific terminal to the collection server. In step 1060, the DU performs the request according to procedure 6, and transmits the SUBSCRPTION RESPONSE message to the Collection server by including the RAN UE ID defined by 3GPP and the report (terminal related information) for each RAN UE ID.

In step 1670, when a preset event occurs in step 1610, the CU-CP transmits information classified by RAN UE ID to the collection server using an indication message defined by the collection server. The information may include one or more RAN UE IDs and information for each RAN UE ID.

In step 1680, when a preset event occurs in step 1630, the CU-UP transmits information classified by RAN UE ID to the collection server using an indication message defined by the collection server. The information may include one or more RAN UE IDs and information for each RAN UE ID.

When a preset event occurs in step 1650 in step 1690, the DU transmits information classified by RAN UE ID to the collection server using an indication message defined by the collection server. The information may include one or more RAN UE IDs and information for each RAN UE ID.

The collection server checks the 5G-GUTI associated with the RAN UE ID and stores the information per RAN UE ID transmitted by the CU-CP, CU-UP, and DU in steps 1620, 1640, and 1650 to be associated with each 5G-GUTI. That is, information on a specific user transmitted by each of the CU-CP, CU-CP and DU for one 5G-GUTI may be stored. At this time, since a plurality of CU-CP, CU-UP, and a plurality of DUs may be connected to the Collection Server, there is a possibility that the RAN UE ID transmitted by each CU-CP, CU-UP, and DU may overlap. At this time, the Collection Server identifies 5G-GUTI based on the port information and RAN UE ID of the CU-CP, CU-UP and/or DU that transmitted the RAN UE ID (and information related thereto), or the CU-CP, CU- 5G-GUTI may be identified based on the RAN function ID and RAN UE ID of the UP and/or DU.

The above-described procedure is not necessarily performed in sequence or all steps are performed, and may be performed by changing the order or omitting specific steps. In addition, another configuration illustrated in FIG. 16 may be performed in addition to the above-described procedure, and a procedure described in another drawing may be performed in combination with the procedure illustrated in FIG. 16. The name of the message described in FIG. 16 is only an example, and the configuration of the present invention may be applied to a method and message similar to that disclosed in the present invention.

17 is a diagram illustrating a procedure for a RIC to receive information classified as for a specific terminal from O-DU, O-CU-UP and O-CU-CP defined in O-RAN.

In step 1700, the O-CU-CP 1703 communicates with the terminal and the AMF to create a 5G-GUTI. 5G-GUTI can be created by the method described above. In step 1710, the RIC 1704 transmits the E2 SUBSCRIPTION REQUEST message defined in the O-RAN to the O-CU-CP, and when a specific event occurs, the RIC 1704 configures to transmit a report classified for each specific terminal. In step 1720, the O-CU-CP performs the RIC's request according to step 1710, and in the E2 SUBSCRIPTION RESPONSE message to the RIC, the RAN UE ID defined in 3GPP and the 5G preset in step 1 are mapped to the RAN UE ID. -Send with GUTI included.

Based on the mapping relationship between the RAN UE ID and 5G-GUTI, the RIC can determine which terminal the collected information is for (ie, which 5G-GUTI is for the terminal). Details will be described later. The RAN UE ID is a unique value within the 3GPP 5G NR base station and can be set by the operator as OAM.

In the present invention, an example in which the RAN UE ID and 5G GUTI are transmitted in the E2 E2-CP RIC SUBSCRIPTION RESPONSE message is described, but the O-CU-CP sets the RAN UE ID based on 5G-GUTI (in this case, the RIC receives It is possible to obtain 5G-GUTI according to a pre-determined or set rule based on one RAN UE ID) or the maximum length of the currently defined RAN UE ID is 64 bits and the length of 5G-GUTI is 62 bits, so O-CU-CP is The content of the RAN UE ID can be set to be the same as 5G-GUTI. In this case, the O-CU-CP can transmit only the RAN UE ID to the RIC.

In addition, the O-CU-CP can transmit the RAN UE ID (and 5G-GUTI) through another message even if it is not an E2 E2-CP RIC SUBSCRIPTION RESPONSE message to the RIC, and the present invention can be applied to this case.

In step 1730, the RIC transmits the E2 SUBSCRIPTION REQUEST message defined in the O-RAN to the O-CU-UP 1702, and when a specific event occurs, the RIC is configured to transmit the report classified for each specific terminal to the RIC. In step 1740, the O-CU-UP performs the RIC's request in step 1730, and transmits the RAN UE ID defined in 3GPP and the information for each RAN UE ID together in a SUBSCRPTION RESPONSE message to the RIC.

In step 1750, the RIC transmits the E2 SUBSCRIPTION REQUEST message provided by the RIC to the O-DU 1701, and when a specific event occurs, the RIC configures to transmit a report classified for each specific terminal to the RIC. In step 1760, the O-DU performs the RIC's request in step 1750, and transmits the RAN UE ID defined in 3GPP and the RAN UE ID information to the RIC in a SUBSCRPTION RESPONSE message together.

When a preset event occurs in step 1710 in step 1770, the O-CU-CP transmits information classified by RAN UE ID to the RIC in the E2 Indication message defined by the RIC. The information may include one or more RAN UE IDs and information for each RAN UE ID. When a preset event occurs in step 1730 in step 1780, the O-CU-UP transmits information classified by RAN UE ID to the RIC in the E2 Indication message defined by the RIC. The information may include one or more RAN UE IDs and information for each RAN UE ID. The information may include at least one of resource status information in CU-UP (buffer status, bearer status information such as the number of bearers, CPU usage status, KPI related information (terminal throughput, delay, etc.). In addition, the content of the information is not limited to the example of FIG. 17 and may be applied to the entire content of the present invention.

In step 1790, when a preset event occurs in step 1750, the O-DU transmits information classified by RAN UE ID to the RIC in an indication message defined by the RIC. The information may include one or more RAN UE IDs and information for each RAN UE ID.

The RIC checks the 5G-GUTI associated with the RAN UE ID and correlates with each 5G-GUTI the information per RAN UE ID transmitted by O-CU-CP, O-CU-UP and O-DU in steps 1720, 1740, and 1760. Save it. That is, information on a specific user transmitted by each of the O-CU-CP and O-DU for one 5G-GUTI may be stored.

At this time, since multiple O-CU-CP, O-CU-UP and multiple O-DUs may be connected to the RIC, the RAN transmitted from each O-CU-CP, O-CU-UP and O-DU There is a fear that the UE ID will be duplicated. At this time, the RIC identifies 5G-GUTI based on the port information and RAN UE ID of the O-CU-CP, O-CU-UP and/or O-DU that transmitted the RAN UE ID (and related information), or -It is possible to identify the 5G-GUTI based on the RAN function ID and RAN UE ID of CU-CP, O-CU-UP and/or O-DU.

In addition, the RAN UE ID described above is only an example of an O-RAN specific user identifier, and a user identifier (or terminal identifier) specific to the O-RAN may be used in this method, and 5G-GUTI is the terminal (or user) This is only an example of a globally unique identifier, and a globally unique identifier of a terminal (or user) may be used in the present method.

The above-described procedure is not necessarily performed in sequence or all steps are performed, and may be performed by changing the order or omitting specific steps. In addition, another configuration illustrated in FIG. 17 may be performed in addition to the above-described procedure, and a procedure described in another drawing may be performed in combination with the procedure illustrated in FIG. 17. The name of the message described in FIG. 17 is only an example, and the configuration of the present invention may be applied to a method and message similar to that disclosed in the present invention. The name of the message described in FIG. 17 is only an example, and the configuration of the present invention may be applied to a method and message similar to that disclosed in the present invention.

In addition, each method described in the present invention may be used in combination with one or more methods.

18 is a diagram illustrating an example of using a 5G-GUTI-based UE identifier proposed by the present invention in an O-RAN. 1800 denotes the usage of O-DU per network slice and per cell physical resource block (Physical Resource Block (PRB), which can be mixed with physical layer resources, radio resources, time-frequency resources, etc.), throughput This is an example of measuring (Throughput) and latency (Latency) and transmitting information for each user to the RIC along with the RAN UE ID based on 5G-GUTI, such as a KPI report.

1810 is an example in which O-CU-CP measures KPI for each network slice and cell, and transmits information for each user to the RIC along with the RAN UE ID based on 5G-GUTI. At this time, 5G-GUTI can be transmitted together.

In 1820, the O-CU-UP measures the throughput per network slice, per bearer per cell, CPU usage, etc., and provides KPI report, resource usage, overload indication, etc. for each user based on the 5G-GUTI RAN UE ID (and 5G-GUTI) is an example of transmission to RIC.

The transmitted information may be received by E2 Termination xApp and stored in a database for each 5G-GUTI. Based on the stored information, xApp, which acts as a KPI monitor, can analyze whether the KPI of each terminal has been achieved, and the information collected and generated for each terminal such as the analysis result (KPI report) is NRT through the O1 interface xApps. Can be transferred to RIC.

The RIC and the NRT-RIC may perform resource optimization to provide necessary services to each terminal based on the information stored for each 5G-GUTI. Specifically, the RIC or NRT-RIC can configure the terminal to use additional radio resources through carrier aggregation or dual access to the terminal, or control the movement of the terminal.

19 is a diagram showing an apparatus capable of carrying out the present invention. The apparatus 1800 of the present invention may include a control unit 1910 and a communication unit 1920, and although not shown, may include a storage unit. The control unit 1910 performs at least one of the above-described functions such as RIC, NRT-RIC, O-CU-CP, O-CU-UP, O-DU, CU-CP, CU-UP, and DU. Operation, and the communication unit 1920 may be controlled by the control unit 1910 to transmit and receive the described message. The storage unit may store information included in the received message and information on each terminal.

20 is a diagram showing a 3GPP Non-Standard Alone (NSA) support system of an O-RAN network system. The 3GPP NSA network supports the existing 4G (eNB) function and uses dual access using 4G and 5G simultaneously using 5G (gNB). In the O-RAN standard, newly defined NRT-RIC (non-real time RAN intelligent controller, 2000), RIC ((near-real-time) RAN intelligent controller, 2010), O-CU-CP (2020), O- While using the CU-UP 2030, O-DU 2040, etc., an NSA scheme that additionally supports the eNB 2050 of 4G LTE is also supported. At this time, the RIC (2010) and/or NRT-RIC based on the data collected from the O-RAN O-eNB through the E2-eNB interface between the RIC (2010) and the O-eNB (2050) defined in O-RAN. (2000) enables near-real-time control and optimization of LTE and 5G RAN elements and resources. To this end, the O-eNB 2050 may transmit call-related information and measurement-related information for a specific terminal to the RIC 2010.

FIG. 21 is a diagram illustrating a procedure for obtaining a GUTI by an eNB to which a UE accesses a call in the case of an NSA EN-DC defined in O-RAN. In the O-RAN NSA, as in the 3GPP NSA, a message for call connection is delivered to the MME through the O-eNB, and then dual-connectivity is supported by establishing an X2 interface with the gNB. Therefore, the initial call connection process is the same as in the case of 4G LTE.

In step 2100, according to the call access procedure defined in the 3GPP standard, the terminal 2101 includes 40 bits of the S-TMSI value allocated from the core network in the initial configuration in the RRC Connection Request message and transmits it to the O-eNB 2102 of the O-RAN. do. In step 2110, the O-eNB stores the S-TMSI value transmitted by the UE. Thereafter, the O-eNB transmits an RRCConnectionSetup message to the terminal, and the terminal transmits an RRCConnectionSetupComplete message to the O-eNB in response thereto. Thereafter, the O-eNB transmits an Initial UE message to the MME 2103. In step 2120, the O-eNB of the O-RAN stores the GUMMEI value transmitted by including it in the S1AP INITIAL CONTEXT SETUP REQUEST message by the MME according to the call connection procedure defined in the 3GPP standard. In step 2130, the O-RAN O-eNB checks the M-TMSI based on the S-TMSI stored in step 2110, and generates a GUTI by concatenating the M-TMSI under the GUMMEI received in step 2120.

The above-described procedure is not necessarily performed in sequence or all steps are performed, and may be performed by changing the order or omitting specific steps. In addition, another configuration illustrated in FIG. 21 may be performed in addition to the above-described procedure, and a procedure described in another drawing may be performed in combination with the procedure illustrated in FIG. 21.

FIG. 22 is a diagram illustrating a procedure for obtaining a GUAMI when a CU-CP of a 5G RAN defined in 3GPP performs an Initial Attach (initial attachment) of a UE.

In accordance with the call connection procedure defined in the 3GPP standard, the terminal 2201 performing the initial attach is RANDOM in the RRCSetupRequest message if there is no 5G-S-TMSI (5G SAE-Temporary Mobile Subscriber Identity) value allocated from the 5G core network in the initial configuration. Includes the value and transmits it (step 2200). According to the call access procedure defined in the 3GPP standard, the DU 2202 transmits the RANDOM value received in step 2200 to the CU-CP 2204 by including it in the F1 Initial UL RRC Message Transfer message (step 2210).

Thereafter, the CU-CP performs a DL RRC message transfer to the DU, and the DU transmits an RRCSetup message (or RRCReject message) to the terminal. The terminal receiving the RRCSetup message transmits the RRCSetupComplete message to the DU, and the DU transmits the UL RRC Message Transfer to the CU-CP.

The CU-CP transmits the initial UE message to the AMF 2205, and the AMP transmits the NGAP INITIAL CONTEXT SETUP REQUEST message to the CU-CP according to the 3GPP call access procedure (step 2220). The CU-CP stores the GUAMI value transmitted by the AMF 2205 in the NGAP INITIAL CONTEXT SETUP REQUEST message (step 2230). In the above-described procedure, the GUAMI value stored by the CU-CP can be used as an identifier that can uniquely identify the terminal within the 3GPP gNB, such as the RAN UE ID value, and in the future access scenario of the terminal, this identifier is 5G- Can be replaced by GUTI. In addition, the GUAMI value is not used, but a value based on the GUAMI value can be used as the identifier of the terminal (for example, RAN UE ID), and this method is similar to the method of using 5G-GUTI as the identifier of the terminal. You can refer to the method.

The above-described procedure is not necessarily performed in sequence or all steps are performed, and may be performed by changing the order or omitting specific steps. In addition, another configuration illustrated in FIG. 22 may be performed in addition to the above-described procedure, and a procedure described in another drawing may be performed in combination with the procedure illustrated in FIG. 8.

FIG. 23 is a diagram illustrating a procedure for obtaining a GUMMEI by an eNB to which a UE accesses a call in the case of 4G LTE defined by O-RAN. The call connection is delivered to the MME through the O-eNB.

If there is no S-TMSI value allocated from the core network in the initial configuration according to the call connection procedure defined in the 3GPP standard, the terminal 2301 includes the RANDOM value in the RRC Connection Request message and the O-RAN O-RAN. It transmits to the eNB 2302 (step 2300). The O-eNB transmits an RRCConnectionSetup message to the terminal, and the terminal transmits an RRCConnectionSetupComplete message to the O-eNB in response thereto. Thereafter, the O-eNB transmits an Initial UE message to the MME 2303.

The O-eNB of O-RAN receives the S1AP INITIAL CONTEXT SETUP REQUEST message transmitted by the MME according to the call connection procedure defined in the 3GPP standard (step 2310), and the GUMMEI value transmitted by including it in the S1AP INITIAL CONTEXT SETUP REQUEST message by the MME. Save (step 2320). In the above-described procedure, the GUMMEI value stored by the O-eNB can be used as an identifier that can uniquely identify the terminal within the 3GPP eNB, like the RAN UE ID value, and in the subsequent access scenario of the terminal, this identifier is used as GUTI. Can be replaced. In addition, the GUMMEI value is not used, but a value based on the GUMMEI value can be used as the identifier of the terminal (for example, RAN UE ID), and this method is similar to the method of using 5G-GUTI or GUTI as the identifier of the terminal. Reference may be made to the method described above.

The above-described procedure is not necessarily performed in sequence or all steps are performed, and may be performed by changing the order or omitting specific steps. In addition, another configuration illustrated in FIG. 23 may be performed in addition to the above-described procedure, and a procedure described in another drawing may be performed in combination with the procedure illustrated in FIG. 23.

FIG. 24 is a diagram illustrating an example of a procedure for allocating a unique RAN UE ID to an operator network allocated by a core network in case of an initial attach of a terminal by an O-CU-CP of a 5G RAN defined by an O-RAN.

According to the call access procedure defined in the 3GPP standard, the terminal 2401 performs the O-DU 2402, O-CU-CP 2404 and RRC Setup procedure, and the procedure may refer to FIG. 8 and the like. In step 2400, the O-CU-CP transmits an NGAP Initial UE message including the RAN UE ID defined in the initial configuration or set in the OAM to the AMF. Alternatively, the O-CU-CP may transmit the NGAP Initial UE message without including the RAN UE ID. In step 2410, the AMF 2405 can identify the UE globally uniquely set by AMF with the RAN UE ID value transmitted by including the O-CU-CP in the NGAP INITIAL UE MESSAGE message according to the call connection procedure defined in the 3GPP standard. It is saved as 5G-GUTI, which is a possible value. That is, the RAN UE ID is set to 5G-GUTI.

In addition, the 5G-GUTI value is not used, but a value based on the 5G-GUTI value, a combination of a GUAMI and a new user identifier, a value based on a GUAMI and a new user identifier, or a value shared with the core network including the GUAMI or GUAMI. A value based on a value shared with the core network may be used as a RAN UE ID or an identifier of a terminal (in O-RAN) (this may be, for example, a GUAMI and a new user identifier). The value shared with the core network may be a value described above in the technology related to FIG. 14. For a method of using information other than the 5G-GUTI as the RAN UE ID or the terminal identifier, a method of identifying the terminal in the operator PLMN may be referred to. That is, the RAN UE ID or the UE ID may be determined based on the UE ID used in the operator PLMN.

In step 2420, the AMF includes the RAN UE ID stored in step 2410 in the NGAP INITIAL CONTEXT SETUP REQUEST message according to the call access procedure defined in the 3GPP standard and transmits it to the O-CU-CP. O-CU-CP stores the RAN UE ID value transmitted by AMF in the NGAP INITIAL CONTEXT SETUP REQUEST message according to the call access procedure defined in the 3GPP standard.

Thereafter, the terminal and O-CU-CP perform the RRC reconfiguration procedure according to the 3GPP standard, and the O-CU-CP includes the RAN UE ID stored in response to the NGAP INITIAL CONTEXT SETUP REQUEST, and sends the NGAP INITIAL CONTEXT SETUP RESPONSE message to AMF. Can be transmitted.

The above-described procedure is not necessarily performed in sequence or all steps are performed, and may be performed by changing the order or omitting specific steps. In addition, another configuration illustrated in FIG. 9 may be performed in addition to the above-described procedure, and a procedure described in another drawing may be performed in combination with the procedure illustrated in FIG. 24.

FIG. 25 is a RAN UE unique to a carrier network allocated by a core network by an O-RAN eNB (O-eNB) (or eNB) in the case of an initial attach of a terminal in the 5G NSA and O-RAN LTE network structure defined by O-RAN It is a diagram showing an example of a procedure for allocating an ID.

According to the call access procedure defined in the 3GPP standard, the terminal 2501 performs an RRC Connection Setup procedure with the O-eNB 2502, and the procedure may refer to FIG. 10 and the like. In step 2500, the O-eNB transmits the S1 Initial UE message to the MME 2503 by including the RAN UE ID defined in the initial configuration or set in the OAM. Alternatively, the O-eNB may transmit the S1 Initial UE message without including the RAN UE ID. In step 2510, the MME includes the RAN UE ID value transmitted by the O-eNB in the S1 INITIAL UE MESSAGE message according to the call connection procedure defined in the 3GPP standard as GUTI, a value that can identify the UE in a globally unique manner newly set by the MME. Save it. That is, the RAN UE ID is set to GUTI.

In addition, the GUTI value is not used, but a value based on a GUTI value or a combination of GUMMEI and a new user identifier, a value based on GUMMEI and a new user identifier, or a value shared with a core network including GUMMEI, or a core network including GUMMEI. A value based on the shared value may be used as a RAN UE ID or an identifier of a terminal (in O-RAN) (this may be, for example, a GUMMEI and a new user identifier). The value shared with the core network may be a value described above in the technology related to FIG. 14. For a method of using information other than the GUTI as a RAN UE ID or an identifier of a terminal, a method of identifying a terminal in an operator PLMN may be referred to. That is, the RAN UE ID or the UE ID may be determined based on the UE ID used in the operator PLMN.

In step 2520, the MME transmits the RAN UE ID stored in step 2510 by including the RAN UE ID in the S1 INITIAL CONTEXT SETUP REQUEST message to the O-eNB according to the call access procedure defined in the 3GPP standard. The O-eNB stores the RAN UE ID value transmitted by the MME in the S1 INITIAL CONTEXT SETUP REQUEST message according to the call connection procedure defined in the 3GPP standard. Thereafter, the O-eNB may transmit an S1 INITIAL CONTEXT SETUP RESPONSE message including the stored RAN UE ID to the MME in response to the S1 INITIAL CONTEXT SETUP REQUEST message.

The above-described procedure is not necessarily performed in sequence or all steps are performed, and may be performed by changing the order or omitting specific steps. In addition, another configuration illustrated in FIG. 25 may be performed in addition to the above-described procedure, and a procedure described in another drawing may be performed in combination with the procedure illustrated in FIG. 25.

FIG. 26 is a diagram showing an example of a procedure for allocating a RAN UE NGAP ID used for configuring a core network and NGAP as a RAN UE ID in case of an initial attach of a terminal by an O-CU-CP of a 5G RAN defined in an O-RAN. According to the call access procedure defined in the 3GPP standard, the terminal 2601 performs the O-DU 2602, O-CU-CP 2603 and RRC Setup procedure, and the procedure may refer to FIG. 8 and the like. Specifically, the terminal 2601 transmits an RRCSetupRequest message to the O-DU 2602 (step 2600). According to the call connection procedure defined in the 3GPP standard, the O-DU 2602 transmits an F1 Initial UL RRC Message Transfer message to the O-CU-CP 2604 (step 2610). Thereafter, the O-CU-CP 2604 performs a DL RRC message transfer to the O-DU 2602, and the O-DU 2602 transmits an RRCSetup message to the terminal 2601. Receiving the RRCSetup message, the terminal 2601 transmits the RRCSetupComplete message to the O-DU 2602 (step 2620), and the O-DU 2602 transmits the UL RRC Message Transfer to the O-CU-CP 2604. (2630).

The O-CU-CP 2604 transmits the NGAP Initial UE message to the AMF 2605 by setting the RAN UE NGAP ID used in the AMF 2605 and NGAP Interface to the RAN UE ID defined in the initial configuration (step 2640). ). Alternatively, the O-CU-CP 2604 may transmit the NGAP Initial UE message without including the RAN UE ID. The details of the RAN UE NGAP ID are shown in FIG. 27. The RAN UE NGAP ID may be a 32-bit integer, but is not limited thereto.

According to the call connection procedure defined in the 3GPP standard, the AMF 2605 is set as the RAN UE NGAP ID value transmitted by the O-CU-CP in the NGAP INITIAL UE MESSAGE message, and stores the transmitted RAN UE ID value as it is, or The ID is set and stored as 5G-GUTI, a value that can identify the UE globally uniquely set by AMF. That is, the RAN UE ID is set to the RAN UE NGAP ID value or 5G-GUTI (by AMF).

In addition, the 5G-GUTI value is not used as the RAN UE ID, but a value based on a 5G-GUTI value or a combination of a GUAMI and a new user identifier, a value based on a GUAMI and a new user identifier, or shared with the core network including the GUAMI A value based on a value or a value shared with the core network including the GUAMI may be used as a RAN UE ID or an identifier of a terminal (in O-RAN) (this may be, for example, a GUAMI and a new user identifier). The value shared with the core network may be a value described above in the technology related to FIG. 14. Alternatively, for a method of using information other than the 5G-GUTI as the RAN UE ID or the terminal identifier, a method of identifying the terminal in the operator PLMN may be referred to. That is, the RAN UE ID or the UE ID may be determined based on the UE ID used in the operator PLMN.

In step 2650, the AMF 2605 includes the stored RAN UE ID in the NGAP INITIAL CONTEXT SETUP REQUEST message according to the call connection procedure defined in the 3GPP standard and transmits it to the O-CU-CP 2604. The O-CU-CP 2604 stores the RAN UE ID value transmitted by the AMF included in the NGAP INITIAL CONTEXT SETUP REQUEST message according to the call connection procedure defined in the 3GPP standard.

Thereafter, the terminal 2601 and O-CU-CP 2604 perform the RRC reconfiguration procedure according to the 3GPP standard, and the O-CU-CP includes the RAN UE ID stored in response to the NGAP INITIAL CONTEXT SETUP REQUEST, and NGAP INITIAL CONTEXT. Send the SETUP RESPONSE message to AMF. Thereafter, the O-CU-CP 2604 can transmit the E2 indication message to the RIC 2606 including the configured RAN UE ID, and in addition, at least one of O-DU 2602 and O-CU-UP 2603 Node of can also transmit the E2 indication message to the RIC (2606).

The above-described procedure is not necessarily performed in sequence or all steps are performed, and may be performed by changing the order or omitting specific steps. In addition, another configuration illustrated in FIG. 26 may be performed in addition to the above-described procedure, and a procedure described in another drawing may be performed in combination with the procedure illustrated in FIG. 26.

27 is a diagram showing RAN UE NGAP ID specified in 3GPP standard. The RAN UE NGAP ID is an identifier used in the RAN used when O-CU-CP and AMF establish NGAP connection. This is a delimiter that enables unique identification of a UE (or an association with a UE) in an NG interface with a base station (gNB or NG-RAN node).

FIG. 28 is a diagram illustrating an example of a procedure for allocating an AMF UE NGAP ID used for configuring a core network and NGAP as a RAN UE ID in case of an initial attach of a terminal by an O-CU-CP of a 5G RAN defined in an O-RAN.

According to FIG. 28, the terminal 2801 performs the O-DU 2802, O-CU-CP 2803 and RRC Setup procedure according to the call access procedure defined in the 3GPP standard, and the procedure is referred to FIG. I can. Specifically, the terminal 2801 transmits an RRCSetupRequest message to the O-DU 2802 (step 2800). According to the call access procedure defined in the 3GPP standard, the O-DU 2802 transmits an F1 Initial UL RRC Message Transfer message to the O-CU-CP 2804 (2810). Thereafter, the O-CU-CP 2804 performs a DL RRC message transfer to the O-DU 2802, and the O-DU 2802 transmits an RRCSetup message to the terminal 2801. Receiving the RRCSetup message, the terminal 2801 transmits the RRCSetupComplete message to the O-DU 2802 (step 2820), and the O-DU 2802 transmits the UL RRC Message Transfer to the O-CU-CP 2804. (2830).

The O-CU-CP 2804 transmits the NGAP Initial UE message to the AMF 2805 by setting the RAN UE NGAP ID used in the AMF 2805 and NGAP Interface as the RAN UE ID defined in the initial configuration (step 2840). ). Alternatively, the O-CU-CP 2804 may transmit the NGAP Initial UE message without including the RAN UE ID. The details of the RAN UE NGAP ID are shown in FIG. 27. The RAN UE NGAP ID may be a 64-bit integer, but is not limited thereto.

AMF (2805) according to the call connection procedure defined in the 3GPP standard (transmitted by O-CU-CP by including in the NGAP INITIAL UE MESSAGE message, defined in the initial configuration or transmitted by setting the RAN UE NGAP ID value) RAN UE ID The value can be set to 5G-GUTI, which is a globally unique value that can identify the UE newly set by the AMF 2806, or the AMF UE NGAP ID used by the AMF to identify the UE can be allocated and stored. That is, the RAN UE ID may be set to an AMF UE NGAP ID value or 5G-GUTI (by AMF). In addition, the 5G-GUTI value is not used as the RAN UE ID, but a value based on a 5G-GUTI value, a combination of a GUAMI and a new user identifier, a value based on a GUAMI and a new user identifier, or a core including a GUAMI A value shared with the network or a value based on a value shared with the core network including the GUAMI may be used as the RAN UE ID or the ID of the terminal (in O-RAN).

29 is a diagram showing a detailed configuration of AMF UE NGAP ID. The AMF UE NGAP ID is an identifier allocated to uniquely identify a terminal in the NG interface with the AMF, and may be uniquely set within the AMF set. For example, the AMF UE NGAP ID may be 40 bits, and when the base station receives the AMF UE NGAP ID, the AMF UE NGAP ID of a specific terminal must be stored while the terminal-related logical NG-connection to a specific terminal is maintained, The AMF UE NGAP ID may be included in NGAP signaling. In addition, in the case of LTE, the MME UE S1AP ID may be used instead of the AMF UE NGAP ID. 30 is a diagram showing the configuration of an MME UE S1AP ID. The MME UE S1AP ID, similar to the AMF UE NGAP ID, is an identifier allocated to uniquely identify a terminal connected to one MME on the S1-MME interface, and may be 32 bits. In the case of the LTE system, instead of the AMF of FIG. 28, the MME may allocate the MME UE S1AP ID as the RAN UE ID. In addition, even if the AMF UE NGAP ID and MME UE S1AP ID are not, the AMF UE NGAP ID or MME UE S1AP ID may be substituted if the AMF or MME is an identifier used to identify the UE.

Alternatively, AMF (or MME) uses a 128-bits, 256-bits SECURE HASH FUNCTION defined by 3GPP or SECURE HASH FUNCTION defined by NIST (National Institute of Standards and Technology), IETF (Internet Engineering Task Force). After generating the row, it is also possible to set the RAN UE ID value by cutting it into 64 bits according to the length of the RAN UE ID, which is 64 bits. This may be the application of the security function so that it is impossible to find the existing AMF NGAP UE ID value (or MME UE S1AP ID) or 5G-GUTI value based on the RAN UE ID. The details of SECURE HASH(SH) 64bits TRUNCATION are shown in FIG. 31. 31 is an example of generating 128 bits using AES-CMAC based on the AMF UE NGAP ID or MME UE S1AP ID, trunking the upper 64 bits of the generated 128 bits, and the lower 64 bits SH-AMF It shows an example of generating a UE NGAP ID or an SH-MME UE S1AP ID and using it as a RAN UE ID. The 64-bit terminal identifier may be an ID that can uniquely identify the terminal in the AMF pool or the MME pool. 31 is only an example of generating an identifier of a terminal using HASH FUNCTION, and the present invention is not limited thereto.

The value shared with the core network may be a value described above in the technology related to FIG. 14. Alternatively, a method of using information other than the 5G-GUTI as a RAN UE ID or an identifier of a terminal may refer to a method of identifying a terminal in an operator PLMN. That is, the RAN UE ID or the terminal identifier may be determined based on the identifier of the terminal used in the operator PLMN.

In step 2850, the AMF 2805 includes the stored RAN UE ID in the NGAP INITIAL CONTEXT SETUP REQUEST message according to the call access procedure defined in the 3GPP standard and transmits it to the O-CU-CP 2804. The O-CU-CP 2804 stores the AMF UE NGAP ID transmitted by the AMF 2806 in the NGAP INITIAL CONTEXT SETUP REQUEST message according to the call access procedure defined in the 3GPP standard as the RAN UE ID value.

Alternatively, O-CU-CP (2804) is a SECURE HASH FUNCTION defined by 3GPP, or 128-bits, 256-bits SECURE HASH FUNCTION defined by NIST and IETF, as the AMF UE NGAP ID transmitted by AMF (2906) in the NGAP INITIAL CONTEXT SETUP REQUEST message After generating a bit stream by applying, it can be cut into 64 bits according to the length of the RAN UE ID, which is 64 bits, and set as the RAN UE ID value. This may be a security function applied so that it is impossible to find an existing AMF NGAP UE ID value or 5G-GUTI value based on the RAN UE ID.

O-CU-CP (2804) sends the E1 Bearer Context Setup Request message specified in the 3GPP standard to O-CU-UP (2803) by including the RAN UE ID set later, and receives the E1 Bearer Context Setup Response message. And (2660, 2670), the RAN UE ID is included in the F1 UE CONTEXT SETUP REQUEST message specified in the 3GPP standard and transmitted to the O-DU 2802, and the F1 UE CONTEXT SETUP RESPONSE message is received (2880, 2890).

Thereafter, the terminal 2801 and O-CU-CP 2804 perform the RRC reconfiguration procedure according to the 3GPP standard, and the O-CU-CP 2804 includes the RAN UE ID stored in response to the NGAP INITIAL CONTEXT SETUP REQUEST. A NGAP INITIAL CONTEXT SETUP RESPONSE message is transmitted to the AMF 2806.

The above-described procedure is not necessarily performed in sequence or all steps are performed, and may be performed by changing the order or omitting specific steps. In addition, another configuration illustrated in FIG. 28 may be performed in addition to the above-described procedure, and a procedure described in another drawing may be performed in combination with the procedure illustrated in FIG. 28.

Various embodiments of the present document and terms used therein are not intended to limit the technical features described in this document to specific embodiments, and should be understood to include various modifications, equivalents, or substitutes of the corresponding embodiments.

Claims (24)

In the method of the first node of a wireless communication system,
Confirming the unique identifier of the terminal;
Checking a radio access network (RAN) terminal identifier of the terminal;
And transmitting information related to a mapping relationship between the radio access network (RAN) terminal identifier and the unique identifier of the terminal to a second node based on the unique identifier of the terminal. The method of claim 1,
The method, characterized in that the unique identifier of the terminal is identified based on the first information transmitted from the terminal and the second information transmitted from the network entity. The method of claim 1,
Information related to the mapping relationship between the RAN terminal identifier and the unique identifier of the terminal is at least one of RAN terminal identifier information set based on the unique identifier of the terminal, the RAN terminal identifier and the unique identifier pair of the terminal A method comprising one. The method of claim 2,
The unique identifier of the terminal is 5G-Globally Unique Temporary Identifier (5G-GUTI), the first information is 5G SAE-Temporary Mobile Subscriber Identity (5G-S-TMSI), and the network entity is Access and Mobility (AMF). Management Function), and the second information is a Globally Unique AMF Identifier (GUAMI). The method of claim 2,
The unique identifier of the terminal is a Globally Unique Temporary Identifier (GUTI), the first information is a SAE-Temporary Mobile Subscriber Identity (S-TMSI), the network entity is a mobility management entity (MME), and the second information GUMMEI (Globally Unique MME Identifier), characterized in that the method. The method of claim 1,
The method according to claim 1, wherein measurement information on the terminal is transmitted from the first node to the second node together with information related to a mapping relationship between the RAN terminal identifier and the unique identifier of the terminal. In the method of the second node of a wireless communication system,
Receiving information related to a mapping relationship between a radio access network (RAN) terminal identifier for a terminal and a unique identifier of the terminal from a first node;
Checking the unique identifier of the terminal and the RAN terminal identifier; And
And processing information related to the terminal received from at least one of a third node and a fourth node based on the RAN terminal identifier of the terminal. The method of claim 7,
Information related to the mapping relationship between the RAN terminal identifier and the unique identifier of the terminal is at least one of RAN terminal identifier information set based on the unique identifier of the terminal, the RAN terminal identifier and the unique identifier pair of the terminal A method comprising one. The method of claim 7,
The method characterized in that the unique identifier of the terminal is a 5G-Globally Unique Temporary Identifier (5G-GUTI) or a Globally Unique Temporary Identifier (GUTI). The method of claim 7,
And measurement information for the terminal is received from the first node to the second node together with information related to a mapping relationship between the RAN terminal identifier and the unique identifier of the terminal. The method of claim 10,
And receiving the RAN terminal identifier and measurement related information on the terminal from at least one of the third node and the fourth node. The method of claim 11,
Transmitting information on the terminal received from at least one of the first node, the third node, and the fourth node to a fifth node,
The method, characterized in that the information on the terminal is transmitted together with the unique identifier of the terminal. In the apparatus for controlling a first node of a wireless communication system,
Communication department; And
Check the unique identifier of the terminal, check the RAN (radio access network) terminal identifier of the terminal, and based on the unique identifier of the terminal, the RAN (radio access network) terminal identifier and the unique identifier of the terminal And a control unit connected to the communication unit for controlling to transmit information related to the mapping relationship to a second node. The method of claim 13,
The device, characterized in that the unique identifier of the terminal is identified based on the first information transmitted from the terminal and the second information transmitted from the network entity. The method of claim 13,
Information related to the mapping relationship between the RAN terminal identifier and the unique identifier of the terminal is at least one of RAN terminal identifier information set based on the unique identifier of the terminal, the RAN terminal identifier and the unique identifier pair of the terminal Device, characterized in that it comprises one. The method of claim 14,
The unique identifier of the terminal is 5G-Globally Unique Temporary Identifier (5G-GUTI), the first information is 5G SAE-Temporary Mobile Subscriber Identity (5G-S-TMSI), and the network entity is Access and Mobility (AMF). Management Function), and the second information is a Globally Unique AMF Identifier (GUAMI). The method of claim 14,
The unique identifier of the terminal is a Globally Unique Temporary Identifier (GUTI), the first information is a SAE-Temporary Mobile Subscriber Identity (S-TMSI), the network entity is a mobility management entity (MME), and the second information GUMMEI (Globally Unique MME Identifier), characterized in that the device. The method of claim 13,
The apparatus, characterized in that, together with information related to a mapping relationship between the RAN terminal identifier and the unique identifier of the terminal, measurement information on the terminal is transmitted from the first node to the second node. In the apparatus for controlling a second node of a wireless communication system,
Communication department; And
Receive information related to a mapping relationship between a radio access network (RAN) terminal identifier for a terminal and a unique identifier of the terminal from a first node, check the unique identifier of the terminal and the RAN terminal identifier, and the terminal And a control unit connected to the communication unit for controlling to process information related to the terminal received from a third node and/or a fourth node based on the RAN terminal identifier of. The method of claim 19,
Information related to the mapping relationship between the RAN terminal identifier and the unique identifier of the terminal is at least one of RAN terminal identifier information set based on the unique identifier of the terminal, the RAN terminal identifier and the unique identifier pair of the terminal Device, characterized in that it comprises one. The method of claim 19,
The device, characterized in that the unique identifier of the terminal is a 5G-Globally Unique Temporary Identifier (5G-GUTI) or a Globally Unique Temporary Identifier (GUTI). The method of claim 19,
The apparatus, characterized in that, together with information related to a mapping relationship between the RAN terminal identifier and the unique identifier of the terminal, measurement information on the terminal is received from the first node to the second node. The method of claim 22,
And receiving the RAN terminal identifier and measurement-related information for the terminal from at least one of the third node and the fourth node. The method of claim 23,
The control unit further controls to transmit information on the terminal received from at least one of the first node, the third node, and the fourth node to a fifth node,
The device, characterized in that the information on the terminal is transmitted together with the unique identifier of the terminal.

Images