WO2011017850A1

WO2011017850A1 - Control method for data processing, service node and terminal equipment

Info

Publication number: WO2011017850A1
Application number: PCT/CN2009/073266
Authority: WO
Inventors: 李亚娟; 常俊仁
Original assignee: 华为技术有限公司
Priority date: 2009-08-14
Filing date: 2009-08-14
Publication date: 2011-02-17
Also published as: CN102239720A

Abstract

A control method for data processing, a service node and a terminal equipment are disclosed by the present invention. The method includes that: configuration information to be used is obtained, said configuration information is at least one of the following items, which includes length of Packet Data Convergence Protocol(PDCP) sequence number to be used and convergence number of each PDCP data packet to be used (11); said configuration information to be used is sent to terminal equipment, said terminal equipment is instructed to modify currently-used configuration according to said configuration information to be used (12). The method of the present invention enables terminal equipment to obtain configuration information to be used, is convenient for user equipment to modify its currently-used configuration, and provides necessary basis for subsequent correct data processing.

Description

Data processing control method, service node and terminal device

Technical field

The present invention relates to wireless communication technologies, and in particular, to a data processing control method, a service node, and a terminal device. Background technique

The uplink and downlink peak rates of the Long Term Evolution Advanced (LTE-A) system are 500 Mbps and 1 Gbps, respectively, and the uplink and downlink peak rates of the Long Term Evolution (LTE) system are 50 Mbps and 100 Mbps, respectively. Due to the increase in data transmission rate, a larger number of Packet Data Convergence Protocol (PDCP) Service Data Units (SDUs) need to be generated in a short period of time. In the current LTE system, the PDCP serial number is 12 bits, that is, the serial number ranges from 0 to 4095. In the LTE-A system, in order to support a larger number of PDCP SDUs, the following two methods can be used: One is to extend the length of the PDCP sequence number, for example, the PDCP sequence number can be increased to 14 bits; the second is in PDCP. The layer adds a packet aggregation function to aggregate multiple PDCP SDUs into one PDCP data packet, which is equivalent to using a PDCP sequence number in association with multiple PDCP SDUs. The configuration used is fixed and the configuration is not flexible enough. Especially when the user equipment (User Equipment, UE) switches from one system to another system with different configurations, the configuration of the new system may be different from the original system. For example, when the UE is handed over from the LTE-A system to the LTE system, the length of the PDCP sequence number of the LTE system or/and the number of PDCP SDUs aggregated in each PDCP data packet may change, resulting in data mismatch after UE handover. And other issues. Summary of the invention

An embodiment of the present invention provides a data processing control method, a service node, and a terminal device. In order to enable the UE to obtain configuration information different from the current configuration, it is convenient for the UE to change the configuration that is used by the UE.

An embodiment of the present invention provides a data processing control method, including:

Obtaining configuration information to be used, the to-be-used configuration information is at least one of the following items: length of the packet data convergence protocol sequence number to be used, and each packet data convergence protocol packet to be used Number of aggregates;

Sending the to-be-used configuration information to the terminal device, to instruct the terminal device to modify the currently used configuration according to the configuration information to be used.

The embodiment of the invention further provides a data processing control method, including:

Receiving configuration information to be used, the configuration information to be used is at least one of the following items: length of the packet data convergence protocol sequence number to be used, and each packet data convergence protocol packet to be used Number of aggregates;

The current configuration is changed according to the configuration information to be used.

The embodiment of the invention further provides a service node, including:

An obtaining module, configured to obtain configuration information to be used, where the configuration information to be used is at least one of the following items: length of a packet data convergence protocol sequence number to be used, and each packet to be used The number of aggregates of data aggregation protocol packets;

And a sending module, configured to send the to-be-used configuration information to the terminal device, to instruct the terminal device to modify the currently used configuration according to the to-be-used configuration information.

The embodiment of the invention further provides a terminal device, including:

