WO2021223623A1

WO2021223623A1 - Configuration method for pdcp duplication of signaling radio bearer, and rrc entity

Info

Publication number: WO2021223623A1
Application number: PCT/CN2021/090078
Authority: WO
Inventors: 肖芳英; 刘仁茂
Original assignee: 夏普株式会社
Priority date: 2020-05-08
Filing date: 2021-04-27
Publication date: 2021-11-11
Also published as: CN113630223A

Abstract

The present disclosure provides a configuration method for PDCP duplication of a signaling radio bearer, and an RRC entity. In the configuration method for PDCP duplication of a signaling radio bearer, when a PDCP entity of the signaling radio bearer is associated with two or more radio link control (RLC) entities, a configuration message used for configuring the PDCP duplication of the signaling radio bearer comprises an indication identifier for indicating whether the PDCP duplication is configured.

Description

Configuration method and RRC entity for PDCP repetition of signaling radio bearer

Technical field

The present disclosure relates to the field of wireless communication technology, and more specifically, the present disclosure relates to user equipment and methods thereof, base stations and methods thereof.

Background technique

In September 2018, at the RAN#81 plenary meeting of the 3rd Generation Partnership Project (3rd Generation Partnership Project: 3GPP), Nokia proposed a research project on the 5G (or NR) Industrial Internet of Things (IIOT) (see Non-patent literature: RP-182090: Revised SID: Study on NR Industrial Internet of Things (IIoT), and was approved. One of the goals of this research project is to improve the reliability of data transmission and reduce the time delay of data transmission through data duplication, including: (1) Resource-efficient PDCP duplication, such as avoiding unnecessary repeated transmission; (2) Use dual connectivity DC or carrier aggregation CA to achieve more than two PDCP repetitions.

In Release 15, a bearer that supports PDCP repetition can be configured with two RLC entities at most. The initial state of the bearer configured with PDCP repetition is to indicate whether the PDCP repetition function is activated at the initial stage through the pdcp-Duplication cell (for a detailed description of the cell, see 3GPP TS38.331). In carrier aggregation, for the bearer whose initial PDCP repetition function is not activated, its data is sent through the logical channel indicated by the primaryPath cell (see 3GPP TS38.331 for the specific description of the cell). In dual connectivity, for a bearer whose initial PDCP repetition function is not activated, it is determined whether the data is sent through the logical channel indicated by the primaryPath cell or in a separate bearer mode according to the amount of data to be sent.

In NR IIoT, in order to achieve the goal of two or more PDCP repetitions using dual connectivity or carrier aggregation, some manufacturers propose to configure multiple RLC entities to support PDCP repetitive bearers, but only activate a few of them each time The manner of the RLC entity (that is, the PDCP entity configured with PDCP repetition delivers the PDCP PDU to two or more associated and activated RLC entities). The network can indicate whether to activate PDCP repetition and/or activated RLC entity through RRC signaling or media access control control element MAC CE. In the currently achieved PDCP repetition configuration method, when there are more than two RLC entities associated with the radio bearer, whether to configure the PDCP repetition for the radio bearer is optional (that is, not necessary). However, in the 3GPP protocol 38.323-g00, the activation of the radio bearer PDCP repetition depends on the indicator used to indicate whether the PDCP repetition is configured. When the indicator flag is configured, it means that the PDCP repetition is configured. If the indicator does not appear , It means that no PDCP repetition is configured. For SRB, when there are more than two RLC entities associated but the indication identifier does not appear, PDCP repetition will not be activated.

This disclosure discusses the related issues involved in configuring the signaling radio bearer PDCP repetition.

Summary of the invention

The present disclosure is proposed in response to the above problems, and its purpose is to provide a signaling radio bearer PDCP repeated configuration method and RRC entity that can solve the problems involved in the signaling radio bearer PDCP repeated configuration, so as to ensure that the signaling radio is configured When the number of bearer-associated RLC entities exceeds 2, its initial state is activated.

According to the first aspect of the present disclosure, a configuration method for PDCP repetition of signaling radio bearers is proposed. When the PDCP entity of the signaling radio bearer is associated with more than two radio link control RLC entities, it is used to configure the signaling radio bearer. The configuration message for making the radio bearer PDCP repetition must include an indication identifier for indicating whether the PDCP repetition is configured.

According to the second aspect of the present disclosure, an RRC entity is proposed, and the RRC entity executes the configuration method for PDCP repetition of signaling radio bearers according to the context.

Invention effect

