WO2021185202A1 - 用户设备及其方法、基站及其方法 - Google Patents

用户设备及其方法、基站及其方法 Download PDF

Info

Publication number
WO2021185202A1
WO2021185202A1 PCT/CN2021/080742 CN2021080742W WO2021185202A1 WO 2021185202 A1 WO2021185202 A1 WO 2021185202A1 CN 2021080742 W CN2021080742 W CN 2021080742W WO 2021185202 A1 WO2021185202 A1 WO 2021185202A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdcp
drb
rlc entity
user equipment
rrc message
Prior art date
Application number
PCT/CN2021/080742
Other languages
English (en)
French (fr)
Inventor
肖芳英
刘仁茂
罗超
Original Assignee
夏普株式会社
肖芳英
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 夏普株式会社, 肖芳英 filed Critical 夏普株式会社
Priority to US17/911,165 priority Critical patent/US20230110070A1/en
Publication of WO2021185202A1 publication Critical patent/WO2021185202A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • 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

Definitions

  • 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.
  • 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).
  • 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).
  • 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.
  • 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.
  • the present disclosure discusses related issues involved in configuring and/or activating/deactivating PDCP duplication and/or RLC entities.
  • the present disclosure provides a user equipment and a method thereof, a base station and a method thereof, which can be based on information related to the PDCP repetition of the radio bearer and/or the activation configuration of the associated RLC entity Performing proper PDCP repetition and/or activation configuration of the associated RLC entity can improve the communication efficiency and reliability of the wireless communication system.
  • a user equipment including: a receiving unit configured to receive a radio resource control RRC message; and a processing unit, including an indication identifier in the RRC message, the indication identifier indicating a piece of data
  • the processing unit considers that the PDCP repetition of the DRB is activated; In the case that the RRC message does not include the indication identifier, the processing unit considers that the PDCP repetition of the DRB is deactivated.
  • a method executed by a user equipment including: receiving a radio resource control RRC message; and including an indication identifier in the RRC message, the indication identifier indicating a data radio bearer DRB associated If there are other RLC entities other than the main RLC entity in the radio link control RLC entity that are activated for packet data convergence protocol PDCP repetition, the PDCP repetition of the DRB is considered to be active; the RRC message does not include all In the case of the indication flag, it is considered that the PDCP repetition of the DRB is deactivated.
  • a base station including: a generating unit that generates a radio resource control RRC message, and the RRC message includes an indication identifier that indicates a radio link associated with a data radio bearer DRB
  • the RRC message does not contain all
  • the user equipment is made to consider that the PDCP repetition of the DRB is deactivated; and the sending unit sends the RRC message to the user equipment.
  • a method executed by a base station including: generating a radio resource control RRC message, including an indication identifier in the RRC message, the indication identifier indicating a radio link associated with a data radio bearer DRB
  • a radio resource control RRC message including an indication identifier in the RRC message, the indication identifier indicating a radio link associated with a data radio bearer DRB
  • the base station and the method thereof of the present disclosure it is possible to perform appropriate PDCP repetition and/or the associated RLC based on the information related to the PDCP repetition of the radio bearer and/or the activation configuration of the associated RLC entity
  • the active configuration of the entity can thereby improve the communication efficiency and reliability of the wireless communication system.
  • 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.
  • 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.
  • data received from or sent to the upper layer is called SDU
  • data sent to or received from the lower layer is called PDU.
  • 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.
  • Non-split bearer In dual connectivity, the wireless protocol is located in MgNB or SgNB and uses the resources of MgNB or SgNB.
  • Non-separated bearers include non-separated SRB and non-separated DRB.
  • Separate bearer In dual connectivity, the wireless protocol is located in MgNB and SgNB and uses the resources of MgNB and SgNB. Separating the bearer includes separating the SRB and separating the DRB.
  • the information element PDCP-Config is used to set configurable PDCP parameters for signaling radio bearer SRB and/or data radio bearer DRB.
  • 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.
  • the RLC entity and/or logical channel configured with PDCP repeated radio bearers belong to (or are respectively associated with) two different MAC entities.
  • a secondary RLC entity and a secondary logical channel are added to the radio bearer to process repeated PDCP PDUs.
  • PDCP For radio bearers configured with PDCP repetition, if PDCP is repeatedly 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 an RLC that is repeatedly activated for PDCP.
  • the sending PDCP entity sends the PDCP PDU to the master RLC entity, for a separated bearer, if a separate secondary RLC entity is configured and the sum of the PDCP data volume and 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 secondary RLC entity is equal to or large plit ul-DataS PDU will be submitted To the primary RLC entity or to separate the secondary RLC entity (submit the PDCP PDU to either the primary RLC entity or the split
  • the information element (referred to as a cell or as a parameter) ul-DataSplitThreshold is included in the PDCP-Config cell.
  • a cell the information element
  • ul-DataSplitThreshold is included in the PDCP-Config cell.
  • 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).
  • PDCP duplication is activated means that at least one secondary RLC entity is activated for PDCP duplication or at least one RLC entity other than the primary RLC entity is activated. Used for PDCP repetition.
  • 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.
  • FIG. 1 shows a flowchart of a method 100 in a user equipment UE based on an embodiment of the present disclosure.
  • step S101 the user equipment UE receives an RRC message (for example, an RRC reconfiguration RRC Reconfiguration message) from the base station, the RRC message contains information related to the PDCP repetition of the radio bearer and/or the activation configuration of the associated RLC entity, for example It is the parameter PDCP-Config (or the parameter moreThanTwoRLC).
  • RRC message for example, an RRC reconfiguration RRC Reconfiguration message
  • the RRC message contains information related to the PDCP repetition of the radio bearer and/or the activation configuration of the associated RLC entity, for example It is the parameter PDCP-Config (or the parameter moreThanTwoRLC).
  • step S102 the user equipment UE performs the PDCP repetition of the radio bearer and/or the activation configuration of the associated RLC entity based on the above-mentioned information.
  • the PDCP-Config (or the parameter moreThanTwoRLC included in the PDCP-Config or the RRC message) does not include the parameter duplicationState (duplicationState is absent)
  • Operation A The initial PDCP repetition state of all associated RLC entities is activated (applicable to all radio bearers), and/or the PDCP repetition state of the corresponding radio bearer is activated.
  • Operation B The initial PDCP repetitive state of all associated RLC entities is deactivated (applicable to all radio bearers), and/or the PDCP repetitive state of the corresponding radio bearer is deactivated.
  • Operation C For SRB, the initial PDCP repetition status of all associated RLC entities is activated and/or the PDCP repetition status of the corresponding SRB is activated; for DRB, the initial PDCP repetition status of all associated RLC entities is deactivated And/or the PDCP repetition status corresponding to the DRB is deactivated.
  • the parameter duplicationState only applies to DRB, that is, this parameter can be included only when PDCP repetition is configured for DRB; when configuring an SRB that supports PDCP repetition, the RRC message or parameter PDCP-Config or parameter moreThanTwoRLC The parameter duplicationState is not carried or the UE ignores the value of the received duplicationState (in other words, no matter what the value of the parameter duplicationState is, the initial PDCP repetition state of all associated RLC entities is always considered to be active).
  • the UE ignores the value of the parameter duplicationState. In other words, no matter what the value of the parameter duplicationState is, it is always considered that the initial PDCP repetition state of all associated RLC entities is active.
  • the parameter moreThanTwoRLC when configuring the SRB, if the parameter moreThanTwoRLC appears in the RRC message or the parameter PDCP-Config, the parameter moreThanTwoRLC must or must also appear in the parameter duplicationState.
  • the duplicationState parameter indicates that the initial PDCP duplication state of all associated RLC entities is activated.
  • the initial PDCP repetition state of the SRB is activated.
  • the parameter moreThanTwoRLC when configuring DRB, if the parameter moreThanTwoRLC appears in the RRC message or the parameter PDCP-Config, the parameter moreThanTwoRLC must also appear in the duplicationState parameter.
  • the associated RLC entity or all associated RLC entities refers 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 the duplicationState parameter is not used to indicate the master RLC entity, and the main RLC entity cannot be deactivated).
  • Signaling radio bearer SRB includes non-separated SRB and separated SRB
  • data radio bearer DRB includes non-separated DRB and separated DRB
  • radio bearer includes SRB and DRB.
  • 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.
  • the parameter duplicationState indicates the initial uplink PDCP duplication state of the associated RLC entity (indicates the initial uplink PDCP duplication state for the associated RLC entities). If its value is set to 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.
  • 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.
  • the parameter moreThanTwoRLC configures uplink data transmission when more than two RLC entities are associated with this PDCP entity (configures UL data transmission when more than two RLC entities are associated with the PDCP entity); the presence of this parameter indicates that PDCP repetition or correspondence is configured
  • the radio bearer is configured with PDCP repetition.
  • the user equipment it is possible to perform appropriate PDCP repetition and/or activation configuration of the associated RLC entity based on the information related to the PDCP repetition of the radio bearer and/or the activation configuration of the associated RLC entity, thereby It can improve the communication efficiency and reliability of the wireless communication system.
  • FIG. 2 shows a block diagram of the user equipment 20 according to an embodiment of the present disclosure.
  • 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.
  • FIG. 3 shows a flowchart of a method 300 in a base station based on an embodiment of the present disclosure.
  • an RRC message is generated, and the RRC message contains information related to the PDCP repetition of the radio bearer and/or the activation configuration of the associated RLC entity.
  • the RRC message is sent to the user equipment, so that the user equipment performs the PDCP repetition of the radio bearer and/or the activation configuration of the associated RLC entity based on the information.
  • the base station it is possible to perform appropriate PDCP repetition and/or the associated RLC entity based on the information related to the PDCP repetition of the radio bearer and/or the activation configuration of the associated RLC entity sent to the user equipment.
  • the activation configuration can improve the communication efficiency and reliability of the wireless communication system.
  • FIG. 4 shows a block diagram of a base station 40 according to an embodiment of the present disclosure.
  • the base station 40 includes a processor 401 and a memory 402.
  • 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.
  • 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开提供一种用户设备及其方法、基站及其方法。由用户设备执行的方法包括: 从基站接收无线资源控制RRC消息，该RRC消息中包含与无线承载的分组数据汇聚协议PDCP重复和/或所关联的无线链路控制RLC实体的激活配置有关的信息; 以及基于所述信息，进行无线承载的PDCP重复和/或所关联的RLC实体的激活配置。由此，能够提高无线通信系统的通信效率以及可靠性。

