Method and apparatus for communication

Abstract

The embodiment of the invention provides a communication method and device. In this application, a principle of key derivation in handover is provided. On one hand, the downlink RB COUNT as the input of key derivation enables the device to confirm the freshness of the message, prevent a replay attack and protect forward security; in another aspect, network functionality for SPM-KMF for key derivation is provided, rather than AMF and / or gNB in 5G systems, which can reduce the overhead of intermediate key exchange and the overhead of parameters for key derivation.

Description

[0001] This application relates to and claims priority to U.S. Provisional Patent Application No. 63 / 586,585, filed September 29, 2023, entitled "System and Method on Key Derivation in Security Handover Mechanism." The disclosure of the above application is incorporated herein by reference in its entirety. Technical Field

[0002] The present invention relates to the field of wireless technology, and more specifically, to methods and apparatus for communication. Background Technology

[0003] Many emerging trends will trigger considerations and designs for future network systems, such as sixth-generation (6G) systems. In future networks, small cells serving high-speed users will lead to frequent handovers. In the secure handover mechanisms of 5G systems, a new key needs to be generated during the handover process. There are two alternative methods for key reset: horizontal derivation and vertical derivation. Frequent handovers can impact the performance of both horizontal and vertical key derivation, potentially leading to replay attacks. Summary of the Invention

[0004] This application provides a method and apparatus for communication that can prevent replay attacks.

[0005] According to a first aspect, a communication method is provided, which can be performed by a first network function or a chip installed in the first network function responsible for key derivation during handover. The method includes: obtaining first information from a source radio bearer (RB) processor, wherein the first information includes a downlink RB COUNT, the downlink RB COUNT indicating the number of radio bearers (RBs) transmitted in the downlink; and deriving a first key, wherein the first key is used to derive a terminal key, the terminal key being used for communication between a device and a target RB processor, and the input for deriving the first key includes the downlink RB COUNT.

[0006] According to the scheme proposed in this application, the downlink COUNT is used as the input for key derivation, enabling the device to verify the freshness of the message, thereby preventing replay attacks and protecting forward security.

[0007] In addition, the network function of SPM-KMF has been introduced. SPM-KMF replaces the access and mobility management function (AMF) or next-generation Node B (gNB) in the 5th generation (5G) system and is responsible for generating keys, thereby reducing the overhead of intermediate key exchange and the overhead of parameters used for key derivation.

[0008] In one implementation of the first aspect, the method further includes: deriving the terminal key based on the first key; and sending the terminal key to the target RB processor.

[0009] In one implementation of the first aspect, the method further includes: obtaining second information from the source RB processing program, wherein the second information includes one or more of the following parameters: the physical cell identifier (PCI) of the target RB processing program, and the downlink frequency or next hop chaining counter (NCC) of the target RB processing program; the input used to derive the first key further includes the one or more parameters.

[0010] The technical effects of the second aspect can be referenced from those of the first aspect, and will not be elaborated further below.

[0011] According to a second aspect, a communication method is provided, which can be executed by a terminal device or a chip installed in the terminal device. The method includes: obtaining first information from a source RB processor, wherein the first information includes a downlink RB COUNT, the downlink RB COUNT indicating the number of radio bearers (RBs) transmitted in the downlink; deriving a first key, wherein the first key is used to derive a terminal key, wherein the terminal key is used for communication between the device and a target RB processor, and the input for deriving the first key includes the downlink RBCOUNT.

[0012] In one implementation of the second aspect, the method further includes: deriving the terminal key based on the first key.

[0013] In one implementation of the second aspect, the method further includes: obtaining second information from the source RB processing program, wherein the second information includes one or more of the following parameters: physical cell identifier (PCI), downlink (DL) frequency, or next hopchaining counter (NCC); the input used to derive the first key further includes the one or more parameters.

[0014] In one implementation of the first or second aspect, deriving the first key includes: if a first value of the NCC received from the source RB processor is equal to a second value of the NCC associated with the currently active first key, then deriving the first key based on the currently active first key and the downlink RB COUNT; or if the first value of the NCC received from the source RB processor is different from the second value of the NCC associated with the currently active first key, then calculating a new NH parameter by increasing the second value until the second value matches the first value, thereby synchronizing the local NH parameter, and calculating the first key based on the synchronized local NH parameter and the downlink RB COUNT.

[0015] In one implementation of the first or second aspect, the method further includes: if the anchor key changes, resetting the downlink RB COUNT to zero, resetting the second value of the NCC associated with the currently active first key to zero, and deriving a new first key based on the new anchor key.

[0016] According to a third aspect, a communication device is provided, the communication device having the function or module to perform the method in the first aspect or the second aspect or any implementation thereof.

[0017] According to a fourth aspect, a chip (system-on-a-chip) is provided. The chip includes at least one processor coupled to at least one memory. The at least one memory is used to store one or more instructions and / or executable computer code. The at least one processor is used to invoke the one or more instructions and / or executable computer code, causing a communication device on which the chip is mounted to perform a method of the first aspect or the second aspect, or any possible implementation thereof. Optionally, the chip may further include at least one memory. Optionally, the chip may further include a communication interface for inputting and / or outputting information or data.

[0018] According to a fifth aspect, a communication device is provided. The communication device includes one or more circuits and one or more communication interfaces. The one or more communication interfaces may include a first interface for receiving (i.e., inputting) information and / or data to be processed by the one or more circuits, and a second interface for transmitting (i.e., outputting) the information and / or data processed by the one or more circuits. The one or more circuits are used to process the information and / or data to be processed, causing the communication device to perform the methods of the first aspect or the second aspect or any implementation thereof.

[0019] According to a sixth aspect, a communication system is provided. The communication system may include at least one communication device according to the methods of the first and second aspects.

[0020] According to a seventh aspect, a computer storage medium is provided that stores executable computer code for performing one or more instructions of a method in the first aspect or the second aspect or any possible implementation thereof.

[0021] According to the eighth aspect, a computer program product comprising one or more instructions is provided, which, when run on a computer, causes the computer to perform the method of the first aspect or the second aspect or any possible implementation thereof. Attached Figure Description

[0022] One or more embodiments have been described by way of example with reference to the accompanying drawings. These exemplary illustrations and drawings do not constitute a limitation on the embodiments. Elements with the same reference numerals in the drawings are shown as similar elements, and the drawings are not limited to scale. Figure 1 This is a schematic diagram of an application scenario provided in the embodiments of this application.

[0023] Figure 2 An example of a communication system is shown.

[0024] Figure 3 Another example of an electronic device (ED) and a base station is shown.

[0025] Figure 4 This is an example of a channel model for a MIMO system.

[0026] Figure 5 This is an example of the conceptual architecture of a 6G system.

[0027] Figure 6 This is a schematic flowchart illustrating a communication method provided in some embodiments of this application.

[0028] Figure 7 This is a schematic flowchart illustrating a communication method provided in some embodiments of this application.

[0029] Figure 8 This is the key chain switching model provided in this application.

[0030] Figure 9 This is the RB key derivation process provided in the embodiments of this application.

[0031] Figure 10 This is an example of the RB key derivation process for the switching device provided in the embodiments of this application.

[0032] Figure 11 This is a schematic block diagram of a communication device provided in an embodiment of this application.

[0033] Figure 12 This is a schematic block diagram of a communication device provided in an embodiment of this application. Detailed Implementation

[0034] To better understand the features and technical content of the embodiments of this application, the implementation methods of the embodiments of this application will be described in detail below with reference to the accompanying drawings. The drawings are for reference and illustration only and are not intended to limit the embodiments of this application. In the following technical description, many details will be set forth for ease of explanation to provide a thorough understanding of the disclosed embodiments.

[0035] This application broadly relates to wireless communication. Many emerging trends will trigger consideration and design for future wireless networks, such as sixth-generation (6G) wireless networks. The proposed 6G wireless communication can meet the following requirements: - New network infrastructure capabilities, such as widely deployed cloud-native / cloud-friendly infrastructure; - New (relatively) mature technologies, such as large-scale models of artificial intelligence (AI), data privacy, blockchain, etc., have made significant progress and have had a major impact on society and human life as a whole. - New applications and services, such as AI services, data (sensing) services, and digital world services, are widely used in industries / businesses and by individual customers; - A more globalized / open / collaborative operating trend, namely, more open and collaborative operating models are becoming common practices in many fields.

