CN110831250A

CN110831250A - Processing method and terminal

Info

Publication number: CN110831250A
Application number: CN201810891527.6A
Authority: CN
Inventors: 吴昱民
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2018-08-07
Filing date: 2018-08-07
Publication date: 2020-02-21
Anticipated expiration: 2038-08-07
Also published as: CN110831250B

Abstract

The invention provides a processing method and a terminal, wherein the method comprises the following steps: in the radio resource control RRC connection control flow, if the terminal meets the preset condition, a packet data convergence protocol PDCP entity of a target radio bearer RB is established according to the stored terminal context information. On one hand, a solution is provided for the processing behavior of the PDCP entity of the target RB in the RRC connection control flow; on the other hand, the terminal establishes the PDCP entity of the target RB according to the stored context information of the terminal, so that the efficiency of data transmission after the RRC connection is completed can be improved.

Description

Processing method and terminal

Technical Field

The embodiment of the invention relates to the technical field of communication, in particular to a processing method and a terminal.

Background

Currently, in order to reduce the power consumption of the terminal, the protocol designs a "suspend-resume" flow. The network side device may Control the terminal to enter an idle (inactive) state by suspending an RRC (Radio Resource Control) connection of the terminal, and when the terminal needs to re-enter a connected state from the idle state, the terminal may initiate an RRC connection Control procedure to the network side device.

However, in the RRC connection control procedure, a processing behavior of a PDCP entity for a suspended RB (Radio Bearer) is not currently defined.

Disclosure of Invention

The embodiment of the invention provides a processing method and a terminal, aiming at providing a solution for the processing behavior of a PDCP entity of a suspended RB in an RRC connection control flow.

The invention is realized by the following steps:

in a first aspect, an embodiment of the present invention provides a processing method, applied to a terminal, where the method includes:

in the radio resource control RRC connection control flow, if a preset condition is met, a packet data convergence protocol PDCP entity of a target radio bearer RB is established according to the stored terminal context information.

In a second aspect, an embodiment of the present invention further provides a terminal, where the terminal includes:

and the establishing module is used for establishing a packet data convergence protocol PDCP entity of the target radio bearer RB according to the stored terminal context information if a preset condition is met in the radio resource control RRC connection control flow.

In a third aspect, an embodiment of the present invention further provides a terminal, where the terminal includes a processor, a memory, and a computer program stored in the memory and being executable on the processor, and when the computer program is executed by the processor, the steps of the processing method described above are implemented.

In a fourth aspect, the embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the steps of the processing method described above.

In the embodiment of the invention, in the radio resource control RRC connection control flow, if the terminal meets the preset condition, a packet data convergence protocol PDCP entity of a target radio bearer RB is established according to the stored terminal context information. On one hand, a solution is provided for the processing behavior of the PDCP entity of the target RB in the RRC connection control flow; on the other hand, the terminal establishes the PDCP entity of the target RB according to the stored context information of the terminal, so that the efficiency of data transmission after the RRC connection is completed can be improved.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments of the present invention will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without inventive exercise.

Fig. 1 is a block diagram of a network system to which an embodiment of the present invention is applicable;

FIG. 2 is a flow chart of a processing method provided by an embodiment of the invention;

FIG. 3 is a second flowchart of a processing method according to an embodiment of the present invention;

fig. 4 is one of the structural diagrams of a terminal provided in the embodiment of the present invention;

fig. 5 is a second structural diagram of a terminal according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

The terms "first," "second," and the like in this application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus. Further, as used herein, "and/or" means at least one of the connected objects, e.g., a and/or B and/or C, means 7 cases including a alone, B alone, C alone, and both a and B present, B and C present, both a and C present, and A, B and C present.

Referring to fig. 1, fig. 1 is a structural diagram of a network system to which an embodiment of the present invention is applicable, and as shown in fig. 1, the network system includes a terminal 11 and a network-side device 12, where the terminal 11 and the network-side device 12 can communicate with each other.

In this embodiment of the present invention, the terminal 11 may also be referred to as a UE (User Equipment), and when the implementation is specific, the terminal 11 may be a terminal-side Device such as a mobile phone, a Tablet Personal Computer (Tablet Personal Computer), a laptop Computer (laptop Computer), a Personal Digital Assistant (PDA), a Mobile Internet Device (MID), a Wearable Device (Wearable Device), or a vehicle-mounted Device, and it should be noted that a specific type of the terminal 11 is not limited in this embodiment of the present invention.

