Method and apparatus for identifying user in ran communication system

Abstract

A method and apparatus for identifying a user in a radio access network (RAN) and a first node in a wireless communication system are provided. The method includes identifying a unique identifier of the UE; a radio access network (RAN) UE identifier of the UE is identified, and information related to a mapping relationship between the RAN UE identifier and the unique identifier of the UE is transmitted to the second node based on the unique identifier of the UE.

Description

[0001] This application is a divisional application of an invention patent application with an application date of July 13, 2020, application number: 202080062649.X, and invention name: “Method and device for identifying users in a RAN communication system”. Technical Field

[0002] The present disclosure relates to a method and apparatus for identifying a user and generating and transmitting an identifier by a Base Station (BS) in a wireless communication system. Background Art

[0003] Due to the commercialization of the fifth generation (5G) communication system (hereinafter, used interchangeably with the 5G system or new radio or next generation radio (NR) system) that meets the demand for radio data services, services with high data transmission rates are provided to users through the 5G system as well as the fourth generation (4G) system, and the provision of IoT and wireless communication services for various purposes, such as services requiring high reliability for specific purposes, is predicted.

[0004] In the systems currently used with 4G communication systems and 5G communication systems, the open radio access network (O-RAN) established by service providers and equipment supply companies defines new network elements (NEs) and interface standards on the basis of conventional 5GPP standards to create an O-RAN structure.

[0005] The above information is provided as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with respect to the present disclosure. Summary of the invention

[0006]

Technical issues

[0007] According to the currently commercialized fourth / fifth generation communication system (hereinafter, referred to as 4G / 5G system, new radio or next generation radio (NR)), it is necessary to support differentiated services for users in a virtualized network, but it is impossible to specify users in cell-related information collected by RAN or O-RAN. A method for solving the problem is proposed.

[0008] [Solution to the problem]

[0009] Aspects of the present disclosure are to solve at least the above problems and / or disadvantages and provide at least the advantages described below. Therefore, one aspect of the present disclosure is to provide a method and apparatus for identifying a user and generating and transmitting an identifier by a BS in a wireless communication system.

[0010] Additional aspects will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the presented embodiments.

[0011] According to one aspect of the present disclosure, a method of a first node in a wireless communication system is provided. The method includes identifying a unique identifier of a user equipment (UE), identifying a radio access network (RAN) UE identifier of the UE, and sending information related to a mapping relationship between the RAN UE identifier and the unique identifier of the UE to a second node based on the unique identifier of the UE.

[0012] The unique identifier of the UE may be identified based on first information sent from the UE and second information sent from the network entity, and information related to a mapping relationship between the RAN UE identifier and the unique identifier of the UE may include RAN UE identifier information configured based on the unique identifier of the UE and at least one of a pair of the RAN UE identifier and the unique identifier of the UE.

[0013] The unique identifier of the UE may be a 5G-Globally Unique Temporary Identifier (5G-GUTI), the first information may be a 5G System Architecture Evolution (SAE)-Temporary Mobile User Identity (5G-S-TMSI), the network entity may be an Access and Mobility Management Function (AMF), and the second information may be a Globally Unique AMF Identifier (GUAMI), or the unique identifier of the UE may be a Globally Unique Temporary Identifier (GUTI), the first information may be an SAE-Temporary Mobile User Identity (S-TMSI), the network entity may be a Mobility Management Entity (MME), and the second information may be a Globally Unique MME Identifier (GUMMEI).

[0014] The measurement information of the UE may be sent from the first node to the second node together with information on a mapping relationship between the RAN UE identifier and the unique identifier of the UE.

[0015] According to another aspect of the present disclosure, a method of a second node in a wireless communication system is provided. The method includes receiving information related to a mapping relationship between a radio access network (RAN) UE identifier and a unique identifier of the UE from a first node, identifying the unique identifier of the UE and the RAN UE identifier, and processing information about the UE received from at least one of a third node and a fourth node based on the RAN UE identifier of the UE.

[0016] The information related to the mapping relationship between the RAN UE identifier and the UE's unique identifier may include RAN UE identifier information configured based on the UE's unique identifier and at least one of the pairs of the RAN UE identifier and the UE's unique identifier, and the UE's unique identifier may be a 5G-Globally Unique Temporary Identifier (5G-GUTI) or a Globally Unique Temporary Identifier (GUTI).

[0017] The measurement information of the UE may be sent from the first node to the second node together with information about a mapping relationship between the RAN UE identifier and the unique identifier of the UE. The second node may receive the RAN UE identifier and the measurement related information of the UE from at least one of the third node and the fourth node, and send the information about the UE received from at least one of the first node, the third node, and the fourth node to the fifth node, and the information about the UE may be sent together with the unique identifier of the UE.

[0018] According to another aspect of the present disclosure, there is provided an apparatus for controlling a first node in a wireless communication system. The apparatus includes a communication unit and a controller, the controller being configured to perform control to identify a unique identifier of a UE and to identify a radio access network (RAN) UE identifier of the UE, and being connected to the communication unit, wherein the communication unit is configured to perform control to send information related to a mapping relationship between the RAN UE identifier and the unique identifier of the UE to a second node based on the unique identifier of the UE.

[0019] According to another aspect of the present disclosure, there is provided an apparatus for controlling a second node in a wireless communication system. The apparatus includes a communication unit and a controller, the controller being configured to receive information related to a mapping relationship between a radio access network (RAN) UE identifier and a unique identifier of the UE from a first node, and identifying the unique identifier of the UE and the RAN UE identifier, and connected to the communication unit, wherein the communication unit is configured to perform control to process information about the UE received from at least one of a third node and a fourth node based on the RAN UE identifier of the UE.

[0020] According to another aspect of the present disclosure, a method performed by a node of an open radio access network O-RAN central unit control plane O-CU-CP in a communication system is provided, the method comprising: receiving a RIC subscription request message from a near real-time RAN intelligent controller (near RTRIC); sending a RIC subscription response message to the near RT RIC in response to the RIC subscription request message; and when an event of the near RT RIC is generated, sending an indication message for reporting to the near RT RIC, wherein the indication message includes at least one user equipment UE identifier ID, and wherein the at least one UE ID includes a RAN UE ID, and the RAN UE ID is used to identify the UE on an E1 interface between the O-CU-CP and the O-RAN CU-user plane O-CU-UP and on an F1 interface between the O-CU-CP and a distributed unit DU.

[0021] According to another aspect of the present disclosure, a method performed by a near real-time radio access network RAN ​​intelligent controller (near RT RIC) in a communication system is provided, the method comprising: sending a RIC subscription request message to a node of an open radio access network O-RAN central unit control plane O-CU-CP; receiving a RIC subscription response message in response to the RIC subscription request message from the node of the O-CU-CP; and receiving an indication message for reporting from the node of the O-CU-CP, wherein the indication message includes at least one user equipment UE identifier ID, and wherein the at least one UE ID includes a RAN UE ID, and the RAN UE ID is used to identify the UE on an E1 interface between the O-CU-CP and an O-RAN CU-user plane O-CU-UP and on an F1 interface between the O-CU-CP and a distributed unit DU.

[0022] According to another aspect of the present disclosure, a device of an open radio access network O-RAN central unit control plane O-CU-CP in a communication system is provided, the device comprising: a communication unit; a control unit, configured to: receive a RIC subscription request message from a near real-time RAN intelligent controller (near-RT RIC) via the communication unit; send a RIC subscription response message to the near-RT RIC via the communication unit in response to the RIC subscription request message; and when an event of the near-RT RIC is generated, send an indication message for reporting to the near-RT RIC via the communication unit, wherein the indication message includes at least one user equipment UE identifier ID, and wherein the at least one UE ID includes a RAN UE ID, and the RAN UE ID is used to identify the UE on the E1 interface between the O-CU-CP and the O-RAN CU-user plane O-CU-UP and on the F1 interface between the O-CU-CP and the distributed unit DU.

[0023] According to another aspect of the present disclosure, a device of a near real-time radio access network RAN ​​intelligent controller (near RT RIC) in a communication system is provided, the device comprising: a communication unit; a control unit, configured to: send a RIC subscription request message to a node of an open radio access network O-RAN central unit control plane O-CU-CP via the communication unit; receive a RIC subscription response message in response to the RIC subscription request message from the node of the O-CU-CP via the communication unit; and receive an indication message for reporting from the node of the O-CU-CP via the communication unit, wherein the indication message includes at least one user equipment UE identifier ID, and wherein the at least one UE ID includes a RAN UE ID, and the RAN UE ID is used to identify the UE on an E1 interface between the O-CU-CP and an O-RAN CU-user plane O-CU-UP and on an F1 interface between the O-CU-CP and a distributed unit DU.

[0024] [Advantageous Effects of the Invention]

[0025] The present disclosure can efficiently provide user-specific services or services required by users by monitoring radio resources of specific users.

[0026] Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses various embodiments of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] The above and other aspects, features and advantages of certain embodiments of the present disclosure will become more apparent from the following description taken in conjunction with the accompanying drawings, in which:

[0028] Figure 1a An example of a 4G Long Term Evolution (LTE) core system according to an embodiment of the present disclosure is shown;

[0029] Figure 1b An example of a 3GPP 5G Non-Standard Alone (NSA) system according to an embodiment of the present disclosure is shown;

[0030] Figure 2 The configuration of IMSI as a unique identifier of a UE commonly used in third generation (3G), 4G, and 5G systems defined in the International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) according to an embodiment of the present disclosure is shown;

[0031] Figure 3 shows the configuration of the GUTI used by the MME of the LTE core network defined in the 3GPP standard according to an embodiment of the present disclosure;

[0032] Figure 4 An example of a 5G NR core system according to an embodiment of the present disclosure is shown;

[0033] Figure 5 shows the configuration of a 5G-GUTI used in a 5G core system according to an embodiment of the present disclosure;

[0034] Figure 6 An example of an O-RAN network system according to an embodiment of the present disclosure is shown;

[0035] Figure 7 An example of connection between an O-RAN intelligent controller (RIC) and multiple nodes (such as O-CU-CP, O-CU-UP, and O-DU) according to an embodiment of the present disclosure is shown;

[0036] Figure 8 The process of obtaining 5G-GUTI by CU-CP of 5G RAN defined in 3GPP according to an embodiment of the present disclosure is shown;

[0037] Fig. 9 The process of obtaining 5G-GUTI by the O-CU-CP of the 5G RAN defined in the O-RAN according to an embodiment of the present disclosure is shown;

[0038] Fig.10 The process of acquiring GUTI by an evolved Node B (eNB) of a 4G RAN defined in 3GPP according to an embodiment of the present disclosure is shown;

[0039] Fig.11 The process of obtaining GUTI by eNB of 4G O-RAN defined in O-RAN according to an embodiment of the present disclosure is shown;

[0040] Fig.12 The process of obtaining GUTI by eNB of 4G RAN defined in 3GPP according to an embodiment of the present disclosure is shown;

[0041] Fig.13 The process of obtaining 5G-GUTI by CU-CP of 5G RAN defined in 3GPP according to an embodiment of the present disclosure is shown;

[0042] Fig.14 A process in which the RIC defined in the O-RAN receives information classified for a specific UE from the O-DU and the O-CU-CP according to an embodiment of the present disclosure is shown;

[0043] Fig.15 The present invention shows a process in which the NRT-RIC defined in the O-RAN receives information classified for a specific UE from the O-DU, O-CU-CP and RIC according to an embodiment of the present disclosure;

[0044] Fig.16 A process in which a collecting server receives information classified for a specific UE from DU, CU-UP, and CU-CP defined in 3GPP according to an embodiment of the present disclosure is shown;

[0045] Fig.17 The present invention shows a process in which the RIC receives information classified for a specific UE from the O-DU, O-CU-UP, and O-CU-CP defined in the O-RAN according to an embodiment of the present disclosure;

[0046] Fig.18 An example of using a UE identifier based on using the 5G-GUTI proposed by the present disclosure in O-RAN according to an embodiment of the present disclosure is shown;

[0047] Fig.19 A device for implementing the present disclosure according to an embodiment of the present disclosure is shown;

[0048] Fig. 20 An example of a 5G non-standard standalone (NSA) system defined in O-RAN according to an embodiment of the present disclosure is shown;

[0049] Fig.21 The process of obtaining the GUTI in the case of NSAEN-DC defined in O-RAN by the eNB to which the UE performs call access according to an embodiment of the present disclosure is shown;

[0050] Fig. 22 The invention shows a process in which the CU-CP of the 5G RAN defined in 3GPP acquires the GUAMI when the UE performs an initial attachment according to an embodiment of the present disclosure;

[0051] Fig.23 The present invention shows a process in which an eNB of a 4G RAN defined in 3GPP acquires a GUMMEI when a UE performs an initial attachment according to an embodiment of the present disclosure;

[0052] Fig.24 An example of a process in which the O-CU-CP of a 5G RAN defined in the O-RAN according to an embodiment of the present disclosure allocates a globally unique RAN UE ID in the core network when the UE performs an initial attachment is shown;

[0053] Fig.25 The present invention shows a process in which an eNB in ​​LTE / NSA defined in O-RAN according to an embodiment of the present disclosure allocates a globally unique RAN UE ID in the core network when the UE performs an initial attachment;

[0054] Fig.26An example of a process in which the O-CU-CP of the 5G RAN defined in the O-RAN according to an embodiment of the present disclosure allocates a RAN UE NGAP ID used for NGAP configuration with the core network as the RAN UE ID when the UE performs an initial attachment is shown;

[0055] Fig. 27 shows the RAN UE NGAP ID specified in the 3GPP standard according to an embodiment of the present disclosure;

[0056] Fig.28 An example of a process in which the O-CU-CP of the 5G RAN defined in the O-RAN according to an embodiment of the present disclosure allocates the AMF UE NGAP ID used for NGAP configuration with the core network as the RAN UE ID when the UE performs an initial attach is shown;

[0057] Fig.29 shows the detailed configuration of the AMF UE NGAP ID according to an embodiment of the present disclosure;

[0058] Fig.30 shows the configuration of the MME UE S1AP ID according to an embodiment of the present disclosure;

[0059] Fig.31 An example of generating a 64-bit UE identifier by a hash function according to an embodiment of the present disclosure is shown;

[0060] Fig.32 An example in which NRT-RIC manages information related to UE-ID of each RFSP group according to an embodiment of the present disclosure is shown;

[0061] Fig.33 An example in which NRT-RIC manages information related to UE-ID of each SPID group according to an embodiment of the present disclosure is shown;

