Method and apparatus for handling secondary node operation in multi-RAT dual connectivity

Abstract

The present disclosure relates to a 5G communication system or a 6G communication system for supporting a higher data rate than a 4G communication system such as Long Term Evolution (LTE). The method includes receiving at least one piece of user equipment (UE) capability information from at least one UE, wherein the at least one piece of UE capability information includes post quantum cryptography (PQC) information; transmitting an SN addition request message including the PQC information to at least one secondary node (SN) based on the at least one UE capability information; if PQC is supported between the at least one UE and the at least one SN, receiving an SN addition request acknowledgement message from the at least one SN; and receiving an SN addition request rejection message from the at least one SN if PQC is not supported between the at least one UE and the at least one SN.

Description

Technical Field

[0001] The embodiments disclosed herein relate to a wireless communication network, and more particularly, to a process of adding or modifying a secondary node (SN) in multi-radio access technology (RAT)-dual connectivity (MR-DC). Background Art

[0002] Throughout the generations of wireless communication technology, these technologies have primarily been developed for human-oriented services such as voice calls, multimedia services, and data services. With the commercialization of 5G (fifth-generation) communication systems, the number of connected devices is expected to grow exponentially, with an increasing number of devices connected to communication networks. Examples of connected devices include vehicles, robots, drones, home appliances, displays, smart sensors connected to various infrastructure, construction machinery, and factory equipment. Mobile devices are expected to evolve into various forms, such as augmented reality glasses, virtual reality headsets, and holographic devices. To provide a variety of services in the 6G (sixth-generation) era by connecting hundreds of billions of devices and things, efforts are underway to develop improved 6G communication systems. For this reason, 6G communication systems are referred to as beyond 5G systems.

[0003] The 6G communication system, which is expected to be commercialized around 2030, will have a peak data rate of terabit (1000 gigabits) per second and a wireless delay of less than 100 microseconds, so its speed will be 50 times that of the 5G communication system and the wireless delay will be 1 / 10 of that.

[0004] To achieve such high data rates and ultra-low latency, 6G communication systems are being considered in the terahertz frequency band (e.g., 95 GHz to 3 THz). Because the terahertz band suffers from more severe path loss and atmospheric absorption than the millimeter-wave band introduced in 5G, technologies that ensure signal transmission distance (i.e., coverage) will become even more critical. Key technologies for ensuring coverage include the development of radio frequency (RF) components, antennas, new waveforms with improved coverage compared to orthogonal frequency division multiplexing (OFDM), beamforming and massive multiple-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, and multi-antenna transmission technologies such as massive antennas. Furthermore, new technologies to improve signal coverage in the terahertz band are under ongoing discussion, such as metamaterial-based lenses and antennas, orbital angular momentum (OAM), and reconfigurable smart surfaces (RIS).

[0005] Furthermore, to improve spectrum efficiency and overall network performance, the following technologies are being developed for 6G communication systems: full-duplex technology that enables uplink and downlink transmissions to use the same frequency resources simultaneously; network technologies that integrate and utilize satellites, high-altitude platform stations (HAPS), and other technologies; improved network structures that support mobile base stations and achieve network operation optimization and automation; dynamic spectrum sharing technology that enables conflict avoidance based on spectrum usage prediction; the application of artificial intelligence (AI) in wireless communications that improves overall network operation by leveraging artificial intelligence (AI) during the 6G development design phase and integrating end-to-end AI support capabilities; and next-generation distributed computing technologies that overcome the computing power limitations of UEs through network-accessible ultra-high-performance communication and computing resources such as mobile edge computing (MEC) and the cloud. Furthermore, efforts are ongoing to strengthen device connectivity, optimize networks, promote the softwareization of network entities, and increase the openness of wireless communications by designing new protocols for 6G communication systems, developing mechanisms to implement hardware-based security environments and secure data usage, and developing technologies to maintain privacy.

[0006] Research and development of 6G communication systems are expected to usher in the next generation of hyperconnected experiences, encompassing both human-to-machine (P2M) and machine-to-machine (M2M) connectivity. Specifically, 6G communication systems are expected to enable services such as truly immersive extended reality (XR), high-fidelity mobile holograms, and digital replicas. Furthermore, services such as remote surgery, industrial automation, and emergency response designed to enhance safety and reliability will be delivered through 6G communication systems, enabling the application of these technologies in various fields, including industry, healthcare, automotive, and home appliances. Summary of the Invention

[0007] Technical issues

[0008] The main purpose of the embodiments herein is to disclose a method and system for handling a Secondary Node (SN) procedure in a Multiple Radio Access Technology (RAT)-Dual Connectivity (MR-DC).

[0009] Another object of the embodiments herein is to disclose a process of adding or modifying a SN in a next generation network (eg, a sixth generation (6G) network).

[0010] Another object of the embodiments herein is to disclose a process for adding or modifying a SN in a 6G network, wherein security aspects related to PQC are disclosed when adding a SN.

[0011] Another object of the embodiments herein is to disclose a process for adding or modifying a SN in a 6G network, wherein security aspects related to PQC are disclosed when modifying the SN.

[0012] Another object of the embodiments herein is to disclose a method and system for handling SN procedures based on the types of security algorithms supported by the User Equipment (UE) and the network.

[0013] Another object of the embodiments herein is to disclose a process for adding a SN in a 6G network, wherein a primary cell and a secondary cell (PSCell) can be conditionally added with support for PQC.

[0014] Another object of embodiments herein is to disclose a method and system for performing SN addition, SN modification, and conditional SN addition procedures to handle the non-standalone (NSA) option when next generation RATs are introduced.

[0015] Another object of the embodiments herein is to disclose methods and systems for executing SN procedures to process new and improved security algorithms that are resistant to quantum computing.

[0016] Another object of the embodiments herein is to disclose the procedures and information elements required to be included in the SN modification procedure for handling a 6G Radio Access Network (RAN) node as a secondary node.

[0017] Technical Solution

[0018] Therefore, embodiments herein provide a method for processing the addition of a secondary node (SN) in a multi-radio access technology (RAT)-dual connectivity (MR-DC) network, performed by a master node (MN) in a wireless communication system. The method includes receiving at least one piece of UE capability information from at least one user equipment (UE). The UE capability information includes post-quantum cryptography (PQC) information. The method includes, based on the UE capability information, sending an SN add request message including the PQC information to at least one SN. If PQC is supported between the UE and the SN, the method includes receiving an SN add request acknowledgement message from the SN. Thereafter, if PQC is not supported between the UE and the SN, the method includes receiving an SN add request rejection message from the SN.

[0019] Therefore, embodiments herein provide a network mobile network (MN). The MN includes a processor configured to receive at least one UE capability information from at least one UE. The processor is configured to send, based on the UE capability information, an SN add request message including PQC information to at least one SN. The processor is configured to receive an SN add request confirmation message from the SN if PQC is supported between the UE and the SN. Furthermore, the processor is configured to receive an SN add request rejection message from the SN if PQC is not supported between the UE and the SN.

[0020] Therefore, an embodiment of the present invention provides a method for processing SN addition in an MR-DC. The method includes measuring, by a UE, one or more node parameters of one or more SNs based on service requirements to add at least one SN. The method includes selecting, by the UE, an SN with a strong cell from the one or more SNs based on the measured one or more node parameters. Thereafter, the MN indicates to the selected SN ID using its MN ID that the UE has requested to add the SN. The method includes receiving, by the UE, a radio resource control (RRC) reconfiguration message containing network data and one or more security parameters of the SN from the MN. Thereafter, the method includes initiating, by the UE, a random access channel (RACH) procedure for the selected SN. The SN sends an indication to the MN associated with the MN ID that the UE has requested to add the SN.

[0021] Therefore, embodiments herein provide a UE, comprising a processor. The processor is configured to measure one or more node parameters of one or more SNs based on service requirements to add the SNs. The processor is configured to select, from the one or more SNs, an SN with a strong cell based on the measured node parameters. The processor is configured to receive an RRC reconfiguration message from the mobile node including network data and one or more security parameters of the SN. Furthermore, the processor is configured to initiate a RACH procedure for the selected SN.

[0022] Therefore, embodiments herein provide a method for processing SN modification in an MR-DC. The method includes receiving, by a mobile network (MN) of a network, at least one UE capability information from at least one UE. The UE capability information includes PQC information. The method includes sending, by the MN, an SN modification request message including the PQC information to at least one SN based on the UE capability information. The method includes receiving, by the MN, an SN modification request confirmation message from the SN if PQC is supported between the UE and the SN. The method includes receiving, by the MN, an SN modification request rejection message from the SN if PQC is not supported between the UE and the SN.

[0023] Therefore, embodiments herein provide a mobile network (MN) for a network. The MN includes a processor configured to receive at least one UE capability information from at least one UE. The processor is configured to send an SN modification request message including PQC information to at least one SN based on the UE capability information. The processor is configured to receive an SN modification request confirmation message from the SN if PQC is supported between the UE and the SN. Furthermore, the processor is configured to receive an SN modification request rejection message from the SN if PQC is not supported between the UE and the SN.