The network side device 12 may be a base station, a relay, an access point, or the like. The base station may be a base station of 5G and later versions (e.g., a 5G NR NB), or a base station in another communication system (e.g., an evolved Node B (eNB)), and it should be noted that the specific type of the network side device 12 is not limited in this embodiment of the present invention.

For convenience of description, some contents related to the embodiments of the present invention are explained below:

and RRC connection control flow.

The RRC connection control procedure may be represented as an RRC connection recovery procedure, an RRC connection establishment procedure, or an RRC connection reestablishment procedure.

Referring to fig. 2, as shown in fig. 2, the RRC connection control procedure may include the following steps:

and step 0, the network side equipment sends an RRC connection release message to the terminal.

The RRC Connection Release message carries a Suspend field, so as to inform the terminal that the RRC Connection is suspended, and the terminal switches from the connected state to the idle state.

After receiving the RRC connection release message, the terminal may store the context information of the terminal corresponding to the PDCP entity, so as to prevent the loss of data in the PDCP entity in the suspended state.

Specifically, the terminal context information corresponding to the PDCP entity may include at least one of: RRC configuration information of the PDCP entity, PDCP status information of the PDCP entity. Further, the PDCP status information of the PDCP entity may include at least one of: header compression state information of the PDCP entity, and state variable state information of a receive window and a transmit window of the PDCP entity.

In some embodiments, the terminal context information corresponding to the PDCP entity may further include at least one of: the information processing method includes security context information, Service Data Attachment Protocol (SDAP) configuration information, Cell Radio Network temporary identity (C-RNTI) information of a source Cell (Primary Cell), and Cell identification information of the source Cell.

In addition, the terminal may suspend all SRBs (Signaling Radio bearers) and DRBs (Data Radio bearers) except the SRB 0.

It should be noted that, when the RRC connection control procedure is represented as an RRC connection establishment procedure or an RRC connection reestablishment procedure, the RRC connection control procedure may not include step 0. That is, for a terminal that needs to enter a connected state from a spatial state, the terminal may directly perform step 1 to trigger an RRC connection control procedure.

Step 1, the terminal sends an RRC connection request message to the network side equipment.

In practical application, when the terminal needs to enter a connected state from an idle state, the terminal may send an RRC connection request message to the network side device.

At this time, the terminal may recover the RRC configuration information and the security context information from the stored terminal context information. The terminal can restore the PDCP state of the PDCP entity corresponding to the SRB1 and reestablish the SRB, and at the same time, resume data transceiving of the SRB 1.

The RRC Connection Request message may be represented as an RRC Connection resume Request (RRC Connection resumerrequest) message, an RRC Connection Setup Request (RRC Connection Setup Request) message, or an RRC Connection Reestablishment Request (RRC Connection Reestablishment Request) message.

And step 2, the network side equipment sends an RRC connection confirmation message to the terminal.

In practical applications, if the network side device receives the RRC connection request sent by the terminal, the network side device may send an RRC connection confirmation message to the terminal.

The specific form of the RRC connection confirmation message may be the specific form of the RRC connection request message. For example, if the RRC Connection request message represents an RRC Connection recovery request message, the RRC Connection confirm message may represent an RRC Connection recovery (RRC Connection Resume) message; if the RRC Connection request message is expressed as an RRC Connection Setup request message, the RRC Connection confirm message may be expressed as an RRC Connection Setup (RRC Connection Setup) message; if the RRC Connection request message is represented as an RRC Connection Reestablishment request message, the RRC Connection confirm message may be represented as an RRC Connection Reestablishment (RRC Connection request) message.

In addition, it should be noted that, for the RRC connection restoration request sent by the terminal, the network side device may select to restore the previously suspended RRC connection or establish a new RRC connection. Therefore, if the RRC connection request message is represented as an RRC connection restoration request message, the RRC connection confirmation message may also be represented as an RRC connection setup message or an RRC connection reestablishment message.

And step 3, the terminal sends an RRC connection completion message to the network side equipment.

