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

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

Info

Publication number
WO2020119632A1
WO2020119632A1 PCT/CN2019/124011 CN2019124011W WO2020119632A1 WO 2020119632 A1 WO2020119632 A1 WO 2020119632A1 CN 2019124011 W CN2019124011 W CN 2019124011W WO 2020119632 A1 WO2020119632 A1 WO 2020119632A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdcp
logical channel
mac
rlc
entity
Prior art date
Application number
PCT/CN2019/124011
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/311,791 priority Critical patent/US20220038950A1/en
Priority to EP19895583.3A priority patent/EP3897014A4/en
Priority to CA3123118A priority patent/CA3123118A1/en
Publication of WO2020119632A1 publication Critical patent/WO2020119632A1/zh
Priority to IL283889A priority patent/IL283889A/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • 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/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • 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
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0096—Indication of changes in allocation
    • H04L5/0098—Signalling of the activation or deactivation of component carriers, subcarriers or frequency bands
    • 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
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data
    • H04W8/205—Transfer to or from user equipment or user record carrier
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers

Definitions

  • the present disclosure relates to the technical field of wireless communication, and more specifically, the present disclosure relates to user equipment and its method, base station and its method.
  • up to two RLC entities can be configured for PDCP repeat bearers.
  • the initial state of the bearer configured with PDCP repetition is to indicate whether to activate the PDCP repetition function at the beginning through pdcp-Duplication cells (see 3GPP TS38.331 for the specific description of the cells).
  • carrier aggregation for a bearer whose initial PDCP repetition function is not activated, its data is sent through the logical channel indicated by the primaryPath information element (see 3GPP TS38.331 for a detailed description of the information element).
  • NRIIOT in order to achieve the goal of using dual connectivity or carrier aggregation to achieve more than two times of PDCP duplication, some manufacturers have proposed to configure multiple RLC entities for PDCP duplicate bearers, but only activate a few RLC entities at a time. the way. If a bearer that supports PDCP duplication can be configured with multiple (more than two) RLC entities, after deactivating the bearer duplication of PDCP, how the PDCP entity sends PDCP PDUs is a problem that needs to be solved.
  • the present invention provides a method in user equipment, a method in user equipment, a method in a base station, and a base station.
  • a method in a user equipment comprising: receiving from a base station a MAC control element MAC for deactivation of packet data convergence protocol PDCP repetition; and based on the received MAC The PDCP is repeatedly deactivated.
  • the MAC CE may include: repeatedly activating/deactivating the MAC CE, and switching the MAC CE.
  • a radio resource control RRC message including primary path indication information is received from the base station, and when the UE and the base station communicate based on carrier aggregation, when the PDCP is repeatedly deactivated , Sending the PDCP protocol data unit PDCP PDU to the main path indicated by the main path indication information.
  • the main path indication information includes a cell group indication identifier, which is used to indicate which cell group the radio link control RLC entity and/or Or a logical channel as the main path.
  • the PDCP protocol data unit PDCP PDU is sent to the activated radio link control RLC entity specified by the handover MAC.
  • the PDCP protocol data unit PDCP PDU is selected as the PDCP protocol data unit according to the logical channel identifier size of the logical channel associated with the radio link control RLC entity activated when the MAC is received.
  • the logical channel or RLC entity of the sending object when the PDCP is repeatedly deactivated, the PDCP protocol data unit PDCP PDU is selected as the PDCP protocol data unit according to the logical channel identifier size of the logical channel associated with the radio link control RLC entity activated when the MAC is received.
  • the data separation method when the UE is in dual connectivity, when receiving the MAC for deactivating the PDCP duplication, if there are two RLC entities in the activated state, the data separation method is used Send the PDCP PDU to the RLC entity in the activated state; if there are more than two RLC entities in the activated state in the cell group, the PDCP PDU is sent to a predefined predefined according to the logical channel identifier according to the data separation method The RLC entity associated with the logical channel.
  • a user equipment including: a processor; and a memory, storing instructions; wherein the instructions execute the method in the user equipment according to the context when executed by the processor .
  • a method in a base station comprising: generating a MAC control element MAC for deactivating packet data aggregation protocol PDCP repetition; and sending the MAC to user equipment UE, the The UE performs the repeated deactivation of the PDCP based on the MAC.
  • a base station including: a processor; and a memory, storing instructions; wherein the instructions execute the method in the base station according to the context when executed by the processor.
  • 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 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.
  • 5 shows a schematic diagram of MAC switching CE.
  • RRC Radio Resource Control, radio resource control.
  • PDCP Packet Data Convergence Protocol, packet data aggregation protocol.
  • RLC Radio Link Control, wireless link control.
  • the transmission mode of the RLC entity can be configured as one of the transparent transmission mode TM, the unacknowledged 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 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 RLC entity or the data sent to the RLC entity is called PDCP PDU (that is, RLC SDU).
  • the cell PDCP-Config is used to set configurable PDCP parameters for signaling bearers and data bearers.
  • RLC-BearerConfig information element The information element RLC-BearerConfig is used to configure the association of the RLC entity, the corresponding logical channel in the MAC and the PDCP entity (bearer of the service) (used to configure RLC entity, a correspondence channel, logical channel in MAC) and the linking to PDCP entity (served radio bearer)).
  • Master base station Master eNB or Master gNB, denoted as MeNB (base station corresponding to E-UTRAN or LTE or eLTE) or MgNB (base station corresponding to 5G-RAN or NR).
  • MeNB base station corresponding to E-UTRAN or LTE or eLTE
  • MgNB base station corresponding to 5G-RAN or NR.
  • S1-MME control node mobility management entity
  • NG-C which is NG -Control plane interface of RAN and 5GC.
  • Secondary base station Secondary eNB or Secondary gNB, denoted as SeNB (base station corresponding to E-UTRAN or LTE or eLTE) or SgNB (base station corresponding to 5G-RAN or NR).
  • SeNB base station corresponding to E-UTRAN or LTE or eLTE
  • SgNB base station corresponding to 5G-RAN or NR.
  • a base station that is not the primary base station but provides additional wireless resources for the UE.
  • Primary cell Primary Cell, PCell.
  • the cell operating on the primary frequency may be the cell on which the UE performs the initial connection establishment process or initiates the connection reestablishment process or is designated as the primary cell during the handover process.
  • the cell described in the present disclosure may also be referred to as a carrier or a set of beam.
  • Primary and secondary cells Primary Secondary Cell, PSCell.
  • PSCell Primary Secondary Cell
  • Secondary cell Secondary Cell, SCell.
  • a cell operating on a secondary frequency which can be configured after RRC connection establishment and can be used to provide additional radio resources.
  • Cell group Cell, Group, CG.
  • a group of serving cells or carriers associated with the primary or secondary base station may be MCG or SCG.
  • Main cell group Master Cell, MCG.
  • the MCG is composed of all serving cells; for UEs that are configured for dual connectivity, the MCG is composed of a subset of serving cells (that is, a group of serving cells associated with the primary base station), which includes PCell and 0 Or one or more SCells.
  • Secondary cell group Secondary Cell Group, SCG.
  • SCG Secondary Cell Group
  • the SCG may contain one PSCell and one or more SCells.
  • Dual connectivity dual Connectivity, DC.
  • DRB Data Radio Bearer carrying user plane data, data wireless bearer carrying user plane data or data wireless bearer for short.
  • SRB Signaling Radio Bearer, signaling radio bearer.
  • the bearer or radio bearer in the present disclosure may be: SRB, DRB, split DRB (for example: MCG split DRB or SCG split DRB), split SRB (for example MCG split SRB or SCG split SRB).
  • PDCP repetition It can also be called repetition or group repetition or data repetition.
  • SRB, DRB, separated SRB, and separated DRB can be configured with PDCP repetition.
  • a secondary RLC entity and a secondary logical channel are added to the radio bearer to process the repeated PDCP PDU.
  • PDCP duplication means that the same PDCP PDU is sent two or more times, and the two or more PDCP PDUs 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 radio bearer PDCP repetition.
  • Total amount of data the total amount of PDCP data and the associated two or more RLC (or activated RLC) data (the amount of RLC data waiting for initial transmission) (the total amount of PDCP data data volume and RLC data volume pending for initial transmission in the activated RLC entities).
  • Primary path Primary path.
  • carrier aggregation when PDCP is repeatedly deactivated, the PDCP entity sends PDCP PDUs to the primary path.
  • dual connectivity when PDCP is repeatedly deactivated, if the total amount of data is less than the data separation threshold, the PDCP entity sends the PDCP PDU to the main path.
  • Secondary path secondary path, in carrier aggregation and dual connection, when PDCP is repeatedly activated, the RLC entity and/or logical channel and/or RLC bearer used to send the PDCP PDU. Specifically, when the PDCP is repeatedly activated, the PDCP entity copies the PDCP PDU and sends it to the activated RLC entity and/or logical channel and or RLC bearer (also called primary path and secondary path).
  • the embodiments in the present disclosure specifically describe those RLC entities and/or logical channels and/or RLC bearers that are considered activated, in which the activated RLC entities and/or logical channels and/or RLC bearers, except the main path
  • the external RLC entities and/or logical channels and/or RLC bearers may be called secondary paths.
  • 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 from the base station a MAC control element MAC for deactivating the packet data aggregation protocol PDCP repetition CE.
  • step S102 the user equipment UE performs the repeated deactivation of the PDCP based on the received MAC and CE.
  • the MAC CE may include: repeatedly activating/deactivating the MAC CE and switching the MAC CE.
  • the user equipment UE Before step S101 is performed, the user equipment UE first receives a radio resource control RRC message containing primary path indication information from the base station.
  • a radio resource control RRC message containing primary path indication information from the base station.
  • the UE and the base station communicate based on carrier aggregation (that is, the bearer is configured to perform carrier aggregation based communication
  • the RLC entity and/or logical channel and/or RLC bearer associated with the bearer or its PDCP entity belong to a cell group or use the resources of cells in the same cell group for data transmission)
  • the PDCP if the PDCP is repeatedly deactivated, the PDCP entity
  • the PDCP protocol data unit PDCP PDU is sent to the main path indicated by the main path indication information.
  • the bearer when the UE is in dual connectivity (ie, the bearer is configured as a separate bearer, the bearer or its PDCP entity associated RLC entity and/or logical channel and/or RLC bearer belong to different cell groups or use different cell groups
  • the resource of the cell in the cell is used for data transmission
  • the main path indication information includes a cell group indication identifier, which is used to indicate which cell group the radio link control RLC entity and/or logical channel are used as the Main path.
  • the PDCP protocol data unit PDCP PDU may be sent to the activated radio link control RLC entity specified by the handover MAC.
  • the PDCP when the PDCP is repeatedly deactivated, it can be selected as the PDCP protocol data unit PDCP PDU to be sent as the PDCP protocol data unit according to the logical channel identification size of the logical channel associated with the radio link control RLC entity activated when the MAC is received.
  • the logical channel or RLC entity of the object when the PDCP is repeatedly deactivated, it can be selected as the PDCP protocol data unit PDCP PDU to be sent as the PDCP protocol data unit according to the logical channel identification size of the logical channel associated with the radio link control RLC entity activated when the MAC is received.
  • the data separation method For example, when the UE is in dual connectivity, when receiving the MAC for deactivating the PDCP duplication, if there are two RLC entities in the activated state, the data separation method The PDCP PDU is sent to the activated RLC entity; if there are more than two activated RLC entities in the cell group, the PDCP PDU is sent to the predefined logical channel association according to the logical channel identifier according to the data separation method The RLC entity.
  • 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, or 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 may be executed.
  • FIG. 3 shows a flowchart of a method 300 in a base station based on an embodiment of the present disclosure.
  • step S301 the base station device generates a MAC control element MAC for deactivating the packet data aggregation protocol PDCP repetition.
  • step S302 the base station device sends the generated MAC to the user equipment UE, and the user equipment UE performs the repeated deactivation of the PDCP based on the MAC.
  • FIG. 4 shows a block diagram of the 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 the present disclosure may be any type of base station, including but not limited to: Node B, enhanced base station eNB, or 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, or 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 this disclosure can be executed.
  • a base station configures a user equipment to support a PDCP repeated bearer and sets its initial state.
  • the user equipment receives an RRC message from the base station (the RRC message in the embodiment of the present disclosure may be an RRC reconfiguration message), and the message includes an activation indicator (recorded as a first indicator, for example, represented by a cell activatedPath) .
  • the activation indicator may be used to indicate the RLC entity and/or logical channel and/or RLC bearer in the activated state; or, the activation indicator may be used to indicate that the PDCP is activated when it is repeatedly activated or deactivated.
  • the activation indicator may be used to indicate the RLC entity and/or logical channel and/or RLC bearer in the active state in the initial state; or, the activation The indication identifier may be used to indicate whether the corresponding RLC entity and/or logical channel and/or RLC bearer are in an activated state.
  • the RRC message further includes an information element (denoted as maxNrofActivatedLCH) for indicating the maximum number of RLC entities and/or logical channels and/or RLC bearers that can be activated when the PDCP is repeatedly activated.
  • the value of the information element is an integer and does not exceed the maximum RLC entity and/or logical channel and/or RLC bearer number or maximum value of the logical channel identifier maxLC-ID that can be configured for one bearer.
  • the RRC message also includes a cell (denoted as releaseAllowedServingCells) used to indicate whether to deactivate the restriction of the serving cell after repeated deactivation of PDCP (the restriction of the serving cell can be configured through the allowedServingCells of the cell, if the cell appears ), the UL MAC SDU corresponding to the logical channel can only be mapped to the serving cell in the cell list specified by the cell).
  • the uplink UL MAC SDU from the logical channel can be mapped to any (or all) serving cells configured in the cell group.
  • the information element can be configured in PDCP-config, and is applied to all RLC entities or logical channels at this time.
  • the information element may also be configured in LogicalChannelConfig, at this time it only applies to the corresponding logical channel or the RLC entity associated with the logical channel. For example, if the value of the cell is 1 or TRUE or the cell appears, it means that after the deactivation of PDCP is repeated, the serving cell restriction is canceled.
  • PDCP in carrier aggregation, if the number of activated RLC entities and/or logical channels and/or RLC bearers indicated by the activation indication identifier exceeds two, PDCP is repeatedly activated. The PDCP entity will copy the PDCP PDU and send it to its associated activated RLC entity and/or logical channel and/or RLC bearer. If there is only one activated RLC entity and/or logical channel and/or RLC bearer indicated by the activation indicator, the PDCP is repeatedly deactivated. The PDCP entity sends the PDCP PDU to the activated RLC entity and/or logical channel and/or RLC bearer.
  • the RRC message also includes a PDCP repetition indicator (denoted as pdcp-Duplication), which is used to indicate whether the uplink repetition status is configured and activated when this cell is received.
  • a PDCP repetition indicator (denoted as pdcp-Duplication)
  • the PDCP entity copies the PDCP PDU and sends it to multiple activated RLC entities.
  • the PDCP entity sends the PDCP PDU to the activated RLC entity (or main path) or the PDCP entity sends the PDCP PDU to an activated RLC entity (the RLC entity is the least correlated among the activated RLC entities ( Or smaller or largest or larger) RLC entity of the logical channel identified by the logical channel). If the value of the PDCP repeated indication flag is false, and no main path is configured in the RRC message, only one RLC entity and/or logical channel and/or RLC bearer is activated (that is, its activation indication flag is TRUE).
  • the PDCP entity copies the PDCP PDU and sends it to its associated multiple activated RLC entities and/or logical channels and/or RLC bearers. If the value of pdcp-Duplication is false (FALSE), the PDCP entity sends the PDCP PDU according to the separate bearer data transmission method. Specifically, in this case, the RRC message also includes the configuration of the main path and/or the data separation threshold (referred to as ul-DataSplitThreshold in this disclosure). If the total amount of data is equal to or exceeds the data separation threshold, the PDCP entity will The PDU is sent to one of the two or more RLC entities that are activated.
  • the PDCP entity sends the PDCP PDU to the RLC entity specified by the main path.
  • the value of the main path may be a cell group identifier or MCG or SCG.
  • the PDCP entity sends the PDCP PDU to the cell that is activated and belongs to (or is associated with) the main path.
  • the PDCP control PDU when the PDCP is repeatedly activated, the PDCP control PDU may be predefined to be sent to the logic that is activated and associated with the smallest (or smaller or larger or larger) logical channel identifier The RLC entity of the channel.
  • the RLC entity that is activated and associated with the logical channel with the smallest (or smaller or largest or larger) logical channel identifier is used as the main path.
  • the activation indication identifier may be included in the PDCP-config to indicate that one or more RLC entities or logical channels or RLC bearers of a certain cell group are activated.
  • the activation indication identifier (denoted as ActivatedPath) may include a cell group indication identifier (for example, represented by a cell group) and/or a logical channel indication identifier (for example, represented by a logicalHChannelList).
  • the cell group indicator is used to indicate the cell group.
  • the cell group identifier (denoted as CellGroupId) of the master cell group (MCG) may be 0, and other values indicate the secondary cell group.
  • the logical channel indication identifier is used to indicate the activated RLC entity (or its associated logical channel) and/or logical channel and/or RLC bearer, and its value may be a logical channel identifier LogicalChannelIdentity (that is, LCH ID) list or a Bitmap, each bit in the bitmap corresponds to a logical channel, and the logical channel identifier of the logical channel associated with the bearer or its PDCP entity may be corresponding to each bitmap in order from large to small or from small to large. One bit (from left to right).
  • LogicalChannelIdentity that is, LCH ID
  • the RLC entity and/or logical channel and/or RLC bearer corresponding to the bit with a value of 0 in the bitmap is deactivated (or activated); the RLC entity and/or corresponding to the bit with a value of 1 in the bitmap
  • the logical channel and/or RLC bearer is activated (or deactivated).
  • the activation indicator may only include the logical channel indicator.
  • the number of elements in the logical channel identification list or the length of the bitmap can be set to the maximum number of configurable RLC entities or the maximum number of logical channels that support PDCP repetition bearers minus 1.
  • the activation indication identifier may be included in the PDCP-config, and the activation indication identifier has two information elements, one information element (denoted as MCGActivatedPath) is used to indicate the activated RLC entity and/or logical channel in the primary cell group MCG And/or RLC bearer. Another information element (denoted as SCGActivatedPath) is used to indicate the activated RLC entity and/or logical channel and/or RLC bearer in the secondary cell group SCG.
  • MCGActivatedPath is used to indicate the activated RLC entity and/or logical channel in the primary cell group MCG And/or RLC bearer.
  • SCGActivatedPath Another information element (denoted as SCGActivatedPath) is used to indicate the activated RLC entity and/or logical channel and/or RLC bearer in the secondary cell group SCG.
  • the value of the MCGActivatedPath may be a logical channel identifier LogicalChannelIdentity (that is, LCH ID) list or a bitmap, each bit in the bitmap corresponds to a logical channel, and may be associated with the bearer or its PDCP entity and
  • the logical channel identifier of the logical channel located in the MCG (or SCG) corresponds to each bit in the bitmap (from left to right) in order from large to small or small to large.
  • the RLC entity and/or logical channel and/or RLC bearer corresponding to the bit with a value of 0 in the bitmap is deactivated (or activated); the RLC entity and/or corresponding to the bit with a value of 1 in the bitmap
  • the logical channel and/or RLC bearer is activated (or deactivated).
  • the number of elements in the logical channel identification list or the length of the bitmap can be set to the maximum number of configurable RLC entities or the maximum number of logical channels that support PDCP repetition bearers minus 1.
  • the MCGActivatedPath and/or SCGActivatedPath include a main path indication information element for indicating the corresponding cell group or the RLC entity (or logical channel) belonging to the corresponding cell group or the activated RLC entity belonging to the corresponding cell group (Or logical channel) whether it is the main path. If the primary path indication cell value is TRUE or 1 or appears, the corresponding cell group or RLC entity (or logical channel) belonging to the corresponding cell group or the activated RLC entity belonging to the corresponding cell group ( Or logical channel) as the main path, otherwise not as the main path, and vice versa.
  • the activation indication identifier (denoted as initialActivated) may be included in RLC-BearerConfig to indicate whether the corresponding RLC entity and/or logical channel and/or RLC bearer are in the activated state, or to indicate the corresponding RLC entity and/or Or whether the logical channel and/or RLC bearer is in an active state when receiving this cell.
  • the activation indication flag initialActivated takes the value TRUE or 1 or the flag appears, it means that the corresponding RLC entity and/or logical channel and/or RLC bearer are in the activated state; if the activation indication flag initialActivated takes the value FALSE or 0 or the If the identifier does not appear, it indicates that the corresponding RLC entity and/or logical channel and/or RLC bearer are in a deactivated state. vice versa.
  • the RLC-BearerConfig can also contain the main path cell, the value of which is true (TRUE) or false (FALSE), or 0 or 1, or based on its presence or absence to determine, if the main path is trusted If the value of the element is TRUE or 1, or appears, the associated RLC entity is used as the main path; otherwise, it is not used as the main path. vice versa.
  • the initial state of carrier aggregation if PDCP is repeatedly deactivated (for example, pdcp-Duplication does not appear or is set to False), only one RLC entity is in the activated state, that is, only one RLC entity's activation indicator identifies initialActivated The value is TRUE or 1 or the logo appears; if PDCP is repeatedly activated, at least two RLC entities are in the activated state, that is, the activation indication flag of at least two RLC entities is initialActivated The value is TRUE or 1 or the logo appears .
  • the PDCP entity In carrier aggregation, in the initial state, if the PDCP is repeatedly activated, the PDCP entity sends the PDCP PDU to the RLC entity (here two with the smallest and the second smallest (or the largest and the next largest) logical channel identifier). For example, if there are more than one, the analogy follows). If the PDCP is repeatedly deactivated, the PDCP entity sends the PDCP PDU to the RLC entity associated with the logical channel with the smallest (or largest) logical channel identification.
  • the PDCP entity In dual connectivity, in the initial state, if the PDCP is repeatedly activated, the PDCP entity sends the PDCP PDU to the RLC entity associated with the logical channel with the smallest (or largest) logical channel identifier in each cell group. If PDCP is repeatedly deactivated and the total amount of data is greater than or equal to the data separation threshold, the PDCP entity sends the PDCP PDU to one of the RLC entities in the two cell groups that are respectively associated with the logical channel with the smallest (or largest) logical channel identifier RLC entity. If PDCP is repeatedly deactivated and the total amount of data is less than the data separation threshold, the PDCP entity sends the PDCP PDU to the main path.
  • the main path may configure a cell group to which the main path belongs through RRC, and then predefine an RLC entity associated with a logical channel having a minimum (or maximum) logical channel identifier in the cell group as the main path.
  • the initial state of PDCP repetition is always deactivated.
  • the PDCP entity sends the PDCP PDU to the RLC entity associated with the logical channel with the smallest (or largest) logical channel identification.
  • the PDCP entity sends the PDCP PDU to one of the RLC entities in the two cell groups that is associated with the logical channel with the smallest (or largest) logical channel identifier. entity. If the total amount of data is less than the data separation threshold, the PDCP entity sends the PDCP PDU to the main path.
  • the main path may configure a cell group to which the main path belongs through RRC, and then predefine an RLC entity associated with a logical channel having a minimum (or maximum) logical channel identifier in the cell group as the main path.
  • the activation indicator may be included in the PDCP-config, and the activation indicator includes two cells, namely a primary path indicator (remembered as PrimaryPath) and a secondary path indicator (remembered as SecondaryPath).
  • the main path indication identifier may further include two indication identifiers, one is a cell group identifier (ie cell ID) used to indicate the cell group of the main path (or the main RLC entity) and/or a logical channel indicating the main path Logical channel identification (or logical channel identification list or bitmap); the secondary path indication identification may also include two indication identifications, one is a cell group identification used to indicate the cell group of the secondary path and/or used to indicate the secondary path.
  • the logical channel identifier (or logical channel identifier list or bitmap) of the logical channel of Each bit in the bitmap corresponds to a logical channel, which can be from large to small or from small to large according to the logical channel ID of the logical channel associated with the bearer or its
  • the RLC entity and/or logical channel and/or RLC bearer corresponding to the bit with a value of 0 in the bitmap is deactivated (or activated); the RLC entity and/or corresponding to the bit with a value of 1 in the bitmap
  • the logical channel and/or RLC bearer is activated (or deactivated).
  • the number of elements in the logical channel identifier list or the length of the bitmap can be set to the maximum number of RLC entities or the maximum number of logical channels that can be configured to support PDCP repetition bearer minus 1.
  • the logical channel or RLC entity or RLC logical channel with the maximum or minimum logical channel identifier can be pre-defined as the PDCP PDU that is sent Logical channel or RLC entity or RLC logical channel (that is, the PDCP entity sends PDCP PDUs to the logical channel or RLC entity or RLC logical channel), or through RRC configuration (for example, indicated by an indicator) one of the logical channels or RLC Entity or RLC logical channel is used to send PDCP PDU.
  • the activation indication flag may not be included.
  • the activation indicator only includes logical channel indicator information.
  • the following describes an embodiment of dynamically switching RLC entities when PDCP is repeatedly activated.
  • Embodiment 6 MAC switching CE
  • the user equipment UE receives an RRC message from a base station, where the RRC message configures multiple RLC entities and/or logical channels for a bearer that supports PDCP repetition.
  • the user equipment receives the handover MAC CE from the base station, which is used to activate and/or deactivate the RLC entity and/or logical channel associated with the bearer supporting PDCP duplication.
  • the handover MAC includes a domain for indicating a bearer supporting PDCP duplication (can be denoted as Di) and a domain of an RLC entity or logical channel associated with the bearer (or PDCP entity of the bearer) (can be denoted as Lij) ).
  • the handover MAC CE is related to the MAC entity.
  • the handover MAC from a certain MAC entity only indicates the RLC entity (or logical channel) associated with this MAC entity and its corresponding DRB or SRB that supports repetition.
  • Fig. 5 shows a schematic diagram of MAC switching CE.
  • Di corresponds to DRBi or SRBi, where i is the corresponding sequence number according to the ascending or descending order of the DRB identifier (or SRB identifier) of the DRB (or SRB) configured with PDCP duplication, and the DRB (or SRB) is associated
  • the RLC entity (or associated RLC part) is located in this MAC entity.
  • SRB can also support dynamic switching of RLC entities or logical channels for data transmission.
  • SRB and DRB can use different switching MACs; or CE includes a field in the switching MAC to indicate whether the corresponding switching MAC is used for SRB or CE DRB (based on the different values of the domain to distinguish between MAC used for SRB and CE used for DRB), for example, if the value of the domain is 0 (or 1), the corresponding switch MAC Used for SRB (or DRB), that is, Di corresponds to SRB (or DRB), and vice versa; or it is mapped to Di in the manner of SRB before DRB or DRB before SRB.
  • each SRB (or DRB) can be mapped to the Di in the MAC switching CE according to the order of the bearer ID from small to large or from large to small (it can be mapped from left to right or right to left, for example D0 corresponds to the DRB or SRB with the smallest or largest bearer identifier).
  • the field Lij is used to indicate the activation or deactivation of the j-th RLC entity and/or logical channel of the bearer corresponding to Di.
  • j is the RLC entity and/or logical channel of the bearer corresponding to Di associated with this MAC entity according to the logic
  • the channel numbers are listed in ascending or descending order. If the value of the field is 0, the corresponding RLC entity and/or logical channel is deactivated, and if the value of the field is 1, the corresponding RLC entity and/or logical channel is activated. vice versa.
  • the corresponding Lij field is not included in the handover MAC CE.
  • the handover MAC CE contains a field used to indicate the deactivated RLC entity and/or logical channel that are in the activated state after PDCP repetition.
  • the value of the domain may be the logical channel identifier of the activated logical channel or the logical channel identifier of the logical channel associated with the activated RLC entity, or the value of the domain of 0 or 1 indicates that deactivation is not associated with The RLC entity other than the RLC entity of the logical channel identified by the smallest logical channel, or the value of the field being 0 or 1 indicates that other RLC entities other than the RLC entity associated with the logical channel having the largest logical channel identifier are deactivated.
  • the handover MAC CE may contain only the logical channel corresponding to the activated bearer (may be only the logical channel belonging to this MAC entity).
  • the Di domain in FIG. 5 may not be carried, and the switching MAC carries only the Lij domain corresponding to the activated bearers.
  • the arrangement of the Lij field is the same as that in FIG. 5, and it can be arranged in ascending or descending order according to the size of its corresponding Di bearer identifier, and the Lij corresponding to each activated bearer can be arranged in ascending or descending order according to the size of the logical channel identifier.
  • the switching MAC may also indicate only one bearer switching RLC entity and/or logical channel at a time. At this time, the switching MAC carries the bearer identifier and the Lij field (used to indicate the logical channel where the corresponding bearer is activated).
  • the user equipment After receiving the MAC switching CE, the user equipment performs one of the following operations:
  • the PDCP is repeatedly activated (Di field is 1), this case indicates that the RLC entity or logical channel is switched, then the upper layer is instructed to switch the RLC entity and/or logical channel; or the logical channel identifier or the activated logical channel identifier of the upper layer is indicated
  • the logical channel identifier of the logical channel associated with the RLC entity indicates the logical layer identifier of the upper layer or the RLC entity indicating that the upper layer is activated.
  • it also instructs the upper layer to activate the PDCP repetition of the corresponding bearer.
  • Embodiment 7 RRC configuration + handover MAC CE
  • the user equipment receives an RRC message (such as an RRC reconfiguration message) from the base station, where the message contains an RLC entity group or logical channel group or RLC bearer group that can be used after indicating that PDCP is repeatedly activated.
  • RRC message such as an RRC reconfiguration message
  • the RLC entities and/or logical channels associated with the same bearer are divided into several groups, and each group can be configured with a group number in the RRC message.
  • a group number indication indicator indicates a group number
  • another group indication indicator indicates an RLC entity or logical channel included in the group.
  • the logical channel identification list mode or the bitmap mode may be used to indicate grouping.
  • each bit in the bitmap corresponds to each RLC entity and/or logical channel associated with this bearer (can be mapped in order from small to large or large to small), which is 1 in the bitmap
  • the RLC entities and/or logical channels corresponding to the bits are divided into the same group.
  • the RLC entities and/or logical channel groups are numbered according to the order in which the RLC entities and/or logical channels are grouped, the first group number is 0 (or 1) and the second group number is 1 (or 2 ), and so on.
  • the user receives the handover MAC from the base station CE.
  • the switching MAC is used to instruct the PDCP repeated RLC entity or logical channel to switch to the RLC entity or logical channel generally indicated by the MAC.
  • the field of the MAC switching CE is the RLC entity and/or logical channel group number.
  • the switching MAC CE is a bitmap, and the bits in the bitmap correspond one by one in ascending or descending order according to the packet number, and the bit (or bit) value in the bitmap is 1 indicating that the RLC entity in the packet is activated and /Or logical channel, a bit (or bit) in the bitmap with a value of 0 means deactivating the RLC entity and/or logical channel in the packet. At most only one bit in MAC CE can be set to 1. Optionally, if all bits in the bitmap are set to 0, the PDCP duplication of the corresponding bearer is deactivated.
  • the following describes an embodiment of how to determine to which RLC entity the PDCP entity sends the PDCP PDU after PDCP is repeatedly deactivated (discussed separately for carrier aggregation and dual connectivity scenarios).
  • RLC entities and/or logical channels and/or RLC bearers associated with the same PDCP repeating bearer or its PDCP entity belong to the same cell group.
  • Embodiment 8 (After deactivating PDCP repeatedly, the PDCP entity sends the PDCP PDU to the main path)
  • the UE receives an RRC message from the base station, and the RRC message carries a primary path indication information element (denoted as primaryPath).
  • the main path indication information element may include a cell group indication information element cellGroup for indicating a cell group identification and/or a logical channel indication information element logicalChannel for indicating a logical channel identification). If the PDCP is repeatedly deactivated (for example, the repeated activation/deactivation MAC is received), the PDCP entity sends the PDCP PDU to the main path.
  • the main path is activated and used by the PDCP entity to send PDCP PDUs.
  • the MAC entity receives the repeated activation/deactivation MAC (or MAC switching CE)
  • the MAC layer MAC layer indicates the upper layer
  • the MAC layer indicates that the upper layer PDCP is repeatedly deactivated
  • the upper layer activates the main path or the RLC indicated by the main path Entity or logical channel or RLC bearer; or when the MAC entity receives repeated activation/deactivation MAC (or MAC switching CE), it instructs the upper layer to deactivate PD
  • Embodiment 9 (After repeating the deactivation of PDCP, the PDCP entity sends the PDCP PDU to the activated RLC entity designated by the switch MAC CE)
  • the UE receives the handover MAC CE from the base station.
  • the handover MAC indicates that the Di corresponding to the bearer DRB i (or SRB i) has a value of 0, that is, the PDCP is repeatedly deactivated.
  • the MAC entity activates the RLC entity and/or logical channel and/or RLC bearer corresponding to the Lij value of 1 corresponding to DRB i (or SRB i), and instructs the upper layer to deactivate the PDCP repetition of the corresponding bearer; or, At the same time, it instructs the upper layer to activate the RLC entity and/or logical channel and/or RLC bearer and/or logical channel identifier; or instructs the upper layer to activate the PDCP repeated and/or activated RLC entity and/or logical channel.
  • the corresponding Dij with a value of 0 has only one Lij with a value of 1.
  • the handover MAC CE contains a field used to indicate the deactivated RLC entity and/or logical channel after the PDCP is repeated.
  • the value of the field is the logical channel identifier of the activated logical channel or the logical channel associated with the activated RLC entity.
  • Embodiment 10 (After the deactivation of the PDCP is repeated, the PDCP entity sends the PDCP PDU to the activated/deactivated PDCP repetitive MAC, and the logical channel identifier of the logical channel associated with the activated RLC entity is small (or larger or smallest or Maximum)
  • the MAC entity when receiving a MAC for deactivating PDCP duplication (such as duplicate activation/deactivation MAC or CE switching MAC), if the PDCP of a bearer is repeatedly deactivated, the MAC entity receives The MAC performs at least one of the following operations during the CE:
  • D. Instruct the upper layer to activate the logical channel with the largest (or smallest) logical channel identifier or to indicate the upper layer to activate the RLC entity or RLC bearer where the largest (or smallest) logical channel identifier is associated.
  • the maximum or minimum only considers the largest or smallest of the logical channel identifiers corresponding to the activated logical channel (or RLC entity).
  • the PDCP entity sends the PDCP PDU to the RLC entity associated with the logical channel having the smallest (or largest) logical channel identifier.
  • the maximum or minimum only considers the largest or smallest of the logical channel identifiers corresponding to the activated logical channel (or RLC entity).
  • activating one RLC entity means that the PDCP entity sends the PDCP PDU to the RLC entity.
  • Deactivating an RLC entity means that the PDCP entity no longer sends PDCP PDUs to the RLC entity.
  • Example 11 to Example 13 As an example, the processing in the case of dual connection will be described.
  • RLC entities and/or logical channels and/or RLC bearers associated with the same PDCP-supporting bearer or its PDCP entity belong to different cell groups.
  • bearers configured with PDCP repetition for example, the base station configures the user equipment through RRC messages
  • the PDCP entity will copy the PDCP PDU and send it to its associated and activated RLC entity; if the PDCP repetition
  • the deactivated and activated RLC entities belong to different cell groups and the total number is equal to or greater than the data separation threshold configured in the RRC message (for example, using the cell ulDataSplitThreshold indication), and sends the data (that is, PDCP PDU) to the master Path (in this disclosure, the primary path may also be referred to as the primary RLC entity) or the secondary RLC entity (or the activated secondary RLC entity); if the PDCP is repeatedly in the deactivated state and the activated RLC entity belongs to a different cell
  • This comparison is based on the total amount of data and the data separation threshold. If the total amount of data is less than the data separation threshold, the PDCP entity sends the PDCP PDU only to the main path. If the total amount of data is greater than or equal to the data separation threshold, then The PDCP entity sends PDCP PDUs to the main path and one of the other activated RLC entities.
  • the data transmission method is called data separation.
  • the main path may be defined in the manner described in other embodiments of the present disclosure.
  • Embodiment 11 (After repeating the deactivation of PDCP, the PDCP entity sends the PDCP PDU to the RLC entity used in the initial state)
  • the UE receives an RRC message from the base station, where the RRC message includes a configuration that supports PDCP repeat bearers.
  • the RRC message includes the configuration of the main path, and the configuration of the main path may include a cell group indicator (or a cell group indicator and a logical channel indicator), and the cell group indicator is used to indicate which The RLC entity and/or logical channel in the cell group may serve as the main path.
  • the main path configuration includes both the cell group indicator and the logical channel indicator, only the RLC entity (or the logical channel identifier is a logical channel) located in the cell indicated by the cell group indicator and associated with the logical channel indicated by the logical channel indicator The logical channel indicating the value of the ID) can be used as the main path.
  • the UE When the UE receives the repeated MAC (ie repeated activation/deactivation MAC or CE switching MAC) CE for deactivating PDCP of a bearer from the base station, it performs one of the following operations:
  • the MAC entity instructs the upper layer to deactivate PDCP duplication. After receiving the PDCP duplication deactivation instruction, the PDCP entity uses data separation and uses RRC messages to activate the RLC entity and the main path to transmit data.
  • the MAC entity activates the RLC entity and/or logical channel activated in the RRC message and instructs the upper layer to deactivate PDCP repetition.
  • the MAC entity indicates the RLC entity and/or logical channel or logical channel identifier activated in the upper layer RRC message. Optionally, it also instructs the upper layer to deactivate the PDCP repetition.
  • Embodiment 12 (After the deactivation of PDCP is repeated, the PDCP entity sends the PDCP PDU to the activated RLC entity specified by the switch MAC CE)
  • the MAC used to deactivate the PDCP duplication of the bearer carries the logical channel identification indication information, which is used to instruct the PDCP entity to send the PDCP PDU to the logical channel identification indication information indication after the deactivation of the PDCP duplication.
  • RLC entity of the logical channel carries the logical channel identification indication information, which is used to instruct the PDCP entity to send the PDCP PDU to the logical channel identification indication information indication after the deactivation of the PDCP duplication.
  • the MAC CE activates the RLC entity corresponding to the Lij value of 1 or the RLC entity and/or logical channel associated with the logical channel indicated by the logical channel identifier indication indicator and/or instructs the upper layer to deactivate PDCP repetition and/or to take Lij
  • the logical channel identifier (or logical channel or RLC entity associated with the logical channel with the logical channel identifier) corresponding to the value 1 is indicated to the upper layer.
  • Embodiment 13 (After the deactivation of PDCP is repeated, the PDCP entity sends the PDCP PDU to the activated RLC entity)
  • the PDCP entity when receiving the MAC for deactivating PDCP duplication (for example, repeated activation/deactivation of MAC or CE switching), if there are only two RLC entities in the activated state, the PDCP entity follows the data separation method Send PDCP PDU to the activated RLC entity (that is, the activated RLC entity when receiving the deactivated PDCP repeated MAC) CE; if there are more than two activated RLC entities in a cell group, The RLC entity that predefines the logical channel identifier with the smallest (or largest) logical channel in the cell group or the logical channel associated with the smallest (or largest) logical channel identifier is used by the PDCP entity to send PDCP PDUs according to the data separation method. The maximum or minimum only considers the largest or smallest of the logical channel identifiers corresponding to the activated logical channel (or RLC entity).
  • the MAC entity when the UE receives the PDCP repeated MAC from the base station to deactivate a bearer, the MAC entity performs at least one of the following operations:
  • the MAC entity deactivates (or instructs the upper layer to deactivate) the RLC entity associated with the logical channel with a larger (or smaller or largest or smallest) logical channel identifier And/or RLC bearers, or deactivate logical channels with larger (or smaller or largest or smallest) logical channel identifiers.
  • the MAC entity deactivates (or instructs the upper layer to deactivate) the RLC entity and/or logic corresponding to the bearer (or associated with the PDCP entity of the bearer) Except for channels and/or RLC bearers, except those with the largest (or smallest or larger or smaller) logical channel identifier or associated with the RLC entity and/or RLC with the largest (or smallest or larger or smaller) logical channel identifier Except for carrying.
  • the MAC entity instructs the upper layer to activate the logical channel with the largest (or smallest or larger or smaller) logical channel identifier or indicates that the upper layer activation is associated with the largest ( Or the smallest or larger or smaller) logical channel identified RLC entity or RLC bearer.
  • the larger or smaller or the largest or the smallest described in this embodiment only considers the larger or the smaller or the largest or the smallest of the logical channel identifiers corresponding to the activated logical channel (or RLC entity).
  • the RLC entity and/or logical channel and/or RLC bearer in the activated state may also be referred to as the RLC entity and/or logical channel and/or RLC bearer that are activated or used to transmit data. If PDCP is repeatedly activated, the uplink UL MAC SDU from the activated RLC entity or logical channel can only be sent on the serving cell configured for it.
  • the RLC entity and/or logical channel and/or RLC bearer in the activated state may be the RLC entity and/or logical channel and/or RLC bearer used for transmitting PDCP PDU after the PDCP is repeatedly activated or deactivated.
  • the activated RLC entity and/or logical channel and/or RLC bearer refers to the RLC entity indicated in the RRC message (or the RLC entity in the activated state indicated in the RRC message) or the RLC entity indicated by the lower layer (or indicated by the lower layer Active RLC entity).
  • the main path in the present disclosure refers to the RLC entity (or RLC entity used to transmit PDCP PDU) to which the PDCP entity sends the PDCP PDU after the PDCP deactivation is repeated.
  • the main path in the present disclosure refers to when the sum of the PDCP data volume and the RLC data volume to be initially transmitted with the associated (or associated and activated) RLC is less than the RRC message
  • the RLC entity (or entity used to transmit PDCP PDUs) to which the data is sent.
  • the upper layer RLC entity indicating in the embodiment of the present disclosure may also be expressed as indicating the upper layer logical channel or logical channel identifier.
  • the activated RLC entity refers to an entity for sending PDCP PDUs. After an RLC entity is activated, the PDCP entity may send the PDCP PDU to the RLC entity.
  • the deactivation RLC entity described in this disclosure may also be replaced with deactivation logical channel.
  • the UE receives the capability query message from the base station.
  • the UE sends a capability report message to the base station, where the capability report message carries an information element that is used to indicate the maximum number of RLC entities and/or logical channels that can be supported; or the information element is used to indicate that it can be activated simultaneously The maximum number of RLC entities and/or logical channels; or the information element is used to indicate that the PDCP entity can send duplicate PDCP PDUs to several RLC entities at most.
  • the PDCP sending entity performs the following operations:
  • the deactivated RLC entity instructs to delete all duplicate PDCP data PDUs.
  • the deactivated RLC entity or logical channel or RLC bearer in the present disclosure means that the PDCP entity no longer sends PDCP PDUs to the deactivated RLC entity.
  • the computer-executable instructions or programs running on the device according to the present invention may be programs that cause the computer to realize the functions of the embodiments of the present invention by controlling a central processing unit (CPU).
  • the program or information processed by the program may 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 the embodiments of the present invention may be recorded on a computer-readable storage medium.
  • the corresponding functions can be realized by causing the computer system to read the programs recorded on the recording medium and execute the programs.
  • the so-called "computer system” here may be a computer system embedded in the device, and may include an operating system or hardware (such as a peripheral device).
  • the “computer-readable storage medium” may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a recording medium that dynamically stores a program for a short 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 may include general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, discrete Gate or transistor logic, discrete hardware components, or any combination of the above devices.
  • DSPs digital signal processors
  • ASICs application specific integrated circuits
  • FPGAs field programmable gate arrays
  • a general-purpose processor may be a microprocessor, or any existing processor, controller, microcontroller, or state machine.
  • the above circuit may be a digital circuit or an analog circuit.
  • the present invention is not limited to the above-mentioned embodiment. Although various examples of the embodiments have been described, the present invention is not limited to this.
  • 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)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明提供一种用户设备及其方法、基站及其方法。所述用户设备中的方法包括：从基站接收用于去激活分组数据汇聚协议PDCP重复的MAC控制元素MAC CE；和基于接收到的所述MAC CE，进行所述PDCP重复的去激活。

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(IoT))，并获批准。该研究项目的目标之一是通过数据重复(data duplication)来提高数据传输的可靠性和减少数据传输的时延，具体包括：(1)资源有效的PDCP重复，例如避免不必要的重复传输；(2)利用双连接或载波聚合实现超过两次的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实体的方式。如果支持PDCP重复的承载可以配置多个(超过两个)RLC实体，在去激活承载的PDCP重复后，PDCP实体如何发送PDCP PDU是需要解决的问题。
发明内容
为了解决现有技术中的上述问题，本发明提供了一种用户设备中的方法、用户设备、基站中的方法、以及基站。
根据本发明的第一方面，提供一种用户设备中的方法包括：从基站接收用于去激活分组数据汇聚协议PDCP重复的MAC控制元素MAC CE；和基于接收到的所述MAC CE，进行所述PDCP重复的去激活。
在上述方法中，所述MAC CE可以包含：重复激活/去激活MAC CE、以及切换MAC CE。
在上述方法中，从所述基站接收包含主路径指示信息的无线资源控制RRC消息，在所述UE与所述基站之间基于载波聚合进行通信的情况下，在所述PDCP重复被去激活时，将PDCP协议数据单元PDCP PDU发送至所述主路径指示信息所指示的主路径。
在上述方法中，在所述UE处于双连接的情况下，所述主路径指示信息包括小区组指示标识，所述小区组指示标识用于指示哪个小区组中的无线链路控制RLC实体和/或逻辑信道作为所述主路径。
在上述方法中，在所述PDCP重复被去激活时，将PDCP协议数据单元PDCP PDU发送至所述切换MAC CE指定的激活的无线链路控制RLC实体。
在上述方法中，在所述PDCP重复被去激活时，根据接收到所述MAC CE时激活的无线链路控制RLC实体关联的逻辑信道的逻辑信道标识大小，来选择作为PDCP协议数据单元PDCP PDU的发送对象的逻辑信道或者RLC实体。
在上述方法中，在所述UE处于双连接的情况下，在接收到用于去激活所述PDCP重复的所述MAC CE时，若处于激活态的RLC实体存在两个，则按照数据分离方法将所述PDCP PDU发送到处于激活态的所述RLC实体；若小区组中处于激活态的RLC实体超过两个，则按照数据分离方法将所述PDCP PDU发送到根据逻辑信道标识而预定义的逻辑信道关联的所述RLC实体。
根据本发明的第二方面，提供一种用户设备，包括：处理器；以及存储器，存储有指令；其中，所述指令在由所述处理器运行时执行根据上下文所述的用户设备中的方法。
根据本发明的第三方面，提供一种基站中的方法，包括：生成用于去 激活分组数据汇聚协议PDCP重复的MAC控制元素MAC CE；和将所述MAC CE发送至用户设备UE，所述UE基于所述MAC CE进行所述PDCP重复的去激活。
根据本发明的第四方面，提供一种基站，包括：处理器；以及存储器，存储有指令；其中，所述指令在由所述处理器运行时执行根据上下文所述的基站中的方法。
附图说明
通过下文结合附图的详细描述，本公开的上述和其它特征将会变得更加明显，其中：
图1表示基于本公开的实施例的用户设备UE中的方法100的流程图。
图2表示基于本公开实施例的用户设备20的框图。
图3表示基于本公开的实施例的基站中的方法300的流程图。
图4表示基于本公开实施例的基站40的框图。
图5表示切换MAC CE的示意图。
具体实施方式
下面结合附图和具体实施方式对本公开进行详细阐述。应当注意，本公开不应局限于下文所述的具体实施方式。另外，为了简便起见，省略了对与本公开没有直接关联的公知技术的详细描述，以防止对本公开的理解造成混淆。
下面描述本公开涉及的部分术语，如未特别说明，本公开涉及的术语采用此处定义。本公开给出的术语在NR、LTE和eLTE中可能采用不同的命名方式，但本公开中采用统一的术语，在应用到具体的系统中时，可以替换为相应系统中采用的术语。
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-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 eNB或Master gNB，记为MeNB(对应E-UTRAN或LTE或eLTE的基站)或MgNB(对应5G-RAN或NR的基站)。在双连接中，至少终止于处理UE与核心网间交互的控制节点移动管理实体(可记为S1-MME)的eNB；或者，至少终止于NG-C的gNB，所述NG-C是NG-RAN和5GC的控制面接口。
辅基站：Secondary eNB或Secondary gNB，记为SeNB(对应E-UTRAN或LTE或eLTE的基站)或SgNB(对应5G-RAN或NR的基站)。在双连接中，不是主基站但为UE提供额外的无线资源的基站。
主小区：Primary Cell，PCell。工作在主频率上的小区，可以是UE在其上执行初始连接建立过程或发起连接重建过程或在切换过程中被指定为主小区的小区。本公开所述小区也可称为载波或光束集(a set ofbeam)。
主辅小区：Primary Secondary Cell，PSCell。在执行改变SCG的过程中指示UE用于执行随机接入的SCG小区。
辅小区：Secondary Cell，SCell。工作在辅频率上的小区，所述小区可在RRC连接建立之后配置且可用于提供额外的无线资源。
小区组：Cell Group，CG，在双连接或多连接中，关联到主基站或辅基站的一组服务小区或载波，可以是MCG或SCG。
主小区组：Master Cell Group，MCG。对于未配置双连接的UE，MCG由所有的服务小区组成；对于配置了双连接的UE，MCG由服务小区的子集组成(即关联到主基站的一组服务小区)，其中包含PCell和0个或1个或多个SCell。
辅小区组：Secondary Cell Group，SCG。在双连接中，与SeNB或SgNB关联的一组服务小区。SCG可以包含一个PSCell，还可以包含一个或多个SCell。
双连接：dual Connectivity，DC。
DRB：Data Radio Bearer carrying user plane data，承载用户面数据的数据无线承载或简称数据无线承载。
SRB：Signalling Radio Bearer，信令无线承载。
分离SRB：split SRB。
如未特别说，本公开中所述承载或无线承载可以是：SRB、DRB、分离DRB(例如：MCG分离DRB或SCG分离DRB)、分离SRB(例如MCG分离SRB或SCG分离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重复。
数据总量：PDCP数据量和所关联的两个或多个RLC(或被激活的RLC)数据量(等待初始传输的RLC数据量)的总量(the total amount of PDCP data volume and RLC data volume pending for initial transmission in the activated RLC entities)。
主路径：Primary path，在载波聚合中，当PDCP重复被去激活时，PDCP实体将PDCP PDU发送到主路径。在双连接中，当PDCP重复被去激活时，如果数据总量小于数据分离门限，则，PDCP实体将PDCP PDU发送到主路径。
辅路径：secondary path，在载波聚合和双连接中，当PDCP重复被激活时，用于发送PDCP PDU的RLC实体和/或逻辑信道和/或RLC承载。具体的，当PDCP重复被激活时，PDCP实体复制PDCP PDU并发送到被激活的RLC实体和/或逻辑信道和或RLC承载(也可称为主路径和辅路径)。 本公开中的实施例具体描述了那些RLC实体和/或逻辑信道和或RLC承载是被认为激活的，在所述被激活的RLC实体和/或逻辑信道和/或RLC承载中，除主路径外的RLC实体和/或逻辑信道和/或RLC承载均可称为辅路径。
下面，对本公开中的用户设备UE中的方法进行说明，具体而言，对用户设备UE中承载的PDCP重复所涉及的控制方法进行说明。作为一例，图1中表示基于本公开的实施例的用户设备UE中的方法100的流程图。
在步骤S101中，用户设备UE从基站接收用于去激活分组数据汇聚协议PDCP重复的MAC控制元素MAC CE。
在步骤S102中，用户设备UE基于接收到的所述MAC CE，进行所述PDCP重复的去激活。
所述MAC CE可以包含：重复激活/去激活MAC CE、以及切换MAC CE。
在步骤S101执行之前，用户设备UE先从基站接收包含主路径指示信息的无线资源控制RRC消息，在UE与基站之间基于载波聚合进行通信的情况下(即承载被配置为基于载波聚合通信，所述承载或其PDCP实体关联的RLC实体和/或逻辑信道和/或RLC承载属于一个小区组或利用同一小区组中的小区的资源进行数据传输)，若PDCP重复被去激活，则PDCP实体将PDCP协议数据单元PDCP PDU发送至主路径指示信息所指示的主路径。
进而，在UE处于双连接的情况下(即承载被配置为分离承载，所述承载或其PDCP实体关联的RLC实体和/或逻辑信道和/或RLC承载属于不同的小区组或利用不同小区组中的小区的资源进行数据传输)，所述主路径指示信息包括小区组指示标识，所述小区组指示标识用于指示哪个小区组中的无线链路控制RLC实体和/或逻辑信道作为所述主路径。
另外，例如，在所述PDCP重复被去激活时，可以将PDCP协议数据单元PDCP PDU发送至所述切换MAC CE指定的激活的无线链路控制RLC实体。
例如，在所述PDCP重复被去激活时，可以根据接收到所述MAC CE时激活的无线链路控制RLC实体关联的逻辑信道的逻辑信道标识大小，来选择作为PDCP协议数据单元PDCP PDU的发送对象的逻辑信道或者RLC实体。
例如，在所述UE处于双连接的情况下，在接收到用于去激活所述PDCP重复的所述MAC CE时，若处于激活态的RLC实体存在两个，则按照数据分离方法将所述PDCP PDU发送到处于激活态的所述RLC实体；若小区组中处于激活态的RLC实体超过两个，则按照数据分离方法将所述PDCP PDU发送到根据逻辑信道标识而预定义的逻辑信道关联的所述RLC实体。
关于在PDCP重复被去激活时如何发送PDCP PDU，并不限定于上述内容，可以根据以下记载的实施例进行适当变更。
此外，图2示出了根据本公开实施例的用户设备20的框图。如图2所示，该用户设备20包括处理器201和存储器202。处理器201例如可以包括微处理器、微控制器、嵌入式处理器等。存储器202例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统等。存储器202上存储有程序指令。该指令在由处理器201运行时，可以执行本公开详细描述的用户设备中的上述方法。
再有，作为一例，图3中表示基于本公开的实施例的基站中的方法300的流程图。
在步骤S301中，基站装置生成用于去激活分组数据汇聚协议PDCP重复的MAC控制元素MAC CE。
在步骤S302中，基站装置将所生成的MAC CE发送至用户设备UE，用户设备UE基于所述MAC CE进行所述PDCP重复的去激活。
此外，图4示出了根据本公开实施例的基站40的框图。如图4所示，该基站40包括处理器401和存储器402。如上述所述，本公开中的基站40可以是任何类型基站，包含但不限于：Node B、增强基站eNB，也可以是5G通信系统基站gNB、或者微基站、微微基站、宏基站、家庭基站等。处理器401例如可以包括微处理器、微控制器、嵌入式处理器等。存储器402例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统等。存储器402上存储有程序指令。该指令在由处理器401运行时，可以执行本公开详细描述的基站中的上述方法。
以下，对本公开所涉及的具体的示例以及实施例等进行详细说明。另外，如上所述，本公开中记载的示例以及实施例等是为了容易理解本发明 而进行的示例性说明，并不是对本发明的限定。
首先，下面描述基站为用户设备配置支持PDCP重复的承载并设置其初始状态的实施例。
用户设备接收来自基站的RRC消息(本公开实施例中的RRC消息可以是RRC重配置消息)，所述消息中包含一个激活指示标识(记为第一指示标识，例如，用信元activatedPath表示)。所述激活指示标识可以用于指示处于激活态的RLC实体和/或逻辑信道和/或RLC承载；或者，所述激活指示标识可以用于指示当PDCP重复被激活或去激活时，处于激活态的RLC实体和/或逻辑信道和/或RLC承载；或者，所述激活指示标识可以用于指示初始状态中处于激活态的RLC实体和/或逻辑信道和/或RLC承载；或者，所述激活指示标识可以用于指示对应的RLC实体和/或逻辑信道和/或RLC承载是否处于激活态。
可选的，所述RRC消息中还包括一个信元(记为maxNrofActivatedLCH)用于指示在PDCP重复被激活时，最大可激活的RLC实体和/或逻辑信道和/或RLC承载数。所述信元的取值为整数且不超过可为一个承载配置的最大RLC实体和/或逻辑信道和/或RLC承载数或逻辑信道标识的最大值maxLC-ID。
可选的，所述RRC消息中还包含一个信元(记为releaseAllowedServingCells)用于指示去激活PDCP重复后是否取消服务小区的限制(服务小区的限制可通过信元allowedServingCells配置，如果该信元出现，则对应逻辑信道的UL MAC SDU只能映射到该信元指定的小区列表中的服务小区)。换言之，去激活PDCP重复后，来自逻辑信道的上行UL MAC SDU可以映射到该小区组中配置的任意(或所有)服务小区。所述信元可以在PDCP-config中配置，此时应用于所有RLC实体或逻辑信道。所述信元也可以在LogicalChannelConfig中配置，此时仅应用于对应的逻辑信道或关联所述逻辑信道的RLC实体。例如，如果所述信元的取值为1或TRUE或所述信元出现，则表示去激活PDCP重复后，取消服务小区限制。
可选的，在载波聚合中，如果所述激活指示标识指示的被激活的RLC实体和/或逻辑信道和/或RLC承载数超过两个，则PDCP重复被激活。PDCP实体将复制PDCP PDU并发送到其关联的被激活的RLC实体和/或逻辑信 道和/或RLC承载。如果所述激活指示标识指示的被激活的RLC实体和/或逻辑信道和/或RLC承载只有一个，则PDCP重复被去激活。PDCP实体将PDCP PDU发送到所述被激活的RLC实体和/或逻辑信道和/或RLC承载。
可选的，RRC消息中还包含一个PDCP重复指示标识(记为pdcp-Duplication)，用于指示上行重复状态在收到此信元时是否配置且激活。在载波聚合中，如果所述PDCP重复指示标识取值为真(TRUE)，则PDCP实体复制PDCP PDU并发送到被激活的多个RLC实体，如果所述PDCP重复指示标识取值为假(FALSE)，则PDCP实体将PDCP PDU发送到被激活的RLC实体(或者主路径)或者PDCP实体将PDCP PDU发送到被激活的一个RLC实体(所述RLC实体是被激活的RLC实体中关联到最小(或较小或最大或较大)逻辑信道标识的逻辑信道的RLC实体)。如果PDCP重复指示标识的取值为假，并且RRC消息中没有配置主路径，则只有一个RLC实体和/或逻辑信道和/或RLC承载被激活(即其激活指示标识取值为TRUE)。在双连接中，如果所述pdcp-Duplication取值为真(TRUE)，则PDCP实体复制PDCP PDU并发送到其关联的多个被激活的RLC实体和/或逻辑信道和/或RLC承载。如果pdcp-Duplication取值为假(FALSE)，则PDCP实体按照分离承载数据发送方式发送PDCP PDU。具体地，在这种情况下RRC消息中还包含主路径和/或数据分离门限(在本公开中记为ul-DataSplitThreshold)的配置，如果数据总量等于或超过数据分离门限，PDCP实体将PDCP PDU发送到所被激活的两个或多个RLC实体中的一个。如果数据总量小于数据分离门限，PDCP实体将PDCP PDU发送到主路径指定的RLC实体。所述主路径的取值可以是小区组标识或者MCG或者SCG，此时当数据总量小于数据分离门限时，PDCP实体将PDCP PDU发送到被激活且属于(或关联到)主路径指示的小区组的RLC实体和/或逻辑信道和/或RLC承载。
可选的，载波聚合中，对于PDCP控制PDU，当PDCP重复被激活时，可以预定义将PDCP控制PDU发送到被激活且关联到逻辑信道标识最小(或较小或最大或较大)的逻辑信道的RLC实体。换言之，此时将被激活且关联到逻辑信道标识最小(或较小或最大或较大)的逻辑信道的RLC实体作为主路径。
实施例一
所述激活指示标识可以包含在PDCP-config中，用于指示某个小区组的一个或多个RLC实体或逻辑信道或RLC承载被激活。所述激活指示标识(记为ActivatedPath)可以包括小区组指示标识(例如，用信元cellGroup表示)和/或逻辑信道指示标识(例如，用信元logicalHChannelList表示)。所述小区组指示标识用于指示小区组，主小区组(master cell group，MCG)的小区组标识(记为CellGroupId)可为0，其他取值表示辅小区组。所述逻辑信道指示标识用于指示被激活的RLC实体(或其关联的逻辑信道)和/或逻辑信道和/或RLC承载，其取值可以是逻辑信道标识LogicalChannelIdentity(即LCH ID)列表或一个位图，位图中的每一位对应一个逻辑信道，可以按关联到所述承载或其PDCP实体的逻辑信道的逻辑信道标识从大到小或从小到大的顺序依次对应位图中的每一比特(从左到右)。例如，位图中取值为0的比特对应的RLC实体和/或逻辑信道和/或RLC承载被去激活(或被激活)；位图中取值为1的比特对应的RLC实体和/或逻辑信道和/或RLC承载被激活(或被去激活)。在载波聚合中，激活指示标识可以仅包含逻辑信道指示标识。在双连接中，逻辑信道标识列表中的元素个数或者位图的长度可设置为支持PDCP重复的承载可配置的最大RLC实体数或最大逻辑信道数减1。
PDCP-Config information element
Figure PCTCN2019124011-appb-000001
Figure PCTCN2019124011-appb-000002
实施例二
所述激活指示标识可以包含在PDCP-config中，所述激活指示标识有两个信元，一个信元(记为MCGActivatedPath)用于指示主小区组MCG中被激活的RLC实体和/或逻辑信道和/或RLC承载。另一个信元(记为SCGActivatedPath)用于指示辅小区组SCG中被激活的RLC实体和/或逻辑信道和/或RLC承载。所述MCGActivatedPath(或SCGActivatedPath)取值可以是逻辑信道标识LogicalChannelIdentity(即LCH ID)列表或一个位图，位图中的每一位对应一个逻辑信道，可以按关联到所述承载或其PDCP实体且位于MCG(或SCG)中的逻辑信道的逻辑信道标识从大到小或从小到大的顺序依次对应位图中的每一比特(从左到右)。例如，位图中取值为0的比特对应的RLC实体和/或逻辑信道和/或RLC承载被去激活(或被激活)；位图中取值为1的比特对应的RLC实体和/或逻辑信道和/或RLC承载被激活(或被去激活)。在双连接中，逻辑信道标识列表中的元素个数或者位图的长度可设置为支持PDCP重复的承载可配置的最大RLC实体数或最大逻辑信道数减1。
可选的，在MCGActivatedPath和/或SCGActivatedPath中包含一个主路径指示信元，用于指示对应的小区组或属于对应小区组的RLC实体(或逻辑信道)或属于对应小区组的被激活的RLC实体(或逻辑信道)是否作为主路径。如果所述主路径指示信元取值为真(TRUE)或1或出现，则对应的小区组或属于对应小区组的RLC实体(或逻辑信道)或属于对应小区组的被激活的RLC实体(或逻辑信道)作为主路径，否则不作为主路径，反之亦然。
PDCP-Config information element
Figure PCTCN2019124011-appb-000003
Figure PCTCN2019124011-appb-000004
实施例三
所述激活指示标识(记为initialActivated)可以包含在RLC-BearerConfig中，用于指示对应的RLC实体和/或逻辑信道和/或RLC承载是否处于激活态，或者用于指示对应的RLC实体和/或逻辑信道和/或RLC承载在收到此信元时是否处于激活态。
如果激活指示标识initialActivated取值为TRUE或1或所述标识出现，表示对应的RLC实体和/或逻辑信道和/或RLC承载处于激活态；如果激活指示标识initialActivated取值为FALSE或0或所述标识不出现，表示对应的RLC实体和/或逻辑信道和/或RLC承载处于去激活态。反之亦然。
可选的，在RLC-BearerConfig中还可以包含主路径信元，其取值为真(TRUE)或假(FALSE)，或者0或1，或者根据其出现或不出现来确定，如果主路径信元取值为TRUE或1或出现，则其关联的RLC实体作为主路径，否则，不作为主路径。反之亦然。
可选的，在载波聚合的初始状态中，如果PDCP重复被去激活(例如pdcp-Duplication不出现或被置为False)，只有一个RLC实体处于激活态，即只有一个RLC实体的激活指示标识initialActivated取值为TRUE或1或所述标识出现；如果PDCP重复被激活，至少有两个RLC实体处于激活态即至少有两个RLC实体的激活指示标识initialActivated取值为TRUE或1或所述标识出现。
RLC-BearerConfig information element
Figure PCTCN2019124011-appb-000005
实施例四
在载波聚合中，初始状态中，如果PDCP重复被激活，PDCP实体将PDCP PDU发送到关联到具有最小和次小(或最大和次大)逻辑信道标识的逻辑信道的RLC实体(此处以两个为例，如果由多个，在依次类推)。如果PDCP重复被去激活，PDCP实体将PDCP PDU发送到关联到具有最小(或最大)逻辑信道标识的逻辑信道的RLC实体。
在双连接中，初始状态中，如果PDCP重复被激活，PDCP实体将PDCP PDU发送到每个小区组中关联到具有最小(或最大)逻辑信道标识的逻辑信道的RLC实体。如果PDCP重复被去激活且数据总量大于或等于数据分离门限，PDCP实体将PDCP PDU发送到两个小区组中分别关联到具有最小(或最大)逻辑信道标识的逻辑信道的RLC实体中的一个RLC实体。如果PDCP重复被去激活且数据总量小于数据分离门限，PDCP实体将PDCP PDU发送到主路径。所述主路径可以通过RRC配置主路径所属的小区组，然后预定义所述小区组中关联到具有最小(或最大)逻辑信道标识的逻辑信道的RLC实体作为主路径。
备选的，PDCP重复的初始状态总是去激活的。在载波聚合中，PDCP实体将PDCP PDU发送到关联到具有最小(或最大)逻辑信道标识的逻辑信道的RLC实体。在双连接中，如果数据总量大于或等于数据分离门限，PDCP实体将PDCP PDU发送到两个小区组中分别关联到具有最小(或最 大)逻辑信道标识的逻辑信道的RLC实体中的一个RLC实体。如果数据总量小于数据分离门限，PDCP实体将PDCP PDU发送到主路径。所述主路径可以通过RRC配置主路径所属的小区组，然后预定义所述小区组中关联到具有最小(或最大)逻辑信道标识的逻辑信道的RLC实体作为主路径。
实施例五
所述激活指示标识可以包含在PDCP-config中，所述激活指示标识包含两个信元，即主路径指示标识(记为PrimaryPath)和辅路径指示标识(记为SecondaryPath)。所述主路径指示标识又可以包含两个指示标识，一个是用于指示主路径(或主RLC实体)的小区组的小区组标识(即cell group ID)和/或指示主路径的逻辑信道的逻辑信道标识(或逻辑信道标识列表或位图)；所述辅路径指示标识也可以包含两个指示标识，一个是用于指示辅路径的小区组的小区组标识和/或用于指示辅路径的逻辑信道的逻辑信道标识(或逻辑信道标识列表或位图)。所述位图中的每一位对应一个逻辑信道，可以按关联到所述承载或其PDCP实体且位于小区组标识指示的小区组中的逻辑信道的逻辑信道标识从大到小或从小到大的顺序依次对应位图中的每一比特(从左到右)。例如，位图中取值为0的比特对应的RLC实体和/或逻辑信道和/或RLC承载被去激活(或被激活)；位图中取值为1的比特对应的RLC实体和/或逻辑信道和/或RLC承载被激活(或被去激活)。在双连接中，逻辑信道标识列表中的元素个数或者位图的长度可设置为支持PDCP重复的承载可配置的最大RLC实体数或最大逻辑信道数减1。在去激活PDCP重复后，如果主路径包含多个逻辑信道或RLC实体或RLC逻辑信道，可以预定义其中具有最大或最小逻辑信道标识的或逻辑信道或RLC实体或RLC逻辑信道作为发送PDCP PDU的逻辑信道或RLC实体或RLC逻辑信道(即PDCP实体将PDCP PDU发送到所述逻辑信道或RLC实体或RLC逻辑信道)，或者通过RRC配置(例如，通过一个指示标识指示)其中一个逻辑信道或RLC实体或RLC逻辑信道用于发送PDCP PDU。
需要说明的是，在本公开中，对应基于载波聚合的PDCP重复，由于关联到同一个支持PDCP重复的载波(或PDCP实体)的RLC实体或逻辑信道属于一个小区组，此时激活指示标识中可以不包含小区组标识，换言之，激活指示标识中仅包含逻辑信道指示信息。
下面描述PDCP重复被激活时动态切换RLC实体的实施例。
实施例六：切换MAC CE
用户设备UE接收来自基站的RRC消息，所述RRC消息为支持PDCP重复的承载配置多个RLC实体和/或逻辑信道。
用户设备接收来自基站的切换MAC CE，所述切换MAC CE用于激活和/或去激活关联到支持PDCP重复的承载的RLC实体和/或逻辑信道。所述切换MAC CE中包含用于指示支持PDCP重复的承载的域(可记为Di)以及所述承载(或所述承载的PDCP实体)关联的RLC实体或逻辑信道的域(可记为Lij)。切换MAC CE是MAC实体相关的，来自某个MAC实体的切换MAC CE仅指示关联到此MAC实体的RLC实体(或逻辑信道)及其对应的支持重复的DRB或SRB。
图5示出了切换MAC CE示意图。在图5中，Di对应DRBi或SRBi，其中i是按照配置了PDCP重复的DRB(或SRB)的DRB标识(或SRB标识)的升序或降序排列对应的序号，所述DRB(或SRB)关联的RLC实体(或关联的部分RLC)位于此MAC实体中。SRB也可以支持动态切换用于数据传输的RLC实体或逻辑信道。如果SRB支持动态切换用于数据传输的RLC实体或逻辑信道，则SRB和DRB可以采用不同的切换MAC CE；或者在切换MAC CE中包含一个域用于指示对应的切换MAC CE是用于SRB还是DRB(根据所述域的不同取值来区分时用于SRB的MAC CE还是用于DRB的MAC CE)，例如，如果所述域的取值为0(或1)，则对应的切换MAC CE用于SRB(或DRB)，即Di对应SRB(或DRB)，反之亦然；又或者按先SRB后DRB或先DRB后SRB的方式映射到Di。同时，各SRB(或DRB)间又可以按照承载标识从小到大或从大到小的顺序映射到切换MAC CE中的各个Di(可以按照从左到右或从右到左的顺序映射，例如D0对应承载标识最小或最大的DRB或SRB)。
图5中，域Lij用于表示激活或去激活Di所对应承载的第j个RLC实体和/或逻辑信道，j是Di对应的承载关联到这个MAC实体的RLC实体和/或逻辑信道按照逻辑信道标识升序或降序排列的序号。如果所述域的取值为0，则去激活对应的RLC实体和/或逻辑信道，如果所述域的取值为1， 则激活对应的RLC实体和/或逻辑信道。反之亦然。
优选的，当Di＝0时，其对应的Lij域不包含在切换MAC CE中。备选的，当Di＝0，最多只有一个Lij域取值为1。备选的，当Di＝0，其对应的Lij域不包含在切换MAC CE中，但切换MAC CE中包含一个域用来指示去激活PDCP重复后处于激活态的RLC实体和/或逻辑信道，所述域的取值可以为被激活的逻辑信道的逻辑信道标识或者被激活的RLC实体关联的逻辑信道的逻辑信道标识，或者所述域的取值为0或1表示去激活除关联到具有最小逻辑信道标识的逻辑信道的RLC实体外的其他RLC实体，或者所述域的取值为0或1表示去激活除关联到具有最大逻辑信道标识的逻辑信道的RLC实体外的其他RLC实体。
如果切换MAC CE还用于激活或去激活PDCP重复，那么Di用于指示SRBi或DRBi的PDCP重复是处于激活态还是去激活态。Di＝0表示SRBi或DRBi的PDCP重复被去激活，Di＝1表示SRBi或DRBi的PDCP重复被激活。反之亦然。可选的，Di还用于指示Lij是否出现在所述切换MAC CE中，当Di＝0时，其对应的Lij域不包含在切换MAC CE中，当Di＝1时，其对应的Lij域包含在切换MAC CE中。
如果切换MAC CE不用于重复激活/去激活，切换MAC CE中可以仅包含激活的承载对应的逻辑信道(可以是仅属于这个MAC实体的逻辑信道)。此时图5中Di域可以不携带，切换MAC CE中仅携带那些被激活的承载对应的Lij域。Lij域的排列与图5一致，可以按照其对应的Di的承载标识大小按升序或降序排列，每个被激活的承载对应的Lij可以按照逻辑信道标识大小升序或降序排列。
备选的，切换MAC CE还可以每次仅指示一个承载切换RLC实体和/或逻辑信道，此时，切换MAC CE中携带承载标识和Lij域(用于指示对应承载被激活的逻辑信道)。
在接收到切换MAC CE后，用户设备执行以下操作之一：
1)如果PDCP重复被去激活(Di域为0)，指示上层去激活对应承载的PDCP重复。
2)如果PDCP重复被激活(Di域为1)，这种情况表示切换RLC实体或逻辑信道，则指示上层切换RLC实体和/或逻辑信道；或者指示上层被激活的逻辑信道标识或被激活的RLC实体关联的逻 辑信道的逻辑信道标识或指示上层逻辑信道标识或指示上层被激活的RLC实体。可选的，还指示上层激活对应承载的PDCP重复。
3)如果切换RLC实体，指示承载标识对应的上层(PDCP实体)切换逻辑信道(或RLC实体)或将逻辑信道标识(或其对应的RLC实体)指示上层。
实施例七：RRC配置+切换MAC CE
用户设备接收到来自基站的RRC消息(例如RRC重配置消息)，所述消息中包含用于指示PDCP重复激活后可使用的RLC实体组或逻辑信道组或RLC承载组。具体地，将关联到同一承载的RLC实体和/或逻辑信道分成若干个组，可以在RRC消息中为每个组配置一个组号。例如用一个组号指示标识指示组号，另一个分组指示标识指示组中包含的RLC实体或逻辑信道，可以用逻辑信道标识列表方式或位图方式来表示分组。按照位图方式分组时，位图中的每位对应关联到此承载的每个RLC实体和/或逻辑信道(可按照从小到大或从大到小的顺序映射)，位图中为1的位对应的RLC实体和/或逻辑信道划分到同一组中。备选的，按照RLC实体和/或逻辑信道分组的先后顺序对RLC实体和/或逻辑信道组进行编号，第一个分组编号为0(或1)，第2个分组编号为1(或2)，以此类推。
用户接收来自基站的切换MAC CE。所述切换MAC CE用于指示PDCP重复的RLC实体或逻辑信道切换到MAC CE总指示的RLC实体或逻辑信道。优选的，所述切换MAC CE的域取值为RLC实体和/或逻辑信道分组的编号。备选，所述切换MAC CE是一个位图，位图中的比特按照分组编号升序或降序一一对应，位图中比特(或位)取值为1表示激活所述分组中的RLC实体和/或逻辑信道，位图中比特(或位)取值为0表示去激活所述分组中的RLC实体和/或逻辑信道。MAC CE中最多只有一个比特可以置为1。可选的，如果位图中所有比特都被置位0，则去激活对应承载的PDCP重复。
下面描述PDCP重复被去激活后如何确定PDCP实体将PDCP PDU发送到哪个RLC实体的实施例(对载波聚合和双连接场景分别讨论)。
以实施例八～实施例十为例，对载波聚合的情况下的处理进行说明。在 载波聚合中，关联到同一支持PDCP重复的承载或其PDCP实体的RLC实体和/或逻辑信道和/或RLC承载属于同一小区组。
实施例八(去激活PDCP重复后，PDCP实体将PDCP PDU发送到主路径)
在本实施例中，UE接收到来自基站的RRC消息，所述RRC消息中携带一个主路径指示信元(记为primaryPath)。所述主路径指示信元可以包括用于指示小区组标识的小区组指示信元cellGroup和/或用于指示逻辑信道标识的逻辑信道指示信元logicalChannel)。如果PDCP重复被去激活(例如接收到重复激活/去激活MAC CE)，则PDCP实体将PDCP PDU发送到主路径。换言之，即使在PDCP重复被去激活前主路径被去激活，当PDCP重复被去激活时，主路径被激活并被PDCP实体用于发送PDCP PDU。例如，当MAC实体接收到重复激活/去激活MAC CE(或切换MAC CE)时，如果主路径或主路径指示的RLC实体或逻辑信道或RLC承载被去激活，则MAC层(MAC层指示上层)激活主路径或主路径指示的RLC实体或逻辑信道或RLC承载，并指示上层PDCP重复被去激活；或者，MAC层指示上层PDCP重复被去激活，由上层激活主路径或主路径指示的RLC实体或逻辑信道或RLC承载；或者当MAC实体接收到重复激活/去激活MAC CE(或切换MAC CE)时，指示上层去激活PDCP重复和/或主路径定义的RLC实体或逻辑信道标识对应的RLC实体或逻辑信道或逻辑信道标识。
实施例九(去激活PDCP重复后，PDCP实体将PDCP PDU发送到切换MAC CE指定的激活的RLC实体)
在本实施例中，UE接收到来自基站的切换MAC CE，例如所述切换MAC CE指示承载DRB i(或SRB i)对应的Di取值为0，即PDCP重复被去激活。
优选的，MAC实体激活承载DRB i(或SRB i)对应的Lij取值为1所对应的RLC实体和/或逻辑信道和/或RLC承载，并指示上层去激活对应承载的PDCP重复；或者，同时指示上层激活的RLC实体和/或逻辑信道和/或RLC承载和/或逻辑信道标识；或者，指示上层激活PDCP重复和/或被激活的RLC实体和/或逻辑信道。在这种情况下，对应取值为0的Di，其对应的Lij只有一个取值为1。
备选的，当Di＝0，其对应的Lij域不包含在切换MAC CE中，但切换 MAC CE中包含一个域用来指示去激活PDCP重复后处于激活态的RLC实体和/或逻辑信道。所述域的取值为被激活的逻辑信道标识或被激活的RLC实体关联的逻辑信道的逻辑信道标识。
实施例十(去激活PDCP重复后，PDCP实体将PDCP PDU发送到接收到激活/去激活PDCP重复的MAC CE时激活的RLC实体关联的逻辑信道的逻辑信道标识较小(或较大或最小或最大)者)
在本实施例中，在接收到用于去激活PDCP重复的MAC CE(例如重复激活/去激活MAC CE或切换MAC CE)时，如果某个承载的PDCP重复被去激活，MAC实体在接收到所述MAC CE时执行以下操作至少一项：
A.去激活(或指示上层去激活)关联到逻辑信道标识较大(或较小)的逻辑信道的RLC实体和/或RLC承载，或者去激活逻辑信道标识较大(或较小)的逻辑信道。
B.去激活(或指示上层去激活)所述承载对应的(或所述承载的PDCP实体关联)的RLC实体和/或逻辑信道和/或RLC承载，逻辑信道标识最大(或者最小)者除外或者关联到其中最大(或者最小)逻辑信道标识的RLC实体和/或RLC承载除外或者具有最大(或者最小)逻辑信道标识的逻辑信道除外。所述最大或最小仅考虑被激活的逻辑信道(或RLC实体)对应的逻辑信道标识中最大者或最小者。
C.指示上层去激活PDCP重复。
D.指示上层激活其中具有最大(或最小)逻辑信道标识的逻辑信道或指示上层激活关联到其中最大(或最小)逻辑信道标识的RLC实体或RLC承载。所述最大或最小仅考虑被激活的逻辑信道(或RLC实体)对应的逻辑信道标识中最大者或最小者。
在本实施例中，预定义去激活承载的PDCP重复后，PDCP实体将PDCP PDU发送到关联到具有最小(或最大)逻辑信道标识的逻辑信道的RLC实体。所述最大或最小仅考虑被激活的逻辑信道(或RLC实体)对应的逻辑信道标识中最大者或最小者。本公开实施例中，激活一个RLC实体是指PDCP实体将PDCP PDU发送到所述RLC实体。去激活一个RLC实体是指PDCP实体不再将PDCP PDU发送到所述RLC实体。
接下来，以实施例十一～实施例十三为例，对双连接情况下的处理进行说明。
在双链接中，关联到同一支持PDCP重复的承载或其PDCP实体的RLC实体和/或逻辑信道和/或RLC承载属于不同的小区组。对于配置了PDCP重复的承载(例如，基站通过RRC消息为用户设备配置)，如果PDCP重复处于激活态，PDCP实体将复制PDCP PDU并发送到其关联的且被激活的RLC实体上；如果PDCP重复处于去激活态且被激活的RLC实体属于不同的小区组且数量总量等于或大于RRC消息中配置的数据分离门限(例如，利用信元ulDataSplitThreshold指示)，将数据(即PDCP PDU)发送到主路径(在本公开中，主路径也可称为主RLC实体)或辅RLC实体(或被激活的辅RLC实体)；如果PDCP重复处于去激活态且被激活的RLC实体属于不同的小区组且如果数据总量小于RRC消息中配置的数据分离门限(例如，利用信元ulDataSplitThreshold指示)，将数据(即PDCP PDU)发送到主路径。这种根据数据总量与数据分离门限值的大小进行比较，如果数据总量小于数据分离门限，那么PDCP实体将PDCP PDU仅发送到主路径，如果数据总量大于或等于数据分离门限，那么PDCP实体将PDCP PDU发送到主路径和其他被激活的RLC实体之一的数据发送方式称为数据分离。主路径可以通过本公开其他实施例中所述的方式定义。
实施例十一(去激活PDCP重复后，PDCP实体将PDCP PDU发送到初始状态使用的RLC实体)
在本实施例中，UE接收到来自基站的RRC消息，所述RRC消息中包含支持PDCP重复的承载的配置。具体地，所述RRC消息中包含主路径的配置，所述主路径的配置可以包括小区组指示标识(或包括小区组指示标识和逻辑信道指示标识)，所述小区组指示标识用于指示哪个小区组中的RLC实体和/或逻辑信道可以作为主路径。如果主路径配置同时包括小区组指示标识和逻辑信道指示标识，则只有位于小区组指示标识指示的小区且关联到所述逻辑信道指示标识指示的逻辑信道的RLC实体(或逻辑信道标识为逻辑信道指示标识的值的逻辑信道)可以作为主路径。
当UE接收到来自基站的用于去激活某承载的PDCP重复的MAC CE(例如重复激活/去激活MAC CE或切换MAC CE)时，执行以下操作之一：
A.MAC实体指示上层去激活PDCP重复，PDCP实体在收到去激活PDCP重复的指示后，采用数据分离方式，利用RRC消息中激活RLC实体和主路径传输数据。
B.MAC实体激活RRC消息中激活的RLC实体和/或逻辑信道并指示 上层去激活PDCP重复。
C.MAC实体指示上层RRC消息中激活的RLC实体和/或逻辑信道或逻辑信道标识，可选的，还指示上层去激活PDCP重复。
实施例十二(去激活PDCP重复后，PDCP实体将PDCP PDU发送到切换MAC CE指定的激活的RLC实体)
在这个实施例中，用于去激活承载的PDCP重复的MAC CE中携带逻辑信道标识指示信息，用于指示去激活PDCP重复后PDCP实体将PDCP PDU发送到关联到所述逻辑信道标识指示信息指示的逻辑信道的RLC实体。例如，当UE接收到来自基站的用于去激活某承载的PDCP重复的MAC CE(例如重复激活/去激活MAC CE或切换MAC CE)时，在MAC CE中，所述承载对应的Di取值为0，MAC实体激活对应Lij取值为1的RLC实体或关联到逻辑信道标识指示标识指示的逻辑信道的RLC实体和/或逻辑信道和/或指示上层去激活PDCP重复和/或将Lij取值为1所对应的逻辑信道标识(或逻辑信道或关联到具有所述逻辑信道标识的逻辑信道的RLC实体)指示给上层。
实施例十三(去激活PDCP重复后，PDCP实体将PDCP PDU发送到激活的RLC实体)
在这个实施例中，接收到用于去激活PDCP重复的MAC CE(例如重复激活/去激活MAC CE或切换MAC CE)时，如果处于激活态的RLC实体只有两个，PDCP实体按照数据分离方式将PDCP PDU发送到所述处于激活态的RLC实体(即在收到去激活PDCP重复的MAC CE时处于激活态的RLC实体)；如果某个小区组中处于激活态的RLC实体超过两个，预定义该小区组中逻辑信道标识最小(或最大)的逻辑信道或关联到最小(或最大)逻辑信道标识的逻辑信道的RLC实体用于PDCP实体根据数据分离方式发送PDCP PDU。所述最大或最小仅考虑被激活的逻辑信道(或RLC实体)对应的逻辑信道标识中最大者或最小者。
具体地，当UE接收到来自基站的用于去激活某承载的PDCP重复的MAC CE时，MAC实体执行以下操作至少一项：
A.对属于同一个小区组的多个被激活的RLC实体，MAC实体去激活(或指示上层去激活)关联到逻辑信道标识较大(或较小或最大或最小)的逻辑信道的RLC实体和/或RLC承载，或者去激活逻辑信道标识较大(或较小或最大或最小)的逻辑信道。
B.对属于同一个小区组的多个被激活的RLC实体，MAC实体去激活(或指示上层去激活)所述承载对应的(或所述承载的PDCP实体关联)的RLC实体和/或逻辑信道和/或RLC承载的除，逻辑信道标识最大(或者最小或较大或较小)者除外或者关联到其中最大(或者最小或较大或较小)逻辑信道标识的RLC实体和/或RLC承载除外。
C.指示上层去激活PDCP重复。
D.对属于同一个小区组的多个被激活的RLC实体，MAC实体指示上层激活其中具有最大(或最小或较大或较小)逻辑信道标识的逻辑信道或指示上层激活关联到其中最大(或最小或较大或较小)逻辑信道标识的RLC实体或RLC承载。
本实施例所述较大或较小或最大或最小仅考虑被激活的逻辑信道(或RLC实体)对应的逻辑信道标识中较大者或较小者或最大者或最小者。
在本公开实施例中，处于激活态的RLC实体和/或逻辑信道和/或RLC承载也可以称为被激活或被用于传输数据的RLC实体和/或逻辑信道和/或RLC承载。如果PDCP重复被激活，来自被激活的RLC实体或逻辑信道的上行UL MAC SDU只能在为其配置的服务小区上发送。所述处于激活态的RLC实体和/或逻辑信道和/或RLC承载可以是在PDCP重复被激活或去激活后用于传输PDCP PDU的RLC实体和/或逻辑信道和/或RLC承载。被激活的RLC实体和/或逻辑信道和/或RLC承载是指RRC消息中指示的RLC实体(或RRC消息中指示的处于激活态的RLC实体)或下层指示的RLC实体(或下层指示的处于激活态的RLC实体)。在载波聚合中，对应某个承载而言，本公开所述主路径是指去激活PDCP重复后，PDCP实体将PDCP PDU发往的RLC实体(或用于传输PDCP PDU的RLC实体)。在双连接中，对应某个承载而言，本公开所述主路径是指当PDCP数据量和和关联的(或关联且被激活的)RLC的待初始传输的RLC数据量的和小于RRC消息中配置的数据分离门限时，PDCP实体将数据发往的RLC实体(或用于传输PDCP PDU的实体)。本公开实施例所述指示上层RLC实体也可以表述为指示上层逻辑信道或逻辑信道标识。本公开中说述被激活的RLC实体是指用于发送PDCP PDU的实体，一个RLC实体被激活后，PDCP实体可将PDCP PDU发送到所述RLC实体。本公开中所述去激活RLC实体也可以替换为 去激活逻辑信道。
UE能力上报
UE接收来自基站的能力查询消息。UE向基站发送能力上报消息，所述能力上报消息中携带一个信元，所述信元用于指示可支持的最大RLC实体和/或逻辑信道数；或者所述信元用于指示可同时激活的最大RLC实体和/或逻辑信道数；或者所述信元用于指示PDCP实体最多可将重复的PDCP PDU发送给几个RLC实体。
重复PDU删除
对于配置了PDCP重复的PDCP实体，PDCP发送实体执行以下操作：
如果关联的RLC实体被切换(或者收到来自下层的切换RLC实体的指示或者收到来自下层的切换指示)，指示去激活的RLC实体删除所有重复的PDCP数据PDU。
本公开中所述去激活的RLC实体或逻辑信道或RLC承载是指PDCP实体不再将PDCP PDU发送到所述去激活的RLC实体。
运行在根据本发明的设备上的计算机可执行指令或者程序可以是通过控制中央处理单元(CPU)来使计算机实现本发明的实施例功能的程序。该程序或由该程序处理的信息可以临时存储在易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统中。
用于实现本发明各实施例功能的计算机可执行指令或程序可以记录在计算机可读存储介质上。可以通过使计算机系统读取记录在所述记录介质上的程序并执行这些程序来实现相应的功能。此处的所谓“计算机系统”可以是嵌入在该设备中的计算机系统，可以包括操作系统或硬件(如外围设备)。“计算机可读存储介质”可以是半导体记录介质、光学记录介质、磁性记录介质、短时动态存储程序的记录介质、或计算机可读的任何其他记录介质。
用在上述实施例中的设备的各种特征或功能模块可以通过电路(例如，单片或多片集成电路)来实现或执行。设计用于执行本说明书所描述的功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、或其他可编程逻辑器件、分立的门或晶体管逻辑、分立的硬件组件、或上述器件的任意组合。通用处理器可 以是微处理器，也可以是任何现有的处理器、控制器、微控制器、或状态机。上述电路可以是数字电路，也可以是模拟电路。因半导体技术的进步而出现了替代现有集成电路的新的集成电路技术的情况下，本发明的一个或多个实施例也可以使用这些新的集成电路技术来实现。
此外，本发明并不局限于上述实施例。尽管已经描述了所述实施例的各种示例，但本发明并不局限于此。安装在室内或室外的固定或非移动电子设备可以用作终端设备或通信设备，如AV设备、厨房设备、清洁设备、空调、办公设备、自动贩售机、以及其他家用电器等。
如上，已经参考附图对本发明的实施例进行了详细描述。但是，具体的结构并不局限于上述实施例，本发明也包括不偏离本发明主旨的任何设计改动。另外，可以在权利要求的范围内对本发明进行多种改动，通过适当地组合不同实施例所公开的技术手段所得到的实施例也包含在本发明的技术范围内。此外，上述实施例中所描述的具有相同效果的组件可以相互替代。

