WO2020220238A1 - 用于小区切换的方法及设备 - Google Patents

用于小区切换的方法及设备 Download PDF

Info

Publication number
WO2020220238A1
WO2020220238A1 PCT/CN2019/085100 CN2019085100W WO2020220238A1 WO 2020220238 A1 WO2020220238 A1 WO 2020220238A1 CN 2019085100 W CN2019085100 W CN 2019085100W WO 2020220238 A1 WO2020220238 A1 WO 2020220238A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdcp entity
terminal device
base station
pdcp
parameter
Prior art date
Application number
PCT/CN2019/085100
Other languages
English (en)
French (fr)
Inventor
尤心
卢前溪
Original Assignee
Oppo广东移动通信有限公司
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 Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to PCT/CN2019/085100 priority Critical patent/WO2020220238A1/zh
Priority to EP19927220.4A priority patent/EP3934321A4/en
Priority to CN201980090039.8A priority patent/CN113330775A/zh
Priority to CN202111107327.5A priority patent/CN113660707A/zh
Priority to KR1020217039064A priority patent/KR20220002597A/ko
Publication of WO2020220238A1 publication Critical patent/WO2020220238A1/zh
Priority to US17/497,093 priority patent/US20220030470A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0016—Hand-off preparation specially adapted for end-to-end data sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0077—Transmission or use of information for re-establishing the radio link of access information of target access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/25—Maintenance of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H04W36/00695—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink using split of the control plane or user plane
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/02—Buffering or recovering information during reselection ; Modification of the traffic flow during hand-off
    • H04W36/023—Buffering or recovering information during reselection
    • H04W36/0235—Buffering or recovering information during reselection by transmitting sequence numbers, e.g. SN status transfer