[0062] Fig.34 Another example of NRT-RIC managing information related to UE-ID of each RFSP group according to an embodiment of the present disclosure is shown;

[0063] Fig.35 Another example of NRT-RIC managing information related to UE-ID of each SPID group according to an embodiment of the present disclosure is shown;

[0064] Fig.36 The RIC UE ID registration table stored by the RIC proposed by the present disclosure according to an embodiment of the present disclosure is shown;

[0065] Fig.37shows an NRT-RIC UE ID registry stored by the NRT-RIC according to an embodiment of the present disclosure; and

[0066] Fig.38 A method for RIC to generate secure hash 5G-GUTI / secure hash GUTI according to an embodiment of the present disclosure is shown.

[0067] Throughout the drawings, like reference numerals will be understood to refer to like parts, components and structures. DETAILED DESCRIPTION

[0068] The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of the various embodiments of the present disclosure as defined by the claims and their equivalents. It includes various specific details to assist in understanding, but these are to be considered as exemplary only. Therefore, it will be appreciated by those of ordinary skill in the art that various changes and modifications to the various embodiments described herein may be made without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and structures may be omitted for clarity and conciseness.

[0069] The terms and words used in the following description and claims are not limited to the bibliographic meanings, but are merely used by the inventor to enable a clear and consistent understanding of the present disclosure. Therefore, it should be apparent to those skilled in the art that the following description of various embodiments of the present disclosure is provided for illustrative purposes only and not for the purpose of limiting the present disclosure as defined by the appended claims and their equivalents.

[0070] It is to be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more of such surfaces.

[0071] By referring to the embodiments described in detail below in conjunction with the accompanying drawings, the advantages and features of the present disclosure and the ways to achieve them will be apparent. However, the present disclosure is not limited to the embodiments set forth below, but can be implemented in various different forms. The following embodiments are provided only to fully disclose the present disclosure and inform those skilled in the art of the scope of the present disclosure, and the present disclosure is limited only by the scope of the attached claims. Throughout the specification, the same or similar reference numerals designate the same or similar elements.

[0072] Here, it will be understood that each frame of the flowchart diagram and the combination of frames in the flowchart diagram can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device create a device for implementing the function specified in the flowchart frame or multiple flowchart frames. These computer program instructions can also be stored in a computer-available or computer-readable memory, wherein the computer program instructions can guide the computer or other programmable data processing device to operate in a particular manner, so that the instructions stored in the computer-available or computer-readable memory produce a product including an instruction device for implementing the function specified in the flowchart frame or multiple flowchart frames. The computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operations are performed on a computer or other programmable device to produce a computer-implemented process, so that the instructions executed on a computer or other programmable device provide operations for implementing the function specified in the flowchart frame or multiple flowchart frames.

[0073] In addition, each frame of the flowchart diagram can represent a module, a code segment or a code portion, which includes one or more executable instructions for implementing (multiple) specified logical functions. It should also be noted that in some alternative implementations, the functions mentioned in the frame may not occur in order. For example, depending on the functions involved, the two frames shown in succession can actually be executed substantially simultaneously, or these frames can sometimes be executed in reverse order.

[0074] As used herein, "unit" refers to a software element or hardware element that performs a predetermined function, such as a Field Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC). However, "unit" does not always have a meaning that is limited to software or hardware. "Unit" can be constructed to be stored in an addressable storage medium or to execute one or more processors. Therefore, "unit" includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcodes, circuits, data, databases, data structures, tables, arrays and parameters. The elements and functions provided by "unit" can be combined into fewer elements or "units", or divided into more elements or "units". In addition, elements and "units" or can be implemented as one or more CPUs in a reproduction device or a secure multimedia card.

[0075] In the present disclosure, an uplink is a radio link through which a terminal (User Equipment (UE) or Mobile Station (MS)) sends data or a control signal to a base station (BS) (or eNode B), and a downlink is a radio link through which a BS sends data or a control signal to a terminal. A BS is an entity that allocates resources to a UE, and may be one of an eNode B, a Node B, a base station (BS), a next generation Node B (gNB), a radio access unit, a base station controller, and a node on a network. A 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.

[0076] Due to the commercialization of the 5th generation communication system (hereinafter, used interchangeably with the 5G system or the new radio or the next generation radio (NR) system) that meets the demand for radio data services, services with high data transmission rates are provided to users through the 5G system as well as the 4G system, and the provision of IoT and wireless communication services for various purposes, such as services requiring high reliability for specific purposes, is predicted.

[0077] In the system currently used with the 4G communication system and the 5G communication system, the Open Radio Access Network (O-RAN) established by service providers and equipment supply companies defines new network elements (NE) and interface standards on the basis of conventional 5GPP standards to create an O-RAN structure. O-RAN newly defines conventional 3GPP NE, RU, DU, CU-CP and CU-UP as O-RU, O-DU, O-CU-CP and O-CU-UP (integrated into O-RAN BS), and additionally standardizes the near real-time RAN intelligent controller (RAN Intelligent Controller, RIC) and the non-real-time RAN intelligent controller (Non-Real-Time RAN Intelligent Controller, NRT-RIC). The newly defined RIC is a logical node that can densely arrange servers in one physical location and can collect information about cell sites sent and received by actual terminals as well as O-DU, O-CU-CP and O-CU-UP (O-RAN BS). The O-DU and RIC may be connected via Ethernet, the O-CU-CP and RIC may be connected via Ethernet, and the O-CU-UP and RIC may be connected via Ethernet. In addition, an interface standard for communication between the O-DU and RIC, between the O-CU-CP and RIC, and between the O-CU-UP and RIC is required, and currently the standards E2-DU, E2-CU-CP, and E2-CU-UP are used between the RIC and the O-CU, the O-CU-CP, and the O-CU-UP, respectively.

[0078] According to the current commercialization of fourth / fifth generation communication systems (hereinafter referred to as 4G / 5G systems, new radio or next generation radio (NR)), it is necessary to support differentiated services for users in virtualized networks, but it is impossible to specify users with respect to cell-related information collected by RAN or O-RAN. The reason is that in the radio access network (RAN) according to the 3GPP standard, there is an identifier of the UE (hereinafter referred to as RAN UE identifier) ​​used by O-DU, O-CU-CP and O-CU-UP, but (unique) information about the user (or information used to specify a user, user identifier or user identity, such as International Mobile Subscriber Identity (IMSI), Subscription Permanent Identifier (SUPI) or Subscription Concealed Identifier (SUCI)) cannot be known.

[0079] Specifically, when the RIC receives UE-specific measurement information and call-related information based on the RAN UE identifier from the O-DU, O-CU-CP, and O-CU-UP, multiple O-CU-CPs may be connected to the RIC, so the RAN UE identifier may overlap, and when the O-CU-CP connected to the UE is changed, the RAN UE identifier may be changed. Therefore, based on the 3GPP standard, in order to specify a user to indicate a user for whom information is collected by the RAN or O-RAN, the RAN and the core network may identify the user, and a user identifier (ID) (interchangeably used with a user identity, a UE identifier, or a UE identity) that can be used by the RAN is required.

[0080] RIC and / or NRT-RIC can identify that the information collected by RAN or O-RAN is for a specific user based on the user identifier. The collected information can be sent from at least one of (O-)CU-CP, (O-)CU-UP and (O-)DU, and the collection server, RIC and / or NRT-RIC can identify that the information collected from different entities is for a specific user based on the user identifier, and determine the key performance indicator (KPI) of the service provided to each user based on the collected information.

[0081] Since it was previously impossible to identify that the collected information was for a specific user, it was not possible to monitor the radio resources of each user. However, in the present disclosure, resources can be optimized for users, and user-specific services or services required by users can be efficiently provided by monitoring the radio resources of specific users. For example, RIC (NRT-RIC or collection server) can efficiently truncate network slices or configure additional carriers to allow specific UEs to receive services through carrier aggregation in order to optimize resources, or additional cells for dual connections can be configured to allow specific UEs to receive services through dual connections. In addition, RIC (NRT-RIC or collection server) can configure a specific UE to avoid connection with a specific cell during movement between cells and connect to a specific cell. In addition, RIC (NRT-RIC or collection server) can efficiently optimize resources by machine learning based on analysis of the collected information. Resource optimization according to the present disclosure is not limited to this description. In addition, according to the present disclosure, not only information of each UE can be collected, but also information of each bearer can be collected.

[0082] In addition, the information collected about a specific user can be used by a collection server, RIC or NRT-RIC, and can be provided to an Operations Support System (OSS) and / or a Business Support System (BSS) and used to provide specialized services to the user.

[0083] Figure 1a A 4G LTE core system according to an embodiment of the present disclosure is shown.

[0084] refer to Figure 1a , an evolved Node B (eNB) 100 as a 4G BS 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 collects status information such as the buffer status, available transmission power, and channel status of the UE 110 to perform scheduling. The MME performs the functions of managing the mobility of the UE and performing various controls. The serving gateway 130 provides a data bearer and generates or controls the data bearer according to the control of the MME. The MME is able to identify the UE internally with a Globally Unique Temporary Identifier (GUTI).

[0085] Carrier aggregation (CA) technology is a technology for aggregating multiple component carriers and allowing one UE to use multiple component carriers simultaneously to send and receive signals, thereby improving frequency usage efficiency from the perspective of the UE or BS. Specifically, according to the CA technology, the UE and the BS can send and receive signals by using the broadband of multiple component carriers in each of the uplink (UL) and the downlink (DL), in which case the respective component carriers are located in different frequency bands. In the following, the uplink is a communication link through which the UE sends a signal to the BS, and the downlink is a communication link through which the BS sends a signal to the UE. At this time, the number of uplink component carriers and the number of downlink component carriers may be different from each other.

[0086] Dual connection / multi-connection technology is a technology in which one UE is connected to multiple different BSs and uses carriers located in different frequency bands within the multiple BSs to simultaneously send and receive signals, thereby improving frequency usage efficiency from the perspective of the UE or BS. The UE can be simultaneously connected to a first BS (for example, a BS providing services using long-term evolution (LTE) technology or fourth-generation mobile communication technology) and a second BS (for example, a BS providing services using new radio (NR) technology or fifth-generation mobile communication technology) to send and receive services. In this case, the frequency resources used by the BSs can be located in different frequency bands. As described above, the operating scheme of dual connection based on LTE and NR can be referred to as 5G non-standalone (5G Non-Standalone, 5GNSA).

[0087] Figure 1b An example of a 5G NAS system according to an embodiment of the present disclosure is shown.

[0088] refer to Figure 1b , a 5G NSA system may include EPC 150 LTE 160 (or may be used interchangeably with LTE BS or eNB), NR 170 (or may be used interchangeably with NR BS or gNB), and UE 180. LTE BS 160 and NR BS 170 may be connected to EPC 150, and UE 180 may receive services from LTE 160 and NR 170 at the same time.

[0089] In this case, the UE can perform an RRC connection through the first BS, receive functions provided in the control plane (e.g., connection management or mobility management functions), and receive additional radio resources for sending and receiving data through the second BS. The dual connection technology may be referred to as Evolved Universal Terrestrial Radio Access (EN-DC)-NR dual connection. The present disclosure is not limited to EN-DC, and may be applied to NR-E-UTRA dual connection (NE-DC) in which the first BS uses NR and the second BS uses LTE, as well as any multi-connection in various forms. In addition, the present disclosure may be applied to carrier aggregation.

[0090] Furthermore, the present disclosure may 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 a case where a first BS and a second BS are located in the same geographical location.

[0091] Figure 2 An International Mobile Subscriber Identity (IMSI) which is a unique identifier of a UE commonly used by all 3G, 4G, and 5G systems defined in ITU-T according to an embodiment of the present disclosure is shown.

[0092] refer to Figure 2 , a UE can be uniquely identified globally by IMSI 200. IMSI includes a Mobile Country Code (MCC) 210, a Mobile Network Code (MNC) 220, and a Mobile Subscriber Identification Number (MSIN) 230. MCC is an identifier for identifying countries around the world, and MNC is an identifier for identifying a Public Land Mobile Network (PLMN) (which can be used interchangeably with an operator). MSIN is an identifier for identifying a UE within a PLMN.

[0093] Figure 3 A GUTI used in a 4G LTE core system according to an embodiment of the present disclosure is shown.

[0094] refer to Figure 3, GUTI 300 is an identifier for identifying a specific UE in a core network (which can be used interchangeably with network) including multiple MMEs. GUTI includes a globally unique MME identifier (Globally Unique MME Identifier, GUMMEI) 310 and an M-temporary mobile user identifier (Temporary Mobile Subscription Identifier, TMSI) 320. GUMMEI includes MCC 330, MNC 340 and MME identifier 350. The MME identifier includes an MME group ID 360 and an MME code 370. The MME group ID indicates an MME group including multiple MMEs, and the MME code indicates a specific MME. M-TMSI 320 is an MME-TMSI and can uniquely identify a UE only within an MME. SAE-Temporary Mobile Subscriber Identity (SAE-Temporary Mobile Subscriber Identity, S-TMSI) 380 can be generated by a combination of an MME code and an M-TMSI, and is a temporary UE identifier for an MME to identify a user within an MME group.

[0095] Figure 4 A 5G NR core system according to an embodiment of the present disclosure is shown.

[0096] refer to Figure 4 , the 5G core system 460 may include network functions such as access and mobility management function (AMF) 430, session management function (SMF) 440, and user plane function (UPF) 450. AMF provides access and mobility management functions in units of UE 420, which may be similar to the role of MME of the LTE core network. SMF provides session management functions, and UPF delivers downlink data received from a data network (not shown) to the UE via gNB 400, and delivers uplink data received from the UE to the data network via gNB.

[0097] The 5G BS (generation Node B (gNB)) 400 can be logically divided into a radio unit (Radio Unit, RU) 410 that performs physical layer functions, a digital unit (Digital Unit, DU) 402 that performs medium access control (Medium Access Control, MAC) and radio link control (Radio Link Control, RLC) functions, a central unit control plane (Central Unit-Control Plane, CU-CP) 404 that performs high-level functions such as Radio Resource Control (Radio Resource Control, RRC) and Packet Data Convergence Protocol (Packet Data Convergence Protocol, PDCP) and a central unit user plane (Central Unit-User Plane, CU-UP) function 406. CU-CP performs functions related to the control plane, and specifically, can perform functions related to connection establishment, mobility, and security. CU-UP can perform user data transmission / reception related functions as functions related to the user plane. The gNB is connected to the AMF, and multiple AMFs of the 5G core network exist in the service provider network.