[0036] New expectations and more stringent requirements for future networks have also driven a rethinking and development of next-generation wireless networks. These requirements may include: - Privacy and trustworthiness, etc.; - Simplified standardization; - Rapid deployment; -etc.

[0037] All of the above factors have driven research into 6G network architecture. The proposed 6G network architecture (centered on X) is based on service-based architecture (SBA) (XaaS services) and cloud-native principles. The requirements for 6G system network architecture design may include: - The proposed 6G network architecture needs to support new 6G services, which can be developed / deployed by third parties; - The proposed 6G network architecture needs to embrace a more open ecosystem and open its doors to technically capable third parties; - The proposed 6G network architecture needs to achieve better trusted management.

[0038] A solution is needed to achieve the above requirements.

[0039] In the third generation project partner (3GPP) 33.501[1], in the security handover mechanism of the 5th generation (5G) network, the AMF and UE must obtain And the next hop (NH) parameter. During handover within the gNB's centralized unit (CU), the gNB notifies the UE via a handover control message whether to use the existing key or generate a new key. In Xn handover, the serving gNB generates a new key based on knowledge of the {NH, NH chaining counter (NCC)} pair. At the end of the handover process, a message is sent to the AMF to update the UE's state, and this information is used to generate a new key during the next handover. In N2 handover, if the AMF in the serving gNB has not changed the active key... And no generation is required. If so, the AMF should increment its locally stored NCC value by 1 and calculate the fresh NH, then send the new {NH, NCC} pair to the target gNB for use in the switching process.

[0040] There are two alternative methods for key reset: horizontal key derivation and vertical key derivation. In horizontal key derivation, the current key is used to derive the input key for the next key using the target physical cell identifier (PCI) and downlink (DL) frequency. The drawback of this method is that forward security cannot be guaranteed, as learning the old key allows an attacker to derive all subsequent keys. In vertical key derivation, the new key is derived using intermediate NH parameters provided by the AMF. However, a jammer could potentially disrupt this process by sending messages containing {NH, NCC} or interfering with acknowledgment messages. Therefore, it is vulnerable to replay attacks.

[0041] In future systems, such as 6G systems, the shrinking coverage area, in addition to high-speed users within these networks, makes handover management a fundamental challenge for providing secure and seamless connectivity. Frequent changes in radio links can impact the performance of both horizontal and vertical key derivation. Therefore, the number of key resets will obviously increase, leading to a significant increase in network costs.

[0042] To address the aforementioned issues, this application should consider the following points: (1) In order to provide forward security in horizontal key derivation, the inputs of {PCI and DL frequencies} with the current key are insufficient to protect forward security. What inputs should we consider during horizontal key derivation that can achieve forward security? (2) In order to prevent the jammer from launching a replay attack during vertical key derivation, what methods can be used to confirm the freshness of messages during the handover? What information should be exchanged? (3) In 6G systems, high-speed users frequently hand over to small cells. This frequent handover necessitates extensive message exchange between the AMF and gNB for key reset. This approach is inflexible and incurs high costs. If we introduce a function (e.g., SPM-KMF) to handle key derivation during handover, in other words, the AMF and gNB should not participate in key derivation during handover. This function can be deployed on the core network side or the RAN side. Therefore, several issues need to be addressed, such as the following: - What information should be exchanged during the Xn handover? Should all parameters related to key derivation be derived by SPM-KMF? Who triggers the key reset? - What information should be exchanged during the N2 handover? Should all parameters related to key derivation be derived by the SPM-KMF? What information should be exchanged between the AMF and the SPM-KMF? This application provides several embodiments.

[0043] Example 1 provides the principle of key derivation during handover. This application provides a model of the handover key chain. Compared with key derivation in 5G handover, the differences are as follows: (1) The downlink RB COUNT is used as the input for key derivation, enabling the device to confirm the freshness of the message and prevent replay attacks, thereby protecting forward security. (2) The function of SPM-KMF is used instead of AMF / gNB in ​​5G to generate keys, which reduces the overhead of exchanging intermediate keys and key derivation parameters.

[0044] Example 2 provides further details to illustrate the following: Figure 6 The principle of key derivation during the switching process is explained. These details illustrate which operations SPM-KMF performs and which actions the device takes.

[0045] refer to Figure 1 This diagram, provided as an illustrative example and not as limiting, is a simplified schematic of a communication system. Communication system 100 includes a radio access network 120. Radio access network 120 may be a next-generation (e.g., sixth-generation, 6G, or later) radio access network or a traditional (e.g., 5G or 4G) radio access network. One or more electronic devices (EDs) 110a, 110b, 110c, 110d, 110e, 110f, 110g, 110h, 110i, 110j (generally referred to as 110) may interconnect with each other or be connected to one or more network nodes (170a, 170b, generally referred to as 170) within radio access network 120. Core network 130 may be part of the communication system and may depend on or be independent of the radio access technology used in communication system 100. Communication system 100 also includes a public switched telephone network (PSTN) 140, the Internet 150, and other networks 160.

[0046] Figure 2An exemplary communication system 100 is illustrated. Typically, the communication system 100 enables multiple wireless or wired components to transmit data and other content. The purpose of the communication system 100 may be to provide content such as voice, data, video, and / or text via broadcast, multicast, ensemble, unicast, etc. The communication system 100 can operate by sharing resources (e.g., carrier spectrum bandwidth) among its components. The communication system 100 may include terrestrial communication systems and / or non-terrestrial communication systems. The communication system 100 can provide a wide range of communication services and applications (e.g., earth monitoring, remote sensing, passive sensing and positioning, navigation and tracking, autonomous delivery and mobility, etc.). The communication system 100 can provide high availability and robustness through the joint operation of terrestrial and non-terrestrial communication systems. For example, integrating a non-terrestrial communication system (or components thereof) into a terrestrial communication system can enable a heterogeneous network comprising multiple layers. Compared to traditional communication networks, heterogeneous networks can achieve better overall performance through efficient multi-link joint operation, more flexible function sharing, and faster physical layer link switching between terrestrial and non-terrestrial networks.

[0047] Terrestrial communication systems and non-terrestrial communication systems can be considered subsystems of a communication system. Figure 5 In the example shown, communication system 100 includes electronic devices (EDs) 110a, 110b, 110c, and 110d (generally referred to as ED 110), radio access networks (RANs) 120a and 120b, a non-terrestrial communication network 120c, a core network 130, a public switched telephone network (PSTN) 140, the Internet 150, and other networks 160. RANs 120a and 120b include corresponding base stations (BSs) 170a and 170b, which may generally be referred to as terrestrial transmit and receive points (T-TRPs) 170a and 170b. The non-terrestrial communication network 120c includes an access node 172, which may generally be referred to as a non-terrestrial transmit and receive point (NT-TRP) 172.

[0048] Any ED 110 can be used alternatively or additionally to connect, access, or communicate with any T-TRP 170a and 170b, NT-TRP 172, Internet 150, core network 130, PSTN 140, other network 160, or any combination thereof. In some examples, ED 110a can perform uplink and / or downlink transmission with T-TRP 170a via terrestrial air interface 190a. In some examples, ED 110a, 110b, 110c, and 110d can also communicate directly with each other via one or more sidelink air interfaces 190b. In some examples, ED 110d can perform uplink and / or downlink transmission with NT-TRP 172 via non-terrestrial air interface 190c.

[0049] Air interfaces 190a and 190b can use similar communication technologies, such as any suitable wireless access technology. For example, communication system 100 can implement one or more channel access methods in air interfaces 190a and 190b, such as code division multiple access (CDMA), space division multiple access (SDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), and single-carrier FDMA (SC-FDMA) (or discrete fourier transform spread OFDMA (DFT-s-OFDMA)). Air interfaces 190a and 190b can utilize other high-dimensional signal spaces, which may involve combinations of orthogonal and / or non-orthogonal dimensions.

