Communication method and corresponding apparatus

MYPI2025006575A0Undetermined Publication Date: 2024-10-26HUAWEI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
MYPI2025006575
Authority / Receiving Office
MY · MY
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-04-26
Filing Date
2024-04-26
Publication Date
2024-10-26

AI Technical Summary

Technical Problem

In the prior art, when the communication device switches between slave nodes, the input parameters of the communication data may be exactly the same, which poses a security risk.

Method used

By allocating at least two different DRB IDs to each candidate cell, the communication device can use different DRB IDs to securely protect the transmitted data when accessing the same cell at different times, ensuring different input parameters and improving communication security.

Benefits of technology

It effectively improves the secure connection between the communication device and the slave node, prevents data leakage and tampering, and enhances communication security performance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure PI2025006575_DRAWING_001
    Figure PI2025006575_DRAWING_001
  • Figure PI2025006575_DRAWING_002
    Figure PI2025006575_DRAWING_002
  • Figure PI2025006575_DRAWING_003
    Figure PI2025006575_DRAWING_003
Patent Text Reader

Abstract

This application provides a communication method and a communication apparatus, to improve communication security between the communication apparatus and a secondary node. The method includes: A reconfiguration message received by the communication apparatus from a network side includes configuration information of at least two candidate cells, and the at least two candidate cells include a first candidate cell and a second candidate cell. When accessing the first candidate cell, the communication apparatus selects an unused DRB ID from a plurality of DRB IDs carried in the configuration information of the first candidate cell, to protect communication data transmitted between the communication apparatus and the first candidate cell through a first DRB.
Need to check novelty before this filing date? Find Prior Art

Description

A communication method and corresponding device

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on April 26, 2023, with application number 202310474589.8 and application name “A communication method and corresponding device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of communication technology, and in particular to a communication method and corresponding device. Background Art

[0004] With the development of communication technology, some communication devices, such as mobile phones, can support dual-connection communication mode. Among them, dual connection is a mode in which the communication device is in a radio resource control (RRC) connection state. The communication device in dual connection can communicate not only with the master node (MN), but also with the secondary node (SN). The applicant found in the study that according to the prior art, when the communication device switches between cells in one or more slave nodes, it may cause the input parameters used to protect the communication data between the communication device and the cell to be exactly the same, thereby causing certain security risks in the communication between the communication device and the slave node.

[0005] Therefore, how to establish a secure connection between a communication device and a SN and improve the security performance between the communication device and the SN is a technical problem that needs to be solved urgently.

[0006] Summary of the Invention

[0007] The present application provides a communication method and corresponding device, which can improve the communication security between the communication device and the connected slave node.

[0008] To achieve the above objectives, this application adopts the following technical solutions:

[0009] In a first aspect, a communication method is provided, the method comprising: the communication device receives an RRC reconfiguration message, the RRC reconfiguration message including configuration information of at least two candidate cells, wherein the at least two candidate cells include a first candidate cell and a second candidate cell. The configuration information of the first candidate cell includes a first count value and a first identification list corresponding to a first data radio bearer DRB, the first identification list including at least 2 DRB identification IDs for characterizing the first DRB. The configuration information of the second candidate cell includes a second identification list corresponding to a second count value and a second DRB, the second identification list including at least 2 DRB IDs for characterizing the second DRB. In the case of accessing the first candidate cell, the communication device protects the communication data transmitted between the communication device and the first candidate cell using the first DRB according to a first root key and a first DRB ID in the first identification list, wherein the first root key is generated by the communication device according to the first count value.

[0010] It is understood that in the present application, the communication device described in the first aspect and the following aspects can be a terminal device (such as a mobile phone), or a chip (system) that can be set in the terminal device. In other words, the communication method described in the first aspect can be executed by the terminal device, or by the chip (system) in the terminal device.

[0011] By allocating at least two different DRB IDs to the DRB corresponding to the same candidate cell, when the communication device accesses the same candidate cell at different times, different DRB IDs can be used to securely protect the transmitted data when using the DRB to transmit data. The security protection may include encryption protection and / or integrity protection. For example, when the security protection is encryption, different key streams can be generated according to different DRB IDs.

[0012] In one possible implementation, the configuration information of the first candidate cell includes a first identification list corresponding to multiple DRBs, and the first identification list includes at least 2 DRB IDs for representing each DRB in the multiple DRBs. It can be understood that the first identification list corresponds to the multiple DRBs.

[0013] In one possible implementation, before the communication device protects the communication data transmitted using the first DRB between the communication device and the first candidate cell based on the first root key and the first DRB ID in the first identification list, the method further includes: the communication device selects the first DRB ID from the first identification list. Selecting the first DRB ID can also be understood as the communication device obtaining the first DRB ID from the first identification list. The rule for the communication device to select or obtain the DRB ID may be a preconfigured rule, such as replacing it in order from small to large or replacing it according to the front and back relationship of the DRB ID in the message. In one possible implementation, the first identification list includes a default DRB ID and at least one candidate DRB ID, wherein the default DRB ID is the initial DRB ID of the DRB; or the first identification list includes at least two candidate DRB IDs.

[0014] In one possible implementation, the first DRB ID is an unused DRB ID in the first identification list. By using an unused DRB ID in the first identification list, it is ensured that at least one DRB ID among the multiple input parameter values ​​used to protect communication data is different.

[0015] In one possible implementation, the communication device deletes the first DRB ID or marks the first DRB ID as used. When the communication device leaves the first candidate cell, by deleting or marking the used DRB ID in the first candidate cell, it is ensured that when accessing the first candidate cell again, the communication device can use a different DRB ID to securely protect the transmitted communication data.

[0016] In one possible implementation, the configuration of the first candidate cell also includes a first execution condition corresponding to the first candidate cell, and the configuration of the second candidate cell includes a second execution condition corresponding to the second candidate cell. If the first execution condition is met, the communication device accesses the first candidate cell. Alternatively, if the second execution condition is met, the communication device accesses the second candidate cell.

[0017] In one possible implementation, when the communication device leaves the first candidate cell and accesses the second candidate cell, the communication device protects the communication data transmitted between the communication device and the second candidate cell using the second DRB according to the second root key and the second DRB ID in the second identification list, wherein the second root key is generated by the communication device according to the second count value. By making the first count value corresponding to the first candidate cell and the second count value corresponding to the second candidate cell different, it is ensured that the first root key of the first candidate cell and the second root key of the second candidate cell are different, thereby ensuring that at least one security input parameter value generated according to the second root key for protecting the communication data is different.

[0018] In one possible implementation, when leaving the second candidate cell and accessing the first candidate cell again, the communication device protects the communication data transmitted between the communication device and the first candidate cell using the first DRB according to the first root key and the third DRB ID in the first identification list, wherein the third DRB ID is different from the first DRB ID. When the communication device accesses the first candidate cell again, the communication device uses a DRB ID different from the one used for the previous access to the first candidate cell as an input parameter to securely protect the communication data transmitted between itself and the first candidate cell, thereby ensuring that when the communication device accesses the first candidate cell successively, at least one of the input parameters used to securely protect the communication data is different. It should be noted that leaving the second candidate cell and accessing the first candidate cell again may be accessing other candidate cells first after leaving the second candidate cell, then leaving the other candidate cells, and then accessing the first candidate cell again. In one possible implementation, before the communication device protects the communication data transmitted using the second DRB between the communication device and the second candidate cell based on the second root key and the second DRB ID in the second identification list, the method also includes: the communication device selects the second DRB ID from the second identification list.

[0019] In one possible implementation, the second DRB ID is a DRB ID that has not been used in the second identification list.

[0020] In one possible implementation, the communication device deletes the second DRB ID or marks the second DRB ID as used. In this way, if the communication device switches to the same candidate cell again, it can know which DRB IDs are not used, so that the communication device can use different DRB IDs when accessing the same candidate cell, thereby improving the security of communication.

[0021] In a possible implementation, the first count value and the second count value are different.

[0022] In one possible implementation, the first count value and the second count value are the same, and the DRB ID in the first identification list and the DRB ID in the second identification list are different from each other.

[0023] In a second aspect, a communication method is provided, which includes: a master node receives a first identification list corresponding to a first data radio bearer DRB corresponding to a first candidate cell and a second identification list corresponding to a second DRB corresponding to a second candidate cell; the first identification list includes at least 2 DRB identification IDs for characterizing the first DRB. The second identification list includes at least 2 DRB IDs for characterizing the second DRB; and an RRC reconfiguration message is sent to a communication device, the RRC reconfiguration message including configuration information of the first candidate cell and configuration information of the second candidate cell. The configuration information of the first candidate cell includes a first count value and the first identification list. The configuration information of the second candidate cell includes a second count value and the second identification list. The first count value is used to generate a first root key shared between the communication device and the first candidate cell. The second count value is used to generate a second root key shared between the communication device and the second candidate cell.

[0024] By allocating at least two different DRB IDs to the DRB corresponding to the same candidate cell, when the communication device accesses the same candidate cell at different times, different DRB IDs can be used to securely protect the transmitted data when using the DRB to transmit data. The security protection can include encryption protection and / or integrity protection. For example, when the security protection is encryption, different key streams can be generated according to different DRB IDs.

[0025] In one possible implementation, the master node receives a first identifier list corresponding to a first data radio bearer DRB corresponding to a first candidate cell and a second identifier list corresponding to a second DRB corresponding to a second candidate cell, including: receiving the first identifier list from a first slave node, and receiving the second identifier list from a second slave node, wherein the first slave node is different from the second slave node.

[0026] In a possible implementation, the master node sends the first root key to the first slave node, and sends the second root key to the second slave node.

[0027] In one possible implementation, the master node receives a first identifier list corresponding to a first data radio bearer DRB corresponding to a first candidate cell and a second identifier list corresponding to a second DRB corresponding to a second candidate cell, including: receiving the first identifier list and the second identifier list from a third slave node.

[0028] In a possible implementation, the first root key and the second root key are sent to the third slave node.

[0029] In a possible implementation, the first count value is different from the second count value.

[0030] In one possible implementation, the first count value is the same as the second count value, and the DRB ID in the first identification list is different from the DRB ID in the second identification list.

[0031] In a possible implementation manner, the first root key and / or the second root key is sent to the third slave node.

[0032] According to a third aspect, a communication method is provided, wherein a slave node receives a slave node addition request message from a master node; generates a first identification list corresponding to a first data radio bearer DRB corresponding to a first candidate cell; the first identification list includes at least 2 DRB IDs for characterizing the first DRB; and in response to the slave node addition request message, sends a slave node addition request confirmation message to the master node, wherein the slave node addition request confirmation message includes the first identification list.

[0033] By allocating at least two different DRB IDs to the DRB corresponding to the same candidate cell, when the communication device accesses the same candidate cell at different times, different DRB IDs can be used to securely protect the data transmitted using the DRB. This security protection can include encryption protection and / or integrity protection. Exemplarily, when the security protection is encryption, different key streams can be generated based on different DRB IDs.

[0034] In one possible implementation, the slave node further generates a second identifier list corresponding to a second data radio bearer (DRB) of the second candidate cell. The second identifier list is used to represent at least two DRB IDs of the second DRB. In response to the slave node addition request message, the slave node sends a slave node addition request confirmation message to the master node, where the slave node addition request confirmation message includes the second identifier list.

[0035] In one possible implementation, the slave node generates a first identifier list corresponding to the first data radio bearer DRB corresponding to the first candidate cell and a second identifier list corresponding to the second DRB corresponding to the second candidate cell, including: the first slave node generates the first identifier list, and the second slave node generates the second identifier list, wherein the first slave node is different from the second slave node.