Definitions

  • the embodiments of the present application relate to the field of communications, and more specifically, to a method and device for cell handover.
  • the New Radio (NR) system supports cell handover, for example, when a terminal device moves from one cell to another, or due to wireless communication service load adjustment, activation operation and maintenance, equipment failure, etc., in order to ensure continuous communication
  • the quality and service quality need to transfer the communication link between the terminal device and the source base station to the target base station, that is, perform the handover process.
  • PDCP packet data convergence protocol
  • This application provides a method and device for cell handover, and provides a method for a terminal device to establish a PDCP entity during the handover process.
  • a method for cell handover including: establishing a first packet data convergence protocol PDCP entity, where the first PDCP entity is used for communication between a terminal device and a target cell base station; and releasing a second PDCP Entity, the second PDCP entity is used for communication between the terminal device and the source cell base station, wherein the time of releasing the second PDCP entity is no earlier than the time of establishing the first PDCP entity.
  • a method for cell handover including: releasing a second PDCP entity, where the second PDCP entity is used for communication between a source cell base station and a terminal device, wherein the second PDCP is released The time of the entity is no earlier than the time when the terminal device establishes a first PDCP entity, and the first PDCP entity is used for communication between the terminal device and the target cell base station.
  • a method for cell handover including: establishing a first packet data convergence protocol PDCP entity, the first PDCP entity being used for communication between a target cell base station and a terminal device, wherein The time of a PDCP entity is no later than the time when the terminal device releases a second PDCP entity, and the second PDCP entity is used for communication between the terminal device and the source cell base station.
  • a terminal device which is used to execute the method in the first aspect or its implementation manners.
  • the terminal device includes a functional module for executing the method in the foregoing first aspect or each implementation manner thereof.
  • a network device is provided, which is used to execute the method in the second aspect or its implementation manners.
  • the network device includes a functional module for executing the method in the foregoing second aspect or each implementation manner thereof.
  • a network device is provided, which is used to execute the method in the third aspect or its implementation manners.
  • the network device includes a functional module for executing the method in the third aspect or its implementation manners.
  • a terminal device including a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory to execute the method in the above-mentioned first aspect or each of its implementation modes.
  • a network device including a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory to execute the method in the above-mentioned second aspect or each of its implementation modes.
  • a network device including a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory, and execute the method in the third aspect or its implementation manners.
  • a device for implementing any one of the foregoing first to third aspects or the method in each implementation manner thereof.
  • the device includes: a processor, configured to call and run a computer program from the memory, so that the device installed with the device executes any one of the above-mentioned first aspect to the third aspect or any of its implementation modes method.
  • a computer-readable storage medium for storing a computer program that enables a computer to execute any one of the above-mentioned first to third aspects or the method in each implementation manner thereof.
  • a computer program product including computer program instructions that cause a computer to execute any one of the above-mentioned first to third aspects or the method in each implementation manner thereof.
  • a computer program which, when run on a computer, causes the computer to execute any one of the above-mentioned first to third aspects or the method in each implementation manner thereof.
  • the establishment of the target PDCP entity can be achieved during the cell handover of the terminal equipment, and the establishment of the PDCP of the terminal equipment can also meet the handover interruption time of 0 ms.
  • Fig. 1 is a schematic diagram of a wireless communication system applied in an embodiment of the present application.
  • Fig. 2 is a schematic diagram of a contention-based random access process provided by an embodiment of the present application.
  • Fig. 3 is a schematic diagram of a non-contention-based random access process provided by an embodiment of the present application.
  • Figure 4 is a schematic diagram of a cell handover method provided by an embodiment of the present application.
  • Fig. 5 is a schematic flowchart of a method for cell handover provided by an embodiment of the present application.
  • FIG. 6 is a schematic flowchart of another method for cell handover provided by an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of another method for cell handover provided by an embodiment of the present application.
  • FIG. 8 is a schematic diagram of a PDCP entity established by a terminal device according to an embodiment of the present application.
  • FIG. 9 is a schematic diagram of a process of establishing a PDCP entity by a terminal device according to an embodiment of the present application.
  • FIG. 10 is a schematic diagram of data transmission by a terminal device according to an embodiment of the present application.
  • FIG. 11 is a schematic diagram of another terminal device transmitting data according to an embodiment of the present application.
  • FIG. 12 is a schematic diagram of a process of releasing a PDCP entity by a terminal device according to an embodiment of the present application.
  • FIG. 13 is a schematic diagram of a process of establishing a PDCP entity by a terminal device according to an embodiment of the present application.
  • FIG. 14 is a schematic block diagram of a terminal device according to an embodiment of the present application.
  • FIG. 15 is a schematic block diagram of a network device provided by an embodiment of the present application.
  • FIG. 16 is a schematic block diagram of yet another network device provided by an embodiment of the present application.
  • FIG. 17 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 18 is a schematic structural diagram of a device provided by an embodiment of the present application.
  • FIG. 19 is a schematic block diagram of a communication system provided by an embodiment of the present application.
  • Fig. 1 is a schematic diagram of a system 100 according to an embodiment of the present application.
  • the terminal device 110 is connected to the first network device 130 under the first communication system and the second network device 120 under the second communication system.
  • the first network device 130 is a Long Term Evolution (Long Term Evolution).
  • the second network device 120 is a network device under a New Radio (NR).
  • NR New Radio
  • the first network device 130 and the second network device 120 may include multiple cells.
  • FIG. 1 is an example of a communication system in an embodiment of the present application, and the embodiment of the present application is not limited to that shown in FIG. 1.
  • the communication system to which the embodiment of the present application is adapted may include at least multiple network devices under the first communication system and/or multiple network devices under the second communication system.
  • the system 100 shown in FIG. 1 may include one main network device under the first communication system and at least one auxiliary network device under the second communication system. At least one auxiliary network device is respectively connected to the one main network device to form multiple connections, and is connected to the terminal device 110 to provide services for it. Specifically, the terminal device 110 may simultaneously establish a connection through the main network device and the auxiliary network device.
  • connection established between the terminal device 110 and the main network device is the main connection
  • connection established between the terminal device 110 and the auxiliary network device is the auxiliary connection.
  • the control signaling of the terminal device 110 may be transmitted through the main connection
  • the data of the terminal device 110 may be transmitted through the main connection and the auxiliary connection at the same time, or may be transmitted only through the auxiliary connection.
  • first communication system and the second communication system in the embodiment of the present application are different, but the specific types of the first communication system and the second communication system are not limited.
  • the first communication system and the second communication system may be various communication systems, such as: Global System of Mobile Communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Time Division Duplex (TDD) ), Universal Mobile Telecommunication System (UMTS), etc.
  • GSM Global System of Mobile Communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • TDD Time Division Duplex
  • UMTS Universal Mobile Telecommunication System
  • the main network device and the auxiliary network device may be any access network device.
  • the access network device may be a base station (Base Transceiver) in the Global System of Mobile Communications (GSM) system or Code Division Multiple Access (CDMA). Station, BTS), it can also be a base station (NodeB, NB) in a Wideband Code Division Multiple Access (WCDMA) system, or an evolved base station in a Long Term Evolution (LTE) system (Evolutional Node B, eNB or eNodeB).
  • GSM Global System of Mobile Communications
  • CDMA Code Division Multiple Access
  • Station, BTS can also be a base station (NodeB, NB) in a Wideband Code Division Multiple Access (WCDMA) system, or an evolved base station in a Long Term Evolution (LTE) system (Evolutional Node B, eNB or eNodeB).
  • GSM Global System of Mobile Communications
  • CDMA Code Division Multiple Access
  • Station, BTS can also be a base station (NodeB, NB) in a Wideband Code Division Multiple Access (WCDMA) system,
  • the access network device may also be a Next Generation Radio Access Network (NG RAN), or a base station (gNB) in an NR system, or a cloud radio access network (Cloud
  • NG RAN Next Generation Radio Access Network
  • gNB base station
  • Cloud Cloud
  • the radio controller in Radio Access Network, CRAN, or the access network device can be a relay station, access point, in-vehicle device, wearable device, or in the future evolution of Public Land Mobile Network (PLMN) Network equipment, etc.
  • PLMN Public Land Mobile Network
  • the first network device 130 is taken as the main network device, and the second network device 120 is taken as an auxiliary network device as an example.
  • the first network device 130 may be an LTE network device, and the second network device 120 may be an NR network device. Or, the first network device 130 may be an NR network device, and the second network device 120 may be an LTE network device. Or both the first network device 130 and the second network device 120 may be NR network devices. Or the first network device 130 may be a GSM network device, a CDMA network device, etc., and the second network device 120 may also be a GSM network device, a CDMA network device, etc. Or the first network device 130 may be a Macrocell, and the second network device 120 may be a Microcell, Picocell, Femtocell, or the like.
  • the terminal device 110 may be any terminal device, and the terminal device 110 includes but is not limited to:
  • wired lines such as via Public Switched Telephone Networks (PSTN), Digital Subscriber Line (DSL), digital cable, direct cable connection; and/or another data connection/network; and/ Or via a wireless interface, such as for cellular networks, wireless local area networks (WLAN), digital TV networks such as DVB-H networks, satellite networks, AM-FM broadcast transmitters; and/or another terminal device
  • PSTN Public Switched Telephone Networks
  • DSL Digital Subscriber Line
  • WLAN wireless local area networks
  • digital TV networks such as DVB-H networks, satellite networks, AM-FM broadcast transmitters
  • IoT Internet of Things
  • a terminal device set to communicate through a wireless interface may be referred to as a "wireless communication terminal", a "wireless terminal” or a "mobile terminal”.
  • Examples of mobile terminals include, but are not limited to, satellites or cellular phones; Personal Communications System (PCS) terminals that can combine cellular radio phones with data processing, fax, and data communication capabilities; can include radio phones, pagers, Internet/intranet PDA with internet access, web browser, memo pad, calendar, and/or Global Positioning System (GPS) receiver; and conventional laptop and/or palmtop receivers or others including radio phone transceivers Electronic device.
  • Terminal equipment can refer to access terminals, user equipment (UE), user units, user stations, mobile stations, mobile stations, remote stations, remote terminals, mobile equipment, user terminals, terminals, wireless communication equipment, user agents, or User device.
  • the access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital processing (Personal Digital Assistant, PDA), with wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in 5G networks, or terminal devices in the future evolution of PLMN, etc.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • the network equipment provides services for the cell, and the terminal equipment communicates with the network equipment through the transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell.
  • the cell may be a network equipment (for example, The cell corresponding to the base station.
  • the cell can belong to a macro base station or a base station corresponding to a small cell.
  • the small cell here can include: Metro cell, Micro cell, Pico Cells, Femto cells, etc. These small cells have the characteristics of small coverage and low transmit power, and are suitable for providing high-rate data transmission services.
  • eMBB which targets users to obtain multimedia content, services and data, and its demand is growing very rapidly.
  • eMBB may be deployed in different scenarios, such as indoors, urban areas, and rural areas, the differences in capabilities and requirements are relatively large. Therefore, detailed analysis can be combined with specific deployment scenarios.
  • URLLC Typical applications of URLLC include: industrial automation, power automation, telemedicine operations (surgery), traffic safety protection, etc.
  • Typical features of mMTC include: high connection density, small data volume, delay-insensitive services, low-cost modules and long service life.
  • the terminal device needs to initiate random access to the network device to establish a connection with the network device.
  • There are many events that trigger a terminal device to perform random access such as in the initial access process of the terminal device; in the reconstruction process of the terminal device; when the terminal device has uplink data to send, but the uplink out of synchronization is detected ;
  • SR scheduling request
  • the random access of the terminal device may include contention-based random access and non-contention-based random access.
  • the terminal device sends a message 1 (message1, MSG1) to the network device on the random access channel, where the MSG1 contains a random access preamble.
  • MSG1 may be a physical layer message.
  • the network device may send MSG2 on a downlink shared channel (DL-SCH), where MSG2 may be a random access response (Random Access Response, RAR).
  • MSG2 may be a media access control (Media Access Control, MAC) layer message.
  • DL-SCH downlink shared channel
  • RAR Random Access Response
  • MAC media access control
  • the RAR response carries the timing advance (TA) adjustment of uplink transmission and the available uplink resource information, as well as the temporary cell radio network temporary identifier (T-CRNTI), that is, the temporary cell radio network temporary identifier (T-CRNTI). CRNTI.
  • TA timing advance
  • T-CRNTI temporary cell radio network temporary identifier
  • T-CRNTI temporary cell radio network temporary identifier
  • the RAR response may be generated by the media access control (Media Access Control, MAC) layer of the network device.
  • Media Access Control Media Access Control
  • One MSG2 can simultaneously respond to random access requests from multiple terminal devices.
  • the terminal device determines whether it belongs to its own RAR message, and when it determines that it belongs to its own RAR message, it sends message 3 (message3, MSG3) in the uplink resource designated by MSG2, and this MSG3 carries the terminal device.
  • message 3 messages3, MSG3
  • MSG3 may be an RRC layer message.
  • the network device may send an MSG4 message to the terminal device.
  • the MSG4 includes contention resolution messages and uplink transmission resources allocated by the network equipment to the terminal equipment.
  • the MSG4 may be a MAC layer message.
  • the terminal device After receiving the MSG4, the terminal device can detect whether the specific RNTI sent in the MSG3 is included in the contention resolution message sent by the network device. If it is included, it indicates that the random access procedure of the terminal device is successful; otherwise, it is considered that the random procedure fails. After the random access process fails, the terminal device needs to initiate the random access process again from the first step.
  • MSG1 and MSG2 may not use the HARQ mechanism, while MSG3 and MSG4 may use the HARQ mechanism.
  • the terminal device can also initiate the next random machine access attempt until the maximum number of retransmissions and/or maximum retransmission time allowed by the network side is reached.
  • the terminal device generally performs random access by sending a preamble to the network device. If the terminal device sends the preamble for the first time, if the current random access fails, the terminal device can send the random access preamble to the network device for the second time, and the transmission power of the second preamble can be the first The transmit power of a preamble after a power rise.
  • the step length of the power increase may be configured by the network device, or may also be pre-configured in the terminal device.
  • the non-contention-based random access process may be as shown in FIG. 3, for example.
  • the network device sends MSG0 to the terminal device.
  • the MSG0 may include a preamble configuration message, which is used to indicate a preamble for random access.
  • the MSG0 may be a physical layer message.
  • the terminal device sends MSG 1 to the network device, where the MSG1 includes the random access preamble in S310.
  • the MSG1 may be a physical layer message.
  • the network device sends MSG2 to the terminal device, where the MSG2 may be a random access response message.
  • the MSG2 may be a MAC layer message.
  • the terminal device can obtain non-competitive random access resources through RRC signaling and/or PDCCH signaling, and perform random access on the non-competitive random access resources.
  • the following takes the handover process as an example to describe the random access process of the terminal device.
  • the embodiment of the present application does not specifically limit the communication scenario of the handover process.
  • it may be an LTE system or an NR system.
  • the communication system needs to transfer the communication link between the terminal equipment and the source cell to the target cell, that is, perform the cell handover process.
  • the source cell can be understood as the cell to which the terminal device is currently connected
  • the target cell can be understood as the cell to which the terminal device is about to switch.
  • the embodiment of the present application does not specifically limit the manner in which the terminal device performs cell handover.
  • the terminal device may perform intra-site handover, that is, the source cell and the target cell belong to the same base station.
  • the terminal device may also perform handover between the base station and the base station, that is, the source cell and the target cell belong to different base stations.
  • the embodiment of the present application does not limit the interface used for cell handover between the base station and the base station.
  • it can be cell handover based on X2 interface or Xn interface, or it can be cell handover based on S1 interface or N2 interface.
  • the handover process of the terminal device can be divided into the following three stages: handover preparation, handover execution and handover completion.
  • the handover preparation may include the terminal device measuring and reporting the link quality, sending a handover request to the source base station, and receiving a handover command sent by the source base station.
  • the handover execution may include that the terminal device immediately executes the handover process after receiving the handover command sent by the source base station.
  • the connection with the source cell can be disconnected and the connection with the target cell can be completed (such as performing random access, sending an RRC handover complete message to the target base station, etc.), serial number (SN) state transfer and data forwarding, etc.
  • SN serial number
  • the completion of the handover may include the target cell and the access and mobility management function (AMF) and the user plane function (UPF) performing link handover, releasing the UE context of the source base station, and so on.
  • AMF access and mobility management function
  • UPF user plane function
  • link switching and releasing the UE context of the source base station can be performed by AMF and UPF.
  • link switching and releasing the UE context of the source base station can be performed by the MME.
  • the embodiments of the present application do not specifically limit the applied system, and may be applied to an LTE system or an NR system.
  • the handover preparation phase (401-405) may include:
  • the source base station triggers the terminal device to measure the neighboring cell, so that the terminal device can measure the neighboring cell and report the measurement result to the source base station.
  • the source base station evaluates the measurement result reported by the terminal device and decides whether to trigger a handover.
  • the source base station decides to trigger a handover, it can send a handover request to the target base station.
  • the target base station may start admission according to the service information carried by the source base station, and perform radio resource configuration.
  • the target base station sends a handover request confirmation message to the source base station, and returns the admission result and wireless resource configuration information in the target base station to the source base station. At this point, the handover preparation phase is complete.
  • the handover execution stage (406-408) may include:
  • the source base station after the source base station receives the handover request confirmation message of the target base station, it can trigger the terminal device to perform handover.
  • the source base station can forward the buffered data, the data packet in transit, the system serial number of the data, etc. to the target base station. And, the target base station can buffer the data received from the source base station
  • the terminal device can disconnect from the source base station and establish synchronization with the target base station.
  • the terminal device synchronizes to the target base station. At this point, the switching execution phase is complete.
  • the third stage, the handover completion stage (409-412) can include:
  • the target base station sends a path switching request to a mobility management function (Access and Mobility Management Function, AMF).
  • AMF Access and Mobility Management Function
  • the AMF after receiving the path switching request of the target base station, the AMF performs path switching with the User Plane Function (UPF) to clear the path mark of the user plane of the source base station.
  • UPF User Plane Function
  • the AMF may send a path switching confirmation message to the target base station.
  • the target base station sends a terminal device context release message to the source base station to notify the source base station that the handover is successful, and trigger the source base station to release the terminal device context. At this point, the switch is complete.
  • the terminal device immediately starts the T304 timer after receiving the handover command, and starts downlink synchronization to the target cell, obtains the master indication block (MIB) information of the target cell, and then initiates random access. During the random access process, multiple preamble retransmissions are allowed until the random access is successful. Further, if the T304 timer expires, indicating that the handover fails, the terminal device can directly trigger the RRC connection re-establishment process.
  • MIB master indication block
  • the terminal device After receiving the handover command, the terminal device will first disconnect the connection with the source base station, and then establish the connection with the target base station. Since the terminal device disconnects the source base station and communicates with the target base station, there will be a time difference. I can call this time difference the handover interruption time.
  • the handover interruption time can be understood as the end time of the communication between the terminal device and the source base station, and the time difference between the start time of the communication between the terminal device and the target base station, or it can also be understood as the time difference between the terminal device and the source base station.
  • the corresponding packet data convergence protocol (PDCP) will be rebuilt for all bearers.
  • Rebuilding the PDCP may refer to rebuilding on the basis of the PDCP entity used to communicate with the source base station to generate the PDCP entity used to communicate with the target base station. Since the terminal device rebuilds the PDCP of the target base station based on the PDCP of the source base station, the terminal device rebuilds the PDCP, which means that the terminal device has released the PDCP of the source base station, and the terminal device cannot continue to communicate with the source base station.
  • an optimization method for reducing the interruption time during handover is proposed, which includes the following two architectures, and the solutions in the embodiments of the present application can be used for both architectures.
  • the target base station is first added as a secondary node (secondary node, SN), and then the target base station is changed from SN to a master node (master node, MN) through role change signaling. Finally, the source base station is released, so as to reduce the handover interruption time.
  • secondary node secondary node
  • MN master node
  • the handover method can be based on the existing handover process. After receiving the handover command, the terminal device continues to maintain the connection with the source base station, and at the same time initiates random access to the target base station, which can also achieve the effect of reducing the terminal handover time .
  • the terminal device will not immediately disconnect from the source base station after receiving the handover command.
  • the terminal device will not be able to establish the PDCP of the target base station in the traditional way of rebuilding PDCP. Therefore, how to establish the PDCP of the target base station is a problem to be solved continuously.
  • the embodiment of the present application provides a method for cell handover, which can solve the problem of establishing the PDCP of the target base station without disconnecting the terminal device from the source base station.
  • the method includes steps S510 to S520. This method can be executed by the terminal device described above.
  • the time when the second PDCP entity is released is no earlier than the time when the first PDCP entity is established.
  • Fig. 6 is another method for cell handover provided by an embodiment of the present application.
  • the method may be executed by the base station of the source cell.
  • the method includes step S610.
  • FIG. 7 is another method for cell handover provided by an embodiment of the present application.
  • the method may be executed by a target cell base station.
  • the method includes step S710.
  • the time of the PDCP entity, the second PDCP entity is used for communication between the terminal device and the source cell base station.
  • FIG. 5, FIG. 6 and FIG. 7 correspond. To simplify the description, the methods in FIG. 5, FIG. 6 and FIG. 7 will be described together below. The following method is also applicable to terminal equipment, source cell base station and target cell base station.
  • the source cell base station and the target cell base station may be the network equipment described above.
  • the source cell base station may refer to the base station to which the source cell belongs, and the source cell may refer to the serving cell where the terminal device is located before the handover.
  • the target cell base station may refer to the base station to which the target cell belongs, and the target cell may refer to the serving cell where the terminal device is located after handover.
  • the target cell is different from the source cell, but the target cell base station can be the same as the source cell base station or different.
  • the base station of the target cell and the base station of the source cell being the same may mean that the terminal device switches between different cells in the same base station.
  • the difference between the base station of the target cell and the base station of the source cell may mean that the terminal device switches between different cells in different base stations.
  • the first PDCP entity refers to the PDCP entity used to carry data between the terminal device and the target cell base station
  • the second PDCP entity refers to the PDCP entity used to carry data between the terminal device and the source cell base station.
  • the PDCP entity established by the target cell base station is also referred to as the first PDCP entity.
  • the first PDCP entity belongs to the target cell base station side
  • the first PDCP entity established by the terminal device belongs to the terminal device side.
  • Two first PDCP entities The entities are used for communication between terminal equipment and the base station of the target cell.
  • the first PDCP entity established by the base station of the target cell and the PDCP entity established by the terminal device may be different entities, but the manner of establishing PDCP between the two may be the same.
  • the manner in which the terminal device establishes a PDCP entity described below is also applicable to the target cell base station.
  • the PDCP entity released by the source cell base station is also referred to as the second PDCP entity.
  • the second PDCP entity belongs to the source cell base station side
  • the second PDCP entity released by the terminal device belongs to the terminal device side. Both of the second PDCP entities are used for communication between the terminal device and the base station of the source cell.
  • the manner and time for releasing the second PDCP by the source cell base station may be the same as the manner and time for releasing the second PDCP entity by the terminal device.
  • the terminal device establishing the first PDCP entity and/or releasing the second PDCP entity may be executed after the terminal device receives the handover command sent by the source cell base station.
  • the release of the second PDCP entity by the source cell base station may be performed after the source cell base station sends a handover command to the terminal device.
  • the establishment of the first PDCP entity by the target cell base station may be performed after the target cell base station sends a handover request confirmation message to the source cell base station.
  • the establishment of the first PDCP entity may refer to the establishment of parameters required on the PDCP for the terminal device to communicate with the target cell base station.
  • Releasing the second PDCP entity may refer to releasing the parameters of the second PDCP entity for the terminal device to communicate with the base station of the source cell. After the terminal device releases the second PDCP entity, the terminal device cannot continue to communicate with the source cell base station. After the source cell base station releases the second PDCP entity, the source cell base station cannot continue to communicate with the terminal device.
  • the time when the second PDCP entity is released is no earlier than the time when the first PDCP entity is established may include that the time when the second PDCP entity is released is equal to the time when the first PDCP entity is established, or the time when the second PDCP entity is released is later than the time when the first PDCP entity is established.
  • the time of releasing the second PDCP entity is no earlier than the time of establishing the second PDCP entity, which means that the establishment of the PDCP entity will not affect the handover interruption time, which is beneficial to reduce the handover interruption time of the terminal device.
  • the time for establishing the first PDCP entity may refer to the time when the PDCP entity is started to be established, or may refer to the time when the establishment of the first PDCP entity is completed.
  • the first PDCP entity and the second PDCP entity may be two different PDCP entities, or the first PDCP entity and the second PDCP entity belong to the same PDCP entity.
  • the first PDCP entity and the second PDCP entity belong to the same PDCP entity, which may mean that the first PDCP entity is generated by modifying part of the configuration on the basis of the second PDCP entity, or the first PDCP entity is adding part of the configuration on the second PDCP entity owned.
  • the process of establishing and/or releasing the PDCP entity in the embodiment of the present application will be described in detail in the following two situations.
  • the manner in which the base station of the target cell establishes the first PDCP entity corresponds to the manner in which the terminal device establishes the first PDCP entity.
  • the terminal device is used as an example for description below.
  • the first PDCP entity is different from the second PDCP entity.
  • the terminal device may establish a first PDCP entity different from the second PDCP entity. That is, the first PDCP entity and the second PDCP entity may exist at the same time, and the terminal device may communicate with the source cell base station and the target cell base station at the same time.
  • the data between the terminal device and the network device can be transmitted between the physical layer, the MAC layer, the Radio Link Control (RLC) layer, and the PDCP layer.
  • PDCP1 is used for the communication between the terminal equipment and the base station of the target cell
  • PDCP2 is used for the communication between the terminal equipment and the base station of the source cell.
  • the terminal equipment can maintain PDCP1 and PDCP2 at the same time, so that the terminal equipment establishes PDCP1 without releasing PDCP2 as the premise ,
  • the release time of PDCP2 can be made later than the establishment time of PDCP1, which can reduce the handover interruption time of the terminal device.
  • the embodiment of the present application does not specifically limit the manner of generating the first PDCP entity.
  • the first PDCP entity may be generated according to the configuration information of the first PDCP entity sent by the base station of the source cell.
  • the source cell base station may send a first message to the terminal device, and the first message may include configuration information of the first PDCP entity.
  • the terminal device may establish the first PDCP entity according to the configuration information of the first PDCP entity included in the first message.
  • the configuration information of the first PDCP entity may include all information required to establish the first PDCP entity.
  • it may include a PDCP context, a security key used for encryption and decryption, a robust header compression (ROHC) configuration used for header compression and decompression, and other parameters.
  • the RoHC configuration can be understood as a RoHC profile.
  • the other parameters may include at least one of the following parameters: buffer size, discard Timer, header compression related profile and configuration, maximum Cell identity (CID), PDCP duplication configuration (Duplication), PDCP SN size configuration, status feedback configuration, PDCP control protocol data unit (protocol data unit, PDU) type, PDU cycle status type, reorder timing Device (t-Reordering), integrity protection indication (rn-Integrity Protection) and status report indication (status Report Required).
  • CID Cell identity
  • Duplication PDCP duplication configuration
  • PDCP SN size configuration status feedback configuration
  • PDU control protocol data unit
  • PDU cycle status type PDU cycle status type
  • t-Reordering reorder timing Device
  • integrity protection indication rn-Integrity Protection
  • status report indication status report indication
  • the first PDCP entity may be established according to related parameters in the second PDCP entity.
  • the PDCP context in the first PDCP entity may be the same as the PDCP context in the second PDCP entity, and the terminal device may use the PDCP context in the second PDCP entity as the PDCP context of the first PDCP entity.
  • the PDCP context can also be referred to as variable parameters in PDCP.
  • the PDCP context may include at least one of the following information: uplink PDCP sequence number, uplink superframe number, downlink PDCP sequence number and downlink superframe number.
  • the terminal device uses the PDCP context in the second PDCP entity as the PDCP context of the first PDCP entity, which may be directly agreed in the protocol, or may be indicated by the source cell base station to the terminal device.
  • the source cell base station may inform the terminal device Send first indication information, where the first indication information is used to indicate that the PDCP context in the first PDCP entity is determined according to the PDCP context in the second PDCP entity.
  • the configuration information of the first PDCP entity sent by the source cell base station to the terminal device may not include the PDCP context.
  • the terminal device may obtain the PDCP context from the second PDCP entity, and The first PDCP entity is established according to the acquired PDCP context and the configuration information of the first PDCP entity.
  • the first message may be a radio resource control (Radio Resource Control, RRC) reconfiguration message or a handover command.
  • RRC Radio Resource Control
  • the first message may include a handover request message.
  • the configuration information of the first PDCP entity may be configured in the handover command.
  • the configuration information of the first PDCP entity may be configured in the handover request message.
  • the terminal device can directly trigger the RRC connection re-establishment process.
  • the source cell base station sends the RRC connection reconfiguration message to the terminal device, it can carry the configuration information of the first PDCP entity in the RRC connection reconfiguration message and send it to the terminal device together.
  • the security keys in the first PDCP entity and the second PDCP entity are different, and/or the RoHC configurations in the first PDCP entity and the second PDCP entity are different. That is to say, the encryption method used for communication between the terminal equipment and the target cell base station is different from the encryption method used for communication between the terminal equipment and the source cell base station; the communication method used between the terminal equipment and the target cell base station The header compression method is different from the header compression method used for communication between the terminal equipment and the base station of the source cell.
  • the terminal device uses two different PDCP entities to communicate with the source cell base station and the target cell base station respectively, so that the establishment of the first PDCP entity will not cause the release of the second PDCP entity, which can ensure that the terminal device continues
  • a PDCP entity corresponding to the base station of the target cell is established.
  • the release time of the first PDCP entity may be later than the time when the establishment of the second PDCP entity is completed, which is beneficial to realize the terminal device handover time of 0 ms and achieve the effect of seamless handover.
  • the embodiment of this application does not specifically limit the time point when the terminal device releases the second PDCP entity.
  • the second PDCP entity may be directly released when the terminal device releases the source cell base station. That is, the terminal device may release the source cell base station. Released at the same time as the second PDCP entity.
  • the embodiment of the present application does not specifically limit the time for the terminal device to establish the first PDCP entity, and it may be any time point after the terminal device receives the handover command.
  • the time point when the terminal device establishes the first PDCP entity can be any one of the following time points: the terminal device receives the second message sent by the source cell base station, the terminal device receives the message in the random access process, and the terminal device sends random Messages and specific timers in the access process expire.
  • the embodiment of the present application does not specifically limit the time point when the target cell base station establishes the first PDCP entity. For example, it may be after the target cell base station sends a message in the random access process. For another example, it may be after the target cell base station receives the message in the random access process.
  • the terminal device receiving the second message sent by the source cell base station may mean that the terminal device receives any message sent by the source cell base station.
  • the second message may be a handover command, or the second message may be an RRC reconfiguration message.
  • the terminal device may establish the first PDCP entity after receiving the second message.
  • the terminal device receiving the message in the random access process may mean that the terminal device has received MSG2 and/or MSG4.
  • the terminal device may establish a first PDCP entity.
  • the target cell base station may establish the first PDCP entity after sending MSG2 and/or MSG4.
  • the terminal device sending a message in the random access process may refer to the terminal device sending MSG1 and/or MSG3.
  • the terminal device may establish the first PDCP entity.
  • the target cell base station may establish the first PDCP entity after receiving MSG1 and/or MSG3.
  • the random access process can be a contention-based random access process or a non-competition-based random access process; the random access process can refer to a four-step random access process or a two-step random access process
  • the embodiments of this application do not specifically limit this.
  • the terminal device receives the message in the random access process, or sends the message in the random access process, indicating that the terminal device has communicated with the target cell. At this time, the handover interruption time of 0ms can be guaranteed, and then the first The PDCP entity will not affect the handover interruption time of the terminal device.
  • a specific timer may refer to a timer that the terminal equipment starts after receiving any message sent by the source cell base station.
  • the specific timer may be started after the terminal equipment receives a handover command sent by the source cell base station.
  • Timer The embodiment of the present application does not specifically limit the duration of the timer.
  • a specific timer may refer to a timer that is started after the target cell base station receives any message sent by the source cell base station and/or terminal equipment.
  • the specific timer may be the target cell base station receiving the source cell base station. The timer started after the handover request message is sent.
  • the terminal device may retransmit data and/or send a status report to the target cell base station through the first PDCP entity after establishing the first PDCP entity and/or releasing the second PDCP entity. For example, during the handover process of the terminal device, data may not be received correctly. In this case, the terminal device may retransmit through the first PDCP entity after the first PDCP entity establishes and/or releases the second PDCP entity. Data received correctly. Retransmitting data through the first PDCP entity may refer to retransmitting data to the target cell base station through the first PDCP entity.
  • the terminal device can also send a status report to the target cell base station, and the status report can include the data reception status, such as which data is received correctly and which data is not received correctly.
  • the target cell base station may receive the retransmission data and/or status report sent by the terminal device through the first PDCP entity.
  • the terminal device may maintain a connection with the base station of the source cell. Then, after the establishment of the first PDCP entity is completed, the connection with the base station of the source cell is released, which helps to reduce the handover interruption time of the terminal device.
  • the terminal device may also receive a handover command sent by the source cell base station, where the handover command is used to instruct the terminal device to switch to the target cell base station.
  • Case 2 The first PDCP entity is the same as the second PDCP entity. In this case, there is only one PDCP entity at the same time.
  • the first PDCP entity may include the second PDCP, that is, the first PDCP entity may retain the parameters in the second PDCP entity. In this way, since the parameters in the second PDCP entity are all reserved, the first PDCP entity can communicate with the target cell base station or the source cell base station.
  • the first PDCP entity may be obtained by adding the first parameter on the basis of the second PDCP entity.
  • the first parameter may be used for communication between the terminal device and the target cell base station, and the first parameter may include, for example, a security key and/or RoHC configuration.
  • the terminal device may add a security key and/or RoHC configuration on the basis of the parameters included in the second PDCP entity, so as to communicate with the target cell base station.
  • the target cell base station may also add a security key and/or RoHC configuration on the basis of the parameters included in the second PDCP entity, so as to communicate with the terminal device.
  • the terminal device before the cell handover, can communicate with the target cell base station through PDCP2. After receiving the handover command, the terminal device can add the first parameter on the basis of PDCP2 to form PDCP1. Since PDCP1 still retains the configuration of PDCP2, such as the second parameter, PDCP1 can be used for communication between the terminal device and the base station of the source cell. In addition, since the first parameter used to communicate with the target cell base station is added to PDCP1, PDCP1 can also be used to communicate with the target cell base station.
  • the second parameter may be used for communication between the terminal device and the base station of the source cell, the second parameter may include a security key and/or RoHc configuration, and the second parameter is different from the first parameter.
  • the security key included in the first parameter is different from the security key included in the second parameter
  • the RoHC configuration included in the first parameter is different from the RoHC configuration included in the second parameter.
  • two sets of keys and RoHC profiles are maintained, which are respectively used for data transmission with the source cell base station and the target cell base station.
  • the first parameter includes the first key and the first RoHC profile
  • the second parameter includes the second key and the second RoHC profile
  • the target cell base station when the target cell base station sends data to the terminal equipment, it can use the first key to encrypt the data, and use the first RoHC profile for header compression; the source cell base station When sending data to the terminal device, the second key can be used to encrypt the data, and the second RoHC profile can be used for header compression.
  • the terminal device receives the data, it can first determine which base station sends the data.
  • the first key is used to decrypt the data, and the first RoHC profile is used to decompress the header; if it is the source cell base station For the sent data, the second key is used to decrypt the data, and the second RoHC profile is used to decompress the header.
  • the terminal device when the terminal device sends data to the base station, if it sends data to the target cell base station, the terminal device can use the first key to encrypt the data, and the first RoHC profile for header compression ; If the data is sent to the source cell base station, the second key is used to encrypt the data, and the second RoHC profile is used for header compression.
  • the target cell base station After the target cell base station receives the data sent by the terminal device, it can use the first key to decrypt the data and use the first RoHC profile to decompress the header; after the source cell base station receives the data sent by the terminal device, it can use the second key to decrypt the data Data, using the second RoHC profile for header decompression.
  • the terminal device releasing the second PDCP entity may refer to the terminal device releasing the second parameter in the second PDCP entity. As shown in FIG. 12, the terminal device releases the second parameter included in PDCP1. Specifically, the terminal device may delete the security key and/or RoHC configuration used for data transmission with the source cell base station.
  • PDCP1 contains two sets of security keys and RoHC configuration, which can simultaneously transmit data with the source cell base station and the target cell base station.
  • the terminal device deletes the security key and RoHC configuration corresponding to the source cell base station, it means that the terminal device releases the source cell base station. At this time, the terminal device can only transmit data with the target cell base station.
  • the embodiment of the present application does not specifically limit the time for the terminal device to establish the first PDCP entity, and it may be any time point after the terminal device receives the handover command.
  • the time point when the terminal device establishes the first PDCP entity can be any one of the following time points: the terminal device receives the second message sent by the source cell base station, the terminal device receives the message in the random access process, and the terminal device sends random Messages and specific timers in the access process expire. To simplify the description, it will not be repeated here.
  • the terminal device may retransmit data and/or send a status report through the first PDCP entity after adding the first parameter and/or releasing the second parameter. To simplify the description, it will not be repeated here.
  • the terminal device can maintain the connection with the base station of the source cell.
  • the terminal device can use the traditional way of rebuilding PDCP.
  • the PDCP entity corresponding to the target cell base station is established, but the time for the terminal device to rebuild PDCP can be after sending MSG1 to the target cell base station.
  • the terminal device reestablishes the PDCP entity, the terminal device has communicated with the base station of the target cell, indicating that the handover interruption time of the terminal device is no longer affected by the PDCP reestablishment, which is beneficial to guarantee the handover interruption time of the terminal device.
  • the base station of the target cell may also generate the first PDCP entity in a reconstruction manner after receiving the MSG1 sent by the terminal device.
  • the terminal device may retain the PDCP context in the second PDCP entity, and only update the security key and RoHC configuration, thereby obtaining the second PDCP entity.
  • the PDCP re-establishment by the terminal device may be established when the random access of the target cell base station is successful.
  • Establishing the first PDCP entity by the terminal device may include: in a case where the random access of the target cell is successful, generating the first PDCP entity through reconstruction based on the second PDCP entity.
  • the terminal device After receiving the handover command, the terminal device will initiate follow-on access to the target cell base station. In the case of successful random access, the terminal device can generate the first PDCP entity through reconstruction.
  • the embodiment of the present application does not specifically limit the random access mode of the terminal device.
  • the terminal device can adopt four-step random access, or two-step random access.
  • the terminal device may adopt a contention-based random access method, or a non-contention-based random access method.
  • the terminal device may generate the first PDCP entity based on the second PDCP entity.
  • the third message may include a random access response message and/or a contention resolution message.
  • the random access response message may refer to a random access response message based on a non-competitive random access process. After the terminal device receives the random access response message, it indicates that the terminal device has successfully accessed randomly. Establish a connection between.
  • the successful random access of the terminal device may also mean that the terminal device successfully sends an RRC reconfiguration complete message.
  • the terminal device after successfully sending the RRC reconfiguration complete message, the terminal device can generate the first PDCP entity through reconstruction.
  • the contention resolution message may refer to MSG4 in a contention-based random access process, and the MSG4 indicates that the terminal device successfully competes. After the terminal device receives the contention resolution message, it indicates that the terminal device has succeeded in random access, and a connection is established between the terminal device and the base station of the target cell.
  • the terminal device may maintain the connection with the source cell base station during the random access process with the target cell base station.
  • the first PDCP entity is generated on the basis of the second PDCP entity, when the terminal device starts to establish the first PDCP entity, it indicates that the second PDCP entity has been released. In this case, the time for the terminal device to release the second PDCP entity is equal to the time for the terminal device to establish the first PDCP entity.
  • the terminal device generates the first PDCP entity when the base station of the target cell is successfully accessed randomly. It can mean that the first PDCP entity is generated as long as the base station of the target cell succeeds in the access, or it can be used after the base station of the target cell succeeds in the access. After a period of time, the first PDCP entity is generated.
  • the target base station and the target cell base station in the embodiments of the present application have the same meaning, and both indicate the base station where the target cell is located.
  • the source base station and the source cell base station have the same meaning, and both indicate the base station where the source cell is located. Both the target base station and the source base station can reach the network equipment described above.
  • the wireless communication method according to the embodiment of the present application is described in detail above.
  • the device according to the embodiment of the present application will be described below in conjunction with FIG. 14 to FIG. 19.
  • the technical features described in the method embodiment are applicable to the following device embodiments.
  • FIG. 14 is a schematic block diagram of a terminal device according to an embodiment of the present application.
  • the terminal device may be any of the terminal devices described above.
  • the terminal device 1400 in FIG. 14 includes a processing unit 1410, wherein:
  • the processing unit 1410 is configured to establish a first packet data convergence protocol PDCP entity, where the first PDCP entity is used for communication between the terminal device and the target cell base station.
  • the processing unit 1410 is further configured to release a second PDCP entity, where the second PDCP entity is used for communication between the terminal device and the source cell base station, wherein the time for releasing the second PDCP entity is no earlier than the establishment of the second PDCP entity. State the time of the first PDCP entity.
  • the first PDCP entity is different from the second PDCP entity.
  • the terminal device further includes a communication unit 1420, configured to receive a first message sent by the source cell base station, where the first message includes configuration information of the first PDCP entity; the processing unit 1410 Used to: establish the first PDCP entity according to the configuration information of the first PDCP entity.
  • a communication unit 1420 configured to receive a first message sent by the source cell base station, where the first message includes configuration information of the first PDCP entity; the processing unit 1410 Used to: establish the first PDCP entity according to the configuration information of the first PDCP entity.
  • the first message includes a radio resource control RRC reconfiguration message and/or a handover command.
  • the context in the first PDCP entity is determined according to the context in the second PDCP entity.
  • the terminal equipment further includes a communication unit 1420, configured to receive first indication information sent by the source cell base station, where the first indication information is used to indicate that the PDCP context in the first PDCP entity is based on The PDCP context in the second PDCP entity is determined.
  • a communication unit 1420 configured to receive first indication information sent by the source cell base station, where the first indication information is used to indicate that the PDCP context in the first PDCP entity is based on The PDCP context in the second PDCP entity is determined.
  • the PDCP context includes at least one of the following information: an uplink PDCP sequence number, an uplink superframe number, a downlink PDCP sequence number, and a downlink superframe number.
  • the security keys in the first PDCP entity and the second PDCP entity are different, and/or the reliable header compression ROHC configurations in the first PDCP entity and the second PDCP entity are different.
  • the first PDCP entity includes parameters in the second PDCP entity, and the first PDCP entity is also used for communication between the terminal device and the source cell base station.
  • the first PDCP entity is obtained by adding a first parameter to the second PDCP entity, and the first parameter is used for communication between the terminal device and the target cell base station
  • the processing unit 1410 is configured to release a second parameter in the second PDCP entity, where the second parameter is used for communication between the terminal device and the source cell base station, wherein the second parameter is released
  • the time of the parameter is not earlier than the time of adding the first parameter, and the first parameter is different from the second parameter.
  • both the first parameter and the second parameter include a security key and/or a reliable header compression ROHC configuration.
  • the time point for establishing the first PDCP entity includes at least one of the following: receiving a second message sent by the source cell base station, receiving a message in the random access process, and sending random access Messages in the process and specific timers expire.
  • the second message includes a handover command.
  • the specific timer is a timer that is started after the terminal device receives a handover command sent by the source cell base station.
  • the processing unit 1410 is further configured to: maintain a connection with the source cell base station during the process of establishing the first PDCP entity.
  • the processing unit 1410 is configured to generate the first PDCP entity based on the second PDCP entity when the random access of the target cell base station is successful.
  • the terminal device further includes a communication unit 1420, configured to receive a third message sent by the source cell base station, where the third message includes at least one of the following messages: random access response RAR message and contention Resolve the message.
  • a communication unit 1420 configured to receive a third message sent by the source cell base station, where the third message includes at least one of the following messages: random access response RAR message and contention Resolve the message.
  • processing unit 1410 is further configured to: maintain a connection with the source cell base station during the random access process with the target cell base station.
  • the terminal device further includes a communication unit 1420, configured to retransmit data and/or send a status report through the first PDCP entity after the first PDCP entity is established or the second PDCP entity is released.
  • a communication unit 1420 configured to retransmit data and/or send a status report through the first PDCP entity after the first PDCP entity is established or the second PDCP entity is released.
  • the terminal device further includes a communication unit 1420, configured to receive a handover command sent by the source cell base station, where the handover command is used to instruct the terminal device to switch to the target cell base station.
  • a communication unit 1420 configured to receive a handover command sent by the source cell base station, where the handover command is used to instruct the terminal device to switch to the target cell base station.
  • FIG. 15 is a schematic block diagram of a network device according to an embodiment of the present application.
  • the network device may be any source cell base station described above.
  • the network device 1500 in FIG. 15 includes a processing unit 1510, wherein:
  • the processing unit 1510 is configured to release a second PDCP entity, where the second PDCP entity is used for the communication between the source cell base station and the terminal device, wherein the release time of the second PDCP entity is no earlier than the establishment of the terminal device The time of the first PDCP entity, which is used for communication between the terminal device and the target cell base station.
  • the first PDCP entity is different from the second PDCP entity.
  • the network device further includes a communication unit 1520, configured to send a first message to the terminal device, where the first message includes configuration information of the first PDCP entity, The configuration information is used by the terminal device to establish the first PDCP entity.
  • a communication unit 1520 configured to send a first message to the terminal device, where the first message includes configuration information of the first PDCP entity, The configuration information is used by the terminal device to establish the first PDCP entity.
  • the first message includes a radio resource control RRC reconfiguration message and/or a handover command.
  • the context in the first PDCP entity is determined according to the context in the second PDCP entity.
  • the network device further includes a communication unit 1520, configured to send first indication information to the terminal device, where the first indication information is used to indicate that the PDCP context in the first PDCP entity is based on the The PDCP context in the second PDCP entity is determined.
  • a communication unit 1520 configured to send first indication information to the terminal device, where the first indication information is used to indicate that the PDCP context in the first PDCP entity is based on the The PDCP context in the second PDCP entity is determined.
  • the PDCP context includes at least one of the following information: an uplink PDCP sequence number, an uplink superframe number, a downlink PDCP sequence number, and a downlink superframe number.
  • the security keys in the first PDCP entity and the second PDCP entity are different, and/or the reliable header compression RoHC configurations in the first PDCP entity and the second PDCP entity are different.
  • the first PDCP entity includes parameters in the second PDCP entity, and the first PDCP entity is also used for communication between the source cell base station and the terminal device.
  • the first PDCP entity is obtained by the terminal device by adding a first parameter on the basis of the second PDCP entity, and the first parameter is used between the terminal device and the target cell base station.
  • the processing unit 1510 is configured to release the second parameter in the second PDCP entity, and the second parameter is used for the communication between the terminal device and the source cell base station, wherein the release The time of the second parameter is not earlier than the time when the terminal device adds the first parameter, and the first parameter is different from the second parameter.
  • both the first parameter and the second parameter include a security key and/or RoHC configuration.
  • the processing unit 1510 is further configured to: maintain a connection with the terminal device when the terminal device establishes the first PDCP entity.
  • the processing unit 1510 is configured to release the second PDCP entity when the random access of the target cell base station is successful.
  • the processing unit 1510 is further configured to: maintain a connection with the terminal device when the terminal device performs random access to the base station of the target cell.
  • the network device further includes a communication unit 1520, configured to send a handover command to the terminal device, where the handover command is used to instruct the terminal device to switch to the target cell base station.
  • a communication unit 1520 configured to send a handover command to the terminal device, where the handover command is used to instruct the terminal device to switch to the target cell base station.
  • FIG. 16 is a schematic block diagram of a network device according to an embodiment of the present application.
  • the network device may be any of the target cell base stations described above.
  • the network device 1600 in FIG. 16 includes a processing unit 1610, wherein:
  • the processing unit 1610 is configured to establish a first packet data convergence protocol PDCP entity, where the first PDCP entity is used for communication between the target cell base station and the terminal device, wherein the time of establishing the first PDCP entity is no later than the terminal The time when the device releases the second PDCP entity, which is used for communication between the terminal device and the source cell base station.
  • the first PDCP entity is different from the second PDCP entity.
  • the network device further includes a communication unit 1620, configured to: receive a first message sent by the source cell base station, where the first message includes configuration information of the first PDCP entity; the processing unit 1610 is configured to: establish the first PDCP entity according to the configuration information of the first PDCP entity.
  • a communication unit 1620 configured to: receive a first message sent by the source cell base station, where the first message includes configuration information of the first PDCP entity; the processing unit 1610 is configured to: establish the first PDCP entity according to the configuration information of the first PDCP entity.
  • the first message includes a handover request message.
  • the context in the first PDCP entity is determined according to the context in the second PDCP entity.
  • the network device further includes a communication unit 1620, configured to receive first indication information sent by the source cell base station, where the first indication information is used to indicate that the PDCP context in the first PDCP entity is based on The PDCP context in the second PDCP entity is determined.
  • a communication unit 1620 configured to receive first indication information sent by the source cell base station, where the first indication information is used to indicate that the PDCP context in the first PDCP entity is based on The PDCP context in the second PDCP entity is determined.
  • the PDCP context includes at least one of the following information: an uplink PDCP sequence number, an uplink superframe number, a downlink PDCP sequence number, and a downlink superframe number.
  • the security keys in the first PDCP entity and the second PDCP entity are different, and/or the reliable header compression ROHC configurations in the first PDCP entity and the second PDCP entity are different.
  • the first PDCP entity includes parameters in the second PDCP entity.
  • the parameters in the second PDCP entity include second parameters, and the second parameters are used for communication between the terminal device and the source cell base station, and the first PDCP entity is in the It is obtained by adding a first parameter on the basis of the second PDCP entity, and the first parameter is used for communication between the target cell base station and the terminal device, and the time for adding the first parameter is no later than that of the terminal The time when the device releases the second parameter, where the first parameter is different from the second parameter.
  • both the first parameter and the second parameter include a security key and/or a reliable header compression ROHC configuration.
  • the time point for establishing the first PDCP entity includes at least one of the following: sending a second message to the source cell base station, receiving a message in the random access process, and sending a message in the random access process The message and the specific timer expired.
  • the second message includes a handover request confirmation message.
  • the specific timer is a timer that is started after the target cell base station sends a handover request confirmation message to the source cell base station.
  • the processing unit 1610 is configured to generate the first PDCP entity based on the second PDCP entity when the random access of the terminal device is successful.
  • the network device before the generating the first PDCP entity based on the second PDCP entity, the network device further includes a communication unit configured to send a third message to the terminal device, the third message It includes at least one of the following messages: a random access response RAR message and a contention resolution message.
  • FIG. 17 is a schematic structural diagram of a communication device 1700 according to an embodiment of the present application.
  • the communication device 1700 shown in FIG. 17 includes a processor 1710, and the processor 1710 can call and run a computer program from a memory to implement the method in the embodiment of the present application.
  • the communication device 1700 may further include a memory 1720.
  • the processor 1710 may call and run a computer program from the memory 1720 to implement the method in the embodiment of the present application.
  • the memory 1720 may be a separate device independent of the processor 1710, or may be integrated in the processor 1710.
  • the communication device 1700 may further include a transceiver 1730, and the processor 1710 may control the transceiver 1730 to communicate with other devices. Specifically, it may send information or data to other devices, or receive other devices. Information or data sent by the device.
  • the transceiver 1730 may include a transmitter and a receiver.
  • the transceiver 1730 may further include an antenna, and the number of antennas may be one or more.
  • the communication device 1700 may specifically be a network device of an embodiment of the application, and the communication device 1700 may implement the corresponding process implemented by the network device in each method of the embodiment of the application. For brevity, details are not repeated here. .
  • the communication device 1700 may specifically be a mobile terminal/terminal device of an embodiment of the application, and the communication device 1700 may implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the application, for the sake of brevity , I won’t repeat it here.
  • Fig. 18 is a schematic structural diagram of a device according to an embodiment of the present application.
  • the apparatus 1800 shown in FIG. 18 includes a processor 1810, and the processor 1810 can call and run a computer program from the memory to implement the method in the embodiment of the present application.
  • the apparatus 1800 may further include a memory 1820.
  • the processor 1810 can call and run a computer program from the memory 1820 to implement the method in the embodiment of the present application.
  • the memory 1820 may be a separate device independent of the processor 1810, or may be integrated in the processor 1810.
  • the device 1800 may further include an input interface 1830.
  • the processor 1810 can control the input interface 1830 to communicate with other devices or chips. Specifically, it can obtain information or data sent by other devices or chips.
  • the device 1800 may further include an output interface 1840.
  • the processor 1810 can control the output interface 1840 to communicate with other devices or chips, specifically, can output information or data to other devices or chips.
  • the device can be applied to the network equipment in the embodiments of the present application, and the device can implement the corresponding processes implemented by the network equipment in the various methods of the embodiments of the present application.
  • the device can implement the corresponding processes implemented by the network equipment in the various methods of the embodiments of the present application.
  • details are not described herein again.
  • the device can be applied to the mobile terminal/terminal device in the embodiment of this application, and the device can implement the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of this application.
  • the device can implement the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of this application.
  • the device can implement the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of this application.
  • the device mentioned in the embodiments of the present application may be a chip, and the chip may also be referred to as a system-level chip, a system-on-chip, a system-on-chip, or a system-on-chip.
  • FIG. 19 is a schematic block diagram of a communication system 1900 according to an embodiment of the present application. As shown in FIG. 19, the communication system 1900 includes a terminal device 1910 and a network device 1920.
  • the terminal device 1910 can be used to implement the corresponding function implemented by the terminal device in the above method
  • the network device 1920 can be used to implement the corresponding function implemented by the network device in the above method. For brevity, it will not be repeated here. .
  • the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capability.
  • the steps of the foregoing method embodiments may be completed by hardware integrated logic circuits in the processor or instructions in the form of software.
  • the aforementioned processor may be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (ASIC), a ready-made programmable gate array (Field Programmable Gate Array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP Digital Signal Processor
  • ASIC application specific integrated circuit
  • FPGA ready-made programmable gate array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), and electrically available Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be random access memory (Random Access Memory, RAM), which is used as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM DDR SDRAM
  • ESDRAM enhanced synchronous dynamic random access memory
  • Synchlink DRAM SLDRAM
  • DR RAM Direct Rambus RAM
  • the memory in the embodiment of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc.
  • static random access memory static random access memory
  • SRAM static random access memory
  • dynamic RAM dynamic random access memory
  • Synchronous dynamic random access memory synchronous DRAM, SDRAM
  • double data rate SDRAM double data rate SDRAM, DDR SDRAM
  • enhanced synchronous dynamic random access memory enhanced synchronous dynamic random access memory
  • ESDRAM enhanced synchronous dynamic random access memory
  • synchronous connection Dynamic random access memory switch link DRAM, SLDRAM
  • Direct Rambus RAM Direct Rambus RAM
  • the embodiment of the present application also provides a computer-readable storage medium for storing computer programs.
  • the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application ,
  • the computer program enables the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application ,
  • I will not repeat it here.
  • the embodiments of the present application also provide a computer program product, including computer program instructions.
  • the computer program product may be applied to the network device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program product can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, For brevity, I won't repeat them here.
  • the embodiment of the present application also provides a computer program.
  • the computer program can be applied to the network device in the embodiment of the present application.
  • the computer program runs on the computer, the computer is caused to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • I won’t repeat it here.
  • the computer program can be applied to the mobile terminal/terminal device in the embodiment of the present application.
  • the computer program runs on the computer, the computer executes each method in the embodiment of the present application. For the sake of brevity, the corresponding process will not be repeated here.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • each unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of this application essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the method described in each embodiment of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory,) ROM, random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code .

Landscapes

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

Abstract

本申请提供了一种用于小区切换的方法及设备，提供了一种终端设备在切换过程中建立PDCP实体的方法。建立第一分组数据汇聚协议PDCP实体，所述第一PDCP实体用于终端设备与目标小区基站之间的通信；释放第二PDCP实体，所述第二PDCP实体用于所述终端设备与源小区基站之间的通信，其中，释放所述第二PDCP实体的时间不早于建立所述第一PDCP实体的时间。

Description

用于小区切换的方法及设备 技术领域
本申请实施例涉及通信领域，并且更具体地，涉及一种用于小区切换的方法及设备。
背景技术
新无线(New Radio，NR)系统支持小区切换，例如，当终端设备从一个小区移动到另一个小区，或由于无线通信业务负荷量调整、激活操作维护、设备故障等原因，为了保证通信的连续性和服务的质量，需要将该终端设备与源基站的通信链路转移到目标基站上，即执行切换过程。
终端设备在从源基站切换到目标基站的过程中，对于所有的承载都会建立其对应的分组数据汇聚协议(packet data convergence protocol，PDCP)，终端设备如何建立PDCP成为亟需解决的问题。
发明内容
本申请提供一种用于小区切换的方法及设备，提供了一种终端设备在切换过程中建立PDCP实体的方法。
第一方面，提供了一种用于小区切换的方法，包括：建立第一分组数据汇聚协议PDCP实体，所述第一PDCP实体用于终端设备与目标小区基站之间的通信；释放第二PDCP实体，所述第二PDCP实体用于所述终端设备与源小区基站之间的通信，其中，释放所述第二PDCP实体的时间不早于建立所述第一PDCP实体的时间。
第二方面，提供了一种用于小区切换的方法，包括：释放第二PDCP实体，所述第二PDCP实体用于源小区基站与终端设备之间的通信，其中，释放所述第二PDCP实体的时间不早于所述终端设备建立第一PDCP实体的时间，所述第一PDCP实体用于所述终端设备与目标小区基站之间的通信。
第三方面，提供了一种用于小区切换的方法，包括：建立第一分组数据汇聚协议PDCP实体，所述第一PDCP实体用于目标小区基站与终端设备之间的通信，其中，建立第一PDCP实体的时间不晚于所述终端设备释放第二PDCP实体的时间，所述第二PDCP实体用于所述终端设备与源小区基站之间的通信。
第四方面，提供了一种终端设备，用于执行上述第一方面或其各实现方式中的方法。
具体地，该终端设备包括用于执行上述第一方面或其各实现方式中的方法的功能模块。
第五方面，提供了一种网络设备，用于执行上述第二方面或其各实现方式中的方法。
具体地，该网络设备包括用于执行上述第二方面或其各实现方式中的方法的功能模块。
第六方面，提供了一种网络设备，用于执行上述第三方面或其各实现方式中的方法。
具体地，该网络设备包括用于执行上述第三方面或其各实现方式中的方法的功能模块。
第七方面，提供了一种终端设备，包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述第一方面或其各实现方式中的方法。
第八方面，提供了一种网络设备，包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述第二方面或其各实现方式中的方法。
第九方面，提供了一种网络设备，包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述第三方面或其各实现方式中的方法。
第十方面，提供了一种装置，用于实现上述第一方面至第三方面中的任一方面或其各实现方式中的方法。
具体地，该装置包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有该装置的设备执行如上述第一方面至第三方面中的任一方面或其各实现方式中的方法。
第十一方面，提供了一种计算机可读存储介质，用于存储计算机程序，该计算机程序使得计算机执行上述第一方面至第三方面中的任一方面或其各实现方式中的方法。
第十二方面，提供了一种计算机程序产品，包括计算机程序指令，所述计算机程序指令使得计算机执行上述第一方面至第三方面中的任一方面或其各实现方式中的方法。
第十三方面，提供了一种计算机程序，当其在计算机上运行时，使得计算机执行上述第一方面至第三方面中的任一方面或其各实现方式中的方法。
通过上述技术方案，使得终端设备进行小区切换的过程中，能够实现目标PDCP实体的建立，并且也能够使得终端设备PDCP的建立满足0ms的切换中断时间。
附图说明
图1是本申请实施例应用的无线通信系统的示意图。
图2是本申请实施例提供的一种基于竞争的随机接入过程的示意图。
图3是本申请实施例提供的一种基于非竞争的随机接入过程的示意图。
图4是本申请实施例提供的一种小区切换的方法的示意图。
图5是本申请实施例提供的一种用于小区切换的方法的示意性流程图。
图6是本申请实施例提供的另一种用于小区切换的方法的示意性流程图。
图7是本申请实施例提供的另一种用于小区切换的方法的示意性流程图。
图8是本申请实施例提供的一种终端设备建立的PDCP实体的示意图。
图9是本申请实施例提供的一种终端设备建立PDCP实体的过程的示意图。
图10是本申请实施例提供的一种终端设备传输数据的示意图。
图11是本申请实施例提供的又一种终端设备传输数据的示意图。
图12是本申请实施例提供的一种终端设备释放PDCP实体的过程的示意图。
图13是本申请实施例提供的一种终端设备建立PDCP实体的过程的示意图。
图14是本申请实施例提供的一种终端设备的示意性框图。
图15是本申请实施例提供的一种网络设备的示意性框图。
图16是本申请实施例提供的又一种网络设备的示意性框图。
图17是本申请实施例提供的一种通信设备的示意性结构图。
图18是本申请实施例提供的一种装置的示意性结构图。
图19是本申请实施例提供的一种通信系统的示意性框图。
具体实施方式
图1是本申请实施例的系统100的示意图。
如图1所示，终端设备110与第一通信系统下的第一网络设备130和第二通信系统下的第二网络设备120相连，例如，该第一网络设备130为长期演进(Long Term Evolution，LTE)下的网络设备，该第二网络设备120为新空口(New Radio,NR)下的网络设备。
其中，该第一网络设备130和该第二网络设备120下可以包括多个小区。
应理解，图1是本申请实施例的通信系统的示例，本申请实施例不限于图1所示。
作为一个示例，本申请实施例适应的通信系统可以包括至少该第一通信系统下的多个网络设备和/或该第二通信系统下的多个网络设备。
例如，图1所示的系统100可以包括第一通信系统下的一个主网络设备和第二通信系统下的至少一个辅助网络设备。至少一个辅助网络设备分别与该一个主网络设备相连，构成多连接，并分别与终端设备110连接为其提供服务。具体地，终端设备110可以通过主网络设备和辅助网络设备同时建立连接。
可选地，终端设备110和主网络设备建立的连接为主连接，终端设备110与辅助网络设备建立的连接为辅连接。终端设备110的控制信令可以通过主连接进行传输，而终端设备110的数据可以通过主连接以及辅连接同时进行传输，也可以只通过辅连接进行传输。
作为又一示例，本申请实施例中的第一通信系统和第二通信系统不同，但对第一通信系统和该第二通信系统的具体类别不作限定。
例如，该第一通信系统和该第二通信系统可以是各种通信系统，例如：全球移动通讯(Global System of Mobile communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、LTE时分双工(Time Division Duplex，TDD)、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)等。
所述主网络设备和所述辅助网络设备可以为任意接入网设备。
可选地，在一些实施例中，所述接入网设备可以是全球移动通讯(Global System of Mobile communication，GSM)系统或码分多址(Code Division Multiple Access，CDMA)中的基站(Base Transceiver Station，BTS)，也可以是宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统中的基站(NodeB，NB)，还可以是长期演进(Long Term Evolution，LTE)系统中的演进型基站(Evolutional Node B，eNB或eNodeB)。
可选地，所述接入网设备还可以是下一代无线接入网(Next Generation Radio Access Network，NG RAN)，或者是NR系统中的基站(gNB)，或者是云无线接入网络(Cloud Radio Access Network，CRAN)中的无线控制器，或者该接入网设备可以为中继站、接入点、车载设备、可穿戴设备，或者未 来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)中的网络设备等。
在图1所示的系统100中，以该第一网络设备130为主网络设备，以该第二网络设备120为辅助网络设备为例。
该第一网络设备130可以为LTE网络设备，该第二网络设备120可以为NR网络设备。或者该第一网络设备130可以为NR网络设备，第二网络设备120可以为LTE网络设备。或者该第一网络设备130和该第二网络设备120都可以为NR网络设备。或者该第一网络设备130可以为GSM网络设备，CDMA网络设备等，该第二网络设备120也可以为GSM网络设备，CDMA网络设备等。或者第一网络设备130可以是宏基站(Macrocell)，第二网络设备120可以为微蜂窝基站(Microcell)、微微蜂窝基站(Picocell)或者毫微微蜂窝基站(Femtocell)等。
可选地，所述终端设备110可以是任意终端设备，所述终端设备110包括但不限于：
经由有线线路连接，如经由公共交换电话网络(Public Switched Telephone Networks，PSTN)、数字用户线路(Digital Subscriber Line，DSL)、数字电缆、直接电缆连接；和/或另一数据连接/网络；和/或经由无线接口，如，针对蜂窝网络、无线局域网(Wireless Local Area Network，WLAN)、诸如DVB-H网络的数字电视网络、卫星网络、AM-FM广播发送器；和/或另一终端设备的被设置成接收/发送通信信号的装置；和/或物联网(Internet of Things，IoT)设备。被设置成通过无线接口通信的终端设备可以被称为“无线通信终端”、“无线终端”或“移动终端”。移动终端的示例包括但不限于卫星或蜂窝电话；可以组合蜂窝无线电电话与数据处理、传真以及数据通信能力的个人通信系统(Personal Communications System，PCS)终端；可以包括无线电电话、寻呼机、因特网/内联网接入、Web浏览器、记事簿、日历以及/或全球定位系统(Global Positioning System，GPS)接收器的PDA；以及常规膝上型和/或掌上型接收器或包括无线电电话收发器的其它电子装置。终端设备可以指接入终端、用户设备(User Equipment，UE)、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、5G网络中的终端设备或者未来演进的PLMN中的终端设备等。
应理解，本文中术语“系统”和“网络”在本文中常被可互换使用。
在本申请实施例中，网络设备为小区提供服务，终端设备通过该小区使用的传输资源(例如，频域资源，或者说，频谱资源)与网络设备进行通信，该小区可以是网络设备(例如基站)对应的小区，小区可以属于宏基站，也可以属于小小区(Small cell)对应的基站，这里的小小区可以包括：城市小区(Metro cell)、微小区(Micro cell)、微微小区(Pico cell)、毫微微小区(Femto cell)等，这些小小区具有覆盖范围小、发射功率低的特点，适用于提供高速率的数据传输服务。
应理解，本申请实施例的方法可以用于传输各种类型的业务。
例如eMBB，eMBB以用户获得多媒体内容、服务和数据为目标，其需求增长十分迅速。又例如eMBB，由于eMBB可能部署在不同的场景中，便如室内，市区，农村等，其能力和需求的差别也比较大，因此可以结合具体的部署场景详细分析。又例如URLLC，URLLC的典型应用包括：工业自动化，电力自动化，远程医疗操作(手术)，交通安全保障等。mMTC的典型特点包括：高连接密度，小数据量，时延不敏感业务，模块的低成本和长使用寿命等。
终端设备在一些特殊的场景下，需要向网络设备发起随机接入，以建立与网络设备之间的连接。触发终端设备进行随机接入的事件有多种，例如在终端设备的初始接入过程中；在终端设备的重建过程中；在终端设备有上行数据需要发送，但检测到上行失步的情况下；终端设备有上行数据需要发送，但没有调度请求(scheduling request，SR)资源的情况下；在终端设备需要进行小区切换的情况下；在基站有下行数据需要发送，但检测到上行失步的情况下。
终端设备的随机接入可以包括基于竞争的随机接入和基于非竞争的随机接入。
基于竞争的随机接入过程可以参照图2所示。
S210、终端设备在随机接入信道向网络设备发送消息1(message1，MSG1)，该MSG1中包含随机接入前导码。其中，该MSG1可以是物理层消息。
S220、网络设备收到MSG1之后，可以在下行共享信道(downlink share channel，DL-SCH)发送MSG2，其中，MSG2可以为随机接入响应(Random Access Response，RAR)。其中，该MSG2可以为媒体接入控制(Media Access Control，MAC)层消息。
其中，RAR响应中携带了上行传输的时间提前量(timeing advance，TA)调整和可以使用的上行资源信息以及临时小区无线网络临时标识(temporary cell radio network temporary identifier，T-CRNTI)， 也即临时CRNTI。
可选地，RAR响应可以由网络设备的媒体接入控制(Media Access Control，MAC)层产生。一条MSG2可以同时对应多个终端设备的随机接入请求响应。
S230中，终端设备在接收到MSG2后，判断是否属于自己的RAR消息，在判断为属于自己的RAR消息时，在MSG2指定的上行资源中发送消息3(message3，MSG3)，该MSG3携带终端设备特定的RNTI。其中，该MSG3可以为RRC层消息。
在步骤240中，网络设备在接收到MSG3之后，可以向终端设备发送MSG4消息。其中，该MSG4中包括竞争解决消息以及网络设备为终端设备分配的上行传输资源。其中，该MSG4可以为MAC层消息。
终端设备接收到MSG4后，可以检测在MSG3发送的特定的RNTI是否包含在网络设备发送的竞争解决消息中。若包含，则表明终端设备随机接入过程成功，否则认为随机过程失败。随机接入过程失败后，终端设备需要再次从第一步开始发起随机接入过程。
可选地，MSG1和MSG2可以不使用HARQ机制，而MSG3和MSG4可以使用HARQ机制。
一次随机接入尝试失败，终端设备还可以发起下一次随机机接入尝试，直至达到网络侧允许的最大重传次数和/或最大重传时间。
终端设备一般是通过向网络设备发送前导码来进行随机接入的。如果终端设备在第一次发送前导码后，如果当前的随机接入失败，则终端设备可以向网络设备第二次发送随机接入的前导码，该第二次前导码的发送功率可以是第一次前导码的发送功率经过功率攀升之后的发送功率。该功率攀升的步长可以是网络设备配置的，或者也可以是预配置在终端设备中的。
基于非竞争的随机接入过程例如可以如图3所示。
S310、网络设备向终端设备发送MSG0，该MSG0可以包括前导码配置消息，用于指示随机接入的前导码。该MSG0可以为物理层消息。
S320、终端设备向网络设备发送MSG 1，该MSG1包括S310中的随机接入前导码。该MSG1可以为物理层消息。
S330、网络设备向终端设备发送MSG2，该MSG2可以为随机接入响应消息。该MSG2可以为MAC层消息。
在基于非竞争的随机接入过程中，终端设备可以通过RRC信令和/或PDCCH信令来获取非竞争随机接入的资源，并在该非竞争随机接入资源上进行随机接入。
下面以切换过程为例，对终端设备的随机接入过程进行描述。本申请实施例对切换过程的通信场景不做具体限定，例如可以为LTE系统，也可以为NR系统。
当正在使用网络服务的终端设备从源小区移动到目标小区的覆盖范围内，或者由于无线传输业务负荷量调整、激活操作维护、设备故障等原因，为了保证终端设备通信的连续性和服务的质量，通信系统需要将终端设备与源小区的通信链路转移到目标小区上，即执行小区切换过程。源小区可以理解为终端设备当前所连接的小区，目标小区可以理解为终端设备即将要切换的小区。
本申请实施例对终端设备进行小区切换的方式不做具体限定，例如终端设备可以进行站内切换，也就是说，源小区与目标小区同属于一个基站。又例如，终端设备也可以进行基站与基站之间的切换，也就是说，源小区与目标小区属于不同的基站。
本申请实施例对进行基站与基站之间的小区切换所采用的接口不做限定。例如可以是基于X2接口或Xn接口的小区切换，或者也可以是基于S1接口或N2接口的小区切换。
以Xn接口为例，终端设备的切换过程可以分为以下三个阶段：切换准备、切换执行和切换完成。
切换准备可以包括终端设备对链路质量进行测量上报、向源基站发送切换请求，以及接收源基站发送的切换命令。
切换执行可以包括终端设备在接收到源基站发送的切换命令后，立即执行切换过程。例如，可以断开与源小区的连接并完成与目标小区的连接(如执行随机接入，发送RRC切换完成消息给目标基站等)，序列号(serial number，SN)状态转移和数据转发等。
切换完成可以包括目标小区与接入与移动性管理功能(access and mobility management function，AMF)和用户面功能(user plane function，UPF)执行链路切换，释放源基站的UE上下文等。
对于NR系统来说，链路切换和释放源基站的UE上下文可以是由AMF和UPF执行的，对于LTE系统来说，链路切换和释放源基站的UE上下文可以是由MME来执行的。本申请实施例对应用的系统不做具体限定，可以应用于LTE系统，也可以应用于NR系统。
具体地，如图4所示，切换准备阶段(401～405)可以包括：
在401中，源基站触发终端设备进行邻区测量，从而终端设备可以对邻区进行测量，并将测量结果 上报给源基站。
在402中，源基站对终端设备上报的测量结果进行评估，决定是否触发切换。
在403中，若源基站决定触发切换，则可以向目标基站发送切换请求。
在404中，目标基站接收到源基站发送的切换请求后，可以根据源基站携带的业务信息开始准入，并进行无线资源配置。
在405中，目标基站向源基站发送切换请求确认消息，将在目标基站内的准入结果和无线资源配置信息返回给源基站。至此，切换准备阶段完成。
第二阶段，切换执行阶段(406～408)可以包括：
在406中，源基站接收到目标基站的切换请求确认消息后，可以触发终端设备进行切换。
在407中，源基站可以将缓冲数据、在传数据包、数据的系统序列号等转发给目标基站。并且，目标基站可以缓存从源基站接收的数据
此外，终端设备可以断开与源基站的连接，与目标基站建立同步。
在408中，终端设备同步到目标基站。至此，切换执行阶段完成。
第三阶段，切换完成阶段(409～412)可以包括：
在409中，目标基站向移动性管理功能(Access and Mobility Management Function，AMF)发送路径切换请求。
在410中，AMF接收到目标基站的路径切换请求后，与用户面功能(User Plane Function，UPF)执行路径切换，清除源基站用户面的路径标记。
在411中，在路径切换完成之后，AMF可以向目标基站发送路径切换确认消息。
在412中，目标基站向源基站发送终端设备上下文释放消息，通知源基站切换成功，并触发源基站释放终端设备上下文。至此，切换完成。
终端设备在收到切换命令后立即启动T304定时器，并开始下行同步到目标小区，获取目标小区主信息块(master indication block，MIB)信息，然后发起随机接入。随机接入过程中允许多次preamble重传直至随机接入成功。进一步地，如果T304定时器超时，说明切换失败，则所述终端设备可以直接触发RRC连接重建过程。
在传统的切换过程中，终端设备在接收到切换命令后，会先断开与源基站之间的连接，然后再建立与目标基站之间的连接。由于终端设备在断开源基站，到与目标基站之间进行通信，会存在时间差，我可以将该时间差称为切换中断时间。
切换中断时间可以理解为终端设备与源基站之间通信的结束时间，以及终端设备与目标基站之间通信的开始时间之间的时间差，或者，也可以理解为终端设备与源基站之间发送的最后一条消息的时间，以及终端设备与目标基站之间发送的第一条消息的时间之间的时间差。
终端设备在切换过程中，对于所有的承载都会重建其对应的分组数据汇聚协议(packet data convergence protocol，PDCP)。重建PDCP可以指在用于与源基站进行通信的PDCP实体的基础上进行重建，生成用于与目标基站进行通信的PDCP实体。由于终端设备重建目标基站的PDCP是在源基站的PDCP的基础上生成的，因此，终端设备重建PDCP，就表示终端设备已经释放了源基站的PDCP，终端设备将无法继续与源基站进行通信。
在3GPP移动性增强课题中，提出了对于切换时减小中断时间的优化方法，包括以下两种架构，本申请实施例的方案对于这两种架构都可以使用。
1、基于双连接的切换，或称为基于分离承载(split bearer)的切换。在切换时，先把目标基站添加为辅节点(secondary node，SN)，然后通过role change信令将目标基站从SN变为主节点(master node，MN)。最后再把源基站释放掉，从而能够达到减小切换中断时间的效果。
2、基于eMBB的切换，或称为基于非分离承载(non-split bearer)的切换。该切换方式可以基于现有的切换流程，终端设备在接收到切换命令后，继续保持与源基站之间的连接，同时向目标基站发起随机接入，这样也能达到减小切换终端时间的效果。
在这两种架构下，终端设备在接收到切换命令后，并不会立即断开与源基站之间的连接。在终端设备不断开与源基站的连接的情况，终端设备将不能采用传统的重建PDCP的方式来建立目标基站的PDCP，因此，如何建立目标基站的PDCP称为继续解决的问题。
本申请实施例提供一种用于小区切换的方法，能够解决终端设备在不断开与源基站连接的情况下，建立目标基站的PDCP的问题。如图5所示，该方法包括步骤S510～S520。该方法可以由上文描述的终端设备来执行。
S510、建立第一PDCP实体，该第一PDCP实体用于终端设备与目标小区基站之间的通信。
S520、释放第二PDCP实体，该第二PDCP实体用于终端设备与源小区基站之间的通信。
其中，释放第二PDCP实体的时间不早于建立第一PDCP实体的时间。
图6是本申请实施例提供的另一种用于小区切换的方法，该方法可以由源小区基站执行，该方法包括步骤S610。
S610、释放第二PDCP实体，所述第二PDCP实体用于源小区基站与终端设备之间的通信，其中，释放所述第二PDCP实体的时间不早于所述终端设备建立第一PDCP实体的时间，所述第一PDCP实体用于所述终端设备与目标小区基站之间的通信。
图7是本申请实施例提供的又一种用于小区切换的方法，该方法可以由目标小区基站执行，该方法包括步骤S710。
S710、建立第一分组数据汇聚协议PDCP实体，所述第一PDCP实体用于目标小区基站与终端设备之间的通信，其中，建立第一PDCP实体的时间不晚于所述终端设备释放第二PDCP实体的时间，所述第二PDCP实体用于所述终端设备与源小区基站之间的通信。
图5、图6和图7的方法对应，为简化描述，下文将对图5、图6和图7的方法一起进行描述。下文的方法同样适用于终端设备、源小区基站和目标小区基站。
源小区基站和目标小区基站可以是上文描述的网络设备。
源小区基站可以指源小区所属的基站，源小区可以指终端设备在切换之前所在的服务小区。目标小区基站可以指目标小区所属的基站，目标小区可以指终端设备在切换之后所在的服务小区。目标小区与源小区不同，但目标小区基站可以与源小区基站相同，也可以不同。
目标小区基站与源小区基站相同可以指终端设备在同一个基站内的不同小区之间进行切换。目标小区基站与源小区基站不同可以指终端设备在不同基站内的不同小区之间进行切换。
第一PDCP实体指的用于承载终端设备与目标小区基站之间的数据的PDCP实体，第二PDCP实体指的是用于承载终端设备与源小区基站之间的数据的PDCP实体。
本文中将目标小区基站建立的PDCP实体也称为第一PDCP实体，第一PDCP实体是属于目标小区基站侧的，终端设备建立的第一PDCP实体是属于终端设备侧的，两个第一PDCP实体都是用于终端设备与目标小区基站之间的通信。但是目标小区基站建立的第一PDCP实体与终端设备建立的PDCP实体可以为不同的实体，但是两者建立PDCP的方式可以相同。下文描述的终端设备建立PDCP实体的方式同样适用于目标小区基站。
类似地，本文中将源小区基站释放的PDCP实体也称为第二PDCP实体，该第二PDCP实体是属于源小区基站侧的，终端设备释放的第二PDCP实体是属于终端设备侧的，两个第二PDCP实体都是用于终端设备与源小区基站之间的通信。但是源小区基站释放第二PDCP的方式和时间等可以与终端设备释放第二PDCP实体的方式和时间相同。
终端设备建立第一PDCP实体和/或释放第二PDCP实体可以是在终端设备接收到源小区基站发送的切换命令后执行的。
源小区基站释放第二PDCP实体可以是在源小区基站向终端设备发送切换命令后执行的。目标小区基站建立第一PDCP实体可以是在目标小区基站向源小区基站发送切换请求确认消息之后执行的。
建立第一PDCP实体可以指建立用于终端设备与目标小区基站进行通信的PDCP上需要的参数。
释放第二PDCP实体可以指释放第二PDCP实体中用于终端设备与源小区基站进行通信的参数。终端设备释放第二PDCP实体后，终端设备将不能继续与源小区基站进行通信。源小区基站释放第二PDCP实体后，源小区基站将不能继续与终端设备进行通信。
释放第二PDCP实体的时间不早于建立第一PDCP实体的时间可以包括，释放第二PDCP实体的时间等于建立第一PDCP实体的时间，也可以包括释放第二PDCP实体的时间晚于建立第一PDCP实体的时间。释放第二PDCP实体的时间不早于建立第二PDCP实体的时间，表示PDCP实体的建立将不会影响切换中断时间，这样有利于减小终端设备的切换中断时间。
建立第一PDCP实体的时间可以指开始建立PDCP实体的时间，也可以指第一PDCP实体建立完成的时间。
本申请实施例中，第一PDCP实体和第二PDCP实体可以是两个不同的PDCP实体，或者第一PDCP实体与第二PDCP实体属于同一个PDCP实体。第一PDCP实体与第二PDCP实体属于同一个PDCP实体可以指第一PDCP实体是在第二PDCP实体的基础上修改部分配置生成的，或者第一PDCP实体是在第二PDCP实体上增加部分配置得到的。
下面通过两种情况，对本申请实施例中的建立和/或释放PDCP实体的过程进行详细描述。目标小区基站建立第一PDCP实体的方式与终端设备建立第一PDCP实体的方式对应，为简化描述，下文以终端设备为例进行描述。
情况1，第一PDCP实体不同于第二PDCP实体。在该情况下，终端设备可以建立不同于第二PDCP 实体的第一PDCP实体。也就是说，第一PDCP实体和第二PDCP实体可以同时存在，终端设备可同时与源小区基站和目标小区基站进行通信。
如图8所示，终端设备与网络设备之间的数据可以在物理层、MAC层、无线链路控制(Radio Link Control，RLC)层和PDCP层之间传输。其中，PDCP1用于终端设备与目标小区基站之间的通信，PDCP2用于终端设备与源小区基站之间的通信，终端设备可以同时维护PDCP1和PDCP2，这样终端设备建立PDCP1不是以释放PDCP2为前提，可以使得PDCP2的释放时间晚于PDCP1的建立时间，能够减小终端设备的切换中断时间。
本申请实施例对生成第一PDCP实体的方式不做具体限定。
作为一个示例，第一PDCP实体可以是根据源小区基站发送的第一PDCP实体的配置信息生成的。例如，源小区基站可以向终端设备发送第一消息，该第一消息中可以包括第一PDCP实体的配置信息。终端设备在接收到第一消息后，可以根据第一消息中包括的第一PDCP实体的配置信息，建立第一PDCP实体。
第一PDCP实体的配置信息可以包括建立第一PDCP实体所需要的全部信息。例如可以包括PDCP上下文，用于加密和解密的安全密钥，用于头压缩和解压缩的可靠头压缩(robust header compression，ROHC)配置以及其他的参数。其中，RoHC配置可以理解为RoHC简档(profile)。
PDCP实体中包括的其他参数可以有多种，例如，该其他参数可以包括以下参数中的至少一种：缓存大小(buffer size)，丢弃定时器(discard Timer)，头压缩相关profile以及配置，最大的小区标识(cell identity，CID)，PDCP复制配置(Duplication)，PDCP的SN大小配置，状态反馈配置，PDCP控制协议数据单元(protocol data unit，PDU)的类型，PDU周期状态类型，重排序计时器(t-Reordering)，完整性保护指示(rn-Integrity Protection)和状态报告指示(status Report Required)。
作为另一个示例，第一PDCP实体可以是根据第二PDCP实体中的有关参数建立的。例如，第一PDCP实体中的PDCP上下文可以与第二PDCP实体中的PDCP上下文相同，终端设备可以将第二PDCP实体中的PDCP上下文作为第一PDCP实体的PDCP上下文。
PDCP上下文也可以称为PDCP中的变量参数。PDCP上下文可以包括以下信息中的至少一种：上行链路的PDCP序列号，上行链路的超帧号，下行链路的PDCP序列号和下行链路的超帧号。
终端设备将第二PDCP实体中的PDCP上下文作为第一PDCP实体的PDCP上下文，可以是协议中直接约定的，或者也可以是源小区基站向终端设备指示的，例如，源小区基站可以向终端设备发送第一指示信息，该第一指示信息用于指示第一PDCP实体中的PDCP上下文是根据第二PDCP实体中的PDCP上下文确定的。
当然，源小区基站向终端设备发送的第一PDCP实体的配置信息中可以不包括PDCP上下文，终端设备在接收到第一PDCP实体的配置信息后，可以从第二PDCP实体中获取PDCP上下文，并根据获取的PDCP上下文以及第一PDCP实体的配置信息，建立第一PDCP实体。
对于终端设备来说，第一消息可以是无线资源控制(radio resource control，RRC)重配置消息，也可以是切换命令。对于目标性小区基站来说，第一消息可以包括切换请求消息。
例如，源小区基站在向终端设备发送切换命令时，可以将第一PDCP实体的配置信息配置在切换命令中。又例如，源小区基站在向目标小区基站发送切换请求消息时，可以将第一PDCP实体的配置信息配置在切换请求消息。
又例如，在T304定时器超时后，表示终端设备切换失败，此时终端设备可以直接触发RRC连接重建过程。源小区基站在向终端设备发送RRC连接重配置消息时，可以将第一PDCP实体的配置信息携带在RRC连接重配置消息中，一同发送给终端设备。
本申请实施例中，第一PDCP实体和第二PDCP实体中的安全密钥不同，和/或第一PDCP实体和第二PDCP实体中的RoHC配置不同。也就是说，终端设备和目标小区基站之间进行通信所采用的加密方式，与终端设备和源小区基站之间进行通信所采用的加密方式不同；终端设备和目标小区基站之间进行通信所采用的头压缩方式，与终端设备和源小区基站之间进行通信所采用的头压缩方式不同。
本申请实施例中，终端设备采用两个不同的PDCP实体分别与源小区基站和目标小区基站进行通信，使得第一PDCP实体的建立不会导致第二PDCP实体的释放，能够保证在终端设备不断开与源小区基站之间的连接的情况下，建立目标小区基站对应的PDCP实体。在该情况下，第一PDCP实体的释放时间可以晚于第二PDCP实体建立完成的时间，这样有利于实现终端设备的0ms的切换终端时间，达到无缝切换的效果。
本申请实施例对终端设备释放第二PDCP实体的时间点不做具体限定，例如可以是在终端设备释放源小区基站的时候直接释放第二PDCP实体，也就是说，终端设备可以将源小区基站和第二PDCP实体同时释放掉。
本申请实施例对终端设备建立第一PDCP实体的时间不做具体限定，可以是终端设备在接收到切换命令后的任意时间点。例如终端设备建立第一PDCP实体的时间点可以是以下中的任意一个时间点：终端设备接收到源小区基站发送的第二消息，终端设备接收到随机接入过程中的消息，终端设备发送随机接入过程中的消息和特定定时器超时。
本申请实施例对目标小区基站建立第一PDCP实体的时间点不做具体限定，例如，可以是目标小区基站发送随机接入过程中的消息之后。又例如，可以是目标小区基站接收到随机接入过程中的消息之后。
终端设备接收到源小区基站发送的第二消息可以指终端设备接收到源小区基站发送的任意消息。例如该第二消息可以为切换命令，或者该第二消息可以为RRC重配置消息。终端设备可以在接收到第二消息后，建立第一PDCP实体。
终端设备接收到随机接入过程中的消息可以指终端设备接收到MSG2和/或MSG4。终端设备在接收到MSG2和/或MSG4的情况下，可以建立第一PDCP实体。对应地，目标小区基站可以在发送MSG2和/或MSG4后，建立第一PDCP实体。
终端设备发送随机接入过程中的消息可以指终端设备发送MSG1和/或MSG3。终端设备在发送MSG1和/或MSG3后，可以建立第一PDCP实体。对应地，目标小区基站可以在接收到MSG1和/或MSG3后，建立第一PDCP实体。
该随机接入过程可以是基于竞争的随机接入过程，也可以是基于非竞争的随机接入过程；该随机接入过程可以指四步随机接入过程，也可以指两步随机接入过程，本申请实施例对此不做具体限定。
终端设备接收到随机接入过程中的消息，或发送随机接入过程中的消息，表示终端设备已经与目标小区进行过通信，此时已经能够保证0ms的切换中断时间，此时再建立第一PDCP实体，不会影响终端设备的切换中断时间。
对于终端设备来说，特定定时器可以指终端设备在接收到源小区基站发送的任意消息后启动的定时器，例如该特定定时器可以是在终端设备接收到源小区基站发送的切换命令后启动的定时器。本申请实施例对定时器的时长不做具体限定。对于目标小区基站来说，特定定时器可以指目标小区基站接收到源小区基站和/或终端设备发送的任意消息后启动的定时器，如该特定定时器可以为目标小区基站接收到源小区基站发送的切换请求消息后启动的定时器。
终端设备可以在建立第一PDCP实体和/或释放第二PDCP实体后，通过第一PDCP实体向目标小区基站重传数据和/或发送状态报告。例如，终端设备在切换过程中，可能会存在数据没有被正确接收的情况，此时终端设备可以在第一PDCP实体建立和/或释放第二PDCP实体后，通过第一PDCP实体重传没有被正确接收的数据。通过第一PDCP实体重传数据可以指通过第一PDCP实体向目标小区基站重传数据。此外，终端设备还可以向目标小区基站发送状态报告，该状态报告中可以包括数据的接收情况，如哪些数据正确接收了，哪些数据没有被正确接收。
目标小区基站可以在建立第一PDCP实体后，通过第一PDCP实体接收终端设备发送的重传数据和/或状态报告。
终端设备在建立第一PDCP实体的过程中，可以保持与源小区基站之间的连接。然后在第一PDCP实体建立完成后，再释放与源小区基站之间的连接，这样有利于减小终端设备的切换中断时间。
终端设备在建立第一PDCP实体之前，还可以接收源小区基站发送的切换命令，该切换命令用于指示终端设备切换至目标小区基站。
情况2，第一PDCP实体与第二PDCP实体相同。在该情况下，同一时间只存在有一个PDCP实体。
作一个示例，第一PDCP实体可以包括第二PDCP，即第一PDCP实体可以保留第二PDCP实体中的参数。这样，由于第二PDCP实体中的参数都被保留，因此第一PDCP实体既可以与目标小区基站进行通信，也可以与源小区基站进行通信。
第一PDCP实体可以是在第二PDCP实体的基础上，增加第一参数得到的。该第一参数可用于终端设备与目标小区基站之间的通信，第一参数例如可以包括安全密钥和/或RoHC配置。终端设备可以在第二PDCP实体中包括的参数的基础上，增加安全密钥和/或RoHC配置，以用于与目标小区基站进行通信。目标小区基站也可以在在第二PDCP实体中包括的参数的基础上，增加安全密钥和/或RoHC配置，以用于与终端设备进行通信。
如图9所示，在小区切换之前，终端设备可以通过PDCP2与目标小区基站进行通信。在接收到切换命令后，终端设备可以在PDCP2的基础上，增加第一参数，形成PDCP1。由于PDCP1仍然保留PDCP2的配置，如第二参数，因此，PDCP1能够用于终端设备与源小区基站之间的通信。另外，由于PDCP1中增加了用于与目标小区基站进行通信的第一参数，因此，PDCP1也能够用于与目标小区基站进行通信。
第二参数可用于终端设备与源小区基站之间的通信，第二参数可以包括安全密钥和/或RoHc配置， 第二参数与第一参数不同。其中，第一参数中包括的安全密钥与第二参数中包括的安全密钥不同，第一参数中包括的RoHC配置与第二参数中包括的RoHC配置不同。
对于PDCP1而言，会维护两套密钥和RoHC profile，分别用于与源小区基站和目标小区基站之间的数据传输。
假设第一参数包括第一密钥和第一RoHC profile，第二参数包括第二密钥和第二RoHC profile。
如图10所示，终端设备在通信过程中，对于下行数据来说，目标小区基站向终端设备发送数据时，可以采用第一密钥加密数据，采用第一RoHC profile进行头压缩；源小区基站向终端设备发送数据时，可以采用第二密钥加密数据，采用第二RoHC profile进行头压缩。终端设备接收到数据时，可以先判断是哪个基站发送的数据，如果是目标小区基站发送的数据，则采用第一密钥解密数据，采用第一RoHC profile进行头解压缩；如果是源小区基站发送的数据，则采用第二密钥解密数据，采用第二RoHC profile进行头解压缩。
如图11所示，对于上行数据来说，终端设备在向基站发送数据时，如果是向目标小区基站发送数据，则终端设备可以采用第一密钥加密数据，采用第一RoHC profile进行头压缩；如果是向源小区基站发送数据，则采用第二密钥加密数据，采用第二RoHC profile进行头压缩。目标小区基站接收到终端设备发送的数据后，可以采用第一密钥解密数据，采用第一RoHC profile进行头解压缩；源小区基站接收到终端设备发送的数据后，可以采用第二密钥解密数据，采用第二RoHC profile进行头解压缩。
终端设备释放第二PDCP实体可以指，终端设备释放第二PDCP实体中的第二参数。如图12所示，终端设备释放PDCP1中包括的第二参数。具体地，终端设备可以删除与源小区基站进行数据传输所使用的安全密钥和/或RoHC配置。
PDCP1中包含了两套安全密钥和RoHC配置，能够同时与源小区基站和目标小区基站进行数据传输。当终端设备删除了源小区基站对应的安全密钥和RoHC配置后，表示终端设备释放源小区基站，此时终端设备仅能与目标小区基站进行数据传输。
参照上文的描述，在该情况下，本申请实施例对终端设备建立第一PDCP实体的时间不做具体限定，可以是终端设备在接收到切换命令后的任意时间点。例如终端设备建立第一PDCP实体的时间点可以是以下中的任意一个时间点：终端设备接收到源小区基站发送的第二消息，终端设备接收到随机接入过程中的消息，终端设备发送随机接入过程中的消息和特定定时器超时。为简化描述，此处不再赘述。
参照上文的描述，在该情况下，终端设备可以在添加第一参数和/或释放第二参数后，通过第一PDCP实体重传数据和/或发送状态报告。为简化描述，此处不再赘述。
终端设备在添加第一参数的过程中，可以保持与源小区基站之间的连接。
作为另一个示例，终端设备可以采用传统的重建PDCP的方式，如图13所示，建立目标小区基站对应的PDCP实体，只是终端设备重建PDCP的时间可以是在向目标小区基站发送MSG1之后，这样终端设备在重建PDCP实体时，终端设备已经与目标小区基站进行过通信，表示终端设备的切换中断时间已不再受PDCP重建的影响，有利于保证终端设备的切换中断时间。
目标小区基站也可以在接收到终端设备发送的MSG1之后，通过重建的方式生成第一PDCP实体。
终端设备在生成第一PDCP实体的过程中，可以保留第二PDCP实体中的PDCP上下文，仅更新安全密钥和RoHC配置，从而得到第二PDCP实体。
终端设备重建PDCP可以是在目标小区基站的随机接入成功的情况下建立的。终端设备建立第一PDCP实体可以包括：在目标小区随机接入成功的情况下，基于第二PDCP实体，通过重建生成第一PDCP实体。
终端设备在接收到切换命令后，会向目标小区基站发起随接入，在随机接入成功的情况下，终端设备可以通过重建生成第一PDCP实体。
本申请实施例对终端设备进行随机接入的方式不做具体限定。例如终端设备可以采用四步随机接入，也可以采用两步随机接入。又例如，终端设备可以采用基于竞争的随机接入方式，也可以采用基于非竞争的随机接入方式。
终端设备可以在接收到第三消息后，基于第二PDCP实体，生成第一PDCP实体。第三消息可以包括随机接入响应消息和/或竞争解决消息。
该随机接入响应消息可以指基于非竞争随机接入过程中的随机接入响应消息，终端设备接收到该随机接入响应消息后，表示终端设备随机接入成功，终端设备与目标小区基站之间建立连接。
对于非竞争的随机接入，终端设备随机接入成功还可以是指终端设备成功发送RRC重配置完成消息。也就是说，在成功发送RRC重配置完成消息后，终端设备可以通过重建来生成第一PDCP实体。
竞争解决消息可以指基于竞争随机接入过程中的MSG4，该MSG4表示终端设备竞争成功。终端设备接收到该竞争解决消息后，表示终端设备随机接入成功，终端设备与目标小区基站之间建立连接。
在本申请实施例中，终端设备在与目标小区基站之间进行随机接入的过程中，可以保持与源小区基站之间的连接。
由于第一PDCP实体是在第二PDCP实体的基础上生成的，因此终端设备在开始建立第一PDCP实体时，就表示已经释放了第二PDCP实体。在该情况下，终端设备释放第二PDCP实体的时间就等于终端设备建立第一PDCP实体的时间。
终端设备在目标小区基站随机接入成功的情况下，生成第一PDCP实体，可以指只要目标小区基站随接入成功，就生成第一PDCP实体，也可以指在目标小区基站随接入成功后的一段时间后，再生成第一PDCP实体。
本申请实施例中的目标基站与目标小区基站的含义相同，均表示目标小区所在的基站。源基站与源小区基站的含义相同，均表示源小区所在的基站。目标基站和源基站均可以至上文描述的网络设备。
上文中详细描述了根据本申请实施例的无线通信方法，下面将结合图14至图19，描述根据本申请实施例的装置，方法实施例所描述的技术特征适用于以下装置实施例。
图14是本申请实施例的一种终端设备的示意性框图，该终端设备可以是上文描述的任一种终端设备，图14的终端设备1400包括处理单元1410，其中：
处理单元1410，用于建立第一分组数据汇聚协议PDCP实体，所述第一PDCP实体用于终端设备与目标小区基站之间的通信。
处理单元1410，还用于释放第二PDCP实体，所述第二PDCP实体用于所述终端设备与源小区基站之间的通信，其中，释放所述第二PDCP实体的时间不早于建立所述第一PDCP实体的时间。
可选地，所述第一PDCP实体不同于所述第二PDCP实体。
可选地，所述终端设备还包括通信单元1420，用于接收所述源小区基站发送的第一消息，所述第一消息中包括所述第一PDCP实体的配置信息；所述处理单元1410用于：根据所述第一PDCP实体的配置信息，建立所述第一PDCP实体。
可选地，所述第一消息包括无线资源控制RRC重配置消息和/或切换命令。
可选地，所述第一PDCP实体中的上下文是根据所述第二PDCP实体中的上下文确定的。
可选地，所述终端设备还包括通信单元1420，用于接收所述源小区基站发送的第一指示信息，所述第一指示信息用于指示所述第一PDCP实体中的PDCP上下文是基于所述第二PDCP实体中的PDCP上下文确定的。
可选地，所述PDCP上下文包括以下信息中的至少一种：上行链路的PDCP序列号，上行链路的超帧号，下行链路的PDCP序列号和下行链路的超帧号。
可选地，所述第一PDCP实体和所述第二PDCP实体中的安全密钥不同，和/或，所述第一PDCP实体和所述第二PDCP实体中的可靠头压缩ROHC配置不同。
可选地，所述第一PDCP实体包括所述第二PDCP实体中的参数，所述第一PDCP实体还用于所述终端设备与所述源小区基站之间的通信。
可选地，所述第一PDCP实体是在所述第二PDCP实体的基础上增加第一参数得到的，所述第一参数用于所述终端设备与所述目标小区基站之间的通信，所述处理单元1410用于：释放所述第二PDCP实体中的第二参数，所述第二参数用于所述终端设备与所述源小区基站之间的通信，其中，释放所述第二参数的时间不早于添加所述第一参数的时间，所述第一参数与所述第二参数不同。
可选地，所述第一参数和所述第二参数均包括安全密钥和/或可靠头压缩ROHC配置。
可选地，所述建立所述第一PDCP实体的时间点包括以下中的至少一种：接收到所述源小区基站发送的第二消息，接收随机接入过程中的消息，发送随机接入过程中的消息和特定定时器超时。
可选地，所述指第二消息包括切换命令。
可选地，所述特定定时器为所述终端设备接收到所述源小区基站发送的切换命令后启动的定时器。
可选地，所述处理单元1410还用于：在建立所述第一PDCP实体的过程中，保持与所述源小区基站之间的连接。
可选地，所述处理单元1410用于：在所述目标小区基站的随机接入成功的情况下，基于所述第二PDCP实体，生成所述第一PDCP实体。
可选地，所述终端设备还包括通信单元1420，用于接收所述源小区基站发送的第三消息，所述第三消息包括以下消息中的至少一种：随机接入响应RAR消息和竞争解决消息。
可选地，所述处理单元1410还用于：在与所述目标小区基站进行随机接入的过程中，保持与所述源小区基站之间的连接。
可选地，所述终端设备还包括通信单元1420，用于在建立第一PDCP实体或释放第二PDCP实体后，通过所述第一PDCP实体重传数据和/或发送状态报告。
可选地，所述终端设备还包括通信单元1420，用于接收所述源小区基站发送的切换命令，所述切换命令用于指示所述终端设备切换至所述目标小区基站。
图15是本申请实施例的一种网络设备的示意性框图，该网络设备可以是上文描述的任一种源小区基站，图15的网络设备1500包括处理单元1510，其中：
处理单元1510，用于释放第二PDCP实体，所述第二PDCP实体用于源小区基站与终端设备之间的通信，其中，释放所述第二PDCP实体的时间不早于所述终端设备建立第一PDCP实体的时间，所述第一PDCP实体用于所述终端设备与目标小区基站之间的通信。
可选地，所述第一PDCP实体不同于所述第二PDCP实体。
可选地，所述网络设备还包括通信单元1520，用于向所述终端设备发送第一消息，所述第一消息中包括所述第一PDCP实体的配置信息，所述第一PDCP实体的配置信息用于所述终端设备建立所述第一PDCP实体。
可选地，所述第一消息包括无线资源控制RRC重配置消息和/或切换命令。
可选地，所述第一PDCP实体中的上下文是根据所述第二PDCP实体中的上下文确定的。
可选地，所述网络设备还包括通信单元1520，用于向所述终端设备发送第一指示信息，所述第一指示信息用于指示所述第一PDCP实体中的PDCP上下文是基于所述第二PDCP实体中的PDCP上下文确定的。
可选地，所述PDCP上下文包括以下信息中的至少一种：上行链路的PDCP序列号，上行链路的超帧号，下行链路的PDCP序列号和下行链路的超帧号。
可选地，所述第一PDCP实体和所述第二PDCP实体中的安全密钥不同，和/或，所述第一PDCP实体和所述第二PDCP实体中的可靠头压缩RoHC配置不同。
可选地，所述第一PDCP实体包括所述第二PDCP实体中的参数，所述第一PDCP实体还用于所述源小区基站与所述终端设备之间的通信。
可选地，所述第一PDCP实体是所述终端设备在所述第二PDCP实体的基础上增加第一参数得到的，所述第一参数用于所述终端设备与所述目标小区基站之间的通信，所述处理单元1510用于：释放所述第二PDCP实体中的第二参数，所述第二参数用于所述终端设备与所述源小区基站之间的通信，其中，释放所述第二参数的时间不早于所述终端设备增加所述第一参数的时间，所述第一参数与所述第二参数不同。
可选地，所述第一参数和所述第二参数均包括安全密钥和/或RoHC配置。
可选地，所述处理单元1510还用于：在所述终端设备建立所述第一PDCP实体的过程中，保持与所述终端设备之间的连接。
可选地，所述处理单元1510用于：在所述目标小区基站的随机接入成功的情况下，释放所述第二PDCP实体。
可选地，所述处理单元1510还用于：在所述终端设备进行目标小区基站的随机接入的过程中，保持与所述终端设备之间的连接。
可选地，所述网络设备还包括通信单元1520，用于向所述终端设备发送切换命令，所述切换命令用于指示所述终端设备切换至所述目标小区基站。
图16是本申请实施例的一种网络设备的示意性框图，该网络设备可以是上文描述的任一种目标小区基站，图16的网络设备1600包括处理单元1610，其中：
处理单元1610，用于建立第一分组数据汇聚协议PDCP实体，所述第一PDCP实体用于目标小区基站与终端设备之间的通信，其中，建立第一PDCP实体的时间不晚于所述终端设备释放第二PDCP实体的时间，所述第二PDCP实体用于所述终端设备与源小区基站之间的通信。
可选地，所述第一PDCP实体不同于所述第二PDCP实体。
可选地，所述网络设备还包括通信单元1620，用于：接收所述源小区基站发送的第一消息，所述第一消息中包括所述第一PDCP实体的配置信息；所述处理单元1610用于：根据所述第一PDCP实体的配置信息，建立所述第一PDCP实体。
可选地，所述第一消息包括切换请求消息。
可选地，所述第一PDCP实体中的上下文是根据所述第二PDCP实体中的上下文确定的。
可选地，所述网络设备还包括通信单元1620，用于接收所述源小区基站发送的第一指示信息，所述第一指示信息用于指示所述第一PDCP实体中的PDCP上下文是基于所述第二PDCP实体中的PDCP上下文确定的。
可选地，所述PDCP上下文包括以下信息中的至少一种：上行链路的PDCP序列号，上行链路的超帧号，下行链路的PDCP序列号和下行链路的超帧号。
可选地，所述第一PDCP实体和所述第二PDCP实体中的安全密钥不同，和/或，所述第一PDCP实体和所述第二PDCP实体中的可靠头压缩ROHC配置不同。
可选地，所述第一PDCP实体包括所述第二PDCP实体中的参数。
可选地，所述第二PDCP实体中的参数包括第二参数，所述第二参数用于所述终端设备与所述源小区基站之间的通信，所述第一PDCP实体是在所述第二PDCP实体的基础上增加第一参数得到的，所述第一参数用于所述目标小区基站与所述终端设备之间的通信，增加所述第一参数的时间不晚于所述终端设备释放第二参数的时间，所述第一参数与所述第二参数不同。
可选地，所述第一参数和所述第二参数均包括安全密钥和/或可靠头压缩ROHC配置。
可选地，所述建立所述第一PDCP实体的时间点包括以下中的至少一种：向所述源小区基站发送第二消息，接收随机接入过程中的消息，发送随机接入过程中的消息和特定定时器超时。
可选地，所述指第二消息包括切换请求确认消息。
可选地，所述特定定时器为所述目标小区基站向所述源小区基站发送切换请求确认消息后启动的定时器。
可选地，所述处理单元1610用于：在所述终端设备的随机接入成功的情况下，基于所述第二PDCP实体，生成所述第一PDCP实体。
可选地，在所述基于所述第二PDCP实体，生成所述第一PDCP实体之前，所述网络设备还包括通信单元，用于向所述终端设备发送第三消息，所述第三消息包括以下消息中的至少一种：随机接入响应RAR消息和竞争解决消息。
图17是本申请实施例提供的一种通信设备1700示意性结构图。图17所示的通信设备1700包括处理器1710，处理器1710可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图17所示，通信设备1700还可以包括存储器1720。其中，处理器1710可以从存储器1720中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器1720可以是独立于处理器1710的一个单独的器件，也可以集成在处理器1710中。
可选地，如图17所示，通信设备1700还可以包括收发器1730，处理器1710可以控制该收发器1730与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。
其中，收发器1730可以包括发射机和接收机。收发器1730还可以进一步包括天线，天线的数量可以为一个或多个。
可选地，该通信设备1700具体可为本申请实施例的网络设备，并且该通信设备1700可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该通信设备1700具体可为本申请实施例的移动终端/终端设备，并且该通信设备1700可以实现本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
图18是本申请实施例的装置的示意性结构图。图18所示的装置1800包括处理器1810，处理器1810可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图18所示，装置1800还可以包括存储器1820。其中，处理器1810可以从存储器1820中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器1820可以是独立于处理器1810的一个单独的器件，也可以集成在处理器1810中。
可选地，该装置1800还可以包括输入接口1830。其中，处理器1810可以控制该输入接口1830与其他设备或芯片进行通信，具体地，可以获取其他设备或芯片发送的信息或数据。
可选地，该装置1800还可以包括输出接口1840。其中，处理器1810可以控制该输出接口1840与其他设备或芯片进行通信，具体地，可以向其他设备或芯片输出信息或数据。
可选地，该装置可应用于本申请实施例中的网络设备，并且该装置可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该装置可应用于本申请实施例中的移动终端/终端设备，并且该装置可以实现本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
应理解，本申请实施例提到的装置可以为芯片，该芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
图19是本申请实施例提供的一种通信系统1900的示意性框图。如图19所示，该通信系统1900包括终端设备1910和网络设备1920。
其中，该终端设备1910可以用于实现上述方法中由终端设备实现的相应的功能，以及该网络设备1920可以用于实现上述方法中由网络设备实现的相应的功能为了简洁，在此不再赘述。
应理解，本申请实施例的处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中， 上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解，上述存储器为示例性但不是限制性说明，例如，本申请实施例中的存储器还可以是静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synch link DRAM，SLDRAM)以及直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)等等。也就是说，本申请实施例中的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提供了一种计算机可读存储介质，用于存储计算机程序。
可选的，该计算机可读存储介质可应用于本申请实施例中的网络设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机可读存储介质可应用于本申请实施例中的移动终端/终端设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序产品，包括计算机程序指令。
可选的，该计算机程序产品可应用于本申请实施例中的网络设备，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序产品可应用于本申请实施例中的移动终端/终端设备，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序。
可选的，该计算机程序可应用于本申请实施例中的网络设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序可应用于本申请实施例中的移动终端/终端设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式 实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。针对这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，)ROM、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (119)

  1. 一种用于小区切换的方法，其特征在于，包括：
    建立第一分组数据汇聚协议PDCP实体，所述第一PDCP实体用于终端设备与目标小区基站之间的通信；
    释放第二PDCP实体，所述第二PDCP实体用于所述终端设备与源小区基站之间的通信，其中，释放所述第二PDCP实体的时间不早于建立所述第一PDCP实体的时间。
  2. 根据权利要求1所述的方法，其特征在于，所述第一PDCP实体不同于所述第二PDCP实体。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    接收所述源小区基站发送的第一消息，所述第一消息中包括所述第一PDCP实体的配置信息；
    所述建立第一PDCP实体，包括：
    根据所述第一PDCP实体的配置信息，建立所述第一PDCP实体。
  4. 根据权利要求3所述的方法，其特征在于，所述第一消息包括无线资源控制RRC重配置消息和/或切换命令。
  5. 根据权利要求1-4中任一项所述的方法，其特征在于，所述第一PDCP实体中的上下文是根据所述第二PDCP实体中的上下文确定的。
  6. 根据权利要求5所述的方法，其特征在于，所述方法还包括：
    接收所述源小区基站发送的第一指示信息，所述第一指示信息用于指示所述第一PDCP实体中的PDCP上下文是基于所述第二PDCP实体中的PDCP上下文确定的。
  7. 根据权利要求6所述的方法，其特征在于，所述PDCP上下文包括以下信息中的至少一种：上行链路的PDCP序列号，上行链路的超帧号，下行链路的PDCP序列号和下行链路的超帧号。
  8. 根据权利要求1-7中任一项所述的方法，其特征在于，所述第一PDCP实体和所述第二PDCP实体中的安全密钥不同，和/或，所述第一PDCP实体和所述第二PDCP实体中的可靠头压缩ROHC配置不同。
  9. 根据权利要求1所述的方法，其特征在于，所述第一PDCP实体包括所述第二PDCP实体中的参数，所述第一PDCP实体还用于所述终端设备与所述源小区基站之间的通信。
  10. 根据权利要求9所述的方法，其特征在于，所述第一PDCP实体是在所述第二PDCP实体的基础上增加第一参数得到的，所述第一参数用于所述终端设备与所述目标小区基站之间的通信，
    所述释放第二PDCP实体，包括：
    释放所述第二PDCP实体中的第二参数，所述第二参数用于所述终端设备与所述源小区基站之间的通信，其中，释放所述第二参数的时间不早于添加所述第一参数的时间，所述第一参数与所述第二参数不同。
  11. 根据权利要求10所述的方法，其特征在于，所述第一参数和所述第二参数均包括安全密钥和/或可靠头压缩ROHC配置。
  12. 根据权利要求1-11中任一项所述的方法，其特征在于，所述建立所述第一PDCP实体的时间点包括以下中的至少一种：接收到所述源小区基站发送的第二消息，接收随机接入过程中的消息，发送随机接入过程中的消息和特定定时器超时。
  13. 根据权利要求12所述的方法，其特征在于，所述指第二消息包括切换命令。
  14. 根据权利要求12或13所述的方法，其特征在于，所述特定定时器为所述终端设备接收到所述源小区基站发送的切换命令后启动的定时器。
  15. 根据权利要求1-14中任一项所述的方法，其特征在于，所述方法还包括：
    在建立所述第一PDCP实体的过程中，保持与所述源小区基站之间的连接。
  16. 根据权利要求1所述的方法，其特征在于，所述建立第一PDCP实体，包括：
    在所述目标小区基站的随机接入成功的情况下，基于所述第二PDCP实体，生成所述第一PDCP实体。
  17. 根据权利要求16所述的方法，其特征在于，在所述基于所述第二PDCP实体，生成所述第一PDCP实体之前，所述方法还包括：
    接收所述目标小区基站发送的第三消息，所述第三消息包括以下消息中的至少一种：随机接入响应RAR消息和竞争解决消息。
  18. 根据权利要求16或17所述的方法，其特征在于，所述方法还包括：
    在与所述目标小区基站进行随机接入的过程中，保持与所述源小区基站之间的连接。
  19. 根据权利要求1-18中任一项所述的方法，其特征在于，所述方法还包括：
    在建立第一PDCP实体或释放第二PDCP实体后，通过所述第一PDCP实体重传数据和/或发送状 态报告。
  20. 根据权利要求1-19中任一项所述的方法，其特征在于，所述方法还包括：
    接收所述源小区基站发送的切换命令，所述切换命令用于指示所述终端设备切换至所述目标小区基站。
  21. 一种用于小区切换的方法，其特征在于，包括：
    释放第二PDCP实体，所述第二PDCP实体用于源小区基站与终端设备之间的通信，其中，释放所述第二PDCP实体的时间不早于所述终端设备建立第一PDCP实体的时间，所述第一PDCP实体用于所述终端设备与目标小区基站之间的通信。
  22. 根据权利要求21所述的方法，其特征在于，所述第一PDCP实体不同于所述第二PDCP实体。
  23. 根据权利要求21或22所述的方法，其特征在于，所述方法还包括：
    向所述终端设备发送第一消息，所述第一消息中包括所述第一PDCP实体的配置信息，所述第一PDCP实体的配置信息用于所述终端设备建立所述第一PDCP实体。
  24. 根据权利要求23所述的方法，其特征在于，所述第一消息包括无线资源控制RRC重配置消息和/或切换命令。
  25. 根据权利要求21-24中任一项所述的方法，其特征在于，所述第一PDCP实体中的上下文是根据所述第二PDCP实体中的上下文确定的。
  26. 根据权利要求25所述的方法，其特征在于，所述方法还包括：
    向所述终端设备发送第一指示信息，所述第一指示信息用于指示所述第一PDCP实体中的PDCP上下文是基于所述第二PDCP实体中的PDCP上下文确定的。
  27. 根据权利要求26所述的方法，其特征在于，所述PDCP上下文包括以下信息中的至少一种：上行链路的PDCP序列号，上行链路的超帧号，下行链路的PDCP序列号和下行链路的超帧号。
  28. 根据权利要求21-27中任一项所述的方法，其特征在于，所述第一PDCP实体和所述第二PDCP实体中的安全密钥不同，和/或，所述第一PDCP实体和所述第二PDCP实体中的可靠头压缩RoHC配置不同。
  29. 根据权利要求21所述的方法，其特征在于，所述第一PDCP实体包括所述第二PDCP实体中的参数，所述第一PDCP实体还用于所述源小区基站与所述终端设备之间的通信。
  30. 根据权利要求29所述的方法，其特征在于，所述第一PDCP实体是所述终端设备在所述第二PDCP实体的基础上增加第一参数得到的，所述第一参数用于所述终端设备与所述目标小区基站之间的通信，
    所述释放第二PDCP实体，包括：
    释放所述第二PDCP实体中的第二参数，所述第二参数用于所述终端设备与所述源小区基站之间的通信，其中，释放所述第二参数的时间不早于所述终端设备增加所述第一参数的时间，所述第一参数与所述第二参数不同。
  31. 根据权利要求30所述的方法，其特征在于，所述第一参数和所述第二参数均包括安全密钥和/或RoHC配置。
  32. 根据权利要求21-31中任一项所述的方法，其特征在于，所述方法还包括：
    在所述终端设备建立所述第一PDCP实体的过程中，保持与所述终端设备之间的连接。
  33. 根据权利要求21所述的方法，其特征在于，所述释放第二PDCP实体，包括：
    在所述目标小区基站的随机接入成功的情况下，释放所述第二PDCP实体。
  34. 根据权利要求33所述的方法，其特征在于，所述方法还包括：
    在所述终端设备进行目标小区基站的随机接入的过程中，保持与所述终端设备之间的连接。
  35. 根据权利要求21-34中任一项所述的方法，其特征在于，所述方法还包括：
    向所述终端设备发送切换命令，所述切换命令用于指示所述终端设备切换至所述目标小区基站。
  36. 一种用于小区切换的方法，其特征在于，包括：
    建立第一分组数据汇聚协议PDCP实体，所述第一PDCP实体用于目标小区基站与终端设备之间的通信，其中，建立第一PDCP实体的时间不晚于所述终端设备释放第二PDCP实体的时间，所述第二PDCP实体用于所述终端设备与源小区基站之间的通信。
  37. 根据权利要求36所述的方法，其特征在于，所述第一PDCP实体不同于所述第二PDCP实体。
  38. 根据权利要求36或37所述的方法，其特征在于，所述方法还包括：
    接收所述源小区基站发送的第一消息，所述第一消息中包括所述第一PDCP实体的配置信息；
    所述建立第一PDCP实体，包括：
    根据所述第一PDCP实体的配置信息，建立所述第一PDCP实体。
  39. 根据权利要求38所述的方法，其特征在于，所述第一消息包括切换请求消息。
  40. 根据权利要求36-39中任一项所述的方法，其特征在于，所述第一PDCP实体中的上下文是根据所述第二PDCP实体中的上下文确定的。
  41. 根据权利要求40所述的方法，其特征在于，所述方法还包括：
    接收所述源小区基站发送的第一指示信息，所述第一指示信息用于指示所述第一PDCP实体中的PDCP上下文是基于所述第二PDCP实体中的PDCP上下文确定的。
  42. 根据权利要求41所述的方法，其特征在于，所述PDCP上下文包括以下信息中的至少一种：上行链路的PDCP序列号，上行链路的超帧号，下行链路的PDCP序列号和下行链路的超帧号。
  43. 根据权利要求36-42中任一项所述的方法，其特征在于，所述第一PDCP实体和所述第二PDCP实体中的安全密钥不同，和/或，所述第一PDCP实体和所述第二PDCP实体中的可靠头压缩ROHC配置不同。
  44. 根据权利要求36所述的方法，其特征在于，所述第一PDCP实体包括所述第二PDCP实体中的参数。
  45. 根据权利要求44所述的方法，其特征在于，所述第二PDCP实体中的参数包括第二参数，所述第二参数用于所述终端设备与所述源小区基站之间的通信，所述第一PDCP实体是在所述第二PDCP实体的基础上增加第一参数得到的，所述第一参数用于所述目标小区基站与所述终端设备之间的通信，增加所述第一参数的时间不晚于所述终端设备释放第二参数的时间，所述第一参数与所述第二参数不同。
  46. 根据权利要求45所述的方法，其特征在于，所述第一参数和所述第二参数均包括安全密钥和/或可靠头压缩ROHC配置。
  47. 根据权利要求36-46中任一项所述的方法，其特征在于，所述建立所述第一PDCP实体的时间点包括以下中的至少一种：向所述源小区基站发送第二消息，接收随机接入过程中的消息，发送随机接入过程中的消息和特定定时器超时。
  48. 根据权利要求47所述的方法，其特征在于，所述指第二消息包括切换请求确认消息。
  49. 根据权利要求47或48所述的方法，其特征在于，所述特定定时器为所述目标小区基站向所述源小区基站发送切换请求确认消息后启动的定时器。
  50. 根据权利要求36所述的方法，其特征在于，所述建立第一PDCP实体，包括：
    在所述终端设备的随机接入成功的情况下，基于所述第二PDCP实体，生成所述第一PDCP实体。
  51. 根据权利要求50所述的方法，其特征在于，在所述基于所述第二PDCP实体，生成所述第一PDCP实体之前，所述方法还包括：
    向所述终端设备发送第三消息，所述第三消息包括以下消息中的至少一种：随机接入响应RAR消息和竞争解决消息。
  52. 根据权利要求36-51中任一项所述的方法，其特征在于，所述方法还包括：
    在建立第一PDCP实体后，通过所述第一PDCP实体接收所述终端设备发送的重传数据和/或状态报告。
  53. 一种终端设备，其特征在于，包括：
    处理单元，用于建立第一分组数据汇聚协议PDCP实体，所述第一PDCP实体用于终端设备与目标小区基站之间的通信；
    所述处理单元还用于，释放第二PDCP实体，所述第二PDCP实体用于所述终端设备与源小区基站之间的通信，其中，释放所述第二PDCP实体的时间不早于建立所述第一PDCP实体的时间。
  54. 根据权利要求53所述的终端设备，其特征在于，所述第一PDCP实体不同于所述第二PDCP实体。
  55. 根据权利要求53或54所述的终端设备，其特征在于，所述终端设备还包括通信单元，用于：接收所述源小区基站发送的第一消息，所述第一消息中包括所述第一PDCP实体的配置信息；
    所述处理单元用于：根据所述第一PDCP实体的配置信息，建立所述第一PDCP实体。
  56. 根据权利要求55所述的终端设备，其特征在于，所述第一消息包括无线资源控制RRC重配置消息和/或切换命令。
  57. 根据权利要求53-56中任一项所述的终端设备，其特征在于，所述第一PDCP实体中的上下文是根据所述第二PDCP实体中的上下文确定的。
  58. 根据权利要求57所述的终端设备，其特征在于，所述终端设备还包括通信单元，用于：接收所述源小区基站发送的第一指示信息，所述第一指示信息用于指示所述第一PDCP实体中的PDCP上下文是基于所述第二PDCP实体中的PDCP上下文确定的。
  59. 根据权利要求58所述的终端设备，其特征在于，所述PDCP上下文包括以下信息中的至少一种：上行链路的PDCP序列号，上行链路的超帧号，下行链路的PDCP序列号和下行链路的超帧号。
  60. 根据权利要求53-59中任一项所述的终端设备，其特征在于，所述第一PDCP实体和所述第二PDCP实体中的安全密钥不同，和/或，所述第一PDCP实体和所述第二PDCP实体中的可靠头压缩ROHC配置不同。
  61. 根据权利要求53所述的终端设备，其特征在于，所述第一PDCP实体包括所述第二PDCP实体中的参数，所述第一PDCP实体还用于所述终端设备与所述源小区基站之间的通信。
  62. 根据权利要求61所述的终端设备，其特征在于，所述第一PDCP实体是在所述第二PDCP实体的基础上增加第一参数得到的，所述第一参数用于所述终端设备与所述目标小区基站之间的通信，
    所述处理单元用于：释放所述第二PDCP实体中的第二参数，所述第二参数用于所述终端设备与所述源小区基站之间的通信，其中，释放所述第二参数的时间不早于添加所述第一参数的时间，所述第一参数与所述第二参数不同。
  63. 根据权利要求62所述的终端设备，其特征在于，所述第一参数和所述第二参数均包括安全密钥和/或可靠头压缩ROHC配置。
  64. 根据权利要求53-63中任一项所述的终端设备，其特征在于，所述建立所述第一PDCP实体的时间点包括以下中的至少一种：接收到所述源小区基站发送的第二消息，接收随机接入过程中的消息，发送随机接入过程中的消息和特定定时器超时。
  65. 根据权利要求64所述的终端设备，其特征在于，所述指第二消息包括切换命令。
  66. 根据权利要求64或65所述的终端设备，其特征在于，所述特定定时器为所述终端设备接收到所述源小区基站发送的切换命令后启动的定时器。
  67. 根据权利要求53-66中任一项所述的终端设备，其特征在于，所述处理单元还用于：
    在建立所述第一PDCP实体的过程中，保持与所述源小区基站之间的连接。
  68. 根据权利要求53所述的终端设备，其特征在于，所述处理单元用于：
    在所述目标小区基站的随机接入成功的情况下，基于所述第二PDCP实体，生成所述第一PDCP实体。
  69. 根据权利要求68所述的终端设备，其特征在于，所述终端设备还包括通信单元，用于：
    接收所述源小区基站发送的第三消息，所述第三消息包括以下消息中的至少一种：随机接入响应RAR消息和竞争解决消息。
  70. 根据权利要求68或69所述的终端设备，其特征在于，所述处理单元还用于：
    在与所述目标小区基站进行随机接入的过程中，保持与所述源小区基站之间的连接。
  71. 根据权利要求53-70中任一项所述的终端设备，其特征在于，所述终端设备还包括通信单元，用于：
    在建立第一PDCP实体或释放第二PDCP实体后，通过所述第一PDCP实体重传数据和/或发送状态报告。
  72. 根据权利要求53-71中任一项所述的终端设备，其特征在于，所述终端设备还包括通信单元，用于：
    接收所述源小区基站发送的切换命令，所述切换命令用于指示所述终端设备切换至所述目标小区基站。
  73. 一种网络设备，其特征在于，所述网络设备为源小区基站，所述网络设备包括处理单元，用于：
    释放第二PDCP实体，所述第二PDCP实体用于源小区基站与终端设备之间的通信，其中，释放所述第二PDCP实体的时间不早于所述终端设备建立第一PDCP实体的时间，所述第一PDCP实体用于所述终端设备与目标小区基站之间的通信。
  74. 根据权利要求73所述的网络设备，其特征在于，所述第一PDCP实体不同于所述第二PDCP实体。
  75. 根据权利要求73或74所述的网络设备，其特征在于，所述网络设备还包括通信单元，用于：
    向所述终端设备发送第一消息，所述第一消息中包括所述第一PDCP实体的配置信息，所述第一PDCP实体的配置信息用于所述终端设备建立所述第一PDCP实体。
  76. 根据权利要求75所述的网络设备，其特征在于，所述第一消息包括无线资源控制RRC重配置消息和/或切换命令。
  77. 根据权利要求73-76中任一项所述的网络设备，其特征在于，所述第一PDCP实体中的上下文是根据所述第二PDCP实体中的上下文确定的。
  78. 根据权利要求77所述的网络设备，其特征在于，所述网络设备还包括通信单元，用于：
    向所述终端设备发送第一指示信息，所述第一指示信息用于指示所述第一PDCP实体中的PDCP上下文是基于所述第二PDCP实体中的PDCP上下文确定的。
  79. 根据权利要求78所述的网络设备，其特征在于，所述PDCP上下文包括以下信息中的至少一种：上行链路的PDCP序列号，上行链路的超帧号，下行链路的PDCP序列号和下行链路的超帧号。
  80. 根据权利要求73-79中任一项所述的网络设备，其特征在于，所述第一PDCP实体和所述第二PDCP实体中的安全密钥不同，和/或，所述第一PDCP实体和所述第二PDCP实体中的可靠头压缩RoHC配置不同。
  81. 根据权利要求80所述的网络设备，其特征在于，所述第一PDCP实体包括所述第二PDCP实体中的参数，所述第一PDCP实体还用于所述源小区基站与所述终端设备之间的通信。
  82. 根据权利要求81所述的网络设备，其特征在于，所述第一PDCP实体是所述终端设备在所述第二PDCP实体的基础上增加第一参数得到的，所述第一参数用于所述终端设备与所述目标小区基站之间的通信，
    所述处理单元用于：
    释放所述第二PDCP实体中的第二参数，所述第二参数用于所述终端设备与所述源小区基站之间的通信，其中，释放所述第二参数的时间不早于所述终端设备增加所述第一参数的时间，所述第一参数与所述第二参数不同。
  83. 根据权利要求82所述的网络设备，其特征在于，所述第一参数和所述第二参数均包括安全密钥和/或RoHC配置。
  84. 根据权利要求73-83中任一项所述的网络设备，其特征在于，所述处理单元还用于：
    在所述终端设备建立所述第一PDCP实体的过程中，保持与所述终端设备之间的连接。
  85. 根据权利要求84所述的网络设备，其特征在于，所述处理单元用于：
    在所述目标小区基站的随机接入成功的情况下，释放所述第二PDCP实体。
  86. 根据权利要求84或85所述的网络设备，其特征在于，所述处理单元还用于：
    在所述终端设备进行目标小区基站的随机接入的过程中，保持与所述终端设备之间的连接。
  87. 根据权利要求73-86中任一项所述的网络设备，其特征在于，所述网络设备还包括通信单元，用于：
    向所述终端设备发送切换命令，所述切换命令用于指示所述终端设备切换至所述目标小区基站。
  88. 一种网络设备，其特征在于，所述网络设备为目标小区基站，所述网络设备包括：
    处理单元，用于建立第一分组数据汇聚协议PDCP实体，所述第一PDCP实体用于目标小区基站与终端设备之间的通信，其中，建立第一PDCP实体的时间不晚于所述终端设备释放第二PDCP实体的时间，所述第二PDCP实体用于所述终端设备与源小区基站之间的通信。
  89. 根据权利要求88所述的网络设备，其特征在于，所述第一PDCP实体不同于所述第二PDCP实体。
  90. 根据权利要求88或89所述的网络设备，其特征在于，所述网络设备还包括通信单元，用于：
    接收所述源小区基站发送的第一消息，所述第一消息中包括所述第一PDCP实体的配置信息；
    所述处理单元用于：根据所述第一PDCP实体的配置信息，建立所述第一PDCP实体。
  91. 根据权利要求90所述的网络设备，其特征在于，所述第一消息包括切换请求消息。
  92. 根据权利要求88-91中任一项所述的网络设备，其特征在于，所述第一PDCP实体中的上下文是根据所述第二PDCP实体中的上下文确定的。
  93. 根据权利要求92所述的网络设备，其特征在于，所述网络设备还包括通信单元，用于：
    接收所述源小区基站发送的第一指示信息，所述第一指示信息用于指示所述第一PDCP实体中的PDCP上下文是基于所述第二PDCP实体中的PDCP上下文确定的。
  94. 根据权利要求93所述的网络设备，其特征在于，所述PDCP上下文包括以下信息中的至少一种：上行链路的PDCP序列号，上行链路的超帧号，下行链路的PDCP序列号和下行链路的超帧号。
  95. 根据权利要求88-94中任一项所述的网络设备，其特征在于，所述第一PDCP实体和所述第二PDCP实体中的安全密钥不同，和/或，所述第一PDCP实体和所述第二PDCP实体中的可靠头压缩ROHC配置不同。
  96. 根据权利要求95所述的网络设备，其特征在于，所述第一PDCP实体包括所述第二PDCP实体中的参数。
  97. 根据权利要求96所述的网络设备，其特征在于，所述第二PDCP实体中的参数包括第二参数，所述第二参数用于所述终端设备与所述源小区基站之间的通信，所述第一PDCP实体是在所述第二PDCP实体的基础上增加第一参数得到的，所述第一参数用于所述目标小区基站与所述终端设备之间的 通信，增加所述第一参数的时间不晚于所述终端设备释放第二参数的时间，所述第一参数与所述第二参数不同。
  98. 根据权利要求97所述的网络设备，其特征在于，所述第一参数和所述第二参数均包括安全密钥和/或可靠头压缩ROHC配置。
  99. 根据权利要求88-98中任一项所述的网络设备，其特征在于，所述建立所述第一PDCP实体的时间点包括以下中的至少一种：向所述源小区基站发送第二消息，接收随机接入过程中的消息，发送随机接入过程中的消息和特定定时器超时。
  100. 根据权利要求99所述的网络设备，其特征在于，所述指第二消息包括切换请求确认消息。
  101. 根据权利要求99或100所述的网络设备，其特征在于，所述特定定时器为所述目标小区基站向所述源小区基站发送切换请求确认消息后启动的定时器。
  102. 根据权利要求101所述的网络设备，其特征在于，所述处理单元用于：
    在所述终端设备的随机接入成功的情况下，基于所述第二PDCP实体，生成所述第一PDCP实体。
  103. 根据权利要求102所述的网络设备，其特征在于，在所述基于所述第二PDCP实体，生成所述第一PDCP实体之前，所述网络设备还包括：
    向所述终端设备发送第三消息，所述第三消息包括以下消息中的至少一种：随机接入响应RAR消息和竞争解决消息。
  104. 根据权利要求88-103中任一项所述的网络设备，其特征在于，所述网络设备还包括通信单元，用于：
    在建立第一PDCP实体后，通过所述第一PDCP实体接收所述终端设备发送的重传数据和/或状态报告。
  105. 一种终端设备，其特征在于，包括：处理器和存储器，该存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行如权利要求1至20中任一项所述的方法。
  106. 一种网络设备，其特征在于，包括：处理器和存储器，该存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行如权利要求21至35中任一项所述的方法。
  107. 一种网络设备，其特征在于，包括：处理器和存储器，该存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行如权利要求36至52中任一项所述的方法。
  108. 一种装置，其特征在于，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述装置的设备执行如权利要求1至20中任一项所述的方法。
  109. 一种装置，其特征在于，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述装置的设备执行如权利要求21至35中任一项所述的方法。
  110. 一种装置，其特征在于，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述装置的设备执行如权利要求36至52中任一项所述的方法。
  111. 一种计算机可读存储介质，其特征在于，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求1至20中任一项所述的方法。
  112. 一种计算机可读存储介质，其特征在于，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求21至35中任一项所述的方法。
  113. 一种计算机可读存储介质，其特征在于，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求36至52中任一项所述的方法。
  114. 一种计算机程序产品，其特征在于，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求1至20中任一项所述的方法。
  115. 一种计算机程序产品，其特征在于，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求21至35中任一项所述的方法。
  116. 一种计算机程序产品，其特征在于，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求36至52中任一项所述的方法。
  117. 一种计算机程序，其特征在于，所述计算机程序使得计算机执行如权利要求1至20中任一项所述的方法。
  118. 一种计算机程序，其特征在于，所述计算机程序使得计算机执行如权利要求21至35中任一项所述的方法。
  119. 一种计算机程序，其特征在于，所述计算机程序使得计算机执行如权利要求36至52中任一项所述的方法。