[0050] The non-terrestrial air interface 190c enables communication between the ED 110d and one or more NT-TRP 172s via a wireless link or a simple link. For some examples, the link is a dedicated connection for unicast transmission, a connection for broadcast transmission, or a connection between a group of ED 110s and one or more NT-TRP 172s for multicast transmission.

[0051] RANs 120a and 120b communicate with core network 130 to provide various services, such as voice, data, and other services, to EDs 110a, 110b, and 110c. RANs 120a and 120b and / or core network 130 may communicate directly or indirectly with one or more other RANs (not shown), which may or may not be directly served by core network 130 and may or may not use the same radio access technology as RANs 120a, RAN 120b, or both. Core network 130 may also serve as a gateway access between (i) RANs 120a and 120b or EDs 110a, 110b, and 110c, or both, and (ii) other networks (e.g., PSTN 140, Internet 150, and other networks 160). Furthermore, some or all of EDs 110a, 110b, and 110c may include the ability to communicate with different wireless networks via different radio links using different radio technologies and / or protocols. Instead of wireless communication (or other than wireless communication), ED 110a, 110b, and 110c can also communicate with service providers or exchanges (not shown) via wired communication channels and with the Internet 150. PSTN 140 may include a circuit-switched telephone network for providing plain old telephone service (POTS). The Internet 150 may include a network of computers and / or subnets (internal networks) and incorporate protocols such as Internet Protocol (IP), Transmission Control Protocol (TCP), and User Datagram Protocol (UDP). ED 110a, 110b, and 110c may be multimode devices capable of operating under various wireless access technologies and include multiple transceivers required to support these wireless access technologies.

[0052] Figure 3Another example of the ED 110 and base stations 170a, 170b, and / or 170c is shown. The ED 110 is used to connect people, objects, machines, etc. The ED 110 can be widely used in various scenarios, including, for example, cellular communication, device-to-device (D2D), vehicle-to-everything (V2X), peer-to-peer (P2P), machine-to-machine (M2M), machine-type communication (MTC), Internet of Things (IoT), virtual reality (VR), augmented reality (AR), mixed reality (MR), virtual reality, digital twins, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearable devices, smart transportation, smart cities, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery and mobility, etc.

[0053] Each ED 110 represents any suitable end-user equipment used for wireless operation and may include, for example (or may be referred to as), user equipment (UE), wireless transmit / receive unit (WTRU), mobile station, fixed or mobile subscriber unit, cellular phone, station (STA), machine type communication (MTC) device, personal digital assistant (PDA), smartphone, laptop, computer, tablet, wireless sensor, consumer electronics device, smart book, vehicle, car, truck, bus, train, or IoT device, wearable device (e.g., watch, glasses, head-mounted device, etc.), industrial equipment, or devices in or including the above-mentioned equipment (e.g., communication module, modem, or chip). Next-generation ED 110 may be referred to using other terms. Base stations 170a and 170b are T-TRPs, hereinafter referred to as T-TRP 170. Also in Figure 3As shown, NT-TRP is referred to below as NT-TRP 172. Each ED 110 connected to T-TRP 170 and / or NT-TRP 172 can be dynamically or semi-statically turned on (i.e., established, activated, or enabled), turned off (i.e., released, deactivated, or disabled), and / or configured in response to one or more of connectivity availability and connectivity necessity.

[0054] ED 110 includes a transmitter 201 and a receiver 203 coupled to one or more antennas 204. To avoid clutter, only one antenna 204 is shown in the figure. One, some, or all of the antennas 204 may also be panels. The transmitter 201 and receiver 203 may be integrated, for example, as a transceiver. The transceiver is used to modulate data or other content for transmission by at least one antenna 204 or a network interface controller (NIC). The transceiver is also used to demodulate data or other content received by at least one antenna 204. Each transceiver includes any suitable structure for generating signals for wireless or wired transmission and / or for processing signals received wirelessly or wiredly. Each antenna 204 includes any suitable structure for transmitting and / or receiving wireless or wired signals.

[0055] ED 110 includes at least one memory 208. Memory 208 stores instructions and data used, generated, or collected by ED 110. For example, memory 208 may store software instructions or modules for implementing some or all of the functions and / or embodiments described herein, and executed by one or more processing units (e.g., processor 210). Each memory 208 includes any suitable one or more volatile and / or non-volatile storage devices with one or more retrieval devices. Any suitable type of memory can be used, such as random access memory (RAM), read-only memory (ROM), hard disk, optical disk, subscriber identity module (SIM) card, memory stick, secure digital (SD) memory card, on-processor cache, etc.

[0056] ED 110 may also include one or more input / output devices (not shown) or interfaces (e.g., connected to...). Figure 1(Wired interface of Internet 150 in the network). Input / output devices or interfaces can interact with users or other devices in the network. Each input / output device or interface includes any suitable structure for providing or receiving information from the user, and / or for network interface communication. Suitable structures include, for example, speakers, microphones, keypads, keyboards, displays, touchscreens, etc.

[0057] ED 110 includes a processor 210 for performing operations related to: preparing uplink transmissions to NT-TRP 172 and / or T-TRP 170, processing downlink transmissions received from NT-TRP 172 and / or T-TRP 170, and processing sidelink transmissions with another ED 110. Processing operations related to preparing uplink transmissions may include operations such as encoding, modulation, transmit beamforming, and generating symbols for transmission. Processing operations related to processing downlink transmissions may include operations such as receive beamforming, demodulation, and decoding of received symbols. According to an embodiment, the downlink transmissions may be received by receiver 203 possibly using receive beamforming, and processor 210 may extract signaling from the downlink transmissions (e.g., by detecting and / or decoding signaling). Examples of signaling may be reference signals transmitted by NT-TRP 172 and / or T-TRP 170. In some embodiments, processor 210 performs transmit beamforming and / or receive beamforming based on beam direction indications received from T-TRP 170, such as beam angle information (BAI). In some embodiments, processor 210 may perform operations related to network access (e.g., initial access) and / or downlink synchronization, such as operations related to detecting synchronization sequences, decoding, and acquiring system information. In some embodiments, processor 210 may perform channel estimation, for example, using reference signals received from NT-TRP 172 and / or T-TRP 170.

[0058] Although not shown, processor 210 may form part of transmitter 201 and / or receiver 203. Although not shown, memory 208 may form part of processor 210.

[0059] The processor 210, the processing components of the transmitter 201, and the processing components of the receiver 203 may each be implemented by one or more processors, which are used to execute instructions stored in memory (e.g., in memory 208). Alternatively, some or all of the processor 210, the processing components of the transmitter 201, and the processing components of the receiver 203 may each be implemented using dedicated circuitry, such as a programmable field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a graphics processing unit (GPU), or a hardware accelerator such as an artificial intelligence (AI) accelerator.

[0060] In some implementations, the T-TRP 170 can use other names, such as base station, basetransceiver station (BTS), wireless base station, network node, network device, network-side device, transmit / receive node, Node B, evolved Node B (eNodeB or eNB), home eNodeB, next-generation Node B (gNB), transmission point (TP), site controller, access point (AP), wireless router, relay station, ground node, ground network device, ground base station, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. The T-TRP 170 can be a macro BS, pico BS, relay node, host node, or a combination thereof. T-TRP 170 may refer to the aforementioned equipment or a device within the aforementioned equipment (e.g., a communication module, modem, or chip).

[0061] In some embodiments, the various parts of T-TRP 170 may be distributed. For example, some modules of T-TRP 170 may be located remotely from the device housing the antenna 256 of T-TRP 170 and may be coupled to the device housing the antenna 256 via a communication link (not shown) (sometimes referred to as a fronthaul, such as a Common Public Radio Interface (CPRI)). Therefore, in some embodiments, the term T-TRP 170 may also refer to modules on the network side that perform processing operations such as ED110 location determination, resource allocation (scheduling), message generation, and encoding / decoding, which are not necessarily part of the device housing the antenna 256 of T-TRP 170. These modules may also be coupled to other T-TRPs. In some embodiments, T-TRP 170 may actually be multiple T-TRPs that operate together, for example, by using the Cooperative Multicast Service ED 110.

