WO2021056563A1 - 通信方法和通信装置 - Google Patents
通信方法和通信装置 Download PDFInfo
- Publication number
- WO2021056563A1 WO2021056563A1 PCT/CN2019/109183 CN2019109183W WO2021056563A1 WO 2021056563 A1 WO2021056563 A1 WO 2021056563A1 CN 2019109183 W CN2019109183 W CN 2019109183W WO 2021056563 A1 WO2021056563 A1 WO 2021056563A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- network device
- message
- access network
- security verification
- terminal device
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/08—Access security
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/15—Setup of multiple wireless link connections
- H04W76/16—Involving different core network technologies, e.g. a packet-switched [PS] bearer in combination with a circuit-switched [CS] bearer
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/06—Authentication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/60—Context-dependent security
- H04W12/69—Identity-dependent
- H04W12/73—Access point logical identity
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/27—Transitions between radio resource control [RRC] states
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W40/00—Communication routing or communication path finding
- H04W40/34—Modification of an existing route
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/04—Large scale networks; Deep hierarchical networks
- H04W84/06—Airborne or Satellite Networks
Definitions
- This application relates to the communication field, and in particular to a communication method and communication device in the communication field.
- the radio resource control (radio resource control, RRC) state of the terminal device includes a connected state (RRC_CONNECTED), a deactivated state (RRC_INACTIVE), and an idle state (RRC_IDLE).
- RRC_CONNECTED When the terminal device is in the connected state, the terminal device has established links with the access network device and the core network device. When data arrives on the network, the core network device and the access network device can directly transmit the data to the terminal device .
- the terminal device is in the deactivated state, it means that the terminal device has previously established links with the access network device and the core network device, but the link between the terminal device and the access network device is released. Although the link is released, the access network device needs to save the context of the terminal device.
- the access network device can quickly restore the released link according to the context of the terminal device.
- the terminal device When the terminal device is in the idle state, there is no link between the terminal device and the access network device and the core network device.
- the link between the terminal device and the access network device and the core network device needs to be established .
- the deactivated state can only be changed through the RRC connection release message when the terminal device is in the connected state.
- the access network device serving the terminal device can be Called anchor point access network equipment or source access network equipment
- the access network device currently serving the terminal device may be referred to as the target access network device
- the access network equipment moves faster, for example, every 1 minute to 2 minutes, the terminal equipment needs to change the serving cell (That is to replace the target access network equipment).
- the context of the terminal device is only stored in the anchor point access network device. If the terminal device in the deactivated state requests to restore the RRC connection, it is difficult for the target access network device to find the anchor point access network device, and then to the anchor point to access the network. The device obtains the context information of the terminal device. Therefore, how to ensure the operation of the connection recovery mechanism of the terminal device has become an urgent problem to be solved.
- the present application provides a communication method and a communication device, which can ensure the operation of the connection recovery mechanism of the terminal device, reduce the influence of the mobility of the access network device on the connection recovery process of the terminal device, and thereby improve the system performance.
- a communication method including: a first access network device sends a first message to a terminal device, the first message is used to instruct the terminal device to enter a deactivated state; the first access The network device sends a second message to the core network device, where the second message carries the context information of the terminal device and a first security verification parameter, and the first security verification parameter is used to perform security verification on the terminal device; The first access network device receives a third message from a second access network device, and the third message is used to request context information of the terminal device; the first access network device sends a message to the second access network device.
- the network access device sends a fourth message, where the fourth message indicates that the first access network device does not provide the context information to the second access network device.
- the context information of the terminal device and the security verification parameters used to verify the terminal device are sent to the core network device through the first access network device, so that the second access network device can receive the information from the core network device. Acquire the context information of the terminal device, thereby restoring the connection between the terminal device and the second access network device, avoiding that the second access network device cannot find the first access network device or the first access network device does not provide the terminal device.
- context information if the connection cannot be restored, the operation of the connection restoration mechanism of the terminal device can be guaranteed, and the influence of the mobility of the access network device on the connection restoration process of the terminal device can be reduced, thereby improving system performance.
- the context information of the terminal device may also be referred to as the context of the terminal device or the context data of the terminal device.
- the context information of the terminal device may include information such as the PDU session context, the security key, the wireless capability of the terminal device, and the security capability of the terminal device.
- the fourth message is further used to indicate identification information of the core network device.
- the first access network device stores the context information of the terminal device, and the method further includes: the first access network device according to the The first security verification parameter performs security verification on the terminal device; the first access network device sends a fourth message to the second access network device according to the third message, including: In the case of passing the security verification, if the first access network device determines not to provide the context information to the second access network device, the first access network device sends the context information to the second access network device. Send the fourth message.
- the foregoing third message may carry the reason why the terminal device requests to resume the connection, and the first access network device may determine whether to provide the second access network device with the context of the terminal device according to the reason why the terminal device requests to resume the connection. information.
- the reason for requesting to restore the connection may be, for example, a radio access network notification area update (RNAU), or any of other active or passive service triggering reasons, which is not limited in the embodiment of the present application.
- RNAU radio access network notification area update
- the third message carries a second security verification parameter of the terminal device, and the second security verification parameter is used to perform security verification on the terminal device
- the method further includes: the first access network device sends a fifth message to the core network device, the fifth message carrying the second security verification parameter to update the security stored in the core network device Verify the parameters.
- the first access network device In the case that the first access network device successfully authenticates the terminal device's security, but determines that the context information of the terminal device is not provided, the first access network device needs to update the stored security verification parameters and update the security verification parameters for the core network device . That is, the core network device needs to update the security verification parameter from the first security verification parameter to the second security verification parameter in order to perform security verification on the terminal device next time. Therefore, the above-mentioned second security verification parameter needs to be carried in the above-mentioned third message, which is sent by the second access network device to the first access network device, and then sent by the first access network device to the core network device through the fifth message .
- the core network device can obtain the latest security verification parameters for the next terminal device security verification, thereby ensuring that the security verification parameters saved by the terminal device and the core network device are consistent, avoiding security verification failures, and ensuring that the terminal device
- the operation of the connection recovery mechanism reduces the impact of the mobility of the access network equipment on the connection recovery process of the terminal equipment, thereby improving system performance.
- the second security verification parameter includes the second cell radio network temporary identifier C-RNTI allocated by the second access network device to the terminal device, and The second physical cell identifier PCI of the terminal device in the cell of the second access network device.
- the method further includes: the first access network device deletes Context information of the terminal device.
- the first security verification parameter includes the first C-RNTI allocated by the first access network device to the terminal device and the terminal device The first PCI of the cell of the first access network device.
- another communication method including: a core network device receives a second message from a first access network device, the second message carrying context information of the terminal device and a first security verification parameter, the The first security verification parameter is used to perform security verification on the terminal device; the core network device saves the context information and the first security verification parameter.
- the method further includes: the core network device receives a sixth message from the second access network device, the sixth message being used to request the Context information of the terminal device; the core network device performs security verification on the terminal device according to the first security verification parameter; in the case where the security verification is passed, the core network device communicates to the second connection
- the network access device sends a seventh message, where the seventh message carries the context information, or the seventh message indicates that the core network device does not provide the context information to the second access network device.
- the sixth message carries a second security verification parameter of the terminal device, and the second security verification parameter is used to perform security verification on the terminal device ,
- the method further includes: the core network device updates a security verification parameter from the first security verification parameter to the second security verification parameter.
- the second security verification parameter includes the second cell radio network temporary identifier C-RNTI allocated by the second access network device to the terminal device, and The second physical cell identifier PCI of the terminal device in the cell of the second access network device.
- the method further includes: the core network The device deletes the context information of the terminal device.
- the first security verification parameter includes the first C-RNTI allocated by the first access network device to the terminal device and the terminal device The first PCI of the cell of the first access network device.
- another communication method including: a second access network device receives an eighth message from a terminal device, where the eighth message is used to request to restore the connection; and the second access network device sends a request to the core
- the network device sends a sixth message, the sixth message is used to request the context information of the terminal device;
- the second access network device receives a seventh message from the core network device, the seventh message carries all The context information, or the seventh message indicates that the core network device does not provide the context information to the second access network device.
- the method before the second access network device sends the sixth message to the core network device, the method further includes: the second access network device according to The eighth message is to send a third message to the first access network device, and the third message is used to request context information of the terminal device; the second access network device receives information from the first access network device.
- the fourth message of the network device where the fourth message indicates that the first access network device does not provide the context information to the second access network device, and the fourth message also indicates that the core network device
- the identification information of the second access network device; the sixth message sent by the second access network device to the core network device includes: the second access network device sends the second access network device to the core network device according to the identification information of the core network device Sixth news.
- the fifth message carries the second security verification parameter of the terminal device, so that the core network device updates the security verification parameter from the first security verification parameter It is a second security verification parameter, and the second security verification parameter is used to perform security verification on the terminal device.
- the first security verification parameter includes the first cell radio network temporary identifier C-RNTI allocated by the first access network device to the terminal device, and The first physical cell identifier PCI of the terminal device in the cell of the first access network device;
- the second security verification parameter includes the second C- assigned by the second access network device to the terminal device The RNTI and the second PCI of the terminal device in the cell of the second access network device.
- a communication device for executing the method in any possible implementation manner of the foregoing aspects.
- the device includes a unit for executing the method in any one of the possible implementation manners of the foregoing aspects.
- another communication device including a processor, which is coupled to a memory and can be used to execute instructions in the memory to implement a method in any possible implementation manner of the foregoing aspects.
- the communication device further includes a memory.
- the communication device further includes a communication interface, and the processor is coupled with the communication interface.
- the communication device is an access network device.
- the communication interface may be a transceiver, or an input/output interface.
- the communication device is a chip configured in an access network device.
- the communication interface may be an input/output interface.
- the communication device is a core network device.
- the communication interface may be a transceiver, or an input/output interface.
- the communication device is a chip configured in a core network device.
- the communication interface may be an input/output interface.
- the communication device is a terminal device.
- the communication interface may be a transceiver, or an input/output interface.
- the communication device is a chip configured in a terminal device.
- the communication interface may be an input/output interface.
- a processor including: an input circuit, an output circuit, and a processing circuit.
- the processing circuit is configured to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor executes the method in any one of the possible implementation manners of the foregoing aspects.
- the above-mentioned processor may be a chip, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a flip-flop, and various logic circuits.
- the input signal received by the input circuit may be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit may be, for example, but not limited to, output to the transmitter and transmitted by the transmitter, and the input circuit and output
- the circuit can be the same circuit, which is used as an input circuit and an output circuit at different times.
- the embodiments of the present application do not limit the specific implementation manners of the processor and various circuits.
- a processing device including a processor and a memory.
- the processor is used to read instructions stored in the memory, and can receive signals through a receiver, and transmit signals through a transmitter, so as to execute the method in any one of the possible implementation manners of the foregoing aspects.
- processors there are one or more processors and one or more memories.
- the memory may be integrated with the processor, or the memory and the processor may be provided separately.
- the memory can be a non-transitory (non-transitory) memory, such as a read only memory (ROM), which can be integrated with the processor on the same chip, or can be set in different On the chip, the embodiment of the present application does not limit the type of the memory and the setting mode of the memory and the processor.
- ROM read only memory
- sending instruction information may be a process of outputting instruction information from the processor
- receiving capability information may be a process of the processor receiving input capability information.
- the processed output data may be output to the transmitter, and the input data received by the processor may come from the receiver.
- the transmitter and receiver can be collectively referred to as a transceiver.
- the processing device in the seventh aspect described above may be a chip, and the processor may be implemented by hardware or software.
- the processor When implemented by hardware, the processor may be a logic circuit, an integrated circuit, etc.; when implemented by software
- the processor may be a general-purpose processor, which is implemented by reading software codes stored in the memory.
- the memory may be integrated in the processor, may be located outside the processor, and exist independently.
- a computer program product includes: a computer program (also called code, or instruction), which when the computer program is executed, causes a computer to execute any of the above aspects.
- a computer program also called code, or instruction
- a computer-readable medium stores a computer program (also referred to as code, or instruction) when it runs on a computer, so that the computer executes any of the above aspects.
- a computer program also referred to as code, or instruction
- a communication system including the aforementioned terminal equipment, access network equipment, and core network equipment.
- Fig. 1 shows a schematic diagram of a communication system according to an embodiment of the present application.
- Fig. 2 shows a schematic flowchart of a communication method according to an embodiment of the present application.
- Fig. 3 shows a schematic flowchart of another communication method according to an embodiment of the present application.
- Fig. 4 shows a schematic flowchart of another communication method according to an embodiment of the present application.
- Fig. 5 shows a schematic block diagram of a communication device according to an embodiment of the present application.
- Fig. 6 shows a schematic block diagram of another communication device according to an embodiment of the present application.
- FIG. 7 shows a schematic block diagram of another communication device according to an embodiment of the present application.
- Figure 8 shows a schematic structural diagram of a network device according to an embodiment of the present application.
- LTE long term evolution
- FDD frequency division duplex
- UMTS universal mobile telecommunication system
- 5G fifth generation
- NR new radio
- the terminal equipment in the embodiments of this application may also be referred to as: user equipment (UE), mobile station (MS), mobile terminal (MT), access terminal, user unit, user station, Mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
- UE user equipment
- MS mobile station
- MT mobile terminal
- access terminal user unit, user station, Mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
- the terminal device may be a device that provides voice/data connectivity to the user, for example, a handheld device with a wireless connection function, a vehicle-mounted device, and so on.
- a handheld device with a wireless connection function for example, a vehicle-mounted device, and so on.
- some examples of terminals are: mobile phones (mobile phones), tablet computers, notebook computers, handheld computers, mobile internet devices (MID), wearable devices, virtual reality (VR) devices, and augmented reality.
- Wireless terminals in transportation safety transportation safety
- wireless terminals in smart city smart city
- wireless terminals in smart home smart home
- cellular phones cordless phones
- session initiation protocol session initiation protocol
- SIP session initiation protocol
- WLL wireless local loop
- PDA personal digital assistant
- handheld device with wireless communication function computing device or other processing device connected to wireless modem
- vehicle Devices wearable devices
- terminal devices in a 5G network or terminal devices in a public land mobile network (PLMN) that will evolve in the future, etc., which are not limited in the embodiment of the present application.
- PLMN public land mobile network
- the terminal device may also be a wearable device.
- Wearable devices can also be called wearable smart devices. It is a general term for using wearable technology to intelligently design everyday wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes.
- a wearable device is a portable device that is directly worn on the body or integrated into the user's clothes or accessories. Wearable devices are not only a kind of hardware device, but also realize powerful functions through software support, data interaction, and cloud interaction.
- wearable smart devices include full-featured, large-sized, complete or partial functions that can be achieved without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, and need to cooperate with other devices such as smart phones.
- the terminal device may also be a terminal device in the Internet of Things (IoT) system.
- IoT Internet of Things
- Its main technical feature is to pass items through communication technology. Connect with the network to realize the intelligent network of human-machine interconnection and interconnection of things.
- the access network equipment and the core network equipment in the embodiments of the present application may be collectively referred to as network equipment.
- the access network device may be a device used to communicate with a terminal device.
- the access network device may also be called a wireless access network device, which may be a transmission reception point (TRP) and an integrated access backhaul.
- TRP transmission reception point
- IAB Integrated access and backhaul
- IAB can be an evolved NodeB (evolved NodeB, eNB, or eNodeB) in an LTE system, or a home base station (for example, home evolved NodeB, or home Node B, HNB), baseband Unit (base band unit, BBU), or it can be a wireless controller in the cloud radio access network (cloud radio access network, CRAN) scenario, or the access network device can be a relay station, an access point, a vehicle Wearable devices and access network equipment in the 5G network or the access network equipment in the future evolving public land mobile network (PLMN) network can be the access point in the WLAN.
- AP which may be a gNB or ng-eNB in a new radio system (NR) system, which is not limited in the embodiment of the present application.
- the access network device may include a centralized unit (CU) node, or a distributed unit (DU) node, or a RAN device including a CU node and a DU node, or a control plane CU node (CU-CP node), user plane CU node (CU-UP node) and RAN equipment of DU node.
- CU centralized unit
- DU distributed unit
- RAN device including a CU node and a DU node, or a control plane CU node (CU-CP node), user plane CU node (CU-UP node) and RAN equipment of DU node.
- CU-CP node control plane CU node
- CU-UP node user plane CU node
- the access network equipment provides services for the cell.
- the terminal equipment communicates with the cell through the transmission resources (for example, frequency domain resources, or spectrum resources) allocated by the access network equipment.
- the cell may belong to a macro base station (for example, a macro eNB or a macro eNB). Macro gNB, etc.), can also belong to the base station corresponding to the small cell, where the small cell can include: metro cell, micro cell, pico cell, femto cell ( Femto cells), etc., these small cells have the characteristics of small coverage and low transmit power, and are suitable for providing high-rate data transmission services.
- the core network element in the embodiment of the application may be a core network element in a 4G network, for example, a mobile management entity (mobile management entity, MME), a serving gateway (SGW), etc., or it may be a core network element in a 5G network Core network elements, for example, access and mobility management function (AMF) network elements, user plane function (UPF) network elements, etc., can also be core network elements with other names This is not limited in the embodiment of the application.
- MME mobile management entity
- SGW serving gateway
- Core network elements for example, access and mobility management function (AMF) network elements, user plane function (UPF) network elements, etc.
- AMF access and mobility management function
- UPF user plane function
- the terminal device or the network device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer.
- the hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also referred to as main memory).
- the operating system may be any one or more computer operating systems that implement business processing through processes, for example, Linux operating systems, Unix operating systems, Android operating systems, iOS operating systems or windows operating systems.
- the application layer includes applications such as browsers, address books, word processing software, and instant messaging software.
- the embodiments of the application do not specifically limit the specific structure of the execution body of the method provided in the embodiments of the application, as long as the program that records the codes of the methods provided in the embodiments of the application can be provided in accordance with the embodiments of the application.
- the execution subject of the method provided in the embodiments of the present application may be a terminal device or a network device, or a functional module in the terminal device or the network device that can call and execute the program.
- various aspects or features of the present application can be implemented as methods, devices, or products using standard programming and/or engineering techniques.
- article of manufacture used in this application encompasses a computer program accessible from any computer-readable device, carrier, or medium.
- computer-readable media may include, but are not limited to: magnetic storage devices (for example, hard disks, floppy disks or tapes, etc.), optical disks (for example, compact discs (CD), digital versatile discs (DVD)) Etc.), smart cards and flash memory devices (for example, erasable programmable read-only memory (EPROM), cards, sticks or key drives, etc.).
- various storage media described herein may represent one or more devices and/or other machine-readable media for storing information.
- machine-readable medium may include, but is not limited to, wireless channels and various other media capable of storing, containing, and/or carrying instructions and/or data.
- Fig. 1 is a schematic diagram of a communication system suitable for an embodiment of the present application.
- the communication system 100 may include a core network device 110, a first access network device 120, a second access network device 130, and a terminal device 140.
- the terminal device 140 is in a cell corresponding to the coverage area of the first access network device and can be connected to the first access network device 120 in a wireless manner.
- the first access network device 120 and the second access network device 130 It may be connected to the core network device 110 in a wireless or wired manner.
- the core network device 110 and the first access network device 120 can be separate and different physical devices, or they can integrate the functions of the core network device 140 with the logical functions of the access network device On the same physical device, it may also be a physical device that integrates the functions of part of the core network equipment and part of the access network equipment, which is not limited in the embodiment of the present application.
- the terminal device 140 may be movable. If the terminal device 140 moves to the cell corresponding to the coverage area of the first access network device 120, the terminal device 140 can transmit the uplink data packet to the first access network device 120, and the first access network device 120 can send it to the core. ⁇ 110 ⁇ Network equipment 110. The first access network device 120 may also transmit the downlink data packet from the core network device 110 to the terminal device 140. If the terminal device 140 moves to a cell corresponding to the coverage area of the second access network device 130, the data transmission mode is the same, and details are not described herein again.
- the first access network device 120 and the second access network device 130 may be movable. If the movement of the first access network device 120 causes the terminal device 140 to be in a cell corresponding to the coverage area of the first access network device 120, the terminal device 140 can transmit the uplink data packet to the first access network device 120, and the first access network device 120 An access network device 120 is sent to the core network device 110. The first access network device 120 may also transmit the downlink data packet from the core network device 110 to the terminal device 140. If the movement of the second access network device 140 causes the terminal device 140 to be in a cell corresponding to the coverage area of the second access network device 130, the data transmission method is the same, and details are not described herein again.
- the aforementioned access network equipment may include a baseband device and a radio frequency device.
- the baseband device can be implemented by one node or multiple nodes.
- the radio frequency device It can be remotely implemented independently from the baseband device, or integrated into the baseband device, or partly remotely and partly integrated into the baseband device.
- the access network equipment includes a baseband device and a radio frequency device.
- the radio frequency device can be arranged remotely relative to the baseband device, for example, a remote radio unit (RRU) is arranged remotely relative to the BBU.
- RRU remote radio unit
- Each of the aforementioned communication devices may be configured with multiple antennas.
- the plurality of antennas may include at least one transmitting antenna for transmitting signals and at least one receiving antenna for receiving signals.
- each communication device additionally includes a transmitter chain and a receiver chain.
- Those of ordinary skill in the art can understand that they can all include multiple components related to signal transmission and reception (such as processors, modulators, multiplexers, etc.). , Demodulator, demultiplexer or antenna, etc.). Therefore, multi-antenna technology can be used to communicate between the access network device and the terminal device.
- FIG. 1 is only a schematic diagram, and the communication system 100 may also include other network devices, such as wireless relay devices and wireless backhaul devices, which are not shown in FIG. 1.
- the embodiment of the present application does not limit the number of core network equipment, access network equipment, and terminal equipment included in the communication system 100.
- Non-terrestrial network non-terrestrial network, NTN
- the NTN communication system may include a satellite communication system, a high altitude platform (HAPS) communication system, or other non-terrestrial communication systems.
- the NTN communication system provides seamless coverage for terminal equipment by deploying the functions of the access network equipment or part of the access network equipment on non-ground equipment (such as high-altitude platforms or satellites, etc.).
- Non-ground equipment is more affected by natural disasters. Small, can improve the reliability of the communication system.
- ground stationary cells In non-terrestrial networks based on satellite deployment, satellites adjust antennas to form different beams to cover the ground.
- two types of cells can be divided: ground stationary cells and ground mobile cells.
- the mapping method of the ground stationary cell means that the location of the cell is not moving on the ground, and the moving satellite adjusts its own beam to form these cells.
- the mapping method of the ground mobile cell means that the beam generated by the satellite moves on the ground along with the movement of the satellite, and correspondingly, the cell formed by the beam also moves on the ground.
- the NTN network equipment corresponding to this cell may also be called a low-earth orbit (LEO) or other mobile NTN network equipment.
- LEO low-earth orbit
- the radio resource control state of the terminal device includes a connected state (RRC_CONNECTED), a deactivated state (RRC_INACTIVE), and an idle state (RRC_IDLE).
- RRC_CONNECTED a connected state
- RRC_INACTIVE a deactivated state
- RRC_IDLE an idle state
- the terminal device When the terminal device is in the connected state, the terminal device has established a link with the access network device and the core network device. When data arrives on the network, the core network device and the access network device can directly transmit the data to The terminal equipment.
- the terminal device When the terminal device is in the deactivated state, it means that the terminal device has previously established links with the access network device and the core network device, but the link between the terminal device and the access network device is released. Although the link is released, the access network device needs to save the context of the terminal device. When data needs to be transmitted, the access network device can quickly restore the released link according to the context of the terminal device.
- the access network device that configures the terminal device to enter the deactivated state and stores the context of the terminal device may be referred to as an anchor access network device or a source access network device.
- the anchor point access network device may change, that is, if the original anchor point access network device transfers the context of the terminal device to the new access network device, the new access network device The network equipment will subsequently be used as a new anchor point to access the network equipment.
- the anchor point access network device may also choose not to transfer the context of the terminal device, and there is no restriction here.
- the deactivated state can only be changed by the RRC connection release message when the terminal device is in the connected state.
- the access network device serving the terminal device ie The aforementioned anchor point access network device or source access network device
- the terminal device subsequently initiates the RRC connection recovery process, it needs to carry the above-mentioned identifier to the access network device currently serving the terminal device (may be referred to as the target access network device) to obtain the context of the terminal device.
- the target access network device may be referred to as the target access network device
- the access network equipment moves faster, for example, every 1 minute to 2 minutes, the terminal equipment needs to be replaced once.
- Residential area that is, to replace the target access network equipment.
- the context of the terminal device is only stored in the anchor point access network device. If the terminal device in the deactivated state requests to restore the RRC connection, it is difficult for the target access network device to find the anchor point access network device, and thus to the anchor point access network device.
- the device obtains the context information of the terminal device. If the context information of the terminal device can be stored in other network devices, the mechanism by which the network device authenticates the terminal device needs to be considered.
- the present application provides a communication method that can ensure the operation of the connection recovery mechanism of the terminal device, reduce the impact of the mobility of the access network device on the connection recovery process of the terminal device, and thereby improve the system performance.
- FIG. 2 shows a schematic flowchart of a communication method 200 according to an embodiment of the present application.
- the method 200 can be applied to the communication system 100 shown in FIG. 1, but the embodiment of the present application is not limited thereto.
- the first access network device is equivalent to the foregoing anchor point access network device or the source access network device
- the second access network device is equivalent to the foregoing target access network device.
- the method includes:
- the first access network device sends a first message to the terminal device, where the first message is used to instruct the terminal device to enter the deactivated state; then, correspondingly, the terminal device receives the first message and enters the deactivated state.
- the first access network device determines that the terminal device needs to enter the deactivated state, it will send the above-mentioned first message to the terminal device and save the context information of the terminal device.
- the context information of the terminal device may also be referred to as the context of the terminal device or the context data of the terminal device.
- the context information of the terminal device may include information such as the PDU session context, the security key, the wireless capability of the terminal device, and the security capability of the terminal device.
- the foregoing first message may also be referred to as an RRC connection release (RRC release) message, or another name, which is not limited in the embodiment of the present application.
- the foregoing first message may carry an identifier assigned by the first access network device to the terminal device (for example, an inactive radio network temporary identifier (I-RNTI)), which is used to identify the first access network device.
- I-RNTI inactive radio network temporary identifier
- the foregoing first message may also carry a next hop chaining count (NCC), which is used for key derivation.
- NCC next hop chaining count
- the first access network device sends a second message to the core network device, where the second message carries context information of the terminal device and a first security verification parameter, and the first security verification parameter is used to perform security on the terminal device. Verification; Correspondingly, the core network device receives the second message.
- the first security verification parameter may include a first cell radio network temporary identifier (C-RNTI) allocated by the first access network device to the terminal device.
- C-RNTI cell radio network temporary identifier
- the first security verification parameter may also include a first physical cell identifier (PCI) of the terminal device in the cell of the first access network device.
- PCI physical cell identifier
- S203 The core network device saves the context information and the first security verification parameter.
- the first access network device may send the context information of the terminal device and the first security verification parameter to the core network device, and the core network device may save the Context information and the first security verification parameter, so that other access network devices can obtain the context information of the terminal device from the core network device. Since the context information of the terminal device is stored on the core network device, the core network device needs to save the first security verification parameter at the same time, so that when other access network devices obtain the context information of the terminal device from the core network device, the terminal device can be secured verification.
- the terminal device sends an eighth message to the second access network device, where the eighth message is used to request to restore the connection (that is, the connection between the terminal device and the second access network device, such as an RRC connection), then correspondingly, The second access network device receives the eighth message from the terminal device.
- the eighth message is used to request to restore the connection (that is, the connection between the terminal device and the second access network device, such as an RRC connection)
- the second access network device receives the eighth message from the terminal device.
- the terminal device Due to the mobility of the terminal device and/or the access network device, when the terminal device in the deactivated state needs to restore the connection (that is, switch to the active state), the terminal device is already in the coverage area of the second access network device. In the small area, the second access network device needs to provide services for the terminal device. Therefore, the terminal device may send the above-mentioned eighth message to the second access network device, requesting to restore the connection.
- the above-mentioned eighth message may carry an identifier (for example, I-RNTI) allocated by the first access network device to the terminal device, so that the second access network device can obtain the context information of the terminal device according to the identifier.
- the above-mentioned eighth message may also carry authentication information of the terminal device.
- the authentication information may be a short message authentication code-integrity (short message authentication code-integrity, short MAC-I) message, and the short MAC-I message is a 16-bit authentication message.
- the terminal device can use the C-RNTI of the cell of the terminal device on the first access network device, the PCI of the cell, and the ID of the cell of the second access network device where the terminal device is currently located as input, combined with other secrets. Key parameters, calculate the above short MAC-I message.
- the above-mentioned eighth message may also carry the reason why the terminal device requests to resume the connection.
- the reason for requesting to restore the connection may be, for example, a radio access network notification area update (RNAU), or any of other active or passive service triggering reasons, which is not limited in the embodiment of the present application.
- RNAU radio access network notification area update
- the second access network device acquiring the context information of the terminal device can be divided into the following different situations:
- the second access network device does not find the first access network device, or the second access network device does not find the first access network device.
- the second access network device can only request the core network device for the context information of the terminal device. Therefore, in this embodiment, the following processes can be executed after S201-S204:
- the second access network device sends a sixth message to the core network device, where the sixth message is used to request context information of the terminal device; then, correspondingly, the core network device receives the sixth message.
- the sixth message may carry I-RNTI and authentication information.
- the sixth message also carries the cell ID of the cell of the second access network device where the terminal device is currently located.
- the sixth message may also carry second security verification parameters.
- the second security verification parameter includes the second C-RNTI allocated by the second access network device to the terminal device.
- the second security verification parameter further includes the second PCI of the terminal device in the cell of the second access network device. It should be understood that, in this article, the cell of the second access network device refers to the cell in which the terminal device initiates an access or recovery request in the second access network device.
- S209 The core network device performs security verification on the terminal device according to the first security verification parameter.
- the core network device may use the previously saved first security verification parameter to verify the terminal device.
- the core network device may verify the terminal device according to the foregoing first C-RNTI, or the foregoing first C-RNTI and the first PCI.
- the above verification of the terminal device may refer to verifying the short MAC-I message of the terminal device.
- the core network device uses the previously stored key and the first The security verification parameters are calculated according to the same method to calculate the short MAC-I message.
- the core network device compares the short MAC-I message calculated by itself with the short MAC-I message received from the second access network device, and if they are the same, the verification passes, otherwise, the verification fails.
- the core network device sends a seventh message to the second access network device.
- the seventh message carries the context information, or the seventh message indicates that the core network device does not provide the context information to the second access network device; then, correspondingly, the second access network device The network device receives the seventh message from the core network device.
- the second access network device may send a response message (not shown in FIG. 2) to the terminal device according to the seventh message.
- the response message may indicate that the terminal device is allowed to resume the connection or the response message may instruct the terminal device to release the connection; the seventh message indicates that the core network device does not provide context to the second access network device In case of information, the response message may indicate that the terminal device is refused to resume the connection, or the response message may indicate that the terminal device releases the connection.
- the core network device generates a response message, and sends a seventh message carrying the response message to the second access network device.
- the seventh message instructs the core network device not to provide context information to the second access network device. 2.
- the access network device forwards the response message to the terminal device.
- the core network device may determine whether to provide the second access network device with the context of the terminal device. If the core network device determines to provide the second access network device with the context information of the terminal device, the core network device can find the context information of the terminal device according to the identifier (for example, I-RNTI) assigned to the terminal device by the first access network device , And directly send the context information to the second access network device. If the core network device determines not to provide the second access network device with the context information of the terminal device, the core network device may send to the second access network device to instruct the core network device not to provide the second access network device Context information message.
- the core network device may send to the second access network device to instruct the core network device not to provide the second access network device Context information message.
- the above-mentioned sixth message may carry a reason why the terminal device requests to resume the connection, and the reason for requesting to resume the connection is obtained by the second access network device from the eighth message from the terminal device.
- the reason for requesting to restore the connection may be, for example, a radio access network notification area update (RNAU), or any of other active or passive service triggering reasons, which is not limited in the embodiment of the present application.
- the core network device may determine whether to provide the second access network device with the context information of the terminal device according to the reason why the terminal device requests to resume the connection.
- the context information of the terminal device and the security verification parameters used to verify the terminal device are sent to the core network device through the first access network device, so that the second access network device can receive the information from the core network device. Acquire the context information of the terminal device, thereby restoring the connection between the terminal device and the second access network device, avoiding that the second access network device cannot find the first access network device or the first access network device does not provide the terminal device.
- context information if the connection cannot be restored, the operation of the connection restoration mechanism of the terminal device can be guaranteed, and the influence of the mobility of the access network device on the connection restoration process of the terminal device can be reduced, thereby improving system performance.
- the second access network device has found the first access network device, but the first access network device does not store the context information of the terminal device, that is, the first access network device cannot provide the second access network device Context information of the terminal device.
- this embodiment may execute the following process after S201-S204:
- the second access network device sends a third message to the first access network device, where the third message is used to request context information of the terminal device; then, correspondingly, the first access network device receives the The third news.
- the third message may carry I-RNTI and authentication information.
- the third message also carries the cell ID of the cell of the second access network device where the terminal device is currently located.
- the third message also carries the second security verification parameter of the second access network device where the terminal device is currently located.
- the second security verification parameter includes the second C-RNTI allocated by the second access network device to the terminal device.
- the second security verification parameter further includes the second PCI of the terminal device in the cell of the second access network device.
- the first access network device may directly send a fourth message to the second access network device, where the fourth message indicates that the first access network device does not provide the second access network device with the Context information; for example, because the first access network device does not store the context information of the terminal device, security verification of the terminal device cannot be performed, and the first access network device cannot provide the context information to the second access network device.
- the second access network device receives the fourth message.
- the fourth message further indicates identification information of the core network device.
- the second access network device may obtain the identification information of the core network device from the fourth message, and send a sixth message to the core network device; then, correspondingly, the core network device receives the sixth message.
- S209 The core network device performs security verification on the terminal device according to the first security verification parameter.
- the core network device sends a seventh message to the second access network device, where the seventh message carries the context information, or the seventh message indicates the The core network device does not provide the context information to the second access network device; correspondingly, the second access network device receives the seventh message from the core network device.
- the second access network device may send a response message (not shown in FIG. 2) to the terminal device according to the seventh message.
- the second access network device finds the first access network device, and the first access network device stores the context information of the terminal device, but the first access network device is determined not to be the second access network
- the device provides the context information of the terminal device.
- this embodiment may execute the following process after S201-S204:
- S205 The second access network device sends a third message to the first access network device, where the third message is used to request context information of the terminal device; then, correspondingly, the first access network device receives the third message. news.
- S205 refer to Case 2, which will not be repeated here.
- the first access network device may use the first security verification parameter to perform security verification on the terminal device.
- the security verification performed by the first access network device refer to the description of the security verification performed by the core network device in Case 1, which is not repeated here.
- the first access network device may determine whether to provide the second access network device with the context of the terminal device.
- the foregoing third message may carry the reason why the terminal device requests to resume the connection, and the first access network device may determine whether to provide the second access network device with the context of the terminal device according to the reason why the terminal device requests to resume the connection. information.
- the first access network device determines not to provide the second access network device with the context information of the terminal device, and the first access network device may send a fourth message to the second access network device.
- the fourth message indicates that the first access network device does not provide the second access network device with the context information of the terminal device, and correspondingly, the second access network device receives the fourth message.
- the second access network device may send a response message (not shown in FIG. 2) to the terminal device according to the foregoing fourth message.
- the response message may indicate that the terminal device is refused to resume the connection, or in other words, the response message may instruct the terminal device to release the connection.
- the first access network device generates a response message, and sends a fourth message carrying the response message to the second access network device.
- the fourth message indicates that the first access network device does not access the second access network device.
- the network device provides context information of the terminal device, and the second access network device forwards the response message to the terminal device.
- the first access network device sends a fifth message to the core network device, where the fifth message carries the second security verification parameter to update the security verification parameter stored by the core network device; then, correspondingly, the The core network device receives the fifth message.
- the first access network device when the first access network device sends a fourth message to the second access network, the fourth message carries a response message, and the response message instructs the terminal device to release the connection and enter the deactivated state, the first access network device sends the core The network device sends the fifth message.
- S213 The core network device updates the security verification parameter from the first security verification parameter to the second security verification parameter.
- the first access network device In the case that the first access network device successfully authenticates the terminal device's security, but determines that the context information of the terminal device is not provided, the first access network device needs to update the stored security verification parameters and update the security verification parameters for the core network device . That is, the core network device needs to update the security verification parameter from the first security verification parameter to the second security verification parameter in order to perform security verification on the terminal device next time. Therefore, the above-mentioned second security verification parameter needs to be carried in the above-mentioned third message, which is sent by the second access network device to the first access network device, and then sent by the first access network device to the core network device through the fifth message .
- the core network device can obtain the latest security verification parameters for the next terminal device security verification, thereby ensuring that the security verification parameters saved by the terminal device and the core network device are consistent, avoiding security verification failures, and ensuring that the terminal device
- the operation of the connection recovery mechanism reduces the impact of the mobility of the access network equipment on the connection recovery process of the terminal equipment, thereby improving system performance.
- the second access network device finds the first access network device, the first access network device stores the context information of the terminal device, and the first access network device determines to provide the second access network device Context information of the terminal device.
- this embodiment may execute the following process after S201-S204:
- S205 The second access network device sends a third message to the first access network device, where the third message is used to request context information of the terminal device; then, correspondingly, the first access network device receives the third message. news.
- S205 refer to Case 2, which will not be repeated here.
- the first access network device may use the first security verification parameter to perform security verification on the terminal device.
- the security verification performed by the first access network device refer to the description of the security verification performed by the core network device in Case 1, which is not repeated here.
- the first access network device may determine whether to provide the second access network device with the context of the terminal device.
- the foregoing third message may carry the reason why the terminal device requests to resume the connection, and the first access network device may determine whether to provide the second access network device with the context of the terminal device according to the reason why the terminal device requests to resume the connection. information.
- the first access network device determines to provide the second access network device with the context information of the terminal device, and the first access network device may send a fourth message to the second access network device.
- the fourth message carries the context information of the terminal device, and correspondingly, the second access network device receives the fourth message.
- the second access network device may send a response message (not shown in FIG. 2) to the terminal device according to the foregoing fourth message.
- the response message may indicate that the terminal device is allowed to resume the connection, or the response message may indicate that the terminal device releases the connection.
- the second access network device sends a ninth message to the core network device, where the ninth message carries the second security verification parameter to update the security verification parameter stored by the core network device; then, correspondingly, the core network device receives the Ninth news. For example, when the second access network device sends a response message to the terminal device, the response message instructs the terminal device to release the connection and enter the deactivated state, the second access network device sends a ninth message to the core network device.
- the ninth message also carries context information of the terminal device, so that when the terminal device resumes the connection next time, if the new access network device that provides services for the terminal device cannot find the second access network device, the The new access network device can obtain the context information of the terminal device from the core network device.
- S213 The core network device updates the security verification parameter from the first security verification parameter to the second security verification parameter.
- S213 refer to Case 3, which will not be repeated here.
- the method further includes: the first access network device deletes the Context information of the terminal device.
- the method further includes: the core network device deletes Context information of the terminal device.
- the terminal device as the UE
- the first access network device as the LEO 1
- the second access network device as the LEO 2
- the core network device as the AMF
- FIG. 3 shows a schematic flowchart of another communication method 300 according to an embodiment of the present application.
- the method 300 can be applied to the system architecture 100 shown in FIG. 1, but the embodiment of the present application is not limited thereto.
- the method 300 is aimed at the scenario where LEO 1 stores the context information of the UE when the UE requests to resume the connection.
- the method includes:
- LEO 1 sends a first message to the UE, the first message is used to request the UE to enter the deactivated state, and LEO 1 saves the context information of the UE; then, correspondingly, the UE receives the first message and enters the deactivated state.
- LEO 1 sends a second message to the AMF, where the second message carries the context information of the UE and the first security verification parameter; then, correspondingly, the AMF receives the second message.
- the foregoing first security verification parameter may include the first C-RNTI allocated by LEO 1 for the UE.
- the foregoing first security verification parameter may also include the first PCI of the UE in the cell of LEO 1.
- the AMF may perform security verification on the UE according to the first security verification parameter when another access network device requests to obtain the context information of the UE next time.
- the AMF saves the context information of the UE and the first security verification parameter.
- S304 The UE sends an eighth message to LEO 2, where the eighth message is used to request to restore the connection; then, correspondingly, LEO 2 receives the eighth message.
- LEO 2 can find LEO 1, and send a third message to LEO 1, where the third message is used to request the context of the terminal device; then, correspondingly, LEO 1 receives the third message.
- the foregoing third message may include a second security verification parameter, and the second security verification parameter includes the second C-RNTI allocated by the LEO 2 for the UE.
- the second security verification parameter may also include the second PCI of the cell in which the UE initiates the access or recovery request in LEO 2.
- LEO 1 performs security verification on the terminal device.
- LEO 1 sends a fourth message to LEO 2.
- LEO 1 determines whether to provide the context information of the UE to LEO 2. In the embodiment of the present application, LEO 1 determines not to provide UE context information to LEO 2, and this LEO 1 sends a fourth message (also referred to as a rejection response) to LEO 2, indicating that it does not provide UE context information. LEO1 generates a response message, and the first message carries the response message. The response message is used to instruct the UE to release the RRC connection.
- a fourth message also referred to as a rejection response
- LEO 1 sends a fifth message to the AMF, where the fifth message carries the second security verification parameter.
- the AMF receives the fifth message.
- the foregoing second security verification parameter may include the second C-RNTI allocated by LEO 2 for the UE and the second PCI of the UE in the cell of LEO 2.
- the AMF updates the security verification parameter from the first security verification parameter to the second security verification parameter.
- LEO 2 sends a response message to the UE after receiving the fourth message sent by LEO 1.
- the response message is used to release the RRC connection of the UE; correspondingly, the UE receives the response message.
- the response message can be used to instruct the UE to enter the idle state or the deactivated state. As an example, in this process, the response message instructs the UE to enter the deactivated state.
- the context information of the UE and the security verification parameters used to verify the UE are sent to the AMF through the LEO 1, but the LEO 1 still retains the context of the UE. If the UE initiates a recovery request in LEO 2, LEO 2 requests LEO 1 to obtain the context of the UE. Optionally, LEO 2 may send new security verification parameters to LEO 1. If LEO 1 successfully authenticates the UE, but LEO 1 does not provide the UE context to LEO 2, LEO 1 needs to update the stored security verification parameters and send the updated security verification parameters to the AMF. The updated security verification parameters are used for the next security verification of the terminal device to improve the security of the system.
- FIG. 4 shows a schematic flowchart of another communication method 400 according to an embodiment of the present application.
- the method 400 can be applied to the system architecture 100 shown in FIG. 1, but the embodiment of the present application is not limited thereto.
- the method 400 is aimed at a scenario where the LEO 1 does not store the context information of the UE when the UE requests to resume the connection.
- the method includes:
- LEO 1 sends a first message to the UE, the first message is used to request the UE to enter the deactivated state, and LEO 1 saves the context information of the UE; then, correspondingly, the UE receives the first message and enters the deactivated state.
- LEO 1 sends a second message to the AMF, where the second message carries the context information of the UE and the first security verification parameter; then, correspondingly, the AMF receives the second message.
- the foregoing first security verification parameter may include the first C-RNTI allocated by LEO 1 for the UE.
- the foregoing first security verification parameter may also include the first PCI of the UE in the cell of LEO 1.
- the AMF may perform security verification on the UE according to the first security verification parameter when another access network device requests to obtain the context information of the UE next time.
- the AMF saves the context information of the UE and the first security verification parameter.
- S404 The UE sends an eighth message to LEO 2, where the eighth message is used to request to restore the connection; then, correspondingly, LEO 2 receives the eighth message.
- LEO 2 can find LEO 1, and send a third message to LEO 1, where the third message is used to request the context of the terminal device; then, correspondingly, LEO 1 receives the third message.
- the foregoing third message may include the second security verification parameter, and the second security verification parameter includes the second C-RNTI allocated by the LEO 2 for the UE.
- the second security verification parameter may also include the second PCI of the cell in which the UE initiates an access or recovery request in LEO 2.
- LEO 1 sends a fourth message to LEO 2.
- the fourth message may carry the AMF identifier.
- the fourth message may indicate that the context information of the UE is not provided to LEO 2.
- LEO 2 receives the fourth message.
- LEO 1 does not store the context information of the UE.
- the LEO 1 may delete the context information of the UE after S403.
- LEO 2 sends a sixth message to the AMF, where the sixth message is used to request context information of the UE; then, correspondingly, the AMF receives the sixth message.
- LEO 2 may determine the AMF for sending the sixth message according to the AMF identifier in the fourth message.
- the aforementioned sixth message may carry a second security verification parameter, which is used by the AMF to perform security verification on the UE next time.
- the second security verification parameter includes the second cell radio network temporary identifier C-RNTI allocated by the second access network device to the terminal device.
- the second security verification parameter may also include the second physical cell identifier PCI of the cell in which the terminal device initiates the access or recovery request of the second access network device.
- the AMF performs security verification on the UE according to the first security verification parameter stored above.
- the AMF sends a seventh message to LEO 2, the seventh message carries the context information of the UE, or the seventh message indicates that the AMF does not provide the context information of the UE to the LEO 2; then correspondingly , LEO 2 receives the seventh message from AMF. If the AMF does not provide the context information of the UE to the LEO 2, the AMF can generate a response message, and send the response message to the LEO 2 with the response message in the seventh message.
- the AMF needs to save the second security verification parameter carried in the sixth message, and update the security verification parameter from the first security verification parameter to the second security verification parameter.
- Safety verification parameters to improve the security of the system.
- LEO 2 sends a response message to the UE.
- the response message can be used to restore the connection of the UE, and can also be used to release the connection of the UE. Specifically, it can be determined by LEO2. If the above seventh message indicates that the AMF does not provide the context information of the UE, the response message is used to release the RRC connection of the UE; correspondingly, the UE receives the response message.
- the response message can be used to instruct the UE to enter the idle state or the deactivated state. As an example, in this process, the response message instructs the UE to enter the deactivated state. .
- LEO2 may not perform S405 and S406.
- LEO2 defaults that LEO1 has deleted the UE context, so it only requests the UE context from the AMF. Specifically, LEO2 can request the UE context from the AMF to which it is connected.
- the context information of the UE and the security verification parameters used to verify the UE are sent to the AMF through LEO 1, and then LEO 1 deletes the context of the UE, so that LEO 2 can obtain the context information of the UE from the AMF In this way, the connection between the UE and LEO 2 is restored, avoiding the situation that the connection cannot be restored when the second access network device cannot find the first access network device or the first access network device does not provide the context information of the terminal device , Can ensure the operation of the connection recovery mechanism of the terminal device, reduce the influence of the mobility of the access network device on the connection recovery process of the terminal device, thereby improving the system performance.
- Fig. 5 is a schematic block diagram of a communication device provided by an embodiment of the present application.
- the apparatus 500 for data transmission can implement various steps or processes performed by the first access network device corresponding to the above method embodiments.
- the apparatus 500 can be the first access network device or be configured in the first access network device. Chip or circuit in access network equipment.
- the apparatus 500 may include: a sending unit 510 and a receiving unit 520.
- the sending unit 510 is configured to: send a first message to the terminal device, where the first message is used to instruct the terminal device to enter the deactivated state; and send a second message to the core network device, the second message carrying The context information of the terminal device and a first security verification parameter, where the first security verification parameter is used to perform security verification on the terminal device;
- the receiving unit 520 is used to: receive a third message from the second access network device , The third message is used to request the context information of the terminal device;
- the sending unit 510 is also used to: send a fourth message to the second access network device, the fourth message indicating the first The access network device does not provide the context information to the second access network device.
- the fourth message is also used to indicate identification information of the core network device.
- the first access network device stores context information of the terminal device
- the apparatus further includes: a processing unit configured to perform security verification on the terminal device according to the first security verification parameter
- the sending unit 510 is specifically configured to: in the case where the security verification is passed, if the communication apparatus determines not to provide the context information to the second access network device, to the second access network device The device sends the fourth message.
- the third message carries a second security verification parameter of the terminal device
- the second security verification parameter is used to perform security verification on the terminal device
- the sending unit 510 is specifically configured to:
- the core network device sends a fifth message, where the fifth message carries the second security verification parameter to update the security verification parameter stored by the core network device.
- the second security verification parameter includes the second cell radio network temporary identifier C-RNTI allocated by the second access network device to the terminal device and the terminal device is in the second access network The second physical cell identification PCI of the cell of the device.
- the apparatus further includes: a processing unit configured to delete the context information of the terminal device.
- the first security verification parameter includes the first C-RNTI allocated by the first access network device to the terminal device and the first C-RNTI of the terminal device in the cell of the first access network device.
- One PCI One PCI.
- the device 500 here is embodied in the form of a functional unit.
- the term "unit” here can refer to application specific integrated circuits (ASICs), electronic circuits, processors used to execute one or more software or firmware programs (such as shared processors, proprietary processors, or groups). Processor, etc.) and memory, merged logic circuits, and/or other suitable components that support the described functions.
- ASICs application specific integrated circuits
- the apparatus 500 may be specifically the first access network device in the foregoing embodiment, and the apparatus 500 may be used to execute the method corresponding to the first access network device in the foregoing embodiment. In order to avoid repetition, the various processes and/or steps of, will not be repeated here.
- FIG. 6 is a schematic block diagram of another communication device provided by an embodiment of the present application.
- the device 600 for data transmission can implement various steps or processes corresponding to the core network equipment in the above method embodiment.
- the device 600 can be a core network device, or a chip or circuit configured in the core network device.
- the device 600 may include: a receiving unit 610 and a processing unit 620.
- the receiving unit 610 is configured to: receive a second message from the first access network device, the second message carrying context information of the terminal device and a first security verification parameter, and the first security verification parameter is used to The terminal device performs security verification; the processing unit 620 is configured to save the context information and the first security verification parameter.
- the receiving unit 610 is further configured to: receive a sixth message from the second access network device, where the sixth message is used to request context information of the terminal device; the processing unit 620 is further configured to : Perform security verification on the terminal device according to the first security verification parameter; the device further includes: a sending unit, configured to send to the second access network device when the security verification is passed A seventh message, where the seventh message carries the context information, or the seventh message indicates that the core network device does not provide the context information to the second access network device.
- the sixth message carries a second security verification parameter of the terminal device, and the second security verification parameter is used to perform security verification on the terminal device, and the processing unit 620 is further configured to: The verification parameter is updated from the first security verification parameter to the second security verification parameter.
- the second security verification parameter includes the second cell radio network temporary identifier C-RNTI allocated by the second access network device to the terminal device and the terminal device is in the second access network The second physical cell identification PCI of the cell of the device.
- the processing unit 620 is further configured to delete the context information of the terminal device.
- the first security verification parameter includes the first C-RNTI allocated by the first access network device to the terminal device and the first C-RNTI of the terminal device in the cell of the first access network device.
- One PCI One PCI.
- the device 600 here is embodied in the form of a functional unit.
- the term "unit” here can refer to application specific integrated circuits (ASICs), electronic circuits, processors used to execute one or more software or firmware programs (such as shared processors, proprietary processors, or groups). Processor, etc.) and memory, merged logic circuits, and/or other suitable components that support the described functions.
- ASICs application specific integrated circuits
- the apparatus 600 may be specifically the core network equipment in the above-mentioned embodiment, and the apparatus 500 may be used to execute various processes and/or processes corresponding to the core network equipment in the above-mentioned method embodiment. Steps, in order to avoid repetition, will not be repeated here.
- FIG. 7 is a schematic block diagram of another communication device provided by an embodiment of the present application.
- the apparatus 700 for data transmission can implement various steps or processes performed by the second access network device corresponding to the above method embodiments.
- the apparatus 700 can be the second access network device, or is configured to be configured in the second access network device.
- the apparatus 700 may include: a receiving unit 710 and a sending unit 720.
- the receiving unit 710 is configured to receive an eighth message from the terminal device, the eighth message is used to request to restore the connection; the sending unit 720 is configured to: send a sixth message to the core network device, the sixth message is Request the context information of the terminal device; the receiving unit 710 is further configured to: receive a seventh message from the core network device, the seventh message carrying the context information, or the seventh message indicating the The core network device does not provide the context information to the second access network device.
- the sending unit 720 is further configured to: according to the eighth message, send a third message to the first access network device, where the third message is used for Request the context information of the terminal device; the receiving unit 710 is further configured to: receive a fourth message from the first access network device, the fourth message instructing the first access network device not to The second access network device provides the context information, and the fourth message also indicates the identification information of the core network device; the sending unit 720 is further configured to: according to the identification information of the core network device, The core network device sends the sixth message.
- the fifth message carries the second security verification parameter of the terminal device, so that the core network device updates the security verification parameter from the first security verification parameter to the second security verification parameter, and the second security verification parameter
- the verification parameter is used to perform security verification on the terminal device.
- the first security verification parameter includes the first cell radio network temporary identifier C-RNTI allocated by the first access network device to the terminal device, and the terminal device is in the first access network The first physical cell identifier PCI of the cell of the device; the second security verification parameter includes the second C-RNTI allocated by the second access network device for the terminal device and the terminal device in the second interface The second PCI of the cell of the connected device.
- the device 700 here is embodied in the form of a functional unit.
- the term "unit” here can refer to application specific integrated circuits (ASICs), electronic circuits, processors used to execute one or more software or firmware programs (such as shared processors, proprietary processors, or groups). Processor, etc.) and memory, merged logic circuits, and/or other suitable components that support the described functions.
- ASICs application specific integrated circuits
- the apparatus 700 may be specifically the second access network device in the foregoing embodiment, and the apparatus 500 may be used to execute the second access network device in the foregoing method embodiment. In order to avoid repetition, the various processes and/or steps of, will not be repeated here.
- the aforementioned device 500 has the function of realizing the corresponding steps performed by the first access network device in the aforementioned method; the aforementioned device 600 has the function of realizing corresponding steps executed by the core network device in the aforementioned method; the aforementioned device 700 has the function of realizing the second access network device in the aforementioned method.
- the function can be realized by hardware, or by hardware executing corresponding software.
- the hardware or software includes one or more modules corresponding to the above-mentioned functions.
- the foregoing sending unit may be replaced by a transmitter, and the foregoing receiving unit may be replaced by a receiver, respectively performing the receiving and sending operations and related processing operations in each method embodiment.
- the sending unit and the receiving unit can be collectively referred to as a transceiver unit, and accordingly, the receiver and transmitter can be collectively referred to as a transceiver.
- the processing unit in the above embodiments may be implemented by a processor or processor-related circuits, and the receiving unit and the sending unit may be implemented by a transceiver or a transceiver-related circuit or interface circuit.
- a storage unit may be further included, and the storage unit is used to store a computer program, and the processing unit may call and run the computer program from the storage unit, so that the device 500 executes the foregoing method embodiments.
- the method of the first access network device in the first access network device, or the apparatus 600 is caused to execute the method of the core network device in the foregoing method embodiment, or the apparatus 700 is caused to execute the method of the second access network device in the foregoing method embodiment.
- the units in the above embodiments may also be referred to as modules or circuits or components.
- FIG. 8 is a schematic structural diagram of a network device 3000 provided by an embodiment of the present application.
- the network device 3000 may be a schematic structural diagram of an access network device, or the network device 3000 may be a schematic structural diagram of a core network device.
- the network device 3000 can be applied to the communication system shown in FIG. 1 to implement the steps or processes performed by the first access network device in the foregoing method embodiments, or implement the steps or processes performed by the core network device in the foregoing method embodiments , Or to implement the steps or processes executed by the second access network device in the foregoing method embodiments, which will not be repeated here.
- the network device 3000 may include one or more radio frequency units, such as a remote radio unit (RRU) 3100 and one or more baseband units (BBU) 3200, among which, BBU 3200 It may also be called a digital unit (DU), and the RRU 3100 may be called a transceiver unit, which corresponds to the receiving unit and the sending unit in FIGS. 5-7.
- the RRU 3100 may also be called a transceiver, a transceiver circuit, or a transceiver, etc., and it may include at least one antenna 3101 and a radio frequency unit 3102.
- the RRU 3100 may include a receiving unit and a sending unit.
- the receiving unit may correspond to a receiver (or receiver or receiving circuit), and the sending unit may correspond to a transmitter (or transmitter or transmitting circuit).
- the RRU 3100 part is mainly used for sending and receiving of radio frequency signals and conversion of radio frequency signals and baseband signals, for example, for sending instruction information to terminal equipment.
- the 3200 part of the BBU is mainly used for baseband processing, control of network equipment, and so on.
- the RRU 3100 and the BBU 3200 may be physically set together, or may be physically separated, such as a distributed base station.
- the BBU 3200 is the control center of the network equipment, and may also be referred to as a processing unit, which may correspond to the processing unit in the foregoing device, and is mainly used to complete baseband processing functions, such as channel coding, multiplexing, modulation, and spreading.
- the BBU 3200 may be used to control the network device to execute the operation process of the first access network device, the second access network device, or the core network device in the foregoing method embodiment, for example, to generate the foregoing handover condition, or send the handover condition Wait.
- the BBU 3200 may be composed of one or more single boards, and multiple single boards may jointly support a radio access network (such as an LTE network) of a single access standard, or support different access standards. Wireless access network (such as LTE network, 5G network or other networks).
- the BBU 3200 also includes a memory 3201 and a processor 3202.
- the memory 3201 is used to store necessary instructions and data.
- the processor 3202 is configured to control the network device to perform necessary actions, for example, to control the network device to execute the operation process of the first access network device, the second access network device, or the core network device in the foregoing method embodiment.
- the memory 3201 and the processor 3202 may serve one or more single boards. In other words, the memory and the processor can be set separately on each board. It can also be that multiple boards share the same memory and processor. In addition, necessary circuits can be provided on each board.
- the network device 3000 shown in FIG. 8 can implement each process involving the first access network device, the second access network device, or the core network device in the method embodiments of FIGS. 2 to 4.
- the operations and/or functions of each module in the network device 3000 are respectively for implementing the corresponding processes in the foregoing method embodiments.
- the above-mentioned BBU 3200 can be used to perform the actions described in the previous method embodiment by the first access network device, the second access network device or the core network device internally, and the RRU 3100 can be used to perform the actions described in the previous method embodiment
- the first access network device, the second access network device, or the core network device sends or receives actions to the terminal device.
- the description in the previous method embodiment please refer to the description in the previous method embodiment, which will not be repeated here.
- the embodiment of the present application also provides a processing device, including a processor and an interface.
- the processor may be used to execute the method in the foregoing method embodiment.
- the processing device may be a chip.
- the processing device may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), or It is a central processor unit (CPU), it can also be a network processor (NP), it can also be a digital signal processing circuit (digital signal processor, DSP), or it can be a microcontroller (microcontroller unit). , MCU), it can also be a programmable logic device (PLD) or other integrated chips.
- FPGA field programmable gate array
- ASIC application specific integrated circuit
- SoC system on chip
- CPU central processor unit
- NP network processor
- DSP digital signal processing circuit
- microcontroller unit microcontroller unit
- MCU programmable logic device
- PLD programmable logic device
- each step of the above method can be completed by an integrated logic circuit of hardware in the processor or instructions in the form of software.
- the steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor.
- the software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
- the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware. To avoid repetition, it will not be described in detail here.
- the processor in the embodiment of the present application may be an integrated circuit chip with signal processing capability.
- the steps of the foregoing method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in the form of software.
- the above-mentioned processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components .
- DSP digital signal processor
- ASIC application specific integrated circuit
- FPGA field programmable gate array
- the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
- the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
- the steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor.
- the software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
- the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
- the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
- the non-volatile memory can be read-only memory (ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), and electrically available Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
- the volatile memory may be random access memory (RAM), which is used as an external cache.
- RAM random access memory
- static random access memory static random access memory
- dynamic RAM dynamic RAM
- DRAM dynamic random access memory
- synchronous dynamic random access memory synchronous DRAM, SDRAM
- double data rate synchronous dynamic random access memory double data rate SDRAM, DDR SDRAM
- enhanced synchronous dynamic random access memory enhanced SDRAM, ESDRAM
- synchronous connection dynamic random access memory serial DRAM, SLDRAM
- direct rambus RAM direct rambus RAM
- the present application also provides a computer program product, the computer program product includes: computer program code, when the computer program code runs on a computer, the computer executes any of the above embodiments The method corresponding to any network element.
- the present application also provides a computer-readable medium that stores program code, and when the program code runs on a computer, the computer executes the steps shown in FIGS. 2 to 4 The method corresponding to any one of the network elements in any one of the embodiments is shown.
- the present application also provides a system, which includes the aforementioned one or more terminal devices, one or more access network devices, and one or more core network devices.
- the computer may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
- software it can be implemented in the form of a computer program product in whole or in part.
- the computer program product includes one or more computer instructions.
- the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
- the computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
- the computer instructions may be transmitted from a website, computer, server, or data center.
- the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrated with one or more available media.
- the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a high-density digital video disc (digital video disc, DVD)), or a semiconductor medium (for example, a solid state disk (solid state disc), SSD)) etc.
- the network equipment in the foregoing device embodiments corresponds to the network equipment or terminal equipment in the terminal equipment and method embodiments, and the corresponding modules or units execute the corresponding steps.
- the communication unit transmits the receiving or sending in the method embodiments.
- other steps can be executed by the processing unit (processor).
- the processing unit processor
- the functions of specific units refer to the corresponding method embodiments. Among them, there may be one or more processors.
- components may be, but is not limited to, a process, a processor, an object, an executable file, an execution thread, a program, and/or a computer running on a processor.
- the application running on the computing device and the computing device can be components.
- One or more components may reside in processes and/or threads of execution, and components may be located on one computer and/or distributed between two or more computers.
- these components can be executed from various computer readable media having various data structures stored thereon.
- the components may communicate through local and/or remote processes, for example, based on signals having one or more data packets (e.g., data from components with a local system, a distributed system, and/or a network).
- At least one refers to one or more, and “multiple” refers to two or more.
- And/or describes the association relationship of the associated object, indicating that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone, where A, B can be singular or plural.
- the character “/” generally indicates that the associated objects before and after are in an “or” relationship.
- "The following at least one item (a)” or similar expressions refers to any combination of these items, including any combination of a single item (a) or a plurality of items (a).
- At least one of a, b, or c can represent: a, b, c, a-b, a-c, b-c or a-b-c, where a, b, and c can be single or multiple.
- the disclosed system, device, and method may be implemented in other ways.
- the device embodiments described above are merely illustrative, for example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented.
- the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
- the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
- the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
- the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
- the technical solution of the present application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the method described in each embodiment of the present application.
- the aforementioned storage media include: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disks or optical disks and other media that can store program codes. .
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本申请提供了一种通信方法和通信装置,能够保证终端设备的连接恢复机制的运行,减少接入网设备的移动性对终端设备的连接恢复流程的影响。该通信方法包括:第一接入网设备向终端设备发送第一消息,该第一消息用于指示该终端设备进入去激活态;该第一接入网设备向核心网设备发送第二消息,该第二消息携带该终端设备的上下文信息和第一安全验证参数,该第一安全验证参数用于对该终端设备进行安全验证;该第一接入网设备接收来自第二接入网设备的第三消息,该第三消息用于请求该终端设备的上下文信息;该第一接入网设备向该第二接入网设备发送第四消息,该第四消息用于指示该第一接入网设备不向该第二接入网设备提供该上下文信息。
Description
本申请涉及通信领域,特别涉及通信领域中的一种通信方法和通信装置。
终端设备的无线资源控制(radio resource control,RRC)状态包括连接态(RRC_CONNECTED)、去激活态(RRC_INACTIVE)和空闲态(RRC_IDLE)。当终端设备处于连接态时,该终端设备与接入网设备以及核心网设备都已建立链路,当有数据到达网络时,核心网设备和接入网设备可以直接将数据传送至该终端设备。当终端设备处于去激活态时,说明该终端设备之前和接入网设备以及核心网设备建立过链路,但是该终端设备与接入网设备之间的链路被释放了。虽然链路被释放了,但是接入网设备需要保存终端设备的上下文,当有数据需要传输时,接入网设备可以根据终端设备的上下文快速恢复被释放的这段链路。当终端设备处于空闲态时,该终端设备与接入网设备和核心网设备之间都没有链路,当有数据需要传输时,需要建立终端设备到接入网设备及核心网设备的链路。
由上可知,去激活态只能在终端设备处于连接态的情况下通过RRC连接释放消息转变,在终端设备从连接态释放到去激活态时,为该终端设备服务的接入网设备(可以称为锚点接入网设备或源接入网设备)会保存终端设备的上下文,并为该终端设备分配一个标识,以此标识存储终端设备的上下文。当终端设备后续发起RRC连接恢复流程时,需携带上述标识给当前为终端设备服务的接入网设备(可以称为目标接入网设备),获取该终端设备的上下文。因为终端设备具有移动性,上述目标接入网设备一般与锚点接入网设备是不同的设备,该目标接入网设备需要根据上述标识从锚点接入网设备处获取该终端设备的上下文。
考虑到在一些场景(例如非陆地网络(non-terrestrial network,NTN))中,接入网设备的运动速度较快,例如,每隔1分钟至2分钟,终端设备就需要更换一次服务小区(即更换目标接入网设备)。而终端设备的上下文仅存储在锚点接入网设备,若处于去激活态的终端设备请求恢复RRC连接,目标接入网设备很难找到锚点接入网设备,从而向锚点接入网设备获取终端设备的上下文信息。因此,如何保证终端设备的连接恢复机制的运行成为一项亟待解决的问题。
发明内容
本申请提供一种通信方法和通信装置,能够保证终端设备的连接恢复机制的运行,减少接入网设备的移动性对终端设备的连接恢复流程的影响,从而提高***性能。
第一方面,提供了一种通信方法,包括:第一接入网设备向终端设备发送第一消息,所述第一消息用于指示所述终端设备进入去激活态;所述第一接入网设备向核心网设备发 送第二消息,所述第二消息携带所述终端设备的上下文信息和第一安全验证参数,所述第一安全验证参数用于对所述终端设备进行安全验证;所述第一接入网设备接收来自第二接入网设备的第三消息,所述第三消息用于请求所述终端设备的上下文信息;所述第一接入网设备向所述第二接入网设备发送第四消息,所述第四消息指示所述第一接入网设备不向所述第二接入网设备提供所述上下文信息。
本申请实施例的通信方法,通过第一接入网设备将终端设备的上下文信息和用于验证终端设备的安全验证参数发送给核心网设备,使得第二接入网设备可以从核心网设备处获取终端设备的上下文信息,从而恢复终端设备和第二接入网设备的连接,避免了在第二接入网设备无法找到第一接入网设备或者第一接入网设备不提供终端设备的上下文信息的情况下,无法恢复连接的情况,能够保证终端设备的连接恢复机制的运行,减少接入网设备的移动性对终端设备的连接恢复流程的影响,从而提高***性能。
终端设备的上下文信息也可以称为终端设备的上下文、或者终端设备的上下文数据。终端设备的上下文信息可以包括PDU会话上下文、安全密钥、终端设备的无线能力和终端设备的安全能力等信息。
结合第一方面,在第一方面的某些实现方式中,所述第四消息还用于指示所述核心网设备的标识信息。
结合第一方面,在第一方面的某些实现方式中,所述第一接入网设备存储有所述终端设备的上下文信息,所述方法还包括:所述第一接入网设备根据所述第一安全验证参数,对所述终端设备进行安全验证;所述第一接入网设备根据所述第三消息,向所述第二接入网设备发送第四消息,包括:在所述安全验证通过的情况下,若所述第一接入网设备确定不向所述第二接入网设备提供所述上下文信息,所述第一接入网设备向所述第二接入网设备发送所述第四消息。
示例性地,上述第三消息中可以携带终端设备请求恢复连接的原因,第一接入网设备可以根据该终端设备请求恢复连接的原因,确定是否向第二接入网设备提供终端设备的上下文信息。该请求恢复连接的原因可以例如是无线接入网通知区更新(ran notification area update,RNAU)、或者其它主动或被动业务触发的原因的任一种,本申请实施例对此不作限定。
结合第一方面,在第一方面的某些实现方式中,所述第三消息携带所述终端设备的第二安全验证参数,所述第二安全验证参数用于对所述终端设备进行安全验证,所述方法还包括:所述第一接入网设备向所述核心网设备发送第五消息,所述第五消息携带所述第二安全验证参数,以更新所述核心网设备存储的安全验证参数。
在第一接入网设备对终端设备安全验证成功,但确定不提供终端设备的上下文信息的情况下,第一接入网设备需要更新存储的安全验证参数,并为核心网设备更新安全验证参数。即核心网设备需要将安全验证参数从第一安全验证参数更新为第二安全验证参数,以便下一次对终端设备进行安全验证。因此,上述第二安全验证参数需要携带在上述第三消息中,由第二接入网设备发送给第一接入网设备,再由第一接入网设备通过第五消息发送给核心网设备。
这样,核心网设备可以获取到最新的安全验证参数,以便进行下一次终端设备的安全验证,从而保证终端设备和核心网设备所保存的安全验证参数保持一致,避免安全验证失 败,能够保证终端设备的连接恢复机制的运行,减少接入网设备的移动性对终端设备的连接恢复流程的影响,从而提高***性能。
结合第一方面,在第一方面的某些实现方式中,所述第二安全验证参数包括所述第二接入网设备为所述终端设备分配的第二小区无线网络临时标识C-RNTI和所述终端设备在所述第二接入网设备的小区的第二物理小区标识PCI。
结合第一方面,在第一方面的某些实现方式中,在所述第一接入网设备向核心网设备发送第二消息之后,所述方法还包括:所述第一接入网设备删除所述终端设备的上下文信息。
结合第一方面,在第一方面的某些实现方式中,所述第一安全验证参数包括所述第一接入网设备为所述终端设备分配的第一C-RNTI和所述终端设备在所述第一接入网设备的小区的第一PCI。
第二方面,提供了另一种通信方法,包括:核心网设备接收来自第一接入网设备的第二消息,所述第二消息携带终端设备的上下文信息和第一安全验证参数,所述第一安全验证参数用于对所述终端设备进行安全验证;所述核心网设备保存所述上下文信息和所述第一安全验证参数。
结合第二方面,在第二方面的某些实现方式中,所述方法还包括:所述核心网设备接收来自第二接入网设备的第六消息,所述第六消息用于请求所述终端设备的上下文信息;所述核心网设备根据所述第一安全验证参数,对所述终端设备进行安全验证;在所述安全验证通过的情况下,所述核心网设备向所述第二接入网设备发送第七消息,所述第七消息携带所述上下文信息,或者,所述第七消息指示所述核心网设备不向所述第二接入网设备提供所述上下文信息。
结合第二方面,在第二方面的某些实现方式中,所述第六消息携带所述终端设备的第二安全验证参数,所述第二安全验证参数用于对所述终端设备进行安全验证,所述方法还包括:所述核心网设备将安全验证参数从所述第一安全验证参数更新为所述第二安全验证参数。
结合第二方面,在第二方面的某些实现方式中,所述第二安全验证参数包括所述第二接入网设备为所述终端设备分配的第二小区无线网络临时标识C-RNTI和所述终端设备在所述第二接入网设备的小区的第二物理小区标识PCI。
结合第二方面,在第二方面的某些实现方式中,在所述核心网设备向所述第二接入网设备发送所述上下文信息的情况下,所述方法还包括:所述核心网设备删除所述终端设备的上下文信息。
结合第二方面,在第二方面的某些实现方式中,所述第一安全验证参数包括所述第一接入网设备为所述终端设备分配的第一C-RNTI和所述终端设备在所述第一接入网设备的小区的第一PCI。
第三方面,提供了另一种通信方法,包括:第二接入网设备接收来自终端设备的第八消息,所述第八消息用于请求恢复连接;所述第二接入网设备向核心网设备发送第六消息,所述第六消息用于请求所述终端设备的上下文信息;所述第二接入网设备接收来自所述核心网设备的第七消息,所述第七消息携带所述上下文信息,或者,所述第七消息指示所述核心网设备不向所述第二接入网设备提供所述上下文信息。
结合第三方面,在第三方面的某些实现方式中,在所述第二接入网设备向核心网设备发送第六消息之前,所述方法还包括:所述第二接入网设备根据所述第八消息,向第一接入网设备发送第三消息,所述第三消息用于请求所述终端设备的上下文信息;所述第二接入网设备接收来自所述第一接入网设备的第四消息,所述第四消息指示所述第一接入网设备不向所述第二接入网设备提供所述上下文信息,且所述第四消息还指示所述核心网设备的标识信息;所述第二接入网设备向核心网设备发送第六消息,包括:所述第二接入网设备根据所述核心网设备的标识信息,向所述核心网设备发送所述第六消息。
结合第三方面,在第三方面的某些实现方式中,所述第五消息携带所述终端设备的第二安全验证参数,以便所述核心网设备将安全验证参数从第一安全验证参数更新为第二安全验证参数,所述第二安全验证参数用于对所述终端设备进行安全验证。
结合第三方面,在第三方面的某些实现方式中,所述第一安全验证参数包括所述第一接入网设备为所述终端设备分配的第一小区无线网络临时标识C-RNTI和所述终端设备在所述第一接入网设备的小区的第一物理小区标识PCI;所述第二安全验证参数包括所述第二接入网设备为所述终端设备分配的第二C-RNTI和所述终端设备在所述第二接入网设备的小区的第二PCI。
第四方面,提供了一种通信装置,用于执行上述各方面中任一种可能的实现方式中的方法。具体地,该装置包括用于执行上述各方面中任一种可能的实现方式中的方法的单元。
第五方面,提供了另一种通信装置,包括处理器,该处理器与存储器耦合,可用于执行存储器中的指令,以实现上述各方面中任一种可能实现方式中的方法。可选地,该通信装置还包括存储器。可选地,该通信装置还包括通信接口,处理器与通信接口耦合。
在一种实现方式中,该通信装置为接入网设备。当该通信装置为接入网设备时,所述通信接口可以是收发器,或,输入/输出接口。
在另一种实现方式中,该通信装置为配置于接入网设备中的芯片。当该通信装置为配置于终端设备中的芯片时,所述通信接口可以是输入/输出接口。
在一种实现方式中,该通信装置为核心网设备。当该通信装置为核心网设备时,所述通信接口可以是收发器,或,输入/输出接口。
在另一种实现方式中,该通信装置为配置于核心网设备中的芯片。当该通信装置为配置于核心网设备中的芯片时,所述通信接口可以是输入/输出接口。
在一种实现方式中,该通信装置为终端设备。当该通信装置为终端设备时,所述通信接口可以是收发器,或,输入/输出接口。
在另一种实现方式中,该通信装置为配置于终端设备中的芯片。当该通信装置为配置于终端设备中的芯片时,所述通信接口可以是输入/输出接口。
第六方面,提供了一种处理器,包括:输入电路、输出电路和处理电路。所述处理电路用于通过所述输入电路接收信号,并通过所述输出电路发射信号,使得所述处理器执行上述各方面中任一种可能实现方式中的方法。
在具体实现过程中,上述处理器可以为芯片,输入电路可以为输入管脚,输出电路可以为输出管脚,处理电路可以为晶体管、门电路、触发器和各种逻辑电路等。输入电路所接收的输入的信号可以是由例如但不限于接收器接收并输入的,输出电路所输出的信号可以是例如但不限于输出给发射器并由发射器发射的,且输入电路和输出电路可以是同一电 路,该电路在不同的时刻分别用作输入电路和输出电路。本申请实施例对处理器及各种电路的具体实现方式不做限定。
第七方面,提供了一种处理装置,包括处理器和存储器。该处理器用于读取存储器中存储的指令,并可通过接收器接收信号,通过发射器发射信号,以执行上述各方面中任一种可能实现方式中的方法。
可选地,所述处理器为一个或多个,所述存储器为一个或多个。
可选地,所述存储器可以与所述处理器集成在一起,或者所述存储器与处理器分离设置。
在具体实现过程中,存储器可以为非瞬时性(non-transitory)存储器,例如只读存储器(read only memory,ROM),其可以与处理器集成在同一块芯片上,也可以分别设置在不同的芯片上,本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
应理解,相关的数据交互过程例如发送指示信息可以为从处理器输出指示信息的过程,接收能力信息可以为处理器接收输入能力信息的过程。具体地,处理输出的数据可以输出给发射器,处理器接收的输入数据可以来自接收器。其中,发射器和接收器可以统称为收发器。
上述第七方面中的处理装置可以是一个芯片,该处理器可以通过硬件来实现也可以通过软件来实现,当通过硬件实现时,该处理器可以是逻辑电路、集成电路等;当通过软件来实现时,该处理器可以是一个通用处理器,通过读取存储器中存储的软件代码来实现,该存储器可以集成在处理器中,可以位于该处理器之外,独立存在。
第八方面,提供了一种计算机程序产品,所述计算机程序产品包括:计算机程序(也可以称为代码,或指令),当所述计算机程序被运行时,使得计算机执行上述各方面中任一种可能实现方式中的方法。
第九方面,提供了一种计算机可读介质,所述计算机可读介质存储有计算机程序(也可以称为代码,或指令)当其在计算机上运行时,使得计算机执行上述各方面中任一种可能实现方式中的方法。
第十方面,提供了一种通信***,包括前述的终端设备、接入网设备以及核心网设备。
图1示出了本申请实施例的通信***的示意图。
图2示出了本申请实施例的一种通信方法的示意性流程图。
图3示出了本申请实施例的另一种通信方法的示意性流程图。
图4示出了本申请实施例的另一种通信方法的示意性流程图。
图5示出了本申请实施例的通信装置的示意性框图。
图6示出了本申请实施例的另一通信装置的示意性框图。
图7示出了本申请实施例的另一通信装置的示意性框图。
图8示出了本申请实施例的网络设备的结构示意图。
本申请实施例的技术方案可以应用于各种通信***,例如:长期演进(long term evolution,LTE)***、LTE频分双工(frequency division duplex,FDD)***、LTE时分双工(time division duplex,TDD)、通用移动通信***(universal mobile telecommunication system,UMTS)、第五代(5th generation,5G)***或新无线(new radio,NR)或者其他演进的通信***等。
本申请实施例中的终端设备也可以称为:用户设备(user equipment,UE)、移动台(mobile station,MS)、移动终端(mobile terminal,MT)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置等。
终端设备可以是一种向用户提供语音/数据连通性的设备,例如,具有无线连接功能的手持式设备、车载设备等。目前,一些终端的举例为:手机(mobile phone)、平板电脑、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device,MID)、可穿戴设备,虚拟现实(virtual reality,VR)设备、增强现实(augmented reality,AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、蜂窝电话、无绳电话、会话启动协议(session initiation protocol,SIP)电话、无线本地环路(wireless local loop,WLL)站、个人数字助理(personal digital assistant,PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备,5G网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network,PLMN)中的终端设备等,本申请实施例对此并不限定。
作为示例而非限定,在本申请实施例中,该终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备,是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称,如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上,或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备,更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能,例如:智能手表或智能眼镜等,以及只专注于某一类应用功能,需要和其它设备如智能手机配合使用,如各类进行体征监测的智能手环、智能首饰等。
此外,在本申请实施例中,终端设备还可以是物联网(internet of things,IoT)***中的终端设备,IoT是未来信息技术发展的重要组成部分,其主要技术特点是将物品通过通信技术与网络连接,从而实现人机互连,物物互连的智能化网络。
另外,本申请实施例中的接入网设备和核心网设备可以统称为网络设备。其中,接入网设备可以是用于与终端设备通信的设备,该接入网设备也可以称为无线接入网设备,可以是传输接收点(transmission reception point,TRP)、接入回传一体化(integrated access and backhaul,IAB),或者可以是LTE***中的演进型基站(evolved NodeB,eNB或eNodeB),或者可以是家庭基站(例如,home evolved NodeB,或home Node B,HNB)、基带单元(base band unit,BBU),或者可以是云无线接入网络(cloud radio access network, CRAN)场景下的无线控制器,或者该接入网设备可以为中继站、接入点、车载设备、可穿戴设备以及5G网络中的接入网设备或者未来演进的陆上公用移动通信网(public land mobile network,PLMN)网络中的接入网设备等,可以是WLAN中的接入点(access point,AP),可以是新型无线***(new radio,NR)***中的gNB或者ng-eNB,本申请实施例并不限定。
在一种网络结构中,接入网设备可以包括集中单元(centralized unit,CU)节点、或分布单元(distributed unit,DU)节点、或包括CU节点和DU节点的RAN设备、或者控制面CU节点(CU-CP节点)和用户面CU节点(CU-UP节点)以及DU节点的RAN设备。
接入网设备为小区提供服务,终端设备通过接入网设备分配的传输资源(例如,频域资源,或者说,频谱资源)与小区进行通信,该小区可以属于宏基站(例如,宏eNB或宏gNB等),也可以属于小小区(small cell)对应的基站,这里的小小区可以包括:城市小区(metro cell)、微小区(micro cell)、微微小区(pico cell)、毫微微小区(femto cell)等,这些小小区具有覆盖范围小、发射功率低的特点,适用于提供高速率的数据传输服务。
本申请实施例的核心网网元可以是4G网络中的核心网网元,例如,移动管理实体(mobile management entity,MME)、服务网关(serving gateway,SGW)等,也可以是5G网络中的核心网网元,例如,接入和移动性管理功能(access and mobility management function,AMF)网元、用户平面功能(user plane function,UPF)网元等,还可以是具有其他名称的核心网网元,本申请实施例对此不作限定。
在本申请实施例中,终端设备或网络设备包括硬件层、运行在硬件层之上的操作***层,以及运行在操作***层上的应用层。该硬件层包括中央处理器(central processing unit,CPU)、内存管理单元(memory management unit,MMU)和内存(也称为主存)等硬件。该操作***可以是任意一种或多种通过进程(process)实现业务处理的计算机操作***,例如,Linux操作***、Unix操作***、Android操作***、iOS操作***或windows操作***等。该应用层包含浏览器、通讯录、文字处理软件、即时通信软件等应用。并且,本申请实施例并未对本申请实施例提供的方法的执行主体的具体结构特别限定,只要能够通过运行记录有本申请实施例的提供的方法的代码的程序,以根据本申请实施例提供的方法进行通信即可,例如,本申请实施例提供的方法的执行主体可以是终端设备或网络设备,或者,是终端设备或网络设备中能够调用程序并执行程序的功能模块。
另外,本申请的各个方面或特征可以实现成方法、装置或使用标准编程和/或工程技术的制品。本申请中使用的术语“制品”涵盖可从任何计算机可读器件、载体或介质访问的计算机程序。例如,计算机可读介质可以包括,但不限于:磁存储器件(例如,硬盘、软盘或磁带等),光盘(例如,压缩盘(compact disc,CD)、数字通用盘(digital versatile disc,DVD)等),智能卡和闪存器件(例如,可擦写可编程只读存储器(erasable programmable read-only memory,EPROM)、卡、棒或钥匙驱动器等)。另外,本文描述的各种存储介质可代表用于存储信息的一个或多个设备和/或其它机器可读介质。术语“机器可读介质”可包括但不限于,无线信道和能够存储、包含和/或承载指令和/或数据的各种其它介质。
为便于理解本申请实施例,首先结合图1对适用于本申请实施例的通信***进行详细说明。
图1是适用于本申请实施例的通信***的示意图。如图1所示,该通信***100可以包括核心网设备110、第一接入网设备120、第二接入网设备130和终端设备140。其中,终端设备140在第一接入网设备的覆盖范围对应的小区内,可以通过无线的方式与第一接入网设备120相连,第一接入网设备120和第二接入网设备130可以通过无线或有线方式与核心网设备110连接。
核心网设备110与第一接入网设备120(或第二接入网设备130)可以是独立的不同的物理设备,也可以是将核心网设备140的功能与接入网设备的逻辑功能集成在同一个物理设备上,还可以是一个物理设备上集成了部分核心网设备的功能和部分的接入网设备的功能,本申请实施例对此不作限定。
此外,在本申请实施例中,在一种可能的实现方式中,终端设备140可以是可移动的。若终端设备140移动到第一接入网设备120的覆盖范围对应的小区,该终端设备140可以将上行数据包传输到第一接入网络设备120,由第一接入网设备120发送到核心网设备110。第一接入网络设备120也可以将来自于核心网设备110的下行数据包传输到终端设备140。若终端设备140移动到第二接入网设备130的覆盖范围对应的小区,数据传输方式同理,不再赘述。
在本申请实施例中,在另一种可能的实现方式中,第一接入网设备120和第二接入网设备130可以是可移动的。若第一接入网设备120的移动使得终端设备140处于第一接入网设备120的覆盖范围对应的小区,该终端设备140可以将上行数据包传输到第一接入网络设备120,由第一接入网设备120发送到核心网设备110。第一接入网络设备120也可以将来自于核心网设备110的下行数据包传输到终端设备140。若第二接入网设备140的移动使得终端设备140处于第二接入网设备130的覆盖范围对应的小区,数据传输方式同理,不再赘述。
上述接入网设备(包括第一接入网设备120和第二接入网设备130)可以包括基带装置和射频装置,其中基带装置可以由一个节点实现,也可以由多个节点实现,射频装置可以从基带装置拉远独立实现,也可以集成基带装置中,或者部分拉远部分集成在基带装置中。例如,在LTE通信***中,接入网设备包括基带装置和射频装置,其中射频装置可以相对于基带装置拉远布置,例如射频拉远单元(remote radio unit,RRU)相对于BBU拉远布置。
上述各个通信设备,如图1中的核心网设备110、第一接入网设备120、第二接入网设备130或终端设备140,可以配置多个天线。该多个天线可以包括至少一个用于发送信号的发射天线和至少一个用于接收信号的接收天线。另外,各通信设备还附加地包括发射机链和接收机链,本领域普通技术人员可以理解,它们均可包括与信号发送和接收相关的多个部件(例如处理器、调制器、复用器、解调器、解复用器或天线等)。因此,接入网设备与终端设备之间可通过多天线技术通信。
应理解,图1只是示意图,该通信***100中还可以包括其它网络设备,例如,无线中继设备和无线回传设备,图1中未示出。本申请实施例对该通信***100中包括的核心网设备、接入网设备和终端设备的数量不做限定。
为便于理解,下面先介绍本申请实施例涉及的相关术语。
1、非陆地网络(non-terrestrial network,NTN)
由于传统地面网络不能为终端设备提供无缝覆盖,特别是在大海、沙漠、空中等无法部署基站的地方,非陆地网络被引入通信***中。NTN通信***可以包括卫星通信***、高空平台(high altitude platform station,HAPS)通信***或者其它非地面的通信***。NTN通信***通过将接入网设备或者部分接入网设备的功能部署在非地面的设备(例如高空平台或者卫星等)上为终端设备提供无缝覆盖,由于非地面设备受自然灾害的影响较小,能提升通信***的可靠性。
为便于说明和理解本申请实施例的方案,本申请后续将以网络设备部署在卫星上的NTN通信***为例进行说明。并且,为描述方便,本申请后续将“卫星上的网络设备”用“卫星”进行替代说明。也即,本申请后续涉及的终端设备与卫星之间的通信,实际上指的是终端设备与卫星上的网络设备之间的通信。这里统一说明,后续不再赘述。
基于卫星部署的非陆地网络中,卫星通过调整天线形成不同波束覆盖地面,按照不同的映射方式可以划分两种小区:地面静止小区和地面移动小区。地面静止小区的映射方式是指,小区的位置在地面是不动的,移动的卫星通过调整自己的波束形成这些小区。地面移动小区的映射方式是指,卫星生成的波束随着卫星的移动,在地面上移动,对应地,波束形成的小区也在地面上移动。这种小区对应的NTN网络设备也可以称为低轨卫星(low-earth orbit,LEO),或者称为其它移动的NTN网络设备。
2、RRC状态
以NR***为例,终端设备的无线资源控制状态包括连接态(RRC_CONNECTED)、去激活态(RRC_INACTIVE)和空闲态(RRC_IDLE)。下面分别对这三种状态进行说明。
(1)当终端设备处于连接态时,该终端设备与接入网设备以及核心网设备都已建立链路,当有数据到达网络时,核心网设备和接入网设备可以直接将数据传送至该终端设备。
(2)当终端设备处于去激活态时,说明该终端设备之前和接入网设备以及核心网设备建立过链路,但是该终端设备与接入网设备之间的链路被释放了。虽然链路被释放了,但是接入网设备需要保存终端设备的上下文,当有数据需要传输时,接入网设备可以根据终端设备的上下文快速恢复被释放的这段链路。
一般情况下,配置终端设备进入去激活态的、存储该终端设备的上下文的接入网设备可以称为锚点(anchor)接入网设备或源接入网设备。应理解,但是随着终端设备的移动,锚点接入网设备可能发生变化,即若原始的锚点接入网设备将终端设备的上下文转移至新的接入网设备,该新的接入网设备后续会作为新的锚点接入网设备。当然,锚点接入网设备也可以选择不转移终端设备的上下文,此处不作限制。
(3)当终端设备处于空闲态时,该终端设备与接入网设备和核心网设备之间都没有链路,当有数据需要传输时,需要建立终端设备到接入网设备及核心网设备的链路。
由上可知,去激活态只能在终端设备处于连接态的情况下通过RRC连接释放消息转变,在终端设备从连接态释放到去激活态时,为该终端设备服务的接入网设备(即上述锚点接入网设备或源接入网设备)会保存终端设备的上下文,并为该终端设备分配一个标识,以此标识存储终端设备的上下文。当终端设备后续发起RRC连接恢复流程时,需携带上述标识给当前为终端设备服务的接入网设备(可以称为目标接入网设备),获取该终端设备的上下文。因为终端设备具有移动性,上述目标接入网设备一般与锚点接入网设备是不同的设备,该目标接入网设备需要根据上述标识从锚点接入网设备处获取该终端设备的上 下文。
可以理解的,上述RRC状态的名称仅仅以NR为例进行说明,不应对本申请构成任何限定。本申请也并不排除在现有或未来的协议中定义其他可能的命名来替代上述NR中的RRC状态的名称,但具有相同或相似的特性。
考虑到在一些场景中,例如上述非陆地网络(non-terrestrial network,NTN)场景中,接入网设备的运动速度较快,例如,每隔1分钟至2分钟,终端设备就需要更换一次服务小区(即更换目标接入网设备)。而终端设备的上下文仅存储在锚点接入网设备,若处于去激活态的终端设备请求恢复RRC连接,目标接入网设备很难找到锚点接入网设备,从而向锚点接入网设备获取终端设备的上下文信息。若终端设备的上下文信息可以存储到其它网络设备,需要考虑该网络设备验证终端设备的机制。有鉴于此,本申请提供了一种通信方法,能够保证终端设备的连接恢复机制的运行,减少接入网设备的移动性对终端设备的连接恢复流程的影响,从而提高***性能。
下面将结合附图详细说明本申请提供的各个实施例。在下文示出的实施例中第一、第二、第三以及各种数字编号仅为描述方便进行的区分,并不用来限制本申请实施例的范围。例如,区分不同的信息、区分不同的安全验证参数等。
图2示出了本申请实施例的通信方法200的示意性流程图。该方法200可以应用于图1所示的通信***100,但本申请实施例不限于此。在方法200中,第一接入网设备相当于上述锚点接入网设备或源接入网设备,第二接入网设备相当于上述目标接入网设备。该方法包括:
S201,第一接入网设备向终端设备发送第一消息,该第一消息用于指示终端设备进入去激活态;则对应地,该终端设备接收该第一消息,并进入去激活态。
应理解,第一接入网设备在确定终端设备需要进入去激活态时,会向终端设备发送上述第一消息,并保存终端设备的上下文信息。终端设备的上下文信息也可以称为终端设备的上下文、或者终端设备的上下文数据。终端设备的上下文信息可以包括PDU会话上下文、安全密钥、终端设备的无线能力和终端设备的安全能力等信息。上述第一消息也可以称为RRC连接释放(RRC release)消息,或者其他名称,本申请实施例对此不作限定。
可选地,上述第一消息可以携带第一接入网设备为终端设备分配的标识(例如去激活态无线网络临时标识(inactive radio network temporary identifier,I-RNTI)),用于标识第一接入网设备存储的该终端设备的上下文信息。可选地,上述第一消息还可以携带下一跳链计数(next hop chaining count,NCC),用于密钥的推导。
S202,该第一接入网设备向核心网设备发送第二消息,该第二消息携带该终端设备的上下文信息和第一安全验证参数,该第一安全验证参数用于对该终端设备进行安全验证;则对应地,核心网设备接收该第二消息。
该第一安全验证参数可以包括该第一接入网设备为所述终端设备分配的第一小区无线网络临时标识(cell radio network temporary identifier,C-RNTI)。可选地,该第一安全验证参数还可以包括该终端设备在该第一接入网设备的小区的第一物理小区标识(physical cell identifier,PCI)。
S203,该核心网设备保存该上下文信息和该第一安全验证参数。
为了避免其他接入网设备找不到第一接入网设备,该第一接入网设备可以将终端设备 的上下文信息和第一安全验证参数发送给核心网设备,该核心网设备可以保存该上下文信息和第一安全验证参数,以便其他接入网设备从核心网设备处获取该终端设备的上下文信息。由于终端设备的上下文信息存储在核心网设备上,核心网设备需要同时保存第一安全验证参数,以便在其他接入网设备从核心网设备处获取终端设备的上下文信息时,对终端设备进行安全验证。
S204,终端设备向第二接入网设备发送第八消息,该第八消息用于请求恢复连接(即终端设备和第二接入网设备之间的连接,例如RRC连接),则对应地,第二接入网设备接收来自终端设备的第八消息。
由于终端设备和/或接入网设备的移动性,当处于去激活态的终端设备需要恢复连接(即转入激活态)时,该终端设备已经处于第二接入网设备的覆盖范围对应的小区内,需要由该第二接入网设备为该终端设备提供服务。因此,该终端设备可以向第二接入网设备发送上述第八消息,请求恢复连接。
示例性地,上述第八消息中可以携带第一接入网设备为终端设备分配的标识(例如I-RNTI),以便第二接入网设备根据该标识,获取该终端设备的上下文信息。此外,上述第八消息中还可以携带终端设备的认证信息。作为一种示例,该认证信息可以为短消息验证代码-完整性(short message authentication code-integrity,short MAC-I)消息,short MAC-I消息是一个16比特的认证消息。例如,终端设备可以利用该终端设备在第一接入网设备上的小区的C-RNTI、该小区的PCI以及终端设备当前所在的第二接入网设备的小区的ID作为输入,结合其他密钥参数,计算出上述short MAC-I消息。
可选地,上述第八消息中还可以携带终端设备请求恢复连接的原因。该请求恢复连接的原因可以例如是无线接入网通知区更新(ran notification area update,RNAU)、或者其它主动或被动业务触发的原因的任一种,本申请实施例对此不作限定。
在本申请实施例中,第二接入网设备获取终端设备的上下文信息可以分下列多种不同的情况:
情况1、第二接入网设备未找到第一接入网设备,或者第二接入网设备没有找第一接入网设备。在这种情况下,该第二接入网设备只能向核心网设备请求终端设备的上下文信息。因此,本实施例可以在S201-S204之后执行下列流程:
S208,该第二接入网设备向核心网设备发送第六消息,该第六消息用于请求终端设备的上下文信息;则对应地,核心网设备接收该第六消息。
示例性地,第六消息可以携带I-RNTI和认证信息。此外,该第六消息还携带终端设备当前所在的第二接入网设备的小区的cell ID。
可选地,该第六消息还可以携带第二安全验证参数。该第二安全验证参数包括该第二接入网设备为所述终端设备分配的第二C-RNTI。可选地,该第二安全验证参数还包括该终端设备在该第二接入网设备的小区的第二PCI。应理解,在本文中,第二接入网设备的小区指的是终端设备在第二接入网设备中发起接入或恢复请求的小区。
S209,核心网设备根据该第一安全验证参数,对该终端设备进行安全验证。
上述核心网设备在收到来自第二接入网设备的第六消息之后,可以利用之前保存的第一安全验证参数对终端设备进行验证。示例性地,核心网设备可以根据上述第一C-RNTI,或者上述第一C-RNTI和第一PCI对终端设备进行验证。
示例性地,以第八消息携带的认证信息为short MAC-I为例,上述对终端设备进行验证可以指验证终端设备的short MAC-I消息,核心网设备利用之前存储的密钥和第一安全验证参数按照相同的方法计算出short MAC-I消息。核心网设备将自身计算出的short MAC-I消息和从第二接入网设备接收到的short MAC-I消息进行比较,若相同,则验证通过,否则,验证不通过。
S210,在所述安全验证通过的情况下,所述核心网设备向所述第二接入网设备发送第七消息。所述第七消息携带所述上下文信息,或者,所述第七消息指示所述核心网设备不向所述第二接入网设备提供所述上下文信息;则对应地,所述第二接入网设备接收来自所述核心网设备的第七消息。
进一步地,第二接入网设备可以根据上述第七消息,向终端设备发送响应消息(图2中未示出)。在该第七消息携带上下文信息时,该响应消息可以指示允许终端设备恢复连接或者该响应消息可以指示终端设备释放连接;在该第七消息指示核心网设备不向第二接入网设备提供上下文信息时,该响应消息可以指示拒绝终端设备恢复连接,或者说该响应消息可以指示终端设备释放连接。作为一种实现方式,核心网设备生成响应消息,向第二接入网设备发送携带响应消息的第七消息,该第七消息指示核心网设备不向第二接入网设备提供上下文信息,第二接入网设备向终端设备转发该响应消息。
在上述安全验证通过的情况下,核心网设备可以确定是否向第二接入网设备提供终端设备的上下文。若核心网设备确定向第二接入网设备提供终端设备的上下文信息,则该核心网设备可以根据第一接入网设备为终端设备分配的标识(例如I-RNTI)找到终端设备的上下文信息,并向第二接入网设备直接发送该上下文信息。若核心网设备确定不向第二接入网设备提供终端设备的上下文信息,则该核心网设备可以向第二接入网设备发送用于指示该核心网设备不向第二接入网设备提供上下文信息的消息。
可选地,上述第六消息中可以携带终端设备请求恢复连接的原因,该请求恢复连接的原因是第二接入网设备从来自终端设备的第八消息中获得的。该请求恢复连接的原因可以例如是无线接入网通知区更新(ran notification area update,RNAU)、或者其它主动或被动业务触发的原因的任一种,本申请实施例对此不作限定。该核心网设备可以根据该终端设备请求恢复连接的原因,确定是否为第二接入网设备提供终端设备的上下文信息。
本申请实施例的通信方法,通过第一接入网设备将终端设备的上下文信息和用于验证终端设备的安全验证参数发送给核心网设备,使得第二接入网设备可以从核心网设备处获取终端设备的上下文信息,从而恢复终端设备和第二接入网设备的连接,避免了在第二接入网设备无法找到第一接入网设备或者第一接入网设备不提供终端设备的上下文信息的情况下,无法恢复连接的情况,能够保证终端设备的连接恢复机制的运行,减少接入网设备的移动性对终端设备的连接恢复流程的影响,从而提高***性能。
情况2、第二接入网设备找到了第一接入网设备,但是,第一接入网设备未存储终端设备的上下文信息,即第一接入网设备无法向第二接入网设备提供终端设备的上下文信息。在这种情况下,本实施例可以在S201-S204之后执行下列流程:
S205,所述第二接入网设备向第一接入网设备发送第三消息,所述第三消息用于请求所述终端设备的上下文信息;则对应地,第一接入网设备接收该第三消息。
示例性地,该第三消息中可以携带I-RNTI和认证信息。此外,该第三消息还携带终 端设备当前所在的第二接入网设备的小区的cell ID。
可选地,该第三消息还携带终端设备当前所在的第二接入网设备的第二安全验证参数。该第二安全验证参数包括该第二接入网设备为所述终端设备分配的第二C-RNTI。可选地,该第二安全验证参数还包括该终端设备在该第二接入网设备的小区的第二PCI。
S207,该第一接入网设备可以直接向第二接入网设备发送第四消息,所述第四消息指示所述第一接入网设备不向所述第二接入网设备提供所述上下文信息;比如,由于第一接入网设备未存储终端设备的上下文信息,无法对终端设备进行安全验证,第一接入网设备无法向第二接入网设备提供所述上下文信息。则对应地,第二接入网设备接收该第四消息。
可选地,所述第四消息还指示所述核心网设备的标识信息。
S208,第二接入网设备可以从第四消息中获取核心网设备的标识信息,向该核心网设备发送第六消息;则对应地,核心网设备接收第六消息。
S209,核心网设备根据该第一安全验证参数,对该终端设备进行安全验证。
S210,在所述安全验证通过的情况下,核心网设备向所述第二接入网设备发送第七消息,所述第七消息携带所述上下文信息,或者,所述第七消息指示所述核心网设备不向所述第二接入网设备提供所述上下文信息;则对应地,所述第二接入网设备接收来自所述核心网设备的第七消息。
进一步地,第二接入网设备可以根据上述第七消息,向终端设备发送响应消息(图2中未示出)。
关于S208-S210和向终端设备发送响应消息的具体描述可参考情况1,此处不再赘述。
情况3、第二接入网设备找到了第一接入网设备,该第一接入网设备存储了终端设备的上下文信息,但是,该第一接入网设备确定不为第二接入网设备提供该终端设备的上下文信息。在这种情况下,本实施例可以在S201-S204之后执行下列流程:
S205,第二接入网设备向第一接入网设备发送第三消息,所述第三消息用于请求所述终端设备的上下文信息;则对应地,第一接入网设备接收该第三消息。关于S205的具体描述可参考情况2,此处不再赘述。
S206,由于第一接入网设备存储了终端设备的上下文,该第一接入网设备可以采用第一安全验证参数对终端设备进行安全验证。关于第一接入网设备进行安全验证的具体描述可参考情况1中核心网设备进行安全验证的描述,此处不再赘述。
S207,在安全验证通过的情况下,第一接入网设备可以确定是否要向第二接入网设备提供终端设备的上下文。示例性地,上述第三消息中可以携带终端设备请求恢复连接的原因,第一接入网设备可以根据该终端设备请求恢复连接的原因,确定是否向第二接入网设备提供终端设备的上下文信息。
在情况3中,第一接入网设备确定不向所述第二接入网设备提供终端设备的上下文信息,该第一接入网设备可以向第二接入网设备发送第四消息,该第四消息指示该第一接入网设备不向第二接入网设备提供终端设备的上下文信息,则对应地,第二接入网设备接收该第四消息。
进一步地,第二接入网设备可以根据上述第四消息,向终端设备发送响应消息(图2中未示出)。该响应消息可以指示拒绝终端设备恢复连接,或者说,该响应消息可以指示终端设备释放连接。作为一种实现方式,第一接入网设备生成响应消息,向第二接入网设 备发送携带响应消息的第四消息,该第四消息指示该第一接入网设备不向第二接入网设备提供终端设备的上下文信息,第二接入网设备向终端设备转发该响应消息。
S211,第一接入网设备向核心网设备发送第五消息,所述第五消息携带所述第二安全验证参数,以更新所述核心网设备存储的安全验证参数;则对应地,所述核心网设备接收所述第五消息。
比如,当第一接入网设备向第二接入网发送第四消息,第四消息携带响应消息,该响应消息指示终端设备释放连接并进入去激活态时,第一接入网设备向核心网设备发送第五消息。
S213,核心网设备将安全验证参数从所述第一安全验证参数更新为所述第二安全验证参数。
在第一接入网设备对终端设备安全验证成功,但确定不提供终端设备的上下文信息的情况下,第一接入网设备需要更新存储的安全验证参数,并为核心网设备更新安全验证参数。即核心网设备需要将安全验证参数从第一安全验证参数更新为第二安全验证参数,以便下一次对终端设备进行安全验证。因此,上述第二安全验证参数需要携带在上述第三消息中,由第二接入网设备发送给第一接入网设备,再由第一接入网设备通过第五消息发送给核心网设备。这样,核心网设备可以获取到最新的安全验证参数,以便进行下一次终端设备的安全验证,从而保证终端设备和核心网设备所保存的安全验证参数保持一致,避免安全验证失败,能够保证终端设备的连接恢复机制的运行,减少接入网设备的移动性对终端设备的连接恢复流程的影响,从而提高***性能。
情况4、第二接入网设备找到了第一接入网设备,该第一接入网设备存储了终端设备的上下文信息,且该第一接入网设备确定向第二接入网设备提供该终端设备的上下文信息。在这种情况下,本实施例可以在S201-S204之后执行下列流程:
S205,第二接入网设备向第一接入网设备发送第三消息,所述第三消息用于请求所述终端设备的上下文信息;则对应地,第一接入网设备接收该第三消息。关于S205的具体描述可参考情况2,此处不再赘述。
S206,由于第一接入网设备存储了终端设备的上下文,该第一接入网设备可以采用第一安全验证参数对终端设备进行安全验证。关于第一接入网设备进行安全验证的具体描述可参考情况1中核心网设备进行安全验证的描述,此处不再赘述。
S207,在安全验证通过的情况下,第一接入网设备可以确定是否要向第二接入网设备提供终端设备的上下文。示例性地,上述第三消息中可以携带终端设备请求恢复连接的原因,第一接入网设备可以根据该终端设备请求恢复连接的原因,确定是否向第二接入网设备提供终端设备的上下文信息。
在情况4中,第一接入网设备确定向所述第二接入网设备提供终端设备的上下文信息,该第一接入网设备可以向第二接入网设备发送第四消息,该第四消息携带终端设备的上下文信息,则对应地,第二接入网设备接收该第四消息。
进一步地,第二接入网设备可以根据上述第四消息,向终端设备发送响应消息(图2中未示出)。该响应消息可以指示允许终端设备恢复连接,或者该响应消息可以指示终端设备释放连接。
S212,第二接入网设备向核心网设备发送第九消息,该第九消息携带第二安全验证参 数,以更新该核心网设备存储的安全验证参数;则对应地,该核心网设备接收该第九消息。比如,当第二接入网设备向终端设备发送响应消息,该响应消息指示终端设备释放连接并进入去激活态时,第二接入网设备向核心网设备发送第九消息。
可选地,该第九消息还携带终端设备的上下文信息,以便下一次终端设备恢复连接时,若为该终端设备提供服务的新的接入网设备找不到第二接入网设备,该新的接入网设备可以从核心网设备获取终端设备的上下文信息。
S213,核心网设备将安全验证参数从所述第一安全验证参数更新为所述第二安全验证参数。关于S213的具体描述可参考情况3,此处不再赘述。
在上述方法200中,作为一个可选的实施例,在所述第一接入网设备向核心网设备发送第二消息之后,所述方法还包括:所述第一接入网设备删除所述终端设备的上下文信息。
在上述方法200中,作为一个可选的实施例,在所述核心网设备向所述第二接入网设备发送所述上下文信息的情况下,所述方法还包括:所述核心网设备删除所述终端设备的上下文信息。
下面,以终端设备为UE,第一接入网设备为LEO 1,第二接入网设备为LEO 2,核心网设备为AMF为例,结合图3和图4对本申请实施例进行详细说明。
图3示出了本申请实施例的另一通信方法300的示意性流程图。该方法300可以应用于图1所示的***架构100,但本申请实施例不限于此。该方法300针对UE请求恢复连接时LEO 1存储有UE的上下文信息的场景,该方法包括:
S301,LEO 1向UE发送第一消息,该第一消息用于请求UE进入去激活态,LEO 1保存UE的上下文信息;则对应地,UE接收该第一消息,进入去激活态。
S302,LEO 1向AMF发送第二消息,该第二消息携带UE的上下文信息和第一安全验证参数;则对应地,AMF接收该第二消息。
上述第一安全验证参数可以包括LEO 1为UE分配的第一C-RNTI。上述第一安全验证参数还可以包括UE在LEO 1的小区的第一PCI。AMF可以根据该第一安全验证参数,在其他接入网设备下一次请求获取UE的上下文信息时对UE进行安全性验证。
S303,AMF保存UE的上下文信息和第一安全验证参数。
S304,UE向LEO 2发送第八消息,该第八消息用于请求恢复连接;则对应地,LEO 2接收该第八消息。
S305,LEO 2可以找到LEO 1,并向LEO 1发送第三消息,该第三消息用于请求终端设备的上下文;则对应地,LEO 1接收该第三消息。
上述第三消息可以包括第二安全验证参数,该第二安全验证参数包括LEO 2为UE分配的第二C-RNTI。可选地,该第二安全验证参数还可以包括UE在LEO 2的发起接入或恢复请求的小区的第二PCI。
S306,LEO 1对终端设备进行安全验证。
S307,LEO 1向LEO 2发送第四消息。
若上述安全验证成功,LEO 1确定是否向LEO 2提供UE的上下文信息。在本申请实施例中,LEO 1确定不向LEO 2提供UE的上下文信息,该LEO 1向LEO 2发送第四消息(也可以称为拒绝响应),表示不提供UE的上下文信息。LEO1生成响应消息,第是消息中携带该响应消息。该响应消息用于指示UE释放RRC连接。
S308,LEO 1向AMF发送第五消息,该第五消息携带第二安全验证参数。则对应地,AMF接收该第五消息。上述第二安全验证参数可以包括LEO 2为UE分配的第二C-RNTI和UE在LEO 2的小区的第二PCI。
S309,AMF将安全验证参数从第一安全验证参数更新为第二安全验证参数。
S310,LEO 2在接收到LEO 1发送的第四消息之后,向UE发送响应消息。该响应消息用于释放UE的RRC连接;则对应地,UE接收该响应消息。该响应消息可以用于指示UE进入空闲态或者去激活态。作为一种示例,本流程中,该响应消息指示UE进入去激活态。
本申请实施例的通信方法,通过LEO 1将UE的上下文信息和用于验证UE的安全验证参数发送给AMF,但LEO 1仍旧保留UE的上下文。若UE在LEO 2发起恢复请求,LEO 2向LEO 1请求获取UE的上下文。可选地,LEO 2可以向LEO 1发送新的安全验证参数。若LEO 1成功验证UE,但是LEO 1没有向LEO 2提供UE的上下文,LEO 1需要更新存储的安全验证参数,并向AMF发送更新的安全验证参数。更新的安全验证参数用于下一次终端设备的安全验证,以提高***的安全性。
图4示出了本申请实施例的另一通信方法400的示意性流程图。该方法400可以应用于图1所示的***架构100,但本申请实施例不限于此。该方法400针对UE请求恢复连接时LEO 1未存储有UE的上下文信息的场景,该方法包括:
S401,LEO 1向UE发送第一消息,该第一消息用于请求UE进入去激活态,LEO 1保存UE的上下文信息;则对应地,UE接收该第一消息,进入去激活态。
S402,LEO 1向AMF发送第二消息,该第二消息携带UE的上下文信息和第一安全验证参数;则对应地,AMF接收该第二消息。
上述第一安全验证参数可以包括LEO 1为UE分配的第一C-RNTI。上述第一安全验证参数还可以包括UE在LEO 1的小区的第一PCI。AMF可以根据该第一安全验证参数,在其他接入网设备下一次请求获取UE的上下文信息时对UE进行安全性验证。
S403,AMF保存UE的上下文信息和第一安全验证参数。
S404,UE向LEO 2发送第八消息,该第八消息用于请求恢复连接;则对应地,LEO 2接收该第八消息。
可选地,S405,LEO 2可以找到LEO 1,并向LEO 1发送第三消息,该第三消息用于请求终端设备的上下文;则对应地,LEO 1接收该第三消息。
上述第三消息可以包括第二安全验证参数,第二安全验证参数包括LEO 2为UE分配的第二C-RNTI。第二安全验证参数还可以包括UE在LEO 2的发起接入或恢复请求的小区的第二PCI。
可选地,S406,LEO 1向LEO 2发送第四消息。该第四消息可以携带AMF的标识。该第四消息可以表示不向LEO 2提供UE的上下文信息。则对应地,LEO 2接收该第四消息。本申请实施例中,LEO 1未存储UE的上下文信息,示例性地,该LEO 1可以在S403之后删除UE的上下文信息。
S407,LEO 2向AMF发送第六消息,该第六消息用于请求UE的上下文信息;则对应地,AMF接收该第六消息。可选的,LEO 2可以根据第四消息中的AMF的标识确定发送第六消息的AMF。
可选地,上述第六消息可以携带第二安全验证参数,用于AMF下一次对UE进行安全验证。第二安全验证参数包括所述第二接入网设备为所述终端设备分配的第二小区无线网络临时标识C-RNTI。第二安全验证参数还可以包括所述终端设备在所述第二接入网设备的发起接入或恢复请求的小区的第二物理小区标识PCI。
S408,AMF根据上述保存的第一安全验证参数,对UE进行安全验证。
S409,在安全验证成功的情况下,AMF向LEO 2发送第七消息,该第七消息携带UE的上下文信息,或者,该第七消息指示AMF不向LEO 2提供UE的上下文信息;则对应地,LEO 2接收来自AMF的第七消息。若AMF不向LEO 2提供UE的上下文信息,AMF可以生产响应消息,并在第七消息中携带该响应消息发送给LEO 2。
应理解,若安全验证成功但是AMF确定不向LEO 2提供UE的上下文信息,该AMF需要保存第六消息中携带的第二安全验证参数,将安全验证参数从第一安全验证参数更新至第二安全验证参数,以提高***的安全性。
S410,LEO 2向UE发送响应消息。
若上述第七消息携带上下文信息,则该响应消息可以用于恢复UE的连接,也可以用于释放UE的连接。具体的,可以由LEO2决定。若上述第七消息指示AMF不提供UE的上下文信息,则该响应消息用于释放UE的RRC连接;则对应地,UE接收该响应消息。该响应消息可以用于指示UE进入空闲态或者去激活态。作为一种示例,本流程中,该响应消息指示UE进入去激活态。。
可以理解的,LEO2可以不执行S405和S406。比如LEO2默认LEO1已经删除了UE的上下文,因此仅向AMF请求UE的上下文。具体的,LEO2可以向其连接的AMF请求UE的上下文。
本申请实施例的通信方法,通过LEO 1将UE的上下文信息和用于验证UE的安全验证参数发送给AMF,随后LEO 1删除了UE的上下文,使得LEO 2可以从AMF处获取UE的上下文信息,从而恢复UE和LEO 2的连接,避免了在第二接入网设备无法找到第一接入网设备或者第一接入网设备不提供终端设备的上下文信息的情况下,无法恢复连接的情况,能够保证终端设备的连接恢复机制的运行,减少接入网设备的移动性对终端设备的连接恢复流程的影响,从而提高***性能。
应理解,上述各过程的序号的大小并不意味着执行顺序的先后,各过程的执行顺序应以其功能和内在逻辑确定,而不应对本申请实施例的实施过程构成任何限定。
上文中结合图1至图4,详细描述了根据本申请实施例的通信方法,下面将结合图5至图8,详细描述根据本申请实施例的通信装置和网络设备。
图5是本申请实施例提供的通信装置的示意性框图。该数据传输的装置500可实现对应于上文方法实施例中的第一接入网设备执行的各个步骤或者流程,例如,该装置500可以为第一接入网设备,或者为配置于第一接入网设备中的芯片或电路。如图所示,该装置500可以包括:发送单元510和接收单元520。
其中,发送单元510用于:向终端设备发送第一消息,所述第一消息用于指示所述终端设备进入去激活态;以及,向核心网设备发送第二消息,所述第二消息携带所述终端设备的上下文信息和第一安全验证参数,所述第一安全验证参数用于对所述终端设备进行安全验证;接收单元520用于:接收来自第二接入网设备的第三消息,所述第三消息用于请 求所述终端设备的上下文信息;所述发送单元510还用于:向所述第二接入网设备发送第四消息,所述第四消息指示所述第一接入网设备不向所述第二接入网设备提供所述上下文信息。
可选地,所述第四消息还用于指示所述核心网设备的标识信息。
可选地,所述第一接入网设备存储有所述终端设备的上下文信息,所述装置还包括:处理单元,用于根据所述第一安全验证参数,对所述终端设备进行安全验证;所述发送单元510具体用于:在所述安全验证通过的情况下,若所述通信装置确定不向所述第二接入网设备提供所述上下文信息,向所述第二接入网设备发送所述第四消息。
可选地,所述第三消息携带所述终端设备的第二安全验证参数,所述第二安全验证参数用于对所述终端设备进行安全验证,所述发送单元510具体用于:向所述核心网设备发送第五消息,所述第五消息携带所述第二安全验证参数,以更新所述核心网设备存储的安全验证参数。
可选地,所述第二安全验证参数包括所述第二接入网设备为所述终端设备分配的第二小区无线网络临时标识C-RNTI和所述终端设备在所述第二接入网设备的小区的第二物理小区标识PCI。
可选地,在向核心网设备发送第二消息之后,所述装置还包括:处理单元,用于删除所述终端设备的上下文信息。
可选地,所述第一安全验证参数包括所述第一接入网设备为所述终端设备分配的第一C-RNTI和所述终端设备在所述第一接入网设备的小区的第一PCI。
应理解,这里的装置500以功能单元的形式体现。这里的术语“单元”可以指应用特有集成电路(application specific integrated circuit,ASIC)、电子电路、用于执行一个或多个软件或固件程序的处理器(例如共享处理器、专有处理器或组处理器等)和存储器、合并逻辑电路和/或其它支持所描述的功能的合适组件。在一个可选例子中,本领域技术人员可以理解,装置500可以具体为上述实施例中的第一接入网设备,装置500可以用于执行上述方法实施例中与第一接入网设备对应的各个流程和/或步骤,为避免重复,在此不再赘述。
图6是本申请实施例提供的另一通信装置的示意性框图。该数据传输的装置600可实现对应于上文方法实施例中的核心网设备执行的各个步骤或者流程,例如,该装置600可以为核心网设备,或者为配置于核心网设备中的芯片或电路。如图所示,该装置600可以包括:接收单元610和处理单元620。
其中,接收单元610用于:接收来自第一接入网设备的第二消息,所述第二消息携带终端设备的上下文信息和第一安全验证参数,所述第一安全验证参数用于对所述终端设备进行安全验证;处理单元620用于:保存所述上下文信息和所述第一安全验证参数。
可选地,所述接收单元610还用于:接收来自第二接入网设备的第六消息,所述第六消息用于请求所述终端设备的上下文信息;所述处理单元620还用于:根据所述第一安全验证参数,对所述终端设备进行安全验证;所述装置还包括:发送单元,用于在所述安全验证通过的情况下,向所述第二接入网设备发送第七消息,所述第七消息携带所述上下文信息,或者,所述第七消息指示所述核心网设备不向所述第二接入网设备提供所述上下文信息。
可选地,所述第六消息携带所述终端设备的第二安全验证参数,所述第二安全验证参数用于对所述终端设备进行安全验证,所述处理单元620还用于:将安全验证参数从所述第一安全验证参数更新为所述第二安全验证参数。
可选地,所述第二安全验证参数包括所述第二接入网设备为所述终端设备分配的第二小区无线网络临时标识C-RNTI和所述终端设备在所述第二接入网设备的小区的第二物理小区标识PCI。
可选地,在所述核心网设备向所述第二接入网设备发送所述上下文信息的情况下,所述处理单元620还用于:删除所述终端设备的上下文信息。
可选地,所述第一安全验证参数包括所述第一接入网设备为所述终端设备分配的第一C-RNTI和所述终端设备在所述第一接入网设备的小区的第一PCI。
应理解,这里的装置600以功能单元的形式体现。这里的术语“单元”可以指应用特有集成电路(application specific integrated circuit,ASIC)、电子电路、用于执行一个或多个软件或固件程序的处理器(例如共享处理器、专有处理器或组处理器等)和存储器、合并逻辑电路和/或其它支持所描述的功能的合适组件。在一个可选例子中,本领域技术人员可以理解,装置600可以具体为上述实施例中的核心网设备,装置500可以用于执行上述方法实施例中与核心网设备对应的各个流程和/或步骤,为避免重复,在此不再赘述。
图7是本申请实施例提供的另一通信装置的示意性框图。该数据传输的装置700可实现对应于上文方法实施例中的第二接入网设备执行的各个步骤或者流程,例如,该装置700可以为第二接入网设备,或者为配置于第二接入网设备中的芯片或电路。如图所示,该装置700可以包括:接收单元710和发送单元720。
其中,接收单元710用于:接收来自终端设备的第八消息,所述第八消息用于请求恢复连接;发送单元720用于:向核心网设备发送第六消息,所述第六消息用于请求所述终端设备的上下文信息;所述接收单元710还用于:接收来自所述核心网设备的第七消息,所述第七消息携带所述上下文信息,或者,所述第七消息指示所述核心网设备不向所述第二接入网设备提供所述上下文信息。
可选地,在向核心网设备发送第六消息之前,所述发送单元720还用于:根据所述第八消息,向第一接入网设备发送第三消息,所述第三消息用于请求所述终端设备的上下文信息;所述接收单元710还用于:接收来自所述第一接入网设备的第四消息,所述第四消息指示所述第一接入网设备不向所述第二接入网设备提供所述上下文信息,且所述第四消息还指示所述核心网设备的标识信息;所述发送单元720还用于:根据所述核心网设备的标识信息,向所述核心网设备发送所述第六消息。
可选地,所述第五消息携带所述终端设备的第二安全验证参数,以便所述核心网设备将安全验证参数从第一安全验证参数更新为第二安全验证参数,所述第二安全验证参数用于对所述终端设备进行安全验证。
可选地,所述第一安全验证参数包括所述第一接入网设备为所述终端设备分配的第一小区无线网络临时标识C-RNTI和所述终端设备在所述第一接入网设备的小区的第一物理小区标识PCI;所述第二安全验证参数包括所述第二接入网设备为所述终端设备分配的第二C-RNTI和所述终端设备在所述第二接入网设备的小区的第二PCI。
应理解,这里的装置700以功能单元的形式体现。这里的术语“单元”可以指应用特 有集成电路(application specific integrated circuit,ASIC)、电子电路、用于执行一个或多个软件或固件程序的处理器(例如共享处理器、专有处理器或组处理器等)和存储器、合并逻辑电路和/或其它支持所描述的功能的合适组件。在一个可选例子中,本领域技术人员可以理解,装置700可以具体为上述实施例中的第二接入网设备,装置500可以用于执行上述方法实施例中与第二接入网设备对应的各个流程和/或步骤,为避免重复,在此不再赘述。
上述装置500具有实现上述方法中第一接入网设备执行的相应步骤的功能;上述装置600具有实现上述方法中核心网设备执行的相应步骤的功能;上述装置700具有实现上述方法中第二接入网设备执行的相应步骤的功能。所述功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。例如,上述发送单元可以由发射器替代,上述接收单元可以由接收器替代,分别执行各个方法实施例中的接收和发送操作以及相关的处理操作。发送单元和接收单元可以统称为收发单元,相应地,接收器和发射器可以统称为收发器。应理解,上文实施例中的处理单元可以由处理器或处理器相关电路实现,接收单元和发送单元可以由收发器或收发器相关电路或接口电路实现。
可选地,在上面各个可能设计的装置中,还可以包括存储单元,该存储单元用于存储计算机程序,处理单元可以从存储单元中调用并运行该计算机程序,使得装置500执行上述方法实施例中第一接入网设备的方法,或者,使得装置600执行上述方法实施例中核心网设备的方法,或者,使得装置700执行上述方法实施例中第二接入网设备的方法。
上述实施例中的单元也可以称为模块或者电路或者部件等。
图8是本申请实施例提供的网络设备3000的结构示意图,例如,该网络设备3000可以为接入网设备的结构示意图,或者该网络设备3000可以为核心网设备的结构示意图。该网络设备3000可应用于如图1所示的通信***中,实现上述方法实施例中第一接入网设备执行的步骤或流程,或者实现上述方法实施例中核心网设备执行的步骤或者流程,或者实现上述方法实施例中第二接入网设备执行的步骤或者流程,此处不再赘述。
如图所示,该网络设备3000可以包括一个或多个射频单元,如远端射频单元(remote radio unit,RRU)3100以及一个或多个基带单元(baseband unit,BBU)3200,其中,BBU 3200也可称为数字单元(digital unit,DU),RRU 3100可以称为收发单元,与图5-图7中的接收单元、发送单元对应。可选地,该RRU 3100还可以称为收发机、收发电路、或者收发器等等,其可以包括至少一个天线3101和射频单元3102。可选地,该RRU 3100可以包括接收单元和发送单元,接收单元可以对应于接收器(或称接收机、接收电路),发送单元可以对应于发射器(或称发射机、发射电路)。所述RRU 3100部分主要用于射频信号的收发以及射频信号与基带信号的转换,例如用于向终端设备发送指示信息。所述BBU 3200部分主要用于进行基带处理,对网络设备进行控制等。所述RRU 3100与BBU 3200可以是物理上设置在一起,也可以物理上分离设置的,例如分布式基站。
所述BBU 3200为网络设备的控制中心,也可以称为处理单元,可以与上述装置中的处理单元对应,主要用于完成基带处理功能,如信道编码,复用,调制,扩频等等。例如所述BBU 3200可以用于控制网络设备执行上述方法实施例中关于第一接入网设备、第二接入网设备或者核心网设备的操作流程,例如,生成上述切换条件,或者发送切换条件等。
在一个示例中,所述BBU 3200可以由一个或多个单板构成,多个单板可以共同支持单一接入制式的无线接入网(如LTE网),也可以分别支持不同接入制式的无线接入网(如LTE网,5G网或其他网)。所述BBU 3200还包括存储器3201和处理器3202。所述存储器3201用以存储必要的指令和数据。所述处理器3202用于控制网络设备进行必要的动作,例如用于控制网络设备执行上述方法实施例中关于第一接入网设备、第二接入网设备或者核心网设备的操作流程。所述存储器3201和处理器3202可以服务于一个或多个单板。也就是说,可以每个单板上单独设置存储器和处理器。也可以是多个单板共用相同的存储器和处理器。此外每个单板上还可以设置有必要的电路。
应理解,图8所示的网络设备3000能够实现图2至图4方法实施例中涉及第一接入网设备、第二接入网设备或者核心网设备的各个过程。网络设备3000中的各个模块的操作和/或功能,分别为了实现上述方法实施例中的相应流程。具体可参见上述方法实施例中的描述,为避免重复,此处适当省略详述描述。
上述BBU 3200可以用于执行前面方法实施例中描述的由第一接入网设备、第二接入网设备或者核心网设备内部实现的动作,而RRU 3100可以用于执行前面方法实施例中描述的第一接入网设备、第二接入网设备或者核心网设备向终端设备发送或从终端设备接收的动作。具体请见前面方法实施例中的描述,此处不再赘述。
本申请实施例还提供了一种处理装置,包括处理器和接口。所述处理器可用于执行上述方法实施例中的方法。
应理解,上述处理装置可以是一个芯片。例如,该处理装置可以是现场可编程门阵列(field programmable gate array,FPGA),可以是专用集成芯片(application specific integrated circuit,ASIC),还可以是***芯片(system on chip,SoC),还可以是中央处理器(central processor unit,CPU),还可以是网络处理器(network processor,NP),还可以是数字信号处理电路(digital signal processor,DSP),还可以是微控制器(micro controller unit,MCU),还可以是可编程控制器(programmable logic device,PLD)或其他集成芯片。
在实现过程中,上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成,或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器,闪存、只读存储器,可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器,处理器读取存储器中的信息,结合其硬件完成上述方法的步骤。为避免重复,这里不再详细描述。
应注意,本申请实施例中的处理器可以是一种集成电路芯片,具有信号的处理能力。在实现过程中,上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成,或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器,闪存、只读存储器,可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质 中。该存储介质位于存储器,处理器读取存储器中的信息,结合其硬件完成上述方法的步骤。
可以理解,本申请实施例中的存储器可以是易失性存储器或非易失性存储器,或可包括易失性和非易失性存储器两者。其中,非易失性存储器可以是只读存储器(read-only memory,ROM)、可编程只读存储器(programmable ROM,PROM)、可擦除可编程只读存储器(erasable PROM,EPROM)、电可擦除可编程只读存储器(electrically EPROM,EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory,RAM),其用作外部高速缓存。通过示例性但不是限制性说明,许多形式的RAM可用,例如静态随机存取存储器(static RAM,SRAM)、动态随机存取存储器(dynamic RAM,DRAM)、同步动态随机存取存储器(synchronous DRAM,SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM,DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM,ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM,SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM,DR RAM)。应注意,本文描述的***和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
根据本申请实施例提供的方法,本申请还提供一种计算机程序产品,该计算机程序产品包括:计算机程序代码,当该计算机程序代码在计算机上运行时,使得该计算机执行上述任意一个实施例中任意一个网元所对应的方法。
根据本申请实施例提供的方法,本申请还提供一种计算机可读介质,该计算机可读介质存储有程序代码,当该程序代码在计算机上运行时,使得该计算机执行图2至图4所示实施例中任意一个实施例中任意一个网元所对应的方法。
根据本申请实施例提供的方法,本申请还提供一种***,其包括前述的一个或多个终端设备、一个或多个接入网设备、以及一个或多个核心网设备。
在上述实施例中,可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时,可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时,全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中,或者从一个计算机可读存储介质向另一个计算机可读存储介质传输,例如,所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line,DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如,软盘、硬盘、磁带)、光介质(例如,高密度数字视频光盘(digital video disc,DVD))、或者半导体介质(例如,固态硬盘(solid state disc,SSD))等。
上述各个装置实施例中网络设备与终端设备和方法实施例中的网络设备或终端设备对应,由相应的模块或单元执行相应的步骤,例如通信单元(收发器)执行方法实施例中接收或发送的步骤,除发送、接收外的其它步骤可以由处理单元(处理器)执行。具体单元的功能可以参考相应的方法实施例。其中,处理器可以为一个或多个。
在本说明书中使用的术语“部件”、“模块”、“***”等用于表示计算机相关的实体、硬件、固件、硬件和软件的组合、软件、或执行中的软件。例如,部件可以是但不限于,在处理器上运行的进程、处理器、对象、可执行文件、执行线程、程序和/或计算机。通过图示,在计算设备上运行的应用和计算设备都可以是部件。一个或多个部件可驻留在进程和/或执行线程中,部件可位于一个计算机上和/或分布在两个或更多个计算机之间。此外,这些部件可从在上面存储有各种数据结构的各种计算机可读介质执行。部件可以例如根据具有一个或多个数据分组(例如来自与本地***、分布式***和/或网络间的部件的数据)的信号通过本地和/或远程进程来通信。
在本申请中,“至少一个”是指一个或者多个,“多个”是指两个或两个以上。“和/或”,描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B的情况,其中A、B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项(个)”或其类似表达,是指的这些项中的任意组合,包括单项(个)或复数项(个)的任意组合。例如,a、b或c中的至少一项(个),可以表示:a,b,c,a-b,a-c,b-c或a-b-c,其中a,b,c可以是单个,也可以是多个。
本领域普通技术人员可以意识到,结合本文中所公开的实施例描述的各种说明性逻辑块(illustrative logical block)和步骤(step),能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行,取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到,为描述的方便和简洁,上述描述的***、装置和单元的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
在本申请所提供的几个实施例中,应该理解到,所揭露的***、装置和方法,可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,所述单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个***,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信连接,可以是电性,机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外,在本申请各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括:U盘、移动硬盘、只读存储器(read-only memory,ROM)、随机 存取存储器(random access memory,RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述,仅为本申请的具体实施方式,但本申请的保护范围并不局限于此,任何熟悉本技术领域的技术人员在本申请揭露的技术范围内,可轻易想到变化或替换,都应涵盖在本申请的保护范围之内。因此,本申请的保护范围应以所述权利要求的保护范围为准。
Claims (26)
- 一种通信方法,其特征在于,包括:第一接入网设备向终端设备发送第一消息,所述第一消息用于指示所述终端设备进入去激活态;所述第一接入网设备向核心网设备发送第二消息,所述第二消息携带所述终端设备的上下文信息和第一安全验证参数,所述第一安全验证参数用于对所述终端设备进行安全验证;所述第一接入网设备接收来自第二接入网设备的第三消息,所述第三消息用于请求所述终端设备的上下文信息;所述第一接入网设备向所述第二接入网设备发送第四消息,所述第四消息用于指示所述第一接入网设备不向所述第二接入网设备提供所述上下文信息。
- 根据权利要求1所述的通信方法,其特征在于,所述第四消息还用于指示所述核心网设备的标识信息。
- 根据权利要求1或2所述的通信方法,其特征在于,所述第一接入网设备存储有所述终端设备的上下文信息,所述通信方法还包括:所述第一接入网设备根据所述第一安全验证参数,对所述终端设备进行安全验证;所述第一接入网设备根据所述第三消息,向所述第二接入网设备发送第四消息,包括:在所述安全验证通过的情况下,若所述第一接入网设备确定不向所述第二接入网设备提供所述上下文信息,所述第一接入网设备向所述第二接入网设备发送所述第四消息。
- 根据权利要求1至3中任一项所述的通信方法,其特征在于,所述第三消息携带所述终端设备的第二安全验证参数,所述第二安全验证参数用于对所述终端设备进行安全验证,所述通信方法还包括:所述第一接入网设备向所述核心网设备发送第五消息,所述第五消息携带所述第二安全验证参数,以更新所述核心网设备存储的安全验证参数。
- 根据权利要求1至4中任一项所述的通信方法,其特征在于,在所述第一接入网设备向核心网设备发送第二消息之后,所述通信方法还包括:所述第一接入网设备删除所述终端设备的上下文信息。
- 一种通信方法,其特征在于,包括:核心网设备接收来自第一接入网设备的第二消息,所述第二消息携带终端设备的上下文信息和第一安全验证参数,所述第一安全验证参数用于对所述终端设备进行安全验证;所述核心网设备保存所述上下文信息和所述第一安全验证参数。
- 根据权利要求6所述的通信方法,其特征在于,所述通信方法还包括:所述核心网设备接收来自第二接入网设备的第六消息,所述第六消息用于请求所述终端设备的上下文信息;所述核心网设备根据所述第一安全验证参数,对所述终端设备进行安全验证;在所述安全验证通过的情况下,所述核心网设备向所述第二接入网设备发送第七消息,所述第七消息携带所述上下文信息,或者,所述第七消息用于指示所述核心网设备不 向所述第二接入网设备提供所述上下文信息。
- 根据权利要求7所述的通信方法,其特征在于,所述第六消息携带所述终端设备的第二安全验证参数,所述第二安全验证参数用于对所述终端设备进行安全验证,所述通信方法还包括:所述核心网设备将安全验证参数从所述第一安全验证参数更新为所述第二安全验证参数。
- 一种通信方法,其特征在于,包括:第二接入网设备接收来自终端设备的第八消息,所述第八消息用于请求恢复连接;所述第二接入网设备向核心网设备发送第六消息,所述第六消息用于请求所述终端设备的上下文信息;所述第二接入网设备接收来自所述核心网设备的第七消息,所述第七消息携带所述上下文信息,或者,所述第七消息用于指示所述核心网设备不向所述第二接入网设备提供所述上下文信息。
- 根据权利要求9所述的通信方法,其特征在于,在所述第二接入网设备向核心网设备发送第六消息之前,所述通信方法还包括:所述第二接入网设备根据所述第八消息,向第一接入网设备发送第三消息,所述第三消息用于请求所述终端设备的上下文信息;所述第二接入网设备接收来自所述第一接入网设备的第四消息,所述第四消息用于指示所述第一接入网设备不向所述第二接入网设备提供所述上下文信息,且所述第四消息还用于指示所述核心网设备的标识信息;所述第二接入网设备向核心网设备发送第六消息,包括:所述第二接入网设备根据所述核心网设备的标识信息,向所述核心网设备发送所述第六消息。
- 根据权利要求9或10所述的通信方法,其特征在于,所述第五消息携带所述终端设备的第二安全验证参数,以便所述核心网设备将安全验证参数从第一安全验证参数更新为第二安全验证参数,所述第二安全验证参数用于对所述终端设备进行安全验证。
- 一种通信装置,其特征在于,包括:发送单元,用于向终端设备发送第一消息,所述第一消息用于指示所述终端设备进入去激活态;以及,向核心网设备发送第二消息,所述第二消息携带所述终端设备的上下文信息和第一安全验证参数,所述第一安全验证参数用于对所述终端设备进行安全验证;接收单元,用于接收来自第二接入网设备的第三消息,所述第三消息用于请求所述终端设备的上下文信息;所述发送单元还用于:向所述第二接入网设备发送第四消息,所述第四消息用于指示所述第一接入网设备不向所述第二接入网设备提供所述上下文信息。
- 根据权利要求12所述的通信装置,其特征在于,所述第四消息还用于指示所述核心网设备的标识信息。
- 根据权利要求12或13所述的通信装置,其特征在于,所述第一接入网设备存储有所述终端设备的上下文信息,所述通信装置还包括:处理单元,用于根据所述第一安全验证参数,对所述终端设备进行安全验证;所述发送单元具体用于:在所述安全验证通过的情况下,若所述通信装置确定不向所述第二接入网设备提供所述上下文信息,向所述第二接入网设备发送所述第四消息。
- 根据权利要求12至14中任一项所述的通信装置,其特征在于,所述第三消息携带所述终端设备的第二安全验证参数,所述第二安全验证参数用于对所述终端设备进行安全验证,所述发送单元具体用于:向所述核心网设备发送第五消息,所述第五消息携带所述第二安全验证参数,以更新所述核心网设备存储的安全验证参数。
- 根据权利要求12至15中任一项所述的通信装置,其特征在于,在向核心网设备发送第二消息之后,所述通信装置还包括:处理单元,用于删除所述终端设备的上下文信息。
- 一种通信装置,其特征在于,包括:接收单元,用于接收来自第一接入网设备的第二消息,所述第二消息携带终端设备的上下文信息和第一安全验证参数,所述第一安全验证参数用于对所述终端设备进行安全验证;处理单元,用于保存所述上下文信息和所述第一安全验证参数。
- 根据权利要求17所述的通信装置,其特征在于,所述接收单元还用于:接收来自第二接入网设备的第六消息,所述第六消息用于请求所述终端设备的上下文信息;所述处理单元还用于:根据所述第一安全验证参数,对所述终端设备进行安全验证;所述通信装置还包括:发送单元,用于在所述安全验证通过的情况下,向所述第二接入网设备发送第七消息,所述第七消息携带所述上下文信息,或者,所述第七消息用于指示所述核心网设备不向所述第二接入网设备提供所述上下文信息。
- 根据权利要求18所述的通信装置,其特征在于,所述第六消息携带所述终端设备的第二安全验证参数,所述第二安全验证参数用于对所述终端设备进行安全验证,所述处理单元还用于:将安全验证参数从所述第一安全验证参数更新为所述第二安全验证参数。
- 一种通信装置,其特征在于,包括:接收单元,用于接收来自终端设备的第八消息,所述第八消息用于请求恢复连接;发送单元,用于向核心网设备发送第六消息,所述第六消息用于请求所述终端设备的上下文信息;所述接收单元还用于:接收来自所述核心网设备的第七消息,所述第七消息携带所述上下文信息,或者,所述第七消息用于指示所述核心网设备不向所述第二接入网设备提供所述上下文信息。
- 根据权利要求20所述的通信装置,其特征在于,在向核心网设备发送第六消息之前,所述发送单元还用于:根据所述第八消息,向第一接入网设备发送第三消息,所述第三消息用于请求所述终端设备的上下文信息;所述接收单元还用于:接收来自所述第一接入网设备的第四消息,所述第四消息用于指示所述第一接入网设备不向所述第二接入网设备提供所述上下文信息,且所述第四消息还用于指示所述核心网设备的标识信息;所述发送单元还用于:根据所述核心网设备的标识信息,向所述核心网设备发送所述第六消息。
- 根据权利要求20或21所述的通信装置,其特征在于,所述第五消息携带所述终端设备的第二安全验证参数,以便所述核心网设备将安全验证参数从第一安全验证参数更新为第二安全验证参数,所述第二安全验证参数用于对所述终端设备进行安全验证。
- 一种通信装置,其特征在于,所述通信装置用于执行权利要求1至11中任一项所述的通信方法。
- 一种通信装置,其特征在于,包括:处理器,所述处理器与存储器耦合,所述存储器用于存储程序或指令,当所述程序或指令被所述处理器执行时,使得所述通信装置执行权利要求1至11中任一项所述的通信方法。
- 一种计算机可读介质,用于存储计算机程序,其特征在于,所述计算机程序包括用于实现权利要求1至11中任一项所述的通信方法的指令。
- 一种计算机程序产品,所述计算机程序产品中包括计算机程序代码,其特征在于,当所述计算机程序代码在计算机上运行时,使得计算机实现权利要求1至11中任一项所述的通信方法。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201980098712.2A CN114145073B (zh) | 2019-09-29 | 2019-09-29 | 通信方法和通信装置 |
EP19947380.2A EP4025007A4 (en) | 2019-09-29 | 2019-09-29 | COMMUNICATION METHOD AND COMMUNICATION DEVICE |
PCT/CN2019/109183 WO2021056563A1 (zh) | 2019-09-29 | 2019-09-29 | 通信方法和通信装置 |
US17/706,357 US11889310B2 (en) | 2019-09-29 | 2022-03-28 | Communication method and communication apparatus |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2019/109183 WO2021056563A1 (zh) | 2019-09-29 | 2019-09-29 | 通信方法和通信装置 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/706,357 Continuation US11889310B2 (en) | 2019-09-29 | 2022-03-28 | Communication method and communication apparatus |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2021056563A1 true WO2021056563A1 (zh) | 2021-04-01 |
Family
ID=75165369
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2019/109183 WO2021056563A1 (zh) | 2019-09-29 | 2019-09-29 | 通信方法和通信装置 |
Country Status (4)
Country | Link |
---|---|
US (1) | US11889310B2 (zh) |
EP (1) | EP4025007A4 (zh) |
CN (1) | CN114145073B (zh) |
WO (1) | WO2021056563A1 (zh) |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN116939505A (zh) * | 2022-03-29 | 2023-10-24 | 华为技术有限公司 | 一种通信方法及装置 |
WO2024026640A1 (en) * | 2022-08-01 | 2024-02-08 | Nokia Shanghai Bell Co., Ltd. | Apparatus, method, and computer program |
CN117858197A (zh) * | 2022-09-30 | 2024-04-09 | 华为技术有限公司 | 一种通信方法、通信装置及*** |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2018081956A1 (zh) * | 2016-11-02 | 2018-05-11 | 华为技术有限公司 | 一种信息发送方法、设备和*** |
WO2018206629A1 (en) * | 2017-05-09 | 2018-11-15 | Telefonaktiebolaget Lm Ericsson (Publ) | Amf eligibility for relay and reroute |
CN109803258A (zh) * | 2017-11-16 | 2019-05-24 | 华为技术有限公司 | 一种请求恢复连接的方法及装置 |
US20190174365A1 (en) * | 2016-08-12 | 2019-06-06 | Huawei Technologies Co., Ltd. | Communication method, apparatus, and system |
CN109936861A (zh) * | 2017-12-18 | 2019-06-25 | 华为技术有限公司 | 通信方法及接入网设备、终端设备、核心网设备 |
CN110149630A (zh) * | 2018-02-11 | 2019-08-20 | 华为技术有限公司 | 一种安全算法的协商、发送方法及装置 |
CN110225600A (zh) * | 2018-03-01 | 2019-09-10 | 华为技术有限公司 | 通信方法及装置 |
Family Cites Families (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101060712B (zh) * | 2006-04-20 | 2011-08-24 | 华为技术有限公司 | 无线连接建立方法 |
US9667485B2 (en) * | 2011-10-04 | 2017-05-30 | Juniper Networks, Inc. | Methods and apparatus for a self-organized layer-2 enterprise network architecture |
US9660804B2 (en) * | 2013-06-26 | 2017-05-23 | Nokia Technologies Oy | Methods and apparatus for generating keys in device-to-device communications |
US9774729B2 (en) * | 2015-03-26 | 2017-09-26 | Futurewei Technologies, Inc. | System and method for mobile core data services |
CN107615825B (zh) * | 2015-05-28 | 2021-01-05 | 瑞典爱立信有限公司 | 在不可信wlan接入上的多个pdn连接 |
CN108307389A (zh) * | 2016-09-26 | 2018-07-20 | 中兴通讯股份有限公司 | 数据安全保护方法、网络接入设备及终端 |
CN108260171A (zh) * | 2016-12-29 | 2018-07-06 | 维沃移动通信有限公司 | 一种业务请求处理方法和相关设备 |
WO2018128528A1 (ko) * | 2017-01-09 | 2018-07-12 | 엘지전자(주) | 무선 통신 시스템에서 pdu 세션 관리 방법 및 이를 위한 장치 |
CN115474247A (zh) * | 2017-01-30 | 2022-12-13 | 瑞典爱立信有限公司 | 连接模式期间5g中的安全性上下文处理的方法和装置 |
US10375665B2 (en) * | 2017-02-06 | 2019-08-06 | Huawei Technologies Co., Ltd. | Method and apparatus for supporting access control and mobility management |
US10645669B2 (en) * | 2017-02-10 | 2020-05-05 | Samsung Electronics Co., Ltd. | Method and apparatus for inactive mode operation in wireless communication system |
CN113423131B (zh) * | 2018-02-13 | 2022-11-11 | 华为技术有限公司 | 通信方法和装置 |
KR102143023B1 (ko) * | 2018-04-16 | 2020-08-10 | 텔레호낙티에볼라게트 엘엠 에릭슨(피유비엘) | 비활성 상태로부터의 rrc 재개를 위한 보안 핸들링 |
US11153792B2 (en) * | 2018-04-18 | 2021-10-19 | Qualcomm Incorporated | Signaling for inactive mobility |
CN110636572A (zh) * | 2018-06-21 | 2019-12-31 | 华为技术有限公司 | 通信方法及装置 |
WO2020010515A1 (en) * | 2018-07-10 | 2020-01-16 | Apple Inc. | Identity-based message integrity protection and verification for wireless communication |
WO2020060007A1 (ko) * | 2018-09-17 | 2020-03-26 | 엘지전자 주식회사 | 5g 이동통신에서 pdu 세션을 핸들링하는 방법 및 무선 기기 |
CN113302951A (zh) * | 2019-01-14 | 2021-08-24 | 苹果公司 | 5g***中的车联万物pc5能力的管理 |
CN112087747A (zh) * | 2019-06-14 | 2020-12-15 | 苹果公司 | 改善的rrc过程安全性 |
-
2019
- 2019-09-29 EP EP19947380.2A patent/EP4025007A4/en active Pending
- 2019-09-29 CN CN201980098712.2A patent/CN114145073B/zh active Active
- 2019-09-29 WO PCT/CN2019/109183 patent/WO2021056563A1/zh unknown
-
2022
- 2022-03-28 US US17/706,357 patent/US11889310B2/en active Active
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20190174365A1 (en) * | 2016-08-12 | 2019-06-06 | Huawei Technologies Co., Ltd. | Communication method, apparatus, and system |
WO2018081956A1 (zh) * | 2016-11-02 | 2018-05-11 | 华为技术有限公司 | 一种信息发送方法、设备和*** |
WO2018206629A1 (en) * | 2017-05-09 | 2018-11-15 | Telefonaktiebolaget Lm Ericsson (Publ) | Amf eligibility for relay and reroute |
CN109803258A (zh) * | 2017-11-16 | 2019-05-24 | 华为技术有限公司 | 一种请求恢复连接的方法及装置 |
CN109936861A (zh) * | 2017-12-18 | 2019-06-25 | 华为技术有限公司 | 通信方法及接入网设备、终端设备、核心网设备 |
CN110149630A (zh) * | 2018-02-11 | 2019-08-20 | 华为技术有限公司 | 一种安全算法的协商、发送方法及装置 |
CN110225600A (zh) * | 2018-03-01 | 2019-09-10 | 华为技术有限公司 | 通信方法及装置 |
Non-Patent Citations (2)
Title |
---|
See also references of EP4025007A4 * |
ZTE, SANECHIPS: "Discussion on Tracking Area Management in NTN", 3GPP DRAFT; R3-185610 DISCUSSION ON TRACKING AREA MANAGEMENT IN NTN, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Chengdu, China; 20181008 - 20181012, 29 September 2018 (2018-09-29), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051528885 * |
Also Published As
Publication number | Publication date |
---|---|
CN114145073B (zh) | 2024-04-12 |
EP4025007A1 (en) | 2022-07-06 |
CN114145073A (zh) | 2022-03-04 |
US11889310B2 (en) | 2024-01-30 |
US20220217538A1 (en) | 2022-07-07 |
EP4025007A4 (en) | 2022-09-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN111491338B (zh) | 上下文存储方法及装置 | |
US11889310B2 (en) | Communication method and communication apparatus | |
US20220248268A1 (en) | Method for relay transmission, relay user equipment, and remote user equipment | |
WO2021238766A1 (zh) | 一种通信方法及装置 | |
WO2022027200A1 (zh) | 一种通信方法及装置 | |
US20230224797A1 (en) | Network access method, terminal device, and network device | |
CN113727342A (zh) | 网络注册的方法和装置 | |
WO2021027660A1 (zh) | 无线通信的方法和通信装置 | |
CN116965102A (zh) | 无线通信方法、终端设备和网络设备 | |
US20230107139A1 (en) | Relay discovery method and terminal | |
CN117544213A (zh) | 一种通信方法和装置 | |
CN116491135A (zh) | 授权配置方法、终端设备和网络设备 | |
US20240251241A1 (en) | Method for ue parameter update | |
WO2024026640A1 (en) | Apparatus, method, and computer program | |
US11924893B2 (en) | Method for establishing connection, and terminal device | |
US20230370922A1 (en) | Method for entering connected mode, and terminal device | |
US20240073762A1 (en) | Communication method, apparatus, and system | |
WO2023102783A1 (zh) | 能力指示方法、终端设备和网络设备 | |
WO2023216242A1 (zh) | 连接配置方法和终端 | |
WO2022099475A1 (zh) | 会话管理方法、终端设备和网络设备 | |
WO2022032453A1 (zh) | 寻呼优化方法和网络设备 | |
WO2022141025A1 (zh) | 用于传输数据的方法与装置 | |
CN117223356A (zh) | 消息接收方法、装置 | |
WO2024022573A1 (en) | Optimize initial access latency | |
CN117204021A (zh) | 时间信息确定方法及装置、通信设备、通信***、存储介质 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 19947380 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2019947380 Country of ref document: EP Effective date: 20220330 |