Claims (10)

  1. 一种用户设备UE中的方法，包括：
    从基站接收用于去激活分组数据汇聚协议PDCP重复的MAC控制元素MAC CE；和
    基于接收到的所述MAC CE，进行所述PDCP重复的去激活。
  2. 根据权利要求1所述的方法，其中，
    所述MAC CE包含：重复激活/去激活MAC CE、以及切换MAC CE。
  3. 根据权利要求2所述的方法，其中，
    从所述基站接收包含主路径指示信息的无线资源控制RRC消息，
    在所述UE与所述基站之间基于载波聚合进行通信的情况下，在所述PDCP重复被去激活时，将PDCP协议数据单元PDCP PDU发送至所述主路径指示信息所指示的主路径。
  4. 根据权利要求3所述的方法，其中，
    在所述UE处于双连接的情况下，所述主路径指示信息包括小区组指示标识，所述小区组指示标识用于指示哪个小区组中的无线链路控制RLC实体和/或逻辑信道作为所述主路径。
  5. 根据权利要求2所述的方法，其中，
    在所述PDCP重复被去激活时，将PDCP协议数据单元PDCP PDU发送至所述切换MAC CE指定的激活的无线链路控制RLC实体。
  6. 根据权利要求2所述的方法，其中，
    在所述PDCP重复被去激活时，根据接收到所述MAC CE时激活的无线链路控制RLC实体关联的逻辑信道的逻辑信道标识大小，来选择作为PDCP协议数据单元PDCP PDU的发送对象的逻辑信道或者RLC实体。
  7. 根据权利要求6所述的方法，其中，
    在所述UE处于双连接的情况下，在接收到用于去激活所述PDCP重复的所述MAC CE时，
    若处于激活态的RLC实体存在两个，则按照数据分离方法将所述PDCP PDU发送到处于激活态的所述RLC实体；
    若小区组中处于激活态的RLC实体超过两个，则按照数据分离方法将所述PDCP PDU发送到根据逻辑信道标识而预定义的逻辑信道关联的所述 RLC实体。
  8. 一种用户设备，包括：
    处理器；以及
    存储器，存储有指令；
    其中，所述指令在由所述处理器运行时执行根据权利要求1至7中任一项所述的方法。
  9. 一种基站中的方法，包括：
    生成用于去激活分组数据汇聚协议PDCP重复的MAC控制元素MAC CE；和
    将所述MAC CE发送至用户设备UE，所述UE基于所述MAC CE进行所述PDCP重复的去激活。
  10. 一种基站，包括：
    处理器；以及
    存储器，存储有指令；
    其中，所述指令在由所述处理器运行时执行根据权利要求9所述的方法。
