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

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

Info

Publication number
WO2021109933A1
WO2021109933A1 PCT/CN2020/132183 CN2020132183W WO2021109933A1 WO 2021109933 A1 WO2021109933 A1 WO 2021109933A1 CN 2020132183 W CN2020132183 W CN 2020132183W WO 2021109933 A1 WO2021109933 A1 WO 2021109933A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdcp
rlc entity
entity
indication
data
Prior art date
Application number
PCT/CN2020/132183
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/780,574 priority Critical patent/US20230007531A1/en
Publication of WO2021109933A1 publication Critical patent/WO2021109933A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1864—ARQ related signaling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1896—ARQ related signaling
    • 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
    • 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).
  • NR IIoT in order to achieve the goal of using dual connectivity or carrier aggregation to achieve more than two PDCP repetitions, some manufacturers propose to configure multiple RLC entities to support PDCP repetitive bearers, but only activate several RLC entities at a time. the way.
  • the network can indicate whether to activate PDCP repetition and the 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 perform appropriate PDCP repetition and/or based on information indicating PDCP repetition and/or activation configuration of an RLC entity Or the activation configuration of the RLC entity, which can improve the communication efficiency and reliability of the wireless communication system.
  • a user equipment including: a receiving unit configured to receive an RRC message including a first indication and a second indication, the first indication being used to indicate a radio bearer The first cell group associated with the primary RLC entity and the first logical channel, the second indication is used to indicate the second logical channel associated with the secondary RLC entity of the radio bearer, and the secondary RLC entity is associated with a different A second cell group of the first cell group; and a sending unit configured to wait when the PDCP of the radio bearer is repeatedly deactivated and the amount of PDCP data and the primary RLC entity and the secondary RLC entity When the total amount of initially transmitted data is greater than or equal to the data transmission threshold ul-DataSplitThreshold, the PDCP PDU is delivered to the primary RLC entity or to the secondary RLC entity, and the data transmission threshold ul-DataSplitThreshold is sent by the base station through an RRC message Configured for the UE.
  • a method executed by a user equipment including: receiving an RRC message containing a first indication and a second indication, the first indication being used to indicate that a primary RLC entity of a radio bearer is associated A first cell group and a first logical channel, the second indication is used to indicate a second logical channel associated with a secondary RLC entity of the radio bearer, and the secondary RLC entity is associated with a second logical channel that is different from the first cell group.
  • the data transmission threshold ul-DataSplitThreshold is configured for the UE by the base station through an RRC message.
  • a base station including: a generating unit that generates an RRC message including a first indication and a second indication, the first indication being used to indicate a first indication associated with a primary RLC entity of a radio bearer A cell group and a first logical channel, the second indication is used to indicate a second logical channel associated with a secondary RLC entity of the radio bearer, and the secondary RLC entity is associated with a second cell different from the first cell group Group; and a sending unit that sends the RRC message to the user equipment, and the sending unit also sends to the user equipment an RRC message containing a data transmission threshold ul-DataSplitThreshold, which is used to enable the user equipment in the radio bearer
  • a data transmission threshold ul-DataSplitThreshold which is used to enable the user equipment in the radio bearer
  • a method executed by a base station including: generating an RRC message including a first indication and a second indication, the first indication being used to indicate the first indication associated with the primary RLC entity of the radio bearer A cell group and a first logical channel, the second indication is used to indicate a second logical channel associated with a secondary RLC entity of the radio bearer, and the secondary RLC entity is associated with a second logical channel different from the first cell group Cell group; and sending the RRC message to the user equipment, the method further includes: sending to the user equipment an RRC message containing a data transmission threshold ul-DataSplitThreshold, the data transmission threshold being used to enable the user equipment to be in the PDCP of the radio bearer When repeatedly deactivated and the PDCP data volume and the total amount of data waiting for initial transmission in the primary RLC entity and the secondary RLC entity are greater than or equal to the data transmission threshold, the PDCP PDU will be delivered to the primary RLC entity or
  • the appropriate PDCP repetition and/or the activation configuration of the RLC entity can be performed based on the information indicating the PDCP repetition and/or the activation configuration of the RLC entity, thereby being able to improve wireless communication The communication efficiency and reliability of the system.
  • Fig. 1 shows a flowchart of a method 100 in a user equipment UE based on an embodiment of the present disclosure.
  • Figure 2 shows a schematic diagram of the first MAC CE.
  • Figure 3 shows a schematic diagram of the second MAC CE.
  • FIG. 4 shows a block diagram of a user equipment 40 based on an embodiment of the present disclosure.
  • FIG. 5 shows a flowchart of a method 500 in a base station based on an embodiment of the present disclosure.
  • FIG. 6 shows a block diagram of a base station 60 based on an embodiment of the present disclosure.
  • Fig. 7 shows a schematic diagram of the correspondence among PDCP entities, RLC entities, logical channels, and MAC entities.
  • 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.
  • MAC Medium Access Control, media access control.
  • MAC CE MAC Control Element, MAC control element.
  • PDU Protocol Data Unit, protocol data unit.
  • SDU Service Data Unit, service data unit.
  • data received from or sent to the upper layer is referred to as SDU
  • data sent to or received from the lower layer is referred to as 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 RLC entity or the data sent to the RLC entity is called PDCP PDU (that is, RLC SDU).
  • the PDCP PDU may be a PDCP control PDU or a PDCP data PDU.
  • the information element PDCP-Config is used to set configurable PDCP parameters for signaling bearers and/or data bearers.
  • RLC-BearerConfig information element The information element RLC-BearerConfig is used to configure the association between the RLC entity, the corresponding logical channel in the MAC, and the PDCP entity (service bearer) (used to configure an RLC entity, a corresponding logical channel in MAC) and the linking to a PDCP entity (served radio bearer)).
  • Primary cell group Master Cell Group, MCG.
  • Primary cell Primary Cell, PCell.
  • the MCG cell working on the primary frequency, on which the UE performs the initial connection establishment process or initiates the connection re-establishment process.
  • Primary SCG cell Primary SCG Cell, PSCell.
  • the SCG cell used by the UE to perform random access in performing synchronous reconfiguration.
  • Secondary cell Secondary Cell, SCell.
  • a UE configured with CA is a cell that provides additional radio resources on the basis of a special cell.
  • Secondary cell group Secondary Cell Group, SCG.
  • SCG Secondary Cell Group, SCG.
  • a subset of the serving cell group which includes a PSCell and zero or more secondary cells.
  • Special cell Special Cell, SPCell.
  • the special cell refers to the PCell of the MCG or the PSCell of the SCG, otherwise (that is, in carrier aggregation), the special cell refers to the PCell of the MCG.
  • Dual connectivity dual Connectivity, DC.
  • Carrier aggregation carrier aggregation, CA.
  • DRB Data Radio Bearer carrying user plane data, a data radio bearer that carries user plane data or simply a data radio bearer.
  • SRB Signaling Radio Bearer, signaling radio bearer.
  • the bearer or radio bearer in the present disclosure may be: SRB, DRB, separate DRB, and separate SRB.
  • PDCP repetition It can also be called repetition or packet repetition or data repetition.
  • SRB, DRB, separate SRB, and separate DRB can all be configured with PDCP repetition.
  • a secondary RLC entity and a secondary logical channel are added to the radio bearer to process repeated PDCP PDUs.
  • PDCP repetition means that the same PDCP PDU is sent two or more times, and the PDCP PDUs sent twice or more are sent through RLC entities and/or logical channels associated with different carriers or carrier groups.
  • the RLC entities and/or logical channels configured with PDCP repeated radio bearers belong to different MAC entities.
  • Repeated activation/deactivation MAC CE Duplication Activation/Deactivation MAC CE, used to activate or deactivate the PDCP duplication of the radio bearer.
  • Primary path also known as the primary RLC entity, used to send PDCP control PDU and PDCP data PDU.
  • the primary path is configured through RRC messages and cannot be deactivated.
  • 3GPP Release 15 in carrier aggregation, when PDCP is repeatedly deactivated, the PDCP entity sends the PDCP PDU to the main path.
  • dual connectivity when PDCP is repeatedly deactivated, if the total amount of data is less than the configured data separation threshold, the PDCP entity sends the PDCP PDU to the main path.
  • the data transmission mode after PDCP repetitive deactivation may also be different from Release 15.
  • the data transmission mode can be the same as that of Release 15.
  • Secondary path secondary path, which is associated with other RLC entities except the primary path among the RLC entities configured with PDCP repeated DRBs.
  • FIG. 1 shows a flowchart of a method 100 in a user equipment UE based on an embodiment of the present disclosure.
  • the user equipment UE receives a single data radio bearer from the base station to repeatedly activate or deactivate the media access control control element (single DRB Duplication Activation/Deactivation MAC CE) (referred to as the first MAC CE) Or enhanced repeated activation/deactivation of MAC CE).
  • the single-data radio bearer repeated activation or deactivation MAC CE is used to indicate to activate or deactivate the PDCP of a DRB and/or to activate or deactivate the associated RLC entity (that is, to indicate whether the corresponding RLC entity is activated).
  • the following describes an example implementation of the first MAC CE.
  • the first MAC CE includes a DRB dup index field and a Ri field.
  • the DRB dup index field indicates the DRB (DRB dup Index field indicates the DRB for which the MAC CE applies) to which the MAC CE applies; preferably, the value of the DRB dup index field is arranged in ascending (or descending) order according to the DRB identifier The value of this field is the ascending order of the DRB ID among the DRBs configured with PDCP duplication and with RLC entity(ies)associated with this MAC entity).
  • the value of the DRB dup index field is the sequence number that arranges the DRB identifiers of the DRB that is configured with PDCP repetition and its associated RLC entity belongs/associates to this MAC entity in ascending order (or descending order), and the predefined starting sequence number is 0 Or the starting sequence number is 1. For example, if DRB1, DRB3, and DRB4 are configured with PDCP repetition and all three DRBs have RLC entities associated with the current MAC entity, then the sequence numbers corresponding to DRB 1, DRB3, and DRB4 (that is , the value of the DRB dup index field) are 0, 1, 2 (or 1, 2, 3). Alternatively, the value of the DRB dup index field is the DRB identifier.
  • the Ri field indicates the activation or deactivation of the corresponding RLC entity, or the Ri field indicates the PDCP repeated activation/deactivation status of the corresponding RLC entity.
  • the RLC entities are arranged in the order of RLC entity identifiers from small to large (or from large to small) ( Except the main path) correspond to R0, R1, and R2 respectively.
  • the main path is also indicated in the first MAC CE, the value of Ri corresponding to the main path is always 1.
  • it can be specified or predefined that its value is always 0 (or 1) or other predefined values. The UE will ignore those Ri to which no RLC entity is mapped.
  • FIG. 1 shows an example format of the first MAC CE.
  • the first MAC CE further includes an A/D field
  • the A/D field is used to indicate the repeated activation/deactivation status of the PDCP of the DRB indicated by the DRB dup index field
  • the A/D field is set to 1, indicating The PDCP corresponding to the DRB is repeatedly activated
  • the A/D field is set to 0 to indicate that the PDCP corresponding to the DRB is repeatedly deactivated. vice versa.
  • all Ri fields are set to 0 (if the first MAC CE contains the Ri corresponding to the main path, the value of Ri corresponding to the main path is 1 but the other Ri takes the value The value is 0).
  • the RLC entity and the logical channel have a one-to-one mapping relationship
  • the RLC entity in the embodiment of the present disclosure can also be replaced with a logical channel, and the RLC entity identifier is correspondingly replaced with a logical channel identifier.
  • the Ri field in the first MAC CE can be It directly corresponds to the RLC identifier, but if the RLC identifier is not configured, the corresponding relationship between the Ri domain and the RLC entity can be indicated according to the logical channel identifier of the logical channel associated with the RLC entity. Since the logical channel identifier is unique to the MAC, in the case of DC, the UE is configured with two MAC entities. A logical channel corresponding to a DRB configured with PDCP repetition may take the same value in the two MACs.
  • DRB1 is associated with logical channels LCID 2, LCID 3 in MCG, and logical channels LCID 1, LCID 3 in SCG, and the RLC entity corresponding to MCG LCID 2 is the primary RLC entity, then it is arranged in ascending order of MCG first, SCG They are MCG LCID 3, SCG LCID 1, SCG LCID 3, which correspond to R0, R1, and R2 respectively.
  • Figure 7 shows the correspondence among PDCP entities, RLC entities, logical channels, and MAC entities.
  • the user equipment UE that is, the MAC entity in the UE instructs the upper layer (for example, the PDCP layer/entity) to activate or deactivate the PDCP repetition and/or the associated RLC entity of the corresponding DRB based on the first MAC CE.
  • the MAC entity performs the following operations:
  • the PDCP repetition of the DRB is deactivated, instruct the upper layer to deactivate the PDCP repetition and/or of this DRB
  • the operation of the MAC after receiving the first MAC CE and instructing the upper layer to activate the RLC entity may be replaced by the upper layer instructing the deactivated RLC entity.
  • Deactivating an RLC entity means that after an RLC entity is deactivated, the PDCP entity does not submit PDCP data PDUs to the RLC entity.
  • an activated RLC entity may also be referred to as a PDCP repeatedly activated RLC entity, which refers to an RLC entity that is activated for transmitting PDCP data PDUs among multiple RLC entities associated with the PDCP entity.
  • the PDCP entity repeats/duplicates the PDCP data PDU and submits the PDCP data PDU to the RLC entity that is associated with the PDCP repeated activation.
  • the following describes an embodiment of the operation performed when the UE receives the repeated activation/deactivation of the media access control control element MAC CE (hereinafter referred to as the second MAC CE) defined by 3GPP Release 15.
  • Figure 3 shows an example format of the second MAC CE.
  • the Di field indicates the PDCP repeated activation/deactivation status of DRB i, where i is the DRB configured with PDCP repetition and the RLC entity is associated with the current MAC entity in ascending order of the DRB identification ID (This field indicates the activation/deactivation status of the PDCP duplication of DRB i where i is the ascending order of the DRB ID among the DRBs configured with PDCP duplication and with RLC entity(ies)associated with this MAC entity).
  • the Di field is set to 1 to indicate that the PDCP duplication of DRB i shall be activated.
  • the D i field is set to 1 to indicate that the PDCP duplication of DRB i shall be activated.
  • the D i field is set to 0 to indicate that the PDCP duplication of DRB i shall be deactivated).
  • the MAC entity For each DRB configured with PDCP repetition, the MAC entity performs the following operations:
  • the second MAC CE activates the PDCP repetition of a DRB, if the associated RLC entity (the RLC entity associated with this DRB or the RLC entity associated with the PDCP entity corresponding to this DRB) does not exceed two or two, it indicates the upper layer activation
  • the DRB does not perform any operation, in other words, ignore this Di).
  • the second MAC CE is used to activate or deactivate PDCP repetition; if 3 or 3 are configured (or associated) If there are more than one RLC entity, the first MAC CE is used to activate or deactivate the PDCP repetition and/or the associated RLC entity of the DRB.
  • the PDCP repetition corresponding to the DRB will be activated and displayed in the RRC message
  • the RLC in the active state configured in the DRB will be used for the PDCP repetition of this DRB, that is, the RLC entity configured in the active state in the RRC message will be activated for the PDCP PDU to be sent when the PDCP repetition of this DRB is activated.
  • the MAC entity indicating the upper layer refers to the MAC entity indicating the PDCP layer or the PDCP entity.
  • the following describes an embodiment in which the base station configures the PDCP repeated bearer for the user equipment.
  • the user equipment UE receives an RRC message, such as an RRC reconfiguration message, from the base station.
  • the RRC message contains an information element IE secondaryFallbackPath, which indicates the secondary RLC entity that can be used or can send PDCP PDUs after deactivating PDCP repetition, or the activated secondary RLC entity or the fallback RLC entity (for details, see the implementation of the PDCP entity Operation example).
  • the value of the secondaryFallbackPath information element can be the logical channel identifier of the secondary RLC entity or the LCID of the secondary RLC entity or the identifier of the logical channel associated with the secondary RLC entity or the identifier of the secondary RLC entity (denoted as RLC ID), the logical channel identifier Or the cell group corresponding to the LCID is different from the cell group corresponding to the main path. Since the current 3GPP system only supports the configuration of two cell groups MCG and SCG for the UE, the cell group identifier CellGroupId corresponding to the MCG is 0, and the cell group identifier CellGroupId corresponding to the SCG is 1.
  • the information element primaryPath included in the RRC message for indicating the primary path contains two information elements, cellGroup IE and logicalChannel IE.
  • the cellGroup IE is used to indicate the cell group where the primary path is located
  • the logicalChannel IE is used to indicate in the cellGroup IE
  • the logical channel or logical channel identifier in the indicated cell group, and the cell group where the logical channel identifier of the logical channel indicated by the secondaryFallbackPath is located is a cell group different from the primary path. If the primary path is in the MCG, then the logical channel indicated by the secondaryFallbackPath is in the SCG, and vice versa.
  • the secondaryFallbackPath cell contains the logicalChannel cell or the RLC entity identification cell (the RLC entity identification cell is used to indicate the fallback RLC entity), or the value of the secondaryFallbackPath cell is the logical channel identification LogicalChannelIdentity or RLC entity Logo.
  • the secondaryFallbackPath information element (referred to as the information element) may also be included in the RLC-BearerConfig information element, which is configured by the base station for the UE through an RRC message.
  • the value of secondaryFallbackPath can be TRUE or False or 1 or 0.
  • the secondary RLC entity indicated by the secondaryFallbackPath of the primary RLC entity is taken as The data transmission path of the DRB, and the PDCP PDU is sent according to the method in the embodiment defined by the operation performed by the sending PDCP entity.
  • the value of secondaryFallbackPath may be a value used to indicate that the corresponding RLC entity is in an activated state (denoted as Activated), a value used to indicate that the corresponding RLC entity is in a deactivated state (deactivated), and a value used to indicate Whether the corresponding RLC entity is used as one of the fallback paths (denoted as FallbackPath) after PDCP repetition is deactivated.
  • the fallback path is used as a secondary RLC entity when the PDCP PDU is sent according to the method in the embodiment defined by the operation performed by the sending PDCP entity after the PDCP repetition is deactivated.
  • a DC configured with carrier aggregation if there is more than one RLC entity in a cell group different from the cell group where the primary RLC entity is located, it must be in a cell group different from the cell group where the primary RLC entity is located Configure a secondaryFallbackPath.
  • the user equipment UE establishes/adds/reconfigures the corresponding DRB based on the RRC message.
  • the following describes the operations performed by the sending PDCP entity.
  • the transmitting PDCP entity performs the following operations when submitting a PDCP PDU to the lower layer:
  • the sending PDCP entity is associated with an RLC entity, then the PDCP PDU is delivered to the associated RLC entity;
  • the sending PDCP entity is associated with at least 2 RLC entities and if the PDCP is repeatedly activated and if the PDCP PDU is a PDCP data PDU, copy the PDCP data PDU and submit it to the activated RLC entity;
  • the sending PDCP entity is associated with at least 2 RLC entities and if the PDCP is repeatedly activated and if the PDCP PDU is a PDCP control PDU, submit the PDCP control PDU to the main RLC entity;
  • the sending PDCP entity is associated with at least 2 RLC entities and if PDCP is repeatedly deactivated, and if the sending PDCP entity is associated with two RLC entities, and the two RLC entities belong to different cell groups, and the number of PDCPs is equal to this
  • the total amount of data waiting for initial transmission in the two associated RLCs is greater than or equal to ul-DataSplitThreshold (if the total amount of PDCP data volume and RLC data volume pending for initial transmission in these two RLC entities is equal to or larger DataSplitThreshold), then this PDCP PDU is delivered to the primary RLC entity or the secondary RLC entity;
  • ul-DataSplitThreshold is a parameter configured through the RRC message;
  • the sending PDCP entity is associated with at least 2 RLC entities and if PDCP is repeatedly deactivated, and if the sending PDCP entity is associated with two RLC entities, and the two RLC entities belong to different cell groups, and the number of PDCPs is equal to this
  • the total amount of data waiting for initial transmission in the two associated RLCs is less than ul-DataSplitThreshold, then this PDCP PDU is delivered to the main RLC entity;
  • PDCP is repeatedly deactivated, and if there are more than two RLC entities associated with the sending PDCP entity, and if secondaryFallbackPath is configured, and the number of PDCPs and the amount of data waiting for initial transmission among the RLC entities indicated by the primary RLC entity and secondaryFallbackPath are configured If the total amount is greater than or equal to ul-DataSplitThreshold, then this PDCP PDU is delivered to the primary RLC entity or the RLC entity indicated by the secondaryFallbackPath;
  • PDCP is repeatedly deactivated, and if there are more than two RLC entities associated with the sending PDCP entity, and if secondaryFallbackPath is configured, and the number of PDCPs and the amount of data waiting for initial transmission among the RLC entities indicated by the primary RLC entity and secondaryFallbackPath are configured If the total amount is less than ul-DataSplitThreshold, then this PDCP PDU is delivered to the main RLC entity;
  • this PDCP PDU is delivered to the primary RLC entity.
  • PDCP can also be specified or pre-defined if PDCP is repeatedly deactivated, and if there are more than two RLC entities associated with the sending PDCP entity, and no secondaryFallbackPath is configured, if the activated secondary RLC entity indicated by the MAC layer is received, and the number of PDCPs If the total amount of data waiting for initial transmission in the activated secondary RLC entity indicated by the primary RLC entity and the MAC layer is greater than or equal to ul-DataSplitThreshold, then this PDCP PDU will be submitted to the primary RLC entity or the activated secondary RLC indicated by the MAC layer entity;
  • PDCP can also be specified or pre-defined if PDCP is repeatedly deactivated, and if there are more than 2 RLC entities associated with the sending PDCP entity, and no secondaryFallbackPath is configured, if the activated secondary RLC entity indicated by the MAC layer is received, and the number of PDCPs If the total amount of data waiting for initial transmission in the activated secondary RLC entity indicated by the primary RLC entity and the MAC layer is less than ul-DataSplitThreshold, then this PDCP PDU is delivered to the primary RLC entity;
  • PDCP is repeatedly deactivated, and if the RLC entity associated with the sending PDCP entity is more than two, and no secondaryFallbackPath is configured, if no secondary RLC entity indicating activation by the MAC layer is received, then this The PDCP PDU is delivered to the main RLC entity.
  • the appropriate PDCP repetition and/or the activation configuration of the RLC entity can be performed based on the information indicating the PDCP repetition and/or the activation configuration of the RLC entity received from the base station, thereby improving the performance of the wireless communication system. Communication efficiency and reliability.
  • FIG. 4 shows a block diagram of a user equipment 40 according to an embodiment of the present disclosure.
  • the user equipment 40 includes a processor 401 and a memory 402.
  • 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, it can execute the foregoing method in the user equipment described in detail in this disclosure.
  • FIG. 5 shows a flowchart of a method 500 in a base station based on an embodiment of the present disclosure.
  • a MAC CE is generated, and the MAC CE is used to indicate the PDCP repetition of the DRB and/or the activation configuration of the associated RLC entity.
  • the MAC CE is sent to the user equipment, and the PDCP repetition of the user equipment and/or the activation configuration of the associated RLC entity is performed based on the MAC CE.
  • the base station it is possible to perform appropriate PDCP repetition and/or activation configuration of the RLC entity based on the information indicating the PDCP repetition and/or the activation configuration of the RLC entity sent to the user equipment, thereby improving the performance of the wireless communication system. Communication efficiency and reliability.
  • FIG. 6 shows a block diagram of a base station 60 according to an embodiment of the present disclosure.
  • the base station 60 includes a processor 601 and a memory 602.
  • the base station 60 in the present 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, and home base station Wait.
  • the processor 601 may include, for example, a microprocessor, a microcontroller, an embedded processor, and the like.
  • the memory 602 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 602 stores program instructions. When the instruction is executed by the processor 601, 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