[0024] These and other aspects of the present invention will be better understood in conjunction with the following description and accompanying drawings. However, it should be understood that the following description, while indicating exemplary embodiments and many specific details thereof, is given by way of illustration only and not limitation. Many changes and modifications may be made within the scope of the exemplary embodiments herein without departing from the scope of the exemplary embodiments herein, and the exemplary embodiments herein include all such modifications. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The embodiments of the present invention are illustrated in the accompanying drawings, wherein like reference characters indicate corresponding parts in the various figures. The embodiments of the present invention will be better understood from the following description with reference to the illustrative drawings. The embodiments of the present invention are illustrated by way of example in the accompanying drawings, wherein: Figure 1a and Figure 1b The present invention illustrates a control plane (C-plane) connection between a master node (MN) and a secondary node (SN) in a multi-radio access technology (RAT)-dual connectivity (MR-DC) according to the prior art; Figure 2a and Figure 2b FIG. 4 shows a user plane (U-plane) connection between a MN and a SN in an MR-DC according to the prior art; Figure 3a 、 Figure 3b and Figure 3c Various deployment options for introducing 6G radio access technology (RAT) based on existing technologies are shown; Figure 4 The present invention illustrates a procedure for adding a secondary gNodeB (SgNB) in E-UTRAN NR dual connectivity (ENDC) according to the prior art. Figure 5 The following describes the SN adding process in an MR-DC with a 5G core network according to the prior art. Figure 6 shows a conditional PSCell addition (CPA) process according to the prior art; Figure 7 A system is shown indicating communications between at least one UE and a network for handling SN operations in an MR-DC according to embodiments disclosed herein; Figure 8 shows multiple modules of a MN according to the embodiments disclosed herein; Figure 9 shows multiple modules of a SN according to the embodiments disclosed herein; Figure 10 Showing multiple modules of a processor of a UE according to the embodiments disclosed herein; Figure 11A method for processing SN addition in MR-DC performed by a MN according to an embodiment disclosed herein is shown; Figure 12 shows a message sequence chart indicating security aspects related to PQC in a SN addition procedure with 5GC according to an embodiment disclosed herein; Figure 13 shows a message sequence chart indicating PQC-related security aspects in an SN addition procedure with an evolved packet core (EPC) according to embodiments disclosed herein; Figure 14 1 shows a flow chart of evaluating PQC information at a SN according to an embodiment disclosed herein; Figure 15 A method of a CPA procedure with a PQC support table performed by a MN according to an embodiment disclosed herein is shown; Figure 16 shows a message sequence chart of a CPA process indicating the use of a PQC support table according to an embodiment disclosed herein; Figure 17 The method of the SN adding process initiated by the UE according to the embodiment disclosed herein is shown; Figure 18 A message sequence chart indicating a UE-initiated SN adding procedure according to an embodiment disclosed herein is shown; Figure 19 A method for processing SN modification in MR-DC according to an embodiment disclosed herein is shown; Figure 20 A message sequence chart illustrating security aspects related to PQC in an SN modification procedure indicating an NSA deployment option with 5GC according to an embodiment disclosed herein is shown; Figure 21 shows a message sequence chart indicating security aspects related to PQC in the S6gNB modification procedure with EPC according to the embodiments disclosed herein; Figure 22a A method for evaluating PQC information at a SN based on an SN modification request message according to an embodiment disclosed herein is shown; Figure 22b The implementation according to the embodiment disclosed herein is shown Figure 22a Step 1 of the method; and Figure 22c The implementation according to the embodiment disclosed herein is shown Figure 22a Step 2 of the method. DETAILED DESCRIPTION

[0026] The embodiments herein and their various features and advantageous details will be more fully explained with reference to non-limiting embodiments, which are illustrated in the accompanying drawings and described in detail in the following description. In order to avoid unnecessarily obscuring the embodiments herein, descriptions of well-known components and processing techniques have been omitted. The examples used herein are intended only to facilitate understanding of the manner in which the embodiments herein may be practiced and to further enable those skilled in the art to practice the embodiments herein. Therefore, these examples should not be construed as limiting the scope of the embodiments herein.

[0027] For purposes of interpreting this specification, the following definitions (as defined herein) shall apply, and whenever appropriate, terms in the singular shall include the plural, and vice versa. It should be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting. The terms "including," "having," and "comprising" are to be construed as open-ended terms unless otherwise indicated.

[0028] The words / phrases "exemplary," "example," "illustrative," "in an instance," "etc.," "such as," "etc.," "for example," and "i.e." are used herein merely to mean "serving as an example, instance, or illustration." Any embodiment or implementation of the subject matter described herein using the words / phrases "exemplary," "example," "illustrative," "in an instance," "etc.," "such as," "etc.," "etc.," "for example," and "i.e." are not necessarily to be construed as preferred or advantageous over other embodiments.

[0029] The embodiments herein may be described and illustrated in terms of blocks that perform the described functions. These blocks, which may be referred to herein as managers, units, modules, hardware components, etc., are physically implemented by analog and / or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hard-wired circuits, and the like, and are optionally driven by firmware. For example, the circuits may be embodied on one or more semiconductor chips, or on a substrate support such as a printed circuit board. The circuits comprising the blocks may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware for performing some of the functions of the block and a processor for performing other functions of the block. Each block of the embodiments herein may be physically separated into two or more interacting discrete blocks without departing from the scope of this disclosure. Similarly, the blocks of the embodiments herein may be physically combined into more complex blocks without departing from the scope of this disclosure.

[0030] It should be noted that the elements in the accompanying drawings are shown to facilitate understanding of the present description and are not necessarily drawn to scale. For example, a flow chart / sequence diagram illustrates a method in terms of the steps required to understand aspects of the embodiments herein. In addition, with respect to the construction of a device, one or more components of the device may be represented in the accompanying drawings with conventional symbols, and the accompanying drawings may only show those specific details relevant to understanding the present embodiment so as not to obscure the drawings with details that would be readily understood by a person of ordinary skill in the art upon reading the description herein. In addition, with respect to a system, one or more components / modules comprising the system may be represented in the accompanying drawings with conventional symbols, and the accompanying drawings may only show those specific details relevant to understanding the present embodiment so as not to obscure the drawings with details that would be readily understood by a person of ordinary skill in the art upon reading the description herein.

[0031] The accompanying drawings are used to facilitate easy understanding of various technical features, and it should be understood that the embodiments presented herein are not limited to the accompanying drawings. Therefore, the present disclosure should be interpreted as extending to any modifications, equivalents, and alternatives other than those specifically listed in the accompanying drawings and their corresponding descriptions. Unless otherwise specified, the use of words such as first, second, third, etc. to describe components / elements / steps is for the purpose of this description only and should not be interpreted as sequential order / position / occurrence.

[0032] Over the years, wireless technology has evolved to meet the ever-increasing demand for services and end-user requirements. The earliest generation of wireless communications, known as second generation, provided mobility and voice services, while third generation provided voice and data services. However, the growing demand for high-speed data necessitated further evolution, leading to the development of fourth-generation wireless communication systems. Within fourth-generation communication systems, a variety of architectural options were devised to deliver high-speed data. These systems included multi-carrier aggregation through carrier aggregation (CA) or dual connectivity (DC), which allowed operators to offer high data rates to every user by aggregating their radio resources.

[0033] However, due to the growing demand for high-speed data, even advances in fourth-generation technologies, such as carrier-based access (CA) and carrier-based access (DC), are insufficient to meet this growing demand. Therefore, fifth-generation wireless communication systems have been designed. New radio spectrum in the high- and mid-band millimeter wave (mmWave) spectrum has been deployed. With the deployment of new radio spectrum and to ensure early deployment of fifth-generation technologies, E-UTRAN NR Dual Connectivity (ENDC) is gaining widespread use and deployment worldwide. Fifth-generation technologies also define multiple dual connectivity options, providing global operators with the flexibility to deploy based on their business and user needs. Multi-Radio Access Technology (RAT) Dual Connectivity (MR-DC) is a generalized concept for Intra-EUTRA dual connectivity, in which multiple receiver / transmitter user equipment (UE) are configured to utilize resources on two different nodes over a non-ideal backhaul. Figure 1a and Figure 1b The control plane (C-plane) connection between the master node (MN) and the secondary node (SN) in MR-DC is shown. Figure 2a and Figure 2b The user plane (U-plane) connection between the MN and the SN in the MR-DC is shown.

[0034] The fifth generation is also expected to provide ultra-reliable low-latency and machine-type communications and enhanced use of mobile broadband. With the variety of use cases that are possible in the fifth generation, there is an increasing need to find sustainable, immersive, intelligent, and secure infrastructure to provide the next generation of services and demands that can sustain current use cases and enable new ones.

[0035] For next-generation wireless communication systems (e.g., 6G), various technologies are being considered, including visible light communication (VLC), the terahertz band (THz) (i.e., frequencies between 100 GHz and 3 THz), infrared waves, and ultraviolet waves. Among all these technologies, the THz band is considered a potential technology for a variety of applications at the nanometer, micrometer, and macroscale levels. Characteristics of the THz band include data rates of terabits per second (Tbps), reliable transmission, and minimal latency.

[0036] Frequencies between 100 GHz and 3 THz are promising frequency bands for next-generation wireless communication systems due to the extensive unused and unexplored spectrum. Based on available literature on THz-band communication systems, these frequencies also offer the potential for revolutionary applications in devices, circuits, software, signal processing, and systems. The ultra-high data rates offered by millimeter-wave and THz wireless local area networks and cellular networks enable ultra-fast download speeds for computer communications, autonomous vehicles, robotic control, information streaming, high-definition holographic gaming and entertainment, video conferencing, and high-speed wireless data distribution in data centers. Beyond their extremely high data rates, future millimeter-wave and THz systems have the potential to develop promising applications in 6G networks and beyond. In 6G, spectrum below 7 GHz and new spectrum from 7 GHz to 24 GHz may be used alongside THz spectrum to achieve sustainable growth.

[0037] In 6G, depending on the use case, cost, complexity, scalability, etc., existing deployment options may be reused, or new deployment options that are not standardized for 5G may be required. Figure 3a 、 Figure 3b and Figure 3c Various such deployment options for the introduction of 6G radio access technology (RAT) are shown.

[0038] There are multiple options for 6G deployment that apply to existing non-standalone (NSA) and standalone (SA) architecture options as well as new NSA architecture options. The following are possible (but not limited to) 6G network architecture options: - NSA: Core network: EPC, RAN: LTE-MCG + 6G-SCG - NSA: Core network: 5GC, RAN: NR-MCG + 6G-SCG With the introduction of 6G RAT, it is necessary to define changes / additions in the UE process of adding SN and the inter-node process of adding SN. The SN adding process currently defined in the 3GPP specification includes: - SN addition / modification based on blind / measurement; and - Conditional addition of primary and secondary cells (PSCells).

[0039] Figure 4 The figure shows the process of adding a secondary gNodeb (SgNB) in ENDC. Figure 5 The figure shows the SN Add procedure in an MR-DC with a 5G core network. The SN Add procedure is initiated by the mobile node to establish a UE context at the SN, so that resources can be provided from the SN to the UE. For bearers that require radio resources from a secondary cell group (SCG), this procedure is used to add at least the first cell of the SCG. Figure 4 and Figure 5 The process shown is included in 3GPP TS 37.340, and there are separate processes for SN addition for ENDC and for SN addition for MR-DC with 5G core network. Figure 6 The Conditional PSCell Addition (CPA) procedure is shown. CPA is defined as a PSCell addition performed by the UE when the execution conditions are met. The UE begins evaluating the execution conditions upon receiving the CPA configuration and stops evaluating the execution conditions once a PSCell addition or PCell change is triggered. In the case of CPA, the Conditional SN Addition procedure can be used for both CPA configuration and CPA execution. The CPA configuration contains the configuration of CPA candidate PSCells, the execution conditions, and may also include the Master Cell Group (MCG) configuration to be applied when CPA execution is triggered.