[0098] Figure 5 The structure of a 5G-Globally Unique Temporary Identifier (5G-GUTI) used in a 5G core system according to an embodiment of the present disclosure is shown.

[0099] refer to Figure 5 , 5G-GUTI 500 is an identifier for identifying a specific UE in a 5G core network including multiple AMFs, and the 5G-GUTI includes a globally unique AMF identifier (GUAMI) 510 and a 5G-temporary mobile user identifier (5G-TMSI) 520. GUAMI includes an MCC 530, an MNC 540, and an AMF identifier 560. The AMF identifier includes an AMF area ID 560, an AMF set ID 570, and an AMF pointer 580. The AMF area ID indicates an AMF set including multiple AMFs, the AMF set ID indicates a specific AMF set within the AMF area, and the AMF pointer indicates a specific AMF within the AMF set. 5G-TMSI is an identifier for uniquely identifying a UE in only the AMF pointer. 5G SAE-Temporary Mobile User Identity (5G-S-TMSI) 590 may include a combination of an AMF set ID, an AMF pointer, and a 5G-TMSI, and may be used to perform wireless signaling more efficiently in a short form of the 5G-GUTI.

[0100] Figure 6 An O-RAN network system according to an embodiment of the present disclosure is shown.

[0101] refer to Figure 6 The O-RAN network is a standard that logically separates the eNB and gNB functions of traditional 4G and 5G, and newly defines a non-real-time RAN intelligent controller (NRT-RIC) 600, a near real-time (RIC) RAN intelligent controller 610, an O-CU-CP 620, an O-CU-UP 630, and an O-DU 640 in the O-RAN standard. The O-CU including the O-CU-CP and the O-CU-UP is a logical node that provides the functions of RRC, Service Data Adaptation Protocol (SDAP) and PDCP, the O-CU-CP is a logical node that provides the functions of the control plane part of RRC and PDCP, the O-CU-UP is a logical node that provides the functions of the user plane part of SDAP and PDCP, the O-DU is a logical node that provides the functions of RLC, MAC and high physical layer (high-PHY based on 7-2x fronthaul split), and the O-RU connected to the O-DU, not shown, is a logical node that provides the functions of the low physical layer (low-PHY based on 7-2x fronthaul split) and RF processing.

[0102] NRT-RIC is a logical node that allows non-real-time control instead of real-time control, optimization of RAN elements and resources, model training and updating, and RIC is a logical node that allows near real-time control and optimization of RAN elements and resources based on data collected from O-DU, O-CU-CP and O-CU-UP through the E2 interface.

[0103] The present disclosure is not limited to the name of each node mentioned above, and the configuration of the present disclosure can be applied to the logical node or entity that performs the above functions. The logical node can be located in the same physical location or different locations, and its function can be provided by the same physical device (e.g., processor or controller) or different physical devices. For example, a physical device can provide the function of at least one logical node through virtualization.

[0104] Figure 7 An example of connection between multiple nodes (such as O-RAN RIC and O-CU-CP, O-CU-UP and O-DU) according to an embodiment of the present disclosure is shown.

[0105] refer to Figure 7, one RIC 700 can be connected to multiple nodes, such as O-CU-CP 720, O-CU-UP 710, and O-DU 730, and can be connected to each node through E2-CP interface 750, E2-UP interface 760, and E2-DU interface 740. In addition, the interface between O-CU-CP and DU and between O-CU-UP and DU can be referred to as F1 interface 770. Hereinafter, DU can be used interchangeably with O-DU, CU-CP can be used interchangeably with O-CU-CP, and CU-UP can be used interchangeably with O-CU-UP. In addition, eNB can be used interchangeably with O-RAN eNB, and gNB can be used interchangeably with O-RAN gNB. Although Figure 7 Only one RIC 700 is shown, but there may be multiple RICs, which may be implemented as multiple hardware located at the same physical site, or by virtualization using one hardware.

[0106] Figure 8 The process of the CU-CP of the 5G RAN defined in 3GPP according to an embodiment of the present disclosure acquiring the 5G-GUTI is shown.

[0107] refer to Figure 8 In operation 800, UE 801 inserts the upper 39 bits of the 5G SAE temporary mobile user identity (5G-S-TMSI) value allocated by the 5G core network in the initial setup into the RRCSetupRequest message according to the call access procedure defined in the 3GPP standard, and sends the RRCSetupRequest message to DU 802. In operation 810, DU 802 inserts the upper 39 bits of the 5G-S-TMSI value received in operation 800 into the F1 initial UL RRC message delivery message according to the call access procedure defined in the 3GPP standard, and sends the F1 initial UL RRC message delivery message to CU-CP 804. In operation 820, CU-CP 804 stores the upper 39 bits of the 5G-S-TMSI value inserted into the F1 message and sent by DU 802. Thereafter, CU-CP delivers a DL RRC message to DU 802, and the DU sends an RRCSetup message (or an RRCReject message) to UE 801.

[0108] When DU 802 sends the RRCSetup message, in operation 830, UE 801 inserts the lower 9 bits of the 5G-S-TMSI value allocated by the core network in the initial establishment into the RRCSetupComplete message according to the call access procedure defined in the 3GPP standard, and sends the RRCSetupComplete message to the DU. In operation 840, DU 802 inserts the lower 9 bits of the 5G-S-TMSI value received in the fourth process into the F1 UL RRC message delivery message according to the call access procedure defined in the 3GPP standard, and sends the F1 UL RRC message delivery message to CU-CP 804. In operation 850, CU-CP 804 stores the lower 9 bits of the 5G-S-TMSI value inserted into the F1 message and sent by DU 802. Thereafter, CU-CP sends an initial UE message to AMF 805.

[0109] In operation 860, the CU-CP 804 stores the GUAMI value inserted into the NGAP INITIAL CONTEXT SETUP REQUEST message and sent by the AMF 805 according to the call access procedure defined in the 3GPP standard. In operation 870, the CU-CP 804 identifies the 5G-TMSI based on the upper 39 bits and lower 9 bits of the 5G-S-TMSI stored in operations 820 and 850, and generates a 5G-GUTI by concatenating the 5G-TMSI with the lower part of the GUAMI received in operation 860.

[0110] In this process, operations do not have to be performed sequentially, or all operations do not have to be performed, and their order may be changed or specific operations may be omitted. Figure 8 Another configuration shown in FIG. 1 may be added to the process, or a process shown in another figure may be combined with the process shown in FIG. Figure 8 The process combination shown in .

[0111] Fig. 9 The process of the O-CU-CP of the 5G RAN acquiring the 5G-GUTI defined in the O-RAN according to an embodiment of the present disclosure is shown.

[0112] refer to Fig. 9In operation 900, the UE 901 inserts the upper 39 bits of the 5G-S-TMSI value allocated by the core network into the RRCSetupRequest message in the initial establishment according to the call access procedure defined in the 3GPP standard, and sends the RRCSetupRequest message to the O-DU 902. In operation 910, the O-DU inserts the upper 39 bits of the 5G-S-TMSI value received in operation 900 into the F1 initial UL RRC messaging message according to the call access procedure defined in the 3GPP standard, and sends the F1 initial UL RRC messaging message to the O-CU-CP 904. In operation 920, the O-CU-CP 904 stores the upper 39 bits of the 5G-S-TMSI value inserted into the F1 message and sent by the O-DU 902. Thereafter, the O-CU-CP 904 delivers a DL RRC message to the O-DU 902 , and the O-DU 902 sends an RRCSetup message (or an RRCReject message) to the UE 901 .

[0113] When the O-DU 902 sends the RRCSetup message, in operation 930, the UE 901 inserts the lower 9 bits of the 5G-S-TMSI value allocated by the core network in the initial setup into the RRCSetupComplete message according to the call access procedure defined in the 3GPP standard, and sends the RRCSetupComplete message to the O-DU 902. In operation 940, the O-DU 902 inserts the lower 9 bits of the 5G-S-TMSI value received in the fourth process into the F1 UL RRC messaging message according to the call access procedure defined in the 3GPP standard, and sends the F1 UL RRC messaging message to the O-CU-CP 904. In operation 950, the O-CU-CP 904 stores the lower 9 bits of the 5G-S-TMSI value inserted into the F1 message and sent by the O-DU 902.

[0114] Thereafter, in operation 960, the O-CU-CP sends an initial UE message to the AMF 905, and stores the GUAMI value inserted into the NGAP INITIAL CONTEXT SETUP REQUEST message and sent by the AMF 905 according to the call access procedure defined in the 3GPP standard. In operation 970, the O-CU-CP identifies the 5G-TMSI based on the upper 39 bits and lower 9 bits of the 5G-S-TMSI stored in operations 920 and 950, and generates a 5G-GUTI by concatenating the 5G-TMSI with the lower part of the GUAMI received in operation 960.

[0115] In this process, operations do not have to be performed sequentially, or all operations do not have to be performed, and their order may be changed or specific operations may be omitted. Fig. 9 Another configuration shown in FIG. 1 may be added to the process, or a process shown in another figure may be combined with the process shown in FIG. Fig. 9 The process combination shown in .

[0116] Fig.10 The process of obtaining GUTI by an eNB of a 4G RAN defined in 3GPP according to an embodiment of the present disclosure is shown.

[0117] refer to Fig.10 In operation 1000, UE 1001 inserts 40 bits of the S-TMSI value allocated by the core network into the RRC connection request message in the initial establishment according to the call access procedure defined in the 3GPP standard, and sends the RRC connection request message to eNB 1002. In operation 1010, eNB 1002 stores the S-TMSI value sent by UE 1001. Thereafter, eNB 1002 sends an RRCConnectionSetup message to UE 1001, and UE 1001 sends an RRCConnectionSetupComplete message to eNB 1002 in response thereto. Thereafter, eNB 1002 sends an initial UE message to MME 1003. In operation 1020, eNB 1002 stores the GUMMEI value inserted into the S1APINITIALCONTEXTSETUPREQUEST message and sent by MME 1003 according to the call access procedure defined in the 3GPP standard. In operation 1030 , the eNB 1002 identifies an MME Temporary Mobile Subscriber Identity (M-TMSI) based on the S-TMSI stored in operation 1010 , and generates a GUTI by concatenating the M-TMSI with a lower portion of the GUMMEI received in operation 1020 .

[0118] In this process, operations do not have to be performed sequentially, or all operations do not have to be performed, and their order may be changed or specific operations may be omitted. Fig.10 Another configuration shown in FIG. 1 may be added to the process, or a process shown in another figure may be combined with the process shown in FIG. Fig.10 The process combination shown in .

[0119] Fig.11 The process of obtaining the GUTI by the eNB of the 4G O-RAN defined in the O-RAN according to an embodiment of the present disclosure is shown.

[0120] refer to Fig.11In operation 1100, UE 1101 inserts 40 bits of the S-TMSI value allocated by the core network into the RRC connection request message in the initial establishment according to the call access procedure defined in the 3GPP standard, and sends the RRC connection request message to the eNB 1102 of the O-RAN. In operation 1110, the eNB 1102 stores the S-TMSI value sent by the UE 1101. Thereafter, the eNB 1102 sends an RRCConnectionSetup message to the UE 1101, and the UE 1101 sends an RRCConnectionSetupComplete message to the eNB 1102 in response thereto. Thereafter, the eNB 1102 sends an initial UE message to the MME 1103. In operation 1120, the eNB 1102 of the O-RAN stores the GUMMEI value inserted into the S1AP INITIAL CONTEXT SETUP REQUEST message and transmitted by the MME 1103 according to the call access procedure defined in the 3GPP standard. In operation 1130, the eNB 1102 of the O-RAN identifies the M-TMSI based on the S-TMSI stored in operation 1110, and generates a GUTI by concatenating the GUMMEI received in operation 1120 with the lower part of the M-TMSI.

[0121] In this process, operations do not have to be performed sequentially, or all operations do not have to be performed, and their order may be changed or specific operations may be omitted. Fig.11 Another configuration shown in FIG. 1 may be added to the process, or a process shown in another figure may be combined with the process shown in FIG. Fig.11 The process combination shown in .

[0122] Fig.12 A configuration is shown in which an eNB of a 4G RAN defined in 3GPP according to an embodiment of the present disclosure generates a GUTI based on an S-TMSI received from a UE and a GUMMEI received from an MME.

[0123] refer to Fig.12 , the eNB identifies the M-TMSI 1220 by applying a mask of the lower 32 bits to the S-TMSI 1200. The eNB generates the GUTI 1230 by concatenating the GUMMEI 1210 before the M-TMSI 1220. At this time, the method of generating the GUTI 1230 is not limited to masking, and the GUTI 1230 may be generated by various methods based on the S-TMSI 1200 and the GUMMEI 1210.

[0124] Fig.13The configuration in which the CU-CP of the 5G RAN defined in 3GPP according to an embodiment of the present disclosure generates a 5G-GUTI based on the 5G-S-TMSI received from the UE and the GUAMI received from the AMF is shown.

[0125] refer to Fig.13 , the CU-CP identifies the 5G-TMSI 1320 by applying a mask of the lower 32 bits to the 5G-S-TMSI 1300. The CU-CP generates the 5G-GUTI 1330 by concatenating the GUAMI 1310 before the 5G-TMSI. At this time, the method of generating the 5G-GUTI 1330 is not limited to masking, and the GUTI can be generated by various methods based on the 5G-S-TMSI 1300 and the GUAMI 1310.

[0126] Fig.14 A process in which the RIC defined in the O-RAN receives information classified for a specific UE from the O-DU and the O-CU-CP according to an embodiment of the present disclosure is shown.

[0127] refer to Fig.14 In operation 1400, O-CU-CP 1402 generates a 5G-GUTI by communicating with the UE and AMF. The 5G-GUTI may be generated by the above method. In operation 1410, RIC 1403 sends an E2-CP RICSUBSCRIPTION REQUEST message defined in O-RAN to O-CU-CP 1402, and sends a report classified for a specific UE when a specific event is generated. In operation 1420, O-CU-CP 1402 processes the request to RIC 1403 configured in operation 1410, and inserts the RAN UE ID defined in 3GPP and the 5G-GUTI mapped to the RAN UE ID configured in operation 1400 into the E2 E2-CP RIC SUBSCRIPTION RESPONSE message, and sends the E2-CP RICSUBSCRIPTION RESPONSE message to RIC 1403.

[0128] RIC 1403 can identify the UE for which information is collected (ie, the 5G-GUTI that the UE has) based on the mapping relationship between RNAUE ID and 5G-GUTI. A detailed description thereof will be described below.