According to the PDCP repeated configuration method and RRC entity for signaling radio bearers of the present disclosure, it can be ensured that when the number of RLC entities associated with the configuration signaling radio bearer exceeds 2, its initial state is activated, thereby improving the wireless communication system. Reliability.

Description of the drawings

The above and other features of the present disclosure will become more apparent through the following detailed description in conjunction with the accompanying drawings, among which:

Fig. 1 shows a flowchart of a method 100 in a user equipment UE based on an embodiment of the present disclosure.

FIG. 2 shows a block diagram of a user equipment 20 based on an embodiment of the present disclosure.

FIG. 3 shows a flowchart of a method 300 in a base station based on an embodiment of the present disclosure.

FIG. 4 shows a block diagram of a base station 40 based on an embodiment of the present disclosure.

Detailed ways

The present disclosure will be described in detail below with reference to the drawings and specific implementations. It should be noted that the present disclosure should not be limited to the specific embodiments described below. In addition, for the sake of brevity, detailed descriptions of well-known technologies that are not directly related to the present disclosure are omitted to prevent confusion in the understanding of the present disclosure.

The following describes some terms involved in the present disclosure. For specific descriptions of the terms, please refer to the latest 3GPP documents TS38.331 and TS38.323.

RRC: Radio Resource Control, radio resource control.

PDCP: Packet Data Convergence Protocol, packet data convergence protocol.

RLC: Radio Link Control, radio link control. The transmission mode of the RLC entity can be configured as one of the transparent transmission mode TM, the unconfirmed mode UM, or the confirmed mode AM.

PDU: Protocol Data Unit, protocol data unit.

SDU: Service Data Unit, service data unit.

In this disclosure, data received from or sent to the upper layer is called SDU, and data sent to or received from the lower layer is called PDU. For example, the data received by the PDCP entity from the upper layer or the data sent to the upper layer is called PDCP SDU; the data received by the PDCP entity from the lower layer (that is, the RLC entity) or the data submitted to the RLC entity is called PDCP PDU (that is, RLC SDU) . PDCP PDU is PDCP control PDU or PDCP data PDU. The currently defined PDCP repetition function only supports the PDCP repetition of the PDCP data PDU, so the PDCP repetition described in this disclosure is all for the PDCP data PDU.

PDCP duplication: PDCP duplication means that the same PDCP PDU is sent twice or more times. The PDCP PDU is sent through RLC entities and/or logical channels associated with different carriers or carrier groups, that is, the same PDCP PDU is delivered to two lower layers Or multiple RLC entities. In dual connectivity, the RLC entity and/or logical channel configured with PDCP repeated radio bearers belong to (or are respectively associated with) two different MAC entities. When the radio bearer is configured with PDCP repetition, a secondary RLC entity and a secondary logical channel are added to the radio bearer to process repeated PDCP PDUs.

For radio bearers configured with PDCP repetition (including DRB and SRB), if PDCP repetition is activated, send a PDCP entity (Tansmitting PDCP entity) to copy the PDCP PDU and deliver the PDCP PDU to the associated RLC entity. The RLC entity is It is the RLC entity that is repeatedly activated for PDCP (duplicate the PDCP Data PDU and submit the PDCP Data PDU to the associated RLC entities activated for PDCP duplication); otherwise (corresponding to the case that the PDCP is not satisfied that it is repeatedly activated), for non-separated bearers, send PDCP The entity delivers the PDCP PDU to the main RLC entity. For a separate bearer, if a separate secondary RLC entity is configured and the PDCP data volume and the sum of the amount of RLC data waiting for initial transmission in the primary RLC entity and the separated secondary RLC entity is greater than or equal to ul-DataSplitThreshold(if the total amount of PDCP data volume and RLC data volume pending for initial transmission (as specified in TS 38.322[5]) in the primary RLC entity and the split to secondary RLC equal-response ), the PDCP PDU is submitted to the primary RLC entity or the separate secondary RLC entity (submit the PDCP PDU to either the primary RLC entity or the split secondary RLC entity), otherwise, the PDCP PDU is submitted to the primary RLC entity. Among them, the information element (referred to as a cell or as a parameter) ul-DataSplitThreshold is included in the PDCP-Config cell. For a specific description of the cell, see 3GPP Technical Document TS38.331, and the specific excerpt is as follows:

It should be noted that, in the present disclosure, if the PDCP sending entity of a separate bearer is only associated with two RLC entities, it is considered that this separate bearer is configured with a separate secondary RLC entity, that is, the separate secondary RLC entity of the separate bearer is different from The RLC entity of the primary RLC entity (or called the secondary RLC entity). For a transmitting PDCP entity or radio bearer that is configured with PDCP repetition and PDCP repetition is deactivated, the condition of configuring a separate secondary RLC entity can be replaced with the following conditions: if the PDCP entity is associated with at least two RLC entities and the RLC entity They belong to or are associated with different cell groups (ie, primary cell group MCG and secondary cell group SCG).

In this disclosure, if the radio bearer PDCP entity is associated with more than two RLC entities, the radio bearer PDCP duplication is activated means that at least one secondary RLC entity is activated for PDCP duplication or there is at least one RLC entity other than the primary RLC entity Activated for PDCP repetition.

Primary path: Primary path, also known as the primary RLC entity, used to send PDCP control PDU and PDCP data PDU. The primary path is configured by the parameter primaryPath carried in the RRC message and cannot be deactivated. The primaryPath is used to indicate the cell ID and logical channel ID of the primary RLC entity (Indicates the cell group ID and LCID of the primary RLC entity)

Secondary path: secondary path, which is associated with other RLC entities except the primary path among the RLC entities configured with PDCP repeated DRBs.

Split secondary RLC entity: Split secondary RLC entity. In dual connectivity, except for the primary RLC entity, it is used to separate the RLC entity for bearer operations.

The following describes the information elements involved in the embodiments of the present disclosure.

The information element PDCP-Config is used to set configurable PDCP parameters for signaling radio bearer SRB and/or data radio bearer DRB.

The duplicationState information element is used to indicate the initial uplink PDCP duplication state for the associated RLC entities (indicates the initial uplink PDCP duplication state for the associated RLC entities). If its value is set to true (ie, true), the initial PDCP repeat state of the associated RLC entity is activated. The index of this indication (i.e. duplicationState) is determined by the logical channel identifiers of the RLC entities other than the primary RLC entity in ascending order of the primary cell group MCG followed by the secondary cell group SCG. If duplicationState indicates that the initial PDCP repetition state of at least one associated RLC entity is active, then the initial PDCP repetition state of the corresponding radio bearer is activated; if duplicationState indicates that the initial PDCP repetition state of all associated RLC entities is deactivated , The initial PDCP repetitive state of the corresponding radio bearer is deactivated. When configuring the PDCP repetition of the radio bearer (such as DRB), if the duplicationState does not appear (that is, the RRC message used to configure the radio bearer PDCP repetition does not include the duplicationState), the initial PDCP repetition state is deactivated, in other words the radio The initial PDCP repetition state of the bearer or its corresponding PDCP entity or associated RLC entity is deactivated. duplicationState is included in moreThanTwoRLC.

The information element moreThanTwoRLC is used to configure uplink data transmission when more than 2 RLC entities are associated with one PDCP entity (configures UL data transmission when more than two RLC entities are associated with the PDCP entity); the appearance of this information element indicates that PDCP repetition is configured Or the corresponding radio bearer is configured with PDCP repetition. It can be stipulated that moreThanTwoRLC only applies to DRB. moreThanTwoRLC is included in PDCP-Config.

The information element pdcp-Duplication is used to indicate whether the uplink repetition state is configured and activated when this information element (referred to as the information element) is received. The presence of this information element indicates that PDCP repetition is configured, and the value of this information element is true (ie, true) to indicate that PDCP repetition is activated. The PDCP-Config used to set configurable PDCP information elements for SRB and/or DRB is included in the RRC message sent by the base station or the network to the UE, and the RRC message is used to configure the UE to support PDCP repetitive SRB And/or DRB. pdcp-Duplication is included in PDCP-Config.

Hereinafter, the method for configuring PDCP repetition for radio bearers in the present disclosure will be described. The method may be executed at the user equipment UE or the base station (more specifically, the method may be executed at the RRC entity of the user equipment UE or the base station. ), specifically as described in the following embodiments.

FIG. 1 shows a flowchart of a method 100 for configuring a PDCP repetition for a radio bearer in a user equipment UE based on an embodiment of the present disclosure.

In step S101, the user equipment UE (more specifically, the RRC entity in the user equipment UE) receives an RRC message (for example, an RRC reconfiguration RRC Reconfiguration message) from the base station, and the RRC message contains the information related to the radio bearer (for example, SRB). PDCP repeated configuration related information, such as the information element PDCP-Config or moreThanTwoRLC or pdcp-Duplication.

In step S102, the user equipment UE (more specifically, the RRC entity in the user equipment UE) performs the repeated PDCP configuration of the radio bearer (for example, the SRB) based on the above information.

