[go: up one dir, main page]

WO2018164499A1 - Procédé de transmission de rapport d'état de tampon, et dispositif associé - Google Patents

Procédé de transmission de rapport d'état de tampon, et dispositif associé Download PDF

Info

Publication number
WO2018164499A1
WO2018164499A1 PCT/KR2018/002750 KR2018002750W WO2018164499A1 WO 2018164499 A1 WO2018164499 A1 WO 2018164499A1 KR 2018002750 W KR2018002750 W KR 2018002750W WO 2018164499 A1 WO2018164499 A1 WO 2018164499A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdcp
logical channel
entity
terminal
data
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/KR2018/002750
Other languages
English (en)
Korean (ko)
Inventor
홍성표
최우진
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
KT Corp
Original Assignee
KT Corp
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
Priority claimed from KR1020170152149A external-priority patent/KR20180131335A/ko
Priority claimed from KR1020180026611A external-priority patent/KR102065137B1/ko
Application filed by KT Corp filed Critical KT Corp
Priority to CN201880004237.3A priority Critical patent/CN109937587B/zh
Priority to US16/349,259 priority patent/US10986530B2/en
Publication of WO2018164499A1 publication Critical patent/WO2018164499A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/24—Cell structures
    • H04W16/32—Hierarchical cell structures
    • 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
    • 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