[0062] T-TRP 170 includes at least one transmitter 252 and at least one receiver 254 coupled to one or more antennas 256. To avoid drawing clutter, only one antenna 256 is shown in the figure. One, some, or all of the antennas 256 may also be panels. The transmitter 252 and receiver 254 may be integrated as a transceiver. T-TRP 170 also includes a processor 260 for performing operations including: preparing transmissions for downlink transmission to ED 110, processing uplink transmissions received from ED 110, preparing transmissions for backhaul transmission to NT-TRP 172, and processing transmissions received from NT-TRP 172 via backhaul. Processing operations related to preparing for downlink or backhaul transmissions may include operations such as encoding, modulation, precoding (e.g., multiple-input multiple-output (MIMO) precoding), transmit beamforming, and generating symbols for transmission. Processing operations related to uplink transmissions or transmissions received via backhaul transmissions may include operations such as receive beamforming, demodulation, and decoding of received symbols. Processor 260 may also perform operations related to network access (e.g., initial access) and / or downlink synchronization, such as generating the contents of a synchronization signal block (SSB), generating system information, etc. In some embodiments, processor 260 also generates a beam direction indication (e.g., BAI), which can be scheduled by scheduler 253 for transmission. Processor 260 performs other network-side processing operations described herein, such as determining the location of ED 110, determining the deployment location of NT-TRP 172, etc. In some embodiments, processor 260 may generate signaling, such as configuring one or more parameters of ED 110 and / or one or more parameters of NT-TRP 172. Any signaling generated by processor 260 is transmitted by transmitter 252. It should be noted that the term "signaling" as used herein may also be referred to as control signaling. Signaling can be transmitted in physical layer control channels (e.g., physical downlink control channel (PDCCH)). In this case, the signaling can be called dynamic signaling. Signaling transmitted in the downlink physical layer control channel can be called downlink control information (DCI). Signaling transmitted in the uplink physical layer control channel can be called uplink control information (UCI). Signaling transmitted in the sidelink physical layer control channel can be called sidelink control information (SCI).Signaling can be included in higher-layer (e.g., above the physical layer) data packets transmitted in physical layer data channels (e.g., in the physical downlink shared channel, PDSCH). In this case, the signaling can be referred to as higher-layer signaling, static signaling, or semi-static signaling. Higher-layer signaling can also refer to radio resource control (RRC) protocol signaling or media access control-control element (MAC-CE) signaling.

[0063] Scheduler 253 may be coupled to processor 260. Scheduler 253 may be included within or operate separately from T-TRP 170. Scheduler 253 may schedule uplink, downlink, lateral link, and / or backhaul transmissions, including issuing scheduling authorizations and / or configuring scheduling-free (e.g., "configured authorization") resources. T-TRP 170 also includes memory 258 for storing information and data. Memory 258 stores instructions and data used, generated, or collected by T-TRP 170. For example, memory 258 may store software instructions or modules executed by one or more processors 260 for implementing some or all of the functions and / or embodiments described herein.

[0064] Although not shown, processor 260 may form part of transmitter 252 and / or receiver 254. Furthermore, although not shown, processor 260 may implement scheduler 253. Although not shown, memory 258 may form part of processor 260.

[0065] The processing components of processor 260, scheduler 253, transmitter 252, and receiver 254 may each be implemented by one or more processors, which may be the same or different, for executing instructions stored in memory (e.g., memory 258). Alternatively, some or all of the processing components of processor 260, scheduler 253, transmitter 252, and receiver 254 may be implemented using dedicated circuitry such as a programmable FPGA, hardware accelerator (e.g., GPU or AI accelerator), or ASIC.

[0066] Although the NT-TRP 172 is shown as an example of a drone only, it can be implemented in any suitable non-terrestrial form, such as satellites and high-altitude platforms, including international mobile communication base stations and unmanned aerial vehicles. Furthermore, in some implementations, the NT-TRP 172 may use other names, such as a non-terrestrial node, a non-terrestrial network device, or a non-terrestrial base station. The NT-TRP 172 includes a transmitter 272 and a receiver 274 coupled to one or more antennas 280. To avoid cluttering the drawing, only one antenna 280 is shown. One, some, or all of the antennas may also be panels. The transmitter 272 and receiver 274 may be integrated as a transceiver. The NT-TRP 172 also includes a processor 276 for performing operations including: preparing transmissions for downlink transmission to ED 110, processing uplink transmissions received from ED 110, preparing transmissions for backhaul transmission to T-TRP 170, and processing transmissions received from T-TRP 170 via backhaul. Processing operations related to preparing for downlink or backhaul transmission may include operations such as encoding, modulation, precoding (e.g., MIMO precoding), transmit beamforming, and generating symbols for transmission. Processing operations related to processing transmissions received during uplink transmission or via backhaul transmission may include operations such as receive beamforming, demodulation, and decoding of received symbols. In some embodiments, processor 276 performs transmit beamforming and / or receive beamforming based on beam direction information (e.g., BAI) received from T-TRP 170. In some embodiments, processor 276 may generate signaling, such as configuring one or more parameters of ED 110. In some embodiments, NT-TRP 172 implements physical layer processing but does not implement higher-layer functions, such as medium access control (MAC) or radio link control (RLC) layer functions. Since this is only an example, more generally, NT-TRP 172 may implement higher-layer functions in addition to physical layer processing.

[0067] The NT-TRP 172 also includes a memory 278 for storing information and data. Although not shown, a processor 276 may form part of the transmitter 272 and / or receiver 274. Although not shown, the memory 278 may form part of the processor 276.

[0068] The processor 276, the processing components of the transmitter 272, and the processing components of the receiver 274 may each be implemented using one or more processors, which are the same or different, to execute instructions stored in memory (e.g., in memory 278). Alternatively, some or all of the processor 276, the processing components of the transmitter 272, and the processing components of the receiver 274 may be implemented using dedicated circuitry such as a programmable FPGA, hardware accelerator (e.g., a GPU or AI accelerator), or ASIC. In some embodiments, the NT-TRP 172 may actually be multiple NT-TRPs that operate together to serve ED 110, for example, through cooperative multicast.

[0069] T-TRP 170, NT-TRP 172 and / or ED 110 may include other components, but for clarity these components are omitted.

[0070] according to Figure 4 One or more steps of the methods in the various embodiments provided herein can be performed by the corresponding units or modules. Figure 4 Units or modules in the device are shown, such as in ED 110, T-TRP 170, or NT-TRP 172. For example, signals may be transmitted by a transmitting unit or transmitting module. Signals may be received by a receiving unit or receiving module. Signals may be processed by a processing unit or processing module. Other steps may be performed by an artificial intelligence (AI) or machine learning (ML) module. The corresponding units or modules may be implemented using hardware, one or more components or devices executing software, or a combination thereof. For example, one or more units or modules in the unit or module may be circuits such as integrated circuits. Examples of integrated circuits include programmable FPGAs, GPUs, or ASICs. For example, one or more units or modules in the unit or module may be logic, such as logical functions executed by circuits, a portion of an integrated circuit, or software instructions executed by a processor. It should be understood that if the above modules are implemented using software executed by a processor, etc., these modules may be retrieved by the processor, wholly or partially, individually or collectively, for processing, or in one or more instances as needed, and these modules themselves may include instructions for further deployment and instantiation.

[0071] Further details regarding ED 110, T-TRP 170, and NT-TRP 172 are known to those skilled in the art. Therefore, these details are omitted herein.

[0072] The solutions described in this application are applicable to next-generation (e.g., 6G or higher) networks or traditional (e.g., 5G or 4G) networks.

[0073] The proposed 6G system architecture is defined as supporting 6G XaaS services through the use of technologies such as network function virtualization and network slicing. The 6G system architecture utilizes service-based interactions between 6G services.

[0074] 6G systems utilize a service-based architecture and the XaaS concept. XaaS services in 6G systems are categorized into three layers. Figure 5 The conceptual architecture of a 6G system is shown.