[0036] In one possible implementation, the slave node receives a first root key from the master node, and protects communication data transmitted between the communication device and the first candidate cell using the first DRB based on the first root key and the first DRB ID in the first identification list. The first DRB ID is a DRB ID that has not been used in the first identification list. By using an unused DRB ID in the first identification list, it is ensured that at least one DRB ID among multiple input parameter values ​​used to protect communication data is different.

[0037] In one possible approach, the slave node deletes the first DRB ID or marks the first DRB ID as used. In this way, if the communication device switches to the same candidate cell under the slave node again, by deleting or marking the used DRB ID in the same candidate cell, it is ensured that when accessing the candidate cell again, the slave node can use a different DRB ID to securely protect the transmitted communication data.

[0038] In one possible implementation, generating a first identifier list corresponding to the first data radio bearer DRB corresponding to the first candidate cell and a second identifier list corresponding to the second DRB corresponding to the second candidate cell includes: a third slave node generating the first identifier list and the second identifier list.

[0039] In a possible implementation manner, the third slave node receives a first root key corresponding to the first candidate cell and a second root key corresponding to the second candidate cell from the master node.

[0040] In a fourth aspect, a communication method is provided, the method comprising: a master node sends a slave node addition request message to a slave node. The slave node generates a first identifier list corresponding to the first data radio bearer DRB corresponding to the first candidate cell; the first identifier list includes at least 2 DRB identifier IDs for characterizing the first DRB; and in response to the slave node addition request message, the slave node sends a slave node addition request confirmation message to the master node, and the slave node addition request confirmation message includes the first identifier list. The master node receives the first identifier list and sends an RRC reconfiguration message to the communication device, the RRC reconfiguration message including the configuration information of the first candidate cell. The configuration information of the first candidate cell includes a first count value and the first identifier list. The first count value is used to generate a first root key shared between the communication device and the first candidate cell.

[0041] In the communication method provided in the fourth aspect, the relevant beneficial effects can be referred to the relevant contents of the second and third aspects above, which will not be repeated here.

[0042] In one possible implementation, the master node receives the first identifier list, including: the first slave node sends a slave node add request confirmation message to the master node in response to the slave node add request message, wherein the slave node add request confirmation message includes the first identifier list. The master node receives the first identifier list from the first slave node.

[0043] In one possible implementation, the master node sends a first root key to the first slave node. The first slave node receives the first root key from the master node. The first slave node protects the communication data transmitted using the first DRB between the communication device and the first candidate cell based on the first root key and the first DRB ID in the first identification list; wherein the first DRB ID is a DRB ID that has not been used in the first identification list. By using an unused DRB ID in the first identification list, it is ensured that at least one DRB ID among the multiple input parameter values ​​used to protect the communication data is different.

[0044] In one possible implementation, the slave node deletes the first DRB ID or marks the first DRB ID as used. In this way, if the communication device switches to the same candidate cell under the slave node again, by deleting or marking the used DRB ID in the same candidate cell, it is ensured that when the communication device accesses the candidate cell again, the slave node can use a different DRB ID to securely protect the transmitted communication data.

[0045] In one possible implementation, the slave node determines at least two candidate cells, where the at least two candidate cells include a first candidate cell and a second candidate cell, generates a first identifier list corresponding to a first data radio bearer (DRB) corresponding to the first candidate cell, and further includes the slave node generating a second identifier list corresponding to a second DRB corresponding to the second candidate cell. The second identifier list includes at least two DRB IDs used to represent the second DRB. In response to the slave node addition request message, the slave node sends a slave node addition request confirmation message to the master node, the slave node adding the request confirmation message including the second identifier list. The master node receives the second identifier list and sends an RRC reconfiguration message to the communication device, the RRC reconfiguration message including configuration information of the second candidate cell, a second count value, and the second identifier list. The second count value is used to generate a second root key shared between the communication device and the second candidate cell. In a fifth aspect, a communication device is provided. The communication device includes: a module for executing any of the communication methods described above, such as a transceiver module and a processing module. The transceiver module is configured to execute corresponding message transmission and reception actions, and the processing module can be configured to execute all actions except information transmission and reception.

[0046] Optionally, the communication device described in the fifth aspect may further include a storage module, wherein the storage module stores a program or instruction. When the processing module executes the program or instruction, the communication device can execute any communication method executed by the terminal device described above.

[0047] In a sixth aspect, a network device is provided. The network device includes a module for executing any of the communication methods described above, such as a transceiver module and a processing module. The transceiver module is configured to execute corresponding message sending and receiving actions, and the processing module can be configured to execute all actions except sending and receiving messages.

[0048] Optionally, the network device described in the sixth aspect may further include a storage module, wherein the storage module stores a program or instruction. When the processing module executes the program or instruction, the communication device may execute any communication method executed by the network device described above.

[0049] In a seventh aspect, a communication device is provided, comprising: a processor configured to execute instructions stored in a memory, so that the communication device performs any communication method described above by the terminal device.

[0050] In a possible design solution, the communication device may further include the memory. The memory may be integrated with the processor or provided separately.

[0051] In an eighth aspect, a network device is provided, comprising: a processor configured to execute instructions stored in a memory, so as to enable the communication apparatus to perform any communication method described above.

[0052] In a ninth aspect, a computer-readable storage medium is provided, comprising: a computer program or instructions; when the computer program or instructions are run on a computer, the computer is caused to execute the communication method described in any one of the possible implementations above.

[0053] In a tenth aspect, a computer program product is provided, comprising a computer program or instructions, which, when executed on a computer, enables the computer to execute the communication method described in any one of the possible implementations described above.

[0054] In the above scheme, the reconfiguration message received by the communication device from the network side includes configuration information of at least two candidate cells, wherein the at least two candidate cells include a first candidate cell and a second candidate cell, and the configuration information includes at least two DRB IDs corresponding to the first DRB. Thus, when accessing the first candidate cell, the communication device can select an unused DRB ID from the multiple DRB IDs carried in the configuration information of the first candidate cell. Security protection is performed on the first DRB using different DRB IDs, thereby protecting the communication data transmitted between the communication device and the first candidate cell using the first DRB. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] FIG1 shows an architecture diagram of a communication system applicable to the present application.

[0056] FIG2 shows a schematic diagram of SCG selective activation.

[0057] FIG3 is a schematic diagram of a CPA process provided in an embodiment of the present application.

[0058] FIG4 is a CPC process diagram provided in an embodiment of the present application.

[0059] FIG5 is a schematic diagram of a security establishment process between a UE and a SN provided in an embodiment of the present application.

[0060] FIG6 is a schematic diagram of a communication method provided in an embodiment of the present application.

[0061] FIG7 is an exemplary flowchart of a communication method 700 provided in an embodiment of the present application.

[0062] FIG8 is an exemplary flowchart of a communication method 800 provided in an embodiment of the present application.

[0063] FIG9 is an exemplary flowchart of a communication method 900 provided in an embodiment of the present application.

[0064] FIG10 is a schematic structural diagram of a device provided in an embodiment of the present application.

[0065] FIG11 is a schematic structural diagram of another device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0066] To make the objectives, technical solutions, and advantages of this application more clear, the present application will be further described in detail below with reference to the accompanying drawings. The specific operating methods in the method embodiments can also be applied to the device embodiments or system embodiments. In the description of this application, unless otherwise specified, the meaning of "multiple" is two or more.

[0067] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0068] It is understood that the various numbers used in this application are merely for ease of description and are not intended to limit the scope of this application. The order of execution of the above-mentioned processes does not necessarily imply a specific order of execution. The order of execution of each process should be determined by its function and inherent logic.

[0069] The terms "first," "second," "third," "fourth," and various other terminology designations, if any, in the specification and claims of this application and in the accompanying drawings are used to distinguish similar objects and are not necessarily used to describe a particular order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate so that the embodiments described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "including" and "having," and any variations thereof, are intended to cover non-exclusive inclusions, e.g., a process, method, system, product, or apparatus comprising a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0070] The technical solutions provided in this application can be applied to various communication systems, such as: fifth generation (5G) or new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, etc. The technical solutions provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system. The technical solutions provided in this application can also be applied to device to device (D2D) communication, vehicle-to-everything (V2X) communication, machine to machine (M2M) communication, machine type communication (MTC), and Internet of Things (IoT) communication systems or other communication systems.

[0071] The following will illustrate a 5G system applicable to the embodiments of the present application with reference to Figure 1(a) and Figure 1(b). It should be understood that the 5G system described herein is merely an example and does not limit the present application in any way.

[0072] It should also be understood that certain network elements in the 5G system can communicate using a service-oriented interface or a point-to-point interface. The following introduces the 5G system framework based on a point-to-point interface and the 5G system framework based on a service-oriented interface in conjunction with (a) in Figure 1 and (b) in Figure 1, respectively.

[0073] As an exemplary illustration, FIG1(a) shows a schematic diagram of the architecture of a 5G system 200a to which an embodiment of the present application is applicable. FIG1(a) is a schematic diagram of a 5G network architecture based on a point-to-point interface. As shown in FIG1(a), the network architecture may include but is not limited to the following network elements (or referred to as functional network elements, functional entities, nodes, devices, etc.):

[0074] (Radio) access network equipment (radio access network, (R)AN), access and mobility management function (AMF) network element, session management function (SMF) network element, user plane function (UPF) network element, policy control function (PCF) network element, unified data management (UDM) network element, AF network element, data network (DN), network slice selection function (NSSF), authentication server function (AUSF), unified data management (UDM), BSF network element, unified data repository (UDR), etc.

[0075] The following is a brief introduction to the network elements shown in (a) of Figure 1:

[0076] 1. User equipment (UE): This term may also be referred to as terminal equipment, terminal device, access terminal, subscriber unit, subscriber station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, communication device, user agent, or user device. UE is a device that provides voice / data connectivity to a user, such as a handheld device or vehicle-mounted device with wireless connectivity. At present, some examples of terminals may include: mobile phones, tablet computers, computers with wireless transceiver functions (such as laptops, PDAs, etc.), mobile internet devices (MIDs), virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication functions, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in 5G networks or future evolved public land mobile communication networks (PLMNs). For the convenience of expression, this application will take UE as an example to describe the relevant solutions.

[0077] Furthermore, user devices can also be terminal devices in the Internet of Things (IoT) system. IoT is a crucial component of future information technology development. Its primary technical feature is connecting objects to the Internet through communications, thereby enabling intelligent networks that interconnect humans and machines, and objects and things. IoT technology, for example, utilizes narrowband (NB) technology to achieve massive connectivity, deep coverage, and power-saving terminals.

[0078] In addition, user devices can also include smart printers, train detectors, etc. Their main functions include collecting data (part of the terminal equipment), receiving control information and downlink data from network equipment, and sending electromagnetic waves to transmit uplink data to network equipment.

[0079] It should be understood that the user equipment may be any device that can access a network. The user equipment and the access network device may communicate with each other using a certain air interface technology.

[0080] 2. (Radio) access network (R)AN) equipment: used to provide network access for authorized user devices in a specific area, and can use transmission tunnels with different service qualities based on the level of user devices and business requirements.

[0081] (R)AN can manage wireless resources, provide access services to user equipment, and forward control signals and user equipment data between the user equipment and the core network. (R)AN can also be understood as a base station in a traditional network.

[0082] Exemplarily, the access network device in the embodiment of the present application may be any communication device with wireless transceiver functions for communicating with a user equipment. The access network device includes but is not limited to an evolved Node B (eNB) or a gNB in ​​a 5G, such as an NR, system, or a transmission point (TRP or TP), one or a group (including multiple antenna panels) of antenna panels of a base station in a 5G system, or a network node constituting a gNB or a transmission point, such as a baseband unit (BBU), or a distributed unit (DU).