[0129] RAN UE ID is a temporary UE identifier defined in 3GPP and corresponds to a UE identifier used between CU-CP, CU-UP and DU. This can be configured between nodes in the establishment of the F1 interface, used to identify a specific UE between nodes and report call-related information and measurement-related information to a specific UE, and is defined to have 64 bits. RAN UE ID is a UE identifier temporarily determined within the O-RAN BS and can be configured by the service provider for Operation Administration Maintenance (OAM). For a specific example, the RAN UE ID can be used to report Call Summary Log (CSL) information to a call log collection server. O-CU-CP 1402 can configure the RAN UE ID in any way. For example, the RAN UE ID can be included in the UE context establishment request message and the UE context establishment response message sent and received between the DU and the CU, and can be included in the bearer context modification request message and the bearer context modification failure message sent and received between the CU-CP and the CU-UP. In another example, the RAN UE ID may be included in a handover request message and a handover request confirm message sent and received by the source gNB and the target gNB, may be included in a retrieve UE context request message and a retrieve UE context response message of the old gNB and the new gNB, may be included in a handover request message and a handover command message between the source gNB and the AMF, may be included in an S-node add request message and an S-node request confirm message between the primary gNB and the second gNB, may be included in an initial UE message sent by the gNB to the AMF, and may be included in a handover request message and a handover request confirm message between the target gNB and the AMF.

[0130] The present disclosure describes an example in which the RAN UE ID and the 5G GUTI are inserted into the E2-CP RICSUBSCRIPTION RESPONSE message and sent, and the O-CU-CP 1402 may configure the RAN UE ID based on a combination of the 5G-GUTI and a value shared with the core network for uniquely identifying the UE or a combination of the GUAMI and a value shared with the core network for identifying the UE. In a 5G network, User Data Management (UDM) stores a user's permanent ID, a subscription permanent ID (SUPI), subscription data, and policy data, and the AMF stores mapping information between the SUPI and the 5G-GUTI or mapping information between the RAN UE ID, the 5G-GUTI, and the SUPI. The value shared with the core network for identifying the UE may be based on the mapping information. The AMF may store mapping information between a value for identifying the UE and an identifier (such as a 5GGUTI or SUPI) for globally and uniquely identifying the UE.

[0131] In this case, the RAN UE ID may be determined by a function (or rule) having one or more parameters including 5G-GUTI (or a value shared with the core network for uniquely identifying the UE or a combination of GUAMI and a value shared with the core network for identifying the UE, and hereinafter, 5G-GUTI may be understood as one of 5G-GUTI, a value shared with the core network for uniquely identifying the UE, or a combination of GUAMI and a value shared with the core network for identifying the UE) as a key, and the function may be predetermined or preconfigured. In this case, the RIC 1403 may acquire the 5G-GUTI value of the specific UE according to a predetermined or preconfigured function (or rule) based on the received RANUE ID of the specific UE. The O-CU-CP 1402 may send only the RAN UE ID and / or 5G-GUTI to the RIC 1403, or, in addition to the RAN UE ID and / or 5G-GUTI, also send parameters used to generate the RAN UE ID from the 5G-GUTI. Alternatively, the maximum length of the currently defined RAN UE ID is 64 bits, and the length of the 5G-GUTI is 62 bits, so the O-CU-CP 1402 may configure the content of the RAN UE ID to be the same as the 5G-GUTI. In the above case, or when the value for identifying the UE shared with the core network including the GUAMI is used as the RAN UE ID, the O-CU-CP 1402 may send only the RAN UE ID to the RIC. This method is not limited to Fig.14 of examples, and can be applied throughout the disclosure.

[0132] The O-CU-CP 1402 may send the RAN UE ID (and 5G-GUTI) through another message other than the E2 E2-CP RIC SUBSCRIPTION RESPONSE message, and the present disclosure may be applied to this case.

[0133] In operation 1430, the RIC sends an E2-DU RICSUBSCRIPTION REQUEST message defined in the O-RAN standard to the O-DU 1401, and when a specific event is generated, sends a report classified for each specific UE. In operation 1440, the O-DU 1401 processes the request from the RIC 1403 in operation 1430, and inserts the RAN UE ID and the report of each RANID into the E2-DU RIC SUBSCRIPTION RESPONSE, and sends the E2-DU RIC SUBSCRIPTION RESPONSE to the RIC 1403. The report is UE related information, and specifically UE related measurement information, and may include at least one of DU resource status information, UE KPI related information (including at least one of throughput and latency related information). The report is not limited to Fig.14 of examples, and can be applied throughout the disclosure.

[0134] When the preset event of operation 1410 is generated, in operation 1460, O-CU-CP 1402 sends information classified for each RAN UE ID to RIC 1403 through an E2-CP INDICATION message defined in O-RAN. The information may include one or more RAN UE IDs and information of each RAN UE ID. The information may belong to at least one of KPI related information and UE context information of each UE in CU-CP, and may be applied to the entire disclosure without limitation. Fig.14 .

[0135] When the preset event of operation 1410 is generated, in operation 1460, the O-DU 1401 transmits information classified for each RAN UE ID to the RIC 1403 through an E2-DU INDICATION message defined in O-RAN. The information may include one or more RAN UE IDs and information of each RAN UE ID.

[0136] The RIC 1403 identifies the 5G-GUTI associated with the RAN UE ID, and stores information about each RAN UE ID transmitted by the O-CU-CP 1402 and the O-DU 1401 in operations 1450 and 1460 to be associated with the 5G-GUTI. That is, for one 5G-GUTI, information about a specific user transmitted by each of the O-CU-CP 1402 and the O-DU 1401 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 1403, the RAN UE IDs transmitted by the O-CU-CP 1402 and the O-DU 1401 may overlap with each other. The RIC 1403 may identify the 5G-GUTI based on the port information of the O-CU-CP 1402 and / or the O-DU 1401 that sends the RAN UE ID (and information about it), or may identify the 5G-GUTI based on the RAN function ID and the RAN UE ID of the O-CU-CP 1402 and / or the O-DU 1401.

[0137] RAN UE ID is only an example of a specific user identifier of O-RAN, and a specific user identifier (or UE identifier) ​​of O-RAN can be used in the present disclosure. 5G-GUTI is only an example of a globally unique identifier of a UE (or user), and a globally unique identifier of a UE (or user) can be used in the present disclosure.

[0138] In this process, operations do not have to be performed in order, or all operations do not have to be performed, and their order may be changed or certain operations may be omitted. In addition to the products described, Fig.14 Another component shown in FIG. 1 may be executed, and a process shown in another figure may be executed in Fig.14 The process combination shown in Fig.14 The names of the messages shown in are merely examples, and the configuration of the present disclosure may be applied to methods and messages similar to those used in the present disclosure.

[0139] Fig.15 A process in which NRT-RIC defined in O-RAN receives information classified for a specific UE from O-DU, O-CU-CP, and RIC according to an embodiment of the present disclosure is shown.

[0140] refer to Fig.15In operation 1500, O-DU 1501, O-CU-UP 1502, O-CU-CP 1503, and RIC 1504 transmit information about each UE identified by RAN UE ID and information about each cell to NRT-RIC 1505 through an O1 message defined in O-RAN. RIC 1504 also transmits 5G-GUTI information having a mapping relationship with RAN UE ID together with RAN UE ID. (Although not shown), the information transmitted by RIC 1504 may be measurement information of each UE received from O-DU 1501, O-CU-CP 1503, and O-CU-UP 1502 together with RAN UE ID. The xApps of RIC 1504 processes the received information of each UE and transmits the processed information of each UE together with RAN UE ID and / or 5G-GUTI to NRT-RIC 1505.

[0141] NRT-RIC 1505 collects information of each RAN UE ID transmitted by O-DU 1501, O-CU-UP 1502, O-CU-CP 1503, and RIC 1504 through the O-1 interface, connects to the 5G-GUTI transmitted by RIC 1504, and stores the information. That is, NRT-RIC 1505 may also store information corresponding to each user transmitted by O-DU 1501, O-CU-UP 1502, O-CU-CP 1503, and RIC 1504 based on 5G-GUTI. In addition, NRT-RIC 1505 may provide the collected information to OSS and / or BSS.

[0142] The RAN UE ID may be configured based on the 5G-GUTI (in this case, the NRT-RIC 1505 may acquire the 5G-GUTI based on the RAN UE ID according to a predetermined or preset rule), or may be configured such that the content of the RAN UE ID is the same as the 5G-GUTI, because the maximum length of the RAN UE ID currently defined is 64 bits, and the length of the 5G-GUTI is 62 bits. In this case, the RIC 1504 may send only the RAN UE ID to the RIC 1504.

[0143] RAN UE ID is only an example of a specific user identifier of O-RAN, and a specific user identifier (or UE identifier) ​​of O-RAN can be used in the present disclosure. 5G-GUTI is only an example of a globally unique identifier of a UE (or user), and a globally unique identifier of a UE (or user) can be used in the present disclosure.

[0144] In this process, operations do not have to be performed sequentially, or all operations do not have to be performed, and their order may be changed or specific operations may be omitted. Fig.15 Another configuration shown in FIG. 1 may be added to the process, or a process shown in another figure may be combined with the process shown in FIG. Fig.15 The process combination shown in Fig.15 The names of the messages shown in are merely examples, and the configuration of the present disclosure may be applied to methods and messages similar to those used in the present disclosure.

[0145] Fig.16 A process in which a collecting server receives information classified for a specific UE from DU, CU-UP, and CU-CP defined in 3GPP according to an embodiment of the present disclosure is shown.

[0146] refer to Fig.16 In operation 1600, the CU-CP 1603 generates a 5G-GUTI by communicating with the UE and the AMF. The method may be performed as the same as the above method. In operation 1610, the collection server 1604 sends a SUBSCRIPTION REQUEST message to the CU-CP 1603, and when a specific event is generated, a report classified for each specific UE is sent. In operation 1620, the CU-CP 1603 processes the request (SUBSCRIPTIONRESPONSE message) to the collection server configured in operation 1610, in which case the RAN UE ID defined in 3GPP and the 5G-GUTI mapped to the RAN UE ID and configured in operation 1600 are also sent to the collection server.

[0147] The collection server can identify the UE for which information is collected (i.e., the 5G-GUTI that the UE has) based on the mapping relationship between the RAN UE ID and the 5G-GUTI. A detailed description thereof will be described below. The RAN UE ID is a unique value within the 3GPP 5G NRBS and can be configured as OAM by the service provider.

[0148] Although the present disclosure describes an example of sending the RAN UE ID and the 5G-GUTI through the SUBSCRIPTION RESPONSE message, the CU-CP 1603 may configure the RAN UE ID based on the 5G-GUTI (in this case, the 5G-GUTI may be acquired according to a predetermined or preset rule based on the RAN UE ID received by the RIC), or the CU-CP 1603 may configure the content of the RAN UE ID to be the same as the 5G-GUTI, because the maximum length of the RAN UE ID currently defined is 64 bits, and the length of the 5G-GUTI is 62 bits. In this case, the CU-CP 1603 may send only the RAN UE ID to the RIC.

[0149] In addition, the CU-CP 1603 may send the RAN UE ID (and 5G-GUTI) to the collection server through a message other than the SUBSCRIPTION RESPONSE message, and the present disclosure may be applied to this case.

[0150] In operation 1630, the collection server may send a SUBSCRIPTION REQUEST message to the CU-UP 1602, and when a specific event is generated, a report classified for each specific UE is sent to the collection server. In operation 1640, the CU-UP 1602 may process the request according to operation 1630, insert the RAN UE ID defined in 3GPP and the report for each RAN UE ID (UE related information) into the SUBSCRIPTION RESPONSE message, and send the SUBSCRIPTION RESPONSE message.

[0151] In operation 1650, the collection server sends a SUBSCRIPTION REQUEST message to the DU 1601, and when a specific event is generated, a report classified for each specific UE is sent to the collection server. In operation 1660, the DU 1601 processes the request according to the sixth procedure, inserts the RAN UE ID defined in 3GPP and the report for each RAN UE ID (UE related information) into the SUBSCRIPTION RESPONSE message, and sends the SUBSCRIPTION RESPONSE message to the collection server.

[0152] When a preset event is generated in operation 1610, the CU-CP 1603 transmits information classified for each RAN UE ID to the collection server through an indication message defined by the collection server in operation 1670. The information may include one or more RAN UE IDs and information of each RAN UE ID.

[0153] When a preset event is generated in operation 1630, CU-UP 1602 transmits information classified for each RAN UE ID to the collection server through an indication message defined by the collection server in operation 1680. The information may include one or more RAN UE IDs and information of each RAN UE ID.

[0154] When a preset event is generated in operation 1650, DU 1601 transmits information classified for each RAN UE ID to the collection server through an indication message defined by the collection server in operation 1690. The information may include one or more RAN UE IDs and information of each RAN UE ID.

[0155] The collection server identifies the 5G-GUTI associated with the RAN UE ID, and stores information about each RAN UE ID transmitted by the CU-CP 1603, the CU-UP 1602, and the DU 1601 in operations 1620, 1640, and 1650 to be associated with the 5G-GUTI. That is, for one 5G-GUTI, information about a specific user transmitted by each of the CU-CP 1603, the CU-UP 1602, and the DU 1601 may be stored. At this time, since a plurality of CU-CPs and CU-UPs and a plurality of DUs may be connected to the collection server, the RAN UE IDs transmitted by the CU-CP 1603, the CU-UP 1602, and the DU 1601 may be comprehensive with each other. The collection server can identify the 5G-GUTI based on the port information of the CU-CP 1603, CU-UP 1602 and / or DU 1601 that sends the RAN UE ID (and information about it) and the RAN UE ID, or identify the 5G-GUTI based on the RAN function ID and RAN UE ID of the CU-CP 1603, CU-UP 1602 and / or DU 1601.

[0156] In this process, operations do not have to be performed sequentially, or all operations do not have to be performed, and their order may be changed or specific operations may be omitted. Fig.16 Another configuration shown in FIG. 1 may be added to the process, or a process shown in another figure may be combined with the process shown in FIG. Fig.16 The process combination shown in Fig.16 The names of the messages shown in are merely examples, and the configuration of the present disclosure may be applied to methods and messages similar to those used in the present disclosure.

[0157] Fig.17A process in which the RIC receives information classified for a specific UE from the O-DU, O-CU-UP, and OC-CP defined in the O-RAN according to an embodiment of the present disclosure is shown.