Definitions

  • the present disclosure relates to a technology in which a terminal configures carrier aggregation with one base station in a next generation mobile communication network (NR) to duplicate data transmission and transmit a buffer status report accordingly.
  • NR next generation mobile communication network
  • the present invention relates to a configuration method and apparatus for a UE to redundantly transmit user plane or control plane data in a single base station based carrier aggregation state, and to a specific method and procedure for transmitting a buffer status report in a single base station based carrier aggregation state. It is about.
  • LTE Long Term Evolution
  • 5G Long Term Evolution-Advanced
  • 3GPP 3rd Generation Partnership Project
  • the base station can improve the data transmission and reception speed and capacity of the terminal by using a plurality of cells configured (provided) by the base station.
  • the base station and the terminal may satisfy a user's request by configuring a carrier merge using a plurality of carriers.
  • the present embodiment is to provide a configuration and processing technology for the carrier and the base station to configure a carrier merge using a plurality of cells, and to transmit and receive data redundantly through a plurality of carrier merged cells.
  • the present embodiment is to provide a specific technique for transmitting a buffer status report by the terminal configured for redundant transmission.
  • an embodiment of the present invention provides a method for transmitting a buffer status report by a terminal constituting carrier aggregation to perform higher layer signaling including information for configuring data redundant transmission through carrier aggregation from a base station.
  • RLC Radio Link Control
  • PDCP Packet Data Convergence Protocol
  • the buffer status report configured to be included in both the logical channel group and the logical channel group associated with the second RLC entity is sent to the base station. It provides a method comprising the step of transmitting.
  • a method for receiving a buffer status report by a base station configuring a carrier merge in a terminal may include generating information for configuring data redundant transmission through carrier merge and data duplication through carrier merge to a terminal. Transmitting a higher layer signaling including information for configuring a transmission, and when data duplex transmission of the terminal is activated, a logical channel group associated with the first RLC entity of the terminal and a logical channel associated with the second RLC entity of the terminal It provides a method comprising the step of receiving a buffer status report containing the PDCP data volume of the terminal set to be included in all groups.
  • an embodiment of the present invention provides a terminal for configuring a carrier merge to transmit a buffer status report based on a receiver and a higher layer signaling for receiving higher layer signaling including information for configuring data redundant transmission through carrier aggregation from a base station.
  • RLC Radio Link Control
  • PDCP Packet Data Convergence Protocol
  • MAC Medium Access Control
  • the control unit constituting the logical channel associated with the first RLC entity and the logical channel associated with the second RLC entity, and when data redundancy transmission is activated, the PDCP data volume is assigned to the logical channel group and the second RLC entity associated with the first RLC entity.
  • a terminal including a transmitter for transmitting a buffer status report configured to be included in all associated logical channel groups to the base station Provide the device.
  • an embodiment is a base station configured to receive a buffer status report by configuring a carrier merge in the terminal, the control unit for generating information for configuring data redundant transmission through the carrier merge and the data redundant transmission through the carrier merge to the terminal
  • the control unit for generating information for configuring data redundant transmission through the carrier merge and the data redundant transmission through the carrier merge to the terminal
  • the data transmission of the transmitter and the terminal for transmitting the upper layer signaling including information to configure is activated, both the logical channel group associated with the first RLC entity of the terminal and the logical channel group associated with the second RLC entity of the terminal
  • a base station apparatus including a receiving unit for receiving a buffer status report including a PDCP data volume of a terminal set to be included in the terminal.
  • the above-described embodiment provides an effect that a terminal and a base station can quickly and accurately transmit and receive data for providing a low latency high reliability service, and provide a specific method for distinguishing and processing redundant data transmitted and received for each logical channel. Provide effect.
  • the present embodiment provides an effect that the terminal configured with redundant transmission can transmit the accurate buffer status report to the base station.
  • FIG. 1 is a diagram illustrating an example of a layer 2 structure for a new radio access technology (New RAT).
  • New RAT new radio access technology
  • FIG. 2 is a diagram illustrating an operation of a terminal according to an exemplary embodiment.
  • FIG. 3 is a diagram for describing an operation of a base station according to an exemplary embodiment.
  • FIG. 4 is a diagram for describing an operation of a base station according to another exemplary embodiment.
  • FIG. 5 is a diagram illustrating a split bearer structure through a master cell group in multi connectivity between heterogeneous base stations.
  • FIG. 6 is a diagram illustrating an example of a structure for carrier merge-based data redundant transmission.
  • FIG. 7 is a diagram illustrating another example of a structure for carrier merge-based data redundant transmission.
  • FIG. 8 is a diagram illustrating another example of a structure for carrier merge-based data redundant transmission.
  • FIG. 9 is a diagram illustrating an example of RLC configuration information according to an embodiment.
  • FIG. 10 is a diagram illustrating another example of RLC configuration information according to an embodiment.
  • FIG 11 illustrates another example of RLC configuration information according to an embodiment.
  • FIG 12 illustrates another example of RLC configuration information according to an embodiment.
  • FIG. 13 is a diagram illustrating another example of RLC configuration information according to an embodiment.
  • FIG. 14 is a diagram illustrating a Short BSR and Truncated BSR format according to the prior art.
  • 16 is a diagram illustrating an example of radio bearer configuration information according to an embodiment.
  • 17 is a diagram illustrating an example of cell group configuration information according to an embodiment.
  • FIG. 18 is a diagram illustrating a terminal configuration according to an embodiment.
  • 19 is a diagram illustrating a configuration of a base station according to an embodiment.
  • the MTC terminal may mean a terminal supporting low cost (or low complexity) or a terminal supporting coverage enhancement.
  • the MTC terminal may mean a terminal supporting low cost (or low complexity) and coverage enhancement.
  • the MTC terminal may mean a terminal defined in a specific category for supporting low cost (or low complexity) and / or coverage enhancement.
  • the MTC terminal may mean a newly defined 3GPP Release-13 low cost (or low complexity) UE category / type for performing LTE-based MTC related operations.
  • the MTC terminal supports enhanced coverage compared to the existing LTE coverage, or supports UE category / type defined in the existing 3GPP Release-12 or lower, or newly defined Release-13 low cost (or lower power consumption).
  • low complexity can mean UE category / type.
  • the wireless communication system in the present invention is widely deployed to provide various communication services such as voice, packet data, and the like.
  • the wireless communication system includes a user equipment (UE) and a base station (base station, BS, or eNB).
  • a user terminal is a generic concept meaning a terminal in wireless communication.
  • user equipment (UE) in WCDMA, LTE, and HSPA, as well as mobile station (MS) in GSM, user terminal (UT), and SS It should be interpreted as a concept that includes a subscriber station, a wireless device, and the like.
  • a base station or a cell generally refers to a station that communicates with a user terminal, and includes a Node-B, an evolved Node-B, an Sector, a Site, and a BTS.
  • Other terms such as a base transceiver system, an access point, a relay node, a remote radio head (RRH), a radio unit (RU), and a small cell may be called.
  • RRH remote radio head
  • RU radio unit
  • a base station or a cell is interpreted in a comprehensive sense to indicate some areas or functions covered by a base station controller (BSC) in CDMA, a NodeB in WCDMA, an eNB or a sector (site) in LTE, and the like. It is meant to cover various coverage areas such as mega cell, macro cell, micro cell, pico cell, femto cell and relay node, RRH, RU, small cell communication range.
  • BSC base station controller
  • the base station may be interpreted in two senses. i) the device providing the megacell, the macrocell, the microcell, the picocell, the femtocell, the small cell in relation to the wireless area, or ii) the wireless area itself. In i) all devices which provide a given wireless area are controlled by the same entity or interact with each other to cooperatively configure the wireless area to direct the base station.
  • the base station may indicate the radio area itself to receive or transmit a signal from the viewpoint of the user terminal or the position of a neighboring base station.
  • megacells macrocells, microcells, picocells, femtocells, small cells, RRHs, antennas, RUs, low power nodes (LPNs), points, eNBs, transmit / receive points, transmit points, and receive points are collectively referred to as base stations. do.
  • the user terminal and the base station are two transmitting and receiving entities used to implement the technology or technical idea described in this specification in a comprehensive sense and are not limited by the terms or words specifically referred to.
  • the user terminal and the base station are two types of uplink or downlink transmitting / receiving subjects used to implement the technology or the technical idea described in the present invention, and are used in a generic sense and are not limited by the terms or words specifically referred to.
  • the uplink (Uplink, UL, or uplink) refers to a method for transmitting and receiving data to the base station by the user terminal
  • the downlink (Downlink, DL, or downlink) means to transmit and receive data to the user terminal by the base station It means the way.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal frequency division multiple access
  • OFDM-FDMA OFDM-TDMA
  • OFDM-CDMA OFDM-CDMA
  • One embodiment of the present invention can be applied to resource allocation in the fields of asynchronous wireless communication evolving to LTE and LTE-advanced through GSM, WCDMA, HSPA, and synchronous wireless communication evolving to CDMA, CDMA-2000 and UMB.
  • the present invention should not be construed as being limited or limited to a specific wireless communication field, but should be construed as including all technical fields to which the spirit of the present invention can be applied.
  • the uplink transmission and the downlink transmission may use a time division duplex (TDD) scheme that is transmitted using different times, or may use a frequency division duplex (FDD) scheme that is transmitted using different frequencies.
  • TDD time division duplex
  • FDD frequency division duplex
  • a standard is configured by configuring uplink and downlink based on one carrier or a pair of carriers.
  • the uplink and the downlink include a Physical Downlink Control CHannel (PDCCH), a Physical Control Format Indicator CHannel (PCFICH), a Physical Hybrid ARQ Indicator CHannel (PHICH), a Physical Uplink Control CHannel (PUCCH), an Enhanced Physical Downlink Control CHannel (EPDCCH), and the like.
  • Control information is transmitted through the same control channel, and data is configured by a data channel such as a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH).
  • PDSCH physical downlink shared channel
  • PUSCH physical uplink shared channel
  • control information may also be transmitted using an enhanced PDCCH (EPDCCH or extended PDCCH).
  • EPDCCH enhanced PDCCH
  • extended PDCCH extended PDCCH
  • a cell means a component carrier having a coverage of a signal transmitted from a transmission / reception point or a signal transmitted from a transmission point or a transmission / reception point, and the transmission / reception point itself. Can be.
  • the wireless communication system to which the embodiments are applied includes a coordinated multi-point transmission / reception system (CoMP system) or a coordinated multi-antenna transmission system in which two or more transmission / reception points cooperate to transmit a signal. May be a cooperative multi-cell communication system.
  • the CoMP system may include at least two multiple transmission / reception points and terminals.
  • the multiple transmit / receive point is at least one having a high transmission power or a low transmission power in a macro cell region, which is connected to an eNB or a macro cell (hereinafter referred to as an 'eNB') and wired controlled by an optical cable or an optical fiber to an eNB. May be RRH.
  • downlink refers to a communication or communication path from a multiple transmission / reception point to a terminal
  • uplink refers to a communication or communication path from a terminal to multiple transmission / reception points.
  • a transmitter may be part of multiple transmission / reception points, and a receiver may be part of a terminal.
  • a transmitter may be part of a terminal, and a receiver may be part of multiple transmission / reception points.
  • a situation in which a signal is transmitted and received through a channel such as a PUCCH, a PUSCH, a PDCCH, an EPDCCH, and a PDSCH may be described in the form of 'sending and receiving a PUCCH, a PUSCH, a PDCCH, an EPDCCH, and a PDSCH.
  • a description of transmitting or receiving a PDCCH or transmitting or receiving a signal through the PDCCH may be used as a meaning including transmitting or receiving an EPDCCH or transmitting or receiving a signal through the EPDCCH.
  • the physical downlink control channel described below may mean PDCCH or EPDCCH, and may also be used to include both PDCCH and EPDCCH.
  • the EPDCCH which is an embodiment of the present invention, may be applied to the portion described as the PDCCH, and the EPDCCH may be applied to the portion described as the EPDCCH as an embodiment of the present invention.
  • high layer signaling described below includes RRC signaling for transmitting RRC information including an RRC parameter.
  • the eNB performs downlink transmission to the terminals.
  • the eNB includes downlink control information and an uplink data channel (eg, a physical downlink shared channel (PDSCH), which is a primary physical channel for unicast transmission, and scheduling required to receive the PDSCH.
  • a physical downlink control channel (PDCCH) for transmitting scheduling grant information for transmission on a physical uplink shared channel (PUSCH) may be transmitted.
  • PUSCH physical uplink shared channel
  • NR New Radio
  • eMBB enhanced Mobile BroadBand
  • MMTC massive machine type communication
  • URLLC Ultra Reliable and Low Latency Communication
  • LTE and NR mean different radio access technologies, and a new radio access technology discussed in Release-15 of 3GPP will be described using NR.
  • NR may include various differences from LTE to other frame structures, channels, and core network technologies, and may add various functions for high-bandwidth wireless transmission, high speed, and large data transmission.
  • the base station may be an eNB using the LTE technology, may be a gNB using the NR technology, and will be described separately as necessary.
  • a cell in the present specification is used as a term encompassing a radio path, a radio link, a carrier, and the like for transmitting data, and one base station can transmit and receive data through a plurality of cells.
  • the terminal may transmit and receive data using a plurality of cells through a cell controlled by two base stations.
  • carrier aggregation when one base station controls a plurality of cells, and described as dual connectivity when using a plurality of cells controlled by two or more base stations.
  • the dual connectivity operation is configured to connect to two base stations connected via non-ideal backhaul to use radio resources provided by two different schedulers located at each base station.
  • the terminal can transmit and receive data through a plurality of cells provided by two or more base stations, describe the main base station as a MeNB (Master eNB), and the base station providing additional cells as a SeNB (Secondary eNB) It describes by describing.
  • MeNB Master eNB
  • SeNB Secondary eNB
  • a SeNB addition procedure is used to establish a terminal context in the SeNB to provide radio resources from the SeNB to the terminal.
  • NR next generation / 5G radio access technology
  • FIG. 1 is a diagram illustrating an example of a layer 2 structure for a new radio access technology (New RAT).
  • New RAT new radio access technology
  • the main services and functions of the new AS sublayer are as follows.
  • the new user plane protocol layer can be applied to the connection to the next generation core.
  • the new user plane protocol layer is applicable for connections to the NextGen Core.A single protocol entity of the new user plane protocol layer is configured for each individual PDU session.).
  • Dual connectivity in an NR environment can be defined as multi-connection.
  • multi-connectivity may be defined as an operation mode of a terminal for using a radio resource configured by an LTE base station and / or an NR base station.
  • Multi-Connectivity Mode of operation whereby a multipleRx / Tx UE in the connected mode is configured to utilize radio resources amongst E-UTRA and / or NR provided by multipledistinct schedulers connected via non-ideal backhaul.
  • NR may be established even in a high frequency band (for example, high frequency of 6GHz or more).
  • a high frequency band for example, high frequency of 6GHz or more.
  • fast SINR drops may occur due to high frequency band link blockage and high transmission loss. This may cause unnecessary delay or lower reliability when the NR base station wants to send a control plane RRC message or user plane data through an interface between the NR and the terminal.
  • this problem makes it difficult to provide services such as URLLC.
  • a control plane RRC message may be repeatedly transmitted through one or more radio paths.
  • the user plane data may be redundantly transmitted through one or more radio paths based on multi connectivity.
  • New radio access technologies also need to provide carrier aggregation (CA) to increase data rates and throughput.
  • the terminal may transmit data through a plurality of cells based on a CA by a single base station.
  • CA carrier aggregation
  • a description will be given of a cell, but if necessary, a radio path, a radio link, a carrier, or the like may be used interchangeably.
  • terms such as a radio path, a radio link, a carrier, and a cell are used to mean a data path provided by a base station for data transmission and reception with a terminal.
  • the terminal may perform redundant transmission through one or more cells.
  • the control plane RRC message may be repeatedly transmitted through one or more cells.
  • the user plane data may be redundantly transmitted through one or more cells.
  • a redundant transmission through two or more radio paths can be considered as a method for providing a low latency, reliable service such as URLLC in a wireless access network.
  • a CA is configured in a terminal based on a single base station, redundant transmission through two radio paths through the CA cannot be supported.
  • the present disclosure devised to solve such a problem is to provide a method and apparatus for configuring redundant transmission of a terminal and a base station to efficiently process a service such as URLLC when applying a single base station-based CA. It is also an object of the present invention to provide a method for effectively controlling a CA-based multiple transmission cell.
  • the present disclosure can be applied to any wireless access (eg, LTE) network and terminal as well as next generation mobile communication (5G mobile communication / NR) terminals.
  • wireless access eg, LTE
  • 5G mobile communication / NR next generation mobile communication
  • the base station may refer to an eNodeB, an LTE base station of LTE / E-UTRAN, and may be an NR node, a CU, a DU, or a 5G wireless network in which a central unit (CU) and a distributed unit (DU) are separated.
  • a CU and a DU may represent a gNodeB and an NR base station implemented as one logical entity.
  • the NR base station is described, but all the aforementioned entities may be included in the scope of the present invention.
  • One or more NR cells and one or more LTE cells are provided through an LTE base station to apply a CA.
  • One or more NR cells and one or more LTE cells are provided to the NR base station to apply the CA.
  • One or more NR cells are provided to the NR base station to apply the CA.
  • One or more LTE cells are provided to the LTE base station to apply the CA.
  • LTE-NR dual connectivity where the LTE base station becomes the master base station, NR base station becomes the secondary base station, NR base station becomes the master base station, NR-LTE dual connectivity, where the LTE base station becomes the secondary base station, and NR base station becomes the master base station.
  • Another NR base station may also be included in the embodiment of the present disclosure in which redundant transmission is applied by applying a CA at a corresponding single base station for NR-NR dual connectivity serving as a secondary base station. That is, when a plurality of base stations or a plurality of NR base stations using different radio access technologies configure dual connectivity, and also configure carrier aggregation in a single base station, the embodiments herein may be applied.
  • the NR base station may control the NR radio resource of the terminal.
  • the NR base station adds / modifies / releases / manages NR cells / cell groups / transmission points / transmission point groups / transmission / reception points / transmission / reception points groups / TRP / antennas / antenna groups / beams (hereinafter, collectively referred to as cells).
  • One or more control functions of measurement, NR measurement reporting, NR resource allocation, NR radio bearer addition / modification / release, NR radio resource configuration, and NR mobility control may be performed.
  • the NR base station may instruct one or more control functions described above for the terminal through an RRC configuration or reconfiguration message.
  • the NR base station may configure a CA through one or more NR cells in the terminal.
  • the NR base station may perform data redundant transmission to the CA using the PDCP redundant transmission function.
  • the PDCP entity of the base station copies or duplicates PDCP PDUs (or PDCP SDUs) having the same sequence number (SN) to duplicate data transmission through one or more radio cells to the lower layer.
  • the PDCP entity of the terminal receives PDCP PDUs (or PDCP SDUs) received through one or more radio cells.
  • the PDCP entity may first process the received data and discard the duplicated data.
  • the function of detecting and discarding duplicate data may be performed by the PDCP entity.
  • the transmitting side may transmit data having the same PDCP SN through two paths, and the receiving side may detect (or detect) duplicate data based on the PDCP SN.
  • the base station may instruct the terminal configuration information for instructing / processing such an operation.
  • the PDCP entity of the UE copies / duplicates PDCP PDUs (or PDCP SDUs) having the same SN and submits them to lower layers in order to duplicate data transmission through one or more radio cells.
  • the PDCP entity of the base station receives PDCP PDUs (or PDCP SDUs) received through one or more radio cells.
  • the PDCP entity may first process the received data and discard the duplicated data.
  • the function of detecting and discarding duplicate data may be performed by a PDCP object.
  • the transmitter may transmit data having the same PDCP SN through two paths, and the receiver may detect (or detect) duplicate data based on the PDCP SN.
  • the base station may instruct the terminal configuration information for instructing / processing such an operation.
  • redundant data transmission can be handled in the PDCP layer connected through the new AS sublayer.
  • RRC messages may or may not be through the new AS sublayer.
  • duplicate data transmission may be processed in PDCP through a new AS sublayer.
  • the RRC message may be directly connected to the PDCP without a new AS sublayer, thereby processing redundant data transmission.
  • FIG. 2 is a diagram illustrating an operation of a terminal according to an exemplary embodiment.
  • the terminal may perform a step of receiving a higher layer signaling including information for configuring data redundant transmission through carrier aggregation from the base station (S210).
  • the terminal may configure a carrier merge with one base station and receive an RRC message including additional RLC configuration information for redundantly transmitting the same data to the base station through a plurality of carriers using the carrier merge.
  • the information for configuring redundant transmission includes information on a plurality of RLC entities configured in the terminal for redundant transmission of data, logical channel information associated with each RLC entity, and each RLC entity and one PDCP. It may include at least one of information for linking the entity and MAC entity configuration information for redundant transmission.
  • the terminal configures a plurality of RLC entities including a first Radio Link Control (RLC) entity and a second RLC entity associated with one Packet Data Convergence Protocol (PDCP) entity based on higher layer signaling.
  • RLC Radio Link Control
  • PDCP Packet Data Convergence Protocol
  • a logical channel linked to the first RLC entity and a logical channel linked to the second RLC entity may be configured in a medium access control (MAC) entity (S220).
  • MAC medium access control
  • the terminal may configure an additional RLC entity in the terminal based on the information for configuring the received redundant transmission.
  • a plurality of additional RLC entities may be configured by the configuration of the base station.
  • two RLC entities are described as examples for convenience of description.
  • the present invention is not limited thereto.
  • the UE may configure the first RLC entity and the second RLC entity in association with one PDCP entity according to higher layer signaling.
  • the terminal may configure a logical channel in association with the RLC entity to distinguish the RLC entity added to one MAC entity. That is, the terminal may configure a logical channel associated with the first RLC entity and a logical channel associated with the second RLC entity in the MAC entity.
  • the MAC entity maps and processes data transmitted and received through one radio bearer to each logical channel, thereby repeatedly transmitting PDCP data to a base station through a plurality of RLC entities, and transmitting the duplicated data to the PDCP entity. It can also pass through each logical channel.
  • one MAC entity may transmit data transmitted through a logical channel associated with the first RLC entity and a logical channel associated with the second RLC entity to the base station through different carriers.
  • first RLC entity and the second RLC entity may be configured in association with different logical channels based on logical channel identifiers.
  • the first RLC entity and the second RLC entity may be configured in association with the one PDCP entity based on a radio bearer identifier.
  • the terminal transmits a buffer status report configured by setting the PDCP data volume to be included in both the logical channel group associated with the first RLC entity and the logical channel group associated with the second RLC entity to the base station.
  • the process may be performed.
  • the terminal may transmit a buffer status report to the base station under a buffer status report trigger condition.
  • the redundant transmission function may not be activated according to a setting.
  • activation of data duplication transmission may be indicated through a separate signal from the base station.
  • a signal for activation of redundant transmission may be indicated from the base station through the MAC control element for each data radio bearer. That is, the base station may activate or deactivate the redundant transmission function configured in the terminal through a MAC control element for each radio bearer.
  • the terminal transmits the buffer status report to the base station.
  • the terminal transmits the buffer status report to the base station.
  • the terminal may set the PDCP data volume to be included in both the logical channel group associated with the first RLC entity and the logical channel group associated with the second RLC entity.
  • the UE may set the PDCP data volume of the logical channel associated with the second RLC entity (an RLC entity additionally configured for redundant transmission) to include and remove the PDCP control PDU, and the logical channel associated with the first RLC entity.
  • the PDCP data volume can be set to include the PDCP control PDU.
  • the terminal may transmit a buffer status report including buffer information of each logical channel group to the base station. That is, the PDCP data volume may be set to be included in all of the logical channel groups associated with each RLC entity.
  • the terminal may perform all the operations of the embodiments described below, and some steps may be changed, omitted, and added as necessary.
  • FIG. 3 is a diagram for describing an operation of a base station according to an exemplary embodiment.
  • the base station may perform the step of generating information for configuring data redundant transmission through carrier aggregation (S310).
  • the information for configuring redundant transmission includes information on a plurality of RLC entities configured in the terminal, logical channel information associated with each RLC entity, and each RLC entity and one PDCP in order for the terminal to transmit data redundantly. It may include at least one of information for linking the entity and MAC entity configuration information for redundant transmission.
  • the base station may perform a step of transmitting higher layer signaling including information for configuring data redundant transmission through carrier aggregation to the terminal (S320).
  • the base station may transmit the information for configuring the single base station-based redundant transmission of the aforementioned terminal through higher layer signaling such as an RRC message.
  • the terminal receives information for configuring redundant transmission and configures a plurality of RLC entities including a first Radio Link Control (RLC) entity and a second RLC entity associated with one Packet Data Convergence Protocol (PDCP) entity.
  • RLC Radio Link Control
  • PDCP Packet Data Convergence Protocol
  • One medium access control (MAC) entity may configure a logical channel associated with the first RLC entity and a logical channel associated with the second RLC entity.
  • the terminal may configure an additional RLC entity in the terminal based on the information for configuring the received redundant transmission.
  • a plurality of additional RLC entities may be configured by the configuration of the base station.
  • the first RLC entity and the second RLC entity may be configured in association with one PDCP entity.
  • the terminal may configure a logical channel in association with the RLC entity to distinguish the RLC entity added to one MAC entity. That is, the terminal may configure a logical channel associated with the first RLC entity and a logical channel associated with the second RLC entity in the MAC entity.
  • the first RLC entity and the second RLC entity may be configured in association with different logical channels based on logical channel identifiers.
  • the UE may be configured to associate the first RLC entity and the second RLC entity with one PDCP entity based on the radio bearer identifier.
  • the base station can receive data transmitted in association with each logical channel of the terminal through different carriers. That is, the same data can be received in duplicate.
  • different carriers may be carriers constituting the CA of the terminal.
  • the base station When the redundant data transmission of the terminal is activated, the base station includes a buffer including the PDCP data volume of the terminal configured to be included in both the logical channel group associated with the first RLC entity of the terminal and the logical channel group associated with the second RLC entity of the terminal. Receiving a status report may be performed (S330).
  • the terminal transmits the buffer status report to the base station according to the buffer status report trigger condition, and the base station may receive the same.
  • the buffer status report may include a PDCP data volume for each logical channel group.
  • the terminal may assign the PDCP data volume to both the logical channel group associated with the first RLC entity and the logical channel group associated with the second RLC entity. It can be transmitted to the base station. That is, the PDCP data volume may be included in all logical channel groups associated with each RLC entity. At this time, the PDCP data volume of the logical channel associated with the second RLC entity may remove the PDCP control PDU and receive the included value. In addition, the PDCP data volume of the logical channel associated with the first RLC entity may receive a value including a PDCP control PDU.
  • the PDCP control PDU included in the PDCP data volume may be included only in a logical channel (logical channel group) associated with the first RLC entity. Accordingly, the PDCP control PDU may be indicated to the MAC entity without being included in the PDCP data volume of the logical channel or logical channel group associated with the RLC entity configured for redundant transmission.
  • the base station may perform all the operations of the embodiments described below, and some steps may be changed, omitted, and added as necessary.
  • FIG. 4 is a diagram for describing an operation of a base station according to another exemplary embodiment.
  • the base station transmits information indicating that data duplication transmission of the terminal is activated through a MAC control element for each data radio bearer. It may be (S410). That is, activation of data redundant transmission may be indicated through a separate signal from the base station. For example, a signal for activating redundant transmission may be indicated to the terminal through a MAC control element for each data radio bearer. That is, the base station may activate or deactivate the redundant transmission function configured in the terminal through a MAC control element (MAC CE) for each radio bearer.
  • MAC CE MAC control element
  • the base station may not transmit the MAC control element for activating the redundant transmission.
  • the terminal and the base station can configure redundant transmission through a single base station-based CA and process a buffer status report.
  • various embodiments in which the terminal and the base station configure redundant transmission will be described, and then various embodiments in which the buffer status report is processed will be described.
  • FIG. 5 is a diagram illustrating a split bearer structure through a master cell group in multi connectivity between heterogeneous base stations.
  • a split bearer structure based on dual / multi connectivity may be recycled.
  • the terminal may configure a dual connectivity-based split bearer structure. That is, the terminal may transmit and receive data through two radio resources through a bearer through the NR base station 501 and a split bearer branched from the PDCP entity of the NR base station 501 and linked to the RLC entity of the LTE base station 502. have.
  • redundant transmission may be performed in a structure similar to a split bearer as shown in FIG. 5.
  • 6 is a diagram illustrating an example of a structure for carrier merge-based data redundant transmission.
  • 7 is a diagram illustrating another example of a structure for carrier merge-based data redundant transmission.
  • the terminals 601 and 701 may be configured to redundantly transmit data through one or more carriers provided according to CAs using two MAC entities in the terminals 601 and 701.
  • the base station refers to a MAC entity for redundant transmission (for convenience of description, this is referred to as a second MAC entity.
  • MAC entity and MAC entity added for redundant transmission on a single base station basis are referred to as create / establish).
  • the terminals 601, 701 create a second MAC entity.
  • the second MAC entity configured by a single base station is used by the base station to efficiently provide detailed configuration information about the two MAC entities. Can be configured by setting.
  • the first MAC entity and the second MAC entity may be independently performed some or all of the MAC procedure. Because the second MAC entity is used for reliable duplication rather than efficiency, for some or all of the MAC procedure, the second MAC entity may perform a procedure independent of the first MAC entity.
  • the MAC procedure may be one or more of a buffer state report (BSR), a scheduling request (SR), a logical channel prioritization (LCP), and a power headroom report (PHR).
  • BSR buffer state report
  • SR scheduling request
  • LCP logical channel prioritization
  • PHR power headroom report
  • the first MAC entity and the second MAC entity may perform a MAC procedure through coordination.
  • the second MAC entity is used for reliable redundant transmission rather than efficiency, it may be efficient for some MAC procedures to coordination on their own.
  • This MAC procedure may be one or more of BSR, SR, LCP, PHR, and DRX.
  • the first MAC entity may provide all or most of the procedures occurring in the two MAC entities and the second MAC entity may perform only some limited functions. For example, at least one of a function of associating data transmitted / received from a second RLC entity belonging to one radio bearer with a logical channel, a related routing function, or a function of adding / removing information to distinguish it on a data header. May be performed at the second MAC entity.
  • Each MAC entity may distinguish a logical channel associated with each RLC entity belonging to one radio bearer. Or each MAC entity may comprise one or more carriers.
  • each MAC entity When the redundant transmission function is configured, at least one of the carriers (or cells) included in each MAC entity may be activated for redundant transmission.
  • the base station may configure one or more cells configured in the second MAC entity in an activation state.
  • the base station when configuring the redundant transmission function, may define and indicate one or more cells configured in the second MAC entity as a special cell that is distinguished from the general Scell. However, this particular cell may not need to provide the function for transmitting the PUCCH.
  • the base station when configuring a redundant transmission function, may always configure a specific cell configured in the second MAC entity in an activation state.
  • the base station when the base station configures the redundant transmission function, the base station configures a cell configured in the second MAC entity in an inactive state.
  • the base station may activate one or more (or specific cells) of cells configured in the second MAC entity to activate the redundant transmission function.
  • the cell may not apply the deactivation timer provided to the SCell.
  • the base station when the base station configures the redundant transmission function, the base station configures a cell configured in the second MAC entity in an inactive state.
  • the base station may activate the redundant transmission function only when at least one of the cells configured in the second MAC entity is activated.
  • the base station when the base station configures the redundant transmission function, the base station configures a cell configured in the second MAC entity in an inactive state.
  • the base station may keep one or more of the cells configured in the second MAC entity from being deactivated.
  • the timer can be instructed to restart.
  • the deactivation timer may be indicated by a specific value.
  • the base station when the base station configures the redundant transmission function, the base station configures a cell configured in the second MAC entity in an inactive state.
  • the base station configures (or activates) the redundant transmission function, it may instruct to activate one or more of the cells configured in the second MAC entity.
  • the terminal may activate one or more of the cells configured in the second MAC entity when configuring the redundant transmission function by the base station or when activating the redundant transmission function.
  • the base station when the base station configures the redundant transmission function, the base station may configure the redundant transmission activation condition as a terminal.
  • the terminal may indicate to the base station information for activating one or more of the cells configured in the second MAC entity when the redundant transmission condition is satisfied.
  • FIG. 8 is a diagram illustrating another example of a structure for carrier merge-based data redundant transmission.
  • a single MAC entity in the terminal 801 may be configured to redundantly transmit data through one or more cells / carriers provided through a CA.
  • the base station 802 may include one or more RLC entities and one or more logical channels associated with one MAC entity for one radio bearer. have.
  • the MAC entity may comprise one or more cells / carriers.
  • each logical channel belonging to one radio bearer must be mapped (associated or connected) with one or more mutually exclusive cells / carriers. That is, duplicate data may be transmitted in PDCP through different cells / carriers. This will be described later.
  • At least one of the cells / carriers associated with each logical channel belonging to one radio bearer may be activated to perform redundant transmission.
  • the base station may configure one or more cells of cells / carriers associated with each logical channel belonging to one radio bearer in an activation state.
  • one or more cells may be generalized on a cell / carrier / cell group / carrier group that does not include a PCell for a cell / carrier / cell group / carrier group associated with each logical channel belonging to one radio bearer. It can be defined as a special cell that is distinguished from scell.
  • the base station may always configure a specific cell (specific secondary cell) among cells / carriers associated with each logical channel belonging to one radio bearer in an activation state.
  • the base station when the base station configures a redundant transmission function, the base station configures a secondary cell associated with each logical channel belonging to one radio bearer in an inactive state.
  • the base station may activate one or more of the secondary cells / carriers (or specific cells) associated with each logical channel belonging to one radio bearer to activate the redundant transmission function.
  • the cell may not apply the deactivation timer provided to the SCell.
  • the base station when the base station configures a redundant transmission function, the base station configures a secondary cell associated with each logical channel belonging to one radio bearer in an inactive state.
  • the base station can enable the redundant transmission function only when one or more of the secondary cells associated with each logical channel belonging to one radio bearer are activated.
  • the base station when the base station configures a redundant transmission function, the base station configures a secondary cell associated with each logical channel belonging to one radio bearer in an inactive state.
  • the base station may keep the secondary cell associated with each logical channel belonging to one radio bearer not to be inactivated.
  • the timer can be instructed to restart.
  • the deactivation timer may be indicated by a specific value.
  • the base station when the base station configures a redundant transmission function, the base station configures a secondary cell associated with each logical channel belonging to one radio bearer in an inactive state.
  • the base station may instruct to activate the secondary cell associated with each logical channel belonging to one radio bearer.
  • the terminal may activate the secondary cell associated with each logical channel belonging to one radio bearer when configuring the redundant transmission function by the base station or activating the redundant transmission function.
  • the base station when the base station configures the redundant transmission function, the base station may configure the redundant transmission activation condition as a terminal.
  • the terminal receives information for activating at least one secondary cell (for example, a secondary cell associated with a cell group not including a PCell) associated with each logical channel belonging to one radio bearer. Can be indicated.
  • mapping between logical channels and cells will be described.
  • Logic channel-to-cell mapping may be provided for the foregoing cases.
  • Traffic transmission (or routing) restriction may be configured for each logical channel for one or more logical channels belonging to one SRB or DRB.
  • the logical channel configuration may indicate whether traffic for one logical channel is transportable in certain cells.
  • this may be configured for each serving cell. As another example, this may be configured for each logical channel.
  • the PCell may be configured in the aforementioned first MAC entity.
  • the SCell may be included in either the first MAC entity or the second MAC entity.
  • the base station may include information for indicating this in the SCell configuration information.
  • the cell configured in the first MAC entity may be configured to transmit traffic only for the logical channel / logical channel group configured in the first MAC entity.
  • the cell configured in the second MAC entity may be configured to transmit traffic only for the logical channel / logical channel group configured in the second MAC entity. Joint processing of uplink grants in one TTI is allowed only when the uplink grants serve the same logical channel in each MAC entity.
  • the terminal For an uplink grant for a cell belonging to the first MAC entity, the terminal performs LCP on logical channels associated with the first MAC entity.
  • the terminal For an uplink grant for a cell belonging to a second MAC entity, the terminal performs LCP on logical channels associated with the second MAC entity.
  • the base station refers to a SCell cell for redundant transmission (for convenience of description, referred to as a second cell or a second cell group. That is, a single base station-based general cell (PCell or SCell) is referred to as the first cell or the first SCell added for redundant transmission based on one cell group and based on a single base station may be referred to as a second cell or a second cell group).
  • a basic logical channel for convenience of explanation, refers to this as a first logical channel for each logical channel belonging to one radio bearer, that is, a MAC entity for one radio bearer.
  • the primary logical channel mapped in the above is referred to as a primary logical channel, and the logical channel added for the radio bearer is referred to as a secondary logical channel.
  • information for instructing transmission through the aforementioned second cell or second cell group may be configured.
  • the base station may include information on one or more of cell identification information (PCI, ServingCellindex, SCellindex, or a corresponding cell identification information list of the second cell for redundant transmission in logical channel configuration information to include a second logic belonging to one radio bearer.
  • the channel identification information list included in the logical channel configuration information may be included as a sequence or a bitmap, if the ServingCellindex / SCellindex is equal to or less than 7.
  • a bitmap composed of 8 bits may be configured, for example, when ServingCellindex / SCellindex configures the second and third cells as the second cell / second cell group, '00110000'
  • the bitmap indicated by may be included in the logical channel configuration information for the second logical channel so that the logical channel is transmitted only through the cell set to 1.
  • the second cell / second cell group is composed of SCells having ServingCellindex / SCellindex of 15 or less
  • a 16-bit bitmap may be configured.
  • the bitmap indicated by '0011000000000000' may be included in the logical channel configuration information for the second logical channel.
  • the logical channel may be configured to be transmitted only through a cell set to 1 in the corresponding bitmap. If a second cell / second cell group is composed of SCells having ServingCellindex / SCellindex of 31 or less, a 32-bit bitmap Can be configured.
  • the bitmap indicated as '0011000000000000000000000000' is included in the logical channel configuration information for the second logical channel. can do.
  • the logical channel may be configured to be transmitted only through a cell set to 1 in the corresponding bitmap.
  • the UE For the uplink grant for the first cell or the first cell group, the UE performs LCP only for the logical channel transmitted to the first cell or the first cell group.
  • the UE For the uplink grant for the second cell or the second cell group, the UE performs LCP only for the logical channel transmitted to the second cell or the second cell group.
  • one or more logical channels belonging to one SRB or DRB may indicate whether transmission is possible in a specific cell for each logical channel.
  • the first logical channel may be instructed to transmit only through the PCell, and the second logical channel may be instructed to transmit through the remaining cells / cell groups (or not to allow transmission through the PCell).
  • the first logical channel is transmitted through a specific cell group including the PCell and the second logical channel is transmitted through the remaining cell / cell group (or transmission is not allowed through the specific cell group including the PCell). Can be directed.
  • it may be instructed to transmit only through a specific SCell / cell group.
  • Two logical channels belonging to the duplicate transmission bearer may have a cell identifier or a cell identifier list for each logical channel.
  • the cell identifier or the cell identifier group for each logical channel may be configured not to overlap each other.
  • Cell identifiers or group of cell identifiers for each logical channel may be configured mutually exclusive.
  • PDCP data belonging to one radio bearer may need to be divided into logical channels through one or more RLC entities and transmitted to associated cells / carriers.
  • a cell group / carrier group (or second cell group) for redundant transmission may be defined.
  • a logical channel group (or second logical channel group) mapped to this cell group can be defined.
  • the logical channel identification information in each logical channel group may be configured independently of each other.
  • each logical channel group may have one of values from 3 to 8 for the DRB.
  • RLC entities associated with this cell group or logical channel group may be distinguished and configured.
  • a logical channel group (or a second logical channel group) mapped to a cell / cell group using a cell group / carrier group (or a second cell group or a specific cell or a cell other than a specific cell) for redundant transmission
  • a logical channel group (or second logical channel group) list may be defined.
  • the logical channel group list included in the cell group / carrier group configuration information may be included as a sequence or a bitmap.
  • the cell group / carrier group configuration information may include each logical channel configuration information having each logical channel identifier included in the second logical channel group in order.
  • the cell group / carrier group configuration information may include information for indicating a second cell / second cell group.
  • each logical channel group may be configured independently of each other.
  • each logical channel group may have one of values of 3 to 8 or 4 to 31 for the DRB.
  • one RLC entity (second RLC entity) configuration information and one logical channel (second logical channel) for one radio bearer may include configuration information (logical channel identification information). This can be mapped via the radio bearer identification.
  • RLC entity RLC entity
  • the base station denotes an additional RLC entity for redundant transmission (hereinafter, referred to as a second RLC entity for redundant transmission for convenience of description.
  • a second RLC entity for redundant transmission for convenience of description.
  • an arbitrary name such as a second RLC entity distinguished from a primary RLC entity configured for one bearer may be used.
  • the base station may configure a CA for a terminal having a single connection with one base station. This allows the terminal to transmit and receive data with a single base station through a plurality of radio paths.
  • the base station may indicate the configuration information for this to the terminal.
  • the base station may configure one or more RLC entities mapped to one data radio bearer (DRB) to the terminal.
  • DRB data radio bearer
  • This may be an RLC entity that is distinct from the SCG RLC entity provided for the Split bearer in conventional dual connectivity. That is, it may be an RLC entity included in the general (or added for MCG) DRB configuration information DRB-ToAddModd, which is distinguished from the RLC entity included in the DRB configuration information DRB-ToAddModSCG added for the SCG.
  • this may be an RLC entity included in the cell group configuration information (CellGroupConfig) added for the MCG distinguished from the RLC entity included in the cell group configuration information (CellGroupConfig) added for the SCG.
  • FIG. 9 is a diagram illustrating an example of RLC configuration information according to an embodiment.
  • the RLC configuration information may include one or more information of an RLC entity for redundant transmission, a logical channel identifier for redundant transmission, and logical channel configuration information for redundant transmission for one SRB or DRB.
  • the UE may configure a second RLC entity for redundant transmission in association with a logical channel for redundant transmission.
  • FIG. 10 is a diagram illustrating another example of RLC configuration information according to an embodiment.
  • the RLC configuration information is one of radio bearer identification information for redundant transmission, RLC entity for redundant transmission, logical channel identifier for redundant transmission, and logical channel configuration information for redundant transmission for one SRB or DRB.
  • the above information may be included.
  • the UE may configure a second RLC entity for redundant transmission in association with a logical channel for redundant transmission.
  • the PDCP entity may also be configured to associate with the first RLC entity and the second RLC entity for the radio bearer.
  • FIG 11 illustrates another example of RLC configuration information according to an embodiment.
  • the radio bearer configuration information for one SRB or DRB may include at least one of RLC configuration information used for redundant transmission and logical channel configuration information used for redundant transmission.
  • the RLC configuration information may be listed in the form of SEQUENCE.
  • the RLC configuration information may include information for identifying each RLC entity associated with one radio bearer. For example, it may include RLC identification information. RLC identification information may be configured to have a maximum of two or four. Alternatively, the information may be indicated as BOOLEAN to identify a duplicate RLC entity. If it has an integer value, the smallest value (eg 0) may be the default RLC entity (the first RLC entity).
  • the identification information of one RLC entity may be set to the same value as the logical channel identification information (logical carrier identifier).
  • mapping information / mapping rules thereof may be included for mapping between RLC entities and logical channel information.
  • the RLC entity for redundant transmission may be distinguished through logical channel identification information of the logical channel for redundant transmission.
  • the PDCP entity may also be configured to associate with the first RLC entity and the second RLC entity for the radio bearer.
  • FIG. 12 illustrates another example of RLC configuration information according to an embodiment.
  • 13 is a diagram illustrating another example of RLC configuration information according to an embodiment.
  • the radio bearer configuration information for one SRB or DRB may include information for distinguishing and mapping an RLC entity and a logical channel used for redundant transmission.
  • an RLC entity may be identified through logical channel identification information of a logical channel for redundant transmission for one radio bearer.
  • the PDCP entity may be configured to be associated with the first RLC entity and the second RLC entity for the radio bearer.
  • the terminal may perform redundant transmission.
  • the PDCP entity of the base station copies / duplicates PDCP PDUs (or PDCP SDUs) having the same SN and submits them to lower layers in order to redundantly transmit data through one or more radio cells.
  • the PDCP entity of the terminal receives PDCP PDUs (or PDCP SDUs) received through one or more radio cells. For example, the PDCP entity may first process the received data and discard the duplicated data.
  • the PDCP entity of the UE copies / duplicates PDCP PDUs (or PDCP SDUs) having the same SN and submits them to lower layers in order to duplicately transmit data through one or more radio cells.
  • the PDCP entity of the base station receives PDCP PDUs (or PDCP SDUs) received through one or more radio cells.
  • the PDCP entity of the base station submits PDCP PDUs to the first RLC entity for downlink transmission. Otherwise, the PDCP entity of the base station submits PDCP PDUs to the first RLC entity and the second RLC entity.
  • the PDCP entity of the terminal submits PDCP PDUs to the first RLC entity for uplink transmission. Otherwise, the PDCP entity of the base station submits PDCP PDUs to the first RLC entity and the second RLC entity.
  • the terminal receives data through a plurality of carriers by PDCP duplication on a single base station basis.
  • the MAC entity of the terminal transfers it to a higher layer (RLC) based on logical channel identification information. That is, the MAC entity of the terminal transfers data to the RLC entity based on the logical channel identification information.
  • RLC higher layer
  • data may be delivered to a corresponding RLC entity based on logical channel identification information included in a MAC header.
  • the MAC entity of the terminal may deliver the corresponding data to each corresponding RLC entity based on the respective logical channel identification information.
  • the base station should be able to configure each RLC entity and each logical channel mapping information in the terminal. For example, this may be provided by combining one or several of the above-described embodiments of FIGS. 6 to 11. As another example, this may be provided through various embodiments described above.
  • the UE transmits data through a plurality of carriers by PDCP duplication on a single base station basis.
  • the PDCP entity of the UE copies / duplicates PDCP PDUs (or PDCP SDUs) having the same SN and submits them to lower layers in order to duplicately transmit data through one or more radio cells.
  • a PDCP entity copies / duplicates PDCP PDUs (or PDCP SDUs) with the same SN to one or more RLC entities.
  • This may be provided based on one PDCP entity configuration information and one or more RLC entity configuration information belonging to one radio bearer. For example, it may be mapped based on the same radio bearer identifier (eg, DRB-identity).
  • this may be provided by configuring one PDCP configuration information in association with one or more RLC entities.
  • Each RLC entity passes it to a MAC entity.
  • each RLC entity can deliver an RLC PDU to each associated MAC entity.
  • each RLC entity delivers the corresponding RLC PDU to the MAC entity.
  • the MAC entity may generate a MAC PDU based on logical channel identification information associated with the corresponding RLC entity.
  • the RLC entity configuration information should be able to map logical channel configuration information associated with it. This may be provided in combination with one or several of the above-described embodiments of FIGS. 9 to 13 or various embodiments of the present invention.
  • This may be provided as a mapping through defining logical channel identification information and RLC entity identification information, and defining the logical channel identification information and RLC entity index.
  • the RLC entity index (or RLC identification information) may be provided in the same manner as the logical channel identification information.
  • the RLC entity may be configured in association with the logical channel identification information.
  • the second RLC entity and the second logical channel may be mapped to one radio bearer.
  • radio resources are consumed by redundantly transmitting RRC signaling messages or user plane data on a plurality of air interfaces.
  • this can improve the reliability of control plane message transmission or user plane data transmission.
  • the secondary base station can directly transmit the RRC message to the terminal through the air interface, there may be an advantage that can quickly transmit data without delay of the backhaul interval between base stations.
  • the multipath redundant transmission method improves reliability but causes a consumption of radio resources due to complexity and redundant transmission.
  • the RRC message will be described based on duplicate transmission. This is for convenience of description only and duplicated transmission of user plane data may be provided in the same manner. Therefore, user plane data duplication transmission is also included in the scope of the present invention. For example, this may be handled by the PDCP entity of an individual radio bearer that processes it by control plane data or user plane data.
  • the function (duplicate transmission function) is activated / deactivated or on / off (in the present specification, for convenience of description, denoted as enable / disable, enable / disable, can also be expressed in other terms such as on / off, activation / deactivation, etc.).
  • the base station efficiently transmits the data by determining the RRC data transmission over the implementation (implementation).
  • Uplink RRC data redundancy transmission may be performed by an indication of a base station.
  • the terminal when instructing the terminal by setting the indication information indicating whether to activate the duplicate transmission of the RRC message to activate, when the terminal generates an uplink RRC message, the corresponding RRC message to the two transmission paths in the PDCP entity Can be sent via
  • the base station instructs the terminal by setting the indication information indicating whether to activate the RRC message duplication transmission to the deactivation
  • the terminal when the terminal generates an uplink RRC message, the terminal transmits one RRC message in the PDCP entity Can be sent over the path.
  • the base station instructs the terminal by setting information indicating whether to activate the RRC message duplication transmission to inactive
  • the terminal when the terminal generates an uplink RRC message, the terminal transmits the corresponding RRC message specified in the PDCP entity Can be sent through.
  • the transmission path for this may be preconfigured in the terminal or indicated by the base station.
  • the base station efficiently transmits the data by determining the RRC data transmission over the implementation (implementation).
  • the base station may indicate a timer for multi-path redundant transmission.
  • the base station may indicate a duplicate transmission activation timer.
  • the terminal receives the RRC message including the duplicate transmission activation timer, the terminal starts the timer.
  • the UE may transmit the corresponding RRC message through two transmission paths in the PDCP entity.
  • the terminal may transmit the PDCP entity through one transmission path.
  • the transmission path for this may be preconfigured in the terminal or indicated by the base station.
  • This may be an RLC entity configured by default for the radio bearer.
  • the RLC entity, primary RLC entity, default RLC entity, initial configuration RLC entity, etc. which are configured for convenience of description, may be used under various names, and the names thereof are not limited.
  • the base station may indicate a timer for deactivating redundant transmission when redundant transmission is activated.
  • the terminal After receiving the RRC message including the timer for deactivating the redundant transmission, the terminal starts the timer when the redundant transmission is activated according to a specific indication or condition.
  • the UE may allow the PDCP entity to transmit the RRC message through two transmission paths.
  • the terminal may transmit the PDCP entity through one transmission path.
  • the UE may generate a duplicate RRC message while a timer for deactivating duplicate transmission is generated, or transmit the corresponding RRC message through two transmission paths in the PDCP entity or duplicate transmission in the PDCP entity.
  • the terminal may transmit the PDCP entity through one transmission path.
  • the base station may check the radio link quality state of the terminal through the RRM measurement report or CQI feedback from the terminal. Accordingly, the base station may instruct redundant transmission activation / deactivation through lower layer information.
  • whether to activate the duplicate transmission function in the PDCP entity configured in the terminal may be indicated through the MAC CE. That is, if a duplicate transmission function in the PDCP entity is configured in the terminal, the base station may transmit the indication information indicating activation or deactivation of the corresponding function to the terminal.
  • the indication information may include information for indicating whether to activate for each data radio bearer.
  • the terminal may duplicately transmit data through a plurality of radio paths for the radio bearer.
  • the PDCP entity may deliver the same PDCP PDU to different RLC entities.
  • the indication information provided through the MAC CE to indicate whether the corresponding PDCP entity activates the redundant transmission operation for each of the one or more data radio bearers is for indicating an activation / deactivation state for each radio bearer corresponding to each radio bearer identifier. It may include bitmap information.
  • the base station may indicate the indication information indicating whether to activate through the PDCCH.
  • the terminal may transmit the indication information to the RRC or PDCP layer that processes the duplicate transmission.
  • the base station may indicate the indication information through the PDCP control data.
  • the terminal may transmit information indicating to activate or deactivate (or activate / deactivate) redundant transmission to the base station using MAC CE or PUCCH.
  • the configuration information indicating the configuration of the RRC message redundant transmission to the terminal may include condition information for activating / deactivating the RRC data redundant transmission.
  • the configuration information may include switching information for instructing the terminal to switch the data transmission path between two paths configured with dual connectivity, and the switching information may include condition information for switching the data transmission path.
  • the following describes a condition for activating redundant transmission.
  • the conditions for instructing to switch the data transmission path between two paths configured as dual connectivity may also be set identically or similarly. The condition may be included in the condition information described above.
  • the reference radio signal quality value for activating the RRC message duplication transmission may be included in the condition information.
  • the terminal is a radio of a master base station (or a master TRP or a master cell or a PCell or anchor beam or best beam, a master base station for convenience of description, but any transmission signal on the NR is included in the scope of the present embodiment). If the quality meets (or exceeds or equals or is greater than) the corresponding reference radio quality value, there is no need to activate RRC redundant transmission. For example, when the radio quality of the master base station is greater than (or equal to or greater than) the reference value indicated by the base station, the RRC message may be transmitted through one transmission path in the PDCP entity.
  • the RRC message may be transmitted through the master base station.
  • the terminal may activate RRC redundant transmission. That is, when the radio quality of the master base station is less than (or equal to or less than) the threshold indicated by the base station, the RRC message may be transmitted through two transmission paths in the PDCP entity.
  • condition may be an uplink data separation threshold. If the redundant data transfer is not configured and enabled, and if the data-secure transfer is configured but not enabled, then the available PDCP data volume and RLC data volume associated with the two RLC objects are less than those conditions. Can be passed to an RLC entity in a single configured path.
  • the RRC message may be transmitted through one transmission path in the PDCP entity.
  • the terminal may transmit data only through the secondary base station.
  • the master base station and the secondary base station may be instructed to transmit data through a path providing a better radio quality.
  • the RRC message may be transmitted through the two transmission paths in the PDCP entity.
  • the physical layer may transmit it to the higher layer. For example, when the PDCP layer transmits through two transmission paths, the physical layer may indicate this to the PDCP entity. Alternatively, when the RRC layer transmits through two transmission paths, the physical layer may indicate this to the RRC.
  • the PDCP entity may activate or deactivate redundant transmission.
  • the base station may determine a threshold of radio quality associated with activation / deactivation, a threshold condition (e.g., a higher quality than the threshold, a lower quality than the threshold, a continuous outofsync, a continuous in sync, Link data separation data amount threshold, etc.), a timer for checking a threshold condition, a period for checking a threshold condition, and an indication condition and filtering parameters may be instructed to a higher layer to the terminal. For example, you can use an RLM procedure for this. As another example, RRM measurements can be used for this. For another example, beam measurements can be used for this.
  • a threshold condition e.g., a higher quality than the threshold, a lower quality than the threshold, a continuous outofsync, a continuous in sync, Link data separation data amount threshold, etc.
  • a timer for checking a threshold condition e.g., a higher quality than the threshold, a lower quality than the threshold, a continuous outofsync, a continuous
  • the downlink radio quality may be monitored by the terminal for a specific cell in the master cell group or all cells in the master cell group. This may be for triggering (determining / stopping / releasing / stopping) RRC redundant transmission or PDCP data (PDCP SDU or PDCP PDU) redundant transmission. Alternatively, the monitoring may be for indicating a state for an RRC redundant transmission or PDCP data redundant transmission to a higher layer.
  • downlink radio quality may be monitored by the terminal for a specific cell in the secondary cell group or all cells in the secondary cell group. This may be for triggering (determining / stopping / releasing / stopping) RRC redundant transmission or PDCP data (PDCP SDU or PDCP PDU) redundant transmission. Alternatively, the monitoring may be for indicating a state for an RRC redundant transmission or PDCP data redundant transmission to a higher layer.
  • the base station may indicate a threshold for indicating the physical layer of the terminal to the upper layer in performing the RLM operation.
  • the threshold value may be a separate threshold value separate from the threshold value for existing general RLM operation.
  • the terminal may configure one or more MAC entity or RLC entity to redundantly transmit data through a single base station based CA. Through this, the terminal may efficiently perform redundant transmission even when the data required for securing reliability is repeatedly transmitted.
  • buffer status report buffer status report
  • the terminal configures a single base station based CA to perform redundant transmission
  • the buffer status reporting procedure is a procedure used to provide the serving base station with information about data available for transmission in uplink (UL) buffers associated with the MAC entity.
  • the RRC entity configures three timers (for example, periodicBSR-Timer , retxBSR-Timer and logicalChannelSR-ProhibitTimer ), and reports buffer status through signaling to assign logical channels to logical channel groups for each logical channel. Control Status Repot (BSR) transmission.
  • periodicBSR-Timer for example, periodicBSR-Timer , retxBSR-Timer and logicalChannelSR-ProhibitTimer
  • BSR Control Status Repot
  • the buffer status report should be triggered when the following event occurs:
  • Uplink data is available for one logical channel belonging to one logical channel group (LCG) for transmission in a Radio Link Control (RLC) entity or a Packet Data Convergence Protocol (PDCP) entity. Lose. And the data belongs to a logical channel group belonging to any logical channel group and having a higher priority than the priority of the logical channels for the already available data, or among the logical channels belonging to one logical channel group. No data is available for anything.
  • RLC Radio Link Control
  • PDCP Packet Data Convergence Protocol
  • buffer status reporting is called “regular BSR” (UL data, for a logical channel which belongs to a LCG, becomes available for transmission in the RLC entity or in the PDCP entity (the definition of what data shall be considered as available for transmission is specified in [3] and [4] respectively) and either the data belongs to a logical channel with higher priority than the priorities of the logical channels which belong to any LCG and for which data is already available for transmission, or there is no data available for transmission for any of the logical channels which belong to a LCG, in which case the BSR is referred below to as "Regular BSR)
  • the buffer status report is called "padding BSR".
  • the buffer status report when the retransmission BSR timer (retxBSR-Timer) expires and the terminal has available data for transmission on any of the logical channels belonging to the LCG is also called a "regular BSR".
  • Period BSR The buffer status report when the periodic BSR-Timer expires.
  • the buffer status report together with the above-described classification according to the BSR trigger type may be divided into short BSR, Truncated BSR and Long BSR depending on the format.
  • FIG. 14 is a diagram illustrating a short BSR format according to the prior art
  • FIG. 15 is a diagram illustrating a long BSR format according to the prior art.
  • the number of padding bits is equal to or greater than the Short BSR plus its subheader, but less than the Long BSR plus its subheader, and if one or more LCGs are sent for If there is available data, transmit the Truncated BSR of the LCG with the highest priority logical channel with the available data for transmission (if the number of padding bits is equal to or larger than the size of the Short BSR plus its subheaderbutsmaller than the size of the Long BSR plus its subheader: if more than one LCG has data available for transmission in the TTI where the BSR is transmitted: report Truncated BSR of the LCG with the highest priority logical channel with data available for transmission;) . Otherwise, send a short BSR.
  • the long BSR is transmitted.
  • the Short BSR and Truncated BSR include logical channel group ID information and buffer size information.
  • the Long BSR sequentially includes buffer size information for four LCGs.
  • the BSR is transmitted to the MAC Control Element (MAC CE), and one MAC Protocol Data Unit (PDU) may include at most one MAC BSR control element.
  • MAC CE MAC Control Element
  • PDU MAC Protocol Data Unit
  • the MAC entity should transmit at most one Regular / Periodic BSR within one Transmission Time Interval (TTI).
  • TTI Transmission Time Interval
  • All BSRs sent in one TTI always indicate the buffer status after all MAC PDUs have been created for this TTI.
  • Each logical channel group must transmit at most one buffer status value per TTI. This value must be transmitted in all BSRs that carry the buffer status for this logical channel group.
  • the UE For the purpose of reporting the buffer status of the MAC layer, the UE should consider the following as the amount of data available in the RLC layer.
  • the UE For the purpose of reporting the buffer status of the MAC layer, the UE shall consider PDCP control PDUs and the following as the amount of data available in the PDCP layer.
  • the buffer status of the UE is reported through the Regular BSR, Periodic BSR, or Padding BSR. If packet duplication transmission is configured for a CA-based specific bearer between a single base station and a terminal or packet duplication transmission for a corresponding bearer is started / activated / on, if the terminal reports a buffer status through a short BSR procedure, the base station determines You may not be able to accurately determine the state of the buffers that should actually be sent. Accordingly, there is a problem that the base station can under-assign uplink resources to the terminal.
  • This embodiment devised to solve this problem effectively provides buffer status reporting of a terminal when packet duplication transmission is configured for a CA-based specific bearer between a single base station and a terminal or packet duplication transmission for a corresponding bearer is started / activated. It is an object of the present invention to provide a method and apparatus.
  • TTI may mean a transmission unit (for example, any physical layer transmission unit such as a slot or a minislot) defined in NR.
  • BSR buffer status report
  • Embodiment 1 An embodiment in which one BSR is transmitted through two different carriers to one transport unit (TTI)
  • TTI transport unit
  • the MAC entity should transmit at most one Regular / Periodic BSR within one Transmission Time Interval (TTI).
  • TTI Transmission Time Interval
  • a radio bearer configured to provide PDCP redundant transmission it may be difficult to stably transmit buffer states for two logical channels associated with the radio bearer.
  • the BSR is triggered. Can be.
  • the existing BSR trigger criteria Can trigger the BSR.
  • two logical channels associated with the corresponding radio bearer may be indicated to be included in different logical channel groups.
  • a Regular BSR or Periodic BSR is triggered for each of two logical channel / logical channel groups that are included in different logical channel groups (LCGs) and associated with the radio bearer, the TTI to which the BSR is transmitted is one or more LCGs. If you have data available for transmission, you can report a long BSR. Therefore, when each logical channel associated with the radio bearer is included in different logical channel groups, the BSR including buffer status information of each logical channel group may be delivered to the base station.
  • LCGs logical channel groups
  • the BSR including the buffer state of each logical channel group described above may be transmitted through each mutually exclusive cell / carrier associated with each logical channel belonging to the corresponding radio bearer in one TTI.
  • the scheduling request SR may be triggered on each mutually exclusive carrier.
  • the base station receiving the SR may transmit the corresponding BSR on each mutually exclusive carrier.
  • Uplink resources may be allocated.
  • the SR is received when the PDCP redundant transmission of the radio bearer is started / activated by the base station's L2 signaling (MAC CE or PDCP Control PDU) to transmit the corresponding BSR on each mutually exclusive carrier.
  • One base station may allocate uplink resources to transmit the corresponding BSR on each mutually exclusive cell / carrier.
  • the SR may be triggered to transmit the corresponding BSR on each mutually exclusive carrier.
  • the SR may include information for indicating this.
  • the base station may indicate information indicating that the corresponding SR is allowed.
  • the BSR including the buffer state of each logical channel group may be transmitted through one of mutually exclusive carriers associated with each logical channel belonging to the corresponding radio bearer in one TTI.
  • the amount of available data of the PDCP entity included in the buffer status report may be included in the buffer size of each logical channel group. Processing of the PDCP data volume including this will be described later.
  • a radio bearer in which redundant transmission is configured or a radio bearer in which PDCP redundant transmission of a corresponding radio bearer is started / activated by L2 signaling of a base station when a UE reports a BSR to a base station, the base station allocates an uplink grant based on this. Can be. If the MAC PDU including the BSR is lost, reliable low latency transmission may be difficult when uplink data is available for two logical channels associated with the corresponding radio bearer.
  • the base station may set a dedicated wireless bearer (or wireless bearer) RetxBSR-Timer.
  • the base station may set the corresponding radio bearer dedicated (or radio bearer) RetxBSR-Timer to a specific value other than the existing retransmission BSR timer values (sf320, sf640, sf1280, sf2560, sf5120, sf10240).
  • the terminal may trigger (or transmit to the base station) the BSR when the corresponding retransmission BSR timer (retxBSR-Timer) expires.
  • timers (periodicBSR-Timer, retxBSR-Timer) are configured for each radio bearer, for each logical channel, or for each logical channel group, for each timer for each radio bearer, logical channel, or logical channel group, or Multiple relationship between timers for each radio bearer, logical channel, and logical channel group, or timers for each radio bearer, logical channel, and logical channel group, and a terminal-specific timer (commonly configured in the terminal) It can have
  • two logical channels associated with the corresponding radio bearer may be indicated to be included in the same logical channel group.
  • two logical channels associated with the radio bearer may be indicated to be included in different logical channel groups.
  • the logical channel / logical channel group belongs to one logical channel with a higher priority than the priority of the logical channels for the data already available, or for any of the logical channels belonging to one logical channel group. Only when no data is available, the Regular BSR is triggered.
  • the terminal may perform uplink data on two logical channels associated with the corresponding radio bearer.
  • the base station may indicate information for indicating this to the terminal through RRC signaling.
  • the base station may indicate the PeriodicBSR-Timer to a specific value (for example, 0)
  • the UE may trigger a regular BSR when uplink data for the corresponding radio bearer becomes available.
  • the base station may set a periodicBSR-Timer dedicated to the corresponding radio bearer (or radio bearer). In this case, the UE may trigger a regular BSR when uplink data for the corresponding radio bearer (or logical channel / logical channel group) becomes available.
  • the UE has a specific threshold value for two logical channels associated with the corresponding radio bearer. If the available uplink data is greater than or equal to (or greater than) the corresponding threshold, the regular BSR can be triggered. To this end, the base station may instruct the terminal the threshold value for the radio bearer or logical channel.
  • the logical channel priority procedure took into account the following relative priorities (For the Logical Channel Prioritization procedure, the MAC entity shall take into account the following relative priority in decreasing order).
  • the priority of the MAC CE for the BSR included in the padding is lower than the data from any logical channel.
  • the uplink data belonging to the radio bearer If link data continues to occur, it is necessary to send a BSR quickly.
  • the priority of the MAC CE for the BSR included in the padding may be considered higher.
  • the priority of the MAC CE for the BSR included in the padding may be higher than the data from any logical channel.
  • the priority of the MAC CE for the BSR included in the padding may be set higher than any of the above-described priority orders.
  • the MAC PDU may be transmitted to the base station without including the additional padding BSR.
  • an additional padding BSR may be transmitted to the base station.
  • the radio bearer belonging to the radio bearer It is possible to define a BSR for available uplink data transmission.
  • the priority of MAC CE for BSR can be considered higher.
  • the priority of the MAC CE for the corresponding BSR may be higher than data from any logical channel.
  • the priority of the MAC CE for the corresponding BSR may be higher than any of the above-described priority orders.
  • the priority of the MAC CE for the corresponding BSR may be set to the same or higher priority as the aforementioned MAC control element for BSR and with exception of BSR included for padding.
  • the base station may allocate an uplink grant based on this. have.
  • the base station knows information about logical channel / logical channel group belonging to the radio bearer and mutually exclusive carriers associated with the logical channel. Therefore, even if a buffer state of one of the logical channels is received without reporting each buffer state for each logical channel / logical channel group belonging to the radio bearer, an uplink grant can be allocated accordingly.
  • the UE may transmit only a buffer state of one logical channel (or a logical channel including a first logical channel or default logical channel or PCell, or a logical channel associated with the first RLC entity) of the bearer to the base station.
  • the terminal transmits only available data for uplink data of one logical channel (or a logical channel including a first logical channel or a default logical channel or a PCell, or a logical channel associated with a first RLC entity) of one of the bearers to the base station. Can be.
  • the UE may use available data for uplink data of uplink data of a logical channel other than the logical channel among the bearers (or the logical channel not including the second logical channel or the PCell or the logical channel associated with the second RLC entity). It may not be considered as a trigger target.
  • the UE may perform an RLC entity for uplink data on a logical channel other than the logical channel among the bearers (or a logical channel not including the second logical channel or the PCell or a logical channel associated with the second RLC entity). You can choose not to indicate to the MAC entity or ignore the indicated available data.
  • the BSR may include a field for identifying whether a duplicate BSR is included in specific indication information (for example, logical channel identifier (LCID), index value, or division value).
  • specific indication information for example, logical channel identifier (LCID), index value, or division value.
  • the BSR can be used to send a buffer status report for a single logical channel group using a short BSR.
  • Sixth Embodiment An embodiment in which a BSR triggered for a logical channel / logical channel group associated with a radio bearer providing redundant transmission is maintained or transmitted to the next uplink grant
  • the number of logical channel groups is less than a specific value
  • all triggered BSRs may be cancelled.
  • the specific value described above may be preconfigured (or fixed) in the terminal or indicated to the terminal by the base station.
  • the number of logical channel groups is greater than a specific value, even if one BSR is included in one MAC PDU for transmission, the remaining BSR (or the specific triggered BSR except the transmitted BSR) may be maintained. Thereafter, if an uplink grant is received at the next TTI or within a certain number of TTIs, the corresponding BSR may be transmitted.
  • one BSR is transmitted for a logical channel / logical channel group of the corresponding radio bearer. Even if included in one MAC PDU, the remaining BSR except for the transmitted BSR (or a specific BSR triggered by including the logical channel / logical channel group of the corresponding radio bearer except the transmitted BSR) may be maintained. Thereafter, if an uplink grant is received at the next TTI or within a certain number of TTIs, the corresponding BSR may be transmitted.
  • the base station may configure two RLC entities associated with one radio bearer for redundant transmission to the terminal.
  • the base station may configure two RLC entities associated with one radio bearer in a terminal by being divided into a primary / default RLC entity and an additional RLC entity.
  • a basic / default RLC entity associated with a radio bearer will be referred to as a second RLC entity, which is added for redundant transmission to the first RLC entity.
  • the buffer status reporting procedure is used to provide the serving base station with information about available data or data volume for transmission in uplink (UL) buffers of the terminal associated with the MAC entity of the serving base station.
  • available data or data volume for transmission in uplink (UL) buffers of the terminal is referred to as “available data” or “amount of data available for transmission” or “data volume”. do.
  • the UE For reporting the MAC buffer status, the UE should consider the following as available data for transmission in the RLC layer.
  • RLC SDUs or segments according, that have not yet been included in an RLC data PDU
  • the UE should consider PDCP control PDUs and the following as available data for transmission in the PDCP layer.
  • the SDU itself if the SDU has not yet been processed by PDCP, or
  • the PDU if the SDU has been processed by PDCP
  • PDCP SDUs and PDCP Data PDUs corresponding to user data and PDCP control PDUs used for user data control in the PDCP layer were used to calculate available PDCP data volumes.
  • the terminal should consider the following as the amount of data (PDCP data volume) available for transmission in the PDCP layer.
  • the PDU once it has been processed by PDCP.
  • the available data may be processed in the terminal using the embodiments described below individually or in combination. This may be applied to the case of performing redundant transmission through two base stations (dual connectivity) based multiple cells as well as the case of performing redundant transmission through a plurality of carriers based on CA in a single base station.
  • the base station may configure one PDCP entity and two associated RLC entities in one radio bearer for redundant transmission to the terminal.
  • the UE may operate as follows when indicating available data (data volume) for transmission to the MAC entity for BSR triggering and buffer size calculation.
  • the terminal Upon receiving the information indicating arrival, the terminal (the PDCP entity of the terminal) indicates twice the data buffered in the PDCP entity with available data for transmission to the MAC entity. If, n times the data buffered in the PDCP entity redundantly transmitted through the n radio paths through the n logical channels.
  • the terminal (the PDCP entity of the terminal) Available data for transmission to the MAC entity indicates twice the data buffered in the PDCP entity.
  • the aforementioned L2 signaling may be information for instructing to activate a duplicate transmission by defining a control PDU in the RLC layer (or the first RLC entity).
  • the aforementioned L2 signaling may be information for instructing to activate a duplicate transmission by defining a control PDU in the PDCP layer (or PDCP entity).
  • the aforementioned L2 signaling may be information for defining a control PDU in a MAC layer (or MCG MAC entity) or for indicating to activate duplication transmission through a MAC control element (with a new LCID).
  • the MAC control element may include radio bearer identification information or logical channel identification information for a logical channel to activate redundant transmission, and activation / deactivation indication information of the corresponding radio bearer or logical channel.
  • the terminal when the terminal provides PDCP redundancy transmission using a single MAC entity based on a CA in a single base station, as shown in FIG. 8, the terminal (PDCP entity of the terminal) is available data for transmission to the MAC entity under the above conditions. It may indicate twice the total data buffered in the PDCP entity.
  • the PDCP data volume of the logical channel associated with the first RLC entity may be set to include PDCP data volumes for PDCP SDUs, PDCP data PDUs, and PDCP control PDUs and may be indicated to the corresponding MAC entity.
  • the PDCP data volume of the logical channel associated with the second RLC entity may also be set to include PDCP data volumes for PDCP SDUs, PDCP data PDUs, and PDCP control PDUs and may be indicated to the corresponding MAC entity. That is, data volume for PDCP SDUs, PDCP data PDUs, and PDCP control PDUs, which are all PDCP data, are calculated for calculating the PDCP data volume of the logical channel linked to the first RLC entity and the PDCP data volume of the logical channel linked to the second RLC entity. It can be calculated to include.
  • the PDU if the SDU is processed by PDCP, the PDU if the SDU has been processed by PDCP PDCP data PDU available data may be indicated.
  • PDCP control PDU available data may be indicated for the PDCP control PDU.
  • the PDCP available data calculated in the above manner may be indicated to the MAC entity. Therefore, when the PDCP PDU is copied by the PDCP, since the PDCP PDUs have already doubled the amount of data, the SDU data amount is doubled, but the PDCP PDU data amount is intact and may be indicated to the terminal MAC entity. In addition, since the PDCP control PDUs used for user data control do not need duplicate transmission, the corresponding data amount may be directly indicated for PDCP control PDUs that are not user data. Redundant transmissions are for low latency, high reliability services for user data. Accordingly, the PDCP control PDU for controlling user data may be transmitted through a cell / cell group associated with the first cell or the first RLC entity.
  • the PDCP data volume of the logical channel associated with the first RLC entity may be indicated to the corresponding MAC entity including PDCP SDUs, PDCP data PDUs, and PDCP data volumes for PDCP control PDUs.
  • the PDCP data volume of the logical channel associated with the second RLC entity may be indicated to the corresponding MAC entity including only the PDCP data volumes for the PDCP SDUs. That is, the PDCP data volume of the logical channel linked to the second RLC entity may be indicated to the corresponding MAC entity except for PDCP data PDUs and PDCP data volumes for PDCP control PDUs.
  • PDU if the SDU has been processed by PDCP (if the SDU has been processed by PDCP or PDCP and has been duplicated / copied or if there are duplicate PDUs before submitting to the lower layer from PDCP) Available data can be indicated.
  • -PDCP control PDU available data / data volume may be indicated for the PDCP control PDU.
  • the PDCP available data calculated in the above manner may be indicated to the MAC entity. This may be a function that the PDCP duplicate function is provided by PDCP. For example, if there are duplicated / copied PDCP PDUs when calculating the PDCP data volume, the duplicated / copied PDCP PDUs must be distinguished from the duplicated / copied PDCP PDUs when calculating the PDCP data volume. Otherwise, if the PDCP PDU for the user data is duplicated / copyed when submitting to the lower layer, it may be necessary to distinguish the PDCP PDUs when calculating the PDCP data volume.
  • the PDCP SDUs or PDCP PDUs will be instructed to double the amount of data until the PDCP PDUs for user data are duplicated / copied. Can be.
  • the amount of PDCP control PDU data other than user data may be instructed to the terminal MAC entity as it is.
  • the PDCP data volume of the logical channel associated with the first RLC entity may be indicated to the corresponding MAC entity including PDCP SDUs, PDCP data PDUs, and PDCP data volumes for PDCP control PDUs.
  • the PDCP data volume of the logical channel associated with the second RLC entity may be indicated to the corresponding MAC entity including PDCP SDUs and PDCP data volumes for PDCP data PDUs. That is, the PDCP data volume of the logical channel associated with the second RLC entity may be indicated to the corresponding MAC entity except for the PDCP data volumes for the PDCP control PDUs.
  • the terminal when the terminal provides PDCP redundant transmission using two MAC entities on a DC basis at two base stations, the terminal (PDCP entity of the terminal) is PDCP as available data for transmission to each MAC entity under the above conditions. It can indicate the amount of available data buffered in the entity.
  • Second Embodiment An Example of Indicating Existing PDCP Data Amount as Available Data When a Redundant Transmission Radio Bearer Is Disabled
  • the base station may configure one PDCP entity and two associated RLC entities in one radio bearer for redundant transmission to the terminal.
  • the terminal may operate as follows when indicating available data (data volume) for transmission to the MAC entity for BSR triggering and buffer size calculation.
  • the terminal Upon receipt of information indicating no, or no information indicating that a duplicate transmission condition has been reached by the physical layer, the terminal (PDCP entity of the terminal) is buffered in the PDCP entity with available data for transmission to the MAC entity. Indicates data As another example, if the radio bearer indication information is configured by the base station for redundant transmission and the base station does not receive the L2 signaling for activating the redundant transmission, or if the base station receives the L2 signaling for deactivating the redundant transmission.
  • the terminal (PDCP entity of the terminal) if receiving a signaling for releasing / deactivating the redundant transmission by the base station, the terminal (PDCP entity of the terminal) indicates the amount of data buffered in the PDCP entity as available data for transmission to the MAC entity.
  • the terminal (PDCP entity of the terminal) is It indicates the amount of data buffered in the PDCP entity as available data for transmission to the MAC entity (the MAC entity associated with the first RLC entity).
  • the terminal when the terminal provides PDCP redundancy transmission using a single MAC entity based on a CA in a single base station as shown in FIG. 8, the terminal (the PDCP entity of the terminal) is connected to the MAC entity (the first RLC entity) under the above conditions.
  • MAC data may be used to indicate the amount of available data buffered in the PDCP entity as available data for transmission.
  • the UE when the UE provides PDCP redundant transmission using one MAC entity based on CA in a single base station, the UE may indicate available data of the second RLC entity according to whether the redundant transmission bearer is activated. have.
  • the terminal (the PDCP entity of the terminal or the second RLC entity of the terminal) is transferred to the MAC entity. Indicates available data buffered in the second RLC entity with available data for transmission.
  • the terminal Upon receipt of the information indicating that the message is received), the terminal (second RLC entity of the terminal) indicates available data buffered in the second RLC entity with available data for transmission to the MAC entity.
  • the terminal Upon receiving the information indicating that the packet has not been received or receiving the information indicating that the duplicate transmission condition has been reached by the physical layer, the terminal (second RLC entity of the terminal) sets the available data for transmission to the MAC entity to zero. Instruct. Or not instructed.
  • the radio bearer indication information is configured by the base station for redundant transmission and the base station does not receive the L2 signaling for activating the redundant transmission, or if the base station receives the L2 signaling for deactivating the redundant transmission. Or, if receiving a signaling for releasing / deactivating redundant transmission by the base station, the terminal (second RLC entity of the terminal) indicates 0 available data for transmission to the MAC entity. Or not instructed.
  • the MAC entity may calculate the buffer size by including the PDCP data volume in each logical channel / logical channel group associated with the corresponding radio bearer.
  • the base station may configure one PDCP entity and two associated RLC entities for one radio bearer for redundant transmission to the terminal.
  • the base station may transmit information instructing the terminal to activate / deactivate the redundant transmission for the radio bearer configured for the redundant transmission. Accordingly, the base station may make an approximate uplink scheduling when calculating the amount of uplink buffer for a specific bearer. Therefore, the terminal may indicate the PDCP available data amount as it is, even if the configuration information for the redundant transmission radio bearer.
  • the buffer status size of the corresponding radio bearer may be calculated in consideration of whether the redundant transmission is activated.
  • the terminal Upon receipt of the information indicating that the message is received), the terminal (the PDCP entity of the terminal) indicates the data buffered in the PDCP entity as available data for transmission to the MAC entity.
  • the MAC doubles the available data of the PDCP entity corresponding to the buffer status reporting to calculate the buffer status. That is, when calculating the buffer state of the first logical channel and the buffer state of the second logical channel associated with the radio bearer, the available data amount of the PDCP entity is included.
  • the terminal PDCP entity of the terminal
  • the terminal is available data for transmission to the MAC entity.
  • the MAC doubles the available data of the PDCP entity corresponding to the buffer status reporting to calculate the buffer status. That is, when calculating the buffer state of the first logical channel and the buffer state of the second logical channel associated with the radio bearer, the available data amount of the PDCP entity is included.
  • the terminal when the terminal provides PDCP redundant transmission using one MAC entity on a CA based on a single base station, the terminal (PDCP entity of the terminal) is a PDCP entity as available data for transmission to the MAC entity. It can indicate the amount of data buffered in.
  • the MAC doubles the available data of the PDCP entity corresponding to the buffer status reporting to calculate the buffer status. That is, when calculating the buffer state of the first logical channel and the buffer state of the second logical channel associated with the radio bearer, the available data amount of the PDCP entity is included.
  • two logical channels associated with one radio bearer may be processed to include data volumes (available data) of PDCP entities.
  • the terminal may transmit a buffer size including a PDCP data volume to each base station or logical channel group associated with one radio bearer.
  • the RRC connection reconfiguration messages used to configure / modify RRC connections are described in the master cell group configuration information, the secondary cell. It may include one or more of group configuration information, radio bearer configuration information, dedicated NAS configuration information (dedeicatedInfoNAS), measurement configuration information and other configuration information.
  • 16 is a diagram illustrating an example of radio bearer configuration information according to an embodiment.
  • 17 is a diagram illustrating an example of cell group configuration information according to an embodiment.
  • the radio bearer configuration information includes SRB (signaling radio bearer) configuration information (eg srb-ToAddModList), DRB (data radio bearer) configuration information (eg drb-ToAddModList), and security configuration information (eg securityConfig). ) May include one or more pieces of information.
  • SRB signal radio bearer
  • DRB data radio bearer
  • securityConfig securityConfig
  • SRB configuration information (e.g. srb-ToAddMod) and DRB configuration information (e.g. drb-ToAddMod) may include PDCP configuration information.
  • the PDCP entity configured in the corresponding radio bearer and the RLC entity associated with the bearer could be identified through the radio bearer type information.
  • more radio bearer types have been defined than the LTE, such as the introduction of SCG split bearer, and accordingly, the radio bearer reconfiguration procedure is more complicated.
  • the upper layer configuration for example, bearer configuration including PDCP and SDAP
  • the lower layer configuration for example, MCG / SCG configuration including RLC and MAC
  • RRC signaling information can be designed.
  • the cell group configuration information may include master cell group (master node) configuration information or secondary cell group (secondary node) configuration information.
  • the base station directs the configuration parameter for one cell group to the terminal through the cell group configuration information element (CellGroupConfig IE).
  • CellGroupConfig IE cell group configuration information element
  • the cell group configuration information may distinguish the MCG and the SCG through the cell group identifier. For example, if the cell group identifier is not included, it may represent an MCG, otherwise it may represent an SCG. As another example, the cell group configuration information may include a parameter for distinguishing the MCG and the SCG.
  • Cell group configuration information includes logical channel configuration information (eg logicalChannel-ToAddModList), MAC cell group configuration information (eg mac-CellGroupConfig), RLF timer configuration information (eg rlf-TimersAndConstants), PCell configuration information (eg pCellConfig), and SCell configuration information. It may include one or more pieces of information (eg sCellToAddModList).
  • mapping / association information should be indicated between the PDCP entity included in the radio bearer configuration information as the upper layer configuration information and the RLC entity included in the cell group configuration information as the lower layer configuration information. do.
  • the PDCP entity included in the radio bearer configuration information may include information for indicating an additional RLC entity associated with the PDCP configuration information.
  • this indicates information distinguished from information for indicating a basic RLC entity associated with PDCP configuration information for the PDCP entity included in the radio bearer configuration information.
  • the PDCP configuration information may include information for indicating a redundant transmission configuration.
  • the logical channel configuration information (LCH-Config) included in the cell group configuration information includes information (RLC-config) for indicating configuration of the RLC entity associated with the corresponding logical channel. It may include.
  • the logical channel configuration information (LCH-Config) may include radio bearer identification information associated with the logical channel, cell information (allowedCells) or cell list information allowed for the logical channel.
  • the terminal may process the available data (data volume) of the PDCP entity according to the number of associated RLC entities, whether to configure and activate the PDCP duplication transmission, and whether or not the CA-based PDCP duplication transmission.
  • the terminal may process the PDCP available data as follows.
  • the terminal may assign the PDCP data volume to the corresponding MAC entity. Instructed by This indicates that the PDCP entity of the terminal directs the PDCP data volume to the MAC entity associated with the first RLC entity.
  • the sending PDCP entity is associated with two RLC entities (or associated with two logical channels)
  • PDCP duplication is configured and activated, and different logical channels for the duplicate transmission have the same MAC entity.
  • the terminal indicates the PDCP data volume to the corresponding MAC entity for each of two logical channels associated with the corresponding MAC entity.
  • the terminal indicates twice the PDCP data volume to the corresponding MAC entity.
  • the terminal indicates two logical channel identification information and PDCP data volume associated with the corresponding MAC entity to the corresponding MAC entity.
  • the terminal indicates the PDCP data volume to the corresponding MAC entity.
  • the terminal (PDCP entity of the terminal) indicates the PDCP data volume of the first logical channel associated with the first RLC entity to the associated MAC entity and associates the PDCP data volume of the second logical channel associated with the second RLC entity with the associated MAC entity. Indicated by a MAC entity.
  • the terminal calculates the BSR buffer size including the corresponding PDCP data ballroom for each of the two linked logical channels.
  • the sending PDCP entity is associated with two RLC entities (or with two logical channels), and PDCP duplication (pdcpDuplication) is configured and activated, but different logical channels for duplicate transmission have different MAC entities.
  • the terminal (PDCP entity of the terminal) directs the PDCP data volume to the MCG MAC entity and the SCG MAC entity (both the MCG MAC entity and the SCG MAC entity).
  • the terminal (PDCP entity of the terminal) indicates the data volume of the first logical channel associated with the first RLC entity to the associated first MAC entity and associates the data volume of the second logical channel associated with the second RLC entity. Point to the second MAC entity.
  • the terminal (PDCP entity of the terminal) directs the PDCP data volume to the corresponding MAC entity.
  • the terminal (PDCP entity of the terminal) indicates the PDCP data volume to the MCG MAC entity.
  • the terminal (PDCP entity of the terminal) directs the PDCP data volume to the MAC entity associated with the first RLC entity.
  • the terminal (PDCP entity of the terminal) indicates the PDCP data volume to the corresponding MAC entity for one logical channel associated with the corresponding MAC entity.
  • the sending PDCP entity is associated with two RLC entities (or with two logical channels) and PDCP duplication (pdcpDuplication) is configured but not activated, then different logical channels for duplicate transmission have different MAC entities.
  • the terminal indicates the PDCP data volume to the corresponding MAC entity.
  • the terminal indicates the PDCP data volume to the MCG MAC entity.
  • the terminal directs the PDCP data volume to the MAC entity associated with the first RLC entity.
  • the sending PDCP entity is associated with two RLC entities (or with two logical channels), but if PDCP duplication (pdcpDuplication) is not configured, the entire pending for initial transmission in the two associated RLC entities
  • the terminal (PDCP of the terminal) Entity directs the PDCP data volume to the corresponding MAC entity.
  • the terminal (PDCP entity of the terminal) directs the PDCP data volume to the MAC entity configured in the uplink path.
  • the terminal (PDCP entity of the terminal) directs the PDCP data volume to the associated MAC entity.
  • the terminal (PDCP entity of the terminal) directs the PDCP data volume to the MAC entity associated with the associated RLC entity.
  • the terminal (PDCP entity of the terminal) directs the PDCP data volume to the MAC entity including the associated logical channel.
  • the terminal (PDCP entity of the terminal) directs the PDCP data volume to the MAC entity associated with the first RLC entity.
  • the terminal (the PDCP entity of the terminal) indicates the PDCP data volume to 0 to another MAC entity. Or, the terminal (PDCP entity of the terminal) indicates the PDCP data volume to 0 as the MAC entity associated with the second RLC entity.
  • the sending PDCP entity is associated with two RLC entities (or with two logical channels), but if PDCP duplication (pdcpDuplication) is not configured, the entire pending for initial transmission in the two associated RLC entities If the PDCP data volume and the RLC data volume are greater than the uplink data split threshold (or if the PDCP data volume is greater than the up-link data split threshold), the terminal (PDCP entity on the terminal) Indicates the PDCP data volume to the MCG MAC entity and the SCG MAC entity. The terminal (PDCP entity of the terminal) directs the PDCP data volume to the MAC entity associated with the first RLC entity and the MAC entity associated with the second RLC entity.
  • pdcpDuplication PDCP duplication
  • the BS when the UE is configured or activated through CA by a single BS for a specific bearer, the BS effectively provides uplink resource allocation by providing buffer status reporting of the UE. It is effective to perform as.
  • FIG. 18 is a diagram illustrating a terminal configuration according to an embodiment.
  • a terminal 1800 configuring a carrier merge and transmitting a buffer status report includes a receiver 1830 receiving higher layer signaling including information for configuring data redundant transmission through carrier aggregation from a base station.
  • a transmitter 1820 for transmitting a buffer status report configured to be included in both the channel group and the logical channel group associated with the second RLC entity to the base station.
  • the receiver 1830 may configure a carrier merge with one base station and receive an RRC message including additional RLC configuration information for redundant transmission of the same data to the base station through a plurality of carriers using carrier merge.
  • the information for configuring redundant transmission includes information on a plurality of RLC entities configured in the terminal for redundant transmission of data, logical channel information associated with each RLC entity, and each RLC entity and one PDCP. It may include at least one of information for linking the entity and MAC entity configuration information for redundant transmission.
  • the controller 1810 may configure an additional RLC entity in the terminal based on the information for configuring the received duplicate transmission.
  • a plurality of additional RLC entity may be configured by the configuration of the base station.
  • the controller 1810 may configure the first RLC entity and the second RLC entity in association with one PDCP entity according to higher layer signaling.
  • the controller 1810 may configure a logical channel in association with the RLC entity to distinguish the RLC entity added to one MAC entity. That is, the controller 1810 may configure a logical channel linked to the first RLC entity and a logical channel linked to the second RLC entity in the MAC entity.
  • the MAC entity maps and processes data transmitted and received through one radio bearer to each logical channel, thereby repeatedly transmitting PDCP data to a base station through a plurality of RLC entities, and transmitting the duplicated data to the PDCP entity. It can also pass through each logical channel.
  • the transmitter 1820 may transmit the data transmitted through the logical channel associated with the first RLC entity and the logical channel associated with the second RLC entity to the base station through different carriers.
  • the first RLC entity and the second RLC entity may be configured in association with different logical channels based on logical channel identifiers.
  • the first RLC entity and the second RLC entity may be configured in association with one PDCP entity based on the radio bearer identifier.
  • the transmitter 1820 may transmit a buffer status report to the base station according to a buffer status report trigger condition when a redundant transmission configuration such as a plurality of RLC entities is completed and the data redundant transmission function is activated.
  • a redundant transmission configuration such as a plurality of RLC entities
  • the redundant transmission function may not be activated according to a setting.
  • activation of data duplication transmission may be indicated through a separate signal from the base station.
  • a signal for activation of redundant transmission may be indicated from the base station through the MAC control element for each data radio bearer. That is, the base station may activate or deactivate the redundant transmission function configured in the terminal through a MAC control element for each radio bearer.
  • the controller 1810 may set the PDCP data volume to be included in both the logical channel group associated with the first RLC entity and the logical channel group associated with the second RLC entity.
  • the transmitter 1820 may transmit a buffer status report including buffer information of each logical channel group to the base station. That is, the PDCP data volume may be set to be included in all of the logical channel groups associated with each RLC entity.
  • controller 1810 may process the information for configuring the above-described redundant transmission or the information for activating the redundant transmission or the data for the redundant transmission.
  • the controller 1810 may be configured as a general terminal according to a terminal constituting a single base station-based CA according to the above-described embodiments of the present invention performing redundant transmission and reception of data through a plurality of carriers and processing a buffer status report. 1800 controls the operation.
  • the receiver 1830 receives the downlink control information, data, and messages from the base station through the corresponding channel, and the transmitter 1820 transmits the uplink control information, data, and message to the base station through the corresponding channel.
  • 19 is a diagram illustrating a configuration of a base station according to an embodiment.
  • a base station 1900 for configuring a carrier merge in a terminal and receiving a buffer status report includes a control unit 1910 for generating information for configuring data redundant transmission through carrier merge and a carrier merge with a terminal.
  • a receiving unit 1930 for receiving a buffer status report including the PDCP data volume of the terminal set to be included in all of the logical channel groups associated with the.
  • the information for configuring redundant transmission includes information on a plurality of RLC entities configured in the terminal, logical channel information associated with each RLC entity, and each RLC entity and one PDCP in order for the terminal to transmit data redundantly. It may include at least one of information for linking the entity and MAC entity configuration information for redundant transmission.
  • the transmitter 1920 may transmit information for configuring single base station-based redundant transmission of the terminal through higher layer signaling such as an RRC message.
  • the UE receives information for configuring redundant transmission and includes a plurality of RLCs including a first Radio Link Control (RLC) entity and a second RLC entity associated with one Packet Data Convergence Protocol (PDCP) entity.
  • RLC Radio Link Control
  • PDCP Packet Data Convergence Protocol
  • An entity may be configured, and a logical channel associated with the first RLC entity and a logical channel associated with the second RLC entity may be configured in one medium access control (MAC) entity.
  • MAC medium access control
  • the reception unit 1930 may receive data transmitted in association with each logical channel of the terminal by overlapping them through different carriers. That is, the receiver 1930 may receive the same data repeatedly through different carriers.
  • different carriers may be carriers constituting the CA of the terminal.
  • the buffer status report may include a PDCP data volume for each logical channel group.
  • the terminal may assign the PDCP data volume to both the logical channel group associated with the first RLC entity and the logical channel group associated with the second RLC entity. It can be transmitted to the base station. That is, the PDCP data volume may be included in all logical channel groups associated with each RLC entity.
  • the transmitter 1920 may transmit information indicating that data duplication transmission of the terminal is activated through a MAC control element for each data radio bearer. For example, a signal for activating redundant transmission may be indicated to the terminal through a MAC control element for each data radio bearer.
  • the controller 1910 may be configured to repeatedly transmit and receive the same data through a plurality of carriers and to receive a buffer status report from a terminal constituting a single base station-based CA according to the above-described embodiments.
  • the overall operation of the base station 1900 is controlled.
  • the transmitter 1920 and the receiver 1930 are used to transmit and receive signals, messages, and data necessary for performing the above-described embodiments with the terminal.