本公开提供一种用户设备及其方法、基站及其方法。由用户设备执行的方法，包括：从基站接收媒体访问控制控制元素MAC CE，该MAC CE用于指示数据无线承载DRB的分组数据汇聚协议PDCP重复和/或关联的无线链路控制RLC实体的激活配置；基于所述MAC CE，进行所述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信元(所述信元的具体描述见3GPP TS38.331)指示的逻辑信道发送还是采用分离承载方式发送。
在NR IIOT中，为达成利用双连接或载波聚合实现超过两次的PDCP重复这一目标，部分厂商提出为支持PDCP重复的承载配置多个RLC实体但每次仅激活其中的若干个RLC实体的方式。网络可以通过RRC信令或媒体访问控制控制元素MAC CE来指示是否激活PDCP重复以及激活的RLC实体。本公开讨论配置和/或激活/去激活PDCP重复和/或RLC实体所涉及的相关问题。
发明内容
为了解决现有技术中的上述问题，本公开提供了一种用户设备及其方法、基站及其方法，能够基于指示PDCP重复和/或RLC实体的激活配置的信息来执行适当的PDCP重复和/或RLC实体的激活配置，从而能够提高无线通信系统的通信效率以及可靠性。
根据本公开的第一方面，提供了一种用户设备，包括：接收单元，所述接收单元被配置为接收包含第一指示和第二指示的RRC消息，所述第一指示用于指示无线承载的主RLC实体关联的第一小区组和第一逻辑信道，所述第二指示用于指示所述无线承载的辅RLC实体关联的第二逻辑信道，所述辅RLC实体关联到不同于所述第一小区组的第二小区组；以及发送单元，所述发送单元被配置为当所述无线承载的PDCP重复被去激活且PDCP数据量和所述主RLC实体以及所述辅RLC实体中等待初始传输的数据量的总量大于等于数据传输门限ul-DataSplitThreshold时，将PDCP PDU递交给所述主RLC实体或递交给所述辅RLC实体，所述数据传输门限ul-DataSplitThreshold由基站通过RRC消息为UE配置。
根据本公开的第二方面，提供了一种由用户设备执行的方法，包括：接收包含第一指示和第二指示的RRC消息，所述第一指示用于指示无线承载的主RLC实体关联的第一小区组和第一逻辑信道，所述第二指示用于指示所述无线承载的辅RLC实体关联的第二逻辑信道，所述辅RLC实体关联到不同于所述第一小区组的第二小区组；以及当所述无线承载的PDCP重复被去激活且PDCP数据量和所述主RLC实体以及所述辅RLC实体中等待初始传输的数据量的总量大于等于数据传输门限ul-DataSplitThreshold时，将PDCP PDU递交给所述主RLC实体或递交给所述辅RLC实体，所述数据传输门限ul-DataSplitThreshold由基站通过RRC消息为UE配置。
根据本公开的第三方面，提供了一种基站，包括：生成单元，生成包含第一指示和第二指示的RRC消息，所述第一指示用于指示无线承载的主RLC实体关联的第一小区组和第一逻辑信道，所述第二指示用于指示所述无线承载的辅RLC实体关联的第二逻辑信道，所述辅RLC实体关联到不同于所述第一小区组的第二小区组；以及发送单元，向用户设备发送所述RRC 消息，所述发送单元还向用户设备发送包含数据传输门限ul-DataSplitThreshold的RRC消息，该数据传输门限用于使用户设备在所述无线承载的PDCP重复被去激活且PDCP数据量和所述主RLC实体以及所述辅RLC实体中等待初始传输的数据量的总量大于等于该数据传输门限时将PDCP PDU递交给所述主RLC实体或递交给所述辅RLC实体。
根据本公开的第四方面，提供了一种由基站执行的方法，包括：生成包含第一指示和第二指示的RRC消息，所述第一指示用于指示无线承载的主RLC实体关联的第一小区组和第一逻辑信道，所述第二指示用于指示所述无线承载的辅RLC实体关联的第二逻辑信道，所述辅RLC实体关联到不同于所述第一小区组的第二小区组；以及向用户设备发送所述RRC消息，所述方法还包括：向用户设备发送包含数据传输门限ul-DataSplitThreshold的RRC消息，该数据传输门限用于使用户设备在所述无线承载的PDCP重复被去激活且PDCP数据量和所述主RLC实体以及所述辅RLC实体中等待初始传输的数据量的总量大于等于该数据传输门限时将PDCP PDU递交给所述主RLC实体或递交给所述辅RLC实体。
发明效果
根据本公开的用户设备及其方法、基站及其方法，能够基于指示PDCP重复和/或RLC实体的激活配置的信息来执行适当的PDCP重复和/或RLC实体的激活配置，从而能够提高无线通信系统的通信效率以及可靠性。
附图说明
通过下文结合附图的详细描述，本公开的上述和其它特征将会变得更加明显，其中：
图1表示基于本公开的实施例的用户设备UE中的方法100的流程图。
图2表示第一MAC CE的示意图。
图3表示第二MAC CE的示意图。
图4表示基于本公开实施例的用户设备40的框图。
图5表示基于本公开的实施例的基站中的方法500的流程图。
图6表示基于本公开实施例的基站60的框图。
图7表示PDCP实体、RLC实体、逻辑信道、MAC实体间对应关系的示意图。
具体实施方式
下面结合附图和具体实施方式对本公开进行详细阐述。应当注意，本公开不应局限于下文所述的具体实施方式。另外，为了简便起见，省略了对与本公开没有直接关联的公知技术的详细描述，以防止对本公开的理解造成混淆。
下面描述本公开涉及的部分术语，如未特别说明，本公开涉及的术语采用此处定义。
RRC：Radio Resource Control，无线资源控制。
PDCP：Packet Data Convergence Protocol，分组数据汇聚协议。
RLC：Radio Link Control，无线链路控制。RLC实体的传输模式可以配置为透传模式TM、非确认模式UM或确认模式AM之一。
MAC：Medium Access Control，媒体访问控制。
MAC CE：MAC Control Element，MAC控制元素。
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-Config信元：所述信元PDCP-Config用于为信令承载和/或数据承载设置可配置的PDCP参数。
RLC-BearerConfig信元：所述信元RLC-BearerConfig用于配置RLC实体、在MAC中对应的逻辑信道和PDCP实体(服务的承载)的关联(used to configure an RLC entity，a corresponding logical channel in MAC and the linking to a PDCP entity(served radio bearer))。
主小区组：Master Cell Group，MCG。
主小区：Primary Cell，PCell。工作在主频率上的MCG小区，UE在其 上执行初始连接建立过程或发起连接重建过程。
主SCG小区：Primary SCG Cell，PSCell。在双连接中，在执行同步重配置中UE用于执行随机接入的SCG小区。
辅小区：Secondary Cell，SCell。配置了CA的UE，在特殊小区的基础上提供额外无线资源的小区。
辅小区组：Secondary Cell Group，SCG。对于配置了双连接的UE，服务小区组的子集，它包含PSCell和0个或多个辅小区。
特殊小区：Special Cell，SPCell。在双连接中，特殊小区指MCG的PCell或SCG的PSCell，否则(即在载波聚合中)，特殊小区指MCG的PCell。
双连接：dual Connectivity，DC。
载波聚合：carrier aggregation，CA。
DRB：Data Radio Bearer carrying user plane data，承载用户面数据的数据无线承载或简称数据无线承载。
SRB：Signalling Radio Bearer，信令无线承载。
如未特别说明，本公开中所述承载或无线承载可以是：SRB、DRB、分离DRB、分离SRB。
PDCP重复：也可称为重复或分组重复或数据重复，SRB、DRB、分离SRB、分离DRB均可配置PDCP重复。当无线承载配置了PDCP重复时，为所述无线承载增加辅RLC实体和辅逻辑信道来处理重复的PDCP PDU。PDCP重复是指相同的PDCP PDU发送两次或多次，所述两次或多次发送的PDCP PDU通过关联到不同载波或载波组的RLC实体和/或逻辑信道发送。在双连接方式下，所述配置了PDCP重复的无线承载的RLC实体和/或逻辑信道属于不同的MAC实体。
重复激活/去激活MAC CE：Duplication Activation/Deactivation MAC CE，用于激活或去激活无线承载的PDCP重复。
主路径：Primary path，也称为主RLC实体，用于发送PDCP控制PDU和PDCP数据PDU，主路径通过RRC消息配置且不能被去激活。
在3GPP版本15(release 15)中，在载波聚合中，当PDCP重复被去激活时，PDCP实体将PDCP PDU发送到主路径。在双连接中，当PDCP重复被去激活时，如果数据总量小于配置的数据分离门限，则PDCP实体将PDCP PDU发送到主路径。但3GPP版本16中，对于配置了PDCP重复的 DRB关联的RLC实体超过2个的双连接场景中，在PDCP重复去激活后的数据发送方式也可能不同于版本15。在载波聚合场景中，去激活PDCP重复后，数据发送方式可与版本15相同。
辅路径：secondary path，关联到配置了PDCP重复的DRB的RLC实体中除主路径外的其他RLC实体。
下面，对本公开中的用户设备UE中的方法进行说明，具体而言，对用户设备UE中承载的PDCP重复所涉及的控制方法进行说明。作为一例，图1中表示基于本公开的实施例的用户设备UE中的方法100的流程图。
在步骤S101中，用户设备UE(即UE中的MAC实体)从基站接收单数据无线承载重复激活或去激活媒体访问控制控制元素(single DRB Duplication Activation/Deactivation MAC CE)(称为第一MAC CE或增强的重复激活/去激活MAC CE)。所述单数据无线承载重复激活或去激活MAC CE用于指示激活或去激活一个DRB的PDCP重复和/或激活或去激活关联的RLC实体(即指示对应的RLC实体是否被激活)。
以下描述第一MAC CE的示例实现方式。
在一个实施例中，第一MAC CE包含DRB dup索引域和Ri域。其中，DRB dup索引域指示这个MAC CE所应用的DRB(DRB dup Index field indicates the DRB for which the MAC CE applies)；优选的，DRB dup索引域的取值为按照DRB标识升序(或降序)排列的序号，所述DRB是配置了PDCP重复且存在RLC实体关联到这个MAC实体(The value of this field is the ascending order of the DRB ID among the DRBs configured with PDCP duplication and with RLC entity(ies)associated with this MAC entity)。换言之，DRB dup索引域的取值是将配置了PDCP重复且其关联的RLC实体属于/关联到这个MAC实体的DRB的DRB标识按照升序(或降序)排列的序号，预定义起始序号为0或起始序号为1。例如，DRB1、DRB3、DRB4配置了PDCP重复且这三个DRB都存在RLC实体关联到当前MAC实体，那么DRB 1、DRB3、DRB4对应的序号(即DRB dup索引域的取值)分别为0、1、2(或1、2、3)。备选的，DRB dup索引域的取值为DRB标识。Ri域指示激活或去激活对应的RLC实体，或者Ri域指示对应的RLC实体的PDCP重 复的激活/去激活状态，RLC实体按照RLC实体标识从小到大(或从大到小)的顺序排列(主路径除外)分别对应R0、R1、R2。此外，如果主路径也在第一MAC CE中指示，那么对应主路径的Ri的取值总是为1。对于没有RLC实体映射到的Ri域，可以规定或预定义其取值总是为0(或1)或其他预定义的值。UE将忽略那些没有RLC实体映射到的Ri。例如，假设配置了PDCP重复的DRB1(或其PDCP实体)关联了RLC 1、RLC 2、RLC 3且RLC 1是主路径，那么RLC 2和RLC 3分别映射到R0和R1，而R2没有映射到任何RLC实体。图2给出了第一MAC CE的示例格式。
可选的，第一MAC CE还包含A/D域，所述A/D域用于指示DRB dup索引域指示的DRB的PDCP重复的激活/去激活状态，A/D域设置为1，表示对应DRB的PDCP重复被激活，A/D域设置为0表示对应DRB的PDCP重复被去激活。反之亦然。可选的，如果A/D域设置为0，则所有的Ri域均设置为0(如果第一MAC CE中包含主路径对应的Ri，则主路径对应的Ri取值为1但其他Ri取值为0)。
需要说明的是，由于RLC实体和逻辑信道存在一一映射的关系，所以本公开实施例中RLC实体也可以替换为逻辑信道，RLC实体标识相应的替换为逻辑信道标识。
在本公开实施例中，如果基站在发送给UE的RRC消息中为每个配置了PDCP重复的DRB关联的RLC实体分别配置了一个针对DRB唯一的RLC标识，那么第一MAC CE中Ri域可以直接对应RLC标识，但是如果没有配置RLC标识，Ri域与RLC实体的对应关系可以根据RLC实体关联的逻辑信道的逻辑信道标识来指示。由于逻辑信道标识是针对MAC唯一的，在DC情况下，UE配置了两个MAC实体，一个配置了PDCP重复的DRB对应的逻辑信道在两个MAC中可能取相同的值，此时按照逻辑信道标识由小到大(或由大到小或升序或降序)且先MCG后SCG(或先MCG或SCG)(如果存在)的方式与Ri(i＝0、1、2或i＝0、1、2、3)一一对应。例如，DRB1在MCG中关联逻辑信道LCID 2、LCID 3，在SCG中关联逻辑信道LCID 1、LCID 3，MCG LCID 2对应的RLC实体为主RLC实体，那么按照先MCG后SCG且升序的顺序排列为MCG LCID 3、SCG LCID 1、SCG  LCID 3，它们分别对应R0、R1、R2。
图7示出了PDCP实体、RLC实体、逻辑信道、MAC实体间的对应关系。
在步骤S102中，用户设备UE(即UE中的MAC实体)基于所述第一MAC CE指示上层(例如PDCP层/实体)激活或去激活对应DRB的PDCP重复和/或关联的RLC实体。具体的，对于每个配置了PDCP重复的DRB，MAC实体执行以下操作：
在一个实施例中，如果接收到针对配置了PDCP重复的DRB所关联的RLC实体的第一MAC CE，如果Ri均为0(所有的RLC实体或辅RLC实体均被去激活)，指示上层去激活这个DRB的PDCP重复；否则，指示上层激活这个DRB的PDCP重复和/或激活的RLC实体(即Ri＝1的位对应的RLC实体)。
在一个实施例中，如果接收到针对配置了PDCP重复的DRB所关联的RLC实体的第一MAC CE，如果至少存在一个Ri为1(至少一个RLC实体或至少一个辅RLC实体被激活)，指示上层激活这个DRB的PDCP重复和/或激活的RLC实体(即Ri＝1的位对应的RLC实体)；否则，指示上层去激活这个DRB的PDCP重复。
在一个实施例中，如果接收到针对配置了PDCP重复的DRB所关联的RLC实体的第一MAC CE，如果所述DRB的PDCP重复被去激活，指示上层去激活这个DRB的PDCP重复和/或激活的RLC实体(如果存在)；否则(即如果所述DRB的PDCP重复被激活)，指示上层激活这个DRB的PDCP重复和/或激活的RLC实体(即Ri＝1的位对应的RLC实体)。
本公开实施例中，MAC在接收到第一MAC CE并向上层指示激活的RLC实体的操作可以替换为向上层指示去激活的RLC实体。去激活一个RLC实体是指一个RLC实体在被去激活后，PDCP实体不将PDCP数据PDU提交给这个RLC实体。
本公开中，激活的RLC实体也可称为为PDCP重复激活的RLC实体，是指PDCP实体关联的多个RLC实体中，激活以用于传输PDCP数据PDU的RLC实体。当PDCP重复被激活时，PDCP实体重复/复制(duplicate) PDCP数据PDU并且将所述PDCP数据PDU提交(submit)所关联的为PDCP重复激活的RLC实体。需要注意的是，在双连接中，PDCP重复被去激活后如果采用分离承载数据发送方式，则存在两个激活的RLC实体(主RLC实体和一个辅RLC实体)，但此时激活的辅RLC实体不是为PDCP重复的目的。
以下描述UE接收到3GPP版本15定义的重复激活/去激活媒体访问控制控制元素MAC CE(以下简称第二MAC CE)时执行的操作实施例。
可以规定或预定义第二MAC CE仅用于去激活PDCP重复，而不用于激活PDCP重复，或者，对于关联的RLC实体大于2个的PDCP实体，UE忽略对应Di＝1的值；对于关联的RLC实体等于2个的PDCP实体，如果Di＝1，MAC实体指示上层激活对应DRB的PDCP重复；对于关联的RLC实体等于2个的PDCP实体，如果Di＝0，MAC实体指示上层去激活对应DRB的PDCP重复。图3给出了第二MAC CE的示例格式。其中，Di域指示DRB i的PDCP重复激活/去激活状态，其中i是配置了PDCP重复且RLC实体关联到当前MAC实体的那些DRB按照DRB标识ID升序排列(This field indicates the activation/deactivation status of the PDCP duplication of DRB i where i is the ascending order of the DRB ID among the DRBs configured with PDCP duplication and with RLC entity(ies)associated with this MAC entity)。Di域设置为0表示去激活DRB i的PDCP重复，Di域设置为1表示激活DRB i的PDCP重复(The D i field is set to 1 to indicate that the PDCP duplication of DRB i shall be activated.The D i field is set to 0 to indicate that the PDCP duplication of DRB i shall be deactivated)。
具体的，对于每个配置了PDCP重复的DRB，MAC实体执行以下操作：
在一个实施例中，当Di＝0(即接收到的第二MAC CE去激活一个DRB的PDCP重复)时，MAC实体指示上层去激活这个DRB的PDCP重复；当Di＝1(即接收到的第二MAC CE激活一个DRB的PDCP重复)时，如果关联的RLC实体(这个DRB关联的RLC实体或这个DRB对应的PDCP实体关联的RLC实体)不超过两个或为两个，则指示上层激活这个DRB的PDCP重复；否则(即如果关联的RLC实体(这个DRB关联的RLC实体或这个DRB对应的PDCP实体关联的RLC实体)超过两个)，UE不向 上层指示(即针对Di＝1对应的DRB不执行任何操作，换言之，忽略这个Di)。
在一个实施例中，当Di＝0(即接收到的第二MAC CE去激活这个Di对应的DRB的PDCP重复)时，MAC实体指示上层去激活这个DRB的PDCP重复；当Di＝1(即接收到的第二MAC CE激活这个Di对应的DRB的PDCP重复)且对应的DRB的PDCP重复当前处于激活态时，则指示上层激活这个DRB的PDCP重复和/或指示上层保持当前激活的RLC实体；如果Di＝1且对应DRB关联两个RLC实体或关联的RLC实体不超过两个，则指示上层激活这个DRB的PDCP重复。
在一个实施例中，当Di＝0(即接收到的第二MAC CE去激活这个Di对应的DRB的PDCP重复)时，MAC实体指示上层去激活这个DRB的PDCP重复；当Di＝1(即接收到的第二MAC CE激活这个Di对应的DRB的PDCP重复)时，UE不向上层指示激活这个DRB的PDCP重复(即针对Di＝1对应的DRB不执行任何操作，换言之，忽略这个Di)。
也可以规定或预定义如果一个配置了PDCP重复的DRB只配置(或关联)了两个RLC，则采用第二MAC CE来激活或去激活PDCP重复；如果配置(或关联)了3个或3个以上RLC实体，则采用第一MAC CE来激活或去激活所述DRB的PDCP重复和/或关联的RLC实体。
还可以规定或预定义，对于接收到的第二MAC CE中Di＝1对应的DRB，无论该DRB的PDCP重复当前处于激活态还是去激活态，对应DRB的PDCP重复将被激活并且在RRC消息中配置的处于激活态的RLC将用于这个DRB的PDCP重复，即在RRC消息中配置为激活态的RLC实体将被激活以用于这个DRB的PDCP重复被激活时发送PDCP PDU。
在本公开实施例中，如未特别说明，MAC实体指示上层是指MAC实体指示PDCP层或PDCP实体。
以下描述基站为用户设备配置PDCP重复承载的实施例。
在第一步骤中，用户设备UE从基站接收RRC消息，例如RRC重配置消息。所述RRC消息中包含一个信息元素IE secondaryFallbackPath，secondaryFallbackPath指示去激活PDCP重复后可 使用的或可发送PDCP PDU的辅RLC实体或激活的辅RLC实体或回退RLC实体(具体见发送PDCP实体执行的操作实施例)。secondaryFallbackPath信元的取值可以是辅RLC实体的逻辑信道标识或辅RLC实体的LCID或辅RLC实体所关联的逻辑信道的标识或辅RLC实体的标识(记为RLC ID)，所述逻辑信道标识或LCID对应的小区组不同于主路径对应的小区组。由于目前3GPP系统仅支持为UE配置两个小区组MCG和SCG的情况，MCG对应的小区组标识CellGroupId为0，SCG对应的小区组标识CellGroupId为1。包含在所述RRC消息中的用于指示主路径的信元primaryPath中包含两个信元cellGroup IE和logicalChannel IE，cellGroup IE用于指示主路径所在的小区组，logicalChannel IE用于指示在cellGroup IE中指示的小区组中的逻辑信道或逻辑信道标识，secondaryFallbackPath指示的逻辑信道的逻辑信道标识所在的小区组是不同于主路径的小区组。如果主路径在MCG中，那么secondaryFallbackPath指示的逻辑信道在SCG中，反之亦然。
可以规定或预定义，在DC中，如果为配置了PDCP重复的DRB配置/关联的RLC实体在不同于主路径所在小区组的小区组中包含RLC实体数超过1个，则必须配置secondaryFallbackPath。
以下是secondaryFallbackPath包含在用于为DRB或SRB设置可配置的PDCP参数的PDCP-Config IE中的示例描述：
Figure PCTCN2020132183-appb-000001
Figure PCTCN2020132183-appb-000002
在上述示例描述中，secondaryFallbackPath信元中包含logicalChannel信元或RLC实体标识信元(RLC实体标识信元用于指示回退RLC实体)， 或者secondaryFallbackPath信元的取值为逻辑信道标识LogicalChannelIdentity或RLC实体标识。
所述secondaryFallbackPath信息元素(简称信元)也可以包含在RLC-BearerConfig信元中，由基站通过RRC消息为UE配置。优选的，secondaryFallbackPath的取值可以为TRUE或False或1或0，当取值为TRUE或1或所述secondaryFallbackPath出现时，在去激活PDCP重复后，将主RLC实体的secondaryFallbackPath指示的辅RLC实体作为DRB的数据传输路径，并根据发送PDCP实体执行的操作所定义的实施例中的方法发送PDCP PDU。备选的，secondaryFallbackPath的取值可以为用于指示对应的RLC实体处于激活态的值(记为Activated)、用于指示对应的RLC实体处于去激活态的值(记为Deactivated)、用于指示去激活PDCP重复后对应的RLC实体是否作为回退路径(记为FallbackPath)之一。所述回退路径是作为在去激活PDCP重复后按照发送PDCP实体执行的操作所定义的实施例中的方法发送PDCP PDU时的辅RLC实体。
可以规定或预定义，在配置了载波聚合的DC中，如果不同于主RLC实体所在小区组的小区组中存在多于一个RLC实体，则必须在不同于主RLC实体所在小区组的小区组中配置一个secondaryFallbackPath。
在第二步骤中，用户设备UE基于所述RRC消息建立/增加/重配置对应的DRB。
以下描述发送PDCP实体执行的操作。
发送PDCP实体(the transmitting PDCP entity)在向下层提交(submit)一个PDCP PDU时执行以下操作：
如果发送PDCP实体关联了一个RLC实体，则将所述PDCP PDU递交给关联的RLC实体；
如果发送PDCP实体至少关联了2个RLC实体且如果PDCP重复被激活且如果所述PDCP PDU是PDCP数据PDU，则复制这个PDCP数据PDU并提交给激活的RLC实体；
如果发送PDCP实体至少关联了2个RLC实体且如果PDCP重复被激活且如果所述PDCP PDU是PDCP控制PDU，则将所述PDCP控制PDU 提交给主RLC实体；
如果发送PDCP实体至少关联了2个RLC实体且如果PDCP重复被去激活，且如果所述发送PDCP实体关联了两个RLC实体，并且这两个RLC实体属于不同的小区组，并且PDCP数量和这两关联的RLC中等待初传的数据量的总量大于或等于ul-DataSplitThreshold(if the total amount of PDCP data volume and RLC data volume pending for initial transmission in these two RLC entities is equal to or larger than ul-DataSplitThreshold)，则将这个PDCP PDU递交给主RLC实体或辅RLC实体；其中ul-DataSplitThreshold是通过RRC消息配置的一个参数；
如果发送PDCP实体至少关联了2个RLC实体且如果PDCP重复被去激活，且如果所述发送PDCP实体关联了两个RLC实体，并且这两个RLC实体属于不同的小区组，并且PDCP数量和这两关联的RLC中等待初传的数据量的总量小于ul-DataSplitThreshold，则将这个PDCP PDU递交给主RLC实体；
如果PDCP重复被去激活，且如果所述发送PDCP实体关联的RLC实体为2个以上，并且如果配置了secondaryFallbackPath，并且PDCP数量和主RLC实体和secondaryFallbackPath指示的RLC实体中等待初传的数据量的总量大于或等于ul-DataSplitThreshold，则将这个PDCP PDU递交给主RLC实体或secondaryFallbackPath指示的RLC实体；
如果PDCP重复被去激活，且如果所述发送PDCP实体关联的RLC实体为2个以上，并且如果配置了secondaryFallbackPath，并且PDCP数量和主RLC实体和secondaryFallbackPath指示的RLC实体中等待初传的数据量的总量小于ul-DataSplitThreshold，则将这个PDCP PDU递交给主RLC实体；
如果PDCP重复被去激活，且如果所述发送PDCP实体关联的RLC实体为2个以上，并且如果没有配置secondaryFallbackPath，则将这个PDCP PDU递交给主RLC实体。
也可以规定或预定义如果PDCP重复被去激活，且如果所述发送PDCP实体关联的RLC实体为2个以上，并且没有配置secondaryFallbackPath，如果接收到MAC层指示的激活的辅RLC实体，并且PDCP数量和主RLC 实体和MAC层指示的激活的辅RLC实体中等待初传的数据量的总量大于或等于ul-DataSplitThreshold，则将这个PDCP PDU递交给主RLC实体或MAC层指示的激活的辅RLC实体；
又可以规定或预定义如果PDCP重复被去激活，且如果所述发送PDCP实体关联的RLC实体为2个以上，并且没有配置secondaryFallbackPath，如果接收到MAC层指示的激活的辅RLC实体，并且PDCP数量和主RLC实体和MAC层指示的激活的辅RLC实体中等待初传的数据量的总量小于ul-DataSplitThreshold，则将这个PDCP PDU递交给主RLC实体；
还可以规定或预定义如果PDCP重复被去激活，且如果所述发送PDCP实体关联的RLC实体为2个以上，并且没有配置secondaryFallbackPath，如果没有接收到MAC层指示激活的辅RLC实体，则将这个PDCP PDU递交给主RLC实体。
根据上述由用户设备执行的方法，能够基于从基站接收的指示PDCP重复和/或RLC实体的激活配置的信息来执行适当的PDCP重复和/或RLC实体的激活配置，从而能够提高无线通信系统的通信效率以及可靠性。
此外，图4示出了根据本公开实施例的用户设备40的框图。如图4所示，该用户设备40包括处理器401和存储器402。处理器401例如可以包括微处理器、微控制器、嵌入式处理器等。存储器402例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统等。存储器402上存储有程序指令。该指令在由处理器401运行时，可以执行本公开详细描述的用户设备中的上述方法。
再有，作为一例，图5中表示基于本公开的实施例的基站中的方法500的流程图。在步骤S501中，生成MAC CE，该MAC CE用于指示DRB的PDCP重复和/或关联的RLC实体的激活配置。在步骤S502中，将所述MAC CE发送至用户设备，基于所述MAC CE进行用户设备的PDCP重复和/或关联的RLC实体的激活配置。
根据上述由基站执行的方法，能够基于向用户设备发送的指示PDCP重复和/或RLC实体的激活配置的信息来执行适当的PDCP重复和/或RLC实体的激活配置，从而能够提高无线通信系统的通信效率以及可靠性。
此外，图6示出了根据本公开实施例的基站60的框图。如图6所示，该基站60包括处理器601和存储器602。如上述所述，本公开中的基站60可以是任何类型基站，包含但不限于：Node B、增强基站eNB，也可以是5G通信系统基站gNB、或者微基站、微微基站、宏基站、家庭基站等。处理器601例如可以包括微处理器、微控制器、嵌入式处理器等。存储器602例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统等。存储器602上存储有程序指令。该指令在由处理器601运行时，可以执行本公开详细描述的基站中的上述方法。
运行在根据本公开的设备上的计算机可执行指令或者程序可以是通过控制中央处理单元(CPU)来使计算机实现本公开的实施例功能的程序。该程序或由该程序处理的信息可以临时存储在易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统中。
用于实现本公开各实施例功能的计算机可执行指令或程序可以记录在计算机可读存储介质上。可以通过使计算机系统读取记录在所述记录介质上的程序并执行这些程序来实现相应的功能。此处的所谓“计算机系统”可以是嵌入在该设备中的计算机系统，可以包括操作系统或硬件(如外围设备)。“计算机可读存储介质”可以是半导体记录介质、光学记录介质、磁性记录介质、短时动态存储程序的记录介质、或计算机可读的任何其他记录介质。
用在上述实施例中的设备的各种特征或功能模块可以通过电路(例如，单片或多片集成电路)来实现或执行。设计用于执行本说明书所描述的功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、或其他可编程逻辑器件、分立的门或晶体管逻辑、分立的硬件组件、或上述器件的任意组合。通用处理器可 以是微处理器，也可以是任何现有的处理器、控制器、微控制器、或状态机。上述电路可以是数字电路，也可以是模拟电路。因半导体技术的进步而出现了替代现有集成电路的新的集成电路技术的情况下，本公开的一个或多个实施例也可以使用这些新的集成电路技术来实现。
此外，本公开并不局限于上述实施例。尽管已经描述了所述实施例的各种示例，但本公开并不局限于此。安装在室内或室外的固定或非移动电子设备可以用作终端设备或通信设备，如AV设备、厨房设备、清洁设备、空调、办公设备、自动贩售机、以及其他家用电器等。
如上，已经参考附图对本公开的实施例进行了详细描述。但是，具体的结构并不局限于上述实施例，本公开也包括不偏离本公开主旨的任何设计改动。另外，可以在权利要求的范围内对本公开进行多种改动，通过适当地组合不同实施例所公开的技术手段所得到的实施例也包含在本公开的技术范围内。此外，上述实施例中所描述的具有相同效果的组件可以相互替代。