In one embodiment, if there are more than two RLC entities associated with the SRB, the received PDCP repeated RRC message for configuring the SRB includes (or must include or must include) the pdcp for the SRB -Duplication information element. In other words, when there are more than two RLC entities associated with an SRB (or when there are more than two RLC entities configured for the SRB), the RRC message configured for the SRB contains (or must contain or must contain) to indicate whether PDCP repetition The configured indication identifier pdcp-Duplication, in addition, it can also be specified that its value must or must be set to true (ie, true).

In this disclosure, the RLC entity associated with the radio bearer (ie, SRB or DRB) is the RLC entity associated with the PDCP entity of the radio bearer.

In an embodiment, no matter whether there are two or more RLC entities associated with the radio bearer, the RRC message used to configure PDCP repetition for the radio bearer must include pdcp-Duplication. When the pdcp-Duplication configuration is false (ie false), the PDCP-Config containing the pdcp-Duplication (or the information element moreThanTwoRLC in the PDCP-Config containing the pdcp-Duplication or the RRC message) does not contain information The element duplicationState (duplicationState is absent) or the value of all bits (or bits) of the information element duplicationState are false. When pdcp-Duplication is configured to be true (ie, true), at least one bit of the information element duplicationState is configured to be true.

In the embodiments of the present disclosure, the setting of pdcp-Duplication to true (that is, true) can be replaced by pdcp-Duplication being set to other values indicating the activation of PDCP duplication, and the duplicationState being set to true can be replaced by duplicationState being set to other indicating activation of the corresponding RLC entity The repeated value of PDCP. Correspondingly, pdcp-Duplication set to false (ie false) can also be replaced with pdcp-Duplication set to other values indicating deactivation (or inactivation) of PDCP repetition, duplicationState set to false can also be replaced with duplicationState set to other means to go Activation (or inactivation) corresponds to the value of the PDCP repetition of the RLC entity.

In one embodiment, different processes are repeated for SRB and DRB to activate PDCP. Specifically, for the SRB, if the PDCP entity is configured with pdcp-Duplication or there are more than two associated RLC entities, the PDCP entity (the transmitting PDCP entity) is sent to activate the PDCP repetition. For DRB, if the PDCP entity is configured with pdcp-Duplication or moreThanTwoRLC, the sending PDCP entity performs the following operations:

If the PDCP repetition of the DRB is indicated as active, then the PDCP repetition of the DRB is activated;

If the PDCP repetition of at least one associated RLC entity is indicated as active, then perform: (1) Activate the PDCP repetition of the indicated RLC entity; (2) Preferably, activate the PDCP repetition of the DRB; alternatively, only when this The PDCP repetition of the DRB is activated only when the PDCP repetition of the DRB is in the deactivated state).

If the PDCP repetition of the DRB is indicated as deactivated, the PDCP repetition of the DRB is deactivated;

If the PDCP repetition of at least one associated RLC entity is indicated as deactivated, then deactivate the PDCP repetition of the indicated RLC entity. If the PDCP repetition of other associated RLC entities except the main RLC entity are all deactivated, then deactivate the PDCP repetition of the indicated RLC entity. The PDCP of the DRB is repeated.

The associated RLC entity or all associated RLC entities in the embodiments of the present disclosure refer to the RLC entity associated with the PDCP entity of the radio bearer or all associated RLC entities (except for the master RLC entity, because duplicationState is not used to indicate the master RLC entity). Entity, and the main RLC entity cannot be deactivated).

In the embodiments of the present disclosure, the initial PDCP repetition state is the initial uplink PDCP repetition state, which refers to the PDCP repetition state of the associated RLC entity when the UE receives the RRC message and configures the corresponding SRB or DRB or the corresponding PDCP when the corresponding RLC entity is configured Repeating state or the PDCP repeating state of the corresponding radio bearer when the corresponding SRB or DRB is configured. The initial PDCP repetition state of the RLC entity is activated, which means that the PDCP entity delivers the PDCP PDU to the RLC entity. The initial PDCP repetition state of the RLC entity is deactivated, which means that the PDCP entity does not deliver the PDCP PDU to the RLC entity.

According to the above method executed by the user equipment (more specifically, the method executed by the user equipment RRC entity), it is possible to perform PDCP repeated configuration for signaling radio bearers with more than 2 associated RLC entities, thereby improving the performance of the wireless communication system. reliability.