[0040] Quantum computers are machines that use quantum mechanical phenomena to solve mathematical problems that are intractable for conventional computers. Such quantum computers are capable of cracking conventional cryptographic algorithms. If such systems are deployed in digital and communication systems, developing quantum-resistant cryptographic algorithms is crucial to ensuring the security of future communication systems. Post-quantum cryptography (PQC) refers to a set of algorithms that are considered secure even against quantum computers, a level of security unattainable by conventional algorithms, and can be used in 6G networks. Therefore, the use of PQC algorithms requires processes that address non-standalone mode operation in next-generation wireless communication systems.

[0041] Embodiments herein implement secondary node (SN) addition, SN modification, and conditional SN addition procedures to handle non-standalone (NSA) options when next generation (NG) (e.g., 6G) radio access technologies (RATs) are introduced. These procedures are intended to handle new and improved security algorithms that are quantum resistant. Referring now to the accompanying drawings, embodiments are shown, and more particularly with reference to Figures 7 to 22c , wherein like reference characters denote corresponding features throughout the drawings.

[0042] Figure 7 A system 700 is shown indicating communications between at least one user equipment (UE) 702 and a network 704 for handling SN operations in MR-DC. The system 700 includes at least one UE 702 and the network 704. The UE 702 also includes a processor 706, a communication module 708, and a memory module 710. The network 704 also includes a master node (MN) 712 and one or more secondary nodes (SNs) 714 (e.g., SN1, SN2, ..., SNn).

[0043] In the embodiment of this document, the MN 712 further includes a processor 802, a communication module 804, and a memory module 806. Figure 8As shown. Processor 802 includes an SN operation module 808, a PQC support module 810, and an RRC module 812. SN operation module 808 may receive at least one UE capability information from at least one UE 702. The UE capability information may include post-quantum cryptography (PQC) information. Based on the UE capability information, SN operation module 808 may send an SN add request message or an SN modify request message including PQC information to at least one SN 714. The SN add request message or SN modify request message may include information about one or more candidate cells. The information about the one or more candidate cells may include measurement results of one or more node parameters of one or more SNs 714 for selecting and configuring at least one SN. In the embodiments herein, the SN add request message or SN modify request message may include UE capability information and UE capability coordination results. The UE capability information may include RAT information, which may include a 6G RAT. Therefore, the UE capability and UE capability coordination results may be sent from MN 712 to SN 714 or a secondary cell group (SCG).

[0044] In the embodiments herein, the PQC information includes at least one PQC support and at least one PQC profile or related PQC parameters. The PQC support indicates whether the UE 702 supports at least one of the following: PQC, traditional security methods, or both PQC and traditional security methods. The PQC profile or related PQC parameters indicate whether the UE 702 supports related mechanisms for PQC support. In the embodiments herein, the traditional security methods may include, but are not limited to, at least one security support of the SN 714 of the network 704. The security support may include, but are not limited to, one or more security capabilities and one or more security keys.

[0045] In the embodiment of this document, if PQC is supported between the UE 702 and the SN 714, the SN operation module 808 may receive an SN add request confirmation message or an SN modify request confirmation message from the SN 714. In the embodiment of this document, if PQC is not supported between the UE 702 and the SN 714, the SN operation module 808 may receive an SN add request rejection message or an SN modify request rejection message from the SN 714.

[0046] In embodiments herein, the PQC support module 810 is configured with a PQC support table. This PQC support table is configured and maintained at the mobile station (MN) 712, enabling the PQC support module 810 to evaluate PQC information between the UE 702 and at least one SN 714. The PQC support table includes one or more values ​​indicating PQC information between the UE 702 and the SN 714. In embodiments herein, the PQC support module 810 may evaluate the PQC support tables of one or more SNs 714 to perform a conditional primary / secondary cell (PSCell) addition (CPA) procedure. Based on this evaluation, the MN 712 may send at least one SN add request message or at least one SN modify request message to the SN 714 via the SN operation module 808. The SN operation module 808 may receive at least one SN add request confirmation message or at least one SN modify request confirmation message in response to the SN add request message or the SN modify request message.

[0047] In an embodiment herein, the RRC module 812 may send a radio resource control (RRC) reconfiguration message to the UE 702, the RRC reconfiguration message including information about one or more SNs 714 in the received SN add request confirm message, so that the UE 702 can evaluate the conditional configuration of the SNs 714. After receiving the SN add request confirm message or the SN modify request confirm message from the SN 714, the RRC module 812 may send the RRC reconfiguration message including network data and one or more security parameters to the UE 702. The SN add request confirm message or the SN modify request confirm message may include, but is not limited to, RRC reconfiguration information related to at least one SN 714 of the network 704 and the global cell identifier of the SN 714 of the network 704 for the UE 702 to perform a CPA procedure. After completing the reconfiguration based on the network data and the security parameters, the RRC module 812 may receive an RRC reconfiguration complete message from the UE 702.

[0048] In the embodiment of this document, the SN 714 further includes a processor 902, a communication module 904, and a memory module 906. Figure 9As shown. Processor 902 includes a PQC evaluation module 908. In the embodiment herein, PQC evaluation module 908 may receive an SN add request message or an SN modify request message including PQC information based on UE capability information from SN operation module 808 of MN 712. PQC evaluation module 908 may evaluate PQC information between UE 702 and at least one SN 714 based on the received SN add request message or SN modify request message. PQC evaluation module 908 may determine whether UE 702 supports PQC. If UE 702 supports PQC, PQC evaluation module 908 may verify whether SN 714 supports PQC. If both UE 702 and SN 714 support PQC, PQC evaluation module 908 may send an SN add request confirmation message or an SN modify request confirmation message including a PQC security method to SN operation module 808 of MN 712. The SN add request confirmation message or the SN modify request confirmation message may include, but is not limited to, RRC reconfiguration information related to at least one SN 714 of the network 704, and the global cell identifier of the SN 714 of the network 704 used by the UE 702 to perform the CPA procedure. The PQC evaluation module 908 may transmit a PQC profile or related PQC parameters used by the UE 702 to the MN 712 when PQC is supported between the UE 702 and the SN 714. In the embodiments herein, if the UE 702 supports PQC and a traditional security method, but the SN 714 does not support PQC, the PQC evaluation module 908 may send an SN add request confirmation message or an SN modify request confirmation message including the traditional security method. In the embodiments herein, if the UE 702 supports PQC and the SN 714 supports the traditional security method, the PQC evaluation module 908 may send an SN add request rejection message or an SN modify request rejection message to the SN operation module 808 of the MN 712.

[0049] In the embodiments herein, the PQC evaluation module 908 may determine whether the UE 702 supports PQC. The PQC evaluation module 908 may verify whether the SN 714 supports legacy security methods when the UE 702 does not support PQC. If the UE 702 does not support PQC and the SN 714 does support legacy security methods, the PQC evaluation module 908 may send an SN add request confirmation message or an SN modify request confirmation message containing the legacy security methods. If the UE 702 does not support PQC and the SN 714 does not support legacy security methods, the PQC evaluation module 908 may send an SN add request rejection message or an SN modify request rejection message.

[0050] In the embodiment of this document, the PQC evaluation module 908 may update one or more security parameters after the evaluation. For example, the security parameters may include but are not limited to the PQC algorithm, key length, security level, and other security parameters.

[0051] In the embodiment of this document, the PQC evaluation module 908 may be configured and maintained with a PQC support table to evaluate PQC information between the UE 702 and the SN 714. The PQC support table includes one or more values ​​indicating PQC information between the UE 702 and the SN 714.

[0052] In the embodiments herein, the communication module 904 of the SN 714 may receive random access channel (RACH) initiation information from the UE 702 .

[0053] In the embodiment of this document, the processor 706 further includes a UE information module 1002, an SN evaluation module 1004, and a RACH module 1006. Figure 10 In the embodiment of this document, the UE information module 1002 may send at least one UE capability information to the SN operation module 808 of the MN 712. The UE capability information includes PQC information. The UE capability information includes RAT information, and the RAT information includes 6G RAT.

[0054] In the embodiments herein, the SN evaluation module 1004 may receive an RRC reconfiguration message from the RRC module 812 of the MN 712. The RRC reconfiguration message includes information about one or more SNs 714, enabling the UE 702 to evaluate the conditional configuration of the one or more SNs 714. The conditional configuration includes one or more conditional event-related parameters of the RAT of the network 704, which are required to trigger the UE-side CPA procedure. For example, a conditional event is a measurement event configured with specific conditions. When the specific conditions are met, the UE 702 automatically adds the SN 714. The conditional event-related parameters may include, but are not limited to, a conditional event ID, a hysteresis, a trigger time, etc. The SN evaluation module 1004 may evaluate one or more security parameters of at least one SN 714 to match the PQC capabilities of the UE 702. The SN evaluation module 1004 may determine whether the conditional configuration of the corresponding SN 714 needs to be evaluated. If conditional configuration is required, the SN evaluation module 1004 may evaluate the conditional configuration of the SN 714. If the evaluated conditions are met, the SN evaluation module 1004 may connect to the desired at least one SN 714.

[0055] In embodiments herein, RACH module 1006 may measure one or more node parameters of one or more SNs 714 based on service requirements to add at least one SN. MN 712 may configure all available measurement objects in one or more SNs 714. UE 702 is aware of its service or data requirements. RACH module 1006 may select at least one SN with a strong cell from one or more SNs 714 based on the measured node parameters. MN 712 may then indicate to the selected SN ID using its MN ID that UE 702 has requested to add SN 714. RACH module 1006 may receive an RRC reconfiguration message from MN 712 containing network data and one or more security parameters of SN 714. RACH module 1006 may initiate a RACH procedure for the selected SN. SN 714 may send an indication to the MN 712 associated with the MN ID that UE 702 has requested to add SN 714.

[0056] In the embodiments herein, processors 706, 802, and 902 may process and execute data from multiple modules of UE 702, MN 712, and one or more SNs 714, respectively. Processors 706, 802, and 902 may be configured to execute instructions stored in memory modules 710, 806, and 906, respectively. Processors 706, 802, and 902 may include one or more microprocessors, circuits, and other hardware configured for processing. Processors 706, 802, and 902 may be at least one of a single processor, multiple processors, multiple homogeneous or heterogeneous cores, multiple central processing units (CPUs) of different types, microcontrollers, dedicated media, and other accelerators. Processors 706, 802, and 902 may be application processors (APs), units dedicated only to graphics processing (e.g., graphics processing units (GPUs) or visual processing units (VPUs)), and / or processors dedicated to artificial intelligence (AI) (e.g., neural processing units (NPUs)).