Landscapes

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

Abstract

La présente invention concerne une technologie dans laquelle un terminal configure une agrégation de porteuses avec une seule station de base dans un réseau de communications mobiles de prochaine génération (NR) afin d'exécuter une transmission répétée de données, et transmet un rapport d'état de tampon correspondant.
PCT/KR2018/002750 2017-03-10 2018-03-08 Procédé de transmission de rapport d'état de tampon, et dispositif associé Ceased WO2018164499A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201880004237.3A CN109937587B (zh) 2017-03-10 2018-03-08 缓冲区状态报告传输方法及其设备
US16/349,259 US10986530B2 (en) 2017-03-10 2018-03-08 Buffer state report transmission method and device therefor

Applications Claiming Priority (8)

Application Number Priority Date Filing Date Title
KR20170030764 2017-03-10
KR10-2017-0030764 2017-03-10
KR20170068074 2017-05-31
KR10-2017-0068074 2017-05-31
KR1020170152149A KR20180131335A (ko) 2017-05-31 2017-11-15 차세대 이동통신을 위한 중복전송 버퍼 상태 트리거 방법 및 장치
KR10-2017-0152149 2017-11-15
KR10-2018-0026611 2018-03-07
KR1020180026611A KR102065137B1 (ko) 2017-03-10 2018-03-07 버퍼 상태 리포트 전송 방법 및 그 장치