In practical applications, after completing the RRC connection, the terminal may send an RRC connection Complete (rrcconnectioncomplete) message to the network side device to inform the network side device that the RRC connection is completed.

It should be understood that the detailed representation of the RRC connection complete message corresponds to the detailed representation of the RRC connection confirm message. That is, if the RRC Connection confirm message is expressed as an RRC Connection Resume message, the RRC Connection Complete message may be expressed as an RRC Connection Resume Complete (RRC Connection Resume Complete) message; if the RRC connection Complete message is expressed as an RRC connection setup message, the RRC connection Complete message may be expressed as an RRC connection setup Complete (RRC connection setup Complete) message; if the RRC Connection Complete message is represented as an RRC Connection Reestablishment message, the RRC Connection Complete message may be represented as an RRC Connection Reestablishment Complete (RRC Connection request Complete) message.

The processing method of the embodiment of the present invention will be explained below.

It should be noted that, in the embodiment of the present invention, for a PDCP entity that is established before the RRC connection control procedure, it may be referred to as a first PDCP entity; for the established PDCP entity in the RRC connection control procedure, it may be referred to as a second PDCP entity.

Referring to fig. 3, fig. 3 is a second flowchart of a processing method according to an embodiment of the invention. As shown in fig. 3, the processing method of the present embodiment includes the following steps:

step 301, in the RRC connection control procedure, if a preset condition is met, a PDCP entity of the target RB is established according to the stored context information of the terminal.

It should be noted that, in this embodiment, when the terminal meets the preset condition, a new PDCP entity may be established for the target RB according to the stored terminal context information, that is, the PDCP entity of the target RB is reconstructed according to the stored terminal context information. Further, the PDCP state of the new PDCP entity may be recovered to the PDCP state before the RRC connection control procedure, that is, the newly established PDCP state of the PDCP entity may be configured (or referred to as recovered) according to the PDCP state of the PDCP entity established before the RRC connection control procedure.

The terminal context information may be the terminal context information corresponding to the first PDCP entity that is established before the RRC connection control procedure.

In a specific implementation, the terminal may store the terminal context information before sending the RRC connection request message. For example, in the RRC connection recovery procedure, the terminal may store (or is called to retain) the terminal context information after receiving the RRC connection release message sent by the network side device and before sending the RRC connection recovery request message.

Specifically, the terminal context information corresponding to the first PDCP entity may include at least one of: first RRC configuration information of the first PDCP entity, PDCP status information of the first PDCP entity.

Further, the PDCP status information of the first PDCP entity may include at least one of: header compression state information of the first PDCP entity, and state variable state information of a receive window and a transmit window of the first PDCP entity.

In this way, under the condition that the terminal context information corresponding to the first PDCP entity includes the first RRC configuration information of the first PDCP entity, the terminal may establish a new PDCP entity for the target RB according to the first RRC configuration information, so as to speed up the establishment of the new PDCP entity.

Under the condition that the context information of the terminal corresponding to the first PDCP entity includes the PDCP state information of the first PDCP entity, the terminal can restore the PDCP state of the new PDCP entity to the state before the RRC connection control procedure according to the PDCP state information of the first PDCP entity, so that the efficiency of data transmission after RRC connection can be improved.

In practical applications, the network side device may instruct the terminal to resume the previously suspended RRC connection, or may instruct the terminal to establish a new RRC connection, which may be specifically determined according to a type of an RRC connection confirmation message sent by the network side device.

If the RRC connection confirmation message is an RRC connection resume message, the terminal and the network side device may resume the previously suspended RRC connection. In this scenario, the terminal may establish a new PDCP entity according to the first RRC configuration information of the first PDCP entity.

If the RRC connection confirmation message is an RRC connection setup message or an RRC connection reestablishment message, the terminal and the network side device may establish a new RRC connection. In this scenario, the terminal may establish a new PDCP entity according to RRC configuration information sent by the network side device.

Therefore, in an embodiment, optionally, the establishing a packet data convergence protocol PDCP entity of the target radio bearer RB according to the stored terminal context information includes:

deleting the first PDCP entity of the target RB;

establishing a second PDCP entity of the target RB;

recovering the PDCP state of the second PDCP entity according to the PDCP state information in the context information of the terminal;