[0083] In some deployments, a gNB may include a centralized unit (CU) and a DU. The gNB may also include an active antenna unit (AAU). The CU implements some gNB functions, while the DU implements some gNB functions. For example, the CU is responsible for processing non-real-time protocols and services, implementing the functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers. The DU is responsible for processing physical layer protocols and real-time services, implementing the functions of the radio link control (RLC), media access control (MAC), and physical (PHY) layers. The AAU implements some physical layer processing functions, RF processing, and active antenna-related functions. Because RRC layer information ultimately becomes PHY layer information, or is converted from PHY layer information, in this architecture, higher-layer signaling, such as RRC layer signaling, can also be considered to be sent by the DU, or by both the DU and the AAU. It is understood that an access network device can be a device that includes one or more of a CU node, a DU node, or an AAU node. In addition, the CU may be classified as an access network device in an access network (radio access network, RAN), or the CU may be classified as an access network device in a core network (core network, CN), which is not limited in this application.

[0084] 3. User plane function (UPF) network element: used for packet routing and forwarding, as well as quality of service (QoS) processing of user plane data.

[0085] In a 5G communication system, the user plane network element may be a user plane function (UPF) network element. In future communication systems, the user plane network element may still be a UPF network element, or may have other names, which are not limited in this application.

[0086] 4. Access and mobility management function (AMF) network element: The access and mobility management function network element is mainly used for mobility management and access management. It can be used to implement other functions of MME in addition to session management, such as access authorization / authentication.

[0087] In future communication systems, the access and mobility management device may still be AMF, or may have other names, which is not limited in this application.

[0088] 5. Session management function (SMF) network element: mainly used for session management, Internet protocol (IP) address allocation and management of user equipment, selection of endpoints for manageable user plane functions, policy control and charging function interfaces, and downlink data notification.

[0089] In future communication systems, the session management network element may still be an SMF network element, or may have other names, which is not limited in this application.

[0090] 6. Policy control function (PCF) network element: A unified policy framework used to guide network behavior and provide policy rule information to control plane function network elements (such as AMF, SMF, etc.).

[0091] In future communication systems, the policy control network element may still be a PCF network element, or may have other names, which is not limited in this application.

[0092] 7. Application function (AF): used for data routing affected by applications, open functional network elements of wireless access networks, and interaction with the policy framework for policy control.

[0093] In future communication systems, the application network element may still be an AF network element, or may have other names, which is not limited in this application.

[0094] 8. Unified data management (UDM) network element: used to process UE identification, access authentication, registration, and mobility management.

[0095] In future communication systems, unified data management may still be a UDM network element, or it may have other names, which is not limited in this application.

[0096] 9. Authentication server function (AUSF) network element: used for authentication services, generating keys to achieve two-way authentication of user devices, and supporting a unified authentication framework.

[0097] In future communication systems, the authentication server function network element may still be an AUSF network element, or it may have other names, which is not limited in this application.

[0098] 10. Network Data Analytics Function (NWDAF) NE: This element is used to identify network slice instances and load information about their load levels. The NWDAF allows NF consumers to subscribe or unsubscribe to periodic notifications and notify consumers when thresholds are exceeded.

[0099] In future communication systems, the network data analysis function network element may still be an NWDAF network element, or may have other names, which is not limited in this application.

[0100] 11. Data Network (DN): A DN is a network located outside of a carrier network. A carrier network can access multiple DNs, and a variety of services can be deployed on the DN, providing data and / or voice services to terminal devices. For example, a DN is the private network of a smart factory. Sensors installed in the workshop of the smart factory can be terminal devices. The DN is equipped with a control server for the sensors, and the control server can provide services to the sensors. The sensors can communicate with the control server, obtain instructions from the control server, and transmit the collected sensor data to the control server according to the instructions. For another example, a DN is the internal office network of a company. The mobile phones or computers of the company's employees can be terminal devices, and the employees' mobile phones or computers can access information and data resources on the company's internal office network.

[0101] In FIG1(a), Nausf, Nnef, Npcf, Nudm, Naf, Namf, Nsmf, N1, N2, N3, N4, and N6 are interface sequence numbers. The meanings of these interface sequence numbers can be found in the 3GPP standard protocol and are not limited here.

[0102] In the network architecture shown in (a) of Figure 1, each network element can communicate with each other through the interfaces shown in the figure. As shown in the figure, the UE and AMF can interact through the N1 interface, and the interaction message can be called an N1 message. The RAN and AMF can interact through the N2 interface, and the N2 interface can be used for sending non-access stratum (NAS) messages, etc. The RAN and UPF can interact through the N3 interface, and the N3 interface can be used to transmit user plane data, etc. The SMF and UPF can interact through the N4 interface, and the N4 interface can be used to transmit information such as tunnel identification information of the N3 connection, data cache indication information, and downlink data notification messages. The UPF and DN can interact through the N6 interface, and the N6 interface can be used to transmit user plane data, etc. The relationship between other interfaces and each network element is shown in (a) of Figure 1. For the sake of brevity, they are not described in detail here.

[0103] As shown in Figure 1(b), this is a schematic diagram of a 5G network architecture based on a point-to-point interface. The functions of the network elements therein can be referred to the functions of the corresponding network elements in Figure 1(a), and will not be repeated here. The main difference between Figure 1(b) and Figure 1(a) is that the interfaces between the network elements in Figure 1(b) are point-to-point interfaces, rather than service-based interfaces.

[0104] In the architecture shown in Figure 1(b), the interface names and functions between the various network elements are as follows:

[0105] 1) N7: The interface between PCF and SMF, used to deliver protocol data unit (PDU) session granularity and service data flow granularity control policy.

[0106] 2) N15: Interface between PCF and AMF, used to deliver UE policies and access control related policies.

[0107] 3) N5: The interface between AF and PCF, used for issuing application service requests and reporting network events.

[0108] 4) N4: The interface between SMF and UPF is used to transfer information between the control plane and the user plane, including the control of the forwarding rules, QoS control rules, traffic statistics rules, etc. for the user plane and the reporting of information on the user plane.

[0109] 5) N11: The interface between SMF and AMF, used to transfer PDU session tunnel information between RAN and UPF, transfer control messages sent to UE, transfer radio resource control information sent to RAN, etc.

[0110] 6) N2: The interface between AMF and RAN, used to transmit radio bearer control information from the core network side to the RAN.

[0111] 7) N1: The interface between AMF and UE, access-independent, used to deliver QoS control rules to the UE.

[0112] 8) N8: Interface between AMF and UDM, used by AMF to obtain access and mobility management related subscription data and authentication data from UDM, and AMF to register UE current mobility management related information with UDM.

[0113] 9) N10: Interface between SMF and UDM, used by SMF to obtain session management-related subscription data from UDM, and for SMF to register UE current session-related information with UDM.

[0114] 10) N35: Interface between UDM and UDR, used by UDM to obtain user contract data information from UDR.

[0115] 11) N36: Interface between PCF and UDR, used by PCF to obtain policy-related contract data and application data-related information from UDR.

[0116] 12) N12: Interface between AMF and AUSF, used by AMF to initiate the authentication process to AUSF, which can carry SUCI as the contract identifier;

[0117] 13) N13: Interface between UDM and AUSF, used by AUSF to obtain the user authentication vector from UDM to execute the authentication process.

[0118] As an example, Figure 1(c) shows an architectural diagram of a dual connectivity (DC) communication system 100c applicable to the present application. Dual connectivity can also be referred to as multi-radio dual connectivity (MR-DC). Generally, a dual connectivity communication system supports the simultaneous deployment of two wireless access systems, allowing devices to communicate with each other based on these two wireless access systems, so as to improve wireless resource utilization, reduce system switching delay, and improve user and system performance.

[0119] It is understandable that Figure 1 (a) and Figure 1 (b) are illustrated using a 5G communication system as an example, but the present application is not limited to this. For example, the wireless access system in the above-mentioned communication system 100c may include but is not limited to the following systems: long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), universal mobile telecommunication system (UMTS), fifth generation (5G) system or new radio (NR) or future evolved communication system (such as sixth generation (6G) system), etc. Exemplarily, two identical communication systems can be deployed simultaneously in a dual-connection communication system, or two different communication systems can be deployed, such as deploying a long term evolution (LTE) system and a new radio (NR) system at the same time, but the embodiments of the present application are not limited to this.

[0120] As shown in (c) of Figure 1, the communication system 100c may include: one or more terminal devices 101, a master node (MN) 102, a secondary node (SN) 103, one or more other potential slave nodes (other potential SN) 104, and a core network 105, wherein the master node 102 and the slave node 103 (or slave node 104) may correspond to the same or different wireless access systems.

[0121] It is understood that the master node and the slave node in the communication system 100c are both network devices. The master node 102 may be the network device used when the terminal device 101 initially accesses the network, responsible for radio resource control (RRC) communication with the terminal device 101, and the slave node 203 may be added during RRC reconfiguration to provide additional radio resources.

[0122] Among them, the terminal device 101 establishes connections with the master node 102 and the slave node 103 respectively, that is, the terminal device 101 can support simultaneous access to two different nodes. In addition, the terminal device 101 can also switch from the slave node 103 to any other potential slave node 104; the master node 102 and the slave node 103 can establish connections with the core network 105. For example, the master node 102 can transmit control information or user data to the core network 105 via a backhaul interface (such as the N2 interface), and the slave node 103 can transmit user data to the core network 105 via a backhaul interface (such as the S1 interface); the master node 102 and the slave nodes (including the slave node 103 and other potential slave nodes 204) can also communicate.

[0123] The core network 105 may refer to the core network of any communication system. Taking the 5G communication system as an example, the core network 205 includes multiple network function (NF) entity network elements. For a specific description, please refer to the corresponding description of Figure 1 (a) and Figure 1 (b), and will not be described in detail here.

[0124] Since the terminal device 101 can simultaneously receive services from multiple cells of a node under a node, the service cell group provided by the master node 102 for the terminal device 101 can be called a master cell group (MCG), and the service cell group provided by the slave node 103 for the terminal device 101 can be called a secondary cell group (SCG). The MCG and SCG each contain at least one cell. There is a primary cell (PCell) in the master node 102, and a primary SCG cell (PSCell) (or primary and secondary cells) in the slave node 103.

[0125] To facilitate understanding of the embodiments of the present application, some of the terms involved in this application are exemplified below. It is understandable that the terms given below are explained using the current NR system as an example, but it should be understood that in other communication systems (such as future sixth-generation communication systems), the following terms may have other names, and this application does not limit this.

[0126] 1. CPAC

[0127] Due to the mobility of a terminal device, a PSCell change may be triggered, i.e., the terminal device may switch from one PSCell to another. It should be understood that a PSCell change may occur when the terminal device switches from one slave node's cell to another, or from one cell of a slave node to another cell of the same slave node. Furthermore, the PSCell change may be triggered by either the master node or a slave node.

[0128] In order to enable terminal devices to quickly add or modify PScells, a conditional PSCell addition / change (CPAC) mechanism is introduced. CPAC includes conditional PSCell addition (CPA) and conditional PSCell change (CPC). Both CPA and CPC are for adding or changing the primary SCG cell (PSCell) of the secondary station in the DC scenario. The main idea is that the network configures multiple candidate PSCell cells, and each candidate PSCell cell configuration includes the configuration of the candidate cell and the corresponding execution conditions. When the UE evaluates that the execution conditions of a candidate cell are met, the UE can execute the addition or change of the PSCell.