[0075] The infrastructure layer includes the infrastructure that supports 6G services. This includes wireless network infrastructure (e.g., RAN, CN), cloud / data center infrastructure, satellite networks, storage / database infrastructure, and sensing networks. This infrastructure can be provided by a single provider or multiple providers.

[0076] Each of these infrastructures can have its own control and management functions, represented as control and management (C / M) functions, for infrastructure management. Each of these infrastructures is an Infrastructure as a Service.

[0077] The C / M layer includes control and management services for the 6G system. These are developed and deployed using slicing technology and leverage resources provided by the infrastructure layer. 6G services in the C / M layer may include: Resource management (RM) as a service provides lifecycle management of various slices and the ability to allocate over-the-air resources to wireless devices; - A 6G task is defined as a service provided by a 6G system to a customer. A task can be a type of service provided by a single 6G XaaS service, or a type of service that requires contributions from multiple XaaS services. - Mission management (MM) is a service that provides the ability to provide mission services by delivering XaaS services at the service layer.

[0078] - Confederation Network (CONET) as a service provides the ability for multiple partners to jointly deliver 6G services. This capability is provided through the negotiation of federation formation, mutual authentication and authorization among partners, and protocols for recording and backtracking selected actions performed by partners, ensuring a trusted environment for the operation of 6G systems.

[0079] Service provisioning management (SPM) is a service that provides control and management over customer access to 6G services and the provision of requested services. This capability is provided through unified mutual authentication, authorization and policies, key management, quality of service (QoS) guarantees, and billing between any pair of XaaS service providers and customers. Customers include not only end customers in the physical world but also digital representatives in the digital world.

[0080] - Connectivity management (CM) as a service leverages 5G connectivity management capabilities but extends to include the digital world.

[0081] Protocol as a Service (PCA) provides the ability to customize protocol stacks for interface design services.

[0082] - Protocol stacks can be predefined for selection on demand, or designed on demand.

[0083] - Cybersecurity as a Service provides infrastructure owners with the ability to detect potential security risks to their infrastructure.

[0084] XaaS services in the C / M layer support the control and management of the 6G system itself and provide support to vertical services upon request. For example, the RM service can provide air resource management services to the RAN, and also provide services to vertical services to enable the allocation of air resources to their end customers. XaaS in the C / M layer can be deployed using slicing technology.

[0085] The service layer includes 6G services provided to customers. In the 6G system conceptual architecture: - AI services are represented as NET4AI as a Service. Artificial intelligence services provide AI capabilities to support a wide range of AI applications.

[0086] - Data collection, data cleansing, data analysis, and data delivery services are referred to as DAM as a service. This service provides the ability to manage the lifecycle of statistical data, including acquiring, de-privatizing, analyzing, and delivering statistical data from any type of sensor, device, network function, etc.

[0087] - Data storage and sharing services are represented as NET4Data as a Service, which provides the ability to store and share data reliably under the control of the data owner and in accordance with the regulations of recognized authorities regarding the control of data identification.

[0088] - Services that provide access to the digital world are represented as NET4DW as a Service. Digital world services provide the ability to build, control, and manage the digital world. The digital world is defined as the digital realization of the physical world.

[0089] - The 6G blockchain service is represented as NET4BC as a service. The 6G connectivity service is represented as NET4Con as a service. This service provides the capability to support 6G blockchain services.

[0090] - Enhanced connectivity services, such as Connectivity Network (NET4CON) as a service. This service provides the ability to exchange messages and data between supporting new 6G services.

[0091] All XaaS services in this layer are developed and deployed using resources provided within the infrastructure and leveraging network function virtualization and slicing technologies. The capabilities of each 6G service are provided by its control and management functions and service-specific data processing capabilities.

[0092] In addition to supporting 6G XaaS services at the service layer, the 6G system also utilizes the 5G system to provide vertical services. The difference between 6G XaaS services and other vertical services is that a vertical service is a pure client that requires other XaaS services to support its operation, while each service in the XaaS service provides its capabilities to the 6G client.

[0093] In a 6G system, any pair of XaaS services can also act as both customer and provider to each other. Some examples include infrastructure owners providing their resources to XaaS services in the service layer and C / M layer; RM services potentially requiring the capabilities provided by NET4AI, DAM, and NET4DW for vertical slice resource management; and CONET and NET4Data services potentially requiring the capabilities provided by NET4BC to function.

[0094] Key concepts of 6G systems may include: - Basic XaaS services are defined by decoupling comprehensive types of services into basic XaaS services. Basic XaaS services provide unique capabilities to enable specific types of services, such as NET4AI services, NET4DW services, DAM services, NET4Data services, blockchain services, task management services, etc.

[0095] -Supports multiple partners to jointly operate the 6G system.

[0096] - Define the data plane of the 6G system, including the data plane processing capabilities of XaaS services. By programming the interconnection of these capabilities through task management services, various customized customer services can be supported.

[0097] -Simplify the 6G system architecture by classifying basic control and management services and combining them into basic XaaS services in the control and management (C / M) layer; - Define the C / M plane of the 6G system, which includes C / M functionality in XaaS services and may include 5G CP (e.g., AMF) depending on the implementation options.

[0098] - Define the basic architecture structure (BAS), which is a unified basic structure with a minimal number of interfaces and is independent of the infrastructure type.

[0099] - The BAS concept simplifies the standardization, development, and deployment of 6G systems, while supporting a variety of infrastructure deployment scenarios.

[0100] - By applying BAS or subsets of it to the infrastructure based on the capabilities, capacity, and needs of the infrastructure network, it can be adapted to a variety of deployment scenarios.

[0101] -Utilize the SBI interface concept and apply SBI interaction in the 6G C / M plane and 6G data plane.

[0102] -Simplify the SBI interface by introducing a trusted GW in the data plane and C / M plane of the 6G system.

[0103] - Improve trustworthiness from the perspective of 6G system operation by introducing CONET capabilities, NET4BC capabilities and anonymity service configurations provided by a trusted GW into the C / M plane and data plane of the 6G system.

[0104] - Enhance trustworthiness from the perspective of end-customer privacy protection by providing unified mutual authentication, IDM, data cleansing, etc. through SPM service, DAM service and 6G blockchain service.

[0105] - Simplify roaming management of wireless devices in the physical and digital worlds through unified authentication (including all participating partners and customers).

[0106] - By defining multiple architecture options, it supports multiple development paths from 5G systems to 6G systems, requiring minimal work due to the introduction of the BAS concept.

[0107] - By leveraging the advantages of SBA and its additional features, backward compatibility is supported. 5G users can use 6G systems to access 5G services.

[0108] - Supporting future expansion by adding new XaaS services minimizes the impact on standardization and deployment, thanks to the anonymous service configuration concept introduced in the Trusted GW implemented in the 6G C / M plane and 6G data plane.

[0109] To address the aforementioned issues, this application provides the following key points.

[0110] First, in order to provide forward security in horizontal key derivation and prevent jammers from launching replay attacks in vertical key derivation, this application introduces a parameter in key derivation, which is described as downlink RBCOUNT in the following embodiments.

[0111] Furthermore, in future systems, small cells with high-speed users will lead to frequent handovers. Frequent handovers necessitate extensive message exchanges between the AMF and gNB for key resets, which is inflexible and costly. Therefore, this application introduces a network function, described in the following embodiments as a service provisioning management-key management (SPM-KMF) function, responsible for key derivation during handover. In other words, the AMF and gNB should not participate in key derivation during handover. This network function can be deployed on the core network side or the RAN side, without limitation.

[0112] The following embodiments provide a principle for key derivation during handover. First, a model for the handover key chain is provided. Compared with the 5G system, there are two differences: (1) the downlink (DL) RBCOUNT (which can also be represented as a DL RB counter) as input to the key derivation enables the device to verify the freshness of the message, prevent replay attacks, and protect forward security; (2) the network function of SPM-KMF, instead of AMF and / or gNB in ​​the 5G system, is responsible for key derivation, which can reduce the overhead of intermediate key exchange and the overhead of parameters used for key derivation.

[0113] The proposed solution is applicable to future networks, such as 6G systems or subsequent networks, or to traditional networks, such as 5G systems, 4G systems, etc.