the first PDCP entity is a PDCP entity established before the RRC connection control procedure, and the terminal context information is terminal context information corresponding to the first PDCP entity. Therefore, it can be understood that the PDCP state in the terminal context information is the PDCP state of the first PDC entity, and the first RRC configuration information in the terminal context information is the first RRC configuration information of the first PDCP entity.

In this embodiment, further, the establishing the second PDCP entity of the target RB includes:

establishing a second PDCP entity of the target RB according to first RRC configuration information in the terminal context information; alternatively, the first and second electrodes may be,

and establishing a second PDCP entity of the target RB according to the received second RRC configuration information.

It should be understood that the second RRC configuration information is sent by the network side device.

Wherein, whether the terminal establishes the second PDCP entity according to the first RRC configuration information or the second configuration information may be determined according to a type of the RRC connection confirmation message.

Specifically, if the RRC connection confirmation message is an RRC connection recovery message, the terminal may establish the second PDCP entity according to the stored first RRC configuration information. Therefore, the network side equipment is not required to send RRC configuration information, signaling overhead can be saved, and the establishment speed of the PDCP entity can be increased.

If the RRC connection confirmation message is an RRC connection setup message or an RRC connection reestablishment message, the terminal may establish the second PDCP entity according to the second RRC configuration message.

In this embodiment, the terminal recovers the PDCP state of the second PDCP entity according to the PDCP state information in the context information of the terminal, and recovers the PDCP state of the second PDCP entity to a state before an RRC connection control procedure, such as a state before suspension of an RRC connection, so as to improve efficiency of data transmission after the RRC connection is completed.

It should be noted that, in the case that the terminal context information corresponding to the first PDCP entity does not include the PDCP state information of the first PDCP entity, the PDCP state of the second PDCP entity may be configured by the network side device or read from the protocol, which may be specifically determined according to actual needs, and the embodiment of the present invention does not limit this.

In practical application, when the COUNT value of the first PDCP entity is reset, that is, the COUNT value is restored to an initial value (e.g., 0), both the transmission data and the reception data of the first PDCP entity cannot be retained, and at this time, the packet data convergence protocol PDCP entity of the target RB may be established according to the stored context information of the terminal.

In addition, the terminal may trigger the COUNT value of the first PDCP entity to perform a reset operation when receiving the RRC connection confirm message or the first indication information for indicating to restore the COUNT value of the first PDCP entity to the initial value.

Therefore, optionally, the meeting of the preset condition includes at least one of:

receiving an RRC connection recovery message;

receiving an RRC connection establishment message;

receiving an RRC connection reestablishment message;

receiving first indication information, wherein the first indication information is used for indicating that the count value of the first PDCP entity is restored to an initial value;

the counting value of the first PDCP entity is restored to an initial value;

wherein the first PDCP entity is a PDCP entity established before the RRC connection control procedure.

That is, if the terminal satisfies any of the above conditions, the packet data convergence protocol PDCP entity of the target RB may be established according to the stored context information of the terminal.

Optionally, after the establishing the packet data convergence protocol PDCP entity of the target radio bearer RB, the method further includes:

if the second indication information is received, controlling the established PDCP entity to perform header compression according to robust header compression (ROHC) context information in the context of the terminal;

wherein the second indication information is used for indicating header compression according to ROHC context information.

The established PDCP entity may be understood as a second PDCP entity.

In this step, if the network side device indicates to continue using the ROHC (Robust Header Compression) context information, the second PDCP entity of the terminal may continue using the ROHC context information in the stored terminal context information, and perform Header Compression according to the ROHC context information, thereby increasing the rate of Header decompression.

In this embodiment, the target RB may be represented as a suspended RB. In this scenario, optionally, the target RB includes at least one of: SRBs, data radio bearers DRBs in addition to the signaling radio bearer SRB0 and SRB 1. That is, the target RB may be any SRB other than SRB0 and SRB1, or any DRB.

In addition, for the RRC connection establishment procedure or the RRC connection reestablishment procedure, the target RB may be any SRB or any DRB.

It should be noted that, in this embodiment, after the packet data convergence protocol PDCP entity of the target radio bearer RB is established according to the stored terminal context information, the terminal may delete the stored terminal context information and release the storage memory.