[0129] Exemplarily, one implementation method of CPAC is as follows: the network side first configures multiple candidate PSCells, notifies the terminal device of the configurations of the multiple candidate PSCells and the execution conditions corresponding to each candidate PSCell, and subsequently when the terminal device determines that there is a candidate PSCell that meets its corresponding execution conditions, the terminal device can directly access the candidate PScell ​​that meets the execution conditions. In this way, the network side does not need to wait for the terminal device to report a measurement report before sending a new PSCell configuration to the terminal device, which can shorten the delay required to add or change the PSCell. For scenarios where the slave node triggers the change of the PSCell, it can avoid the inability to report the measurement report and send the reconfiguration message when the PSCell signal quality changes rapidly, thereby improving the robustness of the PSCell change.

[0130] The following first briefly introduces a CPA process provided by an embodiment of the present application in conjunction with the various steps in Figure 3. This process only shows the main steps, and the detailed process can be found in 3GPP TS37.340.

[0131] S301: Upon determining to configure CPA for a UE, the MN sends an SN Addition Request message to at least one candidate SN. This SN Addition Request message requests resource allocation from the candidate SN. The SN Addition Request message includes security parameters used to enable SRB3 establishment. As an example, the SNs shown in Figure 3 and other potential SNs are candidate SNs for the UE.

[0132] It is understandable that the present application does not limit the number of candidate SNs, that is, the MN may send an SN add request message to only one SN, or may send an add request message to two or more SNs, and the present application does not impose any limitation on this.

[0133] S302: After receiving the SN adding request message from the MN, the candidate SN sends an SN adding confirmation message to the MN after confirming that the resource request can be allowed.

[0134] Optionally, in S302a, the MN sends Xn user plane (Xn-U) address indication information to the candidate SN.

[0135] S303: The MN sends an RRC reconfiguration message to the UE, where the RRC reconfiguration message includes CPA configuration.

[0136] Exemplarily, a CPA configuration includes one or more candidate SCG configurations and execution conditions associated with each candidate SCG configuration. Each candidate SCG configuration includes an SN counter, meaning the conditional configuration corresponding to the SN includes an SN counter. The SN counter value is carried in the Sk counter information element.

[0137] For example, the CPA configuration information includes SCG configuration information of one or more candidate PSCells and execution conditions associated with the one or more SCG configuration information. It is understandable that each SCG configuration information corresponds to a PSCell, so each PSCell has a corresponding execution condition.

[0138] S304: After receiving the RRC reconfiguration message from the MN, the UE replies with an RRC reconfiguration complete message to the MN. The UE uses other RRC configurations in the RRC reconfiguration message except the CPA configuration.

[0139] S304a: The UE begins evaluating the execution conditions associated with the SCG configuration information. If the execution conditions for a candidate PSCell are met, the UE uses the configuration of the candidate PSCell selected in the RRC reconfiguration message (the configuration associated with the execution conditions) and sends an RRC reconfiguration complete message to the mobile node. The RRC reconfiguration complete message includes the RRC reconfiguration complete message for the selected candidate PSCell and information enabling the mobile node to identify the selected candidate PSCell.

[0140] S305a, the MN sends an SN reconfiguration completion message to the SN, where the SN reconfiguration completion message is used to inform the SN where the selected PSCell is located that the UE has successfully completed the reconfiguration process.

[0141] Optionally, in S305b, if other candidate SNs are configured, the MN sends an SN release request message to the other candidate SNs. After receiving the SN release request message, the candidate SN replies with an SN release confirmation message to the MN in S305c.

[0142] S306: The UE performs synchronization to the target PSCell (the candidate PSCell selected above / the candidate cell that meets the execution conditions). Synchronization can be achieved through a random access process, and the specific process is not limited in this application. It is understood that this application does not limit the order in which the UE sends the RRC reconfiguration complete message and performs the random access process.

[0143] S307, the MN sends an SN status transfer message to the SN.

[0144] S308: The MN forwards data to the target SN.

[0145] S309-S312, execute the path update process, the specific process is not limited in this application.

[0146] The following briefly introduces a CPC process provided by an embodiment of the present application in conjunction with the various steps in Figure 4. This process only shows the main steps. For detailed processes, please refer to 3GPP TS37.340.

[0147] It can be understood that the source SN shown in FIG4 refers to the SN currently accessed by the UE, and the target SN shown in FIG4 refers to the candidate SN of the UE, that is, the SN to be accessed.

[0148] S401: When the MN determines to initiate a CPC process, it sends an SN Addition Request message to at least one candidate SN. The SN Addition Request message is used to request the candidate SN to allocate resources, etc.

[0149] S402: After confirming that the resource request can be allowed, the SN where the candidate cell is located sends an SN Addition Request Acknowledge message to the MN.

[0150] S403, the MN sends an RRC reconfiguration message to the UE, the RRC reconfiguration message including CPC configuration. The CPC configuration includes one or more candidate SCG configuration information and execution conditions associated with each SCG configuration information, and the SCG configuration comes from the candidate target SN.

[0151] S404: After receiving the RRC reconfiguration message from the MN, the UE replies with an RRC reconfiguration complete message to the MN. The UE uses the other RRC configurations in the RRC reconfiguration message except the CPC configuration.

[0152] In step S405, the UE begins evaluating the execution conditions. If the execution conditions for a candidate cell are met, the UE uses the configuration of the candidate PSCell selected in the RRC reconfiguration message and responds with an RRC reconfiguration complete message to the MN. The RRC reconfiguration complete message includes the RRC reconfiguration complete message for the selected candidate PSCell and information that enables the MN to identify the selected candidate PSCell.

[0153] It can be understood that the candidate SCG configuration information here corresponds to the configuration of the candidate PSCell, so the execution conditions associated with the SCG configuration information can also be understood as the execution conditions corresponding to one or more candidate PSCells.

[0154] S406a: The MN sends an SN release request message to the source SN to inform the source SN to stop data transmission with the UE.

[0155] S406b: After receiving the SN release request message from the MN, the source SN sends an SN release request confirmation message to the MN.

[0156] S407a, the MN sends an SN reconfiguration completion message to the target SN to inform the SN where the selected candidate PSCell is located that the reconfiguration process is completed.

[0157] Optionally, in S407b, if other candidate SNs are configured, the MN sends an SN release request message to the other candidate SNs. After receiving the SN release request message, the candidate SN replies with an SN release confirmation message to the MN in S407c.

[0158] S408: The UE performs synchronization toward the target PSCell (the candidate PSCell selected above / a candidate cell that meets the execution conditions). The synchronization may be achieved through a random access process.

[0159] S409a-S409b, optionally, the source SN sends an SN state transfer to the target SN via the MN.

[0160] S410, optionally, the MN forwards data to the target SN.

[0161] S411-S417: Execute the path conversion process. The specific process is not limited in this application.

[0162] 2. SCG selective activation

[0163] In the CPAC process, after the UE completes the random access procedure with the target PSCell, the UE releases the CPAC configuration. Therefore, the UE cannot perform subsequent CPAC procedures to add / change PSCells before network reconfiguration or network restart.

[0164] If a PSCell needs to be added or changed, the network needs to reconfigure the cell configuration corresponding to the candidate PSCell. To reduce the latency and signaling overhead caused by multiple SCG changes, Selective SCG activation is introduced. After allowing SCG changes and before network reconfiguration, the UE can continue to use the previously stored candidate PSCell cell configuration, also known as the candidate secondary cell group configuration or primary and secondary cell configuration.

[0165] Figure 2 shows a possible example of selective activation of the SCG. In this example, the network configures one or more candidate PSCell cell configurations among multiple candidate SNs for the UE, where the candidate SNs may include SN1, SN2, ..., SNx.

[0166] If the UE detects that the configuration execution conditions corresponding to the candidate PSCell in SN1 are met, it will switch to or access the cell in SN1. After the UE completes the connection with SN1, it does not release the candidate PSCell cell configuration, that is, it continues to maintain the PSCell cell configuration and executes the PSCell cell change process.

[0167] The UE can continue to evaluate the conditions (i.e., evaluate whether the execution conditions for accessing the new PSCell are met). When the execution conditions of other candidate PSCell cells are met, the UE triggers the change process, such as the UE switching from the PSCell of SN1 to the PSCell of SN2, or the UE switching from PSCell 1 of SN1 to PSCell 2. It is understandable that after switching to the PSCell of SN2, the UE can also switch back to the PSCell of SN1.

[0168] It is understandable that the above process is an example, but the present application is not limited thereto. The MN may also perform a conditional PSCell addition process when the SN0 is not established, and then perform a conditional change process based on the configuration information of the PSCell.

[0169] 3. PDU splitting

[0170] PDU splitting means that part of the services of a PDU session is transmitted by the master node and part of the services is transmitted by the slave node.

[0171] 4. SRB3

[0172] SRB3 refers to the signaling plane bearer between the UE and the SN.

[0173] 5. Primary SCG Cell (PSCell)

[0174] The PSCell refers to the SCG cell to which the UE randomly accesses when performing a synchronous reconfiguration procedure for dual connectivity operation.

[0175] 6. Secondary Cell Group (SCG)

[0176] The SCG is a serving cell subset consisting of a PSCell and zero or more secondary cells.

[0177] 7. Secondary Cell

[0178] A secondary cell refers to a cell that provides additional radio resources on top of a special cell for a UE configured with carrier aggregation (CA).

[0179] 8. Communication Key

[0180] The communication key described in the embodiment of the present application refers to a key used to protect the security of air interface communications between devices. For example, the communication key between the UE and the SN is used to protect the security of communications between the UE and the SN. As an example, the communication key includes a signaling plane key (also referred to as an RRC key) and / or a user plane key (UP key), wherein the signaling plane key is used to protect the security of signaling plane messages transmitted between devices, and the user plane key is used to protect the security of user plane data transmitted between devices. The signaling plane key may include a signaling plane integrity protection key K RRCint and / or signaling plane encryption and decryption key K RRCenc , where K RRCint Used to prevent signaling messages from being tampered with, K RRCenc Used to prevent signaling plane message leakage; the user plane key may include the user plane integrity protection key K UPint and / or user plane encryption and decryption key K UPenc , where K UPint Used to prevent user plane data from being tampered with, K UPenc Used to prevent user plane data leakage.

[0181] In the dual connectivity scenario, security protection includes control plane security protection and user plane security protection. Among them, the control plane security protection between UE and MN is based on K gNB Derived signaling plane keys (such as integrity protection key K RRCint and encryption / decryption key K RRCenc ); The user plane security protection between UE and MN is based on K gNB Derived user plane keys (such as integrity protection key K UPint and / or encryption / decryption key K UPenc ).

[0182] The communication key is used to generate a key stream for encrypting air interface communication data between devices. The key stream is generated based on parameters such as the communication key, count value (COUNT), bearer identifier (BEARER), direction (DIRECTION) and length (LENGTH).

[0183] The control plane security protection between UE and SN is based on K SN The derived signaling plane keys (such as integrity protection keys, encryption and decryption keys), the user plane security protection between UE and SN is based on K SNThe derived user plane keys (such as integrity protection keys, encryption and decryption keys) and whether the user plane security protection between UE and SN is enabled are determined by SN. gNB The communication key used to protect the communication security between UE and MN can be derived by UE and SN through K SN The communication key used to protect the communication security between the UE and the SN is derived. The following describes a security establishment process between the UE and the SN with reference to FIG5 .

[0184] S501: An RRC connection is established between the UE and the MN. The specific process is not limited in this application.

[0185] S502, MN sends SN add / modify request message to SN, which is used to negotiate available resources, configuration and algorithm used by SN. SN , then MN generates K SN The SN add / modify request message is sent to the SN via an SN add / modify request message. The SN add / modify request also includes the UE security capabilities and UP security policy. For PDU splitting scenarios, the SN add / modify request can also include the activation decision for user plane integrity protection and ciphering protection.