[0057] In the embodiments herein, multiple modules of the processor 706 of the UE 702, the processor 802 of the MN 712, and the processor 902 of the SN 714 can communicate via the communication modules 708, 804, and 904, respectively. Communication between the UE 702, the MN 712, and one or more SNs 714 is performed via the communication modules 708, 804, and 904. The communication modules 708, 804, and 904 can be in the form of wired or wireless communication network modules. Wireless communication networks may include, but are not limited to, Global Positioning System (GPS), Global System for Mobile Communications (GSM), Wi-Fi, Bluetooth Low Energy, Near Field Communication (NFC), and the like. Depending on the usage environment, wireless communication may further include one or more of Bluetooth, ZigBee, short-range wireless communication (e.g., ultra-wideband (UWB)), medium-range wireless communication (e.g., Wi-Fi), or long-range wireless communication (e.g., 3G / 4G / 5G / 6G and non-3GPP technologies or WiMAX).

[0058] In the embodiments herein, memory modules 710, 806, and 906 may include one or more volatile and non-volatile memory components capable of storing data and instructions to be executed by modules of UE 702, MN 712, and one or more SNs 714. Examples of memory modules 710, 806, and 906 may include, but are not limited to, NAND, embedded MultiMediaCard (eMMC), secure digital (SD) card, universal serial bus (USB), serial advanced technology attachment (SATA), solid-state drive (SSD), and the like. In some examples, memory modules 710, 806, and 906 may also include one or more computer-readable storage media. Examples of non-volatile storage elements may include magnetic hard disks, optical disks, floppy disks, flash memory, or electrically programmable programmable memory (EPROM) or electrically erasable programmable programmable memory (EEPROM). Furthermore, in some examples, memory modules 710, 806, and 906 may be considered non-transitory storage media. The term "non-transitory" may indicate that the storage media is not contained within a carrier wave or propagating signal. However, the term "non-transitory" should not be interpreted as meaning that memory modules 710, 806, and 906 are non-removable. In some examples, non-transitory storage media may store data that changes over time (eg, in random access memory (RAM) or cache).

[0059] Figure 7Example modules of UE 702 and network 704 are shown separately, but it should be understood that other embodiments are not limited thereto. In other embodiments, UE 702 and network 704 may include fewer or more modules. Furthermore, the labels or names of the modules are for illustrative purposes only and do not limit the scope of the present invention. One or more modules may be combined to perform the same or substantially similar functions in UE 702 and network 704.

[0060] Figure 11 A method 1100 for processing SN addition in an MR-DC, performed by a mobile station (MN) 712, is shown. The method 1100 includes receiving, by the MN 712, at least one UE capability information from at least one UE 702, as shown in step 1102. The UE capability information includes PQC information. The method 1100 includes sending, by the MN 712, an SN add request message including PQC information to at least one SN 714 based on the UE capability information, as shown in step 1104. The method 1100 includes receiving, by the MN 712, an SN add request confirmation message from the SN 714 if PQC is supported between the UE 702 and the SN 714, as shown in step 1106.

[0061] The method 1100 includes, after receiving the SN add request confirm message from the SN 714, sending an RRC reconfiguration message including network data and one or more security parameters to the UE 702 by the MN 712, as shown in step 1108. The method 1100 includes, after the reconfiguration based on the network data and the security parameters is completed, receiving an RRC reconfiguration complete message from the UE 702 by the MN 712, as shown in step 1110. In addition, the method 1100 includes, if PQC is not supported between the UE 702 and the SN 714, receiving an SN add request reject message from the SN 714 by the MN 712, as shown in step 1112.

[0062] The various actions in method 1100 may be performed in the order shown, in a different order, or simultaneously. In addition, in some embodiments, the Figure 11 Some of the actions listed in .

[0063] Figure 12 A message sequence chart 1200 is shown, illustrating security aspects related to PQC in the SN add procedure with the 5G Core Network (5G Core Network). For example, new and improved algorithms such as PQC, which are quantum-resistant, may be introduced in the security of 6G systems. Message sequence chart 1200 discusses methods and procedures for handling SN add based on the types of security algorithms supported by the UE 702 and network 704. Message sequence chart 1200 illustrates the 6G SN add procedure with the MN 712 acting as the 5G and 5GC network.

[0064] As shown in step 1206, UE capability information including PQC information is sent from UE 702 to MN 712. As shown in step 1208, a measurement report for SN addition is sent from UE 702 to MN 712. The measurement report contains the measured signal levels of different cells by UE 702. An SN Add Request message including PQC information is sent from MN 712 to SN 714, as shown in step 1210. SN 714 evaluates the PQC information between UE 702 and SN 714 and sets security parameters, as shown in step 1212. If PQC is supported between UE 702 and SN 714, an SN Add Request Confirm message is sent from SN 714 to MN 712, as shown in step 1214. Otherwise, if UE 702 or SN 714 does not support PQC, an SN Add Request Reject message is sent from SN 714 to MN 712, as shown in step 1216.

[0065] After receiving the SN Add Request Confirm message, MN 712 sends an RRC Reconfiguration message (e.g., including 6G RRC reconfiguration and security configuration details) to UE 702, as shown in step 1218. Furthermore, after completing the reconfiguration based on the network data and one or more security parameters, UE 702 sends an RRC Reconfiguration Complete message to MN 712, as shown in step 1220. The SN Reconfiguration Complete message is sent from MN 712 to SN 714, as shown in step 1222. Furthermore, as shown in step 1224, a bearer is established between UE 702, MN 712, SN 714, user plane function (UPF) 1202, and access and mobility management function (AMF) 1204, and a data forwarding process is implemented.

[0066] Figure 13 A message sequence chart 1300 is shown, illustrating security aspects related to PQC in the SN add procedure with an evolved packet core (EPC). For example, message sequence chart 1300 illustrates a 6G SN add procedure with MN 712 as the 4G and EPC network. As shown in step 1306, UE capability information including PQC information is sent from UE 702 to MN 712. A measurement report for adding an S6gNB (6G next generation base station) is sent from UE 702 to MN 712, as shown in step 1308. Based on the UE capability information and the measurement report, MN 712 sends an S6gNB Add Request message including PQC information to SN 714, as shown in step 1310.

[0067] SN 714 evaluates the PQC information between UE 702 and SN 714 and sets or updates security parameters, as shown in step 1312. If PQC is supported between UE 702 and SN 714, SN 714 sends an S6gNB Add Request Confirm message to MN 712, as shown in step 1314. Otherwise, if UE 702 or SN 714 does not support PQC, SN 714 sends an S6gNB Add Request Reject message to MN 712, as shown in step 1316. Furthermore, after receiving the S6gNB Add Request Confirm message, MN 712 sends an RRC Reconfiguration message containing 6G RRC reconfiguration and security configuration details to UE 702, as shown in step 1318. After completing the RRC connection reconfiguration, UE 702 sends an RRC Reconfiguration Complete message to MN 712, as shown in step 1320. In addition, as shown in step 1322, a bearer is established between the UE 702, the MN 712, the SN 714, the S-GW 1302 and the mobility management entity (MME) 1304, and the data forwarding process is implemented.

[0068] Table 1 shows the PQC-related information within the SN Add Request message. The SN Add Request message includes aspects related to PQC support. MN 712 prepares an SN / S6gNB Add Request message containing UE capabilities, particularly security-related elements, for transmission to SN 714. The UE capability information carries PQC support capability information. The following SN Add Request message is used when MN 712 is a 5G RAT and SN 714 is a 6G RAT.

[0069]

Table 1

[0070] As shown in Table 2, a new IE for PQC information is introduced in the SN Add Request message. Details within the PQC information may include PQC support and PQC profiles. As shown in the table, PQC support can be divided into three types, such as PQC, traditional security methods, or both PQC and traditional security methods. The PQC profile or related PQC parameters indicate whether the UE supports at least one related mechanism for PQC support. For example, when PQC is supported, the related profile or algorithm is shared as P1, P2, P3, etc. Based on the PQC-related content in the SN Add Request message, the SN 714 needs to evaluate the PQC support of the UE 702 and the SN, update the security parameters, and determine whether the UE is allowed to add the SN 714.

[0071]

Table 2

[0072] Table 3 indicates the S6gNB add request message.

[0073]

Table 3

[0074] As shown in Table 4, the S6gNB Add Request message introduces a new IE for PQC information. This 6gNB Add Request message is used when the MN 712 is 4G and the SN 714 is 6G RAT.

[0075]

Table 4

[0076] Table 5 indicates the PQC parameters that can be exchanged between network nodes / UEs:

Table 5

[0077] PQC Algorithm: PQC Algorithm is a list of all supported algorithms. In Table 5, classic McEliece, Crtystals-Kyber, NTRU and SABER are listed as possible candidates for standardization.

[0078] Security Level: Indicates whether it has the highest level of security including quantum safety.

[0079] Key Length: Indicates the length of the supported encryption keys. The key length is a numeric value, denoted as n. The range of this key length may be specified in detail when the specification is detailed.

[0080] Security Parameters: This indicates a further list of unique security parameters required for each algorithm during the exchange

[0081] Figure 14 A flowchart 1400 is shown for evaluating PQC information at SN 714. Based on the PQC-related content in the SN Add Request message received from MN 712, SN 714 needs to evaluate PQC support of UE 702 and SN 714, update security parameters, and determine whether to allow UE 702 to add SN 714. As shown in step 1402, the SN Add Request message carries PQC information, which includes PQC support supported on the UE 702 side and related PQC profiles or related PQC parameters or algorithms.

[0082] SN 714 determines whether UE 702 supports PQC, as shown in step 1404. If UE 702 supports PQC, SN 714 checks whether it supports PQC, as shown in step 1406. If both UE 702 and SN 714 support PQC, PQC is prioritized, and an SN Add Request Confirm message including PQC as the preferred security method is sent from SN 714 to MN 712, as shown in step 1408. If UE 702 supports PQC and a traditional security method, but SN 714 does not support PQC, an SN Add Request Confirm message including the traditional security method is sent from SN 714 to MN 712, as shown in step 1412. Verification of whether UE 702 supports the traditional security method is performed in step 1410. If UE 702 only supports PQC and SN 714 only supports legacy security methods, the SN add request is rejected due to the capability mismatch between UE 702 and SN 714, as shown in step 1414.

