CN108234092A - A kind of signaling configuration method, RRC entities and PDCP entities - Google Patents
A kind of signaling configuration method, RRC entities and PDCP entities Download PDFInfo
- Publication number
- CN108234092A CN108234092A CN201611154862.5A CN201611154862A CN108234092A CN 108234092 A CN108234092 A CN 108234092A CN 201611154862 A CN201611154862 A CN 201611154862A CN 108234092 A CN108234092 A CN 108234092A
- Authority
- CN
- China
- Prior art keywords
- entity
- rlc
- rsn
- pdcp
- length
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 230000011664 signaling Effects 0.000 title claims abstract description 87
- 238000000034 method Methods 0.000 title claims abstract description 43
- 238000013507 mapping Methods 0.000 claims abstract description 79
- 230000005540 biological transmission Effects 0.000 claims description 15
- 238000012545 processing Methods 0.000 claims description 11
- 238000011217 control strategy Methods 0.000 claims description 8
- 230000006870 function Effects 0.000 description 24
- 239000000969 carrier Substances 0.000 description 4
- 238000013468 resource allocation Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 238000003672 processing method Methods 0.000 description 2
- 230000011218 segmentation Effects 0.000 description 2
- 238000013461 design Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012163 sequencing technique Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
- H04W80/02—Data link layer protocols
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a kind of signaling configuration method, RRC entities and PDCP entities, methods to include：Determine the mapping relations between PDCP entities and radio link protocol RLC entities；Wherein, being included at least in the mapping relations has the corresponding PDCP entities of each carrier wave and at least one RLC entities；Based on the mapping relations between the PDCP entities and the RLC entities, the first configuration signal is sent, and the second configuration signal is sent to the RLC entities to the PDCP entities.
Description
Technical Field
The present invention relates to signaling management technology in the field of communications, and in particular, to a signaling configuration method, an RRC entity, and a PDCP entity.
Background
The 5G network architecture provides a distributed architecture of an access network, air interface protocol stacks are respectively operated on different distributed entities, and transmission among the distributed entities is non-ideal transmission. Taking RCC-RRS distributed architecture (RCC: Radio cloud center, RRS: Radio Remote System) as an example, the transmission between RCC-RRS is non-ideal transmission, so the segmentation and reconstruction of the protocol stack function under the non-ideal transmission need to be considered.
In the prior art, protocol segmentation is carried out between PDCP and RLC, a reordering function of PDCP PDUs is added in a PDCP protocol function, and the function of RLC is kept unchanged. However, this solution has the following problems: 1. a whole set of in-sequence sending and receiving reordering mechanism is added in the PDCP protocol, and when 2, PDCP sequences through SN numbers of PDCP PDUs, PDCP PDUs transmitted by a plurality of RLC can be sequenced, which causes great complexity and prolongs sequencing time. 3. When reestablishing (reestablishment), because the transmission delay of each bearer air interface between the RLC and the PDCP is different, the SN number span corresponding to the PDU received by the PDCP is large, which brings challenges to the maintenance of the PDCP reordering window and the design of the reordering timer.
Disclosure of Invention
In view of the above, an object of the present invention is to provide a signaling configuration method, an RRC entity and a PDCP entity, which can at least solve the above problems in the prior art.
In order to achieve the purpose, the technical scheme of the invention is realized as follows:
the embodiment of the invention provides a signaling configuration method, which comprises the following steps:
determining a mapping relation between a PDCP entity and a radio link protocol RLC entity; wherein, the mapping relationship at least comprises a PDCP entity and at least one RLC entity corresponding to each carrier;
based on the mapping relation between the PDCP entity and the RLC entity, sending a first configuration signaling to the PDCP entity and sending a second configuration signaling to the RLC entity;
wherein, the first configuration signaling at least carries identification information of a carrier corresponding to the PDCP entity and identification information of at least one RLC entity corresponding to the carrier; the second configuration information at least carries identification information of a carrier corresponding to the RLC entity and identification information of the RLC entity.
The embodiment of the invention provides a signaling configuration method, which comprises the following steps:
receiving a first configuration signaling sent by an RRC entity;
and determining the identification information of the carrier corresponding to the first configuration signaling and the identification information of the corresponding at least one RLC entity based on the first configuration signaling.
An embodiment of the present invention provides an RRC entity, including:
a processing unit, configured to determine a mapping relationship between a PDCP entity and a radio link protocol RLC entity; wherein, the mapping relationship at least comprises a PDCP entity and at least one RLC entity corresponding to each carrier;
a signaling sending unit, configured to send a first configuration signaling to the PDCP entity and send a second configuration signaling to the RLC entity based on a mapping relationship between the PDCP entity and the RLC entity;
wherein, the first configuration signaling at least carries identification information of a carrier corresponding to the PDCP entity and identification information of at least one RLC entity corresponding to the carrier; the second configuration information at least carries identification information of a carrier corresponding to the RLC entity and identification information of the RLC entity.
The embodiment of the invention provides a PDCP entity, which is characterized by comprising the following components:
a signaling receiving unit, configured to receive a first configuration signaling sent by an RRC entity;
and a configuration unit, configured to determine, based on the first configuration signaling, identification information of a carrier corresponding to the configuration unit and identification information of at least one corresponding RLC entity.
The embodiment of the invention provides a signaling configuration method, an RRC entity and a PDCP entity, wherein the mapping relation of identification information of the PDCP entity and the RLC entity corresponding to each carrier is determined by the RRC entity side, and a first configuration signaling and a second configuration information are respectively sent to the PDCP entity and the RLC entity according to the mapping relation. Therefore, in a scene that the PDCP corresponds to a plurality of RLC entities, different network architectures can be adapted.
In addition, the sequence number length of the RLC entity can be set through the RRC entity, so that the reordering speed and accuracy are ensured when one PDCP entity manages a plurality of RLC entities and a data unit is sent.
Drawings
Fig. 1 is a first flowchart illustrating a signaling configuration method according to an embodiment of the present invention;
FIG. 2 is a first diagram illustrating a network architecture according to an embodiment of the present invention;
FIG. 3 is a second exemplary network architecture according to the present invention;
FIG. 4 is a third exemplary network architecture according to the present invention;
FIG. 5 is a schematic flow chart of configuration issuing to different entities and terminal devices according to an embodiment of the present invention;
fig. 6 is a flowchart illustrating a signaling configuration method according to a second embodiment of the present invention;
FIG. 7 is a schematic diagram of an RRC entity configuration according to an embodiment of the present invention;
FIG. 8 is a block diagram of a PDCP entity according to an embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and specific embodiments.
The first embodiment,
An embodiment of the present invention provides a signaling configuration method, which is applied to an RRC entity, and as shown in fig. 1, includes:
step 101: determining a mapping relation between a PDCP entity and a radio link protocol RLC entity; wherein, the mapping relationship at least comprises a PDCP entity and at least one RLC entity corresponding to each carrier;
step 102: based on the mapping relation between the PDCP entity and the RLC entity, sending a first configuration signaling to the PDCP entity and sending a second configuration signaling to the RLC entity;
wherein, the first configuration signaling at least carries identification information of a carrier corresponding to the PDCP entity and identification information of at least one RLC entity corresponding to the carrier; the second configuration information at least carries identification information of a carrier corresponding to the RLC entity and identification information of the RLC entity.
It should be noted that, as shown in fig. 2, fig. 3, and fig. 4, the network protocol layer architecture applied in this embodiment may be that an RCC (wireless cloud center) completes big data operation, and then sends an instruction to an RRS, and the RRS completes resource allocation of a corresponding air interface on the basis of an operation result of the RCC. Similarly, each RRS performs certain processing on information collected from the air interface and reports the processed information to the RCC. The RCC and the RRS adopt a flexible connection mode, in order to reduce the data transmission pressure between the RCC and the RRS, the functions between the RCC and the RRS can be flexibly divided, and the RCC and the RRS are connected through a transmission network. The reordering function of PDCP PDU is added in the PDCP protocol function, and the RLC function is kept unchanged. As can be seen from fig. 2, fig. 3 and fig. 4, one PDCP entity may correspond to one or more RLC entities, that is, one PDCP entity may manage a plurality of carriers, and each carrier may be assigned a mapping with one RLC entity.
In order to correctly receive and process information between protocol layers in the network structure, the embodiment provides a more suitable signaling configuration method.
The mapping relationship between the PDCP entities and the RLC entities is determined, specifically, identification information of a carrier corresponding to each PDCP entity is determined, and identification information of at least one RLC entity corresponding to each PDCP entity is determined. Through the mapping relationship, at least one RLC entity corresponding to each carrier can be determined.
Based on the mapping relationship, corresponding configuration information is generated respectively for the PDCP entity and the RLC entity, and then a first configuration signaling is sent to the PDCP entity and a second configuration signaling is sent to the RLC entity.
That is to say, the RRC entity configures a mapping relationship between the PDCP and the RLC, wherein the RRC may directly notify an RLC _ id of each RLC corresponding to the PDCP entity and notify an RLC configuration bearer id.
In order to ensure that the network side and the terminal side can normally receive information, corresponding configuration information is also sent to the terminal device according to the mapping relationship, specifically: and sending RRC connection reconfiguration information to the terminal equipment based on the mapping relation between the PDCP entity and the RLC entity, and indicating the identification information of each RLC entity and the identification information of the carrier corresponding to each RLC entity to the terminal equipment through the RRC connection reconfiguration information. Wherein the RRC connection reconfiguration information is specifically RRCConnectionReconfiguration.
Further, in the RLC configuration of RRCConnectionReconfiguration, a bearer id corresponding to the RLC is indicated, and an RLC-id of the RLC in the bearer is newly added, and in the PDCP configuration of RRCConnectionReconfiguration, a bearer id corresponding to the PDCP is indicated. And the UE determines the mapping relation between the PDCP corresponding to the bearer and the plurality of RLC through the bearer id.
For example, referring to fig. 5, after the RRC entity determines the carrier corresponding to each PDCP entity and the RLC corresponding to each carrier based on the mapping relationship, the RRC entity sends the corresponding mapping relationship to the UE through the RRC connection reconfiguration information, and receives the completion information fed back by the UE; and then, sending first configuration information, namely PDCPcontrol configuration, to the PDCP entity based on the mapping relationship, and sending at least one second configuration information, namely RLCCconfiguration, to at least one RLC entity respectively.
And adding indexes corresponding to a plurality of RLC entities under the same PDCP bearer in the RRC configuration RRCConnectionReconfiguration or certain configuration contained in the RRCConnectionReconfiguration. An example is given below, and the specific implementation is not limited to this:
the method further comprises the following steps: and at least sending the RLC entity sequence number RSN length to the PDCP entity and/or the terminal equipment.
Specifically, in order to adapt to the network deployment type and different scenarios and services of 5G, the RSN length may be increased and configured through RRCConnectionConfiguration or RRCConnectionReconfiguration; in addition, RRCConnectionConfiguration or RRCConnectionReconfiguration, in addition to the above-described RSN length, an SN length may be transmitted. To balance in gain and overhead by the RSN length and SN length.
It should be noted that the above-mentioned manner of sending the RSN length may be implemented by the following two manners:
in a first way,
The sending at least the RLC entity sequence number, RSN, length to the PDCP entity and/or the terminal device includes:
sending the RSN lengths corresponding to different RLC working modes to the PDCP entity and/or the terminal equipment;
or,
and sending the RSN lengths and the SN lengths corresponding to different RLC working modes to the PDCP entity and/or the terminal equipment.
For the traditional network structure, or under the condition that there is no PDCP to multi-RLC entity routing, the length of the RSN is set to 0, and the traditional mode is compatible. In other cases, the length of the RSN is configured to be non-zero through RRC signaling, and the PDCP PDUs are sequenced by using the RSN. The length of the RSN may be determined according to a specific scenario. Specifically, the determination may be based on whether the RLC operation mode is AM (acknowledged mode) or UM (unacknowledged mode), for example, when the RLC is AM, the RSN length may be set to 8bits, and the SN length may be set to 15bits, respectively; when the RLC working mode is UM, the length of RSN is determined to be 0bits and the SN length is determined to be 8 bits.
The RSN can also be understood as the extension of the SN length, and particularly, some high-order bits of the SN in the SN can realize the function of the RSN and be used for ordering the PDCP PDU.
The length setting of the RSN is added in the RRC configuration PDCP-Config, and the values of the configuration AM and the configuration UM are different. An example is given below, and the length value of RSN in the implementation is not limited to this:
in this embodiment, the working mode and the RSN length and the SN length corresponding thereto are both sent to the PDCP entity and the terminal device, so that the PDCP entity selects the corresponding RSN length and SN length based on the working mode.
The second way,
Before the at least sending the RLC entity sequence number, RSN, length to the PDCP entity and/or the terminal device, the method further includes:
determining a working mode of an RLC entity, and selecting a corresponding RSN length based on the working mode corresponding to the RLC;
or,
and determining the working mode of the RLC entity, and selecting the corresponding RSN length and SN length based on the working mode corresponding to the RLC.
The difference between this processing method and the first method is that the RRC entity determines the corresponding RSN length directly according to the RLC operation mode, or determines the corresponding RSN length and SN length.
The manner of sending the command to the PDCP entity and the terminal device by the RRC may be the same as the first manner, and is not described herein again.
Therefore, by adopting the above scheme, the mapping relationship of the identification information of the PDCP entity and the RLC entity corresponding to each carrier can be determined by the RRC entity side, and the first configuration signaling and the second configuration information are respectively sent to the PDCP entity and the RLC entity according to the mapping relationship. Therefore, in a scene that the PDCP corresponds to a plurality of RLC entities, different network architectures can be adapted.
In addition, the sequence number length of the RLC entity can be set through the RRC entity, so that the reordering speed and accuracy are ensured when one PDCP entity manages a plurality of RLC entities and a data unit is sent.
Example II,
An embodiment of the present invention provides a signaling configuration method, which is applied to a PDCP entity, and as shown in fig. 6, the method includes:
step 601: receiving a first configuration signaling sent by an RRC entity;
step 602: and determining the identification information of the carrier corresponding to the first configuration signaling and the identification information of the corresponding at least one RLC entity based on the first configuration signaling.
It should be noted that, as shown in fig. 2, fig. 3, and fig. 4, the network protocol layer architecture applied in this embodiment may be that an RCC (wireless cloud center) completes big data operation, and then sends an instruction to an RRS, and the RRS completes resource allocation of a corresponding air interface on the basis of an operation result of the RCC. Similarly, each RRS performs certain processing on information collected from the air interface and reports the processed information to the RCC. The RCC and the RRS adopt a flexible connection mode, in order to reduce the data transmission pressure between the RCC and the RRS, the functions between the RCC and the RRS can be flexibly divided, and the RCC and the RRS are connected through a transmission network. The reordering function of PDCP PDU is added in the PDCP protocol function, and the RLC function is kept unchanged. As can be seen from fig. 2, fig. 3 and fig. 4, one PDCP entity may correspond to one or more RLC entities, that is, one PDCP entity may manage a plurality of carriers, and each carrier may be assigned a mapping with one RLC entity.
In order to correctly receive and process information between protocol layers in the network structure, the embodiment provides a more suitable signaling configuration method.
The mapping relationship between the PDCP entities and the RLC entities is determined, specifically, identification information of a carrier corresponding to each PDCP entity is determined, and identification information of at least one RLC entity corresponding to each PDCP entity is determined. Through the mapping relationship, at least one RLC entity corresponding to each carrier can be determined.
Based on the mapping relationship, corresponding configuration information is generated respectively for the PDCP entity and the RLC entity, and then a first configuration signaling is sent to the PDCP entity and a second configuration signaling is sent to the RLC entity.
That is to say, the RRC entity configures a mapping relationship between the PDCP and the RLC, wherein the RRC may directly notify an RLC _ id of each RLC corresponding to the PDCP entity and notify an RLC configuration bearer id.
In order to ensure that the network side and the terminal side can normally receive information, corresponding configuration information is also sent to the terminal device according to the mapping relationship, specifically: and sending RRC connection reconfiguration information to the terminal equipment based on the mapping relation between the PDCP entity and the RLC entity, and indicating the identification information of each RLC entity and the identification information of the carrier corresponding to each RLC entity to the terminal equipment through the RRC connection reconfiguration information. Wherein the RRC connection reconfiguration information is specifically RRCConnectionReconfiguration.
Further, in the RLC configuration of RRCConnectionReconfiguration, a bearer id corresponding to the RLC is indicated, and an RLC-id of the RLC in the bearer is newly added, and in the PDCP configuration of RRCConnectionReconfiguration, a bearer id corresponding to the PDCP is indicated. And the UE determines the mapping relation between the PDCP corresponding to the bearer and the plurality of RLC through the bearer id.
For example, referring to fig. 5, after the RRC entity determines the carrier corresponding to each PDCP entity and the RLC corresponding to each carrier based on the mapping relationship, the RRC entity sends the corresponding mapping relationship to the UE through the RRC connection reconfiguration information, and receives the completion information fed back by the UE; and then, sending first configuration information, namely PDCPcontrol configuration, to the PDCP entity based on the mapping relationship, and sending at least one second configuration information, namely RLCCconfiguration, to at least one RLC entity respectively.
And adding indexes corresponding to a plurality of RLC entities under the same PDCP bearer in the RRC configuration RRCConnectionReconfiguration or certain configuration contained in the RRCConnectionReconfiguration. An example is given below, and the specific implementation is not limited to this:
the method further comprises the following steps: receiving the RSN length sent by the RRC entity.
Specifically, receiving RSN lengths corresponding to different RLC operation modes sent by the RRC entity; acquiring an RLC working mode, and determining a corresponding RSN length based on the RLC working mode;
or,
receiving RSN lengths and SN lengths corresponding to different RLC working modes sent by the RRC entity; and acquiring the working mode of the RLC, and determining the corresponding RSN length and SN length based on the working mode of the RLC.
In order to adapt to the network deployment type and different scenes and services of 5G, the RSN length can be increased and configured through RRCConnectionconfiguration or RRCConnectionReconfiguration; in addition, RRCConnectionConfiguration or RRCConnectionReconfiguration, in addition to the above-described RSN length, an SN length may be transmitted. To balance in gain and overhead by the RSN length and SN length.
It should be noted that the above-mentioned manner of sending the RSN length may be implemented by the following two manners:
for the traditional network structure, or under the condition that there is no PDCP to multi-RLC entity routing, the length of the RSN is set to 0, and the traditional mode is compatible. In other cases, the length of the RSN is configured to be non-zero through RRC signaling, and the PDCP PDUs are sequenced by using the RSN. The length of the RSN may be determined according to a specific scenario. Specifically, the determination may be based on whether the RLC operation mode is AM (acknowledged mode) or UM (unacknowledged mode), for example, when the RLC is AM, the RSN length may be set to 8bits, and the SN length may be set to 15bits, respectively; when the RLC working mode is UM, the length of RSN is determined to be 0bits and the SN length is determined to be 8 bits.
The RSN can also be understood as the extension of the SN length, and particularly, some high-order bits of the SN in the SN can realize the function of the RSN and be used for ordering the PDCP PDU.
The length setting of the RSN is added in the RRC configuration PDCP-Config, and the values of the configuration AM and the configuration UM are different. An example is given below, and the length value of RSN in the implementation is not limited to this:
in this embodiment, the working mode and the RSN length and the SN length corresponding thereto are both sent to the PDCP entity and the terminal device, so that the PDCP entity selects the corresponding RSN length and SN length based on the working mode.
Further, the PDCP entity is further capable of generating a corresponding PDU based on the RSN length, and specifically includes:
determining an RSN for each RLC entity at least based on the RSN length and the corresponding identification information of at least one RLC entity;
determining a data protocol unit (PDU) to be sent by each RLC entity, adding at least the RSN to the PDU, and mapping the PDU to the corresponding RLC entity to send the PDU through the RLC entity.
When transmitting the PDU, the RSN and SN may be generated according to the first configuration signaling and the information such as the corresponding RSN length, and added to the PDU, so as to transmit the PDU to the corresponding RLC entity.
The processing manner for generating SN and the like is not described in detail in this embodiment.
The method further comprises the following steps: acquiring a flow control strategy for RLC entities, and sending data to each RLC entity based on the flow control strategy;
the flow control policy at least includes a data byte length and air interface link control information distributed on an air interface channel for each RLC entity.
As shown in fig. 3 and 4, the source for obtaining the flow control policy may receive the flow control policy sent by the fast control FC-MAC, or may generate the flow control policy for the PDCP entity itself.
That is, the PDCP entity is provided with a flow control policy that mainly includes notification of the length of data bytes distributed on each air interface channel by several RLC bearers corresponding to each PDCP bearer, and air interface link information control information during air interface cell handover. For parameters related to a flow control strategy, such as data air interface throughput and air interface link information distributed on each bearer, if the PDCP can be independently obtained, the PDCP is automatically completed without being provided by FC-MAC.
Therefore, by adopting the above scheme, the mapping relationship of the identification information of the PDCP entity and the RLC entity corresponding to each carrier can be determined by the RRC entity side, and the first configuration signaling and the second configuration information are respectively sent to the PDCP entity and the RLC entity according to the mapping relationship. Therefore, in a scene that the PDCP corresponds to a plurality of RLC entities, different network architectures can be adapted.
In addition, the sequence number length of the RLC entity can be set through the RRC entity, so that the reordering speed and accuracy are ensured when one PDCP entity manages a plurality of RLC entities and a data unit is sent.
Example III,
An embodiment of the present invention provides an RRC entity, as shown in fig. 7, including:
a processing unit 71, configured to determine a mapping relationship between a PDCP entity and a radio link protocol RLC entity; wherein, the mapping relationship at least comprises a PDCP entity and at least one RLC entity corresponding to each carrier;
a signaling sending unit 72, configured to send a first configuration signaling to the PDCP entity and a second configuration signaling to the RLC entity based on a mapping relationship between the PDCP entity and the RLC entity;
wherein, the first configuration signaling at least carries identification information of a carrier corresponding to the PDCP entity and identification information of at least one RLC entity corresponding to the carrier; the second configuration information at least carries identification information of a carrier corresponding to the RLC entity and identification information of the RLC entity.
It should be noted that, as shown in fig. 2, fig. 3, and fig. 4, the network protocol layer architecture applied in this embodiment may be that an RCC (wireless cloud center) completes big data operation, and then sends an instruction to an RRS, and the RRS completes resource allocation of a corresponding air interface on the basis of an operation result of the RCC. Similarly, each RRS performs certain processing on information collected from the air interface and reports the processed information to the RCC. The RCC and the RRS adopt a flexible connection mode, in order to reduce the data transmission pressure between the RCC and the RRS, the functions between the RCC and the RRS can be flexibly divided, and the RCC and the RRS are connected through a transmission network. The reordering function of PDCP PDU is added in the PDCP protocol function, and the RLC function is kept unchanged. As can be seen from fig. 2, fig. 3 and fig. 4, one PDCP entity may correspond to one or more RLC entities, that is, one PDCP entity may manage a plurality of carriers, and each carrier may be assigned a mapping with one RLC entity.
In order to correctly receive and process information between protocol layers in the network structure, the embodiment provides a more suitable signaling configuration method.
The mapping relationship between the PDCP entities and the RLC entities is determined, specifically, identification information of a carrier corresponding to each PDCP entity is determined, and identification information of at least one RLC entity corresponding to each PDCP entity is determined. Through the mapping relationship, at least one RLC entity corresponding to each carrier can be determined.
Based on the mapping relationship, corresponding configuration information is generated respectively for the PDCP entity and the RLC entity, and then a first configuration signaling is sent to the PDCP entity and a second configuration signaling is sent to the RLC entity.
That is to say, the RRC entity configures a mapping relationship between the PDCP and the RLC, wherein the RRC may directly notify an RLC _ id of each RLC corresponding to the PDCP entity and notify an RLC configuration bearer id.
In order to ensure that the network side and the terminal side can normally receive information, corresponding configuration information is also sent to the terminal device according to the mapping relationship, specifically: and sending RRC connection reconfiguration information to the terminal equipment based on the mapping relation between the PDCP entity and the RLC entity, and indicating the identification information of each RLC entity and the identification information of the carrier corresponding to each RLC entity to the terminal equipment through the RRC connection reconfiguration information. Wherein the RRC connection reconfiguration information is specifically RRCConnectionReconfiguration.
Further, in the RLC configuration of RRCConnectionReconfiguration, a bearer id corresponding to the RLC is indicated, and an RLC-id of the RLC in the bearer is newly added, and in the PDCP configuration of RRCConnectionReconfiguration, a bearer id corresponding to the PDCP is indicated. And the UE determines the mapping relation between the PDCP corresponding to the bearer and the plurality of RLC through the bearer id.
For example, referring to fig. 5, after the RRC entity determines the carrier corresponding to each PDCP entity and the RLC corresponding to each carrier based on the mapping relationship, the RRC entity sends the corresponding mapping relationship to the UE through the RRC connection reconfiguration information, and receives the completion information fed back by the UE; and then, sending first configuration information, namely PDCPcontrol configuration, to the PDCP entity based on the mapping relationship, and sending at least one second configuration information, namely RLCCconfiguration, to at least one RLC entity respectively.
And adding indexes corresponding to a plurality of RLC entities under the same PDCP bearer in the RRC configuration RRCConnectionReconfiguration or certain configuration contained in the RRCConnectionReconfiguration. An example is given below, and the specific implementation is not limited to this:
the method further comprises the following steps: and at least sending the RLC entity sequence number RSN length to the PDCP entity and/or the terminal equipment.
Specifically, in order to adapt to the network deployment type and different scenarios and services of 5G, the RSN length may be increased and configured through RRCConnectionConfiguration or RRCConnectionReconfiguration; in addition, RRCConnectionConfiguration or RRCConnectionReconfiguration, in addition to the above-described RSN length, an SN length may be transmitted. To balance in gain and overhead by the RSN length and SN length.
It should be noted that the above-mentioned manner of sending the RSN length may be implemented by the following two manners:
in a first way,
The signaling sending unit is configured to send RSN lengths corresponding to different RLC operating modes to the PDCP entity and/or the terminal device;
or,
and sending the RSN lengths and the SN lengths corresponding to different RLC working modes to the PDCP entity and/or the terminal equipment.
For the traditional network structure, or under the condition that there is no PDCP to multi-RLC entity routing, the length of the RSN is set to 0, and the traditional mode is compatible. In other cases, the length of the RSN is configured to be non-zero through RRC signaling, and the PDCP PDUs are sequenced by using the RSN. The length of the RSN may be determined according to a specific scenario. Specifically, the determination may be based on whether the RLC operation mode is AM (acknowledged mode) or UM (unacknowledged mode), for example, when the RLC is AM, the RSN length may be set to 8bits, and the SN length may be set to 15bits, respectively; when the RLC working mode is UM, the length of RSN is determined to be 0bits and the SN length is determined to be 8 bits.
The RSN can also be understood as the extension of the SN length, and particularly, some high-order bits of the SN in the SN can realize the function of the RSN and be used for ordering the PDCP PDU.
The length setting of the RSN is added in the RRC configuration PDCP-Config, and the values of the configuration AM and the configuration UM are different. An example is given below, and the length value of RSN in the implementation is not limited to this:
in this embodiment, the working mode and the RSN length and the SN length corresponding thereto are both sent to the PDCP entity and the terminal device, so that the PDCP entity selects the corresponding RSN length and SN length based on the working mode.
The second way,
The signaling sending unit is used for determining the working mode of the RLC entity and selecting the corresponding RSN length based on the working mode corresponding to the RLC;
or,
and determining the working mode of the RLC entity, and selecting the corresponding RSN length and SN length based on the working mode corresponding to the RLC.
The difference between this processing method and the first method is that the RRC entity determines the corresponding RSN length directly according to the RLC operation mode, or determines the corresponding RSN length and SN length.
The manner of sending the command to the PDCP entity and the terminal device by the RRC may be the same as the first manner, and is not described herein again.
Therefore, by adopting the above scheme, the mapping relationship of the identification information of the PDCP entity and the RLC entity corresponding to each carrier can be determined by the RRC entity side, and the first configuration signaling and the second configuration information are respectively sent to the PDCP entity and the RLC entity according to the mapping relationship. Therefore, in a scene that the PDCP corresponds to a plurality of RLC entities, different network architectures can be adapted.
In addition, the sequence number length of the RLC entity can be set through the RRC entity, so that the reordering speed and accuracy are ensured when one PDCP entity manages a plurality of RLC entities and a data unit is sent.
Example four,
An embodiment of the present invention provides a PDCP entity, as shown in fig. 8, including:
a signaling receiving unit 81, configured to receive a first configuration signaling sent by an RRC entity;
a configuring unit 82, configured to determine, based on the first configuration signaling, identification information of a carrier corresponding to itself and identification information of at least one corresponding RLC entity.
It should be noted that, as shown in fig. 2, fig. 3, and fig. 4, the network protocol layer architecture applied in this embodiment may be that an RCC (wireless cloud center) completes big data operation, and then sends an instruction to an RRS, and the RRS completes resource allocation of a corresponding air interface on the basis of an operation result of the RCC. Similarly, each RRS performs certain processing on information collected from the air interface and reports the processed information to the RCC. The RCC and the RRS adopt a flexible connection mode, in order to reduce the data transmission pressure between the RCC and the RRS, the functions between the RCC and the RRS can be flexibly divided, and the RCC and the RRS are connected through a transmission network. The reordering function of PDCP PDU is added in the PDCP protocol function, and the RLC function is kept unchanged. As can be seen from fig. 2, fig. 3 and fig. 4, one PDCP entity may correspond to one or more RLC entities, that is, one PDCP entity may manage a plurality of carriers, and each carrier may be assigned a mapping with one RLC entity.
In order to correctly receive and process information between protocol layers in the network structure, the embodiment provides a more suitable signaling configuration method.
The mapping relationship between the PDCP entities and the RLC entities is determined, specifically, identification information of a carrier corresponding to each PDCP entity is determined, and identification information of at least one RLC entity corresponding to each PDCP entity is determined. Through the mapping relationship, at least one RLC entity corresponding to each carrier can be determined.
Based on the mapping relationship, corresponding configuration information is generated respectively for the PDCP entity and the RLC entity, and then a first configuration signaling is sent to the PDCP entity and a second configuration signaling is sent to the RLC entity.
That is to say, the RRC entity configures a mapping relationship between the PDCP and the RLC, wherein the RRC may directly notify an RLC _ id of each RLC corresponding to the PDCP entity and notify an RLC configuration bearer id.
In order to ensure that the network side and the terminal side can normally receive information, corresponding configuration information is also sent to the terminal device according to the mapping relationship, specifically: and sending RRC connection reconfiguration information to the terminal equipment based on the mapping relation between the PDCP entity and the RLC entity, and indicating the identification information of each RLC entity and the identification information of the carrier corresponding to each RLC entity to the terminal equipment through the RRC connection reconfiguration information. Wherein the RRC connection reconfiguration information is specifically RRCConnectionReconfiguration.
Further, in the RLC configuration of RRCConnectionReconfiguration, a bearer id corresponding to the RLC is indicated, and an RLC-id of the RLC in the bearer is newly added, and in the PDCP configuration of RRCConnectionReconfiguration, a bearer id corresponding to the PDCP is indicated. And the UE determines the mapping relation between the PDCP corresponding to the bearer and the plurality of RLC through the bearer id.
For example, referring to fig. 5, after the RRC entity determines the carrier corresponding to each PDCP entity and the RLC corresponding to each carrier based on the mapping relationship, the RRC entity sends the corresponding mapping relationship to the UE through the RRC connection reconfiguration information, and receives the completion information fed back by the UE; and then, sending first configuration information, namely PDCPcontrol configuration, to the PDCP entity based on the mapping relationship, and sending at least one second configuration information, namely RLCCconfiguration, to at least one RLC entity respectively.
And adding indexes corresponding to a plurality of RLC entities under the same PDCP bearer in the RRC configuration RRCConnectionReconfiguration or certain configuration contained in the RRCConnectionReconfiguration. An example is given below, and the specific implementation is not limited to this:
the signaling receiving unit is configured to receive the RSN length sent by the RRC entity.
Specifically, the signaling receiving unit is configured to receive RSN lengths corresponding to different RLC operating modes sent by the RRC entity; correspondingly, the configuration unit is further configured to obtain a working mode of the RLC, and determine a corresponding RSN length based on the working mode of the RLC;
or,
the signaling receiving unit is configured to receive RSN lengths and SN lengths corresponding to different RLC operating modes sent by the RRC entity; correspondingly, the configuration unit is further configured to obtain a working mode of the RLC, and determine the corresponding RSN length and SN length based on the working mode of the RLC.
In order to adapt to the network deployment type and different scenes and services of 5G, the RSN length can be increased and configured through RRCConnectionconfiguration or RRCConnectionReconfiguration; in addition, RRCConnectionConfiguration or RRCConnectionReconfiguration, in addition to the above-described RSN length, an SN length may be transmitted. To balance in gain and overhead by the RSN length and SN length.
It should be noted that the above-mentioned manner of sending the RSN length may be implemented by the following two manners:
for the traditional network structure, or under the condition that there is no PDCP to multi-RLC entity routing, the length of the RSN is set to 0, and the traditional mode is compatible. In other cases, the length of the RSN is configured to be non-zero through RRC signaling, and the PDCP PDUs are sequenced by using the RSN. The length of the RSN may be determined according to a specific scenario. Specifically, the determination may be based on whether the RLC operation mode is AM (acknowledged mode) or UM (unacknowledged mode), for example, when the RLC is AM, the RSN length may be set to 8bits, and the SN length may be set to 15bits, respectively; when the RLC working mode is UM, the length of RSN is determined to be 0bits and the SN length is determined to be 8 bits.
The RSN can also be understood as the extension of the SN length, and particularly, some high-order bits of the SN in the SN can realize the function of the RSN and be used for ordering the PDCP PDU.
The length setting of the RSN is added in the RRC configuration PDCP-Config, and the values of the configuration AM and the configuration UM are different. An example is given below, and the length value of RSN in the implementation is not limited to this:
in this embodiment, the working mode and the RSN length and the SN length corresponding thereto are both sent to the PDCP entity and the terminal device, so that the PDCP entity selects the corresponding RSN length and SN length based on the working mode.
Further, the PDCP entity further includes:
an information sending unit 83, configured to determine a data protocol unit PDU to be sent by each RLC entity, add at least the RSN to the PDU, and map the PDU to a corresponding RLC entity to send the PDU through the RLC entity;
correspondingly, the configuration unit is configured to determine the RSN for each RLC entity based on at least the RSN length and the identification information of the corresponding at least one RLC entity.
When transmitting the PDU, the RSN and SN may be generated according to the first configuration signaling and the information such as the corresponding RSN length, and added to the PDU, so as to transmit the PDU to the corresponding RLC entity.
The processing manner for generating SN and the like is not described in detail in this embodiment.
The method further comprises the following steps: acquiring a flow control strategy for RLC entities, and sending data to each RLC entity based on the flow control strategy;
the flow control policy at least includes a data byte length and air interface link control information distributed on an air interface channel for each RLC entity.
As shown in fig. 3 and 4, the source for obtaining the flow control policy may receive the flow control policy sent by the fast control FC-MAC, or may generate the flow control policy for the PDCP entity itself.
That is, the PDCP entity is provided with a flow control policy that mainly includes notification of the length of data bytes distributed on each air interface channel by several RLC bearers corresponding to each PDCP bearer, and air interface link information control information during air interface cell handover. For parameters related to a flow control strategy, such as data air interface throughput and air interface link information distributed on each bearer, if the PDCP can be independently obtained, the PDCP is automatically completed without being provided by FC-MAC.
Therefore, by adopting the above scheme, the mapping relationship of the identification information of the PDCP entity and the RLC entity corresponding to each carrier can be determined by the RRC entity side, and the first configuration signaling and the second configuration information are respectively sent to the PDCP entity and the RLC entity according to the mapping relationship. Therefore, in a scene that the PDCP corresponds to a plurality of RLC entities, different network architectures can be adapted.
In addition, the sequence number length of the RLC entity can be set through the RRC entity, so that the reordering speed and accuracy are ensured when one PDCP entity manages a plurality of RLC entities and a data unit is sent.
The integrated module according to the embodiment of the present invention may also be stored in a computer-readable storage medium if it is implemented in the form of a software functional module and sold or used as an independent product. Based on such understanding, the technical solutions of the embodiments of the present invention may be essentially implemented or a part contributing to the prior art may be embodied in the form of a software product stored in a storage medium, and including several instructions for enabling a computer device (which may be a personal computer, a network device, or a network device) to execute all or part of the methods described in the embodiments of the present invention. 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. Thus, embodiments of the invention are not limited to any specific combination of hardware and software.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.
Claims (20)
1. A signaling configuration method applied to an RRC entity, the method comprising:
determining a mapping relation between a PDCP entity and a radio link protocol RLC entity; wherein, the mapping relationship at least comprises a PDCP entity and at least one RLC entity corresponding to each carrier;
based on the mapping relation between the PDCP entity and the RLC entity, sending a first configuration signaling to the PDCP entity and sending a second configuration signaling to the RLC entity;
wherein, the first configuration signaling at least carries identification information of a carrier corresponding to the PDCP entity and identification information of at least one RLC entity corresponding to the carrier; the second configuration information at least carries identification information of a carrier corresponding to the RLC entity and identification information of the RLC entity.
2. The method of claim 1, further comprising:
and at least sending the RLC entity sequence number RSN length to the PDCP entity and/or the terminal equipment.
3. The method according to claim 2, wherein the sending at least the RLC entity sequence number, RSN, length to the PDCP entity and/or the terminal device comprises:
sending the RSN lengths corresponding to different RLC working modes to the PDCP entity and/or the terminal equipment;
or,
and sending the RSN lengths and the SN lengths corresponding to different RLC working modes to the PDCP entity and/or the terminal equipment.
4. The method according to claim 2, wherein before sending at least the RLC entity sequence number, RSN, length to the PDCP entity and/or terminal device, the method further comprises:
determining a working mode of an RLC entity, and selecting a corresponding RSN length based on the working mode corresponding to the RLC;
or,
and determining the working mode of the RLC entity, and selecting the corresponding RSN length and SN length based on the working mode corresponding to the RLC.
5. The method of claim 1, further comprising:
and indicating the identification information of each RLC entity and the identification information of the carrier wave corresponding to each RLC entity to terminal equipment based on the mapping relation between the PDCP entity and the RLC entity.
6. A signaling configuration method applied to a PDCP entity is characterized by comprising the following steps:
receiving a first configuration signaling sent by an RRC entity;
and determining the identification information of the carrier corresponding to the first configuration signaling and the identification information of the corresponding at least one RLC entity based on the first configuration signaling.
7. The method of claim 6, further comprising:
receiving the RSN length sent by the RRC entity.
8. The method of claim 7, wherein the receiving the RSN length from the RRC entity comprises:
receiving RSN lengths corresponding to different RLC working modes sent by the RRC entity; acquiring an RLC working mode, and determining a corresponding RSN length based on the RLC working mode;
or,
receiving RSN lengths and SN lengths corresponding to different RLC working modes sent by the RRC entity; and acquiring the working mode of the RLC, and determining the corresponding RSN length and SN length based on the working mode of the RLC.
9. The method of claim 8, further comprising:
determining an RSN for each RLC entity at least based on the RSN length and the corresponding identification information of at least one RLC entity;
determining a data protocol unit (PDU) to be sent by each RLC entity, adding at least the RSN to the PDU, and mapping the PDU to the corresponding RLC entity to send the PDU through the RLC entity.
10. The method of claim 6, further comprising:
acquiring a flow control strategy for RLC entities, and controlling to generate and send PDU to each RLC entity based on the flow control strategy;
the flow control policy at least includes a data byte length and air interface link control information distributed on an air interface channel for each RLC entity.
11. An RRC entity, comprising:
a processing unit, configured to determine a mapping relationship between a PDCP entity and a radio link protocol RLC entity; wherein, the mapping relationship at least comprises a PDCP entity and at least one RLC entity corresponding to each carrier;
a signaling sending unit, configured to send a first configuration signaling to the PDCP entity and send a second configuration signaling to the RLC entity based on a mapping relationship between the PDCP entity and the RLC entity;
wherein, the first configuration signaling at least carries identification information of a carrier corresponding to the PDCP entity and identification information of at least one RLC entity corresponding to the carrier; the second configuration information at least carries identification information of a carrier corresponding to the RLC entity and identification information of the RLC entity.
12. The RRC entity according to claim 11, wherein the signaling sending unit is configured to send at least an RLC entity sequence number, RSN, length to the PDCP entity and/or a terminal device.
13. The RRC entity of claim 12, wherein the signaling sending unit is configured to send RSN lengths corresponding to different RLC operation modes to the PDCP entity and/or the terminal device;
or,
and sending the RSN lengths and the SN lengths corresponding to different RLC working modes to the PDCP entity and/or the terminal equipment.
14. The RRC entity of claim 12, wherein the processing unit is configured to determine an operation mode of an RLC entity, and select a corresponding RSN length based on the operation mode corresponding to the RLC entity;
or,
and determining the working mode of the RLC entity, and selecting the corresponding RSN length and SN length based on the working mode corresponding to the RLC.
15. The RRC entity of claim 11, wherein the processing unit is configured to indicate, to a terminal device, identification information of each RLC entity and identification information of a carrier corresponding to each RLC entity based on a mapping relationship between the PDCP entity and the RLC entity.
16. A PDCP entity, comprising:
a signaling receiving unit, configured to receive a first configuration signaling sent by an RRC entity;
and a configuration unit, configured to determine, based on the first configuration signaling, identification information of a carrier corresponding to the configuration unit and identification information of at least one corresponding RLC entity.
17. The PDCP entity of claim 16, wherein the signaling receiving unit is configured to receive an RSN length sent by the RRC entity.
18. The PDCP entity of claim 17, wherein the signaling receiving unit is configured to receive RSN lengths corresponding to different RLC operation modes sent by the RRC entity;
correspondingly, the configuration unit is further configured to obtain a working mode of the RLC, and determine a corresponding RSN length based on the working mode of the RLC;
or,
the signaling receiving unit is configured to receive RSN lengths and SN lengths corresponding to different RLC operating modes sent by the RRC entity; correspondingly, the configuration unit is further configured to obtain a working mode of the RLC, and determine the corresponding RSN length and SN length based on the working mode of the RLC.
19. The PDCP entity of claim 18, wherein the PDCP entity further comprises:
an information sending unit, configured to determine a data protocol unit PDU to be sent by each RLC entity, at least add the RSN to the PDU, and map the PDU to a corresponding RLC entity to send the PDU through the RLC entity;
correspondingly, the configuration unit is configured to determine the RSN for each RLC entity based on at least the RSN length and the identification information of the corresponding at least one RLC entity.
20. The PDCP entity of claim 16, wherein the configuration unit is configured to obtain a flow control policy for an RLC entity, and control generation and transmission of a PDU to each RLC entity based on the flow control policy;
the flow control policy at least includes a data byte length and air interface link control information distributed on an air interface channel for each RLC entity.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611154862.5A CN108234092B (en) | 2016-12-14 | 2016-12-14 | Signaling configuration method, RRC entity and PDCP entity |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611154862.5A CN108234092B (en) | 2016-12-14 | 2016-12-14 | Signaling configuration method, RRC entity and PDCP entity |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108234092A true CN108234092A (en) | 2018-06-29 |
| CN108234092B CN108234092B (en) | 2020-09-11 |
Family
ID=62650139
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611154862.5A Active CN108234092B (en) | 2016-12-14 | 2016-12-14 | Signaling configuration method, RRC entity and PDCP entity |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108234092B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2021082837A1 (en) * | 2019-10-29 | 2021-05-06 | 中国移动通信有限公司研究院 | Traffic control method and apparatus, related device, and storage medium |
| WO2021097689A1 (en) * | 2019-11-19 | 2021-05-27 | 华为技术有限公司 | Communication method, apparatus and device |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101677266A (en) * | 2008-09-19 | 2010-03-24 | 大唐移动通信设备有限公司 | Method, system and apparatus for the operation of reordering and repeated elimination |
| WO2012167563A1 (en) * | 2011-11-17 | 2012-12-13 | 华为技术有限公司 | Carrier aggregation scheduling device, carrier aggregation scheduling method, and base station |
| US20160057665A1 (en) * | 2012-06-20 | 2016-02-25 | Ofinno Technologies, Llc | Carrier Configuration in Wireless Networks |
| CN105706387A (en) * | 2013-11-01 | 2016-06-22 | 三星电子株式会社 | Method and apparatus for reconfiguring a bearer |
| CN106134099A (en) * | 2014-01-29 | 2016-11-16 | 三星电子株式会社 | For the method and apparatus using multiple carrier wave to send and receive data in mobile communication system |
-
2016
- 2016-12-14 CN CN201611154862.5A patent/CN108234092B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101677266A (en) * | 2008-09-19 | 2010-03-24 | 大唐移动通信设备有限公司 | Method, system and apparatus for the operation of reordering and repeated elimination |
| WO2012167563A1 (en) * | 2011-11-17 | 2012-12-13 | 华为技术有限公司 | Carrier aggregation scheduling device, carrier aggregation scheduling method, and base station |
| US20160057665A1 (en) * | 2012-06-20 | 2016-02-25 | Ofinno Technologies, Llc | Carrier Configuration in Wireless Networks |
| CN105706387A (en) * | 2013-11-01 | 2016-06-22 | 三星电子株式会社 | Method and apparatus for reconfiguring a bearer |
| CN106134099A (en) * | 2014-01-29 | 2016-11-16 | 三星电子株式会社 | For the method and apparatus using multiple carrier wave to send and receive data in mobile communication system |
Non-Patent Citations (1)
| Title |
|---|
| ERICSSON: "Introduction of Downlink Multi-Carrier", 《3GPP TSG-GERAN #61 GP-140155》 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2021082837A1 (en) * | 2019-10-29 | 2021-05-06 | 中国移动通信有限公司研究院 | Traffic control method and apparatus, related device, and storage medium |
| WO2021097689A1 (en) * | 2019-11-19 | 2021-05-27 | 华为技术有限公司 | Communication method, apparatus and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108234092B (en) | 2020-09-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP5478487B2 (en) | Data transmission method, data reception method, and apparatus | |
| US11606306B2 (en) | Packet transmission method and apparatus | |
| CN103782569B (en) | Data processing equipment and method | |
| EP3737183B1 (en) | Communication methods, apparatuses and computer-readable storage medium | |
| CN110505714B (en) | Multi-link communication method, equipment and terminal | |
| US11785496B2 (en) | Quality of service implementations for separating user plane | |
| CN104272796A (en) | Handling packet data convergence protocol data units | |
| US20220014971A1 (en) | Wireless communication method, terminal device and network device | |
| US20220015172A1 (en) | Communication method and communications apparatus | |
| US20220368782A1 (en) | Baseband chip and method for layer 2 downlink data processing | |
| JP7100135B6 (en) | Data transmission control method and related products | |
| CN107347199B (en) | It is a kind of switching and its control method, device | |
| CN108811154A (en) | Data pack transmission method and equipment | |
| WO2018166517A1 (en) | Data transmission method, data transmitting device, and data receiving device | |
| CN110971351B (en) | Method for coordinating repeated transmission | |
| CN111357322A (en) | Terminal device, base station device, and method | |
| CN111385071B (en) | Data transmission method, device and computer storage medium | |
| CN108234092B (en) | Signaling configuration method, RRC entity and PDCP entity | |
| WO2021244356A1 (en) | Data transmission method and apparatus | |
| CN105517020A (en) | Configuration parameter updating method and apparatus | |
| WO2023030452A1 (en) | Data transmission method and related device | |
| JP7083854B2 (en) | How to support data replication, sender and receiver devices | |
| EP3742635A1 (en) | Method for reporting data amount of data replication, user equipment and network device | |
| CN111432458B (en) | Communication method and device based on double connections | |
| WO2021152363A2 (en) | Layer 2 uplink data inline processing using integrated circuits |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |