WO2022021984A1 - 一种数据传输方法以及相关设备 - Google Patents

一种数据传输方法以及相关设备 Download PDF

Info

Publication number
WO2022021984A1
WO2022021984A1 PCT/CN2021/091332 CN2021091332W WO2022021984A1 WO 2022021984 A1 WO2022021984 A1 WO 2022021984A1 CN 2021091332 W CN2021091332 W CN 2021091332W WO 2022021984 A1 WO2022021984 A1 WO 2022021984A1
Authority
WO
WIPO (PCT)
Prior art keywords
network device
key
downlink data
message
pdcp entity
Prior art date
Application number
PCT/CN2021/091332
Other languages
English (en)
French (fr)
Inventor
张大刚
郑志龙
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP21850474.4A priority Critical patent/EP4185069A4/en
Priority to KR1020237005497A priority patent/KR20230040361A/ko
Publication of WO2022021984A1 publication Critical patent/WO2022021984A1/zh
Priority to US18/159,188 priority patent/US20230164548A1/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/30Security of mobile devices; Security of mobile applications
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/20Manipulation of established connections
    • H04W76/27Transitions between radio resource control [RRC] states
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/03Protecting confidentiality, e.g. by encryption
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/04Key management, e.g. using generic bootstrapping architecture [GBA]
    • H04W12/043Key management, e.g. using generic bootstrapping architecture [GBA] using a trusted network node as an anchor
    • H04W12/0431Key distribution or pre-distribution; Key agreement
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/20Manipulation of established connections
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/30Connection release

Definitions

  • the embodiments of the present application relate to the field of communications, and in particular, to a data transmission method and related equipment.
  • Option 3X is a commonly used networking mode in a non-standalone (NSA) mode.
  • the core network adopts the LTE core network
  • the access network equipment adopts the LTE access network equipment or the NR access network equipment.
  • NR users can use LTE access network equipment to exchange access signaling with the LTE core network through the LTE S1-C interface, and the data plane is offloaded to NR RLC and LTE RLC through NR PDCP.
  • the carrier often changes due to the movement of the terminal equipment.
  • the terminal device needs to change the key, and needs to use the changed key to rebuild the PDCP entity, so that the PDCP entity rebuilt by the terminal device uses the changed key to encrypt and decrypt data.
  • the terminal device cannot receive data from the network device during the process of re-establishing the PDCP entity, network delay will occur, resulting in a brief interruption of data services during the secondary carrier change process, affecting user experience.
  • the embodiments of the present application provide a data transmission method and related equipment, which are used to reduce the network delay generated by the terminal equipment when the carrier is changed, thereby reducing the probability of data service interruption caused by the change of the carrier.
  • an embodiment of the present application provides a data transmission method, and the data transmission method involves a primary network device, a secondary network device, and a terminal device.
  • the primary network device When the carrier is changed (for example, adding a secondary network device, deleting a secondary network device, or changing a secondary network device), the primary network device will send a first message to the terminal device.
  • the terminal device uses the key of the main network device to encrypt and decrypt data before the carrier is changed, and the first message is used to instruct the terminal device to still use the key of the main network device stored by the terminal device after the carrier is changed. Encrypt and decrypt data.
  • the terminal device when the carrier is changed, because the terminal device has stored the key of the primary network device, and after the carrier is changed, the terminal device still uses the key of the primary network device. That is to say, during the carrier change, the terminal device does not change the key, and the terminal device does not need to rebuild the PDCP entity. Therefore, when the carrier is changed, the network delay caused by the re-establishment of the PDCP entity of the terminal equipment can be reduced, thereby reducing the probability of data service interruption caused by the change of the carrier.
  • the first message is a radio resource control RRC reconfiguration message
  • the RRC reconfiguration message carries first indication information
  • the first indication information is used to indicate that the The key of the main network device is used to encrypt and decrypt data.
  • the aforementioned first message is to instruct the terminal device to still use the key of the main network device through the first indication information, and there is no need to send the key of the main network device to the terminal device, which is beneficial to ensure communication security.
  • the method before the primary network device sends the first message to the terminal device, the method further includes: the primary network device receives the secondary network device A second message sent, where the second message is used to instruct the secondary network device to confirm that a change will occur, and the second message carries the first indication information configured by the secondary network device.
  • the first indication information sent by the primary network device to the terminal device is carried by the secondary network device in the second message. After the primary network device receives the aforementioned first indication information, it will use the first indication information forwarded to the end device.
  • the method before the primary network device receives the second message sent by the secondary network device, the method further includes: the primary network device sends the message to the primary network device.
  • the secondary network device sends a third message, where the third message carries the key of the primary network device, and the third message is used to instruct the secondary network device to use the key of the primary network device to encrypt and decrypt data.
  • the secondary network device before the secondary network device sends the aforementioned first indication information to the primary network device, the secondary network device receives the master key from the primary network device. Therefore, the secondary network device will use the key of the primary network device to create the PDCP entity of the secondary network device in the subsequent process. Since both the secondary network device and the terminal device use the key of the primary network device, in the subsequent data exchange process between the secondary network device and the terminal device, data transmission interruption caused by inconsistent keys can be avoided.
  • the foregoing carrier change process adds a secondary network device to a primary network device
  • the foregoing third message is a secondary carrier addition request
  • the The secondary carrier addition request is used to request to add the secondary network device as a secondary carrier
  • the aforementioned second message is a secondary carrier addition request response
  • the secondary carrier addition request response is used to instruct the secondary network device to confirm the addition, and the secondary network device will use
  • the key of the master station is encrypted and decrypted.
  • an optional embodiment of the foregoing third message and second message is proposed when the primary network device adds a secondary network device. That is to say, the key of the primary network device may be carried in the secondary carrier addition request, and the aforesaid first indication information may be carried in the secondary carrier addition request response.
  • the method further includes: the primary network device controlling the PDCP entity of the primary network device to send the data to the RLC entity of the primary network device and the RLC entity controlling the main network device sends the downlink data packet to the terminal device, and the PDCP entity of the terminal device uses the key of the main network device to encrypt and decrypt the downlink data packet.
  • the process of transmitting the downlink data packet from the RLC entity of the main network device to the PDCP entity of the terminal device it will also go through the MAC entity of the main network device, the physical layer of the main network device, and the physical layer of the terminal device. , the MAC entity of the terminal device, and the RLC entity of the terminal device, etc.
  • the embodiments of the present application only limit the aforementioned RLC entity of the main network device to be able to transmit downlink data packets to the PDCP entity of the terminal device, and do not limit the specific transmission process between the two entities.
  • the terminal device since the primary network device, the terminal device, and the secondary network device all use the key of the primary network device, when the PDCP entity of the secondary network device has not been activated, the terminal device can use the key of the primary network device Receive downlink data packets from the RLC entity of the primary network device through the PDCP entity of the terminal device. Because the terminal device can also receive downlink data packets when the PDCP entity of the secondary network device has not been activated, the terminal device will not cause delay due to the reconstruction of the PDCP entity, which can effectively reduce the probability of data transmission interruption.
  • the primary network device when the foregoing carrier change process is initiated by the primary network device to delete the secondary network device, the primary network device sends the first Before a message, the method further includes: the primary network device sends a secondary carrier release request to the secondary network device, where the secondary carrier release request is used to notify the secondary network device to release; the primary network device receives the secondary carrier release request sent by the secondary network device. A carrier release response, where the secondary carrier release response is used to instruct the secondary network device to confirm the release.
  • the primary network device when the foregoing carrier change process is initiated by the secondary network device to delete the secondary network device, the primary network device sends a message to the terminal device. Before the first message, the method further includes: the primary network device receives a secondary carrier release request sent by the secondary network device, where the secondary carrier release request is used to request to release the secondary network device; the primary network device sends a secondary carrier release request to the secondary network device A carrier release confirmation message, the secondary carrier release confirmation message is used to indicate that the secondary network device is allowed to release.
  • the data transmission method It also includes: the primary network device controls the RLC entity of the primary network device to receive the downlink data packet from the PDCP entity of the secondary network device, and the PDCP entity of the secondary network device encrypts and decrypts the downlink data packet using the key of the primary network device; The main network device controls the RLC entity of the main network device to send the downlink data packet to the terminal device, and the PDCP entity of the terminal device uses the key of the main network device to encrypt and decrypt the downlink data packet.
  • the secondary network device will be deleted, and the terminal device needs to change from the state of simultaneously receiving downlink data packets from the RLC entity from the primary network device and downlink data packets from the RLC entity from the secondary network device to only from the primary network device
  • the RLC entity receives downlink data packets. Because, before and after the change of the secondary network device, the terminal device has always used the key of the primary network device, so even if the RLC entity of the secondary network device no longer sends downlink data packets to the PDCP entity of the terminal device, the The RLC entity of the primary network device still sends downlink data packets to the PDCP entity of the terminal device, and the PDCP entity of the terminal device can encrypt and decrypt data by using the key of the primary network device. Therefore, the time when the terminal equipment cannot receive the downlink data packet can be shortened, and the time delay caused by the inability to receive the downlink data packet can be reduced.
  • the foregoing carrier change process is a process of changing from one secondary network device to another secondary network device
  • the secondary network device can be understood as the target secondary network device, that is, the secondary network device that performs data interaction between the primary network device and the terminal device after the change. Before the change, it is the source and secondary network devices that perform data interaction with the aforementioned primary network device and terminal device.
  • the change from the source secondary network device to the target secondary network device is used as an example for description.
  • the aforementioned second message is a response to the secondary carrier addition request, and the second message is used to instruct the target secondary network device to confirm the addition, and the target secondary network device will use the key of the primary station to perform encryption and decryption.
  • the primary network device when a source secondary network device initiates a change to a target secondary network device, the primary network device sends a message to the target secondary network device. Before the third message, the method further includes: the primary network device receives a secondary carrier change request sent by the source secondary network device, the carrier change request carries the identification information of the target secondary network device, and the secondary carrier change request is used to indicate The source secondary network device is changed to the target secondary network device.
  • the primary network device when the primary network device initiates the change to the source secondary network device, the primary network device receives the data sent by the target secondary network device.
  • the method further includes: the primary network device sends a carrier release request to the source secondary network device, where the carrier release request is used to request to release the source secondary network device; the primary network device receives the transmission from the source secondary network device The carrier release request response is used to confirm the release.
  • the data transmission method further includes: the primary network device controls the RLC entity of the primary network device to receive downlink data packets from the PDCP entity of the source secondary network device, and the PDCP entity of the source secondary network device adopts the password of the primary network device. key to encrypt and decrypt the downlink data packet; the main network device controls the RLC entity of the main network device to send the downlink data packet to the terminal device, and the PDCP entity of the terminal device uses the key of the main network device to encrypt and decrypt the downlink data Bag.
  • the source auxiliary network device will be deleted and the target auxiliary network device will be added. Since the newly added target auxiliary network device has not been activated, the downlink data packet cannot be immediately sent to the terminal device. Therefore, the terminal device needs to change from the state of simultaneously receiving downlink data packets from the RLC entity of the primary network device and downlink data packets from the RLC entity of the source secondary network device to only receiving downlink data packets from the RLC entity of the primary network device. Because, before and after the change of the source and secondary network equipment, the terminal equipment has always used the key of the primary network equipment.
  • the RLC entity of the aforementioned source and secondary network equipment no longer sends downlink data packets to the PDCP entity of the terminal equipment
  • the RLC entity of the primary network device still sends downlink data packets to the PDCP entity of the terminal device, and the PDCP entity of the terminal device can encrypt and decrypt data by using the key of the primary network device. Therefore, the time when the terminal equipment cannot receive the downlink data packet can be shortened, and the time delay caused by the inability to receive the downlink data packet can be reduced.
  • an embodiment of the present application provides a data transmission method, where the data transmission method involves a primary network device, a secondary network device, and a terminal device.
  • the carrier is changed (for example, adding a secondary network device, deleting a secondary network device, or changing a secondary network device)
  • the terminal device receives the first message sent by the primary network device, and the terminal device adopts the primary network device's
  • the key is used to encrypt and decrypt data
  • the first message is used to instruct the terminal device to use the key of the main network device stored by the terminal device to encrypt and decrypt data after the carrier is changed.
  • the terminal device when the carrier is changed, because the terminal device has stored the key of the primary network device, and after the carrier is changed, the terminal device still uses the key of the primary network device. That is to say, during the carrier change, the terminal device does not change the key, and the terminal device does not need to rebuild the PDCP entity. Therefore, when the carrier is changed, the network delay caused by the re-establishment of the PDCP entity of the terminal equipment can be reduced, thereby reducing the probability of data service interruption caused by the change of the carrier.
  • the first message is a radio resource control RRC reconfiguration message
  • the RRC reconfiguration message carries first indication information
  • the first indication information is used to indicate that the The key of the main network device is used to encrypt and decrypt data.
  • the aforementioned first message is to instruct the terminal device to still use the key of the main network device through the first indication information, and there is no need to send the key of the main network device to the terminal device, which is beneficial to ensure communication security.
  • the method further includes: the terminal device controls the terminal The PDCP entity of the device receives the downlink data packet from the RLC entity of the main network device, the downlink data packet comes from the PDCP entity of the main network device, and the PDCP entity of the terminal device uses the key of the main network device to encrypt and decrypt the downlink data Bag.
  • the terminal device since the primary network device, the terminal device, and the secondary network device all use the key of the primary network device, when the PDCP entity of the secondary network device has not been activated, the terminal device can use the key of the primary network device Receive downlink data packets from the RLC entity of the primary network device through the PDCP entity of the terminal device. Because the terminal device can also receive downlink data packets when the PDCP entity of the secondary network device has not been activated, the terminal device will not cause delay due to the reconstruction of the PDCP entity, which can effectively reduce the probability of data transmission interruption.
  • the method further includes: the terminal device controlling the terminal device's The PDCP entity receives the downlink data packet from the RLC entity of the primary network device, the downlink data packet is from the PDCP entity of the secondary network device, the secondary network device is the network device to be released, the PDCP entity of the terminal device and the secondary network device All PDCP entities use the key of the main network device to encrypt and decrypt the downlink data packet.
  • the secondary network device will be deleted, and the terminal device needs to change from the state of simultaneously receiving downlink data packets from the RLC entity from the primary network device and downlink data packets from the RLC entity from the secondary network device to only from the primary network device
  • the RLC entity receives downlink data packets. Because, before and after the change of the secondary network device, the terminal device has always used the key of the primary network device, so even if the RLC entity of the secondary network device no longer sends downlink data packets to the PDCP entity of the terminal device, the The RLC entity of the primary network device still sends downlink data packets to the PDCP entity of the terminal device, and the PDCP entity of the terminal device can encrypt and decrypt data by using the key of the primary network device. Therefore, the time when the terminal equipment cannot receive the downlink data packet can be shortened, and the time delay caused by the inability to receive the downlink data packet can be reduced.
  • the aforementioned carrier change process is a process of changing from one secondary network device to another secondary network device
  • the aforementioned secondary network device may be understood as the source secondary network device.
  • an embodiment of the present application provides a data transmission method, where the data transmission method involves a primary network device, a secondary network device, and a terminal device.
  • the primary network device initiates adding a secondary network device
  • the secondary network device receives a third message sent by the primary network device, where the third message carries the key of the primary network device, and the third message is used to instruct the secondary network device to use the The key of the primary network device encrypts and decrypts the data; then, the secondary network device sends a second message to the primary network device, the second message is used to instruct the secondary network device to confirm that the change will occur, and the second message carries the The first indication information configured by the secondary network device, where the first indication information is used to indicate that the key of the primary network device is used to encrypt and decrypt data.
  • the foregoing third message is a secondary carrier addition request, and the secondary carrier addition request is used to request to add the secondary network device as a secondary carrier;
  • the foregoing second message is a secondary carrier An add request response, where the secondary carrier add request response is used to instruct the secondary network device to confirm the addition, and the secondary network device will use the key of the primary station to perform encryption and decryption.
  • the method further includes: the secondary network device uses the key of the primary network device to create a PDCP entity.
  • the secondary network device since the secondary network device uses the key of the primary network device to create the PDCP entity, the downlink data packets encrypted by the PDCP entity of the secondary network device can be transferred to the terminal device using the primary network device through multiple entity streams.
  • the PDCP entity of the key of the network device Therefore, it is not necessary for the terminal device to rebuild the PDCP entity, which can shorten the time that the terminal device cannot receive the downlink data packet, and can reduce the time delay caused by the inability to receive the downlink data packet.
  • an embodiment of the present application provides a data transmission method, where the data transmission method involves a primary network device, a secondary network device, and a terminal device.
  • the data transmission method includes: the secondary network device controls the PDCP entity of the secondary network device to send downlink data packets to the RLC entity of the primary network device , the PDCP entity of the secondary network device uses the key of the primary network device to encrypt and decrypt the downlink data packet.
  • the secondary network device when it learns that it will be deleted, it can buffer a part of downlink data packets in the RLC entity of the primary network device, so that the primary network device controls the RLC entity to send the aforementioned downlink data packets to the terminal device. Since both the PDCP entity of the terminal device and the PDCP entity of the secondary network device use the key of the primary network device, the PDCP entity of the terminal device can decrypt the aforementioned downlink data packets, which can reduce network delay and avoid terminal Equipment business interruption.
  • the secondary network device controls the PDCP entity of the secondary network device to the primary network device's PDCP entity.
  • the method further includes: the secondary network device receives a secondary carrier release request sent by the primary network device, where the secondary carrier release request is used to notify the secondary network device to release; the secondary network device reports to the primary network device The network device sends a secondary carrier release response, where the secondary carrier release response is used to instruct the secondary network device to confirm the release.
  • the secondary network device controls the secondary network Before the PDCP entity of the device sends the downlink data packet to the RLC entity of the primary network device, the method further includes: the secondary network device sends a secondary carrier release request to the primary network device, where the secondary carrier release request is used to request to release the secondary network device ; the secondary network device receives the secondary carrier release confirmation message sent by the primary network device, where the secondary carrier release confirmation message is used to indicate that the secondary network device is allowed to release.
  • the secondary network device when the source secondary network device initiates the change to the target secondary network device, the secondary network device is the source secondary network device; the Before the secondary network device controls the PDCP entity of the secondary network device to send the downlink data packet to the RLC entity of the primary network device, the method further includes: the secondary network device sends a carrier change request to the primary network device, where the carrier change request carries the target secondary network device. Identification information of the network device, the secondary carrier change request is used to instruct the source secondary network device to be changed to the target secondary network device, so that the primary network device sends the key of the primary network device to the target secondary network device.
  • the secondary network device when the primary network device initiates the change to the source secondary network device, the secondary network device is the source secondary network device; the secondary network device is the source secondary network device; Before the network device controls the PDCP entity of the secondary network device to send the downlink data packet to the RLC entity of the primary network device, the method further includes: the secondary network device receives a carrier release request sent by the primary network device, where the carrier release request is used to request Release the source secondary network device.
  • an embodiment of the present application provides a primary network device, including: a sending module configured to send a first message to a terminal device, where the terminal device adopts the key of the primary network device before the carrier is changed Encrypt and decrypt data, the first message is used to instruct the terminal device to use the key of the main network device stored by the terminal device to encrypt and decrypt data after the carrier is changed.
  • the first message is a radio resource control RRC reconfiguration message
  • the RRC reconfiguration message carries first indication information, where the first indication information is used to indicate that the The key of the main network device is used to encrypt and decrypt data.
  • the primary network device further includes: a receiving module for receiving a second message sent by the secondary network device, where the second message is used for Indicates that the confirmation of the secondary network device will be changed, and the second message carries the first indication information configured by the secondary network device.
  • the sending module is further configured to send a third message to the secondary network device, where the third message carries the primary network device The third message is used to instruct the secondary network device to use the key of the primary network device to encrypt and decrypt data.
  • the aforementioned third message is a secondary carrier addition request, and the secondary carrier addition request is used to request to add the secondary network device as a secondary carrier;
  • the aforementioned second message is a secondary carrier An add request response, where the secondary carrier add request response is used to instruct the secondary network device to confirm the addition, and the secondary network device will use the key of the primary station to perform encryption and decryption.
  • the primary network device further includes a processing module, and the processing module is configured to control the PDCP entity of the primary network device to report to the primary network device.
  • the RLC entity of the network device sends the downlink data packet
  • the RLC entity that controls the main network device sends the downlink data packet to the terminal device
  • the PDCP entity of the terminal device uses the key of the main network device to encrypt and decrypt the downlink data. Bag.
  • the sending module when the primary network device initiates deletion of the secondary network device, is further configured to send a secondary carrier release request to the secondary network device , the secondary carrier release request is used to notify the secondary network device to release; the receiving module is further used to receive a secondary carrier release response sent by the secondary network device, where the secondary carrier release response is used to instruct the secondary network device to confirm the release.
  • the receiving module when the secondary network device initiates deletion of the secondary network device, is further configured to receive the secondary carrier sent by the secondary network device A release request, the secondary carrier release request is used to request the release of the secondary network device; the sending module is further configured to send a secondary carrier release confirmation message to the secondary network device, where the secondary carrier release confirmation message is used to indicate that the secondary network device is allowed to be released to release.
  • the processing module is further configured to control the RLC entity of the primary network device to receive downlink data from the PDCP entity of the secondary network device packet, the PDCP entity of the secondary network device uses the key of the primary network device to encrypt and decrypt the downlink data packet; the RLC entity that controls the primary network device sends the downlink data packet to the terminal device, and the PDCP entity of the terminal device uses The key of the main network device encrypts and decrypts the downlink data packet.
  • the secondary network device is the target secondary network device
  • the second message is the secondary carrier addition request response
  • the second message is used to instruct the target secondary network device to confirm the addition
  • the target secondary network device will use the primary station's key for encryption and decryption.
  • the receiving module is further configured to receive a secondary carrier change request sent by the source secondary network device, where the carrier change request carries the information of the target secondary network device. Identification information, where the secondary carrier change request is used to instruct the source secondary network device to be changed to the target secondary network device.
  • the foregoing carrier change process is a process of changing from one secondary network device to another secondary network device
  • the foregoing implementation manner The secondary network device can be understood as the target secondary network device
  • the second message is the secondary carrier add request response
  • the second message is used to instruct the target secondary network device to confirm the addition
  • the target secondary network device will use the primary station. key for encryption and decryption.
  • the sending module is further configured to send a carrier release request to the source secondary network device, where the carrier release request is used to request to release the source secondary network device ;
  • the receiving module is further configured to receive a carrier release request response sent by the source secondary network device, and the carrier release request response is used to confirm the release.
  • the processing module is further configured to control the RLC entity of the primary network device to receive the downlink from the PDCP entity of the source secondary network device data packet, the PDCP entity of the source secondary network device uses the key of the primary network device to encrypt and decrypt the downlink data packet; the RLC entity that controls the primary network device sends the downlink data packet to the terminal device, and the PDCP of the terminal device The entity uses the key of the main network device to encrypt and decrypt the downlink data packet.
  • an embodiment of the present application provides a terminal device, including: a receiving module configured to receive a first message sent by a primary network device, where the terminal device uses the key of the primary network device to perform encryption and decryption before the carrier is changed data, the first message is used to instruct the terminal device to use the key of the main network device stored by the terminal device to encrypt and decrypt data after the carrier is changed.
  • the first message is a radio resource control RRC reconfiguration message
  • the RRC reconfiguration message carries first indication information, where the first indication information is used to indicate that the The key of the main network device is used to encrypt and decrypt data.
  • the processing module in the terminal device is used to control the PDCP of the terminal device
  • the entity receives the downlink data packet from the RLC entity of the main network device, the downlink data packet comes from the PDCP entity of the main network device, and the PDCP entity of the terminal device uses the key of the main network device to encrypt and decrypt the downlink data packet.
  • the processing module is further configured to control the PDCP entity of the terminal device to receive a downlink data packet from the RLC entity of the primary network device, the downlink data packet from The PDCP entity of the secondary network device, which is the network device to be released, both the PDCP entity of the terminal device and the PDCP entity of the secondary network device use the key of the primary network device to encrypt and decrypt the downlink data packet.
  • an embodiment of the present application provides a secondary network device, including: a receiving module configured to receive a third message sent by a primary network device, where the third message carries a key of the primary network device, the third message used to instruct the secondary network device to use the key of the primary network device to encrypt and decrypt data; the sending module is used to send a second message to the primary network device, where the second message is used to instruct the secondary network device to confirm that the change will occur , the second message carries first indication information configured by the secondary network device, where the first indication information is used to indicate that the key of the primary network device is used to encrypt and decrypt data.
  • the aforementioned third message is a secondary carrier addition request, and the secondary carrier addition request is used to request to add the secondary network device as a secondary carrier;
  • the aforementioned second message is a secondary carrier An add request response, where the secondary carrier add request response is used to instruct the secondary network device to confirm the addition, and the secondary network device will use the key of the primary station to perform encryption and decryption.
  • the secondary network device further includes: a processing module configured to create a PDCP entity by using the key of the primary network device.
  • an embodiment of the present application provides a secondary network device, including: a processing module configured to control a PDCP entity of the secondary network device to send a downlink data packet to an RLC entity of the primary network device, and the PDCP entity of the secondary network device The downlink data packet is encrypted and decrypted using the key of the main network device.
  • the sending module is further configured to send the message to the secondary network device.
  • the primary network device sends a secondary carrier release request, where the secondary carrier release request is used to request to release the secondary network device.
  • the secondary network device further includes a receiving module configured to receive the secondary carrier release confirmation message sent by the primary network device, where the secondary carrier release confirmation message is used to indicate that the secondary network device is allowed to release.
  • the secondary network device when the source secondary network device initiates the change to the target secondary network device, the secondary network device is the source secondary network device; the The sending module is further configured to send a carrier change request to the primary network device, where the carrier change request carries the identification information of the target secondary network device, and the secondary carrier change request is used to instruct the source secondary network device to be changed to the target secondary network device , so that the primary network device sends the key of the primary network device to the target secondary network device.
  • the secondary network device when the primary network device initiates the change to the source secondary network device, the secondary network device is the source secondary network device; the receiving module , and is further configured to receive a carrier release request sent by the primary network device, where the carrier release request is used to request to release the source secondary network device.
  • an embodiment of the present application provides a communication device, where the communication device may be the main network device in the foregoing embodiments, or may be a chip in the main network device.
  • the communication device may include a processing module and a transceiver module.
  • the processing module may be a processor, and the transceiver module may be a transceiver;
  • the main network device may further include a storage module, and the storage module may be a memory; the storage module is used for storing instructions , the processing module executes the instructions stored in the storage module, so that the primary network device executes the method in the first aspect or any one of the implementation manners of the first aspect.
  • the processing module may be a processor, and the transceiver module may be an input/output interface, a pin or a circuit, etc.; the processing module executes the instructions stored in the storage module to make The primary network device performs the method of the first aspect or any one of the embodiments of the first aspect.
  • the storage module may be a storage module (eg, a register, a cache, etc.) within the chip, or a storage module (eg, a read-only memory, a random access memory, etc.) located outside the chip in the main network device.
  • an embodiment of the present application provides a communication device, where the communication device may be the terminal device in the foregoing embodiments, or may be a chip in the terminal device.
  • the communication device may include a processing module and a transceiver module.
  • the processing module may be a processor, and the transceiver module may be a transceiver;
  • the terminal device may further include a storage module, and the storage module may be a memory; the storage module is used for storing instructions, the The processing module executes the instructions stored in the storage module, so that the terminal device executes the method in the second aspect or any one of the implementation manners of the second aspect.
  • the processing module may be a processor, and the transceiver module may be an input/output interface, a pin or a circuit, etc.; the processing module executes the instructions stored in the storage module, so that the The terminal device performs the method in the second aspect or any one of the implementation manners of the second aspect.
  • the storage module may be a storage module (eg, register, cache, etc.) within the chip, or may be a storage module (eg, read-only memory, random access memory, etc.) located outside the chip in the terminal device.
  • an embodiment of the present application provides a communication device, and the communication device may be the auxiliary network device in the foregoing embodiments, or may be a chip in the auxiliary network device.
  • the communication device may include a processing module and a transceiver module.
  • the processing module may be a processor, and the transceiver module may be a transceiver;
  • the auxiliary network device may further include a storage module, and the storage module may be a memory; the storage module is used for storing instructions , the processing module executes the instructions stored in the storage module, so that the secondary network device executes the third aspect or the method in any one of the third aspect, or executes the fourth aspect or any one of the fourth aspect method in one embodiment.
  • the processing module may be a processor, and the transceiver module may be an input/output interface, a pin or a circuit, etc.; the processing module executes the instructions stored in the storage module, so that the The secondary network device performs the third aspect or the method in any implementation manner of the third aspect, or performs the fourth aspect or the method in any implementation manner of the fourth aspect.
  • the storage module may be a storage module (eg, a register, a cache, etc.) within the chip, or a storage module (eg, a read-only memory, a random access memory, etc.) located outside the chip in the auxiliary network device.
  • the aforementioned secondary network device may be the source secondary network device or the target secondary network device in the foregoing implementation manner.
  • the present application provides a communication device, which may be an integrated circuit chip.
  • the integrated circuit chip includes a processor.
  • the processor is coupled to a memory for storing programs or instructions which, when executed by the processor, cause the communication device to perform a method as in the first aspect or any embodiment of the first aspect .
  • the present application provides a communication device, which may be an integrated circuit chip.
  • the integrated circuit chip includes a processor.
  • the processor is coupled to a memory for storing programs or instructions which, when executed by the processor, cause the communication device to perform a method as in the second aspect or any embodiment of the second aspect .
  • the present application provides a communication device, which may be an integrated circuit chip.
  • the integrated circuit chip includes a processor.
  • the processor is coupled to a memory for storing programs or instructions which, when executed by the processor, cause the communication device to perform the method as in the third aspect or any one of the embodiments of the third aspect .
  • the present application provides a communication device, which may be an integrated circuit chip.
  • the integrated circuit chip includes a processor.
  • the processor is coupled to a memory for storing programs or instructions which, when executed by the processor, cause the communication device to perform the method as in the fourth aspect or any one of the embodiments of the fourth aspect .
  • embodiments of the present application provide a computer program product containing instructions, which, when run on a computer, enables the computer to perform the aforementioned first to fourth aspects and various implementations of the aforementioned aspects The method described in any one of the embodiments.
  • embodiments of the present application provide a computer-readable storage medium, including instructions, when the instructions are run on a computer, so that the computer executes the first to fourth aspects, and the above-mentioned aspects.
  • an embodiment of the present application provides a communication system, where the communication system includes the first aspect and the communication device in any implementation manner of the first aspect, and any one of the second aspect and the second aspect.
  • the embodiments of the present application have the following advantages:
  • the primary network device when the carrier is changed, the primary network device will send a first message to the terminal device, and the first message will instruct the terminal device to use the key of the primary network device used by the terminal device before the carrier is changed to encrypt and decrypt data. Because the terminal device has stored the key of the primary network device, and after the carrier is changed, the terminal device still uses the key of the primary network device. That is to say, during the carrier change, the terminal device does not change the key, and the terminal device does not need to rebuild the PDCP entity. Therefore, when the carrier is changed, the network delay caused by the re-establishment of the PDCP entity of the terminal equipment can be reduced, thereby reducing the probability of data service interruption caused by the change of the carrier.
  • 3A is another flowchart of a data transmission method in an embodiment of the present application.
  • FIG. 3B is a schematic diagram of an embodiment of a downlink data packet transmission path in an embodiment of the present application.
  • 3C is a schematic diagram of another embodiment of a downlink data packet transmission path in an embodiment of the present application.
  • 5A is another flowchart of a data transmission method in an embodiment of the present application.
  • 5B is a schematic diagram of another embodiment of a downlink data packet transmission path in an embodiment of the present application.
  • 5C is a schematic diagram of another embodiment of a downlink data packet transmission path in an embodiment of the present application.
  • FIG. 6 is another flowchart of the data transmission method in the embodiment of the present application.
  • FIG. 7 is another flowchart of the data transmission method in the embodiment of the present application.
  • FIG. 8 is another flowchart of the data transmission method in the embodiment of the present application.
  • 9A is another flowchart of a data transmission method in an embodiment of the present application.
  • 9B is a schematic diagram of another embodiment of a downlink data packet transmission path in an embodiment of the present application.
  • 9C is a schematic diagram of another embodiment of a downlink data packet transmission path in an embodiment of the present application.
  • 9D is a schematic diagram of another embodiment of a downlink data packet transmission path in an embodiment of the present application.
  • FIG. 13 is a schematic diagram of an embodiment of a communication device in an embodiment of the application.
  • FIG. 14 is a schematic diagram of another embodiment of the communication device in the embodiment of the application.
  • FIG. 15 is a schematic diagram of another embodiment of the communication device in the embodiment of the application.
  • FIG. 16 is a schematic diagram of another embodiment of the communication device in the embodiment of the present application.
  • the embodiments of the present application provide a data transmission method and related equipment, which are used to reduce the network delay generated by the terminal equipment when the carrier is changed, thereby reducing the probability of data service interruption caused by the change of the carrier.
  • Packet Data Convergence Protocol is a wireless transport protocol stack responsible for header compression and decompression, transmission of user data, and maintenance of serial numbers as wireless bearers.
  • An entity that adopts this protocol is called a PDCP entity, and the PDCP entity includes the following functions: header compression and decompression using robust header compression (ROHC) protocol, encryption and decryption, and integrity protection and integrity verification .
  • ROHC robust header compression
  • the encryption and decryption functions of the PDCP entity are mainly introduced.
  • the terminal device, the primary network device, and the secondary network device introduced in the embodiments of this application all include at least one PDCP entity.
  • Radio Link Control The radio link control layer protocol in wireless communication systems.
  • An entity that uses the RLC protocol is called an RLC entity.
  • the RLC entity is located above the medium access control (MAC) entity, and mainly provides segment concatenation and retransmission services for user data.
  • MAC medium access control
  • the function of forwarding downlink data packets of the RLC entity is mainly introduced.
  • the terminal device, the primary network device, and the secondary network device introduced in the embodiments of this application all include at least one RLC entity.
  • the data transmission method proposed in the embodiment of the present application is applied to the option 3X (option 3X) architecture of the non-standalone networking mode.
  • the core network part is undertaken by the 4G core network (evolved packet core, EPC), and the access network part is undertaken by the 4G base station or NR base station.
  • EPC evolved packet core
  • the downlink data packets (ie user data) will flow directly from the EPC to the PDCP entity of the LTE base station, and then to the RLC entity of the LTE base station through the PDCP entity of the LTE base station (Fig. Not shown), and then, the RLC entity of the LTE base station is transmitted to the PDCP entity of the terminal device through the MAC layer and the physical layer.
  • both the PDCP entity of the LTE base station and the PDCP entity of the terminal device use the key of the LTE base station.
  • the downlink data packets (ie user data) will flow directly from the EPC to the PDCP entity of the NR base station, and then the PDCP entity of the NR base station will be offloaded to the RLC entity of the LTE base station and the RLC entity of the NR base station. , and finally transmitted to the PDCP entity of the terminal device by the RLC entity of the LTE base station and the RLC entity of the NR base station.
  • the terminal device In order to enable the PDCP entity of the terminal device to decrypt the downlink data packets from the PDCP entity of the NR base station, the terminal device needs to use the same key as the PDCP entity of the NR base station. Since the newly added NR base station often uses a new key to create a PDCP entity, the terminal device needs to change the key and rebuild the PDCP entity. Therefore, network delay will be introduced, resulting in interruption of user data transmission.
  • the secondary carrier needs to be deleted (for example, the aforementioned NR base station is deleted) or the secondary carrier needs to be replaced (for example, the NR base station A is changed to the NR base station B), there will also be cases where the terminal device re-establishes the PDCP entity due to changing the key . Therefore, the network is also delayed, resulting in interruption of user data transmission.
  • the embodiments of the present application propose a data transmission method for the aforementioned system architecture and application scenarios, which can reduce the network delay generated by the terminal equipment when the carrier is changed, thereby reducing the probability of data service interruption caused by the change of the carrier.
  • the data transmission method proposed by the embodiment of the present application will be introduced below from the data interaction between the primary network device, the secondary network device, and the terminal device with reference to FIG. 2 :
  • the main network device is an access network device (radio access network, RAN) that currently provides services for terminal devices, which may be a 4G wireless access network device, or a 4G access network device.
  • the main network device may be the LTE base station shown in FIG. 1 , and may also be referred to as an evolved base station (evolutional node B, NodeB) in a long term evolution LTE system or an evolved LTE system (long term evolution advanced, LTE-A). or eNB or e-NodeB). Because, in the scenario of carrier aggregation or carrier change, the primary network device can affect whether other network devices can access the system.
  • the aforementioned primary network device is also called the primary evolved NodeB (P-eNB) or the master node (master). evolved NodeB, MeNB).
  • P-eNB primary evolved NodeB
  • MeNB master node
  • the primary network device can be used to convert received air frames to internet protocol (IP) packets and act as a router between the terminal device and the rest of the access network, where the rest of the access network can include IP network.
  • IP internet protocol
  • the primary network device may also coordinate attribute management of the air interface. There is no specific limitation here.
  • the main network device in this embodiment of the present application may be any of the foregoing devices or a chip in the foregoing devices, which is not specifically limited here. Whether as a device or as a chip, the main network device can be manufactured, sold, or used as a stand-alone product. In this embodiment and subsequent embodiments, only the main network device is used as an example for description.
  • the primary network device may be a new radio (new radio, NR) access network RAN device, for example, the NR base station shown in Figure 1; it may also be an NR access network that passes through one or more cells on the air interface
  • a device that communicates with a wireless terminal device may also include a centralized unit (centralized unit, CU) and a distributed unit (distributed unit, DU) in a cloud access network (Cloud RAN) system.
  • the secondary network device may be the next generation node B (gNB) in the NR system.
  • gNB next generation node B
  • the aforementioned multiple secondary network devices can be respectively represented as source next generation node B (S-gNB) (ie source secondary network device or source base station) and target next generation node (target next generation node B, T-gNB) (that is, the target secondary network device or the target base station).
  • S-gNB source next generation node B
  • target next generation node B, T-gNB target next generation node B
  • the source secondary network device is the secondary network device that communicates with the terminal device and the primary network device before the change
  • the target secondary network device is the secondary network device that communicates with the terminal device and the primary network device after the change. That is, the above-mentioned source secondary network device is changed to the target secondary network device.
  • the secondary network device may be used to interconvert received air frames and Internet Protocol IP packets, acting as a router between the terminal device and the rest of the access network, which may include the IP network. Secondary network devices may also coordinate attribute management of the air interface. There is no specific limitation here. In addition, the secondary network device communicates with the aforementioned primary network device through the X2 interface.
  • auxiliary network device in this embodiment of the present application may be any of the foregoing devices or a chip in the foregoing devices, which is not specifically limited here. No matter as a device or a chip, the auxiliary network device can be manufactured, sold or used as an independent product. In this embodiment and subsequent embodiments, only the auxiliary network device is used as an example for description.
  • the aforementioned terminal devices include devices that provide voice and/or data connectivity to users.
  • a handheld device with wireless connectivity or a processing device connected to a wireless modem may be included.
  • the terminal device may communicate with the core network (eg, the aforementioned 4G core network EPC) via the radio access network RAN (eg, the aforementioned primary network device or the aforementioned secondary network device), and may exchange voice and/or data with the RAN.
  • the terminal equipment may include user equipment (UE), wireless terminal equipment, mobile terminal equipment, subscriber unit (subscriber unit), subscriber station (subscriber station), mobile station (mobile station), mobile station (mobile), remote remote station, access point (AP), remote terminal, access terminal, user terminal, user agent, or user equipment (user device), etc.
  • the terminal device can also be a vehicle-mounted terminal, for example, a vehicle-mounted box (telematics box, T-Box), a domain controller (domain controller, DC), a multi-domain controller (multi domain controller, MDC) integrated in the vehicle Or on board unit (OBU).
  • vehicle-mounted terminal for example, a vehicle-mounted box (telematics box, T-Box), a domain controller (domain controller, DC), a multi-domain controller (multi domain controller, MDC) integrated in the vehicle Or on board unit (OBU).
  • the terminal device can also be a wearable device, such as glasses, gloves, watches, clothing and shoes, or other portable devices that can be directly worn on the body or integrated into the user's clothing or accessories, which is not limited in this application. .
  • the terminal device in this embodiment of the present application may be any of the foregoing devices or chips, which is not specifically limited here. Whether as a device or as a chip, the terminal device can be manufactured, sold or used as an independent product. In this embodiment and subsequent embodiments, only a terminal device is used as an example for description.
  • the primary network device sends a first message to the terminal device.
  • the main network device is an access network device that provides services for the terminal device, and is also an access network device that decides whether to change the carrier.
  • the terminal device receives downlink data packets from the core network from the primary network device, or simultaneously receives downlink data packets from the core network from the primary network device and other secondary network devices.
  • the terminal device uses the key of the main network device (hereinafter referred to as the main station key). That is to say, the PDCP entity of the terminal device is created by using the master station key, the PDCP entity of the terminal device can use the master station key to package and encrypt data, and at the same time, the PDCP entity of the terminal device can also decrypt the data using the master station key. Station key encrypted packets.
  • the main network device When the main network device initiates the carrier change process, the main network device will send a first message to the terminal device, where the first message is used to instruct the terminal device to use the master key stored in the terminal device to perform encryption after the carrier is changed. Decrypt data.
  • the primary network device if the aforementioned carrier change process is to add a secondary carrier, the primary network device will notify the secondary network device to be added to use the aforementioned primary station key; if the aforementioned carrier change process is to change the added secondary carrier to another If the secondary carrier is used, the primary network device will notify the changed secondary network device to use the aforementioned primary station key. It should be understood that, if the primary network device will delete the added secondary carrier, and only the primary network device and the terminal device perform data transmission, the terminal device still uses the primary station key.
  • the foregoing first message carries first indication information, where the first indication information is used to indicate that the key of the primary network device is used to encrypt and decrypt data.
  • the aforementioned first message is a radio resource control RRC reconfiguration message (RRC connection reconfiguration), and the RRC reconfiguration message carries the aforementioned first indication information.
  • the first indication information may be an identifier, and the identifier is used to indicate the key of the primary network device.
  • the first indication information may be represented by a key to use information element.
  • the first indication information may also be represented in other forms, and the specific form of the first indication information is not limited in this embodiment of the present application.
  • the primary network device when the carrier is changed, the primary network device will send a first message to the terminal device, and the first message will instruct the terminal device to use the key of the primary network device used by the terminal device before the carrier is changed to encrypt and decrypt data. . Because the terminal device has stored the key of the primary network device, and after the carrier is changed, the terminal device still uses the key of the primary network device. That is to say, during the carrier change, the terminal device does not change the key, and the terminal device does not need to rebuild the PDCP entity. Therefore, when the carrier is changed, the network delay caused by the re-establishment of the PDCP entity of the terminal equipment can be reduced, thereby reducing the probability of data service interruption caused by the change of the carrier.
  • the foregoing carrier change process mainly includes the following three scenarios:
  • Adding a secondary carrier means that the primary network device adds a secondary network device, so that the secondary network device participates in data offloading.
  • the secondary carrier is deleted, and the added secondary network device is deleted.
  • the process of deleting the secondary carrier can be initiated by the primary network device or by the secondary network device.
  • Changing one carrier to another carrier refers to changing one secondary network device to another secondary network device. This process can be initiated by the primary network device or by the secondary network device. The following describes each of the aforementioned scenarios:
  • FIG. 3A it is a signaling interaction process among the primary network device, the secondary network device and the terminal device when the primary network device initiates adding the secondary network device.
  • the terminal device receives downlink data packets from the core network through the primary network device, and uses the primary network device's key (ie, the master station key) to encrypt and decrypt data. Specifically, as shown in FIG.
  • the core network device sends the downlink data packet to the PDCP entity 04 of the main network device, and the PDCP entity 04 of the main network device uses the main station key to encrypt and decrypt the downlink data packet, and controls the PDCP
  • the entity 04 transmits the downlink data packet encrypted with the master key to the RLC entity 05 of the main network device, and then the RLC entity 05 transmits the aforementioned downlink data packet to the PDCP entity 01 of the terminal device through the MAC layer and the physical layer.
  • the terminal device can control the PDCP entity 01 to decrypt the downlink data packet by using the master key, so as to obtain the service data of the downlink data packet.
  • the process of transmitting the downlink data packet from the RLC entity 05 of the main network device to the PDCP entity 01 of the terminal device it will also go through the MAC entity 06 of the main network device, the physical layer of the main network device, the terminal device The physical layer of the terminal device, the MAC entity 03 of the terminal device, and the RLC entity 02 of the terminal device, etc.
  • the embodiment of the present application only limits that the RLC entity 05 of the main network device can transmit the downlink data packet to the PDCP entity 01 of the terminal device, and does not limit the specific transmission process between the two entities.
  • the primary network device and the secondary network device (that is, the secondary network device to be added) will perform the following steps:
  • the primary network device sends a third message to the secondary network device.
  • the third message carries the master station key, and is used to instruct the secondary network device to use the master station key to encrypt and decrypt data. That is to say, the master key is used to instruct the secondary network device to use the master key when creating the PDCP entity.
  • the aforementioned third message is a secondary carrier addition request (S-gNB addition request), and the secondary carrier addition request is used to request to add the secondary network device as a secondary carrier.
  • S-gNB addition request secondary carrier addition request
  • the secondary network device uses the master station key to create a PDCP entity of the secondary network device.
  • the secondary network device After the secondary network device receives the aforementioned third message and obtains the primary station key carried in the third message, the secondary network device uses the primary station key to create a PDCP entity of the secondary network device. It should be understood that the PDCP entity created by the secondary network device using the master station key cannot immediately participate in data packet transmission. Only the PDCP entity of the secondary network device can be activated and used. The signaling interaction process between the main network device and the core network device will be described in detail in the subsequent embodiment corresponding to FIG. 4 , and will not be repeated here.
  • the primary network device will only send the key of the secondary network device (that is, the secondary station key) to the secondary network device to be added, and the secondary station key is generally a key derived from the primary station key. , and the secondary station key is different from the primary station key.
  • the main network device sends the master key to the auxiliary network device, and notifies the terminal device to also use the master key in subsequent steps, so that both the auxiliary network device and the terminal device use the master key.
  • the PDCP entity of the terminal device can process the downlink data packets from the PDCP entity of the secondary network device.
  • the secondary network device sends a second message to the primary network device.
  • the second message is used to instruct the secondary network device to confirm that it will be added as a secondary carrier.
  • the second message carries first indication information
  • the first indication information is used to indicate that the master station key is used to encrypt and decrypt data.
  • the first indication information is configured by the secondary network device. It can be understood that the secondary network device carries the first indication information into the aforementioned second message, on the one hand, it means that the secondary network device has confirmed that it will use the master station key to create a PDCP entity in the subsequent process, on the other hand, it is Indicates that the primary network device is notified of the first indication information, so that the primary network device instructs the terminal device to also use the primary station key according to the first indication information in the second message. Based on the latter aspect, the first indication information in the second message may be used as a trigger source to trigger the primary network device to perform the subsequent step 304 .
  • the second message is a secondary carrier addition request response (S-gNB addition request acknowledge), and the secondary carrier addition request response carries multiple information elements, one of which is used to indicate a key.
  • the information element is key to use .
  • the secondary network device sets the key to use cell to "master" to indicate that the secondary network device uses the master key. It should be understood that, in practical applications, other information elements may also be used as the foregoing first indication information, which is not specifically limited here.
  • step 302 there is no definite time sequence limitation between step 302 and step 303 . That is to say, the secondary network device may perform step 302 first and then perform step 303, or may perform step 303 first and then perform step 302, which is not specifically limited here.
  • the primary network device sends the first message to the terminal device.
  • the primary network device When the primary network device receives the second message from the secondary network device and obtains the aforementioned first indication information from the second message, the primary network device can determine that the secondary network device will use the primary key in the subsequent process Encrypt and decrypt. Therefore, the primary network device carries the first indication information in the first message, and sends the first message to the terminal device.
  • the first message is an RRC reconfiguration message (RRC connection reconfiguration), and the RRC reconfiguration message carries the foregoing first indication information. If the first indication information in step 303 is represented by the key to use information element set as "master”, then the first indication information in the RRC reconfiguration message is also the key to use information element set as "master”.
  • neither the aforementioned second message nor the first message directly carries the master station key, but instead carries the first indication information for indicating the master station key. Since the terminal device uses the master key before adding the secondary network device, the terminal device stores the master key, and the PDCP entity in the terminal device is also created using the master key. Therefore, after the terminal device receives the aforementioned first indication information, the terminal device can directly use the PDCP entity of the terminal device to decrypt the downlink data packets encrypted with the master key, without recalculating the key, and without rebuilding the PDCP entity.
  • the primary network device controls the PDCP entity of the primary network device to send a downlink data packet to the RLC entity of the primary network device.
  • the primary network device controls the RLC entity of the primary network device to send downlink data packets to the terminal device.
  • the terminal device since the terminal device still uses the master station key after receiving the aforementioned first indication information, the PDCP entity of the terminal device can use the master station key to encrypt the PDCP entity of the main network device. Downlink packets are decrypted. Therefore, the main network device controls the PDCP entity of the main network device to send downlink data packets to the PDCP entity of the main network device, and then the main network device controls the RLC entity of the main network device to send downlink data packets to the terminal device. After passing through the MAC layer and the physical layer, it is transmitted to the PDCP entity of the terminal device. It should be understood that the flow direction of the downlink data packets is the same as when the primary network device does not add the secondary network device. As shown in FIG.
  • the core network device cannot temporarily allocate downlink data packets to the PDCP entity 07 of the secondary network device.
  • the core network device still sends the downlink data packet to the PDCP entity 04 of the main network device, and the PDCP entity 04 of the main network device uses the master station key to encrypt and decrypt the downlink data packet, and controls the PDCP entity 04
  • the downlink data packet encrypted with the master key is transmitted to the RLC entity 05 of the main network device, and then the RLC entity 05 transmits the aforementioned downlink data packet to the PDCP entity 01 of the terminal device through the MAC layer and the physical layer.
  • the terminal device can control the PDCP entity 01 to decrypt the downlink data packet by using the master key, so as to obtain the service data of the downlink data packet.
  • the primary network device when adding a secondary network device, the primary network device sends a secondary station key that is different from the primary station key to the secondary network device.
  • the PDCP entity of the current terminal equipment uses the master station key, and the terminal equipment may not be able to decrypt the data packets encrypted with the secondary station key. Therefore, the terminal equipment needs to rebuild the PDCP entity. Before the terminal device rebuilds the PDCP entity, the PDCP entity of the primary network device will be frozen, and will no longer transmit downlink data packets to the terminal device.
  • the PDCP entity of the terminal device cannot receive downlink data packets until the PDCP using the secondary station key is activated by the secondary network device, the PDCP using the secondary station key rebuilt by the terminal device is activated, and the core network device has confirmed the addition of the secondary carrier. .
  • the terminal device does not need to rebuild the PDCP entity, nor does it need to wait for the network device side to interact with the core network device before starting to receive downlink data packets again. Therefore, network delay can be shortened, thereby reducing the probability of data service interruption caused by adding secondary carriers.
  • the following takes the primary network device as the eNB, the secondary network device as the gNB, and the terminal device as the UE as an example for further introduction:
  • the eNB sends a secondary carrier addition request (SgNB addition request) to the gNB.
  • SgNB addition request a secondary carrier addition request
  • the secondary carrier addition request carries the primary station key (ie, the eNB's key), and the secondary carrier addition request is used to notify the gNB to use the primary station key to establish a PDCP entity.
  • the gNB uses the master station key to create a gNB PDCP entity.
  • step 402 although the gNB uses the master station key to create a PDCP entity, the PDCP entity has not been activated and cannot immediately participate in data transmission.
  • the gNB sends a secondary carrier addition request response (SgNB addition request acknowledge) to the eNB.
  • SgNB addition request acknowledge a secondary carrier addition request response
  • the secondary carrier addition request response carries first indication information
  • the first indication information is used to instruct the gNB to confirm that the PDCP entity will be created by using the primary station key.
  • the first indication information is represented by an information element that the gNB fills in the SgNB to MeNB Container.
  • step 402 and step 403 have no definite time sequence limitation. That is to say, the gNB may perform step 402 first and then step 403, or may perform step 403 first and then perform step 402, and may also perform step 402 and step 403 at the same time, which is not specifically limited here.
  • the eNB sends RRC reconfiguration (RRC connection reconfiguration) signaling to the UE.
  • RRC reconfiguration RRC connection reconfiguration
  • the eNB After the eNB receives the carrier addition request response from the gNB, the eNB can determine that the gNB will use the master key to create the PDCP entity. Therefore, the eNB will send RRC reconfiguration signaling to the UE, where the RRC reconfiguration signaling carries the first indication information carried in the carrier addition request response.
  • the UE When the UE recognizes the first indication information in the foregoing RRC reconfiguration signaling, the UE can learn to use the master key. Since the PDCP entity of the UE uses the master key before, the UE can continue to use the PDCP entity using the master key without rebuilding the PDCP entity using the new key. Therefore, in the subsequent steps, when the downlink data packet encrypted with the master key is transmitted to the UE, the UE can use the PDCP entity to decrypt the downlink data packet, and then obtain the service data in the downlink data packet.
  • RRC reconfiguration signaling may also carry other parameters for reconfiguration, which are not specifically limited here.
  • the UE sends an RRC reconfiguration complete (RRC connection reconfiguration complete) signaling to the eNB.
  • RRC reconfiguration complete RRC connection reconfiguration complete
  • the RRC reconfiguration completion signaling is used to notify the eNB that the UE has received the aforementioned first indication information and completed the related reconfiguration.
  • the eNB sends a secondary carrier reconfiguration complete (SgNB reconfiguration complete) signaling to the gNB.
  • SgNB reconfiguration complete secondary carrier reconfiguration complete
  • the secondary carrier reconfiguration completion signaling is used to notify the gNB that the aforementioned UE has been reconfigured, and the gNB can start to prepare for the random access of the UE.
  • the UE initiates a random access procedure to the gNB.
  • the random access procedure between the UE and the gNB includes:
  • the UE sends a random access request (ie msg1) to the gNB, and the random access request carries a random access preamble.
  • a random access request ie msg1
  • the gNB sends a random access response (random access response, RAR) (ie, msg2) to the UE.
  • RAR random access response
  • the UE sends an RRC connection establishment request (RRC connection request) (ie msg3) to the gNB, and the RRC connection establishment request carries the identification information of the UE.
  • RRC connection request RRC connection request
  • the gNB sends an RRC connection establishment (RRC contention resolution) signaling (ie msg4) to the UE.
  • RRC contention resolution RRC contention resolution
  • the random access process may also involve other signaling or parameters, which will not be repeated here.
  • the UE When the UE successfully accesses the gNB, it means that the UE can receive downlink data packets from the aforementioned gNB thereafter. It can also be understood that the gNB can provide services for the aforementioned UE.
  • the eNB controls the eNB PDCP entity to send downlink data packets to the eNB RLC entity.
  • step 408 and the aforementioned step 407 are independent of each other. That is, this step 408 may be performed after the eNB performs step 406 .
  • the downlink data packet comes from a serving gateway (serving gateway, S-GW), which is a gateway terminated at a UMTS terrestrial radio access network (UMTS terrestrial radio access network, E-UTRAN) interface.
  • serving gateway is mainly used for the eNB or gNB to send downlink data packets and negotiate transmission path switching with a mobility management entity (mobility management entity, MME).
  • MME mobility management entity
  • the eNB PDCP entity will use the master key to encrypt the downlink data packet from the S-GW, and then control the eNB PDCP entity to transmit the downlink data packet to the eNB RLC entity.
  • the eNB controls the eNB RLC entity to send downlink data packets to the UE PDCP entity.
  • step 409 and the aforementioned step 407 are independent of each other. However, immediately after step 408, the eNB will perform step 409.
  • the eNB controls the eNB RLC entity to transmit the aforementioned downlink data packets encrypted with the master key to the UE PDCP entity through the MAC layer and the physical layer. Since the UE PDCP entity also adopts the master station key, the UE PDCP entity can decrypt the downlink data packet and obtain the service data in the downlink data packet.
  • the gNB notifies the eNB that the random access is completed.
  • step 410 is independent of the aforementioned steps 408 to 409 , and this step 410 may be executed after step 407 .
  • the eNB sends an evolved radio access bearer modification indication (E-RAB modification indication) to the MME.
  • E-RAB modification indication an evolved radio access bearer modification indication
  • the evolved radio access bearer modification indication is used to request the MME to switch the transmission path to the gNB.
  • the MME sends a path switch request (path switch request) to the S-GW.
  • the path switching request is used to request the S-GW to transmit the subsequent downlink data packets to the gNB. Therefore, the gNB PDCP entity will receive downlink data packets from the aforementioned S-GW.
  • the S-GW sends a path switch request acknowledgement (path switch request acknowledge) to the MME.
  • the path switch request response is used to indicate that the switch has been completed.
  • the S-GW sends an end marker (end marker) data packet to the eNB.
  • the end marker data packet is the last data packet sent by the S-GW to the eNB, and is used to indicate that after the end marker data packet, the S-GW no longer sends downlink data packets to the eNB.
  • the eNB sends the system frame number status transfer (SN status transfer) and end marker (end marker) data packets to the gNB.
  • SN status transfer system frame number status transfer
  • end marker end marker
  • the system frame number status forwarding is used to indicate the sequence number of the downlink data packet that the current S-GW has transmitted to the eNB, so that the gNB receives the data packet after the sequence number from the S-GW in the subsequent process. Therefore, the gNB can avoid repeatedly receiving downlink data packets or missing downlink data packets.
  • the eNB also forwards the end marker data packet in the aforementioned step 414 to the gNB to indicate that the eNB has forwarded the last data packet to the gNB. After the gNB receives the end marker data packet, the gNB will execute step 417 .
  • the MME sends an evolved radio access bearer modification indication complete (E-RAB modification indication complete) to the eNB.
  • E-RAB modification indication complete an evolved radio access bearer modification indication complete
  • the gNB controls the gNB PDCP entity to receive downlink data packets from the S-GW.
  • the gNB PDCP entity After the gNB receives the end marker data packet, the gNB PDCP entity is activated. The gNB can control the gNB PDCP entity to receive downlink data packets from the S-GW. Since the gNB uses the master key when creating the gNB PDCP entity, the gNB PDCP entity encrypts the received downlink data packet with the master key, and then performs subsequent transmission.
  • the gNB controls the gNB PDCP entity to send downlink data packets to the gNB RLC entity and the eNB RLC entity.
  • the gNB controls the gNB RLC entity to send downlink data packets to the UE PDCP entity.
  • the eNB controls the eNB RLC entity to send downlink data packets to the UE PDCP entity.
  • step 419 and step 420 are performed simultaneously.
  • FIG. 3B and FIG. 3C are used as examples for description.
  • the core network device in the aforementioned FIG. 3B and FIG. 3C is the S-GW
  • the primary network device is the eNB
  • the secondary network device is the gNB
  • the terminal device is the UE.
  • the S-GW sends the downlink data packet to the eNB PDCP entity 04, the eNB PDCP entity 04 encrypts and decrypts the downlink data packet using the master key, and controls the eNB PDCP entity 04 to use the master key to encrypt the downlink data
  • the packet is transmitted to the eNB RLC entity 05, and then the eNB RLC entity 05 transmits the aforementioned downlink data packet to the UE PDCP entity 01 through the MAC layer and the physical layer.
  • the UE can control the UE PDCP entity 01 to decrypt the downlink data packet by using the master station key, so as to obtain the service data of the downlink data packet.
  • the S-GW sends the downlink data packet to the gNB PDCP entity 07, the gNB PDCP entity 07 encrypts and decrypts the downlink data packet using the master key, and controls the gNB PDCP entity 07 to use the master key to encrypt the downlink data
  • the packets are transmitted to the eNB RLC entity 05 and the gNB RLC entity 08, and then the eNB RLC entity 05 and the gNB RLC entity 08 respectively transmit the aforementioned downlink data packets to the UE PDCP entity 01, so that the UE can control the UE PDCP entity 01 to adopt
  • the master station key decrypts the downlink data packet, and then obtains the service data of the downlink data packet.
  • the process of deleting the secondary carrier may be initiated by the primary network device, or may be initiated by the secondary network device. As shown in FIG. 5A , when the primary network device initiates deletion of the secondary network device, the signaling interaction process among the primary network device, the secondary network device and the terminal device is shown.
  • the terminal device receives the downlink data packets from the core network through the primary network device and the secondary network device, and uses the key of the primary network device (that is, the master station key) to encrypt Decrypt data. Specifically, as shown in FIG.
  • the core network device sends the downlink data packet to the PDCP entity 07 of the secondary network device, and the PDCP entity 07 of the secondary network device encrypts and decrypts the downlink data packet using the master key, and controls the
  • the PDCP entity 07 of the secondary network device transmits the downlink data packets encrypted with the primary station key to the primary network device RLC entity 05 and the RLC entity 08 of the secondary network device, and then the RLC entity 05 of the primary network device and the secondary network
  • the RLC entity 08 of the device transmits the aforementioned downlink data packets to the PDCP entity 01 of the terminal device through the MAC layer and the physical layer respectively.
  • the primary network device and the secondary network device (that is, the secondary network device to be deleted) will perform the following steps:
  • the primary network device sends a secondary carrier release request to the secondary network device.
  • the secondary carrier release request is used to indicate that the secondary network device is ready to release.
  • the secondary network device sends a secondary carrier release request response to the primary network device.
  • the secondary carrier release request response is used to indicate that the secondary network device has received the aforementioned secondary carrier release request and confirms that it is ready to release.
  • the secondary carrier release request may be used as a trigger source to trigger the primary network device to perform the subsequent step 503 .
  • the primary network device sends the first message to the terminal device.
  • the primary network device after the primary network device receives the carrier release response from the secondary network device, the primary network device will send a first message to the terminal device, where the first message is used to instruct the terminal device to use the master key Encrypt and decrypt data.
  • the foregoing first message does not carry certain specific indication information for indicating the key.
  • the terminal device receives the aforementioned first message and detects that the first message does not carry the indication information about the key, the terminal device will not change the key, that is, the terminal device will still use the master key .
  • the secondary network device controls the PDCP entity of the secondary network device to only send downlink data packets to the RLC entity of the primary network device.
  • the primary network device controls the RLC entity of the primary network device to send downlink data packets to the terminal device.
  • step 503 there is no definite time sequence limitation between step 503 and step 504 . That is to say, the secondary network device may execute step 503 first and then execute step 504, or may execute step 504 first and then execute step 503, which is not specifically limited here.
  • the secondary network device after the secondary network device receives the carrier release request and before the PDCP entity of the secondary network device is deleted, since the terminal device still uses the master key, the secondary network device can The received downlink data packets are forwarded to the main network device, and the main network device sends the part of the downlink data packets to the terminal device. As shown in FIG.
  • the core network device sends the downlink data packet to the PDCP entity 07 of the secondary network device, and the PDCP entity 07 of the secondary network device encrypts and decrypts the downlink data packet using the master key, and controls the PDCP
  • the entity 07 transmits the downlink data packet encrypted by the master station key to the RLC entity 05 of the main network device, and then the RLC entity 05 transmits the aforementioned downlink data packet to the terminal device, and then transmits it to the terminal device after passing through the MAC layer and the physical layer.
  • the PDCP entity in the secondary network device will stop forwarding downlink data packets.
  • the PDCP entity of the primary network device cannot receive downlink data packets from the core network device and control the PDCP entity of the primary network device until the primary network device is activated using the PDCP of the primary station key and the core network device has confirmed the deletion of the secondary carrier.
  • the downlink data packet is transmitted to the RLC entity of the main network device, and then the RLC entity of the main network device transmits it to the PDCP entity of the terminal device through the MAC layer and the physical layer.
  • the terminal equipment since both the terminal equipment and the secondary network equipment use the master station key, the terminal equipment does not need to rebuild the PDCP entity, and the secondary network equipment can continue to transmit the buffered downlink data packets to the primary network equipment and the terminal equipment, and does not need to recreate the PDCP entity. It is necessary to wait for the network device side to interact with the core network device before starting to receive downlink data packets again. Therefore, network delay can be shortened, thereby reducing the probability of data service interruption caused by adding secondary carriers.
  • the following takes the primary network device as the eNB, the secondary network device as the gNB, and the terminal device as the UE as an example for further introduction:
  • the eNB sends a secondary carrier release request (SgNB release request) to the gNB.
  • SgNB release request a secondary carrier release request
  • the secondary carrier release request is used to notify the gNB to prepare for release.
  • the gNB sends a secondary carrier release request response (SgNB release request acknowledge) to the eNB.
  • SgNB release request acknowledge a secondary carrier release request response
  • the secondary carrier release request response is used to indicate that the gNB has received the aforementioned secondary carrier release request and confirms that it is ready to release.
  • the secondary carrier release request may be used as a trigger source to trigger the eNB to perform subsequent step 604 .
  • the gNB controls the gNB PDCP entity to only send downlink data packets to the eNB RLC entity.
  • the downlink data packet comes from the serving gateway S-GW, and the downlink data packet is the downlink data packet received by the gNB from the S-GW before the gNB PDCP entity is deleted after the gNB receives the carrier release request.
  • the gNB PDCP entity uses the master station key to encrypt the aforementioned downlink data packets, and then controls the gNB PDCP entity to transmit the downlink data packets to the eNB RLC entity.
  • the eNB sends RRC reconfiguration (RRC connection reconfiguration) signaling to the UE.
  • RRC reconfiguration RRC connection reconfiguration
  • the eNB After the eNB receives the carrier release request response from the gNB, the eNB will send RRC reconfiguration signaling to the UE, and the RRC reconfiguration signaling is used to instruct the terminal device to still use the master key.
  • the foregoing RRC reconfiguration signaling does not carry certain specific indication information for indicating a key.
  • the UE receives the aforementioned RRC reconfiguration signaling and detects that the RRC reconfiguration signaling does not carry the indication information about the key, the UE will not change the key, that is, the UE will still use the master key .
  • RRC reconfiguration signaling may also carry other parameters for reconfiguration, which are not specifically limited here.
  • step 604 and the aforementioned step 603 are independent of each other. That is to say, in practical applications, the gNB may perform step 603 first, and then the eNB may perform step 604; it is also possible that the eNB performs step 604 first, and then the gNB performs step 603; it is also possible that the gNB and the eNB perform simultaneously Steps 603 and 604 are performed. There is no specific limitation here.
  • the UE sends an RRC reconfiguration complete (RRC connection reconfiguration complete) signaling to the eNB.
  • RRC reconfiguration complete RRC connection reconfiguration complete
  • the RRC reconfiguration completion signaling is used to notify the eNB that the UE has completed the relevant reconfiguration.
  • the eNB controls the eNB RLC entity to send downlink data packets to the UE PDCP entity.
  • the eNB controls the eNB RLC entity to transmit the aforementioned downlink data packets encrypted with the master key to the UE PDCP entity through the MAC layer and the physical layer. Since the UE PDCP entity also adopts the master station key, the UE PDCP entity can decrypt the downlink data packet and obtain the service data in the downlink data packet.
  • the eNB sends an evolved radio access bearer modification indication (E-RAB modification indication) to the MME.
  • E-RAB modification indication an evolved radio access bearer modification indication
  • the evolved radio access bearer modification indication is used to request the MME to switch the transmission path to the eNB.
  • the MME sends a path switch request (path switch request) to the S-GW.
  • the path switching request is used to request the S-GW to transmit subsequent downlink data packets to the eNB. Therefore, the eNB will control the eNB PDCP entity to receive downlink data packets from the aforementioned S-GW.
  • the S-GW sends a path switch request acknowledgement (path switch request acknowledge) to the MME.
  • the path switch request response is used to indicate that the switch has been completed.
  • the S-GW sends an end marker (end marker) data packet to the gNB.
  • the end marker data packet is the last data packet sent by the S-GW to the gNB, and is used to indicate that after the end marker data packet, the S-GW no longer sends downlink data packets to the gNB.
  • the gNB sends a system frame number status transfer (SN status transfer) and an end marker (end marker) data packet to the eNB.
  • SN status transfer system frame number status transfer
  • end marker end marker
  • the system frame number status forwarding is used to indicate the sequence number of the downlink data packet that the current S-GW has transmitted to the gNB, so that the eNB receives the data packet after the sequence number from the S-GW in the subsequent process. Therefore, the eNB can avoid repeatedly receiving downlink data packets or missing downlink data packets.
  • the gNB also forwards the end marker data packet in the aforementioned step 610 to the eNB to indicate that the gNB has forwarded the last data packet to the eNB. After the eNB receives the end marker data packet, the eNB will perform step 613 .
  • the MME sends an evolved radio access bearer modification indication complete (E-RAB modification indication complete) to the eNB.
  • E-RAB modification indication complete an evolved radio access bearer modification indication complete
  • the eNB controls the eNB PDCP entity to receive downlink data packets from the S-GW.
  • the gNB PDCP entity After the gNB receives the end marker data packet, the gNB PDCP entity is activated. The gNB can control the gNB PDCP entity to receive downlink data packets from the S-GW. Since the gNB uses the master key when creating the gNB PDCP entity, the gNB PDCP entity encrypts the received downlink data packet with the master key, and then performs subsequent transmission.
  • the eNB controls the eNB PDCP entity to send downlink data packets to the eNB RLC entity.
  • the eNB controls the eNB RLC entity to send downlink data packets to the UE PDCP entity.
  • FIG. 5B and FIG. 5C are used as examples for description.
  • the core network device in the aforementioned FIG. 5B and FIG. 5C is the S-GW
  • the primary network device is the eNB
  • the secondary network device is the gNB
  • the terminal device is the UE.
  • the flow of the downlink data packet is as shown in FIG. 5B .
  • the S-GW sends the downlink data packet to the gNB PDCP entity 07, the gNB PDCP entity 07 encrypts and decrypts the downlink data packet using the master key, and controls the gNB PDCP entity 07 to use the master key to encrypt the downlink data
  • the packet is transmitted to the eNB RLC entity 05, and then the eNB RLC entity 05 transmits the aforementioned downlink data packet to the UE PDCP entity 01 through the MAC layer and the physical layer.
  • the UE can control the UE PDCP entity 01 to decrypt the downlink data packet by using the master station key, so as to obtain the service data of the downlink data packet.
  • the S-GW sends the downlink data packet to the eNB PDCP entity 04, the eNB PDCP entity 04 encrypts and decrypts the downlink data packet using the master key, and controls the eNB PDCP entity 04 to use the master key to encrypt the downlink data
  • the packet is transmitted to the eNB RLC entity 05, and then the eNB RLC entity 05 transmits the aforementioned downlink data packet to the UE PDCP entity 01 through the MAC layer and the physical layer, so that the UE can control the UE PDCP entity 01 to use the master station key pair
  • the downlink data packet is decrypted, and then the service data of the downlink data packet is obtained.
  • FIG. 7 it is a signaling interaction process among the primary network device, the secondary network device and the terminal device when the secondary network device initiates deletion of the secondary network device.
  • the terminal device receives the downlink data packets from the core network through the primary network device and the secondary network device, and uses the key of the primary network device (that is, the master station key) to encrypt Decrypt data.
  • the primary network device that is, the master station key
  • the primary network device and the secondary network device (that is, the secondary network device to be deleted) will perform the following steps:
  • the secondary network device sends a secondary carrier release request to the primary network device.
  • the secondary carrier release request is used to request the primary network device to allow the secondary network device to release.
  • the primary network device sends a secondary carrier release confirmation message to the secondary network device.
  • the secondary carrier release confirmation message is used to indicate that the secondary network device is allowed to be released in the subsequent process.
  • both the secondary carrier release request in the aforementioned step 701 and the carrier release confirmation message in the step 702 can be used as trigger sources to trigger the primary network device to execute the subsequent step 703 .
  • the primary network device sends the first message to the terminal device.
  • the secondary network device controls the PDCP entity of the secondary network device to only send downlink data packets to the RLC entity of the primary network device.
  • the primary network device controls the RLC entity of the primary network device to send downlink data packets to the terminal device.
  • step 703 there is no definite time sequence limitation between step 703 and step 704 . That is to say, the secondary network device may perform step 703 first and then perform step 704, or may perform step 704 first and then perform step 703, which is not limited herein.
  • steps 703 to 705 are the same as the aforementioned steps 503 to 505 .
  • steps 703 to 705 are the same as the aforementioned steps 503 to 505 .
  • steps 703 to 705 are not repeated here.
  • the terminal equipment since both the terminal equipment and the secondary network equipment use the master station key, the terminal equipment does not need to rebuild the PDCP entity, and the secondary network equipment can also continue to transmit the buffered downlink data packets to the primary network equipment and the terminal equipment, without It is necessary to wait for the network device side to interact with the core network device before starting to receive downlink data packets again. Therefore, network delay can be shortened, thereby reducing the probability of data service interruption caused by adding secondary carriers.
  • the following takes the primary network device as the eNB, the secondary network device as the gNB, and the terminal device as the UE as an example for further introduction:
  • the gNB sends a secondary carrier release request (SgNB release request) to the eNB.
  • SgNB release request a secondary carrier release request
  • the secondary carrier release request is used by the eNB to allow the gNB to release in the subsequent process.
  • the eNB sends a secondary carrier release acknowledgement (SgNB release request acknowledge) message to the gNB.
  • SgNB release request acknowledge secondary carrier release acknowledgement
  • the secondary carrier release request confirmation message is used to instruct the eNB to allow the gNB to be released in the subsequent process.
  • steps 801 and 802 can both be used as trigger sources to trigger the eNB to perform the subsequent step 804 .
  • the gNB controls the gNB PDCP entity to only send downlink data packets to the eNB RLC entity.
  • the eNB sends RRC reconfiguration (RRC connection reconfiguration) signaling to the UE.
  • RRC reconfiguration RRC connection reconfiguration
  • the UE sends an RRC reconfiguration complete (RRC connection reconfiguration complete) signaling to the eNB.
  • RRC reconfiguration complete RRC connection reconfiguration complete
  • the eNB controls the eNB RLC entity to send downlink data packets to the UE PDCP entity.
  • the eNB sends an evolved radio access bearer modification indication (E-RAB modification indication) to the MME.
  • E-RAB modification indication evolved radio access bearer modification indication
  • the MME sends a path switch request (path switch request) to the S-GW.
  • the S-GW sends a path switch request acknowledgement (path switch request acknowledge) to the MME.
  • the S-GW sends an end marker (end marker) data packet to the gNB.
  • the gNB sends the system frame number status transfer (SN status transfer) and end marker (end marker) data packets to the eNB.
  • SN status transfer system frame number status transfer
  • end marker end marker
  • the MME sends an evolved radio access bearer modification indication complete (E-RAB modification indication complete) to the eNB.
  • E-RAB modification indication complete an evolved radio access bearer modification indication complete
  • the eNB controls the eNB PDCP entity to receive downlink data packets from the S-GW.
  • the eNB controls the eNB PDCP entity to send downlink data packets to the eNB RLC entity.
  • the eNB controls the eNB RLC entity to send downlink data packets to the UE PDCP entity.
  • steps 803 to 815 are the same as the aforementioned steps 603 to 615 .
  • steps 803 to 815 are the same as the aforementioned steps 603 to 615 .
  • This process may be initiated by the primary network device or by the secondary network device. As shown in FIG. 9A , it is a signaling interaction process among the primary network device, the source secondary network device, the target secondary network device and the terminal device when the source secondary network device initiates the change of the secondary network device.
  • the terminal device receives downlink data packets from the core network through the primary network device and the source secondary network device, and uses the key of the primary network device (ie, the master key) to encrypt and decrypt data.
  • the core network device sends the downlink data packet to the PDCP entity 07 of the source auxiliary network device, and the PDCP entity 07 of the source auxiliary network device encrypts and decrypts the downlink data packet using the master key, and then encrypts and decrypts the downlink data packet.
  • the PDCP entity 07 that controls the source secondary network device transmits the downlink data packets encrypted with the master key to the primary network device RLC entity 05 and the RLC entity 08 of the source secondary network device, and then the RLC entity 05 of the primary network device. and the RLC entity 08 of the source and secondary network device respectively transmit the aforementioned downlink data packets to the terminal device, and then transmit to the PDCP entity 01 of the terminal device after passing through the MAC layer and the physical layer.
  • the primary network device When the source secondary network device requests to change to the target secondary network device, the primary network device, the source secondary network device (that is, the secondary network device to be deleted) and the target secondary network device (that is, the secondary network device to be added) will execute as follows step:
  • the source secondary network device sends a secondary carrier change request to the primary network device.
  • the secondary carrier change request is used to request the primary network device to change the secondary carrier.
  • the secondary carrier change request carries the identification information of the target secondary network device. Therefore, after the primary network device obtains the identification information of the target secondary network device from the aforementioned secondary carrier change request, the primary network device will initiate a secondary carrier addition process to the target secondary network device. Specifically, the primary network device will execute step 902 .
  • the primary network device sends a third message to the target secondary network device.
  • the third message carries the master key, and is used to instruct the target secondary network device to use the master key to encrypt and decrypt data. That is to say, the master key is used to instruct the target secondary network device to use the master key when creating the PDCP entity.
  • the aforementioned third message is a secondary carrier addition request (S-gNB addition request), and the secondary carrier addition request is used to request to add the target secondary network device as a secondary carrier.
  • S-gNB addition request secondary carrier addition request
  • the target secondary network device uses the master station key to create a PDCP entity of the target secondary network device.
  • the target secondary network device After the target secondary network device receives the aforementioned third message and obtains the master station key carried in the third message, the target secondary network device uses the master station key to create the PDCP entity of the target secondary network device. It should be understood that the PDCP entity created by the target secondary network device using the master station key cannot immediately participate in data packet transmission. It needs to wait for the terminal device to access the target secondary network device and the primary network device to notify the core network device that the carrier has changed. After that, the PDCP entity of the target secondary network device can be activated and used. The signaling interaction process between the main network device and the core network device will be described in detail in the subsequent embodiment corresponding to FIG. 10 , and will not be repeated here.
  • the primary network device will only send a new key different from the primary key to the target secondary network device to be added.
  • the main network device sends the master key to the target auxiliary network device, and in the subsequent steps, the terminal device is notified to also use the master key, so that both the target auxiliary network device and the terminal device use the master key.
  • the PDCP entity of the terminal device can process the downlink data packets from the PDCP entity of the target secondary network device.
  • the target secondary network device sends a second message to the primary network device.
  • the second message is used to instruct the target secondary network device to confirm that it will be added as a secondary carrier.
  • the second message carries first indication information
  • the first indication information is used to indicate that the master station key is used to encrypt and decrypt data.
  • the first indication information is configured by the target secondary network device. It can be understood that the target secondary network device carries the first indication information into the aforementioned second message, on the one hand, it indicates that the target secondary network device has confirmed that it will use the master station key to create a PDCP entity in the subsequent process, and on the other hand
  • the aspect means that the primary network device is notified of the first indication information, so that the primary network device instructs the terminal device to also use the primary station key according to the first indication information in the second message. Based on the latter aspect, the first indication information in the second message may be used as a trigger source to trigger the primary network device to perform subsequent step 905 .
  • the second message is a secondary carrier addition request response (S-gNB addition request acknowledge).
  • the target secondary network device sets the key to use information element indicating the key as "master”, and carries it in the aforementioned second message to indicate that the target secondary network device adopts the master key. It should be understood that, in practical applications, other information elements may also be used as the foregoing first indication information, which is not specifically limited here.
  • step 903 and step 904 there is no definite time sequence limitation between step 903 and step 904 . That is to say, the target secondary network device may first execute step 903 and execute step 904, or may first execute step 904 and then execute step 903, which is not specifically limited here.
  • the primary network device sends the first message to the terminal device.
  • the primary network device When the primary network device receives the second message from the target secondary network device and obtains the aforementioned first indication information from the second message, the primary network device can determine that the target secondary network device will use the primary station in the subsequent process key for encryption and decryption. Therefore, the primary network device carries the first indication information in the first message, and sends the first message to the terminal device.
  • the first message is an RRC reconfiguration message (RRC connection reconfiguration), and the RRC reconfiguration message carries the foregoing first indication information. If the first indication information in step 904 is represented by the key to use information element set as "master”, then the first indication information in the RRC reconfiguration message is also the key to use information element set as "master”.
  • neither the aforementioned second message nor the first message directly carries the master station key, but instead carries the first indication information for indicating the master station key. Since the terminal device uses the master key before adding the secondary network device, the terminal device stores the master key, and the PDCP entity in the terminal device is also created using the master key. Therefore, after the terminal device receives the aforementioned first indication information, the terminal device can directly use the PDCP entity of the terminal device to decrypt the downlink data packet encrypted with the master key, without recalculating the key, and without rebuilding the PDCP entity.
  • the source secondary network device controls the PDCP entity of the source secondary network device to send a downlink data packet to the RLC entity of the primary network device.
  • step 906 is independent of the aforementioned steps 902 to 905 .
  • the source network device may perform step 906 after performing step 901 .
  • the primary network device controls the RLC entity of the primary network device to send downlink data packets to the terminal device.
  • both the terminal device and the source-secondary network device use the master key, and the terminal device still uses the master key after receiving the aforementioned first indication information. Therefore, the PDCP entity of the terminal device can decrypt the downlink data packets encrypted by the PDCP entity of the source secondary network device using the master key. Therefore, the source auxiliary network device controls the PDCP entity of the source auxiliary network device to send downlink data packets to the PDCP entity of the primary network device, and then the primary network device controls the RLC entity of the primary network device to send the downlink data packet to the terminal device through the MAC layer and the physical layer. The PDCP entity sends downlink data packets.
  • Such an implementation enables the terminal device to receive a part of downlink data packets buffered in the source secondary network device before the target secondary network device starts to transmit downlink data packets after the source secondary network device sends a secondary carrier change request. Therefore, the time for interrupting the transmission of downlink data packets can be shortened, the network delay can be shortened, and the probability of service interruption of the terminal equipment can be reduced.
  • the flow of downlink data packets is shown in FIG. 9C , because the PDCP entity of the target secondary network device has not been activated, the core network device cannot temporarily allocate downlink data packets to the PDCP entity 10 of the target secondary network device.
  • the core network device sends the downlink data packet to the PDCP entity 07 of the source auxiliary network device, and the PDCP entity 07 of the source and auxiliary network device encrypts and decrypts the downlink data packet using the master key, and controls the PDCP entity 07
  • the downlink data packet encrypted by the master station key is transmitted to the RLC entity 05 of the main network device, and then the RLC entity 05 transmits the aforementioned downlink data packet to the terminal device, and then transmits it to the terminal device after the MAC layer and the physical layer.
  • the terminal device can control the PDCP entity 01 to use the master station key to decrypt the downlink data packet, thereby obtaining the service data of the downlink data packet.
  • the following takes the primary network device as eNB, the source secondary network device as S-gNB, the target secondary network device as T-gNB, and the terminal device as UE as an example. To go further:
  • the S-gNB sends a secondary carrier change request (SgNB change request) to the eNB.
  • SgNB change request a secondary carrier change request
  • the secondary carrier change request carries the identification information of the T-gNB to be added.
  • the eNB After the eNB acquires the identification information of the T-gNB from the aforementioned secondary carrier change request, the eNB will perform step 1002 .
  • the S-gNB At the same time, the S-gNB will perform step 1009.
  • the eNB sends a secondary carrier addition request (SgNB addition request) to the T-gNB.
  • SgNB addition request a secondary carrier addition request
  • the secondary carrier addition request carries the primary station key (that is, the eNB's key), and the secondary carrier addition request is used to notify the T-gNB to use the primary station key to establish a PDCP entity.
  • the T-gNB uses the master key to create a T-gNB PDCP entity.
  • step 1003 although the T-gNB uses the master station key to create a PDCP entity, the PDCP entity has not been activated and cannot immediately participate in data transmission.
  • the T-gNB sends a secondary carrier addition request response (SgNB addition request acknowledge) to the eNB.
  • SgNB addition request acknowledge secondary carrier addition request response
  • the secondary carrier addition request response carries first indication information
  • the first indication information is used to instruct the T-gNB to confirm that the PDCP entity will be created by using the primary station key.
  • the first indication information is represented by an information element that the T-gNB fills in the SgNB to MeNB Container.
  • step 1003 and step 1004 have no definite time sequence limitation. That is to say, the T-gNB may perform step 1003 first and then step 1004, or may perform step 1004 first and then perform step 1003, and may also perform step 1003 and step 1004 at the same time, which is not limited herein.
  • the eNB sends RRC reconfiguration (RRC connection reconfiguration) signaling to the UE.
  • RRC reconfiguration RRC connection reconfiguration
  • the eNB After the eNB receives the carrier addition request response from the T-gNB, the eNB can determine that the T-gNB will use the master key to create the PDCP entity. Therefore, the eNB will send RRC reconfiguration signaling to the UE, where the RRC reconfiguration signaling carries the first indication information carried in the carrier addition request response.
  • the UE When the UE recognizes the first indication information in the foregoing RRC reconfiguration signaling, the UE can learn to use the master key. Since the PDCP entity of the UE uses the master key before, the UE can continue to use the PDCP entity using the master key without rebuilding the PDCP entity using the new key. Therefore, in the subsequent steps, when the downlink data packet encrypted with the master key is transmitted to the UE, the UE can use the PDCP entity to decrypt the downlink data packet, and then obtain the service data in the downlink data packet.
  • RRC reconfiguration signaling may also carry other parameters for reconfiguration, which are not specifically limited here.
  • the UE sends an RRC reconfiguration complete (RRC connection reconfiguration complete) signaling to the eNB.
  • RRC reconfiguration complete RRC connection reconfiguration complete
  • the RRC reconfiguration completion signaling is used to notify the eNB that the UE has received the aforementioned first indication information and completed the related reconfiguration.
  • the eNB sends secondary carrier reconfiguration complete signaling (SgNB reconfiguration complete) to the T-gNB.
  • SgNB reconfiguration complete secondary carrier reconfiguration complete signaling
  • the secondary carrier reconfiguration completion signaling is used to notify the T-gNB that the aforementioned UE has been reconfigured, and the T-gNB can start to prepare for the random access of the UE.
  • the UE initiates a random access procedure to the T-gNB.
  • the random access process between the UE and the T-gNB is similar to the random access process between the UE and the gNB in the foregoing step 407 .
  • the relevant introduction in the foregoing step 407 please refer to the relevant introduction in the foregoing step 407 , which will not be repeated here.
  • the UE When the UE successfully accesses the T-gNB, it means that the UE can receive downlink data packets from the aforementioned T-gNB thereafter. It can also be understood that the T-gNB can provide services for the aforementioned UE.
  • the S-gNB controls the S-gNB PDCP entity to send downlink data packets to the eNB RLC entity.
  • the downlink data packet in step 1009 comes from the downlink data packet from the serving gateway S-GW.
  • the S-gNB PDCP entity will use the master key to encrypt the downlink data packet from the S-GW, and then control the S-gNB PDCP entity to transmit the downlink data packet to the eNB RLC entity.
  • step 1009 is independent of the aforementioned steps 1002 to 1008 .
  • the S-gNB After the S-gNB performs step 1001, the S-gNB will perform step 1009.
  • the eNB controls the eNB RLC entity to send downlink data packets to the UE PDCP entity.
  • step 1010 and the aforementioned steps 1008 to 1009 are independent of each other. However, immediately after step 1007, the eNB will perform step 1010.
  • the eNB controls the eNB RLC entity to transmit the aforementioned downlink data packets encrypted with the master key to the UE PDCP entity through the MAC layer and the physical layer. Since the UE PDCP entity also adopts the master station key, the UE PDCP entity can decrypt the downlink data packet and obtain the service data in the downlink data packet.
  • both the UE and the S-gNB use the master key, and the UE still uses the master key after receiving the aforementioned first indication information. Therefore, the UE PDCP entity can decrypt the downlink data packets encrypted by the S-gNB PDCP entity using the master key. Therefore, the S-gNB controls the S-gNB PDCP entity to send downlink data packets to the eNB PDCP entity, and then the eNB controls the eNB RLC entity to send downlink data packets to the UE PDCP entity.
  • Such an embodiment can enable the UE to receive a part of downlink data packets buffered in the S-gNB before the T-gNB starts to transmit the downlink data packets after the S-gNB sends the secondary carrier change request. Therefore, the time for interrupting the transmission of downlink data packets can be shortened, the network delay can be shortened, and the probability of UE service interruption can be reduced.
  • the T-gNB notifies the eNB that the random access is completed.
  • step 1011 and the aforementioned steps 1009 to 1010 are independent of each other, and this step 1011 may be executed after step 1008 .
  • the eNB sends an evolved radio access bearer modification indication (E-RAB modification indication) to the MME.
  • E-RAB modification indication evolved radio access bearer modification indication
  • the evolved radio access bearer modification indication is used to request the MME to switch the transmission path to the T-gNB.
  • the MME sends a path switch request (path switch request) to the S-GW.
  • the path switching request is used to request the S-GW to transmit the subsequent downlink data packets to the T-gNB. Therefore, the T-gNB PDCP entity will receive downlink data packets from the aforementioned S-GW.
  • the S-GW sends a path switch request acknowledgement (path switch request acknowledge) to the MME.
  • the path switch request response is used to indicate that the switch has been completed.
  • the S-GW sends an end marker (end marker) data packet to the S-gNB.
  • the end marker data packet is the last data packet sent by the S-GW to the S-gNB, and is used to indicate that after the end marker data packet, the S-GW no longer sends downlink data packets to the S-gNB.
  • the S-gNB forwards the aforementioned end marker data packet to the eNB.
  • the eNB forwards the aforementioned end marker data packet to the T-gNB.
  • the S-gNB forwards the aforementioned end marker data packet to the T-gNB through the eNB to indicate that the last data packet has been forwarded to the T-gNB.
  • the T-gNB After the T-gNB receives the end marker data packet, the T-gNB will perform step 1021 .
  • the S-gNB sends a system frame number status transfer (SN status transfer) to the eNB.
  • SN status transfer system frame number status transfer
  • the eNB sends the foregoing system frame number status forwarding to the T-gNB.
  • the system frame number status forwarding is used to indicate the sequence number of the downlink data packet that has been transmitted by the current S-GW to the S-gNB. Sending the sequence number to the T-gNB enables the T-gNB to receive data packets after the sequence number from the S-GW in the subsequent process. Therefore, the T-gNB can avoid repeatedly receiving downlink data packets or missing downlink data packets.
  • steps 1016 to 1017 and steps 1018 to 1019 are independent of each other.
  • the MME sends an evolved radio access bearer modification indication complete (E-RAB modification indication complete) to the eNB.
  • E-RAB modification indication complete an evolved radio access bearer modification indication complete
  • the T-gNB controls the T-gNB PDCP entity to receive downlink data packets from the S-GW.
  • the T-gNB PDCP entity After the T-gNB receives the end marker data packet, the T-gNB PDCP entity is activated.
  • the T-gNB can control the T-gNB PDCP entity to receive downlink data packets from the S-GW. Since the T-gNB uses the master key when creating the T-gNB PDCP entity, the T-gNB PDCP entity encrypts the received downlink data packets with the master key, and then performs subsequent transmission.
  • the T-gNB controls the T-gNB PDCP entity to send downlink data packets to the T-gNB RLC entity and the eNB RLC entity.
  • the T-gNB controls the T-gNB RLC entity to send downlink data packets to the UE PDCP entity.
  • the eNB controls the eNB RLC entity to send downlink data packets to the UE PDCP entity.
  • step 1023 and step 1024 are performed simultaneously.
  • FIG. 9C and FIG. 9D are used as examples for description.
  • the core network device in the aforementioned FIG. 9C and FIG. 9D is the S-GW
  • the primary network device is the eNB
  • the source secondary network device is the S-gNB
  • the target secondary network device is the T-gNB
  • the terminal device is the UE.
  • the S-GW sends the downlink data packet to the S-gNB PDCP entity 07, and the S-gNB PDCP entity 07 encrypts and decrypts the downlink data packet using the master station key, and controls the S-gNB PDCP entity 07 to use the master station key
  • the key encrypted downlink data packet is transmitted to the eNB RLC entity 05, and then the eNB RLC entity 05 transmits the aforementioned downlink data packet to the UE PDCP entity 01 through the MAC layer and the physical layer.
  • the UE can control the UE PDCP entity 01 to decrypt the downlink data packet by using the master station key, so as to obtain the service data of the downlink data packet.
  • the S-GW sends the downlink data packet to the T-gNB PDCP entity 10, the T-gNB PDCP entity 10 encrypts and decrypts the downlink data packet using the master station key, and controls the T-gNB PDCP entity 10 to use the master station key
  • the key-encrypted downlink data packets are transmitted to the eNB RLC entity 05 and the T-gNB RLC entity 11, and then the eNB RLC entity 05 and the T-gNB RLC entity 11 respectively transmit the aforementioned downlink data packets to the UE PDCP entity 01, so that the The UE can control the UE PDCP entity 01 to decrypt the downlink data packet using the master station key, and then obtain the service data of the downlink data packet.
  • the primary network device initiates the change of the secondary network device
  • the signaling interaction process among the primary network device, the source secondary network device, the target secondary network device and the terminal device is shown.
  • the terminal device receives downlink data packets from the core network through the primary network device and the source secondary network device, and uses the key of the primary network device (ie, the master key) to encrypt and decrypt data.
  • the primary network device ie, the master key
  • the primary network device When the primary network device is ready to change the source secondary network device to the target secondary network device, the primary network device, the source secondary network device (ie the secondary network device to be deleted) and the target secondary network device (ie the secondary network device to be added) ) will perform the following steps:
  • the primary network device sends a third message to the target secondary network device.
  • the target secondary network device uses the master station key to create a PDCP entity of the target secondary network device.
  • the target secondary network device sends a second message to the primary network device.
  • the primary network device sends the first message to the terminal device.
  • steps 1101 to 1104 are the same as the aforementioned steps 902 to 905 .
  • steps 1101 to 1104 are the same as the aforementioned steps 902 to 905 .
  • the primary network device since the secondary carrier change is initiated by the primary network device, the primary network device needs to add the target secondary network device first, and then delete the source secondary network device. Therefore, after performing the aforementioned steps 1101 to 1104 , the primary network device will perform step 1105 .
  • the primary network device sends a secondary carrier release request to the source secondary network device.
  • the secondary carrier release request is used to notify the source secondary network device to prepare for release.
  • the source secondary network device sends a secondary carrier release request response to the primary network device.
  • the secondary carrier release request response is used to indicate that the source secondary network device has been confirmed and will be released in the subsequent process.
  • the source secondary network device since the carrier change is initiated by the primary network device, the source secondary network device performs the release process only when the source secondary network device receives the aforementioned secondary carrier release request. Therefore, steps 1105 and 1106 will be used as trigger sources to trigger the source secondary network device to execute step 1107 .
  • the source secondary network device controls the PDCP entity of the source secondary network device to send a downlink data packet to the RLC entity of the primary network device.
  • the primary network device controls the RLC entity of the primary network device to send downlink data packets to the terminal device.
  • steps 1107 to 1108 are the same as the aforementioned steps 906 to 907 .
  • steps 1107 to 1108 are the same as the aforementioned steps 906 to 907 .
  • both the terminal device and the source-secondary network device use the master key, and the terminal device still uses the master key after receiving the aforementioned first indication information. Therefore, the PDCP entity of the terminal device can decrypt the downlink data packets encrypted by the PDCP entity of the source secondary network device using the master key. Therefore, the source auxiliary network device controls the PDCP entity of the source auxiliary network device to send the downlink data packet to the PDCP entity of the main network device, and then the main network device controls the RLC entity of the main network device to send the downlink data packet to the terminal device. The layer and the physical layer transmit the downlink data packet to the PDCP entity of the terminal device.
  • Such an implementation enables the terminal device to receive a part of downlink data packets buffered in the source secondary network device before the target secondary network device starts to transmit downlink data packets after the source secondary network device sends a secondary carrier change request. Therefore, the time for interrupting the transmission of downlink data packets can be shortened, the network delay can be shortened, and the probability of service interruption of the terminal equipment can be reduced.
  • the following takes the primary network device as eNB, the source secondary network device as S-gNB, the target secondary network device as T-gNB, and the terminal device as UE as an example. To go further:
  • the eNB sends a secondary carrier addition request (SgNB addition request) to the T-gNB.
  • SgNB addition request a secondary carrier addition request
  • the secondary carrier addition request carries the primary station key (that is, the eNB's key), and the secondary carrier addition request is used to notify the T-gNB to use the primary station key to establish a PDCP entity.
  • the T-gNB uses the master key to create a T-gNB PDCP entity.
  • step 1202 although the T-gNB uses the master station key to create a PDCP entity, the PDCP entity has not been activated and cannot immediately participate in data transmission.
  • the T-gNB sends a secondary carrier addition request response (SgNB addition request acknowledge) to the eNB.
  • SgNB addition request acknowledge a secondary carrier addition request response
  • the secondary carrier addition request response carries first indication information
  • the first indication information is used to instruct the T-gNB to confirm that the PDCP entity will be created by using the primary station key.
  • the first indication information is represented by an information element that the T-gNB fills in the SgNB to MeNB Container.
  • step 1202 and step 1203 are not clearly defined in time sequence. That is to say, the T-gNB may perform step 1202 first and then step 1203, or may perform step 1203 first and then perform step 1202, and may also perform step 1202 and step 1203 at the same time, which is not limited herein.
  • the eNB sends RRC reconfiguration (RRC connection reconfiguration) signaling to the UE.
  • RRC reconfiguration RRC connection reconfiguration
  • the eNB After the eNB receives the carrier addition request response from the T-gNB, the eNB can determine that the T-gNB will use the master key to create the PDCP entity. Therefore, the eNB will send RRC reconfiguration signaling to the UE, where the RRC reconfiguration signaling carries the first indication information carried in the carrier addition request response.
  • the UE When the UE recognizes the first indication information in the foregoing RRC reconfiguration signaling, the UE can learn to use the master key. Since the PDCP entity of the UE uses the master key before, the UE can continue to use the PDCP entity using the master key without rebuilding the PDCP entity using the new key. Therefore, in the subsequent steps, when the downlink data packet encrypted with the master key is transmitted to the UE, the UE can use the PDCP entity to decrypt the downlink data packet, and then obtain the service data in the downlink data packet.
  • RRC reconfiguration signaling may also carry other parameters for reconfiguration, which are not specifically limited here.
  • the UE sends an RRC reconfiguration complete (RRC connection reconfiguration complete) signaling to the eNB.
  • RRC reconfiguration complete RRC connection reconfiguration complete
  • the RRC reconfiguration completion signaling is used to notify the eNB that the UE has received the aforementioned first indication information and completed the related reconfiguration.
  • the eNB after the eNB receives the RRC reconfiguration completion signaling from the UE, the eNB will initiate a secondary carrier release procedure to the S-gNB. The eNB will perform step 1206.
  • the eNB sends a secondary carrier release request (SgNB release request) to the S-gNB.
  • SgNB release request a secondary carrier release request
  • the S-gNB after the S-gNB receives the secondary carrier release request from the eNB, the S-gNB will perform steps 1207 and 1208 . It should be understood that there is no definite time sequence limitation between step 1207 and step 1208 . That is to say, the S-gNB may perform step 1207 first and then step 1208, or may perform step 1208 first and then perform step 1207, and may also perform step 1207 and step 1208 at the same time. There is no specific limitation here.
  • the S-gNB sends a secondary carrier release request response (SgNB release request acknowledge) to the eNB.
  • SgNB release request acknowledge a secondary carrier release request response
  • the S-gNB controls the S-gNB PDCP entity to send downlink data packets to the eNB RLC entity.
  • the downlink data packet in step 1208 comes from the downlink data packet from the serving gateway S-GW.
  • the S-gNB PDCP entity will use the master key to encrypt the downlink data packet from the S-GW, and then control the S-gNB PDCP entity to transmit the downlink data packet to the eNB RLC entity.
  • the eNB sends secondary carrier reconfiguration complete (SgNB reconfiguration complete) signaling to the T-gNB.
  • SgNB reconfiguration complete secondary carrier reconfiguration complete
  • the secondary carrier reconfiguration completion signaling is used to notify the T-gNB that the aforementioned UE has been reconfigured, and the T-gNB can start to prepare for the random access of the UE.
  • the UE initiates a random access procedure to the T-gNB.
  • the random access process between the UE and the T-gNB is similar to the random access process between the UE and the gNB in the foregoing step 407 .
  • the relevant introduction in the foregoing step 407 please refer to the relevant introduction in the foregoing step 407 , which will not be repeated here.
  • the UE When the UE successfully accesses the T-gNB, it means that the UE can receive downlink data packets from the aforementioned T-gNB thereafter. It can also be understood that the T-gNB can provide services for the aforementioned UE.
  • the eNB controls the eNB RLC entity to send downlink data packets to the UE PDCP entity.
  • step 1211 and the aforementioned steps 1209 to 1210 are independent of each other. However, immediately after step 1208, the eNB will perform step 1211.
  • the eNB controls the eNB RLC entity to transmit the aforementioned downlink data packets encrypted with the master key to the UE PDCP entity through the MAC layer and the physical layer. Since the UE PDCP entity also adopts the master station key, the UE PDCP entity can decrypt the downlink data packet and obtain the service data in the downlink data packet.
  • both the UE and the S-gNB use the master key, and the UE still uses the master key after receiving the aforementioned first indication information. Therefore, the UE PDCP entity can decrypt the downlink data packets encrypted by the S-gNB PDCP entity using the master key. Therefore, the S-gNB controls the S-gNB PDCP entity to send downlink data packets to the eNB PDCP entity, and then the eNB controls the eNB RLC entity to send downlink data packets to the UE, which are transmitted to the UE PDCP entity through the MAC layer and the physical layer.
  • Such an embodiment can enable the UE to receive a part of downlink data packets buffered in the S-gNB before the T-gNB starts to transmit the downlink data packets after the S-gNB sends the secondary carrier change request. Therefore, the time for interrupting the transmission of downlink data packets can be shortened, the network delay can be shortened, and the probability of UE service interruption can be reduced.
  • the T-gNB notifies the eNB that the random access is completed.
  • the eNB sends an evolved radio access bearer modification indication (E-RAB modification indication) to the MME.
  • E-RAB modification indication evolved radio access bearer modification indication
  • the MME sends a path switch request (path switch request) to the S-GW.
  • the S-GW sends a path switch request acknowledgement (path switch request acknowledge) to the MME.
  • the S-GW sends an end marker (end marker) data packet to the S-gNB.
  • the S-gNB forwards the aforementioned end marker data packet to the eNB.
  • the eNB forwards the aforementioned end marker data packet to the T-gNB.
  • the S-gNB sends a system frame number status transfer (SN status transfer) to the eNB.
  • SN status transfer system frame number status transfer
  • the eNB sends the foregoing system frame number status forwarding to the T-gNB.
  • the MME sends an evolved radio access bearer modification indication complete (E-RAB modification indication complete) to the eNB.
  • E-RAB modification indication complete an evolved radio access bearer modification indication complete
  • the T-gNB controls the T-gNB PDCP entity to receive downlink data packets from the S-GW.
  • the T-gNB controls the T-gNB PDCP entity to send downlink data packets to the T-gNB RLC entity and the eNB RLC entity.
  • the T-gNB controls the T-gNB RLC entity to send downlink data packets to the UE PDCP entity.
  • the eNB controls the eNB RLC entity to send downlink data packets to the UE PDCP entity.
  • steps 1213 to 1225 are the same as the aforementioned steps 1012 to 1024 .
  • steps 1213 to 1225 are the same as the aforementioned steps 1012 to 1024 .
  • steps 1213 to 1225 are the same as the aforementioned steps 1012 to 1024 .
  • steps 1213 to 1225 are the same as the aforementioned steps 1012 to 1024 .
  • this embodiment provides a schematic structural diagram of a communication device 130 .
  • the UEs in the method embodiments may all be based on the structure of the communication device 130 shown in FIG. 13 in this embodiment.
  • the communication device 130 includes at least one processor 1301 , at least one memory 1302 and at least one transceiver 1303 .
  • the processor 1301 , the memory 1302 and the transceiver 1303 are connected.
  • the communication device 130 may further include an input device 1305 , an output device 1306 and one or more antennas 1304 .
  • the antenna 1304 is connected to the transceiver 1303 , and the input device 1305 and the output device 1306 are connected to the processor 1301 .
  • the memory 1302 is mainly used for storing software programs and data.
  • the memory 1302 may exist independently and be connected to the processor 1301 .
  • the memory 1302 may be integrated with the processor 1301, for example, in one or more chips.
  • the memory 1302 can store program codes for implementing the technical solutions of the embodiments of the present application, and is controlled and executed by the processor 1301 .
  • FIG. 13 in this embodiment only shows one memory and one processor, but, in practical applications, the communication device 130 may have multiple processors or multiple memories, which is not specifically described here. limited.
  • the memory 1302 may also be referred to as a storage medium or a storage device or the like.
  • the memory 1302 may be a storage element on the same chip as the processor (ie, an on-chip storage element), or an independent storage element, which is not limited in this embodiment of the present application.
  • the transceiver 1303 may be used to support the reception or transmission of radio frequency signals between the communication device 130 and the access network device, and the transceiver 1303 may be connected to the antenna 1304 .
  • the transceiver 1303 includes a transmitter Tx and a receiver Rx.
  • one or more antennas 1304 can receive radio frequency signals
  • the receiver Rx of the transceiver 1303 is configured to receive the radio frequency signals from the antenna 1304, convert the radio frequency signals into digital baseband signals or digital intermediate frequency signals, and convert the radio frequency signals into digital baseband signals or digital intermediate frequency signals.
  • the digital baseband signal or digital intermediate frequency signal is provided to the processor 1301, so that the processor 1301 performs further processing on the digital baseband signal or digital intermediate frequency signal, such as demodulation processing and decoding processing.
  • the transmitter Tx in the transceiver 1303 is also used to receive the modulated digital baseband signal or digital intermediate frequency signal from the processor 1301, and convert the modulated digital baseband signal or digital intermediate frequency signal into a radio frequency signal, and pass a
  • the radio frequency signal is transmitted by the antenna or antennas 1304.
  • the receiver Rx can selectively perform one or more stages of down-mixing processing and analog-to-digital conversion processing on the radio frequency signal to obtain a digital baseband signal or a digital intermediate frequency signal.
  • the sequence of the aforementioned down-mixing processing and analog-to-digital conversion processing The order is adjustable.
  • the transmitter Tx can selectively perform one or more stages of up-mixing processing and digital-to-analog conversion processing on the modulated digital baseband signal or digital intermediate frequency signal to obtain a radio frequency signal, and the up-mixing processing and digital-to-analog conversion processing
  • the sequence of s is adjustable.
  • Digital baseband signals and digital intermediate frequency signals can be collectively referred to as digital signals.
  • the aforementioned transceiver 1303 may also be referred to as a transceiver unit, a transceiver, a transceiver device, and the like.
  • the device used to implement the receiving function in the transceiver unit may be regarded as a receiving unit
  • the device used to implement the transmitting function in the transceiver unit may be regarded as a transmitting unit, that is, the transceiver unit includes a receiving unit and a transmitting unit, and the receiving unit also It can be called a receiver, an input port, a receiving circuit, etc.
  • the sending unit can be called a transmitter, a transmitter, or a transmitting circuit, etc.
  • the processor 1301 may be a baseband processor or a central processing unit (central processing unit, CPU), and the baseband processor and the CPU may be integrated or separated.
  • the processor 1301 can be used to implement various functions for the terminal device, for example, to process communication protocols and communication data, or to control the entire terminal device, execute software programs, and process data of software programs; or It is used to assist in completing computing processing tasks, such as graphics and image processing or audio processing, etc.; or the processor 1301 is used to implement one or more of the above functions.
  • the output device 1306 communicates with the processor 1301, and can display information in various ways, which is not specifically limited here.
  • the transceiver 1303 can receive the first message sent by the main network device.
  • the terminal device uses the key of the main network device to encrypt and decrypt data before the carrier is changed, and the first message is used to instruct the terminal device to use the key of the main network device stored in the terminal device to perform encryption and decryption after the carrier is changed. Encrypt and decrypt data.
  • the processor 1301 controls the PDCP entity of the terminal device to receive a downlink data packet from the RLC entity of the main network device, and the downlink data packet comes from the PDCP entity of the main network device.
  • the terminal device The PDCP entity uses the key of the main network device to encrypt and decrypt the downlink data packet.
  • the processor 1301 controls the PDCP entity of the terminal device to receive a downlink data packet from the RLC entity of the primary network device, and the downlink data packet comes from the PDCP entity of the secondary network device.
  • the processor 1301 controls the PDCP entity of the terminal device to receive a downlink data packet from the RLC entity of the primary network device, and the downlink data packet comes from the PDCP entity of the secondary network device.
  • both the PDCP entity of the terminal device and the PDCP entity of the secondary network device use the key of the primary network device to encrypt and decrypt the downlink data packet.
  • this embodiment provides a schematic structural diagram of another communication device 140 .
  • both the eNB and the gNB in the method embodiment corresponding to FIG. 12 may be based on the structure of the communication device 140 shown in FIG. 14 in this embodiment.
  • the subsequent evolved access network or base station may also use the communication shown in FIG. 14 in this embodiment. Structure of device 140.
  • the communication device 140 includes at least one processor 1401 , at least one memory 1402 , at least one transceiver 1403 , at least one network interface 1405 and one or more antennas 1404 .
  • the processor 1401 , the memory 1402 , the transceiver 1403 and the network interface 1405 are connected by connecting means, and the antenna 1404 is connected with the transceiver 1403 .
  • the aforementioned connection device may include various types of interfaces, transmission lines, or buses, which are not limited in this embodiment.
  • the aforementioned network interface 1405 is used to connect the communication device 140 with other communication devices through a communication link.
  • the network interface 1405 may include a network interface between the communication device 140 and a core network element, such as an S1 interface; the network interface 1405 may also include the communication device 140 and other network devices (such as other access network devices) or network interface between core network elements), such as X2 or Xn interface.
  • transceiver 1403, the memory 1402, and the antenna 1404 reference may be made to the related descriptions of the transceiver 1303, the memory 1302, and the antenna 1304 in the embodiment corresponding to FIG. 13, and details are not repeated here.
  • the aforementioned processor 1401 is mainly used to process communication protocols and communication data, control the entire network device, execute software programs, and process data of software programs, for example, to support the communication device 140 to execute the above-mentioned embodiments. described action.
  • the communication device 140 may include a baseband processor and a central processing unit, wherein the baseband processor is mainly used to process communication protocols and communication data, and the central processing unit is mainly used to control the entire communication device 140, execute software programs, and process software. program data.
  • the processor 1401 in FIG. 14 can integrate the functions of the baseband processor and the central processing unit. Those skilled in the art can understand that the baseband processor and the central processing unit can also be independent processors, which are interconnected through technologies such as buses.
  • the communication device 140 may include multiple baseband processors to adapt to different network standards, the communication device 140 may include multiple central processors to enhance its processing capability, and the various components of the communication device 140 may use various bus connection.
  • the baseband processor may also be expressed as a baseband processing circuit or a baseband processing chip.
  • the central processing unit can also be expressed as a central processing circuit or a central processing chip.
  • the function of processing the communication protocol and communication data may be built in the processor, or may be stored in the memory in the form of a software program, and the processor executes the software program to realize the baseband processing function.
  • the communication device 140 is the main network device:
  • the transceiver 1403 can send a first message to the terminal device.
  • the first message is used to instruct the terminal device to encrypt and decrypt data using the key (master key) of the main network device stored by the terminal device after the carrier is changed.
  • the transceiver 1403 can receive a second message sent by the secondary network device, the second message is used to instruct the secondary network device to confirm that a change will occur, and the second message carries the configuration configured by the secondary network device. the first indication information.
  • the transceiver 1403 can send a third message to the secondary network device, where the third message carries the key of the primary network device, and the third message is used to instruct the secondary network device to use the primary network The device's key to encrypt and decrypt data.
  • the processor 1403 can control the PDCP entity of the main network device to send a downlink data packet to the RLC entity of the main network device, and control the RLC entity of the main network device to send the downlink data packet Sent to the PDCP entity of the terminal device.
  • the processor 1403 can control the RLC entity of the primary network device to receive the downlink data packet from the PDCP entity of the secondary network device, and the PDCP entity of the secondary network device uses the key of the primary network device to encrypt and decrypt the downlink data packet ;
  • the RLC entity controlling the primary network device sends the downlink data packet to the PDCP entity of the terminal device, and the PDCP entity of the terminal device encrypts and decrypts the downlink data packet using the key of the primary network device.
  • the processor 1403 controls the RLC entity of the primary network device to receive downlink data packets from the PDCP entity of the source secondary network device, and the PDCP entity of the source secondary network device uses the key of the primary network device to encrypt and decrypt the downlink data.
  • the main network device controls the RLC entity of the main network device to send the downlink data packet to the PDCP entity of the terminal device, and the PDCP entity of the terminal device encrypts and decrypts the downlink data packet using the key of the main network device.
  • the processor 1401 uses the key of the primary network device to create a PDCP entity.
  • the communication device 140 is a secondary network device:
  • the transceiver 1403 can receive a third message sent by the primary network device, where the third message carries the key of the primary network device, and the third message is used to instruct the secondary network device to use the primary network The device's key to encrypt and decrypt data.
  • the transceiver 1403 can send a second message to the primary network device, the second message is used to instruct the secondary network device to confirm that a change will occur, and the second message carries the configuration configured by the secondary network device.
  • the first indication information where the first indication information is used to indicate that the key of the main network device is used to encrypt and decrypt data.
  • the processor 1401 uses the key of the primary network device to create a PDCP entity.
  • this embodiment provides another communication device 150, and the communication device 150 may be a terminal device or a chip in the terminal device.
  • the communication device 150 includes a transceiver unit 1501 and a processing unit 1502 .
  • this embodiment provides another communication device 160 .
  • the communication device 160 may be a main network device or a chip in the main network device; or a secondary network device or a chip in the auxiliary network device.
  • the communication device 160 includes a transceiver unit 1601 and a processing unit 1602 .
  • the transceiver unit 1501 and the transceiver unit 1601 can be a sending unit or a transmitter when sending information, and the transceiver unit 1501 and The transceiver unit 1601 may be a receiving unit or a receiver when receiving information.
  • the aforementioned transceiver unit may be a transceiver, and the transceiver, transmitter or receiver may be a radio frequency circuit, when the terminal device or the user equipment includes a storage unit, the storage unit is used for storing computer instructions, and the processor is connected in communication with the memory,
  • the processor executes the computer instructions stored in the memory, so that the terminal device, the primary network device, and the secondary network device execute the methods involved in the method embodiments corresponding to FIG. 2 , FIG. 3A , FIG. 5A , FIG. 7 , FIG. 9A and FIG.
  • the eNB and the gNB execute the methods involved in the embodiments corresponding to FIG. 4 , FIG. 6 , FIG. 8 , FIG. 10 , and FIG. 12 .
  • processing unit 1502 and processing unit 1602 may be a general-purpose central processing unit (CPU), a microprocessor, a digital signal processor (DSP), or a microcontroller (MCU).
  • the processor can be a separate semiconductor chip, or can be integrated with other circuits into a semiconductor chip, for example, it can form a system-on-chip with other circuits (such as codec circuits, hardware acceleration circuits, or various bus and interface circuits). system-on-a-chip, SoC), or can also be integrated in the ASIC as a built-in processor of an application specific integrated circuit (ASIC).
  • ASIC application specific integrated circuit
  • the transceiver unit 1501 and the transceiver unit 1601 may be input and/or output interfaces, pins or circuits Wait.
  • the aforementioned processing unit 1502 may be a processor of a chip in the terminal device
  • the processing unit 1602 may be a processor of a chip in the access network device.
  • the processor can execute the computer-executed instructions stored in the storage unit, so that the chip in the terminal device and the chip in the access network device execute the instructions shown in Figure 2, Figure 3A, Figure 4, Figure 5A, Figure 6, Figure 7, Figure 8, 9A , 10 , 11 , and 12 correspond to the methods involved in the embodiments.
  • the storage unit is a storage unit in the chip, such as a register, a cache, etc., and the storage unit may also be a storage unit in the terminal device located outside the chip.
  • ROM read only memory
  • RAM random access memory
  • the aforementioned terminal device may have functional units (means) corresponding to the steps of the method or process of the terminal device
  • the aforementioned access network device may have functional units corresponding to the steps of the method or process of the access network device.
  • One or more of the above modules or units may be implemented in software, hardware or a combination of both.
  • the software exists in the form of computer program instructions and is stored in the memory, and the processor can be used to execute the program instructions to implement the above method flow.
  • the embodiment of the present application further provides a communication system, where the communication system includes a terminal device and an access network device.
  • the communication system includes a terminal device and an access network device.
  • the communication device 130 in the embodiment corresponding to FIG. 13
  • the structure of the primary network device or the secondary network device refer to the communication device 140 in the embodiment corresponding to FIG. 14 .
  • the chip in the terminal device may refer to the communication device 150 in the embodiment corresponding to FIG. 15; when the aforementioned primary network device or secondary network device is a chip, the primary network device or secondary network device
  • the communication device 160 in the corresponding embodiment of FIG. 16 .
  • each step of the above-mentioned method can be completed by an integrated logic circuit of hardware in the processor or an instruction in the form of software.
  • the steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware processor, or executed by a combination of hardware and software modules in the processor.
  • the software module may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art.
  • 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, detailed description is omitted here. It should also be understood that the first, second, third, fourth and various numeral numbers involved in this document are only distinctions made for convenience of description, and are not used to limit the scope of the embodiments of the present application.
  • the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not be dealt with in the embodiments of the present application. implementation constitutes any limitation.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例公开了一种数据传输方法以及相关设备,应用于非独立组网的选项3X中。该数据传输方法涉及主网络设备、辅网络设备和终端设备。当载波发生变更(例如,添加辅网络设备、删除辅网络设备或者变更辅网络设备)时,主网络设备将向终端设备发送第一消息。其中,终端设备在载波变更之前采用该主网络设备的密钥进行加解密数据,第一消息用于指示该终端设备在载波变更之后仍旧采用终端设备存储的主网络设备的密钥进行加解密数据。由于,在载波变更前后,终端设备均采用主网络设备的密钥,终端设备不需要变更密钥,也无需重建PDCP实体。因此,能够减少终端设备因重建PDCP实体而产生的网络延迟,进而降低由载波变更而导致数据业务中断的几率。

Description

一种数据传输方法以及相关设备
本申请要求于2020年07月27日提交中国专利局、申请号为202010731310.6、发明名称为“一种数据传输方法以及相关设备”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信领域,尤其涉及一种数据传输方法以及相关设备。
背景技术
选项3X(Option3X)是非独立组网(non-standalone,NSA)模式中的一种普通使用的组网模式。在该模式下,核心网沿用LTE核心网,接入网设备采用LTE的接入网设备或NR的接入网设备。
在选项3X组网下,NR用户可以通过LTE接入网设备将接入信令通过LTE S1-C接口与LTE核心网交互,数据面通过NR PDCP向NR RLC和LTE RLC分流。在这种组网方式下,由于终端设备的移动,常导致载波的变更。当载波变更时,终端设备需要变更密钥,并且需要采用变更后的密钥重建PDCP实体,以使得该终端设备重建的PDCP实体使用变更后的密钥进行加解密数据。
由于,终端设备在重建PDCP实体的过程中无法接收来自网络设备的数据,因此,会产生网络延迟,导致辅载波变更过程中出现短暂数据业务中断,影响用户体验。
发明内容
本申请实施例提供了一种数据传输方法以及相关设备,用于在载波变更时减少终端设备产生的网络延迟,进而降低由载波变更而导致数据业务中断的几率。
第一方面,本申请实施例提供了一种数据传输方法,该数据传输方法涉及主网络设备、辅网络设备和终端设备。当载波发生变更(例如,添加辅网络设备、删除辅网络设备或者变更辅网络设备)时,该主网络设备将向终端设备发送第一消息。其中,该终端设备在载波变更之前采用该主网络设备的密钥进行加解密数据,该第一消息用于指示该终端设备在载波变更之后仍旧采用该终端设备存储的该主网络设备的密钥进行加解密数据。
本申请实施例中,在载波变更时,由于,该终端设备已存储了前述主网络设备的密钥,并且,在载波变更之后,该终端设备依旧采用的是主网络设备的密钥。也就是说,在载波变更期间,终端设备不变更密钥,终端设备无需重建PDCP实体。因此,在载波变更时减少终端设备因重建PDCP实体而产生的网络延迟,进而可以降低由载波变更而导致数据业务中断的几率。
基于前述第一方面,在一种可选的实施方式中,该第一消息为无线资源控制RRC重配置消息,该RRC重配置消息携带第一指示信息,该第一指示信息用于指示采用该主网络设 备的密钥进行加解密数据。
本实施方式中,提出前述第一消息是通过第一指示信息指示终端设备仍旧采用主网络设备的密钥,无需将主网络设备的密钥发送给终端设备,有利于保证通信安全。
基于前述第一方面或前述可选的实施方式,在另一种可选的实施方式中,该主网络设备向终端设备发送第一消息之前,该方法还包括:该主网络设备接收辅网络设备发送的第二消息,该第二消息用于指示该辅网络设备确认将发生变更,该第二消息携带由该辅网络设备配置的该第一指示信息。
本实施方式中,提出主网络设备发送给终端设备的第一指示信息是由辅网络设备携带于第二消息中的,当主网络设备收到前述第一指示信息之后,便将该第一指示信息转发给终端设备。
基于前述第一方面或前述可选的实施方式,在另一种可选的实施方式中,该主网络设备接收辅网络设备发送的第二消息之前,该方法还包括:该主网络设备向该辅网络设备发送第三消息,该第三消息携带该主网络设备的密钥,该第三消息用于指示该辅网络设备采用该主网络设备的密钥进行加解密数据。
本实施方式中,提出辅网络设备在向主网络设备发送前述第一指示信息之前,该辅网络设备接收到来自主网络设备的主站密钥。因此,该辅网络设备便将在后续过程中采用主网络设备的密钥创建辅网络设备的PDCP实体。由于,辅网络设备和终端设备均采用主网络设备的密钥,因此,在后续的辅网络设备和终端设备的数据交互过程中,可以避免因密钥不一致而造成的数据传输中断。
基于前述第一方面或前述可选的实施方式,在另一种可选的实施方式中,当前述载波变更过程为主网络设备添加辅网络设备时,前述第三消息为辅载波添加请求,该辅载波添加请求用于请求添加该辅网络设备作为辅载波;前述第二消息为辅载波添加请求响应,该辅载波添加请求响应用于指示该辅网络设备确认添加,且该辅网络设备将采用该主站的密钥进行加解密。
本实施方式中,提出了当主网络设备添加辅网络设备时,前述第三消息和第二消息的一种可选的实施方式。也就是说,可以将前述主网络设备的密钥携带于辅载波添加请求,将前述第一指示信息携带于辅载波添加请求响应中。
基于前述第一方面或前述可选的实施方式,在另一种可选的实施方式中,该方法还包括:该主网络设备控制该主网络设备的PDCP实体向该主网络设备的RLC实体发送下行数据包,并且,控制该主网络设备的RLC实体将该下行数据包发送至该终端设备,该终端设备的PDCP实体采用该主网络设备的密钥加解密该下行数据包。
应当理解的是,该下行数据包从该主网络设备的RLC实体传输至终端设备的PDCP实体的过程中,还将经历主网络设备的MAC实体、主网络设备的物理层、终端设备的物理层、终端设备的MAC实体以及终端设备的RLC实体等。本申请实施例仅限定前述主网络设备的RLC实体能够将下行数据包传输至终端设备的PDCP实体,不对这两个实体之间的具体传输过程进行限定。
本实施方式中,由于主网络设备、终端设备、辅网络设备均采用主网络设备的密钥, 因此,在辅网络设备的PDCP实体还未被激活时,终端设备可以用主网络设备的密钥通过终端设备的PDCP实体接收来自主网络设备的RLC实体的下行数据包。由于,在辅网络设备的PDCP实体还未激活的情况下,终端设备也能够接收下行数据包,因此,该终端设备不会因重建PDCP实体而造成时延,能够有效降低数据传输中断的几率。
基于前述第一方面或前述可选的实施方式,在另一种可选的实施方式中,当前述载波变更过程为由主网络设备发起删除辅网络设备时,该主网络设备向终端设备发送第一消息之前,该方法还包括:该主网络设备向辅网络设备发送辅载波释放请求,该辅载波释放请求用于通知该辅网络设备进行释放;该主网络设备接收该辅网络设备发送的辅载波释放响应,该辅载波释放响应用于指示该辅网络设备确认释放。
基于前述第一方面或前述可选的实施方式,在另一种可选的实施方式中,当前述载波变更过程为由辅网络设备发起删除该辅网络设备时,该主网络设备向终端设备发送第一消息之前,该方法还包括:该主网络设备接收辅网络设备发送的辅载波释放请求,该辅载波释放请求用于请求释放该辅网络设备;该主网络设备向该辅网络设备发送辅载波释放确认消息,该辅载波释放确认消息用于指示允许该辅网络设备进行释放。
基于前述第一方面或前述可选的实施方式,在另一种可选的实施方式中,无论是主网络设备发起的删除辅网络设备,还是辅网络设备发起的删除辅网络设备,数据传输方法还包括:该主网络设备控制该主网络设备的RLC实体从该辅网络设备的PDCP实体接收下行数据包,该辅网络设备的PDCP实体采用该主网络设备的密钥加解密该下行数据包;该主网络设备控制该主网络设备的RLC实体将该下行数据包发送至该终端设备,该终端设备的PDCP实体采用该主网络设备的密钥加解密该下行数据包。
本实施方式中,辅网络设备将被删除,终端设备需要从同时接收来自主网络设备的RLC实体下行数据包和来自辅网络设备的RLC实体的下行数据包的状态,转变为仅从主网络设备的RLC实体接收下行数据包。由于,在该辅网络设备变更前后,该终端设备一直使用的是主网络设备的密钥,因此,即使前述辅网络设备的RLC实体不再向该终端设备的PDCP实体发送下行数据包,但该主网络设备的RLC实体仍旧向该终端设备的PDCP实体发送下行数据包,并且,该终端设备的PDCP实体能够采用主网络设备的密钥进行加解密数据。因此,能够缩短终端设备收不到下行数据包的时间,能够减少因收不到下行数据包而产生的时延。
基于前述第一方面或前述可选的实施方式,在另一种可选的实施方式中,当前述载波变更过程为从一个辅网络设备变更到另一个辅网络设备的过程时,前述实施方式中的辅网络设备可以理解为目标辅网络设备,即变更之后于主网络设备和终端设备进行数据交互的辅网络设备。而在变更之前,是源辅网络设备与前述主网络设备和终端设备进行数据交互。本实施方式以及后续实施方式均以,从源辅网络设备变更到目标辅网络设备为例进行介绍。此时,前述第二消息为辅载波添加请求响应,该第二消息用于指示该目标辅网络设备确认添加,且该目标辅网络设备将采用该主站的密钥进行加解密。
基于前述第一方面或前述可选的实施方式,在另一种可选的实施方式中,当由源辅网络设备发起变更到目标辅网络设备时,该主网络设备向该目标辅网络设备发送第三消息之 前,该方法还包括:该主网络设备接收该源辅网络设备发送的辅载波变更请求,该载波变更请求携带该目标辅网络设备的标识信息,该辅载波变更请求用于指示将该源辅网络设备变更为该目标辅网络设备。
基于前述第一方面或前述可选的实施方式,在另一种可选的实施方式中,当由主网络设备发起变更到源辅网络设备时,该主网络设备接收该目标辅网络设备发送的第二消息之后,该方法还包括:该主网络设备向该源辅网络设备发送载波释放请求,该载波释放请求用于请求释放该源辅网络设备;该主网络设备接收该源辅网络设备发送的载波释放请求响应,该载波释放请求响应用于确认释放。
基于前述第一方面或前述可选的实施方式,在另一种可选的实施方式中,无论是由源辅网络设备发起变更到目标辅网络设备,还是由主网络设备发起变更到源辅网络设备,该数据传输方法还包括:该主网络设备控制该主网络设备的RLC实体从该源辅网络设备的PDCP实体接收下行数据包,该源辅网络设备的PDCP实体采用该主网络设备的密钥加解密该下行数据包;该主网络设备控制该主网络设备的RLC实体将该下行数据包发送至该终端设备,该终端设备的PDCP实体采用该主网络设备的密钥加解密该下行数据包。
本实施方式中,将删除源辅网络设备并添加目标辅网络设备,由于刚添加的目标辅网络设备还未被激活,还无法立即向终端设备发送下行数据包。因此,终端设备需要从同时接收来自主网络设备的RLC实体下行数据包和来自源辅网络设备的RLC实体的下行数据包的状态,转变为仅从主网络设备的RLC实体接收下行数据包。由于,在该源辅网络设备变更前后,该终端设备一直使用的是主网络设备的密钥,因此,即使前述源辅网络设备的RLC实体不再向该终端设备的PDCP实体发送下行数据包,但该主网络设备的RLC实体仍旧向该终端设备的PDCP实体发送下行数据包,并且,该终端设备的PDCP实体能够采用主网络设备的密钥进行加解密数据。因此,能够缩短终端设备收不到下行数据包的时间,能够减少因收不到下行数据包而产生的时延。
第二方面,本申请实施例提供了一种数据传输方法,该数据传输方法涉及主网络设备、辅网络设备和终端设备。当载波发生变更(例如,添加辅网络设备、删除辅网络设备或者变更辅网络设备)时,该终端设备接收主网络设备发送的第一消息,该终端设备在载波变更之前采用该主网络设备的密钥进行加解密数据,该第一消息用于指示该终端设备在载波变更之后采用该终端设备存储的该主网络设备的密钥进行加解密数据。
本申请实施例中,在载波变更时,由于,该终端设备已存储了前述主网络设备的密钥,并且,在载波变更之后,该终端设备依旧采用的是主网络设备的密钥。也就是说,在载波变更期间,终端设备不变更密钥,终端设备无需重建PDCP实体。因此,在载波变更时减少终端设备因重建PDCP实体而产生的网络延迟,进而可以降低由载波变更而导致数据业务中断的几率。
基于前述第二方面,在一种可选的实施方式中,该第一消息为无线资源控制RRC重配置消息,该RRC重配置消息携带第一指示信息,该第一指示信息用于指示采用该主网络设备的密钥进行加解密数据。
本实施方式中,提出前述第一消息是通过第一指示信息指示终端设备仍旧采用主网络设备的密钥,无需将主网络设备的密钥发送给终端设备,有利于保证通信安全。
基于前述第二方面或前述可选的实施方式,在另一种可选的实施方式中,当前述载波变更过程为主网络设备添加辅网络设备时,该方法还包括:该终端设备控制该终端设备的PDCP实体接收来自该主网络设备的RLC实体的下行数据包,该下行数据包来自该主网络设备的PDCP实体,该终端设备的PDCP实体采用该主网络设备的密钥加解密该下行数据包。
本实施方式中,由于主网络设备、终端设备、辅网络设备均采用主网络设备的密钥,因此,在辅网络设备的PDCP实体还未被激活时,终端设备可以用主网络设备的密钥通过终端设备的PDCP实体接收来自主网络设备的RLC实体的下行数据包。由于,在辅网络设备的PDCP实体还未激活的情况下,终端设备也能够接收下行数据包,因此,该终端设备不会因重建PDCP实体而造成时延,能够有效降低数据传输中断的几率。
基于前述第二方面或前述可选的实施方式,在另一种可选的实施方式中,当前述载波变更过程为删除该辅网络设备时,该方法还包括:该终端设备控制该终端设备的PDCP实体接收来自该主网络设备的RLC实体的下行数据包,该下行数据包来自辅网络设备的PDCP实体,该辅网络设备为待释放的网络设备,该终端设备的PDCP实体和该辅网络设备的PDCP实体均采用该主网络设备的密钥加解密该下行数据包。
本实施方式中,辅网络设备将被删除,终端设备需要从同时接收来自主网络设备的RLC实体下行数据包和来自辅网络设备的RLC实体的下行数据包的状态,转变为仅从主网络设备的RLC实体接收下行数据包。由于,在该辅网络设备变更前后,该终端设备一直使用的是主网络设备的密钥,因此,即使前述辅网络设备的RLC实体不再向该终端设备的PDCP实体发送下行数据包,但该主网络设备的RLC实体仍旧向该终端设备的PDCP实体发送下行数据包,并且,该终端设备的PDCP实体能够采用主网络设备的密钥进行加解密数据。因此,能够缩短终端设备收不到下行数据包的时间,能够减少因收不到下行数据包而产生的时延。
此外,当前述载波变更过程为从一个辅网络设备变更到另一个辅网络设备的过程时,前述辅网络设备可以理解为源辅网络设备。
需要说明的是,本申请实施例还有多种具体其他实施方式,具体可参见第一方面的具体实施方式和其有益效果,在此不再赘述。
第三方面,本申请实施例提供了一种数据传输方法,该数据传输方法涉及主网络设备、辅网络设备和终端设备。当主网络设备发起添加辅网络设备时,该辅网络设备接收主网络设备发送的第三消息,该第三消息携带该主网络设备的密钥,该第三消息用于指示该辅网络设备采用该主网络设备的密钥进行加解密数据;然后,该辅网络设备向该主网络设备发送第二消息,该第二消息用于指示该辅网络设备确认将发生变更,该第二消息携带由该辅网络设备配置的第一指示信息,该第一指示信息用于指示采用该主网络设备的密钥进行加解密数据。
基于前述第三方面,在一种可选的实施方式中,前述第三消息为辅载波添加请求,该辅载波添加请求用于请求添加该辅网络设备作为辅载波;前述第二消息为辅载波添加请求响应,该辅载波添加请求响应用于指示该辅网络设备确认添加,且该辅网络设备将采用该主站的密钥进行加解密。
基于前述第三方面或前述可选的实施方式,在另一种可选的实施方式中,该方法还包括:该辅网络设备采用该主网络设备的密钥创建PDCP实体。
本实施方式中,由于辅网络设备采用的是主网络设备的密钥创建PDCP实体,因此,经过该辅网络设备的PDCP实体加密的下行数据包,可以经多个实体流转到终端设备的采用主网络设备的密钥的PDCP实体中。因此,无需终端设备重建PDCP实体,能够缩短终端设备收不到下行数据包的时间,能够减少因收不到下行数据包而产生的时延。
需要说明的是,本申请实施例还有多种具体其他实施方式,具体可参见第一方面的具体实施方式和其有益效果,在此不再赘述。
第四方面,本申请实施例提供了一种数据传输方法,该数据传输方法涉及主网络设备、辅网络设备和终端设备。当删除辅网络设备时,或者,当源辅网络设备变更至目标辅网络设备时,该数据传输方法包括:辅网络设备控制该辅网络设备的PDCP实体向主网络设备的RLC实体发送下行数据包,该辅网络设备的PDCP实体采用该主网络设备的密钥加解密该下行数据包。
本实施方式中,由于辅网络设备在获知将要被删除时,能够向主网络设备的RLC实体缓存一部分下行数据包,以使得该主网络设备控制该RLC实体将前述下行数据包发送至终端设备。由于,终端设备的PDCP实体和辅网络设备的PDCP实体均采用的主网络设备的密钥,因此,该终端设备的PDCP实体可以对前述下行数据包进行解密,能够较少网络时延,避免终端设备业务中断。
基于前述第四方面,在一种可选的实施方式中,当前述载波变更过程为由主网络设备发起删除辅网络设备时,该辅网络设备控制该辅网络设备的PDCP实体向主网络设备的RLC实体发送下行数据包之前,该方法还包括:该辅网络设备接收主网络设备发送的辅载波释放请求,该辅载波释放请求用于通知该辅网络设备进行释放;该辅网络设备向该主网络设备发送辅载波释放响应,该辅载波释放响应用于指示该辅网络设备确认释放。
基于前述第四方面或前述可选的实施方式,在另一种可选的实施方式中,当前述载波变更过程为由辅网络设备发起删除该辅网络设备时,该辅网络设备控制该辅网络设备的PDCP实体向主网络设备的RLC实体发送下行数据包之前,该方法还包括:该辅网络设备向该主网络设备发送辅载波释放请求,该辅载波释放请求用于请求释放该辅网络设备;该辅网络设备接收主网络设备发送的该辅载波释放确认消息,该辅载波释放确认消息用于指示允许该辅网络设备进行释放。
基于前述第四方面或前述可选的实施方式,在另一种可选的实施方式中,当由源辅网络设备发起变更到目标辅网络设备时,该辅网络设备为源辅网络设备;该辅网络设备控制该辅网络设备的PDCP实体向主网络设备的RLC实体发送下行数据包之前,该方法还包括: 该辅网络设备向该主网络设备发送载波变更请求,该载波变更请求携带目标辅网络设备的标识信息,该辅载波变更请求用于指示将该源辅网络设备变更为该目标辅网络设备,以使得该主网络设备向该目标辅网络设备发送该主网络设备的密钥。
基于前述第四方面或前述可选的实施方式,在另一种可选的实施方式中,当由主网络设备发起变更到源辅网络设备时,该辅网络设备为源辅网络设备;该辅网络设备控制该辅网络设备的PDCP实体向主网络设备的RLC实体发送下行数据包之前,该方法还包括:该辅网络设备接收该主网络设备发送的载波释放请求,该载波释放请求用于请求释放该源辅网络设备。
需要说明的是,本申请实施例还有多种具体其他实施方式,具体可参见第一方面的具体实施方式和其有益效果,在此不再赘述。
第五方面,本申请实施例提供了一种主网络设备,包括:发送模块,用于向终端设备发送第一消息,所述该终端设备在载波变更之前采用所述该主网络设备的密钥进行加解密数据,所述该第一消息用于指示所述该终端设备在载波变更之后采用所述该终端设备存储的所述该主网络设备的密钥进行加解密数据。
基于前述第五方面,在一种可选的实施方式中,该第一消息为无线资源控制RRC重配置消息,该RRC重配置消息携带第一指示信息,该第一指示信息用于指示采用该主网络设备的密钥进行加解密数据。
基于前述第五方面或前述可选的实施方式,在另一种可选的实施方式中,该主网络设备还包括:接收模块,接收辅网络设备发送的第二消息,该第二消息用于指示该辅网络设备确认将发生变更,该第二消息携带由该辅网络设备配置的该第一指示信息。
基于前述第五方面或前述可选的实施方式,在另一种可选的实施方式中,该发送模块,还用于向该辅网络设备发送第三消息,该第三消息携带该主网络设备的密钥,该第三消息用于指示该辅网络设备采用该主网络设备的密钥进行加解密数据。
示例性的,当前述主网络设备发起添加辅网络设备时,前述第三消息为辅载波添加请求,该辅载波添加请求用于请求添加该辅网络设备作为辅载波;前述第二消息为辅载波添加请求响应,该辅载波添加请求响应用于指示该辅网络设备确认添加,且该辅网络设备将采用该主站的密钥进行加解密。
基于前述第五方面或前述可选的实施方式,在另一种可选的实施方式中,该主网络设备还包括处理模块,该处理模块,用于控制该主网络设备的PDCP实体向该主网络设备的RLC实体发送下行数据包,并且,控制该主网络设备的RLC实体将该下行数据包发送至该终端设备,该终端设备的PDCP实体采用该主网络设备的密钥加解密该下行数据包。
基于前述第五方面或前述可选的实施方式,在另一种可选的实施方式中,当主网络设备发起删除辅网络设备时,该发送模块,还用于向辅网络设备发送辅载波释放请求,该辅载波释放请求用于通知该辅网络设备进行释放;该接收模块,还用于接收该辅网络设备发送的辅载波释放响应,该辅载波释放响应用于指示该辅网络设备确认释放。
基于前述第五方面或前述可选的实施方式,在另一种可选的实施方式中,当辅网络设 备发起删除辅网络设备时,该接收模块,还用于接收辅网络设备发送的辅载波释放请求,该辅载波释放请求用于请求释放该辅网络设备;该发送模块,还用于向该辅网络设备发送辅载波释放确认消息,该辅载波释放确认消息用于指示允许该辅网络设备进行释放。
基于前述第五方面或前述可选的实施方式,在另一种可选的实施方式中,该处理模块,还用于控制该主网络设备的RLC实体从该辅网络设备的PDCP实体接收下行数据包,该辅网络设备的PDCP实体采用该主网络设备的密钥加解密该下行数据包;控制该主网络设备的RLC实体将该下行数据包发送至该终端设备,该终端设备的PDCP实体采用该主网络设备的密钥加解密该下行数据包。
基于前述第五方面或前述可选的实施方式,在另一种可选的实施方式中,当前述载波变更过程为从一个辅网络设备变更到另一个辅网络设备的过程时,前述实施方式中的,该辅网络设备为目标辅网络设备,该第二消息为辅载波添加请求响应,该第二消息用于指示该目标辅网络设备确认添加,且该目标辅网络设备将采用该主站的密钥进行加解密。若由辅网络设备发起从源辅网络设备变更至目标辅网络设备,则该接收模块,还用于接收该源辅网络设备发送的辅载波变更请求,该载波变更请求携带该目标辅网络设备的标识信息,该辅载波变更请求用于指示将该源辅网络设备变更为该目标辅网络设备。
基于前述第五方面或前述可选的实施方式,在另一种可选的实施方式中,当前述载波变更过程为从一个辅网络设备变更到另一个辅网络设备的过程时,前述实施方式中的该辅网络设备可以理解为目标辅网络设备,该第二消息为辅载波添加请求响应,该第二消息用于指示该目标辅网络设备确认添加,且该目标辅网络设备将采用该主站的密钥进行加解密。若由主网络设备发起从源辅网络设备变更至目标辅网络设备,则该发送模块,还用于向该源辅网络设备发送载波释放请求,该载波释放请求用于请求释放该源辅网络设备;该接收模块,还用于接收该源辅网络设备发送的载波释放请求响应,该载波释放请求响应用于确认释放。
基于前述第五方面或前述可选的实施方式,在另一种可选的实施方式中,该处理模块,还用于控制该主网络设备的RLC实体从该源辅网络设备的PDCP实体接收下行数据包,该源辅网络设备的PDCP实体采用该主网络设备的密钥加解密该下行数据包;控制该主网络设备的RLC实体将该下行数据包发送至该终端设备,该终端设备的PDCP实体采用该主网络设备的密钥加解密该下行数据包。
需要说明的是,本申请实施例还有多种具体其他实施方式,具体可参见第一方面的具体实施方式和其有益效果,在此不再赘述。
第六方面,本申请实施例提供了一种终端设备,包括:接收模块,用于接收主网络设备发送的第一消息,该终端设备在载波变更之前采用该主网络设备的密钥进行加解密数据,该第一消息用于指示该终端设备在载波变更之后采用该终端设备存储的该主网络设备的密钥进行加解密数据。
基于前述第六方面,在一种可选的实施方式中,该第一消息为无线资源控制RRC重配置消息,该RRC重配置消息携带第一指示信息,该第一指示信息用于指示采用该主网络设 备的密钥进行加解密数据。
基于前述第六方面或前述可选的实施方式,在另一种可选的实施方式中,当主网络设备发起添加辅网络设备时,该终端设备中的处理模块,用于控制该终端设备的PDCP实体接收来自该主网络设备的RLC实体的下行数据包,该下行数据包来自该主网络设备的PDCP实体,该终端设备的PDCP实体采用该主网络设备的密钥加解密该下行数据包。
基于前述第六方面或前述可选的实施方式,在另一种可选的实施方式中,当删除辅网络设备(例如,主网络设备发起删除辅网络设备,或者辅网络设备发起删除辅网络设备,或者,从源辅网络设备变更至目标辅网络设备)时,该处理模块,还用于控制该终端设备的PDCP实体接收来自该主网络设备的RLC实体的下行数据包,该下行数据包来自辅网络设备的PDCP实体,该辅网络设备为待释放的网络设备,该终端设备的PDCP实体和该辅网络设备的PDCP实体均采用该主网络设备的密钥加解密该下行数据包。
需要说明的是,本申请实施例还有多种具体其他实施方式,具体可参见第二方面的具体实施方式和其有益效果,在此不再赘述。
第七方面,本申请实施例提供了一种辅网络设备,包括:接收模块,用于接收主网络设备发送的第三消息,该第三消息携带该主网络设备的密钥,该第三消息用于指示该辅网络设备采用该主网络设备的密钥进行加解密数据;发送模块,用于向该主网络设备发送第二消息,该第二消息用于指示该辅网络设备确认将发生变更,该第二消息携带由该辅网络设备配置的第一指示信息,该第一指示信息用于指示采用该主网络设备的密钥进行加解密数据。
示例性的,当前述主网络设备发起添加辅网络设备时,前述第三消息为辅载波添加请求,该辅载波添加请求用于请求添加该辅网络设备作为辅载波;前述第二消息为辅载波添加请求响应,该辅载波添加请求响应用于指示该辅网络设备确认添加,且该辅网络设备将采用该主站的密钥进行加解密。
基于前述第七方面,在一种可选的实施方式中,该辅网络设备还包括:处理模块,用于采用该主网络设备的密钥创建PDCP实体。
需要说明的是,本申请实施例还有多种具体其他实施方式,具体可参见第三方面的具体实施方式和其有益效果,在此不再赘述。
第八方面,本申请实施例提供了一种辅网络设备,包括:处理模块,用于控制该辅网络设备的PDCP实体向主网络设备的RLC实体发送下行数据包,该辅网络设备的PDCP实体采用该主网络设备的密钥加解密该下行数据包。
基于前述第八方面或前述可选的实施方式,在另一种可选的实施方式中,当前述载波变更过程为由辅网络设备发起删除该辅网络设备时,发送模块,还用于向该主网络设备发送辅载波释放请求,该辅载波释放请求用于请求释放该辅网络设备。该辅网络设备还包括接收模块,用于接收主网络设备发送的该辅载波释放确认消息,该辅载波释放确认消息用于指示允许该辅网络设备进行释放。
基于前述第八方面或前述可选的实施方式,在另一种可选的实施方式中,当由源辅网 络设备发起变更到目标辅网络设备时,该辅网络设备为源辅网络设备;该发送模块,还用于向该主网络设备发送载波变更请求,该载波变更请求携带目标辅网络设备的标识信息,该辅载波变更请求用于指示将该源辅网络设备变更为该目标辅网络设备,以使得该主网络设备向该目标辅网络设备发送该主网络设备的密钥。
基于前述第八方面或前述可选的实施方式,在另一种可选的实施方式中,当由主网络设备发起变更到源辅网络设备时,该辅网络设备为源辅网络设备;接收模块,还用于接收该主网络设备发送的载波释放请求,该载波释放请求用于请求释放该源辅网络设备。
需要说明的是,本申请实施例还有多种具体其他实施方式,具体可参见第八方面的具体实施方式和其有益效果,在此不再赘述。
第九方面,本申请实施例提供了一种通信设备,该通信设备可以是前述实施方式中的主网络设备,也可以是该主网络设备内的芯片。该通信设备可以包括处理模块和收发模块。当该通信设备是主网络设备时,该处理模块可以是处理器,该收发模块可以是收发器;该主网络设备还可以包括存储模块,该存储模块可以是存储器;该存储模块用于存储指令,该处理模块执行该存储模块所存储的指令,以使该主网络设备执行第一方面或第一方面的任一种实施方式中的方法。当该通信设备是主网络设备内的芯片时,该处理模块可以是处理器,该收发模块可以是输入/输出接口、管脚或电路等;该处理模块执行存储模块所存储的指令,以使该主网络设备执行第一方面或第一方面的任一种实施方式中的方法。该存储模块可以是该芯片内的存储模块(例如,寄存器、缓存等),也可以是该主网络设备内的位于该芯片外部的存储模块(例如,只读存储器、随机存取存储器等)。
第十方面,本申请实施例提供了一种通信设备,该通信设备可以是前述实施方式中的终端设备,也可以是该终端设备内的芯片。该通信设备可以包括处理模块和收发模块。当该通信设备是终端设备时,该处理模块可以是处理器,该收发模块可以是收发器;该终端设备还可以包括存储模块,该存储模块可以是存储器;该存储模块用于存储指令,该处理模块执行该存储模块所存储的指令,以使该终端设备执行第二方面或第二方面的任一种实施方式中的方法。当该通信设备是终端设备内的芯片时,该处理模块可以是处理器,该收发模块可以是输入/输出接口、管脚或电路等;该处理模块执行存储模块所存储的指令,以使该终端设备执行第二方面或第二方面的任一种实施方式中的方法。该存储模块可以是该芯片内的存储模块(例如,寄存器、缓存等),也可以是该终端设备内的位于该芯片外部的存储模块(例如,只读存储器、随机存取存储器等)。
第十一方面,本申请实施例提供了一种通信设备,该通信设备可以是前述实施方式中的辅网络设备,也可以是该辅网络设备内的芯片。该通信设备可以包括处理模块和收发模块。当该通信设备是辅网络设备时,该处理模块可以是处理器,该收发模块可以是收发器;该辅网络设备还可以包括存储模块,该存储模块可以是存储器;该存储模块用于存储指令,该处理模块执行该存储模块所存储的指令,以使该辅网络设备执行第三方面或第三方面的任一种实施方式中的方法,或者,执行第四方面或第四方面的任一种实施方式中的方法。当该通信设备是辅网络设备内的芯片时,该处理模块可以是处理器,该收发模块可以是输 入/输出接口、管脚或电路等;该处理模块执行存储模块所存储的指令,以使该辅网络设备执行第三方面或第三方面的任一种实施方式中的方法,或者,执行第四方面或第四方面的任一种实施方式中的方法。该存储模块可以是该芯片内的存储模块(例如,寄存器、缓存等),也可以是该辅网络设备内的位于该芯片外部的存储模块(例如,只读存储器、随机存取存储器等)。
示例性的,前述辅网络设备可以是前述实施方式中的源辅网络设备或目标辅网络设备。
第十二方面,本申请提供了一种通信装置,该装置可以是集成电路芯片。该集成电路芯片包括处理器。该处理器与存储器耦合,该存储器用于存储程序或指令,当该程序或指令被该处理器执行时,使得该通信装置执行如第一方面或第一方面的任一种实施方式中的方法。
第十三方面,本申请提供了一种通信装置,该装置可以是集成电路芯片。该集成电路芯片包括处理器。该处理器与存储器耦合,该存储器用于存储程序或指令,当该程序或指令被该处理器执行时,使得该通信设备执行如第二方面或第二方面的任一种实施方式中的方法。
第十四方面,本申请提供了一种通信装置,该装置可以是集成电路芯片。该集成电路芯片包括处理器。该处理器与存储器耦合,该存储器用于存储程序或指令,当该程序或指令被该处理器执行时,使得该通信设备执行如第三方面或第三方面的任一种实施方式中的方法。
第十五方面,本申请提供了一种通信装置,该装置可以是集成电路芯片。该集成电路芯片包括处理器。该处理器与存储器耦合,该存储器用于存储程序或指令,当该程序或指令被该处理器执行时,使得该通信设备执行如第四方面或第四方面的任一种实施方式中的方法。
第十六方面,本申请实施例提供了一种包含指令的计算机程序产品,当其在计算机上运行时,使得该计算机执行如前述第一方面至第四方面,以及前述各个方面的各种实施方式中的任一种实施方式所介绍的方法。
第十七方面,本申请实施例提供了一种计算机可读存储介质,包括指令,当该指令在计算机上运行时,以使得计算机执行如前述第一方面至第四方面,以及前述各个方面的各种实施方式中的任一种实施方式所介绍的方法。
第十八方面,本申请实施例提供了一种通信系统,该通信系统包括上述第一方面以及第一方面的任一种实施方式中的通信设备,上述第二方面以及第二方面的任一种实施方式中的通信设备,以及上述第三方面以及第三方面的任一种实施方式中的通信设备;或者,该通信系统包括上述第一方面以及第一方面的任一种实施方式中的通信设备,上述第二方面以及第二方面的任一种实施方式中的通信设备,以及上述第四方面以及第四方面的任一种实施方式中的通信设备。
从以上技术方案可以看出,本申请实施例具有以下优点:
本申请实施例中,在载波变更时,主网络设备将向终端设备发送第一消息,该第一消息将指示终端设备采用终端设备在载波变更之前就使用的主网络设备的密钥进行加解密数 据。由于,该终端设备已存储了前述主网络设备的密钥,并且,在载波变更之后,该终端设备依旧采用的是主网络设备的密钥。也就是说,在载波变更期间,终端设备不变更密钥,终端设备无需重建PDCP实体。因此,在载波变更时减少终端设备因重建PDCP实体而产生的网络延迟,进而可以降低由载波变更而导致数据业务中断的几率。
附图说明
为了更清楚地说明本申请实施例的技术方案,下面将对实施例描述中所需要使用的附图作简单地介绍,显而易见地,下面描述中的附图仅仅是本申请的一些实施例。
图1为本申请实施例中选项3X的系统架构图;
图2为本申请实施例中数据传输方法的一个流程图;
图3A为本申请实施例中数据传输方法的另一个流程图;
图3B为本申请实施例中下行数据包传输路径的一个实施例示意图;
图3C为本申请实施例中下行数据包传输路径的另一个实施例示意图;
图4为本申请实施例中数据传输方法的另一个流程图;
图5A为本申请实施例中数据传输方法的另一个流程图;
图5B为本申请实施例中下行数据包传输路径的另一个实施例示意图;
图5C为本申请实施例中下行数据包传输路径的另一个实施例示意图;
图6为本申请实施例中数据传输方法的另一个流程图;
图7为本申请实施例中数据传输方法的另一个流程图;
图8为本申请实施例中数据传输方法的另一个流程图;
图9A为本申请实施例中数据传输方法的另一个流程图;
图9B为本申请实施例中下行数据包传输路径的另一个实施例示意图;
图9C为本申请实施例中下行数据包传输路径的另一个实施例示意图;
图9D为本申请实施例中下行数据包传输路径的另一个实施例示意图;
图10为本申请实施例中数据传输方法的另一个流程图;
图11为本申请实施例中数据传输方法的另一个流程图;
图12为本申请实施例中数据传输方法的另一个流程图;
图13为本申请实施例中通信设备的一个实施例示意图;
图14为本申请实施例中通信设备的另一个实施例示意图;
图15为本申请实施例中通信设备的另一个实施例示意图;
图16为本申请实施例中通信设备的另一个实施例示意图。
具体实施方式
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行清楚、完整地描述,显然,所描述的实施例仅仅是本申请一部分实施例,而不是全部的实施例。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”、“第三”、“第四”等(如果存在)是用于区别类似的对象,而不必用于描述特定的顺序或先后次序。应该理 解这样使用的数据在适当情况下可以互换,以便这里描述的实施例能够以除了在这里图示或描述的内容以外的顺序实施。此外,术语“包括”和“具有”以及他们的任何变形,意图在于覆盖不排他的包含,例如,包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元,而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
本申请实施例提供了一种数据传输方法以及相关设备,用于在载波变更时减少终端设备产生的网络延迟,进而降低由载波变更而导致数据业务中断的几率。
为便于理解,下面先对本申请实施例所涉及的专业术语进行解释:
分组数据汇聚协议(packet data convergence protocol,PDCP):是一个无线传输协议栈,负责头压缩和解压、传输用户数据并维护为无线承载的序列号。采用该协议的实体被称为PDCP实体,该PDCP实体包括如下功能:使用健壮性包头压缩(robust header compression,ROHC)协议进行标头压缩和解压缩,加密和解密,以及完整性保护和完整性验证。本申请实施例中,主要介绍的是PDCP实体的加密和解密功能。本申请实施例中介绍的终端设备、主网络设备以及辅网络设备中均包含至少一个PDCP实体。
无线链路控制(radio link control,RLC):无线通信系统中的无线链路控制层协议。使用RLC协议的实体被称为RLC实体,该RLC实体位于媒介存取控制(medium access control,MAC)实体之上,主要为用户数据提供分段级连和重传业务。本申请实施例中,主要介绍的是RLC实体的转发下行数据包的功能。本申请实施例中介绍的终端设备、主网络设备以及辅网络设备中均包含至少一个RLC实体。
下面先对本申请实施例提出的数据传输方法适应系统架构和应用场景进行介绍:
本申请实施例提出的数据传输方法应用于非独立组网模式的选项3X(option 3X)架构。如图1所示,在选项3X架构中,核心网部分由4G核心网(evolved packet core,EPC)承担,接入网部分由4G基站或NR基站承担。
在这种架构下,当终端设备仅与LTE基站连接时,下行数据包(即用户数据)将由EPC直接流向LTE基站的PDCP实体,再通过LTE基站的PDCP实体传输至LTE基站的RLC实体(图未示),然后,从该LTE基站的RLC实体经过MAC层以及物理层等传输至终端设备的PDCP实体。此时,前述LTE基站的PDCP实体和终端设备的PDCP实体均采用LTE基站的密钥。但是,若添加了NR基站作为辅载波,则下行数据包(即用户数据)将由EPC直接流向NR基站的PDCP实体,再由NR基站的PDCP实体分流至LTE基站的RLC实体和NR基站的RLC实体,最后再由前述LTE基站的RLC实体和NR基站的RLC实体传输至终端设备的PDCP实体。
为了使终端设备的PDCP实体能够解密来自NR基站的PDCP实体的下行数据包,则该终端设备需要采用与NR基站的PDCP实体相同的密钥。由于,新添加的NR基站往往采用新的密钥创建PDCP实体,因此,终端设备需要变更密钥并重建PDCP实体。因此,将引入网络延时,导致用户数据传输中断。
此外,当需要删除辅载波(例如,删除前述NR基站)或者需要更换辅载波(例如,将NR基站A变更为NR基站B)时,也将存在终端设备因变更密钥而重建PDCP实体的 情况。因此,也将网络延时,导致用户数据传输中断。
对此,本申请实施例针对前述系统架构和应用场景提出了一种数据传输方法,能够在载波变更时减少终端设备产生的网络延迟,进而降低由载波变更而导致数据业务中断的几率。
下面将结合图2,从主网络设备、辅网络设备和终端设备这三者之间的数据交互对本申请实施例提出的数据传输方法进行介绍:
应当注意的是,本实施例中,主网络设备是当前为终端设备提供服务的接入网设备(radio access network,RAN),可以是4G无线接入网络设备,也可以是4G接入网中在空中接口上通过一个或多个小区与无线终端设备通信的设备。例如,主网络设备可以为图1所示的LTE基站,也可以被称为长期演进LTE系统或演进的LTE系统(long term evolution advanced,LTE-A)中的演进型基站(evolutional node B,NodeB或eNB或e-NodeB)。由于,在载波聚合或载波变更的场景中,主网络设备能够影响其他网络设备是否能够接入系统,前述主网络设备也被称为主基站(primary evolved NodeB,P-eNB)或主节点(master evolved NodeB,MeNB)。该主网络设备可用于将收到的空中帧与网际协议(internet protocol,IP)分组进行相互转换,作为终端设备与接入网的其余部分之间的路由器,其中接入网的其余部分可包括IP网络。主网络设备还可协调对空中接口的属性管理。具体此处不做限定。
应当理解的是,本申请实施例中的主网络设备可以是上述任意一种设备或上述设备中的芯片,具体此处不做限定。无论作为设备还是作为芯片,该主网络设备都可以作为独立的产品进行制造、销售或者使用。在本实施例以及后续实施例中,仅以主网络设备为例进行介绍。
辅网络设备主网络设备可以是新无线(new radio,NR)接入网络RAN设备,例如,图1所示的NR基站;也可以是NR接入网中在空中接口上通过一个或多个小区与无线终端设备通信的设备;还可以包括云接入网(Cloud RAN)系统中的集中式单元(centralized unit,CU)和分布式单元(distributed unit,DU)。例如,辅网络设备可以NR系统中的下一代节点B(next generation node B,gNB)。当存在多个辅网络设备时,前述多个辅网络设备可以分别表示为源下一代节点(source next generation node B,S-gNB)(即源辅网络设备或源基站)和目标下一代节点(target next generation node B,T-gNB)(即目标辅网络设备或目标基站)。其中,源辅网络设备为变更之前与终端设备和主网络设备通信的辅网络设备,目标辅网络设备为变更之后与终端设备和主网络设备通信的辅网络设备。也就是说,从前述源辅网络设备变更为目标辅网络设备。该辅网络设备可用于将收到的空中帧与网际协议IP分组进行相互转换,作为终端设备与接入网的其余部分之间的路由器,其中接入网的其余部分可包括IP网络。辅网络设备还可协调对空中接口的属性管理。具体此处不做限定。此外,该辅网络设备与前述主网络设备通过X2接口进行通信。
应当理解的是,本申请实施例中的辅网络设备可以是上述任意一种设备或上述设备中的芯片,具体此处不做限定。无论作为设备还是作为芯片,该辅网络设备都可以作为独立的产品进行制造、销售或者使用。在本实施例以及后续实施例中,仅以辅网络设备为例进行介绍。
此外,前述终端设备,包括向用户提供语音和/或数据连通性的设备。例如,可以包括具有无线连接功能的手持式设备或连接到无线调制解调器的处理设备。该终端设备可以经无线接入网RAN(例如,前述主网络设备或前述辅网络设备)与核心网(例如,前述4G核心网EPC)进行通信,可以与RAN交换语音和/或数据。该终端设备可以包括用户设备(user equipment,UE)、无线终端设备、移动终端设备、用户单元(subscriber unit)、用户站(subscriber station),移动站(mobile station)、移动台(mobile)、远程站(remote station)、接入点(access point,AP)、远程终端设备(remote terminal)、接入终端设备(access terminal)、用户终端设备(user terminal)、用户代理(user agent)、或用户装备(user device)等。此外,该终端设备也可以为车载终端,例如,集成在车辆中的车载盒子(telematics box,T-Box)、域控制器(domain controller,DC)、多域控制器(multi domain controller,MDC)或车载单元(on board unit,OBU)。该终端设备还可以为穿戴设备,例如,眼镜、手套、手表、服饰及鞋,或者其他的可以直接穿在身上或是整合到用户的衣服或配件的一种便携式设备,具体本申请不做限定。
应当理解的是,本申请实施例中的终端设备可以是上述任意一种设备或芯片,具体此处不做限定。无论作为设备还是作为芯片,该终端设备都可以作为独立的产品进行制造、销售或者使用。在本实施例以及后续实施例中,仅以终端设备为例进行介绍。
如图2所示,当载波发生变更时,该数据传输方法涉及的设备将执行如下步骤:
201,主网络设备向终端设备发送第一消息。
其中,该主网络设备是为该终端设备提供服务的接入网设备,也是决策是否进行载波变更的接入网设备。
在载波变更之前,该终端设备从前述主网络设备接收来自核心网的下行数据包,或者,同时从前述主网络设备和其他辅网络设备接收来自核心网的下行数据包。此时,该终端设备采用的是主网络设备的密钥(后文简称主站密钥)。也就是说,该终端设备的PDCP实体是采用主站密钥创建的,该终端设备的PDCP实体能够采用主站密钥对数据进行打包加密,同时,该终端设备的PDCP实体也能够解密采用主站密钥加密的数据包。
当该主网络设备发起载波变更流程时,该主网络设备将向终端设备发送第一消息,该第一消息用于指示该终端设备在载波变更之后采用该终端设备存储的主站密钥进行加解密数据。与此同时,若前述载波变更过程为添加辅载波,则该主网络设备将通知待添加的辅网络设备采用前述主站密钥;若前述载波变更过程为将已添加的辅载波变更为另一个辅载波,则该主网络设备将通知变更后的辅网络设备采用前述主站密钥。应当理解的是,若该主网络设备将删除前述已添加的辅载波,且仅有主网络设备与该终端设备进行数据传输,则该终端设备仍旧使用主站密钥。
可选的,前述第一消息携带第一指示信息,该第一指示信息用于指示采用该主网络设备的密钥进行加解密数据。示例性的,前述第一消息为无线资源控制RRC重配置消息(RRC connection reconfiguration),该RRC重配置消息携带前述第一指示信息。该第一指示信息可以为一个标识符,该标识符用于指示主网络设备的密钥。示例性的,该第一指示信息可以由待使用密钥(key to use)信元表示。一般地,当前述key to use信元配置为master时, 表示使用主站密钥;当前述key to use信元配置为slave时,表示使用辅站密钥。应当理解的是,在实际应用中,该第一指示信息还可能采用其他形式进行表示,本申请实施例对该第一指示信息的具体形式不做限定。
本实施例中,在载波变更时,主网络设备将向终端设备发送第一消息,该第一消息将指示终端设备采用终端设备在载波变更之前就使用的主网络设备的密钥进行加解密数据。由于,该终端设备已存储了前述主网络设备的密钥,并且,在载波变更之后,该终端设备依旧采用的是主网络设备的密钥。也就是说,在载波变更期间,终端设备不变更密钥,终端设备无需重建PDCP实体。因此,在载波变更时减少终端设备因重建PDCP实体而产生的网络延迟,进而可以降低由载波变更而导致数据业务中断的几率。
基于前述图2对应的实施例,前述载波变更过程主要包括如下三种场景:
(1)添加辅载波,指主网络设备添加辅网络设备,以使得该辅网络设备参与数据分流。
(2)删除辅载波,删除已添加的辅网络设备,该删除辅载波的过程可以由主网络设备发起,也可以由辅网络设备发起。(3)将一个载波变更为另一个载波,指将一个辅网络设备变更为另一个辅网络设备,该过程可以由主网络设备发起,也可以由辅网络设备发起。下面分别对前述各个场景进行介绍:
如图3A所示,为当主网络设备发起添加辅网络设备时,主网络设备、辅网络设备和终端设备三者之间的信令交互过程。
在主网络设备添加辅网络设备之前,该终端设备通过该主网络设备接收来自核心网的下行数据包,并且,采用该主网络设备的密钥(即主站密钥)进行加解密数据。具体如图3B所示,核心网设备将下行数据包发送给主网络设备的PDCP实体04,该主网络设备的PDCP实体04采用主站密钥对该下行数据包进行加解密,并控制该PDCP实体04将采用主站密钥加密的下行数据包传输至主网络设备的RLC实体05,再由该RLC实体05将前述下行数据包经过MAC层和物理层传输至终端设备的PDCP实体01。该终端设备收到该下行数据包之后,该终端设备可以控制该PDCP实体01采用主站密钥对该下行数据包解密,从而获取该下行数据包的业务数据。
应当理解的是,该下行数据包从该主网络设备的RLC实体05传输至终端设备的PDCP实体01的过程中,还将经历主网络设备的MAC实体06、主网络设备的物理层、终端设备的物理层、终端设备的MAC实体03以及终端设备的RLC实体02等。本申请实施例仅限定前述主网络设备的RLC实体05能够将下行数据包传输至终端设备的PDCP实体01,不对这两个实体之间的具体传输过程进行限定。
当该主网络设备准备添加辅网络设备时,该主网络设备和辅网络设备(即待添加的辅网络设备)将执行如下步骤:
301,主网络设备向辅网络设备发送第三消息。
其中,该第三消息携带主站密钥,用于指示该辅网络设备采用主站密钥加解密数据。也就是说,该主站密钥用于指示辅网络设备在创建PDCP实体时采用主站密钥。
示例性的,前述第三消息是辅载波添加请求(S-gNB addition request),该辅载波添加请求用于请求添加该辅网络设备作为辅载波。
302,辅网络设备采用主站密钥创建辅网络设备的PDCP实体。
当该辅网络设备收到前述第三消息并获取到该第三消息中携带的主站密钥之后,该辅网络设备采用主站密钥创建辅网络设备的PDCP实体。应当理解的是,该辅网络设备采用主站密钥创建的PDCP实体还不能立即参与数据包传输,需要待终端设备接入该辅网络设备且该主网络设备通知核心网设备载波已变更之后,该辅网络设备的PDCP实体才能被激活使用。该主网络设备与核心网设备的信令交互过程将在后续图4对应的实施例中进行详细介绍,此处不再赘述。
相比于现有技术,主网络设备仅会向待添加的辅网络设备发送辅网络设备的密钥(即辅站密钥),该辅站密钥一般为主站密钥派生出的密钥,并且,该辅站密钥与该主站密钥不同。而本发明则是由主网络设备向辅网络设备发送主站密钥,并在后续步骤中通知终端设备也采用主站密钥,以使得辅网络设备和终端设备均采用主站密钥。进而可以使辅网络设备参与数据包传输之后,终端设备的PDCP实体可以对来自辅网络设备的PDCP实体的下行数据包。
303,辅网络设备向主网络设备发送第二消息。
本实施例中,该第二消息用于指示辅网络设备确认将作为辅载波添加。
其中,该第二消息携带第一指示信息,该第一指示信息用于指示采用主站密钥进行加解密数据。此外,该第一指示信息由辅网络设备配置。可以理解为,该辅网络设备将该第一指示信息携带入前述第二消息中,一方面是表示该辅网络设备已确认在后续过程中将采用主站密钥创建PDCP实体,另一方面是表示将该第一指示信息通知该主网络设备,以便于该主网络设备按照第二消息中的第一指示信息指示终端设备也采用主站密钥。基于后一方面,该第二消息中的第一指示信息可以作为触发源,触发主网络设备执行后续步骤304。
示例性的,该第二消息是辅载波添加请求响应(S-gNB addition request acknowledge),该辅载波添加请求响应中携带多个信元,其中一个用于指示密钥的信元为key to use。该辅网络设备将该key to use信元设置为“master”,以表示该辅网络设备采用主站密钥。应当理解的是,在实际应用中,还可能采用其他信元作为前述第一指示信息,具体此处不做限定。
应当理解的是,步骤302与步骤303之间无明确的时间先后顺序的限定。也就是说,该辅网络设备可以先执行步骤302再执行步骤303,也可以先执行步骤303在执行步骤302,具体此处不做限定。
304,主网络设备向终端设备发送第一消息。
当该主网络设备收到来自辅网络设备的第二消息,并从该第二消息中获取到前述第一指示信息,该主网络设备可以确定辅网络设备在后续过程中将采用主站密钥进行加解密。于是,该主网络设备将该第一指示信息携带于第一消息中,并将该第一消息发送至终端设备。
示例性的,该第一消息为RRC重配置消息(RRC connection reconfiguration),该RRC 重配置消息携带前述第一指示信息。若步骤303中的第一指示信息由设置为“master”的key to use信元来表示,则该RRC重配置消息中的第一指示信息也为设置为“master”的key to use信元。
应当理解的是,前述第二消息和第一消息中均未直接携带主站密钥,而携带的是用于指示主站密钥的第一指示信息。由于,终端设备在添加辅网络设备之前采用的是主站密钥,因此,终端设备中存储有主站密钥,该终端设备中的PDCP实体也是采用主站密钥创建的。因此,当终端设备收到前述第一指示信息之后,该终端设备便可直接采用该终端设备的PDCP实体解密采用主站密钥加密的下行数据包,而无需重新计算密钥,更无需重建PDCP实体。
305,主网络设备控制主网络设备的PDCP实体向主网络设备的RLC实体发送下行数据包。
306,主网络设备控制主网络设备的RLC实体向终端设备发送下行数据包。
本实施例中,由于终端设备在收到前述第一指示信息之后,仍旧采用的是主站密钥,因此,该终端设备的PDCP实体可以对主网络设备的PDCP实体采用主站密钥加密的下行数据包进行解密。于是,该主网络设备控制主网络设备的PDCP实体向主网络设备的PDCP实体发送下行数据包,然后,该主网络设备控制主网络设备的RLC实体向终端设备发送下行数据包,该下行数据包经过MAC层和物理层之后传输至终端设备的PDCP实体。应当理解的是,下行数据包的流向与主网络设备未添加辅网络设备时相同。如图3B所示,由于该辅网络设备的PDCP实体还未被激活,核心网设备暂时还无法向辅网络设备的PDCP实体07分配下行数据包。此时,该核心网设备仍旧将下行数据包发送给主网络设备的PDCP实体04,该主网络设备的PDCP实体04采用主站密钥对该下行数据包进行加解密,并控制该PDCP实体04将采用主站密钥加密的下行数据包传输至主网络设备的RLC实体05,再由该RLC实体05将前述下行数据包经过MAC层和物理层传输至终端设备的PDCP实体01。该终端设备收到该下行数据包之后,该终端设备可以控制该PDCP实体01采用主站密钥对该下行数据包解密,从而获取该下行数据包的业务数据。
应当理解的是,现有技术中,主网络设备在添加辅网络设备时,向辅网络设备发送的是与主站密钥不同的辅站密钥。而当前终端设备的PDCP实体使用的是主站密钥,采用辅站密钥加密的数据包终端设备可能无法解密,因此,需要终端设备重建PDCP实体。在该终端设备重建好PDCP实体之前,该主网络设备的PDCP实体将被冻结,而不再向终端设备传输下行数据包。直到辅网络设备采用辅站密钥的PDCP被激活,终端设备重建的采用辅站密钥的PDCP被激活,且核心网设备已确认辅载波添加时,该终端设备的PDCP实体才能接收下行数据包。而在本发明中,终端设备无需重建PDCP实体,也不需要等待网络设备侧与核心网设备交互之后才开始重新接收下行数据包。因此,可以缩短网络延迟,进而降低由添加辅载波而导致数据业务中断的几率。
为便于进一步理解前述图3A对应的实施例,如图4所示,下面以主网络设备为eNB,辅网络设备为gNB,终端设备为UE为例进行进一步介绍:
401,eNB向gNB发送辅载波添加请求(SgNB addition request)。
其中,该辅载波添加请求携带主站密钥(即eNB的密钥),该辅载波添加请求用于通知gNB采用该主站密钥建立PDCP实体。
402,gNB采用主站密钥创建gNB PDCP实体。
应当理解的是,步骤402中,虽然gNB采用主站密钥创建了PDCP实体,但该PDCP实体还未被激活,无法立即参与数据传输。
403,gNB向eNB发送辅载波添加请求响应(SgNB addition request acknowledge)。
其中,该辅载波添加请求响应携带第一指示信息,该第一指示信息用于指示该gNB确认将采用该主站密钥创建PDCP实体。该第一指示信息由gNB填入在SgNB to MeNB Container中的一个信元表示。该SgNB to MeNB Container中存在一个用于指示密钥的信元key to use,该gNB将该key to use信元设置为master,以表示该gNB将使用主站密钥。
应当注意的是,步骤402和步骤403无明确的时间先后顺序限定。也就是说,该gNB可以先执行步骤402再执行步骤403,也可以先执行步骤403再执行步骤402,还可以同时执行步骤402和步骤403,具体此处不做限定。
404,eNB向UE发送RRC重配置(RRC connection reconfiguration)信令。
当该eNB收到来自gNB的载波添加请求响应之后,该eNB可以确定gNB将采用主站密钥创建PDCP实体。于是,该eNB将向UE发送RRC重配置信令,该RRC重配置信令携带前述载波添加请求响应中所携带的第一指示信息。
当UE识别到前述RRC重配置信令中的第一指示信息,则该UE便可获知采用主站密钥。由于,在此之前该UE的PDCP实体采用的是主站密钥,因此,该UE可以延续使用采用该主站密钥的PDCP实体,而无需重建采用新密钥的PDCP实体。因此,在后续步骤中,采用主站密钥加密的下行数据包在传输至UE时,该UE可以采用该PDCP实体解密该下行数据包,进而获得该下行数据包中的业务数据。
应当理解的是,前述RRC重配置信令还可以携带其他用于重配置的参数,具体此处不做限定。
405,UE向eNB发送RRC重配置完成(RRC connection reconfiguration complete)信令。
其中,该RRC重配置完成信令用于通知eNB该UE已收到前述第一指示信息,并完成了相关的重配置。
406,eNB向gNB发送辅载波重配置完成(SgNB reconfiguration complete)信令。
其中,该辅载波重配置完成信令用于通知gNB前述UE已经重配置完成,该gNB可以开始为UE的随机接入做准备。
407,UE向gNB发起随机接入流程。
具体地,UE与gNB之间的随机接入过程包括:
S1,UE向gNB发送随机接入请求(random access request)(即msg1),该随机接入请求携带随机接入前导码(random access preamble)。
S2,gNB向UE发送随机接入响应(random access response,RAR)(即msg2)。
S3,UE向gNB发送RRC连接建立请求(RRC connection request)(即msg3),该RRC连接建立请求携带了UE的标识信息。
S4,gNB向UE发送RRC连接建立(RRC contention resolution)信令(即msg4)。
应当理解的是,在实际应用中该随机接入过程还可能涉及其他信令或参数,此处不再赘述。
当该UE成功接入该gNB,则说明此后UE可以从前述gNB接收下行数据包。也可以理解为,该gNB可以为前述UE提供服务。
408,eNB控制eNB PDCP实体向eNB RLC实体发送下行数据包。
本实施例中,步骤408与前述步骤407是相互独立的。也就是说,该步骤408可以在eNB执行步骤406之后便执行。
其中,该下行数据包来自服务网关(serving gateway,S-GW),是终止于UMTS陆地无线接入网(UMTS terrestrial radio access network,E-UTRAN)接口的网关。在本实施例中,该服务网关主要用于eNB或gNB发送下行数据包,以及与移动性管理实体(mobility management entity,MME)协商传输路径切换。
该eNB PDCP实体将采用主站密钥对来自S-GW的下行数据包加密,然后,控制该eNB PDCP实体将该下行数据包传输至eNB RLC实体。
409,eNB控制eNB RLC实体向UE PDCP实体发送下行数据包。
本实施例中,步骤409与前述步骤407是相互独立的。但是,在步骤408之后,该eNB将立即执行步骤409。
本步骤中,eNB控制eNB RLC实体将前述采用主站密钥加密的下行数据包经过MAC层和物理层传输至UE PDCP实体。由于该UE PDCP实体也采用的主站密钥,因此,该UE PDCP实体能够对该下行数据包解密并获取该下行数据包中的业务数据。
410,gNB通知eNB随机接入完成。
本实施例中,步骤410与前述步骤408至步骤409是相互独立的,该步骤410在步骤407之后执行即可。
411,eNB向MME发送演进的无线接入承载修改指示(E-RAB modification indication)。
其中,该演进的无线接入承载修改指示用于请求MME将传输路径切换至gNB。
412,MME向S-GW发送路径切换请求(path switch request)。
其中,路径切换请求用于请求S-GW将后续的下行数据包传输至gNB。于是,该gNB PDCP实体将从前述S-GW接收下行数据包。
413,S-GW向MME发送路径切换请求响应(path switch request acknowledge)。
其中,路径切换请求响应用于指示切换已完成。
414,S-GW向eNB发送结束标记(end marker)数据包。
其中,该结束标记数据包为S-GW发送给eNB的最后一个数据包,用于指示在该结束标记数据包之后,该S-GW不再向该eNB发送下行数据包。
415,eNB向gNB发送系统帧号状态转发(SN status transfer)和结束标记(end marker)数据包。
本实施例中,系统帧号状态转发用于指示当前S-GW已传输给eNB的下行数据包的序列号,以使得该gNB在后续过程中从S-GW接收该序列号之后的数据包。于是,可以避免该gNB重复接收下行数据包或遗漏下行数据包。
此外,eNB还将前述步骤414中的结束标记数据包转发给gNB,以指示该eNB已经将最后一个数据包转发给gNB。当该gNB收到该结束标记数据包之后,该gNB将执行步骤417。
416,MME向eNB发送演进的无线接入承载修改指示完成(E-RAB modification indication complete)。
417,gNB控制gNB PDCP实体从S-GW接收下行数据包。
当该gNB收到结束标记数据包之后,该gNB PDCP实体被激活。该gNB便能够控制gNB PDCP实体从S-GW接收下行数据包。由于,该gNB在创建gNB PDCP实体时采用的是主站密钥,因此,该gNB PDCP实体将对收到的下行数据包采用主站密钥进行加密,然后再进行后续传输。
418,gNB控制gNB PDCP实体向gNB RLC实体和eNB RLC实体发送下行数据包。
419,gNB控制gNB RLC实体向UE PDCP实体发送下行数据包。
420,eNB控制eNB RLC实体向UE PDCP实体发送下行数据包。
本实施例中,步骤419和步骤420是同时执行的。
为便于理解,以图3B和图3C为例进行介绍。此时,前述图3B和图3C中的核心网设备为S-GW,主网络设备为eNB,辅网络设备为gNB,终端设备为UE。
当eNB执行前述步骤408至步骤409时,下行数据包的流向如图3B所示。S-GW将下行数据包发送给eNB PDCP实体04,该eNB PDCP实体04采用主站密钥对该下行数据包进行加解密,并控制该eNB PDCP实体04将采用主站密钥加密的下行数据包传输至eNB RLC实体05,再由该eNB RLC实体05经过MAC层和物理层将前述下行数据包传输至UE PDCP实体01。该UE收到该下行数据包之后,该UE可以控制该UE PDCP实体01采用主站密钥对该下行数据包解密,从而获取该下行数据包的业务数据。
当gNB执行前述步骤417至步骤419,eNB执行前述步骤420时,下行数据包的流向如图3C所示。S-GW将下行数据包发送给gNB PDCP实体07,该gNB PDCP实体07采用主站密钥对该下行数据包进行加解密,并控制该gNB PDCP实体07将采用主站密钥加密的下行数据包传输至eNB RLC实体05和gNB RLC实体08,再由该eNB RLC实体05和gNB RLC实体08分别将前述下行数据包传输至UE PDCP实体01,以使得该UE可以控制该UE PDCP实体01采用主站密钥对该下行数据包解密,进而获取该下行数据包的业务数据。
下面对删除辅载波的情况进行介绍,该删除辅载波的过程可以由主网络设备发起,也可以由辅网络设备发起。如图5A所示,为当主网络设备发起删除辅网络设备时,主网络设备、辅网络设备和终端设备三者之间的信令交互过程。
在主网络设备删除辅网络设备之前,该终端设备通过该主网络设备和辅网络设备接收来自核心网的下行数据包,并且,采用该主网络设备的密钥(即主站密钥)进行加解密数 据。具体如前述图3C所示,核心网设备将下行数据包发送给辅网络设备的PDCP实体07,该辅网络设备的PDCP实体07采用主站密钥对该下行数据包进行加解密,并控制该辅网络设备的PDCP实体07将采用主站密钥加密的下行数据包传输至主网络设备RLC实体05和该辅网络设备的RLC实体08,再由该主网络设备的RLC实体05和该辅网络设备的RLC实体08分别将前述下行数据包经过MAC层和物理层传输至终端设备的PDCP实体01。
当该主网络设备准备删除辅网络设备时,该主网络设备和辅网络设备(即待删除的辅网络设备)将执行如下步骤:
501,主网络设备向辅网络设备发送辅载波释放请求。
其中,该辅载波释放请求用于指示该辅网络设备准备释放。
502,辅网络设备向主网络设备发送辅载波释放请求响应。
其中,该辅载波释放请求响应用于指示该辅网络设备已收到前述辅载波释放请求,并确认准备释放。辅载波释放请求可以作为触发源,触发主网络设备执行后续步骤503。
503,主网络设备向终端设备发送第一消息。
本实施例中,当该主网络设备收到来自辅网络设备的载波释放响应之后,该主网络设备将向终端设备发送第一消息,该第一消息用于指示终端设备采用主站密钥进行加解密数据。
在一种可选的实施方式中,前述第一消息未携带某个特定的用于指示密钥的指示信息。当该终端设备收到前述第一消息并检测到该第一消息未携带关于密钥的指示信息,则该终端设备将不改变密钥,也就是说,该终端设备将仍旧采用主站密钥。
504,辅网络设备控制辅网络设备的PDCP实体仅向主网络设备的RLC实体发送下行数据包。
505,主网络设备控制主网络设备的RLC实体向终端设备发送下行数据包。
应当理解的是,步骤503与步骤504之间无明确的时间先后顺序的限定。也就是说,该辅网络设备可以先执行步骤503再执行步骤504,也可以先执行步骤504在执行步骤503,具体此处不做限定。
本实施例中,辅网络设备在收到载波释放请求之后,该辅网络设备的PDCP实体被删除之前,由于终端设备仍旧采用主站密钥,因此,该辅网络设备可以将已经从核心网设备接收的下行数据包转发至主网络设备,由该主网络设备将这部分下行数据包发送至终端设备。如图5B所示,该核心网设备将下行数据包发送给辅网络设备的PDCP实体07,该辅网络设备的PDCP实体07采用主站密钥对该下行数据包进行加解密,并控制该PDCP实体07将采用主站密钥加密的下行数据包传输至主网络设备的RLC实体05,再由该RLC实体05将前述下行数据包传输至终端设备,经过MAC层和物理层之后传输至终端设备的PDCP实体01。
应当理解的是,现有技术中,当该辅网络设备收到来自主网络设备的辅载波释放请求之后,该辅网络设备中的PDCP实体将停止转发下行数据包。直到主网络设备采用主站密钥的PDCP被激活,且核心网设备已确认辅载波删除时,主网络设备的PDCP实体才能从核心网设备接收下行数据包,并控制该主网络设备的PDCP实体将下行数据包传输至主网 络设备的RLC实体,再由该主网络设备的RLC实体经过MAC层和物理层传输至终端设备的PDCP实体。而在本发明中,由于终端设备和辅网络设备均采用主站密钥,终端设备无需重建PDCP实体,辅网络设备也可以继续向主网络设备和终端设备传送已缓存的下行数据包,也不需要等待网络设备侧与核心网设备交互之后才开始重新接收下行数据包。因此,可以缩短网络延迟,进而降低由添加辅载波而导致数据业务中断的几率。
为便于进一步理解前述图5A对应的实施例,如图6所示,下面以主网络设备为eNB,辅网络设备为gNB,终端设备为UE为例进行进一步介绍:
601,eNB向gNB发送辅载波释放请求(SgNB release request)。
其中,该辅载波释放请求用于通知gNB准备释放。
602,gNB向eNB发送辅载波释放请求响应(SgNB release request acknowledge)。
其中,该辅载波释放请求响应用于指示该gNB已收到前述辅载波释放请求,并确认准备释放。辅载波释放请求可以作为触发源,触发eNB执行后续步骤604。
603,gNB控制gNB PDCP实体仅向eNB RLC实体发送下行数据包。
其中,该下行数据包来自服务网关S-GW,该下行数据包是gNB在收到载波释放请求之后,该gNB PDCP实体被删除之前,该gNB已从S-GW接收的下行数据包。该gNB PDCP实体采用主站密钥对前述下行数据包进行加密,然后,控制该gNB PDCP实体将下行数据包传输至eNB RLC实体。
604,eNB向UE发送RRC重配置(RRC connection reconfiguration)信令。
当该eNB收到来自gNB的载波释放请求响应之后,该eNB将向UE发送RRC重配置信令,该RRC重配置信令用于指示该终端设备仍旧使用主站密钥。
在一种可选的实施方式中,前述RRC重配置信令未携带某个特定的用于指示密钥的指示信息。当UE收到前述RRC重配置信令并检测到该RRC重配置信令未携带关于密钥的指示信息,则该UE将不改变密钥,也就是说,该UE将仍旧采用主站密钥。
应当理解的是,前述RRC重配置信令还可以携带其他用于重配置的参数,具体此处不做限定。
本实施例中,步骤604与前述步骤603是相互独立的。也就是说,在实际应用中,可能先由gNB先执行步骤603,再由eNB执行步骤604;也可能先由eNB先执行步骤604,再由gNB执行步骤603;还有可能gNB和eNB分别同时执行步骤603和步骤604。具体此处不做限定。
605,UE向eNB发送RRC重配置完成(RRC connection reconfiguration complete)信令。
其中,该RRC重配置完成信令用于通知eNB该UE已完成了相关的重配置。
606,eNB控制eNB RLC实体向UE PDCP实体发送下行数据包。
本步骤中,eNB控制eNB RLC实体将前述采用主站密钥加密的下行数据包经过MAC层和物理层传输至UE PDCP实体。由于该UE PDCP实体也采用的主站密钥,因此,该UE PDCP实体能够对该下行数据包解密并获取该下行数据包中的业务数据。
607,eNB向MME发送演进的无线接入承载修改指示(E-RAB modification indication)。
其中,该演进的无线接入承载修改指示用于请求MME将传输路径切换至eNB。
608,MME向S-GW发送路径切换请求(path switch request)。
其中,路径切换请求用于请求S-GW将后续的下行数据包传输至eNB。于是,该eNB将控制eNB PDCP实体将从前述S-GW接收下行数据包。
609,S-GW向MME发送路径切换请求响应(path switch request acknowledge)。
其中,路径切换请求响应用于指示切换已完成。
610,S-GW向gNB发送结束标记(end marker)数据包。
其中,该结束标记数据包为S-GW发送给gNB的最后一个数据包,用于指示在该结束标记数据包之后,该S-GW不再向该gNB发送下行数据包。
611,gNB向eNB发送系统帧号状态转发(SN status transfer)和结束标记(end marker)数据包。
本实施例中,系统帧号状态转发用于指示当前S-GW已传输给gNB的下行数据包的序列号,以使得该eNB在后续过程中从S-GW接收该序列号之后的数据包。于是,可以避免该eNB重复接收下行数据包或遗漏下行数据包。
此外,gNB还将前述步骤610中的结束标记数据包转发给eNB,以指示该gNB已经将最后一个数据包转发给eNB。当该eNB收到该结束标记数据包之后,该eNB将执行步骤613。
612,MME向eNB发送演进的无线接入承载修改指示完成(E-RAB modification indication complete)。
613,eNB控制eNB PDCP实体从S-GW接收下行数据包。
当该gNB收到结束标记数据包之后,该gNB PDCP实体被激活。该gNB便能够控制gNB PDCP实体从S-GW接收下行数据包。由于,该gNB在创建gNB PDCP实体时采用的是主站密钥,因此,该gNB PDCP实体将对收到的下行数据包采用主站密钥进行加密,然后再进行后续传输。
614,eNB控制eNB PDCP实体向eNB RLC实体发送下行数据包。
615,eNB控制eNB RLC实体向UE PDCP实体发送下行数据包。
为便于理解,以图5B和图5C为例进行介绍。此时,前述图5B和图5C中的核心网设备为S-GW,主网络设备为eNB,辅网络设备为gNB,终端设备为UE。
当gNB执行前述步骤603且eNB执行前述步骤606时,下行数据包的流向如图5B所示。S-GW将下行数据包发送给gNB PDCP实体07,该gNB PDCP实体07采用主站密钥对该下行数据包进行加解密,并控制该gNB PDCP实体07将采用主站密钥加密的下行数据包传输至eNB RLC实体05,再由该eNB RLC实体05将前述下行数据包经过MAC层和物理层传输至UE PDCP实体01。该UE收到该下行数据包之后,该UE可以控制该UE PDCP实体01采用主站密钥对该下行数据包解密,从而获取该下行数据包的业务数据。
当eNB执行前述步骤613至步骤615时,下行数据包的流向如图5C所示。S-GW将下行数据包发送给eNB PDCP实体04,该eNB PDCP实体04采用主站密钥对该下行数据 包进行加解密,并控制该eNB PDCP实体04将采用主站密钥加密的下行数据包传输至eNB RLC实体05,再由该eNB RLC实体05将前述下行数据包经过MAC层和物理层传输至UE PDCP实体01,以使得该UE可以控制该UE PDCP实体01采用主站密钥对该下行数据包解密,进而获取该下行数据包的业务数据。
如图7所示,为当辅网络设备发起删除辅网络设备时,主网络设备、辅网络设备和终端设备三者之间的信令交互过程。
在主网络设备删除辅网络设备之前,该终端设备通过该主网络设备和辅网络设备接收来自核心网的下行数据包,并且,采用该主网络设备的密钥(即主站密钥)进行加解密数据。具体请参阅前文图3C对应的相关描述,此处不再赘述。
当该辅网络设备发起删除时,该主网络设备和辅网络设备(即待删除的辅网络设备)将执行如下步骤:
701,辅网络设备向主网络设备发送辅载波释放请求。
其中,该辅载波释放请求用于请求主网络设备允许辅网络设备进行释放。
702,主网络设备向辅网络设备发送辅载波释放确认消息。
其中,该辅载波释放确认消息用于指示允许辅网络设备在后续过程中释放。
此外,前述步骤701中的辅载波释放请求和步骤702中的载波释放确认消息均可以作为触发源,触发主网络设备执行后续步骤703。
703,主网络设备向终端设备发送第一消息。
704,辅网络设备控制辅网络设备的PDCP实体仅向主网络设备的RLC实体发送下行数据包。
705,主网络设备控制主网络设备的RLC实体向终端设备发送下行数据包。
应当理解的是,步骤703与步骤704之间无明确的时间先后顺序的限定。也就是说,该辅网络设备可以先执行步骤703再执行步骤704,也可以先执行步骤704在执行步骤703,具体此处不做限定。
此外,本实施例中,步骤703至步骤705与前述步骤503至步骤505相同,具体请参阅前述步骤503至步骤505的相关描述,具体此处不再赘述。
本实施例中,由于终端设备和辅网络设备均采用主站密钥,终端设备无需重建PDCP实体,辅网络设备也可以将已缓存的下行数据包继续向主网络设备和终端设备传送,也不需要等待网络设备侧与核心网设备交互之后才开始重新接收下行数据包。因此,可以缩短网络延迟,进而降低由添加辅载波而导致数据业务中断的几率。
应当理解的是,本实施例中的辅载波删除流程由辅网络设备发起,其余步骤可以参阅前述图5A对应的实施例,具体此处不再赘述。
为便于进一步理解前述图7对应的实施例,如图8所示,下面以主网络设备为eNB,辅网络设备为gNB,终端设备为UE为例进行进一步介绍:
801,gNB向eNB发送辅载波释放请求(SgNB release request)。
其中,该辅载波释放请求用于eNB允许gNB在后续过程中释放。
802,eNB向gNB发送辅载波释放确认(SgNB release request acknowledge)消息。
其中,该辅载波释放请求确认消息用于指示该eNB允许gNB在后续过程中释放。
应当理解的是,前述步骤801和步骤802均可以作为触发源,触发eNB执行后续步骤804。
803,gNB控制gNB PDCP实体仅向eNB RLC实体发送下行数据包。
804,eNB向UE发送RRC重配置(RRC connection reconfiguration)信令。
805,UE向eNB发送RRC重配置完成(RRC connection reconfiguration complete)信令。
806,eNB控制eNB RLC实体向UE PDCP实体发送下行数据包。
807,eNB向MME发送演进的无线接入承载修改指示(E-RAB modification indication)。
808,MME向S-GW发送路径切换请求(path switch request)。
809,S-GW向MME发送路径切换请求响应(path switch request acknowledge)。
810,S-GW向gNB发送结束标记(end marker)数据包。
811,gNB向eNB发送系统帧号状态转发(SN status transfer)和结束标记(end marker)数据包。
812,MME向eNB发送演进的无线接入承载修改指示完成(E-RAB modification indication complete)。
813,eNB控制eNB PDCP实体从S-GW接收下行数据包。
814,eNB控制eNB PDCP实体向eNB RLC实体发送下行数据包。
815,eNB控制eNB RLC实体向UE PDCP实体发送下行数据包。
本实施例中,步骤803至步骤815与前述步骤603至步骤615相同,具体请参阅前述步骤603至步骤615的相关介绍,此处不再赘述。
下面对从一个辅载波变更至另一个辅载波的情况进行介绍,该过程可以由主网络设备发起,也可以由辅网络设备发起。如图9A所示,为当源辅网络设备发起变更辅网络设备时,主网络设备、源辅网络设备、目标辅网络设备和终端设备三者之间的信令交互过程。
在变更之前,该终端设备通过该主网络设备和源辅网络设备接收来自核心网的下行数据包,并且,采用该主网络设备的密钥(即主站密钥)进行加解密数据。具体如前述图9B所示,核心网设备将下行数据包发送给源辅网络设备的PDCP实体07,该源辅网络设备的PDCP实体07采用主站密钥对该下行数据包进行加解密,并控制该源辅网络设备的PDCP实体07将采用主站密钥加密的下行数据包传输至主网络设备RLC实体05和该源辅网络设备的RLC实体08,再由该主网络设备的RLC实体05和该源辅网络设备的RLC实体08分别将前述下行数据包传输至终端设备,经过MAC层和物理层之后传输至终端设备的PDCP实体01。
当该源辅网络设备请求变更至目标辅网络设备时,该主网络设备、源辅网络设备(即待删除的辅网络设备)和目标辅网络设备(即待添加的辅网络设备)将执行如下步骤:
901,源辅网络设备向主网络设备发送辅载波变更请求。
本实施例中,该辅载波变更请求用于请求主网络设备变更辅载波。其中,该辅载波变更请求携带目标辅网络设备的标识信息。因此,当该主网络设备从前述辅载波变更请求中获取了目标辅网络设备的标识信息之后,该主网络设备将向目标辅网络设备发起辅载波添加流程。具体地,该主网络设备将执行步骤902。
902,主网络设备向目标辅网络设备发送第三消息。
其中,该第三消息携带主站密钥,用于指示该目标辅网络设备采用主站密钥加解密数据。也就是说,该主站密钥用于指示目标辅网络设备在创建PDCP实体时采用主站密钥。
示例性的,前述第三消息是辅载波添加请求(S-gNB addition request),该辅载波添加请求用于请求添加该目标辅网络设备作为辅载波。
903,目标辅网络设备采用主站密钥创建目标辅网络设备的PDCP实体。
当该目标辅网络设备收到前述第三消息并获取到该第三消息中携带的主站密钥之后,该目标辅网络设备采用主站密钥创建目标辅网络设备的PDCP实体。应当理解的是,该目标辅网络设备采用主站密钥创建的PDCP实体还不能立即参与数据包传输,需要待终端设备接入该目标辅网络设备且该主网络设备通知核心网设备载波已变更之后,该目标辅网络设备的PDCP实体才能被激活使用。该主网络设备与核心网设备的信令交互过程将在后续图10对应的实施例中进行详细介绍,此处不再赘述。
相比于现有技术,主网络设备仅会向待添加的目标辅网络设备发送不同于主站密钥的新密钥。而本发明则是由主网络设备向目标辅网络设备发送主站密钥,并在后续步骤中通知终端设备也采用主站密钥,以使得目标辅网络设备和终端设备均采用主站密钥。进而可以使目标辅网络设备参与数据包传输之后,终端设备的PDCP实体可以对来自目标辅网络设备的PDCP实体的下行数据包。
904,目标辅网络设备向主网络设备发送第二消息。
本实施例中,该第二消息用于指示目标辅网络设备确认将作为辅载波添加。
其中,该第二消息携带第一指示信息,该第一指示信息用于指示采用主站密钥进行加解密数据。此外,该第一指示信息由目标辅网络设备配置。可以理解为,该目标辅网络设备将该第一指示信息携带入前述第二消息中,一方面是表示该目标辅网络设备已确认在后续过程中将采用主站密钥创建PDCP实体,另一方面是表示将该第一指示信息通知该主网络设备,以便于该主网络设备按照第二消息中的第一指示信息指示终端设备也采用主站密钥。基于后一方面,该第二消息中的第一指示信息可以作为触发源,触发主网络设备执行后续步骤905。
示例性的,该第二消息是辅载波添加请求响应(S-gNB addition request acknowledge)。该目标辅网络设备将指示密钥的信元key to use信元设置为“master”,并携带于前述第二消息中,以表示该目标辅网络设备采用主站密钥。应当理解的是,在实际应用中,还可能采用其他信元作为前述第一指示信息,具体此处不做限定。
应当理解的是,步骤903与步骤904之间无明确的时间先后顺序的限定。也就是说,该目标辅网络设备可以先执行步骤903执行步骤904,也可以先执行步骤904在执行步骤 903,具体此处不做限定。
905,主网络设备向终端设备发送第一消息。
当该主网络设备收到来自目标辅网络设备的第二消息,并从该第二消息中获取到前述第一指示信息,该主网络设备可以确定目标辅网络设备在后续过程中将采用主站密钥进行加解密。于是,该主网络设备将该第一指示信息携带于第一消息中,并将该第一消息发送至终端设备。
示例性的,该第一消息为RRC重配置消息(RRC connection reconfiguration),该RRC重配置消息携带前述第一指示信息。若步骤904中的第一指示信息由设置为“master”的key to use信元来表示,则该RRC重配置消息中的第一指示信息也为设置为“master”的key to use信元。
应当理解的是,前述第二消息和第一消息中均未直接携带主站密钥,而携带的是用于指示主站密钥的第一指示信息。由于,终端设备在添加辅网络设备之前采用的是主站密钥,因此,终端设备中存储有主站密钥,该终端设备中的PDCP实体也是采用主站密钥创建的。因此,当终端设备收到前述第一指示信息之后,该终端设备便可直接采用该终端设备的PDCP实体解密采用主站密钥加密的下行数据包,而无需重新计算密钥,更无需重建PDCP实体。
906,源辅网络设备控制源辅网络设备的PDCP实体向主网络设备的RLC实体发送下行数据包。
应当注意的是,步骤906与前述步骤902至步骤905是相互独立的。该源网络设备可以在执行了步骤901之后便执行步骤906。
907,主网络设备控制主网络设备的RLC实体向终端设备发送下行数据包。
本实施例中,在载波变更之前,终端设备和源辅网络设备均采用主站密钥,并且,终端设备在收到前述第一指示信息之后,仍旧采用的是主站密钥。因此,该终端设备的PDCP实体可以对源辅网络设备的PDCP实体采用主站密钥加密的下行数据包进行解密。于是,该源辅网络设备控制源辅网络设备的PDCP实体向主网络设备的PDCP实体发送下行数据包,然后,该主网络设备控制主网络设备的RLC实体经过MAC层和物理层向终端设备的PDCP实体发送下行数据包。这样的实施方式,可以使得在源辅网络设备发出辅载波变更请求之后,目标辅网络设备开始传输下行数据包之前,该终端设备可以接收一部分缓存于源辅网络设备的下行数据包。因此,可以缩短中断传输下行数据包的时间,缩短网络延迟,降低终端设备业务中断的几率。
此时,下行数据包的流向如图9C所示,由于该目标辅网络设备的PDCP实体还未被激活,核心网设备暂时还无法向目标辅网络设备的PDCP实体10分配下行数据包。此时,该核心网设备将下行数据包发送给源辅网络设备的PDCP实体07,该源辅网络设备的PDCP实体07采用主站密钥对该下行数据包进行加解密,并控制该PDCP实体07将采用主站密钥加密的下行数据包传输至主网络设备的RLC实体05,再由该RLC实体05将前述下行数据包传输至终端设备,经过MAC层和物理层之后传输至终端设备的PDCP实体01。该终端设备收到该下行数据包之后,该终端设备可以控制该PDCP实体01采用主站密钥对该下 行数据包解密,从而获取该下行数据包的业务数据。
为便于进一步理解前述图9A对应的实施例,如图10所示,下面以主网络设备为eNB,源辅网络设备为S-gNB,目标辅网络设备为T-gNB,终端设备为UE为例进行进一步介绍:
1001,S-gNB向eNB发送辅载波变更请求(SgNB change request)。
其中,该辅载波变更请求携带待添加的T-gNB的标识信息。当eNB从前述辅载波变更请求中获取到T-gNB的标识信息之后,eNB将执行步骤1002。与此同时,该S-gNB将执行步骤1009。
1002,eNB向T-gNB发送辅载波添加请求(SgNB addition request)。
其中,该辅载波添加请求携带主站密钥(即eNB的密钥),该辅载波添加请求用于通知T-gNB采用该主站密钥建立PDCP实体。
1003,T-gNB采用主站密钥创建T-gNB PDCP实体。
应当理解的是,步骤1003中,虽然T-gNB采用主站密钥创建了PDCP实体,但该PDCP实体还未被激活,无法立即参与数据传输。
1004,T-gNB向eNB发送辅载波添加请求响应(SgNB addition request acknowledge)。
其中,该辅载波添加请求响应携带第一指示信息,该第一指示信息用于指示该T-gNB确认将采用该主站密钥创建PDCP实体。该第一指示信息由T-gNB填入在SgNB to MeNB Container中的一个信元表示。该SgNB to MeNB Container中存在一个用于指示密钥的信元key to use,该T-gNB将该key to use信元设置为master,以表示该T-gNB将使用主站密钥。
应当注意的是,步骤1003和步骤1004无明确的时间先后顺序限定。也就是说,该T-gNB可以先执行步骤1003再执行步骤1004,也可以先执行步骤1004再执行步骤1003,还可以同时执行步骤1003和步骤1004,具体此处不做限定。
1005,eNB向UE发送RRC重配置(RRC connection reconfiguration)信令。
当该eNB收到来自T-gNB的载波添加请求响应之后,该eNB可以确定T-gNB将采用主站密钥创建PDCP实体。于是,该eNB将向UE发送RRC重配置信令,该RRC重配置信令携带前述载波添加请求响应中所携带的第一指示信息。
当UE识别到前述RRC重配置信令中的第一指示信息,则该UE便可获知采用主站密钥。由于,在此之前该UE的PDCP实体采用的是主站密钥,因此,该UE可以延续使用采用该主站密钥的PDCP实体,而无需重建采用新密钥的PDCP实体。因此,在后续步骤中,采用主站密钥加密的下行数据包在传输至UE时,该UE可以采用该PDCP实体解密该下行数据包,进而获得该下行数据包中的业务数据。
应当理解的是,前述RRC重配置信令还可以携带其他用于重配置的参数,具体此处不做限定。
1006,UE向eNB发送RRC重配置完成(RRC connection reconfiguration complete)信令。
其中,该RRC重配置完成信令用于通知eNB该UE已收到前述第一指示信息,并完成了相关的重配置。
1007,eNB向T-gNB发送辅载波重配置完成信令(SgNB reconfiguration complete)。
其中,该辅载波重配置完成信令用于通知T-gNB前述UE已经重配置完成,该T-gNB可以开始为UE的随机接入做准备。
1008,UE向T-gNB发起随机接入流程。
具体地,UE与T-gNB之间的随机接入过程与前文步骤407中UE与gNB之间的随机接入过程类似,具体请参阅前文步骤407的相关介绍,此处不再赘述。
当该UE成功接入该T-gNB,则说明此后UE可以从前述T-gNB接收下行数据包。也可以理解为,该T-gNB可以为前述UE提供服务。
1009,S-gNB控制S-gNB PDCP实体向eNB RLC实体发送下行数据包。
其中,步骤1009中的下行数据包来自该下行数据包来自服务网关S-GW。该S-gNB PDCP实体将采用主站密钥对来自S-GW的下行数据包加密,然后,控制该S-gNB PDCP实体将该下行数据包传输至eNB RLC实体。
应当注意的是,本步骤1009与前述步骤1002至步骤1008是相互独立的。当该S-gNB执行步骤1001之后,该S-gNB将执行步骤1009。
1010,eNB控制eNB RLC实体向UE PDCP实体发送下行数据包。
本实施例中,步骤1010与前述步骤1008至步骤1009是相互独立的。但是,在步骤1007之后,该eNB将立即执行步骤1010。
本步骤中,eNB控制eNB RLC实体将前述采用主站密钥加密的下行数据包经过MAC层和物理层传输至UE PDCP实体。由于该UE PDCP实体也采用的主站密钥,因此,该UE PDCP实体能够对该下行数据包解密并获取该下行数据包中的业务数据。
本实施例中,在载波变更之前,UE和S-gNB均采用主站密钥,并且,UE在收到前述第一指示信息之后,仍旧采用的是主站密钥。因此,该UE PDCP实体可以对S-gNB PDCP实体采用主站密钥加密的下行数据包进行解密。于是,该S-gNB控制S-gNB PDCP实体向eNB PDCP实体发送下行数据包,然后,该eNB控制eNB RLC实体向UE PDCP实体发送下行数据包。这样的实施方式,可以使得在S-gNB发出辅载波变更请求之后,T-gNB开始传输下行数据包之前,该UE可以接收一部分缓存于S-gNB的下行数据包。因此,可以缩短中断传输下行数据包的时间,缩短网络延迟,降低UE业务中断的几率。
1011,T-gNB通知eNB随机接入完成。
本实施例中,步骤1011与前述步骤1009至步骤1010是相互独立的,该步骤1011在步骤1008之后执行即可。
1012,eNB向MME发送演进的无线接入承载修改指示(E-RAB modification indication)。
其中,该演进的无线接入承载修改指示用于请求MME将传输路径切换至T-gNB。
1013、MME向S-GW发送路径切换请求(path switch request)。
其中,路径切换请求用于请求S-GW将后续的下行数据包传输至T-gNB。于是,该T-gNB PDCP实体将从前述S-GW接收下行数据包。
1014,S-GW向MME发送路径切换请求响应(path switch request acknowledge)。
其中,路径切换请求响应用于指示切换已完成。
1015,S-GW向S-gNB发送结束标记(end marker)数据包。
其中,该结束标记数据包为S-GW发送给S-gNB的最后一个数据包,用于指示在该结束标记数据包之后,该S-GW不再向该S-gNB发送下行数据包。
1016,S-gNB将前述结束标记数据包转发至eNB。
1017,eNB将前述结束标记数据包转发至T-gNB。
本实施例中,经过步骤1016和步骤1017,S-gNB通过eNB将前述结束标记数据包转发给T-gNB,以指示该已经将最后一个数据包转发给T-gNB。当该T-gNB收到该结束标记数据包之后,该T-gNB将执行步骤1021。
1018,S-gNB向eNB发送系统帧号状态转发(SN status transfer)。
1019,eNB向T-gNB发送前述系统帧号状态转发。
本实施例中,系统帧号状态转发用于指示当前S-GW已传输给S-gNB的下行数据包的序列号。将该序列号发送至T-gNB,可以使得该T-gNB在后续过程中从S-GW接收该序列号之后的数据包。于是,可以避免该T-gNB重复接收下行数据包或遗漏下行数据包。
应当注意的是,步骤1016至步骤1017与步骤1018至步骤1019是相互独立的。
1020,MME向eNB发送演进的无线接入承载修改指示完成(E-RAB modification indication complete)。
1021,T-gNB控制T-gNB PDCP实体从S-GW接收下行数据包。
当该T-gNB收到结束标记数据包之后,该T-gNB PDCP实体被激活。该T-gNB便能够控制T-gNB PDCP实体从S-GW接收下行数据包。由于,该T-gNB在创建T-gNB PDCP实体时采用的是主站密钥,因此,该T-gNB PDCP实体将对收到的下行数据包采用主站密钥进行加密,然后再进行后续传输。
1022,T-gNB控制T-gNB PDCP实体向T-gNB RLC实体和eNB RLC实体发送下行数据包。
1023,T-gNB控制T-gNB RLC实体向UE PDCP实体发送下行数据包。
1024,eNB控制eNB RLC实体向UE PDCP实体发送下行数据包。
本实施例中,步骤1023和步骤1024是同时执行的。
为便于理解,以图9C和图9D为例进行介绍。此时,前述图9C和图9D中的核心网设备为S-GW,主网络设备为eNB,源辅网络设备为S-gNB,目标辅网络设备为T-gNB,终端设备为UE。
当S-gNB执行前述步骤1009且eNB执行前述步骤1010时,下行数据包的流向如图9C所示。S-GW将下行数据包发送给S-gNB PDCP实体07,该S-gNB PDCP实体07采用主站密钥对该下行数据包进行加解密,并控制该S-gNB PDCP实体07将采用主站密钥加密的下行数据包传输至eNB RLC实体05,再由该eNB RLC实体05将前述下行数据包经过MAC层和物理层传输至UE PDCP实体01。该UE收到该下行数据包之后,该UE可以控制该UE PDCP实体01采用主站密钥对该下行数据包解密,从而获取该下行数据包的业务数据。
当T-gNB执行前述步骤1021至步骤1023,eNB执行前述步骤1024时,下行数据包的 流向如图9D所示。S-GW将下行数据包发送给T-gNB PDCP实体10,该T-gNB PDCP实体10采用主站密钥对该下行数据包进行加解密,并控制该T-gNB PDCP实体10将采用主站密钥加密的下行数据包传输至eNB RLC实体05和T-gNB RLC实体11,再由该eNB RLC实体05和T-gNB RLC实体11分别将前述下行数据包传输至UE PDCP实体01,以使得该UE可以控制该UE PDCP实体01采用主站密钥对该下行数据包解密,进而获取该下行数据包的业务数据。
如图11所示,为当主网络设备发起变更辅网络设备时,主网络设备、源辅网络设备、目标辅网络设备和终端设备三者之间的信令交互过程。
在变更之前,该终端设备通过该主网络设备和源辅网络设备接收来自核心网的下行数据包,并且,采用该主网络设备的密钥(即主站密钥)进行加解密数据。具体请参阅前述图9A对应的实施例中,关于图9B的相关介绍,具体此处不再赘述。
当该主网络设备准备将源辅网络设备变更至目标辅网络设备时,该主网络设备、源辅网络设备(即待删除的辅网络设备)和目标辅网络设备(即待添加的辅网络设备)将执行如下步骤:
1101,主网络设备向目标辅网络设备发送第三消息。
1102,目标辅网络设备采用主站密钥创建目标辅网络设备的PDCP实体。
1103,目标辅网络设备向主网络设备发送第二消息。
1104,主网络设备向终端设备发送第一消息。
本实施例中,步骤1101至步骤1104与前述步骤902至步骤905相同,具体请参阅前述步骤902至步骤905中的相关介绍,此处不再赘述。
本实施例中,由于是主网络设备发起的辅载波变更,因此,主网络设备需要先添加目标辅网络设备,再删除源辅网络设备。因此,当执行了前述步骤1101至步骤1104之后,该主网络设备将执行步骤1105。
1105,主网络设备向源辅网络设备发送辅载波释放请求。
其中,该辅载波释放请求用于通知该源辅网络设备准备释放。
1106,源辅网络设备向主网络设备发送辅载波释放请求响应。
其中,该辅载波释放请求响应用于指示该源辅网络设备已确认,并将在后续过程中释放。
本实施例中,由于载波变更是由主网络设备发起的,当该源辅网络设备收到前述辅载波释放请求时,该源辅网络设备才执行释放流程。因此,步骤1105和步骤1106将作为触发源,触发该源辅网络设备执行步骤1107。
1107,源辅网络设备控制源辅网络设备的PDCP实体向主网络设备的RLC实体发送下行数据包。
1108,主网络设备控制主网络设备的RLC实体向终端设备发送下行数据包。
本实施例中,步骤1107至步骤1108与前述步骤906至步骤907相同,具体请参阅前述步骤906至步骤907中的相关介绍,此处不再赘述。
本实施例中,在载波变更之前,终端设备和源辅网络设备均采用主站密钥,并且,终端设备在收到前述第一指示信息之后,仍旧采用的是主站密钥。因此,该终端设备的PDCP实体可以对源辅网络设备的PDCP实体采用主站密钥加密的下行数据包进行解密。于是,该源辅网络设备控制源辅网络设备的PDCP实体向主网络设备的PDCP实体发送下行数据包,然后,该主网络设备控制主网络设备的RLC实体向终端设备发送下行数据包,经过MAC层和物理层将该下行数据包传输至终端设备的PDCP实体。这样的实施方式,可以使得在源辅网络设备发出辅载波变更请求之后,目标辅网络设备开始传输下行数据包之前,该终端设备可以接收一部分缓存于源辅网络设备的下行数据包。因此,可以缩短中断传输下行数据包的时间,缩短网络延迟,降低终端设备业务中断的几率。
为便于进一步理解前述图11对应的实施例,如图12所示,下面以主网络设备为eNB,源辅网络设备为S-gNB,目标辅网络设备为T-gNB,终端设备为UE为例进行进一步介绍:
1201,eNB向T-gNB发送辅载波添加请求(SgNB addition request)。
其中,该辅载波添加请求携带主站密钥(即eNB的密钥),该辅载波添加请求用于通知T-gNB采用该主站密钥建立PDCP实体。
1202,T-gNB采用主站密钥创建T-gNB PDCP实体。
应当理解的是,步骤1202中,虽然T-gNB采用主站密钥创建了PDCP实体,但该PDCP实体还未被激活,无法立即参与数据传输。
1203,T-gNB向eNB发送辅载波添加请求响应(SgNB addition request acknowledge)。
其中,该辅载波添加请求响应携带第一指示信息,该第一指示信息用于指示该T-gNB确认将采用该主站密钥创建PDCP实体。该第一指示信息由T-gNB填入在SgNB to MeNB Container中的一个信元表示。该SgNB to MeNB Container中存在一个用于指示密钥的信元key to use,该T-gNB将该key to use信元设置为master,以表示该T-gNB将使用主站密钥。
应当注意的是,步骤1202和步骤1203无明确的时间先后顺序限定。也就是说,该T-gNB可以先执行步骤1202再执行步骤1203,也可以先执行步骤1203再执行步骤1202,还可以同时执行步骤1202和步骤1203,具体此处不做限定。
1204,eNB向UE发送RRC重配置(RRC connection reconfiguration)信令。
当该eNB收到来自T-gNB的载波添加请求响应之后,该eNB可以确定T-gNB将采用主站密钥创建PDCP实体。于是,该eNB将向UE发送RRC重配置信令,该RRC重配置信令携带前述载波添加请求响应中所携带的第一指示信息。
当UE识别到前述RRC重配置信令中的第一指示信息,则该UE便可获知采用主站密钥。由于,在此之前该UE的PDCP实体采用的是主站密钥,因此,该UE可以延续使用采用该主站密钥的PDCP实体,而无需重建采用新密钥的PDCP实体。因此,在后续步骤中,采用主站密钥加密的下行数据包在传输至UE时,该UE可以采用该PDCP实体解密该下行数据包,进而获得该下行数据包中的业务数据。
应当理解的是,前述RRC重配置信令还可以携带其他用于重配置的参数,具体此处不做限定。
1205,UE向eNB发送RRC重配置完成(RRC connection reconfiguration complete)信令。
其中,该RRC重配置完成信令用于通知eNB该UE已收到前述第一指示信息,并完成了相关的重配置。
本实施例中,当eNB收到来自UE的RRC重配置完成信令之后,该eNB将向S-gNB发起辅载波释放流程。该eNB将执行步骤1206。
1206,eNB向S-gNB发送辅载波释放请求(SgNB release request)。
本实施例中,S-gNB收到来自eNB的辅载波释放请求之后,该S-gNB将执行步骤1207和步骤1208。应当理解的是,步骤1207和步骤1208之间无明确时间先后顺序的限定。也就是说,该S-gNB可以先执行步骤1207再执行步骤1208,也可以先执行步骤1208再执行步骤1207,还可以同时执行步骤1207和步骤1208。具体此处不做限定。
1207,S-gNB向eNB发送辅载波释放请求响应(SgNB release request acknowledge)。
1208,S-gNB控制S-gNB PDCP实体向eNB RLC实体发送下行数据包。
其中,步骤1208中的下行数据包来自该下行数据包来自服务网关S-GW。该S-gNB PDCP实体将采用主站密钥对来自S-GW的下行数据包加密,然后,控制该S-gNB PDCP实体将该下行数据包传输至eNB RLC实体。
1209,eNB向T-gNB发送辅载波重配置完成(SgNB reconfiguration complete)信令。
其中,该辅载波重配置完成信令用于通知T-gNB前述UE已经重配置完成,该T-gNB可以开始为UE的随机接入做准备。
1210,UE向T-gNB发起随机接入流程。
具体地,UE与T-gNB之间的随机接入过程与前文步骤407中UE与gNB之间的随机接入过程类似,具体请参阅前文步骤407的相关介绍,此处不再赘述。
当该UE成功接入该T-gNB,则说明此后UE可以从前述T-gNB接收下行数据包。也可以理解为,该T-gNB可以为前述UE提供服务。
1211,eNB控制eNB RLC实体向UE PDCP实体发送下行数据包。
本实施例中,步骤1211与前述步骤1209至步骤1210是相互独立的。但是,在步骤1208之后,该eNB将立即执行步骤1211。
本步骤中,eNB控制eNB RLC实体将前述采用主站密钥加密的下行数据包经过MAC层和物理层传输至UE PDCP实体。由于该UE PDCP实体也采用的主站密钥,因此,该UE PDCP实体能够对该下行数据包解密并获取该下行数据包中的业务数据。
本实施例中,在载波变更之前,UE和S-gNB均采用主站密钥,并且,UE在收到前述第一指示信息之后,仍旧采用的是主站密钥。因此,该UE PDCP实体可以对S-gNB PDCP实体采用主站密钥加密的下行数据包进行解密。于是,该S-gNB控制S-gNB PDCP实体向eNB PDCP实体发送下行数据包,然后,该eNB控制eNB RLC实体向UE发送下行数据包,经过MAC层和物理层传输至UE PDCP实体。这样的实施方式,可以使得在S-gNB发出辅载波变更请求之后,T-gNB开始传输下行数据包之前,该UE可以接收一部分缓存于S-gNB的下行数据包。因此,可以缩短中断传输下行数据包的时间,缩短网络延迟,降低UE业 务中断的几率。
1212,T-gNB通知eNB随机接入完成。
1213,eNB向MME发送演进的无线接入承载修改指示(E-RAB modification indication)。
1214,MME向S-GW发送路径切换请求(path switch request)。
1215,S-GW向MME发送路径切换请求响应(path switch request acknowledge)。
1216,S-GW向S-gNB发送结束标记(end marker)数据包。
1217,S-gNB将前述结束标记数据包转发至eNB。
1218,eNB将前述结束标记数据包转发至T-gNB。
1219,S-gNB向eNB发送系统帧号状态转发(SN status transfer)。
1220,eNB向T-gNB发送前述系统帧号状态转发。
1221,MME向eNB发送演进的无线接入承载修改指示完成(E-RAB modification indication complete)。
1222,T-gNB控制T-gNB PDCP实体从S-GW接收下行数据包。
1223,T-gNB控制T-gNB PDCP实体向T-gNB RLC实体和eNB RLC实体发送下行数据包。
1224,T-gNB控制T-gNB RLC实体向UE PDCP实体发送下行数据包。
1225,eNB控制eNB RLC实体向UE PDCP实体发送下行数据包。
本实施例中,步骤1213至步骤1225与前述步骤1012至步骤1024相同,具体请参阅前述步骤1012至步骤1024的相关介绍,具体此处不再赘述。
如图13所示,本实施例提供了一种通信设备130的结构示意图。应当理解的是,前述图2、图3A、图5A、图7、图9A以及图11对应的方法实施例中的终端设备,以及图4、图6、图8、图10以及图12对应的方法实施例中的UE均可以基于本实施例中图13所示的通信设备130的结构。
该通信设备130包括至少一个处理器1301、至少一个存储器1302和至少一个收发器1303。其中,处理器1301、存储器1302和收发器1303相连。可选的,该通信设备130还可以包括输入设备1305、输出设备1306和一个或多个天线1304。其中,天线1304与收发器1303相连,输入设备1305、输出设备1306与处理器1301相连。
本实施例中,该存储器1302主要用于存储软件程序和数据。存储器1302可以是独立存在,与处理器1301相连。可选的,该存储器1302可以和该处理器1301集成于一体,例如集成于一个或多个芯片之内。其中,该存储器1302能够存储执行本申请实施例的技术方案的程序代码,并由处理器1301来控制执行,被执行的各类计算机程序代码也可被视为是处理器1301的驱动程序。应当理解的是,本实施例中的图13仅示出了一个存储器和一个处理器,但是,在实际应用中,该通信设备130可以存在多个处理器或多个存储器,具体此处不做限定。此外,该存储器1302也可以称为存储介质或者存储设备等。该存储器1302可以为与处理器处于同一芯片上的存储元件(即片内存储元件),或者为独立的存储元件,本申请实施例对此不做限定。
本实施例中,该收发器1303可以用于支持该通信设备130与接入网设备之间射频信号的接收或者发送,收发器1303可以与天线1304相连。收发器1303包括发射机Tx和接收机Rx。具体地,一个或多个天线1304可以接收射频信号,该收发器1303的接收机Rx用于从天线1304接收所述射频信号,并将射频信号转换为数字基带信号或数字中频信号,并将该数字基带信号或数字中频信号提供给所述处理器1301,以便处理器1301对该数字基带信号或数字中频信号做进一步的处理,例如解调处理和译码处理。此外,收发器1303中的发射机Tx还用于从处理器1301接收经过调制的数字基带信号或数字中频信号,并将该经过调制的数字基带信号或数字中频信号转换为射频信号,并通过一个或多个天线1304发送所述射频信号。具体地,接收机Rx可以选择性地对射频信号进行一级或多级下混频处理和模数转换处理以得到数字基带信号或数字中频信号,前述下混频处理和模数转换处理的先后顺序是可调整的。发射机Tx可以选择性地对经过调制的数字基带信号或数字中频信号时进行一级或多级上混频处理和数模转换处理以得到射频信号,所述上混频处理和数模转换处理的先后顺序是可调整的。数字基带信号和数字中频信号可以统称为数字信号。
应当理解的是,前述收发器1303也可以称为收发单元、收发机、收发装置等。可选的,可以将收发单元中用于实现接收功能的器件视为接收单元,将收发单元中用于实现发送功能的器件视为发送单元,即收发单元包括接收单元和发送单元,接收单元也可以称为接收机、输入口、接收电路等,发送单元可以称为发射机、发射器或者发射电路等。
该处理器1301可以是基带处理器,也可以是中央处理单元(central processing unit,CPU),基带处理器和CPU可以集成在一起或者分开。该处理器1301可以用于为该终端设备实现各种功能,例如用于对通信协议以及通信数据进行处理,或者用于对整个终端设备进行控制,执行软件程序,处理软件程序的数据;或者用于协助完成计算处理任务,例如对图形图像处理或者音频处理等等;或者处理器1301用于实现上述功能中的一种或者多种。
此外,该输出设备1306和处理器1301通信,可以以多种方式来显示信息,具体从此处不做限定。
具体地,在该通信设备130中,该收发器1303能够接收主网络设备发送的第一消息。其中,该终端设备在载波变更之前采用该主网络设备的密钥进行加解密数据,该第一消息用于指示该终端设备在载波变更之后采用该终端设备存储的该主网络设备的密钥进行加解密数据。
具体地,在该通信设备130中,该处理器1301控制该终端设备的PDCP实体从该主网络设备的RLC实体接收下行数据包,该下行数据包来自该主网络设备的PDCP实体,该终端设备的PDCP实体采用该主网络设备的密钥加解密该下行数据包。
具体地,在该通信设备130中,该处理器1301控制该终端设备的PDCP实体从该主网络设备的RLC实体接收下行数据包,该下行数据包来自辅网络设备的PDCP实体,该辅网络设备为待释放的网络设备,该终端设备的PDCP实体和该辅网络设备的PDCP实体均采用该主网络设备的密钥加解密该下行数据包。
其余可以参考上述实施例中终端设备或UE的方法,此处不再赘述。
如图14所示,本实施例提供了另一种通信设备140的结构示意图。应当理解的是,前述图2、图3A、图5A、图7、图9A以及图11对应的方法实施例中的主网络设备和辅网络设备,以及图4、图6、图8、图10以及图12对应的方法实施例中的eNB和gNB均可以基于本实施例中图14所示的通信设备140的结构。还应理解的是,当后续演进制式的接入网设备或基站执行本申请实施例所涉及的方法时,后续演进制式的接入网或基站也可以采用本实施例中图14所示的通信设备140的结构。
该通信设备140包括至少一个处理器1401、至少一个存储器1402、至少一个收发器1403、至少一个网络接口1405和一个或多个天线1404。处理器1401、存储器1402、收发器1403和网络接口1405通过连接装置相连,天线1404与收发器1403相连。其中,前述连接装置可包括各类接口、传输线或总线等,本实施例对此不做限定。
其中,前述网络接口1405用于使该通信设备140通过通信链路,与其它通信设备相连。具体地,该网络接口1405可以包括该通信设备140与核心网网元之间的网络接口,例如S1接口;该网络接口1405也可以包括该通信设备140和其他网络设备(例如其他接入网设备或者核心网网元)之间的网络接口,例如X2或者Xn接口。
收发器1403、存储器1402以及天线1404可以参考图13对应实施例中收发器1303、存储器1302以及天线1304的相关描述,具体此处不再赘述。
此外,前述处理器1401主要用于对通信协议以及通信数据进行处理,以及对整个网络设备进行控制,执行软件程序,处理软件程序的数据,例如用于支持该通信设备140执行前述实施例中所描述的动作。通信设备140可以包括基带处理器和中央处理器,其中,基带处理器主要用于对通信协议以及通信数据进行处理,中央处理器主要用于对整个通信设备140进行控制,执行软件程序,处理软件程序的数据。如图14中的处理器1401可以集成基带处理器和中央处理器的功能,本领域技术人员可以理解,基带处理器和中央处理器也可以是各自独立的处理器,通过总线等技术互联。本领域技术人员可以理解,通信设备140可以包括多个基带处理器以适应不同的网络制式,通信设备140可以包括多个中央处理器以增强其处理能力,通信设备140的各个部件可以通过各种总线连接。所述基带处理器也可以表述为基带处理电路或者基带处理芯片。所述中央处理器也可以表述为中央处理电路或者中央处理芯片。对通信协议以及通信数据进行处理的功能可以内置在处理器中,也可以以软件程序的形式存储在存储器中,由处理器执行软件程序以实现基带处理功能。
具体地,当该通信设备140为主网络设备时:
在该通信设备140中,该收发器1403能够向终端设备发送第一消息。其中,该第一消息用于指示该终端设备在载波变更之后采用该终端设备存储的该主网络设备的密钥(主站密钥)进行加解密数据。
在该通信设备140中,该收发器1403能够接收辅网络设备发送的第二消息,该第二消息用于指示该辅网络设备确认将发生变更,该第二消息携带由该辅网络设备配置的该第一指示信息。
在该通信设备140中,该收发器1403能够向该辅网络设备发送第三消息,该第三消息 携带该主网络设备的密钥,该第三消息用于指示该辅网络设备采用该主网络设备的密钥进行加解密数据。
此外,在该通信设备140中,该处理器1403能够控制该主网络设备的PDCP实体向该主网络设备的RLC实体发送下行数据包,并且,控制该主网络设备的RLC实体将该下行数据包发送至该终端设备的PDCP实体。
又例如,该处理器1403能够控制该主网络设备的RLC实体从该辅网络设备的PDCP实体接收下行数据包,该辅网络设备的PDCP实体采用该主网络设备的密钥加解密该下行数据包;控制该主网络设备的RLC实体将该下行数据包发送至该终端设备的PDCP实体,该终端设备的PDCP实体采用该主网络设备的密钥加解密该下行数据包。
又例如,该处理器1403控制该主网络设备的RLC实体从该源辅网络设备的PDCP实体接收下行数据包,该源辅网络设备的PDCP实体采用该主网络设备的密钥加解密该下行数据包;该主网络设备控制该主网络设备的RLC实体将该下行数据包发送至该终端设备的PDCP实体,该终端设备的PDCP实体采用该主网络设备的密钥加解密该下行数据包。
在该通信设备140中,该处理器1401采用该主网络设备的密钥创建PDCP实体。
其余可以参考上述实施例中主网络设备或eNB的方法,此处不再赘述。
具体地,当该通信设备140为辅网络设备时:
在该通信设备140中,该收发器1403能够接收主网络设备发送的第三消息,该第三消息携带该主网络设备的密钥,该第三消息用于指示该辅网络设备采用该主网络设备的密钥进行加解密数据。
在该通信设备140中,该收发器1403能够向该主网络设备发送第二消息,该第二消息用于指示该辅网络设备确认将发生变更,该第二消息携带由该辅网络设备配置的第一指示信息,该第一指示信息用于指示采用该主网络设备的密钥进行加解密数据。
在该通信设备140中,该处理器1401采用该主网络设备的密钥创建PDCP实体。
其余可以参考上述实施例中辅网络设备或gNB的方法,此处不再赘述。
如图15所示,本实施例提供了另一种通信设备150,该通信设备150可以为终端设备或终端设备中的芯片。该通信设备150包括收发单元1501、处理单元1502。
如图16所示,本实施例提供了另一种通信设备160,该通信设备160可以为主网设备或主网设备中的芯片;或者,辅网络设备或辅网络设备中的芯片。该通信设备160包括收发单元1601、处理单元1602。
其中,当该通信设备150为终端设备或者UE时,当通信设备160为接入网设备或基站时,收发单元1501以及收发单元1601在发送信息时可以为发送单元或发射器,收发单元1501以及收发单元1601在接收信息时可以为接收单元或接收器。前述收发单元可以为收发器,此收发器、发射器或接收器可以为射频电路,当终端设备或用户设备包含存储单元时,该存储单元用于存储计算机指令,该处理器与存储器通信连接,处理器执行存储器存储的计算机指令,使终端设备、主网络设备以及辅网络设备执行图2、图3A、图5A、图7、图9A以及图11对应的方法实施例涉及的方法,使UE、eNB以及gNB执行图4、图6、 图8、图10以及图12对应的实施例涉及的方法。此外,前述处理单元1502以及处理单元1602可以是一个通用中央处理器(CPU)、微处理器、数字信号处理器(digital signal processor,DSP)、微控制器(microcontroller unit,MCU)。该处理器可以是个单独的半导体芯片,也可以跟其他电路一起集成为一个半导体芯片,例如,可以跟其他电路(如编解码电路、硬件加速电路或各种总线和接口电路)构成一个片上系统(system-on-a-chip,SoC),或者也可以作为一个特殊应用集成电路(application specific integrated circuit,ASIC)的内置处理器集成在所述ASIC当中。
当该通信设备150为终端设备中的芯片,当该通信设备160为主网设备或辅网络设备中的芯片时,收发单元1501以及收发单元1601可以是输入和/或输出接口、管脚或电路等。此外,前述处理单元1502可以为该终端设备中的芯片的处理器,该处理单元1602可以为该接入网设备中的芯片中的处理器。该处理器可执行存储单元存储的计算机执行指令,以使终端设备内的芯片和接入网设备内的芯片执行图2、图3A、图4、图5A、图6、图7、图8、图9A、图10、图11以及图12对应的实施例涉及的方法。可选地,该存储单元为所述芯片内的存储单元,如寄存器、缓存等,该存储单元还可以是该终端设备内的位于该芯片外部的存储单元。例如,只读存储器(read only memory,ROM)或可存储静态信息和指令的其他类型的静态存储设备,随机存取存储器(random access memory,RAM)等。
应当理解的是,前述终端设备可以存在与终端设备的方法或者流程的步骤对应的功能单元(means),前述接入网设备可以存在与接入网设备的方法或者流程的步骤对应的功能单元。以上模块或单元的一个或多个可以软件、硬件或二者结合来实现。当以上任一模块或单元以软件实现的时候,所述软件以计算机程序指令的方式存在,并被存储在存储器中,处理器可以用于执行所述程序指令以实现以上方法流程。
根据本申请实施例提供的方法,本申请实施例还提供一种通信系统,该通信系统包括终端设备和接入网设备。其中,终端设备的结构可以参阅前述图13对应实施例中的通信设备130;主网络设备或辅网络设备的结构可以参阅前述图14对应实施例中的通信设备140。此外,当前述终端设备为芯片时,该终端设备内的芯片可以参阅前述图15对应实施例中的通信设备150;当前述主网络设备或辅网络设备为芯片时,主网络设备或辅网络设备内的芯片可以参阅前述图16对应实施例中的通信设备160。
在实现过程中,上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成,或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器,闪存、只读存储器,可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器,处理器读取存储器中的信息,结合其硬件完成上述方法的步骤。为避免重复,这里不再详细描述。还应理解,本文中涉及的第一、第二、第三、第四以及各种数字编号仅为描述方便进行的区分,并不用来限制本申请实施例的范围。
应理解,本文中术语“和/或”,仅仅是一种描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三 种情况。另外,本文中字符“/”,一般表示前后关联对象是一种“或”的关系。
应理解,在本申请的各种实施例中,上述各过程的序号的大小并不意味着执行顺序的先后,各过程的执行顺序应以其功能和内在逻辑确定,而不应对本申请实施例的实施过程构成任何限定。
所属领域的技术人员可以清楚地了解到,为描述的方便和简洁,上述描述的系统,装置和单元的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
以上实施例仅用以说明本申请的技术方案,而非对其限制;尽管参照前述实施例对本申请进行了详细的说明,本领域的普通技术人员应当理解:其依然可以对前述各实施例所记载的技术方案进行修改,或者对其中部分技术特征进行等同替换;而这些修改或者替换,并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围。

