CN109757130B

CN109757130B - Method for configuring packet data convergence protocol PDCP, terminal equipment and network equipment

Info

Publication number: CN109757130B
Application number: CN201780050436.3A
Authority: CN
Inventors: 唐海
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2017-09-08
Filing date: 2017-09-08
Publication date: 2020-06-23
Anticipated expiration: 2037-09-08
Also published as: CN109757130A; WO2019047163A1

Abstract

The embodiment of the application provides a method for configuring PDCP, a terminal device and a network device, wherein the network device can realize the switching between different PDCP entities without confirming that the terminal device does not have uplink data transmission currently, and meanwhile, the terminal device can also realize the switching between different PDCP entities. The method comprises the following steps: receiving configuration information sent by a network device through a first PDCP entity, wherein the configuration information is used for indicating switching from the first PDCP entity to a second PDCP entity, and the first PDCP entity and the second PDCP entity are PDCP entities under different communication protocol versions; transmitting, by the first PDCP entity, a response message for the configuration information to the network device; after transmitting the response message, switching the PDCP transmitting entity and the PDCP receiving entity from the first PDCP entity to the second PDCP entity according to the configuration information.

Description

Method for configuring packet data convergence protocol PDCP, terminal equipment and network equipment

Technical Field

The present application relates to the field of communications, and more particularly, to a method, a terminal device and a network device for configuring PDCP.

Background

In a 5G communication system, there may be two types of radio bearers on a Long Term Evolution (LTE) base station, which are:

a Packet Data Convergence Protocol (PDCP) layer of the LTE version, and a Radio Link Control (RLC) layer and a Media Access Control (MAC) layer of the LTE version as lower layers;

a New Radio (NR) version of PDCP layer, and lower layers are LTE versions of RLC and MAC layers.

In the prior art, a network device performs a conversion of two Bearer forms only when it is determined that no uplink data is currently in a buffer of a Signaling Radio Bearer (SRB) of a terminal device, which results in that a PDCP entity cannot be converted when the terminal device transmits or receives data, and meanwhile, when the network device cannot determine that no uplink data is currently in the buffer of the SRB, if the terminal device has uplink data transmission, the network device may not receive the data.

Disclosure of Invention

The embodiment of the application provides a method for configuring PDCP, a terminal device and a network device, wherein the network device can realize the switching between different PDCP entities without confirming that the terminal device does not have uplink data transmission currently, and meanwhile, the terminal device can also realize the switching between different PDCP entities.

In a first aspect, an embodiment of the present application provides a method for configuring a packet data convergence protocol PDCP, including:

receiving configuration information sent by a network device through a first PDCP entity, wherein the configuration information is used for indicating switching from the first PDCP entity to a second PDCP entity, and the first PDCP entity and the second PDCP entity are PDCP entities under different communication protocol versions;

transmitting, by the first PDCP entity, a response message for the configuration information to the network device;

after transmitting the response message, switching the PDCP transmitting entity and the PDCP receiving entity from the first PDCP entity to the second PDCP entity according to the configuration information.

Therefore, in the method for configuring the PDCP according to the embodiment of the present application, the terminal device receives the configuration information indicating the PDCP handover sent by the network device, and performs the PDCP handover according to the configuration information after sending the response message, so that data sent by the terminal device in a time period after receiving the configuration information and before sending the response message can be received by the network device, and it is further ensured that the PDCP handover does not affect the data sending of the terminal device.

Optionally, in an implementation manner of the first aspect, the switching the PDCP sending entity and the PDCP receiving entity from the first PDCP entity to the second PDCP entity according to the configuration information includes:

according to the configuration information, the first PDCP entity for the PDCP transmitting entity and the PDCP receiving entity is released, and the second PDCP entity for the PDCP transmitting entity and the PDCP receiving entity is established.

Optionally, in an implementation manner of the first aspect, the method further includes:

and performing data transceiving through the second PDCP entity.

Optionally, in an implementation manner of the first aspect, the configuration information is radio resource control, RRC, connection reconfiguration information.

Optionally, in an implementation manner of the first aspect, the first PDCP entity is a PDCP entity supporting a long term evolution, LTE, communication protocol, and the second PDCP entity is a PDCP entity supporting a new radio NR communication protocol; or