Claims (4)

  1. 一种用户设备，包括：
    接收单元，所述接收单元被配置为接收包含第一指示和第二指示的RRC消息，所述第一指示用于指示无线承载的主RLC实体关联的第一小区组和第一逻辑信道，所述第二指示用于指示所述无线承载的辅RLC实体关联的第二逻辑信道，所述辅RLC实体关联到不同于所述第一小区组的第二小区组；以及
    发送单元，所述发送单元被配置为当所述无线承载的PDCP重复被去激活且PDCP数据量和所述主RLC实体以及所述辅RLC实体中等待初始传输的数据量的总量大于等于数据传输门限ul-DataSplitThreshold时，将PDCP PDU递交给所述主RLC实体或递交给所述辅RLC实体，
    所述数据传输门限ul-DataSplitThreshold由基站通过RRC消息为UE配置。
  2. 一种由用户设备执行的方法，包括：
    接收包含第一指示和第二指示的RRC消息，所述第一指示用于指示无线承载的主RLC实体关联的第一小区组和第一逻辑信道，所述第二指示用于指示所述无线承载的辅RLC实体关联的第二逻辑信道，所述辅RLC实体关联到不同于所述第一小区组的第二小区组；以及
    当所述无线承载的PDCP重复被去激活且PDCP数据量和所述主RLC实体以及所述辅RLC实体中等待初始传输的数据量的总量大于等于数据传输门限ul-DataSplitThreshold时，将PDCP PDU递交给所述主RLC实体或递交给所述辅RLC实体，
    所述数据传输门限ul-DataSplitThreshold由基站通过RRC消息为UE配置。
  3. 一种基站，包括：
    生成单元，生成包含第一指示和第二指示的RRC消息，所述第一指示用于指示无线承载的主RLC实体关联的第一小区组和第一逻辑信道，所述第二指示用于指示所述无线承载的辅RLC实体关联的第二逻辑信道，所述辅RLC实体关联到不同于所述第一小区组的第二小区组；以及
    发送单元，向用户设备发送所述RRC消息，
    所述发送单元还向用户设备发送包含数据传输门限ul-DataSplitThreshold的RRC消息，该数据传输门限用于使用户设备在所述无线承载的PDCP重复被去激活且PDCP数据量和所述主RLC实体以及所述辅RLC实体中等待初始传输的数据量的总量大于等于该数据传输门限时将PDCP PDU递交给所述主RLC实体或递交给所述辅RLC实体。
  4. 一种由基站执行的方法，包括：
    生成包含第一指示和第二指示的RRC消息，所述第一指示用于指示无线承载的主RLC实体关联的第一小区组和第一逻辑信道，所述第二指示用于指示所述无线承载的辅RLC实体关联的第二逻辑信道，所述辅RLC实体关联到不同于所述第一小区组的第二小区组；以及
    向用户设备发送所述RRC消息，
    所述方法还包括：
    向用户设备发送包含数据传输门限ul-DataSplitThreshold的RRC消息，该数据传输门限用于使用户设备在所述无线承载的PDCP重复被去激活且PDCP数据量和所述主RLC实体以及所述辅RLC实体中等待初始传输的数据量的总量大于等于该数据传输门限时将PDCP PDU递交给所述主RLC实体或递交给所述辅RLC实体。