[0083] If UE 702 does not support PQC, as shown in step 1404, and if SN 714 supports legacy security methods, the SN add request is confirmed using the legacy security method, as shown in step 1418. Verification of whether SN 714 supports legacy security methods is performed in step 1416. If UE 702 does not support PQC and SN 714 does not support legacy security methods (i.e., if SN 714 only supports PQC, in which case the capabilities of the UE and SN do not match), the SN add request is rejected, as shown in step 1414. To further optimize the process, a table can be maintained to update PQC support, and the PQC support table can be referenced whenever the SN 714 add or SN modify procedure is called, as shown in step 1420.

[0084] Table 6 indicates an exemplary PQC support table.

[0085]

Table 6

[0086] The PQC support table can be maintained at the MN 712 or SN 714 to optimize SN addition by taking PQC support into account. Assume that the Xx interface between the MN 712 and the SN 714 is used for either deployment option of NSA with 6G RAT. ID is an integer value that can be ranged. MN node UE XxAP ID indicates the ID assigned at the MN 712 for the UE 702 using the Xx interface, and SN (6G) node UE XxAP ID is the ID assigned at the SN-6G 714. PQC Support is a set of values ​​that indicate, for a given ID assigned by the MN 712 or SN 714 to the UE 702 on the Xx interface, the overall result of PQC support: Legacy, PQC Supported, or SN Rejected.

[0087] When updating the PQC support table with these values, SN 714 does not need to evaluate the PQC information. SN 714 can directly reference the PQC support between UE 702 and SN 714 from the table and make a decision accordingly. PQC support between UE 702 and SN 714 is evaluated at SN 714, and an SN Add Request Confirm message or an SN Add Request Reject message is sent by SN 714 accordingly. Alternatively, the PQC support table can be maintained at MN 712, and the evaluation can then be performed at MN 712.

[0088] In the case of the S6gNB / SN Add Request message - Measurement, when the 6G RAT is introduced in the SN 714, specification modifications are required to certain messages and related IEs. During SN Add, an SN Add Request message is sent from the MN 712 to the SN 714. The SN Add Request message carries relevant information that the SN 714 needs to prepare and serve the UE 702. For example, CG-ConfigInfo is one such IE that carries relevant information and needs to be updated to include 6G RAT related information.

[0089] Table 7 indicates an exemplary SN add request where the MN is 5G and the SN is 6G.

[0090]

Table 7

[0091] Table 8 indicates an exemplary S6gNB add request where the MN is 4G and the SN is 6G.

[0092]

Table 8

[0093] As shown in Table 7 and Table 8, when an S-Node add request message or an S6gNB add request message is sent, CG-ConfigInfo needs to be updated to include 6G RAT information related to measurement.

[0094] The S6gNB / SN Add Request message may include measurement and / or CG-ConfigInfo. This message is used to convey the SCG radio configuration generated by the SgNB or SeNB. It can also be used by the Centralized Unit (CU) to request the Distributed Unit (DU) to perform certain actions; for example, requesting the DU to perform new low-layer configuration. CG-ConfigInfo may be represented as shown in Table 9 below.

[0095]

Table 9

[0096] For example, add IE within CG-ConfigInfo. In CG-ConfigInfo-vXX-IE, vXX indicates the specification containing these changes. CandidateCellInfoList6GMN and CandidateCellInfoList6GSN are included in CG-ConfigInfo-vXX-IEs, which have MeasResult6G. The measurement results can be expressed as shown in the following Table 10:

Table 10

[0097] MeasResult6G, MeasResultList6G: Contains PCI / TRP ID and related measurement results.

[0098] Frequencynumber-6G: indicates the related arfcn of the serving frequency.

[0099] In the case of the SN / SgNB Add Request message used for UE capability transmission, according to the SN Add call flow, the SN Add Request message contains the information required by the SN 714 to prepare a suitable SN cell for the UE 702. The SN Add Request message includes UE capability information. The UE capability information is transmitted in the CG-ConfigInfo IE shown in Table 11. When 6G RAT is introduced, the IE needs to be modified to include RAT information and 6G RAT capability information, and these changes need to be addressed.

[0100]

Table 11

[0101] For example, ue-CapabilityInfo contains the IE UE-CapabilityRAT-ContainerList supported by the UE 702. The gNB that retrieves the MR-DC related capability container ensures that the set of included MR-DC containers is consistent with respect to the feature set related information.

[0102] In the case of the S6gNB / SN Add Request message - UE Capabilities, Table 12 indicates whether the RAT capabilities are included in the ue-CapabilityInfo for each MN RAT and SN RAT. If the UE Radio Capability ID is not specified, 6G RAT related information needs to be added to the UE Capabilities.

[0103]

Table 12

[0104] Table 12 includes the existing Evolved UMTS Terrestrial Radio Access (EUTRA) and New Radio (NR) RATs. However, when 6G RATs are introduced, the table will need to include a direction for including 6G capabilities for EUTRA-6G or NR-6G as MN-SN, respectively. 6G Capability and MR-DC Capability columns are added, and are added to the SN RAT in the above table.

[0105] In the S6gNB / SN Add Request message - Legacy Security, the UE Security Capability IE defines the encryption and integrity protection algorithms supported by UE 702, and the S-NG-RAN Node Security Key IE is used to apply security to the S-NG-RAN node, as defined in TS 33.501. With the introduction of 6G RAT, these IEs need to include 6G RAT information and S-NG-RAN node security keys for security, as shown in Tables 13 and 14 below, which include the 6G UE Security Capability IE and the S-6G-RAN Node Security Key IE / S6gNB Security Key IE. Table 13 indicates the SN Add Request (5G-MN, 6G-SN).

[0106]

Table 13

[0107] Table 14 indicates S6gNB add request (4G-MN, 6G-SN).

[0108]

Table 14

[0109] The S-6G-RAN node security key and S6gNB security key are keys provided by the MN.

[0110] In the case of S6gNB / SN Add Request Message - Legacy Security, the 6G UE Security Capability IE defines the ciphering and integrity protection algorithms supported in the UE 702. Table 15 indicates the 6G ciphering algorithm and the 6G integrity protection algorithm.

[0111]

Table 15

[0112] In this embodiment, the SN Add Request Confirmation message includes CG-Config, which contains RadioBearerConfig. RadioBearerConfig is defined in TS 38.331 and includes the corresponding bearer's SecurityAlgorithmConfig. To reflect PQC support, the network-side PQC algorithm and PQC support are indicated in the RRC Reconfiguration message. Table 16 shows the SN Add Request Confirmation message.

[0113] Table 16

[0114] Table 17 indicates the S6gNB add request confirmation message.

[0115]

Table 17

[0116] For example, when 6G RAT is introduced to the SN, certain messages and related IEs need to be modified. During SN addition, according to known procedures, an SN Add Request Confirm message is sent from SN 714 to MN 712. This message carries relevant information notifying MN 712 about the SN. CG-Config is one such IE that carries relevant information and needs to be updated to include 6G RAT-related information.

[0117] In the case of SN add request confirmation, CG-Config can be represented as shown in the following Table 18:

Table 18

[0118] For example, IEs have been added to CG-Config. In CG-Config-vXX-IE, vXX indicates the specifications that may include these changes. scg-CellGroupConfig6G, candidateCellInfoListSN-6G, and scellFrequenciesSN-6G are included in CG-Config-vXX-IE.

[0119] Scg-CellGroupConfig6G IE—carries the RRC reconfiguration information of the 6G SN.

[0120] CandidateCellInfoListSN-6G—contains information about the cells that the source secondary node recommends the target secondary node to consider configuring.

[0121] ScellFrequenciesSN-6G—Indicates the frequencies of all secondary cells (Scells) configured with synchronization signals.

[0122] In the case of the SN Add Request Confirm IE, such as during RRC reconfiguration, 6G RAT-related information needs to be added to the CG-Config from the SN (6G RAT) to the MN (NR or Long Term Evolution (LTE)), depending on the situation. scg-CellGroupConfig and scg-CellGroupConfigEUTRA—carry RRC reconfiguration information. Similarly, scg-CellGroupConfig6G is required to carry the RRC reconfiguration message. Table 19 indicates the RRC reconfiguration.

[0123]

Table 19

[0124] For example, the candidate cell information list SN contains information about the cells that the source secondary node recommends the target secondary node to consider configuring. Similarly, the 6G RAT-related IE (Candidate Cell Information List-6G) requires 6G candidate cells to be configured for the target SN. Table 20 shows the candidate cell information list SN.

[0125] Table 20

[0126] For example, frequencies configured in the SN, such as scellFrequenciesSN-EUTRA and scellFrequenciesSN-NR, indicate the frequencies of all SCells in the SCG with synchronization signal blocks (SSBs) configured. The scellFrequenciesSN-EUTRA field is used in NE-DC; the scellFrequenciesSN-NR field is used in (NG) E-UTRAN NR Dual Connectivity (ENDC) and New Radio Dual Connectivity (NR-DC). In (NG) ENDC, this field is optionally provided to the MN. scellFrequenciesSN-NR indicates the absoluteFrequencySSB. Similarly, 6G SN frequencies need to be added. Therefore, scellFrequenciesSN-6G has been added, containing 6G frequency numbers. Table 21 shows scellFrequenciesSN.

[0127] Table 21

[0128] In case of SN add request confirmation for PQC, RadioBearerConfig can be represented as in the following Table 22.

[0129] Table 22

[0130] The IE RadioBearerConfig is used to add, modify, and release signaling, multicast radio bearers (MRBs), and / or data radio bearers. Additionally, a USE PQC IE is defined within RadioBearerConfig and is set to TRUE. If the USE PQC IE is absent, it indicates that PQC is not supported and that the UE 702 may use the legacy algorithm.

[0131] In addition, UE procedures for handling PQC support are defined in TS 3x.331. The added aspects of AS security key update can be represented as shown in Table 23 below.

[0132] Table 23

[0133] In SecurityAlgorithmConfig, additional PQC algorithms can be added to indicate the set of algorithms supported within PQC, such as P1, P2, P3, etc. SecurityAlgorithmConfig can be represented as shown in Table 24 below: Table 24

[0134] In the case of the SN addition procedure on the UE side with an NR Master Cell Group (MCG), specification 38.331 describes the reception of the RRC reconfiguration message for SN addition. The RRC reconfiguration message and procedure need to handle 6G SCG information. 6G-SCG information needs to be added to handle the RRC configuration information of the 6G SN.

[0135] 5.3.5.3 UE receives RRCReconfiguration