[0158] refer to Fig.17 , in operation 1700, O-CU-CP 1703 generates a 5G GUTI by communicating with the UE and AMF. The 5G-GUTI may be generated by the above method. In operation 1710, RIC 1704 sends an E2SUBSCRIPTION REQUEST message defined in O-RAN to O-CU-CP 1703, and sends a report classified for a specific UE when a specific event is generated. In operation 1720, O-CU-CP 1703 processes the request of RIC 1704 according to operation 1710, and inserts the RAN UE ID defined in 3GPP and the 5G-GUTI preset in the first process and mapped to the RAN UE ID into the E2SUBSCRIPTION RESPONSE message, and sends the E2SUBSCRIPTION RESPONSE message to RIC 1704.

[0159] RIC 1704 can identify the UE for which information is collected (i.e., the 5G-GUTI that the UE has) based on the mapping relationship between the RAN UE ID and the 5G-GUTI. A detailed description thereof will be described below. The RAN UE ID is a unique value within the 3GPP 5G NRBS and can be configured by the service provider as OAM.

[0160] Although the present disclosure describes an example of sending the RAN UE ID and the 5G GUTI through the E2 E2-CP RIC SUBSCRIPTION RESPONSE message, the O-CU-CP 1703 may configure the RAN UE ID based on the 5G-GUTI (in this case, the 5G-GUTI may be acquired according to a predetermined or preset rule based on the RAN UE ID received by the RIC 1704), or the O-CU-CP 1703 may configure the content of the RAN UE ID to be the same as the 5G-GUTI, because the maximum length of the RAN UE ID currently defined is 64 bits, and the length of the 5G-GUTI is 62 bits. In this case, the O-CU-CP 1703 may send only the RAN UE ID to the RIC 1704.

[0161] In addition, the O-CU-CP 1703 may send the RAN UE ID (and 5G-GUTI) to the RIC 1704 through a message other than the E2 E2-CP RIC SUBSCRIPTION RESPONSE message, and the present disclosure may be applied to this case.

[0162] In operation 1730, RIC 1704 may send an E2 SUBSCRIPTION REQUEST message defined in O-RAN to O-CU-UP 1702, and when a specific event is generated, a report classified for each specific UE is sent to RIC 1704. In operation 1740, O-CU-UP 1702 processes the request of RIC 1704 in operation 1730, and sends a RAN UE ID defined in 3GPP and information about each RAN UE ID to RIC 1704 together with the SUBSCRIPTION RESPONSE message.

[0163] In operation 1750, the RIC 1704 transmits an E2 SUBSCRIPTION REQUEST message to the O-DU 1701, and when a specific event is generated, a report classified for each specific UE is transmitted to the RIC 1704. In operation 1760, the O-DU 1701 processes the request from the RIC 1704 in operation 1750, and transmits the RAN UE ID defined in 3GPP and information on each RANUE ID to the RIC 1704 together with the SUBSCRPTION RESPONSE message.

[0164] When a preset event is generated in operation 1710, in operation 1770, the O-CU-CP 1703 sends information classified for each RAN UE ID to the RIC 1704 through an E2 indication message defined by the RIC 1704. The information may include one or more RAN UE IDs and information of each RAN UE ID. When a preset event is generated in operation 1730, in operation 1780, the O-CU-CP 1703 sends information classified for each RAN UE ID to the RIC 1704 through an E2 indication message defined by the RIC 1704. The information may include one or more RAN UE IDs and information of each RAN UE ID. The information may include at least one of resource status information (buffer status) in the CU-UP, bearer status information such as the number of bearers, CPU usage status, and KPI related information (throughput and delay of UE), and may be applied to the entire disclosure without limitation. Fig.17 .

[0165] When a preset event is generated in operation 1750, in operation 1790, the O-DU 1701 transmits information classified for each RAN UE ID to the RIC 1704 through an indication message defined by the RIC 1704. The information may include one or more RAN UE IDs and information of each RAN UE ID.

[0166] The RIC 1704 identifies the 5G-GUTI associated with the RAN UE ID, and stores information of each RAN UE ID transmitted by the O-CU-CP 1703, the O-CU-UP 1702, and the O-DU 1701 in operations 1720, 1740, and 1760 to be associated with the 5G-GUTI. That is, for one 5G-GUTI, information about a specific user transmitted by each of the O-CU-CP 1703 and the O-DU 1701 may be stored.

[0167] At this time, since a plurality of O-CU-CPs and O-CU-UPs and a plurality of O-DUs may be connected to the RIC 1704, the RAN UE IDs transmitted by the O-CU-CP 1703, the O-CU-UP 1702, and the O-DU 1701 may overlap with each other. At this time, the RIC 1704 may identify the 5G-GUTI based on the port information of the O-CU-CP 1703, the O-CU-UP 1702, and / or the O-DU 1701 that transmits the RAN UE ID (and information related thereto) and the RAN UE ID, or configure the 5G-GUTI based on the RAN function ID and the RAN UE ID of the O-CU-CP 1703, the O-CU-UP 1702, and / or the O-DU.

[0168] RAN UE ID is only an example of a specific user identifier of O-RAN, and a specific user identifier (or UE identifier) ​​of O-RAN can be used in the present disclosure. 5G-GUTI is only an example of a globally unique identifier of a UE (or user), and a globally unique identifier of a UE (or user) can be used in the present disclosure.

[0169] In this process, operations do not have to be performed sequentially, or all operations do not have to be performed, and their order may be changed or specific operations may be omitted. Fig.17 Another configuration shown in FIG. 1 may be added to the process, or a process shown in another figure may be combined with the process shown in FIG. Fig.17 The process combination shown in Fig.17 The names of the messages shown in are only examples, and the configuration of the present disclosure may be applied to methods and messages similar to those used in the present disclosure. Fig.17The names of the messages shown in are merely examples, and the configuration of the present disclosure may be applied to methods and messages similar to those used in the present disclosure.

[0170] One or more methods according to the present disclosure may be combined and used.

[0171] Fig.18 An example of using a UE identifier based on using 5G-GUTI in O-RAN according to an embodiment of the present disclosure is shown.

[0172] refer to Fig.18 , reference numeral 1800 indicates an example in which the O-DU measures the usage, throughput, and latency of physical resource blocks (PRBs) (interchangeably used with physical layer resources, radio resources, or time-frequency resources) of each network slice or each cell, and sends the information about each user together with the RAN UE ID to the RIC based on the KPI report and 5G-GUTI.

[0173] Reference numeral 1810 indicates an example in which the O-CU-CP measures a network slice-specific or cell-specific KPI and sends information about each user together with the RAN UE ID to the RIC based on the 5G-GUTI. At this time, the 5G-GUTI may also be sent.

[0174] Reference numeral 1820 indicates an example in which the O-CU-UP measures throughput and CPU usage for each network slice, each cell, or each bearer, and sends information about each user (such as KPI reports, resource usage, and overload indications) together with the RAN UE ID (and 5G-GUTI) to the RIC based on the 5G-GUTI.

[0175] The information sent can be received by the E2 termination xApp and can be stored in the database of each 5G-GUTI. Based on the stored information, the xAPP used as a KPI monitor can analyze whether the KPI of each UE is achieved, the analysis results (KPI report) can be collected for each UE, and the generated information can be sent to the NRT RIC through the O1 interface xAPP.

[0176] RIC and NRT-RIC can optimize resources based on the information stored for each 5G-GUTI to provide the services required by each UE. Specifically, RIC or NRT-RIC can allow the UE to use additional radio resources through carrier aggregation or dual connectivity, or control the mobility of the UE.

[0177] Fig.19 A device capable of implementing the present disclosure according to an embodiment of the present disclosure is shown.

[0178] refer to Fig.19 , the device 1900 according to the present disclosure may include a controller 1910 and a transceiver 1920, and further include a storage unit not shown. The controller 1910 may operate to perform at least one of the functions of RIC, NRT-RIC, O-CU-CP, O-CU-UP, O-DU, CU-CP, CU-UP, and DU, and the transceiver 1920 may be controlled by the controller 1910 to send and receive messages. The storage unit may store information included in the received message and information about each UE.

[0179] Fig. 20 A 3GPP Non-Standard Standalone (NSA) support system of an O-RAN network system according to an embodiment of the present disclosure is shown.

[0180] refer to Fig. 20 , the 3GPP NSA network uses dual connectivity using 4G and 5G while supporting traditional 4G (eNB) functions and additionally using 5G (gNB). The O-RAN standard uses the newly defined non-real-time RAN intelligent controller (NRT-RIC) 2000, (near real-time) RAN intelligent controller (RIC) 2010, O-CU-CP 2020, O-CU-UP 2030, and O-DU 2040, and additionally supports the NSA scheme of the eNB 2050 supporting 4G LTE. At this time, RIC 2010 and / or NRT-RIC 2000 perform near real-time control and optimize LTE and 5G RAN elements and resources based on 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. To this end, the O-eNB 2050 can send call-related information and measurement-related information of a specific UE to the RIC 2010.

[0181] Fig.21 The process of obtaining GUTI in the case of NSAEN-DC defined in O-RAN by the eNB for call access by the UE according to an embodiment of the present disclosure is shown. Like 3GPP NSA, in O-RAN NSA, the message for call access is sent to MME through O-eNB, and then dual connectivity is supported by establishing an X2 interface with gNB. Therefore, the initial call access process is the same as 4G LTE.

[0182] refer to Fig.21In operation 2100, UE 2101 inserts 40 bits of the S-TMSI value allocated by the core network into the RRC connection request message in the initial establishment according to the call access procedure defined in the 3GPP standard, and sends the RRC connection request message to O-eNB 2102. In operation 2110, O-eNB 2102 stores the S-TMSI value sent by UE 2101. Thereafter, O-eNB 2102 sends an RRCConnectionSetup message to UE 2101, and UE 2101 sends an RRCConnectionSetupComplete message to O-eNB 2102 in response thereto. Thereafter, O-eNB 2102 sends an initial UE message to MME 2103. In operation 2120, the O-eNB 2102 of the O-RAN stores the GUMMEI value inserted into the S1AP INITIAL CONTEXT SETUP REQUEST message and sent by the MME 2103 according to the call access procedure defined in the 3GPP standard. In operation 2130, the O-RAN O-eNB 2102 identifies the M-TMSI based on the S-TMSI stored in operation 2110, and generates a GUTI by concatenating the M-TMSI with the lower part of the GUMMEI received in operation 2120.

[0183] In this process, operations do not have to be performed sequentially, or all operations do not have to be performed, and their order may be changed or specific operations may be omitted. Fig.21 Another configuration shown in FIG. 1 may be added to the process, or a process shown in another figure may be combined with the process shown in FIG. Fig.21 The process combination shown in .

[0184] Fig. 22 The process of obtaining the GUAMI when the UE performs initial attachment (initial access) by the CU-CP of the 5G RAN defined in 3GPP according to an embodiment of the present disclosure is shown.

[0185] refer to Fig. 22 , when there is no 5G SAE-Temporary Mobile Subscriber Identity (5G-S-TMSI) value allocated by the 5G core network in the initial establishment, in operation 2200, the UE 2201 that performs the initial attachment according to the call access procedure defined in the 3GPP standard inserts a random value into the RRCSetupRequest message and sends the RRCSetupRequest message. In operation 2210, the DU 2202 inserts the random value received in operation 2200 into the F1 Initial UL RRC Messaging Message according to the call access procedure defined in 3GPP, and sends the F1 Initial UL RRC Messaging Message to the CU-CP 2204. Fig. 22 Also includes CU-UP 203.

[0186] Thereafter, CU-CP 2204 transfers a DL RRC message to DU 2202, and DU 2202 sends an RRCSetup message (or an RRCReject message) to UE 2201. UE 2201 receiving the RRCSetup message sends an RRCSetupComplete message to DU 2202, and DU 2202 sends an UL RRC message transfer to CU-CP 2204.

[0187] The CU-CP 2204 sends an initial UE message to the AMF 2205, and in operation 2220, the AMF 2205 sends an NGAP INITIAL CONTEXT SETUP REQUEST message to the CU-CP 2204 according to the 3GPP call access procedure. In operation 2230, the CU-CP 2204 stores the GUAMI inserted into the NGAP INITIAL CONTEXT SETUP REQUEST and sent by the AMF 2205. In this process, the GUAMI stored by the CU-CP 2204 can be used as an identifier such as a RAN UE ID for uniquely identifying the UE 2201 within the 3GPP gNB, and the identifier can be replaced with a 5G-GUTI in future UE additional access scenarios. In addition, a value based on the GUAMI instead of the GUAMI can be used as an identifier of the UE 2201 (e.g., RAN UE ID), and this method is similar to the method of using the 5G-GUTI as the identifier of the UE 2201, so the described method can be referred to.

[0188] In this process, operations do not have to be performed sequentially, or all operations do not have to be performed, and their order may be changed or specific operations may be omitted. Fig. 22 Another configuration shown in FIG. 1 may be added to the process, or a process shown in another figure may be combined with the process shown in FIG. Figure 8 The process combination shown in .

[0189] Fig.23 The process of obtaining GUMMEI in the case of 4G LTE defined in O-RAN by the eNB to which the UE performs call access according to an embodiment of the present disclosure is shown. The call access is sent to the MME through the O-eNB.

[0190] refer to Fig.23, when there is no S-TMSI value allocated by the core network in the initial establishment, in operation 2300, the UE 2301 performing the initial attachment according to the call access procedure defined in the 3GPP standard inserts a random value into the RRC connection request message, and sends the RRC connection request message to the O-eNB 2302 of the O-RAN. The O-eNB 2302 sends an RRCConnectionSetup message to the UE 2301, and the UE 2301 sends an RRCConnectionSetupComplete message to the O-eNB 2302 in response thereto. Thereafter, the O-eNB 2302 sends an initial UE message to the MME 2303.

[0191] The O-eNB 2302 of the O-RAN receives the S1AP INITIAL CONTEXT SETUP REQUEST message from the MME 2303 according to the call access procedure defined in the 3GPP standard in operation 2310, and stores the GUMMEI value inserted into the S1AP INITIAL CONTEXT SETUP REQUEST and sent by the MME 2303 in operation 2320. In this process, the GUMMEI value stored by the O-eNB 2302 can be used as an identifier such as the RAN UEID for uniquely identifying the UE 2301 within the 3GPP gNB, and the identifier can be replaced with the GUTI in future UE attachment access scenarios. In addition, a value based on the GUMMEI instead of the GUMMEI can be used as an identifier of the UE 2301 (e.g., the RAN UE ID), and this method is similar to the method of using the 5G-GUTI or the GUTI as the identifier of the UE 2301, so the described method can be referred to.