PCT/CN2019/124011 2018-12-11 2019-12-09 用户设备及其方法、基站及其方法 WO2020119632A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
US17/311,791 US20220038950A1 (en) 2018-12-11 2019-12-09 User equipment and method thereof, and base station and method thereof
EP19895583.3A EP3897014A4 (en) 2018-12-11 2019-12-09 USER DEVICE AND METHODS THEREIN AND BASE STATION AND METHODS THEREIN
CA3123118A CA3123118A1 (en) 2018-12-11 2019-12-09 User equipment and method therein, and base station and method therein
IL283889A IL283889A (en) 2018-12-11 2021-06-10 User equipment and method thereof, and base station and method thereof

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811514595.7 2018-12-11
CN201811514595.7A CN111314906A (zh) 2018-12-11 2018-12-11 用户设备及其方法、基站及其方法

Publications (1)

Publication Number Publication Date
WO2020119632A1 true WO2020119632A1 (zh) 2020-06-18

Family

ID=71076259

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/124011 WO2020119632A1 (zh) 2018-12-11 2019-12-09 用户设备及其方法、基站及其方法

Country Status (6)

Country Link
US (1) US20220038950A1 (zh)
EP (1) EP3897014A4 (zh)
CN (1) CN111314906A (zh)
CA (1) CA3123118A1 (zh)
IL (1) IL283889A (zh)
WO (1) WO2020119632A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113630223A (zh) * 2020-05-08 2021-11-09 夏普株式会社 用户设备及其方法、基站及其方法

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107241164A (zh) * 2017-05-05 2017-10-10 电信科学技术研究院 一种无线承载重复传输的处理方法及装置
WO2018171734A1 (en) * 2017-03-24 2018-09-27 Mediatek Inc. User equipment and methods for pdcp duplication in 5g ran

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9883467B2 (en) * 2014-03-06 2018-01-30 Sharp Kabushiki Kaisha Terminal device, base station device, communication system, control method, and integrated circuit
US10448386B2 (en) * 2017-01-06 2019-10-15 Kt Corporation Method and apparatus for controlling redundant data transmission
KR102056197B1 (ko) * 2017-02-02 2019-12-16 엘지전자 주식회사 데이터 유닛을 전송하는 방법 및 장치
US10805836B2 (en) * 2017-05-05 2020-10-13 Qualcomm Incorporated Packet duplication at a packet data convergence protocol (PDCP) entity
EP3422767A1 (en) * 2017-06-26 2019-01-02 Panasonic Intellectual Property Corporation of America User equipment and base station participating in packet duplication during handover for nr
US11540205B2 (en) * 2018-08-08 2022-12-27 Lenovo (Singapore) Pte. Ltd. Method and apparatus for applying a cell restriction configuration
WO2020029137A1 (zh) * 2018-08-08 2020-02-13 富士通株式会社 重复传输的配置和或激活方法、重复传输的方法及装置

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018171734A1 (en) * 2017-03-24 2018-09-27 Mediatek Inc. User equipment and methods for pdcp duplication in 5g ran
CN107241164A (zh) * 2017-05-05 2017-10-10 电信科学技术研究院 一种无线承载重复传输的处理方法及装置

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
"Study on NR Industrial Internet of Things (IoT", RP-182090
3GPP TS38.331
HUAWEI ET AL.: "Discussion on PDCP duplication in L2 parameters", 3GPP TSG-RAN WG2 MEETING 102 R2-1808423, 25 May 2018 (2018-05-25), XP051444697, DOI: 20200225084923X *
See also references of EP3897014A4
ZTE: "Initial consideration on URLLC duplication enhancement", 3GPP TSG-RAN WG3 #101BIS R3-185577, 12 October 2018 (2018-10-12), XP051528853, DOI: 20200225084748X *