In the processing method of this embodiment, in the RRC connection control procedure of radio resource control, if the terminal meets the preset condition, the PDCP entity of the packet data convergence protocol of the target RB is established according to the stored context information of the terminal. On one hand, a solution is provided for the processing behavior of the PDCP entity of the target RB in the RRC connection control flow; on the other hand, the terminal establishes the PDCP entity of the target RB according to the stored context information of the terminal, so that the efficiency of data transmission after the RRC connection is completed can be improved.

It should be noted that, various optional implementations described in the embodiments of the present invention may be implemented in combination with each other or implemented separately, and the embodiments of the present invention are not limited thereto.

For convenience of understanding, the RRC connection control procedure is exemplified as an RRC connection recovery procedure.

Step 0: and the network side equipment suspends the RRC connection of the UE, controls the UE to enter an INACTIVE state and sends an RRC connection release message to the UE.

After receiving the message, the UE retains the UE Context (UE Context) information.

The UE Context information may include at least one of:

current RRC configuration information;

current security context information;

a PDCP state, further, the PDCP state may include an ROHC state;

SDAP configuration information;

C-RNTI of source PCell;

cell identification information of the source PCell.

In addition, the UE may suspend all SRBs and DRBs except for SRB 0.

Step 1: the UE transmits an RRC connection restoration request message when it is necessary to restore the RRC connection. At this time, the UE restores the "RRC configuration information" and the "security context information" from the stored UE context. The UE restores the PDCP state of the SRB1, reconstructs the SRB and restores the data transceiving of the SRB 1.

Step 2: and the UE receives the RRC connection recovery message sent by the network side equipment. The UE's operations on suspended SRBs (e.g., SRBs 2, SRBs 3) and/or DRBs include:

a PDCP entity deleting these RBs;

establishing a new PDCP entity for the RBs by using the stored UE context information;

the state of the new PDCP entities (e.g., header compression protocol context information) of these RBs is restored with the stored UE context information.

In addition, if the network side device indicates that the ROHC context continues to be used, the PDCP entity of the UE continues to use the ROHC context in the UE context that was previously stored.

And step 3: the UE deletes its stored UE context.

The above embodiment has at least the following points:

when the COUNT value of the PDCP entity of the UE is to be reset, the UE may delete the established PDCP entity, then establish a new PDCP entity using the stored UE Context information, and restore the PDCP state of the new PDCP entity to the state before the RRC connection is suspended using the stored UE Context information.

The above embodiment has at least the following beneficial effects:

and establishing a new PDCP entity through the UE Context information stored in the INACTIVE state, initializing the COUNT value of the PDCP entity, and recovering the PDCP state of the new PDCP entity to the state before the suspension of the RRC connection through the stored UE Context information. Therefore, the UE can process and delete the data reserved in the PDCP entity in the suspended state, the data loss in the PDCP entity in the suspended state is prevented, the PDCP state of the new PDCP entity is recovered to the state before the RRC connection is suspended, and the efficiency of data transmission after the connection recovery is higher.

Referring to fig. 4, fig. 4 is a diagram illustrating a structure of a terminal according to an embodiment of the present invention. As shown in fig. 4, the terminal 400 includes:

a building module 401, configured to build a packet data convergence protocol PDCP entity of the target radio bearer RB according to the stored terminal context information if a preset condition is met in the RRC connection control procedure of radio resource control.

In addition to fig. 4, a description will be given below of modules included in the terminal 400 and 4 units included in each module.

Optionally, the establishing module 401 includes:

a deleting unit, configured to delete the first PDCP entity of the target RB if a preset condition is met in a radio resource control RRC connection control procedure;

a establishing unit, configured to establish a second PDCP entity of the target RB;

a recovering unit, configured to recover a PDCP state of the second PDCP entity according to PDCP state information in the context information of the terminal;

the first PDCP entity is a PDCP entity established before the RRC connection control procedure, and the terminal context information is terminal context information corresponding to the first PDCP entity.

Optionally, the establishing module 401 is specifically configured to:

Optionally, the meeting the preset condition includes at least one of:

receiving an RRC connection recovery message;

receiving an RRC connection establishment message;

receiving an RRC connection reestablishment message;

the counting value of the first PDCP entity is restored to an initial value;

Optionally, as shown in fig. 4, the terminal 300 further includes:

the control module is used for controlling the established PDCP entity to carry out header compression according to robust header compression (ROHC) context information in the context of the terminal if second indication information is received after the PDCP entity of the target Radio Bearer (RB) is established;

Optionally, the target RB includes at least one of: SRBs, data radio bearers DRBs in addition to the signaling radio bearer SRB0 and SRB 1.

The terminal 400 can implement each process in the method embodiment of the present invention and achieve the same beneficial effects, and is not described herein again to avoid repetition.

Referring to fig. 5, fig. 5 is a second structural diagram of a terminal according to a second embodiment of the present invention, where the terminal may be a hardware structural diagram of a terminal for implementing various embodiments of the present invention. As shown in fig. 5, terminal 500 includes, but is not limited to: a radio frequency unit 501, a network module 502, an audio output unit 503, an input unit 504, a sensor 505, a display unit 506, a user input unit 507, an interface unit 508, a memory 509, a processor 510, and a power supply 511. Those skilled in the art will appreciate that the terminal configuration shown in fig. 5 is not intended to be limiting, and that the terminal may include more or fewer components than shown, or some components may be combined, or a different arrangement of components. In the embodiment of the present invention, the terminal includes, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palm computer, a vehicle-mounted terminal, a wearable device, a pedometer, and the like.

Wherein, the processor 510 is configured to:

Optionally, the processor 510 is further configured to:

deleting the first PDCP entity of the target RB;

establishing a second PDCP entity of the target RB;

Optionally, the processor 510 is further configured to:

Optionally, the meeting the preset condition includes at least one of:

receiving an RRC connection recovery message;

receiving an RRC connection establishment message;

receiving an RRC connection reestablishment message;

the counting value of the first PDCP entity is restored to an initial value;

Optionally, the processor 510 is further configured to:

It should be noted that, in this embodiment, the terminal 500 may implement each process in the method embodiment of the present invention and achieve the same beneficial effects, and for avoiding repetition, details are not described here again.

It should be understood that, in the embodiment of the present invention, the radio frequency unit 501 may be used for receiving and sending signals during a message sending and receiving process or a call process, and specifically, receives downlink data from a base station and then processes the received downlink data to the processor 510; in addition, the uplink data is transmitted to the base station. In general, radio frequency unit 501 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit 501 can also communicate with a network and other devices through a wireless communication system.

The terminal provides wireless broadband internet access to the user through the network module 502, such as helping the user send and receive e-mails, browse web pages, access streaming media, and the like.

The audio output unit 503 may convert audio data received by the radio frequency unit 501 or the network module 502 or stored in the memory 509 into an audio signal and output as sound. Also, the audio output unit 503 may also provide audio output related to a specific function performed by the terminal 500 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output unit 503 includes a speaker, a buzzer, a receiver, and the like.

The input unit 504 is used to receive an audio or video signal. The input Unit 504 may include a Graphics Processing Unit (GPU) 5041 and a microphone 5042, and the Graphics processor 5041 processes image data of a still picture or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The processed image frames may be displayed on the display unit 506. The image frames processed by the graphic processor 5041 may be stored in the memory 509 (or other storage medium) or transmitted via the radio frequency unit 501 or the network module 502. The microphone 5042 may receive sounds and may be capable of processing such sounds into audio data. The processed audio data may be converted into a format output transmittable to a mobile communication base station via the radio frequency unit 501 in case of the phone call mode.