[0186] Among them, MN maintains a 16-bit SN Counter in the access layer security context, and MN derives K SN SN Counter is used as one of the inputs. For example, MN derives K SN The input parameters include: K gNB , SN Counter, SN Counter length, etc.

[0187] The MN should maintain the SN Counter in the access layer security context, but the UE does not need to maintain the SN Counter because when the UE calculates a new K SN When the MN releases the SN connection, it will provide the current SN Counter to the UE. If the MN decides to release the SN connection and then restarts the connection with the same SN, the SN Counter should continue to increase to maintain the calculated K SN It's new.

[0188] S503, SN allocates necessary resources and selects security algorithms. If SN receives a new K SN , then SN uses the new K SN Calculate the required RRC keys and UP keys.

[0189] For SN-derived UP keys, in non-PDU splitting scenarios, the SN can determine the derived UP keys based on the received UP security policy, such as deriving the corresponding keys only when it is determined to activate the integrity protection and / or encryption protection of the user plane; in PDU splitting scenarios, the SN can determine the derived keys based on the received activation decisions of the user plane integrity protection and encryption protection, such as deriving the corresponding keys only when the activation policy indicates activation.

[0190] S504, the SN sends an SN add / modify confirmation message to the MN, where the confirmation message is used to indicate to the MN the availability of the requested resource, the selected algorithm identifier, and the UP integrity protection and encryption indication.

[0191] S505: The MN sends an RRC reconfiguration request message to the UE, where the request message is used to instruct the UE to configure a new data radio bearer (DRB) and / or signaling radio bearer (SRB) for the SN. The request message includes an SN Counter, which is used to instruct the UE to derive a new K SN , the request message also includes algorithm identification, UP integrity protection and encryption indication.

[0192] S506: After successfully receiving the RRC reconfiguration message, the UE sends an RRC reconfiguration complete message to the MN. If the RRC reconfiguration message includes the SN Counter, the UE derives K based on the received SN Counter. SN , and based on K SN Derive RRC and UP keys for communication security between UE and SN, and activate RRC protection and user plane protection according to the received indication.

[0193] It is understandable that UE and MN deduce K SN The algorithm and input parameters used are the same, so the K deduced by UE is SN K sent by MN to SN SN Same; on the other hand, UE uses K SN The algorithms and input parameters used to derive the RRC key and UP key (ie, communication key) are also the same. Therefore, the RRC key and UP key (ie, communication key) derived by the UE and SN are also the same.

[0194] S507: The MN sends an SN Reconfiguration Complete message to the SN. Upon receiving this message, the SN may activate encryption, decryption, and integrity protection between the SN and the UE. If the SN does not activate encryption, decryption, and integrity protection at this stage, the SN shall activate encryption, decryption, and integrity protection upon receiving the random access request from the UE.

[0195] After the above process, UE and SN both get the same K SN , and use the same K SN The same RRC key and UP key are derived, and thus the same RRC key and UP key are used to secure communications between the UE and the SN.

[0196] However, the method flow shown in Figure 5 only defines the process for the MN to establish a secure connection between the UE and the SN in the process scenario of adding or modifying an SN. In the SCG selective activation scenario, there can be multiple candidate SNs, and each SN can be configured with multiple candidate SCGs. If a secure connection is established according to the existing process, the MN may provide the same K to different candidate SNs. SN , or provide the same K to multiple candidate SCGs under the same SN SN , so it cannot support key isolation. In addition, when UE accesses K at different times SN For the same SN or SCG, according to the same K SN The derived security protection keys are the same, and the parameters used to generate the key stream may be repeated, further causing key stream reuse. Therefore, how to establish a secure connection between the UE and the SN in the SCG selective activation scenario is an issue that needs to be considered.

[0197] In order to solve the above problem, this embodiment proposes the following solution. FIG6 shows an exemplary flow chart of the method provided by this application, which includes the following steps.

[0198] S600: An RRC connection is established between the communication device and the master node.

[0199] Specifically, the detailed process of establishing an RRC connection can be found in 3GPP TS38.331.

[0200] S601: The master node sends a slave node adding request message to the slave node. Correspondingly, the slave node receives the slave node adding request message from the master node.

[0201] In one possible implementation, when the master node determines to configure SCG selective activation for the communication device, the slave node addition request message includes SCG selective activation indication information. The SCG selective activation indication information can be a newly added IE, or an existing IE with a new value, which is not limited in this application (for details, please refer to step S701 in method 700).

[0202] In another possible implementation, the slave node addition request message also includes a root key. In one possible implementation, the root key is specific to only one candidate cell in the slave node (for details, see step S801 in method 800). In another possible implementation, the root key is specific to all candidate cells in the slave node, which can be understood as all candidate cells in the slave node using the root key (for details, see step S901 in method 900).

[0203] S602: The slave node sends a slave node addition request confirmation message to the master node. Correspondingly, the master node receives the slave node addition request confirmation message from the slave node.

[0204] The slave node addition request confirmation message includes the determined candidate cells and the DRB ID list. The DRB ID list is used to characterize at least two DRB IDs for each DRB in the candidate cell (for details, refer to step S702 in method 700). In another possible implementation, the DRB IDs in the corresponding configurations of different candidate cells under the slave node are different, so the DRB ID list is used to characterize at least two DRB IDs for each DRB in all candidate cells under the slave node (for details, refer to step S902 in method 900).

[0205] S603: The master node sends a reconfiguration message to the communication device. Correspondingly, the communication device receives the reconfiguration message from the master node.

[0206] The reconfiguration message includes configuration information of the candidate cell, and the configuration information of the candidate cell includes a count value corresponding to the candidate cell and a DRB ID list corresponding to the DRB.

[0207] In one possible implementation, before the master node sends a reconfiguration message to the communication device, the master node generates M root keys corresponding to M (M>=1) candidate cells determined by the slave node, and sends the M root keys corresponding to the M candidate cells to the slave node (for details, please refer to steps S703-S704 in method 700).

[0208] In another possible implementation, before the master node sends a reconfiguration message to the communication device, after receiving confirmation of the slave node addition request message from the slave node, the master node determines whether to further provide the slave node with the root key corresponding to the candidate cell. Specifically, when the slave node provides N (N>=2) candidate cells, the master node generates N-1 root keys corresponding to the N candidate cells determined by the slave node, and sends the N-1 root keys corresponding to the N candidate cells to the slave node. When N=1, the master node does not need to further provide the root key to the slave node (for details, please refer to steps S803-S804 in method 800).

[0209] In another possible implementation, before the master node sends a reconfiguration message to the communication device, the master node sends the root key corresponding to the slave node to the slave node in step S601, and the root key is shared by all candidate cells in the slave node (for details, please refer to step S901 in method 900).

[0210] In a possible implementation manner, the reconfiguration message further includes an execution condition corresponding to the configuration information of each candidate cell.

[0211] S604: The communication device establishes a connection with the selected candidate cell.

[0212] In a possible implementation manner, when the communication device determines that the first candidate cell meets its corresponding execution condition, it chooses to establish a connection with the first candidate cell.

[0213] In a possible implementation, before the communication device establishes a connection with the selected candidate cell, a reconfiguration completion message is sent to the master node.

[0214] S605, the communication device selects a DRB ID that has not been used in the DRB ID list to protect the communication data transmitted using DRB between the communication device and the first candidate cell.

[0215] Exemplarily, when multiple DRBs are used to transmit communication data between the communication device and the first candidate cell, the multiple DRBs are all DRB IDs that have not been used.

[0216] The first DRB is securely protected by an unused DRB ID, thereby protecting the communication data transmitted between the communication device and the first candidate cell using the first DRB.

[0217] FIG7 shows an exemplary flow chart of a method 700 provided in an embodiment of the present application. The method 700 is exemplarily described below with reference to each step in FIG7 .

[0218] S700: An RRC connection is established between the UE and the MN.

[0219] Specifically, the detailed process of establishing an RRC connection can be found in 3GPP TS38.331.

[0220] S701: The MN sends an SN adding request message to the candidate SN. Correspondingly, the candidate SN receives the SN adding request message from the MN.

[0221] For example, when the MN determines to configure SCG selective activation for the UE, it sends an SN add request to the candidate SN1 and other candidate SNs respectively. It is understandable that the other candidate SNs described in the embodiment of the present application include one or more SNs other than SN1. For the sake of convenience, the embodiment of the present application takes SN2 as the other candidate SN as an example, but the present application is not limited to this.

[0222] It should be noted that, when it is determined that the initiated process is SCG selective activation, the SN add request message includes UE security capabilities, UE security policies, available DRB ID list and SCG selective activation indication information. Among them, the SCG selective activation indication information is used to indicate that the current process is an SCG selective activation process. The SCG selective activation indication information can be a newly added IE, or a new value can be assigned using an existing IE. This application is not limited.

[0223] Optionally, for the scenario of PDU splitting, the SN adding request message also includes the activation decision of the user plane integrity protection and encryption protection of the PDU session determined by the MN.

[0224] It is understandable that the SN add request message does not carry the key K of the candidate SN. SN , that is, MN can skip K SN Derivative of .

[0225] S702: SN1 sends an SN add request confirmation message to MN. Correspondingly, MN receives the SN add request confirmation message from SN1.

[0226] SN1 selects the security algorithm to be used based on the UE security capability received in S601, and determines whether to enable security protection (encryption protection and / or integrity protection) of the user plane based on the UE security policy. The SN addition request confirmation message includes the radio bearer configuration, the security algorithm selected by SN1, the user plane security protection indication, and the DRB ID list.

[0227] For the DRB ID list, if it includes a DRB terminated on SN1 and the security protection of the user plane is enabled (encryption protection and / or integrity protection), SN1 generates a first identification list corresponding to the first DRB corresponding to each candidate PSCell determined, and the first identification list includes at least 2 DRB IDs for characterizing the first DRB. At this time, the DRB ID list is equivalent to the first identification list.

[0228] It should be noted that, when the candidate PSCell includes N (N>=2) DRBs, the relationship between the DRB ID list and the first identification list is as follows:

[0229] Relationship 1: The DRB ID list includes N identification lists, and the first identification list is one of the N identification lists: SN1 generates N identification lists corresponding to the N DRBs respectively, where each identification list includes at least two DRB IDs for representing each DRB in the N DRBs, which can be understood as generating an identification list for each DRB respectively;

[0230] Relationship 2: The DRB ID list is a list of identifiers corresponding to N DRBs, and the DRB ID list includes the first identifier list: SN1 generates an identifier list corresponding to the N DRBs, that is, a DRB ID list. The DRB ID list includes identifiers for representing the N DRBs, and it can be understood that the DRB ID corresponding to each DRB is selected from the DRB ID list.

[0231] In this embodiment of the present application, SN1 may generate the DRB ID list in any of the following ways:

[0232] Method 1: The DRB ID list includes a corresponding default DRB ID for each DRB, and corresponds to at least one candidate DRB ID. The default DRB ID can be understood as the initial ID of the DRB.

[0233] For the case where the relationship between the above-mentioned DRB ID list and the first identification list is 1, SN1 generates corresponding N identification lists for the N DRBs in the candidate PSCell respectively. For each DRB ID therein, each of the N identification lists includes a default DRB ID and at least one candidate DRB ID. At this time, the DRB ID list includes the N identification lists.