PCT/CN2020/132183 2019-12-06 2020-11-27 用户设备及其方法、基站及其方法 WO2021109933A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US17/780,574 US20230007531A1 (en) 2019-12-06 2020-11-27 User equipment and method thereof, and base station and method thereof

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201911254116.7A CN112929136A (zh) 2019-12-06 2019-12-06 用户设备及其方法、基站及其方法
CN201911254116.7 2019-12-06

Publications (1)

Publication Number Publication Date
WO2021109933A1 true WO2021109933A1 (zh) 2021-06-10

Family

ID=76162113

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/132183 WO2021109933A1 (zh) 2019-12-06 2020-11-27 用户设备及其方法、基站及其方法

Country Status (3)

Country Link
US (1) US20230007531A1 (zh)
CN (1) CN112929136A (zh)
WO (1) WO2021109933A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023001250A1 (en) * 2021-07-21 2023-01-26 FG Innovation Company Limited Method and user equipment for handling a survival time state

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018085203A1 (en) * 2016-11-01 2018-05-11 Sharp Laboratories Of America, Inc. Configurable radio link controller frame structure
CN108617004A (zh) * 2017-01-25 2018-10-02 电信科学技术研究院 一种rrc连接态传输数据的方法及装置

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180124843A1 (en) * 2016-11-01 2018-05-03 Sharp Laboratories Of America, Inc. Configurable radio link controller frame structure
EP4266815A3 (en) * 2017-02-02 2024-01-31 LG Electronics Inc. Method and device for transmitting data unit
TWI691181B (zh) * 2018-01-10 2020-04-11 香港商鴻穎創新有限公司 無線通訊系統中封包資料匯聚協定（pdcp）資料傳輸的方法及裝置
US11051309B2 (en) * 2018-09-21 2021-06-29 Lg Electronics Inc. Method for managing duplication modes by user equipment in wireless communication system and apparatus therefor
KR20210117309A (ko) * 2019-01-18 2021-09-28 에프쥐 이노베이션 컴퍼니 리미티드 차세대 무선 네트워크들 내에서의 패킷 데이터 컨버전스 프로토콜 복제
KR20210120055A (ko) * 2019-01-28 2021-10-06 지티이 코포레이션 동적 패킷 중복 융합 프로토콜 구성
US11159422B2 (en) * 2019-02-03 2021-10-26 FG Innovation Company Limited Evolved packet data convergence protocol duplication

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018085203A1 (en) * 2016-11-01 2018-05-11 Sharp Laboratories Of America, Inc. Configurable radio link controller frame structure
CN108617004A (zh) * 2017-01-25 2018-10-02 电信科学技术研究院 一种rrc连接态传输数据的方法及装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
LG ELECTRONICS INC.: "Consideration on RLC polling with multiple RLC entities", 3GPP DRAFT; R2-1808392 CONSIDERATION ON RLC POLLING WITH MULTIPLE RLC ENTITIES, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Busan, Korea; 20180521 - 20180525, 20 May 2018 (2018-05-20), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051444666 *
LG ELECTRONICS INC.: "Introduction of PDCP duplication for LTE", 3GPP DRAFT; 36323_CR(0230)_(REL-15)_R2-1808537_INTRODUCTION OF PDCP DUPLICATION FOR LTE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Busan, South Korea; 20180521 - 20180525, 20 May 2018 (2018-05-20), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051442949 *

