Communication method, communication device, communication system, storage medium, and program product
By updating the key during the RRC connection recovery process, the terminal mobility robustness issue is resolved, and security and integrity protection between the terminal and access network equipment is achieved, avoiding interruption of service data transmission.
Patent Information
- Application Number
- PCT/CN2025/093552
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-08
- Publication Date
- 2026-11-12
AI Technical Summary
How to improve the mobility robustness of terminals in RRC inactive state to avoid interruption of service data transmission caused by key updates.
During the RRC connection recovery process, key updates are performed. Through cooperation between access network equipment and core network equipment, key information between the terminal and access network equipment is determined and updated for security and integrity protection.
It enhances the mobility and robustness of the terminal, avoids interruption of business data transmission due to key updates, and improves the service performance of the terminal.
Smart Images

Figure CN2025093552_12112026_PF_FP_ABST
Abstract
Description
Communication methods, communication equipment, communication systems, storage media and software products Technical Field
[0001] This disclosure relates to the field of communication technology, and in particular to a communication method, communication device, communication system, storage medium, and program product. Background Technology
[0002] Currently, network environments have introduced an RRC inactive state in the terminal's radio resource control (RRC) state. When data transmission is not required, the terminal remains in the RRC inactive state, reducing communication with the network, thereby saving power and lowering network connection latency. Summary of the Invention
[0003] Improving the robustness of terminal mobility is a problem that needs to be solved.
[0004] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.
[0005] According to a first aspect of the present disclosure, a communication method is provided, executed by a first access network device. The method includes: receiving an RRC connection recovery request message sent by a terminal; and sending a first message to a core network device based on the RRC connection recovery request message. The first message is used to trigger the core network device to determine first key information. The first key information is used for key updates between the terminal and the first access network device. The updated key is used for security protection and / or integrity protection between the terminal and the first access network device.
[0006] According to a second aspect of the present disclosure, a communication method is provided, executed by a terminal. The method includes: sending an RRC connection recovery request message to a first access network device to trigger the first access network device to send a first message to a core network device based on the RRC connection recovery request message; the first message is used to trigger the core network device to determine first key information; the first key information is used for key updates between the terminal and the first access network device; and the updated key is used for security protection and / or integrity protection between the terminal and the first access network device.
[0007] According to a third aspect of the present disclosure, a communication method is proposed, executed by a core network device. The method includes: receiving a first message sent by a first access network device, the first message being used to trigger the core network device to determine first key information, the first key information being used for key updates between a terminal and the first access network device, the updated key being used for security protection and / or integrity protection between the terminal and the first access network device, and the first message being sent by the first access network device upon receiving an RRC connection recovery request message sent by the terminal.
[0008] According to a fourth aspect of the present disclosure, a communication method is proposed, applied to a communication system, the communication system including a first access network device, a terminal, and a core network device. The method includes: the terminal sending an RRC connection recovery request message to the first access network device; the first access network device sending a first message to the core network device based on the RRC connection recovery request message; the first message being used to trigger the core network device to determine first key information; the first key information being used for key updates between the terminal and the first access network device; and the updated key being used for security protection and / or integrity protection between the terminal and the first access network device.
[0009] According to a fifth aspect of the present disclosure, a first access network device is provided. The first access network device includes: a transceiver module configured to receive an RRC connection recovery request message sent by a terminal; and based on the RRC connection recovery request message, to send a first message to a core network device, the first message being used to trigger the core network device to determine first key information, the first key information being used for key updates between the terminal and the first access network device, and the updated key being used for security protection and / or integrity protection between the terminal and the first access network device.
[0010] According to a sixth aspect of the present disclosure, a terminal is provided. The terminal includes: a transceiver module configured to send an RRC connection recovery request message to a first access network device, which triggers the first access network device to send a first message to a core network device based on the RRC connection recovery request message. The first message triggers the core network device to determine first key information. The first key information is used for key updates between the terminal and the first access network device. The updated key is used for security protection and / or integrity protection between the terminal and the first access network device.
[0011] According to a seventh aspect of the present disclosure, a core network device is provided. The core network device includes: a transceiver module configured to receive a first message sent by a first access network device. The first message triggers the core network device to determine first key information. The first key information is used for key updates between a terminal and the first access network device. The updated key is used for security and / or integrity protection between the terminal and the first access network device. The first message is sent by the first access network device upon receiving an RRC connection recovery request message from the terminal.
[0012] According to an eighth aspect of the present disclosure, a communication device is provided, comprising: one or more processors, and one or more memories for storing a computer program; wherein the processor executes the computer program to implement the communication method of any one of the first to third aspects.
[0013] According to a ninth aspect of the present disclosure, a communication system is provided, including a first access network device, a terminal, and a core network device, wherein the first access network device is configured to implement the communication method as described in the first aspect; the terminal is configured to implement the communication method as described in the second aspect; and the core network device is configured to implement the communication method as described in the third aspect.
[0014] According to a tenth aspect of the present disclosure, a computer-readable storage medium is provided that stores a computer program thereon, wherein the computer program, when executed by a processor, implements the communication method of any one of the first to third aspects described above.
[0015] According to the eleventh aspect of the present disclosure, a computer program product is provided, including a computer program that, when executed by a processor, implements the communication method of any one of the first to third aspects described above.
[0016] According to a twelfth aspect of the present disclosure, a computer program is provided, the computer program including code that, when executed by a processor, implements the communication method of any one of the first to third aspects described above.
[0017] The technical solutions provided in this disclosure can improve the robustness of terminal mobility. Attached Figure Description
[0018] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments of the invention and, together with the description, serve to explain the principles of the embodiments of the invention.
[0019] Figure 1A is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.
[0020] Figure 1B is an exemplary interactive schematic diagram of a communication method according to an embodiment of the present disclosure.
[0021] Figure 1C is an exemplary interactive schematic diagram of a communication method according to an embodiment of the present disclosure.
[0022] Figure 1D is an exemplary interactive schematic diagram of a communication method according to an embodiment of the present disclosure.
[0023] Figure 1E is an exemplary interactive schematic diagram of a communication method according to an embodiment of the present disclosure.
[0024] Figure 1F is an exemplary interactive schematic diagram of a communication method according to an embodiment of the present disclosure.
[0025] Figure 1G is an exemplary interactive schematic diagram of a communication method according to an embodiment of the present disclosure.
[0026] Figure 2 is an exemplary interactive schematic diagram of a communication method according to an embodiment of the present disclosure.
[0027] Figure 3 is an exemplary interactive schematic diagram of a communication method according to an embodiment of the present disclosure.
[0028] Figure 4 is an exemplary interactive schematic diagram of a communication method according to an embodiment of the present disclosure.
[0029] Figure 5 is a schematic diagram of the structure of a communication device according to an embodiment of the present disclosure.
[0030] Figure 6A is a schematic diagram of the structure of a communication device according to an embodiment of the present disclosure.
[0031] Figure 6B is a schematic diagram of the chip structure according to an embodiment of the present disclosure. Detailed Implementation
[0032] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.
[0033] In a first aspect, embodiments of this disclosure propose a communication method executed by a first access network device. The method includes: receiving an RRC connection recovery request message sent by a terminal; and sending a first message to a core network device based on the RRC connection recovery request message. The first message is used to trigger the core network device to determine first key information. The first key information is used for key updates between the terminal and the first access network device. The updated key is used for security protection and / or integrity protection between the terminal and the first access network device.
[0034] In the above embodiments, after receiving the RRC connection recovery request message sent by the terminal, the first access network device triggers the core network device to determine the first key information for key updates between the terminal and the first access network device. That is, this embodiment performs key updates during the RRC connection recovery process, thus avoiding interruptions in service data transmission due to key updates during subsequent data transmission, which would otherwise affect the terminal's service performance. This enhances the robustness of terminal mobility.
[0035] In some embodiments of the first aspect, the above method further includes: receiving a second message sent by a core network device based on a first message, the second message carrying first key information; and sending the first key information to a terminal for the terminal to perform key updates.
[0036] In conjunction with some embodiments of the first aspect, in some embodiments, the first key information is carried in downlink signaling associated with the transport block (TB) where the RRC connection recovery message sent to the terminal is located. The downlink signaling includes one of the following: downlink control information (DCI) for scheduling the TB; medium access control (MAC) control element (CE); and RRC signaling.
[0037] In conjunction with some embodiments of the first aspect, in some embodiments, the downlink signaling is MAC CE or RRC signaling, the downlink signaling is unencrypted, and / or, the downlink signaling is protected for integrity using an updated key.
[0038] In conjunction with some embodiments of the first aspect, in some embodiments the above method further includes: updating the key based on the first key information.
[0039] In conjunction with some embodiments of the first aspect, in some embodiments, the updated key is also used to provide security and / or integrity protection for third messages between the terminal and the first access network device; wherein the third message includes at least one of the following: an RRC connection recovery message sent to the terminal; uplink information; downlink information.
[0040] In conjunction with some embodiments of the first aspect, in some embodiments, the third message does not include the RRC connection recovery message, which is used for security and / or integrity protection based on the key used by the terminal before entering the RRC disconnected state.
[0041] In conjunction with some embodiments of the first aspect, in some embodiments, the terminal locally stores second key information, the second key information is in an available state, and the key used by the terminal before entering the RRC disconnected state is determined based on the second key information; or, the second key information is in an unavailable state, and the key used by the terminal before entering the RRC disconnected state is the key stored locally by the terminal.
[0042] In conjunction with some embodiments of the first aspect, in some embodiments, the first message carries at least one of the following: an identifier of the terminal; an identifier of a first connection between the second access network device and the core network device, the first connection being associated with the terminal; wherein the second access network device is an anchor device of the first access network device.
[0043] Secondly, this disclosure provides a communication method executed by a terminal. The method includes: sending an RRC connection recovery request message to a first access network device to trigger the first access network device to send a first message to a core network device based on the RRC connection recovery request message. The first message is used to trigger the core network device to determine first key information. The first key information is used for key updates between the terminal and the first access network device. The updated key is used for security protection and / or integrity protection between the terminal and the first access network device.
[0044] In the above embodiments, the terminal sends an RRC connection recovery request message to the first access network device, triggering the core network device to determine the first key information for key updates between the terminal and the first access network device. In other words, this embodiment performs key updates during the RRC connection recovery process, thus avoiding subsequent interruptions in service data transmission due to key updates, which could affect the terminal's service performance. This enhances the robustness of terminal mobility.
[0045] In conjunction with some embodiments of the second aspect, in some embodiments, the above method further includes: receiving first key information sent by a first access network device, the first key information being used by the terminal to update the key, the first key information being sent by the first access network device upon receiving a second message sent by the core network device based on a first message, the second message carrying the first key information.
[0046] In conjunction with some embodiments of the second aspect, in some embodiments, the first key information is carried in the downlink signaling associated with the TB where the RRC connection recovery message sent by the first access network device is located. The downlink signaling includes one of the following: DCI, used for scheduling the TB; MAC CE; RRC signaling.
[0047] In conjunction with some embodiments of the second aspect, in some embodiments, the downlink signaling is MAC CE or RRC signaling, the downlink signaling is unencrypted, and / or, the downlink signaling is protected for integrity using an updated key.
[0048] In conjunction with some embodiments of the second aspect, in some embodiments the above method further includes: updating the key based on the first key information.
[0049] In conjunction with some embodiments of the second aspect, in some embodiments, the updated key is also used to provide security and / or integrity protection for third messages between the terminal and the first access network device; wherein the third message includes at least one of the following: receiving an RRC connection recovery message sent by the first access network device; uplink information; downlink information.
[0050] In conjunction with some embodiments of the second aspect, in some embodiments, the third message does not include the RRC connection recovery message, which is used for security and / or integrity protection based on the key used by the terminal before entering the RRC disconnected state.
[0051] In conjunction with some embodiments of the second aspect, in some embodiments, the terminal locally stores second key information, the second key information is in an available state, and the key used by the terminal before entering the RRC disconnected state is determined based on the second key information; or, the second key information is in an unavailable state, and the key used by the terminal before entering the RRC disconnected state is the key stored locally by the terminal.
[0052] Thirdly, this disclosure provides a communication method executed by a core network device. The method includes: receiving a first message sent by a first access network device, the first message being used to trigger the core network device to determine first key information, the first key information being used for key updates between the terminal and the first access network device, and the updated key being used for security protection and / or integrity protection between the terminal and the first access network device. The first message is sent by the first access network device upon receiving an RRC connection recovery request message sent by the terminal.
[0053] In the above embodiments, the core network device receives a first message sent by the first access network device based on an RRC connection recovery request message, and determines first key information for key updates between the terminal and the first access network device. In other words, this embodiment performs key updates during the RRC connection recovery process. This avoids subsequent interruptions in service data transmission due to key updates, thus preventing impact on terminal service performance and enhancing the robustness of terminal mobility.
[0054] In conjunction with some embodiments of the third aspect, in some embodiments, the above method further includes: sending a second message to a first access network device based on the first message, the second message carrying the first key information.
[0055] In conjunction with some embodiments of the third aspect, in some embodiments, the first message carries at least one of the following: an identifier of the terminal; an identifier of a first connection between the second access network device and the core network device, the first connection being associated with the terminal; wherein the second access network device is an anchor device of the first access network device.
[0056] Fourthly, embodiments of this disclosure provide a communication method applied to a communication system, the communication system including a first access network device, a terminal, and a core network device. The method includes: the terminal sending an RRC connection recovery request message to the first access network device; the first access network device sending a first message to the core network device based on the RRC connection recovery request message; the first message triggering the core network device to determine first key information; the first key information being used for key updates between the terminal and the first access network device; and the updated key being used for security protection and / or integrity protection between the terminal and the first access network device.
[0057] In conjunction with some embodiments of the fourth aspect, in some embodiments, the above method further includes: the core network device sending a second message to the first access network device based on the first message, the second message carrying first key information, the first access network device sending the first key information to the terminal, the first key information being used by the terminal to update the key.
[0058] In conjunction with some embodiments of the fourth aspect, in some embodiments, the first key information is carried in the downlink signaling associated with the TB where the RRC connection recovery message sent by the first access network device to the terminal is located. The downlink signaling includes one of the following: DCI, used for scheduling the TB; MAC CE; RRC signaling.
[0059] In conjunction with some embodiments of the fourth aspect, in some embodiments, the downlink signaling is MAC CE or RRC signaling, the downlink information is unencrypted, and / or, the downlink signaling is protected for integrity using an updated key.
[0060] In conjunction with some embodiments of the fourth aspect, in some embodiments, the above method further includes: the first access network device updating the key based on the first key information; and the terminal updating the key based on the first key information.
[0061] In conjunction with some embodiments of the fourth aspect, in some embodiments, the updated key is also used to provide security and / or integrity protection for third messages between the terminal and the first access network device; wherein the third message includes at least one of the following: an RRC connection recovery message sent by the first access network device to the terminal; uplink information; downlink information.
[0062] In conjunction with some embodiments of the fourth aspect, in some embodiments, the third message does not include the RRC connection recovery message, which is used for security and / or integrity protection based on the key used by the terminal before entering the RRC disconnected state.
[0063] In conjunction with some embodiments of the fourth aspect, in some embodiments, the terminal locally stores second key information, the second key information is in an available state, and the key used by the terminal before entering the RRC disconnected state is determined based on the second key information; or, the second key information is in an unavailable state, and the key used by the terminal before entering the RRC disconnected state is the key stored locally by the terminal.
[0064] In conjunction with some embodiments of the fourth aspect, in some embodiments, the communication system further includes a second access network device, and the first message carries at least one of the following: an identifier of the terminal; an identifier of a first connection between the second access network device and the core network device, the first connection being associated with the terminal; wherein the second access network device is an anchor device of the first access network device.
[0065] Fifthly, embodiments of this disclosure provide a first access network device. The first access network device includes: a transceiver module configured to receive an RRC connection recovery request message sent by a terminal; and based on the RRC connection recovery request message, to send a first message to a core network device, the first message being used to trigger the core network device to determine first key information, the first key information being used for key updates between the terminal and the first access network device, and the updated key being used for security protection and / or integrity protection between the terminal and the first access network device.
[0066] In conjunction with some embodiments of the fifth aspect, in some embodiments, the transceiver module is further configured to receive a second message sent by the core network device based on the first message, the second message carrying first key information; and to send the first key information to the terminal, the first key information being used by the terminal to update the key.
[0067] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first key information is carried in the downlink signaling associated with the TB where the RRC connection recovery message sent to the terminal is located. The downlink signaling includes one of the following: DCI, used for scheduling the TB; MAC CE; RRC signaling.
[0068] In conjunction with some embodiments of the fifth aspect, in some embodiments, the downlink signaling is MAC CE or RRC signaling, the downlink signaling is unencrypted, and / or, the downlink signaling is protected for integrity using an updated key.
[0069] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first access network device further includes: a processing module configured to perform key updates based on the first key information.
[0070] In conjunction with some embodiments of the fifth aspect, in some embodiments, the updated key is also used to provide security and / or integrity protection for third messages between the terminal and the first access network device; wherein the third message includes at least one of the following: an RRC connection recovery message sent to the terminal; uplink information; downlink information.
[0071] In conjunction with some embodiments of the fifth aspect, in some embodiments, the third message does not include the RRC connection recovery message, which is used for security and / or integrity protection based on the key used by the terminal before entering the RRC disconnected state.
[0072] In conjunction with some embodiments of the fifth aspect, in some embodiments, the terminal locally stores second key information, the second key information is in an available state, and the key used by the terminal before entering the RRC disconnected state is determined based on the second key information; or, the second key information is in an unavailable state, and the key used by the terminal before entering the RRC disconnected state is the key stored locally by the terminal.
[0073] In conjunction with some embodiments of the fifth aspect, in some embodiments, the first message carries at least one of the following: an identifier of the terminal; an identifier of a first connection between the second access network device and the core network device, the first connection being associated with the terminal; wherein the second access network device is an anchor device of the first access network device.
[0074] Sixthly, this disclosure provides a terminal. The terminal includes a transceiver module configured to send an RRC connection recovery request message to a first access network device, which triggers the first access network device to send a first message to a core network device based on the RRC connection recovery request message. The first message triggers the core network device to determine first key information. The first key information is used for key updates between the terminal and the first access network device. The updated key is used for security and / or integrity protection between the terminal and the first access network device.
[0075] In conjunction with some embodiments of the sixth aspect, in some embodiments, the transceiver module is further configured to receive first key information sent by the first access network device. The first key information is used by the terminal to update the key. The first key information is sent by the first access network device after receiving a second message sent by the core network device based on the first message. The second message carries the first key information.
[0076] In conjunction with some embodiments of the sixth aspect, in some embodiments, the first key information is carried in the downlink signaling associated with the TB where the RRC connection recovery message sent by the first access network device is located. The downlink signaling includes one of the following: DCI, used for scheduling the TB; MAC CE; RRC signaling.
[0077] In conjunction with some embodiments of the sixth aspect, in some embodiments, the downlink signaling is MAC CE or RRC signaling, the downlink signaling is unencrypted, and / or, the downlink signaling is protected for integrity using an updated key.
[0078] In conjunction with some embodiments of the sixth aspect, in some embodiments, the terminal further includes: a processing module configured to perform a key update based on the first key information.
[0079] In conjunction with some embodiments of the sixth aspect, in some embodiments, the updated key is also used to provide security and / or integrity protection for third messages between the terminal and the first access network device; wherein the third message includes at least one of the following: receiving an RRC connection recovery message sent by the first access network device; uplink information; downlink information.
[0080] In conjunction with some embodiments of the sixth aspect, in some embodiments, the third message does not include the RRC connection recovery message, which is used for security and / or integrity protection based on the key used by the terminal before entering the RRC disconnected state.
[0081] In conjunction with some embodiments of the sixth aspect, in some embodiments, the terminal locally stores second key information, the second key information is in an available state, and the key used by the terminal before entering the RRC disconnected state is determined based on the second key information; or, the second key information is in an unavailable state, and the key used by the terminal before entering the RRC disconnected state is the key stored locally by the terminal.
[0082] According to a seventh aspect of the present disclosure, a core network device is provided. The core network device includes: a transceiver module configured to receive a first message sent by a first access network device. The first message triggers the core network device to determine first key information. The first key information is used for key updates between a terminal and the first access network device. The updated key is used for security and / or integrity protection between the terminal and the first access network device. The first message is sent by the first access network device upon receiving an RRC connection recovery request message from the terminal.
[0083] In conjunction with some embodiments of the seventh aspect, in some embodiments, the transceiver module is further configured to send a second message to the first access network device based on the first message, the second message carrying the first key information.
[0084] In conjunction with some embodiments of the seventh aspect, in some embodiments, the first message carries at least one of the following: an identifier of the terminal; an identifier of a first connection between the second access network device and the core network device, the first connection being associated with the terminal; wherein the second access network device is an anchor device of the first access network device.
[0085] Eighthly, embodiments of this disclosure provide a communication device, comprising: one or more processors, and one or more memories for storing a computer program; wherein the processor executes the computer program to implement the communication method of any one of the first to third aspects.
[0086] In a ninth aspect, embodiments of this disclosure provide a communication system including a first access network device, a terminal, and a core network device, wherein the terminal is configured to send an RRC connection recovery request message to the first access network device; the first access network device is configured to send a first message to the core network device based on the RRC connection recovery request message, the first message being used to trigger the core network device to determine first key information, the first key information being used for key updates between the terminal and the first access network device, and the updated key being used for security protection and / or integrity protection between the terminal and the first access network device.
[0087] In conjunction with some embodiments of the ninth aspect, in some embodiments, the core network device is used to send a second message to the first access network device based on the first message, the second message carrying first key information; the first access network device is also used to send the first key information to the terminal, the first key information being used by the terminal to update the key.
[0088] In conjunction with some embodiments of the ninth aspect, in some embodiments, the first key information is carried in the downlink signaling associated with the TB where the RRC connection recovery message sent by the first access network device is located, and the downlink signaling includes one of the following: DCI, used for scheduling the TB; MAC CE; RRC signaling.
[0089] In conjunction with some embodiments of the ninth aspect, in some embodiments, the downlink signaling is MAC CE or RRC signaling, the downlink signaling is unencrypted, and / or, the downlink signaling is protected for integrity using an updated key.
[0090] In some embodiments of the ninth aspect, the first access network device updates the key based on the first key information; the terminal updates the key based on the first key information.
[0091] In some embodiments of the ninth aspect, the updated key is also used to provide security and / or integrity protection for a third message between the terminal and the first access network device; wherein the third message includes at least one of the following: an RRC connection recovery message sent to the terminal; uplink information; downlink information.
[0092] In some embodiments of the ninth aspect, the third message does not include an RRC connection recovery message, which provides security and / or integrity protection based on the key used by the terminal before entering the RRC disconnected state.
[0093] In some embodiments of the ninth aspect, the terminal locally stores second key information, the second key information is in an available state, and the key used by the terminal before entering the RRC disconnected state is determined based on the second key information; or, the second key information is in an unavailable state, and the key used by the terminal before entering the RRC disconnected state is the key stored locally by the terminal.
[0094] In some embodiments of the ninth aspect, the communication system further includes a second access network device, wherein the first message carries at least one of the following: an identifier of a terminal; an identifier of a first connection between the second access network device and a core network device, the first connection being associated with the terminal; wherein the second access network device is an anchor device of the first access network device.
[0095] In a tenth aspect, embodiments of this disclosure provide a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the communication method of any one of the first to third aspects described above.
[0096] In one aspect, embodiments of this disclosure provide a computer program product, including a computer program that, when executed by a processor, implements the communication method of any one of the first to third aspects described above.
[0097] In a twelfth aspect, embodiments of this disclosure provide a computer program including code that, when executed by a processor, implements the communication method of any one of the first to third aspects described above.
[0098] It is understood that the aforementioned communication equipment, communication system, storage medium, program product, etc., are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.
[0099] This disclosure provides a communication method, communication device, communication system, storage medium, and program product. In some embodiments, terms such as communication method, information processing method, and paging method can be used interchangeably; terms such as terminal, communication device, information processing device, information transmission device, network device, network function, and network entity can be used interchangeably; and terms such as communication system, information processing system, and information transmission system can be used interchangeably.
[0100] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments. In all embodiments of this disclosure, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.
[0101] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.
[0102] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.
[0103] In the embodiments of this disclosure, "multiple" refers to two or more.
[0104] In some embodiments, the terms “at least one of A or B, at least one of A and B”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.
[0105] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.
[0106] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, and C.
[0107] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.
[0108] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.
[0109] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain.
[0110] In some embodiments, the terms “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “if…”, “if…”, etc., can be used interchangeably.
[0111] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.
[0112] In some embodiments, devices, etc., can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as “device”, “equipment”, “circuit”, “network element”, “node”, “function”, “unit”, “section”, “system”, “network”, “chip”, “chip system”, “entity”, and “subject” can be used interchangeably.
[0113] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).
[0114] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.
[0115] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "subscriber station", "mobile unit", "subscriber unit", "wireless unit", "remote unit", "mobile device", "wireless device", "wireless communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", and "client" can be used interchangeably.
[0116] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced by communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.
[0117] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.
[0118] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.
[0119] In some embodiments, data, information, etc., may be obtained with the user's consent.
[0120] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.
[0121] Figure 1A is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure. As shown in Figure 1A, the communication system 100 includes at least one of a terminal 101, an access network device 102, and a core network device 103.
[0122] In some embodiments, terminal 101 includes, but is not limited to, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home.
[0123] In some embodiments, the access network device 102, such as a node or device for connecting a terminal to a wireless network, may include at least one of, but is not limited to, an evolved node B (eNB), a next-generation eNB (ng-eNB), a next-generation node B (gNB), a node B (NB), a home node B (HNB), a home evolved node B (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open RAN, a cloud RAN, a base station in other communication systems, and an access node in a Wi-Fi system.
[0124] In some embodiments, the technical solutions of this disclosure can be applied to Open Radio Access Network (Open RAN) architectures. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.
[0125] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.
[0126] In some embodiments, the core network device 103 may be a single device comprising one or more network elements, or it may be multiple devices or a group of devices, each comprising all or part of one or more network elements. Network elements may be virtual or physical. The core network may include, for example, at least one of an evolved packet core (EPC) network, a 5G core (5GC) network, and a next-generation core (NGC) network.
[0127] In some embodiments, the communication system 100 may include a terminal, a first access network device, a second access network device, and a core network device.
[0128] In one embodiment, the terminal accesses the network through a first access network device. In one example, the first access network device is a base station.
[0129] In one embodiment, the second access network device is an anchor device of the first access network device. The second access network device stores the terminal's context information. In one embodiment, the second access network device can be an anchor base station.
[0130] In some embodiments, the core network equipment may be an access and mobility management function (AMF).
[0131] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.
[0132] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1A, or some of the main components in the communication system 100, but are not limited thereto. The main components shown in FIG1A are illustrative. The communication system 100 may include all or some of the main components in FIG1A, or may include other main components other than those in FIG1A. The number and form of each main component are arbitrary. Each main component may be physical or virtual. The connection relationship between the main components is illustrative. The main components may not be connected or may be connected. The connection may be in any way, such as direct connection or indirect connection, wired connection or wireless connection.
[0133] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), Super 3G, International Mobile Telecommunications-Advanced (IMT-Advanced), 4th Generation Mobile Communication System (4G), 5th Generation Mobile Communication System (5G), 5G New Radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future Generation Radio Access (FX), Global System for Mobile Communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, ultra-wideband (UWB), Bluetooth (a registered trademark), public land mobile network (PLMN) networks, device-to-device (D2D) systems, machine-to-machine (M2M) systems, internet of things (IoT) systems, vehicle-to-everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).
[0134] In some embodiments, in a 5G network environment, to reduce air interface signaling and quickly restore data services for wireless connections, a new RRC connection state, namely the RRC inactive state (RRC_INACTIVE), is introduced. This state is different from the RRC idle state (RRC_IDLE) and the RRC connected state (RRC_CONNECTED).
[0135] In some embodiments, RRC_IDLE is an access layer state in which a terminal (such as a UE) is camped on a cell but has not established any RRC connection. The UE will enter the RRC_IDLE state when it is disconnected from the network or is in an unregistered state.
[0136] In some embodiments, RRC_CONNECTED indicates that an RRC connection has been established between the UE and the network. The UE enters the RRC_CONNECTED state when it needs to transmit data or is in an active state.
[0137] In some embodiments, RRC_INACTIVE indicates that the UE is connected to the network, but the UE is in an inactive state. When the UE is inactive for a certain period of time, the connection will change from the RRC_CONNECTED state to the RRC_INACTIVE state to save terminal power consumption and reduce signaling load.
[0138] In some embodiments, the characteristics of the RRC_INACTIVE state include: (1) the connection between the RAN and CN is maintained; (2) the UE (e.g., a terminal or IoT device) and at least one gNB retain the access layer context; (3) the UE is reachable from the RAN side, and the relevant parameters are configured by the RAN; (4) when the UE moves within the RAN-based notification area (RNA), it does not need to notify the network side, but when it moves out of the RNA, it needs to notify the network side; (5) the UE moves within the RNA according to the cell selection reselection method; and (6) there are Xn links between gNBs within the RNA.
[0139] In some embodiments, the RAN configures configuration parameters for the RRC state, which may include configuration parameters regarding RRC state transitions, such as configuration information required to transition the UE from the RRC_CONNECTED state to the RRC_INACTIVE state. These configuration parameters allow the UE to enter a low-power RRC_INACTIVE state when data transmission is not required, while maintaining connectivity with the core network, so that the RRC connection can be quickly restored when needed.
[0140] In some embodiments, the configuration parameters of RRC_INACTIVE can be configured through the RRC_Release message and may include one or more of the following: SuspendConfig, device identifier (such as I-RNTI), RNA, RAN discontinuous reception (DRX) period, RAN-based notification area update (RNAU) periodicity configuration, and Next-Hop chaining counter (NCC).
[0141] In some embodiments, SuspendConfig represents the configuration information for the RRC_INACTIVE state, including the context information and timer settings that the UE needs to retain in the RRC_INACTIVE state.
[0142] In some embodiments, the I-RNTI is a unique identifier for the device (anchor base station) storing the UE's context information. The I-RNTI may include: I-RNTI (40 bits) and short I-RNTI (24 bits).
[0143] In some embodiments, RNA may include: a list of cells, a list of RAN Area IDs, and a list of TAIs.
[0144] It should be noted that the RAN area code is broadcast in the cell's system broadcast. The RAN area is larger than the cell, but smaller than the Tracking Area (TA). For example, the RAN area code is 8 bits, indicating that there are a maximum of 255 RAN areas within a TA.
[0145] It's important to note that the TAI list contains information on all TAIs within the network, which is crucial for location and mobility management. When a UE moves between different TAIs, a Tracking Area Update (TAU) procedure needs to be performed to notify the network of its current location. Maintaining the TAI list helps ensure that the network can accurately track the UE's location and provide necessary services.
[0146] In some embodiments, the RAN DRX period is used to calculate the paging frame (PF) or paging opportunity (PO) of the initial paging message in the RAN. The DRX period is selected for PF or PO calculation based on the minimum value among the cell default DRX period, UE specific DRX period, and RAN DRX period.
[0147] In some embodiments, the periodic configuration of RNAU can be used to control periodic RNAU.
[0148] In some embodiments, NCC is used as the key for message 4 (e.g., MSG4) during the RRC connection resume process. During the RRC resume process, the key for MSG4 can be encrypted or verified using the NCC algorithm. By calculating the normalized cross-correlation coefficient of the two sequences, NCC can assess their similarity, thereby ensuring the integrity and security of MSG4.
[0149] In some embodiments, the UE transitions from the RRC_INACTIVE state to the RRC_CONNECTED state using the RRC connection recovery process in NR, as follows:
[0150] (1) Triggering reason
[0151] In some embodiments, for a UE in the RRC_INACTIVE state, this process is triggered when uplink data arrives, the periodic RNAU timer times out, or an initial RAN paging is received.
[0152] (2) RRC connection restored to RRC_CONNECTED
[0153] Figure 1B is an interactive schematic diagram of an exemplary communication method provided according to an embodiment of the present disclosure. As shown in Figure 1B, the RRC connection recovery process includes:
[0154] In step S101, the UE is in an RRC inactive state, and it is determined that the RRC connection needs to be restored.
[0155] In some embodiments, the UE is in an RRC inactive state and can camp on a cell provided by the serving base station. In one embodiment, the serving base station can be understood as the base station that provides the UE with the cell to camp on.
[0156] In step S102, the UE sends message 1 (MSG1) to the serving base station. In some embodiments, message 1 includes a random access preamble. In one example, the UE can obtain physical random access channel (PRACH) configuration information from system messages (e.g., SIB1) and send the random access preamble through the PRACH channel. In one example, the configuration information includes the length of the preamble sequence, time-domain resources, and other information.
[0157] In some embodiments, the UE may select a preamble sequence and transmit the preamble sequence to the serving base station on the PRACH channel.
[0158] It should be noted that the term "message" in the embodiments of this disclosure can be replaced by terms such as "information," "signaling," "signaling," and "command." Of course, it can also refer to other transmission forms sent by network devices to terminals to perform certain operations on terminal devices. The embodiments of this disclosure do not specifically limit this.
[0159] In step S103, the serving base station sends message 2 (MSG2) to the UE according to message 1.
[0160] In some embodiments, message 2 may be a random access response (RAR) message.
[0161] In some embodiments, after detecting a preamble sequence, the serving base station sends a RAR response message as message 1 to the UE. In one embodiment, the RAR message may include timing adjustment information, uplink resource allocation information, and other information.
[0162] In step S104, the UE sends message 3 (MSG3) to the serving base station.
[0163] In some embodiments, message 3 may be an RRC Connection Resume Request (RRC Connection Resume Request) message.
[0164] In some embodiments, the UE transmits the following message via the uplink common control channel (UL_CCCH) on signaling radio bearers (SRB) 0: the UE's initial access stratum (AS) identification information, short message authentication code-integrity (ShortMAC-I), and the reason for recovery. This message corresponds to MSG3 in the random access procedure. After sending this message, the UE activates security, generates a key, and resumes SRB1 waiting to receive message 4 (MSG4).
[0165] In step S105, the serving base station obtains the UE context message stored on the anchor base station.
[0166] In some embodiments, the anchor base station stores the UE's context information.
[0167] In some embodiments, when the UE is in the RRC_INACTIVE state, the context information stored by the UE and the anchor base station includes: security context information, AS context information, and partial non-access stratum (NAS) context information. The security context information is used to protect the security of communication between the UE and network devices. The AS context information is used to manage the configuration and state of the radio access stratum. The NAS context information is used to manage communication between the UE and the core network.
[0168] In one embodiment, security context information may include key information, integrity protection, and encryption algorithms.
[0169] In one example, key information may include KgNB, KAMF, NCC, and next-hop key (NH). KgNB is the security key between the serving base station and the UE, used for encryption and integrity protection. KgNB is the security key between the AMF and the UE, used to protect control plane signaling. NCC is used to prevent replay attacks and ensure the order of key updates. NH is used to protect communication between the serving base station and the AMF.
[0170] In one example, integrity protection and encryption algorithms may include an integrity protection algorithm and an encryption algorithm. The integrity protection algorithm is used to verify the integrity and legitimacy of the signaling message's origin. The encryption algorithm is used to protect the confidentiality of user data and signaling messages.
[0171] In one embodiment, AS context information may include radio bearer configuration, radio resource management information, radio protocol status, cell-related information, etc. In one example, the radio bearer may include a data radio bearer (DRB) and an SRB.
[0172] In some embodiments, the serving base station may send a context request message to the anchor base station to obtain the UE's context information. Upon receiving the context request message, the anchor base station sends the UE's context information to the serving base station.
[0173] In step S106, the serving base station sends message 4 (MSG4) to the UE.
[0174] In some embodiments, message 4 may be an RRC Connection Resume or RRC Resume message.
[0175] In some embodiments, the serving base station transmits this message on SRB1 via the downlink dedicated control channel (DL_DCCH), which corresponds to MSG4 of the random access procedure. MSG4 provides security and integrity protection.
[0176] In step S107, the UE enters the RRC connection state.
[0177] In step S108, the UE sends message 5 (MSG5) to the serving base station.
[0178] In some embodiments, message 5 may be an RRC Connection Resume Complete (RRC Connection Resume Complete) message.
[0179] In some embodiments, the UE transmits the data on SRB1 via the uplink dedicated control channel (UL_DCCH) without carrying any actual information, serving as an RRC layer confirmation function.
[0180] At this point, the UE transitions from the RRC inactive state to the RRC connected state.
[0181] In one example, Figure 1C is an interactive schematic diagram of an exemplary communication method provided according to an embodiment of the present disclosure. As shown in Figure 1C, the RRC connection recovery process includes:
[0182] In step S111, the UE sends an RRC connection restoration request message to the network (such as the serving base station).
[0183] In step S112, the network sends an RRC connection restoration message to the UE.
[0184] In step S113, the UE sends an RRC connection restoration complete message to the network.
[0185] (3) RRC connection restored to RRC_INACTIVE
[0186] In some embodiments, if the serving base station decides to release the UE to the RRC_INACTIVE state (e.g., periodic RNAU) after receiving the RRC connection restoration request message, the serving base station carries an RRC release message in message 4, which is used to update the INACTIVE configuration parameters.
[0187] In one example, as shown in Figure 1D, the RRC connection recovery process includes:
[0188] In step S121, the UE sends an RRC connection restoration request message to the network (such as the serving base station);
[0189] In step S122, the network sends an RRC release message to the UE, which carries the suspend configuration (RRCRelease with suspend configuration).
[0190] (4) RRC connection restored to RRC_IDLE
[0191] In some embodiments, if the serving base station decides to release the UE to the RRC_IDLE state after receiving the RRC connection restoration request message, the serving base station carries the RRCRelease message in message 4.
[0192] In one example, Figure 1E is an interactive schematic diagram of an exemplary communication method provided according to an embodiment of the present disclosure. As shown in Figure 1E, the RRC connection recovery process includes:
[0193] In step S131, the UE sends an RRC connection restoration request message to the network (such as the serving base station);
[0194] In step S132, the network sends an RRC release message to the UE.
[0195] (5) RRC connection recovery failed
[0196] In some embodiments, if at least one of the following occurs: the first timer (e.g., T319) for the RRC connection recovery request times out, the integrity protection verification of the RRC connection recovery message (MSG4) fails, or cell reselection occurs during the operation of the second timer (e.g., T310), then the RRC connection reconstruction fails for the above reasons, and the UE returns to the RRC_IDLE state.
[0197] In some embodiments, if there is no UE context information in the network (such as the serving base station), an RRC connection re-establishment (or RRC connection establishment) message is sent on SRB0 via the downlink common control channel (DL_CCCH). Upon receiving this message, the UE deletes the previous context and performs the RRC connection re-establishment process.
[0198] In one example, Figure 1F is an interactive schematic diagram of an exemplary communication method provided according to an embodiment of the present disclosure. As shown in Figure 1F, the RRC connection recovery process includes:
[0199] In step S141, the UE sends an RRC connection restoration request to the network (such as the serving base station);
[0200] In step S142, if there is no UE context information in the network, an RRC connection establishment (RRC Setup) message is sent on SRB0 via DL_CCCH;
[0201] In step S143, the UE establishes an RRC connection and sends an RRC Setup Complete message to the network.
[0202] In some embodiments, the UE receives an RRC connection rejection (RRCReject) message, for example, due to network load control reasons. At this point, the UE returns to the initial RRC_INACTIVE state.
[0203] In one example, Figure 1G is an interactive schematic diagram of an exemplary communication method provided according to an embodiment of the present disclosure. As shown in Figure 1G, the RRC connection recovery process includes:
[0204] In step S151, the UE sends an RRC connection restoration request message to the network (such as the serving base station);
[0205] In step S152, the network sends an RRCReject message to the UE for reasons such as load control.
[0206] At this point, the UE returns to its initial RRC_INACTIVE state.
[0207] It should be noted that both the RRC connection establishment and recovery processes require context information existing on the network side to restore the RRC connection and services. The RRC connection establishment process focuses on restoring the RRC connection, requiring an RRC connection reconfiguration message to configure the bearer. The RRC connection recovery process focuses on restoring the RRC connection and service bearer, therefore it has shorter latency. Furthermore, the RRC connection recovery process offers better security.
[0208] In some embodiments, if the serving base station determines, after receiving the UE's context information, that it does not support the security algorithm used by the UE before entering the RRC inactive state, the serving base station instructs the UE to fall back to the RRC connection establishment procedure.
[0209] In some embodiments, after receiving the UE's context information from the anchor base station, the serving base station can encrypt and protect the integrity of the RRC connection recovery message based on the key information in the context information. However, since this key information is provided by the anchor base station, it may not meet security requirements. To address this issue, the serving base station can perform an intra-cell handover after path switching to isolate the key, so that the anchor base station is no longer aware of the key information used by the serving base station. However, this key update will cause the UE's L2 protocol entity to reset, interrupting service data transmission and thus affecting the UE's service performance.
[0210] To address the aforementioned issues, embodiments of this disclosure provide a communication method, communication device, communication system, storage medium, and program product that can complete key update and key isolation operations in one step during RRC connection recovery, avoiding interruption of subsequent service data transmission and thereby improving the robustness of terminal mobility.
[0211] Figure 2 is an exemplary interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 2, the embodiment of the present disclosure relates to a communication method executed by the aforementioned communication system 100. In one example, the aforementioned communication method includes steps S201 to S207.
[0212] In step S201, the terminal sends an RRC connection recovery request message to the first access network device.
[0213] In some embodiments, the terminal sends an RRC connection restoration request message. In some embodiments, the RRC connection restoration request message can be sent by the terminal, but is not limited to this; it can also be sent by other entities.
[0214] In some embodiments, the first access network device receives an RRC connection restoration request message. In some embodiments, the RRC connection restoration request message may be received by the first access network device, but is not limited to this; it may also be received by other entities.
[0215] In some embodiments, when a terminal is in an RRC inactive state, it can select a cell to camp on in order to restore the RRC connection on that cell. In one embodiment, when a terminal in an RRC inactive state has uplink data to send, it selects a cell to camp on. In one embodiment, when a terminal in an RRC inactive state receives a paging message from the network side and determines to respond to the paging message, it selects a cell to camp on. In one embodiment, when a terminal in an RRC inactive state experiences a tracking area update, it selects a cell to camp on. Of course, the terminal can also select a cell to camp on in other situations, and this disclosure does not specifically limit this.
[0216] In some embodiments, the terminal may select a cell to camp on. In one embodiment, the cell may be a cell that the terminal accessed before entering the RRC inactive state, a new cell that the terminal reselected, or the cell that the terminal is currently in. Of course, the cell may also be other types, and this disclosure does not specifically limit this.
[0217] In some embodiments, the aforementioned cell is provided by a first access network device.
[0218] In some embodiments, after the terminal camps on a cell, it can send an RRC connection restoration request message on that cell.
[0219] In some embodiments, the RRC connection recovery request message can be an RRC Connection Resume Request message or an RRC Resume Request message.
[0220] In some embodiments, the RRC connection recovery request message may carry first information, which is used to indicate the anchor device (such as a second access network device) storing the context information of the terminal.
[0221] In some embodiments, the first information may be the device identifier of the storage terminal's context information, such as I-RNTI.
[0222] In some embodiments, the RRC connection restoration request message may carry a ShortMAC-I. The ShortMAC-I is used to verify the integrity and legitimacy of the origin of radio interface uplink messages (e.g., MSG3).
[0223] In one embodiment, when the terminal is in an RRC inactive state, it locally stores its context information. The terminal then calculates the ShortMAC-I based on this context information and can subsequently include the ShortMAC-I in the RRC connection recovery request message.
[0224] In some embodiments, the context information of the terminal may include security context information, AS context information, partial NAS context information, and other information.
[0225] In one embodiment, security context information may include key information, integrity protection, and encryption algorithms.
[0226] In one embodiment, the key information is used for security and / or integrity protection between the terminal and the first access network device. In one example, the key information may be second key information.
[0227] In one embodiment, the key information may include KgNB, KAMF, NCC, NH, etc. KgNB is a security key between the base station (such as the first access network device) and the terminal, used for encryption and integrity protection. KgNB is a security key between the AMF and the terminal, used to protect control plane signaling. NCC is used to prevent replay attacks and ensure the sequential nature of key updates. NH is used to protect communication between the serving base station and the AMF.
[0228] In one embodiment, the key information may further include at least one of the following derived from the base key KgNB: KRRCint, KRRCenc, KUPenc, and KUPint. KRRCint is used to calculate and verify the integrity protection code (such as MAC-I) of the RRC signaling. KRRCenc is used for encryption of the RRC signaling. KUPenc is used for encryption of user plane data. KUPint is used for integrity protection of user plane data.
[0229] In one embodiment, the integrity protection and encryption algorithm may include an integrity protection algorithm and an encryption algorithm. The integrity protection algorithm is used to verify the integrity and legitimacy of the signaling message's origin. The encryption algorithm is used to protect the confidentiality of user data and signaling messages.
[0230] In one embodiment, the AS context information includes radio bearer configuration, radio resource management information, radio protocol status, cell-related information, etc. In one example, the radio bearer may include DRB and SRB.
[0231] In one embodiment, the NAS context information includes information such as the terminal's identifier and some mobility information.
[0232] In some embodiments, the terminal can use key information (such as KgNB or KRRCint) included in locally stored context information to calculate ShortMAC-I. In one example, this key information is old key information (such as old KgNB or old KRRCint).
[0233] In some embodiments, the RRC connection recovery request message may include first information and ShortMAC-I.
[0234] In step S202, the first access network device sends a context request message to the second access network device.
[0235] In some embodiments, the first access network device sends a context request message. In some embodiments, the context request message may be sent by the first access network device, but is not limited to this, and may also be sent by other entities.
[0236] In some embodiments, the second access network device receives a context request message. In some embodiments, the context request message may be received by the second access network device, but is not limited thereto, and may also be received by other entities.
[0237] In some embodiments, after receiving an RRC connection recovery request message, the first access network device determines, based on first information, the device storing the terminal's context information (e.g., the second access network device). At this time, the first access network device triggers a context request procedure to obtain the terminal's context information stored in the second access network device.
[0238] In some embodiments, the first access network device may send a context request message to the second access network device, the context request message being used to request context information of the terminal.
[0239] In some embodiments, the context request message may carry the identifier of the terminal (e.g., a first identifier).
[0240] In step S203, the second access network device sends a context response message to the first access network device.
[0241] In some embodiments, the second access network device sends a context response message. In some embodiments, the context response message may be sent by the second access network device, but is not limited to this, and may also be sent by other entities.
[0242] In some embodiments, the first access network device receives a context response message. In some embodiments, the context response message may be received by the first access network device, but is not limited thereto, and may also be received by other entities.
[0243] In some embodiments, after receiving a context request message, the second access network device can determine which terminal's context information the first access network device is requesting based on the first identifier, and then send the context information of the terminal associated with the first identifier to the first access network device.
[0244] In some embodiments, the context information of the terminal may include security context information, AS context information, partial NAS context information, and other information.
[0245] In one embodiment, the security context information may include key information, integrity protection, and encryption algorithms. In one example, the key information may be second key information.
[0246] In one embodiment, the key information may include KgNB, KAMF, NCC, NH, etc. KgNB is a security key between the access network device and the terminal, used for encryption and integrity protection. KgNB is a security key between the AMF and the terminal, used to protect control plane signaling. NCC is used to prevent replay attacks and ensure the sequential nature of key updates. NH is used to protect communication between the serving base station and the AMF.
[0247] In one embodiment, the key information may further include at least one of the following derived from the base key KgNB: KRRCint, KRRCenc, KUPenc, and KUPint. KRRCint is used to calculate and verify the integrity protection code (such as MAC-I) of the RRC signaling. KRRCenc is used for encryption of the RRC signaling. KUPenc is used for encryption of user plane data. KUPint is used for integrity protection of user plane data.
[0248] In one embodiment, the integrity protection and encryption algorithm may include an integrity protection algorithm and an encryption algorithm. The integrity protection algorithm is used to verify the integrity and legitimacy of the signaling message's origin. The encryption algorithm is used to protect the confidentiality of user data and signaling messages.
[0249] In one embodiment, the AS context information includes radio bearer configuration, radio resource management information, radio protocol status, cell-related information, etc. In one example, the radio bearer may include DRB and SRB.
[0250] In one embodiment, the NAS context information includes information such as the terminal's identifier and some mobility information.
[0251] In some embodiments, the context information of the terminal stored locally by the second access network device is the same as the context information of the terminal stored locally by the terminal.
[0252] In some embodiments, after obtaining the terminal's context information, the first access network device can recalculate the ShortMAC-I using the key information (such as KgNB or KRRCint) included in the context information. Furthermore, the calculated ShortMAC-I is matched with the ShortMAC-I carried in the received RRC connection restoration request message to verify the integrity of the RRC connection restoration request message and the legitimacy of the terminal.
[0253] In one embodiment, if the calculated ShortMAC-I matches the ShortMAC-I carried in the received RRC connection restoration request message, the first access network device can determine that the RRC connection restoration request message is complete and the terminal is legitimate. In this case, the first access network device can continue with subsequent operations. Otherwise, the first access network device can determine that the RRC connection restoration request message may have been tampered with or that the terminal is illegitimate. In this case, the first access network device will refuse to perform subsequent operations and may take further security measures, such as recording a security time or notifying the network management system.
[0254] In some embodiments, the context response message may also carry at least one of the following: the identifier of the terminal (such as a first identifier), the device identifier of the core network device serving the terminal (such as a second identifier), and the identifier of the first connection between the second access network device and the core network device (such as a third identifier).
[0255] In some embodiments, the terminal identifier is used by the first access network device to determine which terminal's key is being requested.
[0256] In some embodiments, the identifier of the core network device is used by the first access network device to determine which device to request the key from.
[0257] In some embodiments, the first connection is associated with a terminal. In one embodiment, the identifier of the first connection may be a next-generation application protocol identifier (NG AP ID).
[0258] In one example, the NG AP ID may include the RAN UE NGAP ID and the Source AMF UE NGAP ID. The RAN UE NGAP ID is assigned by the first access network device and is used to uniquely identify a terminal within the first access network device. When the first access network device needs to communicate with the core network device, it can send the RAN UE NGAP ID to the core network device so that the core network device can associate messages sent by the first access network device with a specific terminal. The Source AMF UE NGAP ID is assigned by the core network device and is used to uniquely identify a terminal within the core network device. When the core network device needs to communicate with the first access network device, it can send the Source AMF UE NGAP ID to the first access network device so that the first access network device can associate messages sent by the core network device with a specific terminal.
[0259] In step S204, the first access network device sends a first message to the core network device.
[0260] In some embodiments, the first access network device sends a first message. In some embodiments, the first message may be sent by the first access network device, but is not limited to this, and may also be sent by other entities.
[0261] In some embodiments, the core network device receives a first message. In some embodiments, the first message may be received by the core network device, but is not limited thereto, and may also be received by other entities.
[0262] In some embodiments, after receiving a context response message, the first access network device determines that the key needs to be updated. In this case, the first access network device may send a first message to the core network device based on the identifier of the core network device carried in the context response message.
[0263] In some embodiments, the first message is used to trigger the core network device to determine the first key information, the first key information is used for the terminal and the first access network device to update the key, and the updated key is used for security protection and / or integrity protection between the terminal and the first access network device.
[0264] In some embodiments, the first message is used to trigger the core network device to configure key information for the terminal and the first access network device, and the key information configured by the core network device is used by the terminal and the first access network device to update the key.
[0265] In one example, the first message could be a key request message. In another example, the first message could be a path switch request message.
[0266] In some embodiments, the first message may include at least one of the following: the identifier of the terminal, the identifier of the first connection, second key information, and the identifier of the first access network device.
[0267] In some embodiments, the terminal identifier is used by the core network device to determine which terminal to configure the key for.
[0268] In some embodiments, the first connection is associated with a terminal. In one embodiment, the identifier of the first connection may be an NG AP ID.
[0269] In one example, the NG AP ID may include the RAN UE NGAP ID and the Source AMF UE NGAP ID. The RAN UE NGAP ID is assigned by the first access network device and is used to uniquely identify a terminal within the first access network device. When the first access network device needs to communicate with the core network device, it can send the RAN UE NGAP ID to the core network device so that the core network device can associate messages sent by the first access network device with a specific terminal. The Source AMF UE NGAP ID is assigned by the core network device and is used to uniquely identify a terminal within the core network device. When the core network device needs to communicate with the first access network device, it can send the Source AMF UE NGAP ID to the first access network device so that the first access network device can associate messages sent by the core network device with a specific terminal.
[0270] In some embodiments, the second key information is used to indicate the key information currently stored by the first access network device and the terminal, so that the core network device can configure first key information that is different from the second key information based on the second key information.
[0271] In some embodiments, the identifier of the first access network device is used by the core network device to determine which access network device to configure the key for.
[0272] In some embodiments, after receiving the first message, the core network device can generate new key information (first key information) based on the current key information and key management policy.
[0273] In one example, the first key information configured in the core network can be {NCC, NH}. Here, NCC identifies the version of the NH value. NH is an intermediate key used to derive a new key from the old key.
[0274] In some embodiments, the core network device successfully configures the first key information, that is, the key update is successful.
[0275] In some embodiments, the core network device fails to configure the first key information, that is, the key update fails.
[0276] In step S205, the core network device sends a second message to the first access network device.
[0277] In some embodiments, the core network device sends a second message. In some embodiments, the second message may be sent by the core network device, but is not limited thereto, and may also be sent by other entities.
[0278] In some embodiments, the first access network device receives the second message. In some embodiments, the second message may be received by the first access network device, but is not limited thereto, and may also be received by other entities.
[0279] In some embodiments, after receiving the first message, the core network device may send a second message to the terminal as a response to the first message.
[0280] In one example, the second message could be a path switch request acknowledge message.
[0281] In some embodiments, the second message carries first key information.
[0282] In one embodiment, if the core network device determines that the key update was successful, the second message can carry the first key information and send it to the first access network device. Thus, upon receiving the second message, the first access network device can confirm the key update. At this point, the first access network device can obtain the updated key based on the first key information.
[0283] In some embodiments, the second message does not carry the first key information.
[0284] In some embodiments, if the core network device fails to configure the first key information, the second message sent by the core network device to the first access network device does not carry key information. Thus, upon receiving the second message, the first access network device can determine that the key has not been updated, and therefore, the first access network device may choose not to update the key obtained based on the second key information.
[0285] In some embodiments, if the core network device fails to configure the first key information, the core network device may not send the second message to the first access network device. Thus, if the first access network device does not receive the second message within a preset time period after sending the first message, it can determine that the key has not been updated. In this case, the first access network device may not update the key obtained based on the second key information. In this situation, step S205 can be omitted.
[0286] In some embodiments, the first access network device updates the key based on the first key information in the second message.
[0287] In some embodiments, when the second message carries first key information, the first access network device can determine that the key has been updated after receiving the second message. Then, the first access network device updates the key based on the first key information to obtain the updated key.
[0288] In one embodiment, the first access network device can derive a new key (such as KRRCint, KRRCenc) based on the NCC and NH in the first key information and the current key (such as KgNB), thus obtaining the updated key.
[0289] In some embodiments, the first access network device may store the updated key in a local security context for subsequent communication with the terminal.
[0290] In some embodiments, when the second access network device receives a second message carrying first key information, it may send the first key information to the terminal for the terminal to update the key.
[0291] In step S206, the first access network device sends an RRC connection recovery message to the terminal.
[0292] In some embodiments, the first access network device sends an RRC connection restoration message. In some embodiments, the RRC connection restoration message may be sent by the first access network device, but is not limited to this; it may also be sent by other entities.
[0293] In some embodiments, the terminal receives an RRC connection restoration message. In some embodiments, the RRC connection restoration message may be received by the terminal, but is not limited to this; it may also be received by other entities.
[0294] In one example, the RRC connection recovery message can be either an RRC Connection Resume message or an RRC Resume message.
[0295] In some embodiments, the first access network device sends an RRC connection restoration message to the terminal to restore the RRC connection and establish radio bearers such as SRB1, SRB2, and DRB. SRB1 and SRB2 are used for signaling transmission, while DRB is used for user data transmission, ensuring that the terminal can communicate efficiently with the network.
[0296] In some embodiments, the RRC connection recovery message sent by the first access network device uses a key for security and / or integrity protection.
[0297] In some embodiments, the updated key can be used to protect the security and / or integrity of a third message between the terminal and the first access network device, wherein the third message may include at least one of the following: an RRC connection recovery message, uplink information, and downlink information sent by the first access network device to the terminal.
[0298] In some embodiments, the updated key can be used to provide security and / or integrity protection for uplink and downlink information between the terminal and the first access network device. In other words, the updated key may not be used to provide full and / or integrity protection for RRC connection recovery messages sent by the first access network device to the terminal.
[0299] In some embodiments, the updated key can be used to provide security and / or integrity protection for the RRC connection recovery message sent by the first access network device to the terminal, as well as for the uplink and downlink information between the terminal and the first access network device.
[0300] In some embodiments, when the first access network device receives the first key information, the first access network device can use the updated key to perform security and / or integrity protection on the RRC connection recovery message.
[0301] In one embodiment, the updated key may include a KRRCenc key and a KRRCint key, wherein the KRRCenc key is used for encryption and the KRRCint key is used for integrity protection.
[0302] In one example, the first access network device can use the KRRCenc key and an encryption algorithm (such as AES-128) to encrypt the RRC connection recovery message to protect the security of the RRC connection recovery message.
[0303] In one example, the first access network device can use the KRRCint key and an integrity protection algorithm (such as HMAC-SHA256) to calculate the integrity check value (MAC-I) of the RRC connection recovery message, and then append the calculated MAC-I to the RRC connection recovery message to protect the integrity of the RRC connection recovery message.
[0304] In some embodiments, the third message does not include the RRC connection recovery message, which is used for security and / or integrity protection based on the key used by the terminal before entering the RRC inactive state.
[0305] In some embodiments, when the first access network device receives the first key information, the first access network device may not use the updated key to perform security and / or integrity protection on the RRC connection recovery message. Instead, it may use the key from the second key information obtained from the second access network device to perform security and / or integrity protection on the RRC connection recovery message. In other words, the first access network device uses the key used by the terminal before entering the RRC inactive state to perform security and / or integrity protection on the RRC connection recovery message.
[0306] In some embodiments, if the core network device successfully configures the first key information, the first key information can be sent together with the RRC connection recovery message. In one embodiment, the first key information and the RRC connection recovery message can be sent on the same resource. In one example, the first key information and the RRC connection recovery message can be sent on the same transport block (TB). In one embodiment, the first key information and the RRC connection recovery message can be sent on adjacent resources. In one example, the first key information can be sent on the (i-1)th TB, and the RRC connection recovery message can be sent on the ith TB, where i is a positive integer.
[0307] In some embodiments, the first key information may be carried in the downlink signaling associated with the TB containing the RRC connection recovery message. In one embodiment, the downlink signaling carrying the first key information may include DCI, MAC CE, or RRC signaling for scheduling the TB. In one embodiment, the first key information is included in the scheduling information of the RRC connection recovery message. In one example, the first key information is carried in a DCI used to schedule the TB containing the RRC connection recovery message. In one embodiment, the first key information is included in other messages within the TB containing the RRC connection recovery message. In one example, the first key information is carried in MAC CE or RRC signaling contained in the TB containing the RRC connection recovery message.
[0308] In some embodiments, the first key information is carried in the DCI contained in the TB where the RRC connection recovery message is located, and the DCI is used to schedule the TB where the RRC connection recovery message is located.
[0309] In some embodiments, the first key information is carried in the MAC CE contained in the TB where the RRC connection recovery message is located.
[0310] In some embodiments, the first key information is carried in the RRC signaling contained in the TB where the RRC connection recovery message is located.
[0311] In some embodiments, the first access network device may add a first field to the DCI to instruct the terminal to use the updated key for security and / or integrity protection. In one embodiment, the first field may have a first value, instructing the terminal to use the updated key for security and / or integrity protection of RRC connection recovery messages, uplink information, and downlink information. In one embodiment, the first field may have a second value, instructing the terminal to use the updated key for security and / or integrity protection of uplink and downlink information. In one example, the first field may include one bit. For example, the first value may be 1, and the second value may be 0.
[0312] In some embodiments, the first access network device may include a MAC CE in the TB containing the RRC connection recovery message, through which the MAC CE instructs the terminal to use an updated key for security and / or integrity protection. In one embodiment, the MAC CE may instruct the terminal to use an updated key for security and / or integrity protection of the RRC connection recovery message, uplink information, and downlink information. In another embodiment, the MAC CE may instruct the terminal to use an updated key for security and / or integrity protection of both uplink and downlink information.
[0313] In some embodiments, when the downlink signaling is MAC CE or RRC signaling, the first key information is not encrypted. Thus, when the terminal receives the first key information based on MAC CE or RRC signaling, it can decode the first key information to determine whether to use the updated key for security and / or integrity protection.
[0314] In some embodiments, when the first access network device instructs the terminal to use an updated key to perform security and / or integrity protection on RRC connection recovery messages, uplink information, and downlink information, the terminal, upon receiving the RRC connection recovery message, can obtain the first key information indicated in the downlink signaling and generate an updated key based on the first key information. Then, the terminal can use the updated key to perform integrity protection verification and decryption operations on the RRC connection recovery message. In one embodiment, after generating the updated key, the terminal can use the updated key to perform integrity protection verification on the downlink signaling. If the verification passes, the terminal performs integrity protection verification and decryption operations on the RRC connection recovery message using the updated key. If the verification fails, the terminal enters an RRC idle state and waits to re-access the network.
[0315] In some embodiments, when the first access network device instructs the terminal to use an updated key to perform security and / or integrity protection on uplink and downlink information, the terminal, after receiving the RRC connection recovery message, can use the key used before entering the RRC inactive state to perform integrity protection verification and decryption on the RRC connection recovery message.
[0316] In some embodiments, the second key information stored locally on the terminal is available, and the key used by the terminal before entering the RRC inactive state is determined based on the second key information; or, the second key information is unavailable, and the key used by the terminal before entering the RRC inactive state is the key stored locally on the terminal.
[0317] In some embodiments, the second key information includes {NCC, NH}, where an NCC counter is used to identify the version of the NH value. The NCC increments each time NH is updated. The NCC value ranges from 0 to 255. When the NCC value reaches its maximum value of 255, NH can no longer be updated, and the second key information is in an unavailable state. Conversely, when the NCC value has not reached its maximum value, NH can be updated, and the second key information is in an available state.
[0318] In one embodiment, when the NH cannot be updated, the terminal can determine the key for the RRC connection recovery message using the last updated NH, and then perform integrity protection verification and decryption operations on the RRC connection recovery message. In one example, the terminal can use the last updated key KgNB* to perform integrity protection verification and decryption on the RRC connection recovery message.
[0319] In one embodiment, when the NH can be updated, the terminal can update the NH and determine the key for the RRC connection recovery message using the updated NH, so as to perform integrity protection verification and decryption operations on the RRC connection recovery message. In one embodiment, the terminal can use the key KgNB* (or KRRCint) calculated based on the NH corresponding to the NCC to perform integrity protection verification and decryption on the RRC connection recovery message.
[0320] In some embodiments, when the first access network device instructs the terminal to use an updated key for security and / or integrity protection of uplink and downlink information, the terminal may first use the key used before entering the RRC inactive state to perform integrity protection verification and decryption of the RRC connection recovery message. If the verification is successful, the terminal can obtain the first key information indicated in the downlink signaling sent along with the RRC connection recovery message and generate an updated key based on the first key information. If the verification fails, the terminal enters the RRC idle state and waits to re-access the network. In one embodiment, the terminal can perform integrity protection verification and decryption of downlink signaling using the updated key. If the verification fails, the terminal can enter the RRC idle state and wait to re-access the network.
[0321] In some embodiments, if the core network device fails to configure the first key information, the terminal may also use the key used before entering the RRC inactive state to perform integrity protection verification and decryption of the RRC connection recovery message after receiving the RRC connection recovery message sent by the first access network device. This will not be elaborated here.
[0322] In some embodiments, the RRC connection restoration message sent by the first access network device to the terminal may include radio bearer configuration. For example, the radio bearer configuration is used to reactivate or configure SRB1, SRB2, and DRB.
[0323] In some embodiments, after receiving the RRC connection restoration message, the terminal can decode the message using the indicated key according to the first key information, thereby obtaining the radio bearer configuration. Then, the terminal can activate the radio bearer, restore SRB1, SRB2, and DRB, and complete the RRC restoration process.
[0324] In step S207, the terminal sends an RRC connection restoration complete message to the first access network device.
[0325] In some embodiments, the terminal sends an RRC connection restoration complete message. In some embodiments, the RRC connection restoration complete message can be sent by the terminal, but is not limited to this; it can also be sent by other entities.
[0326] In some embodiments, the first access network device receives an RRC connection restoration complete message. In some embodiments, the RRC connection restoration complete message may be received by the first access network device, but is not limited to this; it may also be received by other entities.
[0327] In one example, the RRC connection establishment complete message can be either an RRC Connection Resume Complete message or an RRC Resume Complete message.
[0328] In some embodiments, after completing the RRC connection recovery process, the terminal enters the RRC connection state to prepare for data transmission.
[0329] In some embodiments, after completing the RRC connection restoration, the terminal sends an RRC connection restoration completion message to the first access network device. In one embodiment, the terminal can use an updated key to protect the security and / or integrity of the RRC connection restoration completion message.
[0330] This completes the process of restoring the RRC connection between the terminal and the first access network device.
[0331] In this embodiment, during the RRC connection recovery process, the first access network device sends a first message to the core network device to trigger the core network device to determine the first key information used for key updates between the terminal and the first access network device. That is, key updates are performed during the RRC connection recovery process. Furthermore, the second access network device does not participate in transmitting the first key information; therefore, the second access network device is no longer aware of the keys used by the first access network device and the terminal, meaning key isolation is completed during the RRC connection recovery process. This avoids key isolation during subsequent intra-site handover, key updates during subsequent data transmission, and interruption of service data transmission, which could affect the terminal's service performance and thus improve the robustness of terminal mobility.
[0332] The communication method involved in the embodiments of this disclosure may include at least one of steps S201 to S207. For example, a combination of steps S201 and steps S204 to S207 can be implemented as an independent embodiment. A combination of steps S201 to S204, steps S206, and steps S207 can be implemented as an independent embodiment. A combination of steps S201 to S207 can be implemented as an independent embodiment. It should be noted that the possible independent embodiments consisting of one or more steps S201 to S207 are not limited thereto.
[0333] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.
[0334] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.
[0335] In some embodiments, the terms “carrying,” “indicating,” “carrying,” “including,” “containing,” and “encapsulating” may be used interchangeably.
[0336] In some embodiments, the terms “radio”, “wireless”, “radioaccessnetwork (RAN)”, “accessnetwork (AN)”, and “RAN-based” can be used interchangeably.
[0337] In some embodiments, "acquire," "get," "obtain," "receive," "transmit," "bidirectional transmission," and "send and / or receive" can be used interchangeably and can be interpreted as receiving from other entities, acquiring from protocols, acquiring from higher layers, obtaining through self-processing, or autonomous implementation. Protocols include, for example, at least one of the 3GPP protocol, Wi-Fi protocol, and audio and / or video protocols.
[0338] In some embodiments, terms such as “send,” “transmit,” “report,” “transmit,” “request,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.
[0339] In some embodiments, the terms “issue,” “return,” “feedback,” “response,” and “acknowledgement” can be used interchangeably.
[0340] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.
[0341] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values (e.g., a comparison with a predetermined value), but is not limited thereto.
[0342] Figure 3 is an exemplary interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 3, the communication method includes steps S301 to S302.
[0343] In step S301, the terminal sends an RRC connection recovery request message to the first access network device.
[0344] The optional implementation of step S301 can be found in the optional implementation of step S201 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0345] In step S302, the first access network device sends a first message to the core network device.
[0346] In some embodiments, the first access network device sends a first message to the core network device based on an RRC connection recovery request message. The first message is used to trigger the core network device to determine first key information. The first key information is used for key updates between the terminal and the first access network device. The updated key is used for security protection and / or integrity protection between the terminal and the first access network device.
[0347] The optional implementation of step S302 can be found in the optional implementation of step S204 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0348] In the following, specific embodiments of the present disclosure will be described by way of example.
[0349] In some embodiments, FIG4 is an exemplary interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG4, the following embodiment process is given:
[0350] 1. UE 51 sends an RRCResumeRequest message to the current serving base station 52, triggering the RRC connection recovery process.
[0351] 2. The current serving base station 52 determines the identification information gNB ID of the base station storing the UE context, i.e. the identifier of the anchor gNB, based on the I-RNTI carried in the RRCResumeRequest message, and initiates the context request process by sending a context request message to the anchor base station 53.
[0352] 3. Anchor base station 53 sends a context response message to the current serving base station 52 based on the context request message. Optionally, the context response message carries the identification information of the AMF, i.e., the identification information of the AMF served by the current UE, or the UE's identifier, or the NG AP ID between the anchor base station and the AMF. That is: RAN UE NGAP ID, Source AMF UE NGAP ID.
[0353] 4. After obtaining the security context, the current serving base station 52 requests key information from the AMF 54. This request can be a path switch procedure. To ensure the AMF 54 knows the target UE 51, the UE ID or the NG AP ID between the anchor base station and the AMF can be included in the key request message sent by the current serving base station 52 to the AMF 54. Specifically: RAN UE NGAP ID, Source AMF UE NGAP ID.
[0354] 5. AMF54 configures {NCC, NH} to the current serving base station 52.
[0355] 6. The current serving base station 52 sends an RRCResume message to UE 51. The RRCResume message corresponds to the DCI of the TB, or the MAC CE within the TB, or the RRC signaling, indicating:
[0356] Option 1: The NCC corresponding to the key used for MSG4 encryption and integrity protection.
[0357] In this TB, UE 51 first obtains the key indicated in the MAC CE or RRC signaling sent together, and generates a new key. Optionally, it uses the key to perform integrity protection verification on the RRC signaling or MAC CE. If successful, it performs integrity protection verification and decryption operations on the RRCREsume message. If unsuccessful, the UE enters the idle state.
[0358] Option 2: The NCC corresponding to the key used for encryption and integrity protection of all DL and UL signaling after MSG4. MSG4 still uses the key generated within the UE for encryption and integrity protection, i.e.:
[0359] In one example, if no NH is available, old KgNB(KRRCint) calculates the shortMAC-I of MSG3, and uses KgNB* to calculate the integrity protection and encryption of the following MSG4, using the previously stored algorithm.
[0360] In one example, if there is an unused NH, then old KgNB(KRRCint) calculates the shortMAC-I of MSG3, and KgNB*(KRRCint) calculated based on the NH corresponding to NCC is used to calculate the integrity protection and encryption of the next MSG4, using the previously stored algorithm.
[0361] In this TB, UE 51 first performs integrity protection verification and decryption on RRCREsume. If successful, it obtains the key indicated in the MAC CE or RRC signaling sent together and generates a new key. Optionally, it uses the key to perform integrity protection verification on the RRC signaling or MAC CE. If the verification fails, the UE enters the idle state.
[0362] The aforementioned RRC signaling or MAC CE carrying the NCC can perform integrity protection based on the key corresponding to the new NCC.
[0363] 7. UE 51 sends RRCResumeComplete to the current serving base station 52, at which point RRC recovery is successful. RRCResumeComplete uses a new key to perform encryption and integrity protection.
[0364] In this embodiment of the disclosure, the key update and key isolation operations are completed in one step during the RRCResume process, avoiding the need for subsequent intra-cell HO to perform key isolation, avoiding key updates during data transmission, L2 protocol entity reset, interruption of service data transmission, impact on UE service performance, and improving the robustness of terminal mobility.
[0365] In some embodiments, the key is directly updated based on the key indicated by RRC signaling or MAC CE in MSG4 by the serving base station, avoiding key updates during data transmission.
[0366] In some embodiments, the network side performs path switching in advance to obtain the key.
[0367] In the embodiments disclosed herein, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations in other embodiments.
[0368] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, an apparatus is proposed that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Furthermore, another apparatus is proposed that includes units or modules for implementing the steps performed by a network device (e.g., a first access network device, a core network device, etc.) in any of the above methods.
[0369] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through a configuration file, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.
[0370] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a CPU, microprocessor, graphics processing unit (GPU) (which can be understood as a microprocessor), or digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented as an ASIC or PLD, such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), tensor processing unit (TPU), deep learning processing unit (DPU), etc.
[0371] Figure 5 is a schematic diagram of a communication device according to an embodiment of the present disclosure. As shown in Figure 5, the communication device 500 may include at least one of a transceiver module 501 and a processing module 502.
[0372] In some embodiments, the communication device 500 may be a first access network device. In some embodiments, the transceiver module 501 is configured to receive an RRC connection restoration request message sent by a terminal; based on the RRC connection restoration request message, it sends a first message to a core network device, the first message being used to trigger the core network device to determine first key information, the first key information being used for key updates between the terminal and the first access network device, and the updated key being used for security and / or integrity protection between the terminal and the first access network device. Optionally, the transceiver module 501 may be used to perform at least one of the communication steps (e.g., steps S201 to S207, but not limited thereto) performed by the first access network device in any of the above methods, which will not be elaborated here. In some embodiments, the processing module 502 may be configured to perform at least one of the other steps performed by the first access network device in any of the above methods, which will not be elaborated here.
[0373] In some embodiments, the communication device 500 may be a core network device. In some embodiments, the transceiver module 501 is configured to receive a first message sent by a first access network device. The first message is used to trigger the core network device to determine first key information. The first key information is used for key updates between the terminal and the first access network device. The updated key is used for security and / or integrity protection between the terminal and the first access network device. The first message is sent by the first access network device upon receiving an RRC connection recovery request message sent by the terminal. Optionally, the transceiver module 501 is used to perform at least one of the communication steps (e.g., steps S204 to S205, but not limited thereto) performed by the core network device in any of the above methods, which will not be elaborated here. In some embodiments, the processing module 502 is configured to perform at least one of the other steps performed by the core network device in any of the above methods besides the communication steps such as sending and / or receiving, which will not be elaborated here.
[0374] In some embodiments, the communication device 500 may be a terminal. In some embodiments, the transceiver module 501 is configured to send an RRC connection recovery request message to a first access network device, which triggers the first access network device to send a first message to a core network device based on the RRC connection recovery request message. The first message triggers the core network device to determine first key information. The first key information is used by the terminal and the first access network device to perform a key update. The updated key is used for security protection and / or integrity protection between the terminal and the first access network device. Optionally, the transceiver module 501 may perform at least one of the communication steps (e.g., steps S201, S206, but not limited thereto) performed by the terminal in any of the above methods, which will not be elaborated here. In some embodiments, the processing module 502 is configured to perform at least one of the other steps performed by the terminal in any of the above methods, which will not be elaborated here.
[0375] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.
[0376] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module.
[0377] In some embodiments, the processing module can be replaced by the processor, and the transceiver module can be replaced by the transceiver.
[0378] Figure 6A is a schematic diagram of the structure of a communication device according to an embodiment of the present disclosure. The communication device 6100 can be a network device (e.g., a first access network device, core network device, etc.), a terminal (e.g., a user equipment), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 6100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.
[0379] As shown in Figure 6A, the communication device 6100 is used to execute any of the above methods. In some embodiments, the communication device 6100 includes one or more processors 6101. The processor 6101 may be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 6100 is used to execute any of the above methods. Optionally, one or more processors 6101 are used to invoke instructions to cause the communication device 6100 to execute any of the above methods.
[0380] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceiver 6102 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S201 to S207, but not limited thereto), and the processor 6101 performs at least one of the other steps. In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated together. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, sending unit, transmitter, sending circuit, etc., can be used interchangeably; the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.
[0381] In some embodiments, the communication device 6100 further includes one or more memories 6103 for storing data and / or instructions. Optionally, one or more processors 6101 are used to invoke instructions stored in the memory 6103 to cause the communication device 6100 to perform any of the above methods. Optionally, all or part of the memory 6103 may also be located outside the communication device 6100. In an optional embodiment, the communication device 6100 may include one or more interface circuits 6104. Optionally, the interface circuit 6104 is connected to the memory 6103 and can be used to receive data and / or instructions from the memory 6103 or other devices, and can be used to send data and / or instructions to the memory 6103 or other devices. For example, the interface circuit 6104 can read data and / or instructions stored in the memory 6103 and send the data and / or instructions to the processor 6101.
[0382] The communication device 6100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 6100 described in this disclosure is not limited thereto, and the structure of the communication device 6100 may not be limited by FIG. 6A. The communication device may be a standalone device or a part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data, programs and / or instructions; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.
[0383] Figure 6B is a schematic diagram of the chip structure according to an embodiment of the present disclosure. For cases where the communication device 6100 can be a chip or a chip system, please refer to the schematic diagram of the chip 6200 shown in Figure 6B, but it is not limited thereto.
[0384] Chip 6200 includes one or more processors 6201. Chip 6200 is used to perform any of the methods described above.
[0385] In some embodiments, chip 6200 further includes one or more interface circuits 6202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 6200 further includes one or more memories 6203 for storing data and / or instructions. Optionally, all or part of the memories 6203 may be located outside of chip 6200. Optionally, interface circuit 6202 is connected to memory 6203, and interface circuit 6202 can be used to receive data and / or instructions from memory 6203 or other devices, and interface circuit 6202 can be used to send data and / or instructions to memory 6203 or other devices. For example, interface circuit 6202 can read data and / or instructions stored in memory 6203 and send the data and / or instructions to processor 6201.
[0386] In some embodiments, the interface circuit 6202 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., steps S201 to S207, but not limited thereto). For example, the interface circuit 6202 performing the communication steps such as sending and / or receiving in the above-described method means that the interface circuit 6202 performs data and / or instruction interaction between the processor 6201, the chip 6200, the memory 6203, or the transceiver device. In some embodiments, the processor 6201 performs at least one of the other steps.
[0387] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.
[0388] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform any of the methods described above. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.
[0389] This disclosure also provides a program product, including a program and / or instructions, which, when executed by a communication device, cause the communication device to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.
[0390] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.
[0391] Other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of the invention are indicated by the following claims.
[0392] It should be understood that the present invention is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.
Claims
1. A communication method, executed by a first access network device, the method comprising: Receive the Radio Resource Control (RRC) connection restoration request message sent by the terminal; Based on the RRC connection recovery request message, a first message is sent to the core network device. The first message is used to trigger the core network device to determine the first key information. The first key information is used for the terminal and the first access network device to perform key updates. The updated key is used for security protection and / or integrity protection between the terminal and the first access network device.
2. The method according to claim 1, wherein, The method further includes: Receive a second message sent by the core network device based on the first message, wherein the second message carries the first key information; The first key information is sent to the terminal, and the first key information is used by the terminal to update the key.
3. The method according to claim 2, wherein, The first key information is carried in downlink signaling associated with the transport block TB containing the RRC connection recovery message sent to the terminal, and the downlink signaling includes one of the following: Downlink control information (DCI) is used to schedule the TB. Media access control MAC control unit CE; RRC signaling.
4. The method according to claim 3, wherein, The downlink signaling is the MAC CE or the RRC signaling, the downlink signaling is unencrypted, and / or the downlink signaling is protected for integrity using the updated key.
5. The method according to any one of claims 2 to 4, wherein, The method further includes: Based on the first key information, the key is updated.
6. The method according to any one of claims 1 to 5, wherein, The updated key is also used to provide security and / or integrity protection for third messages between the terminal and the first access network device; wherein the third message includes at least one of the following: An RRC connection restoration message is sent to the terminal; Uplink information; Downlink information.
7. The method according to claim 6, wherein, The third message does not include the RRC connection recovery message, which is used for security and / or integrity protection based on the key used by the terminal before entering the RRC disconnected state.
8. The method according to claim 7, wherein, The terminal locally stores second key information. The second key information is in an available state, and the key used by the terminal before entering the RRC disconnected state is determined based on the second key information; or, the second key information is in an unavailable state, and the key used by the terminal before entering the RRC disconnected state is the key stored locally by the terminal.
9. The method according to any one of claims 1 to 8, wherein, The first message carries at least one of the following: The identifier of the terminal; An identifier for a first connection between the second access network device and the core network device, wherein the first connection is associated with the terminal; The second access network device is the anchor point device of the first access network device.
10. A communication method executed by a terminal, the method comprising: Sending a Radio Resource Control (RRC) Connection Recovery Request message to a first access network device triggers the first access network device to send a first message to a core network device based on the RRC Connection Recovery Request message. The first message triggers the core network device to determine first key information. The first key information is used for key updates between the terminal and the first access network device. The updated key is used for security and / or integrity protection between the terminal and the first access network device.
11. The method according to claim 10, wherein, The method further includes: The terminal receives the first key information sent by the first access network device. The first key information is used by the terminal to update the key. The first key information is sent by the first access network device after receiving a second message sent by the core network device based on the first message. The second message carries the first key information.
12. The method according to claim 11, wherein, The first key information is carried in the downlink signaling associated with the transport block TB containing the RRC connection recovery message sent by the first access network device, and the downlink signaling includes one of the following: Downlink control information (DCI) is used to schedule the TB. Media access control MAC control unit CE; RRC signaling.
13. The method according to claim 12, wherein, The downlink signaling is the MAC CE or the RRC signaling, the downlink signaling is unencrypted, and / or the downlink signaling is protected for integrity using the updated key.
14. The method according to any one of claims 11 to 13, wherein, The method further includes: Based on the first key information, the key is updated.
15. The method according to any one of claims 10 to 14, wherein, The updated key is also used to provide security and / or integrity protection for third messages between the terminal and the first access network device; wherein the third message includes at least one of the following: Receive the RRC connection recovery message sent by the first access network device; Uplink information; Downlink information.
16. The method according to claim 15, wherein, The third message does not include the RRC connection recovery message, which is used for security and / or integrity protection based on the key used by the terminal before entering the RRC disconnected state.
17. The method according to claim 16, wherein, The terminal locally stores second key information. The second key information is in an available state, and the key used by the terminal before entering the RRC disconnected state is determined based on the second key information; or, the second key information is in an unavailable state, and the key used by the terminal before entering the RRC disconnected state is the key stored locally by the terminal.
18. A communication method, performed by a core network device, the method comprising: The system receives a first message sent by a first access network device. The first message is used to trigger the core network device to determine first key information. The first key information is used for key updates between the terminal and the first access network device. The updated key is used for security protection and / or integrity protection between the terminal and the first access network device. The first message is sent by the first access network device when it receives a Radio Resource Control (RRC) connection recovery request message sent by the terminal.
19. The method according to claim 18, wherein, The method further includes: Based on the first message, a second message is sent to the first access network device, the second message carrying the first key information.
20. The method according to claim 18 or 19, wherein, The first message carries at least one of the following: The identifier of the terminal; An identifier for a first connection between the second access network device and the core network device, wherein the first connection is associated with the terminal; The second access network device is the anchor point device of the first access network device.
21. A communication device for performing the communication method according to any one of claims 1 to 9, 10 to 17, 18 to 20.
22. A communication system comprising a first access network device, a terminal, and a core network device, wherein the first access network device is configured to implement the communication method of any one of claims 1 to 9, the terminal is configured to implement the communication method of any one of claims 10 to 17, and the core network device is configured to implement the communication method of any one of claims 18 to 20.
23. A storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the communication method as described in any one of claims 1 to 9, 10 to 17, and 18 to 20.
24. A program product comprising at least one of a program and instructions, wherein the program and instructions, when executed by a communication device, implement the communication method according to any one of claims 1 to 9, 10 to 17, and 18 to 20.
