method performed on base station and user equipment and corresponding devices

专利摘要:
the present disclosure provides a method performed on user equipment (eu) and a corresponding eu. the method comprises: receiving a control element (ce) to control access to media (mac) to indicate the activation and / or deactivation of packet duplication from a data radio carrier (drb); if packet duplication is configured and packet duplication is enabled, then provide, through a packet data convergence protocol entity (pdcp), a pdcp protocol data unit (pdu) for two control entities radio link (rlc); and if packet duplication is configured and packet duplication is disabled, then provide, by the pdcp entity, the pdcp pdu for one of the two rlc entities, with the mac ce comprising a bitmap that has a fixed size, each bit in the bitmap corresponds to a packet duplication drb identity arranged in an ascending order; and a bit set with the value "1" in the bitmap indicates the activation of the duplication of packets from the corresponding drb, and a bit set with the value "0" in the bitmap indicates the disabling of the duplication of packets from the corresponding drb. the present disclosure provides yet another method performed at the eu and the corresponding eu, as well as a method performed at a base station and a corresponding base station.
公开号:BR112019019535A2
申请号:R112019019535
申请日:2018-03-19
公开日:2020-04-22
发明作者:Xiao Fangying；Liu Renmao
申请人:Fg innovation co ltd；Sharp Kk；
IPC主号:

专利说明:

Invention Patent Descriptive Report for METHOD EXECUTED IN BASE STATION AND USER EQUIPMENT AND CORRESPONDING DEVICES.
FIELD OF TECHNIQUE [001] The present invention relates to the field of wireless communication technology. More specifically, the present disclosure relates to a method performed on user equipment (UE) and a corresponding UE, as well as a method performed on a base station (BS) and a corresponding base station. BACKGROUND [002] A new research item on 5G standards (see non - patent literature: RP 160 671: New SI D Proposal: Study on New Radio Access Technology) was proposed by NTT DOCOMO at the plenary session of the Partnership Project 3 Generation (3GPP) RAN # 71 in March 2016, and was approved. The objective of the research project is to develop a New Radio Access Technology (NR) to meet all 5G application scenarios, requirements and implementation environments. NR has mainly three application scenarios: enhanced mobile broadband communication (eMBB enhanced Mobile Broadband), massive machine type Communication (mMTC), ultra-reliable low latency communication (URLLC - Ultra-reliable and Low Latency Communication).
[003] At the RAN2 meeting # 96 of the 3GPP consortium held in October 2016, it was agreed that the survey will be carried out in a multi-connection (including double connection) in order to satisfy the URLLC reliability requirement. Multiconnection can adopt a mechanism such as packet duplication or link selection. At the ad hoc meeting on NR of the 3GPP consortium held in January 2017 it was agreed that an NR-PDCP entity (NR packet data protocol)
Petition 870190093832, of 9/19/2019, p. 10/192
2/59 supports a function of duplicating packets from a user plan and a control plan, with the function of a PDCP entity on a transmission side being to support the duplication of packets, whereas the function of a PDCP entity on one receiving side is to support packet deduplication, that is, the removal of duplicate packets. At the 3GPP RAN2 meeting # 97 held in February 2017, it was agreed that, for uplink and downlink support in carrier aggregation, packet duplication uses a packet data unit (PDU - Protocol Data Unit) and / or a service data unit (SDU - Service Data Unit) of Packet Data Convergence Protocol (PDCP) for transmission on multiple logical channels, and causes duplicate PDCP PDUs to be transmitted through different carriers.
[004] It is expected to solve problems related to a packet duplication carrier in multi-connection scenarios and in carrier aggregation scenarios that support packet duplication, including configuration and reconfiguration problems of a signaling radio carrier ( SRB - Signaling Radio Bearer), and enabling and disabling a packet duplication function from a PDCP entity, and how to perform processing when the UE receives duplicate PDCP PDUs from a packet duplication SRB.
SUMMARY [005] According to a first aspect of the present disclosure, a method performed on user equipment (UE) is presented. The method comprises: receiving a control element (CE Control Element) for access control to media (MAC - Medium Access Control) (MAC of MAC) to indicate the activation and / or deactivation of packet duplication from a radio carrier of data (DRB); if packet duplication is configured and the
Petition 870190093832, of 9/19/2019, p. 10/202
3/59 packet duplication is enabled, then provide, through a packet data convergence protocol entity (PDCP), a PDCP protocol data unit (PDU) for two radio link control entities (RLC - Radio Resource Control); and if packet duplication is configured and packet duplication is disabled, then provide, through the PDCP entity, the PDCP PDU for one of the two RLC entities. The MAC CE comprises a bitmap that has a fixed size, with each bit in the bitmap corresponding to a packet duplication DRB identity arranged in an ascending order. A bit set with a value of 1 in the bitmap indicates the activation of packet duplication of the corresponding DRB, and a bit set with a value of 0 in the bitmap indicates the deactivation of packet duplication of the corresponding DRB.
[006] In accordance with a second aspect of this disclosure, a UE is provided which comprises: a receiving unit, configured to receive a control element (CE) for media access control (MAC) to indicate activation and / or disabling packet duplication from a data radio carrier (DRB), and a sending unit, configured for: if packet duplication is configured and packet duplication is enabled, then provide, by a protocol entity packet data convergence (PDCP), a PDCP protocol data unit (PDU) for two radio link control entities (RLC); and if packet duplication is configured and packet duplication is disabled, then provide, through the PDCP entity, the PDCP PDU for one of the two RLC entities. The MAC CE comprises a bitmap that has a fixed size, with each bit in the bitmap corresponding to a packet duplication DRB identity arranged in an ascending order. A bit set with a value of 1 in the bitmap indicates the activation of packet duplication of the corresponding DRB, and a bit set with a value of 0 in the
Petition 870190093832, of 9/19/2019, p. 10/212
4/59 bitmap indicates that the corresponding DRB packet duplication has been disabled.
[007] In accordance with a third aspect of the present disclosure, a method performed by a base station is provided. The method comprises: transmitting a control element (CE) of media access control (MAC) to indicate to the user equipment (UE) the activation and / or deactivation of the duplication of packets from a data radio carrier (DRB) ). If packet duplication is configured and packet duplication is enabled, then a UE packet data convergence protocol (PDCP) entity provides a PDCP protocol data unit (PDU) for two link control entities radio (RLC). If packet duplication is configured and packet duplication is disabled, then the PDCP entity provides the PDCP PDU for one of the two RLC entities. The MAC CE comprises a bitmap that has a fixed size, with each bit in the bitmap corresponding to a packet duplication DRB identity arranged in an ascending order. A bit set with a value of 1 in the bitmap indicates the activation of packet duplication of the corresponding DRB, and a bit set with a value of 0 in the bitmap indicates the deactivation of packet duplication of the corresponding DRB.
[008] In accordance with a fourth aspect of this disclosure, a base station (BS) is provided which comprises: a transmission unit, configured to transmit a control element (CE) for access control to media (MAC) for indicate to the user equipment (UE) the activation and / or deactivation of packet duplication of a data radio carrier (DRB). If packet duplication is configured and packet duplication is enabled, then a UE packet data convergence protocol (PDCP) entity provides a PDCP protocol data unit (PDU) for two
Petition 870190093832, of 9/19/2019, p. 10/22
5/59 radio link control entities (RLC); and if packet duplication is set up and packet duplication is disabled, then the PDCP entity provides the PDCP PDU for one of the two RLC entities. The MAC CE comprises a bitmap that has a fixed size, with each bit in the bitmap corresponding to a packet duplication DRB identity arranged in an ascending order. A bit set with a value of 1 in the bitmap indicates the activation of packet duplication of the corresponding DRB, and a bit set with a value of 0 in the bitmap indicates the deactivation of packet duplication of the corresponding DRB.
[009] In accordance with a fifth aspect of the present disclosure, a method executed on a user equipment (UE) is provided which comprises: receiving from a lower layer a protocol data unit (PDU) of convergence protocol data packet data (PDCP); if the PDCP data PDU was previously received, then perform an integrity check on the PDCP data PDU; and if the integrity check fails, then indicate to a higher layer the integrity check failed.
[0010] In accordance with a sixth aspect of the present disclosure, a user equipment (UE) is provided comprising: a receiving unit configured to receive a protocol data unit (PDU) of protocol data from a lower layer packet data convergence (PDCP); a verification unit configured for: if the PDCP data PDU was previously received, then perform an integrity check on the PDCP data PDU; and an indication unit configured for: if the integrity check fails, then indicate the failure of the integrity check to a higher layer.
BRIEF DESCRIPTION OF THE DRAWINGS [0011] The above and other characteristics of the present disclosure are
Petition 870190093832, of 9/19/2019, p. 10/23
6/59 will become more evident with the detailed description below, together with the attached drawings.
[0012] Figure 1 is a schematic diagram that illustrates the data transmission of a split DRB of duplication of MCG packets (Master Cell Group, or group of main cells);
[0013] Figure 2 is a schematic diagram illustrating the transmission of data from a split DRB of duplication of SCG packets (Secondary Cell Group, or group of secondary cells);
[0014] Figure 3 is a schematic diagram of a protocol architecture in a user equipment (UE);
[0015] Figure 4 is a flow chart of a method 400 used in user equipment (UE) according to one embodiment of the present disclosure;
[0016] Figure 5 is a flow chart of a method 500 used in a user equipment (UE) according to an embodiment of the present disclosure;
[0017] Figure 6 is a flow chart of a method 600 used in a base station according to one embodiment of the present disclosure;
[0018] Figure 7 is a flow chart of a method 700 used in user equipment (UE) according to one embodiment of the present disclosure;
[0019] Figure 8 is a schematic diagram of a PDCP control PDU;
[0020] Figure 9 is a schematic diagram of the COUNT field (count);
[0021] Figure 10 is a schematic flowchart illustrating the processing of a PDCP PDU received by a PDCP entity;
[0022] Figure 11 is a schematic structural diagram of a UE 1100 according to an embodiment of the present disclosure;
Petition 870190093832, of 9/19/2019, p. 10/242
7/59 [0023] Figure 12 is a schematic structural diagram of a base station 1200 according to an embodiment of the present disclosure;
[0024] Figure 13 is a flowchart of a method 1300 performed on user equipment (UE) according to one embodiment of the present disclosure;
[0025] Figure 14 is a flow chart of a method 1400 executed in a base station (BS) according to one embodiment of the present disclosure;
[0026] Figure 15 is a flow chart of a method 1500 executed in a user equipment (UE) according to one embodiment of the present disclosure;
[0027] Figure 16 is a schematic structural diagram of a UE 1600 according to an embodiment of the present disclosure;
[0028] Figure 17 is a schematic structural diagram of a BS 1700 according to an embodiment of the present disclosure; and [0029] Figure 18 is a schematic structural diagram of an UE 1800 according to an embodiment of the present disclosure.
DETAILED DESCRIPTION [0030] The following text describes the present invention in detail with reference to the attached drawings and specific modalities. It should be noted that the present invention is not limited to the specific modalities described below. In addition, for the sake of simplicity, a detailed description of the known technique not directly related to the present invention is omitted to avoid confusion in the understanding of the present description.
[0031] Some terms involved in this disclosure are described below. Unless specifically indicated, the terms involved in this disclosure use the definitions set forth herein. The terms used in this disclosure may have
Petition 870190093832, of 9/19/2019, p. 10/252
8/59 different names in the New Radio (NR - New Radio), Long Term Evolution (LTE - Long Term Evolution), and improved Long Term Evolution (eLTE - enhanced LTE) technologies, but here unified terms are used. When applied to a specific system, terms can be replaced by terms used in the corresponding system.
[0032] RRC: Radio Resource Control (from Radio Resource Control).
[0033] PDCP: Packet Data Convergence Protocol. In the present disclosure, if not specifically indicated, the PDCP can represent a PDCP in NR, LTE or eLTE.
[0034] RLC: Radio Link Control (from Radio Link Control). In the present disclosure, if not specifically indicated, the RLC may represent an RLC in NR, LTE or eLTE.
[0035] MAC: Media Access Control (from Medium Access Control). In the present disclosure, if not specifically indicated, the MAC can represent a MAC in NR, LTE or eLTE.
[0036] DTCH: dedicated traffic channel (from Dedicated Traffic Channel).
[0037] CCCH: Common Control Channel (Common Control Channel).
[0038] DCCH: Dedicated Control Channel (from Dedicated Control Channel).
[0039] PDU: Protocol Data Unit.
[0040] SDU: Service Data Unit (from Service Data Unit). [0041] In the present disclosure, data received from, or supplied to, a higher layer is called an SDU, and data provided to, or received from, a lower layer is
Petition 870190093832, of 9/19/2019, p. 10/26
9/59 calls from a PDU. For example, data received from or supplied to a higher layer by a PDCP entity is referred to as a PDCP SDU; and data received from or provided to an RLC entity by the PDCP entity is referred to as a PDCP PDU (i.e., an RLC SDU).
[0042] Main base station: main eNB, represented as MeNB (a base station corresponding to E-UTRAN or LTE or eLTE), or as MgNB (a base station corresponding to 5G-RAN radio access network of 5 ^the generation - or NR). The main base station is a base station that at least ends at a mobility management entity (represented as S1-MME) as a control node to process the interaction between a UE and a main network in the multi-connection. In the present disclosure, the main base stations are all represented as MeNBs. It should be noted that all schemes or definitions applicable to MeNB are also applicable to MgNB.
[0043] Secondary base station: secondary eNB, represented as SeNB (a base station corresponding to E-UTRAN or LTE or eLTE), or SgNB (a base station corresponding to 5G-RAN or NR). The secondary base station is a base station that provides additional radio resources to the UE, but does not serve as a MeNB on the multi-connection. In the present disclosure, the secondary base stations are all represented as SeNBs. It should be noted that all regimes or definitions applicable to SeNB are also applicable to SgNB.
[0044] Primary cell: PCell (from Primary Cell). The PCell is a cell that operates on the primary frequency, and is a cell in which the UE performs an initial connection establishment procedure or initiates a reconnection procedure, or a cell that is designated as a primary cell during a connection procedure. - handover - transfer between cells.
Petition 870190093832, of 9/19/2019, p. 10/272
10/59 [0045] Primary secondary cell: PSCell (from Primary Secundary Cell). PSCell is an SCG cell in which the UE is instructed to perform random access while performing the SCG switching, or switching, process.
[0046] Secondary cell: SCell (from Secondary Cell). SCell is a cell that operates on the secondary frequency. The cell can be configured as soon as the RRC connection is established and can be used to provide additional radio capabilities.
[0047] Cell group: CG (from Cell Group). The GC is a group of server or carrier cells associated with a main base station or a secondary base station. It should be noted that the cell in the present disclosure can also be called a bundle of bundles.
[0048] Main cell group: MCG (from Master Cell Group). For an UE not configured with multi-connection, the MCG comprises all server cells; for a UE configured with multi-connection, the MCG comprises a subset of server cells (ie, a group of server cells associated with a MeNB or MgNB) comprising a primary cell - PCell - and 0, 1 or more secondary cells - SCells.
[0049] Secondary cell group: SCG (from Secondary Cell Group). The SCG is a group of server cells associated with a SeNB or SgNB in the multiconnection. The SCG can include a PSCell, and can additionally include one or more SCells.
[0050] Multiconnection: a mode of operation of UE in a connected state of RRC. In multiconnection, multiple groups of cells are configured, and the multiple groups of cells include an MCG and one or more SCGs (ie, the UE is connected to multiple base stations). If only one MCG (or MeNB or MgNB) and one SCG (or SeNB or SgNB) are configured, then the multi-connection is
Petition 870190093832, of 9/19/2019, p. 10/282
11/59 double connection call. Specifically, the UE in the connected state and having multiple receivers and / or transmitters is configured to use EUTRAN and / or 5G-RAN radio resources provided by multiple different schedulers; schedulers can be connected by non-ideal backhaul or ideal backhaul. The multi-connection in the present disclosure includes the double connection. A multi-connection data transmission mode includes, but is not limited to, data duplication and link selection.
[0051] DRB: radio data carrier that carries user plan data, also called data carrier for short.
[0052] SRB: signaling radio carrier (from Signaling Radio Bearer). The carrier can be used to transmit a RRC message and a Non-Access Stratum message (NAS), or to transmit only an RRC message or a NAS message. SRB can include types SRBO, SRB1, SRB1 bis and SRB2. SRBO is used for an RRC message that uses a CCCH logical channel; SRB1 is used for an RRC message that uses a logical DCCH channel, the RRC message can include a NAS message; SRB1 is additionally used to transmit a NAS message before SRB2 is established. SRBIbis is used for an RRC message and a NAS message that use a logical DCCH channel before secure activation, the RRC message can include a NAS message. SRB2 is used for an RRC message and a NAS message using a logical DCCH channel, the RRC message includes recorded measurement information (also known as a measurement record).
[0053] The carrier in the present disclosure can be a DRB or an SRB.
Petition 870190093832, of 9/19/2019, p. 10/29
12/59 [0054] Split DRB: a carrier whose wireless protocol is located in both MeNB (or MgNB) and SeNB (or SgNB), and which uses resources from both MeNB (or MgNB) and SeNB (or SgNB ) on the multi-connection. If a split DRB PDCP entity is located on a main base station (that is, the data arrives first at the main base station and is sent by the main base station to a secondary base station to divide the data at the main base), then the split DRB is called a split MCB DRB; if a split DRB PDCP entity is located on a secondary base station (that is, the data first arrives at the secondary base station and is sent by the secondary base station to a primary base station to split the data at the secondary base), then the split DRB is called a SCG split DRB. If not specifically indicated, the split DRB in the present disclosure can be an MCG split DRB or an SCG split DRB.
[0055] Split SRB: a carrier whose wireless connection protocol is located in a MeNB (or MgNB) and a SeNB (or SgNB), and which uses resources from both MeNB (or MgNB) and SeNB (or SgNB) multi-connection. If a PDCP entity and / or a split SRB RRC are located on a main base station (ie, signaling, also called data, is sent by the main base station to a secondary base station to share the signaling on the main base station), then the split SRB is called a split MCB SRB; if a PDCP entity and / or a split SRB RRC are located on a secondary base station (ie, signaling, also called data, is sent by the secondary base station to a primary base station to share the signaling on the secondary base station), then the split SRB is called an SCG split SRB. If not specifically indicated, the SRB divided into
Petition 870190093832, of 9/19/2019, p. 10/30
13/59 the present disclosure can be an MCG split SRB or a SCG split SRB.
[0056] In the present disclosure, the split carrier can be a split SRB or a split DRB. A split MCG carrier can be a split MCG SRB or a split MCG DRB. A SCG split carrier can be a SCG split SRB or a SCG split DRB.
[0057] Duplication of packets: also called duplication of data (unless specifically indicated, the data in this disclosure may be signaling the control plane or user plane data, which correspond, respectively, to the signaling of an SRB and DRB data). In a multi-connection mode, the same data (also referred to as a packet, that is, a PDCP PDU or PDCP SDU) is transmitted in the server cells of multiple cell groups (CGs); that is, the same data is transmitted using resources provided by both a primary base station (or an MCG) and a secondary base station (or an SCG); or the same data is provided respectively for lower layers (or layers of RLC) located in the MCG and SCG; or a PDCP entity provides the same PDCP PDU for multiple associated lower tier entities (or RLC entities); or the same data is transmitted on multiple different carriers. In a carrier aggregation or single connection mode, a PDCP entity provides duplicate PDCP PDUs or the same PDCP PDUs for multiple RLC entities (also referred to as lower layer entities) and / or logical channels, an entity MAC transmits the PDCP PDUs to a receiving side through different carriers (or server cells), and a PDCP entity on the receiving side is responsible for detecting and deduplicating the PDCP PDUs or SDUs.
Petition 870190093832, of 9/19/2019, p. 10/312
14/59 [0058] Packet duplication carrier: a carrier that supports packet duplication in a carrier aggregation or single connection mode, including a packet duplication SRB and a packet duplication DRB. A carrier's PDCP entity is associated with one or more RLC entities, multiple logical channels and one or more MAC entities; a PDCP entity on a transmission side provides duplicate PDCP PDUs or the same PDCP PDUs to one or more RLC entities (or lower layer entities) and / or multiple logical channels, and a MAC entity transmits the PDCP PDUs for a receiving side through different carriers (or server cells); and a PDCP entity on the receiving side deduplicates the PDCP PDUs or SDUs from the lower tier entities.
[0059] Split packet carrier: a split carrier that supports packet duplication in a multi-connection mode. In transmission mode, the same data is transmitted over multiple wireless carrier split protocols, including an MCG packet split SRB, an SCG packet split SRB, an MCG packet split DRB and a split DRB for duplicating SCG packets. In the case of a split carrier for duplicating MCG packets, a PDCP entity located at a main base station or MCG is responsible for packet duplication and / or packet deduplication; in the case of a split carrier for duplicating SCG packets, a PDCP entity located at a secondary base station or SCG is responsible for packet duplication and / or packet deduplication.
[0060] PDCP configuration information element, pdcpConfig: includes PDCP parameters configurable from a DRB.
Petition 870190093832, of 9/19/2019, p. 10/32
15/59 [0061] RLC configuration information element, rlcConfig: includes configuration information for an RLC entity corresponding to an SRB and a DRB.
[0062] Logical channel identity information element, logicalChannelldentity: identity of a logical channel.
[0063] Logical channel configuration information element, logicalChannelConfig: includes parameters used to configure a logical channel.
[0064] Logical channel group information element, logicalChannelConfig: identity of a group of logical channels that is used to map a logical channel to a group of logical channels for issuing buffer status reports (BSR - Buffer Status Reports) .
[0065] Figure 1 is a schematic diagram showing the downlink transmission of a split MCB packet duplication DRB between a base station and a user equipment (UE). It should be understood that the DRB uplink transmission of duplicated MCG packet duplication between the base station and the UE can adopt the same protocol architecture, except that the data is transmitted from the UE to the base station , that is, the arrows in Figure 1 are inverted. As shown in Figure 1, the data (for example, a packet data convergence protocol (PDCP PDU) protocol data unit) is transmitted over multiple wireless protocols (corresponding to multiple RLC entities associated with the same PDCP entity) of the DRB divided using the resources of a MeNB and a SeNB. In a multi-connection mode of PDCP PDU data duplication, each PDCP PDU is transmitted to a receiving part through multiple RLC entities. An interface between MeNB and SeNB can be represented as Xn or Xx or X2. The interface can receive other
Petition 870190093832, of 9/19/2019, p. 10/332
16/59 names, according to different types of MeNB and SeNB. For example, the interface is represented as Xx if MeNB is an eNB LTE and SeNB is a gNB; or the interface is represented as Xn if MeNB is a gNB and SeNB is an eNB eLTE. Consequently, a split MCB packet duplication SRB adopts a similar protocol architecture, and the difference lies in the fact that a higher layer entity providing data to a PDCP entity is an RRC entity, and the PDCP entity receives data from a lower tier entity and then provides the data to the RRC entity at the higher tier.
[0066] Figure 2 is a schematic diagram illustrating the downlink transmission of a split DRB for duplicating SCG packets between a base station and a user equipment (UE). It should be understood that the DRB uplink transmission of duplicate SCG packet duplication between the base station and the UE can adopt the same protocol architecture, except that the data is transmitted from the UE to the base station , that is, the arrows in Figure 2 are inverted. As shown in Figure 2, the data (for example, a packet data convergence protocol (PDCP PDU) protocol data unit) is transmitted over multiple wireless protocols (which correspond to multiple RLC entities associated with the same PDCP entity) of a DRB divided using the resources of a MeNB and a SeNB. In a multi-connection mode of PDCP PDU data duplication, each PDCP PDU is transmitted to a receiving part through multiple RLC entities. An interface between MeNB and SeNB can be represented as Xn or Xx or X2. The interface can be given other names, according to different types of MeNB and SeNB. For example, the interface is represented as Xx if MeNB is an eNB LTE and SeNB is a gNB; or the interface is represented as Xn if the
Petition 870190093832, of 9/19/2019, p. 10/34
17/59
MeNB is a gNB and SeNB is an eNB eLTE. Consequently, a split SRB of SCG packet duplication adopts a similar protocol architecture, and the difference lies in the fact that a higher layer entity providing data to a PDCP entity is an RRC entity, and the PDCP entity receives data from a lower tier entity and then provides the data to the RRC entity at the higher tier.
[0067] Some embodiments of the present disclosure use the technique of repeatedly transmitting a PDU or PDU of a data packet PDCP twice as an example (i.e., a PDCP entity is associated with two RLC entities and / or two logical channels ). However, the technical solution in the present disclosure is not limited to the scenarios of repeatedly transmitting a data packet PDCP PDU or SDU twice, and those skilled in the art can easily expand that technical solution to scenarios of repeatedly transmitting a data packet. often (ie, a PDCP entity is associated with multiple RLC entities and / or multiple logical channels).
[0068] Figure 3 is a schematic diagram of a protocol architecture on user equipment (UE) in a carrier aggregation scenario. In the schematic diagram shown in Figure 3 (a), a PDB entity of a DRB is associated with two RLC entities and two logical channels, and a MAC entity. In the schematic diagram shown in Figure 3 (b), a PDB entity of a DRB is associated with two RLC entities and two logical channels, and two MAC entities. In the schematic diagram shown in Figure 3 (c), an RRC entity and a PDCP entity of an SRB are associated with two RLC entities and two logical channels, and a MAC entity. In the schematic diagram shown in Figure 3 (d), an RRC entity and a PDCP entity of an SRB are
Petition 870190093832, of 9/19/2019, p. 10/35
18/59 associated with two RLC entities and two logical channels, and two MAC entities.
[0069] Unless specifically indicated, the activation of a packet duplication function (which may also be called a PDCP packet duplication function or a carrier packet duplication function) in the present disclosure may also be expressed such as configuring a PDCP entity to provide the same PDCP PDU to multiple lower tier entities or associated RLC entities. In the case of an MCG packet split SRB or an SCG packet split SRB, the packet duplication function is activated so that the same PDCP PDU is transmitted through an MCG and an SCG. Disabling a packet duplication function can also be expressed as configuring a PDCP entity to provide the same PDCP PDU for one of the multiple lower layer entities (or RLC entities) associated with it; or all PDCP PDUs are transmitted only through one of the multiple lower layer entities. For example, when an instruction to disable a PDCP packet duplication function from a higher layer or a MAC layer or a lower layer is received, a PDCP PDU is transmitted only through an RLC associated with a logical channel that has a predefined logical channel identity or through an RLC entity associated with a logical channel that has a smaller logical channel identity or the smaller logical channel identity or a larger logical channel identity or greater logical channel identity. In the case of a split MCG packet duplication SRB, the PDCP packet duplication function is disabled so that a PDCP PDU is transmitted only via an MCG or SCG, or the PDCP packet duplication function is deactivated so that a
Petition 870190093832, of 9/19/2019, p. 36/102
19/59
PDCP is transmitted only through the MCG, or the PDCP packet duplication function is disabled so that a PDCP PDU is transmitted only through the SCG; in the case of a split SCG packet duplication SRB, the PDCP packet duplication function is disabled so that a PDCP PDU is transmitted only through an SCG or MCG, or the PDCP packet duplication function it is disabled so that a PDCP PDU is transmitted only through the MCG, or the PDCP packet duplication function is disabled so that a PDCP PDU is transmitted only through the SCG.
[0070] Figure 4 is a flow chart of a method 400 used in user equipment (UE) according to one embodiment of the present disclosure. Method 400 is used to establish a packet duplication SRB.
[0071] As shown in the figure, in step S410, the UE receives, from a base station, an indication to indicate whether a corresponding signaling radio carrier (SRB) supports packet duplication, and configuration information from an SRB that supports duplication of packages.
[0072] In an implementation, if the SRB identity (represented as srb-ldentity) of a packet duplication SRB is the same as that of a corresponding SRB that does not support packet duplication, then method 400 will additionally include: receive from the base station (not shown) the SRB identity of the corresponding packet duplication SRB.
[0073] In another implementation, if the packet duplication SRB has a different SRB identity than a corresponding SRB that does not support packet duplication, then the indication will be the SRB identity of the packet duplication SRB. In other words, as the packet duplication SRB has a
Petition 870190093832, of 9/19/2019, p. 37/102
20/59 SRB identity that is different from that of the corresponding SRB that does not support packet duplication, upon receiving an SRB identity, the UE can determine whether the corresponding SRB supports packet duplication.
[0074] In step S420, the UE establishes the corresponding packet duplication SRB according to the configuration information received.
[0075] The following text describes modalities for establishing a packet duplication SRB by user equipment in a carrier aggregation scenario (CA - Carrier Aggregation), and the modalities are equally applicable to the establishment of a split duplication SRB of packages.
Mode 1 [0076] A packet duplication SRB uses the same SRB identity as a corresponding SRB that does not support packet duplication (the SRB and the packet duplication SRB transmit the same data and implement the same quality of service (QoS), and the difference is in the fact that one supports the packet duplication function, while the other does not); then, two logical channel identities are predefined for the packet duplication SRB, one logical channel identity is the same as the SRB which does not support packet duplication. For example, an SRB1 that supports packet duplication and an SRB1 that does not support packet duplication are both called SRB1. In that case, an indication is used in the RRC signaling to indicate whether a packet duplication SRB should be established or an SRB that does not support packet duplication. Specifically, the following steps are included:
[0077] Step 1: The user equipment receives RRC signaling (for example, a connection reconfiguration message from
Petition 870190093832, of 9/19/2019, p. 38/102
21/59
RRC) of a base station, the RRC signaling may include an indication to indicate whether a corresponding SRB is a packet duplication SRB or an SRB that supports packet duplication, or whether the corresponding PDCP entity supports the repeated transmission of a PDCP PDU twice or more, or if the corresponding PDCP entity supports the packet duplication function. For example, when the indication has a value of 1 or TRUE (true) or Setup (configure) or when the indication appears, it indicates that the corresponding SRB is a packet duplication SRB or an SRB that supports the duplication function. packets, or that the PDB entity corresponding to the SRB supports the repeated transmission of each PDCP PDU twice or more, or that the corresponding PDCP entity supports the packet duplication function; when the indication has a value of 0 or FALSE (false) or Release (release) or when the indication does not appear, it indicates that the corresponding SRB is not a packet duplication SRB or is an SRB that does not support the duplication function packets, or that the corresponding PDCP entity does not repeatedly transmit a PDCP PDU, or that the corresponding PDCP entity does not support the packet duplication function, or that the corresponding PDCP entity provides a PDCP PDU for one of the multiple lower tier entities (or RLC entities) associated. RRC signaling additionally includes configuration information from an SRB that supports packet duplication.
[0078] Step 2: The user equipment establishes the corresponding packet duplication SRB according to the configuration information of the packet duplication SRB included in the received RRC signaling. The following operations (operations are interchangeable in terms of order) may be specifically included:
Petition 870190093832, of 9/19/2019, p. 39/102
22/59 [0079] - Optionally, apply a predefined configuration of the corresponding packet duplication SRB. In the case of a split packet duplication SRB, predefined settings in a MeNB or MCG and in a SeNB or SCG are used respectively.
[0080] - Establish a PDCP entity, and if the PDCP entity requires a security configuration, then the PDCP entity will be configured according to an MCG security configuration. If the PDCP entity or SCG packet duplication SRB or SCG packet split SRB is established in an SCG, then the PDCP entity will be configured according to an SCG security configuration. Optionally, the operation additionally includes configuring the PDCP entity to activate the packet duplication function, or configuring the PDCP entity to disable the packet duplication function.
[0081] - Establish one or two RLC entities according to the RLC configuration information element, rlc-Config, included in the RRC signaling, and the two RLC entities can employ the same or different configurations. If different configurations are used, then the corresponding packet duplication SRB in the RRC signaling will include two elements of information rlc-Config.
[0082] - Establish two logical DCCH channels according to the logical channel configuration information element, logicalChannelConfig, included in the RRC signaling, and the logical channel identities of the logical channels are respectively defined with two predefined values corresponding to the Packet duplication SRB. In the case of a split packet duplication SRB, predefined settings in a MeNB or MCG and in a SeNB or SCG are used respectively.
Petition 870190093832, of 9/19/2019, p. 40/102
23/59
Mode 2 [0083] A packet duplication SRB uses the same SRB identity (srb-ldentity) as a corresponding SRB that does not support packet duplication (the SRB and the packet duplication SRB transmit the same data and implement the same QoS function, and the difference is that one supports the packet duplication function, while the other does not), and a packet duplication SRB logical channel identity is a predefined logical channel identity (represented as LCH_ID) of the corresponding SRB that does not support packet duplication, and the other logical channel identity of the packet duplication SRB is the default logical channel identity plus an offset. Preferably, the offset is a maximum configurable logical channel identity, and it is represented as MAX_LCH_ID. Specifically, the following steps are included:
[0084] Step 1: The user equipment receives RRC signaling (for example, an RRC connection reconfiguration message) from a base station, the RRC signaling may include an indication to indicate whether a corresponding SRB is a packet duplication SRB or an SRB that supports packet duplication, or if the corresponding PDCP entity supports the repeated transmission of a PDCP PDU twice or more, or if the corresponding PDCP entity supports the duplication function packages. For example, when the indication has a value of 1 or TRUE (true) or Setup (configure) or when the indication appears, it indicates that the corresponding SRB is a packet duplication SRB or an SRB that supports the duplication function. packets, or that the PDB entity corresponding to the SRB supports the repeated transmission of each PDCP PDU twice or more, or that the corresponding PDCP entity supports the
Petition 870190093832, of 9/19/2019, p. 41/102
24/59 duplication of packages; when the indication has a value of 0 or FALSE (false) or Release (release) or when the indication does not appear, it indicates that the corresponding SRB is not a packet duplication SRB or is an SRB that does not support the duplication function packets, or that the corresponding PDCP entity does not support the repeated transmission of a PDCP PDU, or that the corresponding PDCP entity does not support the packet duplication function. RRC signaling additionally includes configuration information from an SRB that supports packet duplication.
[0085] Step 2: The user equipment establishes the corresponding packet duplication SRB according to the configuration information of the packet duplication SRB included in the received RRC signaling. The following operations (operations are interchangeable in terms of order) may be specifically included:
[0086] - Optionally, apply a predefined configuration of
Corresponding packet duplication SRB.
[0087] - Establish a PDCP entity, and if the PDCP entity requires a security configuration, then the PDCP entity will be configured according to an MCG security configuration. If the PDCP entity or SCG packet duplication SRB or SCG packet split SRB is established in an SCG, then the PDCP entity will be configured according to an SCG security configuration. Optionally, the operation additionally includes configuring the PDCP entity to activate the packet duplication function, or configuring the PDCP entity to disable the packet duplication function.
[0088] - Establish one or two RLC entities according to the RLC configuration information element, rlc-Config,
Petition 870190093832, of 9/19/2019, p. 42/102
25/59 included in the RRC signaling, and the two RLC entities can use the same or different configurations. If different configurations are used, then the corresponding packet duplication SRB in the RRC signaling will include two elements of information rlc-Config.
[0089] - Establish two DCCH logical channels according to the logical channel configuration information element, logicalChannelConfig, included in the RRC signaling. A logical channel identity of a logical channel is defined with a default value LCHJD, and a logical channel identity of the other logical channel is defined with the value LCHJD + offset. Preferably, the logical channel identity of the other logical channel is LCHJD + MAX_LCHJD. If a third logical channel also needs to be established, then a corresponding logical channel identity can be defined with the value LCH + 2 (offset), and so on. That is, the logical channel identities of other logical channels are LCHJD plus a multiple of the offset.
Mode 3 [0090] A packet duplication SRB uses the same SRB identity (srb-ldentity) as a corresponding SRB that does not support packet duplication (the SRB and the packet duplication SRB transmit the same data and implement the same QoS function, and the difference is that one supports the packet duplication function, while the other does not), and a packet duplication SRB logical channel identity is a predefined logical channel identity (represented as LCHJD) of the corresponding SRB that does not support packet duplication, and the other packet duplication SRB logical channel identity is included in the RRC signaling to configure the packet duplication SRB.
Petition 870190093832, of 9/19/2019, p. 43/102
26/59 [0091] Step 1: The user equipment receives RRC signaling (for example, an RRC connection reconfiguration message) from a base station, the RRC signaling may include an indication to indicate whether a Corresponding SRB is a packet duplication SRB or an SRB that supports packet duplication, or if the corresponding PDCP entity supports the repeated transmission of a PDCP PDU twice or more, or if the corresponding PDCP entity supports the function duplication of packages. For example, when the indication has a value of 1 or TRUE (true) or Setup (configure) or when the indication appears, it indicates that the corresponding SRB is a packet duplication SRB or an SRB that supports the duplication function. packets, or that the PDB entity corresponding to the SRB supports the repeated transmission of each PDCP PDU twice or more, or that the corresponding PDCP entity supports the packet duplication function; when the indication has a value of 0 or FALSE (false) or Release (release) or when the indication does not appear, it indicates that the corresponding SRB is not a packet duplication SRB or is an SRB that does not support the duplication function packets, or that the corresponding PDCP entity does not support the repeated transmission of a PDCP PDU, or that the corresponding PDCP entity does not support the packet duplication function. RRC signaling additionally includes configuration information from an SRB that supports packet duplication.
[0092] Step 2: The user equipment establishes the corresponding packet duplication SRB according to the configuration information of the packet duplication SRB included in the received RRC signaling. The following operations (operations are interchangeable in terms of order) may be specifically included:
Petition 870190093832, of 9/19/2019, p. 44/102
27/59 [0093] - Optionally, apply a predefined configuration of the
Corresponding packet duplication SRB.
[0094] - Establish a PDCP entity, and if the PDCP entity requires a security configuration, then the PDCP entity will be configured according to an MCG security configuration. If the PDCP entity or SCG packet duplication SRB or SCG packet split SRB is established in an SCG, then the PDCP entity will be configured according to an SCG security configuration. Optionally, the operation additionally includes configuring the PDCP entity to activate the packet duplication function, or configuring the PDCP entity to disable the packet duplication function.
[0095] - Establish one or two RLC entities according to the RLC configuration information element, rlc-Config, included in the RRC signaling, and the two RLC entities can employ the same or different configurations. If different configurations are used, then the corresponding packet duplication SRB in the RRC signaling will include two elements of information rlc-Config.
[0096] - Establish two logical DCCH channels according to the logical channel configuration information element, logicalChannelConfig, included in the RRC signaling, and a logical channel identity of a logical channel is defined with a predefined value, and a logical channel identity of the other logical channel is defined with a corresponding value carried in the RRC signaling.
Mode 4 [0097] A packet duplication SRB uses an SRB identity (srb-ldentity) different from that of a corresponding SRB that does not support packet duplication (the SRB and the duplication SRB
Petition 870190093832, of 9/19/2019, p. 45/102
28/59 packets transmit the same data and implement the same QoS function, and the difference is in the fact that one supports the packet duplication function, while the other does not), the SRB identity is predefined, and one user can determine to establish the packet duplication SRB according to the SRB identity. Two logical channel identities are predefined for the packet duplication SRB corresponding to the SRB identity. The two logical channel identities can be different from an SRB logical channel identity that does not support packet duplication, or one of the logical channel identities is the same as the SRB logical channel identity that does not support packet duplication (in that case case, one logical channel identity can be predefined for the packet duplication SRB, and the other logical channel identity is a predefined logical channel identity of the corresponding SRB that does not support packet duplication). Specifically, the following steps are included: [0098] Step 1: The user equipment receives RRC signaling (for example, an RRC connection reconfiguration message) from a base station, the RRC signaling includes an identity of a packet duplication SRB to be established and additionally includes configuration information from the SRB that supports packet duplication.
[0099] Step 2: The user equipment establishes the corresponding packet duplication SRB according to the identity of the packet duplication SRB and the corresponding configuration information that is included in the received RRC signaling. The following operations (operations are interchangeable in terms of order) may be specifically included:
[00100] - Optionally, apply a predefined SRB configuration for duplicating packets corresponding to the SRB identity.
[00101] - Establish a PDCP entity, and if the
Petition 870190093832, of 9/19/2019, p. 46/102
29/59 PDCP entity requires a security configuration, then the PDCP entity will be configured according to an MCG security configuration. If the PDCP entity or SCG packet duplication SRB or SCG packet split SRB is established in an SCG, then the PDCP entity will be configured according to an SCG security configuration. Optionally, the operation additionally includes configuring the PDCP entity to activate the packet duplication function, or configuring the PDCP entity to disable the packet duplication function.
[00102] - Establish one or two RLC entities according to the RLC configuration information element, rlc-Config, included in the RRC signaling, and the two RLC entities can employ the same or different configurations. If different configurations are used, then the corresponding packet duplication SRB in the RRC signaling will include two elements of information rlc-Config.
[00103] - Establish two logical DCCH channels according to the logical channel configuration information element, logicalChannelConfig, included in the RRC signaling, and the logical channel identities of the logical channels are respectively defined with two predefined values corresponding to the Packet duplication SRB.
Mode 5 [00104] A packet duplication SRB uses a different SRB (srb-ldentity) identity than a corresponding SRB that does not support packet duplication (the SRB and the packet duplication SRB transmit the same data and implement the same QoS function, and the difference is that one supports the packet duplication function, while the other does not), the SRB identity is predefined, and a user can determine to establish the SRB
Petition 870190093832, of 9/19/2019, p. 47/102
30/59 duplication of packages according to the identity of the SRB. A logical channel identity (represented as LCH_ID) is predefined for the packet duplication SRB corresponding to the SRB identity. The logical channel identity is different from a predefined logical channel identity of the corresponding SRB that does not support packet duplication, or the logical channel identity is the same as the SRB default logical channel identity that does not support packet duplication . The other logical channel identity is the default logical channel identity plus an offset (represented as an offset). Preferably, the offset is a maximum configurable logical channel identity, and it is represented as MAX_LCH_ID. Specifically, the following steps are included: [00105] Step 1: The user equipment receives RRC signaling (for example, an RRC connection reconfiguration message) from a base station, the RRC signaling includes an identity of a packet duplication SRB to be established and additionally includes configuration information from the SRB that supports packet duplication.
[00106] Step 2: The user equipment establishes the corresponding packet duplication SRB according to the identity of the packet duplication SRB and the configuration information of the packet duplication SRB that are included in the received RRC signaling. The following operations (operations are interchangeable in terms of order) may be specifically included:
[00107] - Optionally, apply a predefined configuration of
Duplicate packet SRB corresponding to the SRB identity.
[00108] - Establish a PDCP entity, and if the PDCP entity requires a security configuration, then the PDCP entity will be configured according to an MCG security configuration. If the PDCP entity or an SRB of
Petition 870190093832, of 9/19/2019, p. 48/102
31/59 SCG packet duplication or a split SCG packet duplication SRB is established in an SCG, then the PDCP entity will be configured according to an SCG security configuration. Optionally, the operation additionally includes configuring the PDCP entity to activate the packet duplication function, or configuring the PDCP entity to disable the packet duplication function.
[00109] - Establish one or two RLC entities according to the RLC configuration information element, rlc-Config, included in the RRC signaling, and the two RLC entities can employ the same or different configurations. If different configurations are used, then the corresponding packet duplication SRB in the RRC signaling will include two elements of information rlc-Config.
[00110] - Establish two DCCH logical channels according to the logical channel configuration information element, logicalChannelConfig, included in the RRC signaling. A logical channel identity of a logical channel is defined with a default value LCHJD, and a logical channel identity of the other logical channel is defined with the value LCHJD + offset. Preferably, the logical channel identity of the other logical channel is LCHJD + MAX_LCHJD. If a third logical channel also needs to be established, then a corresponding logical channel identity can be defined with the value LCH + 2 (offset), and so on. That is, the logical channel identities of other logical channels are LCHJD plus a multiple of the offset.
[00111] Figure 5 is a flow chart of a method 500 used in a user equipment (UE) according to one embodiment of the present disclosure. Method 500 is used for reconfiguration if an SRB supports packet duplication.
[00112] As shown in the figure, in step S510, the UE receives,
Petition 870190093832, of 9/19/2019, p. 49/102
32/59 of a base station, an indication to indicate whether a reconfigured radio signaling (SRB) carrier supports packet duplication.
[00113] Step S520: If the configured SRB does not support packet duplication and the indication indicates that the reconfigured SRB supports packet duplication, then the UE reconfigures the configured SRB as supporting packet duplication.
[00114] In an implementation, method 500 additionally includes: if the configured SRB supports packet duplication and the indication indicates that the reconfigured SRB does not support packet duplication, then the UE reconfigures the configured SRB as not supporting duplication of packets packages (not shown).
[00115] The following text describes ways to reconfigure an SRB for duplicating packages by user equipment in a carrier aggregation (CA) scenario.
Mode 1 [00116] In this mode, a packet duplication SRB uses the same SRB identity as that of a corresponding SRB that does not support packet duplication (the SRB and the packet duplication SRB transmit the same data and implement the same QoS function, and the difference lies in the fact that one supports the packet duplication function, while the other does not).
[00117] Specifically, in step 1: the user equipment receives an RRC message from a base station, the message being an RRC reconfiguration message that can be used for a transfer scenario (the RRC message includes a mobility control information element, mobilityControilnfo, to indicate a transfer) or a non-transfer scenario (the RRC message does not include a mobilityControilnfo information element to indicate a transfer). The RRC message
Petition 870190093832, of 9/19/2019, p. 50/102
33/59 includes an indication (represented as fullConfig) to indicate the application of the complete configuration to the RRC reconfiguration message. The RRC message additionally includes an SRB identity that requires reconfiguration, for example, an SRB identity that requires reconfiguration included in an srbToAddModList information element. An indication can also be associated with the SRB that requires reconfiguration. The indication is used to indicate that the reconfigured SRB is a packet duplication SRB, or that a corresponding PDCP entity supports the repeated transmission of a PDCP PDU twice or more, or that the corresponding PDCP entity supports the duplication of packages. That is, the user equipment reconfigures a configured SRB (also called an existing or current SRB, which is an SRB already configured before the UE receives the RRC message) corresponding to the SRB identity as a packet duplication SRB. The configured SRB can be a packet duplication SRB or an SRB that does not support packet duplication. For example, when the indication has a value of 1 or TRUE (true) or Setup (configure) or when the indication appears, it indicates that the corresponding SRB is a packet duplication SRB or an SRB that supports the duplication function. packets, or that the PDB entity corresponding to the SRB supports the repeated transmission of each PDCP PDU twice or more, or that the PDCP entity supports the packet duplication function; when the indication has a value of 0 or FALSE (false) or Release (release) or when the indication does not appear, it indicates that the corresponding SRB is not a packet duplication SRB or is an SRB that does not support the duplication function packets, or that the corresponding PDCP entity does not support the packet duplication function.
[00118] Step 2: For an SRB corresponding to the SRB identity included in the RRC message: if the configured SRB is a
Petition 870190093832, of 9/19/2019, p. 51/102
34/59
SRB that does not support packet duplication, that is, an SRB that does not support packet duplication must be reconfigured as an SRB that supports packet duplication, so the following operations must be performed (operations can be performed in different sequences ):
[00119] - Apply a predefined configuration to a packet duplication SRB (optional).
[00120] - Configure a PDCP entity to activate or deactivate the packet duplication function (optional).
[00121] - Establish a new RLC entity and a new DCCH logical channel for the packet duplication SRB corresponding to the SRB identity. A logical channel identity of the logical channel can be defined with one of the following values (ie the definition of the logical channel identity of the newly established logical channel is the same as that of the method for defining a logical channel identity given in the establishment modalities of a packet duplication SRB): another default value corresponding to the SRB identity, a default value corresponding to the SRB identity plus an offset, and a logical channel identity corresponding to the SRB identity carried in the RRC message.
[00122] - Apply a standard logical channel configuration that corresponds to the SRB identity to the corresponding SRB. The same or another standard logic channel configuration can be applied to two logical channels. You can also use a default configuration for one logical channel, and use the logical channel configuration information, logicalChannelConfig, included in the RRC message for the other logical channel.
[00123] For the SRB corresponding to the SRB identity included in the RRC message: if the configured SRB is a duplication SRB
Petition 870190093832, of 9/19/2019, p. 52/102
35/59 packets and the RRC flag does not include an indication to indicate that the SRB is a duplication SRB, that is, a packet duplication SRB must be reconfigured as an SRB that does not support packet duplication, so the following operations must be performed (operations can be performed in different sequences):
[00124] - Configure a PDCP entity to disable the packet duplication function (optional).
[00125] - Apply a predefined configuration corresponding to the SRB identity to an SRB that is an SRB that does not support packet duplication, that is, the default configuration is a predefined configuration that corresponds to an SRB that does not support packet duplication .
[00126] - Release an RLC entity, that is, release other entities in addition to an RLC entity corresponding to the SRB that does not support the duplication of packages or release other RLC entities in addition to an RLC entity associated with a logical channel ( a logical channel identity of the logical channel is a default value corresponding to the SRB that does not support packet duplication) corresponding to the SRB that does not support packet duplication.
[00127] - Release a logical channel, that is, release other logical channels in addition to the logical channel corresponding to the SRB that does not support the duplication of packets.
[00128] - Apply a standard RLC configuration that corresponds to the SRB identity to the corresponding SRB.
[00129] - Apply a standard logical channel configuration that corresponds to the SRB identity to the corresponding SRB.
Mode 2 [00130] If the user's equipment receives an RRC message from a base station, then the message may be an
Petition 870190093832, of 9/19/2019, p. 53/102
36/59 RRC reconfiguration that can be used for a transfer scenario (the RRC message includes a mobility control information element, mobilityControlInfo, to indicate a transfer) or a non-transfer scenario (the RRC message does not include an information element mobilityControlInfo to indicate a transfer). The RRC message includes an indication (represented as fullConfig) to indicate the application of the complete configuration to the RRC reconfiguration message. The RRC message additionally includes an SRB identity that requires reconfiguration, for example, an SRB identity that requires reconfiguration included in an srb-ToAddModList information element. For an SRB corresponding to the SRB identity included in the RRC message: the user equipment reconfigures a configured SRB (also called an existing or current SRB, which is an SRB already configured before the UE receives the RRC message) to the SRB identity as an SRB that does not support packet duplication. The configured SRB can be a packet duplication SRB or an SRB that does not support packet duplication. Specifically, the following operations are included (operations can be performed in different sequences):
[00131] - Apply a predefined configuration corresponding to the SRB identity to an SRB that is an SRB that does not support packet duplication, that is, the default configuration is a predefined configuration that corresponds to an SRB that does not support packet duplication .
[00132] - Release an RLC entity if the configured SRB is a packet duplication SRB. That is, releasing other entities in addition to an RLC entity corresponding to the SRB that does not support packet duplication, or releasing other RLC entities in addition to an RLC entity associated with a logical channel (an identity of
Petition 870190093832, of 9/19/2019, p. 54/102
37/59 logical channel of the logical channel is a default value corresponding to the SRB that does not support duplication of packets) corresponding to the SRB that does not support duplication of packets.
[00133] - Release a logical channel if the configured SRB is a
Packet duplication SRB. That is, releasing other logical channels in addition to the logical channel corresponding to the SRB that does not support packet duplication, and a logical channel identity of the logical channel is not a predefined value that corresponds to the SRB that does not support packet duplication.
[00134] - Apply a standard RLC configuration that corresponds to the SRB identity to the corresponding SRB.
[00135] - Apply a standard logical channel configuration that corresponds to the SRB identity to the corresponding SRB.
[00136] - Configure a PDCP entity to disable the packet duplication function (optional). Figure 6 is a flow chart of a method 600 used at a base station in accordance with one embodiment of the present disclosure. Method 600 is used to instruct the UE to activate and deactivate a PDCP packet duplication function.
[00137] As shown in the figure, in step S610, the base station configures indication information to activate and / or deactivate a packet duplication function. For example, the indication information can be represented by a newly defined PDCP control PDU, or one or more bits in a PDCP control PDU that is already defined for the implementation of other functions, or a CE (control element). newly defined MAC Control Element, or similar.
[00138] Step S620: The base station transmits the indication information configured to the user equipment (UE) to instruct the UE to activate or deactivate the packet duplication function.
Petition 870190093832, of 9/19/2019, p. 55/102
38/59 [00139] Figure 7 is a flow chart of a method 700 used in user equipment (UE) according to one embodiment of the present disclosure. Method 700 is used to enable and / or disable a PDCP packet duplication function.
[00140] As shown in Figure 7, in step S710 the UE receives, from a base station, an indication information to activate and / or deactivate a packet duplication function. For example, the indication information can be represented by a newly defined PDCP control PDU, or one or more bits in a PDCP control PDU that is already defined for the implementation of other functions, or a CE (control element). control) of newly defined MAC, or similar.
[00141] Step S720: 0 UE enables or disables the packet duplication function according to the indication information received.
[00142] The following text describes modalities for activating and deactivating a PDCP packet duplication function, and the methods in the modalities can be applied to an SRB (ie, a packet duplication SRB and / or an SRB split duplication DRB (ie a duplicate DRB and / or split duplicate DRB) Mode 1 [00143] A PDCP control PDU is defined and used to transmit information indication to enable and / or disable a packet duplication function for a PDCP entity. Figure 8 illustrates an exemplary format of a PDCP control PDU. D / C: 1 bit, indication information for a control PDU and a data PDU. A value of 0 indicates that the corresponding PDU is a control PDU, and a value of 1 indicates that the corresponding PDU is a data PDU. PDU Type - Type of PDU: 3 bits, information indicating a type of PDU. Different values correspond to different types of
Petition 870190093832, of 9/19/2019, p. 56/102
39/59
Control PDUs. A value can be predefined for a control PDU to enable or disable the PDCP entity's packet duplication function. For example, when the Type PDU has a value of 011, the corresponding control PDU is a control PDU to enable and / or disable the PDCP entity's packet duplication function. A: 1 bit, representing Reserved, whose value can be set to 0 so that the receiving side ignores the information of a bit. I: 1 bit or multiple bits (I can also be represented by other symbols), values different from which are defined to represent the activation or deactivation of the PDCP entity's packet duplication function. For example, I occupies 1 bit, and a value of 0 represents the disabling of the packet duplication function, and a value of 1 represents the activation of the packet duplication function, and vice versa. [00144] In the case of an MCG packet duplication SRB, an MCG packet duplication DRB, an SCG packet duplication SRB or an SCG packet duplication DRB, the PDCP control PDU to disable the PDCP packet duplication function can additionally include an indication (which can also be a field) to indicate whether a PDCP PDU should be transmitted via an MCG or an SCG after the packet duplication function is deactivated. Or, I is not defined when the indication is defined. In this case, the user equipment reconfigures the PDCP entity according to the indication so that the PDCP PDU is transmitted only through the CG - group of cells indicated in the indication, is not transmitted through the CG indicated in the indication, ie transmitted through GCs other than the GC indicated in the indication.
Mode 2 [00145] One or more bits in a PDCP control PDU that is already defined to implement other functions are used to indicate
Petition 870190093832, of 9/19/2019, p. 57/102
40/59 the activation or deactivation of a package duplication function of a PDCP entity. Optionally, the PDCP control PDU used to implement other functions and enable or disable the PDCP entity's packet duplication function is defined as a new type of PDU.
[00146] Preferably, a reserved bit R in the PDCP control PDU used to issue a PDCP status report is used to transmit information on enabling or disabling the PDCP entity's packet duplication function. Optionally, the PDCP control PDU, which includes a PDCP status report and is used to enable or disable the PDCP entity's packet duplication function, is defined as a new type of PDU.
[00147] Alternatively, a reserved R bit in the PDCP control PDU used for a robust ROHC header compression interleaved packet - Robust Header Compression - is used to transmit information on enabling or disabling the packet duplication function of the PDCP entity. Optionally, the PDCP control PDU that includes the ROHC interleaved feedback package and is used to enable or disable the PDCP entity's packet duplication function is defined as a new type of PDU.
Mode 3 [00148] A MAC (control element) of MAC is defined and is used to activate and / or deactivate a packet duplication function (or a packet duplication function of a PDCP entity). Optionally, an indication is predefined for the MAC CE to enable and / or disable the packet duplication function (or the PDCP entity packet duplication function) and can be represented as LCID - Logical Channel Identity. logical. The LCID
Petition 870190093832, of 9/19/2019, p. 58/102
41/59 is used to indicate that the corresponding MAC CE is a MAC CE to enable and / or disable the packet duplication function.
[00149] Preferably, the MAC CE includes a DRB identity and / or an SRB identity to activate the packet duplication function, and when a DRB identity and / or an SRB identity is included in the MAC, this represents the activation (or deactivation) of the corresponding packet duplication function. In contrast, if a DRB identity and / or an SRB identity are not included in the MAC CE, then this may represent the deactivation (or activation) of the corresponding packet duplication function. When a MAC entity receives the MAC CE, the MAC entity indicates the DRB identity and / or SRB identity included in the MAC CE to a higher layer (an RRC layer or a PDCP layer), and the highest layer activates or deactivates the DRB and / or corresponding SRB packet duplication function according to the indication information. Optionally, for a DRB and / or SRB duplicating packets corresponding to a DRB identity and / or an SRB identity not indicated by a lower layer, the corresponding DRB and / or SRB packet duplication function is disabled or activated.
[00150] Alternatively, the MAC CE includes a bitmap. The bitmap has a fixed or variable size. Each bit in the bitmap corresponds to an SRB and / or DRB (packet duplication SRB and / or packet duplication DRB). Each bit in the bitmap has a value of 0 or 1, which corresponds, respectively, to disable or enable (or 0 represents to activate and 1 represents to disable) the corresponding packet duplication function of the corresponding SRB and / or DRB. The bitmap size can be a maximum of SRBs and / or DRBs configurable by a system, or the number of SRBs and DRBs configured, or the number of packet and / or duplication SRBs
Petition 870190093832, of 9/19/2019, p. 59/102
42/59
Packet duplication DRBs configured by a base station for a UE. Optionally, first the SRBs and then the DRBs arranged in an ascending order according to the SRB and / or DRB identities correspond sequentially to the bits in the bitmap. The sequential match can be in the sequence from the first bit on the left in the first byte of the bitmap to the right, or from the first bit on the far right in the last byte of the bitmap to the left. That is, the first bit on the left in the first byte of the bitmap corresponds to an SRB that has the smallest identity or the first bit on the far right in the last byte of the bitmap corresponds to a DRB that has the largest identity. For example, supposing that SRB2, DRB1 and DRB3 that support the packet duplication function are set in the UE, three bits from the first bit on the left in the first byte of the bitmap towards the right correspond sequentially to SRB2, DRB1 and DRB3. As another example, the respective bits in the bitmap can correspond sequentially to SRBs and DRBs in the system where they are configured as carriers that support the packet duplication function. Assuming that SRB1 and SRB2 can be configured as carriers that support the packet duplication function and all DRBs can be configured as carriers that support the packet duplication function, and assuming that the number of DRBs supported by the system is n, then , 2 + n bits from the first bit from left to right (or from the last bit from right to left) in the bitmap correspond to SRB1, SRB2, DRB1, DRB2, .... and DRBn respectively. DRBi represents a DRB that has a DRB II j II identity [00151] Alternatively, packet duplication SRBs and packet duplication DRBs are transmitted via different
Petition 870190093832, of 9/19/2019, p. 60/102
43/59
MAC CEs to enable and / or disable packet duplication. Preferably, different LCID values are predefined for the two MAC CES. Alternatively, the two MAC CEs use the same LCID value, but a field is used in the MAC CEs to indicate the type of MAC CEs, and different values in the field are used to indicate whether the corresponding MAC CEs are a CE MAC to enable and / or disable packet duplication corresponding to a packet duplication SRB or MAC MAC to enable and / or disable packet duplication corresponding to a packet duplication DRB. For example, if the field value is 0, then this indicates that the MAC CE is a MAC CE to enable and / or disable packet duplication corresponding to a packet duplication SRB; if the field value is 1, then this indicates that the MAC CE is a MAC CE to enable and / or disable packet duplication corresponding to a packet duplication DRB. And vice versa.
[00152] In the case of an MCG packet duplication SRB or an MCG packet duplication DRB or an SCG packet duplication SRB or an SCG packet duplication DRB, it can be predefined that the MAC CE can only be transmitted from a MAC corresponding to an MCG or SCG when the packet duplication function is enabled or disabled. For example, in the case of an MCG packet duplication SRB or an MCG packet duplication DRB, the corresponding MAC CE is transmitted via the MCG; in the case of an SCG packet duplication SRB or an SCG packet duplication DRB, the corresponding MAC CE is transmitted via the SCG.
Mode 4 [00153] A PDCP packet duplication function is activated or deactivated based on an activation / deactivation MAC CE.
Petition 870190093832, of 9/19/2019, p. 61/102
44/59
When a MAC layer receives an activation / deactivation-based MAC CE to activate or deactivate a SCell, the indication information is indicated for a higher layer. The topmost layer will activate or deactivate the packet duplication function according to the indication information.
[00154] Preferably, when a MAC CE for activating or deactivating a SCell is received, if the number of cells (including a PCell and a SCell) that are in an activated state is greater than one, then a layer more discharge (for example, from RRC) is instructed to activate the packet duplication function of an SRB and / or a DRB that is already configured to support the packet duplication function; if the number of cells in an activated state is less than two (that is, only the PCell is in an activated state and the other cells are in a disabled state), then the topmost layer (for example, RRC ) is instructed to disable the SRB and / or DRB packet duplication function that is already configured to support the packet duplication function.
[00155] Alternatively, when a MAC CE for activating or deactivating a SCell is received, if the number of cells (including a PCell and a SCell) that are in an activated state is greater than one, then the indication information is indicated for the highest layer (for example, RRC), where the indication information indicates that the number of cells that is in the activated state is greater than one or indicates the number of cells that is in the activated state. The top layer enables, according to the indication information, the packet duplication function of the SRB and / or DRB that is already configured as supporting the packet duplication function. If the number of cells (including a PCell and SCell) that are in an activated state is less than two,
Petition 870190093832, of 9/19/2019, p. 62/102
45/59 then the indication information is indicated for the highest layer (for example, RRC), where the indication information indicates that the number of cells in the activated state is less than two or indicates the number of cells that is in the activated state. The top layer disables, according to the indication information, the packet duplication function of the SRB and / or DRB that is already configured as supporting the packet duplication function.
[00156] Alternatively, when the MAC layer receives a MAC CE to activate or deactivate a SCell, the indication information is indicated for the highest layer only when the activated cells (including a PCell and a SCell) change from one SCell to another. for many and / or change from multiples to one, where the information indication is used to indicate the number of cells that are in the activated state or to activate or deactivate the SRB and / or DRB packet duplication function. The topmost layer will activate or deactivate the packet duplication function according to the indication information.
Mode 5 [00157] When only one cell is in an activated state, but a MAC layer receives data from two or more logical channels corresponding to the same packet duplication SRB or packet duplication DRB, the MAC layer indicates an error to a higher layer (for example, from RRC) or indicates to the highest layer that only one cell is in the activated state or instructs the highest layer to disable the packet duplication function; or the MAC layer transmits data from two or more logical channels via a component carrier CC (Component Carrier); or the MAC layer transmits data from only one logical channel (for example, transmits data from a logical channel that has a smaller logical channel identity or the smaller logical channel identity); or a MAC CE is built to request a stationPetition 870190093832, of 19/09/2019, p. 63/102
46/59 base that activates a SCell. If the MAC layer indicates an error to the highest layer or indicates to the highest layer that only one cell is in the activated state, then the highest layer can disable the packet duplication function or transmit an RRC message to the base station after receiving the indication, and the RRC message is used to request the base station to activate a SCell.
[00158] The following describes the processing of a PDCP PDU received by a PDCP entity from a packet duplication SRB on a user device [00159] The UE receives a PDCP data PDU from a base station; if the PDCP data PDU is a duplicate PDU or SDU, then the UE performs an integrity check (if the function is supported) on the PDCP PDU or SDU; and if the integrity check fails, then the UE indicates the failure of the integrity check to a higher layer (for example, an RRC layer). After receiving the indication, the highest layer performs the restoration of the RRC connection.
[00160] The algorithm modality described below involves the following parameters:
[00161] Last_Submitted_PDCP_RX_SN: the variable is used to indicate a sequence number - SN - from a PDCP SDU sent to a higher layer last time to a PDCP entity corresponding to a DRB mapped to a recognized AM mode - Acknowledged Mode - radio link control - RLC. In the form of this disclosure, as Last_Submitted_PDCP_RX_SN = Next_PDCP_RX_SN - 1, the two variables can be used interchangeably.
[00162] Reordering_Window: indicates the size of a reordering window. The size of the reordering window is related
Petition 870190093832, of 9/19/2019, p. 64/102
47/59 to the number of bits occupied by a PDCP SN - PDCP sequence number, and is half the space of the PDCP SN.
[00163] RX_HFN: the variable is used to indicate the value of a number of hyperframes HFN - Hyper Frame Number - that generates a value of COUNT, and COUNT is used for PDCP PDUs received by a given PDCP entity.
[00164] Next_PDCP_RX_SN: the variable is used to indicate a desired next PDCP SN on the receiving side of a specific PDCP entity.
[00165] PSCP SN: a PDCP sequence number, which can be a sequence number of an SDU or PDCP PDU.
[00166] Maximum_PDCP_SN: a maximum number of PDCP SN that is related to the number of bits occupied by an SN configured for a PDCP entity.
[00167] COUNT: consists of an HFN and a PDCP SN, as shown in Figure 9.
[00168] PDCP SN received: an SN from a PDCP PDU received. [00169] Figure 10 is a schematic flowchart illustrating the processing of a PDCP PDU received by a PDCP entity;
[00170] Step 1001: The user equipment receives a PDCP PDU from a base station (or a lower layer).
[00171] Step 1002: Judge whether a received SN PDCP satisfies the received SN PDCP condition - Last_Submitted_PDCP_RX_SN> Reordering_Window. If so, then step 1003 is performed; otherwise, step 1004 is performed.
[00172] Step 1003: Perform decryption and integrity check (if supported) on the received PDU using COUNT and received SN PDCP, where COUNT is based on RX_HFN - 1 (a PDCP SDU is obtained after the PDU be decrypted);
Petition 870190093832, of 9/19/2019, p. 65/102
48/59 and if the integrity check fails, then indicate the failure of the integrity check to a higher layer (for example, from RRC). Optionally, the obtained PDCP SDU is deleted. If the integrity check fails, then the algorithm ends; if the integrity check is successful, then the process returns to step 1001.
[00173] Step 1004: Judge whether the received PDCP SN satisfies condition 0 <= Last_Submitted_PDCP_RX_SN - Received PDCP SN <Reordering_Window. If so, then step 1005 is performed; otherwise, step 1006 is performed.
[00174] Step 1005: Perform decryption and integrity check (if supported) on the received PDU using COUNT and the received SN PDCP, where COUNT is based on RX_HFN (a PDCP SDU is obtained after the PDU is decrypted ); and if the integrity check fails, then indicate the failure of the integrity check to a higher layer (for example, from RRC). Optionally, the obtained PDCP SDU is deleted. If the integrity check fails, then the algorithm ends; if the integrity check is successful, then the process returns to step 1001. [00175] Step 1006: Judging whether a received SN PDCP satisfies the received PDCP SN condition <Next_PDCP_RX_SN. If so, then step 1007 is performed; otherwise, step 1008 is performed.
[00176] Step 1007: Perform decryption and integrity check (if supported) on the received PDU using COUNT and the received SN PDCP, where COUNT is based on RX_HFN - 1 (a PDCP SDU is obtained after the PDU decrypted).
[00177] Step 1008: Perform decryption and integrity check (if supported) on the received PDU using COUNT and the received SN PDCP, where COUNT is based on RX_HFN (a PDCP SDU is obtained after the PDU is decrypted ).
Petition 870190093832, of 9/19/2019, p. 66/102
49/59 [00178] Step 1009: Perform step 1010 if the health check is supported and the health check is successful or if the health check is not supported. Otherwise, step 1014 is performed.
[00179] Step 1010: If the PDCP SN received <Next_PDCP_RX_SN, then RX_HFN = RX_HFN + 1.
[00180] Step 1011: Next_PDCP_RX_SN t = PDCP SN received + 1. If Next_PDCP_RX_SN> Maximum_PDCP_SN, then Next_PDCP_RX_SN = 0 and RX_HFN = RX_HFN + 1.
[00181] Step 1012: Send the obtained PDCP SDU to a higher layer.
[00182] Step 1013: Define Last_Submitted_PDCP_RX_SN with a PDCP SN from a last PDCP SDU sent to the highest layer. This step will not be performed if the Last_Submitted_PDCP_RX_SN variable is not used.
[00183] Step 1014: Erase the received PDCP data PDU and indicate the failure of the integrity check for the highest layer.
[00184] It should be noted that the judgment conditions in steps 1002 and 1004 can be performed in reverse order. The PDCP SN judgment condition received <Next_PDCP_RX_SN in step 1006 and in step 1010 is equivalent to the Next_PDCP_RX_SN condition - PDCP SN received> Reordering_Window.
[00185] The structure of a UE according to one embodiment of the present disclosure will be described below with reference to Figure 11. Figure 11 is a schematic structural diagram of a UE 1100 according to the embodiment of the present disclosure. The UE 1100 can be used to perform the method described with reference to Figure 4, Figure 5 or Figure 7.
[00186] As shown in Figure 11, the UE 1100 includes a transceiver 1101 configured to perform external communication;
Petition 870190093832, of 9/19/2019, p. 67/102
50/59 a processing unit or a processor 1103, the processor 1103 being either a single unit or a combination of multiple units configured to perform different steps of the method; and a memory 1105 that stores computer executable instructions that, when executed by processor 1103, cause the UE 1100 to perform the following operations corresponding to method 400: receiving, from a base station via transceiver 1101, an indication to indicate whether a corresponding radio signaling (SRB) carrier supports packet duplication and configuration information from an SRB that supports packet duplication; and establish the corresponding packet duplication SRB according to the configuration information received.
[00187] In an exemplary mode, memory 1105 additionally stores instructions that cause processor 1103 to perform the following operation: if the packet duplication SRB has the same SRB identity as that of an SRB that does not support duplication then receive the corresponding packet duplication SRB SRB identity from the base station.
[00188] In an exemplary mode, if the packet duplication SRB has a different SRB identity than a corresponding SRB that does not support packet duplication, then the indicator will be the SRB identity of the packet duplication SRB.
[00189] Memory 1105 can also store instructions executable by computer which, when executed by processor 1103, cause the UE 1100 to perform the following operations corresponding to method 500: receiving, from a base station via transceiver 1101, an indication to indicate whether a reconfigured radio signaling (SRB) carrier supports the
Petition 870190093832, of 9/19/2019, p. 68/102
51/59 duplication of packages; if the configured SRB does not support packet duplication and the indication indicates that the reconfigured SRB supports packet duplication, then reconfigure, at UE, the packet duplication SRB configured as supporting packet duplication.
[00190] In an exemplary mode, memory 1105 additionally stores instructions that cause processor 1103 to perform the following operation: if the configured SRB supports packet duplication and the indication indicates that the reconfigured SRB does not support packet duplication, then reconfigure the SRB configured as not supporting packet duplication.
[00191] Memory 1105 can also store instructions executable by computer which, when executed by processor 1103, cause the UE 1100 to perform the following operations corresponding to method 700: receiving, from a base station via transceiver 1101, indication information to activate and / or deactivate a packet duplication function according to the indication information received.
[00192] The structure of a base station according to one embodiment of the present disclosure will be described below with reference to Figure 12. Figure 12 is a schematic structural diagram of a base station 1200 according to one embodiment of the present disclosure . Base station 1200 can be used to perform the method described with reference to Figure 6.
[00193] As shown in Figure 12, base station 1200 includes a transceiver 1201 configured to perform external communication; a processing unit or a processor 1203, the processor 1203 being either a single unit or a combination of multiple units configured to perform different steps of the method; and a 1205 memory that stores instructions executable by
Petition 870190093832, of 9/19/2019, p. 69/102
52/59 computer that, when executed by processor 1203, cause base station 1200 to perform the following operations corresponding to method 600: configure the indication information to activate and / or deactivate a packet duplication function; and transmitting the indication information configured to the user equipment (UE) to instruct the UE to enable or disable the packet duplication function.
[00194] Figure 13 is a flowchart of a method 1300 performed on user equipment (UE) according to one embodiment of the present disclosure.
[00195] As shown in Figure 13, in step S1310, the UE receives a control element (CE) of media access control (MAC) to indicate the activation and / or deactivation of packet duplication from a radio carrier (DRB).
[00196] If packet duplication is configured and packet duplication is enabled, then, in step S1320, a packet data convergence protocol (PDCP) entity provides a PDCP protocol data unit (PDU) for two radio link control entities (RLC).
[00197] If packet duplication is configured and packet duplication is disabled, then, in step S1330, the PDCP entity supplies the PDCP PDU to one of the two RLC entities.
[00198] The MAC CE includes a bitmap that has a fixed size, with each bit in the bitmap corresponding to a packet duplication DRB identity arranged in an ascending order; a bit set with a value of 1 in the bitmap indicates the activation of the duplication of packets of the corresponding DRB, and a bit set with a value of 0 in the bitmap indicates the deactivation of duplication of packets of the corresponding DRB.
Petition 870190093832, of 9/19/2019, p. 70/102
53/59 [00199] Figure 14 is a flowchart of a method 1400 performed at a base station (BS) according to one embodiment of the present disclosure.
[00200] As shown in Figure 14, in step S1410, the base station, BS, transmits a control element (CE) of media access control (MAC) to indicate to the user equipment (UE) the activation and / or disabling duplication of packets from a radio data carrier (DRB).
[00201] If packet duplication is configured and packet duplication is enabled, then a UE packet data convergence protocol (PDCP) entity provides a PDCP protocol data unit (PDU) for two entities from radio link control (RLC).
[00202] If packet duplication is configured and packet duplication is disabled, then the PDCP entity provides the PDCP PDU for one of the two RLC entities.
[00203] The MAC CE includes a bitmap that has a fixed size, each bit in the bitmap corresponding to a packet duplication DRB identity arranged in an ascending order; a bit set with a value of 1 in the bitmap indicates the activation of the duplication of packets of the corresponding DRB, and a bit set with a value of 0 in the bitmap indicates the deactivation of duplication of packets of the corresponding DRB.
[00204] Figure 15 is a flow chart of a method 1500 executed in a user equipment (UE) according to a modality of the present disclosure.
[00205] As shown in Figure 15, in step S1510, the UE receives a packet data convergence protocol (PDCP) protocol data unit (PDU) from a lower layer.
Petition 870190093832, of 9/19/2019, p. 71/102
54/59 [00206] If the PDCP data PDU was previously received, then, in step S1520, the integrity check is performed on the PDCP data PDU. If the PDCP data PDU has not been received previously, then the method ends.
[00207] If the integrity check fails, in step S1530, then the failure of the integrity check is indicated for a higher layer. If the integrity check is successful, then the method ends.
[00208] Figure 16 is a schematic structural diagram of a UE 1600 according to an embodiment of the present disclosure.
[00209] UE 1600 can be used to execute the method described with reference to Figure 13.
[00210] As shown in Figure 16, the UE 1600 includes a 1610 receiving unit configured to receive a media access control (CE) control element (MAC) to indicate the activation and / or deactivation of packet duplication a radio data carrier (DRB); and a 1620 sending unit configured for: if packet duplication is configured and packet duplication is enabled, then provide, through a packet data convergence protocol (PDCP) entity, a protocol data unit (PDU) ) of PDCP for two radio link control entities (RLC); and if packet duplication is configured and packet duplication is disabled, then provide, through the PDCP entity, the PDCP PDU for one of the two RLC entities.
[00211] The MAC CE includes a bitmap that has a fixed size, with each bit in the bitmap corresponding to a packet duplication DRB identity arranged in an ascending order; a bit set with a value of 1 in the bitmap indicates the activation of duplicate packets of the corresponding DRB, and a bit set with a value of 0 in the
Petition 870190093832, of 9/19/2019, p. 72/102
55/59 bitmap indicates the disabling of duplicate packets from the corresponding DRB.
[00212] Figure 17 is a schematic structural diagram of a BS 1700 according to an embodiment of the present disclosure.
[00213] BS 1700 can be used to execute the method described with reference to Figure 14.
[00214] As shown in Figure 17, BS 1700 includes a 1710 transmission unit configured to transmit a media access control (CE) control element (MAC) to indicate to user equipment (UE) activation and / or disabling duplication of packets from a radio data carrier (DRB).
[00215] If packet duplication is configured and packet duplication is enabled, then a UE packet data convergence protocol (PDCP) entity provides a PDCP protocol data unit (PDU) for two entities from radio link control (RLC).
[00216] If packet duplication is configured and packet duplication is disabled, then the PDCP entity supplies the PDCP PDU to one of the two RLC entities.
[00217] The MAC CE includes a bitmap that has a fixed size, with each bit in the bitmap corresponding to a packet duplication DRB identity arranged in an ascending order; a bit set with a value of 1 in the bitmap indicates the activation of the duplication of packets of the corresponding DRB, and a bit set with a value of 0 in the bitmap indicates the deactivation of duplication of packets of the corresponding DRB.
[00218] Figure 18 is a schematic structural diagram of a UE 1800 according to an embodiment of the present disclosure.
[00219] UE 1800 can be used to execute the method described with reference to Figure 15.
Petition 870190093832, of 9/19/2019, p. 73/102
56/59 [00220] As shown in Figure 18, UE 1800 includes a receiving unit 1810 configured to receive a packet data convergence protocol (PDCP) protocol data unit (PDU) from a lower layer. ); a verification unit 1820 configured for: if the PDCP data PDU was previously received, then perform an integrity check on the PDCP data PDU; and an 1830 indicating unit configured for: if the integrity check fails, then indicate the failure of the integrity check to a higher layer.
[00221] The present disclosure additionally provides at least one computer storage medium in the form of a volatile or non-volatile memory, such as a programmable and electrically erasable read-only memory (EEPROM), a flash memory and a disk drive. hard. Computer executable instructions, when executed by processor 1103, cause the UE 1100 to execute, for example, the actions of the processes described above with reference to Figure 4, Figure 5, Figure 7, Figure 13 and Figure 15 , or when executed by processor 1203, cause base station 1200 to perform, for example, the actions of the processes described previously with reference to Figure 6 and Figure 14.
[00222] The processor can be a single CPU (central processing unit), but it can also include two or more processors. For example, the processor may include a general purpose microprocessor, an instruction set processor and / or a related integrated circuit set and / or a dedicated microprocessor (for example, an application specific integrated circuit (ASIC)). The processor may also include an integrated memory for caching purposes. For example, computer storage media can be flash memory, a
Petition 870190093832, of 9/19/2019, p. 74/102
57/59 random access memory (RAM), a read-only memory (ROM), or an EEPROM.
[00223] The instructions executable on a computer or the program executed on the device according to the present invention can be a program that allows the computer to implement the functions of the modalities of the present invention by controlling the central processing unit (CPU). The program or the information processed by the program can be temporarily stored in volatile memory (for example, random access memory (RAM), hard disk drive (HDD Hard Disk Drive), non-volatile memory ( eg flash memory) or other memory systems.
[00224] The instructions executable on a computer or the program to implement the functions of the modalities of the present invention can be recorded on a computer-readable recording medium. The corresponding functions can be obtained by reading programs recorded on the recording medium and executing them by the computer system. The so-called computer system mentioned here may be a computer system integrated into the device, which may include operating systems or hardware (for example, peripherals). The computer-readable storage media can be a semiconductor-based recording medium, an optical recording medium, a magnetic recording medium, a short-term dynamic memory program recording medium, or any other recording medium readable by a computer.
[00225] Various features or functional modules of the device used in the above modalities can be implemented or executed by means of circuits (for example, monolithic or multiple integrated circuits). Circuits designed to perform the functions described here may include general purpose processors, processors
Petition 870190093832, of 9/19/2019, p. 75/102
58/59 Digital Signal Processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, discrete ports or transistor logic, or different hardware components, or any combination of the above. The general purpose processor can be a microprocessor, or it can be any existing processor, a controller, a microcontroller, or a state machine. The circuit can be a digital circuit or an analog circuit. When new integrated circuit technologies emerge that replace existing integrated circuits, due to advances in semiconductor technology, one or more modalities of the present invention can also be implemented with the use of these new integrated circuit technologies.
[00226] Furthermore, the present invention is not limited to the modalities described above. Although several examples of the modalities have been described, the present invention is not limited to them. Fixed or non-mobile electronic devices installed indoors or outdoors, such as audio / video (AV) equipment, kitchen equipment, cleaning equipment, air conditioners, office equipment, vending machines and other household appliances can be used terminal devices or communication devices.
[00227] The modalities of the present invention have been described in detail above, with reference to the attached drawings. However, the specific structures are not limited to the aforementioned modalities. The present invention also includes any design modifications that do not depart from the main idea of the present invention. In addition, various modifications can be made to the present invention within the scope of the claims. The modalities resulting from the
Petition 870190093832, of 9/19/2019, p. 76/102
59/59 Suitable combinations of the technical means disclosed in different modalities are also included in the technical scope of the present invention. In addition, components with the same effect described in the above modalities can be replaced with each other.

权利要求:
Claims (6)
[1]
1. Method performed on user equipment (UE), characterized by the fact that it comprises:
receive a control element (CE) for media access control (MAC) to indicate the activation and / or deactivation of packet duplication from a data radio carrier (DRB);
if packet duplication is configured and packet duplication is enabled, then provide, through a packet data convergence protocol entity (PDCP), a PDCP protocol data unit (PDU) for two control entities radio link (RLC); and if packet duplication is configured and packet duplication is disabled, then provide, by the PDCP entity, the PDCP PDU for one of the two RLC entities, the MAC CE comprising a bitmap that is sized fixed, with each bit in the bitmap corresponding to a packet duplication DRB identity arranged in an ascending order; and a bit set with a value of 1 in the bitmap indicates the activation of packet duplication of the corresponding DRB, and a bit set with a value of 0 in the bitmap indicates the deactivation of packet duplication of the corresponding DRB.
[2]
2. User equipment (UE), characterized by the fact that it comprises:
a receiving unit, configured to receive a control element (CE) for media access control (MAC) to indicate the activation and / or deactivation of packet duplication from a data radio carrier (DRB); and a sending unit, configured for: if duplication
Petition 870190093832, of 9/19/2019, p. 78/102
2/4 packets is configured and packet duplication is enabled, so provide, through a packet data convergence protocol entity (PDCP), a PDCP protocol data unit (PDU) for two control entities radio link (RLC); and if packet duplication is configured and packet duplication is disabled, then provide, by the PDCP entity, the PDCP PDU for one of the two RLC entities, in which the MAC CE comprises a bitmap that is sized fixed, with each bit in the bitmap corresponding to a packet duplication DRB identity arranged in an ascending order; and a bit set with a value of 1 in the bitmap indicates the activation of packet duplication of the corresponding DRB, and a bit set with a value of 0 in the bitmap indicates the deactivation of packet duplication of the corresponding DRB.
[3]
3. Method performed at a base station (BS), characterized by the fact that it comprises:
transmitting a control element (CE) for access control to media (MAC) to indicate to the user equipment (UE) the activation and / or deactivation of packet duplication of a data radio carrier (DRB);
if packet duplication is configured and packet duplication is enabled, then provide, through a UE packet data convergence protocol (PDCP) entity, a PDCP protocol data unit (PDU) for two radio link control (RLC); and if packet duplication is set up and packet duplication is disabled, then provide, for the
Petition 870190093832, of 9/19/2019, p. 79/102
3/4 PDCP entity, the PDCP PDU for one of the two RLC entities, where the MAC CE comprises a bitmap that has a fixed size, with each bit in the bitmap corresponding to a DRB identity of duplication of packages arranged in an ascending order; and a bit set with a value of 1 in the bitmap indicates the activation of packet duplication of the corresponding DRB, and a bit set with a value of 0 in the bitmap indicates the deactivation of packet duplication of the corresponding DRB.
[4]
4. Base station (BS), characterized by the fact that it comprises:
a transmission unit, configured to transmit a control element (CE) for access control to media (MAC) to indicate to the user equipment (UE) the activation and / or deactivation of packet duplication of a radio carrier data (DRB);
if packet duplication is configured and packet duplication is enabled, then provide, through a UE packet data convergence protocol (PDCP) entity, a PDCP protocol data unit (PDU) for two radio link control (RLC); and if packet duplication is configured and packet duplication is disabled, then provide, by the PDCP entity, the PDCP PDU for one of the two RLC entities, the MAC CE comprising a bitmap that is sized fixed, with each bit in the bitmap corresponding to a packet duplication DRB identity arranged in an ascending order; and
Petition 870190093832, of 9/19/2019, p. 80/102
4/4 a bit set with the value 1 in the bitmap indicates the activation of the duplication of packets of the corresponding DRB, and a bit set with the value 0 in the bitmap indicates the deactivation of the duplication of packets of the corresponding DRB.
[5]
5. Method performed on user equipment (UE), characterized by the fact of understanding:
receiving a packet data convergence protocol (PDCP) protocol data unit (PDU) from a lower layer;
if the PDCP data PDU was previously received, then perform an integrity check on the PDCP data PDU; and if the integrity check fails, then indicate to a higher layer the integrity check failed.
[6]
6. User equipment (UE), characterized by the fact that it comprises:
a receiving unit configured to receive a packet data convergence protocol (PDCP) protocol data unit (PDU) from a lower layer;
a verification unit configured for: if the PDCP data PDU was previously received, then perform an integrity check on the PDCP data PDU; and an indication unit configured for: if the integrity check fails, then indicate the failure of the integrity check to a higher layer.

类似技术:

---

公开号 | 公开日 | 专利标题

---

BR112019019535A2|2020-04-22|method performed on base station and user equipment and corresponding devices

---

JP2017514367A|2017-06-01|Bearer management apparatus, method, and communication system

---

US20200029379A1|2020-01-23|Radio configuration method, user equipment, and base station

---

EP3644684A1|2020-04-29|User equipment and related method

---

BR112019019578A2|2020-04-14|user equipment

---

US11057958B2|2021-07-06|Method and device for establishing/reconfiguring data bearer

---

CN109150415B|2022-01-21|Base station, user equipment and related method

---

BR112019026085A2|2020-07-07|method for providing data packet, user equipment, and base station

---

US20200374752A1|2020-11-26|User equipment and related method

---

BR112019013841A2|2020-01-28|method of transmitting data, device and computer-readable storage media

---

US11172537B2|2021-11-09|Wireless communication method and device

---

US20220030616A1|2022-01-27|User equipment and method thereof, and base station and method thereof

---

BR112019025411A2|2020-06-23|BASE STATION, USER EQUIPMENT AND RELATED METHOD

---

ES2846699T3|2021-07-28|Communication control methods and communication systems

---

BR112019026010A2|2020-06-23|WIRELESS PROTOCOL LAYER ENTITY PROCESSING METHOD AND CORRESPONDING USER EQUIPMENT

---

US11134527B2|2021-09-28|Radio configuration method and corresponding user equipment

---

BR112019026296A2|2020-06-30|user device

---

WO2018059148A1|2018-04-05|Data forwarding method and device thereof

---

CN111314906A|2020-06-19|User equipment and method thereof, base station and method thereof

---

WO2020221155A1|2020-11-05|Base station, user equipment and related method

---

BR112021010897A2|2021-08-24|User device and method thereof, and base station and method thereof

---

BR112020011126A2|2020-11-17|user terminal and radiocommunication method

同族专利:

---

公开号 | 公开日

---

CN108924948A|2018-11-30|

---

CO2019011607A2|2020-02-18|

---

EP3606274A4|2020-12-23|

---

MX2019011164A|2019-10-21|

---

CN108924948B|2021-06-22|

---

EP3606274A1|2020-02-05|

---

US11026281B2|2021-06-01|

---

WO2018171546A1|2018-09-27|

---

US20210112610A1|2021-04-15|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

KR101669966B1|2009-05-11|2016-10-27|엘지전자 주식회사|Method for transmitting and receiving duplicated data in a multi-carrier supported wireless communication system and appratus for the same|

---

EP3061309B1|2013-10-21|2020-04-08|LG Electronics Inc.|Method and ue for transmitting uplink data in a dual connectivity and a device therefor|

---

US10433176B2|2013-11-11|2019-10-01|Telefonaktiebolaget Lm Ericsson |Discarding a duplicate protocol data unit associated with a data transmission via a first signaling radio bearer or a second signaling radio bearer|

---

CN104935414B|2014-03-21|2019-05-24|上海诺基亚贝尔股份有限公司|A kind of method and apparatus for transmitting information in doubly-linked welding system|

---

CN104955064B|2014-03-28|2019-01-11|上海诺基亚贝尔股份有限公司|A kind of method and apparatus handling user equipment end RLC/PDCP entity in doubly-linked welding system|

---

US20180375621A1|2015-12-14|2018-12-27|Nokia Solutions And Networks Oy|Data retransmission|

---

KR20180050015A|2016-11-04|2018-05-14|삼성전자주식회사|Method and apparatus for data transmission and reception of ultra reliable and low latency communications in wireless communication system|

---

US10716094B2|2017-03-23|2020-07-14|Ofinno, Llc|Packet duplication in a wireless device and wireless network|

---

CN108924948B|2017-03-23|2021-06-22|夏普株式会社|Method performed at user equipment and base station and corresponding equipment|

---

WO2018170891A1|2017-03-24|2018-09-27|Nokia Technologies Oy|Handling of pdcp duplication and data recovery in new radio access technology|

---

EP3610694A1|2017-04-10|2020-02-19|Nokia Technologies Oy|Control mechanism for packet duplication in multi-connectivity communication|

---

WO2018230849A1|2017-06-14|2018-12-20|Lg Electronics Inc.|Method for handling deactivation for a cell in which packet duplication is performed in wireless communication system and a device therefor|

---

EP3923499A1|2017-06-15|2021-12-15|Samsung Electronics Co., Ltd.|Packet duplication control|

---

US20180367288A1|2017-06-16|2018-12-20|Huawei Technologies Co., Ltd.|Dynamic activation and deactivation of packet duplication|

---

EP3661090A4|2017-07-28|2021-03-10|Fujitsu Limited|Command instruction method and device, and information interaction method and device|

---

US10772008B2|2018-01-11|2020-09-08|Comcast Cable Communications, Llc|Cell configuration for packet duplication|

---

US10869223B2|2018-02-13|2020-12-15|Samsung Electronics Co., Ltd.|Method and apparatus for efficient operation upon packet duplication activation and deactivation in next generation wireless communication system|

---

KR20190143295A|2018-06-20|2019-12-30|삼성전자주식회사|Method and apparatus to control the packet duplication considering a dual connectivity in the next generation mobile communication system|

---

EP3836457A4|2018-10-30|2021-09-01|Guangdong Oppo Mobile Telecommunications Corp., Ltd.|Method for indicating state of pdcp duplicate data, terminal device, and network device|

---

CN111148157B|2018-11-06|2022-01-25|大唐移动通信设备有限公司|Processing method and device for repeated transmission and network node|

---

WO2020156565A1|2019-02-03|2020-08-06|FG Innovation Company Limited|Evolved packet data convergence protocol duplication|CN108924948B|2017-03-23|2021-06-22|夏普株式会社|Method performed at user equipment and base station and corresponding equipment|

---

WO2018230623A1|2017-06-14|2018-12-20|株式会社Ｎｔｔドコモ|Wireless communication system, user device, wireless base station, and wireless communication method|

---

EP3923499A1|2017-06-15|2021-12-15|Samsung Electronics Co., Ltd.|Packet duplication control|

---

JP2020529751A|2017-06-16|2020-10-08|オッポ広東移動通信有限公司Ｇｕａｎｇｄｏｎｇ Ｏｐｐｏ Ｍｏｂｉｌｅ Ｔｅｌｅｃｏｍｍｕｎｉｃａｔｉｏｎｓ Ｃｏｒｐ．， Ｌｔｄ．|Data transmission method, terminal equipment and network equipment|

---

EP3668220A4|2017-08-08|2021-04-14|Mitsubishi Electric Corporation|Communication system, communication terminal device, and base station device|

---

CN109547175B|2017-08-11|2020-10-30|电信科学技术研究院|Bearer mapping method, device, base station and terminal|

---

CN109802922A|2017-11-16|2019-05-24|电信科学技术研究院|A kind of processing method and equipment of cache synchronization exception|

---

EP3836457A4|2018-10-30|2021-09-01|Guangdong Oppo Mobile Telecommunications Corp., Ltd.|Method for indicating state of pdcp duplicate data, terminal device, and network device|

---

CN111148157B|2018-11-06|2022-01-25|大唐移动通信设备有限公司|Processing method and device for repeated transmission and network node|

---

US11228960B2|2018-11-12|2022-01-18|Nokia Technologies Oy|Efficient signaling in multi-connectivity scenarios|

---

CN111314970A|2018-12-11|2020-06-19|夏普株式会社|User equipment and method thereof, base station and method thereof|

---

CN111404633B|2019-01-03|2021-10-26|华为技术有限公司|Method and equipment for selecting transmission mode|

---

EP3912300A1|2019-01-18|2021-11-24|FG Innovation Company Limited|Packet data convergence protocol duplication in next generation wireless networks|

---

CN113366782A|2019-02-01|2021-09-07|瑞典爱立信有限公司|First communication device, second communication device and methods performed therein for controlling transmissions|

---

WO2020164114A1|2019-02-15|2020-08-20|华为技术有限公司|Communication method and apparatus|

---

CN110856275B|2019-11-07|2021-10-26|展讯通信（上海）有限公司|DRB configuration method and related device|

---

WO2021162600A1|2020-02-13|2021-08-19|Telefonaktiebolaget Lm Ericsson |Packet duplication indication for mdt|

法律状态:
2021-10-19| B350| Update of information on the portal [chapter 15.35 patent gazette]|

优先权:

---

申请号 | 申请日 | 专利标题

---

CN201710180715.3A|CN108924948B|2017-03-23|2017-03-23|Method performed at user equipment and base station and corresponding equipment|

---

PCT/CN2018/079446|WO2018171546A1|2017-03-23|2018-03-19|Method executed in user equipment and base station and corresponding equipment|

---