Also Published As

Publication number Publication date
US20230007531A1 (en) 2023-01-05
CN112929136A (zh) 2021-06-08

Similar Documents

Publication Publication Date Title
WO2018171512A1 (zh) 无线配置方法、用户设备和基站
WO2018171546A1 (zh) 用户设备和基站处执行的方法及相应的设备
TWI692988B (zh) 基站、使用者設備和相關方法
WO2020119638A1 (zh) 用户设备及其方法、基站及其方法
CN109246766B (zh) 无线配置方法和相应的用户设备
CN109151915B (zh) 用于数据分组递送的方法、用户设备和基站
US11172537B2 (en) Wireless communication method and device
WO2018224030A1 (zh) 基站、用户设备和相关方法
WO2020119640A1 (zh) 用户设备及其方法、基站及其方法
WO2021185202A1 (zh) 用户设备及其方法、基站及其方法
JP2020532158A (ja) 無線通信方法、端末デバイス及びネットワークデバイス
WO2020119632A1 (zh) 用户设备及其方法、基站及其方法
WO2021109933A1 (zh) 用户设备及其方法、基站及其方法
WO2021223623A1 (zh) 针对信令无线承载pdcp重复的配置方法及rrc实体
WO2020221155A1 (zh) 基站、用户设备和相关方法
WO2020156316A1 (zh) Iab网络、mac实体和适配实体的执行方法以及通信设备
WO2020200055A1 (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: 20895529

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: 20895529

Country of ref document: EP

Kind code of ref document: A1