In addition, FIG. 2 shows a block diagram of the user equipment 20 (more specifically, the RRC entity 20 in the user equipment UE) according to an embodiment of the present disclosure. As shown in FIG. 2, the user equipment 20 includes a processor 201 and a memory 202. The processor 201 may include, for example, a microprocessor, a microcontroller, an embedded processor, and the like. The memory 202 may include, for example, volatile memory (such as random access memory RAM), hard disk drive (HDD), non-volatile memory (such as flash memory), or other memory systems. The memory 202 stores program instructions. When the instruction is executed by the processor 201, the above method in the user equipment described in detail in the present disclosure can be executed.

Furthermore, as an example, FIG. 3 shows a flowchart of a method 300 in a base station based on an embodiment of the present disclosure. In step S301, an RRC message is generated, and the RRC message contains information about the PDCP repeated configuration for the radio bearer. In step S302, the RRC message is sent to the user equipment, so that the user equipment performs the repeated PDCP configuration of the radio bearer based on the information.

According to the above method performed by the base station (more specifically, the method performed by the RRC entity in the base station), it is possible to perform appropriate PDCP repetitive configuration based on the information related to the PDCP repetitive configuration of the radio bearer sent to the user equipment, thereby improving Reliability of wireless communication system.

In addition, FIG. 4 shows a block diagram of a base station 40 (more specifically, an RRC entity 40 in the base station) according to an embodiment of the present disclosure. As shown in FIG. 4, the base station 40 includes a processor 401 and a memory 402. As mentioned above, the base station 40 in this disclosure can be any type of base station, including but not limited to: Node B, enhanced base station eNB, 5G communication system base station gNB, or micro base station, pico base station, macro base station, home base station Wait. The processor 401 may include, for example, a microprocessor, a microcontroller, an embedded processor, and the like. The memory 402 may include, for example, volatile memory (such as random access memory RAM), hard disk drive (HDD), non-volatile memory (such as flash memory), or other memory systems. The memory 402 stores program instructions. When the instruction is executed by the processor 401, the above method in the base station described in detail in the present disclosure can be executed.

The computer-executable instructions or program running on the device according to the present disclosure may be a program that enables the computer to implement the functions of the embodiments of the present disclosure by controlling a central processing unit (CPU). The program or the information processed by the program can be temporarily stored in volatile memory (such as random access memory RAM), hard disk drive (HDD), non-volatile memory (such as flash memory), or other memory systems.

Computer-executable instructions or programs for implementing the functions of various embodiments of the present disclosure may be recorded on a computer-readable storage medium. Corresponding functions can be realized by causing the computer system to read the programs recorded on the recording medium and execute these programs. The so-called "computer system" herein may be a computer system embedded in the device, and may include an operating system or hardware (such as peripheral devices). The "computer-readable storage medium" may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a recording medium storing a program dynamically for a short period of time, or any other recording medium readable by a computer.

Various features or functional modules of the devices used in the above-mentioned embodiments can be implemented or executed by circuits (for example, single-chip or multi-chip integrated circuits). Circuits designed to perform the functions described in this specification can include general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, discrete Gate or transistor logic, discrete hardware components, or any combination of the above devices. The general-purpose processor may be a microprocessor, or any existing processor, controller, microcontroller, or state machine. The above-mentioned circuit can be a digital circuit or an analog circuit. In the case of new integrated circuit technologies that replace existing integrated circuits due to advances in semiconductor technology, one or more embodiments of the present disclosure may also be implemented using these new integrated circuit technologies.

In addition, the present disclosure is not limited to the above-mentioned embodiments. Although various examples of the embodiment have been described, the present disclosure is not limited thereto. Fixed or non-mobile electronic equipment installed indoors or outdoors can be used as terminal equipment or communication equipment, such as AV equipment, kitchen equipment, cleaning equipment, air conditioners, office equipment, vending machines, and other household appliances.

As above, the embodiments of the present disclosure have been described in detail with reference to the drawings. However, the specific structure is not limited to the above-mentioned embodiments, and the present disclosure also includes any design changes that do not deviate from the gist of the present disclosure. In addition, various modifications can be made to the present disclosure within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present disclosure. In addition, the components having the same effects described in the above embodiments may be substituted for each other.

Claims

A configuration method for the PDCP repetition of the signaling radio bearer. When the PDCP entity of the signaling radio bearer is associated with more than two radio link control RLC entities, the configuration message used to configure the PDCP repetition of the signaling radio bearer includes The indicator used to indicate whether PDCP repetition is configured.
An RRC entity that executes the configuration method described in claim 1.