a receiving module, configured to receive configuration information to be used, where the configuration information to be used is at least one of the following: a length of a packet data convergence protocol sequence number to be used, and each packet to be used The number of aggregates of data aggregation protocol packets;

The change module is configured to change the currently used configuration according to the configuration information to be used. According to the foregoing technical solution, the embodiment of the present invention enables the terminal device to obtain the configuration information to be used, so that the UE can change the configuration of the user, thereby providing necessary information for subsequent correct data processing. Foundation. DRAWINGS

1 is a schematic flow chart of a method according to a first embodiment of the present invention;

2 is a schematic flow chart of a method according to a second embodiment of the present invention;

3 is a schematic flow chart of a method according to a third embodiment of the present invention;

4 is a schematic flow chart of a method according to a fourth embodiment of the present invention;

FIG. 5 is a schematic flowchart of a method according to a fifth embodiment of the present invention; FIG.

6 is a schematic flow chart of a method according to a sixth embodiment of the present invention;

7 is a schematic flow chart of a method according to a seventh embodiment of the present invention;

8 is a schematic flow chart of a method according to an eighth embodiment of the present invention;

9 is a schematic diagram of PDCP AM Data PDU format signaling used in an eighth embodiment of the present invention;

10 is a schematic diagram of carrying a PDCP sequence number by using PDCP AM Data PDU format signaling in an eighth embodiment of the present invention;

11 is a schematic diagram of the number of aggregated PDCP data packets carried by the PDCP AM Data PDU format signaling according to the eighth embodiment of the present invention;

FIG. 12 is a schematic diagram of PDCP Control PDU format signaling used in an eighth embodiment of the present invention; FIG.

13 is a schematic diagram of carrying a PDCP sequence number by using PDCP Control PDU format signaling in an eighth embodiment of the present invention;

14 is a schematic diagram of the number of aggregated PDCP data packets carried by the PDCP Control PDU format signaling in the eighth embodiment of the present invention;

15 is a schematic flow chart of a method according to a ninth embodiment of the present invention;

16 is a schematic structural diagram of a service node according to a tenth embodiment of the present invention;

FIG. 17 is a schematic structural diagram of a terminal device according to an eleventh embodiment of the present invention. Detailed ways

The technical solution of the present invention will be further described in detail below through the accompanying drawings and embodiments. In an implementation manner, when the UE has a handover, the source system is an LTE-A system (the corresponding device is a source eNB), the target system is an LTE system (the corresponding device is a target eNB), and the terminal device is a UE. Be explained. It can be understood that the solution of the following embodiments can also be applied to other scenarios in which the UE configuration is changed when no handover occurs, where the configuration information is: the length of the PDCP sequence number of the target system or/and each PDCP of the target system. The number of aggregates of SDUs. If there is no special case, the term "configuration" mentioned in the embodiment of the present invention refers to: the length setting of the PDCP sequence number and/or the aggregation number setting of the PDCP SDU.

FIG. 1 is a schematic flowchart of a method according to a first embodiment of the present invention, including:

Step 11: The service node obtains configuration information to be used, and the configuration information to be used is at least one of the following items: length of the PDCP sequence number to be used, and each PDCP data packet to be used. Number of aggregates;

Step 12: The service node sends the to-be-used configuration information to the terminal device, to instruct the terminal device to change the currently used configuration according to the to-be-used configuration information.

The foregoing is the behavior described from the eNB side. For the UE side, the following operations are performed: Step A: The UE receives the configuration information to be used, and the configuration information to be used is at least one of the following items: The length of the PDCP sequence number used, and the number of aggregated PDCP packets to be used;

Step B: The UE changes the currently used configuration according to the configuration information to be used. In this embodiment, the terminal device obtains the configuration information to be used, and provides a necessary basis for subsequent correct data processing. Specifically, the terminal device can conveniently obtain the configuration information to be used, and change the length of the PDCP sequence number or the number of aggregates of each PDCP data packet according to the configuration information to be used, so that the PDCP in the terminal device is changed. The data is configured in a more flexible manner. In this embodiment, the serving node may be a base station (eNB) or a relay node (RN). In order to improve the signaling efficiency, the embodiment of the present invention can use the following methods:

2 is a schematic flowchart of a method according to a second embodiment of the present invention, including:

Step 21: The source eNB determines whether it needs to switch to the target eNB with different configuration information. If yes, go to step 22. Otherwise, go to step 21. The configuration information is at least one of the following: a length of a PDCP sequence number, and an aggregated number of each PDCP data packet.

Step 22: When it is required to switch to the target eNB with different configuration information, the source eNB obtains the configuration information of the target eNB by using the configuration information of the target eNB in association with the target eNB, and uses the configuration information of the target eNB as the configuration information to be used.

Step 23: The source eNB sends the to-be-used configuration information to the UE.

Afterwards, the UE may perform the following steps: The UE receives configuration information to be used, and the configuration information to be used is at least one of the following items: length of the PDCP sequence number to be used, and each to be used The number of aggregated PDCP data packets; the UE changes the currently used configuration according to the configuration information to be used.

In this embodiment, the UE obtains the configuration information of the target eNB, so that the UE can obtain the configuration information of the target eNB, which facilitates the UE to modify the configuration of the target eNB, and provides a necessary basis for subsequent correct data processing. In this embodiment, after determining that the system needs to be switched to a different configuration, the corresponding configuration information is obtained, so that signaling efficiency can be improved and resource waste can be avoided.

3 is a schematic flowchart of a method according to a third embodiment of the present invention. The difference from the second embodiment is that the present embodiment can be applied to a scenario in which an RN exists, including:

Step 31: The RN determines whether it is necessary to switch to the target eNB with different configuration information. If yes, go to step 32. Otherwise, repeat step 31. The configuration information is at least one of the following: a length of the PDCP sequence number, and an aggregated number of each PDCP data packet.

Step 32: The RN sends an indication message to the source eNB, and informs the source eNB that it needs to switch to a target eNB with different configuration information.

Step 33: The source eNB obtains the configuration information of the target eNB by negotiating with the target eNB, and uses the configuration information of the target eNB as the configuration information to be used. Step 34: The source eNB sends the configuration information to be used to the RN.

Step 35: The RN sends the configuration information to be used to the UE.

The above steps may also be substituted for the above steps 34-35: The source eNB directly transmits the configuration information of the target eNB to the UE.

Of course, the following steps may be used instead of the above step 31: The source eNB determines that it is necessary to switch to a target eNB with different configuration information. Alternatively, the source eNB and the RN jointly determine that handover to a target eNB having different configuration information is required.

In this embodiment, the UE obtains the configuration information of the target eNB, so that the UE can obtain the configuration information of the target eNB, which facilitates the UE to modify the configuration of the target eNB, and provides a necessary basis for subsequent correct data processing. In this embodiment, after determining that the system needs to be switched to a different configuration, the corresponding configuration information is obtained, so that signaling efficiency can be improved and resource waste can be avoided. In this embodiment, the RN can perform the handover judgment or the configuration information forwarding, which can improve the application scope of the solution of the embodiment of the present invention.

In the foregoing second embodiment and the third embodiment, there are two base stations, and the UE needs to use new configuration information when switching between two base stations; or there may be one base station, when the network status of the system changes (or reaches The trigger condition of the PDCP layer) requires the use of new configuration information.

4 is a schematic flow chart of a method according to a fourth embodiment of the present invention, including:

Step 41: The serving eNB determines whether the preset trigger condition is reached. If yes, go to step 42, otherwise, repeat step 41. Trigger conditions include, but are not limited to, the following: Service rate requirements, channel conditions, or base station load conditions.

Step 42: The serving eNB obtains the configuration information corresponding to the triggered condition that is obtained, and uses the configuration information corresponding to the obtained trigger condition as the configuration information to be used. Specifically, the corresponding relationship between the triggering condition and the configuration information may be set in the serving eNB, and the new configuration information may be acquired according to the corresponding relationship. Interest. The configuration information is at least one of the following: a length of the PDCP sequence number, and an aggregated number of each PDCP data packet.