[0234] For the case where the relationship between the above-mentioned DRB ID list and the first identifier list is 2, SN1 generates an identifier list corresponding to the N DRBs in the candidate PSCell, that is, a DRB ID list. The DRB ID list includes a default DRB ID for each DRB, and a candidate DRB ID list for the N DRBs. The candidate DRB ID list corresponds to N DRBs, and it can be understood that the candidate DRB IDs of each DRB are selected from the candidate DRB ID list. It should be noted that the DRB ID list may include the default DRB ID and the candidate DRB ID list, or the DRB ID list only includes the candidate DRB ID list, without limitation. It can be understood that the DRB ID used when the UE initially accesses a PScell ​​in SN1 is the default DRB ID, and the candidate DRB ID is the DRB ID that the UE can select when accessing the same PSCell again. The rules for selecting the candidate DRB ID may be preconfigured, and the preconfigured rules are the same on the UE side and the SN1 side. Exemplarily, the preconfigured rules may be based on the replacement of the candidate DRB ID from small to large, or based on the relationship between the DRB IDs in the received message.

[0235] For example, the DRB list of a DRB ID is 1, 4, 3. The default ID of the DRB is 1, and its candidate ID list is 4, 3. When the UE accesses PSCell#1 in SN1 for the first time, the DRB ID used is the default DRB ID value of 1. According to the pre-configuration rule of replacing candidate DRB IDs from small to large, 3 is smaller than 4, so 3 is used first. When the UE accesses the PSCell#1 for the second time, the DRB ID used is the candidate DRB ID value of 3. Similarly, when accessing the PSCell#1 for the third time, the DRB ID used is the candidate DRB ID value of 4; or according to the pre-configuration rule of the relationship between the DRB IDs in the received message, 4 is in front of 3, so 4 is used first, that is, when the UE accesses the PSCell#1 for the second time, the DRB ID used is the candidate DRB ID value of 4.

[0236] Method 2: The DRB ID list includes at least two corresponding candidate DRB IDs for each DRB.

[0237] For the case where the relationship between the above-mentioned DRB ID list and the first identification list is 1, SN1 generates corresponding N identification lists for the N DRBs in the candidate PSCell respectively. For each DRB ID therein, each of the N identification lists includes at least two candidate DRB IDs. At this time, the DRB ID list includes the N identification lists.

[0238] In the case where the relationship between the DRB ID list and the first identifier list is 2, SN1 generates an identifier list corresponding to the N DRBs in the candidate PSCell, that is, a DRB ID list. The DRB ID list contains at least 2N candidate DRB IDs for the N DRBs. It can be understood that the DRB ID of each DRB is selected from the DRB ID list.

[0239] The rule for selecting the candidate DRB ID may be preconfigured, which is the same as the preconfigured rule in Method 1 and will not be described in detail here. It is understood that the DRB ID used by the UE when initially accessing and re-accessing the same PScell ​​in SN1 is determined by the preconfigured rule.

[0240] For example, there are two DRBs between the UE and the SN, and the order of the IDs in the DRB list generated by SN1 is 2, 1, 4, and 3. According to the pre-configured rule of replacing the candidate DRB IDs from small to large, when the UE first accesses PSCell#1 in SN1, the DRB IDs used are 1 and 2 respectively. When accessing the PSCell#1 for the second time, the DRB IDs used are 3 and 4 respectively; or according to the pre-configured rule of the order of the DRB IDs in the received message, when the UE first accesses PSCell#1 in SN1, the DRB IDs used are 2 and 1 respectively. When accessing the PSCell#1 for the second time, the DRB IDs used are 4 and 3 respectively.

[0241] Similarly, SN2 sends an SN add request confirmation message to MN.

[0242] It should be noted that the candidate SN determines at least two candidate PSCells. This may be that SN1 determines at least two candidate PSCells, or that SN1 and SN2 each determine at least one candidate PSCell. This is not limited in this embodiment.

[0243] S703, after receiving the SN add request message confirmation from the candidate SN, MN generates the K corresponding to each candidate SN. SN If a SN provides multiple PSCells, the MN generates a different K for each PSCell. SN Among them, the K corresponding to PSCell SN It is deduced based on the SK counter value. Furthermore, the MN stores the relationship between the SK counter and the corresponding PSCell configuration.

[0244] As an example, the MN generates corresponding K for N PSCells. SNThis can be done in the following way: the MN side has an initial SK counter, and then the MN sequentially increases a fixed value according to the initial value of the SK counter to obtain N different SK counter values, and then derives N root keys for N PSCells based on the values ​​of the N SK counters (for example, if the initial value of the SK counter is 7 and the increased fixed value is 1, then the value of the next SK counter is 8; if the increased fixed value is 2, then the value of the next SK counter is 9, and the fixed values ​​are added sequentially until N SK counters are obtained).

[0245] This application does not limit the manner in which the MN obtains the SK counter. As a possible example, the MN obtains the SK counter from the AS context.

[0246] S704, MN sends a key notification message to the candidate SN, and the key notification message includes the K corresponding to the candidate SN. SN Correspondingly, the candidate SN receives the key notification message from the MN.

[0247] If a single candidate SN provides multiple candidate PSCells, the MN sends multiple K packets for the multiple candidate PSCells to the SN. SN It should be noted that the multiple K SN , can be sent to the SN in one message or multiple messages, each message carries at least one K SN , without restriction. At this time, the key notification message includes the K of each PSCell SN And the corresponding candidate information identification. The candidate information identification is used by SN to determine K SN The corresponding PSCell, so that when the UE subsequently accesses the PSCell, the SN can determine the K SN .

[0248] S705: The MN sends an RRC reconfiguration message to the UE. Correspondingly, the UE receives the RRC reconfiguration message from the MN. The RRC reconfiguration message includes configuration information of at least two candidate PSCells.

[0249] The MN generates an RRC reconfiguration message based on the relationship between the stored SK counter and the corresponding PSCell configuration. The RRC reconfiguration message includes the SK counter and the corresponding PSCell configuration. The SK counter is the one stored by the MN in step S703. Different PSCells correspond to different SK counters. The SK counter is used to generate the K counter shared between the UE and the PSCell. SN . The PSCell configuration includes an SN selection algorithm and an identification list. The identification list for each DRB is generated in step S702, and the identification list can be the default DRB ID and at least one candidate DRB ID in method one, or at least two candidate DRB IDs in method two. Alternatively, when the candidate PSCell contains N DRBs, the DRB ID list is a collection of N identification lists generated in step S702.

[0250] Optionally, the RRC reconfiguration message also includes an execution condition associated with the corresponding PSCell. When the execution condition corresponding to the PSCell is met, the UE can select the PSCell.

[0251] It is understandable that this application does not limit the order in which S704 and S705 are executed.

[0252] S706: The UE sends an RRC reconfiguration complete message to the MN. Correspondingly, the MN receives the RRC reconfiguration complete message from the UE.

[0253] For example, after receiving the RRC reconfiguration message from the MN, the UE processes the RRC reconfiguration message and sends an RRC reconfiguration complete message to the MN. The specific process is not limited in this application.

[0254] In step S707, the UE begins evaluating candidate cells to determine whether the execution conditions corresponding to any candidate cell are met. If the UE detects a candidate cell that meets the execution conditions, the UE sends an RRC reconfiguration complete message* to the MN. Accordingly, the MN receives the RRC reconfiguration complete message* from the UE. The RRC reconfiguration complete message* includes information about the SN of the candidate cell selected by the UE, which may be a conditional reconfiguration identifier. The MN determines the target SN (i.e., SN1) based on the information about the candidate cell's SN.

[0255] It can be understood that each conditional reconfiguration is associated with a candidate PSCell, so each candidate PSCell has an associated execution condition for the conditional reconfiguration.

[0256] For example, the candidate cell selected by the UE is PSCell#1. In the embodiment of the application, the SN corresponding to PSCell#1 is recorded as SN1. It is understood that the candidate cell selected by the UE in the embodiment of the application refers to the candidate PSCell detected by the UE that meets the execution conditions, and similar parts will not be repeated in the following.

[0257] After determining the candidate cell, the UE uses the SK counter in the conditional reconfiguration corresponding to the candidate cell to derive K SN , and further use the K according to the configuration information SN Alternatively, if the MN uses the RRC reconfiguration message to include the SK counter, the UE can use the SK counter to derive the K SN , the SK counter is included in other locations outside of the conditional reconfiguration.

[0258] S708, MN sends an SN reconfiguration complete message to SN1. Correspondingly, SN1 receives the SN reconfiguration complete message from MN. The reconfiguration complete message includes the identifier of the candidate information for UE to select PSCell#1. After receiving the SN reconfiguration complete message from MN, SN1 determines the PSCell and the corresponding K according to the identifier of the candidate information. SN .

[0259] S709: The UE establishes a connection with the selected PScell ​​#1 on SN1.

[0260] After the connection is established, the DRB IDs in the DRB ID list determined in step S702 are used between the UE and SN1 to securely protect the transmitted data. Specifically, for each radio bearer, when performing user plane data security protection, the default DRB ID in method 1 corresponding to each bearer is used as an input parameter, or the selected DRB ID in method 2 is used as an input parameter.

[0261] On the UE side, the UE uses the SK Counter corresponding to the selected PSCell#1 and the master node key to deduce K SN , further based on K SN Derived user plane security protection key, the user plane security protection key can be at least one of the encryption key and the integrity protection key. For SN1 side, SN1 uses PSCell#1 corresponding K SN Derive user plane security protection keys.

[0262] It is understandable that due to the K SNThe same, so SN1 and UE according to the same K SN The derived communication key is the same, and the communication security between SN1 and UE can be protected by the communication key.

[0263] S710, the UE continues to evaluate candidate cells and determines that the execution conditions for accessing another cell PSCell#2 are met. PSCell#2 can be a cell on SN1 that is different from PSCell#1, or a cell on another SN that is different from SN1.

[0264] It should be noted that after the UE determines to switch to another cell, it sets the currently used DRB ID to be used or deletes it from the DRB ID list. Similarly, after SN1 determines that the UE releases the connection, it sets the currently used DRB ID to be used or deletes it from the DRB ID list. The currently used DRB ID is the DRB ID used when the UE communicates with PSCell#1 in step S709. Optionally, the UE and SN1 respectively store user plane security protection keys.

[0265] The process of UE accessing another cell PSCell#2 is the same as the process of initial access to PSCell#1, namely steps S707-S709, which will not be repeated here.

[0266] It should be noted that the DRB ID used by PSCell#2 can be the same as the DRB ID used by the first access to PSCell#1. This is because the K SN Different, so use this K SN The derived user plane security protection keys are different, so different key streams can still be derived when the DRB ID is the same.

[0267] In step S711, the UE continues evaluating candidate cells and determines that the conditions for accessing PSCell #1 in the original cell SN1 are met. The UE then sends an RRC Reconfiguration Complete message* to the MN. In response, the MN receives the RRC Reconfiguration Complete message* from the UE. For related features, see step S707 and are not further described here.

[0268] Optionally, the RRC reconfiguration completion message* also includes a DRB ID. The DRB ID is the DRB ID to be used between the UE and PSCell#1. Specifically, for each DRB, the UE uses a default DRB ID when it initially accesses PSCell#1. When the UE leaves PSCell#1 and switches to another PSCell, the used DRB ID is deleted or marked as used. When the UE subsequently accesses the PSCell#1 again, the UE selects the DRB ID to be used from the remaining candidate DRB IDs in the DRB ID list, and further sends it to SN1 through the MN. It should be noted that this step is used without using pre-configuration rules to determine the DRB ID.

[0269] S712: MN sends an SN reconfiguration complete message to SN1. SN1 receives the SN reconfiguration complete message from MN. For related features, see step S708, which will not be described here.

[0270] Optionally, the SN reconfiguration completion message also includes a DRB ID, where the DRB ID is the DRB ID selected and reported by the UE itself.

[0271] S713, the UE establishes a connection with the PSCell#1 on the selected SN1.