Claims (35)

  1. 一种数据传输方法,其特征在于,包括:
    主网络设备向终端设备发送第一消息,所述终端设备在载波变更之前采用所述主网络设备的密钥进行加解密数据,所述第一消息用于指示所述终端设备在载波变更之后采用所述终端设备存储的所述主网络设备的密钥进行加解密数据。
  2. 根据权利要求1所述的方法,其特征在于,所述第一消息为无线资源控制RRC重配置消息,所述RRC重配置消息携带第一指示信息,所述第一指示信息用于指示采用所述主网络设备的密钥进行加解密数据。
  3. 根据权利要求2所述的方法,其特征在于,所述主网络设备向终端设备发送第一消息之前,所述方法还包括:
    所述主网络设备接收辅网络设备发送的第二消息,所述第二消息用于指示所述辅网络设备确认将发生变更,所述第二消息携带由所述辅网络设备配置的所述第一指示信息。
  4. 根据权利要求3所述的方法,其特征在于,所述主网络设备接收辅网络设备发送的第二消息之前,所述方法还包括:
    所述主网络设备向所述辅网络设备发送第三消息,所述第三消息携带所述主网络设备的密钥,所述第三消息用于指示所述辅网络设备采用所述主网络设备的密钥进行加解密数据。
  5. 根据权利要求4所述的方法,其特征在于,
    所述第三消息为辅载波添加请求,所述辅载波添加请求用于请求添加所述辅网络设备作为辅载波;
    所述第二消息为辅载波添加请求响应,所述辅载波添加请求响应用于指示所述辅网络设备确认添加,且所述辅网络设备将采用所述主站的密钥进行加解密。
  6. 根据权利要求5所述的方法,其特征在于,所述方法还包括:
    所述主网络设备控制所述主网络设备的分组数据汇聚协议PDCP实体向所述主网络设备的无线链路控制RLC实体发送下行数据包,并且,控制所述主网络设备的RLC实体将所述下行数据包发送至所述终端设备,所述终端设备的PDCP实体采用所述主网络设备的密钥加解密所述下行数据包。
  7. 根据权利要求1或2所述的方法,其特征在于,所述主网络设备向终端设备发送第一消息之前,所述方法还包括:
    所述主网络设备向辅网络设备发送辅载波释放请求,所述辅载波释放请求用于通知所述辅网络设备进行释放;
    所述主网络设备接收所述辅网络设备发送的辅载波释放响应,所述辅载波释放响应用于指示所述辅网络设备确认释放。
  8. 根据权利要求1或2所述的方法,其特征在于,所述主网络设备向终端设备发送第一消息之前,所述方法还包括:
    所述主网络设备接收辅网络设备发送的辅载波释放请求,所述辅载波释放请求用于请求释放所述辅网络设备;
    所述主网络设备向所述辅网络设备发送辅载波释放确认消息,所述辅载波释放确认消息用于指示允许所述辅网络设备进行释放。
  9. 根据权利要求7或8所述的方法,其特征在于,所述方法还包括:
    所述主网络设备控制所述主网络设备的RLC实体从所述辅网络设备的PDCP实体接收下行数据包,所述辅网络设备的PDCP实体采用所述主网络设备的密钥加解密所述下行数据包;
    所述主网络设备控制所述主网络设备的RLC实体将所述下行数据包发送至所述终端设备,所述终端设备的PDCP实体采用所述主网络设备的密钥加解密所述下行数据包。
  10. 根据权利要求4所述的方法,其特征在于,所述辅网络设备为目标辅网络设备,所述第二消息为辅载波添加请求响应,所述第二消息用于指示所述目标辅网络设备确认添加,且所述目标辅网络设备将采用所述主站的密钥进行加解密。
  11. 根据权利要求10所述的方法,其特征在于,所述主网络设备向所述目标辅网络设备发送第三消息之前,所述方法还包括:
    所述主网络设备接收所述源辅网络设备发送的辅载波变更请求,所述载波变更请求携带所述目标辅网络设备的标识信息,所述辅载波变更请求用于指示将所述源辅网络设备变更为所述目标辅网络设备。
  12. 根据权利要求10所述的方法,其特征在于,所述主网络设备接收所述目标辅网络设备发送的第二消息之后,所述方法还包括:
    所述主网络设备向所述源辅网络设备发送载波释放请求,所述载波释放请求用于请求释放所述源辅网络设备;
    所述主网络设备接收所述源辅网络设备发送的载波释放请求响应,所述载波释放请求响应用于确认释放。
  13. 根据权利要求11或12所述的方法,其特征在于,所述方法还包括:
    所述主网络设备控制所述主网络设备的RLC实体从所述源辅网络设备的PDCP实体接收下行数据包,所述源辅网络设备的PDCP实体采用所述主网络设备的密钥加解密所述下行数据包;
    所述主网络设备控制所述主网络设备的RLC实体将所述下行数据包发送至所述终端设备,所述终端设备的PDCP实体采用所述主网络设备的密钥加解密所述下行数据包。
  14. 一种数据传输方法,其特征在于,包括:
    终端设备接收主网络设备发送的第一消息,所述终端设备在载波变更之前采用所述主网络设备的密钥进行加解密数据,所述第一消息用于指示所述终端设备在载波变更之后采用所述终端设备存储的所述主网络设备的密钥进行加解密数据。
  15. 根据权利要求14所述的方法,其特征在于,所述第一消息为无线资源控制RRC重配置消息,所述RRC重配置消息携带第一指示信息,所述第一指示信息用于指示采用所述主网络设备的密钥进行加解密数据。
  16. 根据权利要求14或15所述的方法,其特征在于,所述方法还包括:
    所述终端设备控制所述终端设备的PDCP实体接收来自所述主网络设备的RLC实体的下行数据包,所述下行数据包来自所述主网络设备的PDCP实体,所述终端设备的PDCP实体采用所述主网络设备的密钥加解密所述下行数据包。
  17. 根据权利要求14或15所述的方法,其特征在于,所述方法还包括:
    所述终端设备控制所述终端设备的PDCP实体接收来自所述主网络设备的RLC实体的下行数据包,所述下行数据包来自辅网络设备的PDCP实体,所述辅网络设备为待释放的网络设备,所述终端设备的PDCP实体和所述辅网络设备的PDCP实体均采用所述主网络设备的密钥加解密所述下行数据包。
  18. 一种数据传输方法,其特征在于,包括:
    辅网络设备接收主网络设备发送的第三消息,所述第三消息携带所述主网络设备的密钥,所述第三消息用于指示所述辅网络设备采用所述主网络设备的密钥进行加解密数据;
    所述辅网络设备向所述主网络设备发送第二消息,所述第二消息用于指示所述辅网络设备确认将发生变更,所述第二消息携带由所述辅网络设备配置的第一指示信息,所述第一指示信息用于指示采用所述主网络设备的密钥进行加解密数据。
  19. 根据权利要求18所述的方法,其特征在于,所述方法还包括:
    所述辅网络设备采用所述主网络设备的密钥创建PDCP实体。
  20. 一种数据传输方法,其特征在于,包括:
    辅网络设备控制所述辅网络设备的PDCP实体向主网络设备的RLC实体发送下行数据包,所述辅网络设备的PDCP实体采用所述主网络设备的密钥加解密所述下行数据包。
  21. 一种主网络设备,其特征在于,包括:
    发送模块,用于向终端设备发送第一消息,所述终端设备在载波变更之前采用所述主网络设备的密钥进行加解密数据,所述第一消息用于指示所述终端设备在载波变更之后采用所述终端设备存储的所述主网络设备的密钥进行加解密数据。
  22. 根据权利要求21所述的主网络设备,其特征在于,所述第一消息为无线资源控制RRC重配置消息,所述RRC重配置消息携带第一指示信息,所述第一指示信息用于指示采用所述主网络设备的密钥进行加解密数据。
  23. 根据权利要求22所述的主网络设备,其特征在于,所述主网络设备还包括:
    接收模块,接收辅网络设备发送的第二消息,所述第二消息用于指示所述辅网络设备确认将发生变更,所述第二消息携带由所述辅网络设备配置的所述第一指示信息。
  24. 根据权利要求23所述的主网络设备,其特征在于,所述发送模块,还用于向所述辅网络设备发送第三消息,所述第三消息携带所述主网络设备的密钥,所述第三消息用于指示所述辅网络设备采用所述主网络设备的密钥进行加解密数据。
  25. 根据权利要求24所述的主网络设备,其特征在于,所述主网络设备还包括处理模块,用于控制所述主网络设备的PDCP实体向所述主网络设备的RLC实体发送下行数据包,并且,控制所述主网络设备的RLC实体将所述下行数据包发送至所述终端设备,所述终端设备的PDCP实体采用所述主网络设备的密钥加解密所述下行数据包。
  26. 根据权利要求21或22所述的主网络设备,其特征在于,所述主网络设备还包括处理模块,用于:
    控制所述主网络设备的RLC实体从所述辅网络设备的PDCP实体接收下行数据包,所述辅网络设备的PDCP实体采用所述主网络设备的密钥加解密所述下行数据包;
    控制所述主网络设备的RLC实体将所述下行数据包发送至所述终端设备,所述终端设备的PDCP实体采用所述主网络设备的密钥加解密所述下行数据包。
  27. 根据权利要求21至24中任意一项所述的主网络设备,其特征在于,所述主网络设备还包括处理模块,用于:
    控制所述主网络设备的RLC实体从所述源辅网络设备的PDCP实体接收下行数据包,所述源辅网络设备的PDCP实体采用所述主网络设备的密钥加解密所述下行数据包;
    控制所述主网络设备的RLC实体将所述下行数据包发送至所述终端设备,所述终端设备的PDCP实体采用所述主网络设备的密钥加解密所述下行数据包。
  28. 一种终端设备,其特征在于,包括:
    接收模块,用于接收主网络设备发送的第一消息,所述终端设备在载波变更之前采用所述主网络设备的密钥进行加解密数据,所述第一消息用于指示所述终端设备在载波变更之后采用所述终端设备存储的所述主网络设备的密钥进行加解密数据。
  29. 根据权利要求28所述的终端设备,其特征在于,所述第一消息为无线资源控制RRC重配置消息,所述RRC重配置消息携带第一指示信息,所述第一指示信息用于指示采用所述主网络设备的密钥进行加解密数据。
  30. 根据权利要求28或29所述的终端设备,其特征在于,所述终端设备还包括:
    处理模块,用于控制所述终端设备的PDCP实体接收来自所述主网络设备的RLC实体的下行数据包,所述下行数据包来自所述主网络设备的PDCP实体,所述终端设备的PDCP实体采用所述主网络设备的密钥加解密所述下行数据包。
  31. 根据权利要求28或29所述的终端设备,其特征在于,所述终端设备还包括:
    处理模块,用于控制所述终端设备的PDCP实体接收来自所述主网络设备的RLC实体的下行数据包,所述下行数据包来自辅网络设备的PDCP实体,所述辅网络设备为待释放的网络设备,所述终端设备的PDCP实体和所述辅网络设备的PDCP实体均采用所述主网络设备的密钥加解密所述下行数据包。
  32. 一种辅网络设备,其特征在于,包括:
    接收模块,用于接收主网络设备发送的第三消息,所述第三消息携带所述主网络设备的密钥,所述第三消息用于指示所述辅网络设备采用所述主网络设备的密钥进行加解密数据;
    发送模块,用于向所述主网络设备发送第二消息,所述第二消息用于指示所述辅网络设备确认将发生变更,所述第二消息携带由所述辅网络设备配置的第一指示信息,所述第一指示信息用于指示采用所述主网络设备的密钥进行加解密数据。
  33. 根据权利要求32所述的辅网络设备,其特征在于,所述辅网络设备还包括:
    处理模块,用于采用所述主网络设备的密钥创建PDCP实体。
  34. 一种辅网络设备,其特征在于,包括:
    处理模块,用于控制所述辅网络设备的PDCP实体向主网络设备的RLC实体发送下行数据包,所述辅网络设备的PDCP实体采用所述主网络设备的密钥加解密所述下行数据包。
  35. 一种通信系统,其特征在于,包括:
    如权利要求21至27中任意一项所述的主网络设备,如权利要求28至31中任意一项所述的终端设备,以及如权利要求32至34中任意一项所述的辅网络设备。