The first PDCP entity is a PDCP entity supporting an NR communication protocol, and the second PDCP entity is a PDCP entity supporting an LTE communication protocol.

In a second aspect, an embodiment of the present application provides a method for configuring a packet data convergence protocol PDCP, including:

sending configuration information to a terminal device through a first PDCP entity, wherein the configuration information is used for indicating the terminal device to be switched from the first PDCP entity to a second PDCP entity, and the first PDCP entity and the second PDCP entity are PDCP entities under different communication protocol versions;

receiving, by the first PDCP entity, a response message for the configuration information sent by the terminal device;

after receiving the response message, switching the PDCP transmitting entity and the PDCP receiving entity from the first PDCP entity to the second PDCP entity.

Therefore, in the method for configuring the PDCP according to the embodiment of the present application, the network device sends the configuration information indicating the PDCP handover to the terminal device, and performs the PDCP handover after receiving the response message, so that data sent by the terminal device in a time period after receiving the configuration information and before sending the response message can be received by the network device, and it is further ensured that the PDCP handover does not affect data sending of the terminal device.

Optionally, in an implementation manner of the second aspect, before receiving the response message, the method further includes:

and receiving data sent by the terminal equipment through the first PDCP entity.

Optionally, in an implementation manner of the second aspect, the switching the PDCP sending entity and the PDCP receiving entity from the first PDCP entity to the second PDCP entity includes:

releasing the first PDCP entity for the PDCP transmitting entity and the PDCP receiving entity, and establishing the second PDCP entity for the PDCP transmitting entity and the PDCP receiving entity.

Optionally, in an implementation manner of the second aspect, the method further includes:

and performing data transceiving through the second PDCP entity.

Optionally, in an implementation manner of the second aspect, the configuration information is radio resource control, RRC, connection reconfiguration information.

Optionally, in an implementation manner of the second aspect, the first PDCP entity is a PDCP entity supporting a long term evolution LTE communication protocol, and the second PDCP entity is a PDCP entity supporting a new radio NR communication protocol; or

In a third aspect, an embodiment of the present application provides a method for configuring a packet data convergence protocol PDCP, including:

the configuration information is sent to the terminal equipment through the first PDCP entity, the configuration information is used for indicating the switching from the first PDCP entity to the second PDCP entity, and the first PDCP entity and the second PDCP entity are PDCP entities under different communication protocol versions;

after sending the configuration information, maintaining the first PDCP entity and establishing the second PDCP entity;

receiving, by the first PDCP entity and the second PDCP entity, a response message for the configuration information sent by the terminal device;

releasing the first PDCP entity after receiving the response message.

Therefore, in the method for configuring PDCP in this embodiment of the present application, the network device sends configuration information indicating PDCP handover to the terminal device, and after sending the configuration information, the network device keeps the PDCP entity before handover and establishes the PDCP entity to be handed over, and after receiving the response message, releases the PDCP entity before handover, so that data sent by the terminal device in a time period after receiving the configuration information and before sending the response message can be received by the network device, and further, it is ensured that PDCP handover does not affect data sending of the terminal device.

and receiving data sent by the terminal equipment through the first PDCP entity and the second PDCP entity.

and performing data transceiving through the second PDCP entity.

In a fourth aspect, an embodiment of the present application provides a terminal device, which may execute the modules or units of the method in the first aspect or any optional implementation manner of the first aspect.

In a fifth aspect, the present application provides a network device, which may execute the modules or units of the method in any optional implementation manner of the second aspect or the second aspect.

In a sixth aspect, an embodiment of the present application provides a network device, which may execute the modules or units of the method in any optional implementation manner of the third aspect or the third aspect.

In a seventh aspect, a terminal device is provided that includes a processor, a memory, and a communication interface. The processor is coupled to the memory and the communication interface. The memory is for storing instructions, the processor is for executing the instructions, and the communication interface is for communicating with other network elements under control of the processor. The processor, when executing the instructions stored by the memory, causes the processor to perform the method of the first aspect or any possible implementation of the first aspect.

In an eighth aspect, a network device is provided that includes a processor, a memory, and a communication interface. The processor is coupled to the memory and the communication interface. The memory is for storing instructions, the processor is for executing the instructions, and the communication interface is for communicating with other network elements under control of the processor. The processor, when executing the instructions stored by the memory, causes the processor to perform the second aspect or the method of any possible implementation of the second aspect.