[0272] After the connection is established, the transmitted data between the UE and SN1 is securely protected based on the remaining candidate DRB IDs in the DRB ID list, where the candidate DRB ID is a DRB ID that has not been used in the DRB ID list. Specifically, the UE and SN1 each select the remaining candidate DRB IDs from the DRB list according to the same pre-configured rules. The selection method is shown in step S702 and will not be repeated here. For each wireless bearer, when performing user plane data security protection, the newly selected DRB ID is used for security protection. Specifically, if the UE has stored the user plane security key corresponding to the PSCell, the user plane security key and the newly selected DRB ID can be used directly; otherwise, the UE needs to first use the SK Counter and the master node key corresponding to PSCell#1 to deduce K SN , further based on K SN Derive user plane security protection keys.

[0273] When the UE reconnects to PSCell#1, the corresponding DRB ID value between the UE and PSCell#1 is determined according to preconfigured rules. Therefore, in this case, the DRB ID value used when the UE accesses PSCell#1 in SN1 for the second time is different from the DRB ID value used when the UE first accesses PSCell#1. Therefore, the key stream generated by the UE and SN1 using the DRB ID value when the UE accesses PSCell#1 for the second time is different from the key stream generated by the UE and SN1 using the DRB ID value when the UE first accesses SN1, thereby preventing the reuse of key streams and improving the security of communications.

[0274] It is understandable that the process shown in method 700 only shows the main steps, and the actual process may also include other steps, which are not limited in this application.

[0275] In the above scheme, the key notification sent by the MN to the candidate SN includes different K keys corresponding to different PSCells. SN Similarly, the configuration sent by the MN to the UE includes different SK counters corresponding to different PSCells, ensuring that the UE has K counters derived from different PSCells. SN Different, and the K derived on the UE side SN The K received by the SN side for the same PSCell SN The same DRB IDs are used to isolate the keys between different PSCells. Furthermore, through the pre-configured rules for the DRB ID, different DRB IDs are used when the UE connects to the same PSCell multiple times. Different DRB IDs ensure that the key streams used are different even if the keys remain unchanged, further preventing the reuse of key streams.

[0276] FIG8 shows an exemplary flow chart of a method 800 provided in an embodiment of the present application. The following is an exemplary description of the method 800 in conjunction with the various steps in FIG8. The difference from the method 700 is that the MN adds K in the SN adding request. SN If SN provides two or more candidate PSCells, MN will continue to generate K corresponding to the remaining candidate PScells. SN And send it to SN.

[0277] S800: An RRC connection is established between the UE and the MN.

[0278] Specifically, the detailed process of establishing an RRC connection can be found in 3GPP TS38.331.

[0279] S801: The MN sends an SN adding request message to the candidate SN. Correspondingly, the candidate SN receives the SN adding request message from the MN.

[0280] For example, when the MN determines to configure SCG selective activation for the UE, it sends an SN add request to the candidate SN1 and other candidate SNs respectively. It is understandable that the other candidate SNs described in the embodiment of the present application include one or more SNs other than SN1. For the sake of convenience, the embodiment of the present application takes SN2 as the other candidate SN as an example, but the present application is not limited to this.

[0281] It should be noted that, when it is determined that the SCG selective activation is initiated, the SN add request message includes UE security capabilities, UE security policy, available DRB ID list, K SN And SCG selective activation instruction information. Among them, K SN The root key of the candidate SN. MN derives different K for each candidate SN. SN The SCG selective activation indication information is used to request the SN to selectively activate the SCG. The SCG selective activation indication information can be a newly added IE, or an existing IE with a new value. This application does not limit this.

[0282] Optionally, for the scenario of PDU splitting, the SN adding request message also includes the activation decision of the user plane integrity protection and encryption protection of the PDU session determined by the MN.

[0283] S802: The candidate SN sends an SN add request confirmation message to the MN. Correspondingly, the MN receives the SN add request confirmation message from SN1. The specific steps can be referred to in step S702 and will not be repeated here.

[0284] S803: After receiving the SN add request message confirmation from the SN, the MN determines whether to further provide the K corresponding to the PSCell to the SN. SN .

[0285] Specifically, for each SN, if the SN provides only one candidate PSCell, the MN can skip steps S803 and S804. If the SN provides N candidate PSCells (N>=2), the MN needs to generate the remaining N-1 K SN Among them, the K sent by MN to the SN in S801 is SN And the N-1 K SN They correspond to the N candidate PSCells provided by the SN. Furthermore, the MN stores the relationship between the SK counter and the corresponding PSCell configuration. SN It is deduced based on the SK counter value.

[0286] S804: The MN sends a key notification message to the candidate SN that provides N (N>=2) PSCells. Correspondingly, the candidate SN receives the key notification message from the MN.

[0287] The key notification message includes the remaining N-1 K SN , and the corresponding candidate information identifier. The candidate information identifier is used by SN to determine K SN The corresponding PSCell, so that when the UE subsequently accesses the PSCell, the SN can determine the K SN It should be noted that the MN sends the remaining N-1 K SN , can be sent to the SN in one message or multiple messages, each message carries at least one K SN , without restriction.

[0288] SN will K SN The configuration corresponding to the corresponding PSCell is stored in association. Specifically, the candidate SN receives N-1 K SN After that, the SN will send N-1 K SN The configuration corresponding to the corresponding N-1 PSCells is associated and stored. In addition, the SN can also store the K received in step S801 according to the identifier of the candidate information. SN The configuration corresponding to the corresponding PSCell is stored in association with the configuration.

[0289] Step 805: For specific steps, please refer to steps S705-S713, which will not be repeated here.

[0290] In the above solution, MN adds a K in the SN add request. SN In this way, when the SN only provides one candidate PSCell, the MN does not need to send a key notification to the SN, thereby saving signaling, minimizing changes to existing processes, and ensuring system compatibility.

[0291] FIG9 shows an exemplary flow chart of a method 900 provided in an embodiment of the present application. The method 900 is described below in conjunction with the various steps in FIG9. The difference from the method 700 is that in this embodiment, the DRB IDs in the configurations corresponding to different candidate PSCells under the same SN are different, so here K SN It is for SN, that is, the root keys of different PSCells under the same SN are the same, while method 700 and method 800 are for PSCell, that is, the root keys of different PSCells under the same SN are different.

[0292] S900: An RRC connection is established between the UE and the MN.

[0293] Specifically, the detailed process of establishing an RRC connection can be found in 3GPP TS38.331.

[0294] S901: The MN sends an SN adding request message to the candidate SN. Correspondingly, the candidate SN receives the SN adding request message from the MN.

[0295] For example, when the MN determines to configure SCG selective activation for the UE, it sends an SN add request to the candidate SN1 and other candidate SNs respectively. It is understandable that the other candidate SNs described in the embodiment of the present application include one or more SNs other than SN1. For the sake of convenience, the embodiment of the present application takes SN2 as the other candidate SN as an example, but the present application is not limited to this.

[0296] It should be noted that, when it is determined that the SCG selective activation is initiated, the SN add request message includes UE security capabilities, UE security policy, available DRB ID list, K SN And SCG selective activation instruction information. Among them, K SN The key of the candidate SN. MN derives different K for each candidate SN. SN MN stores the relationship between SK counter and corresponding SN, where SK counter is used to deduce K of corresponding SN. SN The SCG selective activation indication information is used to request the SN to selectively activate the SCG. The SCG selective activation indication information can be a newly added IE, or an existing IE with a new value. This application does not limit this.

[0297] Optionally, for the scenario of PDU splitting, the SN adding request message also includes the activation decision of the user plane integrity protection and encryption protection of the PDU session determined by the MN.

[0298] S902, for related descriptions, refer to S702. The difference from S702 is that in this embodiment of the present application, the root key for different PSCells under the same SN is the same, and the DRB ID used for different candidate PSCells under the same SN cannot be repeated. It is understood that the DRB ID used for the UE's initial access and subsequent access to the same PSCell or different PSCells under the same SN is different.

[0299] It should be noted that for different candidate PSCells under the same SN, the DRB IDs used cannot be repeated. The SN can generate a DRB ID list in any of the following ways:

[0300] 1. Generate corresponding DRB ID lists for different candidate PSCells under the same SN: For each determined candidate PSCell, the SN generates a list of identifiers corresponding to the DRBs in the candidate PSCell. The method for generating the list of identifiers is similar to Method 1 and Method 2 in S702. At this time, the DRB ID list includes the identifier lists corresponding to all candidate PSCells.

[0301] 2. Generate a DRB ID list for different candidate PSCells under the same SN: The SN directly generates a DRB ID list corresponding to the SN, and the DRB ID list is shared by all candidate PSCells under the SN. The method of generating the DRB ID list refers to method 1 and method 2 in S702. It can be understood that all candidate PSCells under the SN use the DRB ID list. Exemplarily, the DRB ID list under the SN is 1, 2, 3, and 4. Assume that the UE accesses PSCell#1 under SN1 for the first time and uses DRB IDs 1 and 2. After the UE determines to switch to another SN, the DRB IDs 1 and 2 used between SN1 are set to used, or deleted from the DRB ID list. Subsequently, when the UE accesses any PSCell under SN1 again, the DRB IDs that can be used are 3 and 4.

[0302] S903: The MN sends an RRC reconfiguration message to the UE. Correspondingly, the UE receives the RRC reconfiguration message from the MN.

[0303] The MN generates an RRC reconfiguration message based on the stored relationship between the SK counter and the corresponding SN. The RRC reconfiguration message includes the configuration of the SK counter and the SN.

[0304] Specifically, for each SN, the SK counters corresponding to different PSCells in the SN are the same. For example, the same SK counter may be included in the PSCell configuration of the SN, or only one SK counter may be included in the configuration of the SN, and all PSCell configurations share the SK counter. This is used to instruct the UE to determine the DRB ID to use from the same DRB ID list when accessing any PSCell of the SN. The SK counter is the one stored by the MN in step S901.

[0305] The configuration of the SN includes a DRB ID list. The DRB ID list is the DRB ID list generated in step S702, which can be the default DRB ID and at least one candidate DRB ID in method one, or at least two candidate DRB IDs in method two.

[0306] Optionally, the RRC reconfiguration message also includes an execution condition associated with the corresponding PSCell. When the execution condition corresponding to the PSCell is met, the UE can select the PSCell.

[0307] S904-S906, the specific steps can refer to S706-S708, which will not be repeated here.

[0308] S907, UE establishes a connection with PScell#1 on the selected SN1. For related description, refer to S709. The difference from S709 is that UE uses the corresponding SK counter and master node key to deduce K SN The SK counter here corresponds to the SN, while the SK counter in S709 corresponds to the PSCell.

[0309] S908 (optional), for related descriptions, refer to S710. The difference from S710 is that the cell accessed here is a cell on an SN other than SN1.

[0310] After the UE determines to switch to another SN, it sets the DRB ID used between SN1 to used or deletes it from the DRB ID list. Similarly, after SN1 determines that the UE releases the connection, it sets the currently used DRB ID to used or deletes it from the DRB ID list.

[0311] For PSCells using the same SK counter, the same DRB ID list is used. The UE stores the PSCell configuration associated with the same SK counter in association with the DRB ID list.

[0312] S909, for related descriptions, refer to S711. The difference from S711 is that this can be any PSCell under SN1, and is not limited to a PSCell that has been connected before.

[0313] S910: For specific steps, please refer to S712 and will not be repeated here.

[0314] S911, for related descriptions, refer to S713. The difference from S711 is that this can be any PSCell under SN1, and is not limited to a PSCell that has been accessed before. Security protection is performed on the transmitted data based on the remaining candidate DRB IDs in the DRB ID list between the UE and SN1. The candidate DRB ID is a DRB ID that has not been used in the DRB ID list. Specifically, the UE and SN1 each select the remaining candidate DRB IDs from the DRB list according to the same preconfigured rules. The selection method is shown in step S902.