[0192] In this process, operations do not have to be performed sequentially, or all operations do not have to be performed, and their order may be changed or specific operations may be omitted. Fig.23 Another configuration shown in FIG. 1 may be added to the process, or a process shown in another figure may be combined with the process shown in FIG. Fig.23 The process combination shown in .

[0193] Fig.24 An example of a process in which the O-CU-CP of a 5G RAN defined in the O-RAN according to an embodiment of the present disclosure allocates a unique RAN UE ID to a service provider network allocated by a core network when the UE performs an initial attachment is shown.

[0194] refer to Fig.24UE 2401 performs an RRC establishment process with O-DU 2402 and O-CU-CP 2404 according to a call access process defined in the 3GPP standard, and the process can refer to Figure 8 . In operation 2400, the O-CU-CP 2404 sends an NGAP Initial UE message including the RAN UE ID defined in the initial establishment or configured by OAM to the AMF. Alternatively, the O-CU-CP 2404 may send the RAN UE ID without inserting the RAN UE ID into the NGAP Initial UE message. In operation 2410, the AMF 2405 stores the RAN UE ID inserted into the NGAP Initial UE message and sent by the O-CU-CP 2404 according to the call access procedure defined in the 3GPP standard as the 5G-GUTI newly configured by the AMF 2405 as a value for globally uniquely identifying UE2401. That is, the RAN UE ID is configured as the 5G-GUTI.

[0195] In addition, instead of 5G-BUTI, a value based on 5G-GUTI or GUAMI and a new user identifier, a value based on GUAMI and a new user identifier, a value shared with the core network including GUAMI, or a combination of values ​​based on a value shared with the core network including GUAMI may be used as the RAN UE ID or the identifier of UE 2401 (in O-RAN) (e.g., GUAMI and a new user identifier). The value shared with the core network may be a reference Fig.14 The method of using information other than 5G-GUTI as the RAN UE ID or the identifier of UE 2401 may refer to the method of identifying UE 2401 within the service provider PLMN. That is, the RAN UE ID or the identifier of UE 2401 may be determined based on the identifier of UE 2401 used within the service provider PLMN.

[0196] In operation 2420, the AMF 2405 inserts the RAN UE ID stored in operation 2410 into the NGAP INITIAL CONTEXT SETUP REQUEST message according to the call access procedure defined in the 3GPP standard, and sends the NGAP INITIAL CONTEXT SETUP REQUEST message to the O-CU-CP 2404. The O-CU-CP 2404 stores the RAN UE ID inserted into the NGAP INITIAL CONTEXT SETUP REQUEST message and sent by the AMF 2405 according to the call access procedure defined in the 3GPP standard.

[0197] Thereafter, UE 2401 and O-CU-CP 2404 can perform the RRC reconfiguration process according to the 3GPP standard, and O-CU-CP 2404 can insert the stored RAN UE ID into the NGAP INITIAL CONTEXT SETUP RESPONSE message and send the NGAP INITIAL CONTEXT SETUP RESPONSE message to AMF2405 in response to the NGAP INITIAL CONTEXT SETUP REQUEST.

[0198] In this process, operations do not have to be performed sequentially, or all operations do not have to be performed, and their order may be changed or specific operations may be omitted. Fig. 9 Another configuration shown in FIG. 1 may be added to the process, or a process shown in another figure may be combined with the process shown in FIG. Fig.24 The process combination shown in . Fig.24 Also includes O-CU-UP 2403.

[0199] Fig.25 An example of a process in which an O-RAN eNB (O-eNB) (or eNB) in a 5G NSA and O-RAN LTE network structure defined in O-RAN according to an embodiment of the present disclosure allocates a unique RAN UE ID to a service provider network assigned by a core network when the UE performs an initial attachment is shown.

[0200] refer to Fig.25 UE 2501 performs an RRC connection establishment process with O-eNB 2502 according to a call access process defined in the 3GPP standard, and the process can refer to Fig.10 . In operation 2500, the O-eNB 2502 inserts the RAN UE ID defined in the initial setup or configured by the OAM into the S1 Initial UE message, and sends the S1 Initial UE message to the MME 2503. Alternatively, the O-eNB 2502 may send the RAN UE ID without inserting the RAN UE ID into the S1 Initial UE message. In operation 2510, the MME stores the RAN UE ID inserted into the S1 Initial UE message and sent by the O-eNB 2502 according to the call access procedure defined in the 3GPP standard as the GUTI newly configured by the MME as a value for globally uniquely identifying the UE 2501. That is, the RAN UE ID may be configured as the GUTI.

[0201] In addition, instead of GUTI, a value based on GUTI or GUMMEI and a new user identifier, a value based on GUMMEI and a new user identifier, a value shared with the core network including GUMMEI, or a combination of values ​​based on a value shared with the core network including GUMMEI may be used as the RAN UE ID or the identifier of UE 2501 (in O-RAN) (e.g., GUMMEI and a new user identifier). The value shared with the core network may be a reference Fig.14 The method of using information other than the GUTI as the RAN UE ID or the identifier of the UE 2501 may refer to the method of identifying the UE 2501 within the service provider PLMN. That is, the RAN UE ID or the identifier of the UE 2501 may be determined based on the identifier of the UE 2501 used within the service provider PLMN.

[0202] In operation 2520, the MME inserts the RAN UE ID stored in operation 2510 into the S1 INITIAL CONTEXT SETUP REQUEST message according to the call access procedure defined in the 3GPP standard, and sends the S1 INITIAL CONTEXT SETUP REQUEST message. The O-eNB 2502 stores the RAN UE ID inserted into the S1 INITIAL CONTEXT SETUP REQUEST message and sent by the MME according to the call access procedure defined in the 3GPP standard. Thereafter, the O-eNB 2502 may send 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.

[0203] In this process, operations do not have to be performed sequentially, or all operations do not have to be performed, and their order may be changed or specific operations may be omitted. Fig.25 Another configuration shown in FIG. 1 may be added to the process, or a process shown in another figure may be combined with the process shown in FIG. Fig.25 The process combination shown in .

[0204] Fig.26 An example of a process in which the O-CU-CP of the 5G RAN defined in the O-RAN according to an embodiment of the present disclosure allocates a RAN UE NGAP ID used for NGAP configuration with the core network as the RAN UE ID when UE 2501 performs an initial attachment is shown.

[0205] refer to Fig.26UE 2601 performs an RRC establishment process with O-DU 2602 and O-CU-CP 2604 according to a call access process defined in the 3GPP standard, and the process can refer to Figure 8 . Specifically, in operation 2600, UE 2601 sends an RRCSetupRequest message to O-DU 2602, and in operation 2610, O-DU 2602 sends an F1 initial UL RRC message delivery message to O-CU-CP 2604 according to the call access procedure defined in the 3GPP standard. Thereafter, O-CU-CP 2604 delivers a DL RRC message to O-DU 2602, and O-DU 2602 sends an RRCSetup message to UE 2601. In operation 2620, UE 2601, which has received the RRCSetup message, sends an RRCSetupComplete message to O-DU 2602, and in operation 2630, O-DU 2602 sends an UL RRC message delivery to O-CU-CP 2604.

[0206] In operation 2640, the O-CU-CP 2604 configures the RAN UE NGAP ID defined in the initial establishment or used by the NGAP interface with the AMF 2605 as the RAN UE ID, and sends an NGAP Initial UE message to the AMF 2605. Alternatively, the O-CU-CP 2604 may send the RAN UE ID without inserting the RAN UE ID into the NGAP Initial UE message. Fig. 27 A detailed description of the RAN UE NGAP ID is given below. The RAN UE NGAP ID may be a 32-bit integer, but is not limited thereto.

[0207] The AMF 2605 stores the RAN UE ID configured as the RAN UE NGAP ID inserted into the NGAP Initial UE message according to the call access procedure defined in the 3GPP standard and sent by the O-CU-CP 2604, or stores the RAN UE ID as the 5G-GUTI newly configured by the AMF as a value for globally uniquely identifying the UE 2601. That is, the RAN UE ID is configured (by the AMF) as the RAN UE NGAP ID or the 5G-GUTI.

[0208] In addition, instead of using 5G-GUTI as the RAN UE ID, a value based on 5G-GUTI or GUAMI and a new user identifier, a value based on GUAMI and a new user identifier, a value shared with the core network including GUAMI, or a combination of values ​​based on a value shared with the core network including GUAMI may be used as the RAN UE ID or an identifier of UE 2601 (in O-RAN) (e.g., GUAMI and a new user identifier). The value shared with the core network may be a reference Fig.14 Alternatively, the method of using information other than 5G-GUTI as the RAN UE ID or the identifier of UE 2601 may refer to the method of identifying UE 2601 within the service provider PLMN. That is, the RAN UE ID or the identifier of UE 2601 may be determined based on the identifier of UE 2601 used within the service provider PLMN.

[0209] In operation 2650, the AMF 2605 inserts the stored RAN UEID into the NGAP INITIAL CONTEXT SETUP REQUEST message according to the call access procedure defined in the 3GPP standard, and sends the NGAP INITIAL CONTEXT SETUP REQUEST message to the O-CU-CP 2604. The O-CU-CP 2604 stores the RAN UE ID inserted into the NGAP INITIAL CONTEXT SETUP REQUEST message and sent by the AMF according to the call access procedure defined in the 3GPP standard.

[0210] Thereafter, UE 2601 and O-CU-CP 2604 may perform an RRC reconfiguration procedure according to the 3GPP standard, and O-CU-CP may insert the stored RAN UE ID into the NGAP INITIAL CONTEXT SETUP RESPONSE message, and send the NGAP INITIAL CONTEXT SETUP RESPONSE message to AMF in response to the NGAP INITIAL CONTEXT SETUP REQUEST. Thereafter, O-CU-CP 2604 may insert the RAN UE ID into the E2 indication message, and send the E2 indication message to RIC 2606, and at least one of O-DU 2602 and O-CU-UP 2603 may also send the E2 indication message to RIC 2606.

[0211] In this process, operations do not have to be performed sequentially, or all operations do not have to be performed, and their order may be changed or specific operations may be omitted. Fig.26Another configuration shown in FIG. 1 may be added to the process, or a process shown in another figure may be combined with the process shown in FIG. Fig.26 The process combination shown in .

[0212] Fig. 27 The RAN UE NGAP ID specified in the 3GPP standard according to an embodiment of the present disclosure is shown.

[0213] refer to Fig. 27 , RAN UE NGAP ID is an identifier used in the RAN when the O-CU-CP 2604 and AMF establish an NGAP connection. This is an identifier that uniquely identifies the UE (or an association with the UE) in the NG interface with the BS (gNB or NG-RAN node).

[0214] Fig.28 An example of a process in which the O-CU-CP of a 5G RAN defined in the O-RAN according to an embodiment of the present disclosure allocates an AMF UE NGAP ID used for NGAP configuration with the core network as the RAN UE ID when the UE performs an initial attach is shown.

[0215] refer to Fig.28 UE 2801 performs an RRC establishment process with O-DU 2802 and O-CU-CP 2804 according to a call access process defined in the 3GPP standard, and the process can refer to Figure 8 . Specifically, in operation 2800, UE 2801 sends an RRCSetupRequest message to O-DU 2802, and in operation 2810, O-DU 2802 sends an F1 initial UL RRC message delivery message to O-CU-CP 2804 according to the call access procedure defined in the 3GPP standard. Thereafter, O-CU-CP 2804 delivers a DL RRC message to O-DU 2802, and O-DU 2802 sends an RRCSetup message to UE 2801. In operation 2820, UE 2801 that has received the RRCSetup message sends an RRCSetupComplete message to O-DU 2802, and in operation 2830, O-DU 2802 sends an UL RRC message delivery to O-CU-CP 2804.

[0216] In operation 2840, the O-CU-CP 2804 configures the RAN UE NGAP ID defined in the initial establishment or used by the NGAP interface with the AMF 2806 as the RAN UE ID, and sends an NGAP Initial UE message to the AMF 2806. Alternatively, the O-CU-CP 2804 may send the RAN UE ID without inserting the RAN UE ID into the NGAP Initial UE message. Fig. 27 A detailed description of the RAN UE NGAP ID is given below. The RAN UE NGAP ID may be a 64-bit integer, but is not limited thereto.

[0217] The AMF 2806 configures the RAN UE ID (configured as the RAN UE NGAP ID inserted into the NGAP Initial UE message and sent by the O-CU-CP) as the 5G-GUTI newly configured by the AMF 2806 as a value for globally uniquely identifying the UE 2801, or allocates and stores the AMF UE ENGAP ID for identifying the UE 2801 by the AMF according to the call access procedure defined in the 3GPP standard. That is, the RAN UE ID is configured (by the AMF) as the AMF UE NGAP ID or the 5G-GUTI. In addition, a value based on the 5G-GUTI, a combination of the GUAMI and the new user identifier, a value based on the GUAMI and the new user identifier, a value shared with the core network including the GUAMI, or a combination of values ​​based on the value shared with the core network including the GUAMI may be used as the RAN UE ID or the identifier of the UE 2801 (in the O-RAN), instead of using the 5G-GUTI as the RAN UE ID.

[0218] Fig.29 The detailed configuration of AMF UE NGAP ID according to an embodiment of the present disclosure is shown.

[0219] refer to Fig.29 , AMF UE NGAP ID is an identifier assigned to uniquely identify the UE in the NG interface with the AMF, and can be uniquely configured in the AMF set. For example, the AMF UE NGAP ID can be 40 bits, and when the BS receives the AMF UE NGAP ID, the BS should store the AMF UE NGAP ID of the specific UE, while the UE-related logical NG connection of the specific UE is maintained, and the AMF UE NGAP ID should be inserted into the NGAP signaling. In the case of LTE, the MMEUE S1AP ID can be used instead of the AMF UE NGAP ID.

[0220] Fig.30The configuration of the MME UE S1AP ID according to an embodiment of the present disclosure is shown.

[0221] refer to Fig.30 , similar to the AMF UE NGAP ID, the MME UE S1AP ID is an identifier assigned to uniquely identify a UE connected to an MME through the S1-MME interface and can be 32 bits. In the case of an LTE system, the MME instead of Fig.28 The AMF may allocate the MME UE S1AP ID as the RAN UE ID. In addition, any identifier used to identify the UE by the AMF or MME may replace the AMF UE NGAP ID or the MME UE S1AP ID without using the AMF UE NGAP ID and the MME UE S1AP ID.