In a ninth aspect, a network device is provided that includes a processor, a memory, and a communication interface. The processor is coupled to the memory and the communication interface. The memory is for storing instructions, the processor is for executing the instructions, and the communication interface is for communicating with other network elements under control of the processor. The processor, when executing the instructions stored by the memory, causes the processor to perform the third aspect or the method of any possible implementation of the third aspect.

A tenth aspect provides a computer storage medium having program code stored therein for instructing a computer to execute the instructions of the method of the first aspect or any of the possible implementations of the first aspect.

In an eleventh aspect, there is provided a computer storage medium having program code stored therein for instructing a computer to execute instructions of the method of the second aspect or any possible implementation manner of the second aspect.

In a twelfth aspect, a computer storage medium is provided, in which a program code is stored, the program code being used for instructing a computer to execute the instructions of the method in the third aspect or any possible implementation manner of the third aspect.

In a thirteenth aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the above aspects.

Drawings

Fig. 1 shows a wireless communication system to which an embodiment of the present application is applied.

Fig. 2 is a schematic flow chart of a method of configuring PDCP according to an embodiment of the present application.

Fig. 3 is a schematic flow chart of another method for configuring PDCP according to an embodiment of the present application.

Fig. 4 is a schematic flow chart diagram of still another method for configuring PDCP according to an embodiment of the present application.

Fig. 5 is a schematic block diagram of a terminal device according to an embodiment of the present application.

Fig. 6 is a schematic block diagram of a network device according to an embodiment of the present application.

Fig. 7 is a schematic block diagram of another network device according to an embodiment of the present application.

Fig. 8 is a schematic block diagram illustrating an apparatus for configuring PDCP according to an embodiment of the present application.

Fig. 9 is a schematic structural diagram of a system chip according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application.

The technical scheme of the embodiment of the application can be applied to various communication systems, for example: a global system for Mobile communications (GSM) system, a Code Division Multiple Access (CDMA) system, a Wideband Code Division Multiple Access (WCDMA) system, a General Packet Radio Service (GPRS), a Long Term Evolution (Long Term Evolution, LTE) system, a Frequency Division Duplex (FDD) system, a Time Division Duplex (TDD), a Universal Mobile Telecommunications System (UMTS), a Worldwide Interoperability for microwave Access (WiMAX) communication system, or a future 5G system.

Fig. 1 illustrates a wireless communication system 100 to which an embodiment of the present application is applied. The wireless communication system 100 may include a network device 110. Network device 110 may be a device that communicates with a terminal device. Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices (e.g., UEs) located within the coverage area. Optionally, the Network device 110 may be a Base Transceiver Station (BTS) in a GSM system or a CDMA system, a Base Station (NodeB, NB) in a WCDMA system, an evolved node B (eNB or eNodeB) in an LTE system, or a wireless controller in a Cloud Radio Access Network (CRAN), or a Network device in a relay Station, an Access point, a vehicle-mounted device, a wearable device, a Network-side device in a future 5G Network, or a Network device in a future evolved Public Land Mobile Network (PLMN), or the like.

The wireless communication system 100 also includes at least one terminal device 120 located within the coverage area of the network device 110. The terminal device 120 may be mobile or stationary. Alternatively, terminal Equipment 120 may refer to an access terminal, User Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, User terminal, wireless communication device, User agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device having Wireless communication capabilities, a computing device or other processing device connected to a Wireless modem, a vehicle mounted device, a wearable device, a terminal device in a future 5G network or a terminal device in a future evolved PLMN, etc.

Optionally, a Device to Device (D2D) communication may be performed between the terminal devices 120.

Alternatively, the 5G system or network may also be referred to as a New Radio (NR) system or network.

Fig. 1 exemplarily shows one network device and two terminal devices, and optionally, the wireless communication system 100 may include a plurality of network devices and may include other numbers of terminal devices within the coverage of each network device, which is not limited in this embodiment of the present application.

Optionally, the wireless communication system 100 may further include other network entities such as a network controller, a mobility management entity, and the like, which is not limited in this embodiment.

It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.

Figure 2 is a schematic flow chart diagram of a method 200 for configuring PDCP according to an embodiment of the present application. As shown in fig. 2, the method 200 may be performed by a terminal device, which may be the terminal device shown in fig. 1, and the network device in the method 200 may be the network device shown in fig. 1, and the method 200 includes the following.