Description

用户设备及其方法、基站及其方法 技术领域
本公开涉及无线通信技术领域，更具体地，本公开涉及用户设备及其方法、基站及其方法。
背景技术
2018年9月，在第三代合作伙伴计划(3rd Generation Partnership Project：3GPP)RAN#81次全会上，Nokia提出了一个关于5G(或称为NR)工业物联网(IIOT)的研究项目(参见非专利文献：RP-182090：Revised SID：Study on NR Industrial Internet of Things(IIoT))，并获批准。该研究项目的目标之一是通过数据重复(data duplication)来提高数据传输的可靠性和减少数据传输的时延，具体包括：(1)资源有效的PDCP重复，例如避免不必要的重复传输；(2)利用双连接DC或载波聚合CA实现超过两次的PDCP重复。
在版本15中，支持PDCP重复的承载最多可以配置两个RLC实体。配置了PDCP重复的承载的初始状态是通过pdcp-Duplication信元(所述信元的具体描述见3GPP TS38.331)来指示初始时是否激活PDCP重复功能。在载波聚合中，对于初始PDCP重复功能未激活的承载，其数据通过primaryPath信元(所述信元的具体描述见3GPP TS38.331)指示的逻辑信道发送。在双连接中，对于初始PDCP重复功能未激活的承载，根据待发送数据量的多少来决定数据是通过primaryPath信元指示的逻辑信道发送还是采用分离承载方式发送。
在NR IIOT中，为达成利用双连接或载波聚合实现两次或两次以上的PDCP重复这一目标，部分厂商提出为支持PDCP重复的承载配置多个RLC实体但每次仅激活其中的若干个RLC实体的方式(即配置了PDCP重复的PDCP实体将PDCP PDU递交给所关联的且激活的两个或两个以上RLC实体)。网络可以通过RRC信令或媒体访问控制控制元素MAC CE来指示是 否激活PDCP重复和/或激活的RLC实体。本公开讨论配置和/或激活/去激活PDCP重复和/或RLC实体所涉及的相关问题。
发明内容
为了解决现有技术中的上述问题，本公开提供了一种用户设备及其方法、基站及其方法，能够基于与无线承载的PDCP重复和/或所关联的RLC实体的激活配置有关的信息来执行适当的PDCP重复和/或所关联的RLC实体的激活配置，从而能够提高无线通信系统的通信效率以及可靠性。
根据本公开的第一方面，提供了一种用户设备，包括：接收单元，被配置为接收无线资源控制RRC消息；以及处理单元，在所述RRC消息中包含指示标识，该指示标识指示一个数据无线承载DRB关联的无线链路控制RLC实体中存在除主RLC实体外的其他RLC实体被激活用于分组数据汇聚协议PDCP重复的情况下，该处理单元认为该DRB的PDCP重复是激活的；在所述RRC消息中不包含所述指示标识的情况下，该处理单元认为该DRB的PDCP重复是去激活的。
根据本公开的第二方面，提供了一种由用户设备执行的方法，包括：接收无线资源控制RRC消息；以及在所述RRC消息中包含指示标识，该指示标识指示一个数据无线承载DRB关联的无线链路控制RLC实体中存在除主RLC实体外的其他RLC实体被激活用于分组数据汇聚协议PDCP重复的情况下，认为该DRB的PDCP重复是激活的；在所述RRC消息中不包含所述指示标识的情况下，认为该DRB的PDCP重复是去激活的。
根据本公开的第三方面，提供了一种基站，包括：生成单元，生成无线资源控制RRC消息，在所述RRC消息中包含指示标识，该指示标识指示一个数据无线承载DRB关联的无线链路控制RLC实体中存在除主RLC实体外的其他RLC实体被激活用于分组数据汇聚协议PDCP重复的情况下，使用户设备认为该DRB的PDCP重复是激活的；在所述RRC消息中不包含所述指示标识的情况下，使用户设备认为该DRB的PDCP重复是去激活的；以及发送单元，向用户设备发送所述RRC消息。
根据本公开的第四方面，提供了一种由基站执行的方法，包括：生成无线资源控制RRC消息，在所述RRC消息中包含指示标识，该指示标识指示一个数据无线承载DRB关联的无线链路控制RLC实体中存在除主 RLC实体外的其他RLC实体被激活用于分组数据汇聚协议PDCP重复的情况下，使用户设备认为该DRB的PDCP重复是激活的；在所述RRC消息中不包含所述指示标识的情况下，使用户设备认为该DRB的PDCP重复是去激活的；以及向用户设备发送所述RRC消息。
发明效果
根据本公开的用户设备及其方法、基站及其方法，能够基于与无线承载的PDCP重复和/或所关联的RLC实体的激活配置有关的信息来执行适当的PDCP重复和/或所关联的RLC实体的激活配置，从而能够提高无线通信系统的通信效率以及可靠性。
附图说明
通过下文结合附图的详细描述，本公开的上述和其它特征将会变得更加明显，其中：
图1表示基于本公开的实施例的用户设备UE中的方法100的流程图。
图2表示基于本公开的实施例的用户设备20的框图。
图3表示基于本公开的实施例的基站中的方法300的流程图。
图4表示基于本公开的实施例的基站40的框图。
具体实施方式
下面结合附图和具体实施方式对本公开进行详细阐述。应当注意，本公开不应局限于下文所述的具体实施方式。另外，为了简便起见，省略了对与本公开没有直接关联的公知技术的详细描述，以防止对本公开的理解造成混淆。
下面描述本公开涉及的部分术语，如未特别说明，本公开涉及的术语采用此处定义。
RRC：Radio Resource Control，无线资源控制。
PDCP：Packet Data Convergence Protocol，分组数据汇聚协议。
RLC：Radio Link Control，无线链路控制。RLC实体的传输模式可以配置为透传模式TM、非确认模式UM或确认模式AM之一。
PDU：Protocol Data Unit，协议数据单元。
SDU：Service Data Unit，服务数据单元。
在本公开中，将从上层接收或发往上层的数据称为SDU，将发往下层或从下层接收的数据称为PDU。例如，PDCP实体从上层接收的数据或发往上层的数据称为PDCP SDU；PDCP实体从下层(即RLC实体)接收到的数据或递交给RLC实体的数据称为PDCP PDU(也就是RLC SDU)。PDCP PDU是PDCP控制PDU或PDCP数据PDU。目前定义的PDCP重复功能仅支持PDCP数据PDU的PDCP重复，所以本公开所述PDCP重复均是针对PDCP数据PDU。
非分离承载：Non-split bearer，在双连接中，无线协议位于MgNB或SgNB并使用MgNB或SgNB的资源的承载。非分离承载包括非分离SRB和非分离DRB。
分离承载：Split bearer，在双连接中，无线协议位于MgNB和SgNB并使用MgNB和SgNB的资源的承载。分离承载包括分离SRB和分离DRB。
PDCP-Config信元：所述信元PDCP-Config用于为信令无线承载SRB和/或数据无线承载DRB设置可配置的PDCP参数。
PDCP重复：PDCP duplication，是指同一PDCP PDU发送两次或多次，所述PDCP PDU通过关联到不同载波或载波组的RLC实体和/或逻辑信道发送，即同一PDCP PDU递交给下层的两个或多个RLC实体。在双连接中，所述配置了PDCP重复的无线承载的RLC实体和/或逻辑信道分属于(或分别关联到)两个不同的MAC实体。当无线承载配置了PDCP重复时，为所述无线承载增加辅RLC实体和辅逻辑信道来处理重复的PDCP PDU。
对于配置了PDCP重复的无线承载，如果PDCP重复被激活，发送PDCP实体(Tansmitting PDCP entity)复制PDCP PDU并将所述PDCP PDU递交给关联的RLC实体，所述RLC实体是为PDCP重复激活的RLC实体(duplicate the PDCP Data PDU and submit the PDCP Data PDU to the associated RLC entities activated for PDCP duplication)；否则(对应不满足PDCP重复被激活的情况)，对于非分离承载，发送PDCP实体将PDCP PDU递交主RLC实体，对于分离承载，如果配置了分离辅RLC实体并且PDCP数据量(data volumn)和主RLC实体以及分离辅RLC实体中等待初始传输的RLC数据量的总和大于或等于ul-DataSplitThreshold(ifthe 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 secondary RLC entity is equal to or larger than ul-DataSplitThreshold)，则将PDCP PDU递交给主RLC实体或分离辅RLC实体(submit the PDCP PDU to either the primary RLC entity or the split secondary RLC entity)，否则，将PDCP PDU递交给主RLC实体。其中，信息元素(简称信元或称为参数)ul-DataSplitThreshold包含在PDCP-Config信元中，关于所述信元的具体描述见3GPP技术文挡TS38.331，具体摘录如下：
Figure PCTCN2021080742-appb-000001
需要说明的是，在本公开中，如果分离承载的发送PDCP实体仅关联了两个RLC实体，则认为这个分离承载配置了分离辅RLC实体，即所述分离承载的分离辅RLC实体就是不同于主RLC实体的RLC实体(或称辅RLC实体)。对配置了PDCP重复且PDCP重复被去激活的发送PDCP实体或无线承载而言，配置了分离辅RLC实体这个条件可以用以下条件替换：如果PDCP实体关联了至少两个RLC实体且所述RLC实体分别属于或关联到不同的小区组(即主小区组MCG和辅小区组SCG)。
在本公开中，如果无线承载PDCP实体关联的RLC实体超过两个，PDCP重复被激活是指至少存在一个辅RLC实体被激活用于PDCP重复或至少存在除主RLC实体外的一个RLC实体被激活用于PDCP重复。
主路径：Primary path，也称为主RLC实体，用于发送PDCP控制PDU和PDCP数据PDU，主路径通过RRC消息中携带的参数primaryPath配置且不能被去激活。所述primaryPath用于指示主RLC实体的小区标识和逻辑信道标识(Indicates the cell group ID and LCID of the primary RLC entity)
辅路径：secondary path，关联到配置了PDCP重复的DRB的RLC实体中除主路径外的其他RLC实体。
分离辅RLC实体：Split secondary RLC entity，在双连接中，除主RLC实体外用于分离承载操作的RLC实体。
下面，对本公开中的用户设备UE中的方法进行说明，具体而言，对用户设备UE中配置无线承载的PDCP重复所涉及的控制方法进行说明。作为一例，图1中表示基于本公开的实施例的用户设备UE中的方法100的流程图。
在步骤S101中，用户设备UE从基站接收RRC消息(例如RRC重配置RRCReconfiguration消息)，所述RRC消息中包含与无线承载的PDCP重复和/或所关联的RLC实体的激活配置有关的信息，例如为参数PDCP-Config(或者参数moreThanTwoRLC)。
在步骤S102中，用户设备UE基于上述信息，进行无线承载的PDCP重复和/或所关联的RLC实体的激活配置。
在一个实施例中，如果所述PDCP-Config(或者包含在所述PDCP-Config中的参数moreThanTwoRLC或者所述RRC消息)中不包含参数duplicationState(duplicationState is absent)，则执行以下操作A～C至少一项：
操作A：所关联的所有RLC实体的初始PDCP重复状态是激活(activated)的(适用于所有无线承载)，并且/或者对应无线承载的PDCP重复状态是激活的。
操作B：所关联的所有RLC实体的初始PDCP重复状态是去激活(deactivated)的(适用于所有无线承载)，并且/或者对应无线承载的PDCP重复状态是去激活的。
操作C：对于SRB，所关联的所有RLC实体的初始PDCP重复状态是激活的并且/或者对应SRB的PDCP重复状态是激活的；对于DRB，所关联的所有RLC实体的初始PDCP重复状态是去激活的并且/或者对应DRB的PDCP重复状态是去激活的。
在一个实施例中，参数duplicationState仅应用于DRB，即只有在为DRB配置PDCP重复时才可以包含这个参数；在配置支持PDCP重复的SRB时，所述RRC消息或参数PDCP-Config或参数moreThanTwoRLC中不携带参数duplicationState或者UE忽略接收到的duplicationState的取值(换言之，无论参数duplicationState的取值是什么，总是认为所关联的所有RLC实体的初始PDCP重复状态是激活的)。
在一个实施例中，对于SRB，如果所述RRC消息或参数PDCP-Config中出现参数moreThanTwoRLC，则所关联的所有RLC实体的初始PDCP重复状态是激活的；可选的，如果参数moreThanTwoRLC中出现参数duplicationState，UE忽略参数duplicationState的取值。换言之，无论参数duplicationState的取值是什么，总是认为所关联的所有RLC实体的初始PDCP重复状态是激活的。
在一个实施例中，在配置SRB时，如果所述RRC消息或参数PDCP-Config中出现参数moreThanTwoRLC，则所述参数moreThanTwoRLC中也必须或必定出现duplicationState参数。可选的，duplicationState参数指示所关联的所有RLC实体的初始PDCP重复状态是激活的。
在一个实施例中，对于SRB，如果所述RRC消息或参数PDCP-Config中出现参数moreThanTwoRLC，则认为所述SRB的初始PDCP重复状态是激活的。
在一个实施例中，在配置DRB时，如果所述RRC消息或参数PDCP-Config中出现参数moreThanTwoRLC，则所述参数moreThanTwoRLC也必须出现duplicationState参数。
本公开实施例中所述所关联的RLC实体或所关联的所有RLC实体是指无线承载的PDCP实体关联的RLC实体或关联的所有RLC实体(但主RLC实体除外，因为duplicationState参数不用于指示主RLC实体，且主RLC实体不能被去激活)。信令无线承载SRB包含非分离SRB和分离SRB，数据无线承载DRB包含非分离DRB和分离DRB，无线承载包括SRB和DRB。
本公开实施例中，初始PDCP重复状态就是初始上行PDCP重复状态，是指UE接收到RRC消息并配置对应SRB或DRB时关联的RLC实体的PDCP重复状态或者配置对应的RLC实体时其对应的PDCP重复状态或者配置对应的SRB或DRB时对应无线承载的PDCP重复状态。RLC实体的初始PDCP重复状态是激活的表示PDCP实体将PDCP PDU递交给所述RLC实体。RLC实体的初始PDCP重复状态是去激活的表示PDCP实体不将PDCP PDU递交给所述RLC实体。
下面描述对本公开实施例中所涉及的参数。
所述参数duplicationState指示所关联的RLC实体的初始上行PDCP重 复状态(indicates the initial uplink PDCP duplication state for the associated RLC entities)。如果其值设置为true，则关联的RLC实体的初始PDCP重复状态是激活的。这个指示(即duplicationState)的索引由除主RLC实体外的RLC实体的逻辑信道标识按照先主小区组MCG后辅小区组SCG的方式升序排列决定。如果duplicationState指示至少有一个关联的RLC实体的初始PDCP重复状态是激活的，则对应无线承载的初始PDCP重复状态是激活的；如果duplicationState指示所关联的所有RLC实体的初始PDCP重复状态是去激活的，则对应无线承载的初始PDCP重复状态是去激活的。
所述参数moreThanTwoRLC配置当超过两个RLC实体关联到这个PDCP实体时的上行数据传输(configures UL data transmission when more than two RLC entities are associated with the PDCP entity)；这个参数出现表示配置了PDCP重复或对应的无线承载配置了PDCP重复。
根据上述由用户设备执行的方法，能够基于与无线承载的PDCP重复和/或所关联的RLC实体的激活配置有关的信息来执行适当的PDCP重复和/或所关联的RLC实体的激活配置，从而能够提高无线通信系统的通信效率以及可靠性。
此外，图2示出了根据本公开的实施例的用户设备20的框图。如图2所示，该用户设备20包括处理器201和存储器202。处理器201例如可以包括微处理器、微控制器、嵌入式处理器等。存储器202例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统等。存储器202上存储有程序指令。该指令在由处理器201运行时，可以执行本公开详细描述的用户设备中的上述方法。
再有，作为一例，图3中表示基于本公开的实施例的基站中的方法300的流程图。在步骤S301中，生成RRC消息，该RRC消息中包含与无线承载的PDCP重复和/或所关联的RLC实体的激活配置有关的信息。在步骤S302中，将所述RRC消息发送至用户设备，使用户设备基于所述信息进行 无线承载的PDCP重复和/或所关联的RLC实体的激活配置。
根据上述由基站执行的方法，能够基于向用户设备发送的与无线承载的PDCP重复和/或所关联的RLC实体的激活配置有关的信息来执行适当的PDCP重复和/或所关联的RLC实体的激活配置，从而能够提高无线通信系统的通信效率以及可靠性。
此外，图4示出了根据本公开实施例的基站40的框图。如图4所示，该基站40包括处理器401和存储器402。如上述所述，本公开中的基站40可以是任何类型基站，包含但不限于：Node B、增强基站eNB，也可以是5G通信系统基站gNB、或者微基站、微微基站、宏基站、家庭基站等。处理器401例如可以包括微处理器、微控制器、嵌入式处理器等。存储器402例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统等。存储器402上存储有程序指令。该指令在由处理器401运行时，可以执行本公开详细描述的基站中的上述方法。
运行在根据本公开的设备上的计算机可执行指令或者程序可以是通过控制中央处理单元(CPU)来使计算机实现本公开的实施例功能的程序。该程序或由该程序处理的信息可以临时存储在易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统中。
用于实现本公开各实施例功能的计算机可执行指令或程序可以记录在计算机可读存储介质上。可以通过使计算机系统读取记录在所述记录介质上的程序并执行这些程序来实现相应的功能。此处的所谓“计算机系统”可以是嵌入在该设备中的计算机系统，可以包括操作系统或硬件(如外围设备)。“计算机可读存储介质”可以是半导体记录介质、光学记录介质、磁性记录介质、短时动态存储程序的记录介质、或计算机可读的任何其他记录介质。
用在上述实施例中的设备的各种特征或功能模块可以通过电路(例如，单片或多片集成电路)来实现或执行。设计用于执行本说明书所描述的功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路 (ASIC)、现场可编程门阵列(FPGA)、或其他可编程逻辑器件、分立的门或晶体管逻辑、分立的硬件组件、或上述器件的任意组合。通用处理器可以是微处理器，也可以是任何现有的处理器、控制器、微控制器、或状态机。上述电路可以是数字电路，也可以是模拟电路。因半导体技术的进步而出现了替代现有集成电路的新的集成电路技术的情况下，本公开的一个或多个实施例也可以使用这些新的集成电路技术来实现。
此外，本公开并不局限于上述实施例。尽管已经描述了所述实施例的各种示例，但本公开并不局限于此。安装在室内或室外的固定或非移动电子设备可以用作终端设备或通信设备，如AV设备、厨房设备、清洁设备、空调、办公设备、自动贩售机、以及其他家用电器等。
如上，已经参考附图对本公开的实施例进行了详细描述。但是，具体的结构并不局限于上述实施例，本公开也包括不偏离本公开主旨的任何设计改动。另外，可以在权利要求的范围内对本公开进行多种改动，通过适当地组合不同实施例所公开的技术手段所得到的实施例也包含在本公开的技术范围内。此外，上述实施例中所描述的具有相同效果的组件可以相互替代。