[0222] Alternatively, the AMF (or MME) may generate a bit stream by applying a 128-bit or 256-bit SECURE HASH FUNCTION defined in 3GPP or a SECURE HASH FUNCTION defined in the National Institute of Standards and Technology (NIST) or the Internet Engineering Task Force (IETF) to the generated RAN UE ID, truncating the bit stream by 64 bits according to the 64 bits corresponding to the RAN UE ID length, and then configuring it as the RAN UE ID. This may be an application of a security function that makes it impossible to find a legacy AMF NGAP UE ID (or MME UE S1AP ID) or 5G-GUTI based on the RAN UE ID. Details of the secure hash (SECURE HASH, SH) 64-bit truncation are described in Fig.31 Shown in.

[0223] Fig.31 An example is shown of generating 128 bits through AES-CMAC based on the AMF UE NGAP ID or the MME UE S1AP ID according to an embodiment of the present disclosure, truncating the upper 64 bits of the generated 128 bits, and generating the lower 64 bits as the SH-AMF UE NGAP ID or the SH-MME UE S1AP ID to use it as the RAN UE ID.

[0224] refer to Fig.31 , the 64-bit UE identifier can be an ID used to uniquely identify the UE in the AMF pool or MME pool. Fig.31 This is merely an example of generating an identifier of a UE through a hash function, and the present disclosure is not limited thereto.

[0225] The value shared with the core network can be a reference Fig.14Alternatively, the method of using information other than 5G-GUTI as the RAN UE ID or the identifier of the UE may refer to the method of identifying the UE within the service provider PLMN. That is, the RAN UE ID or the identifier of the UE may be determined based on the identifier of the UE used within the service provider PLMN.

[0226] In operation 2850, the AMF 2806 inserts the stored RAN UEID into the NGAP INITIAL CONTEXT SETUP REQUEST message according to the call access procedure defined in the 3GPP standard, and sends the NGAP INITIAL CONTEXT SETUP REQUEST message to the O-CU-CP 2804. The O-CU-CP 2804 stores the AMFUE NGAP ID inserted into the NGAP INITIAL CONTEXT SETUP REQUEST message and sent by the AMF 2806 according to the call access procedure defined in the 3GPP standard as the RAN UE ID.

[0227] Alternatively, the O-CU-CP 2804 may generate a bit stream by applying the SECURE HASH FUNCTION defined in 3GPP or the 128-bit or 256-bit SECURE HASH FUNCTION defined in NIST or IETF to the AMF UE NGAP ID inserted into the NGAPINITIAL CONTEXT SETUP REQUEST message and sent by the AMF 2906, truncating the bit stream by 64 bits according to the 64 bits corresponding to the length of the RAN UE ID, and configuring it as the RAN UE ID. This may be an application of a security function that makes it impossible to find the legacy AMF NGAP UE ID or 5G-GUTI based on the RAN UE ID.

[0228] O-CU-CP 2804 inserts the configured RAN UE ID into the E1 bearer context setup request message specified in the 3GPP standard in operations 2860 and 2870, sends the E1 bearer context setup request message to O-CU-UP 2803, and receives an E1 bearer context setup response message, and also inserts the RAN UE ID into the F1 UE CONTEXT SETUP REQUEST message specified in the 3GPP standard in operations 2880 and 2890, sends the F1 UE CONTEXT SETUPREQUEST message to O-DU 2802, and receives an F1 UE CONTEXT SETUP RESPONSE message.

[0229] Thereafter, UE 2801 and O-CU-CP 2804 perform the RRC reconfiguration process according to the 3GPP standard, and O-CU-CP 2804 inserts the stored RAN UE ID into the NGAP INITIAL CONTEXT SETUP RESPONSE message and sends the NGAP INITIAL CONTEXT SETUP RESPONSE message to AMF 2806 in response to the NGAP INITIAL CONTEXT SETUP REQUEST.

[0230] In this process, operations do not have to be performed sequentially, or all operations do not have to be performed, and their order may be changed or specific operations may be omitted. Fig.28 Another configuration shown in FIG. 1 may be added to the process, or a process shown in another figure may be combined with the process shown in FIG. Fig.28 The process combination shown in .

[0231] Fig.32 Such a process according to an embodiment of the present disclosure is shown, wherein the O-CU-CP of the 5G RAN defined in the O-RAN generates an information list for each UE based on the 5G-S-TMSI, GUAMI and AMF UE NGAP ID of each RAT / Frequency Selection Priority (RFSP) group received from the UE and the AMF, and sends the list to the RIC, and the RIC generates an information list for each UE based on at least one of the 5G-S-TMSI, GUAMI and AMF UE NGAP ID of each RFSP group, allocates a UE ID, and sends the information to the NRT-RIC through an A1 enriched information message, and the NRT RIC performs management related to the UE ID of each RFSP group.

[0232] refer to Fig.32In operation 3200, the UE 3201 inserts the upper 39 bits of the 5G-S-TMSI value (or a random value, and hereinafter, may be used interchangeably with the random value) allocated by the core network into the RRCSetupRequest message in the initial setup according to the call access procedure defined in the 3GPP standard, and sends the RRCSetupRequest message to the O-DU 3202. In operation 3210, the O-DU 3202 inserts the upper 39 bits of the 5G-S-TMSI value received in operation 3200 into the F1 Initial UL RRC Messaging Message according to the call access procedure defined in the 3GPP standard, and sends the F1 Initial UL RRC Messaging Message to the O-CU-CP 3204. In operation 3215, the O-CU-CP 3204 stores the upper 39 bits of the 5G-S-TMSI value inserted into the F1 message and sent by the O-DU 3202. Thereafter, in operation 3220, the O-CU-CP 3204 delivers a DL RRC message to the O-DU 3202, and in operation 3225, the O-DU 3202 sends an RRCSetup message (or an RRCReject message) to the UE.

[0233] When the O-DU 3202 sends the RRCSetup message, in operation 3230, the UE inserts the lower 9 bits of the 5G-S-TMSI value allocated by the core network in the initial setup according to the call access procedure defined in the 3GPP standard into the RRCSetupComplete message, and sends the RRCSetupComplete message to the O-DU 3202. In operation 3235, the O-DU 3202 inserts the lower 9 bits of the 5G-S-TMSI value received in operation 3230 into the F1 UL RRC messaging message according to the call access procedure defined in the 3GPP standard, and sends the F1 UL RRC messaging message to the O-CU-CP 3204. In operation 3240, the O-CU-CP 3204 stores the lower 9 bits of the 5G-S-TMSI value inserted into the F1 message and sent by the O-DU 3202. O-CU-CP 3204 sends an initial UE message to AMF 3205 in operation 3245, and stores at least one of the GUAMI value, AMF UE NGAP ID, and RFSP value inserted and sent by AMF in the NGAP INITIAL CONTEXT SETUP REQUEST message according to the call access procedure defined in the 3GPP standard in operation 3250. RFSP is a RAT / frequency selection priority and is used to specify a specific service group to which UE 3201 belongs in the 5G system.

[0234] In operation 3255, the NRT RIC 3207 transmits a policy related to a specific RFSP group to the RIC 3206 through an A1 policy message regardless of the order of the procedures.

[0235] Thereafter, in operation 3260, the O-CU-CP 3204 performs an RIC subscription procedure specified in the O-RAN standard with the RIC 3206, inserts at least one of the GUAMI, 5G-S-TMSI, and AMF UE NGAP ID of each UE having the RFSP as a representative key into an E2 indication (report) message based on at least one of the GUAMI, 5G-S-TMSI, and AMF UE NFAP ID of the UE belonging to a specific group RFSP specified by the RIC 3206 through the subscription message, and sends the E2 indication (report) message to the RIC 3206. In operation 3265, the RIC 3206 allocates a UE ID to each UE based on the GUAMI, 5G-S-TMSI, and AMF UE NGAP ID of the UE belonging to the RFSP received through the E2 indication message, and stores at least one of the RFSP GUAMI, 5G-S-TMSI, and AMF UE NGAP ID for each UE ID.

[0236] In operation 3270, RIC 3206 sends a UE ID list to NRT RIC 3207 as part of the A1 enrichment process in response to the A1 policy message or the A1 enrichment information message. The UE ID list included in the response message includes at least one of the RFSP GUAMI, 5G-S-TMSI, and AMF UE NGAP ID of each UE.

[0237] In this process, operations do not have to be performed sequentially, or all operations do not have to be performed, and their order may be changed or specific operations may be omitted. Fig.32 Another configuration shown in FIG. 1 may be added to the process, or a process shown in another figure may be combined with the process shown in FIG. Fig.32 The process combination shown in . Fig.32 Also includes O-CU-UP 3203.

[0238] Fig.33Such a process according to an embodiment of the present disclosure is shown, in which the O-eNB of the 4G RAN defined in the O-RAN generates an information list for each UE based on at least one of the S-TMSI, GUMMEI and MME UE S1AP ID of each Subscriber Profile ID (SPID) group received from the UE and the MME, and sends the list to the RIC, and the RIC allocates a UE ID to each UE based on at least one of the S-TMSI, GUMMEI and MME UE S1AP ID of each SPID group, generates and manages the UE list (which may include the information), and sends the information to the NRT RIC 3207 through an A1 enriched information message, and the NRT RIC 3207 performs management related to the UE ID of each SPID group.

[0239] refer to Fig.33 In operation 3300, UE 3301 inserts the upper 40 bits of the S-TMSI value (or random value, and hereinafter, may be used interchangeably with the random value) allocated by the core network into the RRC connection request message in the initial establishment according to the call access procedure defined in the 3GPP standard, and sends the RRC connection request message to O-eNB 3302. In operation 3310, O-eNB 3302 stores the S-TMSI value sent by UE 3301. Thereafter, O-eNB 3302 sends an RRCConnectionSetup message to UE 3301, and UE 3301 sends an RRCConnectionSetupComplete message to O-eNB 3302 in response thereto. Thereafter, O-eNB 3302 sends an initial UE message to MME 3303. In operation 3320, O-eNB 3302 stores at least one of SPID, GUMMEI, and MME UE S1AP ID inserted into the S1APINITIAL CONTEXT SETUP REQUEST message and sent by MME 3303 according to the call access procedure defined in the 3GPP standard. SPID is a user profile ID and is used to specify a specific service group to which UE 3301 belongs in the LTE system.

[0240] In operation 3330, the NRT RIC 3305 sends a policy related to a specific SPID group to the RIC 3304 through an A1 policy message regardless of the order of the process.

[0241] Thereafter, in operation 3340, the O-eNB 3302 performs an RIC subscription procedure specified in the O-RAN standard with the RIC 3304, inserts at least one of the GUMMEI, S-TMSI, and MME UE S1AP ID of each UE having the SPID as a representative key into an E2 indication (report) message based on at least one of the GUMMEI, S-TMSI, and MME UE S1AP ID of the UE belonging to the specific group SPID specified by the RIC 3304 through the subscription message, and sends the E2 indication (report) message to the RIC 3304. In operation 3350, the RIC 3304 allocates a UE ID of each UE to the information based on at least one of the GUMMEI, S-TMSI, and MME UE S1AP ID of the UE belonging to the SPID sent through the E2 indication message, and stores at least one of the SPID GUMMEI, S-TMSI, and MME UE S1AP ID for each UE ID. In operation 3360, RIC 3304 sends a UE ID list to NRT RIC 3305 as part of the A1 enrichment process in response to the A1 policy message or the A1 enrichment information message. The UE ID list included in the response message includes at least one of the UE ID, SPID GUAMI, S-TMSI, and MME UE S1APID of each UE.

[0242] In this process, operations do not have to be performed sequentially, or all operations do not have to be performed, and their order may be changed or specific operations may be omitted. Fig.33 Another configuration shown in FIG. 1 may be added to the process, or a process shown in another figure may be combined with the process shown in FIG. Fig.33 The process combination shown in .

[0243] Fig.34Such a process according to an embodiment of the present disclosure is shown, in which the O-CU-CP of the 5G RAN defined in the O-RAN generates a list of each UE based on the 5G-S-TMSI, GUAMI and AMF UE NGAP ID of each RFSP group received from the UE and the AMF, and sends the list to the RIC, and the RIC generates an information list of each UE based on the 5G-S-TMSI, GUAMI and AMF UE NGAP ID of each RFSP group, generates a secure hash 5G-GUTI after generating the 5G-GUTI based on the 5G-S-TMSI and GUAMI, or generates the secure hash 5G-GUTI using the GUAMI as a key, and sends the UEID and at least one of the secure hash 5G-GUTI, RFSP and GUAMI to the NRT-RIC through an A1 enriched information message, and the NRT RIC performs management related to the UE ID of each RFSP group.

[0244] refer to Fig.34 In operation 3400, the UE 3401 inserts the upper 39 bits of the 5G-S-TMSI value (or a random value, and hereinafter, may be used interchangeably with the random value) allocated by the core network into the RRCSetupRequest message in the initial setup according to the call access procedure defined in the 3GPP standard, and sends the RRCSetupRequest message to the O-DU 3402. In operation 3410, the O-DU 3402 inserts the upper 39 bits of the 5G-S-TMSI value received in operation 3400 into the F1 initial UL RRC messaging message according to the call access procedure defined in the 3GPP standard, and sends the F1 initial UL RRC messaging message to the O-CU-CP 3404. In operation 3415, the O-CU-CP 3404 stores the upper 39 bits of the 5G-S-TMSI value inserted into the F1 message and sent by the O-DU 3402. Thereafter, in operation 3420 , the O-CU-CP 3404 delivers a DL RRC message to the O-DU 3402 , and in operation 3425 , the O-DU 3402 sends an RRCSetup message (or an RRCReject message) to the UE 3401 .

[0245] When the O-DU 3402 sends the RRCSetup message, in operation 3430, the UE 3401 inserts the lower 9 bits of the 5G-S-TMSI value allocated by the core network in the initial setup according to the call access procedure defined in the 3GPP standard into the RRCSetupComplete message, and sends the RRCSetupComplete message to the O-DU 3402. In operation 3435, the O-DU 3402 inserts the lower 9 bits of the 5G-S-TMSI value received in operation 3430 into the F1 UL RRC messaging message according to the call access procedure defined in the 3GPP standard, and sends the F1 UL RRC messaging message to the O-CU-CP 3404. In operation 3440, the O-CU-CP 3404 stores the lower 9 bits of the 5G-S-TMSI value inserted into the F1 message and sent by the O-DU 3402. O-CU-CP 3404 sends an initial UE message to AMF 3405 in operation 3445, and stores at least one of the GUAMI value, AMF UE NGAP ID, and RFSP value inserted and sent by AMF in the NGAP INITIAL CONTEXT SETUP REQUEST message according to the call access procedure defined in the 3GPP standard in operation 3450. RFSP is a RAT / frequency selection priority and is used to specify a specific service group to which UE 3401 belongs in the 5G system.