And 210, receiving, by a first PDCP entity, configuration information sent by a network device, where the configuration information is used to indicate a handover from the first PDCP entity to a second PDCP entity, and the first PDCP entity and the second PDCP entity are PDCP entities in different communication protocol versions.

It should be understood that, for data sent by the terminal device through the first PDCP entity, the network device also needs to receive the data through the first PDCP entity, that is, the terminal device and the network device can send and receive the data through PDCP entities in the same communication protocol version.

It is understood that the PDCP entity is located in the PDCP layer, and includes a transmitting entity and a receiving entity.

Optionally, for a terminal device, a plurality of PDCP entities may be defined, each PDCP entity carrying data of one radio bearer.

Optionally, one PDCP entity may be associated with the control plane and also associated with the user plane, depending mainly on which radio bearer it carries data.

Optionally, the switching from the first PDCP entity to the second PDCP entity refers to establishing the second PDCP entity and releasing the first PDCP entity.

It should be understood that establishing the PDCP entity refers to establishing a new PDCP transmitting entity and PDCP receiving entity. Releasing the PDCP entity refers to releasing the original PDCP transmitting entity and PDCP receiving entity.

Optionally, the PDCP entity is established simultaneously with the establishment of the RCL layer and the MAC layer of its lower layer.

Optionally, the PDCP entity is released simultaneously with the release of the RCL layer and the MAC layer of its lower layer.

Optionally, the configuration information is Radio Resource Control (RRC) connection reconfiguration information, for example, the configuration information may be RRCconnectionreconfiguration information.

Optionally, the bit sequences sent by the PDCP entities in different communication protocol versions may have different interpretations, for example, bits occupied by data headers, data packets, and the like sent by the PDCP entities in different communication protocol versions are different.

Optionally, the first PDCP entity is a PDCP entity supporting an LTE communication protocol, and the second PDCP entity is a PDCP entity supporting an NR communication protocol.

Optionally, the first PDCP entity is a PDCP entity supporting an NR communication protocol, and the second PDCP entity is a PDCP entity supporting an LTE communication protocol.

Optionally, the lower layer of the PDCP layer of the LTE release is an RLC layer and an MAC layer of the LTE release; the lower layer of the NR version PDCP layer is the LTE version RLC layer and MAC layer.

Optionally, the first PDCP entity is a PDCP entity supporting an Evolved LTE (Evolved LTE) communication protocol, and the second PDCP entity is a PDCP entity supporting an NR communication protocol.

It should be understood that other PDCP entities in different communication protocol versions are also possible, and the present application is not limited by this comparison.

220, a response message for the configuration information is sent to the network device through the first PDCP entity.

Alternatively, the response message may be radio resource control connection reconfiguration complete information, for example, the response message is rrcconnectionconfigurationcomplete information.

It is to be understood that the network device also receives the response message through the first PDCP entity at this time.

Optionally, the terminal device has buffered uplink data in a buffer (buffer) of the SRB before receiving the configuration information, that is, the network device receives the uplink data buffered in the SRB through the first PDCP entity before receiving the response message (rrcconnectionconfiguration complete).

And 230, after transmitting the response message, switching the PDCP transmitting entity and the PDCP receiving entity from the first PDCP entity to the second PDCP entity according to the configuration information.

Optionally, the terminal device converts versions of its PDCP transmitting entity (Up-Link, UL) and PDCP receiving entity (Down Link, DL) after replying rrcconnectionconfigurationcomplete.

Optionally, the switching the PDCP sending entity and the PDCP receiving entity from the first PDCP entity to the second PDCP entity according to the configuration information includes:

It is understood that the PDCP transmitting entity and the PDCP receiving entity are the same PDCP entity.

Optionally, the method 200 further comprises: and performing data transceiving through the second PDCP entity. That is, after the PDCP transmitting entity and the PDCP receiving entity are switched from the first PDCP entity to the second PDCP entity, the terminal device performs data transceiving through the second PDCP entity.

Figure 3 is a schematic flow chart diagram of a method 300 for configuring PDCP according to an embodiment of the present application. As shown in fig. 3, the method 300 may be performed by a network device, which may be a network device as shown in fig. 1, and a terminal device in the method 300 may be a terminal device as shown in fig. 1, and the method 300 includes the following.