PCT/CN2019/085100 2019-04-30 2019-04-30 用于小区切换的方法及设备 WO2020220238A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
PCT/CN2019/085100 WO2020220238A1 (zh) 2019-04-30 2019-04-30 用于小区切换的方法及设备
EP19927220.4A EP3934321A4 (en) 2019-04-30 2019-04-30 METHOD AND DEVICE FOR CELL DELIVERY
CN201980090039.8A CN113330775A (zh) 2019-04-30 2019-04-30 用于小区切换的方法及设备
CN202111107327.5A CN113660707A (zh) 2019-04-30 2019-04-30 用于小区切换的方法及设备
KR1020217039064A KR20220002597A (ko) 2019-04-30 2019-04-30 셀 핸드오버 방법 및 기기
US17/497,093 US20220030470A1 (en) 2019-04-30 2021-10-08 Method and device for cell handover

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/085100 WO2020220238A1 (zh) 2019-04-30 2019-04-30 用于小区切换的方法及设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/497,093 Continuation US20220030470A1 (en) 2019-04-30 2021-10-08 Method and device for cell handover

Publications (1)

Publication Number Publication Date
WO2020220238A1 true WO2020220238A1 (zh) 2020-11-05

Family

ID=73029605

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/085100 WO2020220238A1 (zh) 2019-04-30 2019-04-30 用于小区切换的方法及设备

