WO2018171512A1 - 无线配置方法、用户设备和基站 - Google Patents

无线配置方法、用户设备和基站 Download PDF

Info

Publication number
WO2018171512A1
WO2018171512A1 PCT/CN2018/079226 CN2018079226W WO2018171512A1 WO 2018171512 A1 WO2018171512 A1 WO 2018171512A1 CN 2018079226 W CN2018079226 W CN 2018079226W WO 2018171512 A1 WO2018171512 A1 WO 2018171512A1
Authority
WO
WIPO (PCT)
Prior art keywords
drb
packet
logical channel
data
base station
Prior art date
Application number
PCT/CN2018/079226
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/496,054 priority Critical patent/US11324059B2/en
Publication of WO2018171512A1 publication Critical patent/WO2018171512A1/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/22—Arrangements for detecting or preventing errors in the information received using redundant apparatus to increase reliability
    • 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/0278—Traffic management, e.g. flow control or congestion control using buffer status reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H04W28/065—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information using assembly or disassembly of packets
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/34—Selective release of ongoing connections

Definitions

  • the present disclosure relates to the field of wireless communication technologies. More specifically, the present disclosure relates to a wireless configuration method, a user equipment, and a base station.
  • 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 data plane in the NR-PDCP entity is achieved, the PDCP entity function support packet repetition at the transmitting end and the PDCP entity function support removal packet repetition at the receiving end.
  • the packet repeatedly uses PDCP PDUs and/or SDUs to transmit on multiple logical channels and makes repeated PDCP PDUs pass differently. Carrier transmission.
  • the present application mainly solves the problem of how the base station configures a packet for the user equipment (UE) to repeat the DRB and how the user equipment calculates the data to be transmitted by the PDCP entity in the multi-connection scenario and the carrier aggregation scenario in which the packet is repeated.
  • a method performed by a user equipment UE comprising: receiving radio resource control RRC signaling, the RRC signaling comprising a data radio bearer DRB for configuring a support packet repetition for the UE Configuration information; and establishing a corresponding DRB according to the configuration information.
  • the method further comprises calculating and reporting transmittable data of the packet data convergence protocol PDCP entity for a logical channel corresponding to the established DRB.
  • the configuration information includes: two or more logical channel identifiers for which the DRB is repeated for the packet; or a logical channel identifier for the packet repetition DRB and an indication identifier for the packet repetition DRB.
  • establishing a corresponding DRB according to the configuration information includes: establishing and configuring a PDCP entity and configuring a PDCP entity to enable a packet repetition function; establishing and configuring a radio link control RLC entity; and establishing and configuring a logical channel.
  • calculating and reporting the transmittable data of the PDCP entity includes: when the media access control MAC entity triggers the buffer status report BSR and calculates the buffer size, the PDCP entity transmittable data indication to the two associated with the packet repeat DRB One or more logical channels.
  • the logical channel group identity corresponding to the packet repetition DRB is predefined; or the logical channel group identity corresponding to the packet repetition DRB is included in the configuration information.
  • calculating and reporting the transmittable data of the PDCP entity includes indicating the PDCP entity transmittable data to the MAC entity configured for the secondary cell group SCG and the MAC entity configured for the primary cell group MCG.
  • a user equipment UE including a processor and a memory. Instructions are stored on the memory. The instructions, when executed by the processor, perform the method according to the above.
  • a method performed by a base station comprising: configuring radio resource control RRC signaling, the RRC signaling comprising a data radio bearer DRB for configuring a support packet repetition for a user equipment UE Configuring information; and transmitting the RRC signaling to the UE.
  • a base station including a processor and a memory. Instructions are stored on the memory. The instructions, when executed by the processor, perform the method according to the above.
  • 1 is a schematic diagram showing packet repetition MCG separation DRB data transmission according to an embodiment of the present application
  • FIG. 2 is a schematic diagram showing packet repeated SCG split DRB data transmission according to an embodiment of the present application
  • 3(a)-3(b) are diagrams showing a protocol architecture in a user equipment according to an embodiment of the present application.
  • FIG. 4(a) is a flow chart showing a method performed by a user equipment in accordance with one embodiment of the present application
  • 4(b) is a flowchart showing a method performed by a base station according to an embodiment of the present application
  • FIG. 5(a) is a block diagram showing a user equipment according to an embodiment of the present application.
  • FIG. 5(b) is a block diagram showing a base station according to an embodiment of the present application.
  • 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 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.
  • 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 addressed 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
  • the primary base station in the present disclosure is referred to as an MeNB. It should be noted that all schemes 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 schemes or definitions applicable to the SeNB are also applicable to the SgNB.
  • Primary cell Primary Cell, PCell. A cell operating on the primary frequency on which the UE performs an initial connection setup procedure or initiates a connection re-establishment procedure or is designated as a primary cell in the handover procedure.
  • 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 associated with a primary base station or a secondary base station. 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, the scheduler being able to pass 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.
  • BSR Buffer Status Report, cache status report. Information for providing the serving base station with the amount of data to be transmitted in the uplink buffer corresponding to the associated MAC entity.
  • DRB Data Radio Bearer carrying user plane data, data radio bearer or simply data bearer.
  • 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. Unless otherwise specified, the separation DRB described in the present disclosure may be an MCG separation DRB or an SCG separation DRB.
  • 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 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 that separates the SRB and/or the RRC are located in the primary base station (ie, the signaling of the primary base station is forwarded to the secondary base station, and the signaling is separated in the primary base station), it is called MCG separation SRB; if the PDCP entity of the SRB is separated and / Or the RRC is located in the secondary base station (that is, the signaling of the secondary base station is forwarded by the secondary base station to the primary base station, and the signaling is separated in the secondary base station), which is called the SCG separation SRB.
  • the isolated SRB in the present invention may be an MCG-separating SRB or an SCG-separating SRB.
  • the separation carrier in the present invention may be a separation SRB or a separation DRB.
  • the MCG split carrier can be an MCG split SRB or an MCG split DRB.
  • the SCG split bearer may be an SCG split SRB or an SCG split DRB.
  • Packet duplication It can also be called data duplication or packet duplication.
  • the same data (or a packet, that is, a PDCP PDU or a PDCP SDU) is transmitted in multiple CG serving cells, that is, the same data is in multiple different bearers (for example, data bearer DRB or signaling bearer) SRB) transmitting or the same data simultaneously using the resource transmission provided by the primary base station (or MCG) and the secondary base station (or SCG) or the same data is sent to the lower layer (or RLC layer) located at the MCG or SCG or the PDCP entity to the same PDCP PDU. Send to multiple lower-level entities (or RLC entities) associated with the association.
  • the PDCP entity sends the same PDCP PDU to multiple RLC entities (or lower layer entities) and/or logical channels, and sends them to the receiving end through different carriers (or serving cells);
  • the PDCP entity is responsible for detecting and deleting duplicate PDCP PDUs or SDUs.
  • Packet Duplicate Bearer A DRB or SRB that supports packet repetition in carrier aggregation or single-link mode.
  • the DRB or SRB is associated with one PDCP entity, one or more RLC entities, multiple logical channels, and one or more MAC entities and the transmitting PDCP entity sends duplicate or same PDCP PDUs to the one or more RLCs
  • the entity and/or multiple logical channels are sent to the receiving end through different carriers; the receiving PDCP entity removes duplicate PDCP PDUs or SDUs from the underlying entity.
  • a multi-connection data transmission mode or DRB or SRB which is a separate DRB or SRB that supports packet repetition.
  • the same data (or the same PDCP PDU) is transmitted on multiple radio protocols separating the DRB or SRB, including packet repetition MCG separation DRB, packet repetition SCG separation DRB, repeated MCG separation SRB, and packet repetition SCG. Separate the SRB. If the packet repeats the MCG separation DRB or SRB, the PDCP entity located at the primary base station or the MCG is responsible for packet repetition and/or repeated packet removal; if the packet repeats the SCG separation DRB or SRB, the PDCP is located at the secondary base station or the SCG. The entity is responsible for packet duplication and/or duplicate packet removal.
  • pdcp-Config cell A configurable PDCP parameter containing the DRB.
  • rlc-Config cell Contains configuration information of the RLC entity corresponding to the SRB and the DRB.
  • logicalChannelIdentity cell Logical channel identifier
  • logicalChannelConfig cell Contains parameters used to configure the logical channel.
  • logicalChannelGroup A logical channel group identifier used to map a logical channel to a logical channel group for BSR reporting.
  • FIG. 1 is a schematic diagram of performing downlink packet repetition MCG separation DRB transmission between a base station and a user equipment UE. It should be understood that the same protocol architecture may be adopted for performing uplink packet repetition 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.
  • a Packet Data Convergence Protocol Protocol Data Unit (PDCP PDU) is transmitted on a plurality of radio protocols (corresponding to a plurality of RLC entities associated with the same PDCP entity) separating the DRBs, utilizing MeNB and SeNB resources.
  • PDCP PDU packet repeated multi-connection mode 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.
  • the interface is denoted as Xx
  • the MeNB is a gNB and the SeNB is an eLTE eNB
  • the interface is denoted as Xn.
  • FIG. 2 is a schematic diagram showing downlink packet repeat SCG separation DRB transmission between a base station and a user equipment UE. It should be understood that the same protocol architecture may be adopted for performing uplink packet repetition 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.
  • a Packet Data Convergence Protocol Protocol Data Unit (PDCP PDU) is transmitted on a plurality of radio protocols (corresponding to a plurality of RLC entities associated with the same PDCP entity) separating the DRBs, utilizing MeNB and SeNB resources.
  • PDCP PDU packet repeated multi-connection mode 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.
  • the interface is denoted as Xx
  • the MeNB is a gNB and the SeNB is an eLTE eNB
  • the interface is denoted as Xn.
  • a packet also referred to as a packet
  • PDCP PDU or an SDU repeatedly transmitted twice i.e., one PDCP entity associates two RLC entities and/or two logical channels.
  • the technical solution of the present disclosure is not limited to a scenario in which a packet PDCP PDU or an SDU is repeatedly transmitted twice.
  • Those skilled in the art can extend it to the scenario of repeatedly transmitting multiple times after reading the following (for example, one PDCP entity associates multiple RLC entities and/or multiple logical channels).
  • 3(a)-3(b) are diagrams showing the protocol architecture in the user equipment UE in the carrier aggregation scenario. Specifically, in the schematic diagram shown in FIG. 3(a), one DRB is mapped to one PDCP entity, two RLC entities, and two logical channels, one MAC entity; and in the schematic diagram shown in FIG. 3(b), one The DRB is mapped to one PDCP entity, two RLC entities, and two logical channels, two MAC entities.
  • FIG. 4(a) is a flow chart showing a method 40a performed by a user equipment in accordance with one embodiment of the present application.
  • the method 40a begins at step S400.
  • the user equipment receives RRC signaling (for example, an RRC connection reconfiguration message) from the base station, where the RRC signaling includes configuring configuration information of the DRB supporting the packet repetition for the user equipment.
  • RRC signaling for example, an RRC connection reconfiguration message
  • the DRB may be a packet repetition DRB, a packet repetition MCG separation DRB, or a packet repetition SCG separation DRB.
  • step S420 the user equipment establishes a corresponding DRB according to the received DRB configuration information.
  • step S430 the user equipment calculates PDCP entity transmittable data for the logical channel corresponding to the established DRB.
  • method 40a ends at step S440.
  • FIG. 4(b) is a flow chart showing a method 40b performed by a base station in accordance with an embodiment of the present application.
  • the method 40b begins at step S450.
  • the base station configures radio resource control RRC signaling (e.g., RRC connection reconfiguration message), the RRC signaling including configuration information for configuring a data radio bearer DRB supporting the packet repetition for the user equipment UE.
  • RRC signaling e.g., RRC connection reconfiguration message
  • the DRB may be a packet repetition DRB, a packet repetition MCG separation DRB, or a packet repetition SCG separation DRB.
  • step S470 the base station sends the RRC signaling to the user equipment.
  • method 40b ends at step S480.
  • the base station repeats the DRB for the user equipment configuration packet.
  • the user equipment receives RRC signaling (eg, an RRC connection reconfiguration message) from the base station, where the RRC signaling includes configuration information for the user equipment configuration packet to repeat the DRB.
  • RRC signaling eg, an RRC connection reconfiguration message
  • two logical channel identifiers are configured in the RRC signaling for the packet repetition DRB.
  • An example of packet repeat DRB configuration information is given below:
  • the RRC signaling configures a logical channel identifier for the packet repetition DRB
  • the RRC signaling further includes a packet repetition DRB indication identifier.
  • the indication identifier is used to indicate that the DRB is a packet repetition DRB or a DRB supporting a packet repetition function or a corresponding PDCP entity supports a PDCP PDU repeatedly transmitted two or more times or a corresponding PDCP entity support packet repetition function. For example, when the indication identifier takes a value of “1” or “TRUE” or “Setup” or the identifier appears, it indicates that the corresponding DRB is a PDCP entity supporting the DRB or the DRB supporting the packet repetition function or supporting the packet repetition function.
  • Each PDCP PDU is repeatedly sent two or more times or the corresponding PDCP entity supports the packet repetition function; when the identifier takes a value of "0" or "FALSE” or “Release” or the identifier does not appear, the corresponding The DRB is not a packet repeating DRB or a DRB that does not support the packet repetition function or the corresponding PDCP entity does not support repeated transmission of PDCP PDUs or the corresponding PDCP entity does not support the packet repetition function.
  • An example of packet repeat DRB configuration information is given below:
  • the user equipment establishes a packet repetition DRB according to the received configuration information.
  • the user equipment establishes a corresponding DRB according to the configuration information of the DRB carried in the RRC signaling.
  • the process of establishing a DRB may include the following operations:
  • the PDCP entity is configured according to the security configuration of the MCG and the pdcp-Config (if the SCG DRB is established, the PDCP entity is configured according to the security configuration of the SCG); optionally, the PDCP entity is also configured to be enabled.
  • Packet repetition function (the enabling packet repetition function in the present disclosure may also be expressed as configuring the PDCP entity to send the same PDCP PDU to the associated multiple lower layer entities or RLC entities); or, configuring the PDCP entity does not enable the packet repetition function. .
  • the PDCP entity sends the PDCP PDU to a lower layer entity, that is, each PDCP PDU is not repeatedly transmitted.
  • the PDCP PDU is sent only through RLC entities whose logical channel identifies a smaller or smallest (or larger or largest) logical channel association.
  • the PDCP PDU is transmitted only through the RLC entity whose logical channel identifies a small or smallest or larger or largest logical channel association.
  • One or two MCG RLC entities are established according to the received rlc-Config (if the SCG DRB is established, an MCG RLC and an SCG RLC are established). If only one rlc-Config configuration is received, the two MCG RLC entities adopt the same rlc-Config configuration. Otherwise, the corresponding RLC entity is configured according to the two received rlc-Configs.
  • the process of establishing a DRB may include the following operations:
  • Establishing a PDCP entity and configuring the PDCP entity according to the security configuration of the MCG and pdcp-Config (if the SCG DRB is established, the PDCP entity is configured according to the security configuration of the SCG); optionally, if the RRC signaling includes a packet The DRCP indication is repeated, and the PDCP entity is configured to enable the packet repetition function. Alternatively, if the RRC signaling includes the packet repetition DRB indication identifier, the configuration PDCP entity does not enable the packet repetition function. If the packet repetition function of the PDCP entity is not enabled, the PDCP entity sends the PDCP PDU to a lower layer entity, that is, each PDCP PDU is not repeatedly transmitted.
  • the PDCP PDU is transmitted only through the RLC entity associated with the logical channel identification of a smaller (or larger) logical channel.
  • the PDCP PDU is transmitted only through the RLC entity whose logical channel identifies a small or smallest or larger or largest logical channel association.
  • one or two MCG RLC entities are established according to the received rlc-Config (if the packet is repeated SCG DRB, an MCG RLC and an SCG RLC are established). If only one rlc-Config configuration is received, the two MCG RLC entities adopt the same rlc-Config configuration. Otherwise, the corresponding RLC entity is configured according to the two received rlc-Configs.
  • two MCG DTCH logical channels are established according to the received logical channel identifier (recorded as logicalChannelIdentity) and the logical channel configuration (denoted as logicalChannelConfig) (if the packet repeat SCG DRB is established, an MCG DTCH is established) And a SCG DTCH).
  • the logical channel identifiers of the two MCG DTCH logical channels are different.
  • the identifier of one logical channel is a value carried in the RRC signaling, and the identifier of the other logical channel can be obtained according to a predefined rule.
  • the rule includes that the identifier of another logical channel is a logical channel identifier carried in the RRC signaling plus an offset, and the offset may be a predefined or default value. If more than two logical channels are configured for one DRB, the identifiers of the other logical channels may be sequentially assigned to the logical channel identifiers configured in the RRC signaling plus 1x, 2x, 3x... shift.
  • the offset is a maximum value MAX_LogicalChannel_Identity of a logical channel identifier supported by the system (or configurable or defined).
  • the identifier of one logical channel corresponding to the packet repetition DRB is 5, and another logical channel identifier is For 15, the third logical channel is identified as 25, and so on.
  • the two MCG DTCH logical channels may be configured with the same or different logical channels; if two logical channel configurations are received, the two MCG DTCHs adopt different logical channel configurations; otherwise, the same logical channel configuration is employed.
  • the MAC layer identifies the logical channel (or packet or RLC PDU) from the logical channel identified by the logical channel i and the logical channel as the logical channel of i+MAX_LogicalChannel_Identity (or the logical channel identifier is j and j satisfies j)
  • the RRC signaling of the configured DRB may further include an indication identifier, where the indication identifier is used to indicate the number of logical channels and/or the RLC entity corresponding to the DRB. number.
  • the user equipment establishes a corresponding number of RLC entities and/or logical channels according to the indication identifier and sets corresponding logical channel identifiers according to the method given in the foregoing embodiment.
  • User equipment calculates PDCP to transmit data
  • the transmittable data of the PDCP entity can be defined as follows:
  • the PDCP SDU, the SDU corresponding PDU has not been delivered to the next layer (or RLC layer), and the next layer may be the next layer corresponding to the logical channel.
  • the next layer may include: an SDU that has not been processed by the PDCP and a PDU that has been processed by the PDCP.
  • the user equipment reports PDCP to transmit data.
  • the PDCP entity transmittable data is indicated to two logical channels of a packet repetition DRB or a packet repetition SRB association.
  • the packet repetition function of the PDCP entity is enabled
  • the PDCP entity may transmit the data indication to the two logical channels of the packet repetition DRB or the packet repetition SRB association; Otherwise, only the PDCP entity transmittable data indicates to the smaller or the smallest or the largest or largest of the logical channel identifiers of the two logical channels of the packet repetition DRB or the packet repetition SRB association.
  • the logical channel group identity corresponding to the packet repetition DRB or the packet repetition SRB is predefined.
  • the predefined logical channel group identifier is associated with (or applied to) one logical channel DTCH or two logical channels of the established packet repetition DRB or packet repetition SRB. DTCH. If associated with a logical channel DTCH, the logical channel group identity can be associated to the smaller or smallest or larger or largest of the logical channel identifiers.
  • the predefined logical channel group identifier is applied only to the packet repetition DRB.
  • the logical channel group identity of the packet repetition DRB or packet repetition SRB is included in the RRC signaling for configuring the packet repetition DRB or the packet repetition SRB.
  • the logical channel group identifier is associated with (or applied to) one logical channel DTCH or two logical channels DTCH of the established packet repetition DRB or packet repetition SRB. . If associated with a logical channel DTCH, the logical channel group identity can be associated to the smaller or smallest or larger or largest of the logical channel identifiers.
  • the same logical channel group identifier is allocated for the packet repetition DRB, and the packet repetition DRB and the DRB that does not support the packet repetition allocate different logical channel identifiers.
  • User equipment reports PDCP to transmit data in a multi-connection scenario.
  • the user equipment receives RRC signaling from the base station, such as an RRC connection reconfiguration message, the RRC signaling is used to repeatedly separate the DRB for the UE (including the MCG split DRB and the SCG split DRB) or the packet repeat split SRB (including the MCG split) SRB and SCG separate SRB).
  • RRC signaling is used to repeatedly separate the DRB for the UE (including the MCG split DRB and the SCG split DRB) or the packet repeat split SRB (including the MCG split) SRB and SCG separate SRB).
  • the user equipment repeats the separation of the DRB or the packet repetition separation SRB according to the received RRC signaling establishment packet.
  • the transmittable data in the PDCP entity is indicated to the MAC entity configured for the SCG and the MAC entity configured for the MCG. Further, in a case where the packet repetition function of the PDCP entity is enabled, the transmittable data in the PDCP entity is indicated to the MAC entity configured for the SCG and the MAC entity configured for the MCG.
  • FIG. 5 (a) is a block diagram showing user equipment 50a in accordance with one embodiment of the present application.
  • the user equipment 50a includes a processor 510a and a memory 520a.
  • Processor 510a can include, for example, a microprocessor, a microcontroller, an embedded processor, and the like.
  • the memory 520a may include, for example, a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a nonvolatile memory (such as a flash memory), or other memory.
  • Program instructions are stored on the memory 520a. The instructions, when executed by processor 510a, can perform the above-described methods performed by the user equipment as described in detail in this disclosure.
  • FIG. 5(b) is a block diagram showing a base station (BS) 50b in accordance with one embodiment of the present application.
  • the BS 50b includes a processor 510b and a memory 520b.
  • Processor 510b can include, for example, a microprocessor, a microcontroller, an embedded processor, and the like.
  • the memory 520b may include, for example, a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a nonvolatile memory (such as a flash memory), or other memory.
  • Program instructions are stored on the memory 520b. The instructions, when executed by processor 510b, can perform the above-described methods performed by the base station as described in detail in this disclosure.
  • a program for realizing the functions of the embodiments of the present disclosure may be recorded on a computer readable recording medium.
  • the corresponding functions can be realized by causing a 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 recording 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 disclosure may also be implemented using these new integrated circuit technologies in the context of new integrated circuit technologies that replace existing integrated circuits due to advances in semiconductor technology.
  • present disclosure is not limited to the above embodiment. Although various examples of the embodiment have been described, the present disclosure 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)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供了一种由用户设备UE执行的方法，包括：接收无线资源控制RRC信令，所述RRC信令包括用于为所述UE配置支持包重复的数据无线承载DRB的配置信息；根据所述配置信息建立相应的DRB；以及针对与所建立的DRB相对应的逻辑信道，计算分组数据汇聚协议PDCP实体的可传输数据。本申请还提供了一种相应的用户设备UE，以及一种基站和由基站执行的相应方法。图4(a)

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通过不同的载波发送。
发明内容
本申请主要解决在支持包重复的多连接场景和载波聚合场景下，基站如何为用户设备(UE)配置包重复DRB以及用户设备如何计算PDCP实体待发送数据的问题。
根据本发明的一个方面，提供了一种由用户设备UE执行的方法，包括：接收无线资源控制RRC信令，所述RRC信令包括用于为所述UE配置支持包重复的数据无线承载DRB的配置信息；以及根据所述配置信息建立相应的DRB。
在一个实施例中，所述方法还包括：针对与所建立的DRB相对应的逻辑信道，计算并报告分组数据汇聚协议PDCP实体的可传输数据。
在一个实施例中，所述配置信息包括：针对包重复DRB的两个或更多个逻辑信道标识；或者针对包重复DRB的逻辑信道标识以及针对包重复DRB的指示标识。
在一个实施例中，根据所述配置信息建立相应的DRB包括：建立和配置PDCP实体并配置PDCP实体去使能包重复功能；建立和配置无线链路控制RLC实体；以及建立和配置逻辑信道。
在一个实施例中，计算并报告PDCP实体的可传输数据包括：当媒体访问控制MAC实体触发缓存状态报告BSR且计算缓存大小时，将PDCP实体可传输数据指示给与包重复DRB相关联的两个或更多个逻辑信道。
在一个实施例中，与包重复DRB相对应的逻辑信道群标识是预定义的；或者与包重复DRB相对应的逻辑信道群标识包含在所述配置信息中。
在一个实施例中，计算并报告PDCP实体的可传输数据包括：将PDCP实体可传输数据指示给为辅小区组SCG配置的MAC实体和为主小区组MCG配置的MAC实体。
根据本发明的另一个方面，提供了一种用户设备UE，包括处理器以及存储器。所述存储器上存储有指令。所述指令在由所述处理器运行时执行根据上文所述的方法。
根据本发明的另一个方面，提供了一种由基站执行的方法，包括：配置无线资源控制RRC信令，所述RRC信令包括用于为用户设备UE配置支持包重复的数据无线承载DRB的配置信息；以及向所述UE发送所述RRC信令。
根据本发明的另一个方面，提供了一种基站，包括处理器以及存储器。所述存储器上存储有指令。所述指令在由所述处理器运行时执行根据上文所述的方法。
附图说明
通过下文结合附图的详细描述，本申请的上述和其它特征将会变得更加明显，其中：
图1是示出了根据本申请一个实施例的包重复MCG分离DRB数据传输的示意图；
图2是示出了根据本申请一个实施例的包重复SCG分离DRB数据传输的示意图；
[根据细则91更正 25.04.2018]　
图3(a)-3(b)是示出了根据本申请一个实施例的用户设备中的协议架构的示意图；
图4(a)是示出了根据本申请一个实施例的由用户设备执行的方法的流程图；
图4(b)是示出了根据本申请一个实施例的由基站执行的方法的流程图；
图5(a)是示出了根据本申请一个实施例的用户设备的框图；以及
图5(b)是示出了根据本申请一个实施例的基站的框图。
具体实施方式
下面结合附图和具体实施方式对本公开进行详细阐述。应当注意，本公开不应局限于下文所述的具体实施方式。另外，为了简便起见，省略了对与本公开没有直接关联的公知技术的详细描述，以防止对本公开的理解造成混淆。
下面首先描述本公开涉及的部分术语，如未特别说明，本公开涉及的术语采用此处定义。本公开给出的术语在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。
MAC：Medium Access Control，媒体访问控制。在本公开中，如未特别说明，MAC可以表示NR或LTE或eLTE中的MAC。
DTCH：Dedicated Traffic 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)，在多连接中，关联到主基站或辅基站的一组服务小区。需要说明的是，本公开所述的小区也可以称为光束集(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连接。本公开所述的多连接包括双连接。多连接数据传输方式包括但不限于：包重复，链路选择。
BSR：Buffer Status Report，缓存状态报告。用于向服务基站提供所关联的MAC实体对应的上行缓冲区待传输数据量的信息。
DRB：Data Radio Bearer carrying user plane data，数据无线承载或简称数据承载。
分离DRB：在多连接中，无线协议位于MeNB(或MgNB)和SeNB(或SgNB)且同时利用MeNB(或MgNB)和SeNB(或SgNB)资源的承载。如果分离DRB的PDCP实体位于主基站(即数据先到达主基站，由主基站转发给辅基站，实现数据在主基站中分离)，则称为MCG分离DRB；如果分离DRB的PDCP实体位于辅基站(即数据先到达辅基站，由辅基站转发给主基站，实现数据在辅基站中分离)，则称为SCG分离DRB。如未特别说明，本公开中所述分离DRB可以是MCG分离DRB，也可以是SCG分离DRB。
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：在多连接中，无线协议位于MeNB(或MgNB)和SeNB(或SgNB)且同时利用MeNB(或MgNB)和SeNB(或SgNB)资源的承载。如果分离SRB的PDCP实体和/或RRC位于主基站(即主基站的信令转发给辅基站，实现信令在主基站中分离)，则称为MCG分离SRB；如果分离SRB的PDCP实体和/或RRC位于辅基站(即辅基站的信令由辅基站转发给主基站，实现信令在辅基站中分离)，则称为SCG分离SRB。如未特别说明，本发明中所述分离SRB可以是MCG分离SRB，也可以是SCG分离SRB。
在本发明中所述分离承载可以是分离SRB或分离DRB。MCG分离承载可以是MCG分离SRB或MCG分离DRB。SCG分离承载可以是SCG分离SRB或SCG分离DRB。
包重复：也可称为数据重复或分组重复。在多连接方式下，同一数据(或称为包，即PDCP PDU或PDCP SDU)在多个CG的服务小区进行传输，即同一数据在多个不同的承载(例如，数据承载DRB或信令承载SRB)上发送或同一数据同时利用主基站(或MCG)和辅基站(或SCG)提供的资源传输或同一数据分别发送到位于MCG或SCG的下层(或RLC层)或PDCP实体将同一PDCP PDU发送到关联的多个下层实体(或RLC实体)。在载波聚合或单连接方式下，PDCP实体将同一PDCP PDU发送到多个RLC实体(或称下层实体)和/或逻辑信道，通过不同的载波(或称服务小区)发送给接收端；接收端PDCP实体负责检测并删除重复的PDCP PDU或SDU。
包重复承载：在载波聚合或单连接方式下，支持包重复功能的DRB或SRB。所述DRB或SRB关联到一个PDCP实体、一个或多个RLC实体、多个逻辑信道以及一个或多个MAC实体且发送端PDCP实体将重复的或同一PDCP PDU发送到所述一个或多个RLC实体和/或多个逻辑信道，通过不同的载波发送给接收端；接收端PDCP实体将来自下层实体的重复的PDCP PDU或SDU移除。
包重复分离承载：一种多连接下的数据发送方式或DRB或SRB，是支持包重复功能的分离DRB或SRB。在所述发送方式中，相同的数据(或同一PDCP PDU)在分离DRB或SRB的多个无线协议上发送，包括包重复 MCG分离DRB、包重复SCG分离DRB、重复MCG分离SRB和包重复SCG分离SRB。如果是包重复MCG分离DRB或SRB，则由位于主基站或MCG的PDCP实体负责包重复和/或重复包移除；如果是包重复SCG分离DRB或SRB，则由位于辅基站或SCG的PDCP实体负责包重复和/或重复包移除。
pdcp-Config信元：包含DRB的可配置的PDCP参数。
rlc-Config信元：包含SRB和DRB对应的RLC实体的配置信息。
logicalChannelIdentity信元：逻辑信道标识。
logicalChannelConfig信元：包含用于配置逻辑信道的参数。
logicalChannelGroup信元：逻辑信道群标识，用于将逻辑信道映射到用于BSR上报的逻辑信道群。
图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。
图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。
下面的实施例以数据包(也可称为分组)PDCP PDU或SDU重复发送两次为例(即一个PDCP实体关联两个RLC实体和/或两个逻辑信道)进行说明。然而，本公开的技术方案并不限于数据包PDCP PDU或SDU重复发送两次的场景。本领域技术人员可以在阅读下文后将其扩展到重复发送多次的场景(例如，一个PDCP实体关联多个RLC实体和/或多个逻辑信道)。
[根据细则91更正 25.04.2018]　
图3(a)-3(b)给出了载波聚合场景下用户设备UE中的协议架构示意图。具体地，在图3(a)所示的示意图中，一个DRB映射到一个PDCP实体、两个RLC实体和两个逻辑信道、一个MAC实体；而在图3(b)所示示意图中，一个DRB映射到一个PDCP实体、两个RLC实体和两个逻辑信道、两个MAC实体。
图4(a)是示出了根据本申请一个实施例的由用户设备执行的方法40a的流程图。该方法40a从步骤S400处开始。
在步骤S410，用户设备接收来自基站的RRC信令(例如，RRC连接重配置消息)，所述RRC信令中包含为用户设备配置支持包重复的DRB的配置信息。例如，该DRB可以是包重复DRB、包重复MCG分离DRB或包重复SCG分离DRB。
在步骤S420，用户设备根据接收到的DRB配置信息建立对应的DRB。
可选的，在步骤S430，用户设备为所建立的DRB对应的逻辑信道计算PDCP实体可传输数据。
最后，方法40a在步骤S440结束。
图4(b)是示出了根据本申请一个实施例的由基站执行的方法40b的流程图.该方法40b从步骤S450处开始。
在步骤S460，基站配置无线资源控制RRC信令(例如，RRC连接重配置消息)，所述RRC信令包括用于为用户设备UE配置支持包重复的数据无线承载DRB的配置信息。例如，该DRB可以是包重复DRB、包重复MCG分离DRB或包重复SCG分离DRB。
在步骤S470，基站向用户设备发送该RRC信令。
最后，方法40b在步骤S480结束。
下面，通过若干具体示例来描述图4(a)-(b)所示方法的各个步骤的实现。
基站为用户设备配置包重复DRB
用户设备接收来自基站的RRC信令(例如RRC连接重配置消息)，所述RRC信令中包含为用户设备配置包重复DRB的配置信息。
具体地，在一个实施例中，所述RRC信令中为包重复DRB配置了两个逻辑信道标识。下面给出了包重复DRB配置信息的一个示例：
Figure PCTCN2018079226-appb-000001
在另一个实施例中，所述RRC信令中为包重复DRB配置一个逻辑信道标识，同时RRC信令中还包含一个包重复DRB指示标识。所述指示标识用于指示DRB是包重复DRB或支持包重复功能的DRB或对应的PDCP实体支持PDCP PDU重复发送两次或多次或对应的PDCP实体支持包重复功能。例如，当所述指示标识取值为“1”或“TRUE”或“Setup”或所述标识出现时，表示对应的DRB是包重复DRB或支持包重复功能的DRB或DRB对应的PDCP实体支持每个PDCP PDU重复发送两次或多次或对应的PDCP实体支持包重复功能；当所述标识取值为“0”或“FALSE”或“Release”或所述标识不出现时，表示对应的DRB不是包重复DRB或不支持包重复功能的DRB或对应的PDCP实体不支持重复发送PDCP PDU或对应的PDCP实体不支持包重复功能。下面给出了包重复DRB配置信息的一个示 例：
Figure PCTCN2018079226-appb-000002
用户设备根据接收到的配置信息建立包重复DRB
用户设备根据RRC信令中携带的DRB的配置信息建立相应的DRB。
在一个实施例中，所述建立DRB的过程可以包括以下操作：
-建立PDCP实体并根据MCG的安全配置和pdcp-Config配置所述PDCP实体(如果是建立包重复SCG DRB，则按照SCG的安全配置配置PDCP实体)；可选的，还包含配置PDCP实体使能包重复功能(本公开中所述使能包重复功能也可以表述为配置PDCP实体将同一PDCP PDU发送到所关联的多个下层实体或RLC实体)；或者，配置PDCP实体不使能包重复功能。如果PDCP实体的包重复功能未使能，则PDCP实体将PDCP PDU发送到一个下层实体，即不会重复发送每个PDCP PDU。例如，将PDCP PDU仅通过逻辑信道标识较小或最小(或较大或最大)的逻辑信道关联的RLC实体发送。当接收到来自上层或MAC层或下层等的去使能PDCP的包重复功能的指令时，将PDCP PDU仅通过逻辑信道标识较小或最小或较大或最大的逻辑信道关联的RLC实体发送。
-根据接收到的rlc-Config建立一个或两个MCG RLC实体(如果建立包重复SCG DRB，则建立一个MCG RLC和一个SCG RLC)。如果只接收到一个rlc-Config配置，则所述两个MCG RLC实体采用相同的rlc-Config配置。否则，根据接收到的两个rlc-Config分别配置对应的RLC实体。
-根据接收到的两个逻辑信道标识(记为logicalChannelIdentity)和一 个或两个逻辑信道配置(记为logicalChannelConfig)建立两个MCG DTCH逻辑信道(如果建立包重复SCG DRB，则建立一个MCG DTCH和一个SCG DTCH)。所述两个MCG DTCH逻辑信道的逻辑信道标识不同，但可以采用相同或不同的逻辑信道配置。如果接收到两个逻辑信道配置，则为两个MCG DTCH采用不同的逻辑信道配置；否则，采用相同的逻辑信道配置。
在另一个实施例中，所述建立DRB的过程可以包括以下操作：
-建立PDCP实体并根据MCG的安全配置和pdcp-Config配置所述PDCP实体(如果是建立包重复SCG DRB，则按照SCG的安全配置配置PDCP实体)；可选的，如果RRC信令中包含包重复DRB指示标识，配置PDCP实体使能包重复功能；或者，如果RRC信令中包含包重复DRB指示标识，配置PDCP实体不使能包重复功能。如果PDCP实体的包重复功能未使能，则PDCP实体将PDCP PDU发送到一个下层实体，即不会重复发送每个PDCP PDU。例如，将PDCP PDU仅通过逻辑信道标识较小(或较大)的逻辑信道关联的RLC实体发送。当接收到来自上层或MAC层或下层等的去使能PDCP的包重复功能的指令时，将PDCP PDU仅通过逻辑信道标识较小或最小或较大或最大的逻辑信道关联的RLC实体发送。
-如果包含包重复DRB指示标识，根据接收到的rlc-Config建立一个或两个MCG RLC实体(如果建立包重复SCG DRB，则建立一个MCG RLC和一个SCG RLC)。如果只接收到一个rlc-Config配置，则所述两个MCG RLC实体采用相同的rlc-Config配置。否则，根据接收到的两个rlc-Config分别配置对应的RLC实体。
-如果包含包重复DRB指示标识，根据接收到的逻辑信道标识(记为logicalChannelIdentity)和逻辑信道配置(记为logicalChannelConfig)建立两个MCG DTCH逻辑信道(如果建立包重复SCG DRB，则建立一个MCG DTCH和一个SCG DTCH)。所述两个MCG DTCH逻辑信道的逻辑信道标识不同，其中一个逻辑信道的标识为RRC信令中携带的值，另一个逻辑信道的标识可以按照预先定义好的规则得到。所述规则包括另一个逻辑信道的标识是RRC信令中携带的逻辑信道标识加上一个偏移得到的值，所述偏移可以是预定义或缺省值。如果为一个DRB配置的逻辑信道超过两个，则其他逻辑信道的标识可以依次取值为RRC信令中配置的逻辑信道标识加上 1倍、2倍、3倍......的偏移。优选的，所述偏移为系统所支持的(或可配置的或定义的)逻辑信道标识的最大值MAX_LogicalChannel_Identity。例如，假设RRC信令中配置的包重复DRB的逻辑信道标识为5，系统定义的最大逻辑信道标识为10，则所述包重复DRB对应的一个逻辑信道的标识为5，另一个逻辑信道标识为15，第3个逻辑信道标识为25，依次类推。所述两个MCG DTCH逻辑信道可以采用相同或不同的逻辑信道配置；如果接收到两个逻辑信道配置，则两个MCG DTCH采用不同的逻辑信道配置；否则，采用相同的逻辑信道配置。
在本实施例中，MAC层将来自逻辑信道标识为i的逻辑信道的数据(或包或RLC PDU)和逻辑信道标识为i+MAX_LogicalChannel_Identity的逻辑信道(或的逻辑信道标识为j且j满足j mod MAX_LogicalChannel_Identity＝i的逻辑信道)的数据在不同的载波上发送。
在本实施例中，如果一个DRB配置多个逻辑信道，则在配置DRB的RRC信令中还可以包含一个指示标识，所述指示标识用于指示DRB所对应的逻辑信道数和/或RLC实体数。用户设备根据所述指示标识建立相应数量的RLC实体和/或逻辑信道并按上述实施例中给出的方法设置相应的逻辑信道标识。
用户设备计算PDCP可传输数据
对于包重复DRB或包重复分离DRB或包重复SRB或包重复分离SRB，可以定义PDCP实体的可传输数据为如下数据：
1、PDCP控制PDU；
2、PDCP SDU，所述SDU对应PDU尚未递交到下一层(或称RLC层)，所述下一层可以是所述逻辑信道对应的下一层。例如可以包括：还没有被PDCP处理的SDU和已经被PDCP处理后得到的PDU。
载波聚合场景下用户设备上报PDCP可传输数据
在一个实施例中，对于包重复DRB或包重复SRB，当MAC实体触发BSR且计算缓存大小时，将PDCP实体可传输数据指示给包重复DRB或包重复SRB关联的两个逻辑信道。进一步的，在使能了PDCP实体的包重复 功能情况下，当MAC实体触发BSR且计算缓存大小时，才将PDCP实体可传输数据指示给包重复DRB或包重复SRB关联的两个逻辑信道；否则，仅将PDCP实体可传输数据指示给包重复DRB或包重复SRB关联的两个逻辑信道中逻辑信道标识较小者或最小者或较大者或最大者。
在另一个实施例中，包重复DRB或包重复SRB对应的逻辑信道群标识是预定义的。在用户设备建立包重复DRB或包重复SRB的DTCH时，将预定义的逻辑信道群标识关联到(或应用于)所建立的包重复DRB或包重复SRB的一个逻辑信道DTCH或两个逻辑信道DTCH。如果是关联到一个逻辑信道DTCH，则可以将所述逻辑信道群标识关联到逻辑信道标识较小者或最小者或较大者或最大者。可选的，所述预定义的逻辑信道群标识只应用于包重复DRB。
在又一个实施例中，包重复DRB或包重复SRB的逻辑信道群标识包含在用于配置包重复DRB或包重复SRB的RRC信令中。在用户设备建立包重复DRB或包重复SRB的DTCH时，将所述逻辑信道群标识关联到(或应用于)所建立的包重复DRB或包重复SRB的一个逻辑信道DTCH或两个逻辑信道DTCH。如果是关联到一个逻辑信道DTCH，则可以将所述逻辑信道群标识关联到逻辑信道标识较小者或最小者或较大者或最大者。也可以为包重复DRB或包重复SRB的两个DTCH配置两个不同的逻辑信道群标识。可选的，为包重复DRB分配相同的逻辑信道群标识，包重复DRB和不支持包重复的DRB分配不同的逻辑信道标识。
多连接场景下用户设备上报PDCP可传输数据
用户设备接收来自基站的RRC信令，例如RRC连接重配置消息，所述RRC信令用于为UE配置包重复分离DRB(包括MCG分离DRB和SCG分离DRB)或包重复分离SRB(包括MCG分离SRB和SCG分离SRB)。
然后，用户设备根据接收到的RRC信令建立包重复分离DRB或包重复分离SRB。
对于所配置的包重复分离DRB或包重复分离SRB，将PDCP实体中的可传输数据指示给为SCG配置的MAC实体和为MCG配置的MAC实体。进一步的，在使能了PDCP实体的包重复功能情况下，才将PDCP实体中的可传输数据指示给为SCG配置的MAC实体和为MCG配置的MAC实体。
图5(a)是示出了根据本申请一个实施例的用户设备50a的框图。如图5(a)所示，该用户设备50a包括处理器510a和存储器520a。处理器510a例如可以包括微处理器、微控制器、嵌入式处理器等。存储器520a例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器等。存储器520a上存储有程序指令。该指令在由处理器510a运行时，可以执行本公开详细描述的由用户设备执行的上述方法。
图5(b)是示出了根据本申请一个实施例的基站(BS)50b的框图。如图5(b)所示，该BS 50b包括处理器510b和存储器520b。处理器510b例如可以包括微处理器、微控制器、嵌入式处理器等。存储器520b例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器等。存储器520b上存储有程序指令。该指令在由处理器510b运行时，可以执行本公开详细描述的由基站执行的上述方法。
另外，用于实现本公开各实施例功能的程序可以记录在计算机可读记录介质上。可以通过使计算机系统读取记录在所述记录介质上的程序并执行这些程序来实现相应的功能。此处的所谓“计算机系统”可以是嵌入在该设备中的计算机系统，可以包括操作系统或硬件(如外围设备)。“计算机可读记录介质”可以是半导体记录介质、光学记录介质、磁性记录介质、短时动态存储程序的记录介质、或计算机可读的任何其他记录介质。
用在上述实施例中的设备的各种特征或功能模块可以通过电路(例如，单片或多片集成电路)来实现或执行。设计用于执行本说明书所描述的功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、或其他可编程逻辑器件、分立的门或晶体管逻辑、分立的硬件组件、或上述器件的任意组合。通用处理器可以是微处理器，也可以是任何现有的处理器、控制器、微控制器、或状态机。上述电路可以是数字电路，也可以是模拟电路。因半导体技术的进步而出现了替代现有集成电路的新的集成电路技术的情况下，本公开的一个或多个实施例也可以使用这些新的集成电路技术来实现。
此外，本公开并不局限于上述实施例。尽管已经描述了所述实施例的 各种示例，但本公开并不局限于此。安装在室内或室外的固定或非移动电子设备可以用作终端设备或通信设备，如AV设备、厨房设备、清洁设备、空调、办公设备、自动贩售机、以及其他家用电器等。
如上，已经参考附图对本公开的实施例进行了详细描述。但是，具体的结构并不局限于上述实施例，本公开也包括不偏离本公开主旨的任何设计改动。另外，可以在权利要求的范围内对本公开进行多种改动，通过适当地组合不同实施例所公开的技术手段所得到的实施例也包含在本公开的技术范围内。此外，上述实施例中所描述的具有相同效果的组件可以相互替代。

Claims (10)

  1. 一种由用户设备UE执行的方法，包括：
    接收无线资源控制RRC信令，所述RRC信令包括用于为所述UE配置支持包重复的数据无线承载DRB的配置信息；以及
    根据所述配置信息建立相应的DRB。
  2. 根据权利要求1所述的方法，还包括：
    针对与所建立的DRB相对应的逻辑信道，计算并报告分组数据汇聚协议PDCP实体的可传输数据。
  3. 根据权利要求1所述的方法，其中，所述配置信息包括：
    针对包重复DRB的两个或更多个逻辑信道标识；或者
    针对包重复DRB的逻辑信道标识以及针对包重复DRB的指示标识。
  4. 根据权利要求1所述的方法，其中，根据所述配置信息建立相应的DRB包括：
    建立和配置PDCP实体并配置PDCP实体去使能包重复功能；
    建立和配置无线链路控制RLC实体；以及
    建立和配置逻辑信道。
  5. 根据权利要求2所述的方法，其中，计算并报告PDCP实体的可传输数据包括：当媒体访问控制MAC实体触发缓存状态报告BSR且计算缓存大小时，将PDCP实体可传输数据指示给与包重复DRB相关联的两个或更多个逻辑信道。
  6. 根据权利要求5所述的方法，其中，
    与包重复DRB相对应的逻辑信道群标识是预定义的；或者
    与包重复DRB相对应的逻辑信道群标识包含在所述配置信息中。
  7. 根据权利要求2所述的方法，其中，计算并报告PDCP实体的可传输数据包括：将PDCP实体可传输数据指示给为辅小区组SCG配置的MAC实体和为主小区组MCG配置的MAC实体。
  8. 一种用户设备UE，包括：
    处理器；以及
    存储器，所述存储器上存储有指令；
    其中，所述指令在由所述处理器运行时执行根据权利要求1-7中任意一 项所述的方法。
  9. 一种由基站执行的方法，包括：
    配置无线资源控制RRC信令，所述RRC信令包括用于为用户设备UE配置支持包重复的数据无线承载DRB的配置信息；以及
    向所述UE发送所述RRC信令。
  10. 一种基站，包括：
    处理器；以及
    存储器，所述存储器上存储有指令；
    其中，所述指令在由所述处理器运行时执行根据权利要求9所述的方法。
PCT/CN2018/079226 2017-03-23 2018-03-16 无线配置方法、用户设备和基站 WO2018171512A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US16/496,054 US11324059B2 (en) 2017-03-23 2018-03-16 Radio configuration method, user equipment, and base station

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710180714.9 2017-03-23
CN201710180714.9A CN108924871B (zh) 2017-03-23 2017-03-23 无线配置方法、用户设备和基站

Publications (1)

Publication Number Publication Date
WO2018171512A1 true WO2018171512A1 (zh) 2018-09-27

Family

ID=63584919

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/079226 WO2018171512A1 (zh) 2017-03-23 2018-03-16 无线配置方法、用户设备和基站

Country Status (3)

Country Link
US (1) US11324059B2 (zh)
CN (1) CN108924871B (zh)
WO (1) WO2018171512A1 (zh)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020088581A1 (zh) * 2018-10-31 2020-05-07 维沃移动通信有限公司 承载的控制方法、终端及网络侧设备
CN111132315A (zh) * 2018-10-31 2020-05-08 维沃移动通信有限公司 一种承载的控制方法、终端及网络侧设备
WO2022047684A1 (en) * 2020-09-03 2022-03-10 Qualcomm Incorporated Voice over new radio reliability enhancement by duplicate transmission of internet protocol multimedia subsystem signaling
US20220330030A1 (en) * 2019-12-31 2022-10-13 Huawei Technologies Co., Ltd. Communication method and apparatus
US11751268B2 (en) 2018-10-26 2023-09-05 Google Llc Efficient handling of a resource control state change and multi-node connectivity
US11792683B2 (en) 2018-10-30 2023-10-17 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Method for data processing, terminal device, and storage medium

Families Citing this family (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108631980B (zh) * 2017-03-24 2021-03-05 电信科学技术研究院 数据传输方法、终端、网络侧设备和计算机可读存储介质
WO2018184503A1 (en) * 2017-04-02 2018-10-11 Wei, Chia-Hung Logical channel data packet transmission method and wireless communication system
US11057956B2 (en) * 2017-06-02 2021-07-06 Lg Electronics Inc. Apparatus and method for performing packet duplication
CN109391639B (zh) * 2017-08-02 2021-01-08 维沃移动通信有限公司 一种激活及去激活数据复制的方法及终端
US10772008B2 (en) * 2018-01-11 2020-09-08 Comcast Cable Communications, Llc Cell configuration for packet duplication
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
KR102632780B1 (ko) * 2018-05-10 2024-02-02 삼성전자주식회사 무선 통신 시스템에서 서비스를 제공하기 위한 장치 및 방법
CN111315027B (zh) * 2018-12-11 2024-03-12 夏普株式会社 用户设备及其方法、基站及其方法
CN111314970A (zh) * 2018-12-11 2020-06-19 夏普株式会社 用户设备及其方法、基站及其方法
WO2020155124A1 (zh) * 2019-02-01 2020-08-06 Oppo广东移动通信有限公司 复制数据的传输方法、终端设备及接入网设备
JP2020156028A (ja) * 2019-03-22 2020-09-24 シャープ株式会社 端末装置、基地局装置、方法、および、集積回路
CN111465119B (zh) * 2019-03-28 2023-02-24 维沃移动通信有限公司 数据发送方法、信息配置方法、终端及网络设备
CN111865520A (zh) * 2019-04-28 2020-10-30 夏普株式会社 基站、用户设备和相关方法
CN112789879B (zh) * 2019-04-30 2023-02-28 Oppo广东移动通信有限公司 一种无线链路失败处理方法、网络设备、终端设备
CN112153692B (zh) * 2019-06-27 2022-04-15 大唐移动通信设备有限公司 一种无线承载的缓存上报方法及装置
CN114642023A (zh) * 2020-01-20 2022-06-17 Oppo广东移动通信有限公司 通信方法、装置、设备及存储介质
CN113452487B (zh) * 2020-03-25 2022-09-13 展讯通信（上海）有限公司 数据传输方法及装置
WO2023106066A1 (ja) * 2021-12-06 2023-06-15 ソニーグループ株式会社 通信装置、通信方法、及び通信システム

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104244450A (zh) * 2013-06-21 2014-12-24 中兴通讯股份有限公司 长期演进业务和集群业务并发时重建立方法、基站和用户设备
US20150215826A1 (en) * 2014-01-30 2015-07-30 Sharp Laboratories Of America, Inc. Systems and methods for dual-connectivity operation
CN106211352A (zh) * 2015-05-04 2016-12-07 中兴通讯股份有限公司 数据无线承载的建立方法和装置
CN106304398A (zh) * 2015-05-15 2017-01-04 夏普株式会社 用于重配置数据承载的方法和用户设备
CN107342851A (zh) * 2017-06-15 2017-11-10 电信科学技术研究院 一种重复传输的配置及重复传输方法及装置

Family Cites Families (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101000699B1 (ko) * 2004-04-19 2010-12-10 엘지전자 주식회사 무선링크 제어계층에서의 데이터 처리방법
US20090016301A1 (en) * 2007-07-11 2009-01-15 Interdigital Technology Corporation Packet data convergence protocol operations
CN101547070A (zh) * 2008-03-24 2009-09-30 华为技术有限公司 一种数据包类型的判断方法及其装置
US20160021581A1 (en) * 2013-01-17 2016-01-21 Interdigital Patent Holdings, Inc. Packet data convergence protocol (pdcp) placement
CN104349387B (zh) * 2013-08-08 2018-08-14 上海诺基亚贝尔股份有限公司 在支持双/多连接的系统中用于下行链路传输的方法和设备
EP2854444A1 (en) * 2013-09-27 2015-04-01 Panasonic Intellectual Property Corporation of America Efficient uplink scheduling mechanism for dual connectivity
US9635655B2 (en) * 2014-02-24 2017-04-25 Intel Corporation Enhancement to the buffer status report for coordinated uplink grant allocation in dual connectivity in an LTE network
CN111954266B (zh) * 2014-06-23 2024-04-09 北京三星通信技术研究有限公司 一种双连接中分割承载的数据分配方法和装置
US9628586B2 (en) * 2014-08-29 2017-04-18 Lg Electronics Inc. PDCP operation in a wireless communication system supporting dual connectivity
JP2016092700A (ja) * 2014-11-07 2016-05-23 株式会社Ｎｔｔドコモ ユーザ装置、及び重複パケット処理方法
US20160198352A1 (en) * 2015-01-05 2016-07-07 Qualcomm Incorporated System and Methods for Improving Data Performance Via Deliberate Hybrid Automatic Repeat Request (HARQ) Acknowledgment (ACK) and Fast Radio Link Control (RLC) Non-acknowledgment (NACK) in a Multi-Subscriber Identity Module (SIM) Wireless Communication Device
US20180092118A1 (en) * 2015-05-15 2018-03-29 Samsung Electronics Co., Ltd. Method and device for transmitting or receiving scheduling request in mobile communication system
CN112437491A (zh) * 2015-05-15 2021-03-02 夏普株式会社 用户设备和由用户设备执行的方法
CN109478945B (zh) * 2015-05-21 2021-11-26 苹果公司 用于多rat卸载的pdcp状态报告
US10314043B2 (en) * 2015-07-20 2019-06-04 Zte Wistron Telecom Ab Mobile terminal and method for data transmission by multiple simultaneous radio access technologies
US10750410B2 (en) * 2016-09-30 2020-08-18 Huawei Technologies Co., Ltd. Ultra reliable low latency connection support in radio access networks
JP6948388B2 (ja) * 2017-02-02 2021-10-13 エルジー エレクトロニクス インコーポレイティドＬｇ Ｅｌｅｃｔｒｏｎｉｃｓ Ｉｎｃ． データユニットを送信する方法及び装置
US10798775B2 (en) * 2017-08-10 2020-10-06 Qualcomm Incorporated Techniques and apparatuses for duplication bearer management
US20200267793A1 (en) * 2017-08-14 2020-08-20 Samsung Electronics Co., Ltd. Method and system for handling packet duplication and resumption of rbs in wireless communication system
US20200404696A1 (en) * 2018-01-11 2020-12-24 Lg Electronics Inc. Communication device, processing device and method for transmitting uplink data

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104244450A (zh) * 2013-06-21 2014-12-24 中兴通讯股份有限公司 长期演进业务和集群业务并发时重建立方法、基站和用户设备
US20150215826A1 (en) * 2014-01-30 2015-07-30 Sharp Laboratories Of America, Inc. Systems and methods for dual-connectivity operation
CN106211352A (zh) * 2015-05-04 2016-12-07 中兴通讯股份有限公司 数据无线承载的建立方法和装置
CN106304398A (zh) * 2015-05-15 2017-01-04 夏普株式会社 用于重配置数据承载的方法和用户设备
CN107342851A (zh) * 2017-06-15 2017-11-10 电信科学技术研究院 一种重复传输的配置及重复传输方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
INTEL CORPORATION: "Packet Duplication for URLLC within a GNB", 3 GPP TSG-RAN WG2 97 MEETING, R2-1701720, 17 February 2017 (2017-02-17), XP051212293 *

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11751268B2 (en) 2018-10-26 2023-09-05 Google Llc Efficient handling of a resource control state change and multi-node connectivity
US11950307B2 (en) 2018-10-26 2024-04-02 Google Llc Efficient handling of a resource control state change and multi-node connectivity
US11792683B2 (en) 2018-10-30 2023-10-17 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Method for data processing, terminal device, and storage medium
WO2020088581A1 (zh) * 2018-10-31 2020-05-07 维沃移动通信有限公司 承载的控制方法、终端及网络侧设备
CN111132315A (zh) * 2018-10-31 2020-05-08 维沃移动通信有限公司 一种承载的控制方法、终端及网络侧设备
CN111130722A (zh) * 2018-10-31 2020-05-08 维沃移动通信有限公司 一种承载的控制方法、终端及网络侧设备
KR20210076982A (ko) * 2018-10-31 2021-06-24 비보 모바일 커뮤니케이션 컴퍼니 리미티드 베어러의 제어 방법, 단말 및 네트워크측 기기
CN111132315B (zh) * 2018-10-31 2023-04-18 维沃移动通信有限公司 一种承载的控制方法、终端及网络侧设备
KR102591426B1 (ko) * 2018-10-31 2023-10-19 비보 모바일 커뮤니케이션 컴퍼니 리미티드 베어러의 제어 방법, 단말 및 네트워크측 기기
US20220330030A1 (en) * 2019-12-31 2022-10-13 Huawei Technologies Co., Ltd. Communication method and apparatus
EP4075861A4 (en) * 2019-12-31 2022-12-28 Huawei Technologies Co., Ltd. COMMUNICATION METHOD AND APPARATUS
WO2022047684A1 (en) * 2020-09-03 2022-03-10 Qualcomm Incorporated Voice over new radio reliability enhancement by duplicate transmission of internet protocol multimedia subsystem signaling

Also Published As

Publication number Publication date
US20200029379A1 (en) 2020-01-23
CN108924871A (zh) 2018-11-30
US11324059B2 (en) 2022-05-03
CN108924871B (zh) 2022-09-20

Similar Documents

Publication Publication Date Title
WO2018171512A1 (zh) 无线配置方法、用户设备和基站
TWI692988B (zh) 基站、使用者設備和相關方法
WO2018171546A1 (zh) 用户设备和基站处执行的方法及相应的设备
TWI678124B (zh) 使用者設備和相關方法
US11057958B2 (en) Method and device for establishing/reconfiguring data bearer
WO2018228283A1 (zh) 无线通信方法和设备
CN109246766B (zh) 无线配置方法和相应的用户设备
JP6416097B2 (ja) 複数の接続を確立するためのデバイス
WO2019029565A1 (zh) 用户设备、基站和相关方法
WO2019134529A1 (zh) 用户设备和相关方法
JP6741024B2 (ja) 無線端末、無線局、及びこれらの方法
CN109246710B (zh) 基站、用户设备和相关方法
CN110999382B (zh) 用于控制分组复制的方法及设备
WO2018054185A1 (zh) 用户设备、基站和相关方法
WO2018059148A1 (zh) 一种数据转发的方法及其设备
WO2020221155A1 (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: 18771151

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18771151

Country of ref document: EP

Kind code of ref document: A1