A method and apparatus for wireless communication
By generating keys using the first air interface and the core network interface in AIoT communication, the problem of key generation and integrity verification for AIoT devices in low power consumption and without cell information is solved, achieving stability and security of communication recovery, and saving time and power consumption.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- HONOR DEVICE CO LTD
- Filing Date
- 2024-11-28
- Publication Date
- 2026-06-05
AI Technical Summary
In AIoT communication, how to reliably generate keys on the first air interface to resume communication, especially for low-power AIoT devices and situations without cell information, how to support key generation and integrity verification.
The system receives a message requesting the resumption of communication via the first air interface, communicates with the core network via the second interface, generates a key for encryption or integrity protection to avoid re-authentication, generates a first key using the target key, and relies on a first set of values and an algorithm identifier to ensure the stability and security of communication.
It achieves power saving, reduced signaling overhead, shorter communication latency, improved communication efficiency and security in AIoT communication, and better adaptability to support communication recovery of AIoT devices.
Smart Images

Figure CN122160762A_ABST
Abstract
Description
Technical Field
[0001] This application relates to security in wireless communication systems, particularly the generation and integrity protection of keys in AIoT communication. Background Technology
[0002] The application scenarios of future wireless communication systems are becoming increasingly diversified, and different application scenarios place different performance requirements on the system. In order to meet the different performance requirements of various application scenarios, the 3GPP (3rd Generation Partner Project) RAN (Radio Access Network) #72 plenary meeting decided to conduct research on New Radio (NR) (or Fifth Generation, 5G). The 3GPP RAN #75 plenary meeting adopted the NR WI (Work Item), and began the standardization work of NR.
[0003] In communications, both LTE (Long Term Evolution) and 5G NR involve reliable and accurate information reception, optimized energy efficiency, determination of information validity, flexible resource allocation, scalable system architecture, efficient non-access stratum information processing, low service interruption and drop rate, and support for low power consumption. These are crucial for normal communication between base stations and user equipment, rational resource scheduling, and balanced system load. They are the cornerstone of high throughput, meeting the communication needs of various services, improving spectrum utilization, and enhancing service quality. They are indispensable for eMBB (enhanced Mobile Broadband), URLLC (Ultra Reliable Low Latency Communication), and eMTC (enhanced Machine Type Communication). Meanwhile, there are extensive needs in IIoT (Industrial Internet of Things), V2X (Vehicle-to-X), Device-to-Device communication, unlicensed spectrum communication, user communication quality monitoring, network planning and optimization, TN (Territory Network), dual connectivity systems, radio resource management and codebook selection for multiple antennas, signaling design, neighbor cell management, service management, and beamforming. Information is transmitted in two ways: broadcast and unicast. Both methods are essential for 5G systems because they are very helpful in meeting the above needs.
[0004] In its latest discussions, 3GPP has focused on A-IoT (Ambient IoT) devices, which are extremely simple devices. Typical AIoT devices do not actively initiate communication; they lack batteries and power amplifiers, relying instead on wireless signals from other devices to harvest energy. Clearly, the communication method of such devices is completely different from traditional cellular communication. Furthermore, due to limitations in capabilities, AIoT devices require a very long time to transmit each signal, which increases energy consumption. AIoT has broad application prospects and will undoubtedly play a crucial role in future communications, including 6G. Summary of the Invention
[0005] Researchers found that reliably and robustly obtaining the key when a request to resume communication is received via the first air interface is a problem that needs to be solved. They also found that relying on the second interface to obtain the key is a better solution.
[0006] To address the problems mentioned above, this application provides a solution.
[0007] It should be noted that, unless otherwise specified, the embodiments and features in any node of this application can be applied to any other node. Unless otherwise specified, the embodiments and features in the embodiments of this application can be arbitrarily combined with each other. Furthermore, the method proposed in this application can also be used to solve other problems in communication, such as those in NR evolution and 6G systems.
[0008] As an example, the interpretation of the terminology in this application is based on the definitions in the 3GPP specification protocol TS38 series.
[0009] As an example, the interpretation of terms in this application is based on the definitions in the 3GPP specification protocol TS37 series.
[0010] This application discloses a method used in a terminal for wireless communication, comprising:
[0011] A first message is received through the first air interface. The first message requests the resumption of communication. The first message includes a first numerical value, wherein the first numerical value is for integrity protection.
[0012] In response to receiving the first message, a second message is sent through the second interface, the second message indicating the resumption of communication, and the second message includes the first numerical value;
[0013] A third message is received through the second interface, the third message indicating a target key; a first key is generated based on the target key, wherein the first key is used for encryption or integrity protection;
[0014] Wherein, the first air interface is an air interface other than the Uu interface; the second interface is the interface between the terminal and the core network; the terminal is a UE; the step of generating the first key according to the target key includes: the first set of values is used as input to the first function; the first key is the output of the first function; the input of the first function includes dependence on the first set of values; the first set of values includes an algorithm identifier, the length of the algorithm identifier, and the target key.
[0015] As an example, the problems to be solved by this application include: how to reliably generate keys for requests to resume communication on a first air interface, and how to support the resumption of AIoT communication across terminals.
[0016] As an example, the advantages of the above method include: saving power, avoiding re-authentication, being particularly suitable for AIoT (A-IoT) devices, better adaptability, and stability and reliability.
[0017] Specifically, according to one aspect of this application, the first air interface is an air interface other than the PC5 interface.
[0018] As an example, the meaning of "the first air interface is an air interface other than the PC5 interface" is that the communication on the first air interface is not sidelink communication.
[0019] Specifically, according to one aspect of this application, whether the target key is a first type key or a second type key depends on whether the terminal is the reader of the most recent communication of the sender of the first message. When the terminal is not the reader of the most recent communication of the sender of the first message, the target key is the second type key; when the terminal is not the reader of the most recent communication of the sender of the first message, the target key is the first type key.
[0020] Wherein, the first type of key generates the second type of key, and the first set of values includes the second type of key.
[0021] Specifically, according to one aspect of this application, the sending of the second message via the second interface depends on whether the terminal has saved the security context of the sender of the first message; the second message is sent only if the terminal has saved the security context of the sender of the first message.
[0022] Specifically, according to one aspect of this application, the second message includes a first temporary identifier, the reason for restoring communication, and whether the paging message originates from at least one of the core network;
[0023] The first temporary identifier is an identifier used by the sender of the first message to restore communication.
[0024] Specifically, according to one aspect of this application, before receiving the first message, a fourth message is sent through the first air interface, the fourth message indicating the end of communication, the fourth message carrying at least one of a first temporary identifier and an identifier of a second type of key;
[0025] Wherein, the first temporary identifier is an identifier used by the sender of the first message to resume communication; the first set of values includes the second type of key.
[0026] Specifically, according to one aspect of this application, a fifth message is sent via the second interface before the first message is received, the fifth message including context for the sender of the first message;
[0027] The context for the first message sender includes at least one of the following: the access layer identifier of the first message sender, at least a portion of the permanent identifier of the sender of the first message, security information used in communication with the first message sender, and a key or key identifier used in communication with the first message sender.
[0028] Specifically, according to one aspect of this application, the third message includes at least one of the following: historical information about the sender of the first message, at least a portion of bits of the sender's permanent identifier, a key update period, and an AIoT service address.
[0029] Specifically, according to one aspect of this application, a first signaling is transmitted through the first air interface, the first signaling indicating a key update, the first signaling including an identifier of a second type of key, at least one of Nonce_1 and Nonce_2;
[0030] The second signaling is received through the second interface, and the second signaling indicates information about the key update.
[0031] Specifically, according to one aspect of this application, the terminal described in this application is also referred to as the first node.
[0032] Specifically, according to one aspect of this application, the terminal is a user equipment.
[0033] Specifically, according to one aspect of this application, the terminal is a vehicle-mounted terminal.
[0034] Specifically, according to one aspect of this application, the terminal is a mobile phone.
[0035] This application discloses a first node used in wireless communication, comprising:
[0036] One or more processors and memory;
[0037] The memory is coupled to the one or more processors and is used to store computer program code, the computer program code including computer instructions, which the one or more processors invoke to cause the terminal to perform a method as described in a terminal used for wireless communication.
[0038] As an example, compared with conventional solutions, this application has the following advantages:
[0039] Resuming communication can save significant time, reduce power consumption, and conserve communication resources compared to re-establishing the communication process. However, to ensure the security of communication restoration, integrity verification is required. This necessitates the generation of new keys and the acquisition of the communication context. This presents a significant challenge for AIoT communication. The parameters used in key generation and integrity verification are generated using specific methods / functions, including existing technologies. These methods have undergone rigorous testing, making arbitrary changes extremely difficult, as such changes cannot guarantee security. Key generation and integrity verification methods include functions for generating relevant parameters and the input parameters of these functions. In communication systems, integrity verification methods are strictly defined by the protocol; currently defined integrity verification methods for communication restoration are inadequate for supporting integrity verification on the first air interface.
[0040] In a typical AIoT communication scenario, communication occurs between AIoT devices and a reader, where the reader is typically a mobile phone, or User Equipment (UE). In such scenarios, key generation and integrity protection require new solutions.
[0041] Meanwhile, AIoT devices may not be required or provided with cell information, which poses a significant obstacle to key generation and integrity verification.
[0042] Meanwhile, if the context is stored in the previous UE, and the AIoT device needs to resume communication with other UEs due to movement or because the previous UE has left, even though these UEs have not communicated with it before, such scenarios make it difficult for other UEs to obtain the context.
[0043] In this application, the context of AIoT communication can be stored in the core network rather than the cell, which is beneficial for supporting the recovery of communication over a wider range, while avoiding the complexity of the cell or UE.
[0044] The method proposed in this application provides a scheme for key generation and integrity verification during communication recovery in the new communication scenario of AIoT. Therefore, it can better support AIoT communication, provide better security, and support communication recovery in AIoT. It also saves power consumption, reduces signaling overhead, increases efficiency, and shortens communication latency. Attached Figure Description
[0045] Other features, objects, and advantages of this application will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings:
[0046] Figure 1 This illustration shows a schematic diagram of receiving a first message through a first air interface, sending a second message through a second interface, receiving a third message through a third interface, and generating a first key according to an embodiment of this application.
[0047] Figure 2 A schematic diagram of a network architecture according to an embodiment of this application is shown;
[0048] Figure 3 A schematic diagram of an embodiment of a wireless protocol architecture for the user plane and control plane according to an embodiment of this application is shown;
[0049] Figure 4 A schematic diagram of a first communication device and a second communication device according to an embodiment of this application is shown;
[0050] Figure 5 A flowchart of wireless signal transmission according to an embodiment of this application is shown;
[0051] Figure 6 A schematic diagram illustrating how the generation of a first numerical value according to an embodiment of this application depends on a first identifier and a second identifier is shown;
[0052] Figure 7 A schematic diagram of a first parameter set and a first key according to an embodiment of this application is shown;
[0053] Figure 8 A schematic diagram illustrating that the verification integrity depends on a first value and a second value according to an embodiment of this application is shown;
[0054] Figure 9 A schematic diagram of a first air interface according to an embodiment of this application is shown;
[0055] Figure 10 A schematic diagram of a processing apparatus for a terminal according to an embodiment of this application is illustrated;
[0056] Figure 11 A schematic diagram illustrating the structure of an A-IoT device according to an embodiment of this application is provided. Implementation
[0057] The technical solution of this application will be further described in detail below with reference to the accompanying drawings. It should be noted that, unless otherwise specified, the embodiments and features in the embodiments of this application can be arbitrarily combined with each other.
[0058] Example 1
[0059] Example 1 illustrates a flowchart of a process according to an embodiment of this application, which describes receiving a first message through a first air interface, sending a second message through a second interface, receiving a third message through a third interface, and generating a first key, as shown in the attached diagram. Figure 1 As shown. (Attached) Figure 1 In the diagram, each box represents a step. It is particularly important to emphasize that the order of the boxes in the diagram does not represent the chronological order of the steps they represent.
[0060] In Embodiment 1, the terminal in this application receives a first message through a first air interface in step 101, sends a second message through a second interface in step 102, receives a third message through a third interface in step 103, and generates a first key number in step 104.
[0061] In this application, the first message requests the resumption of communication and includes a first numerical value for integrity protection; the second message indicates the resumption of communication and includes the first numerical value; the third message indicates a target key, wherein the first key is used for encryption or integrity protection; the first air interface is an air interface other than the Uu interface; the second interface is the interface between the terminal and the core network; the terminal is a UE; the first key is the output of a first function; the input of the first function depends on a first set of numerical values; the first set of numerical values includes an algorithm identifier, the length of the algorithm identifier, and the target key. As an embodiment, the terminal in this application is also referred to as a first node.
[0062] As one embodiment, the first node, in response to receiving the first message, sends the second message through the second interface.
[0063] As an example, the first message triggers the second message.
[0064] As an example, the first node is UE (User Equipment).
[0065] As an example, the first node is a terminal.
[0066] As an example, the first node is in RRC connected state.
[0067] As an example, any parameter in this application may be configured by the network or may be generated by the first node according to an internal algorithm, such as randomization.
[0068] As an example, the values of the timers in this application are all limited, not exceeding 2560 milliseconds.
[0069] As an example, the value of the timer is the running time when the timer is not interfered with.
[0070] As an example, the values of any parameters in this application, including but not limited to the values of timers and counters, are limited unless otherwise stated.
[0071] As a sub-implementation of this embodiment, the upper limit of the value of any parameter in this application is 1024 times 65536.
[0072] As a sub-implementation of this embodiment, the upper limit of the value of any parameter in this application is 65536 or 65535.
[0073] As a sub-implementation of this embodiment, the upper limit of the value of any parameter in this application is 1024.
[0074] As a sub-implementation of this embodiment, the upper limit of the value of any parameter in this application is 640 or 320.
[0075] As an example, this application is directed to NR.
[0076] As an example, this application is directed to NR-evolved wireless communication networks.
[0077] As an example, L1 is Layer-1 or physical layer.
[0078] As an example, L2 is Layer-2.
[0079] As an example, this application pertains to NR and NR evolution networks, such as 6G networks.
[0080] As an example, this application is directed to AIoT communication.
[0081] As an example, the AIoT communication referred to is not cellular communication, not Wi-Fi, and not Bluetooth.
[0082] As an example, before receiving the first message, the first node may send at least one paging message to the sender of the first message.
[0083] In one embodiment, the sender of the first message is the second node.
[0084] As an example, any one of the at least one paging message is directed to the second node.
[0085] As an example, there are no other paging messages related to the second node sent by the first node between any two adjacent paging messages in the at least one paging message.
[0086] As one embodiment, the at least one paging message is all paging messages sent by the first node within a time period.
[0087] As a sub-example of this embodiment, all paging messages are paging messages related to the second node.
[0088] As a sub-example of this embodiment, all paging messages are paging messages related to the second node.
[0089] As an example, the at least one paging message is sent via a first air interface.
[0090] As an example, the second node will not actively initiate random access.
[0091] As an example, the second node will not actively initiate a random access attempt if the random access attempt fails.
[0092] As an example, the second node receives the at least one paging message.
[0093] In one embodiment, the second node is not a network device.
[0094] As one example, the second node is a device.
[0095] As an example, the device is an IoT device.
[0096] As an example, the IoT device is an AIoT device.
[0097] As an example, the device is one that cannot actively initiate random access.
[0098] As an example, the device is a device without a power amplifier.
[0099] As one embodiment, the first air interface is the air interface between the UE and the AIoT device.
[0100] As an example, the first air interface is not a Uu interface.
[0101] As an example, the first air interface is not a PC5 interface.
[0102] As an example, the first air interface is not an interface of the RAN.
[0103] As an example, the first air interface is not used for secondary link communication.
[0104] As one embodiment, the first air interface is the air interface between the first node and the second node.
[0105] As an example, the first air interface is an IoT communication air interface.
[0106] As one embodiment, the first air interface is the air interface between the UE and a non-network node.
[0107] As an example, the first air interface is an air interface defined by 3GPP.
[0108] As an example, on the first air interface, a request to resume communication can only be sent to the terminal by the sender of the first message.
[0109] As an example, on the first air interface, a request to resume communication cannot be sent by the terminal to the sender of the first message. The terminal can only send a paging message to indicate the sender of the first message.
[0110] As an example, the resumption of communication means that the sender of the first message had previously communicated with the terminal.
[0111] As one embodiment, the sender of the first message can only communicate with the reader. In the communication, the terminal acts as the reader. The terminal is the reader.
[0112] As an example, prior to sending the first message, the sender of the first message had communicated with the terminal or other reader. This communication refers to a successful communication.
[0113] As an example, the communication that has occurred refers to the previous communication prior to the request to resume communication.
[0114] As one embodiment, the communication performed includes receiving an instruction to suspend communication.
[0115] As one example, the received indication is sent by the reader to the sender of the first message.
[0116] As one embodiment, the suspended communication includes saving all or part of the context of the communication.
[0117] As one example, the suspended communication includes saving the information needed to resume communication.
[0118] As an example, resuming communication means that communication does not need to be re-established, such as without re-authentication, which helps save power, reduce signaling overhead, and reduce latency.
[0119] As one embodiment, the first value for integrity protection includes: the first value is for verifying integrity.
[0120] As an example, one field of the first message is the first numerical value.
[0121] As an example, the value of one field of the first message is the value of the first numerical value.
[0122] As an example, the first message explicitly indicates the first value.
[0123] As one embodiment, the first value is a parameter for integrity protection, including: the first value is used for integrity protection.
[0124] As one embodiment, the first value is a parameter for integrity protection, including: the first value is a parameter used to verify integrity.
[0125] As an example, the first value is an integrity protection parameter including: the first value is MAC-I (Message Authentication Code for Integrity).
[0126] As an example, the first value is a parameter for integrity protection, which includes: the first value is required to verify integrity.
[0127] As an example, the first value is a code.
[0128] As an example, the first value is used to verify the integrity protection code.
[0129] As an example, verifying integrity includes verifying the integrity of the first message.
[0130] As an example, the integrity verification includes verifying the integrity of the sender's identifier carried in the first message.
[0131] As one example, the integrity verification includes verifying the integrity of the first identifier.
[0132] As an example, the integrity verification includes verifying the integrity of the request to resume communication by the first identifier.
[0133] As an example, the integrity verification includes verifying the integrity of an identifier of the sender of the first message carried by the first message.
[0134] As an example, the identifier is an identifier for integrity.
[0135] As one embodiment, the integrity verification includes comparing whether the first value is equal to the second value. When the first value is equal to the second value, the integrity verification passes; when the first value is not equal to the second value, the integrity verification fails.
[0136] As an example, the second value is generated by the core network.
[0137] As an example, the integrity verification is performed by the core network.
[0138] As an example, the terminal does not verify the integrity of the first value.
[0139] As an example, the terminal does not generate the second value.
[0140] As an example, the generation of the first value depends on the identifier of the terminal.
[0141] As an example, the generation of the first value depends on the second identifier.
[0142] As an example, the second identifier is the identifier of the core network.
[0143] As an example, the identifier of the core network is the identifier of the core network node.
[0144] As an example, the identifier of the core network is the identifier of the core network device.
[0145] As an example, the identifier of the core network is an identifier of the core network's functions.
[0146] As an example, the identifier of the core network is an identifier of a core network logical node or logical function.
[0147] As one example, the identifier of the core network is the identifier of the core network's services or applications.
[0148] As an example, the identifier of the core network is the identifier of the core network registered by the first node.
[0149] As an example, the first identifier occupies fewer than 16 bits.
[0150] As an example, the second identifier occupies fewer than 16 bits.
[0151] As an example, neither the first identifier nor the second identifier is a C-RNTI.
[0152] As an example, the first identifier is an AS identifier.
[0153] As an example, the first identifier is the identifier of the MAC (media access control) layer.
[0154] As an example, the first value is generated by the sender of the first message.
[0155] As an example, the second value is a parameter used for integrity protection.
[0156] As one example, the integrity protection includes verifying integrity.
[0157] As an example, the first message belongs to the random access procedure.
[0158] As an example, the random access process is a random access initiated by the sender of the first message to the terminal.
[0159] As an example, the first identifier is inherent.
[0160] As one example, the first identifier is assigned by the operator.
[0161] As one example, the first identifier is assigned by the terminal.
[0162] As an example, the first identifier is assigned by the network.
[0163] As one embodiment, the second identifier is a core network identifier, which may be inherent or configured by the network.
[0164] As one embodiment, the second identifier is the identifier of the core network, and the second identifier is indicated by the core network.
[0165] As a sub-implementation of this embodiment, the second identifier is indicated by the core network to the terminal.
[0166] As a sub-implementation of this embodiment, the second identifier is indicated by the core network to the sender of the first message.
[0167] As one embodiment, the second identifier is the identifier of the terminal, and the second identifier is assigned by the network.
[0168] As one embodiment, the second identifier is the identifier of the terminal, and the second identifier is indicated by the terminal to the sender of the first message.
[0169] As an example, the second identifier is not inherent.
[0170] As an example, the at least one paging message includes the second identifier.
[0171] As one example, the first identifier is an identifier of the access layer.
[0172] As an example, the first identifier is an identifier other than C-RNTI (C-Radio Network Temporary Identifier).
[0173] As an example, C-RNTI is used for scrambling PDCCH (physical downlink control channel).
[0174] As an example, C-RNTI is used for scrambling PUSCH (physical uplink shared channel).
[0175] As an example, the first identifier is not used for scrambling the PDCCH.
[0176] As an example, the first identifier is not used for scrambling PUSCH.
[0177] As an example, the first identifier is included in the scheduling information.
[0178] As one example, the scheduling information is sent by the terminal to the sender of the first message.
[0179] As one example, the scheduling information includes physical layer scheduling information.
[0180] As an example, the scheduling information belongs to MAC CE (control element).
[0181] As an example, the second value is MAC-I.
[0182] As a sub-implementation of this embodiment, the second value is a MAC-I used to verify the first value. When the first value and the second value are equal, the integrity verification passes; when the first value and the second value are not equal, the integrity verification fails.
[0183] As an example, the generation of the first value depends on a first identifier and a second identifier.
[0184] As one embodiment, the generation of the first value depending on the first identifier and the second identifier includes: the first value is generated by a first function, and when the first value is generated, the first identifier and the second identifier are the inputs of the first function; the generation of the second value depending on the first identifier and the second identifier includes: the second value is generated by the first function, and when the second value is generated, the first identifier and the second identifier are the inputs of the first function.
[0185] As an example, the first message triggers the second message.
[0186] As an example, the second message is sent to the core network.
[0187] As one example, sending to the core network includes sending to the AMF (access mobility function).
[0188] As an example, the second message is a NAS message.
[0189] As an example, the second message is sent via an RRC message.
[0190] As an example, the meaning of sending via RRC message is: the second message is carried by an RRC message.
[0191] As an example, the meaning of the second message being carried by an RRC message includes: the second message is carried by a container of RRC messages.
[0192] As an example, the meaning of the second message being carried by a container of RRC messages includes: the second message is not interpreted by the base station.
[0193] As one embodiment, the meaning of the second message indicating resumption of communication includes: the second message instructs the terminal to resume communication with the sender of the first message.
[0194] As one embodiment, the meaning of the second message indicating the resumption of communication includes: the second message indicates that the reason for sending the second message is to resume communication.
[0195] As one embodiment, the meaning of the second message indicating resumption of communication includes: the second message indicates that the sender of the first message requests the resumption of communication.
[0196] As one embodiment, the meaning of the second message indicating the resumption of communication includes: the second message indicates the resumption of communication between the sender of the first message and the terminal.
[0197] As one embodiment, the meaning of the second message indicating the resumption of communication includes: the second message indicates that the first message has been received.
[0198] As one example, the second message requests the context of the sender of the first message.
[0199] As one example, the second message requests the security context of the sender of the first message.
[0200] As an example, the third message is a response to the second message.
[0201] As an example, the third message is sent by the core network.
[0202] As an example, the third message is received via an RRC message.
[0203] As an example, the third message indicating the target key includes: the third message indicating the index of the target key.
[0204] As an example, the third message indicating the target key includes: the third message includes the target key.
[0205] As an example, the third message indicating the target key includes: the third message includes parameters for generating the target key.
[0206] As an example, the third message indicating the target key includes: the third message includes a counter for generating the target key.
[0207] As an example, the third message indicating the target key includes: the third message indicating the algorithm for generating the target key.
[0208] As an example, the third message includes the context of the sender of the first message.
[0209] As an example, the third message includes the security context of the sender of the first message.
[0210] As an example, the first key is used for encryption.
[0211] As an example, the third message indicates a second key, which is used for integrity protection.
[0212] As an example, the first key is used for integrity protection.
[0213] As an example, the third message indicates a second key, which is used for encryption.
[0214] As an example, the first key being used for encryption or integrity protection means that the first key is used for encryption or integrity protection of communication between the terminal and the sender of the first message.
[0215] As an example, the first function is a key derivation function.
[0216] As an example, the meaning of the first function's input depending on the first parameter set includes: the first parameter set is used to input the first function.
[0217] As one embodiment, the first parameter set for inputting a first function includes: at least some parameters in the first parameter set generating a first input parameter, and the first input parameter being input into the first function.
[0218] As a sub-example of this embodiment, the first input parameter is parameter S.
[0219] As an example, the algorithm identifier is the identifier of the algorithm that generated the first key.
[0220] As an example, the algorithm identifier and its length are predefined.
[0221] As an example, the first function includes multiple input parameters.
[0222] As an example, the first function is used to generate the first value.
[0223] As an example, when generating the first value, the input parameters of the first function may include at most one cell identifier.
[0224] As an example, when generating the first value, the input parameters of the first function do not include the cell identifier.
[0225] As an example, when generating the second value, the input parameters of the first function may include at most one cell identifier.
[0226] As an example, when generating the second value, the cell identifier is not included in the input parameters of the first function.
[0227] As an example, the first value is an output of the first function.
[0228] As a sub-example of this embodiment, the first value is the output when the sender of the first message generates the first value using the first function.
[0229] As an example, the second value is an output of the first function.
[0230] As a sub-example of this embodiment, the second value is the output of the terminal when it uses the first function to generate the second value.
[0231] As an example, when the terminal requests the network to restore communication, the MAC-I carried in the request message for restoring communication is generated using at least two cell identifiers as input parameters.
[0232] As an example, both the first value and the second value are generated using the first function.
[0233] As an example, the first function is predefined.
[0234] As an example, the first function may rely on existing technology.
[0235] As an example, the first function uses an existing 3GPP-defined key generation method.
[0236] As an example, the first function uses the existing 3GPP-defined MAC-I generation method.
[0237] As an example, the first parameter set includes the FC field.
[0238] As a sub-example of this embodiment, the FC field indicates the type of key generated by the first function.
[0239] As an example, the first parameter set includes the P0 field.
[0240] As an example, the first parameter set includes an L0 field. The L0 field indicates the length of the P0 field.
[0241] As an example, the first parameter set includes the P1 field.
[0242] As an example, the first parameter set includes an L1 field. The L1 field indicates the length of the P1 field.
[0243] As an example, the first input parameter is generated by XORing at least some of the parameters in the first parameter set.
[0244] As an example, the process of generating the first key is the process of deriving the first key from the target key.
[0245] As an example, the target key is different from the first key.
[0246] As an example, the first air interface is an air interface other than the PC5 interface.
[0247] As an example, the first air interface is not an interface between UEs.
[0248] As an example, the first air interface is not a secondary link communication interface.
[0249] As an example, whether the target key is a first type key or a second type key depends on whether the terminal was the reader of the most recent communication with the sender of the first message. When the terminal was the reader of the most recent communication with the sender of the first message, the target key is the second type key; when the terminal was not the reader of the most recent communication with the sender of the first message, the target key is the first type key.
[0250] As a sub-implementation of this embodiment, the first type of key generates the second type of key.
[0251] As a sub-implementation of this embodiment, the first parameter set includes the second type of key.
[0252] As an example, the second type of key is derived from the first type of key.
[0253] As an example, the first type of key cannot be derived from the second type of key.
[0254] As an example, the length of the first type of key is greater than the length of the second type of key.
[0255] As an example, the first type of key is the key from which the second type of key is derived.
[0256] As an example, the first type of key is the key determined during the initial authentication.
[0257] As an example, the second type of key is a key that is periodically updated during communication.
[0258] As an example, the second type of key is a session key.
[0259] As an example, the first type of key is the root key for AIoT communication.
[0260] As an example, the first type of key is not a session key.
[0261] As one embodiment, the sending of the second message through the second interface depends on whether the terminal has saved the security context of the sender of the first message. The second message is sent only if the terminal has saved the security context of the sender of the first message.
[0262] As an example, the second message is sent when the terminal has stored the security context for the sender of the first message.
[0263] As an example, the second message is not sent when the terminal does not save the security context of the sender of the first message.
[0264] As an example, the authentication process is triggered when the terminal does not have a security context for the sender of the first message.
[0265] As an example, when the terminal does not save the security context for the sender of the first message, the terminal cannot resume communication with the sender of the first message.
[0266] As an example, the advantages of the above method are: it can save time and reduce latency, especially when communication can only be resumed for the same terminal as the one in the last communication.
[0267] As one embodiment, the second message includes a first temporary identifier, the reason for resuming communication, and whether the paging message comes from at least one of the core network.
[0268] As a sub-implementation of this embodiment, the first temporary identifier is an identifier used by the sender of the first message to resume communication.
[0269] As one example, the first message is triggered by the paging message.
[0270] As an example, the name of the first temporary identifier includes RNTI.
[0271] As an example, the name of the first temporary identifier includes I-RNTI.
[0272] As an example, the third message includes at least one of the following: historical information about the sender of the first message, at least a portion of bits of the sender's permanent identifier, key update period, and AIoT service address.
[0273] As one example, the historical information includes information from the last communication.
[0274] As an example, the information from the last communication includes the resources used during the last communication.
[0275] As an example, the information from the last communication includes the time of the last communication.
[0276] As an example, the information from the previous communication includes the key used in the previous communication.
[0277] As an example, the information from the last communication includes: the identifier used in the last communication.
[0278] As an example, the information from the last communication includes: the service type of the last communication.
[0279] As an example, the information from the last communication includes the duration of the last communication.
[0280] As an example, the information from the last communication includes: the power status at the time of the last communication.
[0281] As an example, the information from the previous communication includes: the retransmission status of the previous communication.
[0282] As an example, the third message includes all bits of the permanent identifier of the sender of the first message.
[0283] As an example, the third message includes 8 bits of the permanent identifier of the sender of the first message.
[0284] As an example, the third message includes 16 bits of the permanent identifier of the sender of the first message.
[0285] As an example, the advantage of the third message including at least a portion of the permanent identifier bits of the sender of the first message is that it facilitates faster context retrieval.
[0286] As an example, the key update cycle is the key update cycle between the sender and reader of the first message in the previous communication.
[0287] As an example, including the key update cycle in the third message helps improve security.
[0288] As an example, the AIoT service address is the address of the AIoT function.
[0289] As one example, the AIoT function is located in the core network.
[0290] As an example, the third message including the address of the AIoT function helps to identify a fast and appropriate service node or entity.
[0291] Example 2
[0292] Example 2 illustrates a schematic diagram of a network architecture according to this application, as shown in the attached diagram. Figure 2 As shown.
[0293] Appendix Figure 2This diagram illustrates the network architecture 200 of 5G NR, LTE (Long-Term Evolution), and LTE-A (Long-Term Evolution Advanced) systems. The 5G NR or LTE network architecture 200 may be referred to as 5GS (5G System) / EPS (Evolved Packet System) 200 or some other suitable term. 5GS / EPS 200 may include one or more UE (User Equipment) 201, NG-RAN (Next Generation Radio Access Network) 202, 5GC (5G Core Network) / EPC (Evolved Packet Core) 210, HSS (Home Subscriber Server) / UDM (Unified Data Management) 220, and Internet services 230. 5GS / EPS can interconnect with other access networks, but these entities / interfaces are not shown for simplicity. As shown in the figure, 5GS / EPS provides packet-switched services; however, those skilled in the art will readily understand that the various concepts presented throughout this application can be extended to networks providing circuit-switched services or other cellular networks. NG-RAN includes NR Node B (gNB) 203 and other gNBs 204. gNB 203 provides user and control plane protocol termination to UE 201. gNB 203 can connect to other gNBs 204 via an Xn interface (e.g., backhaul). gNB 203 may also be referred to as a base station, base transceiver station, radio base station, radio transceiver, transceiver function, Basic Services Set (BSS), Extended Services Set (ESS), TRP (Transmitter Receiver Node), or some other suitable term. gNB 203 provides UE 201 with an access point to 5GC / EPC 210. Examples of UE201 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radios, non-terrestrial base station communications, satellite mobile communications, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, drones, aircraft, narrowband IoT devices, machine-type communication devices, land vehicles, automobiles, wearable devices, or any other similar functional devices. Those skilled in the art may also refer to UE201 as a mobile station, subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, radio communication device, remote device, mobile subscriber station, access terminal, mobile terminal, radio terminal, remote terminal, handheld device, user agent, mobile client, client, or any other suitable term.gNB203 connects to 5GC / EPC210 via the S1 / NG interface. 5GC / EPC210 includes MME (Mobility Management Entity) / AMF (Authentication Management Field) / SMF (Session Management Function) 211, other MME / AMF / SMF 214, S-GW (Service Gateway) / UPF (User Plane Function) 212, and P-GW (Packet Data Network Gateway) / UPF 213. MME / AMF / SMF 211 is the control node handling signaling between UE201 and 5GC / EPC210. Generally, MME / AMF / SMF 211 provides bearer and connection management. All user IP (Internet Protocol) packets are transmitted through S-GW / UPF 212, which is itself connected to P-GW / UPF 213. The P-GW provides UE IP address allocation and other functions. The P-GW / UPF213 connects to Internet service 230. Internet service 230 includes carrier-compliant Internet protocol services, specifically including the Internet, intranet, IMS (IP Multimedia Subsystem), and packet-switched streaming services.
[0294] As an example, the first node in this application is UE201.
[0295] As an example, the base station of the second node in this application is gNB203.
[0296] As an example, the radio link from UE201 to NR node B is an uplink.
[0297] As an example, the radio link from NR node B to UE201 is a downlink.
[0298] As an example, the UE201 includes a mobile phone.
[0299] As an example, the UE201 is a dedicated device or special device with communication functions.
[0300] As an example, the gNB203 is a microcell base station.
[0301] As an example, the gNB203 is a pico cell base station.
[0302] As an example, the gNB203 is a base station used in a home network.
[0303] As an example, the gNB203 is a base station used in a private network.
[0304] As an example, the gNB203 is a base station used in an enterprise network.
[0305] Example 3
[0306] Example 3 illustrates a schematic diagram of an embodiment of a wireless protocol architecture for a user plane and a control plane according to this application, as shown in the attached diagram. Figure 3 As shown. Figure 3 This is a schematic diagram illustrating an embodiment of a radio protocol architecture for the user plane 350 and the control plane 300. Figure 3The radio protocol architecture for the control plane 300 between the first node (UE, gNB) and the second node (gNB, UE), or between the two UEs, is illustrated using three layers: Layer 1, Layer 2, and Layer 3. Layer 1 (L1 layer) is the lowest layer and implements various PHY (Physical Layer) signal processing functions. L1 layer will be referred to as PHY301 in this document. Layer 2 (L2 layer) 305 sits above PHY301 and is responsible for the link between the first and second nodes, and between the two UEs, via PHY301. L2 layer 305 includes the MAC (Medium Access Control) sublayer 302, the RLC (Radio Link Control) sublayer 303, and the PDCP (Packet Data Convergence Protocol) sublayer 304, which terminate at the second node. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. PDCP sublayer 304 also provides security through encrypted data packets and supports cross-regional movement between second nodes to the first node. RLC sublayer 303 provides upper layer data packet segmentation and reassembly, retransmission of lost packets, and packet reordering to compensate for out-of-order reception due to HARQ. MAC sublayer 302 provides multiplexing between logical and transport channels. MAC sublayer 302 is also responsible for allocating various radio resources (e.g., resource blocks) within a cell between first nodes. MAC sublayer 302 is also responsible for HARQ operations. RRC (Radio Resource Control) sublayer 306 in Layer 3 (L3) of the control plane 300 is responsible for acquiring radio resources (i.e., radio bearers) and configuring the lower layer using RRC signaling between the second and first nodes. PC5-S (PC5 Signaling Protocol) sublayer 307 is responsible for processing the signaling protocol of the PC5 interface. The radio protocol architecture of user plane 350 includes layer 1 (L1 layer) and layer 2 (L2 layer). The radio protocol architecture for the first and second nodes in user plane 350 is largely the same as the corresponding layers and sublayers in control plane 300 for physical layer 351, PDCP sublayer 354 in L2 layer 355, RLC sublayer 353 in L2 layer 355 and MAC sublayer 352 in L2 layer 355. However, PDCP sublayer 354 also provides header compression for upper layer packets to reduce radio transmission overhead.The L2 layer 355 in the user plane 350 also includes the SDAP (Service Data Adaptation Protocol) sublayer 356. The SDAP sublayer 356 is responsible for mapping between QoS flows and Data Radio Bearers (DRBs) to support service diversity. SRBs can be seen as services or interfaces provided by the PDCP sublayer to higher layers, such as the RRC sublayer. In the NR system, SRBs include SRB1, SRB2, and SRB3, which are used to transmit different types of control signaling. SRBs are bearers between the UE and the access network, used to transmit control signaling, including RRC signaling, between the UE and the access network. SRB1 is particularly important for the UE; after each UE establishes an RRC connection, there will be an SRB1 used to transmit RRC signaling. Most signaling is transmitted through SRB1. If SRB1 is interrupted or unavailable, the UE must re-establish RRC. SRB2 is generally only used to transmit NAS signaling or security-related signaling. UEs may not need to configure SRB3. Except for emergency services, the UE must establish an RRC connection with the network for subsequent communication. Although not illustrated, the first node may have several upper layers above L2 layer 355. This also includes a network layer (e.g., IP layer) terminating at the P-GW on the network side and an application layer terminating at the other end of the connection (e.g., remote UE, server, etc.). Protocol layers may also be referred to as protocol sublayers. (See Appendix.) Figure 3 The diagram shows a general protocol layer structure. The nodes used in this application may be missing some protocol layers, such as the PDCP sublayer, the RRC sublayer, the RLC sublayer, and the SDAP sublayer.
[0307] As an example, Appendix Figure 3 The wireless protocol architecture described herein is applicable to the first node in this application.
[0308] As an example, Appendix Figure 3 A portion of the wireless protocol architecture is applicable to the second node in this application.
[0309] As an example, the communication between the first node and the second node involves only the physical layer and the MAC sublayer.
[0310] As an example, the second node uses only the physical layer and the MAC sublayer.
[0311] As an example, the first message in this application is generated in MAC302 or PHY301.
[0312] As an example, the second message in this application is generated in the NAS.
[0313] As an example, the third message in this application is generated in the NAS.
[0314] As an example, the fourth message in this application is generated in MAC302 or PHY301.
[0315] As an example, the fifth message in this application is generated in NAS.
[0316] As an example, the first signaling in this application is generated in a protocol layer for AIoT applications, either MAC302 or PHY301 or above MAC302.
[0317] Example 4
[0318] Example 4 illustrates a schematic diagram of a first communication device and a second communication device according to an embodiment of this application, as shown in the attached diagram. Figure 4 As shown. Figure 4 This is a block diagram of a first communication device 450 and a second communication device 410 communicating with each other in the access network.
[0319] The first communication device 450 includes a controller / processor 459, a memory 460, a data source 467, a transmitting processor 468, a receiving processor 456, and optionally may also include a multi-antenna transmitting processor 457, a multi-antenna receiving processor 458, a transmitter / receiver 454, and an antenna 452.
[0320] The second communication device 410 includes a controller / processor 475, a memory 476, a receiver processor 470, a transmitter processor 416, and optionally may also include a multi-antenna receiver processor 472, a multi-antenna transmitter processor 471, a transmitter / receiver 418, and an antenna 420.
[0321] In the transmission from the second communication device 410 to the first communication device 450, at the second communication device 410, upper-layer data packets from the core network are provided to the controller / processor 475. The controller / processor 475 implements L2 (Layer-2) layer functionality. In the transmission from the second communication device 410 to the first communication device 450, the controller / processor 475 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation to the first communication device 450 based on various priority metrics. The controller / processor 475 is also responsible for retransmitting lost packets and signaling to the first communication device 450. The transmit processor 416 and the multi-antenna transmit processor 471 implement various signal processing functions for the L1 layer (i.e., the physical layer). Transmit processor 416 performs encoding and interleaving to facilitate forward error correction (FEC) at the second communication device 410, and mapping of signal clusters based on various modulation schemes (e.g., Binary Phase Shift Keying (BPSK), Quadrature Phase Shift Keying (QPSK), M-Phase Shift Keying (M-PSK), M-QAM). Multi-antenna transmit processor 471 performs digital spatial precoding on the encoded and modulated symbols, including codebook-based and non-codebook-based precoding, and beamforming processing, generating one or more spatial streams. Transmit processor 416 then maps each spatial stream to subcarriers, multiplexes it with a reference signal (e.g., a pilot) in the time and / or frequency domains, and subsequently uses inverse fast Fourier transform (IFFT) to generate a physical channel carrying the time-domain multicarrier symbol stream. Multi-antenna transmit processor 471 then performs transmit analog precoding / beamforming operations on the time-domain multicarrier symbol stream. Each transmitter 418 converts the baseband multicarrier symbol stream provided by the multi-antenna transmitter processor 471 into an radio frequency stream, which is then provided to different antennas 420.
[0322] In the transmission from the second communication device 410 to the first communication device 450, at the first communication device 450, each receiver 454 receives a signal through its corresponding antenna 452. Each receiver 454 recovers the information modulated onto the radio frequency carrier and converts the radio frequency stream into a baseband multicarrier symbol stream, which is then provided to the receiver processor 456. The receiver processor 456 and the multi-antenna receiver processor 458 implement various signal processing functions of the L1 layer. The multi-antenna receiver processor 458 performs receive analog precoding / beamforming operations on the baseband multicarrier symbol stream from the receiver 454. The receiver processor 456 uses a Fast Fourier Transform (FFT) to convert the baseband multicarrier symbol stream after the receive analog precoding / beamforming operations from the time domain to the frequency domain. In the frequency domain, the physical layer data signal and the reference signal are demultiplexed by the receiver processor 456, where the reference signal is used for channel estimation, and the data signal is recovered in the multi-antenna receiver processor 458 after multi-antenna detection to recover any spatial stream destined for the first communication device 450. Symbols on each spatial stream are demodulated and recovered in the receive processor 456, generating soft decisions. The receive processor 456 then decodes and deinterleaves the soft decisions to recover the upper-layer data and control signals transmitted by the second communication device 410 over the physical channel. The upper-layer data and control signals are then provided to the controller / processor 459. The controller / processor 459 implements the functions of Layer 2. The controller / processor 459 may be associated with a memory 460 storing program code and data. The memory 460 may be referred to as computer-readable media. In the transmission from the second communication device 410 to the second communication device 450, the controller / processor 459 provides multiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport and logical channels to recover upper-layer data packets from the core network. The upper-layer data packets are then provided to all protocol layers above Layer 2. Various control signals may also be provided to Layer 3 for Layer 3 processing.
[0323] In the transmission from the first communication device 450 to the second communication device 410, at the first communication device 450, a data source 467 is used to provide upper-layer data packets to the controller / processor 459. The data source 467 represents all protocol layers above the L2 layer. Similar to the transmission functions at the second communication device 410 described in the transmission from the second communication device 410 to the first communication device 450, the controller / processor 459 implements header compression, encryption, packet segmentation and reordering, and multiplexing between logical and transport channels based on radio resource allocation, implementing L2 layer functions for the user plane and control plane. The controller / processor 459 is also responsible for retransmitting lost packets and signaling to the second communication device 410. Transmit processor 468 performs modulation mapping and channel coding processing, while multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based and non-codebook-based precoding, and beamforming processing. Subsequently, transmit processor 468 modulates the generated spatial stream into a multi-carrier / single-carrier symbol stream. After analog precoding / beamforming operations in multi-antenna transmit processor 457, the stream is provided to different antennas 452 via transmitter 454. Each transmitter 454 first converts the baseband symbol stream provided by multi-antenna transmit processor 457 into a radio frequency symbol stream before providing it to antenna 452.
[0324] In the transmission from the first communication device 450 to the second communication device 410, the function at the second communication device 410 is similar to the receiving function at the first communication device 450 described in the transmission from the second communication device 410 to the first communication device 450. Each receiver 418 receives radio frequency signals through its corresponding antenna 420, converts the received radio frequency signals into baseband signals, and provides the baseband signals to the multi-antenna receiving processor 472 and the receiving processor 470. The receiving processor 470 and the multi-antenna receiving processor 472 jointly implement the L1 layer function. The controller / processor 475 implements the L2 layer function. The controller / processor 475 may be associated with a memory 476 storing program code and data. The memory 476 may be referred to as computer-readable media. In the transmission from the first communication device 450 to the second communication device 410, the controller / processor 475 provides multiplexing between the transmission and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover the upper-layer data packets from the first communication device 450. Upper-layer packets from the controller / processor 475 can be provided to the core network.
[0325] As one embodiment, the second communication device may only support attached Figure 4 Some modules / functions in [the system / program].
[0326] As one embodiment, the first communication device 450 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used with the at least one processor, and the first communication device 450 at least: receives a first message through a first air interface, the first message requesting the resumption of communication, the first message including a first value, wherein the first value is for integrity protection; in response to receiving the first message, sends a second message through a second interface, the second message indicating the resumption of communication, the second message including the first value; receives a third message through the second interface, the third message indicating a target key; generates a first key, wherein the first key is used for encryption or integrity protection; wherein the first air interface is an air interface other than the Uu interface; the second interface is an interface between the terminal and the core network; the terminal is a UE; the first key is the output of a first function; the input of the first function depends on a first parameter set; the first parameter set includes an algorithm identifier, the length of the algorithm identifier, and the target key.
[0327] As one embodiment, the first communication device 450 includes: a memory storing a computer-readable instruction program that, when executed by at least one processor, generates actions including: receiving a first message via a first air interface, the first message requesting the resumption of communication, the first message including a first value, wherein the first value is for integrity protection; in response to receiving the first message, sending a second message via a second interface, the second message indicating the resumption of communication, the second message including the first value; receiving a third message via the second interface, the third message indicating a target key; generating a first key, wherein the first key is used for encryption or integrity protection; wherein the first air interface is an air interface other than the Uu interface; the second interface is an interface between the terminal and the core network; the terminal is a UE; the first key is the output of a first function; the input of the first function depends on a first parameter set; the first parameter set includes an algorithm identifier, the length of the algorithm identifier, and the target key.
[0328] As an example, the first communication device 450 corresponds to the first node in this application.
[0329] As an example, the second communication device 410 corresponds to the second node in this application.
[0330] As an example, the first communication device 450 is a UE.
[0331] As an example, the first communication device 450 is a mobile phone.
[0332] As one embodiment, the second communication device 450 is an AIoT device.
[0333] As one embodiment, receiver 454 (including antenna 452), receiver processor 456 and controller / processor 459 are used in this application to receive the first message.
[0334] As one embodiment, receiver 454 (including antenna 452), receiver processor 456 and controller / processor 459 are used in this application to receive the third message.
[0335] As one embodiment, a transmitter 454 (including an antenna 452), a transmitter processor 468, and a controller / processor 459 are used to transmit the at least one paging message in this application.
[0336] As one embodiment, a transmitter 454 (including an antenna 452), a transmitter processor 468, and a controller / processor 459 are used to transmit the first signaling in this application.
[0337] As one embodiment, transmitter 454 (including antenna 452), transmitter processor 468 and controller / processor 459 are used to transmit the second message in this application.
[0338] As one embodiment, transmitter 454 (including antenna 452), transmitter processor 468 and controller / processor 459 are used to transmit the fourth message in this application.
[0339] As one embodiment, transmitter 454 (including antenna 452), transmitter processor 468 and controller / processor 459 are used to transmit the fifth message in this application.
[0340] Example 5
[0341] Example 5 illustrates a wireless signal transmission flowchart according to an embodiment of this application, as shown in the attached diagram. Figure 5 As shown. (Attached) Figure 5 In this example, U01 corresponds to the first node of this application, U02 is the sender of the first message, and U03 is the core network node. It should be noted that the order in this example does not limit the signal transmission order or the implementation order in this application, and the steps in F51 and F52 are optional.
[0342] for First node U01In step S5101, a fourth message is sent; in step S5102, a fifth message is sent; in step S5103, a first paging message is sent; in step S5104, a first message is received; in step S5105, a second message is sent; in step S5106, a third message is received; in step S5107, a first key is generated; in step S5108, a first signaling is sent; and in step S5109, a second signaling is received.
[0343] for Second node U02 In step S5201, a fourth message is received; in step S5202, a first paging message is received; in step S5203, a first message is sent; in step S5204, a first signaling is received; and in step S5205, a second signaling is sent.
[0344] for Third node U03 In step S5301, a fifth message is received; in step S5302, a second message is received; and in step S5303, a third message is sent.
[0345] In embodiment 5, the first message requests the resumption of communication, and the first message includes a first value, wherein the first value is for integrity protection; the second message indicates the resumption of communication, and the second message includes the first value; the third message indicates a target key; and a first key is generated, wherein the first key is used for encryption or integrity protection.
[0346] Wherein, the first air interface is an air interface other than the Uu interface; the second interface is the interface between the terminal and the core network; the terminal is a UE; the first key is the output of a first function; the input of the first function depends on a first parameter set; the first parameter set includes an algorithm identifier, the length of the algorithm identifier, and the target key.
[0347] As an example, the interface between the first node U01 and the second node U02 is the first air interface.
[0348] As an example, the interface between the first node U01 and the third node U03 is the second interface.
[0349] As an example, the first message triggers the second message.
[0350] As an example, the second message triggers the third message.
[0351] As an example, the first node U01 is a UE.
[0352] As an example, the second node U02 is an AIoT device.
[0353] As an example, the communication link between the first node U01 and the second node U02 is not a secondary link.
[0354] As an example, the communication interface between the first node U01 and the second node U02 is not the Uu interface.
[0355] As an example, the second node U02 is not a mobile phone.
[0356] As an example, the second node U02 is not a UE.
[0357] As an example, the third node U03 is a core network node or a core network functional entity.
[0358] As an example, the third node U03 is a node that provides functionality for the core network.
[0359] As an example, the third node U03 is an AMF.
[0360] As an example, the third node U03 is an AIoT function.
[0361] As an example, the first node U01 is the reader of the second node U02.
[0362] As an example, Appendix Figure 5 The numbering order of the steps shown is the chronological order.
[0363] As an example, step S5102 is later than step S5101.
[0364] As an example, step S5103 is later than step S5102.
[0365] As an example, step S5104 is later than step S5103.
[0366] As an example, step S5105 is later than step S5104.
[0367] As an example, step S5106 is later than step S5105.
[0368] As an example, step S5107 is later than step S5106.
[0369] As an example, step S5108 is later than step S5107.
[0370] As an example, step S5109 is later than step S5108.
[0371] As an example, the fourth message indicates the end of communication.
[0372] As an example, the fourth message carries at least one of a first temporary identifier and an identifier of a second type of key.
[0373] As one embodiment, the first temporary identifier is an identifier used by the sender of the first message to resume communication.
[0374] As one embodiment, the first parameter set includes the second type of key.
[0375] As an example, the first temporary identifier is longer than the AS identifier used during communication.
[0376] As an example, the first type of key is Key aiot Key a-iot Key nra Key nraiot Key nra-iot One of them.
[0377] As an example, the second type of key is Key aiot-sess Key a-iot-sess Key nra-sess Key nraiot-sess Key nra-iot-sess One of them.
[0378] As an example, the name of the second type of key includes the name of the first type of key and at least one other symbol.
[0379] As an example, step S5101 can be omitted when it is not necessary to indicate the content carried by the fourth message to the second node U02. The second node U02 can use a fixed identifier, or obtain an identifier or key through the core network, or generate an identifier or key using a predefined algorithm. Indicating via the fourth message of the first node U01 has the advantages of being simple to implement, more secure, and more reliable.
[0380] As one example, the fifth message includes context specific to the sender of the first message.
[0381] As an example, step S5102 can be omitted when the core network always maintains the context of the sender of the first message. Sending the fifth message can support more flexible and dynamic scenarios. It can support scenarios where the first node U01 moves.
[0382] As an example, the context for the first message sender includes at least one of the following: the access layer identifier of the first message sender, at least a portion of the permanent identifier of the sender of the first message, security information used in communication with the first message sender, a key or key identifier used in communication with the second node U02, a first type key used in communication with the second node U02, and a second type key used in communication with the second node U02.
[0383] As an example, the context for the first message sender includes: historical information about communication with the second node U02.
[0384] As an example, the context for the first message sender includes: statistical information about communication with the second node U02.
[0385] As an example, the context for the first message sender includes: logs of communication with the second node U02.
[0386] As an example, the context for the first message sender includes at least one of the location information of the first node U01 and the location information of the second node U02.
[0387] As an example, the first paging message paging the second node U02.
[0388] As one embodiment, the first paging message paging the first node group, and the second node U02 belongs to the first node group.
[0389] As one example, the first paging message is directed to multiple devices.
[0390] As an example, the first paging message is not directed at other UEs.
[0391] As an example, the at least one paging message is not directed to other UEs.
[0392] As one embodiment, the first paging message indicates the second identifier.
[0393] As one embodiment, the first paging message indicating the second identifier includes: the first paging message includes the second identifier.
[0394] As one embodiment, the first paging message indicates that the second identifier includes: the first paging message includes a portion of the bits of the second identifier. For example, the first n bits or the last n bits, where n is a positive integer.
[0395] As a sub-example of this embodiment, n is one of 1, 2, 4, 6, 8, 16.
[0396] As one embodiment, the first paging message indicating the second identifier includes: an index of the identifier of the terminal indicated by the first paging message.
[0397] As an example, the advantage of the above method is that it saves signaling overhead.
[0398] As one example, the second node U02 responds to the first paging message and initiates a random access procedure.
[0399] As one example, initiating random access includes sending signals during the random access process.
[0400] As one embodiment, the signals in the random access process include sending a random access request.
[0401] As one example, the signals in the physical layer of the random access process.
[0402] As one example, the signal preamble during the random access process.
[0403] As one example, initiating random access may also include receiving a response to the random access.
[0404] As an example, the second node U02 can repeatedly transmit signals during the random access process. This can increase the signal power.
[0405] As one embodiment, each signal transmitted by the second node U02 may be accompanied by a signal transmitted by the first node U01. Since the second node U02 has no amplifier or even energy storage, it needs to use the signal from the first node U01 to transmit the signal to be transmitted.
[0406] As one embodiment, the initiation of random access procedure includes sending data and / or receiving a response.
[0407] As an example, the first message belongs to the random access procedure.
[0408] As one example, the first message is accompanied by a random access procedure.
[0409] As an example, the first message is unicast.
[0410] As a sub-implementation of this embodiment, the advantage of the first message being unicast is that it is more targeted and has lower complexity.
[0411] As an example, the first message is multicast.
[0412] As a sub-implementation of this embodiment, the first message is multicast, which facilitates the automatic search for or determination of the best reader.
[0413] As an example, the third message is a NAS message.
[0414] As an example, the first node U01 generates the first key based on the third message.
[0415] As an example, the procedure within F52 is used to update the key. The steps within F2 are not used when updating the key is not required.
[0416] As an example, step S5103 can be omitted, for example, when the first node U01 and the second node U02 always start communicating at an agreed time. The advantage of using step S5103 is increased flexibility.
[0417] As one example, the first signaling indicates a key update.
[0418] As one embodiment, the first signaling includes an identifier of a second type of key, at least one of Nonce_1 and Nonce_2.
[0419] As an example, Nonce_1 and Nonce_2 are used to generate the key.
[0420] As an example, what Nonce_1 and Nonce_2 are is common knowledge in the art.
[0421] As an example, the key update indicated by the first signaling is an update of the second type of key.
[0422] As an example, once communication is established, the first type of key cannot be updated.
[0423] As one example, the second signaling indicates information about the key update.
[0424] As one example, the key update information includes parameters used to generate the key.
[0425] As an example, the key update information includes an indication that the key update is complete.
[0426] As an example, the key update information includes an indication of at least one of Nonce_1 and Nonce_2.
[0427] As an example, the advantages of the above method are that it can improve security while keeping the complexity low.
[0428] As an example, the data packets communicated between the first node U01 and the second node U02 carry at least a portion of the identifier bits of the second type key.
[0429] Example 6
[0430] Example 6 illustrates a schematic diagram illustrating how the generation of a first numerical value according to an embodiment of this application depends on a first identifier and a second identifier, as shown in the attached diagram. Figure 6 As shown.
[0431] As an example, the generation of the first value depends on the meaning of the first identifier and the second identifier, including: the first identifier is the function input for generating the first value.
[0432] As an example, the generation of the first value depends on the meaning of the first identifier and the second identifier, including that a portion of the bits of the first identifier are the function input for generating the first value.
[0433] As an example, the generation of the first value depends on the meaning of the first identifier and the second identifier, including that a portion of the bits of the second identifier are the function input for generating the first value.
[0434] As an example, the generation of the first value depends on the meaning of the first identifier and the second identifier, including: the second identifier is the function input for generating the first value.
[0435] As an example, the generation of the first value depends on the meaning of the first identifier and the second identifier, which means that the first value is generated only when the second identifier is the identifier of the reader saved by the sender of the first message.
[0436] As an example, the saved reader's identifier is the reader's identifier from the last communication.
[0437] As an example, the generation of the first value depends on the meaning of the first identifier and the second identifier, including the XOR of the first identifier and the second identifier as the function input for generating the first value.
[0438] As an example, the generation of the first value depends on the meaning of the first identifier and the second identifier, which includes: the concatenation of the first identifier and the second identifier is the function input for generating the first value.
[0439] Example 7
[0440] Example 7 illustrates a schematic diagram of a first parameter set and a first key according to an embodiment of this application, as shown in the attached diagram. Figure 7 As shown.
[0441] As an example, Appendix Figure 7 In this context, F() represents the first function.
[0442] As an example, the first key is the output of the first function.
[0443] As an example, the input parameters of the first function are the first parameter set.
[0444] As an example, some of the input parameters of the first function belong to the first parameter set.
[0445] As an example, the input key in the input parameters of the first function belongs to the first parameter set.
[0446] As an example, the input key is the first type of key.
[0447] As an example, the first key is a second type of key.
[0448] As an example, the first key is used for encryption.
[0449] As an example, the first key is used for encryption of AIoT communication.
[0450] As an example, the first key is used for integrity protection.
[0451] As one example, the first key is used for integrity protection of AIoT communication.
[0452] As an example, the input parameters of the first function include multiple parameters.
[0453] As an example, at least one of the input parameters is generated from at least a portion of the parameters in the first parameter set.
[0454] As an example, generating at least one of the input parameters from at least a portion of the parameters in the first parameter set includes: the result of the XOR of at least two parameters in the first parameter set is the input parameter.
[0455] As an example, generating at least one of the input parameters from at least a portion of the parameters in the first parameter set includes: the result of the XOR of multiple two parameters in the first parameter set is the input parameter.
[0456] As an example, during the XOR operation, if the number of bits in two input values is unequal, the shorter input value can be padded with 0s or 1s to make the number of bits in the corrected input values equal. If multiple input values have unequal bit lengths, the shorter input values can be padded with 0s or 1s based on the longest input value to make the number of bits in the multiple input values equal.
[0457] As an example, some parameters in the first parameter set come from the third message.
[0458] As an example, some parameters in the first parameter set are derived from the first message.
[0459] As an example, some parameters in the first parameter set come from the context saved by the terminal.
[0460] Example 8
[0461] Example 8 illustrates a schematic diagram of verification integrity depending on a first and a second numerical value according to an embodiment of this application, as shown in the attached diagram. Figure 8 As shown.
[0462] As an example, the integrity verification includes verifying whether the first value and the second value are equal. When the first value and the second value are equal, the integrity verification passes; when the first value and the second value are not equal, the integrity verification fails.
[0463] As an example, the integrity verification includes verifying whether the first value can be generated from the second value. When the first value can be generated from the second value, the integrity verification passes; when the first value cannot be generated from the second value, the integrity verification fails.
[0464] As one embodiment, the generation of the first value from the second value includes: the second value is obtained by shifting or cyclically shifting the second value.
[0465] As one embodiment, the generation of the first value from the second value includes: XORing the second value with a pre-configured sequence to obtain the first value.
[0466] As a sub-implementation of this embodiment, the pre-configured sequence is predefined or fixed.
[0467] As a sub-example of this embodiment, the pre-configured sequence is configured by the reader in the previous communication.
[0468] As a sub-implementation of this embodiment, the pre-configured sequence is configured at the application layer.
[0469] As one embodiment, the generation of the first value from the second value includes: reversing the bits of the second value to obtain the first value.
[0470] Typically, the first value is neither all 0s nor all 1s.
[0471] Typically, the second value is neither all 0s nor all 1s.
[0472] As one example, the first value includes multiple bits.
[0473] As one example, the second value includes multiple bits.
[0474] As an example, the integrity verification includes verifying whether the second value can be generated from the first value. When the second value can be generated from the first value, the integrity verification passes; when the second value cannot be generated from the first value, the integrity verification fails.
[0475] As one embodiment, the generation of the second value from the first value includes: the first value is shifted or cyclically shifted to obtain the second value.
[0476] As one embodiment, the generation of the second value from the first value includes: XORing the first value with a pre-configured sequence to obtain the second value.
[0477] As a sub-implementation of this embodiment, the pre-configured sequence is predefined or fixed.
[0478] As a sub-example of this embodiment, the pre-configured sequence is configured by the reader in the previous communication.
[0479] As a sub-implementation of this embodiment, the pre-configured sequence is configured at the application layer.
[0480] As one embodiment, the generation of the second value from the first value includes: reversing the bits of the first value to obtain the second value.
[0481] Example 9
[0482] Example 9 illustrates a schematic diagram of a first air interface according to an embodiment of this application, as shown in the attached diagram. Figure 9 As shown.
[0483] Appendix Figure 9This application illustrates a communication scenario in which network nodes include base stations and / or core networks, the first node is a UE, the second node is a device, and the method proposed in this application supports more devices.
[0484] As an example, the first node pagees the second node through the first message.
[0485] As one embodiment, the communication interface between the second node and the first node is a first air interface.
[0486] As an example, the first air interface is not a Uu interface.
[0487] As an example, the first air interface is not a secondary link interface.
[0488] As an example, the second node is a passive node.
[0489] As an example, the communication interface between the first node and the network node is a Uu interface.
[0490] As an example, the first node is not an IAB (integrated access backhaul) device.
[0491] As an example, the first paging message is sent through the first air interface.
[0492] As an example, the first data is sent through the first air interface.
[0493] As one example, the second message is sent through the first air interface.
[0494] As an example, the initiation of random access is a random access for the first node.
[0495] As an example, the initiation of random access is not a random access to the network.
[0496] As an example, the first paging message may be triggered by a network node.
[0497] As an example, the protocol structure on the first air interface does not include the PDCP sublayer.
[0498] As an example, the protocol structure on the first air interface does not include the RRC sublayer.
[0499] As an example, the protocol structure on the first air interface does not include the RLC sublayer.
[0500] As an example, the protocol structure on the first air interface does not include the SDAP sublayer.
[0501] As one example, the first air interface is the interface between the reader and the AIoT device.
[0502] As an example, the first node is a reader.
[0503] As one embodiment, the interface between the first node and the network node includes a Uu interface.
[0504] As an example, the method proposed in this application does not rely on the first node needing to be connected to the network. The method proposed in this application allows the first node to be outside of coverage.
[0505] Example 10
[0506] Example 10 illustrates a structural block diagram of a processing apparatus for a first node according to an embodiment of this application; as shown in the appendix. Figure 10 As shown. In the appendix Figure 10 In the terminal, the processing device 1000 includes a first receiver 1001, a first transmitter 1002, and a first processor 1003.
[0507] In embodiment 10, the processing device of the terminal includes the one or more processors and memory;
[0508] The memory is coupled to the one or more processors. The memory is used to store computer program code, which includes computer instructions. The one or more processors call the computer instructions to cause the first receiver 1001 of the terminal to receive a first message through a first air interface. The first message requests the resumption of communication. The first message includes a first value, wherein the first value is for integrity protection.
[0509] In response to receiving the first message, the first transmitter 1002 sends a second message through the second interface, the second message indicating the resumption of communication, and the second message includes the first value;
[0510] The first receiver 1001 receives a third message through the second interface, the third message indicating a target key; and generates a first key, wherein the first key is used for encryption or integrity protection.
[0511] Wherein, the first air interface is an air interface other than the Uu interface; the second interface is the interface between the terminal and the core network; the terminal is a UE; the first key is the output of a first function; the input of the first function depends on a first parameter set; the first parameter set includes an algorithm identifier, the length of the algorithm identifier, and the target key.
[0512] As an example, the first air interface is an air interface other than the PC5 interface.
[0513] As an example, the meaning of "the first air interface is an air interface other than the PC5 interface" is that the communication on the first air interface is not sidelink communication.
[0514] As an example, whether the target key is a first type key or a second type key depends on whether the terminal was the reader of the most recent communication of the sender of the first message. When the terminal was not the reader of the most recent communication of the sender of the first message, the target key is the second type key; when the terminal was not the reader of the most recent communication of the sender of the first message, the target key is the first type key.
[0515] Wherein, the first type of key generates the second type of key, and the first set of values includes the second type of key.
[0516] As one embodiment, the sending of the second message through the second interface depends on whether the terminal has saved the security context of the sender of the first message. The second message is sent only if the terminal has saved the security context of the sender of the first message.
[0517] As one embodiment, the second message includes a first temporary identifier, the reason for resuming communication, and whether the paging message originated from at least one of the core network;
[0518] The first temporary identifier is an identifier used by the sender of the first message to restore communication.
[0519] As an example, before receiving the first message, the first transmitter 1002 sends a fourth message through the first air interface, the fourth message indicating the end of communication, the fourth message carrying at least one of a first temporary identifier and an identifier of a second type of key;
[0520] Wherein, the first temporary identifier is an identifier used by the sender of the first message to resume communication; the first set of values includes the second type of key.
[0521] As an example, the first transmitter 1002 sends a fifth message through the second interface before receiving the first message, the fifth message including context for the sender of the first message;
[0522] The context for the first message sender includes at least one of the following: the access layer identifier of the first message sender, at least a portion of the permanent identifier of the sender of the first message, security information used in communication with the first message sender, and a key or key identifier used in communication with the first message sender.
[0523] As an example, the third message includes at least one of the following: historical information about the sender of the first message, at least a portion of bits of the sender's permanent identifier, key update period, and AIoT service address.
[0524] As one embodiment, the first transmitter 1002 sends a first signaling through the first air interface, the first signaling indicating a key update, the first signaling including an identifier of a second type of key, at least one of Nonce_1 and Nonce_2;
[0525] The first receiver 1001 receives a second signaling through the second interface, the second signaling indicating the key update information.
[0526] As an example, the first node is a user equipment (UE).
[0527] As an example, the first node is a terminal that supports large latency differences.
[0528] As an example, the first node is an NTN-enabled terminal.
[0529] As an example, the first node is an aircraft.
[0530] As an example, the first node is a vehicle-mounted terminal.
[0531] As an example, the first node is a mobile phone.
[0532] As an example, the first node is a ship.
[0533] As an example, the first node is an Internet of Things (IoT) terminal.
[0534] As an example, the first node is an industrial Internet of Things (IIoT) terminal.
[0535] As one embodiment, the first receiver 1001 includes at least one of the following in embodiment 4: antenna 452, receiver 454, receiver processor 456, multi-antenna receiver processor 458, controller / processor 459, memory 460, or data source 467.
[0536] As one embodiment, the first transmitter 1002 includes at least one of the following in embodiment 4: antenna 452, transmitter 454, transmission processor 468, multi-antenna transmission processor 457, controller / processor 459, memory 460, or data source 467.
[0537] Example 11
[0538] Example 11 illustrates a schematic diagram of the structure of an A-IoT device according to an embodiment of this application, as shown in the attached diagram. Figure 11 As shown.
[0539] Appendix Figure 11In this embodiment, the A-IoT device 1400 includes an antenna 1401, an energy-related module 1404, and a processing-related module 1408. The A-IoT device 1400 may also include a matching network 1402 for matching the impedance between the antenna 1401 and other components, including a radio frequency (RF) energy harvester 1403 and a receiver-related module 1409. The A-IoT device 1400 may also include an energy harvester, which can be either an RF energy harvester 1403 or a non-RF energy harvester 1407. The RF energy harvester 1403 may include a rectifier that performs RF signal (AC) to DC conversion. The RF energy harvester 1403 and the receiver / transmitter may share the antenna 1401, or they may use independent antennas. The energy-related module 1404 may include a power management unit (PMU) 1405; the PMU 1405 is responsible for storing energy from the energy harvester in energy storage 1406 and supplying power to active component blocks that require power. The energy-related module 1404 may also include energy storage 1406; the energy storage 1406 stores energy collected from the energy harvester, and the energy storage 1406 may be a capacitor. The processing module 1408 may include a BB (Baseband) logic 1413, a memory 1418, and a clock generator 1419. The BB logic 1413 may include a decoder 1414, a controller 1415, and an encoder 1416. The memory 1418 may include two types: non-volatile memory (NVM), such as EEPROM, for permanent storage of the device ID; and a register for temporarily storing information needed for operation only when energy in the energy storage 1406 is available. The clock generator 1419 provides the required clock signal. The processing module 1408 may also include reception-related blocks 1409 and transmission-related blocks 1417. For different A-IoT devices, the reception-related blocks 1409 and transmission-related blocks 1417 may include different modules.
[0540] As an example, for an A-IoT device 1400 with a peak power consumption of approximately 1 μW, the receive correlation module 1409 may include an RF BPF 1410, an RF envelope detector (RF-ED), a BB LPF 1411, and a comparator 1412. The transmit correlation module 1417 may include a backscatter modulator.
[0541] As a non-limiting embodiment, the output of the matching network 1402 is processed sequentially by the RF BPF 1410, the RF envelope detector, the BB LPF 1411, and the comparator 1412 before being input to the BB logic 1413. The output of the BB logic 1413 is processed by the backscatter modulator and then transmitted by the antenna 1401.
[0542] As an example, for an A-IoT device 1400 with peak power consumption less than or equal to several hundred μW, if an external carrier wave is used, the receive-related module 1409 may include an RF BPF 1410, an LNA (Low-noise amplifier), an RF envelope detector, a BB amplifier, a BB LPF 1411, and a comparator / N-bit ADC 1412. The transmit-related module 1417 may include a large frequency shifter (e.g., tens of megahertz), a backscatter modulator, and a reflection amplifier. At least one of R2D (Reader to Device) / CW2D (Carrier-wave, or carrier-wave node, to Device) and D2R (Device to Reader) can be amplified by the reflection amplifier or the LNA. The large frequency shifter shifts the backscattered signal from one frequency (e.g., an FDD-DL frequency) to another frequency (e.g., an FDD-UL frequency).
[0543] As a non-limiting embodiment, the output of the matching network 1402 is processed sequentially through an RF BPF 1410, an LNA, an RF envelope detector, a BB amplifier, a BB LPF 1411, and a comparator / N-bit ADC 1412 before being input to the BB logic 1413. The output of the BB logic 1413 is then processed by a large frequency shifter, a backscatter modulator, and a reflection amplifier before being transmitted by the antenna 1401.
[0544] As an example, for an A-IoT device 1400 with peak power consumption less than or equal to several hundred μW, if an internally generated carrier wave is used and an RF envelope detector receiver is employed, the receive-related module 1409 may include an RF BPF 1410, an LNA, an RF envelope detector, a BB amplifier, a BB LPF 1411, and a comparator / N-bit ADC 1412. The transmit-related module 1417 may include a transmit modulator (Tx modulator), a digital-to-analog converter (DAC), a low-pass filter, a mixer, a local oscillator (LO) / FLL ( / PLL), and a power amplifier (PA).
[0545] As a non-limiting embodiment, the output of the matching network 1402 is processed sequentially through an RF BPF 1410, an LNA, an RF envelope detector, a BB amplifier, a BB LPF 1411, and a comparator / N-bit ADC 1412 before being input to the BB logic 1413. The output of the BB logic 1413 is then processed by a transmit modulator, a digital-to-analog converter, a low-pass filter, a mixer, a LO / FLL ( / PLL), and a power amplifier before being transmitted by the antenna 1401.
[0546] As an example, for an A-IoT device 1400 with peak power consumption less than or equal to several hundred μW, if an internally generated carrier wave is used and an IF envelope detector receiver is employed, the receive-related module 1409 may include an RF BPF 1410, an LNA, a mixer, an IF amplifier, an IF filter, an IF envelope detector (IF-ED), a BB amplifier, a BB LPF 1411, and a comparator / N-bit ADC 1412. The transmit-related module 1417 may include a transmit modulator, a digital-to-analog converter, a low-pass filter, a mixer, a LO / FLL ( / PLL), and a power amplifier. The IF amplifier amplifies the IF signal. The IF filter filters out unwanted RF and LO signals. The IF envelope detector detects the envelope from the IF signal. The mixer in the receive-related module 1409 down-converts the RF signal to the IF stage. Depending on the implementation, there can be one or two mixers for both the transmitter and receiver.
[0547] As a non-limiting embodiment, the output of the matching network 1402 is processed sequentially through an RF BPF 1410, an LNA, a mixer, an IF amplifier, an IF filter, an IF envelope detector, a BB amplifier, a BB LPF 1411, and a comparator / N-bit ADC 1412 before being input to the BB logic 1413. The output of the BB logic 1413 is processed by a transmit modulator, a digital-to-analog converter, a low-pass filter, a mixer, a LO / FLL ( / PLL), and a power amplifier before being transmitted by the antenna 1401.
[0548] As an example, for an A-IoT device 1400 with peak power consumption less than or equal to several hundred μW, if an internally generated carrierwave is used and a zero-IF (ZIF) receiver is employed, the receive-related module 1409 may include an RF BPF 1410, an LNA, a mixer, a BB amplifier, a BB LPF 1411, and a comparator / N-bit ADC 1412. The transmit-related module 1417 may include a transmit modulator, a digital-to-analog converter, a low-pass filter, a mixer, a LO / FLL ( / PLL), and a power amplifier. The mixer in the receive-related module 1409 down-converts the RF signal to the BB stage. Depending on the implementation, there may be one or two mixers for both the transmitter and receiver.
[0549] As a non-limiting embodiment, the output of the matching network 1402 is processed sequentially through an RF BPF 1410, an LNA, a mixer, a BB amplifier, a BB LPF 1411, and a comparator / N-bit ADC 1412 before being input to the BB logic 1413. The output of the BB logic 1413 is processed by a transmit modulator, a digital-to-analog converter, a low-pass filter, a mixer, a LO / FLL ( / PLL), and a power amplifier before being transmitted by the antenna 1401.
[0550] In the above embodiments, the RF BPF 1410 is used to enhance selectivity; depending on the implementation, the RF BPF 1410 may not be present. The BB LPF 1411 is used to filter out harmonics and high-frequency components, improving the input signal quality of the comparator / ADC 1412; depending on the implementation, the BB LPF 1411 may not be present. The comparator 1412 is used to detect the high / low of the input signal. The backscatter modulator is used to convert the impedance into a modulated backscatter signal carrying the transmit signal from the BB logic 1413. The LNA is used to improve signal strength and receiver sensitivity. The RF envelope detector is used to detect the envelope from the RF signal. The BB amplifier is used to amplify the signal to improve signal strength. The transmit modulator is used to modulate the baseband bits according to the modulation scheme; the transmit modulator may be part of the BB logic 1413. The digital-to-analog converter is used to convert the digital signal to an analog signal. The low-pass filter is used to filter out unwanted signals. The mixer in the transmit correlation module 1417 is used to upconvert the baseband signal to the RF range. The LO (Local Optical Array) is used to generate the carrier frequency; the FLL ( / PLL) can be used for frequency synthesis, and depending on the implementation, the FLL ( / PLL) may not be present. The power amplifier is used to amplify the transmitted signal.
[0551] It should be noted that the structure of the A-IoT device in this example does not limit the specific implementation of A-IoT in this application. Specifically, depending on the different functions and actual application scenarios of the A-IoT device, the A-IoT device may adopt the structure of the A-IoT device in this example, or it may include only some modules of the structure of the A-IoT device in this example, and it may also include the aforementioned appendix. Figure 11 Other modules not shown.
[0552] Those skilled in the art will understand that all or part of the steps in the above methods can be implemented by a program instructing related hardware, and the program can be stored in a computer-readable storage medium, such as a read-only memory, hard disk, or optical disk. Optionally, all or part of the steps in the above embodiments can also be implemented using one or more integrated circuits. Accordingly, each module unit in the above embodiments can be implemented in hardware or in the form of software functional modules. This application is not limited to any specific combination of software and hardware. The user equipment, terminal, and UE in this application include, but are not limited to, drones, communication modules on drones, remote-controlled aircraft, aircraft, small aircraft, mobile phones, tablets, laptops, vehicle-mounted communication equipment, wireless sensors, internet cards, IoT terminals, RFID terminals, NB-IoT terminals, MTC (Machine Type Communication) terminals, eMTC (enhanced MTC) terminals, data cards, internet cards, vehicle-mounted communication equipment, low-cost mobile phones, low-cost tablets, satellite communication equipment, ship communication equipment, NTN user equipment, and other wireless communication equipment. The base station or system equipment in this application includes, but is not limited to, macrocell base stations, microcell base stations, home base stations, relay base stations, gNB (NR Node B), TRP (Transmitter Receiver Point), NTN base stations, satellite equipment, flight platform equipment, and other wireless communication equipment.
[0553] This invention may be practiced in other specified forms without departing from its core or essential characteristics. Therefore, the embodiments disclosed herein should in any way be considered descriptive rather than restrictive. The scope of the invention is defined by the appended claims rather than the foregoing description, and all modifications within their equivalent meaning and scope are considered to be included therein.
Claims
1. A method used in a terminal for wireless communication, wherein, include: A first message is received through the first air interface. The first message requests the resumption of communication. The first message includes a first value, wherein the first value is for integrity protection. In response to receiving the first message, a second message is sent through the second interface, the second message indicating the resumption of communication, and the second message includes the first value; Receive a third message through the second interface, the third message indicating a target key; generate a first key, wherein the first key is used for encryption or integrity protection; Wherein, the first air interface is an air interface other than the Uu interface; the second interface is the interface between the terminal and the core network; the terminal is a UE; the first key is the output of a first function; the input of the first function depends on a first parameter set; the first parameter set includes an algorithm identifier, the length of the algorithm identifier, and the target key.
2. The method in the terminal according to claim 1, characterized in that, The first air interface is an air interface other than the PC5 interface.
3. The method in the terminal according to claim 1 or 2, characterized in that, Whether the target key is a first type key or a second type key depends on whether the terminal was the reader of the most recent communication of the sender of the first message. When the terminal was the reader of the most recent communication of the sender of the first message, the target key is the second type key. When the terminal was not the reader of the most recent communication of the sender of the first message, the target key is the first type key. Wherein, the first type of key generates the second type of key, and the first parameter set includes the second type of key.
4. The method in the terminal according to any one of claims 1 to 3, characterized in that, The sending of the second message via the second interface depends on whether the terminal has saved the security context of the sender of the first message. The second message is sent only if the terminal has saved the security context of the sender of the first message.
5. The method in the terminal according to any one of claims 1 to 4, characterized in that, The second message includes a first temporary identifier, the reason for restoring communication, and whether the paging message originated from at least one of the core networks; The first temporary identifier is an identifier used by the sender of the first message to restore communication.
6. The method in the terminal according to any one of claims 1 to 5, characterized in that, include: Before receiving the first message, a fourth message is sent through the first air interface, the fourth message indicating the end of communication, the fourth message carrying at least one of a first temporary identifier and an identifier of a second type of key; Wherein, the first temporary identifier is an identifier used by the sender of the first message to resume communication; the first parameter set includes the second type of key.
7. The method in the terminal according to any one of claims 1 to 6, characterized in that, include: Before receiving the first message, a fifth message is sent through the second interface, the fifth message including context for the sender of the first message; The context for the first message sender includes at least one of the following: the access layer identifier of the first message sender, at least a portion of the permanent identifier of the sender of the first message, security information used in communication with the first message sender, and a key or key identifier used in communication with the first message sender.
8. The method in the terminal according to any one of claims 1 to 7, characterized in that, The third message includes at least one of the following: historical information about the sender of the first message, at least a portion of bits of the sender's permanent identifier, key update period, and AIoT service address.
9. The method in the terminal according to any one of claims 1 to 8, characterized in that, include: A first signaling message is sent through the first air interface, the first signaling message indicating a key update, the first signaling message including an identifier of a second type of key, at least one of Nonce_1 and Nonce_2; The second signaling is received through the second interface, and the second signaling indicates information about the key update.
10. A terminal used for wireless communication, wherein, include: One or more processors and memory; The memory is coupled to the one or more processors, the memory being used to store computer program code, the computer program code including computer instructions, and the one or more processors invoking the computer instructions to cause the terminal to execute the resource allocation method as described in any one of claims 1-9.