WO2018228289A1 - 基站、用户设备和相关方法 - Google Patents

基站、用户设备和相关方法 Download PDF

Info

Publication number
WO2018228289A1
WO2018228289A1 PCT/CN2018/090468 CN2018090468W WO2018228289A1 WO 2018228289 A1 WO2018228289 A1 WO 2018228289A1 CN 2018090468 W CN2018090468 W CN 2018090468W WO 2018228289 A1 WO2018228289 A1 WO 2018228289A1
Authority
WO
WIPO (PCT)
Prior art keywords
mac
data
entity
mcg
scg
Prior art date
Application number
PCT/CN2018/090468
Other languages
English (en)
French (fr)
Inventor
肖芳英
山田升平
刘仁茂
Original Assignee
夏普株式会社
肖芳英
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 夏普株式会社, 肖芳英 filed Critical 夏普株式会社
Priority to US16/620,626 priority Critical patent/US11388626B2/en
Priority to SG11201911793VA priority patent/SG11201911793VA/en
Priority to EP18817544.2A priority patent/EP3641186A4/en
Publication of WO2018228289A1 publication Critical patent/WO2018228289A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/04—Error control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/189—Transmission or retransmission of more than one copy of a message
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0037—Inter-user or inter-terminal allocation
    • H04L5/0041—Frequency-non-contiguous
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0044—Arrangements for allocating sub-channels of the transmission path allocation of payload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks

Definitions

  • the present disclosure relates to the field of wireless communication technologies, and more particularly, to a base station, user equipment, and related methods of transmitting data in a state in which packet repetition is disabled.
  • NTT DOCOMO proposed a new research project on 5G technology standards (see Non-patent literature: RP-160671) :New SID Proposal: Study on New Radio Access Technology), and approved.
  • the goal of the research project is to develop a new wireless (New Radio: NR) access technology to meet all 5G application scenarios, requirements and deployment environments.
  • NR mainly has three application scenarios: Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC) and Ultra reliable and low latency communications (URLLC).
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • URLLC Ultra reliable and low latency communications
  • the multiple connections may employ mechanisms such as packet repetition or link selection.
  • the packet repetition function supporting the user plane and the control plane in the NR-PDCP entity is achieved, the PDCP entity function of the sender supports packet repetition, and the PDCP entity function of the receiver supports the deletion of the duplicate packet.
  • Packet Data Convergence Protocol PDCP
  • PDUs Packet Data Sheets
  • SDU Service Data Units
  • a method in a user equipment UE the UE operating in a carrier aggregation mode.
  • the method includes receiving a media access control MAC Control Element CE for de-enable packet repetition, transmitting data from a Packet Data Convergence Protocol PDCP entity to a Radio Link Control RLC entity, and at a MAC entity, only by grouping Transmitting the data in a cell or group of cells associated with the RLC entity in a re-enabled state, or by selecting a cell or group of cells from a set of cells or groups of cells pre-configured to the UE.
  • MAC Control Element CE for de-enable packet repetition
  • a method in a user equipment UE the UE operating in a multi-connection mode.
  • the method includes: receiving a medium access control MAC Control Element CE for deactivating packet repetition; and transmitting data only through a radio link control RLC entity or a logical channel corresponding to the primary cell group MCG; or only by The RLC entity or logical channel corresponding to the secondary cell group SCG transmits data; or transmits data through an RLC entity or a logical channel corresponding to the MCG and the SCG in a link selection manner.
  • the data is transmitted over an RLC entity or logical channel corresponding to a predefined one of the MCG or SCG.
  • the indication information carried in the MAC CE indicates that the data is to be sent by an RLC entity or a logical channel corresponding to the MCG or the SCG. According to the indication information, data is transmitted through an RLC entity or a logical channel corresponding to the MCG or SCG.
  • the method further comprises: receiving, by the radio resource control RRC signaling, a data transmission configuration, the data transmission configuration indicating whether to pass an RLC entity corresponding to the MCG or the SCG in a state where the packet repetition is disabled Logical channel to send data.
  • the data transmission configuration data is transmitted through an RLC entity or a logical channel corresponding to the MCG or SCG.
  • the MAC CE is received from a MAC entity corresponding to the MCG or SCG.
  • the RLC entity or logical channel corresponding to the MCG or the SCG transmits data.
  • the MAC CE is received from a MAC entity corresponding to only one cell group predefined in the MCG and the SCG, or the method further comprises: receiving, by the radio resource control RRC signaling, a MAC indicating that the MAC CE is sent. An indication of the entity, and determining, according to the indication identifier, that the MAC CE is received from a MAC entity corresponding to the MCG or the SCG.
  • a user equipment UE including a transceiver, a processor, and a memory, the processor storing instructions executable by the processor, such that the UE performs according to the first or the first The method described in the two aspects.
  • a method in a base station comprising: transmitting, to a user equipment UE, a medium access control MAC Control Element CE for enabling packet repetition.
  • the indication information carried by the MAC CE is used to indicate to the UE to transmit data by using a radio link control RLC entity or a logical channel corresponding to the primary cell group MCG or the secondary cell group SCG.
  • a base station comprising a transceiver, a processor and a memory, the processor storing instructions executable by the processor, such that the base station performs the method according to the fourth aspect above method.
  • Figure 1 shows a schematic diagram of packet repeating MCG split DRB data transmission
  • 2 is a schematic diagram showing packet repeated SCG split DRB data transmission
  • FIG. 3 is a schematic diagram showing a packet repetition bearer protocol architecture in a carrier aggregation scenario
  • FIG. 4 is a schematic diagram showing a packet repetition bearer protocol architecture in a dual connectivity scenario
  • FIG. 5 illustrates a flow chart of a method in a user equipment in accordance with an embodiment of the present disclosure
  • FIG. 6 shows a flowchart of a method in a user equipment according to another embodiment of the present disclosure
  • FIG. 7 shows a block diagram of a user equipment in accordance with an embodiment of the present disclosure
  • FIG. 8 shows a flow chart of a method in a base station according to an embodiment of the present disclosure
  • FIG. 9 shows a block diagram of a base station in accordance with an embodiment of the present disclosure.
  • RRC Radio Resource Control, radio resource control.
  • PDCP Packet Data Convergence Protocol, Packet Data Convergence Protocol.
  • the PDCP may represent NR or PDCP in LTE or eLTE, unless otherwise specified.
  • RLC Radio Link Control, radio link control.
  • the RLC may represent NR or RLC in LTE or eLTE, unless otherwise specified.
  • the RLC entity may be a UM RLC entity or an AM RLC entity.
  • the MAC Medium Access Control, media access control.
  • the MAC may represent a NR or a MAC in LTE or eLTE, unless otherwise specified.
  • DTCH Dedicated Traffic Channel, dedicated traffic channel.
  • CCCH Common Control Channel, common control channel.
  • DCCH Dedicated Control Channel, dedicated control channel.
  • PDU Protocol Data Unit, protocol data unit.
  • SDU Service Data Unit, service data unit.
  • data received from the upper layer or sent to the upper layer is referred to as an SDU
  • data transmitted to the lower layer or received from the lower layer is referred to as a PDU
  • the data received by the PDCP entity from the upper layer or the data sent to the upper layer is called a PDCP SDU
  • the data received by the PDCP entity from the RLC entity or the data sent to the RLC entity is called a PDCP PDU (ie, an RLC SDU).
  • MeNB corresponding to E-UTRAN or base station of LTE or eLTE
  • MgNB base station corresponding to 5G-RAN or NR
  • S1-MME control node mobility management entity
  • MeNB corresponding to E-UTRAN or base station of LTE or eLTE
  • MgNB base station corresponding to 5G-RAN or NR
  • S1-MME control node mobility management entity
  • the primary base station in the present disclosure is referred to as an MeNB. It should be noted that all embodiments or definitions applicable to the MeNB are also applicable to the MgNB.
  • Secondary base station Secondary eNB, denoted as SeNB (corresponding to E-UTRAN or base station of LTE or eLTE) or SgNB (base station corresponding to 5G-RAN or NR).
  • SeNB corresponding to E-UTRAN or base station of LTE or eLTE
  • SgNB base station corresponding to 5G-RAN or NR.
  • a base station that does not serve as an MeNB providing additional radio resources to the UE.
  • the secondary base stations in the present disclosure are all referred to as SeNBs. It should be noted that all embodiments or definitions applicable to the SeNB are also applicable to the SgNB.
  • Primary cell Primary Cell, PCell.
  • a cell of the present disclosure may also be referred to as a carrier.
  • Primary and secondary cells Primary Secondary Cell, PSCell.
  • the SCG cell that the UE is used to perform random access is performed in performing the process of changing the SCG.
  • Secondary cell Secondary Cell, SCell.
  • a cell operating on a secondary frequency that can be configured after the RRC connection is established and can be used to provide additional radio resources.
  • Cell group Cell Group, CG, in a multi-connection, a group of serving cells or carriers associated with a primary base station or a secondary base station.
  • a group of cells associated with a certain logical channel or RLC entity of a packet repetition bearer or a group of cells providing radio resources or data transmission services for a certain logical channel or RLC entity of a packet repetition bearer is called a cell.
  • the cell may be a cell configured with an uplink carrier.
  • the cell may also be referred to as a serving cell. It should be noted that the cell described in the present disclosure may also be referred to as a set of beam.
  • MCG Primary cell group
  • the MCG is composed of all serving cells; for a UE configured with multiple connections, the MCG is composed of a subset of serving cells (ie, a group of serving cells associated with the MeNB or the MgNB), which includes the PCell and 0 or 1 or more SCells.
  • Secondary cell group Secondary Cell Group, SCG.
  • SCG Secondary Cell Group
  • the SCG can contain one PSCell and can also contain one or more SCells.
  • Multi-connection The operation mode of the UE in the RRC connected state, where multiple cell groups are configured, the multiple cell groups include one MCG, 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, it is called dual connectivity. That is, a UE with multiple receivers and/or transmitters in a connected state is configured to use EUTRAN and/or 5G-RAN radio resources provided by a plurality of different schedulers, which may pass non-ideal backhaul ( Non-ideal backhaul) or ideal backhaul connection.
  • the multiple connections described in this disclosure include dual connections. Multi-connection data transmission methods include but are not limited to: packet repetition, link selection.
  • DRB Data Radio Bearer carrying user plane data
  • a data radio bearer carrying the user plane data or simply referred to as a data bearer.
  • the SRB Signalling Radio Bearer, signaling radio bearer.
  • the bearer may be used to transmit RRC messages and NAS messages or only to transmit RRC messages and NAS messages.
  • the SRB may include SRB0, SRB1, SRB1bis, and SRB2.
  • the SRB0 is used for the RRC message using the CCCH logical channel;
  • the SRB1 is used for the RRC message using the DCCH logical channel, and the RRC message may include the NAS message, and the SRB1 is also used to transmit the NAS message before the establishment of the SRB2.
  • the SRB1bis is used for the RRC message and the NAS message of the DCCH logical channel before the security activation, and the RRC message may include the NAS message.
  • SRB2 is used for RRC messages and NAS messages using DCCH logical channels, and the RRC messages include recorded measurement information (or measurement logs).
  • the SRB may be an MCG SRB or an SCG SRB.
  • the bearer in the present disclosure may be a DRB or an SRB.
  • the radio protocol is located at the MeNB (or MgNB) and the SeNB (or SgNB) and utilizes the bearers of the MeNB (or MgNB) and SeNB (or SgNB) resources simultaneously.
  • MCG separation DRB If the PDCP entity that separates the DRB is located at the primary base station (that is, the data first arrives at the primary base station and is forwarded by the primary base station to the secondary base station to implement data separation in the primary base station), it is called MCG separation DRB; if the PDCP entity separating the DRB is located at the secondary base station (The data arrives at the secondary base station first, and the secondary base station forwards it to the primary base station to implement data separation in the secondary base station.) This is called SCG separation DRB.
  • the separation DRB described in the present disclosure may be an MCG separation DRB or an SCG separation DRB.
  • the embodiments of the present disclosure are also applicable to a scenario in which the MCG split DRB and the SCG split DRB are not distinguished, that is, the radio protocol of the split DRB is located in the MeNB (or MgNB) and the SeNB (or SgNB) and simultaneously utilizes the MeNB (or MgNB) and The bearer DRB of the SeNB (or SgNB) resource.
  • the radio protocol is located at the MeNB (or MgNB) and the SeNB (or SgNB) and utilizes the bearers of the MeNB (or MgNB) and SeNB (or SgNB) resources simultaneously.
  • the PDCP entity separating the SRB and/or the RRC are located in the primary base station (ie, signaling, which may also be referred to as data, forwarded by the primary base station to the secondary base station, and signaling is separated in the primary base station), it is referred to as MCG separation SRB;
  • the PDCP entity and/or the RRC that separates the SRBs are located in the secondary base station (ie, signaling, which may also be referred to as data, and is forwarded by the secondary base station to the primary base station to implement signaling separation in the secondary base station), and is referred to as an SCG separation SRB.
  • the isolated SRB described in the present disclosure may be an MCG separation SRB or an SCG separation SRB.
  • the embodiments of the present disclosure are also applicable to a scenario in which the MCG split SRB and the SCG split SRB are not distinguished, that is, the radio protocol of the split SRB is located at the MeNB (or MgNB) and the SeNB (or SgNB) and simultaneously utilizes the MeNB (or MgNB) and The SeNB (or SgNB) resource carries the SRB.
  • the separation carrier may be a separate SRB or a separate DRB.
  • Packet repetition may also be referred to as data repetition or packet repetition or PDCP repetition or PDCP PDU repetition or PDCP SDU repetition or PDCP packet repetition (the data described in the present disclosure may be control plane signaling or user plane data, unless otherwise specified, Corresponding to SRB signaling and DRB data respectively).
  • the same data or packet or packet, that is, PDCP PDU or PDCP SDU
  • the same data is transmitted in multiple CG serving cells, that is, the same data uses both the primary base station (or MCG) and the secondary base station (or SCG).
  • the provided resource transmission or the same data is sent to the lower layer (or RLC layer) located at the MCG and SCG or the PDCP entity sends the same PDCP PDU to the associated multiple lower layer entities (or RLC entities) or the same data in multiple different
  • the bearer is sent on.
  • the PDCP entity sends duplicate (or the same) PDCP PDUs to the associated two or more RLC entities (or lower layer entities) and/or logical channels, and the MAC entities pass different
  • the carrier (which may also be referred to as a cell or serving cell) is sent to the receiving end; the receiving PDCP entity is responsible for detecting and deleting duplicate PDCP PDUs or SDUs.
  • the PDCP entity sends the same packet (ie PDCP PDU or PDCP SDU) to only one RLC entity, and different packets can be sent through different RLC entities.
  • the PDCP entity sends the packet to one of the associated multiple RLC entities.
  • the PDCP entity selects one cell group from the configured cell group for packet transmission, that is, the PDCP entity sends the packet to the RLC entity associated with the MCG or the RLC entity associated with the SCG.
  • Each data utilizes only the resources of the MeNB or SeNB.
  • each PDCP PDU is sent to the receiver through only one RLC entity.
  • Repeating Logical Channels In the present invention, a logical channel corresponding to the same PDCP entity or used to transmit the same data or the same packet repeat bearer is referred to as a repeating logical channel.
  • Packet Repeat Bearer A bearer that supports packet repetition in carrier aggregation or single-link mode, including packet repetition SRB and packet repetition DRB.
  • One PDCP entity of the bearer is associated to two or more RLC entities, two or more logical channels, and one MAC entity and the transmitting PDCP entity sends duplicate (or the same) PDCP PDUs to the two or more RLC entities (or lower layer entities) and/or two or more logical channels are sent by the MAC entity to the receiving end through different carriers (ie, cells or serving cells); the receiving end PDCP entity will repeat from the lower layer entities The PDCP PDU or SDU is removed.
  • Packet Repeat Separation Bearer In the multi-connection mode, separate bearers supporting packet repetition are supported. In the transmission mode, the same data is transmitted on multiple radio protocols of the split bearer, including a packet repeat MCG split SRB, a packet repeat SCG split SRB, a packet repeat MCG split DRB, and a packet repeat SCG split DRB. If it is a packet repeating MCG split bearer, the PDCP entity located at the primary base station or MCG is responsible for packet repetition and/or repeated packet removal; if it is a packet repeat SCG split bearer, the PDCP entity located at the secondary base station or SCG is responsible for packet repetition. (ie, send PDCP PDUs to two or more RLC entities) and/or repeat packet removal.
  • FIG. 1 is a schematic diagram showing downlink packet repeating MCG split DRB transmission between a base station and a user equipment UE in dual connectivity. It should be understood that the same protocol architecture may be adopted for performing uplink packet repeating MCG split DRB transmission between the base station and the UE, except that data is transmitted from the UE to the base station, that is, the arrow in FIG. 1 is reversed. As shown in FIG. 1, data (eg, a Packet Data Convergence Protocol Data Unit (PDCP PDU)) is transmitted on multiple radio protocols (corresponding to a plurality of RLC entities associated with the same PDCP entity) separating the DRBs, utilizing the MeNB and SeNB resources.
  • PDCP PDU Packet Data Convergence Protocol Data Unit
  • each PDCP PDU is sent to the receiver through multiple RLC entities.
  • the interface between the MeNB and the SeNB can be written as Xn or Xx or X2.
  • the interfaces may be named differently depending on the type of MeNB and SeNB. For example, if the MeNB is an LTE eNB, the SeNB is a gNB, the interface is denoted as Xx, and if the MeNB is a gNB and the SeNB is an eLTE eNB, the interface is denoted as Xn.
  • the packet repetition MCG separation SRB adopts a similar protocol architecture, except that the upper layer entity that sends data to the PDCP entity is RRC, and the PDCP entity sends the data from the lower layer entity to the upper layer RRC entity.
  • FIG. 2 shows a schematic diagram of downlink packet repeat SCG split DRB transmission between a base station and a user equipment UE in dual connectivity.
  • the same protocol architecture may be adopted for uplink packet repeating SCG split DRB transmission between the base station and the UE, except that data is transmitted from the UE to the base station, that is, the arrow in FIG. 2 is reversed.
  • data eg, a Packet Data Convergence Protocol Protocol Data Unit (PDCP PDU)
  • PDCP PDU Packet Data Convergence Protocol Protocol Data Unit
  • each PDCP PDU is sent to the receiver through multiple RLC entities.
  • the interface between the MeNB and the SeNB can be written as Xn or Xx or X2.
  • the interfaces may be named differently depending on the type of MeNB and SeNB. For example, if the MeNB is an LTE eNB, the SeNB is a gNB, the interface is denoted as Xx, and if the MeNB is a gNB and the SeNB is an eLTE eNB, the interface is denoted as Xn.
  • the packet repetition SCG separation SRB adopts a similar protocol architecture, except that the upper layer entity that sends data to the PDCP entity is RRC, and the PDCP entity sends the data from the lower layer entity to the upper layer RRC entity.
  • Some embodiments of the present disclosure take the case that the data packet PDCP PDU or the SDU is repeatedly sent twice (that is, one PDCP entity associates two RLC entities and/or two logical channels), but the technical solution described in the present disclosure is not limited to the data packet.
  • a scenario in which a PDCP PDU or an SDU is repeatedly transmitted twice can be easily extended by those skilled in the art to repeatedly transmit multiple scenarios (ie, one PDCP entity associates multiple RLC entities and/or multiple logical channels).
  • FIG. 3 is a schematic diagram of a protocol architecture of a packet repeat bearer in a carrier aggregation scenario.
  • a PDCP entity of one DRB is associated with two RLC entities and two logical channels, one MAC entity.
  • the RRC entity and the PDCP entity of one SRB are associated with two RLC entities and two logical channels and one MAC entity.
  • Figure 4 shows the protocol architecture of the packet repeat bearer in the dual connectivity scenario.
  • the PDCP entity of one DRB is associated with two RLC entities and two logical channels and two MAC entities.
  • the RRC entity and the PDCP entity of one SRB are associated with two RLC entities and two logical channels and two MAC entities.
  • the packet repeat bearer or the packet repeat split bearer may enable all packet repeat bearers or packet repeat split bearer PDCP packet repetitions when the initial configuration may be in the de-enabled state or when the de-enabled MAC CE is received.
  • the MAC CE used to disable PDCP packet repetition is referred to as de-enabled MAC CE. Since the MAC CE for enabling PDCP packet repetition and the MAC CE for deactivating PDCP packet repetition can use the same MAC CE, the MAC CE used to disable PDCP packet repetition is also referred to as enable/ Go to enable MAC CE.
  • enabling/disabling one or more fields in the MAC CE to indicate whether to enable or disable all packet bearers and/or packet repetition of separate bearers or by enabling/disabling one or more of the MAC CEs
  • Fields to indicate whether enabling or disabling one or more packet bearers and/or packet repeating separate bearers or by enabling/disabling MAC CE one or more fields to indicate whether MAC CE is enabled or not enabled MAC CE.
  • the enable/disable MAC CE is applied to all packet repeat bearers and packet repeat split bearers.
  • the UE receives the enable/disable MAC CE, it enables/disables all packet repeat bearers and packet repeat split bearer PDCP packet repetitions.
  • MAC CE Define two enabling/disabling MAC CEs for packet repeat bearer and packet repeat split bearer respectively.
  • a field is defined in the enable/disable MAC CE to indicate whether enabling/disabling the MAC CE is for a packet repeat bearer or for a packet repeat split bearer.
  • a UE that is configured with both a packet repeat bearer and a packet repeat split bearer, when receiving/disabling the MAC CE for the packet repeat bearer, enabling/disabling the PDCP packet repetition of all the packet repeat bearers; when receiving The MAC CE is enabled/disabled for the packet to be separated from the bearer, and the PDCP packet repetition of all the packets is separated/disabled.
  • the indication information that is used to distinguish the bearer is carried in the enabling/disabling MAC CE, and the indication information may be a bearer identifier or a logical channel identifier or a bitmap corresponding to the bearer (each bit in the bitmap) A packet repeating bearer or a packet repeating split bearer.
  • the corresponding bit in the bitmap is 0, it indicates that the PDCP packet repetition of the corresponding bearer is disabled.
  • the corresponding bit in the bitmap is 1, it indicates that the PDCP packet repeat of the corresponding bearer is enabled.
  • bitmap corresponding to the logical channel each bit in the bitmap corresponds to a logical channel in which the packet bearer is associated with the logical channel or the packet is separated from the logical channel associated with the bearer.
  • the corresponding bit in the bitmap When the corresponding bit in the bitmap is 0, it indicates The PDCP packet repetition corresponding to the bearer is disabled.
  • the corresponding bit in the bitmap When the corresponding bit in the bitmap is 1, it indicates that the PDCP packet corresponding to the bearer is enabled, and vice versa.
  • the UE receives the enable/disable MAC CE the PDCP packet repetition of the corresponding bearer is enabled/disabled according to the indication information in the MAC CE.
  • the PDCP packet repetition may be disabled when the initial configuration packet repeat bearer or the packet repeat split bearer is initially enabled, or may be due to receipt.
  • Enable/disable MAC CE to disable PDCP packet repetition.
  • the UE when the UE receives the enable/disable MAC CE, the UE enables or disables all the packets according to the received MAC CE.
  • the repeated bearer or packet repeats the split bearer or enables or disables the packet repeat bearer or packet repeat split bearer specified in the MAC CE.
  • the MAC entity For the logical channel corresponding to the packet repetition bearer, after the PDCP packet is repeated, the MAC entity adds the uplink resource UL Grant of the data from the logical channel corresponding to the packet repeated bearer to the cell in the associated cell or the associated cell group. That is, the new transmission is transmitted; in other words, the MAC entity cannot transmit the data from the logical channel corresponding to the packet repeated bearer on the uplink resource UL Grant of the cell that is not the associated cell or the cell that does not belong to the associated cell group.
  • the MAC entity transmits the data of the logical channel corresponding to the packet repeat bearer on the UL Grant of all cells.
  • the MAC entity sends the data from the logical channel or the bearer through the UL Grant to indicate that, in the new transmission, the MAC entity will come from the Logical Channel Prioritization Procedure (LCP).
  • LCP Logical Channel Prioritization Procedure
  • the data of the packet repeating bearer or the packet repeatedly separating the bearer corresponding to the logical channel and the data from the other logical channel are multiplexed with the same MAC PDU according to the multiplexing manner defined by the LCP.
  • the UL Grant from the cell or cell group associated with the packet repeat bearer or the packet repeat split bearer can only be used to transmit data from the packet repeat bearer or the packet repeat split bearer, ie from association to packet repeat bearer or packet repeat Separating the UL Grant of the bearer cell or the cell group, the MAC entity multiplexes the same MAC PDU or transmits the data from the logical channel corresponding to the packet repeat bearer or the packet repeat split bearer according to the multiplexing manner defined by the LCP.
  • FIG. 5 shows a flow diagram of a method 500 in a user equipment UE in accordance with an embodiment of the disclosure.
  • the method 500 involves disabling the manner in which data is transmitted after the PDCP packet is repeated in carrier aggregation. Accordingly, the UE operates in a carrier aggregation mode.
  • Method 500 includes the following steps.
  • a media access control MAC Control Element CE for de-enable packet repetition is received.
  • step S520 data is transmitted from the packet data convergence protocol PDCP entity to a radio link control RLC entity.
  • step S530 at the MAC entity, only by the cell or group of cells associated with the RLC entity in the state of packet repetition enabled, or by the cell selected from the set of cells or groups of cells pre-configured to the UE or The cell group sends the data.
  • the PDCP entity after the PDCP packet repetition is disabled, the PDCP entity sends the PDCP PDU to an RLC entity and sends it to the MAC entity through the logical channel.
  • the MAC entity After receiving the data from the repeated logical channel, the MAC entity transmits the data through a cell or group of cells associated with the repeated logical channel. That is, for a packet repeat bearer, the MAC entity cannot transmit data from the logical channel corresponding to the bearer through an uplink resource (UL Grant) that is not associated with the cell or cell group of the logical channel.
  • UL Grant uplink resource
  • RLC1/LCH1 the packet repetition function of DRB1 is disabled, all PDCP PDUs can only be sent through RLC1 and using the UL Grant of the cell group associated with RLC1/LCH1.
  • the PDCP entity after the PDCP packet repetition is disabled, the PDCP entity sends the PDCP PDU to an RLC entity and sends it to the MAC entity through the logical channel.
  • the MAC entity may send data from the logical channel over any uplink resource (UL Grant). That is, after the de-enable packet repetition, the data from the corresponding packet repeated bearer or the data from the logical channel associated with the corresponding packet repeat bearer may be sent on the UL Grant provided by any cell configured for the UE or the MAC entity may be at any In the new transmission, data corresponding to the packet repeated bearer or data from the logical channel associated with the corresponding packet repeat bearer is multiplexed to the MAC PDU according to the procedure defined by the LCP.
  • UL Grant uplink resource
  • all PDCP PDUs can only be sent through RLC1 and using the UL Grant of PCell and CG.
  • the PDCP entity sends the same PDCP PDU to one of the associated RLC entities and/or logical channels and transmits through the associated cell or cell group, ie, a PDCP.
  • the PDU can be selected to be sent by any associated RLC entity.
  • the manner in which the PDCP PDU is sent by the PDCP entity after the PDCP packet is re-enabled is configured by the RRC signaling, that is, the RRC signaling carries an indication information, where the indication information is used to indicate that the PDCP packet is disabled.
  • the way in which data is transmitted after repetition ie, which RLC entity the PDCP PDU is sent).
  • the sending manner may be that all PDCP PDUs are sent through one RLC entity or a logical channel (in this case, the value of the indication information is a logical channel identifier, indicating that the fire is enabled to enable the logical channel), and the two RLC entities or logics are used.
  • the channel is transmitted but the same PDCP PDU is only sent to one of the RLC entities.
  • the UE receives the enable/disable MAC CE, according to the indication information carried in the RRC signaling, after the PDCP packet is deactivated, the PDCP PDU is sent according to the manner defined by the indication information.
  • FIG. 6 shows a flow diagram of a method 600 in a user equipment UE in accordance with an embodiment of the disclosure.
  • the method 600 involves disabling the manner in which the PDCP packet is repeated after the data is transmitted in the multiple connections. Accordingly, the UE operates in a multi-connection mode.
  • Method 600 includes the following steps.
  • a media access control MAC Control Element CE for de-enable packet repetition is received.
  • step S620 data is transmitted only through the radio link control RLC entity or logical channel corresponding to the primary cell group MCG.
  • step S620 data is transmitted only through the RLC entity or logical channel corresponding to the secondary cell group SCG.
  • step S630 data is transmitted through an RLC entity or a logical channel corresponding to the MCG and the SCG in a link selection manner.
  • the data is transmitted over an RLC entity or logical channel corresponding to a predefined one of the MCG or SCG.
  • the data transmission manner after the PDCP packet is repeated is predefined.
  • the PDCP PDU is only sent through the MCG after the PDCP packet is repeatedly enabled.
  • the PDCP PDU is only sent through the SCG after the PDCP packet is repeatedly enabled.
  • the PDCP PDU is only defined after the PDCP packet is disabled.
  • the packet repeating split bearer After being sent by the MCG or the SCG (that is, after the packet repetition is disabled, the packet repeating split bearer adopts the data transmission manner of the split bearer, and the same PDCP PDU is not simultaneously sent to the RLC entity corresponding to the MCG and the SCG but only to one of the two. Or; pre-defined to enable PDCP packet repetition, PDCP PDU can only be sent through the RLC entity corresponding to a specific cell group (MCG or SCG), which is the user plane (corresponding packet repeated separation DRB) or control plane The cell group (or the cell group in which the corresponding PDCP is located) terminated (corresponding to the packet repeatedly separating the SRB).
  • MCG or SCG specific cell group
  • the cell group or the cell group in which the corresponding PDCP is located
  • the PDCP packet repetition is disabled, and the PDCP PDU is sent in a predefined manner.
  • the UE is enabled to enable/disable the MAC CE
  • the logical channel corresponding to the SCG or SCG or the RLC entity corresponding to the SCG is disabled.
  • the PDCP entity sends the PDCP PDU to the logical channel or MCG corresponding to the MCG.
  • Corresponding RLC entity or MCG corresponding RLC entity or MCG.
  • the PDCP PDU sends the PDCP PDU to the logical channel corresponding to the SCG or The RLC entity or SCG corresponding to the SCG.
  • the indication information carried in the MAC CE indicates that the data is to be sent through an RLC entity or a logical channel corresponding to the MCG or the SCG. According to the indication information, data is transmitted through an RLC entity or a logical channel corresponding to the MCG or SCG. Specifically, the indication information is carried in the enabling/disabling MAC CE to indicate that the data transmission mode after the PDCP packet is repeated is enabled.
  • the PDCP PDU is sent only through the MCG after the MAC CE is instructed to disable the PDCP packet repetition; or the PDCP PDU is sent only through the SCG after the MAC CE is instructed to disable the PDCP packet repetition; or, the MAC CE indicates After the PDCP packet is enabled, the PDCP PDU is sent only through the MCG or the SCG (that is, the transmission mode of the split bearer data is used, and the same PDCP PDU is not sent to the RLC entity corresponding to the MCG and the SCG at the same time); or, the MAC CE is instructed to enable After the PDCP packet can be repeated, the PDCP PDU can only be transmitted through the RLC entity corresponding to the specific cell group (MCG or SCG), which is terminated by the user plane (corresponding packet repeated separation DRB) or the control plane (corresponding packet repeated separation SRB) The cell group (or the cell group where the corresponding PDCP is located).
  • MCG or SCG specific cell group
  • the indication information may be a logical channel identifier or a cell group identifier (for example, an MCG or an SCG), and correspondingly enable or disable a corresponding logical channel or a logical channel corresponding to a cell group or a cell group.
  • the data transmission configuration is received via RRC signaling, the data transmission configuration indicating that the RLC entity or the logical channel corresponding to the MCG or the SCG is to be transmitted in a state where the packet repetition is disabled.
  • data is transmitted through an RLC entity or a logical channel corresponding to the MCG or SCG.
  • the PDCP packet repeating data transmission mode is disabled by using RRC signaling configuration.
  • the RRC signaling carries an indication information, where the indication information is used to indicate the manner of sending data after the PDCP packet is re-enabled (ie, which RLC entity the PDCP PDU is sent).
  • the sending manner may be that after the PDCP PDU is repeatedly enabled, the PDCP PDU is sent only through the MCG (that is, the RLC entity corresponding to the MCG), and the PDCP PDU is only transmitted through the SCG (that is, the RLC entity corresponding to the SCG).
  • the PDCP PDU is sent only through the MCG or the SCG (that is, the RLC entity corresponding to the MCG or the SCG).
  • the same PDCP PDU is not sent to the RLC entity corresponding to the MCG and the SCG at the same time.
  • the PDCP PDU can only be sent through the RLC entity corresponding to the specific cell group (MCG or SCG), which is the user plane (corresponding packet repeated separation DRB) or control plane (corresponding packet repetition) Separate the SRB) terminated cell group (or the corresponding cell group where the PDCP is located)
  • MCG specific cell group
  • SCG specific cell group
  • DRB user plane
  • control plane corresponding packet repetition
  • the PDCP PDU When the UE receives the enable/disable MAC CE, the PDCP PDU is disabled and the PDCP PDU is sent to the MCG according to the indication information according to the indication information carried in the received RRC signaling.
  • the RLC entity corresponding to the SCG of the corresponding RLC entity is sent.
  • RRC signaling described in this disclosure may be an RRC reconfiguration message.
  • the MAC CE is received from a MAC entity corresponding to the MCG or SCG.
  • the data is transmitted by the RLC entity or logical channel corresponding to the MCG or the SCG according to whether the MAC CE is received from a MAC entity corresponding to the MCG or the SCG.
  • the data is selected to be transmitted through an RLC entity or a logical channel corresponding to the MCG or the SCG according to the indication information carried in the MAC CE.
  • the MAC CE is received from a MAC entity corresponding to only one cell group predefined in the MCG and SCG.
  • the method 600 further includes receiving, by the radio resource control RRC signaling, an indication identifier indicating a MAC entity transmitting the MAC CE, and determining, according to the indication identifier, whether to receive the MAC entity corresponding to the MCG or the SCG. MAC CE.
  • the MAC entity that enables/disables the MAC CE is described below with reference to a specific example.
  • Example 1 Both the MCG MAC entity and the SCG MAC entity can send/disable MAC CE.
  • the corresponding duplicate logical channel is disabled, that is, the PDCP entity corresponding to the packet repeated split bearer no longer has the PDCP PDU.
  • the packet repeating split bearer corresponding PDCP entity sends data to the logical channel or RLC entity corresponding to another MAC entity or the MAC function that receives/disables the MAC CE will disable the corresponding logical channel or RLC entity. .
  • the PDCP entity sends the PDCP PDU to the RLC entity corresponding to the SCG; if the MAC entity corresponding to the SCG receives the MAC entity After the PDCP packet is enabled/disabled to enable the MAC CE, the PDCP entity sends the PDCP PDU to the RLC entity corresponding to the MCG.
  • the MAC entity corresponding to a certain cell group receives the enable/disable MAC CE
  • the other repeated logical channel is disabled, that is, the PDCP PDU corresponding to the PDCP PDU corresponding to the packet repetition split bearer is removed.
  • Sending to the logical channel or the RLC entity corresponding to the MAC entity in other words, the PDCP entity corresponding to the packet repetition split bearer sends data to the logical channel or RLC entity corresponding to the MAC entity or receives/disables the MAC CE.
  • the MAC entity will instruct another MAC entity to enable its corresponding logical channel or RLC entity.
  • the PDCP entity sends the PDCP PDU to the RLC entity corresponding to the MCG; if the MAC entity corresponding to the SCG receives the MAC entity After the PDCP packet is enabled/disabled to enable the MAC CE, the PDCP entity sends the PDCP PDU to the RLC entity corresponding to the SCG.
  • Example 2 Pre-defined MCG MAC entity or SCG MAC entity send enable/disable MAC CE
  • the UE can only enable/disable the MAC CE through the MAC entity corresponding to the MCG or the SCG; or, the cell group in which the predefined PDCP entity is located can enable/disable the MAC CE; or, the predefined control plane
  • the cell group that is terminated (for the packet repeatedly separating the SRB) or the user plane (for the packet repeatedly separating the DRB) is enabled/disabled to the MAC CE.
  • the UE when the PDCP entity is located in the MCG, the UE receives the enable/disable MAC CE from the MAC entity corresponding to the MCG; when the PDCP entity is located in the SCG, the UE receives the enable/disable MAC from the MAC entity corresponding to the SCG.
  • CE the enable/disable MAC
  • the cell group in which the control plane terminates refers to a cell group connected to the core network MME or a cell group to which the corresponding base station is connected to the MME, such as S1-C or NR in LTE/LTE-A.
  • the user group terminated by the user plane in the present invention refers to a cell group connected to the gateway or a corresponding cell group connected to the gateway, such as LTE/LTE a group of cells terminated by NG-U in S1-U or NR in -A or a group of cells corresponding to the base station.
  • Example 3 Instructing to send a MAC entity that enables/disables MAC CE through RRC signaling
  • the RRC signaling carries an indication identifier, where the indication identifier is used to indicate a MAC entity corresponding to a cell group or a cell group that enables or disables the MAC CE.
  • the indication identifier is used to indicate a MAC entity corresponding to a cell group or a cell group that enables or disables the MAC CE.
  • the MCG MAC entity sends an enable/disable MAC CE;
  • the SCG MAC entity sends an enable/disable MAC CE.
  • the PDCP PDU repetition or packet bearer that enables packet repetition also referred to as PDCP packet repetition or packet repetition bearer packet repetition or PDCP PDU repetition or PDCP SDU repetition or PDCP repetition or packet repetition bearer PDCP repetition or packet bearer in the present disclosure
  • the PDCP SDU repetition may also be expressed as a PDCP entity transmitting the same PDCP PDU or PDCP SDU to the associated two or more lower layer entities (or RLC entities and/or logical channels), ie, the same PDCP PDU through the associated two The cell or cell group is sent. If the packet is a duplicate bearer, the packet repeat function is enabled such that the same PDCP PDU is sent through the MCG and SCG.
  • the de-enable packet repetition function may also be expressed as configuring the PDCP entity to send the same PDCP PDU to one or all of the two associated lower layer entities (or RLC entities and/or logical channels) through only two or One of a plurality of lower layer entities (or RLC entities and/or logical channels) is transmitted.
  • the packet repetition described in the present disclosure refers to an uplink packet repetition.
  • FIG. 7 shows a block diagram of a UE 700 in accordance with an embodiment of the disclosure.
  • the UE 700 includes a transceiver 710, a processor 720, and a memory 730 that stores instructions executable by the processor 720 such that the user equipment 700 performs the method described above in connection with FIG. 500 or method 600 as described in connection with FIG.
  • the processor 730 stores instructions executable by the processor 720, such that the user equipment 700 receives a media access control MAC control element CE for de-enable packet repetition; from a packet data convergence protocol PDCP entity a radio link control RLC entity transmitting data; and at the MAC entity, only by a cell or group of cells associated with the RLC entity in a state of packet repetition enabled, or by a cell or cell pre-configured to the UE The selected cell or group of cells in the group set transmits the data.
  • a media access control MAC control element CE for de-enable packet repetition
  • PDCP entity a radio link control RLC entity transmitting data
  • the MAC entity only by a cell or group of cells associated with the RLC entity in a state of packet repetition enabled, or by a cell or cell pre-configured to the UE
  • the selected cell or group of cells in the group set transmits the data.
  • the processor 730 stores instructions executable by the processor 720 such that the user equipment 700 receives a medium access control MAC Control element CE for de-enablement packet repetition; and only through the primary cell group
  • the radio link corresponding to the MCG controls the RLC entity or the logical channel to transmit data; or transmits data only through the RLC entity or logical channel corresponding to the secondary cell group SCG; or corresponds to the MCG and the SCG by using the link selection manner The RLC entity or logical channel to send data.
  • the data is transmitted over an RLC entity or logical channel corresponding to a predefined one of the MCG or SCG.
  • the indication information carried in the MAC CE indicates that the data is to be sent by an RLC entity or a logical channel corresponding to the MCG or the SCG. According to the indication information, data is transmitted through an RLC entity or a logical channel corresponding to the MCG or SCG.
  • the method further comprises: receiving, by the radio resource control RRC signaling, a data transmission configuration, the data transmission configuration indicating whether to pass an RLC entity corresponding to the MCG or the SCG in a state where the packet repetition is disabled Logical channel to send data.
  • the data transmission configuration data is transmitted through an RLC entity or a logical channel corresponding to the MCG or SCG.
  • the MAC CE is received from a MAC entity corresponding to the MCG or SCG.
  • the RLC entity or logical channel corresponding to the MCG or the SCG transmits data.
  • the MAC CE is received from a MAC entity corresponding to only one cell group predefined in the MCG and the SCG, or the method further comprises: receiving, by the radio resource control RRC signaling, a MAC indicating that the MAC CE is sent. An indication of the entity, and determining, according to the indication identifier, that the MAC CE is received from a MAC entity corresponding to the MCG or the SCG.
  • FIG. 8 is a flow chart showing a method 800 in a base station in accordance with an embodiment of the disclosure. As shown, method 800 includes the following steps.
  • a media access control MAC Control Element CE for de-enable packet repetition is transmitted to the user equipment UE.
  • the indication information carried by the MAC CE is used to indicate to the UE to transmit data by using a radio link control RLC entity or a logical channel corresponding to the primary cell group MCG or the secondary cell group SCG.
  • the data transmission configuration may be sent to the UE via radio resource control RRC signaling, the data transmission configuration indicating that the UE is to pass an RLC entity or a logical channel corresponding to the MCG or the SCG in a state where the packet repetition is disabled. send data.
  • RRC radio resource control
  • an indication identifier indicating a MAC entity that sends the MAC CE may be sent to the UE via the radio resource control RRC signaling.
  • FIG. 9 shows a block diagram of a base station 900 in accordance with an embodiment of the present disclosure.
  • base station 900 includes a transceiver 910, a processor 920, and a memory 930 that stores instructions executable by the processor 920 such that the base station 900 performs the method 800 described above in connection with FIG. .
  • the processor 930 stores instructions executable by the processor 920 such that the base station 900 transmits a media access control MAC Control Element CE for enabling packet repetition to the user equipment UE.
  • the indication information carried by the MAC CE is used to indicate to the UE to transmit data by using a radio link control RLC entity or a logical channel corresponding to the primary cell group MCG or the secondary cell group SCG.
  • the processor 930 may store instructions executable by the processor 920 such that the base station 900 transmits a data transmission configuration to the UE via radio resource control RRC signaling, the data transmission configuration indicating that the packet repetition is disabled. In the state, the UE transmits data through an RLC entity or a logical channel corresponding to the MCG or the SCG.
  • the processor 930 may store instructions executable by the processor 920 such that the base station 900 transmits an indication identifier indicating a MAC entity transmitting the MAC CE to the UE via radio resource control RRC signaling.
  • Computer executable instructions or programs running on a device in accordance with the present invention may be a program that causes a computer to implement the functions of an embodiment of the present invention by controlling a central processing unit (CPU).
  • the program or information processed by the program may be temporarily stored in a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memory system.
  • Computer-executable instructions or programs for implementing the functions of various embodiments of the present invention may be recorded on a computer readable storage medium.
  • the corresponding functions can be realized by causing the computer system to read programs recorded on the recording medium and execute the programs.
  • the so-called "computer system” herein may be a computer system embedded in the device, and may include an operating system or hardware (such as a peripheral device).
  • the "computer readable storage medium” may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a recording medium of a short-term dynamic storage program, or any other recording medium readable by a computer.
  • circuitry e.g., monolithic or multi-chip integrated circuits.
  • Circuitry designed to perform the functions described in this specification can include general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, discrete Gate or transistor logic, discrete hardware components, or any combination of the above.
  • DSPs digital signal processors
  • ASICs application specific integrated circuits
  • FPGAs field programmable gate arrays
  • a general purpose processor may be a microprocessor or any existing processor, controller, microcontroller, or state machine.
  • the above circuit may be a digital circuit or an analog circuit.
  • One or more embodiments of the present invention may also be implemented using these new integrated circuit technologies in the context of new integrated circuit technologies that have replaced existing integrated circuits due to advances in semiconductor technology.
  • the present invention is not limited to the above embodiment. Although various examples of the embodiments have been described, the invention is not limited thereto.
  • Fixed or non-mobile electronic devices installed indoors or outdoors can be used as terminal devices or communication devices such as AV devices, kitchen devices, cleaning devices, air conditioners, office equipment, vending machines, and other home appliances.

Landscapes

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

Abstract

本公开提供了一种用户设备UE中的方法，所述UE操作在载波聚合模式。所述方法包括：接收用于去使能分组重复的媒体访问控制MAC控制元素CE；从分组数据汇聚协议PDCP实体向一个无线链路控制RLC实体发送数据；以及在MAC实体处，仅通过在分组重复使能的状态中与所述RLC实体相关联的小区或小区组，或者通过从预先配置给UE的小区或小区组集合中选择的小区或小区组，发送所述数据。

Description

基站、用户设备和相关方法 技术领域
本公开涉及无线通信技术领域，更具体地，本公开涉及基站、用户设备和相关的在分组重复去使能的状态下发送数据的方法。
背景技术
2016年3月，在第三代合作伙伴计划(3rd Generation Partnership Project：3GPP)RAN#71次全会上，NTT DOCOMO提出了一个关于5G技术标准的新的研究项目(参见非专利文献：RP-160671：New SID Proposal：Study on New Radio Access Technology)，并获批准。该研究项目的目的是开发一个新的无线(New Radio：NR)接入技术以满足5G的所有应用场景、需求和部署环境。NR主要有三个应用场景：增强的移动宽带通信(Enhanced mobile broadband：eMBB)、大规模机器类通信(massive Machine type communication：mMTC)和超可靠低延迟通信(Ultra reliable and low latency communications：URLLC)。
在2016年10月召开的3GPP RAN2#96次会议上达成为满足URLLC对可靠性的要求，对多连接(包括双连接)进行研究。所述多连接可以采用分组重复或链路选择等机制。在2017年1月召开的3GPP NR AdHoc会议上达成在NR-PDCP实体中支持用户面和控制面的分组重复功能，发送端PDCP实体功能支持分组重复，且接收端PDCP实体功能支持删除重复包。在2017年2月召开的3GPP RAN2#97次会议上达成在上行和下行均支持：在载波聚合中，分组重复采用分组数据汇聚协议(PDCP)协议数据单(PDU)和/或服务数据单元(SDU)在两个或多个逻辑信道上发送并使得重复的PDCP PDU通过不同的载波发送。在2017年4月召开的3GPP RAN2#98次会议上达成无线资源控制RRC配置将2个重复的逻辑信道映射到不同的载波(Carrier)，即重复的逻辑信道不能映射到同一个载波。
期望解决在支持分组重复的载波聚合和多连接场景下与分组重复去使能相关的问题。
发明内容
根据本公开的第一方面，提供了一种用户设备UE中的方法，所述UE操作在载波聚合模式。所述方法包括：接收用于去使能分组重复的媒体访问控制MAC控制元素CE；从分组数据汇聚协议PDCP实体向一个无线链路控制RLC实体发送数据；以及在MAC实体处，仅通过在分组重复使能的状态中与所述RLC实体相关联的小区或小区组，或者通过从预先配置给UE的小区或小区组集合中选择的小区或小区组，发送所述数据。
根据本公开的第二方面，提供了一种用户设备UE中的方法，所述UE操作在多连接模式。所述方法包括：接收用于去使能分组重复的媒体访问控制MAC控制元素CE；以及仅通过与主小区组MCG相对应的无线链路控制RLC实体或逻辑信道来发送数据；或者仅通过与辅小区组SCG相对应的RLC实体或逻辑信道来发送数据；或者采用链路选择方式通过与MCG和SCG相对应的RLC实体或逻辑信道来发送数据。
在实施例中，通过与MCG或SCG中预定义的一个相对应的RLC实体或逻辑信道来发送数据。
在实施例中，所述MAC CE中携带的指示信息，所述指示信息指示要通过与MCG还是SCG相对应的RLC实体或逻辑信道来发送数据。根据所述指示信息，通过与MCG或SCG相对应的RLC实体或逻辑信道来发送数据。
在实施例中，所述方法还包括：经由无线资源控制RRC信令接收数据发送配置，所述数据发送配置指示在去使能分组重复的状态下要通过与MCG还是SCG相对应的RLC实体或逻辑信道来发送数据。根据所述数据发送配置，通过与MCG或SCG相对应的RLC实体或逻辑信道来发送数据。
在实施例中，所述MAC CE是从与MCG或SCG相对应的MAC实体接收的。根据从与MCG还是SCG相对应的MAC实体接收所述MAC  CE，来选择通过与MCG还是SCG相对应的RLC实体或逻辑信道来发送数据，或根据所述MAC CE中携带的指示信息来选择通过与MCG还是SCG相对应的RLC实体或逻辑信道来发送数据。
在实施例中，从与MCG和SCG中预定义的仅一个小区组相对应的MAC实体接收所述MAC CE，或所述方法还包括：经由无线资源控制RRC信令接收指示发送MAC CE的MAC实体的指示标识，并根据所述指示标识来确定从与MCG还是SCG相对应的MAC实体接收所述MAC CE。
根据本公开的第三方面，提供了一种用户设备UE，包括收发机、处理器和存储器，所述处理器存储所述处理器可执行的指令，使得所述UE执行根据以上第一或第二方面所述的方法。
根据本公开的第四方面，提供了一种基站中的方法，包括：向用户设备UE发送用于去使能分组重复的媒体访问控制MAC控制元素CE。所述MAC CE携带的指示信息，以向UE指示通过与主小区组MCG还是辅小区组SCG相对应的无线链路控制RLC实体或逻辑信道来发送数据。
根据本公开的第五方面，提供了一种基站，包括收发机、处理器和存储器，所述处理器存储所述处理器可执行的指令，使得所述基站执行根据以上第四方面所述的方法。
附图说明
通过下文结合附图的详细描述，本公开的上述和其它特征将会变得更加明显，其中：
图1示出了分组重复MCG分离DRB数据传输的示意图；
图2示出了分组重复SCG分离DRB数据传输的示意图；
图3示出了载波聚合场景中分组重复承载协议架构的示意图；
图4示出了双连接场景中分组重复承载协议架构的示意图；
图5示出了根据本公开实施例的用户设备中的方法的流程图；
图6示出了根据本公开另一实施例的用户设备中的方法的流程图；
图7示出了根据本公开实施例的用户设备的框图；
图8示出了根据本公开实施例的基站中的方法的流程图；
图9示出了根据本公开实施例的基站的框图。
具体实施方式
下面结合附图和具体实施方式对本公开进行详细阐述。应当注意，本公开不应局限于下文所述的具体实施方式。另外，为了简便起见，省略了对与本公开没有直接关联的公知技术的详细描述，以防止对本公开的理解造成混淆。
下面描述本公开涉及的部分术语，如未特别说明，本公开涉及的术语采用此处定义。本公开给出的术语在NR、LTE和eLTE中可能采用不同的命名方式，但本公开中采用统一的术语，在应用到具体的系统中时，可以替换为相应系统中采用的术语。
RRC：Radio Resource Control，无线资源控制。
PDCP：Packet Data Convergence Protocol，分组数据汇聚协议。在本公开中，如未特别说明，PDCP可以表示NR或LTE或eLTE中的PDCP。
RLC：Radio Link Control，无线链路控制。在本公开中，如未特别说明，RLC可以表示NR或LTE或eLTE中的RLC。RLC实体可以是UM RLC实体或AM RLC实体。
MAC：Medium Access Control，媒体访问控制。在本公开中，如未特别说明，MAC可以表示NR或LTE或eLTE中的MAC。
DTCH：Dedicated Traffic Channel，专用业务信道。
CCCH：Common Control Channel，公共控制信道。
DCCH：Dedicated Control Channel，专用控制信道。
PDU：Protocol Data Unit，协议数据单元。
SDU：Service Data Unit，服务数据单元。
在本公开中，将从上层接收或发往上层的数据称为SDU，将发往下层或从下层接收的数据称为PDU。例如，PDCP实体从上层接收的数据或发往上层的数据称为PDCP SDU；PDCP实体从RLC实体接收到的数据或发往RLC实体的数据称为PDCP PDU(也就是RLC SDU)。
主基站：Master eNB，记为MeNB(对应E-UTRAN或LTE或eLTE的基站)或MgNB(对应5G-RAN或NR的基站)。在多连接中，至少 终止于处理UE与核心网间交互的控制节点移动管理实体(可记为S1-MME)的基站。本公开中主基站均记为MeNB，需要说明的是，所有适用于MeNB的实施例或定义也适用于MgNB。
辅基站：Secondary eNB，记为SeNB(对应E-UTRAN或LTE或eLTE的基站)或SgNB(对应5G-RAN或NR的基站)。在多连接中，不作为MeNB，为UE提供额外的无线资源的基站。本公开中辅基站均记为SeNB，需要说明的是，所有适用于SeNB的实施例或定义也适用于SgNB。
主小区：Primary Cell，PCell。工作在主频率上的小区，UE在其上执行初始连接建立过程或发起连接重建过程或在切换过程中被指定为主小区的小区。本公开所述小区也可称为载波。
主辅小区：Primary Secondary Cell，PSCell。在执行改变SCG的过程中指示UE用于执行随机接入的SCG小区。
辅小区：Secondary Cell，SCell。工作在辅频率上的小区，所述小区可在RRC连接建立之后配置且可用于提供额外的无线资源。
小区组：Cell Group，CG，在多连接中，关联到主基站或辅基站的一组服务小区或载波。在本公开中，将关联到分组重复承载的某个逻辑信道或RLC实体的一组小区或为分组重复承载的某个逻辑信道或RLC实体提供无线资源或数据传输服务的一组小区称为小区组，所述小区可以是配置了上行载波的小区。所述小区也可称为服务小区。需要说明的是，本公开所述的小区也可以称为光束集(a set of beam)。
主小区组：Master Cell Group，MCG。对于未配置多连接的UE，MCG由所有的服务小区组成；对于配置了多连接的UE，MCG由服务小区的子集组成(即关联到MeNB或MgNB的一组服务小区)，其中包含PCell和0个或1个或多个SCell。
辅小区组：Secondary Cell Group，SCG。在多连接中，与SeNB或SgNB关联的一组服务小区。SCG可以包含一个PSCell，还可以包含一个或多个SCell
多连接：处于RRC连接态下UE的操作模式，配置了多个小区组，所述多个小区组包括一个MCG，一个或多个SCG(即UE连接到多个基站)。如果只配置了一个MCG(或MeNB或MgNB)和一个SCG(或 SeNB或SgNB)，则称为双连接。即处于连接态的具有多个接收机和/或发送机的UE被配置为使用由多个不同的调度器提供的EUTRAN和/或5G-RAN无线资源，所述调度器可以通过非理想回程(non-ideal backhaul)或理想回程(ideal backhaul)连接。本公开所述的多连接包括双连接。多连接数据传输方式包括但不限于：分组重复，链路选择。
DRB：Data Radio Bearer carrying user plane data，承载用户面数据的数据无线承载或简称数据承载。
SRB：Signalling Radio Bearer，信令无线承载。所述承载可以用于传输RRC消息和NAS消息或仅用于传输RRC消息和NAS消息。SRB可以包括SRB0、SRB1、SRB1bis和SRB2。其中，SRB0用于采用CCCH逻辑信道的RRC消息；SRB1用于采用DCCH逻辑信道的RRC消息，所述RRC消息中可能包含NAS消息，SRB1还用于在SRB2建立之前传输NAS消息。SRB1bis用于安全激活前采用DCCH逻辑信道的RRC消息和NAS消息，所述RRC消息中可能包含NAS消息。SRB2用于采用DCCH逻辑信道的RRC消息和NAS消息，所述RRC消息包括记录的测量信息(或称测量日志)。SRB可以是MCG SRB，也可以是SCG SRB。
本公开中的所述承载可以是DRB，也可以是SRB。
分离DRB：在多连接中，无线协议位于MeNB(或MgNB)和SeNB(或SgNB)且同时利用MeNB(或MgNB)和SeNB(或SgNB)资源的承载。如果分离DRB的PDCP实体位于主基站(即数据先到达主基站，由主基站转发给辅基站，实现数据在主基站中分离)，则称为MCG分离DRB；如果分离DRB的PDCP实体位于辅基站(即数据先到达辅基站，由辅基站转发给主基站，实现数据在辅基站中分离)，则称为SCG分离DRB。如未特别说明，本公开中所述分离DRB可以是MCG分离DRB，也可以是SCG分离DRB。本公开所述实施例也适用于不区分MCG分离DRB和SCG分离DRB的场景，即所述分离DRB的无线协议位于MeNB(或MgNB)和SeNB(或SgNB)且同时利用MeNB(或MgNB)和SeNB(或SgNB)资源的承载DRB。
分离SRB：在多连接中，无线协议位于MeNB(或MgNB)和SeNB(或SgNB)且同时利用MeNB(或MgNB)和SeNB(或SgNB)资源的承载。如果分离SRB的PDCP实体和/或RRC位于主基站(即信令， 也可称为数据，由主基站转发给辅基站，实现信令在主基站中分离)，则称为MCG分离SRB；如果分离SRB的PDCP实体和/或RRC位于辅基站(即信令，也可称为数据，由辅基站转发给主基站，实现信令在辅基站中分离)，则称为SCG分离SRB。如未特别说明，本公开中所述分离SRB可以是MCG分离SRB，也可以是SCG分离SRB。本公开所述实施例也适用于不区分MCG分离SRB和SCG分离SRB的场景，即所述分离SRB的无线协议位于MeNB(或MgNB)和SeNB(或SgNB)且同时利用MeNB(或MgNB)和SeNB(或SgNB)资源的承载SRB。
在本公开中，所述分离承载可以是分离SRB或分离DRB。
分组重复：也可称为数据重复或包重复或PDCP重复或PDCP PDU重复或PDCP SDU重复或PDCP分组重复(如未特别说明，本公开中所述数据可以是控制面信令或用户面数据，分别对应SRB的信令和DRB的数据)。在多连接方式下，同一数据(或称为包或者分组，即PDCP PDU或PDCP SDU)在多个CG的服务小区进行传输，即同一数据同时利用主基站(或MCG)和辅基站(或SCG)提供的资源传输或同一数据分别发送到位于MCG和SCG的下层(或RLC层)或PDCP实体将同一PDCP PDU发送到关联的多个下层实体(或RLC实体)或相同的数据在多个不同的承载上发送。在载波聚合或单连接方式下，PDCP实体将重复的(或同一)PDCP PDU发送到所关联的两个或多个RLC实体(或称下层实体)和/或逻辑信道，并由MAC实体通过不同的载波(可也称为小区或服务小区)发送给接收端；接收端PDCP实体负责检测并删除重复的PDCP PDU或SDU。
链路选择：PDCP实体将同一分组(即PDCP PDU或PDCP SDU)仅发送到一个RLC实体，不同分组可通过不同的RLC实体发送。在载波聚合中，去使能PDCP分组重复后，PDCP实体将分组发送到关联的多个RLC实体中的一个。在多连接方式下，PDCP实体从配置的小区组中选择一个小区组进行分组传输，即PDCP实体将分组发送到与MCG关联的RLC实体或与SCG关联的RLC实体。每个数据只利用MeNB或SeNB的资源。在PDCP PDU链路选择多连接方式下，每个PDCP PDU只经过一个RLC实体发送给接收方。
重复逻辑信道：本发明中，称关联到同一PDCP实体的或用于发送 相同数据的或同一分组重复承载所对应的逻辑信道称为重复逻辑信道。
分组重复承载：在载波聚合或单连接方式下，支持分组重复的承载，包括分组重复SRB和分组重复DRB。所述承载的一个PDCP实体关联到两个或多个RLC实体、两个或多个逻辑信道以及一个MAC实体且发送端PDCP实体将重复的(或同一)PDCP PDU发送到所述两个或多个RLC实体(或称为下层实体)和/或两个或多个逻辑信道，由MAC实体通过不同的载波(即小区或服务小区)发送给接收端；接收端PDCP实体将来自下层实体的重复的PDCP PDU或SDU移除。
分组重复分离承载：在多连接方式下，支持分组重复的分离承载。在所述发送方式中，同一数据在分离承载的多个无线协议上发送，包括分组重复MCG分离SRB、分组重复SCG分离SRB、分组重复MCG分离DRB和分组重复SCG分离DRB。如果是分组重复MCG分离承载，则由位于主基站或MCG的PDCP实体负责分组重复和/或重复分组移除；如果是分组重复SCG分离承载，则由位于辅基站或SCG的PDCP实体负责分组重复(即将PDCP PDU发送到两个或多个RLC实体)和/或重复分组移除。
图1示出了在双连接中，基站与用户设备UE之间进行下行分组重复MCG分离DRB传输的示意图。应理解，对于基站与UE之间进行上行分组重复MCG分离DRB传输可以采用同样的协议架构，只是数据从UE发送到基站，即，将图1中的箭头反向即可。如图1所示，数据(例如分组数据汇聚协议协议数据单元(PDCP PDU))在分离DRB的多个无线协议(对应于与同一PDCP实体相关联的多个RLC实体)上发送，利用MeNB和SeNB资源。在PDCP PDU数据重复多连接方式下，每个PDCP PDU经过多个RLC实体发送给接收方。MeNB和SeNB间的接口可以记为Xn或Xx或X2。根据MeNB和SeNB的不同类型，所述接口可以采用不同命名。例如，如果MeNB为LTE eNB，SeNB为gNB，则所述接口记为Xx；如果MeNB为gNB，SeNB为eLTE eNB，则所述接口记为Xn。相应的，分组重复MCG分离SRB采用相似的协议架构，不同之处在于将数据发送给PDCP实体的上层实体是RRC，PDCP实体在接收到来自下层实体的数据后发送给上层的RRC实体。
图2示出了在双连接中，基站与用户设备UE之间进行下行分组重复SCG分离DRB传输的示意图。应理解，对于基站与UE之间进行上行分组重复SCG分离DRB传输可以采用同样的协议架构，只是数据从UE发送到基站，即，将图2中的箭头反向即可。如图2所示，数据(例如分组数据汇聚协议协议数据单元(PDCP PDU))在分离DRB的多个无线协议(对应于与同一PDCP实体相关联的多个RLC实体)上发送，利用MeNB和SeNB资源。在PDCP PDU数据重复多连接方式下，每个PDCP PDU经过多个RLC实体发送给接收方。MeNB和SeNB间的接口可以记为Xn或Xx或X2。根据MeNB和SeNB的不同类型，所述接口可以采用不同命名。例如，如果MeNB为LTE eNB，SeNB为gNB，则所述接口记为Xx；如果MeNB为gNB，SeNB为eLTE eNB，则所述接口记为Xn。相应的，分组重复SCG分离SRB采用相似的协议架构，不同之处在于将数据发送给PDCP实体的上层实体是RRC，PDCP实体在接收到来自下层实体的数据后发送给上层的RRC实体。
本公开部分实施例以数据包PDCP PDU或SDU重复发送两次为例(即一个PDCP实体关联两个RLC实体和/或两个逻辑信道)，但本公开所述的技术方案并不限于数据包PDCP PDU或SDU重复发送两次的场景，本领域技术人员可以容易地扩展到重复发送多次场景(即一个PDCP实体关联多个RLC实体和/或多个逻辑信道)。
图3给出了载波聚合场景中分组重复承载的协议架构示意图。在图3(a)所示示意图中，一个DRB的PDCP实体关联到两个RLC实体和两个逻辑信道、一个MAC实体。在图3(b)所示示意图中，一个SRB的RRC实体和PDCP实体关联到两个RLC实体和两个逻辑信道、一个MAC实体。
图4给出了双连接场景中分组重复承载的协议架构示意图。在图4(a)所示示意图中，一个DRB的PDCP实体关联到两个RLC实体和两个逻辑信道、两个MAC实体。在图4(b)所示示意图中，一个SRB的RRC实体和PDCP实体关联到两个RLC实体和两个逻辑信道、两个MAC实体。
在本发明中，分组重复承载或分组重复分离承载在初始配置时可能 处于去使能状态或者收到去使能MAC CE时，去使能所有分组重复承载或分组重复分离承载PDCP分组重复。这里，将用于去使能PDCP分组重复的MAC CE称为去使能MAC CE。由于用于使能PDCP分组重复的MAC CE和用于去使能PDCP分组重复的MAC CE可以使用同一MAC CE，因此下文中也将用于去使能PDCP分组重复的MAC CE称为使能/去使能MAC CE。通过使能/去使能MAC CE中的一个或多个字段来指示是使能还是去使能所有分组承载和/或分组重复分离承载或通过使能/去使能MAC CE中的一个或多个字段来指示是使能还是去使能一个或多个分组承载和/或分组重复分离承载或通过使能/去使能MAC CE一个或多个字段来指示是使能MAC CE还是去使能MAC CE。具体的，分以下几种情况：
(1)对于同时配置了分组重复承载和分组重复分离承载的UE，使能/去使能MAC CE应用于所有分组重复承载和分组重复分离承载。UE接收到使能/去使能MAC CE时，使能/去使能所有分组重复承载和分组重复分离承载PDCP分组重复。
(2)定义两种使能/去使能MAC CE分别应用于分组重复承载和分组重复分离承载。优选的，在使能/去使能MAC CE中定义一个字段用于指示使能/去使能MAC CE是针对分组重复承载还是针对分组重复分离承载。对于同时配置了分组重复承载和分组重复分离承载的UE，当接收到针对分组重复承载的使能/去使能MAC CE，使能/去使能所有分组重复承载的PDCP分组重复；当接收到针对分组重复分离承载的使能/去使能MAC CE，使能/去使能所有分组重复分离承载的PDCP分组重复。
(3)在使能/去使能MAC CE中携带用于区别承载的指示信息，所述指示信息可以是承载标识或逻辑信道标识或与承载对应的位图(位图中的每一位对应一个分组重复承载或分组重复分离承载，当位图中对应位为0时，表示去使能对应承载的PDCP分组重复，当位图中对应位为1时，表示使能对应承载的PDCP分组重复，反之亦然)或逻辑信道对应的位图(位图中的每一位对应一个分组承载承载关联的逻辑信道或分组重复分离承载关联的逻辑信道，当位图中对应位为0时，表示去使能对应承 载的PDCP分组重复，当位图中对应位为1时，表示使能对应承载的PDCP分组重复，反之亦然)。当UE接收到使能/去使能MAC CE，根据MAC CE中的指示信息，使能/去使能对应承载的PDCP分组重复。
需要说明的是，本发明以下描述的实施例中，去使能PDCP分组重复可以是在初始配置分组重复承载或分组重复分离承载时PDCP分组重复是去使能的，也可以是由于收到去使能/去使能MAC CE后去使能PDCP分组重复。由于上述使能/去使能MAC CE的不同实现方式，本发明实施例中，在UE接收到使能/去使能MAC CE时，根据接收到的MAC CE来使能或去使能所有分组重复承载或分组重复分离承载或者使能或去使能MAC CE中指定的分组重复承载或分组重复分离承载。
MAC实体的逻辑信道优先级过程或UE的调度过程遵循以下规则中的一个或多个：
1.对于分组重复承载对应的逻辑信道，使能PDCP分组重复后，MAC实体将来自分组重复承载对应的逻辑信道的数据在所关联的小区或关联的小区组中的小区的上行资源UL Grant(即新传输)上发送；换言之，MAC实体不能将来自分组重复承载对应的逻辑信道的数据在不是关联的小区或不属于关联的小区组中的小区的上行资源UL Grant上发送。
2.对于分组重复承载对应的逻辑信道，去使能PDCP分组重复后，MAC实体将自分组重复承载对应的逻辑信道的数据在所有小区的UL Grant上传输。
需要说明的是，本公开中所述MAC实体将来自逻辑信道或承载的数据通过UL Grant发送可以表示：在新传输时，MAC实体基于逻辑信道优先级过程(Logical Channel Prioritization procedure，LCP)将来自所述分组重复承载或分组重复分离承载对应的逻辑信道的数据与来自其他逻辑信道的数据按照LCP定义的复用方式复用道同一MAC PDU。可选的，来自关联到分组重复承载或分组重复分离承载的小区或小区组的UL Grant只能用于传输来自分组重复承载或分组重复分离承载的数据，即来自关联到分组重复承载或分组重复分离承载的小区或小区组的UL  Grant，MAC实体仅按照LCP定义的复用方式复用道同一MAC PDU或发送来自分组重复承载或分组重复分离承载对应的逻辑信道的数据。
图5示出了根据本公开实施例的用户设备UE中的方法500的流程图。方法500涉及在载波聚合中，去使能PDCP分组重复后数据的发送方式。相应地，UE操作在载波聚合模式。方法500包括以下步骤。
在步骤S510，接收用于去使能分组重复的媒体访问控制MAC控制元素CE。
在步骤S520，从分组数据汇聚协议PDCP实体向一个无线链路控制RLC实体发送数据。
在步骤S530，在MAC实体处，仅通过在分组重复使能的状态中与所述RLC实体相关联的小区或小区组，或者通过从预先配置给UE的小区或小区组集合中选择的小区或小区组，发送所述数据。
具体地，在一个实施例中，去使能PDCP分组重复后，PDCP实体将PDCP PDU发送到一个RLC实体，并通过逻辑信道发送到MAC实体。MAC实体接收到来自所述重复逻辑信道的数据后，将所述数据通过与所述重复逻辑信道关联的小区或小区组发送。即对于分组重复承载，MAC实体不能将来自所述承载对应的逻辑信道的数据通过不是关联到所述逻辑信道的小区或小区组的上行资源(UL Grant)上发送。例如，分组重复承载DRB1对应的两个RLC实体RLC1和RLC2及逻辑信道LCH1和LCH2且RLC1/LCH1关联到小区组CG1＝{C1，C2}，RLC2/LCH2关联到小区组CG2＝{C3，C4}。去使能DRB1的分组重复功能后，所有PDCP PDU只能通过RLC1并利用与RLC1/LCH1关联的小区组的UL Grant发送。
在另一个实施例中，去使能PDCP分组重复后，PDCP实体将PDCP PDU发送到一个RLC实体，并通过逻辑信道发送到MAC实体。MAC实体可将来自所述逻辑信道的数据通过任意上行资源(UL Grant)上发送。即在去使能分组重复后，来自对应分组重复承载的数据或来自对应分组重复承载所关联的逻辑信道的数据可以在为UE配置的任意小区所提供的UL Grant上发送或MAC实体可以在任何新传输中根据LCP定义的过程将对应分组重复承载的数据或来自对应分组重复承载所关联的逻 辑信道的数据复用到MAC PDU。例如，为UE配置的用于载波聚合的小区组CG＝{C1，C2，C3，C4，C5}，分组重复承载DRB1对应的两个RLC实体RLC1和RLC2及逻辑信道LCH1和LCH2且RLC1/LCH1关联到小区组CG1＝{C1，C2}，RLC2/LCH2关联到小区组CG2＝{C3，C4}。去使能DRB1的分组重复功能后，所有PDCP PDU只能通过RLC1并利用PCell和CG的UL Grant发送。
在又一个实施例中，去使能PDCP分组重复后，PDCP实体将同一PDCP PDU发送到所关联的RLC实体和/或逻辑信道中的一个并通过所关联的小区或小区组发送，即一个PDCP PDU可以选择所关联的任意一个RLC实体发送。例如，分组重复承载DRB1对应的两个RLC实体RLC1和RLC2及逻辑信道LCH1和LCH2且RLC1/LCH1关联到小区组CG1＝{C1，C2}，RLC2/LCH2关联到小区组CG2＝{C3，C4}。去使能DRB1的分组重复功能后，PDCP PDU可以通过RLC1或RLC2发送。例如SN＝X1的PDCP PDU发送到RLC1，SN＝X2的PDCP PDU发送到RLC2。
在再一个实施例中，通过RRC信令配置去使能PDCP分组重复后PDCP实体发送PDCP PDU的方式，即在RRC信令中携带一个指示信息，所述指示信息用于指示去使能PDCP分组重复后数据的发送方式(即PDCP PDU通过哪个RLC实体发送)。所述发送方式可以是所有PDCP PDU通过一个RLC实体或逻辑信道发送(此时指示信息的取值为逻辑信道标识，表示使能火去使能所述逻辑信道)，通过两个RLC实体或逻辑信道发送但同一PDCP PDU只发送到其中一个RLC实体。当UE接收到使能/去使能MAC CE时，根据RRC信令的中携带的指示信息，在去使能PDCP分组重复后，将PDCP PDU按照所述指示信息定义的方式发送。
图6示出了根据本公开实施例的用户设备UE中的方法600的流程图。方法600涉及在多连接中，去使能PDCP分组重复后数据发送方式。相应地，UE操作在多连接模式。方法600包括以下步骤。
在步骤S610，接收用于去使能分组重复的媒体访问控制MAC控制元素CE。
在步骤S620，仅通过与主小区组MCG相对应的无线链路控制RLC实体或逻辑信道来发送数据。
备选地，在步骤S620，仅通过与辅小区组SCG相对应的RLC实体或逻辑信道来发送数据。
备选地，在步骤S630，采用链路选择方式通过与MCG和SCG相对应的RLC实体或逻辑信道来发送数据。
在一个实施例中，通过与MCG或SCG中预定义的一个相对应的RLC实体或逻辑信道来发送数据。具体地，预定义去使能PDCP分组重复后数据发送方式。例如，预定义去使能PDCP分组重复后PDCP PDU只通过MCG发送；或者，预定义去使能PDCP分组重复后PDCP PDU只通过SCG发送；或者，预定义去使能PDCP分组重复后PDCP PDU只通过MCG或SCG发送(即去使能分组重复后，分组重复分离承载采用分离承载的数据发送方式，同一PDCP PDU不再同时发送到MCG和SCG对应的RLC实体而是只发送到两者之一)；或者，预定义去使能PDCP分组重复后PDCP PDU只能通过与特定小区组(MCG或SCG)对应的RLC实体发送，所述小区组是用户面(对应分组重复分离DRB)或控制面(对应分组重复分离SRB)终止的小区组(或对应的PDCP所在的小区组)。
例如，当UE的某个MAC实体接收到使能/去使能MAC CE时，去使能PDCP分组重复，且按照预定义的方式发送PDCP PDU。例如，当UE的接收到使能/去使能MAC CE时，去使能SCG或SCG对应的逻辑信道或SCG对应的RLC实体，换言之，PDCP实体将PDCP PDU发送到MCG对应的逻辑信道或MCG对应的RLC实体或MCG。又例如，当UE的接收到使能/去使能MAC CE时，去使能MCG或MCG对应的逻辑信道或MCG对应的RLC实体，换言之，PDCP实体将PDCP PDU发送到SCG对应的逻辑信道或SCG对应的RLC实体或SCG。
在另一个实施例中，所述MAC CE中携带的指示信息，所述指示信息指示要通过与MCG还是SCG相对应的RLC实体或逻辑信道来发送数据。根据所述指示信息，通过与MCG或SCG相对应的RLC实体或逻辑信道来发送数据。具体地，在使能/去使能MAC CE中携带指示信息来指示去使能PDCP分组重复后数据发送方式。例如，在MAC CE中 指示去使能PDCP分组重复后PDCP PDU只通过MCG发送；或者，在MAC CE中指示去使能PDCP分组重复后PDCP PDU只通过SCG发送；或者，在MAC CE中指示去使能PDCP分组重复后PDCP PDU只通过MCG或SCG发送(即采用分离承载数据的发送方式，同一PDCP PDU不再同时发送到MCG和SCG对应的RLC实体)；或者，在MAC CE中指示去使能PDCP分组重复后PDCP PDU只能通过与特定小区组(MCG或SCG)对应的RLC实体发送，所述小区组是用户面(对应分组重复分离DRB)或控制面(对应分组重复分离SRB)终止的小区组(或对应的PDCP所在的小区组)。
当UE的某个MAC实体接收到使能/去使能MAC CE时，去使能PDCP分组重复，并根据MAC CE中携带的指示信息发送PDCP PDU。例如，所述指示信息可以是逻辑信道标识或小区组标识(例如MCG或SCG)，相应的使能或去使能对应的逻辑信道或小区组或小区组对应的逻辑信道。
在又一个实施例中，经由无线资源控制RRC信令接收数据发送配置，所述数据发送配置指示在去使能分组重复的状态下要通过与MCG还是SCG相对应的RLC实体或逻辑信道来发送数据。根据所述数据发送配置，通过与MCG或SCG相对应的RLC实体或逻辑信道来发送数据。具体地，通过RRC信令配置去使能PDCP分组重复后数据发送方式。在RRC信令中携带一个指示信息，所述指示信息用于指示去使能PDCP分组重复后数据的发送方式(即PDCP PDU通过哪个RLC实体发送)。所述发送方式可以是去使能PDCP分组重复后PDCP PDU只通过MCG(即MCG对应的RLC实体)发送、去使能PDCP分组重复后PDCP PDU只通过SCG(即SCG对应的RLC实体)发送、去使能PDCP分组重复后PDCP PDU只通过MCG或SCG(即MCG或SCG对应的RLC实体)发送(即采用分离承载数据的发送方式，同一PDCP PDU不再同时发送到MCG和SCG对应的RLC实体)、去使能PDCP分组重复后PDCP PDU只能通过与特定小区组(MCG或SCG)对应的RLC实体发送，所述小区组是用户面(对应分组重复分离DRB)或控制面(对应分组重复分离SRB)终止的小区组(或对应的PDCP所在的小区组)
当UE接收到使能/去使能MAC CE时，去使能PDCP分组重复并根 据接收到的RRC信令的中携带的指示信息，，将PDCP PDU按照所述指示信息定义的方式发送到MCG对应的RLC实体的SCG对应的RLC实体发送。
需要说明的，本公开所述RRC信令可以是RRC重配置消息。
在一个实施例中，所述MAC CE是从与MCG或SCG相对应的MAC实体接收的。根据从与MCG还是SCG相对应的MAC实体接收所述MAC CE，来选择通过与MCG还是SCG相对应的RLC实体或逻辑信道来发送数据。
备选地，根据所述MAC CE中携带的指示信息来选择通过与MCG还是SCG相对应的RLC实体或逻辑信道来发送数据。
在一个示例中，从与MCG和SCG中预定义的仅一个小区组相对应的MAC实体接收所述MAC CE。
在一个示例中，方法600还包括：经由无线资源控制RRC信令接收指示发送MAC CE的MAC实体的指示标识，并根据所述指示标识来确定从与MCG还是SCG相对应的MAC实体接收所述MAC CE。
以下参照具体示例来说明发送使能/去使能MAC CE的MAC实体。
示例1：MCG MAC实体和SCG MAC实体都可以发送使能/去使能MAC CE
在一个实施例中，当与某个小区组对应的MAC实体接收到使能/去使能MAC CE时，去使能对应重复逻辑信道，即分组重复分离承载对应的PDCP实体不再将PDCP PDU发送到所述MAC实体对应的逻辑信道或RLC实体。换言之，分组重复分离承载对应的PDCP实体将数据发送到另一MAC实体对应的逻辑信道或RLC实体或收到使能/去使能MAC CE的MAC实体将去使能对应的逻辑信道或RLC实体。具体的，如果MCG对应的MAC实体接收到去使能PDCP分组重复的使能/去使能MAC CE，则PDCP实体将PDCP PDU发送到SCG对应的RLC实体；如果SCG对应的MAC实体接收到去使能PDCP分组重复的使能/去使能MAC CE，则PDCP实体将PDCP PDU发送到MCG对应的RLC实体。
在另一个实施例中，当与某个小区组对应的MAC实体接收到使能/去使能MAC CE时，去使能另一重复逻辑信道，即分组重复分离承载对应的PDCP实体将PDCP PDU发送到所述MAC实体对应的逻辑信道或 RLC实体，换言之，分组重复分离承载对应的PDCP实体将数据发送到所述MAC实体对应的逻辑信道或RLC实体或收到使能/去使能MAC CE的MAC实体将指示另一MAC实体去使能其对应的逻辑信道或RLC实体。具体的，如果MCG对应的MAC实体接收到去使能PDCP分组重复的使能/去使能MAC CE，则PDCP实体将PDCP PDU发送到MCG对应的RLC实体；如果SCG对应的MAC实体接收到去使能PDCP分组重复的使能/去使能MAC CE，则PDCP实体将PDCP PDU发送到SCG对应的RLC实体。
示例2：预定义MCG MAC实体或SCG MAC实体发送使能/去使能MAC CE
可以预定义UE只能通过MCG或SCG对应的MAC实体接收使能/去使能MAC CE；或者，预定义PDCP实体所在的小区组发送使能/去使能MAC CE；或者，预定义控制面(对于分组重复分离SRB)或用户面(对于分组重复分离DRB)终止的小区组发送使能/去使能MAC CE。例如，当PDCP实体位于MCG时，UE从与MCG对应的MAC实体接收使能/去使能MAC CE；当PDCP实体位于SCG时，UE从与SCG对应的MAC实体接收使能/去使能MAC CE。所述PDCP实体位于某个小区组是指控制面或用户面终止于对应的小区组。
需要说明的是，本发明中所述控制面终止的小区组是指连接到核心网MME的小区组或对应的基站连接到MME的小区组，例如LTE/LTE-A中的S1-C或NR中的NG-C终止的小区组或对应基站的小区组；本发明中所述用户面终止的小区组是指连接到网关的小区组或对应的基站连接到网关的小区组，例如LTE/LTE-A中的S1-U或NR中的NG-U终止的小区组或对应基站的小区组。
示例3：通过RRC信令指示发送使能/去使能MAC CE的MAC实体
在RRC信令中携带一个指示标识，所述指示标识用于指示发送使能或去使能MAC CE的小区组或小区组对应的MAC实体。例如，当所述指示标识的取值为“1”或“setup”或“TRUE”或“MCG”或携带所述指示标识时，MCG MAC实体发送使能/去使能MAC CE；当所述指示标识的取值为“0”或“FALSE”或“SCG”或所述标识不出现时，SCG MAC实体发送 使能/去使能MAC CE。
本公开中所述使能分组重复(也可称PDCP分组重复或分组重复承载分组重复或PDCP PDU重复或PDCP SDU重复或PDCP重复或分组重复承载的PDCP重复或分组承载的PDCP PDU重复或分组承载的PDCP SDU重复)也可以表述为PDCP实体将同一PDCP PDU或PDCP SDU发送到所关联的两个或多个下层实体(或RLC实体和/或逻辑信道)，即同一PDCP PDU通过关联的两个小区或小区组发送。如果是分组重复分离承载，则使能分组重复功能使得同一PDCP PDU通过MCG和SCG发送。去使能分组重复功能也可以表述为配置PDCP实体将同一PDCP PDU发送到所关联的两个多个下层实体(或RLC实体和/或逻辑信道)中的一个或所有PDCP PDU仅通过两个或多个下层实体(或RLC实体和/或逻辑信道)中的一个发送。本公开所述分组重复是指上行分组重复。
与上述方法500或600相对应，本公开提供了一种用户设备UE。图7示出了根据本公开实施例的UE 700的框图。如图所示，UE 700包括：收发机710、处理器720和存储器730，所述处理器730存储所述处理器720可执行的指令，使得所述用户设备700执行以上结合图5描述的方法500或结合图6描述的方法600。
具体地，所述处理器730存储所述处理器720可执行的指令，使得所述用户设备700接收用于去使能分组重复的媒体访问控制MAC控制元素CE；从分组数据汇聚协议PDCP实体向一个无线链路控制RLC实体发送数据；以及在MAC实体处，仅通过在分组重复使能的状态中与所述RLC实体相关联的小区或小区组，或者通过从预先配置给UE的小区或小区组集合中选择的小区或小区组，发送所述数据。
备选地，所述处理器730存储所述处理器720可执行的指令，使得所述用户设备700接收用于去使能分组重复的媒体访问控制MAC控制元素CE；以及仅通过与主小区组MCG相对应的无线链路控制RLC实体或逻辑信道来发送数据；或者仅通过与辅小区组SCG相对应的RLC实体或逻辑信道来发送数据；或者采用链路选择方式通过与MCG和SCG相对应的RLC实体或逻辑信道来发送数据。
在实施例中，通过与MCG或SCG中预定义的一个相对应的RLC实体或逻辑信道来发送数据。
在实施例中，所述MAC CE中携带的指示信息，所述指示信息指示要通过与MCG还是SCG相对应的RLC实体或逻辑信道来发送数据。根据所述指示信息，通过与MCG或SCG相对应的RLC实体或逻辑信道来发送数据。
在实施例中，所述方法还包括：经由无线资源控制RRC信令接收数据发送配置，所述数据发送配置指示在去使能分组重复的状态下要通过与MCG还是SCG相对应的RLC实体或逻辑信道来发送数据。根据所述数据发送配置，通过与MCG或SCG相对应的RLC实体或逻辑信道来发送数据。
在实施例中，所述MAC CE是从与MCG或SCG相对应的MAC实体接收的。根据从与MCG还是SCG相对应的MAC实体接收所述MAC CE，来选择通过与MCG还是SCG相对应的RLC实体或逻辑信道来发送数据，或根据所述MAC CE中携带的指示信息来选择通过与MCG还是SCG相对应的RLC实体或逻辑信道来发送数据。
在实施例中，从与MCG和SCG中预定义的仅一个小区组相对应的MAC实体接收所述MAC CE，或所述方法还包括：经由无线资源控制RRC信令接收指示发送MAC CE的MAC实体的指示标识，并根据所述指示标识来确定从与MCG还是SCG相对应的MAC实体接收所述MAC CE。
本公开还提供了一种基站中的方法。图8是示出了根据本公开实施例的基站中的方法800的流程图。如图所示，方法800包括以下步骤。
在步骤S810，向用户设备UE发送用于去使能分组重复的媒体访问控制MAC控制元素CE。所述MAC CE携带的指示信息，以向UE指示通过与主小区组MCG还是辅小区组SCG相对应的无线链路控制RLC实体或逻辑信道来发送数据。
备选地，可以经由无线资源控制RRC信令向UE发送数据发送配置，所述数据发送配置指示在去使能分组重复的状态下UE要通过与MCG还是SCG相对应的RLC实体或逻辑信道来发送数据。
可选地，可以经由无线资源控制RRC信令向UE发送指示发送MAC CE的MAC实体的指示标识。
与上述方法800相对应，本公开提供了一种基站。图9示出了根据本公开实施例的基站900的框图。如图所示，基站900包括：收发机910、处理器920和存储器930，所述处理器930存储所述处理器920可执行的指令，使得所述基站900执行以上结合图8描述的方法800。
具体地，所述处理器930存储所述处理器920可执行的指令，使得基站900向用户设备UE发送用于去使能分组重复的媒体访问控制MAC控制元素CE。所述MAC CE携带的指示信息，以向UE指示通过与主小区组MCG还是辅小区组SCG相对应的无线链路控制RLC实体或逻辑信道来发送数据。
备选地，所述处理器930可以存储所述处理器920可执行的指令，使得基站900经由无线资源控制RRC信令向UE发送数据发送配置，所述数据发送配置指示在去使能分组重复的状态下UE要通过与MCG还是SCG相对应的RLC实体或逻辑信道来发送数据。
可选地，所述处理器930可以存储所述处理器920可执行的指令，使得基站900经由无线资源控制RRC信令向UE发送指示发送MAC CE的MAC实体的指示标识。
运行在根据本发明的设备上的计算机可执行指令或者程序可以是通过控制中央处理单元(CPU)来使计算机实现本发明的实施例功能的程序。该程序或由该程序处理的信息可以临时存储在易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统中。
用于实现本发明各实施例功能的计算机可执行指令或程序可以记录在计算机可读存储介质上。可以通过使计算机系统读取记录在所述记录 介质上的程序并执行这些程序来实现相应的功能。此处的所谓“计算机系统”可以是嵌入在该设备中的计算机系统，可以包括操作系统或硬件(如外围设备)。“计算机可读存储介质”可以是半导体记录介质、光学记录介质、磁性记录介质、短时动态存储程序的记录介质、或计算机可读的任何其他记录介质。
用在上述实施例中的设备的各种特征或功能模块可以通过电路(例如，单片或多片集成电路)来实现或执行。设计用于执行本说明书所描述的功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、或其他可编程逻辑器件、分立的门或晶体管逻辑、分立的硬件组件、或上述器件的任意组合。通用处理器可以是微处理器，也可以是任何现有的处理器、控制器、微控制器、或状态机。上述电路可以是数字电路，也可以是模拟电路。因半导体技术的进步而出现了替代现有集成电路的新的集成电路技术的情况下，本发明的一个或多个实施例也可以使用这些新的集成电路技术来实现。
此外，本发明并不局限于上述实施例。尽管已经描述了所述实施例的各种示例，但本发明并不局限于此。安装在室内或室外的固定或非移动电子设备可以用作终端设备或通信设备，如AV设备、厨房设备、清洁设备、空调、办公设备、自动贩售机、以及其他家用电器等。
如上，已经参考附图对本发明的实施例进行了详细描述。但是，具体的结构并不局限于上述实施例，本发明也包括不偏离本发明主旨的任何设计改动。另外，可以在权利要求的范围内对本发明进行多种改动，通过适当地组合不同实施例所公开的技术手段所得到的实施例也包含在本发明的技术范围内。此外，上述实施例中所描述的具有相同效果的组件可以相互替代。

Claims (10)

  1. 一种用户设备UE中的方法，所述UE操作在载波聚合模式，所述方法包括：
    接收用于去使能分组重复的媒体访问控制MAC控制元素CE；
    从分组数据汇聚协议PDCP实体向一个无线链路控制RLC实体发送数据；以及
    在MAC实体处，仅通过在分组重复使能的状态中与所述RLC实体相关联的小区或小区组，或者通过从预先配置给UE的小区或小区组集合中选择的小区或小区组，发送所述数据。
  2. 一种用户设备UE中的方法，所述UE操作在多连接模式，所述方法包括：
    接收用于去使能分组重复的媒体访问控制MAC控制元素CE；以及
    仅通过与主小区组MCG相对应的无线链路控制RLC实体或逻辑信道来发送数据；或者
    仅通过与辅小区组SCG相对应的RLC实体或逻辑信道来发送数据；或者
    采用链路选择方式通过与MCG和SCG相对应的RLC实体或逻辑信道来发送数据。
  3. 根据权利要求2所述的方法，其中，通过与MCG或SCG中预定义的一个相对应的RLC实体或逻辑信道来发送数据。
  4. 根据权利要求2所述的方法，其中，所述MAC CE中携带的指示信息，所述指示信息指示要通过与MCG还是SCG相对应的RLC实体或逻辑信道来发送数据，以及
    其中，根据所述指示信息，通过与MCG或SCG相对应的RLC实体或逻辑信道来发送数据。
  5. 根据权利要求2所述的方法，还包括：
    经由无线资源控制RRC信令接收数据发送配置，所述数据发送配置指示在去使能分组重复的状态下要通过与MCG还是SCG相对应的RLC实体或逻辑信道来发送数据，
    其中，根据所述数据发送配置，通过与MCG或SCG相对应的RLC实体或逻辑信道来发送数据。
  6. 根据权利要求2所述的方法，其中所述MAC CE是从与MCG或SCG相对应的MAC实体接收的，以及
    根据从与MCG还是SCG相对应的MAC实体接收所述MAC CE，来选择通过与MCG还是SCG相对应的RLC实体或逻辑信道来发送数据，或
    根据所述MAC CE中携带的指示信息来选择通过与MCG还是SCG相对应的RLC实体或逻辑信道来发送数据。
  7. 根据权利要求6所述的方法，其中
    从与MCG和SCG中预定义的仅一个小区组相对应的MAC实体接收所述MAC CE，或
    所述方法还包括：经由无线资源控制RRC信令接收指示发送MAC CE的MAC实体的指示标识，并根据所述指示标识来确定从与MCG还是SCG相对应的MAC实体接收所述MAC CE。
  8. 一种用户设备UE，包括收发机、处理器和存储器，所述处理器存储所述处理器可执行的指令，使得所述UE执行根据权利要求1-7中任一项所述的方法。
  9. 一种基站中的方法，包括：
    向用户设备UE发送用于去使能分组重复的媒体访问控制MAC控制元素CE，
    其中，所述MAC CE携带的指示信息，以向UE指示通过与主小区组MCG还是辅小区组SCG相对应的无线链路控制RLC实体或逻辑信道来发送数据。
  10. 一种基站，包括收发机、处理器和存储器，所述处理器存储所述处理器可执行的指令，使得所述基站执行根据权利要求9所述的方法。
PCT/CN2018/090468 2017-06-15 2018-06-08 基站、用户设备和相关方法 WO2018228289A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US16/620,626 US11388626B2 (en) 2017-06-15 2018-06-08 Base station, user equipment, and related method
SG11201911793VA SG11201911793VA (en) 2017-06-15 2018-06-08 Base station, user equipment, and related method
EP18817544.2A EP3641186A4 (en) 2017-06-15 2018-06-08 BASE STATION, USER EQUIPMENT, AND RELATED PROCESSES

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710454693.5A CN109150415B (zh) 2017-06-15 2017-06-15 基站、用户设备和相关方法
CN201710454693.5 2017-06-15

Publications (1)

Publication Number Publication Date
WO2018228289A1 true WO2018228289A1 (zh) 2018-12-20

Family

ID=64658834

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/090468 WO2018228289A1 (zh) 2017-06-15 2018-06-08 基站、用户设备和相关方法

Country Status (6)

Country Link
US (1) US11388626B2 (zh)
EP (1) EP3641186A4 (zh)
CN (1) CN109150415B (zh)
SG (1) SG11201911793VA (zh)
TW (1) TWI692988B (zh)
WO (1) WO2018228289A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020198336A1 (en) * 2019-03-28 2020-10-01 Apple Inc. Data duplication over radio link control channels
CN111757520A (zh) * 2019-03-29 2020-10-09 华为技术有限公司 一种数据传输方法及装置
CN112218312A (zh) * 2019-07-12 2021-01-12 诺基亚技术有限公司 上行链路数据复制的灵活网络控制
EP3937559A4 (en) * 2019-03-29 2022-05-11 Huawei Technologies Co., Ltd. DATA TRANSMISSION METHOD AND DEVICE

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102324214B1 (ko) * 2017-01-06 2021-11-12 삼성전자 주식회사 차세대 이동 통신 시스템에서 이중 접속의 데이터 처리를 가속화하는 방법 및 장치
CN109391639B (zh) * 2017-08-02 2021-01-08 维沃移动通信有限公司 一种激活及去激活数据复制的方法及终端
EP3641468B1 (en) * 2017-08-11 2021-10-06 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Control methods, nodes and computer storage media
CN109391362B (zh) * 2017-08-11 2022-07-29 中兴通讯股份有限公司 一种信令传输方法及装置
US11206105B2 (en) * 2017-09-07 2021-12-21 Shenzhen Heytap Technology Corp., Ltd. Data transmission method and terminal device
WO2019080008A1 (zh) * 2017-10-25 2019-05-02 北京小米移动软件有限公司 增补上行载波配置方法及装置和调度资源分配方法及装置
KR20200034921A (ko) * 2018-09-21 2020-04-01 주식회사 케이티 5G IoT를 위한 데이터 중복 전송 방법 및 장치
CN111132375B (zh) * 2018-10-31 2021-09-10 维沃移动通信有限公司 一种分离承载的控制方法及相关设备
US11184275B2 (en) * 2018-11-16 2021-11-23 Huawei Technologies Co., Ltd. System and method for transmission redundancy in wireless communications
US11159422B2 (en) * 2019-02-03 2021-10-26 FG Innovation Company Limited Evolved packet data convergence protocol duplication
CN111436066A (zh) * 2019-02-14 2020-07-21 维沃移动通信有限公司 数据包承载路径确定、信息发送方法和设备
US11438922B2 (en) * 2019-07-19 2022-09-06 Qualcomm Incorporated MAC-CE duplication in packet duplication
ES2953714T3 (es) * 2019-12-23 2023-11-15 Guangdong Oppo Mobile Telecommunications Corp Ltd Método de comunicación inalámbrica, dispositivo terminal, chip, medio de almacenamiento legible por ordenador y producto de programa informático
CN113014370B (zh) * 2021-03-23 2023-05-26 展讯通信（上海）有限公司 信令发送方法及装置、存储介质、基站设备、用户设备
CN115278943A (zh) * 2021-04-30 2022-11-01 华为技术有限公司 一种通信方法及通信装置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104885546A (zh) * 2013-11-01 2015-09-02 三星电子株式会社 用于获取终端的系统帧号的方法、终端、以及移动通信系统
US20160065700A1 (en) * 2014-08-29 2016-03-03 Lg Electronics Inc. Pdcp operation in a wireless communication system supporting dual connectivity

Family Cites Families (38)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101831448B1 (ko) * 2010-02-02 2018-02-26 엘지전자 주식회사 이동 통신 시스템에서 ｐｄｃｐ 기능을 선택적으로 적용하는 방법
CN102857920A (zh) * 2011-06-30 2013-01-02 重庆重邮信科通信技术有限公司 长期演进系统终端侧对下行信令消息的处理方法及装置
US8958422B2 (en) * 2012-03-17 2015-02-17 Blackberry Limited Handling packet data convergence protocol data units
WO2013168850A1 (ko) * 2012-05-09 2013-11-14 삼성전자 주식회사 이동통신 시스템에서 불연속 수신을 제어하는 방법 및 장치
WO2014069856A1 (en) * 2012-10-29 2014-05-08 Lg Electronics Inc. Method and apparatus for releasing connection in wireless communication system
CN105379411B (zh) * 2013-07-19 2019-04-12 夏普株式会社 终端装置及其控制方法、基站装置及其控制方法
US10237911B2 (en) * 2014-01-30 2019-03-19 Intel IP Corporation Packet data convergence protocol (PDCP) enhancements in dual-connectivity networks
TWI628968B (zh) 2014-03-14 2018-07-01 Ｌｇ電子股份有限公司 在雙連結系統中觸發功率餘裕回報的方法及其裝置
CN106538008B (zh) * 2014-07-22 2019-12-27 夏普株式会社 终端装置、基站装置、通信系统、通信方法以及集成电路
US20160192427A1 (en) * 2014-12-30 2016-06-30 Electronics And Telecommunications Research Institute Operation method of communication node in wireless communication network
EP3245754B1 (en) * 2015-01-13 2018-09-26 Telefonaktiebolaget LM Ericsson (publ) Wireless terminals, nodes of wireless communication networks, and methods of operating the same
JP2016220209A (ja) * 2015-05-22 2016-12-22 エイスーステック コンピューター インコーポレーテッドＡＳＵＳＴｅＫ ＣＯＭＰＵＴＥＲ ＩＮＣ． 無線通信システムにおける基準信号送信を実行するための方法および装置
CN106358195B (zh) * 2015-07-24 2019-08-20 苏州简约纳电子有限公司 适用于lte接入层的安全激活优化方法
CN106452705B (zh) * 2015-08-13 2021-03-02 索尼公司 无线通信系统中的电子设备和无线通信方法
KR20170123236A (ko) * 2016-04-28 2017-11-07 엘지전자 주식회사 데이터 볼륨 정보를 전송하는 방법 및 사용자기기
EP3498035B1 (en) * 2016-08-10 2023-12-13 InterDigital Patent Holdings, Inc. Light connectivity and autonomous mobility
US10750410B2 (en) * 2016-09-30 2020-08-18 Huawei Technologies Co., Ltd. Ultra reliable low latency connection support in radio access networks
CN108064078B (zh) * 2016-11-08 2021-09-28 华硕电脑股份有限公司 通信系统中的触发功率余量回报用于波束运作的方法与设备
US10716094B2 (en) * 2017-03-23 2020-07-14 Ofinno, Llc Packet duplication in a wireless device and wireless network
KR102357594B1 (ko) * 2017-03-23 2022-02-04 삼성전자 주식회사 패킷 중복을 위한 데이터 처리 방법 및 장치
US11005606B2 (en) * 2017-03-24 2021-05-11 Telefonaktiebolaget Lm Ericsson (Publ) Systems and methods for removal of duplicated packets for transmission
US10536878B2 (en) * 2017-03-24 2020-01-14 Mediatek Inc. User equipment and methods for PDCP duplication in 5G RAN
KR102625204B1 (ko) * 2017-04-24 2024-01-16 모토로라 모빌리티 엘엘씨 무선 베어러에 대한 pdcp pdu들의 복제
EP3399724B1 (en) * 2017-05-05 2022-10-05 ASUSTek Computer Inc. Method and apparatus of transmitting data duplication in a wireless communication system
US11212701B2 (en) * 2017-05-14 2021-12-28 FG Innovation Company Limited Systems, methods, and devices for ultra-reliable low latency communication quality-of-service guarantee
CN109150432A (zh) * 2017-06-15 2019-01-04 夏普株式会社 无线通信方法和设备
EP3923499B1 (en) * 2017-06-15 2023-02-15 Samsung Electronics Co., Ltd. Packet duplication control
CN115297507A (zh) * 2017-06-16 2022-11-04 三星电子株式会社 用于在下一代移动通信系统中处理分组的方法和装置
SG11201912191QA (en) * 2017-06-16 2020-01-30 Nokia Technologies Oy Communication apparatus, method and computer program
CN110771076B (zh) * 2017-07-28 2022-05-03 富士通株式会社 命令指示方法及装置、信息交互方法及装置
US10687248B2 (en) * 2017-09-25 2020-06-16 Ofinno, Llc Packet duplication activation and deactivation
WO2019137641A1 (en) * 2018-01-11 2019-07-18 Telefonaktiebolaget Lm Ericsson (Publ) Submitting a pdcp pdu for transmission
US10869223B2 (en) * 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
US11212695B2 (en) * 2018-02-15 2021-12-28 Qualcomm Incorporated Configuration, activation and deactivation of packet duplication
KR102598001B1 (ko) * 2018-06-18 2023-11-06 삼성전자 주식회사 이동 통신 시스템에서 효율적인 패킷 중복 전송을 위한 방법 및 장치
KR102601489B1 (ko) * 2018-06-20 2023-11-13 삼성전자 주식회사 차세대 이동통신 시스템에서 이중연결구조를 고려하여 패킷 중복을 제어하는 방법 및 장치
US11540205B2 (en) * 2018-08-08 2022-12-27 Lenovo (Singapore) Pte. Ltd. Method and apparatus for applying a cell restriction configuration
EP3912300B1 (en) * 2019-01-18 2023-06-07 FG Innovation Company Limited Packet data convergence protocol duplication in next generation wireless networks

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104885546A (zh) * 2013-11-01 2015-09-02 三星电子株式会社 用于获取终端的系统帧号的方法、终端、以及移动通信系统
US20160065700A1 (en) * 2014-08-29 2016-03-03 Lg Electronics Inc. Pdcp operation in a wireless communication system supporting dual connectivity

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED: "Further details of PDCP duplication in CA case", 3GPP TSG-RAN WG2 MEETING #98, no. R2-1705055, 6 May 2017 (2017-05-06), Hangzhou, China, XP051264703 *
See also references of EP3641186A4 *
SHARP: "Enable/Disable PDCP Duplication", 3GPP TSG-RAN MEETING #98, no. R2-1704941, 5 May 2017 (2017-05-05), Hangzhou, China, XP051263897 *
ZTE: "Consideration on the activation/deactivation of data duplication for CA", 3GPP TSG-RAN WG2 MEETING #98, no. R2-1704660, 5 May 2017 (2017-05-05), Hangzhou, China, XP051263847 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020198336A1 (en) * 2019-03-28 2020-10-01 Apple Inc. Data duplication over radio link control channels
CN111757520A (zh) * 2019-03-29 2020-10-09 华为技术有限公司 一种数据传输方法及装置
EP3937559A4 (en) * 2019-03-29 2022-05-11 Huawei Technologies Co., Ltd. DATA TRANSMISSION METHOD AND DEVICE
CN111757520B (zh) * 2019-03-29 2023-12-12 华为技术有限公司 一种数据传输方法及装置
CN112218312A (zh) * 2019-07-12 2021-01-12 诺基亚技术有限公司 上行链路数据复制的灵活网络控制