Claims (8)

  1. 一种用户设备，包括：
    接收单元，被配置为接收无线资源控制RRC消息；以及
    处理单元，在所述RRC消息中包含指示标识，该指示标识指示一个数据无线承载DRB关联的无线链路控制RLC实体中存在除主RLC实体外的其他RLC实体被激活用于分组数据汇聚协议PDCP重复的情况下，该处理单元认为该DRB的PDCP重复是激活的；在所述RRC消息中不包含所述指示标识的情况下，该处理单元认为该DRB的PDCP重复是去激活的。
  2. 根据权利要求1所述的用户设备，其中，
    所述指示标识仅应用于DRB。
  3. 一种由用户设备执行的方法，包括：
    接收无线资源控制RRC消息；以及
    在所述RRC消息中包含指示标识，该指示标识指示一个数据无线承载DRB关联的无线链路控制RLC实体中存在除主RLC实体外的其他RLC实体被激活用于分组数据汇聚协议PDCP重复的情况下，认为该DRB的PDCP重复是激活的；在所述RRC消息中不包含所述指示标识的情况下，认为该DRB的PDCP重复是去激活的。
  4. 根据权利要求3所述的方法，其中，
    所述指示标识仅应用于DRB。
  5. 一种基站，包括：
    生成单元，生成无线资源控制RRC消息，在所述RRC消息中包含指示标识，该指示标识指示一个数据无线承载DRB关联的无线链路控制RLC实体中存在除主RLC实体外的其他RLC实体被激活用于分组数据汇聚协议PDCP重复的情况下，使用户设备认为该DRB的PDCP重复是激活的；在所述RRC消息中不包含所述指示标识的情况下，使用户设备认为该DRB的PDCP重复是去激活的；以及
    发送单元，向用户设备发送所述RRC消息。
  6. 根据权利要求5所述的基站，其中，
    所述指示标识仅应用于DRB。
  7. 一种由基站执行的方法，包括：
    生成无线资源控制RRC消息，在所述RRC消息中包含指示标识，该指示标识指示一个数据无线承载DRB关联的无线链路控制RLC实体中存在除主RLC实体外的其他RLC实体被激活用于分组数据汇聚协议PDCP重复的情况下，使用户设备认为该DRB的PDCP重复是激活的；在所述RRC消息中不包含所述指示标识的情况下，使用户设备认为该DRB的PDCP重复是去激活的；以及
    向用户设备发送所述RRC消息。
  8. 根据权利要求7所述的方法，其中，
    所述指示标识仅应用于DRB。