Country Status (5)

Country Link
US (1) US20220030470A1 (zh)
EP (1) EP3934321A4 (zh)
KR (1) KR20220002597A (zh)
CN (2) CN113330775A (zh)
WO (1) WO2020220238A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102581274B1 (ko) 2022-01-07 2023-09-21 주식회사 성우하이텍 배터리 케이스의 크로스 멤버 조립용 코어 및 코어 장착 지그
WO2023146357A1 (en) * 2022-01-29 2023-08-03 Samsung Electronics Co., Ltd. Method, base station, electronic apparatus and storage medium for supporting multicast transmission

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101997660A (zh) * 2009-08-14 2011-03-30 中兴通讯股份有限公司 一种避免上行数据丢失的方法及装置
US20150327236A1 (en) * 2013-01-18 2015-11-12 Huawei Technologies Co., Ltd. Data transmission method, base station, and user equipment
CN108391297A (zh) * 2017-02-03 2018-08-10 华为技术有限公司 设备切换方法及设备、承载配置方法及设备、通信系统
CN109644380A (zh) * 2018-02-12 2019-04-16 Oppo广东移动通信有限公司 无线通信的方法、网络设备和终端设备

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016021822A1 (en) * 2014-08-07 2016-02-11 Lg Electronics Inc. Method for processing a packet data convergence protocol packet data unit at a user equipment in a dual connectivity systme and device therefor
US10244444B2 (en) * 2015-03-04 2019-03-26 Qualcomm Incorporated Dual link handover
CN108632934B (zh) * 2017-03-24 2021-01-01 华为技术有限公司 切换的方法和设备
CN109982360B (zh) * 2017-12-27 2021-12-10 华为技术有限公司 通信方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101997660A (zh) * 2009-08-14 2011-03-30 中兴通讯股份有限公司 一种避免上行数据丢失的方法及装置
US20150327236A1 (en) * 2013-01-18 2015-11-12 Huawei Technologies Co., Ltd. Data transmission method, base station, and user equipment
CN108391297A (zh) * 2017-02-03 2018-08-10 华为技术有限公司 设备切换方法及设备、承载配置方法及设备、通信系统
CN109644380A (zh) * 2018-02-12 2019-04-16 Oppo广东移动通信有限公司 无线通信的方法、网络设备和终端设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3934321A4 *