Also Published As

Publication number Publication date
CN109150415B (zh) 2022-01-21
CN109150415A (zh) 2019-01-04
SG11201911793VA (en) 2020-01-30
US11388626B2 (en) 2022-07-12
US20210144583A1 (en) 2021-05-13
EP3641186A4 (en) 2020-09-02
TWI692988B (zh) 2020-05-01
TW201906465A (zh) 2019-02-01
EP3641186A1 (en) 2020-04-22

Similar Documents

Publication Publication Date Title
WO2018228289A1 (zh) 基站、用户设备和相关方法
WO2018171546A1 (zh) 用户设备和基站处执行的方法及相应的设备
WO2018171512A1 (zh) 无线配置方法、用户设备和基站
TWI678124B (zh) 使用者設備和相關方法
JP7288941B2 (ja) 無線システムにおける段階的再構成のためのシステムおよび方法
WO2018228283A1 (zh) 无线通信方法和设备
WO2019134529A1 (zh) 用户设备和相关方法
EP3637820B1 (en) Base station, user equipment and relevant methods
WO2018059147A1 (zh) 用于建立/重配置数据承载的方法和设备
WO2018199079A1 (ja) 端末装置、基地局装置、通信方法、および、集積回路
WO2019029565A1 (zh) 用户设备、基站和相关方法
WO2018228326A1 (zh) 用于数据分组递送的方法、用户设备和基站
WO2018228328A1 (zh) 无线配置方法和相应的用户设备
KR20170041658A (ko) 단말이 이중 연결 시스템에서의 pdcp pdu를 처리하는 방법 및 그 장치
JP2014513467A (ja) 移動通信システムでキャリアアグリゲーションをサポートするランダムアクセスの制御方法及び装置
KR102025420B1 (ko) 이중연결 방식을 이용하는 무선통신 시스템에서 불연속 수신을 위한 파라미터 구성 방법 및 장치
WO2018054185A1 (zh) 用户设备、基站和相关方法
WO2018059148A1 (zh) 一种数据转发的方法及其设备
WO2020221155A1 (zh) 基站、用户设备和相关方法
CN117750547A (zh) 由用户设备执行的方法及用户设备
CN117769052A (zh) 由用户设备执行的方法及用户设备

Legal Events

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

Ref document number: 18817544

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018817544

Country of ref document: EP

Effective date: 20200115