[0114] The definitions in this application are as follows: (1) RB Processor: Defined as the logical function that performs radio bearer (RB) protocol stack operations after obtaining the configuration.

[0115] (2) C / M Radio Bearer (C / M RB): an air connection used to carry control signaling for air interface management and C / M plane messages.

[0116] (3) Data Radio Bearer (Data RB): an over-the-air connection used to carry data plane traffic.

[0117] (4) C / M session: The secure logical connection between the device and its service C / M-TW-GW.

[0118] (5) Service Control and Management (C / M) - Trustworthiness (TW) - Gateway (GW): The endpoint of the network-side device C / M session. The device C / M session is between the device and the service CM-TW-GW.

[0119] (6) Data session: The secure logical connection between the device and its service Data-TW-GW.

[0120] (7) Service Data-TW-GW: The endpoint of the device’s data session.

[0121] (8) Security context: The state established locally in the device and service network domain.

[0122] (9) C / M RB security context: RB processor-level encryption keys and their identifiers, NH parameters, next-hop (NH) access key derivation, identifiers of RB processor-level encryption algorithms, device security capabilities, etc.

[0123] (10) Anchor Key It should be identified by a 6G key set identifier (referred to as 6gKSI). 6gKSI can be similar to "ngKSI" in a 5G system. The 6g KSI should be stored in the device and the CM-TW-GW being disconnected, as well as... (If available) The anchor key provided to the CM-TW-GW service should also be for authentication occurring between the device and the 6G system.

[0124] (11) Key of RB Processor: Should be defined as key of RB processor, expressed as .

[0125] (12) SPM-KMF: Network function, responsible for key generation, key revocation, key reset and security context management, such as C / M RB security context.

[0126] Figure 6This is a schematic flowchart illustrating a communication method provided in some embodiments of this application. The method can be implemented by a first network function responsible for key derivation, or by a chip (or chip system) installed within the first network function. For example, the first network function can be SPM-KMF, as described above. The SPM-KMF in the following embodiments can be a distributed deployment, and this is not limited.

[0127] In step 110, the first network function obtains first information from the source RB processor. The first information includes a downlink RB counter, denoted as downlink RB COUNT in the following embodiments. The downlink RB COUNT indicates the number of RBs transmitted in the downlink.

[0128] In step 120, the first network function derives the first key based on the first information.

[0129] The first key is used to derive the terminal key, and the terminal key is used for communication between the device and the target RB processor. The inputs used to derive the first key include the downlink RB COUNT.

[0130] In one implementation, the first network function derives the first key based on first information including the downlink RB COUNT.

[0131] In another implementation, the first network function derives a first key based on first information including the downlink RB COUNT and second information from the source RB processor. The second information includes one or more of the following parameters: the PCI of the target RB processor (simplified as PCI in the following embodiments), the DL frequency of the target RB processor (simplified as DL frequency in the following embodiments), or the next hop chaining counter (NCC).

[0132] It should be noted that in the first implementation, PCI is not one of the factors leading to the derivation of the first key. In other words, regardless of whether the PCI changes, the derivation of the first key depends on the downlink RB COUNT. If the downlink RB COUNT changes, the device derives a new first key, and then a new terminal key. However, in the latter case, PCI is one of the factors leading to the derivation of the new first key. For example, the first network function derives a new first key if the PCI changes.

[0133] The method may also include step 130.

[0134] In step 130, the first network function derives the terminal key based on the first key.

[0135] The terminal key is derived from the first key. Furthermore, if the first key changes, the first network can derive a new terminal key based on the new first key. The terminal key includes a C / M RB key and a data RB key. Both the C / M RB key and the data RB key are used for communication from the device to the RB processor. The C / M RB key is used to encrypt control signaling between the device and the RB processor. The data RB key is used to encrypt data plane traffic between the device and the RB processor.

[0136] The method may also include step 140.

[0137] In step 140, the first network function sends the terminal key to the target RB processor.

[0138] Figure 2 The process of deriving the first key or terminal key for the device is given in the document.

[0139] Figure 7 This is a schematic flowchart illustrating a communication method provided in some embodiments of this application. The method can be implemented by a device or chip (or chip system) installed in the device.

[0140] In step 210, the device obtains first information from the source RB processing program. The first information includes the downlink RB COUNT.

[0141] In step 220, the device derives the first key based on the first information.

[0142] The first key is used to derive the terminal key, and the terminal key is used for communication between the device and the target RB processor.

[0143] In one implementation, the device derives a first key based on first information including the downlink RB COUNT. In another implementation, the device derives the first key based on the first information including the downlink RB COUNT and second information from the source RB processor. The second information includes one or more of the following parameters: PCI, DL frequency, or next hop chaining counter (NCC).

[0144] It's important to note that in the first implementation, PCI is not one of the factors leading to the derivation of the first key. In other words, regardless of whether the PCI changes, the derivation of the first key depends on the downlink RB COUNT. If the downlink RB COUNT changes, the device derives a new first key, and then a new terminal key. However, in the latter case, PCI is one of the factors leading to the derivation of the new first key. For example, the device may derive a new first key even if the PCI changes.

[0145] Specifically, the device can derive the first key as follows: if the first value of the NCC received from the source RB processor is equal to the second value of the NCC associated with the currently active first key, then the device derives the first key based on the currently active first key and the downlink RB processor, or the device derives the first key based on the currently active first key, the downlink RB processor, and the second information; or If the first value of NCC received from the source RB processor is different from the second value of NCC associated with the currently active first key, the device calculates a new HN parameter by incrementing the second value until the second value matches the first value. Then, the device calculates the first key based on the synchronized local NH parameter and the downlink RB COUNT, thereby synchronizing the local NH parameter. Alternatively, the device calculates the first key based on the currently active first key, the downlink RB processor, and the second information.

[0146] The method may also include step 230.

[0147] In step 230, the device derives the terminal key based on the first key.

[0148] The terminal key is derived from the first key. Furthermore, if the first key changes, the first network can derive a new terminal key based on the new first key.

[0149] refer to Figure 8 This example, provided as an illustrative example but not a limitation, illustrates a specific model for switching key chains. Whenever an initial C / M RB security context needs to be established between the device and the RB handler, and the local SPM-KMF, the device should derive... And the next hop parameter. and NH are from Derived. The NH chaining counter (NCC) is associated with each RB process and NH parameter. Each And derived from it The corresponding NCC value is associated with this value. During initial setup, From The terminal key is directly derived and then considered to be associated with a virtual NH parameter where the NCC value is equal to zero. The local SPM-KMF generates a terminal key and sends it to the serving RB handler (or RB endpoint). The device and the serving RB handler use the terminal key to ensure secure communication between them. Here, the terminal key used between the device and the serving RB handler includes the C / M RB key and the data RB key.

[0150] When switching or when the downlink RB COUNT value is close to flipping, the communication between the device and the target RB handler will use... The foundation (called ) is from the currently active Or derived from the NH parameter. If If the derivation is from the NH parameters, then the derivation is called vertical key derivation. The NH parameters can only be calculated by the device and the local SPM-KMF.

[0151] In a handover with vertical key derivation, NH is used as a service RB processor. Previously, it was further bound to downlink RB COUNT, PCI, and DL frequencies. In handovers with horizontal key derivation, the current or active... In the service RB handler Previously, it was further bound to the downlink RB COUNT, PCI, and DL frequencies. After the switchover, the serving RB handler should increment its locally stored NCC value by 1 and send the NCC value to the local SPM-KMF. The local SPM-KMF uses the received NCC value to calculate... .

[0152] It should be noted that if If the anchor key changes, the local SPM-KMF should reset the NCC to zero. The NCC should then be sent by the local SPM-KMF to the service RB handler along with the new terminal key.

[0153] Terminal key refresh should be triggered by a new anchor key, or by synchronizing the C / M session and C / M RB security context as part of the handover process, or by the downlink RB COUNT value approaching a bypass, or by a new service RB handler from the current service GW.