PCT/CN2021/080742 2020-03-18 2021-03-15 用户设备及其方法、基站及其方法 WO2021185202A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US17/911,165 US20230110070A1 (en) 2020-03-18 2021-03-15 User equipment and method thereof, and base station and method thereof

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010193855.6 2020-03-18
CN202010193855.6A CN113498220A (zh) 2020-03-18 2020-03-18 用户设备及其方法、基站及其方法

Publications (1)

Publication Number Publication Date
WO2021185202A1 true WO2021185202A1 (zh) 2021-09-23

Family

ID=77770723

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/080742 WO2021185202A1 (zh) 2020-03-18 2021-03-15 用户设备及其方法、基站及其方法

Country Status (3)

Country Link
US (1) US20230110070A1 (zh)
CN (1) CN113498220A (zh)
WO (1) WO2021185202A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117202257A (zh) * 2022-05-31 2023-12-08 荣耀终端有限公司 一种用户数据处理方法和装置
WO2024192643A1 (en) * 2023-03-20 2024-09-26 Nokia Shanghai Bell Co., Ltd. Selective duplication

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190098533A1 (en) * 2017-09-25 2019-03-28 Alireza Babaei Packet Duplication Activation And Deactivation
CN110691421A (zh) * 2018-07-06 2020-01-14 华为技术有限公司 数据传输方法及装置
CN110856275A (zh) * 2019-11-07 2020-02-28 展讯通信（上海）有限公司 Drb的配置方法及相关装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190098533A1 (en) * 2017-09-25 2019-03-28 Alireza Babaei Packet Duplication Activation And Deactivation
CN110691421A (zh) * 2018-07-06 2020-01-14 华为技术有限公司 数据传输方法及装置
CN110856275A (zh) * 2019-11-07 2020-02-28 展讯通信（上海）有限公司 Drb的配置方法及相关装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
FUJITSU: "R2-1913166: MAC CE structure for PDCP duplication activation deactivation", 3GPP TSG-RAN WG2 MEETING #107BIS, 18 October 2019 (2019-10-18), XP051791180 *
HUAWEI ET AL.: "R2-1808423: Discussion on PDCP Duplication in L2 Parameters", 3GPP TSG-RAN WG2 MEETING 102, 25 May 2018 (2018-05-25), XP051519819 *