[0315] The UE can determine that the two accesses are to the same SN based on the same SK counter value when accessing SN1 twice, or the association between the PSCell configuration and the DRB ID list in S908.

[0316] In the above scheme, MN uses different SN counters to ensure that the initial K between different SNs is SN Different. And, when switching to the same SN later, even if the same K SN , but security is protected by different DRB IDs to avoid key stream reuse.

[0317] When the UE reconnects to the SN, the corresponding DRB ID value between the UE and the SN is determined according to preconfigured rules. Therefore, in this case, the DRB ID value used when the UE accesses PSCell#1 or other PSCells in SN1 for the second time is different from the DRB ID value used when the UE first accesses PSCell#1 in SN1. Therefore, when the UE accesses SN1 for the second time, the key stream generated by the UE and SN1 using the DRB ID value is different from the key stream generated by the UE and SN1 using the DRB ID value when the UE first accesses SN1, thereby preventing the reuse of key streams and improving the security of communications.

[0318] It can be understood that the above methods 700-900 are illustrated using the SCG selective activation process as an example, but the present application is not limited to this. As an example, some steps in methods 700-900 can also be applied to the CPA and CPC processes shown in Figures 3 and 4.

[0319] Based on the same inventive concept as the method embodiment, the embodiment of the present application also provides a device 1000 and 1100 for executing the method executed by the UE, MN or SN in the above-mentioned method 700-method 900 embodiments. The relevant features can be found in the above-mentioned method embodiments and will not be repeated here.

[0320] As an example, as shown in Figure 10, the apparatus 1000 includes a processing module 1001 and a transceiver module 1002. The transceiver module is configured to perform corresponding message sending and receiving actions, while the processing module can be configured to perform all actions except sending and receiving messages. The specific functions of the processing module 1001 and the transceiver module 1002 can be found in the description of the above-mentioned method embodiment and will not be further described here.

[0321] For example, FIG11 is a second structural diagram of a communication device provided in an embodiment of the present application. The communication device may be a UE, a MN, or a SN. As shown in FIG11 , the communication device 1100 may include a processor 1101. Optionally, the communication device 1100 may further include a memory 1102 and / or a transceiver 1103. The processor 1101 is coupled to the memory 1102 and the transceiver 1103, for example, via a communication bus.

[0322] The following is a detailed introduction to the various components of the communication device 1100 with reference to FIG11 :

[0323] The processor 1101 is the control center of the communication device 1100 and can be a single processor or a collective term for multiple processing elements. For example, the processor 1101 can be one or more central processing units (CPUs), an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application, such as one or more digital signal processors (DSPs) or one or more field programmable gate arrays (FPGAs).

[0324] Optionally, the processor 1101 may execute various functions of the communication device 1100 by running or executing a software program stored in the memory 1102 and calling data stored in the memory 1102 .

[0325] In a specific implementation, as an embodiment, the processor 1101 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG11 .

[0326] In a specific implementation, as an embodiment, the communication device 1100 may also include multiple processors, such as the processor 1101 and the processor 1104 shown in FIG11 . Each of these processors may be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). The processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0327] Among them, the memory 1102 is used to store the software program for executing the solution of this application, and the execution is controlled by the processor 1101. The specific implementation method can refer to the above method embodiment and will not be repeated here.

[0328] Alternatively, the memory 1102 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type of dynamic storage device that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, an optical disc storage (including a compact disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 1102 may be integrated with the processor 1101 or exist independently and be coupled to the processor 701 via an interface circuit (not shown in FIG. 7 ) of the communication device 1100. This embodiment of the present application does not specifically limit this.

[0329] Transceiver 1103 is used for communication with other communication devices. For example, if communication device 1100 is a terminal device, transceiver 1103 can be used to communicate with a network device or another terminal device. For another example, if communication device 1100 is a network device, transceiver 1103 can be used to communicate with a terminal device or another network device.

[0330] Optionally, the transceiver 1103 may include a receiver and a transmitter (not shown separately in FIG11 ), wherein the receiver is used to implement a receiving function, and the transmitter is used to implement a transmitting function.

[0331] Optionally, the transceiver 1103 may be integrated with the processor 1101 or exist independently and be coupled to the processor 1101 through an interface circuit (not shown in FIG. 11 ) of the communication device 1100 . This embodiment of the present application does not specifically limit this.

[0332] It should be noted that the structure of the communication device 1100 shown in FIG11 does not constitute a limitation on the communication device. An actual communication device may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0333] In addition, the technical effects of the communication device 1100 can refer to the technical effects of the communication method described in the above method embodiment, and will not be repeated here.

[0334] It should be understood that the processor in the embodiments of the present application may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0335] It should also be understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0336] The above embodiments can be implemented in whole or in part by software, hardware (such as circuits), firmware or any other combination. When implemented using software, the above embodiments can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer program are loaded or executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (such as infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that contains one or more available media sets. The available medium can be a magnetic medium (for example, a floppy disk, a hard disk, a tape), an optical medium (for example, a DVD), or a semiconductor medium. The semiconductor medium can be a solid-state drive.

[0337] It should be understood that the term "and / or" as used herein simply describes a relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A alone, A and B together, or B alone. A and B can be singular or plural. Furthermore, the character " / " as used herein generally indicates an "or" relationship between the associated objects, but it may also indicate an "and / or" relationship. For specific understanding, please refer to the context.

[0338] In this application, "at least one" means one or more, and "plurality" means two or more. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or plural.

[0339] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0340] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0341] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0342] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0343] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0344] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0345] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0346] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A communication method, characterized in that: The method comprises: The communication device receives a radio resource control RRC reconfiguration message, wherein the RRC reconfiguration message includes configuration information of at least two candidate cells, wherein the at least two candidate cells include a first candidate cell and a second candidate cell; the configuration information of the first candidate cell includes a first count value and a first identifier list corresponding to a first data radio bearer DRB, the first identifier list includes at least 2 DRB identifiers IDs for characterizing the first DRB; the configuration information of the second candidate cell includes a second count value and a second identifier list corresponding to a second DRB, the second identifier list includes at least 2 DRB IDs for characterizing the second DRB; When accessing the first candidate cell, the communication device protects the communication data transmitted between the communication device and the first candidate cell using the first DRB according to a first root key and the first DRB ID in the first identification list, wherein the first root key is generated by the communication device according to the first count value.

2. The method according to claim 1, characterized in that Before the communication device protects the communication data transmitted using the first DRB between the communication device and the first candidate cell according to the first root key and the first DRB ID in the first identification list, the method further includes: The communication device selects the first DRB ID from the first identification list.

3. The method according to claim 2, characterized in that The first DRB ID is a DRB ID that has not been used in the first identification list.

4. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: The communication device deletes the first DRB ID or marks the first DRB ID as used.

5. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: When leaving the first candidate cell and accessing the second candidate cell, the communication device protects the communication data transmitted between the communication device and the second candidate cell using the second DRB according to the second root key and the second DRB ID in the second identification list, wherein the second root key is generated by the communication device according to the second count value.

6. The method according to claim 5, characterized in that The method further comprises: When leaving the second candidate cell and accessing the first candidate cell again, the communication device protects the communication data transmitted between the communication device and the first candidate cell using the first DRB according to the first root key and the third DRB ID in the first identification list, wherein the third DRB ID is different from the first DRB ID.

7. The method according to claim 5 or 6, characterized in that: Before the communication device protects the communication data transmitted using the second DRB between the communication device and the second candidate cell according to the second root key and the second DRB ID in the second identification list, the method further includes: The communication device selects the second DRB ID from the second identification list.

8. The method according to claim 7, characterized in that The second DRB ID is a DRB ID that has not been used in the second identification list.

9. The method according to any one of claims 5 to 8, characterized in that: The method further comprises: The communication device deletes the second DRB ID or marks the second DRB ID as used.

10. The method according to any one of claims 1 to 9, characterized in that: The first count value and the second count value are different.

11. The method according to any one of claims 1 to 9, characterized in that: The first count value and the second count value are the same, and the DRB ID in the first identification list and the DRB ID in the second identification list are different from each other.

12. A communication method, characterized in that: The method comprises: Receive a first identifier list corresponding to a first data radio bearer DRB corresponding to a first candidate cell and a second identifier list corresponding to a second DRB corresponding to a second candidate cell; the first identifier list includes at least two DRB identifiers for characterizing the first DRB ID; the second identification list includes at least 2 DRB IDs for characterizing the second DRB; and A radio resource control (RRC) reconfiguration message is sent to a communication device, wherein the RRC reconfiguration message includes configuration information of the first candidate cell and configuration information of the second candidate cell; wherein the configuration information of the first candidate cell includes a first count value and the first identifier list; and the configuration information of the second candidate cell includes a second count value and the second identifier list; wherein the first count value is used to generate a first root key shared between the communication device and the first candidate cell; and the second count value is used to generate a second root key shared between the communication device and the second candidate cell.

13. The method according to claim 12, characterized in that The receiving of a first identifier list corresponding to a first data radio bearer DRB corresponding to a first candidate cell and a second identifier list corresponding to a second DRB corresponding to a second candidate cell includes: The first identification list is received from a first slave node, and the second identification list is received from a second slave node, wherein the first slave node is different from the second slave node.

14. The method according to claim 13, characterized in that The method further comprises: sending the first root key to the first slave node, and The second root key is sent to the second slave node.

15. The method according to claim 12, characterized in that The receiving of a first identifier list corresponding to a first data radio bearer DRB corresponding to a first candidate cell and a second identifier list corresponding to a second DRB corresponding to a second candidate cell includes: The first identification list and the second identification list are received from a third slave node.

16. The method according to claim 15, characterized in that The method further comprises: The first root key and the second root key are sent to the third slave node.

17. The method according to any one of claims 12 to 16, characterized in that: The first count value is different from the second count value.

18. The method according to claim 15 or 16, characterized in that The first count value is the same as the second count value, and the DRB ID in the first identification list is different from the DRB ID in the second identification list.

19. The method according to claim 18, characterized in that The first root key and the second root key are the same, and the method further includes: The first root key and / or the second root key is sent to the third slave node.

20. A communication method, characterized in that: The method comprises: Receive a slave node adding request message from the master node; Generate a first identification list corresponding to a first data radio bearer DRB corresponding to a first candidate cell; the first identification list includes at least two DRB identification IDs for characterizing the first DRB; and In response to the slave node adding request message, a slave node adding request confirmation message is sent to the master node, wherein the slave node adding request confirmation message includes the first identifier list.

21. The method according to claim 20, characterized in that The method further comprises: receiving a first root key from the master node, and Communication data transmitted using the first DRB between a communication device and the first candidate cell is protected according to the first root key and the first DRB ID in the first identification list; wherein the first DRB ID is a DRB ID that has not been used in the first identification list.

22. The method according to claim 21, characterized in that The method further comprises: Delete the first DRB ID or mark the first DRB ID as used.

23. A communication device, characterized in that: The invention comprises a module for executing the communication method as claimed in any one of claims 1 to 11.

24. A master node, characterized in that: Comprising modules for executing the method as claimed in any one of claims 12 to 19.

25. A slave node, characterized in that: The slave node comprises a module for executing the method as claimed in any one of claims 20-22.

26. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a computer program or an instruction. When the computer program or the instruction is executed on a computer, the computer is caused to execute the communication method according to any one of claims 1 to 22.

27. A communication system, characterized in that: The communication system comprises a communication device and a master node; wherein the communication device is used to execute the method as described in any one of claims 1-11, and the master node is used to execute the method as described in any one of claims 12-19.

28. A computer program product, characterized in that The computer program product comprises a computer program or instructions, and when the computer program or instructions are executed on a computer, the computer is caused to execute the communication method according to any one of claims 1 to 22.