[0154] In summary, Figure 8 The principle of key derivation during the handover process is provided. This application provides a model of the handover key chain. Compared with the handover key derivation in the 5G system, the differences are as follows: (1) The downlink RB COUNT is used as the input for key derivation, enabling the device to confirm the freshness of the message, prevent replay attacks, and protect forward security. (2) The function of SPM-KMF is used instead of AMF / gNB in ​​the 5G system to generate keys, which reduces the overhead of intermediate key exchange and the overhead of parameters used for key derivation.

[0155] Figure 10 This is the RB key derivation process provided in the embodiments of this application. Further details are provided in this embodiment. Figure 9 The principle of key derivation during the switching process. The new key for the service RB handler can be derived from the new anchor key or NH or . Figure 10 The messages are listed in Table 1.

[0156] Table 1

[0157] In step 401, the service RB handler sends message 1 to the local SPM-KMF.

[0158] Message 1 includes Content 1, and Content 1 may include a downlink RB COUNT value. Content 1 may also include one or more of the following parameters: PCI, DL frequency, or NCC. Message 1 may be triggered under switching conditions, by a downlink RB COUNT value near the winding, or by a new serving RB handler from the current serving GW, without limitation. If a terminal key refresh is required due to a new anchor key, step 401 is skipped.

[0159] In step 402, SPM generates a first key and can also generate a new terminal key.

[0160] Specifically, if the anchor key remains unchanged, the local SPM-KMF should be derived using NH. If an unused {NH, NCC} pair exists (this is called vertical key derivation), otherwise if no unused {NH, NCC} is available, the local SPM-KMF should be derived from the current key. Derivation (This situation is called horizontal key derivation.) Local SPM-KMF should be based on the new... Generate a new terminal key.

[0161] It should be noted that the service RB processing procedure should be used for The derived NCC is sent to the device in the HO command message. Local SPM-KMF and the device should use... As after the switch .

[0162] In step 403, the local SPM-KMF should send a message to the service RB handler.

[0163] Message 2 may include a new terminal key. If a new anchor key is generated, message 2 may also have an NCC value (NCC=0).

[0164] In step 404, the service RB handler stores the NCC and the new terminal key.

[0165] If the NCC value is zero, the serving RB handler can set the downlink RB COUNT value to zero. It should be noted that if the serving RB handler sends an RB to the device, it will increment the downlink RB COUNT value by 1.

[0166] In step 405, the device behaves as follows: If the anchor key changes, the device derives a new anchor key. For example, anchor key binding can be implemented by including a parameter called "Service CM-TW-GW Name" in the key derivation chain of the anchor key. The device resets the uplink / downlink C / M session COUNT to zero, the NCC to zero, and the downlink RB COUNT to zero. The device derives a new terminal key for the RB handler based on the new anchor key.

[0167] If the anchor key remains unchanged, the device can perform the following actions: If the NCC value received by the device in the message from the service RB handler is equal to the currently active value... The associated NCC value indicates that the device should be activated from the currently active NCC value. Derivation of the current downlink RB COUNT, target PCI, and its absolute radio frequency channel number (ARFCN) - DL / E-UTRA absolute radio frequency channel number (EARFCN) - DL ; If the received NCC value is different from the currently active one... If an associated NCC is involved, the device should first synchronize the locally stored NH parameter by calculating the new NH value by incrementing the locally stored NCC value until it matches the NCC value received from the message. When the locally stored NCC value matches the NCC value received from the message, the device should calculate the new NH based on the synchronized local NH parameter and the current downlink RB COUNT. Optionally, the device should calculate based on the synchronization NH parameters and the current downlink RBCOUNT, target PCI, and DL frequencies. .

[0168] Figure 11 More details are provided to illustrate this. Figure 9 The principle of key derivation during the switching process is explained. These details illustrate which operations SPM-KMF performs and which actions the device takes.

[0169] Figure 11 This is an example of the RB key derivation process for a switching device provided in an embodiment of this application. During the handover preparation, the source RB handler requests to transfer the device to the target RB handler, and the SPM-KMF provides the target RB handler with a newly derived terminal key for use with the device.

[0170] exist Figure 11 In this context, KDF stands for "Key Derivation Function". The symbol {} indicates an optional option.

[0171] In step 501, the SPM-KMF receives first information from the source RB processor. The first information includes the downlink RB COUNT. The first information may also include the PCI of the target RB processor and / or the DL frequency of the target RB processor.

[0172] In step 502, SPM-KMF obtains the uplink C / M session COUNT from C / M-TW-GW.

[0173] In step 503, SPM-KMF derives the first key and derives the terminal key based on the first key.

[0174] If horizontal key derivation is used, then the first key, i.e. The derivation is as follows: = KDF( Downlink RB COUNT, {PCI, DL frequency}).

[0175] If vertical key derivation is used, then The derivation is as follows: = KDF(NH, ).

[0176] SPM-KMF further derives the terminal key used for communication between the device and the target RB processor.

[0177] In step 504, SPM-KMF sends the newly derived terminal key to the target RB processor.

[0178] In step 505, SPM-KMF sends an uplink C / M session COUNT to the source RB processor.

[0179] In step 506, the source RB processor sends a downlink RB COUNT and NCC to the device. The source RB processor may also send a PCI and / or an uplink C / M session COUNT to the device.

[0180] In step 507, the device derives the first key and can also derive the terminal key based on the first key.

[0181] The equipment calculates the relevant parameters in the following ways: = KDF( Uplink C / M session COUNT); = KDF( ,NH) or KDF ( ,NH).

[0182] Further, the calculation is as follows: : = KDF( Downlink RB COUNT, {PCI, DL frequency}), or = KDF(NH, ).

[0183] As mentioned above, {PCI, DL frequency} represents the PCI and DL frequencies used in the derivation. Optional parameters.

[0184] Figure 11 It shows the relationship with Figure 10 The corresponding protocol message for RB key derivation during the handover process. During handover preparation, the source RB handler requests to transfer the device to the target RB handler, and SPM-KMF provides the target RB handler with a newly derived RB key for use with the device.

[0185] Prior to handover, an RB key derived by the device and SPM-KMF should be established. All participating entities (e.g., device, serving RB handler, and SPM-KMF) may have information acquired from their previous exchanges, including parameters used for key derivation during initial establishment or for resetting keys from previous handovers. This means that entities share the necessary parameters and keys for secure communication and future key resets. However, the target RB handler does not need any prior knowledge of the parameters of the device or other participants, as long as it is securely connected to the core network. In 3GPP, handover always includes a reset of the RB key, whether from the key itself (called horizontal key derivation) or from intermediate NH parameters (called vertical key derivation). This process may also occur during handover or when the SPM-KMF updates its RB key. Re-derive .

[0186] The methods proposed in the embodiments of this application have been described in detail above. The communication device provided in this application will be described in detail below.

[0187] Figure 12This is a schematic block diagram of the communication device 10 provided in an embodiment of this application. The communication device may be a communication equipment or a device applied to a communication equipment and capable of implementing the corresponding function of any network function in the embodiments of this application. For example, the device may be a chip, a chip system, or a circuit, etc., and is not limited thereto. The communication equipment may be an SPM-KMF, a terminal device, or a chip installed in any of these network functions.

[0188] The communication device 10 includes a processing module 1001. The processing module 1001 may be a processor, processing circuit, processing board, processing unit, or processing device, etc. The processing module 1001 is used to implement processing and / or operations within the communication device, excluding transmission and reception actions.

[0189] The communication device 10 may further include a communication module 1002. The communication module 1002 is used to perform sending and / or receiving operations. The communication module 1002 may also be called a transceiver module, transceiver, or transceiver device, etc., and is used to perform receiving (which may be called input) and / or sending (which may be called output) operations.

[0190] For example, if communication device 10 corresponds to the first network function in the embodiment (e.g., SPM-KMF), then communication module 1002 is used to obtain first information from the source RB processor, such as... Figure 6 As shown in step 110. The communication module 1002 is also used to send a terminal key to the target RB processor. The processing module 1001 is used to implement steps 120 to 130 above.