Also Published As

Publication number Publication date
US20230110070A1 (en) 2023-04-13
CN113498220A (zh) 2021-10-12

Similar Documents

Publication Publication Date Title
JP6868834B2 (ja) デュアルコネクティビティのための効率的アップリンクスケジューリングメカニズム
CN110012454B (zh) 用户设备和相关方法
US11381994B2 (en) Method for delivering data packet, user equipment, and base station
CN109246766B (zh) 无线配置方法和相应的用户设备
WO2018171512A1 (zh) 无线配置方法、用户设备和基站
WO2020119638A1 (zh) 用户设备及其方法、基站及其方法
US20200170072A1 (en) Wireless communication method and device
JP2019508931A (ja) ＰｒｏＳｅ通信における自律的なリソース割当ての場合に優先順位に基づいて最適化されるサイドリンクデータ伝送
WO2020024847A1 (zh) 接入控制方法及用户设备
CN109246710B (zh) 基站、用户设备和相关方法
WO2021185202A1 (zh) 用户设备及其方法、基站及其方法
WO2021197036A1 (zh) 由用户设备执行的方法以及用户设备
JP2020532158A (ja) 無線通信方法、端末デバイス及びネットワークデバイス
WO2020119640A1 (zh) 用户设备及其方法、基站及其方法
WO2019029567A1 (zh) 基站、用户设备和相关方法
WO2021223623A1 (zh) 针对信令无线承载pdcp重复的配置方法及rrc实体
WO2020119632A1 (zh) 用户设备及其方法、基站及其方法
TW201921977A (zh) 服務資料單元處理方法、丟棄方法、相應的使用者設備和電腦可讀媒體
WO2021109933A1 (zh) 用户设备及其方法、基站及其方法
WO2018059148A1 (zh) 一种数据转发的方法及其设备
WO2020221155A1 (zh) 基站、用户设备和相关方法
WO2021027685A1 (zh) Pdcp实体发送端/接收端的执行方法、pdcp实体及通信设备
WO2020156316A1 (zh) Iab网络、mac实体和适配实体的执行方法以及通信设备
WO2024120476A1 (zh) 由用户设备执行的方法以及用户设备
WO2024032500A1 (zh) 由用户设备执行的方法以及用户设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21770609

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21770609

Country of ref document: EP

Kind code of ref document: A1