[0136] When the UE receives an RRCReconfiguration or performs a conditional reconfiguration (Conditional Handover (CHO), CPA or Cooperative Hierarchical Caching (CPC)), it shall perform the following actions: 1> If RRCReconfiguration includes mrdc-SecondaryCellGroupConfig: 2>If mrdc-SecondaryCellGroupConfig is set to establish: 3> If mrdc-SecondaryCellGroupConfig includes mrdc-ReleaseAndAdd: 4> Execute MR-DC release in accordance with the provisions of Section 5.3.5.10; 3> If the received mrdc-SecondaryCellGroup is set to nr-SCG: 4> Perform RRC reconfiguration for the RRCReconfiguration message contained in nr-SCG in accordance with 5.3.5.3; 3> If the received mrdc-SecondaryCellGroup is set to eutra-SCG: 4> Perform RRC connection reconfiguration according to clause 5.3.5.3 of TS 36.331

[10] for the RRCConnectionReconfiguration message contained in the eutra-SCG; 3> If the received mrdc-SecondaryCellGroup is set to 6G-SCG: 4> Perform RRC connection reconfiguration. The 6G RRC specification should describe the process of configuring the contents of this message.

[0137] Mrdc-SecondaryCellGroup can be represented as shown in Table 25 below: Table 25

[0138] 6G SCG is an OCTET string containing the RRC reconfiguration message of the 6G SN.

[0139] When 6G RAT is added, in the case of SN addition procedure on the UE side with LTE MCG, it is necessary to add procedures and IEs to define 6G-SecondaryCellGroupConfig. The UE receives RRCConnectionReconfiguration without mobilityControlInfo as follows: 1> If the UE is in EN-6GDC; and 1> If RRCConnectionReconfiguration does not include 6G-SecondaryCellGroupConfig: 2> If RRCConnectionReconfiguration includes scg-State: 3> Perform SCG deactivation according to the 6G RRC specification; 2> Otherwise: 3> Perform SCG activation without SN message according to the 6G RRC specification; 1> If the received RRCConnectionReconfiguration includes 6G-Config and it is set to release: or 1> If the received RRCConnectionReconfiguration includes EN-6GDC-ReleaseAndAdd and it is set to TRUE: 2> Release MR-DC according to the 6G RRC specification; 1> If the received RRCConnectionReconfiguration includes 6G-SecondaryCellGroupConfig: 2> Perform NR RRC reconfiguration as specified in the 6G RRC specification; 6G-SecondaryCellGroupConfig includes the 6G RRCReconfiguration message as specified in the 6G RRC specification. 6G-SecondaryCellGroupConfig can be represented as shown in Table 26 below: Table 26

[0140] In the case of SN Add Request Reject with PQC Support, if there is a mismatch in the capabilities related to PQC support between UE 702 and SN 714, the SN Add Request Reject procedure is initiated. The following variations for handling this situation are determined. Table 27 indicates SN Add Request Reject.

[0141] Table 27

[0142] The purpose of the 'Reason' IE is to indicate the cause of the XxAP protocol specific event. The 'PQC not supported' cause can be added to the radio network layer cause to indicate the reason for rejection when PQC is not supported. Table 28 indicates the cause of 'PQC not supported'.

[0143] Table 28

[0144] In the embodiment of this document, in the case of conditional PSCell addition (CPA), when adding 6G RAT and considering PQC security aspects, the SN add request confirmation message is as shown in Table 29

[0145] Table 29

[0146] Table 30 shows the S6gNB Add Request Confirm message for CPA when adding 6G RAT and considering PQC security aspects.

[0147]

Table 30

[0148] In the case of CPA, it is necessary to define and utilize 6G Cell Global ID (CGI) information. Table 31 indicates the 6G CGI.

[0149] Table 31

[0150] The SN Add Confirm message contains NR CGI information. However, 6G CGI information needs to be added to handle the impact of 6G RAT. The 6G CGI information contains the 6G cell identity and public land mobile network (PLMN) identity.

[0151] In the case of CPA process, TS 36.331 includes reportconfiginterRAT. 6G RAT needs to be added here, as shown in Table 32 below.

[0152] Table 32

[0153] TS 38.331, ReportConfigInterRAT needs to add 6G RAT related information for the CPA process, as shown in Table 33 below.

[0154]

Table 33

[0155] The above configuration covers the conditional event-related parameters required to trigger the CPA process on the UE side.

[0156] Figure 15 A method 1500 of a CPA procedure with a PQC support table performed by the MN 712 is shown. The method 1500 includes evaluating, by the MN 712, the PQC support tables of one or more SNs 714 for performing the CPA procedure, as shown in step 1502. The method 1500 includes sending, by the MN 712, at least one SN add request message to at least one SN 714 based on the evaluation, as shown in step 1504.

[0157] The method 1500 includes the MN 712 receiving at least one SN add request confirmation message in response to the SN add request message from the SN 714, as shown in step 1506. The method 1500 also includes the MN 712 sending an RRC reconfiguration message including information of one or more SNs 714 to the UE 702 in response to the received at least one SN add request confirmation message, as shown in step 1508, to enable the UE 702 to evaluate conditional configuration of the one or more SNs 714. The conditional configuration includes one or more conditional event-related parameters of the network RAT required to trigger the CPA procedure on the UE side.

[0158] The various actions in method 1500 may be performed in the order shown, in a different order, or simultaneously. In addition, in some embodiments, the Figure 15 Some of the actions listed in .

[0159] During the CPA process, UE 702 prepares multiple SNs 714 and can select to add SNs 714 that meet the conditions specified in the conditional configuration. With PQC support, the CPA process can be further enhanced. Two solutions are proposed for the CPA process: one is CPA based on a PQC support table at MN 712, and the other is UE-based selection for CPA.

[0160] Figure 16 A message sequence chart 1600 is shown indicating a CPA procedure using a PQC support table. As shown in step 1602, UE 702 sends UE capability information including PQC information to MN 712. MN 712 evaluates the PQC support tables of one or more SNs 714 for performing the CPA procedure, as shown in step 1604. MN 712 evaluates that SN1 supports only legacy security methods, SN2 supports only PQC, and SN3 supports PQC and legacy algorithms. Based on this evaluation, MN 712 determines that SN2 and SN3 support PQC and thereafter prepares SN2 and SN3 and an SN add request, as shown in steps 1606 and 1608.

[0161] Subsequently, MN 712 receives SN add request confirmation messages for the SN add request from SN2 and SN3, as shown in steps 1610 and 1612. MN 712 sends an RRC reconfiguration message including information of SN2 and SN3 to UE 702, as shown in step 1614. UE 702 reconfigures using the information of SN2 and SN3 and sends an RRC reconfiguration complete message to MN 712, as shown in step 1616.

[0162] UE 702 evaluates one or more security parameters of SN1 and SN2 to match the PQC capabilities of UE 702. UE 702 determines whether it is necessary to evaluate the conditional configuration of SN1 and SN2. If conditional configuration is required, UE 702 evaluates the conditional configuration of SN1 and SN2, as shown in step 1618. UE 702 connects to the desired SN, i.e., SN3, because the evaluated conditions match SN3. UE 702 sends a reconfiguration complete message with SN3 to MN 712, as shown in step 1620. MN 712 sends an SN reconfiguration complete message to SN3, as shown in step 1622. MN 712 also performs an SN release procedure with SN1 and SN2, as shown in step 1624. Subsequently, as shown in step 1626, a bearer is established between UE 702, MN 712, SN1, SN2, SN3, SN 714, UPF 1202 and AMF 1204, and the data forwarding process is implemented.

[0163] Table 34 below indicates a PQC support table defined and maintained at the MN 712, which keeps information on whether all related SNs 714 support PQC. Table 34 provides a list of security capabilities of the SNs 714 maintained at the MN 712.

[0164] Table 34

[0165] In the case of UE-based selection for CPA, in order for UE 702 to determine PQC support and select the corresponding SN, MN 712 / SN 714 needs to inform UE 702 of the PQC capability in RRC reconfiguration. The PQC capability in RRC reconfiguration can be sent using the format shown in Table 35 below.

[0166] Table 35

[0167] Similar changes may be added for ReportConfigInterRAT in 36.331. The UE 702 may evaluate the security type to match the PQC capability and determine whether a conditional evaluation of the corresponding SN 714 is required.

[0168] For example, if UE 702 supports PQC: for a given measurement ID, reporConfigInterRAT, if the security type also supports PQC, then SN 714 is selected for conditional configuration evaluation.

[0169] If UE 702 only supports legacy: For a given measurement ID, reportConfigInterRAT, if the security type also supports legacy, then select SN 714 for conditional configuration evaluation

[0170] If the UE 702 does not match a given security type, then the SN 714 is not selected for conditional configuration evaluation.

[0171] Therefore, the UE 702 may determine whether a conditional evaluation of the configured cells is required based on the security type.

[0172] Figure 17A method 1700 for a UE-initiated SN addition procedure is shown. The method 1700 includes, by a UE 702, measuring one or more node parameters of one or more SNs 714 based on service requirements to add at least one SN, as shown in step 1702. The method 1700 includes, by the UE 702, selecting an SN 714 with a strong cell from the one or more SNs 714 based on the measured node parameters, as shown in step 1704. Thereafter, the MN 712 indicates to the selected SN ID via its MN ID that the UE 702 has requested to add the SN 714. The method 1700 includes, by the UE 702, receiving an RRC reconfiguration message from the MN 712 containing network data and one or more security parameters of the selected SN 714, as shown in step 1706. The method 1700 includes, by the UE 702, initiating a RACH procedure for the selected SN 714, as shown in step 1708. The SN 714 sends an indication to the MN 712 associated with the MN ID that the UE 702 has requested that the SN 714 be added.

[0173] The various actions in method 1700 may be performed in the order shown, in a different order, or simultaneously. In addition, in some embodiments, the Figure 17 Some of the actions listed in .

[0174] Figure 18 A message sequence diagram 1800 is shown, indicating a UE-initiated SN addition procedure. As shown in step 1802, MN 712 may configure all measurement objects for the relevant SN cells in UE 702. UE 702 is aware of its service or data requirements. Based on the UE requirements, UE 702 may measure one or more node parameters (TRP / Cell ID) of SN1 and SN2 to find the strongest cell, as shown in step 1804.

[0175] UE 702 reads the minimum system information (MIN SI) block for the strongest SN (i.e., SN1) based on the node parameters, as shown in step 1806. The MIN SI block contains information for the RACH procedure. MN 712 indicates to the selected SN1 ID using its MN ID that UE 702 has requested the addition of the selected SN1, as shown in step 1808. UE 702 receives an RRC reconfiguration message from MN 712 containing network data and one or more security parameters for SN1, as shown in step 1810. Subsequently, after the reconfiguration, UE 702 sends an RRC reconfiguration complete message to MN 712, as shown in step 1812.