[0191] For example, if communication device 10 corresponds to the terminal device in the embodiment, then communication module 1002 can be used to obtain first information from the source RB processing program, such as... Figure 7 As shown in step 210. Processing module 1001 can be used to implement... Figure 7 Steps 220 and 230 in the process.

[0192] In short, the operation and / or function of device 10 are designed to implement the corresponding steps of the above-described method embodiments.

[0193] Figure 13 is a schematic block diagram of a communication device provided in an embodiment of this application. The communication device 20 includes at least one processor 21. The at least one processor 21 is coupled to at least one memory 22. The at least one memory 22 is used to store one or more instructions and / or executable computer code. The at least one processor 21 is used to invoke one or more instructions and / or executable computer code to cause the communication device 20 to implement the method provided in the embodiment of this application. Optionally, the communication device 20 may further include at least one memory 22. Optionally, the communication device 20 may further include at least one communication interface 23, and the at least one communication interface 23 is used to input and / or output information or data.

[0194] In one implementation, the communication device 20 can be any of the network functions in the method embodiments. For example, the communication device 20 can be a first network function (e.g., SPM-KMF) or a terminal device. In this implementation, the processor 21 can be a baseband device, and the communication interface 23 can be a radio frequency device.

[0195] In another implementation, the communication device 20 can be a chip (or chip system) installed in a communication device such as a first network function and terminal equipment. In this implementation, the processor 21 can be a circuit, such as a logic circuit, integrated circuit, etc. The communication interface 13 can be a transceiver, interface circuit, input / output interface, bus, module, pin, or other type of interface.

[0196] This application also provides a communication system. The communication system may include any communication device provided in any of the method embodiments. For example, the communication system may include one or more of the following network functions: a first network function (e.g., SPM-KMF) or a terminal device. The communication system may also include other network functions, such as a source RB processor, a target RB processor, and a C / M-TW-GW, without limitation.

[0197] This application also provides a computer storage medium that can store one or more program instructions to execute any of the above methods.

[0198] This application also provides a computer program product that can store one or more instructions for performing any of the above methods.

[0199] In embodiments of this application, the input term "and / or" describes the association relationship between associated objects and indicates that three possible relationships exist. For example, A and / or B can represent the following three cases: only A exists, both A and B exist, and only B exists. The character " / " typically represents an "OR" relationship between associated objects. "At least one" refers to one or more. "At least one of A and B," similar to "A and / or B," describes the association relationship between associated objects, indicating that three possible relationships exist. For example, at least one of A and B can represent the following three cases: only A exists, both A and B exist, and only B exists.

[0200] Furthermore, unless the context clearly specifies otherwise, the use of the singular forms of “a,” “an,” and “the” in the embodiments of this application and the appended claims is also intended to include the plural forms.

[0201] Those skilled in the art will recognize that, in conjunction with the various examples described in connection with the embodiments disclosed in this specification, the units and algorithm steps can be implemented using electronic hardware or a combination of computer software and electronic hardware. Whether a function is executed using hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but these embodiments should not be considered beyond the scope of this application.

[0202] Those skilled in the art will understand that, for convenience and brevity, the detailed working process of the above-described systems, devices, and units can be referred to the corresponding process in the above-described method embodiments, and will not be repeated here.

[0203] Several embodiments are provided in this application, and the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For example, unit division is a logical functional division, and other division methods can be used in actual embodiments. For example, multiple units or components can be merged or integrated into another system, or some features can be ignored or not performed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed can be implemented using various communication interfaces. Indirect coupling or communication connection between devices or units can be implemented electronically, mechanically, or otherwise.

[0204] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0205] When these functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. The technical solution of this application can be implemented as a software product. The software product is stored in a storage medium and includes several instructions to instruct a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the embodiments of this application. The aforementioned storage medium includes any medium capable of storing program code, such as a USB flash drive, external hard drive, ROM, RAM, magnetic disk, or optical disk, etc.

[0206] The units described as separate components may or may not be physically separate. 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 the units can be selected to achieve the purpose of this embodiment according to actual needs. Furthermore, the functional units in the various embodiments of this 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.

[0207] The above descriptions are merely some specific implementations of this application and are not intended to limit the scope of protection of this application. Any variations or substitutions easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method performed by a first network function, the method comprising: The first network function is responsible for key derivation during handover, and the method includes: First information is obtained from the source radio bearer (RB) processing procedure, wherein the first information includes a downlink RB COUNT, the downlink RB COUNT indicating the number of radio bearer RBs transmitted in the downlink; A first key is derived, wherein the first key is used to derive a terminal key, wherein the terminal key is used for communication between the device and the target RB processor, and the input for deriving the first key includes the downlink RBCOUNT.

2. The method according to claim 1, characterized in that, The method further includes: The terminal key is derived based on the first key; Send the terminal key to the target RB processor.

3. The method according to claim 1 or 2, characterized in that, The method further includes: The second information is obtained from the source RB processing program, wherein the second information includes one or more of the following parameters: the physical cell identifier (PCI) of the target RB processing program, the downlink frequency or next-hop chain counter (NCC) of the target RB processing program; The input used to derive the first key also includes one or more parameters.

4. A communication method performed by a device, characterized in that, include: Obtain first information from the source RB processing procedure, wherein the first information includes downlink RB COUNT, the downlink RBCOUNT indicating the number of radio bearer RBs transmitted in the downlink; A first key is derived, wherein the first key is used to derive a terminal key, wherein the terminal key is used for communication between the device and the target RB processor, and the input for deriving the first key includes the downlink RBCOUNT.

5. The method according to claim 4, characterized in that, The method further includes: The terminal key is derived from the first key.

6. The method according to claim 4 or 5, characterized in that, The method further includes: The second information is obtained from the source RB processing program, wherein the second information includes one or more of the following parameters: Physical Cell Identifier (PCI), DL frequency, or Next Hop Chain Counter (NCC); The input used to derive the first key also includes one or more parameters.

7. The method according to any one of claims 4 to 6, characterized in that, Derivation of the first key includes: If the first value of the NCC received from the source RB processor is equal to the second value of the NCC associated with the currently active first key, then the first key is derived based on the currently active first key and the downlink RB COUNT; or If the first value of the NCC received from the source RB processor is different from the second value of the NCC associated with the currently active first key, a new NH parameter is calculated by incrementing the second value until the second value matches the first value, thereby synchronizing the local NH parameter, and the first key is calculated based on the synchronized local NH parameter and the downlink RB COUNT.

8. The method according to any one of claims 4 to 7, characterized in that, The method further includes: If the anchor key changes, the downlink RB COUNT is reset to zero, the second value of the NCC associated with the currently active first key is reset to zero, and a new first key is derived based on the new anchor key.

9. A communication device, characterized in that, The communication device includes a processor for executing one or more instructions stored in a memory to cause the communication device to implement the method according to any one of claims 1 to 3 or any one of claims 4 to 8.

10. The communication device according to claim 9, characterized in that, The communication device also includes the memory.

11. The communication device according to claim 9 or 10, characterized in that, The communication device includes a communication interface, which is used to input and / or output information or data.

12. A communication device, characterized in that, The communication device includes functions or units for performing the method according to any one of claims 1 to 3 or for performing the method according to any one of claims 4 to 8.

13. A communication device, characterized in that, The communication device includes a circuit and a communication interface, the communication interface being used to receive information and / or data to be processed by the circuit, and to send the information and / or data to the circuit; the circuit is used to perform the method according to any one of claims 1 to 3 or to perform the method according to any one of claims 4 to 8.

14. The communication device according to claim 13, characterized in that, The communication interface is also used to output information and / or data processed by the circuit.

15. A communication system, characterized in that, The communication device includes a communication device that performs the method according to any one of claims 1 to 3, and a communication device that performs the method according to any one of claims 4 to 8.

16. A computer-readable storage medium, characterized in that, It includes one or more instructions, which, when executed on a computer, cause the computer to perform the method according to any one of claims 1 to 3 or the method according to any one of claims 4 to 8.

17. A computer program product, characterized in that, It includes one or more instructions, which, when executed on a computer, cause the computer to perform the method according to any one of claims 1 to 3 or the method according to any one of claims 4 to 8.

Images