Step 43: The serving eNB sends the configuration information corresponding to the trigger condition to the UE.

In this embodiment, the UE obtains the configuration information corresponding to the triggering condition, so that the UE can obtain the configuration information of the target eNB, which is convenient for the UE to modify the configuration of the eNB, and provides a necessary basis for subsequent correct data processing. In this embodiment, after determining that the trigger condition is met, the corresponding configuration information is obtained, which can improve signaling efficiency and avoid resource waste.

In the foregoing embodiment, configuration information may be delivered by using different signaling.

FIG. 5 is a schematic flowchart of a method according to a fifth embodiment of the present invention, including:

Step 51: The source eNB obtains configuration information to be used, and the configuration information to be used is configuration information of the target eNB. For example, it can be obtained by means of negotiation between the source eNB and the target eNB.

Step 52: The source eNB carries the configuration information to be used in the radio resource control (RRC) signaling, and sends the configuration information to the UE, where the RRC signaling may be specifically a handover request indication message.

The RRC signaling is configuration or reconfiguration signaling, and part of the code in the RRC signaling in the ASN.1 format may be as follows. In the following code, compared with the prior art, it is required to be in the acknowledge mode (AM). An information element "ENUMERATED" is added to carry configuration information, where the configuration information represented by code 1 is the number of aggregates of each PDCP data packet of the LTE system, and code 2 The configuration information represented is the length of the PDCP sequence number of the LTE system. The names of the added information elements can be modified to others, and the listed values are just examples, and the listed values can be expanded or reduced.

Code one:

-ASN1 START