And 310, sending configuration information to the terminal device through the first PDCP entity, where the configuration information is used to instruct the terminal device to switch from the first PDCP entity to a second PDCP entity, and the first PDCP entity and the second PDCP entity are PDCP entities in different communication protocol versions.

Optionally, the configuration information is RRC connection reconfiguration information.

And 320, receiving a response message for the configuration information sent by the terminal equipment through the first PDCP entity.

Optionally, before receiving the response message, the method 300 further includes:

And a PDCP sending entity and a PDCP receiving entity are handed over from the first PDCP entity to the second PDCP entity after receiving the response message 330.

Optionally, the network device converts versions of its PDCP transmitting entity (DL) and PDCP receiving entity (UL) after receiving the rrcconnectionconfigurationcomplete.

Optionally, the switching the PDCP sending entity and the PDCP receiving entity from the first PDCP entity to the second PDCP entity includes:

Optionally, the method 300 further comprises: and performing data transceiving through the second PDCP entity. That is, after the PDCP transmitting entity and the PDCP receiving entity are switched from the first PDCP entity to the second PDCP entity, the network device performs data transceiving through the second PDCP entity.

It should be understood that the steps in the method 300 for configuring PDCP may refer to the description of the corresponding steps in the method 200 for configuring PDCP, and are not repeated herein for brevity.

Figure 4 is a schematic flow chart diagram of a method 400 of configuring PDCP according to an embodiment of the present application. As shown in fig. 4, the method 400 may be performed by a network device, which may be a network device as shown in fig. 1, and a terminal device in the method 400 may be a terminal device as shown in fig. 1, the method 400 including the following.

And 410, configuration information sent to the terminal device by the first PDCP entity, wherein the configuration information is used for indicating handover from the first PDCP entity to a second PDCP entity, and the first PDCP entity and the second PDCP entity are PDCP entities under different communication protocol versions.

After sending the configuration information, the first PDCP entity is maintained, and the second PDCP entity is established 420.

It is to be understood that the network device maintains the first PDCP entity, i.e., the network device can transceive data through the first PDCP entity.

Alternatively, maintaining the PDCP entity means maintaining a function of transmitting and receiving data of the PDCP entity while maintaining an RLC layer and a MAC layer of a lower layer thereof.

Optionally, the network device may receive at this time an entity holding both PDCP versions (e.g., both LTE and NR versions of PDCP entities).

430, receiving a response message for the configuration information sent by the terminal device through the first PDCP entity and the second PDCP entity.

Optionally, after receiving the RRCconnectionreconfiguration, the terminal device converts versions of its PDCP transmitting entity (UL) and PDCP receiving entity (DL).

Optionally, after receiving the configuration information, the terminal device switches its own PDCP sending entity (UL) and PDCP receiving entity (DL) from the first PDCP entity to the second PDCP entity, and at this time, the terminal device sends the response message through the second PDCP entity.

Optionally, after sending the response message, the terminal device switches its own PDCP sending entity (UL) and PDCP receiving entity (DL) from the first PDCP entity to the second PDCP entity, and at this time, the terminal device sends the response message through the first PDCP entity.

Optionally, before receiving the response message, the method further comprises:

It should be understood that the network device can now receive both the terminal device transmit data via the first PDCP entity and the terminal device transmit data via the second PDCP entity.

Releasing the first PDCP entity after receiving the response message 440.

Optionally, the method further comprises: and performing data transceiving through the second PDCP entity. That is, after the PDCP transmitting entity and the PDCP receiving entity are switched from the first PDCP entity to the second PDCP entity, the network device performs data transceiving through the second PDCP entity.

It should be understood that the steps in the method 400 for configuring PDCP may refer to the description of the corresponding steps in the method 200 for configuring PDCP, and are not repeated herein for brevity.

Fig. 5 is a schematic block diagram of a terminal device 500 according to an embodiment of the present application. As shown in fig. 5, the terminal device 500 includes:

a transceiving unit 510, configured to receive, by a first PDCP entity, configuration information sent by a network device, where the configuration information is used to indicate a handover from the first PDCP entity to a second PDCP entity, and the first PDCP entity and the second PDCP entity are PDCP entities in different communication protocol versions;

the transceiving unit 510 is further configured to send a response message for the configuration information to the network device through the first PDCP entity;