Also Published As

Publication number Publication date
CN111314906A (zh) 2020-06-19
EP3897014A4 (en) 2022-05-18
CA3123118A1 (en) 2020-06-18
IL283889A (en) 2021-07-29
US20220038950A1 (en) 2022-02-03
EP3897014A1 (en) 2021-10-20

Similar Documents

Publication Publication Date Title
WO2020119638A1 (zh) 用户设备及其方法、基站及其方法
US11324059B2 (en) Radio configuration method, user equipment, and base station
EP3606274B1 (en) Method executed in user equipment and base station and corresponding equipment
US11388626B2 (en) Base station, user equipment, and related method
US11758422B2 (en) User equipment and related method
CN110012454B (zh) 用户设备和相关方法
US11172537B2 (en) Wireless communication method and device
EP3637820B1 (en) Base station, user equipment and relevant methods
WO2020119640A1 (zh) 用户设备及其方法、基站及其方法
WO2020119632A1 (zh) 用户设备及其方法、基站及其方法
WO2021109933A1 (zh) 用户设备及其方法、基站及其方法
WO2021223623A1 (zh) 针对信令无线承载pdcp重复的配置方法及rrc实体
WO2020221155A1 (zh) 基站、用户设备和相关方法
WO2021185202A1 (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: 19895583

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 3123118

Country of ref document: CA

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019895583

Country of ref document: EP

Effective date: 20210712