PCT/CN2021/091332 2020-07-27 2021-04-30 一种数据传输方法以及相关设备 WO2022021984A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP21850474.4A EP4185069A4 (en) 2020-07-27 2021-04-30 DATA TRANSMISSION METHOD AND ASSOCIATED DEVICE
KR1020237005497A KR20230040361A (ko) 2020-07-27 2021-04-30 데이터 전송 방법 및 관련 장치
US18/159,188 US20230164548A1 (en) 2020-07-27 2023-01-25 Data transmission method and related device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010731310.6A CN114071800B (zh) 2020-07-27 2020-07-27 一种数据传输方法以及相关设备
CN202010731310.6 2020-07-27

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/159,188 Continuation US20230164548A1 (en) 2020-07-27 2023-01-25 Data transmission method and related device

Publications (1)

Publication Number Publication Date
WO2022021984A1 true WO2022021984A1 (zh) 2022-02-03

Family

ID=80037518

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/091332 WO2022021984A1 (zh) 2020-07-27 2021-04-30 一种数据传输方法以及相关设备

Country Status (5)

Country Link
US (1) US20230164548A1 (zh)
EP (1) EP4185069A4 (zh)
KR (1) KR20230040361A (zh)
CN (1) CN114071800B (zh)
WO (1) WO2022021984A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102711100A (zh) * 2012-04-24 2012-10-03 中国联合网络通信集团有限公司 语音加解密处理方法、基站及网络系统
CN107360569A (zh) * 2013-12-27 2017-11-17 华为技术有限公司 一种安全密钥上下文分发方法,移动管理实体及基站
CN108347727A (zh) * 2017-01-24 2018-07-31 中兴通讯股份有限公司 一种数据传输方法及装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114885375A (zh) * 2016-08-09 2022-08-09 三星电子株式会社 无线通信系统中管理用户平面操作的方法和装置
CN111182539B (zh) * 2017-03-24 2023-04-07 华为技术有限公司 通信方法与设备
EP3677088A4 (en) * 2017-09-29 2020-10-14 Samsung Electronics Co., Ltd. USER PROCESS AND EQUIPMENT FOR MANAGING A DUAL CONNECTIVITY USER PLAN IN A WIRELESS COMMUNICATION SYSTEM
CN110710246A (zh) * 2017-11-14 2020-01-17 Oppo广东移动通信有限公司 处理无线链路失败的方法、终端设备和网络设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102711100A (zh) * 2012-04-24 2012-10-03 中国联合网络通信集团有限公司 语音加解密处理方法、基站及网络系统
CN107360569A (zh) * 2013-12-27 2017-11-17 华为技术有限公司 一种安全密钥上下文分发方法,移动管理实体及基站
CN108347727A (zh) * 2017-01-24 2018-07-31 中兴通讯股份有限公司 一种数据传输方法及装置

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
NEC: "DL PDCP SN handling for RLC UM", 3GPP DRAFT; R2-1915452, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Reno, USA; 20191118 - 20191122, 8 November 2019 (2019-11-08), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051817230 *
See also references of EP4185069A4
TCL: "Interaction between PDCP and RLC Entities for duplication in NR-NR DC", 3GPP DRAFT; R2-1801938 INTERACTION BETWEEN PDCP AND RLC ENTITIES FOR DUPLICATION IN NR-NR DC, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Athens, Greece; 20180226 - 20180302, 14 February 2018 (2018-02-14), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051399048 *