a processing unit 520, configured to switch the PDCP transmitting entity and the PDCP receiving entity from the first PDCP entity to the second PDCP entity according to the configuration information after the transceiving unit 510 transmits the response message.

Optionally, the processing unit 520 is specifically configured to:

Optionally, the transceiving unit 510 is further configured to transceive data through the second PDCP entity.

Optionally, the configuration information is radio resource control, RRC, connection reconfiguration information.

Optionally, the first PDCP entity is a PDCP entity supporting a long term evolution LTE communication protocol, and the second PDCP entity is a PDCP entity supporting a new radio NR communication protocol; or

It should be understood that the terminal device 500 according to the embodiment of the present application may correspond to the terminal device in the method 200 of the present application, and the above and other operations and/or functions of each unit in the terminal device 500 are respectively for implementing the corresponding flow of the terminal device in the method 200 shown in fig. 2, and are not described herein again for brevity.

Fig. 6 is a schematic block diagram of a network device 600 according to an embodiment of the present application. As shown in fig. 6, the network device 600 includes:

a transceiving unit 610, configured to send configuration information to a terminal device through a first packet data convergence protocol PDCP entity, where the configuration information is used to instruct the terminal device to switch from a first PDCP entity to a second PDCP entity, and the first PDCP entity and the second PDCP entity are PDCP entities in different communication protocol versions;

the transceiving unit 610 is further configured to receive, by the first PDCP entity, a response message for the configuration information sent by the terminal device;

a processing unit 620, configured to switch the PDCP transmitting entity and the PDCP receiving entity from the first PDCP entity to the second PDCP entity after the transceiving unit 610 receives the response message.

Optionally, before the transceiving unit 610 receives the response message, the transceiving unit 610 is further configured to receive data sent by the terminal device through the first PDCP entity.

Optionally, the processing unit 620 is specifically configured to:

Optionally, the transceiving unit 610 is further configured to transceive data through the second PDCP entity.

It should be understood that the network device 600 according to the embodiment of the present application may correspond to the network device in the method 300 of the present application, and the above and other operations and/or functions of the units in the network device 600 are respectively for implementing the corresponding flows of the network device in the method 300 shown in fig. 3, and are not described herein again for brevity.

Fig. 7 is a schematic block diagram of a network device 700 according to an embodiment of the present application. As shown in fig. 7, the network device 700 includes:

a transceiving unit 710, configured to send configuration information to a terminal device through a first packet data convergence protocol PDCP entity, where the configuration information is used to indicate a handover from the first PDCP entity to a second PDCP entity, and the first PDCP entity and the second PDCP entity are PDCP entities in different communication protocol versions;

a processing unit 720, configured to maintain the first PDCP entity and establish the second PDCP entity after the transceiver unit 710 transmits the configuration information;

the transceiving unit 710 is further configured to receive a response message for the configuration information sent by the terminal device through the first PDCP entity and the second PDCP entity;

the processing unit 720 is further configured to release the first PDCP entity after receiving the response message.

Optionally, before the transceiving unit 710 receives the response message, the transceiving unit 710 is further configured to receive data sent by the terminal device through the first PDCP entity and the second PDCP entity.

Optionally, the transceiving unit 710 is further configured to transceive data through the second PDCP entity.

It should be understood that the network device 700 according to the embodiment of the present application may correspond to the network device in the method 400 of the present application, and the above and other operations and/or functions of the units in the network device 700 are respectively for implementing the corresponding flows of the network device in the method 400 shown in fig. 4, and are not described herein again for brevity.

Fig. 8 is a schematic block diagram illustrating an apparatus 800 for configuring PDCP according to an embodiment of the present application, where the apparatus 800 includes:

a memory 810 for storing a program, the program comprising code;

a transceiver 820 for communicating with other devices;

a processor 830 for executing the program code in memory 810.

Optionally, when the code is executed, the processor 830 may implement various operations performed by the terminal device in the method 200 in fig. 2, and details are not described herein for brevity. At this time, the device 800 may be a terminal device (e.g., a mobile phone). The transceiver 820 is used to perform specific signal transceiving under the driving of the processor 830.

Optionally, when the code is executed, the processor 830 may also implement the method 300 in fig. 3 or implement the operations performed by the network device in the method 400 in fig. 4, and details are not described herein for brevity. At this time, the device 800 may be a network device (e.g., an access network device or a core network device).