PDCP-Config::= SEQUENCE {

discardTimer ENUMERATED {

Ms50, mslOO, msl50, ms300, ms500 ms750, msl500, infinity

OPTIONAL, -Cond

Setup

rlc-AM SEQUENCE {

statusReportRequired BOOLEAN

pdcp-SDU-num-in-one-PDU ENUMERATED { 1 ,2,3,4}

OPTIONAL -Cond

Rlc-AM

rlc-UM SEQUENCE {

pdcp-SN-Size ENUMERATED {Ien7bits,lenl2bits}

} OPTIONAL, -Cond

Rlc-UM

headerCompression CHOICE{

notUsed NULL,

Rohc SEQUENCE!

maxCID INTEGER(1 · ..16383) DEFAULT 15, profiles SEQUENCE {

profileOxOOOl BOOLEAN,

Profile0x0002 BOOLEAN,

Profile0x0003 BOOLEAN,

Profile0x0004 BOOLEAN,

Profile0x0006 BOOLEAN, profileOxOlOl BOOLEAN:

Profile0x0102 BOOLEAN:

Profile0x0103 BOOLEAN:

Profile0x0104 BOOLEAN

-ASNl STOP

Code 2:

-ASNl START

PDCP-Config: := SEQUENCE {

discardTimer ENUMERATED {

Ms50, mslOO, msl50, ms300, ms500 ms750, msl500, infinity

OPTIONAL, -Cond

Setup

rlc-AM SEQUENCE {

statusReportRequired BOOLEAN

pdcp-SN-Size ENUMERATED{lenl2bits,lenl3bits, lenHbits}

} OPTIONAL, -Cond

Rlc-AM

rlc-UM SEQUENCE {

pdcp-SN-Size ENUMERATED {Ien7bits,lenl2bits}

} OPTIONAL, -Cond

Rlc-UM headerCompression CHOICE{

notUsed NULL,

Rohc SEQUENCE!

maxCID INTEGER(1...16383) DEFAULT 15 profiles SEQUENCE {

profileOxOOOl BOOLEAN,

Profile0x0002 BOOLEAN,

Profile0x0003 BOOLEAN,

Profile0x0004 BOOLEAN,

Profile0x0006 BOOLEAN,

profileOxOlOl BOOLEAN,

Profile0x0102 BOOLEAN,

Profile0x0103 BOOLEAN,

Profile0x0104 BOOLEAN,

},

}

-ASN1STOP

After the UE is configured according to the information, the UE may also return a configuration or reconfiguration complete message to the source eNB.

In this embodiment, the UE obtains the configuration information of the target eNB, so that the UE can modify the configuration of the target eNB to provide a necessary basis for subsequent correct data processing. In this embodiment, by configuring the configuration information in the RRC signaling, the limitation on the number of occupied bits of the configuration information can be reduced.

It can be understood that this embodiment can also be applied to the scenario where the RN exists, in the presence of the RN. For the specific procedure, refer to the third embodiment. For specific RRC signaling, refer to this embodiment.

When the UE is handed over from the source eNB to the target eNB, there may be a part of data that needs to be forwarded to the UE by the target eNB. Therefore, in the scenario where the source eNB needs to be handed over to the target eNB (including the scenario where the RN exists), the source eNB It is also possible to send a start indication information to the UE, where the start indication information is used to indicate from which PDCP data packet the UE starts to make the change.

FIG. 6 is a schematic flowchart of a method according to a sixth embodiment of the present invention, including:

Step 61: The source eNB obtains configuration information to be used, and the configuration information to be used is configuration information of the target eNB. For example, it can be obtained by means of negotiation between the source eNB and the target eNB.

Step 62: The source eNB sends a handover request indication message to the UE, where the handover request indication message carries the configuration information to be used and the change start indication information, where the handover request indication message is an RRC signaling. For the specific manner of carrying the configuration information in the RRC signaling, refer to the fifth embodiment. Since the handover request indication message in the embodiment needs to carry the change start indication information, an information element needs to be added in the RRC signaling. Used to carry the change start indication information.

Step 63: The source eNB and the UE start the PDCP data packet corresponding to the change start indication information, and perform data conversion according to the configuration information to be used. For example, the data is renumbered according to the length of the PDCP sequence number to be used or the aggregate size of the PDCP packet, so that the renumbered PDCP sequence number is within the range supported by the target eNB.

Step 64: The source eNB sends the data converted by the source eNB side to the target eNB.

Step 65: The target eNB forwards the converted data to the UE.

In this embodiment, by carrying the change start indication information, the requirement for correct data processing when the eNB is switched can be satisfied. FIG. 7 is a schematic flowchart of a method according to a seventh embodiment of the present invention, including:

Step 71: The serving eNB obtains configuration information to be used according to the trigger condition.

Step 72: The eNB carries the configuration information to be used in the RRC signaling, and sends the configuration information to the RRC signaling.

UE.

For the carrying manner of the configuration information in the RRC signaling, refer to the fifth embodiment, and details are not described herein.

In this embodiment, the UE obtains the configuration information corresponding to the triggering condition, so that the UE can obtain the configuration information of the target eNB, which is convenient for the UE to modify the configuration of the eNB, and provides a necessary basis for subsequent correct data processing. In this embodiment, by limiting the configuration information in the RRC signaling, the limitation on the number of occupied bits of the configuration information can be reduced.

FIG. 8 is a schematic flowchart of a method according to an eighth embodiment of the present invention, including:

Step 81: The serving eNB obtains configuration information to be used according to the trigger condition.

Step 82: The eNB carries the configuration information to be used in layer 2 signaling, and sends the configuration information to

UE.

Specifically, it can be:

Manner 1: The configuration information is carried in the reserved bit position of the PDCP AM Data PDU format. 9 is a schematic diagram of PDCP AM Data PDU format signaling used in the eighth embodiment of the present invention. Referring to FIG. 9, the PDCP AM Data PDU format signaling includes three reserved bits (using the R table). Show). These reserved bits can be used to carry configuration information.

FIG. 10 is a schematic diagram of carrying a PDCP sequence number by using PDCP AM Data PDU format signaling in an eighth embodiment of the present invention. Referring to Figure 10, if the length of the PDCP is only two, it can be represented by an R. For example, using SNID=0 means using a short PDCP sequence number, for example, a serial number of 12 bits; SNID=1 means 釆Use a long PDCP serial number, for example, a serial number of 14 bits in length.

FIG. 11 is a schematic diagram of the number of aggregated PDCP data packets carried by the PDCP AM Data PDU format signaling according to the eighth embodiment of the present invention. Referring to Figure 11, if there are four possibilities for the number of aggregated PDCP packets (represented by SDU num in Figure 11), then two Rs can be used.

In the first mode, the data resource blocks (RBs) in the AM mode can be separately controlled, that is, different RBs can be assigned the same or different PDCP sequence number lengths or the number of PDCP data packets aggregated.

Manner 2: The configuration information is carried in the reserved bit position of the PDCP Control PDU format. Figure 12 is a schematic diagram of PDCP Control PDU format signaling used in the eighth embodiment of the present invention. Referring to Figure 12, the PDCP AM Data PDU format signaling includes four reserved bits (denoted by R). These reserved bits can be used to carry configuration information.

FIG. 13 is a schematic diagram of carrying a PDCP sequence number by using PDCP Control PDU format signaling in the eighth embodiment of the present invention. Referring to Figure 13, if the length of the PDCP is only two, it can be represented by an R. For example, using SNID=0 means using a short PDCP sequence number, for example, a serial number of 12 bits in length; using SNID=1 to indicate 釆Use a long PDCP serial number, for example, a serial number of 14 bits in length.

FIG. 14 is a schematic diagram of the number of aggregated PDCP data packets carried by the PDCP Control PDU format signaling according to the eighth embodiment of the present invention. Referring to Figure 14, if there are four possibilities for the number of aggregated PDCP packets (represented by SDU num in Figure 14), then two Rs can be used.

In the second mode, the data resource block (RB) in the AM mode can be uniformly controlled, that is, different RBs can be allocated the same PDCP sequence number length or the number of PDCP data packets aggregated.

It can be understood that, in this embodiment, if the length of the PDCP sequence number and the PDCP data The number of aggregates of the packets changes at the same time, and the two types of configuration information are carried in the layer 2 signaling by combining the above-mentioned respective changes.

In this embodiment, the UE obtains the configuration information corresponding to the triggering condition, so that the UE can obtain the configuration information of the target eNB, which is convenient for the UE to modify the configuration of the eNB, and provides a necessary foundation for subsequent correct data processing. In this embodiment, the configuration information can be diversified by carrying the configuration information in the layer 2 signaling.

FIG. 15 is a schematic flowchart of a method according to a ninth embodiment of the present invention, including:

Step 151: The serving eNB obtains configuration information to be used according to the trigger condition.

Step 152: The serving eNB carries the configuration information to be used in the physical layer control channel, and sends the configuration information to the UE.

Specifically, the number of the bits occupied by the control layer of the physical layer is increased, so that the configuration information can be carried. For example, if the length of the PDCP sequence number needs to be carried, and the length of the PDCP is two possibilities, one bit needs to be added. If the number of packets to be aggregated is 4, and the number of aggregated PDCP packets is 4, you need to add two digits. If you need to carry the length of the PDCP sequence number and the number of PDCP packets, and the length of the PDCP sequence number is For both possibilities, there are 4 possibilities for the number of aggregated PDCP packets, and three more bits are required.

The configuration information carried in the physical layer control channel may be carried in each scheduling or only if there is a change.

In this embodiment, the UE obtains the configuration information corresponding to the triggering condition, so that the UE can obtain the configuration information of the target eNB, so that the UE can modify the configuration of the eNB, and provide a necessary basis for subsequent correct data processing. In this embodiment, the configuration information can be diversified by carrying the configuration information in the physical layer control channel. FIG. 16 is a schematic structural diagram of a service node according to a tenth embodiment of the present invention, which includes an obtaining module 161 and a sending module 162. The obtaining module 161 is configured to obtain configuration information to be used, where the configuration information to be used is at least one of the following items: a length of a PDCP sequence number to be used, and a PDCP data packet to be used. The sending module 162 is configured to send the to-be-used configuration information to the terminal device, to instruct the terminal device to modify the currently used configuration according to the to-be-used configuration information.

The obtaining module 161 includes a first determining unit and a second obtaining unit, or the obtaining module 161 includes a second determining unit and a second obtaining unit. The first determining unit is configured to determine whether it is required to switch to a target base station different from the currently used configuration information. The first obtaining unit is configured to determine, in the first determining unit, that the switch to the configuration information that is currently used is different. And obtaining, by the target base station, the configuration information of the target base station, and the configuration information of the target base station as the configuration information to be used; the second determining unit is configured to determine whether the preset trigger is reached. a condition that the triggering condition includes a service rate requirement, a channel condition, or a base station load condition. The second acquiring unit is configured to: when the second determining unit determines that the trigger condition is reached, configure information corresponding to the trigger condition. As the configuration information to be used.

The sending module 162 may include a first unit, a second unit, or a third unit that is connected to the acquiring module. The first unit is configured to carry the configuration information to be used in the RRC signaling, and send the configuration information to the terminal device. The second unit is configured to carry the configuration information to be used in the layer 2 signaling, and send the configuration information to the terminal device, where the third unit is configured to carry the configuration information to be used in the physical layer control channel, and send To the terminal device.

Specifically, the second unit may be specifically configured to carry the configuration information to be used in a reserved bit position of the PDCP AM Data PDU format; or the second unit may be specifically configured to use the configuration information to be used. The reserved bit position carried in the PDCP Control PDU format.

The configuration information in this embodiment is at least one of the following items: the length of the PDCP sequence number, and the number of each PDCP data packet.

The target system in this embodiment may be an LTE system. In this case, the service node in this embodiment may An evolved base station (eNB) that is an LTE or LTE-A system may also be an RN.

In this embodiment, the UE obtains the configuration information of the target eNB, so that the UE can obtain the configuration information of the target eNB, which facilitates the UE to modify the configuration of the target eNB, and provides a necessary basis for subsequent correct data processing.

FIG. 17 is a schematic structural diagram of a terminal device according to an eleventh embodiment of the present invention, including a receiving module 171 and a changing module 172. The receiving module 171 is configured to receive configuration information to be used, and the configuration information to be used is as follows: At least one of: a length of a PDCP sequence number to be used, and a number of aggregates of each PDCP data packet to be used; a change module 172 configured to configure the current configuration according to the configuration information to be used Make changes.

The receiving unit 171 may include a fourth unit, a fifth unit, or a sixth unit. The fourth unit is configured to receive the to-be-used configuration information carried in the RRC signaling, and the fifth unit is configured to receive the The to-be-used configuration information in the layer 2 signaling; the sixth unit is configured to receive the to-be-used configuration information carried in the physical layer control channel.

The UE in this embodiment obtains the configuration information to be used, so that the UE can change the configuration of the UE, which can provide a necessary basis for subsequent correct data processing.

A person skilled in the art can understand that all or part of the steps of implementing the above method embodiments may be completed by using hardware related to program instructions, and the foregoing program may be stored in a computer readable storage medium, and the program is executed when executed. The foregoing steps include the steps of the foregoing method embodiments; and the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

It should be noted that the above embodiments are only intended to illustrate the technical solutions of the present invention and are not to be construed as limiting the embodiments of the present invention. Modifications or equivalent substitutions may be made to the technical solutions of the present invention, and such modifications or equivalents may not detract from the technical solutions of the present invention.

Claims

Rights request

A control method for data processing, comprising:

The method according to claim 1, wherein the obtaining configuration information to be used comprises:

When the target base station that is different from the current configuration is required to be switched, the configuration information of the target base station is used as the configuration information to be used by using the configuration information of the target base station in cooperation with the target base station; or

When the preset trigger condition is reached, the configuration information corresponding to the trigger condition is used as configuration information to be used, and the trigger condition includes a service rate requirement, a channel status, or a base station load condition.

The method according to claim 1, wherein the sending the to-be-used configuration information to the terminal device comprises:

The configuration information to be used is carried in the RRC signaling, and is sent to the terminal device; or the configuration information to be used is carried in the layer 2 signaling and sent to the terminal device; or The configuration information to be used is carried in the physical layer control channel and sent to the terminal device.

The method according to claim 3, wherein the carrying the to-be-used configuration information in the layer 2 signaling includes:

Carrying the configuration information to be used in a reserved bit position of the PDCP AM Data PDU format; or

The configuration information to be used is carried in a reserved bit position of the PDCP Control PDU format.

5. The method of claim 3, wherein

The carrying the configuration information to be used in the RRC signaling includes:

And the configuration information to be used is carried in the handover indication message, where the handover indication message further carries the change start indication information;

The method further includes:

Starting with the PDCP data packet corresponding to the change start indication information, performing data conversion according to the configuration information to be used;

The converted data is sent to the target base station to be handed over, so that the target base station forwards the converted data to the terminal device.

6. A method of controlling data processing, comprising:

The method according to claim 6, wherein the receiving the configuration information to be used comprises:

Receiving the to-be-used configuration information carried in the RRC signaling; or

Receiving the to-be-used configuration information carried in the layer 2 signaling; or

Receiving the to-be-used configuration information carried in the physical layer control channel.

The method according to claim 7, wherein the receiving, by the layer 2 signaling, the to-be-used configuration information comprises:

Receiving the to-be-used configuration information carried in the reserved bit position of the PDCP AM Data PDU format; or

Receiving the to-be-used configuration information carried in the reserved bit position of the PDCP Control PDU format.

9. A service node, comprising: An obtaining module, configured to obtain configuration information to be used, where the configuration information to be used is at least one of the following items: length of a packet data convergence protocol sequence number to be used, and each packet to be used The number of aggregates of data aggregation protocol packets;

10. The service node of claim 9 wherein:

The obtaining module includes a first determining unit and a second acquiring unit, or the acquiring module includes a second determining unit and a second acquiring unit;

The first determining unit is configured to determine whether it is required to switch to a target base station different from the currently used configuration information;

The first obtaining unit is configured to: when the first determining unit determines that the target base station that is different from the currently used configuration information is to be switched, obtain the configuration information of the target base station by negotiating with the target base station, The configuration information of the target base station is used as configuration information to be used;

The second determining unit is configured to determine whether a preset trigger condition is reached, where the trigger condition includes a service rate requirement, a channel status, or a base station load condition;

The second obtaining unit is configured to: when the second determining unit determines that the trigger condition is reached, configure configuration information corresponding to the trigger condition as configuration information to be used.

11. A service node according to claim 9 or 10, characterized in that

The sending module includes a first unit, a second unit, or a third unit;

The first unit is configured to carry the configuration information to be used in the RRC signaling, and send the information to the terminal device.

The second unit is configured to carry the configuration information to be used in layer 2 signaling, and send the information to the terminal device.

The third unit is configured to carry the configuration information to be used in a physical layer control channel and send the configuration information to the terminal device.

12. A terminal device, comprising: a receiving module, configured to receive configuration information to be used, where the configuration information to be used is at least one of the following: a length of a packet data convergence protocol sequence number to be used, and each packet to be used The number of aggregates of data aggregation protocol packets;

The change module is configured to change the currently used configuration according to the configuration information to be used.

13. The terminal device according to claim 12, wherein

The receiving module includes a fourth unit, a fifth unit or a sixth unit;

The fourth unit is configured to receive the to-be-used configuration information that is carried in the RRC signaling; the fifth unit is configured to receive the to-be-used configuration information that is carried in the layer 2 signaling; The sixth unit is configured to receive the to-be-used configuration information carried in the physical layer control channel.