Also Published As

Publication number Publication date
EP4185069A1 (en) 2023-05-24
CN114071800B (zh) 2024-04-12
US20230164548A1 (en) 2023-05-25
CN114071800A (zh) 2022-02-18
KR20230040361A (ko) 2023-03-22
EP4185069A4 (en) 2024-01-17

Similar Documents

Publication Publication Date Title
US10785824B2 (en) Information processing method and related apparatus
US10512009B2 (en) Method for user equipment to switch base station, base station and user equipment
TWI762684B (zh) 切換方法、存取網設備和終端設備
CN109982360B (zh) 通信方法和装置
WO2019242749A1 (zh) 一种切换方法及装置
WO2019095974A1 (zh) 数据处理方法、装置以及计算机存储介质
WO2019024032A1 (zh) 数据传输方法、相关设备及通信系统
CN108781376A (zh) 数据传输方法、用户设备及接入网设备
US20210345195A1 (en) Mobility enforcement in connected wireless state
TWI720571B (zh) 無線電間接入技術切換
WO2019095114A1 (zh) 处理无线链路失败的方法、终端设备和网络设备
CN104429109B (zh) 一种通信方法及装置
WO2020088611A1 (zh) 一种重置mac层、数据传输方法及装置
WO2022021984A1 (zh) 一种数据传输方法以及相关设备
WO2021238813A1 (zh) 一种获取密钥的方法及装置
WO2017193807A1 (zh) 一种数据传输方法、用户终端、基站和系统
WO2018202204A1 (zh) 一种基于反转服务流特性的通信方法及装置
WO2024093719A1 (zh) 一种数据传输的方法和装置
WO2024067365A1 (zh) 数据传输方法及装置
WO2020124540A1 (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: 21850474

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 20237005497

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2021850474

Country of ref document: EP

Effective date: 20230214