It should be understood that, in the embodiment of the present application, the processor 830 may be a Central Processing Unit (CPU), and the processor 830 may also be other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The memory 810 may include a read-only memory and a random access memory, and provides instructions and data to the processor 830. A portion of the memory 810 may also include non-volatile random access memory. For example, the memory 810 may also store device type information.

Transceiver 820 may be a transceiver for performing signal transmission and reception functions such as frequency modulation and demodulation functions or frequency up-and down-conversion functions.

In implementation, at least one step of the above method may be performed by a hardware integrated logic circuit in the processor 830, or the integrated logic circuit may perform the at least one step under instruction driving in a software form. Accordingly, the apparatus 800 configuring the PDCP may be a single chip or a chip set. The steps of a method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in a processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and the processor 830 reads the information in the memory and performs the steps of the method in combination with hardware thereof. To avoid repetition, it is not described in detail here.

Fig. 9 is a schematic block diagram of a system chip 900 according to an embodiment of the present application. The system chip 900 of fig. 9 includes an input interface 901, an output interface 902, a processor 903 and a memory 904, which are connected by an internal communication connection, and the processor 903 is used for executing codes in the memory 904.

Optionally, when the code is executed, the processor 903 implements the method performed by the terminal device in the method embodiment. For brevity, no further description is provided herein.

Optionally, when the code is executed, the processor 903 implements the method performed by the network device in the method embodiment. For brevity, no further description is provided herein.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for configuring a Packet Data Convergence Protocol (PDCP), which is applicable to a 5G communication system, comprises the following steps:

a terminal device receives configuration information sent by a network device of a long term evolution base station through a first PDCP entity, wherein the configuration information is used for indicating the terminal device to be switched from the first PDCP entity to a second PDCP entity, and the first PDCP entity and the second PDCP entity are PDCP entities under different communication protocol versions;

sending, by the first PDCP entity, a response message to the configuration information to the network device;

after sending the response message, the terminal device switches a PDCP sending entity and a PDCP receiving entity from the first PDCP entity to the second PDCP entity according to the configuration information;

wherein the switching the PDCP transmitting entity and the PDCP receiving entity from the first PDCP entity to the second PDCP entity according to the configuration information comprises: establishing the second PDCP entity and releasing the first PDCP entity;

establishing a Radio Link Control (RLC) layer and a Medium Access Control (MAC) layer of a lower layer of the second PDCP entity while establishing the second PDCP entity; releasing an RLC layer and an MAC layer of a lower layer of the first PDCP entity while releasing the first PDCP entity;

the first PDCP entity is a PDCP entity supporting a Long Term Evolution (LTE) communication protocol, and the second PDCP entity is a PDCP entity supporting a new wireless NR communication protocol; or

The first PDCP entity is a PDCP entity supporting NR communication protocol, and the second PDCP entity is a PDCP entity supporting LTE communication protocol.

2. The method of claim 1, wherein establishing the second PDCP entity and releasing the first PDCP entity comprises:

according to the configuration information, the first PDCP entity aiming at the PDCP sending entity and the PDCP receiving entity is released, and the second PDCP entity aiming at the PDCP sending entity and the PDCP receiving entity is established.

3. The method according to claim 1 or 2, characterized in that the method further comprises:

and performing data transceiving through the second PDCP entity.

4. The method according to claim 1 or 2, wherein the configuration information is radio resource control, RRC, connection reconfiguration information.

5. A method for configuring a Packet Data Convergence Protocol (PDCP), which is applicable to a 5G communication system, comprises the following steps:

a network device of a long term evolution base station sends configuration information to a terminal device through a first PDCP entity, wherein the configuration information is used for indicating the terminal device to be switched from the first PDCP entity to a second PDCP entity, and the first PDCP entity and the second PDCP entity are PDCP entities under different communication protocol versions;

switching a PDCP transmitting entity and a PDCP receiving entity from the first PDCP entity to the second PDCP entity after receiving the response message;

wherein the switching the PDCP transmitting entity and the PDCP receiving entity from the first PDCP entity to the second PDCP entity comprises: establishing the second PDCP entity and releasing the first PDCP entity;

6. The method of claim 5, wherein prior to receiving the response message, the method further comprises:

7. The method of claim 5 or 6, wherein establishing the second PDCP entity and releasing the first PDCP entity comprises:

8. The method of claim 5 or 6, further comprising:

and performing data transceiving through the second PDCP entity.

9. The method according to claim 5 or 6, wherein the configuration information is radio resource control, RRC, connection reconfiguration information.

10. A method for configuring a Packet Data Convergence Protocol (PDCP), which is applicable to a 5G communication system, comprises the following steps:

the method comprises the steps that configuration information is sent to a terminal device by a network device of a long-term evolution base station through a first PDCP entity, the configuration information is used for indicating the terminal device to be switched from the first PDCP entity to a second PDCP entity, and the first PDCP entity and the second PDCP entity are PDCP entities under different communication protocol versions;

releasing the first PDCP entity after receiving the response message;

establishing a Radio Link Control (RLC) layer and a Medium Access Control (MAC) layer of a lower layer of the second PDCP entity at the same time of establishing the second PDCP entity; releasing an RLC layer and an MAC layer of a lower layer of the first PDCP entity while releasing the first PDCP entity;

11. The method of claim 10, wherein prior to receiving the response message, the method further comprises:

12. The method according to claim 10 or 11, characterized in that the method further comprises:

and performing data transceiving through the second PDCP entity.

13. The method according to claim 10 or 11, wherein the configuration information is radio resource control, RRC, connection reconfiguration information.

14. A terminal device, adapted for a 5G communication system, comprising:

a transceiving unit, configured to receive, by a first packet data convergence protocol PDCP entity, configuration information sent by a network device of a long term evolution base station, where the configuration information is used to instruct a terminal device to switch from a first PDCP entity to a second PDCP entity, and the first PDCP entity and the second PDCP entity are PDCP entities in different communication protocol versions;

the transceiving unit is further configured to send, by the first PDCP entity, a response message for the configuration information to the network device;

a processing unit, configured to switch a PDCP sending entity and a PDCP receiving entity from the first PDCP entity to the second PDCP entity according to the configuration information after the transceiving unit sends the response message;

15. The terminal device of claim 14, wherein the processing unit is specifically configured to:

16. The terminal device according to claim 14 or 15, wherein the transceiving unit is further configured to transceive data through the second PDCP entity.

17. The terminal device according to claim 14 or 15, wherein the configuration information is radio resource control, RRC, connection reconfiguration information.

18. A network device, adapted for a long term evolution base station of a 5G communication system, comprising:

a transceiving unit, configured to send configuration information to a terminal device through a first packet data convergence protocol PDCP entity, where the configuration information is used to instruct the terminal device to switch from a first PDCP entity to a second PDCP entity, and the first PDCP entity and the second PDCP entity are PDCP entities in different communication protocol versions;

the transceiving unit is further configured to receive, by the first PDCP entity, a response message for the configuration information sent by the terminal device;

a processing unit, configured to switch a PDCP sending entity and a PDCP receiving entity from the first PDCP entity to the second PDCP entity after the transceiving unit receives the response message;

19. The network device of claim 18, wherein the transceiver unit is further configured to receive data sent by the terminal device through the first PDCP entity before the transceiver unit receives the response message.

20. The network device according to claim 18 or 19, wherein the processing unit is specifically configured to:

21. The network device according to claim 18 or 19, wherein the transceiving unit is further configured to transceive data through the second PDCP entity.

22. The network device of claim 18 or 19, wherein the configuration information is radio resource control, RRC, connection reconfiguration information.

23. A network device, adapted for a long term evolution base station of a 5G communication system, comprising:

a processing unit, configured to maintain the first PDCP entity and establish the second PDCP entity after the transceiver unit sends the configuration information;

the transceiving unit is further configured to receive, through the first PDCP entity and the second PDCP entity, a response message for the configuration information sent by the terminal device;

the processing unit is further configured to release the first PDCP entity after receiving the response message;

24. The network device of claim 23, wherein the transceiver unit is further configured to receive data transmitted by the terminal device via the first PDCP entity and the second PDCP entity before the transceiver unit receives the response message.

25. The network device according to claim 23 or 24, wherein the transceiving unit is further configured to transceive data through the second PDCP entity.

26. The network device of claim 23 or 24, wherein the configuration information is radio resource control, RRC, connection reconfiguration information.