[0176] UE 702 initiates a RACH procedure in SN1, as shown in step 1814. SN1 sends an indication to MN 712 associated with the MN ID using an SN Add Request UE message that UE 702 has requested to add SN1, as shown in step 1816. MN 712 sends an SN Add Request Acknowledge message to SN1 based on the received SN Add Request UE message, as shown in step 1818. Thereafter, a data forwarding procedure may be performed between UE 702, MN 712, and SN1, as shown in step 1820.

[0177] Safety aspects related to PQC in SN modification: Figure 19 A method 1900 for processing SN modification in an MR-DC is shown. The method 1900 includes receiving, by the MN 712, at least one UE capability information from at least one UE 702, as shown in step 1902. The UE capability information includes PQC information. The method 1900 includes sending, by the MN 712, an SN modification request message including PQC information to at least one SN 714 based on the UE capability information, as shown in step 1904. The SN modification request message includes information about one or more candidate cells. The candidate cell information includes measurement results of one or more node parameters of one or more SNs for use in selecting and configuring the SN (714). The SN modification request message includes the UE capability information and a UE capability coordination result. The UE capability information includes RAT information, and the RAT information includes a 6G RAT. The method 1900 includes receiving, by the MN 712, an SN modification request confirmation message from the SN 714 if PQC is supported between the UE 702 and the SN 714, as shown in step 1906. The SN modification request confirmation message includes at least one of RRC reconfiguration information related to the SN (714) of the network (704) and a global cell identity of the SN (714) for performing a CPA procedure by the UE (702).

[0178] The method 1900 includes, after receiving the SN modification request confirm message from the SN 714, sending an RRC reconfiguration message including network data and one or more security parameters to the UE 702 by the MN 712, as shown in step 1908. The method 1900 includes, after completing the reconfiguration based on the network data and the security parameters, receiving an RRC reconfiguration complete message from the UE 702 by the MN 712, as shown in step 1910. In addition, the method 1900 includes, if PQC is not supported between the UE 702 and the SN 714, receiving an SN modification request reject message from the SN 714 by the MN 712, as shown in step 1912.

[0179] The various actions in method 1900 may be performed in the order shown, in a different order, or simultaneously. In addition, in some embodiments, the Figure 19 Some of the actions listed in .

[0180] In such Figure 20 and Figure 21 In the SN modification process shown, the SN modification request message or the S6gNB modification request message carries security information among various matters exchanged between the MN 712 and the SN 714, as follows: - When introducing PQC related security aspects along with 6G RAT, mechanisms need to be defined to handle PQC related capability aspects with respect to SN modification in NSA deployments.

[0181] Figure 20 A message sequence chart 2000 is shown, illustrating security aspects related to PQC in the SN modification procedure for the NSA deployment option with a 5GC (5G Core Network). For example, new and improved algorithms, such as PQC, that are quantum-resistant may be introduced in the security of 6G systems. Message sequence chart 2000 discusses methods and procedures for handling SN modification based on the types of security algorithms supported by UE 702 and network 704. Message sequence chart 2000 illustrates the 6G SN modification procedure with MN 712 acting as the 5G and 5GC network.

[0182] As shown in step 2002, UE capability information including PQC information is sent from UE 702 to MN 712. An SN modification procedure for a group of bearers is initiated from UE 702 to MN 712 and SN 714 to perform SN modification, as shown in step 2004. It is assumed that the UE capability information already contains PQC support capabilities. Furthermore, MN 712 prepares an SN Modify Request message to be sent to SN 714. The SN Modify Request message includes UE capabilities, particularly security-related elements. The SN Modify Request message including PQC information is sent from MN 712 to SN 714, as shown in step 2006. SN 714 evaluates the PQC information between UE 702 and SN 714 and sets security parameters, as shown in step 2008. If PQC is supported between UE 702 and SN 714, an SN Modify Request Acknowledge message is sent from SN 714 to MN 712, as shown in step 2010. Otherwise, if the UE 702 or the SN 714 does not support PQC, an SN modification request reject message is sent from the SN 714 to the MN 712, as shown in step 2012.

[0183] After receiving the SN Modify Request Confirm message, MN 712 sends an RRC Reconfiguration message (e.g., including 6G RRC reconfiguration and security configuration details) to UE 702, as shown in step 2014. Furthermore, after completing the reconfiguration based on the network data and one or more security parameters, UE 702 sends an RRC Reconfiguration Complete message to MN 712, as shown in step 2016. The SN Reconfiguration Complete message is sent from MN 712 to SN 714, as shown in step 2018. Furthermore, as shown in step 2020, a bearer is established between UE 702, MN 712, SN 714, user plane function (UPF) 1202, and access and mobility management function (AMF) 1204, and a data forwarding process is implemented.

[0184] Figure 21 A message sequence chart 2100 is shown, illustrating security aspects related to PQC in the S6gNB modification procedure with EPC. For example, message sequence chart 2100 illustrates the S6gNB modification procedure with MN 712 as the 4G and EPC network. As shown in step 2102, UE capability information including PQC information is sent from UE 702 to MN 712. The S6gNB modification procedure for a group of bearers is initiated from UE 702 to MN 712 and SN 714 for SN modification, as shown in step 2104. It is assumed that the UE capability information already includes PQC support capabilities. Furthermore, MN 712 prepares an S6gNB Modify Request message to be sent to SN 714. The S6gNB Modify Request message contains UE capabilities, particularly security-related elements. The S6gNB Modify Request message, including PQC information, is sent from MN 712 to SN 714, as shown in step 2106. SN 714 evaluates the PQC information between UE 702 and SN 714 and sets security parameters, as shown in step 2108. If PQC is supported between UE 702 and SN 714, an S6gNB Modify Request Confirm message is sent from SN 714 to MN 712, as shown in step 2110. Otherwise, if UE 702 or SN 714 does not support PQC, an S6gNB Modify Request Reject message is sent from SN 714 to MN 712, as shown in step 2112.

[0185] In addition, after receiving the S6gNB Modify Request Acknowledge message, MN 712 sends an RRC Reconfiguration message (e.g., including 6G RRC reconfiguration and security configuration details) to UE 702, as shown in step 2114. In addition, after completing the reconfiguration based on the network data and one or more security parameters, UE 702 sends an RRC Reconfiguration Complete message to MN 712, as shown in step 2116. In addition, in step 2118, a bearer is established between UE 702, MN 712, SN 714, S-GW 1302, and MME 1304, and the data forwarding process is implemented.

[0186] SN modification request: In this solution, the SN Modification Request message should include aspects related to PQC support. The following changes need to be incorporated into the 3rd Generation Partnership Project (3GPP) TS 3x.423.

[0187] Table 36 shows the SN modification request.

[0188] Table 36

[0189] As shown in Table 37, the SN Modification Request message introduces a new IE for PQC information.

[0190] Table 37

[0191] Similarly, the following modifications need to be made in 3GPP specification TS 3x.423. Table 38 shows the S6gNB modification request.

[0192] Table 38

[0193] As shown in Table 39, the S6gNB modification request message introduces a new IE for PQC information.

[0194] Table 39

[0195] For sections 9.2.3.Xn and 9.2.Xn of the corresponding specification (TS 3x.423) mentioned above, refer to Table 5.

[0196] Based on the PQC-related SN modification request message content, SN 714 needs to evaluate the PQC support of UE 702 and SN, update security parameters, and determine whether UE 702 is allowed to modify SN 714.

[0197] PQC supports assessments of: Figure 22a A method 2200 for evaluating PQC information at the SN 714 based on the SN modification request message is shown. Based on the PQC-related content in the SN modification request message received from the MN 712, the SN 714 needs to evaluate the PQC support of the UE 702 and the SN 714, update security parameters, and determine whether the UE 702 is allowed to modify the SN 714. As shown in step 2202, the SN modification request message carries PQC information, and the PQC information includes PQC support and related PQC profiles or related PQC parameters or algorithms supported on the UE 702 side.

[0198] SN 714 verifies the valid entry of MN ID or SN ID in the PQC support table (Table 6), as shown in step 2204. The method 2200 for evaluating PQC support can be divided into Figure 22a If there is a valid entry for either the MN ID or the SN ID, then based on the SN modification procedure, the PQC support table (Table 6) is used to determine whether the given UE 702 and SN 714 have matching or mismatching PQC capabilities, as shown in step 2206, and a decision can be made accordingly. If there is no valid entry for UE 702 in the PQC support table, then step 2 can be evaluated to determine PQC support between UE 702 and SN 714, as shown in step 2208.

[0199] Figure 22b Shows the implementation Figure 22a The method of step 1 utilizes a PQC support table to determine whether a given UE 702 and SN 714 have matching or mismatching PQC capabilities. This method is executed when a valid UE XxAP ID entry exists in the PQC support table. The value corresponding to the UE XxAP ID is evaluated and action is taken accordingly, as shown in step 2210. If the value supports only legacy, an SN Modify Request Acknowledgement containing the legacy security method is sent from SN 714 to MN 712, as shown in step 2212. If the value supports PQC, an SN Modify Request Acknowledgement containing the PQC security method is sent from SN 714 to MN 712, as shown in step 2214. If the value is not supported, an SN Modify Request Rejection is sent from SN 714 to MN 712, as shown in step 2216.

[0200] Figure 22c It shows that when there is no valid entry for UE 702 in the PQC support table, Figure 22aStep 2 of the method is described. Step 2 can be evaluated to determine PQC support between UE 702 and SN 714. The SN Modify Request message is checked for UE PQC support. According to the proposed solution, the SN Modify Request message carries PQC information, which includes PQC support and related profiles or algorithms supported on the UE side. As a first step, SN 714 should determine whether the UE supports PQC, as shown in step 2218.

[0201] If UE 702 supports PQC, SN 714 checks whether SN 714 supports PQC, as shown in step 2220. If both UE 702 and SN 714 support PQC, PQC is prioritized and an SN Modify Request Acknowledgement including PQC as the preferred security method is sent, as shown in step 2222. If UE 702 supports PQC and legacy, and SN 714 does not support PQC, an SN Modify Request Acknowledgement including the legacy security method is sent, as shown in step 2224. If UE 702 only supports PQC and SN 714 only supports legacy, the SN Modify Request is rejected due to the capability mismatch between UE 702 and SN 714, as shown in step 2226.