[0246] In operation 3455, the NRT RIC 3407 transmits a policy related to a specific RFSP group to the RIC 3406 through an A1 policy message regardless of the order of the procedures.

[0247] Thereafter, in operation 3460, the O-CU-CP 3404 performs the RIC subscription procedure specified in the O-RAN standard with the RIC 3406, inserts at least one of the GUAMI, 5G-S-TMSI, and AMF UE NGAP ID of each UE having a representative factor as the RFSP into an E2 indication (report) message based on at least one of the GUAMI, 5G-S-TMSI, and AMF UE NGAP ID of the UE belonging to a specific group RFSP specified by the RIC 3406 through the subscription message, and sends the E2 indication (report) message to the RIC 3406. The RIC 3406 allocates a UE ID to each UE based on at least one of the GUAMI, 5G-S-TMSI, and AMF UE NGAP ID of the UE belonging to the RFSP received through the E2 indication message, and stores at least one of the RFSP GUAMI, 5G-S-TMSI, and AMF UE NGAP ID in the RIC UE ID registry for each UE ID. Thereafter, in operation 3465, RIC3406 generates a 5G-GUTI by concatenating the 5G-S-TMSI stored for each newly allocated UE ID and the GUAMI stored therewith. The generated 5G-GUTI is input into a secure hash function, and a secure hash 5G-GUTI is generated. Depending on the situation, the 5G-GUTI and the GUAMI are input into a secure hash function, and a secure hash 5G-GUTI is generated. At this time, the GUAMI may be selectively used as a key for the 5G-GUTI. In operation 3465, the process may be selectively applied.

[0248] In operation 3470, the RIC 3406 sends at least one of the UE ID, RFSP, GUAMI, and 5G-GUTI or secure hash 5G-GUTI to the NRT RIC 3407 in response to the A1 policy message or the A1 enrichment information message as part of the A1 enrichment process. In addition, the response message of the A1 enrichment information message may include at least one of the UE ID, RFSP GUAMI, 5G-S-TMSI, and AMF UE NGAP ID for each UE ID.

[0249] In this process, operations do not have to be performed sequentially, or all operations do not have to be performed, and their order may be changed or specific operations may be omitted. Fig.34 Another configuration shown in FIG. 1 may be added to the process, or a process shown in another figure may be combined with the process shown in FIG. Fig.34 The process combination shown in . Fig.34 Also includes O-CU-UP 3403.

[0250] Fig.35Such a process according to an embodiment of the present disclosure is shown, in which the O-eNB of the 4G RAN defined in the O-RAN generates an information list of each UE based on at least one of the S-TMSI, GUMMEI, and MME UE S1AP ID of each SPID group received from the UE and the MME, and sends the list to the RIC, and the RIC generates a list of each UE for the NRT RIC based on at least one of the S-TMSI, GUMMEI, and MME UE S1AP ID of each SPID group, generates a secure hash GUTI after generating the GUTI using the S-TMSI and the GUMMEI, or generates the secure hash GUTI using the GUMMEI as a key, and sends the UE ID and at least one of the secure hash GUTI, the SPID, and the GUMMEI to the NRT-RIC through an A1 enriched information message, and the NRT RIC performs management related to the UE ID of each SPID group.

[0251] refer to Fig.35 In operation 3500, UE 3501 inserts the upper 40 bits of the S-TMSI value (or random value, and hereinafter, may be used interchangeably with the random value) allocated by the core network into the RRC connection request message in the initial establishment according to the call access procedure defined in the 3GPP standard, and sends the RRC connection request message to O-eNB 3502. In operation 3510, O-eNB 3502 stores the S-TMSI value sent by UE 3501. Thereafter, O-eNB 3502 sends an RRCConnectionSetup message to UE 3501, and UE 3501 sends an RRCConnectionSetupComplete message to O-eNB 3502 in response thereto. Thereafter, O-eNB 3502 sends an initial UE message to MME 3503. In operation 3520, O-eNB 3502 stores at least one of SPID, GUMMEI, and MME UE S1AP ID inserted into the S1APINITIAL CONTEXT SETUP REQUEST message and sent by MME 3503 according to the call access procedure defined in the 3GPP standard. SPID is a user profile ID and is used to specify a specific service group to which UE 3501 belongs in the LTE system.

[0252] In operation 3530, the NRT RIC 3505 sends a policy related to a specific SPID group to the RIC 3504 through an A1 policy message regardless of the order of the process.

[0253] Thereafter, in operation 3540, the O-eNB 3502 performs a RIC subscription procedure specified in the O-RAN standard with the RIC 3504, inserts at least one of the GUMMEI, S-TMSI, and MME UE S1AP ID of each UE having the SPID as a representative key into an E2 indication (report) message based on at least one of the GUMMEI, S-TMSI, and MME UE S1AP ID of the UE belonging to the specific group SPID specified by the RIC 3504 through the subscription message, and sends the E2 indication (report) message to the RIC 3504. The RIC 3504 allocates a UE ID of each UE to the information based on at least one of the GUMMEI, S-TMSI, and MME UE S1AP ID of the UE belonging to the SPID received through the E2 indication message, and stores at least one of the SPID GUMMEI, S-TMSI, and MME UE S1AP ID of each UE ID in the RIC UE ID registration table. Thereafter, in operation 3550, the RIC 3504 generates a GUTI by concatenating the S-TMSI stored for each newly allocated UE ID and the GUMMEI stored therewith. The generated GUTI is input into a secure hash function, and a secure hash GUTI is generated. According to the secure hash algorithm, the GUMMEI may be selectively used as a key for the GUTI. In operation 3550, this process may be selectively applied.

[0254] In operation 3560, the RIC 3504 sends at least one of the UE ID, SPID, GUMMEI and GUTI or a secure hash GUTI of each UE ID to the NRT RIC 3505 in response to the A1 policy message or the A1 enrichment information message as part of the A1 enrichment process. The UE ID list included in the response message of the A1 enrichment information message includes at least one of the UE ID, SPID GUMMEI, S-TMSI and MME UE S1AP ID of each UE.

[0255] In this process, operations do not have to be performed sequentially, or all operations do not have to be performed, and their order may be changed or specific operations may be omitted. Fig.35 Another configuration shown in FIG. 1 may be added to the process, or a process shown in another figure may be combined with the process shown in FIG. Fig.35 The process combination shown in .

[0256] Fig.36 A RIC UE ID registry stored by the RIC according to an embodiment of the present disclosure is shown.

[0257] refer to Fig.36In the case of a 5G system, the RIC UE ID registry stores the RFSP, 5G-S-TMSI, GUAMI and AMF UE NGAP ID of each UE ID assigned by the RIC, and in the case of a 4G system, stores the SPID, S-TMSI, GUMMEI and MME UE S1AP ID.

[0258] Fig.37 An NRT-RIC UE ID registry stored by the NRT-RIC according to an embodiment of the present disclosure is shown.

[0259] refer to Fig.37 The NRT-RIC UE ID registry stores each UE ID received by the RIC for each group ID managed by the NRT-RIC (RFSP in the case of a 5G system and SPID in the case of a 4G system), as well as a secure hash 5G-GUTI (in the case of a 5G system) or a secure hash GUTI (in the case of a 4G system).

[0260] Fig.38 A method for RIC to generate secure hash 5G-GUTI / secure hash GUTI according to an embodiment of the present disclosure is shown.

[0261] refer to Fig.38 In the case of a 5G system, the RIC may generate a 5G-GUTI by concatenating the 5G-S-TMSI (or a random value) received from the O-CU-CP with the GUMMEI, and generate a secure 5G-GUTI by inputting the 5G-GUTI into a secure hash function. In the case of a 4G system, the RIC may generate a GUTI by concatenating the S-TMSI received from the O-eNB with the GUMMEI, and generate a secure GUTI by inputting the GUTI into a secure hash function. The 5G-GUTI and the GUTI may be replaced with other UE identifiers used in the network.

[0262] While the present disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present disclosure as defined by the appended claims and their equivalents.

Claims

1. A method performed by a node of an open radio access network O-RAN central unit control plane O-CU-CP in a communication system, the method include: receiving a RIC subscription request message from a near real-time RAN intelligent controller (near-RT RIC); In response to the RIC subscription request message, sending a RIC subscription response message to the near RT RIC; as well as When an event of the near RT RIC is generated, an indication message for reporting is sent to the near RT RIC. The indication message includes at least one user equipment UE identifier ID, and The at least one UE ID includes a RAN UE ID, and the RAN UE ID is used to identify the UE on the E1 interface between the O-CU-CP and the O-RAN CU-user plane O-CU-UP and on the F1 interface between the O-CU-CP and the distributed unit DU.

2. The method according to claim 1, in, The indication message includes UE context information, and The RAN UE ID is used to send a UE context establishment request message to the DU.

3. The method according to claim 1, in, at least one UE ID including a globally unique access and mobility management function identifier GUAMI and an access and mobility management function user equipment NG application protocol identifier AMF UE NGAP ID, and Among them, GUAMI and AMF UE NGAP ID are obtained from the initial context establishment request message, and the initial context establishment request message is received from the access and mobility management function AMF.

4. The method according to claim 1, in, At least one UEID includes a globally unique mobility management entity identifier GUMMEI and a mobility management entity user equipment S1 application protocol identifier MME UE S1AP ID, and The GUMMEI and the MME UE S1AP ID are obtained from an initial context establishment request message, and the initial context establishment request message is received from a mobility management entity MME.

5. The method according to claim 1, in, The RIC subscription request message is used to configure the O-CU-CP to send the indication message to the near RT RIC according to an event preset by the near RTRIC.

6. A method performed by a Near Real-Time Radio Access Network (RAN) Intelligent Controller (Near RT RIC) in a communication system, the method include: Sending a RIC subscription request message to a node of an open radio access network O-RAN central unit control plane O-CU-CP; receiving, from the node of the O-CU-CP, a RIC subscription response message in response to the RIC subscription request message; and receiving an indication message for reporting from a node of the O-CU-CP, The indication message includes at least one user equipment UE identifier ID, and The at least one UE ID includes a RAN UE ID, and the RAN UE ID is used to identify the UE on the E1 interface between the O-CU-CP and the O-RAN CU-user plane O-CU-UP and on the F1 interface between the O-CU-CP and the distributed unit DU.

7. The method according to claim 6, in, The indication message includes UE context information, and The RAN UE ID is used to send a UE context establishment request message to the DU.

8. The method according to claim 6, in, The at least one UEID includes a globally unique mobility management entity identifier GUMMEI and a mobility management entity user equipment S1 application protocol identifier MME UE S1AP ID.

9. The method according to claim 6, in, The at least one UEID includes a globally unique access and mobility management function identifier GUAMI and an access and mobility management function user equipment NG application protocol identifier AMF UE NGAP ID.

10. The method according to claim 6, in, The RIC subscription request message is used to configure the O-CU-CP to send the indication message to the near RT RIC according to an event preset by the near RT RIC.

11. An apparatus for an open radio access network O-RAN central unit control plane O-CU-CP in a communication system, the apparatus include: Communication unit; A control unit configured to: receiving, via a communication unit, a RIC subscription request message from a near real-time RAN intelligent controller (near-RT RIC); In response to the RIC subscription request message, sending a RIC subscription response message to the near RT RIC via the communication unit; as well as When an event of the near RT RIC is generated, an indication message for reporting is sent to the near RT RIC via the communication unit, The indication message includes at least one user equipment UE identifier ID, and The at least one UE ID includes a RAN UE ID, and the RAN UE ID is used to identify the UE on the E1 interface between the O-CU-CP and the O-RAN CU-user plane O-CU-UP and on the F1 interface between the O-CU-CP and the distributed unit DU.

12. The device according to claim 11, in, The indication message includes UE context information, and The RAN UE ID is used to send a UE context establishment request message to the DU.

13. The device according to claim 11, in, at least one UE ID including a globally unique access and mobility management function identifier GUAMI and an access and mobility management function user equipment NG application protocol identifier AMF UE NGAP ID, and Among them, GUAMI and AMF UE NGAP ID are obtained from the initial context establishment request message, and the initial context establishment request message is received from the access and mobility management function AMF.

14. The device according to claim 11, in, At least one UE ID includes a globally unique mobility management entity identifier GUMMEI and a mobility management entity user equipment S1 application protocol identifier MME UE S1AP ID, and The GUMMEI and the MME UE S1AP ID are obtained from an initial context establishment request message, and the initial context establishment request message is received from a mobility management entity MME.

15. The device according to claim 11, in, The RIC subscription request message is used to configure the O-CU-CP to send the indication message to the near RT RIC according to an event preset by the near RT RIC.

16. A device for a near real-time radio access network RAN ​​intelligent controller (near RT RIC) in a communication system, the device include: Communication unit; A control unit configured to: Sending a RIC subscription request message to a node of an open radio access network O-RAN central unit control plane O-CU-CP via a communication unit; receiving, from the node of the O-CU-CP via the communication unit, a RIC subscription response message in response to the RIC subscription request message; and receiving an indication message for reporting from a node of the O-CU-CP via the communication unit, The indication message includes at least one user equipment UE identifier ID, and The at least one UE ID includes a RAN UE ID, and the RAN UE ID is used to identify the UE on the E1 interface between the O-CU-CP and the O-RAN CU-user plane O-CU-UP and on the F1 interface between the O-CU-CP and the distributed unit DU.

17. The device according to claim 16, in, The indication message includes UE context information, and The RAN UE ID is used to send a UE context establishment request message to the DU.

18. The device according to claim 16, in, The at least one UEID includes a globally unique mobility management entity identifier GUMMEI and a mobility management entity user equipment S1 application protocol identifier MME UE S1AP ID.

19. The device according to claim 16, in, The at least one UEID includes a globally unique access and mobility management function identifier GUAMI and an access and mobility management function user equipment NG application protocol identifier AMF UE NGAP ID.

20. The device according to claim 16, in, The RIC subscription request message is used to configure the O-CU-CP to send the indication message to the near RT RIC according to an event preset by the near RT RIC.

Images