Publications (1)

Publication Number Publication Date
WO2018164499A1 true WO2018164499A1 (fr) 2018-09-13

Family

ID=63447834

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2018/002750 Ceased WO2018164499A1 (fr) 2017-03-10 2018-03-08 Procédé de transmission de rapport d'état de tampon, et dispositif associé

Country Status (1)

Country Link
WO (1) WO2018164499A1 (fr)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020060234A1 (fr) * 2018-09-21 2020-03-26 주식회사 케이티 Procédé et dispositif de transmission de données
KR20200034933A (ko) * 2018-09-21 2020-04-01 주식회사 케이티 데이터 전송 방법 및 장치
CN110972205A (zh) * 2018-09-28 2020-04-07 华为技术有限公司 一种通信方法及设备
WO2020215796A1 (fr) * 2019-04-22 2020-10-29 华为技术有限公司 Procédé et dispositif de communication
CN112153687A (zh) * 2019-06-27 2020-12-29 大唐移动通信设备有限公司 一种缓存信息上报方法、接收方法、终端和网络侧设备
CN112152764A (zh) * 2019-06-27 2020-12-29 大唐移动通信设备有限公司 一种重复传输激活状态上报方法、确认方法和相关设备
CN112399641A (zh) * 2019-08-13 2021-02-23 大唐移动通信设备有限公司 一种直接通信接口重复传输的方法、终端及网络侧设备
CN113194551A (zh) * 2019-01-16 2021-07-30 Oppo广东移动通信有限公司 数据复制传输配置方法、装置、芯片及计算机程序

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015016646A1 (fr) * 2013-07-31 2015-02-05 삼성전자 주식회사 Terminal pour prise en charge de communication de dispositif à dispositif et son procédé de fonctionnement
WO2015020461A1 (fr) * 2013-08-07 2015-02-12 주식회사 팬택 Procédé et appareil de transmission de rapport d'état de tampon dans un système de communication sans fil
US20150181479A1 (en) * 2013-01-18 2015-06-25 Mediatek Inc. Mechanism for Radio Link Monitoring and Radio Link Failure Handling in Small Cell Networks
US20160337895A1 (en) * 2014-03-12 2016-11-17 Lg Electronics Inc. Method for calculating and reporting an amount of data available for transmission and a device therefor

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150181479A1 (en) * 2013-01-18 2015-06-25 Mediatek Inc. Mechanism for Radio Link Monitoring and Radio Link Failure Handling in Small Cell Networks
WO2015016646A1 (fr) * 2013-07-31 2015-02-05 삼성전자 주식회사 Terminal pour prise en charge de communication de dispositif à dispositif et son procédé de fonctionnement
WO2015020461A1 (fr) * 2013-08-07 2015-02-12 주식회사 팬택 Procédé et appareil de transmission de rapport d'état de tampon dans un système de communication sans fil
US20160337895A1 (en) * 2014-03-12 2016-11-17 Lg Electronics Inc. Method for calculating and reporting an amount of data available for transmission and a device therefor

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Data Duplication in Lower Layers (HARQ", TDOC R2-1702032, 3GPP TSG-RAN WG2 #97, 20 February 2017 (2017-02-20), Athens, Greece, XP051237183 *

Cited By (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112740749A (zh) * 2018-09-21 2021-04-30 株式会社Kt 用于传输数据的方法和装置
KR20200034933A (ko) * 2018-09-21 2020-04-01 주식회사 케이티 데이터 전송 방법 및 장치
CN112740749B (zh) * 2018-09-21 2024-08-20 株式会社Kt 用于传输数据的方法和装置
WO2020060234A1 (fr) * 2018-09-21 2020-03-26 주식회사 케이티 Procédé et dispositif de transmission de données
US11523303B2 (en) 2018-09-21 2022-12-06 Kt Corporation Method and device for transmitting data
KR102385544B1 (ko) * 2018-09-21 2022-04-14 주식회사 케이티 데이터 전송 방법 및 장치
US11974162B2 (en) 2018-09-28 2024-04-30 Huawei Technologies Co., Ltd. Communication method and device
CN110972205B (zh) * 2018-09-28 2021-08-13 华为技术有限公司 一种通信方法及设备
CN110972205A (zh) * 2018-09-28 2020-04-07 华为技术有限公司 一种通信方法及设备
CN113194551B (zh) * 2019-01-16 2023-01-03 Oppo广东移动通信有限公司 数据复制传输配置方法、装置、芯片及计算机程序
CN113194551A (zh) * 2019-01-16 2021-07-30 Oppo广东移动通信有限公司 数据复制传输配置方法、装置、芯片及计算机程序
US12058564B2 (en) 2019-01-16 2024-08-06 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Data replication transmission configuration method, apparatus, chip, and computer program
US11991785B2 (en) 2019-04-22 2024-05-21 Huawei Technologies Co., Ltd. Communication method and device for use with a packet data convergence protocol (PDCP) duplicate transmission function
WO2020215796A1 (fr) * 2019-04-22 2020-10-29 华为技术有限公司 Procédé et dispositif de communication
CN112152764A (zh) * 2019-06-27 2020-12-29 大唐移动通信设备有限公司 一种重复传输激活状态上报方法、确认方法和相关设备
CN112153687A (zh) * 2019-06-27 2020-12-29 大唐移动通信设备有限公司 一种缓存信息上报方法、接收方法、终端和网络侧设备
CN112153687B (zh) * 2019-06-27 2022-10-18 大唐移动通信设备有限公司 一种缓存信息上报方法、接收方法、终端和网络侧设备
CN112152764B (zh) * 2019-06-27 2022-08-23 大唐移动通信设备有限公司 一种重复传输激活状态上报方法、确认方法和相关设备
CN112399641A (zh) * 2019-08-13 2021-02-23 大唐移动通信设备有限公司 一种直接通信接口重复传输的方法、终端及网络侧设备
US12470328B2 (en) 2019-08-13 2025-11-11 Datang Mobile Communications Equipment Co., Ltd. Method for sidelink interface duplication transmission, terminal, and network-side device

Similar Documents

Publication Publication Date Title
WO2019160342A1 (fr) Procédé et appareil prenant en charge une mobilité sans rach utilisant des faisceaux préalablement attribués dans un système de communication sans fil
WO2018164499A1 (fr) Procédé de transmission de rapport d'état de tampon, et dispositif associé
WO2020067813A1 (fr) Appareil et procédé permettant d'établir une double connectivité dans un système de communication sans fil
WO2015064972A1 (fr) Procédé et appareil de configuration de connexion double dans un réseau de communication mobile
WO2015142104A1 (fr) Procédé et appareil pour émettre/recevoir un signal dans un système de communication mobile prenant en charge une pluralité de porteuses
WO2014084638A1 (fr) Procédé et dispositif pour exécuter une communication dans un système de communication sans fil
WO2014109558A1 (fr) Procédé de signalement d'état de tampon et dispositif de communication associé
WO2018062977A1 (fr) Procédé de communication dans un système dans lequel coexistent la 4g et la 5g, et dispositif associé
WO2015023128A1 (fr) Méthode et appareil de transmission/réception de données en utilisant de multiples porteuses dans un système de communication mobile
WO2017039042A1 (fr) Procédé et dispositif de transmission/réception de données de terminal dans un système de communication sans fil
WO2020027491A1 (fr) Procédé de traitement de données dans un nœud relais, et dispositif associé
WO2018004278A1 (fr) Procédé et dispositif pour transmettre ou recevoir des données dans un état de double connectivité
WO2018169242A1 (fr) Procédé de réception d'un message de commande en double, et dispositif associé
WO2015020356A1 (fr) Procédé de transmission d'un rapport d'état de tampon dans une communication entre dispositifs et dispositif associé
WO2015046780A1 (fr) Procédé de transmission de données de liaison montante, et appareil correspondant
WO2020159168A1 (fr) Procédé de réplication de données, procédé de comptage de données, entités et supports correspondants
WO2015152554A1 (fr) Procédé de commande de fonctionnement de cellule secondaire d'un terminal, et appareil associé
WO2018016895A1 (fr) Procédé de réalisation d'un processus de mobilité du terminal nb-iot et appareil associé
WO2014163419A1 (fr) Procédé de traitement d'échec de liaison radio et dispositif associé
WO2016159634A1 (fr) Procédé de reconfiguration d'un support sans fil et dispositif associé
WO2014133271A1 (fr) Procédé permettant de transmettre un rapport d'état de mémoire tampon d'un terminal dans un environnement à petites cellules et dispositif associé
WO2014126356A1 (fr) Procédé pour activer ou désactiver une petite cellule et appareil à cet effet
WO2023140626A1 (fr) Procédé et dispositif de fourniture d'informations de capacité de terminal sur des intervalles simultanés dans un système de communication mobile sans fil
WO2014119858A1 (fr) Procédé de transmission de données en clair d'un utilisateur dans un environnement de petite cellule et appareil pour ce procédé
WO2024010315A1 (fr) Procédé et appareil pour la prise en charge de la mobilité de la couche 2

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC ( EPO FORM 1205A DATED 09/12/2019 )

122 Ep: pct application non-entry in european phase

Ref document number: 18764926

Country of ref document: EP

Kind code of ref document: A1