Method and device for linking two techniques for managing keys in dual connectivity in mobile communication system
The method enables secure key management in dual connectivity by generating and managing key values for both updated and non-updated base stations, ensuring seamless communication and system flexibility.
Patent Information
- Application Number
- PCT/KR2024/006040
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-12-20
- Filing Date
- 2024-05-03
- Publication Date
- 2024-11-14
AI Technical Summary
In dual connectivity scenarios of wireless communication systems, there is a need for a method to manage keys securely when base stations with different levels of support for new techniques coexist, specifically when some base stations have been updated to use new key management techniques while others have not.
A method where a Master Node (MN) selects and generates key values for both updated and non-updated Secondary Nodes (SNs), transmits these key values, and provides Conditional PSCell Change (CPC) setting information to the user terminal, enabling secure communication and dynamic key management across different types of base stations.
This approach ensures seamless key management and secure communication in dual connectivity environments, allowing for efficient integration of new techniques across base stations with varying levels of updates, enhancing system flexibility and security.
Smart Images

Figure KR2024006040_14112024_PF_FP_ABST
Abstract
Description
Method and device for linking two techniques for managing keys during dual connection in a mobile communication system
[0001] The present disclosure relates to a method and device for linking two techniques used to manage keys when a terminal has dual connectivity in a wireless communication system.
[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz (THz) band (for example, 3 THz band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.
[0003] In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.
[0004] Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.
[0005] In addition, standardization of wireless interface architecture / protocols is in progress for technologies such as intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) that provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) that simplifies random access procedures. Standardization is also in progress for system architecture / services such as 5G baseline architecture (e.g., Service-based Architecture, Service-based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal.
[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).
[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.
[0008] A UE can perform dual connectivity. In dual connectivity, a base station providing macrocell coverage can be a master node (MN) that processes both the control plane and the user plane, while another base station with smallcell coverage can be called a secondary node (SN) that only processes the user plane and can perform an auxiliary role. In other words, the MN can process control signaling, and the SN can be used to improve data transmission speed. The MN can provide the UE with Conditional PSCell Change (CPC) configuration information, and the UE can evaluate the conditions and request a change to the corresponding SN if it satisfies the conditions. Furthermore, the UE can store CPC configuration information for multiple SNs provided by the MN and, after continuous evaluation, request a change to the SN whenever the conditions are met.
[0009] Based on the above discussion, this disclosure aims to address the following problem: Multiple key management techniques for security in dual connectivity may exist. For example, when a new technique is introduced, there may be base stations that have been updated to support the new technique, while base stations that have not yet been updated exist. In this case, a new method is needed to enable the interoperability of the two different types of base stations. This disclosure proposes a technology that enables the aforementioned method, thereby addressing this issue.
[0010] In a wireless communication system according to one embodiment of the present invention, an operation method of an MN (Master Node) connected to a user terminal may include: selecting a first SN counter value for a first target SN (Secondary Node) that does not support an optional SCG (Secondary Cell Group) function; generating a first key value for secure communication between the user terminal and the first target SN based on the first SN counter value; transmitting a first key value corresponding to the first target SN to the first target SN; selecting a plurality of second SN counter values for a second target SN that supports an optional SCG function; generating a plurality of second key values for secure communication between the user terminal and the second target SN based on the plurality of second SN counter values; transmitting a plurality of second key values corresponding to the second target SN to the second target SN; and transmitting CPC (Conditional PSCell Change) configuration information, the first SN counter value, and the plurality of second SN counter values to the user terminal.
[0011] The operating method of the MN may further include: receiving information from the first target SN regarding whether the first target SN supports a selective SCG function; and receiving information from the second target SN regarding whether the second target SN supports a selective SCG function.
[0012] The above CPC setting information may include information on whether the first target SN or the second target SN supports the optional SCG function.
[0013] The method of operating the MN may further include a step of receiving, from the first target SN or the second target SN, a rejection message for a key value received by the first target SN or the second target SN or a request message for an additional key value.
[0014] The method of operating the MN may further include a step of transmitting information on whether the first target SN that does not support the optional SCG function is reusable to the user terminal.
[0015] The operating method of the MN may further include the steps of: receiving, from the user terminal, a request for reuse of the first target SN when reuse of the first target SN is possible; selecting a third SN counter value for the first target SN and generating a third key value based on the selected third SN counter value; transmitting the third key value to the first target SN; and transmitting the third SN counter value corresponding to the third key value to the user terminal.
[0016] According to another embodiment of the present invention, a method for operating a user terminal in a wireless communication system may include the steps of: receiving, from a Master Node (MN) connected to the user terminal, Conditional PSCell Change (CPC) configuration information, a first SN counter value corresponding to a first key value transmitted to a first target SN (Secondary Node) that does not support an optional SCG (Secondary Cell Group) function, and a plurality of second SN counters corresponding to a plurality of second key values transmitted to a second target SN that supports the optional SCG function; generating a first key value or a second key value based on at least one of the first SN counter value or the plurality of second SN counter values; and performing an SN change to a first target SN through the first key value or an SN change to a second target SN through the second key value.
[0017] The above CPC setting information includes information on whether the first target SN or the second target SN supports the optional SCG function, and the replacement to the second target SN performed by the user terminal can be performed multiple times using a plurality of second key values generated based on the CPC setting information.
[0018] According to another embodiment of the present invention, a MN (Master Node) connected to and operating with a user terminal in a wireless communication system may be configured to include a communication unit and a control unit, wherein the control unit selects a first SN counter value for a first target SN (Secondary Node) that does not support an optional SCG (Secondary Cell Group) function, generates a first key value for secure communication between the user terminal and the first target SN based on the first SN counter value, transmits the first key value corresponding to the first target SN to the first target SN, selects a plurality of second SN counter values for a second target SN that supports an optional SCG function, generates a plurality of second key values for secure communication between the user terminal and the second target SN based on the plurality of second SN counter values, and transmits a plurality of second key values corresponding to the second target SN to the second target SN, and transmits CPC (Conditional PSCell Change) setting information, the first SN counter value, and the plurality of second SN counter values to the user terminal. Can be set to transmit.
[0019] Various embodiments of the present disclosure can provide a device and method capable of effectively providing a service in a wireless communication system.
[0020] According to one embodiment of the present disclosure, when a new technique for managing security keys is introduced when dual connectivity is used, a method for efficiently applying the new technique in a case where updated base stations and non-updated base stations coexist can be presented.
[0021] The effects that can be obtained from the present disclosure are not limited to the effects mentioned in the various embodiments, and other effects that are not mentioned can be clearly understood by a person having ordinary skill in the art to which the present disclosure belongs from the description below.
[0022] FIG. 1A illustrates a communication network including core network entities in a wireless communication system according to various embodiments of the present disclosure.
[0023] FIG. 1b illustrates a wireless environment including a core network in a wireless communication system according to various embodiments of the present disclosure.
[0024] FIG. 2a illustrates an example of a functional structure of a terminal according to embodiments of the present disclosure.
[0025] FIG. 2b illustrates an example of a functional structure of a base station according to embodiments of the present disclosure.
[0026] FIG. 2c illustrates an example of a functional structure of a core network object according to embodiments of the present disclosure.
[0027] FIG. 3 is a diagram illustrating a method for managing a key in dual connectivity according to an embodiment of the present disclosure.
[0028] FIG. 4 is a diagram illustrating a procedure for changing a secondary node in dual connectivity based on the method disclosed in FIG. 3.
[0029] FIG. 5 is a diagram illustrating another method for managing keys in dual connectivity according to an embodiment of the present disclosure.
[0030] FIG. 6 is a diagram illustrating a procedure for changing a secondary node in dual connectivity based on the method disclosed in FIG. 5.
[0031] FIG. 7 is a diagram illustrating a procedure for continuously changing a secondary node in dual connectivity by linking the two methods disclosed in FIG. 3 and FIG. 5.
[0032] FIG. 8 is a diagram illustrating another procedure for continuously changing a secondary node in dual connectivity by linking the two methods disclosed in FIG. 3 and FIG. 5.
[0033] FIG. 9 is a diagram illustrating another method for managing keys in dual connectivity according to an embodiment of the present disclosure.
[0034] FIG. 10 is a diagram illustrating a procedure for changing a secondary node in dual connectivity based on the method disclosed in FIG. 9.
[0035] FIG. 11 is a diagram illustrating a procedure for continuously changing a secondary node in dual connectivity by linking the two methods disclosed in FIG. 3 and FIG. 9.
[0036] FIG. 12 is a diagram illustrating another procedure for continuously changing a secondary node in dual connectivity by linking the two methods disclosed in FIG. 3 and FIG. 9.
[0037] FIG. 13 is a diagram illustrating another method for managing keys in dual connectivity according to an embodiment of the present disclosure.
[0038] FIG. 14 is a diagram illustrating a procedure for changing a secondary node in dual connectivity based on the method disclosed in FIG. 13.
[0039] FIG. 15 is a diagram illustrating another procedure for continuously changing a secondary node in dual connectivity by linking the two methods disclosed in FIG. 3 and FIG. 13.
[0040] The terms used in this disclosure are used only to describe specific embodiments and may not be intended to limit the scope of other embodiments. The singular expression may include plural expressions unless the context clearly indicates otherwise. Terms used herein, including technical or scientific terms, may have the same meaning as commonly understood by those of ordinary skill in the art described in this disclosure. Terms defined in general dictionaries among the terms used in this disclosure may be interpreted as having the same or similar meaning in the context of the relevant technology, and shall not be interpreted in an idealized or overly formal sense unless explicitly defined in this disclosure. In some cases, even if a term is defined in this disclosure, it cannot be interpreted to exclude embodiments of the present disclosure.
[0041] The various embodiments of the present disclosure described below illustrate a hardware-based approach as an example. However, since the various embodiments of the present disclosure include techniques utilizing both hardware and software, the various embodiments of the present disclosure do not exclude a software-based approach.
[0042] 3GPP, responsible for cellular mobile communications standards, is standardizing a new core network architecture, dubbed 5G core (5GC), to facilitate the evolution of existing 4G LTE systems into 5G systems. Compared to the evolved packet core (EPC), the network core for existing 4G systems, 5GC supports the following differentiated features:
[0043] First, 5GC introduces network slicing. As a 5G requirement, 5GC must support various terminal types and services (e.g., eMBB, URLLC, or mMTC services). Each type of service has different requirements for the core network. For example, eMBB services require high data rates, while URLLC services require high reliability and low latency. One technology proposed to meet these diverse service requirements is network slicing.
[0044] Network slicing virtualizes a single physical network to create multiple logical networks. Each network slice instance (NSI) can have different characteristics. Therefore, each NSI can satisfy diverse service requirements by possessing a network function (NF) tailored to its characteristics. If each terminal is assigned an NSI that matches the characteristics of the service it requires, multiple 5G services can be efficiently supported.
[0045] Second, 5GC can facilitate support for the network virtualization paradigm by separating mobility management and session management functions. In 4G LTE (long term evolution), services were provided through signaling exchanges with a single core device called the mobility management entity (MME), which was responsible for registration, authentication, mobility management, and session management for all terminals. However, in 5G, the number of terminals increases explosively, and the mobility and traffic / session characteristics that must be supported for each terminal type become more specialized. Therefore, supporting all functions with a single device like the MME inevitably reduces scalability by adding entities for each required function. Therefore, various functions are being developed based on a structure that separates mobility management and session management functions to improve scalability in terms of functional / implementation complexity and signaling load of the core device responsible for the control plane.
[0046] Hereinafter, various embodiments will be described in detail with reference to the accompanying drawings. Furthermore, when describing embodiments of the present disclosure, detailed descriptions of related known functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the embodiments. Furthermore, the terms described below are defined in consideration of their functions in the embodiments, and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the contents throughout this specification.
[0047] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.
[0048] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described in detail below together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided solely to ensure that the present disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Like reference numerals designate like elements throughout the specification.
[0049] At this time, it will be understood that each block of the processing flowchart drawings and combinations of the flowchart drawings can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flowchart block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flowchart block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).
[0050] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.
[0051] Here, the term '~ unit' used in various embodiments of the present disclosure means a software or hardware component such as an FPGA or ASIC, and the '~ unit' can perform certain roles. However, the '~ unit' is not limited to software or hardware. The '~ unit' may be configured to be on an addressable storage medium and may be configured to play one or more processors. Accordingly, as an example, the '~ unit' may include components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. Additionally, components and '~parts' may be implemented to regenerate one or more CPUs within a device or secure multimedia card.
[0052] Hereinafter, a base station is an entity that performs resource allocation of a terminal, and may be at least one of an eNode B (eNB), a Node B, a BS (base station), a RAN (radio access network), an AN (access network), a RAN node, a NR NB, a gNB, a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (user equipment), an MS (mobile station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In various embodiments of the present disclosure, a case where the terminal is a UE will be described as an example. In addition, although various embodiments of the present disclosure are described below using a system based on LTE, LTE-A, or NR as an example, various embodiments of the present disclosure may be applied to other communication systems having a similar technical background or channel type. In addition, various embodiments of the present disclosure may be applied to other communication systems with some modifications within a range that does not significantly depart from the scope thereof at the discretion of a person having skilled technical knowledge.
[0053] The terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc. are provided as examples for convenience of explanation. Therefore, the present disclosure is not limited to the terms described below, and other terms referring to objects with equivalent technical meanings may be used.
[0054] Additionally, while this disclosure describes various embodiments using terminology used in certain communication standards (e.g., 3rd Generation Partnership Project (3GPP)), these are merely illustrative examples. The various embodiments of this disclosure can be easily modified and applied to other communication systems. Below, some terms used in the core network of this disclosure are predefined.
[0055] AMF Access and Mobility Management Function
[0056] CN Core Network
[0057] CNF Containerized Network Function
[0058] DNN Data Network Name
[0059] PCF Policy Control Function
[0060] HSS Home Subscriber Server
[0061] SMF Session Management Function
[0062] UDM User Data Management
[0063] UPF User Plane Function
[0064] CNF Containerized Network Function
[0065] VNF Virtual Network Function
[0066] AMF Access and Mobility Management Function
[0067] CN Core Network
[0068] CNF Containerized Network Function
[0069] DNN Data Network Name
[0070] PCF Policy Control Function
[0071] HSS Home Subscriber Server
[0072] SMF Session Management Function
[0073] UDM User Data Management
[0074] UPF User Plane Function
[0075] CNF Containerized Network Function
[0076] VNF Virtual Network Function
[0077] FIG. 1A illustrates a communication network including core network entities in a wireless communication system according to embodiments of the present disclosure. A 5G mobile communication network may be configured to include a 5G user equipment (UE) (110), a 5G radio access network (RAN) (120), and a 5G core network.
[0078] The 5G core network may be configured to include network functions such as an access and mobility management function (AMF) (150) that provides a mobility management function of UE, a session management function (SMF) (160) that provides a session management function, a user plane function (UPF) (170) that performs a data transfer role, a policy control function (PCF) (180) that provides a policy control function, a unified data management (UDM) (153) that provides a data management function such as subscriber data and policy control data, or a unified data repository (UDR) that stores data of various network functions.
[0079] Referring to FIG. 1A, a user equipment (UE) (110) may communicate with a base station (e.g., an eNB, a gNB) via a wireless channel, i.e., an access network. In some embodiments, the UE (110) may be a device used by a user and configured to provide a user interface (UI). As an example, the UE (110) may be a terminal mounted (equipment) on a vehicle for driving. In some other embodiments, the UE (110) may be a device that performs machine type communication (MTC) that operates without user intervention, or may be an autonomous vehicle. UE may be referred to as a 'terminal', 'vehicle terminal', 'user equipment (UE)', 'mobile station', 'subscriber station', 'remote terminal', 'wireless terminal', or 'user device' or other terms having equivalent technical meanings, other than electronic devices. As the terminal, in addition to the UE, a customer-premises equipment (CPE) or a dongle-type terminal may be used. The CPE, while connected to the NG-RAN node like the UE, may also provide a network to other communication devices (e.g., a laptop).
[0080] Referring to FIG. 1A, the AMF (150) provides a function for connection and mobility management per terminal (110), and basically, one AMF (150) can be connected to one terminal (110). Specifically, the AMF (150) can perform at least one of signaling between core network nodes for mobility between 3GPP access networks, an interface (N2 interface) between wireless access networks (e.g., 5G RAN) (120), NAS signaling with the terminal (110), identification of the SMF (160), and provision of transmission of session management (SM) messages between the terminal (110) and the SMF (160). Some or all of the functions of the AMF (150) can be supported within a single instance of one AMF (150).
[0081] Referring to FIG. 1A, the SMF (160) provides a session management function, and when the terminal (110) has multiple sessions, each session may be managed by a different SMF (160). Specifically, the SMF (160) may perform at least one of the following functions: session management (e.g., session establishment, modification, and release, including tunnel maintenance between the UPF (170) and the access network node), selection and control of UP (user plane) functions, traffic steering setup for routing traffic to an appropriate destination in the UPF (170), termination of the SM portion of NAS messages, downlink data notification (DDN), and initiation of AN-specific SM information (e.g., delivery to the access network via the N2 interface via the AMF (150)). Some or all of the functions of the SMF (160) may be supported within a single instance of one SMF (160).
[0082] In the 3GPP system, conceptual links connecting NFs within a 5G system may be referred to as reference points. Reference points may also be referred to as interfaces. The following exemplifies reference points (hereafter, interchangeably referred to as interfaces) included in the 5G system architecture represented across various embodiments of the present disclosure.
[0083] - N1: Reference point between UE (110) and AMF (150)
[0084] - N2: Reference point between (R)AN(120) and AMF(150)
[0085] - N3: Reference point between (R)AN(120) and UPF(170)
[0086] - N4: Reference point between SMF (160) and UPF (170)
[0087] - N5: Reference point between PCF (180) and AF (130)
[0088] - N6: Reference point between UPF (170) and DN (140)
[0089] - N7: Reference point between SMF (160) and PCF (180)
[0090] - N8: Reference point between UDM (153) and AMF (150)
[0091] - N9: Reference point between two core UPFs (170)
[0092] - N10: Reference point between UDM (153) and SMF (160)
[0093] - N11: Reference point between AMF (150) and SMF (160)
[0094] - N12: Reference point between AMF (150) and authentication server function (AUSF) (151)
[0095] - N13: Reference point between UDM (153) and authentication server function (151)
[0096] - N14: Reference point between two AMFs (150)
[0097] - N15: For non-roaming scenarios, reference point between PCF (180) and AMF (150), for roaming scenarios, reference point between PCF (180) and AMF (150) within the visited network.
[0098] FIG. 1B illustrates a wireless environment including a core network in a wireless communication system according to embodiments of the present disclosure. Referring to FIG. 1B, the wireless communication system includes a radio access network (RAN) (120) and a core network (CN).
[0099] The wireless access network (120) is a network that is directly connected to a user device, for example, a terminal (110), and is an infrastructure that provides wireless access to the terminal (110). The wireless access network (120) includes a set of a plurality of base stations including a base station (125), and the plurality of base stations can communicate through interfaces formed between each other. At least some of the interfaces between the plurality of base stations can be wired or wireless. The base station (125) can have a structure that is divided into a central unit (CU) and a distributed unit (DU). In this case, one CU can control a plurality of DUs. The base station (125) can be referred to as an 'access point (AP)', 'next generation node B (gNB)', '5th generation node (5G node)', 'wireless point', 'transmission / reception point (TRP)', or other terms having an equivalent technical meaning thereto in addition to the base station. The terminal (110) connects to a wireless access network (120) and communicates with a base station (125) via a wireless channel. The terminal (110) may be referred to as a 'user equipment (UE)', a 'mobile station', a 'subscriber station', a 'remote terminal', a 'wireless terminal', a 'user device', or other terms having an equivalent technical meaning.
[0100] The core network is a network that manages the entire system, controls the wireless access network (120), and processes data and control signals for terminals (110) transmitted and received through the wireless access network (120). The core network performs various functions, such as controlling the user plane and control plane, processing mobility, managing subscriber information, billing, and interworking with other types of systems (e.g., long term evolution (LTE) system). In order to perform the various functions described above, the core network may include a number of functionally separated entities having different network functions (NFs). For example, the core network (200) may include an access and mobility management function (AMF) (150), a session management function (SMF) (160), a user plane function (UPF) (170), a policy and charging function (PCF) (180), a network repository function (NRF) (159), a unified data management (UDM) (153), a network exposure function (NEF) (155), and a unified data repository (UDR) (157).
[0101] The terminal (110) is connected to the wireless access network (120) and accesses the AMF (150) that performs the mobility management function of the core network. The AMF (150) is a function or device that is in charge of both the connection to the wireless access network (120) and the mobility management of the terminal (110). The SMF (160) is an NF that manages sessions. The AMF (150) is connected to the SMF (160), and the AMF (150) routes session-related messages for the terminal (110) to the SMF (160). The SMF (160) is connected to the UPF (170) to allocate user plane resources to be provided to the terminal (110), and establishes a tunnel for transmitting data between the base station (125) and the UPF (170). PCF (180) controls information related to policy and charging for the session used by the terminal (110).
[0102] The NRF (159) stores information about NFs installed in a mobile communication operator network and performs the function of notifying the stored information. The NRF (159) can be connected to all NFs. When each NF starts operating in the operator network, it registers with the NRF (159) to notify the NRF (159) that the NF is operating within the network. The UDM (153) is an NF that performs a role similar to the HSS (home subscriber server) of a 4G network, and stores the subscription information of the terminal (110) or the context used by the terminal (110) within the network.
[0103] The NEF (155) connects a third-party server and an NF within the 5G mobile communication system. It also provides data to, updates, or acquires data from the UDR (157). The UDR (157) stores subscription information for the terminal 120, policy information, data exposed externally, or information required by a third-party application. Furthermore, the UDR (157) provides stored data to other NFs.
[0104] FIG. 2A illustrates an example of the functional structure of a terminal according to embodiments of the present disclosure. The configuration illustrated in FIG. 2A can be understood as the configuration of a terminal (110). Terms such as "... unit" and "... unit" used hereinafter refer to a unit that processes at least one function or operation, which can be implemented using hardware, software, or a combination of hardware and software.
[0105] Referring to FIG. 2a, the terminal includes a communication unit (205), a storage unit (210), and a control unit (215).
[0106] The communication unit (205) performs functions for transmitting and receiving signals via a wireless channel. For example, the communication unit (205) performs a conversion function between a baseband signal and a bit stream according to the physical layer specifications of the system. For example, when transmitting data, the communication unit (205) generates complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the communication unit (205) restores a reception bit stream by demodulating and decoding the baseband signal. In addition, the communication unit (205) upconverts a baseband signal into an RF band signal and transmits it through an antenna, and downconverts an RF band signal received through the antenna into a baseband signal. For example, the communication unit (205) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc.
[0107] In addition, the communication unit (205) may include a plurality of transmit / receive paths. Furthermore, the communication unit (205) may include at least one antenna array composed of a plurality of antenna elements. In terms of hardware, the communication unit (205) may be composed of digital circuits and analog circuits (e.g., radio frequency integrated circuits (RFIC)). Here, the digital circuits and analog circuits may be implemented in a single package. In addition, the communication unit (205) may include a plurality of RF chains. Furthermore, the communication unit (205) may perform beamforming.
[0108] The communication unit (205) transmits and receives signals as described above. Accordingly, all or part of the communication unit (205) may be referred to as a "transmitter," a "receiver," or a "transmitting and receiving unit." Furthermore, in the following description, transmission and reception performed via a wireless channel are used to mean that the communication unit (205) performs the processing described above.
[0109] The storage unit (210) stores data such as basic programs, application programs, and setting information for the operation of the terminal. The storage unit (210) may be composed of volatile memory, non-volatile memory, or a combination of volatile and non-volatile memory. In addition, the storage unit (210) provides stored data upon request from the control unit (215).
[0110] The control unit (215) controls the overall operations of the terminal. For example, the control unit (215) transmits and receives signals through the communication unit (205). In addition, the control unit (215) records and reads data in the storage unit (210). In addition, the control unit (215) can perform functions of the protocol stack required by the communication standard. To this end, the control unit (215) may include at least one processor or microprocessor, or may be a part of a processor. In addition, a part of the communication unit (205) and the control unit (215) may be referred to as a CP (communication processor). According to various embodiments, the control unit (215) may control to perform synchronization using a wireless communication network. For example, the control unit (215) may control the terminal to perform operations according to various embodiments described below.
[0111] According to various embodiments of the present disclosure, a terminal may be composed of a mobile equipment (ME) and a universal mobile telecommunications service (UMTS) subscriber identity module (USIM). The ME may include a mobile terminal (MT) and terminal equipment (TE). The MT may be a part where a wireless access protocol operates, and the TE may be a part where a control function operates. For example, in the case of a wireless communication terminal (e.g., a mobile phone), the MT and the TE may be integrated, and in the case of a laptop, the MT and the TE may be separated. The present disclosure may express the ME and the USIM as distinct entities depending on the operation of each component, but is not limited thereto, and may express the ME and the USIM as a terminal (e.g., UE) including the ME, or it is of course possible to describe various embodiments of the present disclosure by expressing the ME as a terminal.
[0112] FIG. 2B illustrates an example of the functional structure of a base station according to embodiments of the present disclosure. The configuration illustrated in FIG. 2B can be understood as the configuration of a base station (120). Terms such as "...unit" and "...unit" used hereinafter refer to a unit that processes at least one function or operation, which can be implemented using hardware, software, or a combination of hardware and software.
[0113] Referring to FIG. 2b, the base station includes a wireless communication unit (235), a backhaul communication unit (220), a storage unit (225), and a control unit (230).
[0114] The wireless communication unit (235) performs functions for transmitting and receiving signals via a wireless channel. For example, the wireless communication unit (235) performs a conversion function between baseband signals and bit streams according to the physical layer specifications of the system. For example, when transmitting data, the wireless communication unit (235) encodes and modulates the transmitted bit stream to generate complex symbols. Additionally, when receiving data, the wireless communication unit (235) restores the received bit stream by demodulating and decoding the baseband signal.
[0115] In addition, the wireless communication unit (235) upconverts a baseband signal into an RF (radio frequency) band signal and transmits it through an antenna, and downconverts an RF band signal received through the antenna into a baseband signal. To this end, the wireless communication unit (235) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital to analog convertor (DAC), an analog to digital convertor (ADC), etc. In addition, the wireless communication unit (235) may include a plurality of transmission and reception paths. Furthermore, the wireless communication unit (235) may include at least one antenna array composed of a plurality of antenna elements.
[0116] In terms of hardware, the wireless communication unit (235) may be composed of a digital unit and an analog unit, and the analog unit may be composed of a plurality of sub-units depending on operating power, operating frequency, etc. The digital unit may be implemented with at least one processor (e.g., a digital signal processor (DSP)).
[0117] The wireless communication unit (235) transmits and receives signals as described above. Accordingly, all or part of the wireless communication unit (235) may be referred to as a "transmitter," a "receiver," or a "transceiver." Furthermore, in the following description, transmission and reception performed via a wireless channel are used to mean that the wireless communication unit (235) performs the processing described above.
[0118] The backhaul communication unit (220) provides an interface for communicating with other nodes within the network. That is, the backhaul communication unit (220) converts a bit string transmitted from a base station to another node, such as another access node, another base station, an upper node, a core network, etc., into a physical signal, and converts a physical signal received from another node into a bit string.
[0119] The storage unit (225) stores data such as basic programs, application programs, and setting information for the operation of the base station. The storage unit (225) may be composed of volatile memory, non-volatile memory, or a combination of volatile and non-volatile memory. In addition, the storage unit (225) provides stored data upon request from the control unit (230).
[0120] The control unit (230) controls the overall operations of the base station. For example, the control unit (230) transmits and receives signals through the wireless communication unit (235) or the backhaul communication unit (220). In addition, the control unit (230) records and reads data in the storage unit (225). In addition, the control unit (230) can perform the functions of the protocol stack required by the communication standard. According to another implementation example, the protocol stack can be included in the wireless communication unit (235). For this purpose, the control unit (230) can include at least one processor. According to various embodiments, the control unit (230) can control to perform synchronization using a wireless communication network. For example, the control unit (230) can control the base station to perform operations according to various embodiments described below.
[0121] FIG. 2C illustrates an example of the functional structure of a core network object according to embodiments of the present disclosure. It illustrates the configuration of a core network object in a wireless communication system according to various embodiments of the present disclosure. The configuration illustrated in FIG. 2C can be understood as a configuration of a device having the function of at least one of the network entities including the AMF (150) of FIG. 1. Terms such as "... unit" and "... device" used hereinafter mean a unit that processes at least one function or operation, and this can be implemented by hardware, software, or a combination of hardware and software.
[0122] Referring to the above drawing 2c, the core network object is configured to include a communication unit (240), a storage unit (245), and a control unit (250).
[0123] The communication unit (240) provides an interface for performing communication with other devices within the network. That is, the communication unit (240) converts a bit string transmitted from the core network object to another device into a physical signal, and converts a physical signal received from another device into a bit string. That is, the communication unit (240) can transmit and receive signals. Accordingly, the communication unit (240) may be referred to as a modem, a transmitter, a receiver, or a transceiver. In this case, the communication unit (240) enables the core network object to communicate with other devices or systems via a backhaul connection (e.g., wired backhaul or wireless backhaul) or via a network.
[0124] The storage unit (245) stores data such as basic programs, application programs, and setting information for the operation of the core network object. The storage unit (245) may be composed of volatile memory, non-volatile memory, or a combination of volatile and non-volatile memory. In addition, the storage unit (245) provides the stored data upon request from the control unit (250).
[0125] The control unit (250) controls the overall operations of the core network object. For example, the control unit (250) transmits and receives signals through the communication unit (240). In addition, the control unit (250) records and reads data from the storage unit (245). For this purpose, the control unit (250) may include at least one processor. According to various embodiments of the present disclosure, the control unit (250) may control synchronization using a wireless communication network. For example, the control unit (250) may control the core network object to perform operations according to various embodiments described below.
[0126] The terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, and terms referring to various identification information are provided as examples for convenience of explanation. Therefore, the present disclosure is not limited to the terms described below, and other terms referring to objects with equivalent technical meanings may be used.
[0127] For convenience of explanation, this disclosure uses terms and names defined in the 5GS (5G system) and NR (new radio) standards, the most recent standards defined by the 3GPP organization among the existing communication standards. However, this disclosure is not limited to these terms and names and can be equally applied to wireless communication networks conforming to other standards. In particular, this disclosure can be applied to 3GPP 5th generation mobile communication standards (e.g., 5GS and NR).
[0128] FIG. 3 is a diagram illustrating a method for managing a key in dual connectivity according to an embodiment of the present disclosure.
[0129] The MN (Master node) illustrated in Fig. 3 may be a Master base station connected to the UE. The MN may be a cryptographic key (or security key, or may be abbreviated as key) K for secure communication with the UE. MN may have.
[0130] The SN (Secondary Node) illustrated in Fig. 3 may be a secondary base station to be connected to the UE for dual connectivity. The SN may use a key K for secure communication with the UE through a procedure described below. SN can be obtained.
[0131] The following provides individual descriptions of the steps to be performed. While the steps are presented as if they were performed sequentially, the order of the steps may be rearranged if the operation still works.
[0132] In step 1, the MN may perform one or more of the following processes:
[0133] - MN can choose SN counter value. For example, MN can choose SN counter value by generating SN counter value. SN counter can be a constant value associated with a key to be passed to SN as described later. SN counter can be different value for each SN to be connected. SN counter can be different value for each new connection established even if connected SN is the same.
[0134] - MN to pass K to SN SN can be generated. K SN Silver K MN And can be generated using the above selected SN counter value. As an example, K SN Silver K MN And the selected SN counter value may be a key value generated as an output by using it as an input to the KDF (Key Derivation Function).
[0135] In step 2, the MN may perform one or more of the following processes:
[0136] - MN gives SN the K generated in step 1 SN can be transmitted.
[0137] - The MN can transmit security-related information about the UE to the SN. For example, the MN can transmit to the SN the types of security algorithms available to the UE. For example, the MN can transmit to the SN a policy regarding the security methods to be used by the UE.
[0138] In step 3, SN may perform one or more of the following processes:
[0139] - SN can select the security algorithm to be used in secure communication with UE.
[0140] - SN is the received K SN Keys to be used with the UE can be derived from the above derivation process. In the above derivation process, a key corresponding to the selected security algorithm can be derived.
[0141] - The SN can select the security method to use with the UE based on the security policy received in step 2.
[0142] In step 4, SN may perform one or more of the following processes:
[0143] - SN can transmit the security algorithm of its choice to MN.
[0144] - SN can transmit the security method it is using.
[0145] In step 5, the MN may perform one or more of the following processes:
[0146] - MN can transmit the SN Counter value selected in step 1 to UE.
[0147] - MN can transmit information received from SN in step 4 to UE.
[0148] In step 6, the UE may perform one or more of the following processes:
[0149] - UE has K MN Using the SN Counter value received in step 5, K SN can be created.
[0150] In step 7, the UE can notify the MN that the task is complete.
[0151] At step 8, the MN can notify the SN that the task is complete.
[0152] FIG. 4 is a diagram illustrating a procedure for changing a secondary node in dual connectivity based on the method disclosed in FIG. 3.
[0153] The MN (Master node) illustrated in Fig. 4 may be a Master base station connected to the UE. The MN uses a key K for secure communication with the UE. MN may have.
[0154] The S-SN (Source-Secondary Node) illustrated in Fig. 4 may be a secondary base station connected to the UE for dual connectivity. The S-SN may be a key K for secure communication with the UE. SN may have.
[0155] The multiple Target-Secondary Nodes (T-SNs) illustrated in Fig. 4 may be candidate secondary base stations to be connected to the UE instead of the S-SN for dual connectivity. The T-SN may use a key K for secure communication with the UE through a procedure described below. SN can be obtained.
[0156] The procedure of FIG. 4 is disclosed based on the procedure of FIG. 3. In other words, most of the procedures of FIG. 4 correspond to the procedures disclosed in FIG. 3. Therefore, for readability, contents already illustrated in FIG. 3 may not be described in the disclosure of FIG. 4.
[0157] The following provides individual descriptions of the steps to be performed. While the steps are presented as if they were performed sequentially, the order of the steps may be rearranged if the operation still works.
[0158] In step 1, the MN may perform one or more of the following processes:
[0159] - MN can select SN counter values. SN counter may have different values for each SN to be connected. SN counter may have different values for each new connection established, even if the connected SN is the same.
[0160] - MN to deliver K to T-SNs SN can generate each K SN Silver K MN And can be generated using the value of one of the above selected SN counters.
[0161] In step 2, the MN may perform one or more of the following processes:
[0162] - MN can perform the procedure corresponding to step 2 of Figure 3 for each T-SN.
[0163] In step 3, T-SNs may perform one or more of the following processes:
[0164] - Each T-SN can perform the procedure corresponding to step 4 of Figure 3 for the MN.
[0165] In step 4, the MN may perform one or more of the following processes:
[0166] - The MN can provide the UE with a list of selected T-SNs.
[0167] - The MN can provide the UE with conditional information on when each T-SN can be selected. This information can be included as part of the Conditional PSCell Change (CPC) configuration.
[0168] - MN assigns K to each T-SN to UE. SN The corresponding SN Counter values can be provided. Later, the UE can use this information to determine which T-SN is generated using which SN Counter value. SN It may be possible to determine whether you have .
[0169] In step 5, the UE can notify the MN that the task is complete.
[0170] In step 5a, the MN can inform the S-SN of the progress of the task. For example, the MN can inform the S-SN that the UE has received the CPC configuration.
[0171] In step 6, the UE may perform one or more of the following processes:
[0172] - The UE can select a T-SN to replace the S-SN based on the information received in step 4. As an example, the UE can select a T-SN that can be replaced from the received T-SN list based on the received condition information (e.g., CPC configuration).
[0173] - UE has K MN Key K to be used for secure communication with the selected T-SN using the SN Counter value received in step 4. SN can be created.
[0174] In step 7, the UE may notify the MN that the task is complete. At this time, one or more of the following information may be transmitted to the MN.
[0175] - The UE can transmit information to the MN that can indicate the T-SN to which it will be connected.
[0176] In step 8, the MN can request the S-SN to disconnect.
[0177] In step 9, the S-SN can notify the MN that the disconnection is complete.
[0178] In step 10, the MN can notify the T-SN to which the UE will be connected that the task is complete.
[0179] FIG. 5 is a diagram illustrating another method for managing keys in dual connectivity according to an embodiment of the present disclosure.
[0180] The MN (Master node) illustrated in Fig. 5 may be a Master base station connected to the UE. The MN may be a cryptographic key (or security key, or may be abbreviated as key) K for secure communication with the UE. MN may have.
[0181] The SN (Secondary Node) illustrated in Fig. 5 may be a secondary base station to be connected to the UE for dual connectivity. The SN may use a key K for secure communication with the UE through a procedure described below. SN can be obtained.
[0182] The following provides individual descriptions of the steps to be performed. While the steps are presented as if they were performed sequentially, the order of the steps may be rearranged if the operation still works.
[0183] In step 1, the MN may perform one or more of the following processes:
[0184] - The MN can transmit security-related information about the UE to the SN. For example, the MN can transmit to the SN the types of security algorithms available to the UE. For example, the MN can transmit to the SN a policy regarding the security methods to be used by the UE.
[0185] In step 2, SN may perform one or more of the following processes:
[0186] - SN can select the security algorithm to be used in secure communication with UE.
[0187] - The SN can select the security method to use with the UE based on the security policy received in step 2.
[0188] In step 3, SN may perform one or more of the following processes:
[0189] - SN can transmit the security algorithm of its choice to MN.
[0190] - SN can transmit the security method it is using.
[0191] In step 4, the MN may perform one or more of the following processes:
[0192] - MN can transmit information received from SN in step 4 to UE.
[0193] In step 5, the UE may perform one or more of the following processes:
[0194] - The UE can select the SN counter value. For example, the MN can select the SN counter value by generating the SN counter value. The SN counter can be a constant value associated with a key to be passed to the SN described later. The SN counter can have a different value for each SN to be connected. The SN counter can have a different value each time a new connection is established, even if the connected SN is the same.
[0195] - UE has K MN And using the above selected SN Counter value, K SN can be generated. As an example, K SN Silver K MN And the selected SN counter value may be a key value generated as an output by using it as an input to a KDF (Key Derivation Function).
[0196] In step 6, the UE may notify the MN that the task is complete. At this time, the UE may additionally perform one or more of the following steps:
[0197] - The UE can transmit the SN Counter value selected in step 5 to the MN.
[0198] In step 7, the MN may perform one or more of the following processes:
[0199] - MN to pass K to SN SN can be generated. K SN Silver K MN It can be generated using the SN counter value received in step 6.
[0200] In step 8, the MN may notify the SN that the task is complete. At this time, the MN may additionally perform one or more of the following steps:
[0201] - MN gives SN the K generated in step 7 SN can be transmitted.
[0202] FIG. 6 is a diagram illustrating a procedure for changing a secondary node in dual connectivity based on the method disclosed in FIG. 5.
[0203] The MN (Master node) illustrated in Fig. 6 may be a Master base station connected to the UE. The MN may use a key K for secure communication with the UE. MN may have.
[0204] The S-SN (Source-Secondary Node) illustrated in Fig. 6 may be a secondary base station connected to the UE for dual connectivity. The S-SN may be a key K for secure communication with the UE. SN may have.
[0205] The T-SN (Target-Secondary Node) illustrated in Fig. 6 may be a candidate secondary base station to be connected to the UE instead of the S-SN for dual connectivity. The T-SN may use a key K for secure communication with the UE through a procedure described below. SNcan be obtained.
[0206] The procedure of FIG. 6 is disclosed based on the procedure of FIG. 5. In other words, most of the procedures of FIG. 6 correspond to the procedures disclosed in FIG. 5. Therefore, for readability, content already depicted in FIG. 5 may not be described in the disclosure of FIG. 6.
[0207] The following provides individual descriptions of the steps to be performed. While the steps are presented as if they were performed sequentially, the order of the steps may be rearranged if the operation still works.
[0208] In step 1, the MN may perform one or more of the following processes:
[0209] - MN can perform the procedure corresponding to step 1 of Fig. 5 for each T-SN.
[0210] In step 2, T-SNs may perform one or more of the following processes:
[0211] - Each T-SN can perform the procedure corresponding to step 3 of Figure 5 for the MN.
[0212] In step 3, the MN may perform one or more of the following processes:
[0213] - The MN can provide the UE with a list of selected T-SNs.
[0214] - The MN can provide the UE with conditional information on when each T-SN can be selected. This information can be included as part of the Conditional PSCell Change (CPC) configuration.
[0215] In step 4, the UE can notify the MN that the task is complete.
[0216] In step 4a, the MN can inform the S-SN of the progress of the task. For example, the MN can inform the S-SN that the UE has received the CPC configuration.
[0217] In step 5, the UE may perform one or more of the following processes:
[0218] - The UE can select a T-SN to replace the S-SN based on the information received in step 3. As an example, the UE can select a T-SN that can be replaced from the received T-SN list based on the received condition information (e.g., CPC configuration).
[0219] - The UE can select the SN Counter value to be used for key generation for secure communication with the selected T-SN.
[0220] - UE has K MN Key K to be used for secure communication with the selected T-SN using the selected SN Counter value. SN can be created.
[0221] In step 6, the UE may notify the MN that the task is complete. At this time, the UE may additionally perform one or more of the following steps:
[0222] - The UE can transmit information to the MN that can indicate the T-SN to which it will be connected.
[0223] - The UE can transmit the SN counter value selected in step 5 to the MN.
[0224] In step 7, the MN may perform one or more of the following processes:
[0225] - MN will forward K to T-SN to be connected to UE. SN can be generated. The above K SN Silver K MNIt can be generated using the SN counter value received in step 6.
[0226] In step 8, the MN can request the S-SN to disconnect.
[0227] In step 9, the S-SN can notify the MN that the disconnection is complete.
[0228] In step 10, the MN may notify the T-SN to which the UE is connected that the task is complete. At this time, the MN may additionally perform one or more of the following steps.
[0229] - MN sends K generated in step 7 to T-SN SN can be transmitted.
[0230] FIG. 7 is a diagram illustrating a procedure for continuously changing a secondary node in dual connectivity by linking the two methods disclosed in FIG. 3 and FIG. 5.
[0231] The MN (Master node) illustrated in Fig. 7 may be a Master base station connected to the UE. The MN may use a key K for secure communication with the UE. MN may have.
[0232] The S-SN (Source-Secondary Node) illustrated in Fig. 7 may be a secondary base station connected to the UE for dual connectivity. The S-SN may be a key K for secure communication with the UE. SN may have.
[0233] The T-SN (Target-Secondary Node) illustrated in Fig. 7 may be a candidate secondary base station to be connected to the UE instead of the S-SN for dual connectivity. The T-SN generates a key K for secure communication with the UE through a procedure described below. SNcan be obtained. At this time, T-SN(OLD) may mean an SN that operates in the manner described in FIG. 3. At this time, T-SN(NEW) may mean an SN that operates in the manner described in FIG. 5. T-SN(OLD) may mean an SN that does not support the Selective SCG function described later, and T-SN(NEW) may mean an SN that supports the Selective SCG function described later.
[0234] Let us define the term "Selective SCG." Through Figures 4 and 6, the process of a UE receiving CPC configuration information from an MN and then using it to replace an SN is described. Selective SCG refers to a technology that continuously replaces SNs by utilizing the CPC configuration information received by the UE. In other words, this refers to a technology in which a UE receives a CPC configuration from an MN, uses it to replace an SN, and then, when it wants to switch to a new SN later, it repeats the process of switching to a new SN using the CPC configuration already provided without receiving a CPC configuration from the MN again. When Selective SCG technology is utilized, a single SN can be selected multiple times by the UE.
[0235] The procedure of FIG. 7 is disclosed based on the procedures of FIGS. 3 and 5. In other words, most of the procedures of FIG. 7 correspond to the procedures disclosed in FIGS. 3 and 5. Therefore, for readability, contents already illustrated in FIGS. 3 and 5 may not be described in the disclosure of FIG. 7.
[0236] The following provides individual descriptions of the steps to be performed. While the steps are presented as if they were performed sequentially, the order of the steps may be rearranged if the operation still works.
[0237] In step 1, the MN may perform one or more of the following processes:
[0238] - MN can select SN counter values. SN counter may have different values for each SN to be connected. SN counter may have different values for each new connection established, even if the connected SN is the same.
[0239] - MN to deliver K to T-SNs SN can generate each K SN Silver K MN And can be generated using the value of one of the above selected SN counters.
[0240] In step 2, the MN may perform one or more of the following processes:
[0241] - MN can perform the procedure corresponding to step 2 of Figure 3 for each T-SN.
[0242] - The MN can send an indicator to each T-SN asking how it operates. That is, the MN can send an indicator asking whether the T-SN operates in the manner described in FIG. 3 or in the manner described in FIG. 5. This action can be interpreted as having the same meaning as sending an indicator asking whether the T-SN supports the selective SCG function. If the MN knows in advance how the other T-SN operates (or what functions it supports), the transmission of the indicator can be omitted. This indicator can also be understood as a request message for information about the operating method of the T-SN or whether it supports the selective SCG function.
[0243] In step 3, T-SNs may perform one or more of the following processes:
[0244] - Each T-SN can perform a procedure corresponding to step 4 of FIG. 3 or step 3 of FIG. 5 for the MN.
[0245] - If the T-SN is an SN that operates in the manner described in FIG. 5, the T-SN may transmit an indicator indicating that it is an SN that operates in the manner described in FIG. 5. Alternatively, if the T-SN is an SN that operates in the manner described in FIG. 5 and has received an indicator from the MN asking about the operating mode in step 2, the T-SN may transmit an indicator indicating that it is an SN that operates in the manner described in FIG. 5. Such indicators may mean information about the operating mode of each T-SN or information itself about whether the selective SCG function is supported.
[0246] In step 4, the MN may perform one or more of the following processes:
[0247] - The MN can provide the UE with a list of selected T-SNs.
[0248] - The MN can provide the UE with conditional information on when each T-SN can be selected. This information can be included as part of the Conditional PSCell Change (CPC) configuration.
[0249] - MN assigns K to each T-SN to UE. SN The corresponding SN Counter values can be provided. Later, the UE can use this information to determine which T-SN is generated using which SN Counter value. SN It may be possible to determine whether you have .
[0250] - The MN can inform the UE of the functions supported by each T-SN. For example, the ME can transmit information to the UE about whether each T-SN operates as described in FIG. 3 or as described in FIG. 5. This can be interpreted as indicating whether the T-SN supports the selective SCG function or not. This information can be included as part of the Conditional PSCell Change (CPC) configuration.
[0251] - The MN can provide the UE with policy information indicating whether an SN operating in the manner described in FIG. 3 can be reused. SNs operating in the manner described in FIG. 3 do not inherently support selective SCG, and therefore cannot be selected consecutively without additional work. In other words, additional work is required for an SN operating in the manner described in FIG. 3 to be reused. The policy information may include whether this additional work is permitted. The policy information may be included as part of a Conditional PSCell Change (CPC) configuration.
[0252] In step 5, the UE can notify the MN that the task is complete.
[0253] In step 5a, the MN can inform the S-SN of the progress of the task. For example, the MN can inform the S-SN that the UE has received the CPC configuration.
[0254] The process of performing selective SCG will be explained below.
[0255] CASE1. The selected T-SN is based on Fig. 5.
[0256] - If the T-SN is initially selected or re-selected, steps 5 to 10 disclosed in FIG. 6 may be performed.
[0257] - When the T-SN is initially selected, steps 6 to 10 disclosed in FIG. 4 may be performed.
[0258] CASE2. The selected T-SN is based on Figure 3 & is not reusable.
[0259] - The T-SN can be selected only once, and at this time, steps 6 to 10 disclosed in FIG. 4 can be performed.
[0260] CASE3. The selected T-SN is based on the reusable policy in Figure 3.
[0261] - When the corresponding T-SN is initially selected, steps 6 to 10 disclosed in FIG. 4 may be performed.
[0262] - When the corresponding T-SN is re-selected, the following process may be performed. The UE may request the MN to connect to the corresponding T-SN. At this time, the UE may transmit a series of information necessary for the MN to recognize that 'the corresponding T-SN operates based on Fig. 3 and has been re-selected'. For example, the UE may additionally transmit information to the MN about 'the fact that the corresponding T-SN operates based on Fig. 3' and / or 'the fact that the corresponding T-SN has been re-selected'. If the MN already knows the above information, the transmission of such information may be omitted. In addition, one of the following processes may be additionally performed.
[0263] ■ Steps 1 to 8 of FIG. 3 may be performed. Additionally, a procedure for releasing S-SN (steps 8 to 9 of FIG. 4) may be performed.
[0264] ■ Steps 5 to 7 of FIG. 5 may be performed. Subsequently, steps 2 to 4 of FIG. 3 may be performed. Subsequently, step 8 of FIG. 3 may be performed. Additionally, a procedure for releasing the S-SN (steps 8 to 9 of FIG. 4) may be performed.
[0265] FIG. 8 is a diagram illustrating another procedure for continuously changing a secondary node in dual connectivity by linking the two methods disclosed in FIG. 3 and FIG. 5.
[0266] The MN (Master node) illustrated in Fig. 8 may be a Master base station connected to the UE. The MN may use a key K for secure communication with the UE. MN may have.
[0267] The S-SN (Source-Secondary Node) illustrated in Fig. 8 may be a secondary base station connected to the UE for dual connectivity. The S-SN may be a key K for secure communication with the UE. SN may have.
[0268] The T-SN (Target-Secondary Node) illustrated in Fig. 8 may be a candidate secondary base station to be connected to the UE instead of the S-SN for dual connectivity. The T-SN generates a key K for secure communication with the UE through a procedure described below. SN can be obtained. At this time, T-SN(OLD) may mean an SN that operates in the manner described in FIG. 3. At this time, T-SN(NEW) may mean an SN that operates in the manner described in FIG. 5. T-SN(OLD) may mean an SN that does not support the Selective SCG function described later, and T-SN(NEW) may mean an SN that supports the Selective SCG function described later.
[0269] The procedure of FIG. 8 is disclosed based on the procedures of FIGS. 3 and 5. In other words, most of the procedures of FIG. 8 correspond to the procedures disclosed in FIGS. 3 and 5. Therefore, for readability, contents already illustrated in FIGS. 3 and 5 may not be described in the disclosure of FIG. 8.
[0270] The following provides individual descriptions of the steps to be performed. While the steps are presented as if they were performed sequentially, the order of the steps may be rearranged if the operation still works.
[0271] In step 1, the MN may perform one or more of the following processes:
[0272] - MN can select SN counter values for T-SN(OLD). SN counter may have different values for each SN. Also, even for the same SN, if a new connection is established, SN counter may have to have a new value.
[0273] - MN to deliver K to T-SN(OLD) SN can generate each K SN Silver K MN And can be generated using the value of one of the above selected SN counters.
[0274] In step 2, the MN may perform one or more of the following processes:
[0275] - MN can perform the procedure corresponding to step 2 of Figure 3 for each T-SN (OLD).
[0276] - MN can perform the procedure corresponding to step 1 of Fig. 5 for each T-SN (NEW).
[0277] In step 3, T-SNs may perform one or more of the following processes:
[0278] - Each T-SN can perform a procedure corresponding to step 4 of FIG. 3 or step 3 of FIG. 5 for the MN.
[0279] In step 4, the MN may perform one or more of the following processes:
[0280] - The MN can provide the UE with a list of selected T-SNs.
[0281] - The MN can provide the UE with conditional information on when each T-SN can be selected. This information can be included as part of the Conditional PSCell Change (CPC) configuration.
[0282] - MN assigns K to each T-SN (OLD) to UE. SN The corresponding SN Counter values can be provided. Later, the UE can use this information to determine which T-SN (OLD) was generated using which SN Counter value. SN It may be possible to determine whether you have .
[0283] - The MN can transmit information to the UE about the functions supported by each T-SN. For example, the ME can transmit information to the UE about whether each T-SN operates as described in FIG. 3 or as described in FIG. 5. This can be interpreted as indicating whether the T-SN supports the selective SCG function or not. This information can be included as part of the Conditional PSCell Change (CPC) configuration.
[0284] - The MN may transmit policy information to the UE, including whether the SN can be reused, operating in the manner described in FIG. 3. For a more detailed description, refer to the disclosure of FIG. 7. The information may be included as part of the Conditional PSCell Change (CPC) configuration.
[0285] In step 5, the UE can notify the MN that the task is complete.
[0286] In step 5a, the MN can inform the S-SN of the progress of the task. For example, the MN can inform the S-SN that the UE has received the CPC configuration.
[0287] The process of performing selective SCG will be explained below.
[0288] CASE1. The selected T-SN is based on Fig. 5.
[0289] - Steps 5 to 10 disclosed in FIG. 6 can be performed.
[0290] CASE2. The selected T-SN is based on Figure 3 & is not reusable.
[0291] - The T-SN can be selected only once, and at this time, steps 6 to 10 disclosed in FIG. 4 can be performed.
[0292] CASE3. The selected T-SN is based on the reusable policy in Figure 3.
[0293] - When the corresponding T-SN is initially selected, steps 6 to 10 disclosed in FIG. 4 may be performed.
[0294] - When the corresponding T-SN is re-selected, the following process may be performed. The UE may request the MN to connect to the corresponding T-SN. At this time, the UE may transmit a series of information necessary for the MN to recognize that 'the corresponding T-SN operates based on Fig. 3 and has been re-selected'. For example, the UE may additionally transmit information to the MN about 'the fact that the corresponding T-SN operates based on Fig. 3' and / or 'the fact that the corresponding T-SN has been re-selected'. If the MN already knows the above information, the transmission of such information may be omitted. In addition, one of the following processes may be additionally performed.
[0295] ■ Steps 1 to 8 of FIG. 3 may be performed. Additionally, a procedure for releasing S-SN (steps 8 to 9 of FIG. 4) may be performed.
[0296] ■ Steps 5 to 7 of FIG. 5 may be performed. Subsequently, steps 2 to 4 of FIG. 3 may be performed. Subsequently, step 8 of FIG. 3 may be performed. Additionally, a procedure for releasing the S-SN (steps 8 to 9 of FIG. 4) may be performed.
[0297] FIG. 9 is a diagram illustrating another method for managing keys in dual connectivity according to an embodiment of the present disclosure.
[0298] The MN (Master node) illustrated in Fig. 9 may be a Master base station connected to the UE. The MN may be a cryptographic key (or security key, or may be abbreviated as key) K for secure communication with the UE. MN may have.
[0299] The SN (Secondary Node) illustrated in Fig. 9 may be a secondary base station to be connected to the UE for dual connectivity. The SN generates a key K for secure communication with the UE through a procedure described below. SN can be obtained.
[0300] The following provides individual descriptions of the steps to be performed. While the steps are presented as if they were performed sequentially, the order of the steps may be rearranged if the operation still works.
[0301] In step 1, the MN may perform one or more of the following processes:
[0302] - MN can select SN counter values. For example, MN can select SN counter values by generating SN counter values. SN counter can be a constant value associated with a key to be passed to SN, which will be described later.
[0303] - MN to pass K to SN SN can generate each K SN Silver K MN and can be generated using one of the above selected SN counter values. As an example, each K SN Silver K MN It can be a key value generated as an output by using one of the above-mentioned selected SN counter values as an input to a KDF (Key Derivation Function).
[0304] In step 2, the MN may perform one or more of the following processes:
[0305] - MN gives SN the K generated in step 1 SN You can transmit them.
[0306] - The MN can transmit security-related information about the UE to the SN. For example, the MN can transmit to the SN the types of security algorithms available to the UE. For example, the MN can transmit to the SN a policy regarding the security methods to be used by the UE.
[0307] In step 3, SN may perform one or more of the following processes:
[0308] - SN can select the security algorithm to be used in secure communication with UE.
[0309] - SN is the received K SN Keys to be used with the UE can be derived from them. In the above derivation process, a key corresponding to the selected security algorithm can be derived.
[0310] - The SN can select the security method to use with the UE based on the security policy received in step 2.
[0311] In step 4, SN may perform one or more of the following processes:
[0312] - SN can transmit the security algorithm of its choice to MN.
[0313] - SN can transmit the security method it is using.
[0314] In step 5, the MN may perform one or more of the following processes:
[0315] - MN can transmit the SN Counter values selected in step 1 to UE.
[0316] - MN can transmit information received from SN in step 4 to UE.
[0317] In step 6, the UE may perform one or more of the following processes:
[0318] - The UE can select one of the received SN counter values.
[0319] - K you own MN And using the above selected SN Counter value, K SN can be created.
[0320] In step 7, the UE may notify the MN that the task is complete. At this time, one or more of the following steps may be performed.
[0321] - The UE may transmit to the MN information indicating the SN counter value selected by the UE in step 6 (in the drawing, this information is indicated as KI). The information may be the SN counter value selected by the UE in step 6. The information may be a third information that allows the UE to specify the SN counter value selected by the UE in step 6. If the MN can determine which SN counter value was selected by the UE without transmitting the information, the transmission of the information may be omitted.
[0322] In step 8, the MN may notify the SN that the task is complete. At this time, one or more of the following processes may be performed.
[0323] - MN sends K to SN corresponding to the SN counter value selected by UE in step 6. MN Information indicating the SN counter value can be transmitted. If it is possible to determine which SN counter value has been selected without transmitting the above information, transmission of the above information can be omitted.
[0324] FIG. 10 is a diagram illustrating a procedure for changing a secondary node in dual connectivity based on the method disclosed in FIG. 9.
[0325] The MN (Master node) illustrated in Fig. 10 may be a Master base station connected to the UE. The MN may use a key K for secure communication with the UE. MN may have.
[0326] The S-SN (Source-Secondary Node) illustrated in Fig. 10 may be a secondary base station connected to the UE for dual connectivity. The S-SN may be a key K for secure communication with the UE. SN may have.
[0327] The T-SN (Target-Secondary Node) illustrated in Fig. 10 may be a candidate secondary base station to be connected to the UE instead of the S-SN for dual connectivity. The T-SN generates a key K for secure communication with the UE through a procedure described below. SN can be obtained.
[0328] The procedure of FIG. 10 is disclosed based on the procedure of FIG. 9. In other words, most of the procedures of FIG. 10 correspond to the procedures disclosed in FIG. 9. Therefore, for readability, contents already illustrated in FIG. 9 may not be described in the disclosure of FIG. 10.
[0329] The following provides individual descriptions of the steps to be performed. While the steps are presented as if they were performed sequentially, the order of the steps may be rearranged if the operation still works.
[0330] In step 1, the MN may perform one or more of the following processes:
[0331] - MN can select SN counter values. Multiple SN counter values can be assigned to each T-SN.
[0332] - MN to deliver K to each T-SN SN can generate each K SN Silver K MN And can be generated using the value of one of the above selected SN counters.
[0333] In step 2, the MN may perform one or more of the following processes:
[0334] - MN can perform the procedure corresponding to step 2 of Fig. 9 for each T-SN.
[0335] In step 3, T-SNs may perform one or more of the following processes:
[0336] - Each T-SN can perform the procedure corresponding to step 4 of Fig. 9 for the MN.
[0337] In step 4, the MN may perform one or more of the following processes:
[0338] - The MN can provide the UE with a list of selected T-SNs.
[0339] - The MN can provide the UE with conditional information on when each T-SN can be selected. This information can be included as part of the Conditional PSCell Change (CPC) configuration.
[0340] - MN assigns K to each T-SN to UE. SN The SN Counter values corresponding to the fields can be provided. Later, the UE can use this information to determine which T-SN is generated using which SN Counter values. SN It may be possible to determine whether they have the
[0341] In step 5, the UE can notify the MN that the task is complete.
[0342] In step 5a, the MN can inform the S-SN of the progress of the task. For example, the MN can inform the S-SN that the UE has received the CPC configuration.
[0343] In step 6, the UE may perform one or more of the following processes:
[0344] - The UE can select a T-SN to replace the S-SN based on the information received in step 4. As an example, the UE can select a T-SN that can be replaced from the received T-SN list based on the received condition information (e.g., CPC configuration).
[0345] - UE has K MNAnd, a key K to be used for secure communication with the selected T-SN using one of the SN Counter values associated with the selected T-SN received in step 4. SN can be created.
[0346] In step 7, the UE may notify the MN that the task is complete. At this time, one or more of the following steps may be performed.
[0347] - The UE can transmit information to the MN that can indicate the T-SN to which it will be connected.
[0348] - The UE may transmit to the MN information indicating the SN counter value selected by the UE in step 6 (in the drawing, this information is indicated as KI). The information may be the SN counter value selected by the UE in step 6. The information may be third information that allows the UE to specify the SN counter value selected by the UE in step 6. If it is possible to determine which SN counter value has been selected without transmitting the information, the transmission of the information may be omitted.
[0349] In step 8, the MN can request the S-SN to disconnect.
[0350] In step 9, the S-SN can notify the MN that the disconnection is complete.
[0351] In step 10, the MN may notify the T-SN to which the UE is connected that the task is complete. At this time, one or more of the following steps may be performed.
[0352] - MN sends K to T-SN corresponding to the SN counter value selected by UE in step 6. MN Information indicating the SN counter value can be transmitted. If it is possible to determine which SN counter value has been selected without transmitting the above information, transmission of the above information can be omitted.
[0353] FIG. 11 is a diagram illustrating a procedure for continuously changing a secondary node in dual connectivity by linking the two methods disclosed in FIG. 3 and FIG. 9.
[0354] The MN (Master node) illustrated in Fig. 11 may be a Master base station connected to the UE. The MN may use a key K for secure communication with the UE. MN may have.
[0355] The S-SN (Source-Secondary Node) illustrated in Fig. 11 may be a secondary base station connected to the UE for dual connectivity. The S-SN may be a key K for secure communication with the UE. SN may have.
[0356] The T-SN (Target-Secondary Node) illustrated in Fig. 11 may be a candidate secondary base station to be connected to the UE instead of the S-SN for dual connectivity. The T-SN generates a key K for secure communication with the UE through a procedure described below. SN can be obtained. At this time, T-SN(OLD) may mean an SN that operates in the manner described in FIG. 3. At this time, T-SN(NEW) may mean an SN that operates in the manner described in FIG. 9. T-SN(OLD) may mean an SN that does not support the Selective SCG function described later, and T-SN(NEW) may mean an SN that supports the Selective SCG function described later.
[0357] The procedure of FIG. 11 is disclosed based on the procedures of FIG. 3 and FIG. 9. In other words, most of the procedures of FIG. 11 correspond to the procedures disclosed in FIG. 3 and FIG. 9. Therefore, for readability, contents already illustrated in FIG. 3 and FIG. 9 may not be described in the disclosure of FIG. 11.
[0358] The following provides individual descriptions of the steps to be performed. While the steps are presented as if they were performed sequentially, the order of the steps may be rearranged if the operation still works.
[0359] In step 1, the MN may perform one or more of the following processes:
[0360] - MN can select SN counter values. Multiple SN counter values can be assigned to each TT-SN.
[0361] - MN to deliver K to each T-SN SN can generate each K SN Silver K MN And can be generated using the value of one of the above selected SN counters.
[0362] In step 2, the MN may perform one or more of the following processes:
[0363] - MN can perform the procedure corresponding to step 2 of Fig. 9 for each T-SN.
[0364] - The MN can send an indicator to each T-SN asking how it operates. In other words, it can send an indicator asking whether the T-SN operates in the manner described in FIG. 3 or in the manner described in FIG. 9. This can be interpreted as having the same meaning as sending an indicator asking whether the T-SN supports the selective SCG function. Such indicators can mean information about the operating method of each T-SN or information itself about whether the selective SCG function is supported.
[0365] In step 3, T-SNs may perform one or more of the following processes:
[0366] - Each T-SN can perform a procedure corresponding to step 4 of FIG. 3 or step 4 of FIG. 9 for the MN.
[0367] - If the T-SN is an SN that operates in the manner described in Fig. 3, the T-SN receives the K SN Only one of the values (e.g., the received K SN (The first one among the values) can be stored.
[0368] - If the T-SN is an SN that operates in the manner described in Fig. 9, the T-SN receives the K SN It can store all values. In addition, if the T-SN is an SN that operates in the manner described in Fig. 9, it can transmit an indicator indicating that it is an SN that operates in the manner described in Fig. 9.
[0369] In step 4, the MN may perform one or more of the following processes:
[0370] - The MN can provide the UE with a list of selected T-SNs.
[0371] - The MN can provide the UE with conditional information on when each T-SN can be selected. This information can be included as part of the Conditional PSCell Change (CPC) configuration.
[0372] - MN assigns K to each T-SN to UE. SN The SN Counter value(s) corresponding to the T-SN can be provided. Later, the UE can use this information to determine which T-SN is generated using which SN Counter value(s). SN It may be possible to determine whether (s) are in possession.
[0373] - The MN can inform the UE of the functions supported by each T-SN. For example, the ME can inform the UE of whether each T-SN operates as described in FIG. 3 or as described in FIG. 9. This can be interpreted as meaning the same as informing the UE of whether the T-SN supports the selective SCG function or not. This information can be included as part of the Conditional PSCell Change (CPC) configuration.
[0374] - The MN may provide the UE with policy information indicating whether the SN can be reused in the manner described in FIG. 3. For a more detailed description, see FIG. 7. The information may be included as part of the Conditional PSCell Change (CPC) configuration.
[0375] In step 5, the UE can notify the MN that the task is complete.
[0376] In step 5a, the MN can inform the S-SN of the progress of the task. For example, the MN can inform the S-SN that the UE has received the CPC configuration.
[0377] The process of performing selective SCG will be explained below.
[0378] CASE1. The selected T-SN is based on Fig. 9.
[0379] - Steps 6 to 10 disclosed in FIG. 10 can be performed.
[0380] - When a single T-SN is selected multiple times, the UE may select the SN Counter values associated with the corresponding T-SN in a specific order. For example, the UE may select the smallest SN Counter value among the SN Counter values associated with the corresponding T-SN currently held by the UE. The SN Counter values used in this way may be discarded after use.
[0381] - When one T-SN is selected multiple times, the T-SN has K SN can be selected in a specific order. As an example, the T-SN is the K associated with the lowest valued SN counter that the current UE maintains for itself. SN You can choose K used like this SN The value may be discarded when the connection with the UE is disconnected.
[0382] CASE2. The selected T-SN is based on Figure 3 & is not reusable.
[0383] - The T-SN can be selected only once, and at this time, steps 6 to 10 disclosed in FIG. 4 can be performed.
[0384] CASE3. The selected T-SN is based on the reusable policy in Figure 3.
[0385] - When the corresponding T-SN is initially selected, steps 6 to 10 disclosed in FIG. 4 may be performed.
[0386] - When the corresponding T-SN is re-selected, the following process may be performed. The UE may request the MN to connect to the corresponding T-SN. At this time, the UE may transmit a series of information necessary for the MN to recognize that 'the corresponding T-SN operates based on Fig. 3 and has been re-selected'. For example, the UE may additionally transmit information to the MN about 'the fact that the corresponding T-SN operates based on Fig. 3' and / or 'the fact that the corresponding T-SN has been re-selected'. If the MN already knows the above information, the transmission of such information may be omitted. In addition, one of the following processes may be additionally performed.
[0387] ■ Steps 1 to 8 of Fig. 3 can be performed.
[0388] ■ The procedure for releasing S-SN (steps 8 to 9 of Fig. 4) can be performed.
[0389] FIG. 12 is a diagram illustrating another procedure for continuously changing a secondary node in dual connectivity by linking the two methods disclosed in FIG. 3 and FIG. 9.
[0390] The MN (Master node) illustrated in Fig. 12 may be a Master base station connected to the UE. The MN may use a key K for secure communication with the UE. MN may have.
[0391] The S-SN (Source-Secondary Node) illustrated in Fig. 12 may be a secondary base station connected to the UE for dual connectivity. The S-SN may be a key K for secure communication with the UE. SN may have.
[0392] The T-SN (Target-Secondary Node) illustrated in Fig. 12 may be a candidate secondary base station to be connected to the UE instead of the S-SN for dual connectivity. The T-SN generates a key K for secure communication with the UE through the procedure described below. SN can be obtained. At this time, T-SN(OLD) may mean an SN that operates in the manner described in FIG. 3. At this time, T-SN(NEW) may mean an SN that operates in the manner described in FIG. 9. T-SN(OLD) may mean an SN that does not support the Selective SCG function described later, and T-SN(NEW) may mean an SN that supports the Selective SCG function described later.
[0393] The procedure of FIG. 12 is disclosed based on the procedures of FIG. 3 and FIG. 9. In other words, most of the procedures of FIG. 12 correspond to the procedures disclosed in FIG. 3 and FIG. 9. Therefore, for readability, contents already illustrated in FIG. 3 and FIG. 9 may not be described in the disclosure of FIG. 12.
[0394] The following provides individual descriptions of the steps to be performed. While the steps are presented as if they were performed sequentially, the order of the steps may be rearranged if the operation still works.
[0395] In step 1, the MN may perform one or more of the following processes:
[0396] - MN can select SN counter values for T-SN(OLD). The number of SN counter values prepared for the T-SN(OLD) can be single.
[0397] - MN can select SN counter values for T-SN(NEW). There can be multiple SN counter values prepared for the T-SN(NEW).
[0398] - MN sends K to each T-SN (OLD) SN can be generated. The above K SN Silver K MN It can be generated using the SN counter value assigned to the corresponding T-SN (OLD).
[0399] - MN to deliver K to each T-SN(NEW) SN can generate the above K SN Silver K MN and can be generated using one of the SN counter values assigned to the corresponding T-SN (NEW).
[0400] In step 2, the MN may perform one or more of the following processes:
[0401] - MN can perform the procedure corresponding to step 2 of Figure 3 for each T-SN (OLD).
[0402] - MN can perform the procedure corresponding to step 2 of Fig. 9 for each T-SN (NEW).
[0403] In step 3, T-SNs may perform one or more of the following processes:
[0404] - Each T-SN can perform a procedure corresponding to step 4 of FIG. 3 or step 4 of FIG. 9 for the MN.
[0405] In step 4, the MN may perform one or more of the following processes:
[0406] - The MN can provide the UE with a list of selected T-SNs.
[0407] - The MN can provide the UE with conditional information on when each T-SN can be selected. This information can be included as part of the Conditional PSCell Change (CPC) configuration.
[0408] - MN assigns K to each T-SN to UE. SNThe SN Counter value(s) corresponding to the T-SN can be provided. Later, the UE can use this information to determine which T-SN is generated using which SN Counter value(s). SN It may be possible to determine whether (s) are in possession.
[0409] - The MN can inform the UE of the functions supported by each T-SN. For example, the ME can inform the UE of whether each T-SN is an SN that operates in the manner described in FIG. 3 or an SN that operates in the manner described in FIG. 9. This can be interpreted as meaning the same as informing the UE of whether the T-SN supports the selective SCG function or not. The above information can be included as part of the Conditional PSCell Change (CPC) configuration.
[0410] - The MN can provide the UE with policy information indicating whether the SN can be reused in the manner described in FIG. 3. For a more detailed description, see FIG. 7.
[0411] In step 5, the UE can notify the MN that the task is complete.
[0412] In step 5a, the MN can inform the S-SN of the progress of the task. For example, the MN can inform the S-SN that the UE has received the CPC configuration.
[0413] The process of performing selective SCG will be explained below.
[0414] CASE1. The selected T-SN is based on Fig. 9.
[0415] - Steps 6 to 10 disclosed in FIG. 10 can be performed.
[0416] - When a single T-SN is selected multiple times, the UE may select the SN Counter values associated with the corresponding T-SN in a specific order. For example, the UE may select the smallest SN Counter value among the SN Counter values associated with the corresponding T-SN currently held by the UE. The SN Counter values used in this way may be discarded after use.
[0417] - When one T-SN is selected multiple times, the T-SN has K SN can be selected in a specific order. As an example, the T-SN is the K associated with the lowest valued SN counter that the current UE maintains for itself. SN You can choose K used like this SN The value may be discarded when the connection with the UE is disconnected.
[0418] CASE2. The selected T-SN is based on Figure 3 & is not reusable.
[0419] - The T-SN can be selected only once, and at this time, steps 6 to 10 disclosed in FIG. 4 can be performed.
[0420] CASE3. The selected T-SN is based on the reusable policy in Figure 3.
[0421] - When the corresponding T-SN is initially selected, steps 6 to 10 disclosed in FIG. 4 may be performed.
[0422] - When the corresponding T-SN is re-selected, the following process may be performed. The UE may request the MN to connect to the corresponding T-SN. At this time, the UE may notify the MN of a series of information necessary to enable the MN to recognize that 'the corresponding T-SN operates based on Fig. 3 and has been re-selected'. For example, the UE may additionally notify the MN of 'the fact that the corresponding T-SN operates based on Fig. 3' and / or 'the fact that the corresponding T-SN has been re-selected'. If the MN already knows the above information, this notification may be omitted. In addition, one of the following processes may be additionally performed.
[0423] ■ Steps 1 to 8 of Fig. 3 can be performed.
[0424] ■ The procedure for releasing S-SN (steps 8 to 9 of Fig. 4) can be performed.
[0425] FIG. 13 is a diagram illustrating another method for managing keys in dual connectivity according to an embodiment of the present disclosure.
[0426] The MN (Master node) illustrated in Fig. 13 may be a Master base station connected to the UE. The MN may be a cryptographic key (or security key, or may be abbreviated as key) K for secure communication with the UE. MN may have.
[0427] The SN (Secondary Node) illustrated in Fig. 13 may be a secondary base station to be connected to the UE for dual connectivity. The SN may use a key K for secure communication with the UE through a procedure described below. SN can be obtained.
[0428] Below, individual descriptions of the steps to be performed during key management according to Figure 13 are provided. While each step is presented as if it were performed sequentially, the order of the steps may be changed if the operation is still possible with the order of the steps changed.
[0429] In step 1, the MN may perform one or more of the following actions:
[0430] - MN can select SN counter values. For example, MN can select SN counter values by generating SN counter values. SN counter is a constant that is passed to SN as a key K, which will be described later. SN It may be a value associated with .
[0431] - MN to pass K to SN SN can generate each K SN Silver, K MN and can be generated using one of the above selected SN counter values. As an example, each K SN Silver, K MN It may be a key value generated as an output by using one of the above-mentioned selected SN counter values as an input to a KDF (Key Derivation Function).
[0432] - MN generates K for SN SN You can transmit them.
[0433] - MN can transmit the SN counter values it generated to SN. Transmission of the above information may be omitted.
[0434] - The MN can transmit security-related information about the UE to the SN. For example, the MN can transmit to the SN the types of security algorithms available to the UE. In another example, the MN can transmit to the SN a policy regarding the security methods to be used by the UE.
[0435] In step 2, SN may perform one or more of the following processes:
[0436] - SN can select the security algorithm to be used in secure communication with UE.
[0437] - SN is K received from MN SN Security keys to be used with the UE can be derived from them. At this time, security keys corresponding to the selected security algorithm can be derived during the derivation process.
[0438] - The SN can select a security method to use with the UE based on the security policy received from the MN in step 1.
[0439] In step 3, SN may perform one or more of the following processes:
[0440] - SN can send information about the security algorithm it has chosen to MN.
[0441] - SN can transmit the security method it is using to MN.
[0442] In step 4, the MN may perform one or more of the following processes:
[0443] - MN can transmit the SN Counter values selected in step 1 to UE.
[0444] - The MN can transmit to the UE information related to the security algorithm or security method received from the SN in step 3.
[0445] In step 5, the UE may perform one or more of the following processes:
[0446] - The UE can select one of the SN counter values received from the MN.
[0447] - UE has K MN And using the above selected SN Counter value, K SN can be created.
[0448] - UE generates the above K SN The security keys to be used with the SN can be derived from the above derivation process. In the above derivation process, the UE can derive the security keys corresponding to the security algorithm received in step 4.
[0449] In step 6, the UE may notify the MN that the task is complete. At this time, one or more of the following steps may be performed.
[0450] - The UE may transmit to the MN the SN counter value selected in step 5. Transmission of the above information may be omitted.
[0451] In step 7, the MN may notify the SN that the task is complete. At this time, one or more of the following processes may be performed.
[0452] - The MN may transmit the SN counter value received from the UE in step 6 to the SN. Transmission of the above information may be omitted.
[0453] [Error handling method]
[0454] According to the above disclosure, in steps 1, 6, and 7, the SN counter value may be transmitted or, alternatively, transmission may be omitted. If the information is transmitted, the transmitted information may be used to deal with error situations.
[0455] [CASE A]
[0456] - SN checks the SN Counter received from MN in step 7 and generates the corresponding K SN You can choose the value.
[0457] - In the above method, UE and SN have different K SN It can reduce the possibility of errors in selecting values.
[0458] [CASE B]
[0459] - SN does not check the SN Counter received from MN in step 7. SN You can also choose a value.
[0460] - In the above case, UE and SN will be used in a predetermined order. SN A value may need to be selected. As an example, the UE sequentially selects the SN counter value in the order in which it was received and then derives the K SN The values can be used, and the SNs are also sequentially K in the order they were received. SN You can select and use the value.
[0461] - In the above case, the UE and SN are relatively different K SN The possibility of errors in selecting values increases.
[0462] - When the above error occurs, SN checks the SN Counter received in step 7 and sets the corresponding K SN The value can be reselected. In this way, SN can correct the error that occurred.
[0463] The above error handling method can be performed as part of step 7.
[0464] FIG. 14 is a diagram illustrating a procedure for changing a secondary node in dual connectivity based on the method disclosed in FIG. 13.
[0465] The MN (Master node) illustrated in Fig. 14 may be a Master base station connected to the UE. The MN may use a key K for secure communication with the UE. MN may have.
[0466] The S-SN (Source-Secondary Node) illustrated in Fig. 14 may be a secondary base station connected to the UE for dual connectivity. The S-SN may be a key K for secure communication with the UE. SNmay have.
[0467] The T-SN (Target-Secondary Node) illustrated in Fig. 14 may be a candidate secondary base station to be connected to the UE instead of the S-SN for dual connectivity. The T-SN generates a key K for secure communication with the UE through a procedure described below. SN can be obtained.
[0468] The procedure of FIG. 14 is disclosed based on the procedure of FIG. 13. In other words, most of the procedures of FIG. 14 correspond to the procedures disclosed in FIG. 13. Therefore, for readability, contents already illustrated in FIG. 13 may not be described in the disclosure of FIG. 14.
[0469] The following provides individual descriptions of the steps to be performed. While the steps are presented as if they were performed sequentially, the order of the steps may be rearranged if the operation still works.
[0470] In step 1, the MN may perform one or more of the following processes:
[0471] - MN can select SN counter values. Multiple SN counter values can be assigned to each T-SN.
[0472] - MN to deliver K to each T-SN SN can generate each K SN Silver, K MN And can be generated using the value of one of the above selected SN counters.
[0473] - MN generates K for each T-SN SN You can transmit values.
[0474] - MN can transmit SN counter values to each T-SN. Transmission of the above information may be omitted.
[0475] - MN can transmit security-related information to each T-SN. For a detailed description of the security-related information, refer to Step 1 of FIG. 13.
[0476] In step 2, T-SNs may perform one or more of the following processes:
[0477] - Each T-SN can perform procedures corresponding to steps 2 and 3 of FIG. 13.
[0478] In step 3, the MN may perform one or more of the following processes:
[0479] - The MN can provide the UE with a list of selected T-SNs.
[0480] - The MN can provide the UE with conditional information on when each T-SN can be selected. This information can be included as part of the Conditional PSCell Change (CPC) configuration.
[0481] - MN informs UE of 'K allocated to each T-SN' SN The UE can provide the SN Counter values corresponding to the T-SN. Later, the UE can use this information to determine which T-SN is generated using which SN Counter values. SN You can determine if you have the 'field'.
[0482] In step 4, the UE can notify the MN that the task is complete.
[0483] In step 4a, the MN can inform the S-SN of the progress of the task. For example, the MN can inform the S-SN that the UE has received the CPC configuration.
[0484] In step 5, the UE may perform one or more of the following processes:
[0485] - The UE can select a T-SN to replace the S-SN based on the information received from the MN in step 3. As an example, the UE can select a T-SN that can be replaced from the received T-SN list based on the received condition information (e.g., CPC configuration).
[0486] - UE has K MN And, the key K to be used for secure communication with the selected T-SN using 'one of the SN Counter values associated with the selected T-SN' received in step 3. SN can be created.
[0487] In step 6, the UE may notify the MN that the task is complete. At this time, one or more of the following steps may be performed.
[0488] - The UE can transmit information to the MN that can indicate the T-SN to which it will be connected.
[0489] - The UE may transmit to the MN the SN counter value selected by it in step 5. Transmission of the above information may be omitted.
[0490] In step 7, the MN can request the S-SN to disconnect.
[0491] In step 8, the S-SN can notify the MN that the disconnection is complete.
[0492] In step 9, the MN may notify the T-SN to which the UE is connected that the task is complete. At this time, one or more of the following steps may be performed.
[0493] - MN can transmit the 'SN counter value received in step 6' to T-SN. The above information transmission may be omitted.
[0494] [Error handling method]
[0495] - Through the steps described above, the UE and T-SN can communicate securely. However, for some reason, the UE and T-SN may not be able to communicate securely. SN If the values do not match, normal secure communication may not be possible. For the error handling method in the above case, refer to the [Error Handling] method disclosed in Fig. 13. That is, through the SN counter value, K SN Verification or reselection may be performed.
[0496] - The above error handling method can be performed as part of step 9.
[0497] FIG. 15 is a diagram illustrating another procedure for continuously changing a secondary node in dual connectivity by linking the two methods disclosed in FIG. 3 (and FIG. 4) and FIG. 13 (and FIG. 14).
[0498] The MN (Master node) illustrated in Fig. 15 may be a Master base station connected to the UE. The MN may use a key K for secure communication with the UE. MN may have.
[0499] The S-SN (Source-Secondary Node) illustrated in Fig. 15 may be a secondary base station connected to the UE for dual connectivity. The S-SN may be a key K for secure communication with the UE. SN may have.
[0500] The T-SN (Target-Secondary Node) illustrated in Fig. 15 may be a candidate secondary base station to be connected to the UE instead of the S-SN for dual connectivity. The T-SN generates a key K for secure communication with the UE through a procedure described below. SNcan be obtained. At this time, T-SN(OLD) may mean an SN that operates in the manner described in FIG. 3 (and FIG. 4). At this time, T-SN(NEW) may mean an SN that operates in the manner described in FIG. 13 (and FIG. 14). T-SN(OLD) may mean an SN that does not support the Selective SCG function described later, and T-SN(NEW) may mean an SN that supports the Selective SCG function described later.
[0501] The procedure of FIG. 15 is disclosed based on the procedures of FIG. 3 (and FIG. 4) and FIG. 13 (and FIG. 14). In other words, most of the procedures of FIG. 15 correspond to the procedures disclosed in FIG. 3 (and FIG. 4) and FIG. 13 (and FIG. 14). Therefore, for readability, content already illustrated in FIG. 3 (and FIG. 4) and FIG. 13 (and FIG. 14) may not be described in the disclosure of FIG. 15.
[0502] Below, individual descriptions of the steps to be performed according to the procedure of Figure 15 are provided. While each step is presented as if it were performed sequentially, the order of the steps may be changed if the operation is still possible.
[0503] In step 1, the MN may perform one or more of the following processes:
[0504] [For T-SN(OLD)]
[0505] - (Action O) MN can perform the process of step 1 and step 2 disclosed in Fig. 3 for each T-SN(OLD). In other words, MN can select an SN counter value for each T-SN(OLD), and based on the selected SN counter value, K to be transmitted to T-SN(OLD). SN It can generate values, and the generated K SN The value can be passed to T-SN(OLD).
[0506] - If MN knows in advance that a specific T-SN is an OLD version, it can immediately perform the above “action O” for that T-SN.
[0507] - If the MN does not know in advance that a particular T-SN (OLD) is an OLD version, one or more of the following steps may be performed:
[0508] ■ The MN can first check the version of the T-SN and then perform “action O”. For example, the MN can check the version of the T-SN by communicating with the T-SN. In another example, the MN can check the version of the T-SN by obtaining information from an external source without directly communicating with the T-SN.
[0509] ■ The MN can assume that the version of the T-SN is OLD and perform “Action O”. Later, the MN can check the version of the T-SN and confirm that no additional action is required. The MN can check the version of the T-SM by directly communicating with the T-SN or by obtaining information from an external source without directly communicating with the T-SN.
[0510] ■ MN can assume that the version of the T-SN is NEW and perform step 1 of Fig. 13. In this case, the T-SN can respond with a rejection message because it does not support the input received through step 1 of Fig. 13. In the above case, the MN can confirm that the version of the T-SN is OLD and perform “action O” accordingly.
[0511] [For T-SN(NEW)]
[0512] - (Action N) MN can perform the step 1 process disclosed in Fig. 13 for each T-SN(NEW). In other words, MN can select SN counter values for each T-SN(NEW). In addition, MN can transmit K to T-SN(NEW) based on the selected SN counter values. SN can generate values. In addition, MN can generate K SN The values can be transmitted to T-SN(NEW). Additionally, the MN can transmit the selected SN counter values to T-SN(NEW), but the transmission of the information can be omitted.
[0513] - If MN knows in advance that a specific T-SN is a NEW version, it can immediately perform the above “action N” for that T-SN.
[0514] - If the MN does not know in advance that a particular T-SN(NEW) is a NEW version, one or more of the following steps may be performed:
[0515] ■ The MN can first check the version of the T-SN and then perform “action N”. For example, the MN can check the version of the T-SN by communicating with the T-SN. In another example, the MN can check the version of the T-SN by obtaining information from an external source without directly communicating with the T-SN.
[0516] ■ MN can perform “Action O” assuming that the version of the T-SN is OLD. Later, the MN can check the version of the T-SN and determine that additional action is required. The MN can check the version of the T-SN by directly communicating with the T-SN or by obtaining information from the outside without direct communication with the T-SN. After the MN determines that the T-SN requires additional action, “Action N” can be performed. At this time, if the transmission information of the already performed “Action O” is to be reused, some actions of “Action N” can be omitted accordingly. For example, in “Action O”, the MN may already have transmitted one K to the T-SN. SN Since the values have been transmitted, only the remaining values excluding the values previously transmitted in “Action N” can be transmitted.
[0517] ■ MN can assume that the version of the T-SN is NEW and perform “Action N”. Later, the MN can confirm that no additional action is required after checking the version of the T-SN. (The MN can check the version of the T-SM by directly communicating with the T-SN or by obtaining information from the outside without directly communicating with the T-SN. Alternatively, the MN can check the version of the T-SN from the fact that the T-SN did not respond with a rejection message when the “Action N” was performed.)
[0518] In step 2, T-SNs may perform one or more of the following processes:
[0519] - OLD version T-SN(s) can perform steps 3 to 4 of Fig. 3.
[0520] - New version of T-SN(s) can perform steps 2 and 3 of Fig. 13.
[0521] In step 3, the MN may perform one or more of the following processes:
[0522] - The MN can provide the UE with a list of selected T-SNs.
[0523] - The MN can provide the UE with conditional information on when each T-SN can be selected. This information can be included as part of the Conditional PSCell Change (CPC) configuration.
[0524] - MN informs UE of 'K allocated to each T-SN' SN The UE can provide the SN Counter value(s) corresponding to the T-SN. Later, the UE can use this information to determine which T-SN was generated using which SN Counter value(s). SN It may be possible to determine whether (s) are in possession.
[0525] - The MN can inform the UE of the functions supported by each T-SN. For example, the MN can inform the UE of whether each T-SN is an SN that operates in the manner described in FIG. 3 or an SN that operates in the manner described in FIG. 13. (The above information can be transmitted in various ways. For example, the operating manner of a specific T-SN can be informed by the number of SN counter(s) assigned to the specific T-SN. That is, if the value of the SN counter assigned to a specific T-SN is one, the T-SN is an SN that operates in the manner described in FIG. 3, and if the value of the SN counter assigned to a specific T-SN is multiple, the T-SN can be an SN that operates in the manner described in FIG. 13. However, this is just one example, and the method by which the MN informs the UE of the operating manner of each T-SN is not limited to the above example.) This can be interpreted to mean the same as informing the UE of whether the T-SN is an SN that supports the selective SCG function. The above information may be included as part of the Conditional PSCell Change (CPC) configuration.
[0526] - The MN can provide the UE with policy information on whether or not the SN can be reused, operating in the manner described in FIG. 3. For a more detailed description, see FIG. 7.
[0527] In step 4, the UE can notify the MN that the task is complete.
[0528] In step 4a, the MN can inform the S-SN of the progress of the task. For example, the MN can inform the S-SN that the UE has received the CPC configuration.
[0529] The process of performing selective SCG will be explained below.
[0530] CASE1. The selected T-SN is based on Fig. 13 (i.e., the T-SN is the NEW version).
[0531] - Steps 5 to 9 disclosed in Fig. 14 can be performed.
[0532] CASE2. The selected T-SN is based on Figure 3 (i.e., the T-SN is the OLD version) and the non-reusable policy.
[0533] - The T-SN can be selected only once, and at this time, steps 6 to 10 disclosed in FIG. 4 can be performed.
[0534] CASE3. The selected T-SN is based on Figure 3 (i.e., the T-SN is the OLD version) & reusable policy.
[0535] - When the corresponding T-SN is initially selected, steps 6 to 10 disclosed in FIG. 4 may be performed.
[0536] - When the corresponding T-SN is re-selected, the following process may be performed. The UE may request the MN to connect to the corresponding T-SN. At this time, the UE may notify the MN of a series of information necessary to enable the MN to recognize that 'the corresponding T-SN operates based on Fig. 3 and has been re-selected'. For example, the UE may additionally notify the MN of 'the fact that the corresponding T-SN operates based on Fig. 3' and / or 'the fact that the corresponding T-SN has been re-selected'. If the MN already knows the above information, this notification may be omitted. In addition, one of the following processes may be additionally performed.
[0537] ■ Steps 1 to 8 of Fig. 3 can be performed.
[0538] The procedure for releasing the S-SN (steps 8 to 9 of FIG. 4) can be performed. It should be noted that the configuration diagrams, example diagrams of control / data signal transmission and reception methods, and example diagrams of operation procedures illustrated in FIGS. 1A to 15 are not intended to limit the scope of the embodiments of the present disclosure. That is, not all components, entities, or operation steps described in FIGS. 1A to 15 should be construed as essential components for carrying out the disclosure, and implementations may be made within a scope that does not harm the essence of the disclosure even if only some components are included.
[0539] The operations of the embodiments described above can be realized by providing a memory device storing the corresponding program code in any component within the device. That is, the control unit within the device can execute the operations described above by reading and executing the program code stored in the memory device through a processor or a CPU (Central Processing Unit).
[0540] The various components and modules of the entity or terminal device described in the present disclosure may be operated using hardware circuits, such as logic circuits based on complementary metal oxide semiconductors, firmware, software, and / or hardware and firmware and / or software embedded in a machine-readable medium. For example, various electrical structures and methods may be implemented using electrical circuits such as transistors, logic gates, and application-specific semiconductors.
[0541] The methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.
[0542] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to embodiments described in the claims or specification of the present disclosure.
[0543] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage devices, compact disc-ROMs (CD-ROMs), digital versatile discs (DVDs) or other forms of optical storage devices, magnetic cassettes, or may be stored in memories formed by a combination of some or all of these. In addition, each configuration memory may include multiple copies.
[0544] Additionally, the program may be stored on an attachable storage device that is accessible via a communication network, such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device implementing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device implementing an embodiment of the present disclosure.
[0545] In the specific embodiments of the present disclosure described above, components included in the disclosure are expressed singularly or plurally, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in plural may be composed of singular elements, or components expressed in singular may be composed of plural elements.
[0546] While the detailed description of this disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the described embodiments, but should be defined not only by the scope of the claims described below, but also by equivalents thereof.
Claims
1. In a wireless communication system, a method for operating an MN (Master Node) connected to a user terminal, A step of selecting a first SN counter value for a first target SN (Secondary Node) that does not support an optional SCG (Secondary Cell Group) function; A step of generating a first key value for secure communication between the user terminal and the first target SN based on the first SN counter value; A step of transmitting a first key value corresponding to the first target SN to the first target SN; A step of selecting a plurality of second SN counter values for a second target SN supporting optional SCG functionality; A step of generating a plurality of second key values for secure communication between the user terminal and the second target SN based on the plurality of second SN counter values; A step of transmitting a plurality of second key values corresponding to the second target SN to the second target SN; and A method comprising the step of transmitting, to the user terminal, CPC (Conditional PSCell Change) setting information, the first SN counter value, and the plurality of second SN counter values.
2. In paragraph 1, A step of receiving information on whether the first target SN supports the optional SCG function; and A method further comprising the step of receiving information on whether the second target SN supports the optional SCG function.
3. In paragraph 1, A method wherein the CPC setting information includes information on whether the first target SN or the second target SN supports the optional SCG function.
4. In paragraph 1, A method further comprising the step of receiving, from the first target SN or the second target SN, a rejection message for a key value received by the first target SN or the second target SN or a request message for an additional key value.
5. In paragraph 1, A method further comprising the step of transmitting information on whether the first target SN that does not support the optional SCG function is reusable to the user terminal.
6. In paragraph 5, A step of receiving a request for reuse of the first target SN from the user terminal when reuse of the first target SN is possible; A step of selecting a third SN counter value for the first target SN and generating a third key value based on the selected third SN counter value; a step of transmitting the third key value to the first target SN; and A method further comprising the step of transmitting the third SN counter value corresponding to the third key value to the user terminal.
7. In a method of operating a user terminal in a wireless communication system, A step of receiving, from a Master Node (MN) connected to the user terminal, CPC (Conditional PSCell Change) setting information, a first SN counter value corresponding to a first key value transmitted to a first target SN (Secondary Node) that does not support an optional SCG (Secondary Cell Group) function, and a plurality of second SN counters corresponding to a plurality of second key values transmitted to a second target SN that supports the optional SCG function; generating a first key value or a second key value based on at least one of the first SN counter value or the plurality of second SN counter values; and A method comprising the step of performing an SN change to a first target SN through the first key value or an SN change to a second target SN through the second key value.
8. In paragraph 7, The above CPC setting information includes information on whether the first target SN or the second target SN supports the optional SCG function. A method characterized in that the replacement with the second target SN can be performed multiple times using a plurality of second key values generated based on the CPC setting information.
9. In a wireless communication system, in a MN (Master Node) that is connected to a user terminal and operates, Department of Communications; and Includes a control unit, The above control unit, Select the first SN counter value for the first target SN (Secondary Node) that does not support the optional SCG (Secondary Cell Group) feature, Generate a first key value for secure communication between the user terminal and the first target SN based on the first SN counter value, To the first target SN, transmit a first key value corresponding to the first target SN, Select multiple second SN counter values for the second target SN supporting the optional SCG feature, Based on the plurality of second SN counter values, a plurality of second key values are generated for secure communication between the user terminal and the second target SN, To the second target SN, a plurality of second key values corresponding to the second target SN are transmitted, An MN configured to transmit CPC (Conditional PSCell Change) setting information, the first SN counter value and the plurality of second SN counter values to the user terminal.
10. In paragraph 9, The above control unit, Receive information from the first target SN about whether the first target SN supports the optional SCG function, An MN further configured to receive information from the second target SN on whether the second target SN supports the optional SCG function.
11. In paragraph 9, The above CPC setting information includes information on whether the first target SN or the second target SN supports the optional SCG function.
12. In paragraph 8, The above control unit, An MN further configured to receive, from the first target SN or the second target SN, a rejection message for a key value received by the first target SN or the second target SN, or a request message for an additional key value.
13. In paragraph 8, The above control unit, An MN further configured to transmit information on whether the first target SN that does not support the optional SCG feature is reusable to the user terminal.
14. In paragraph 13, The above control unit, If the reuse of the first target SN is possible, a request for reuse of the first target SN is received from the user terminal, Select a third SN counter value for the first target SN, and generate a third key value based on the selected third SN counter value. Transmit the third key value to the first target SN, The MN is further configured to transmit the third SN counter value corresponding to the third key value to the user terminal.
15. In a user terminal operating in a wireless communication system, Department of Communications; and Includes a control unit, The above control unit, Receive, from a MN (Master Node) connected to the user terminal, CPC (Conditional PSCell Change) setting information, a first SN counter value corresponding to a first key value transmitted to a first target SN (Secondary Node) that does not support an optional SCG (Secondary Cell Group) function, and a plurality of second SN counters corresponding to a plurality of second key values transmitted to a second target SN that supports the optional SCG function. Generate a first key value or a second key value based on at least one of the first SN counter value or the plurality of second SN counter values, A user terminal configured to perform an SN change to a first target SN through the first key value or an SN change to a second target SN through the second key value.
Citation Information
Patent Citations
Methods and apparatuses for a SCG deactivation mechanism and a SCG activation mechanism in a mr-DC scenario
WO2022082584A1