Also Published As

Publication number Publication date
EP3934321A1 (en) 2022-01-05
CN113330775A (zh) 2021-08-31
US20220030470A1 (en) 2022-01-27
EP3934321A4 (en) 2022-04-06
CN113660707A (zh) 2021-11-16
KR20220002597A (ko) 2022-01-06

Similar Documents

Publication Publication Date Title
US20210352546A1 (en) Handover method and device
US20220394577A1 (en) Handover method and communication apparatus
US20230262515A1 (en) Communication method and apparatus
WO2020220309A1 (zh) 用于小区切换的方法及设备
US20220022112A1 (en) Method for cell handover, and devices
WO2019237763A1 (zh) 一种rlf的处理方法及装置、通信设备
US9232454B2 (en) Data offloading method
WO2022016413A1 (zh) 切换方法、终端设备和网络设备
US20220394802A1 (en) Re-establishment method and communication apparatus
WO2020062376A1 (zh) 一种切换上报的方法、终端设备及网络设备
WO2020155070A1 (zh) 用于切换网络设备的方法和终端设备
US20220030470A1 (en) Method and device for cell handover
TW202010334A (zh) 一種資料傳輸方法及裝置、終端
US20210360503A1 (en) Method for radio communication and terminal device
WO2021031012A1 (zh) 用于小区切换的方法及设备
WO2020164026A1 (zh) 随机接入的方法、终端设备和网络设备
WO2020248283A1 (zh) 无线通信方法、装置和终端设备
US20220007449A1 (en) Wireless communication method, terminal device and network device
WO2020155157A1 (zh) 切换过程中安全信息的处理方法及装置、网络设备、终端
WO2023178697A1 (zh) 信息处理方法和终端设备
WO2023102812A1 (zh) 无线通信方法、终端设备及网络设备
WO2023108564A1 (zh) 无线通信方法、终端设备以及网络设备
EP4087207A1 (en) Switching processing method and terminal device

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: 19927220

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019927220

Country of ref document: EP

Effective date: 20210929

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20217039064

Country of ref document: KR

Kind code of ref document: A