The terminal 500 also includes at least one sensor 505, such as light sensors, motion sensors, and other sensors. Specifically, the light sensor includes an ambient light sensor that adjusts the brightness of the display panel 5061 according to the brightness of ambient light, and a proximity sensor that turns off the display panel 5061 and/or a backlight when the terminal 500 is moved to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally three axes), detect the magnitude and direction of gravity when stationary, and can be used to identify the terminal posture (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration identification related functions (such as pedometer, tapping), and the like; the sensors 505 may also include fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc., which are not described in detail herein.

The display unit 506 is used to display information input by the user or information provided to the user. The Display unit 506 may include a Display panel 5061, and the Display panel 5061 may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like.

The user input unit 507 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the terminal. Specifically, the user input unit 507 includes a touch panel 5071 and other input devices 5072. Touch panel 5071, also referred to as a touch screen, may collect touch operations by a user on or near it (e.g., operations by a user on or near touch panel 5071 using a finger, stylus, or any suitable object or attachment). The touch panel 5071 may include two parts of a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 510, and receives and executes commands sent by the processor 510. In addition, the touch panel 5071 may be implemented in various types such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. In addition to the touch panel 5071, the user input unit 507 may include other input devices 5072. In particular, other input devices 5072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail herein.

Further, the touch panel 5071 may be overlaid on the display panel 5061, and when the touch panel 5071 detects a touch operation thereon or nearby, the touch operation is transmitted to the processor 510 to determine the type of the touch event, and then the processor 510 provides a corresponding visual output on the display panel 5061 according to the type of the touch event. Although in fig. 5, the touch panel 5071 and the display panel 5061 are two independent components to implement the input and output functions of the terminal, in some embodiments, the touch panel 5071 and the display panel 5061 may be integrated to implement the input and output functions of the terminal, and is not limited herein.

The interface unit 508 is an interface for connecting an external device to the terminal 500. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The interface unit 508 may be used to receive input (e.g., data information, power, etc.) from external devices and transmit the received input to one or more elements within the terminal 500 or may be used to transmit data between the terminal 500 and external devices.

The memory 509 may be used to store software programs as well as various data. The memory 509 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the memory 509 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device.

The processor 510 is a control center of the terminal, connects various parts of the entire terminal using various interfaces and lines, and performs various functions of the terminal and processes data by operating or executing software programs and/or modules stored in the memory 509 and calling data stored in the memory 509, thereby performing overall monitoring of the terminal. Processor 510 may include one or more processing units; preferably, the processor 510 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into processor 510.

The terminal 500 may further include a power supply 511 (e.g., a battery) for supplying power to various components, and preferably, the power supply 511 may be logically connected to the processor 510 through a power management system, so that functions of managing charging, discharging, and power consumption are performed through the power management system.

In addition, the terminal 500 includes some functional modules that are not shown, and are not described in detail herein.

Preferably, an embodiment of the present invention further provides a terminal, including a processor 510, a memory 509, and a computer program stored in the memory 509 and capable of running on the processor 510, where the computer program, when executed by the processor 510, implements each process of the processing method embodiment, and can achieve the same technical effect, and details are not repeated here to avoid repetition.

The embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements each process of the processing method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.

While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.

Claims

1. A processing method applied to a terminal is characterized by comprising the following steps:

2. The method of claim 1, wherein the establishing a packet data convergence protocol PDCP entity of the target radio bearer RB according to the stored terminal context information comprises:

deleting the first PDCP entity of the target RB;

establishing a second PDCP entity of the target RB;

3. The method of claim 2, wherein the establishing the second PDCP entity of the target RB comprises:

4. The method according to claim 1, wherein the predetermined condition is satisfied includes at least one of:

receiving an RRC connection recovery message;

receiving an RRC connection establishment message;

receiving an RRC connection reestablishment message;

the counting value of the first PDCP entity is restored to an initial value;

5. The method of claim 1, wherein after establishing the packet data convergence protocol PDCP entity of the target radio bearer RB, further comprising:

6. The method of claim 1, wherein the target RB comprises at least one of: SRBs, data radio bearers DRBs in addition to the signaling radio bearer SRB0 and SRB 1.

7. A terminal, comprising:

8. The terminal of claim 7, wherein the establishing module comprises:

9. The terminal according to claim 8, wherein the establishing unit is specifically configured to:

10. The terminal according to claim 7, wherein the predetermined condition is satisfied includes at least one of:

receiving an RRC connection recovery message;

receiving an RRC connection establishment message;

receiving an RRC connection reestablishment message;

the counting value of the first PDCP entity is restored to an initial value;

11. The terminal of claim 7, further comprising:

12. The terminal of claim 7, wherein the target RB comprises at least one of: SRBs, data radio bearers DRBs in addition to the signaling radio bearer SRB0 and SRB 1.

13. A terminal, characterized in that it comprises a processor, a memory and a computer program stored on the memory and executable on the processor, the computer program, when executed by the processor, implementing the steps of the processing method according to any one of claims 1 to 6.

14. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, carries out the steps of the processing method of one of claims 1 to 6.