[0202] Furthermore, if UE 702 does not support PQC, SN 714 checks whether it supports legacy, as shown in step 2228. If SN 714 supports legacy, the SN modification request is confirmed with legacy security, as shown in step 2230. If SN 714 supports only PQC, then in this case, the capabilities of UE 702 and SN 714 do not match, and therefore, the SN modification is rejected, as shown in step 2226. To further optimize the process, a table as shown in Table 6 can be maintained to update PQC support, and the table can be referenced whenever the SN modification procedure is called, as shown in step 2232.

[0203] SN / S6gNB modification - further enhancements: Security aspects based on traditional algorithms: The following changes are required to specification TS 3x.423 to add the following: SN modification request: This message is sent by the M-NG-RAN node to the S-6G-RAN node to request preparation for modifying S-6G-RAN node resources for a specific UE, or to query the current SCG configuration, or to provide S-6G-RAN node with S-RLF related information. Table 40 shows the SN Modification Request.

[0204] Table 40

[0205] S6GNB modification request: This message is sent by the MeNB to the S6gNB to request preparation for modifying S6gNB resources for a specific UE, query the current SCG configuration, or provide S-RLF related information to the S6gNB. Table 41 shows the S6gNB Modify Request.

[0206] Table 41

[0207] Both 9.2.3.X and 9.2.X include 6G-related encryption algorithms and integrity protection algorithms, as shown in Table 42 below.

[0208] Table 42

[0209] Enhancements to CG-ConfigInfo included in the SN Modify Request message: In the specification, TS 3x.331 SN / S6GNB Modify Request message has a container carrying CG-ConfigInfo, as shown below.

[0210] SN modification request

[0211] This message is sent by the M-NG-RAN node to the S-6G-RAN node to request preparation for modifying S-6G-RAN node resources for a specific UE, or to query the current SCG configuration, or to provide S-RLF related information to the S-6G-RAN node. Table 43 shows the SN Modification Request.

[0212] Table 43

[0213] S6gNB Modification Request

[0214] This message is sent by the MeNB to the S6gNB to request preparation for modifying S6gNB resources for a specific UE, query the current SCG configuration, or provide S-RLF related information to the S6gNB. Table 44 shows the S6gNB Modify Request.

[0215] Table 44

[0216] CG-ConfigInfo is further defined as shown in Table 45 below.

[0217] Table 45

[0218] Table 46 shows CG-ConfigInfo.

[0219] Table 46

[0220] The SN modification request confirmation includes the IE shown in Table 47 below.

[0221] Table 47

[0222] The S6gNB modification request confirmation includes the IE shown in Table 48 below.

[0223] Table 48

[0224] CG-Config can be expressed as the following Table 49: Table 49

[0225] Table 50 shows the PSCell frequencies.

[0226] Table 50

[0227] pSCellFrequency, pSCellFrequencyEUTRA, and pSCellFrequency6G respectively indicate the PSCell frequency in NR (i.e., pSCellFrequency), the PSCell frequency in E-UTRA (i.e., pSCellFrequencyEUTRA), or the PSCell frequency in 6G (pSCellFrequency6G).

[0228] The proposed system 700 and method provide for including new information elements for measurement in a SN and S6gNB Add Request message or a SN and S6gNB Modify Request message for a 6G or next generation network, new information elements for UE capabilities in a SN and S6gNB Add Request message or a SN and S6gNB Modify Request message for a 6G or next generation network, and new information elements for legacy security in a SN and S6gNB Add Request message or a SN and S6gNB Modify Request message for a 6G or next generation network. The system 700 and method provide for PQC algorithm support factors to be considered in SN add, SN modify, and conditional SN add procedures, as well as PQC support information that can be shared between the MN 712 and SN 714 nodes during SN procedures associated with the UE 702. The proposed method provides for evaluating PQC support using the PQC support information exchanged between the MN 712 and SN 714. In addition, an optimization of the method for evaluating PQC support is disclosed by maintaining a reference table or database between the MN 712 and SN 714 nodes regarding the types of security algorithms supported by the UE 702. The proposed method provides for the SN Add Request Confirmation or SN Modify Request Confirmation procedure to include new information elements for 6G or next generation network RAT and PQC aspects. The method provides for updating the UE-side procedure for SN addition or modification due to 6G or next generation network RAT. The method provides for adding a new cause to handle PQC rejection of the SN. The method provides for new information elements added to handle the CPA procedure for 6G or next generation network RAT. The method also provides new aspects related to the UE-initiated SN Add procedure.

[0229] The embodiments disclosed herein may be implemented by at least one software program running on at least one hardware device and performing network management functions to control network elements. Figure 7 The illustrated network elements include blocks that may be at least one hardware device or a combination of a hardware device and a software module.

[0230] The embodiments disclosed herein describe a system 700 and method to provide SN addition, SN modification, and conditional SN addition processes to handle NSA options when 6G or next generation network RATs are introduced, and to handle new and improved security algorithms with quantum computing resistance.

[0231] The foregoing description of specific embodiments will fully reveal the general nature of the embodiments herein so that others can easily modify and / or adapt such specific embodiments for various applications by applying current knowledge without departing from the general concepts, and therefore, such adaptations and modifications should and are intended to be understood as being included within the meaning and scope of equivalents of the disclosed embodiments. It should be understood that the wording or terminology employed herein is for descriptive and not limiting purposes. Therefore, although the embodiments herein have been described in terms of embodiments and examples, those skilled in the art will recognize that the embodiments disclosed herein can be modified and practiced within the scope of the embodiments described herein.

Claims

1. A method for processing the addition of a secondary node (SN) in a multi-radio access technology (RAT)-dual connectivity (MR-DC) in a wireless communication system, performed by a primary node (MN), the method comprising: receiving at least one UE capability information from at least one user equipment (UE), wherein the at least one UE capability information comprises post-quantum cryptography (PQC) information; Sending, based on the at least one UE capability information, an SN add request message including the PQC information to at least one SN; If PQC is supported between the at least one UE and the at least one SN, receiving an SN add request confirm message from the at least one SN; as well as If PQC is not supported between the at least one UE and the at least one SN, an SN add request reject message is received from the at least one SN.

2. The method according to claim 1, wherein The SN adding request message includes information of one or more candidate cells, wherein the information of the one or more candidate cells includes measurement results of one or more node parameters of one or more SNs, for selecting and configuring the at least one SN.

3. The method according to claim 1, wherein The SN add request message includes the at least one UE capability information and the UE capability coordination result, wherein the at least one UE capability information includes radio access technology RAT information, and the RAT information includes 6G RAT.

4. The method according to claim 1, wherein The PQC information includes at least one PQC support and at least one PQC profile or related PQC parameters, wherein the at least one PQC support indicates whether the at least one UE supports at least one of the following: PQC, traditional security methods, and both PQC and traditional security methods, and the at least one PQC profile or related PQC parameters indicates whether a related mechanism for the at least one PQC support is supported on the UE side.

5. The method according to claim 4, wherein The conventional security method includes at least one security support of one or more SNs of a network, wherein the at least one security support includes at least one of the following: one or more security capabilities and one or more security keys.

6. The method according to claim 1, wherein A PQC support table is configured and maintained at at least one of the MN and the at least one SN so that at least one of the MN and the at least one SN evaluates PQC information between the at least one UE and the at least one SN, wherein the PQC support table includes one or more values ​​indicating the PQC information between the at least one UE and the at least one SN.

7. The method according to claim 6, further comprising: The MN evaluates the PQC support table of one or more SNs to perform a conditional PSCell addition CPA procedure; The MN sends at least one SN add request message to the at least one SN based on the evaluation, and receives at least one SN add request confirmation message for the at least one SN add request message; as well as The MN sends a radio resource control RRC reconfiguration message to the at least one UE for the received at least one SN addition request confirmation message, so that the at least one UE can evaluate the conditional configuration of the one or more SNs, and the RRC reconfiguration message includes information of the one or more SNs.

8. The method according to claim 1, wherein The SN add request confirmation message includes at least one of the following: RRC reconfiguration information related to the at least one SN of the network and a global cell identifier of the at least one SN of the network for performing a CPA procedure by the at least one UE.

9. A master node MN of a network, comprising: Processor, configured as: receiving at least one UE capability information from at least one user equipment (UE), wherein the at least one UE capability information comprises post-quantum cryptography (PQC) information; Sending, based on the at least one UE capability information, an SN add request message including the PQC information to at least one secondary node SN; If PQC is supported between the at least one UE and the at least one SN, receiving an SN add request confirm message from the at least one SN; as well as If PQC is not supported between the at least one UE and the at least one SN, an SN add request reject message is received from the at least one SN.

10. The MN according to claim 9, wherein: The SN adding request message includes information of one or more candidate cells, wherein the information of the one or more candidate cells includes measurement results of one or more node parameters of one or more SNs, for selecting and configuring the at least one SN.

11. The MN according to claim 9, wherein: The SN add request message includes the at least one UE capability information and the UE capability coordination result, wherein the at least one UE capability information includes radio access technology RAT information, and the RAT information includes 6G RAT.

12. The MN according to claim 9, wherein: The PQC information includes at least one PQC support and at least one PQC profile or related PQC parameters, wherein the at least one PQC support indicates whether the at least one UE supports at least one of the following: PQC, traditional security methods, and both PQC and traditional security methods, and the at least one PQC profile or related PQC parameters indicates whether a related mechanism for the at least one PQC support is supported on the UE side.

13. The MN according to claim 12, wherein: The conventional security method includes at least one security support of one or more SNs of a network, wherein the at least one security support includes at least one of the following: one or more security capabilities and one or more security keys.

14. The MN according to claim 9, in, A PQC support table is configured and maintained at at least one of the MN and the at least one SN, so that at least one of the MN and the at least one SN evaluates PQC information between the at least one UE and the at least one SN, wherein the PQC support table includes one or more values ​​indicating the PQC information between the at least one UE and the at least one SN; and The processor of the MN is configured as follows: Evaluate the PQC support table of one or more SNs for performing the conditional PSCell addition CPA process; Based on the evaluation, sending at least one SN add request message to the at least one SN, and receiving at least one SN add request confirmation message for the at least one SN add request message; and A radio resource control (RRC) reconfiguration message is sent to the at least one UE for the received at least one SN addition request confirmation message, so that the at least one UE can evaluate the conditional configuration of the one or more SNs, wherein the RRC reconfiguration message includes information of the one or more SNs.

15. The MN according to claim 9, wherein: The SN add request confirmation message includes at least one of the following: RRC reconfiguration information related to the at least one SN of the network and a global cell identifier of the at least one SN of the network for performing a CPA procedure by the at least one UE.

Images