[go: up one dir, main page]

WO2020060234A1 - Procédé et dispositif de transmission de données - Google Patents

Procédé et dispositif de transmission de données Download PDF

Info

Publication number
WO2020060234A1
WO2020060234A1 PCT/KR2019/012156 KR2019012156W WO2020060234A1 WO 2020060234 A1 WO2020060234 A1 WO 2020060234A1 KR 2019012156 W KR2019012156 W KR 2019012156W WO 2020060234 A1 WO2020060234 A1 WO 2020060234A1
Authority
WO
WIPO (PCT)
Prior art keywords
rlc
rlc entity
transmission
pdcp
radio bearer
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/KR2019/012156
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 KR1020190061275A external-priority patent/KR20200034921A/ko
Application filed by KT Corp filed Critical KT Corp
Priority to CN201980061954.4A priority Critical patent/CN112740749B/zh
Priority to US17/277,714 priority patent/US11523303B2/en
Publication of WO2020060234A1 publication Critical patent/WO2020060234A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • 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/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states

Definitions

  • the present disclosure relates to data duplication transmission technology in the next generation / 5G radio access technology (NR).
  • NR next generation / 5G radio access technology
  • LTE-Advanced a technology for a next-generation wireless access network has been developed to accommodate data transmission and reception of more terminals and to provide higher QoS.
  • development work is underway on a temporary 5G network centering on 3GPP.
  • 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 carrier aggregation using a plurality of carriers.
  • This embodiment is intended to provide a method and apparatus for dynamically providing a redundant transmission function using a next-generation wireless access technology.
  • MAC control element including instructions for configuring a plurality of RLC (Radio Link Control) objects used to process redundant transmission to a radio bearer and instructions for instructing to change the activation state for the plurality of RLC objects. It provides a method comprising the steps of receiving a control element) and changing the RLC entity indicated in the activated state to the activated state by the indication information, and transmitting the data redundantly using the activated RLC object.
  • RLC Radio Link Control
  • a plurality of Radio Link Controls used to process duplicate transmission for a radio bearer associated with one Packet Data Convergence Protocol (PDCP) entity
  • PDCP Packet Data Convergence Protocol
  • Transmitting the configuration information for configuring the object to the terminal transmitting the indication information instructing the activation state change for the plurality of RLC objects to the terminal, and transmitting the duplicated information through the RLC object activated by the indication information
  • It includes a step of receiving the data, the configuration information provides a method comprising at least one of the RLC entity index information and initial activation state information for each of the plurality of RLC entities.
  • one embodiment of the terminal for transmitting data is linked to a single Packet Data Convergence Protocol (PDCP) entity, the redundant transmission to the radio bearer
  • PDCP Packet Data Convergence Protocol
  • a control unit constituting a plurality of RLC (Radio Link Control) objects used to process, and a receiving unit for receiving a MAC control element (MAC Control element) that includes indication information indicating an activation state change for the plurality of RLC entities, and activation
  • MAC Control element MAC Control element
  • the control unit provides a terminal device for changing the RLC entity indicated in the activation state by the indication information to the activation state.
  • a base station for controlling the data transmission of the terminal, a plurality of RLC (Radio Link Control) object used to process the redundant transmission to the radio bearer associated with a single Packet Data Convergence Protocol (PDCP) entity Transmitting the configuration information for configuring the terminal to the terminal, the data transmitted through the RLC entity activated by the transmitting unit and the indication information to transmit the indication information indicating the activation state change for a plurality of RLC entities to the terminal
  • a base station apparatus including at least one of RLC entity index information and initial activation state information for each of a plurality of RLC entities, including a receiving unit for receiving.
  • This embodiment provides an effect of dynamically providing a redundant transmission function using the next generation wireless access technology.
  • FIG. 1 is a diagram briefly showing a structure of an NR wireless communication system to which the present embodiment can be applied.
  • FIG. 2 is a diagram for explaining a frame structure in an NR system to which the present embodiment can be applied.
  • FIG. 3 is a diagram for describing a resource grid supported by a radio access technology to which the present embodiment can be applied.
  • FIG. 4 is a diagram for describing a bandwidth part supported by a radio access technology to which the present embodiment can be applied.
  • FIG. 5 exemplarily shows a synchronization signal block in a radio access technology to which the present embodiment can be applied.
  • FIG. 6 is a diagram for explaining a random access procedure in a radio access technology to which the present embodiment can be applied.
  • FIG. 8 is a diagram for describing a terminal operation according to an embodiment.
  • FIG. 9 is a diagram illustrating a MAC CE including indication information according to an embodiment.
  • FIG. 10 is a diagram for explaining the operation of a base station according to an embodiment.
  • 11 exemplarily shows a MAC CE indicating redundant transmission according to another embodiment.
  • FIG. 13 exemplarily shows a MAC CE indicating a redundant transmission path according to another embodiment.
  • FIG. 14 is a diagram illustrating an exemplary MAC CE indicating a redundant transmission path according to another embodiment.
  • 15 exemplarily shows a MAC CE indicating redundant transmission according to another embodiment.
  • 16 is a diagram showing the configuration of a terminal according to an embodiment.
  • 17 is a diagram showing the configuration of a base station according to an embodiment.
  • first, second, A, B, (a), and (b) may be used. These terms are only for distinguishing the component from other components, and the essence, order, order, or number of the component is not limited by the term.
  • temporal sequential relationships such as “after”, “after”, “after”, “before”, etc. Or, when the flow sequential relationship is described, it may also include a case where the "direct” or “direct” is not continuous unless used.
  • the wireless communication system in the present specification means a system for providing various communication services such as voice and data packets using radio resources, and may include a terminal, a base station, or a core network.
  • the embodiments disclosed below can be applied to a wireless communication system using various wireless access technologies.
  • the present embodiments are code division multiple access (CDMA), frequency division multiple access (FDMA), timedivision multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), and single-electron frequency division multiple access (SC-FDMA).
  • CDMA code division multiple access
  • FDMA frequency division multiple access
  • TDMA timedivision multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single-electron frequency division multiple access
  • the wireless access technology may mean not only a specific access technology, but also a communication technology for each generation established by various communication consultation organizations such as 3GPP, 3GPP2, WiFi, Bluetooth, IEEE, and ITU.
  • CDMA may be implemented with a radio technology such as universal terrestrial radio access (UTRA) or CDMA2000.
  • UTRA universal terrestrial radio access
  • CDMA2000 Code Division Multiple Access 2000
  • TDMA may be implemented with radio technologies such as global system for mobile communications (GSM) / general packet radio service (GPRS) / enhanced data rates for GSM evolution (EDGE).
  • OFDMA can be implemented with wireless technologies such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and Evolved UTRA (E-UTRA).
  • IEEE 802.16m is an evolution of IEEE 802.16e, and provides backward compatibility with a system based on IEEE 802.16e.
  • UTRA is part of a universal mobile telecommunications system (UMTS).
  • 3rd generation partnership project (3GPP) long term evolution (LTE) is part of evolved UMTS (E-UMTS) using evolved-UMTS terrestrial radio access (E-UTRA), adopting OFDMA in the downlink and SC- in the uplink.
  • Adopt FDMA Adopt FDMA.
  • the present embodiments may be applied to a currently disclosed or commercialized wireless access technology, or may be applied to a wireless access technology currently being developed or to be developed in the future.
  • the terminal in the present specification is a comprehensive concept meaning a device including a wireless communication module that performs communication with a base station in a wireless communication system, WCDMA, LTE, NR, HSPA and IMT-2020 (5G or New Radio), etc. It should be interpreted as a concept including all of User Equipment (UE), Mobile Station (MS) in GSM, User Terminal (UT), Subscriber Station (SS), and wireless device.
  • the terminal may be a user portable device such as a smart phone depending on the type of use, in the V2X communication system may mean a vehicle, a device including a wireless communication module in the vehicle, and the like.
  • a machine type communication system it may mean an MTC terminal equipped with a communication module, an M2M terminal, a URLLC terminal, etc. to perform machine type communication.
  • the base station or cell in the present specification refers to an end that communicates with a terminal in terms of a network, Node-B (Node-B), evolved Node-B (eNB), gNode-B (gNB), Low Power Node (LPN), Sector, site, various types of antennas, BTS (Base Transceiver System), access point, access point (e.g., transmission point, reception point, transmission / reception point), relay node (Relay Node) ), Mega cell, macro cell, micro cell, pico cell, femto cell, remote radio head (RRH), radio unit (RU), and small cell (small cell).
  • the cell may mean to include a bandwidth part (BWP) in the frequency domain.
  • the serving cell may mean the Activation BWP of the terminal.
  • the base station can be interpreted in two ways. 1) a device that provides a mega cell, a macro cell, a micro cell, a pico cell, a femto cell, or a small cell in relation to the wireless area, or 2) the wireless area itself. In 1), all devices that provide a predetermined wireless area are controlled by the same entity or interact to configure the wireless area in a collaborative manner. Points, transmission / reception points, transmission points, reception points, and the like, according to a configuration method of a wireless area, are examples of a base station. In 2), the radio area itself, which receives or transmits a signal from the viewpoint of the user terminal or the neighboring base station, may be directed to the base station.
  • a cell is a component carrier having a coverage of a signal transmitted from a transmission / reception point or a signal transmitted from a transmission / reception point, or a transmission / reception point itself. You can.
  • Uplink (Uplink, UL, or uplink) means a method of transmitting and receiving data to the base station by the terminal
  • downlink Downlink (Downlink, DL, or downlink) means a method of transmitting and receiving data to the terminal by the base station do.
  • Downlink may mean a communication or communication path from a multiple transmit and receive point to a terminal
  • uplink may mean a communication or communication path from a terminal to a multiple transmit and receive point.
  • the transmitter may be a part of multiple transmission / reception points
  • the receiver may be a part of the terminal.
  • the transmitter in the uplink, the transmitter may be a part of the terminal, and the receiver may be a part of multiple transmission / reception points.
  • control information is transmitted and received through control channels such as PDCCH (Physical Downlink Control CHannel), PUCCH (Physical Uplink Control CHannel), and PDSCH (Physical Downlink Shared CHannel), PUSCH (Physical Uplink Shared CHannel), etc.
  • the same data channel is configured to transmit and receive data.
  • a situation in which signals are transmitted and received through channels such as PUCCH, PUSCH, PDCCH, and PDSCH is also referred to as 'transmitting and receiving PUCCH, PUSCH, PDCCH and PDSCH'. do.
  • 3GPP develops 5G (5th-Generation) communication technology to meet the requirements of ITU-R's next-generation radio access technology after research on 4G (4th-Generation) communication technology. Specifically, 3GPP develops a new NR communication technology separate from LTE-A pro and 4G communication technology, which have improved LTE-Advanced technology to meet the requirements of ITU-R as a 5G communication technology. LTE-A pro and NR both refer to 5G communication technology.
  • 5G communication technology will be described with reference to NR when a specific communication technology is not specified.
  • the operating scenario in NR has defined various operating scenarios by adding considerations for satellite, automobile, and new verticals in the existing 4G LTE scenario, and has an eMBB (Enhanced Mobile Broadband) scenario and high terminal density in terms of service It is deployed in the range and supports the Massive Machine Communication (mmmTC) scenario, which requires low data rate and asynchronous connection, and the Ultra Reliability and Low Latency (URLLC) scenario, which requires high responsiveness and reliability and supports high-speed mobility. .
  • Massive Machine Communication mmmTC
  • URLLC Ultra Reliability and Low Latency
  • NR discloses a wireless communication system to which a new waveform and frame structure technology, low latency technology, ultra-high-bandwidth (mmWave) support technology, and forward compatibility technology are applied.
  • mmWave ultra-high-bandwidth
  • NR forward compatibility technology
  • FIG. 1 is a diagram briefly showing the structure of an NR system to which the present embodiment can be applied.
  • the NR system is divided into 5GC (5G Core Network) and NR-RAN parts, and NG-RAN is controlled for a user plane (SDAP / PDCP / RLC / MAC / PHY) and UE (User Equipment). It consists of gNB and ng-eNBs that provide a plane (RRC) protocol termination.
  • the gNB interconnects or the gNB and ng-eNB are interconnected via an Xn interface.
  • gNB and ng-eNB are each connected to 5GC through an NG interface.
  • the 5GC may be configured to include an access and mobility management function (AMF) in charge of a control plane such as a terminal access and mobility control function and a user plane function (UPF) in charge of a control function in user data.
  • AMF access and mobility management function
  • UPF user plane function
  • the NR includes support for frequency bands below 6 GHz (FR1, Frequency Range 1) and frequency bands above 6 GHz (FR2, Frequency Range 2).
  • gNB means a base station providing NR user plane and control plane protocol termination to the terminal
  • ng-eNB means a base station providing E-UTRA user plane and control plane protocol termination to the terminal.
  • the base station described in this specification should be understood as a meaning encompassing gNB and ng-eNB, and may be used in a sense to refer to gNB or ng-eNB separately if necessary.
  • a CP-OFDM waveform using a cyclic prefix is used for downlink transmission, and CP-OFDM or DFT-s-OFDM is used for uplink transmission.
  • OFDM technology is easy to combine with multiple input multiple output (MIMO), and has the advantage of being able to use a receiver of high complexity with high frequency efficiency.
  • the NR transmission neurology is determined based on sub-carrier spacing (sub-carrier spacing) and cyclic prefix (CP), and ⁇ value is used as an exponential value of 2 based on 15khz as shown in Table 1 below. Is changed to
  • the NR numerology can be divided into 5 types according to the subcarrier spacing. This is different from that in which the subcarrier spacing of LTE, which is one of 4G communication technologies, is fixed at 15khz. Specifically, the subcarrier interval used for data transmission in NR is 15, 30, 60, and 120 khz, and the subcarrier interval used for synchronization signal transmission is 15, 30, 12, and 240 khz. In addition, the extended CP applies only to the 60khz subcarrier spacing.
  • a frame structure in NR is defined as a frame having a length of 10 ms, which is composed of 10 subframes having the same length of 1 ms. One frame can be divided into 5 ms half frames, and each half frame includes 5 subframes. In the case of a 15khz subcarrier interval, one subframe is composed of one slot, and each slot is composed of 14 OFDM symbols.
  • FIG. 2 is a diagram for explaining a frame structure in an NR system to which the present embodiment can be applied.
  • a slot is fixedly composed of 14 OFDM symbols in the case of a normal CP, but the length in the time domain of the slot may vary according to the subcarrier interval.
  • the slot is 1 ms long and is configured to have the same length as the subframe.
  • a slot is composed of 14 OFDM symbols, but may have two slots in one subframe with a length of 0.5 ms. That is, the subframe and the frame are defined with a fixed time length, and the slot is defined by the number of symbols, so that the time length may vary according to the subcarrier interval.
  • the NR defines a basic unit of scheduling as a slot, and also introduces a mini-slot (or sub-slot or non-slot based schedule) to reduce transmission delay in a radio section. If a wide subcarrier interval is used, the transmission delay in a radio section can be reduced because the length of one slot is inversely shortened.
  • the mini-slot (or sub-slot) is for efficient support for URLLC scenarios and can be scheduled in units of 2, 4, and 7 symbols.
  • uplink and downlink resource allocation is defined as a symbol level within one slot.
  • a slot structure capable of directly transmitting HARQ ACK / NACK within a transmission slot has been defined, and this slot structure is referred to as a self-contained structure.
  • NR is designed to support a total of 256 slot formats, of which 62 slot formats are used in 3GPP Rel-15.
  • a common frame structure constituting an FDD or TDD frame is supported through a combination of various slots.
  • a slot structure in which all symbols of a slot are set to downlink a slot structure in which all symbols are set to uplink
  • a slot structure in which downlink symbols and uplink symbols are combined are supported.
  • the NR supports that data transmission is scheduled in one or more slots.
  • the base station may inform the UE whether the slot is a downlink slot, an uplink slot, or a flexible slot using a slot format indicator (SFI).
  • SFI slot format indicator
  • the base station may indicate a slot format by indicating an index of a table configured through UE-specific RRC signaling using SFI, and dynamically indicate through DCI (Downlink Control Information) or static or through RRC It can also be given quasi-statically.
  • antenna ports With regard to physical resources in the NR, antenna ports, resource grids, resource elements, resource blocks, bandwidth parts, etc. are considered. do.
  • the antenna port is defined such that a channel carrying a symbol on the antenna port can be inferred from a channel carrying another symbol on the same antenna port. If the large-scale property of a channel carrying a symbol on one antenna port can be deduced from a channel carrying a symbol on another antenna port, the two antenna ports are QC / QCL (quasi co-located or quasi co-location).
  • QC / QCL quadsi co-located or quasi co-location.
  • a wide range of characteristics includes one or more of Delay spread, Doppler spread, Frequency shift, Average received power and Received Timing.
  • FIG. 3 is a diagram for describing a resource grid supported by a radio access technology to which the present embodiment can be applied.
  • a resource grid may exist according to each neuromerging because the NR supports a plurality of neuromerging on the same carrier.
  • the resource grid may exist according to the antenna port, subcarrier spacing, and transmission direction.
  • a resource block consists of 12 subcarriers and is defined only on the frequency domain. Further, a resource element is composed of one OFDM symbol and one subcarrier. Accordingly, as shown in FIG. 3, the size of one resource block may vary according to the subcarrier interval.
  • "Point A" serving as a common reference point for a resource block grid, a common resource block, and a virtual resource block are defined.
  • FIG. 4 is a diagram for describing a bandwidth part supported by a radio access technology to which the present embodiment can be applied.
  • a terminal may be used by designating a bandwidth part (BWP) within a carrier bandwidth.
  • BWP bandwidth part
  • the bandwidth part is associated with one neurology and is composed of a subset of consecutive common resource blocks, and can be dynamically activated with time.
  • a maximum of 4 bandwidth parts are configured in the uplink and downlink, respectively, and data is transmitted and received using the bandwidth part activated at a given time.
  • the uplink and downlink bandwidth parts are independently set, and in the case of an unpaired spectrum, unnecessary frequency re-tunning is prevented between downlink and uplink operation.
  • the bandwidth part of the downlink and the uplink is set in pairs so that the center frequency can be shared.
  • a terminal accesses a base station and performs cell search and random access procedures to perform communication.
  • Cell search is a procedure in which a terminal synchronizes with a cell of a corresponding base station, obtains a physical layer cell ID, and acquires system information using a synchronization signal block (SSB) transmitted by the base station.
  • SSB synchronization signal block
  • FIG. 5 exemplarily shows a synchronization signal block in a radio access technology to which the present embodiment can be applied.
  • the SSB is composed of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) occupying 1 symbol and 127 subcarriers, and 3 OFDM symbols and a PBCH spanning 240 subcarriers, respectively.
  • PSS primary synchronization signal
  • SSS secondary synchronization signal
  • the terminal receives the SSB by monitoring the SSB in the time and frequency domain.
  • SSB can be transmitted up to 64 times in 5 ms. Multiple SSBs are transmitted with different transmission beams within 5 ms time, and the terminal performs detection by assuming that SSBs are transmitted every 20 ms period when viewed based on a specific one beam used for transmission.
  • the number of beams that can be used for SSB transmission within 5 ms time may increase as the frequency band increases. For example, up to 4 SSB beams can be transmitted below 3 GHz, and up to 8 SSBs can be transmitted using up to 8 different beams in the frequency band from 3 to 6 GHz and up to 64 in the frequency band above 6 GHz.
  • Two SSBs are included in one slot, and the starting symbol and the number of repetitions in the slot are determined according to the subcarrier interval.
  • the SSB is not transmitted at the center frequency of the carrier bandwidth, unlike the SS of the conventional LTE. That is, the SSB may be transmitted out of the center of the system band, and in the case of supporting broadband operation, a plurality of SSBs may be transmitted on the frequency domain. Accordingly, the terminal monitors the SSB using a synchronization raster, which is a candidate frequency location for monitoring the SSB.
  • the carrier raster and synchronization raster which are the center frequency location information of the channel for initial access, are newly defined in NR, and the synchronization raster has a wider frequency interval than the carrier raster, and thus supports fast SSB search of the UE. You can.
  • the UE may acquire MIB through the PBCH of the SSB.
  • the MIB Master Information Block
  • the MIB includes minimum information for the UE to receive the remaining system information (RMSI, Remaining Minimum System Information) broadcast by the network.
  • RMSI Remaining Minimum System Information
  • PBCH is information on the location of the first DM-RS symbol on the time domain, information for the UE to monitor SIB1 (for example, SIB1 neuromerging information, information related to SIB1 CORESET, search space information, PDCCH Related parameter information, etc.), offset information between the common resource block and the SSB (the position of the absolute SSB in the carrier is transmitted through SIB1), and the like.
  • the SIB1 pneumatic information is equally applied to some messages used in the random access procedure for accessing the base station after the terminal completes the cell search procedure.
  • pneumatic information of SIB1 may be applied to at least one of messages 1 to 4 for a random access procedure.
  • the aforementioned RMSI may mean System Information Block 1 (SIB1), and SIB1 is broadcast periodically (ex, 160 ms) in a cell.
  • SIB1 includes information necessary for the UE to perform the initial random access procedure, and is periodically transmitted through the PDSCH.
  • the UE In order to receive SIB1, the UE must receive pneumatic information used for transmission of SIB1 and control resource set (CORESET) information used for scheduling of SIB1 through PBCH.
  • CORESET control resource set
  • the UE checks scheduling information for SIB1 using SI-RNTI in CORESET, and acquires SIB1 on the PDSCH according to the scheduling information.
  • SIBs other than SIB1 may be periodically transmitted or may be transmitted according to a terminal's request.
  • FIG. 6 is a diagram for explaining a random access procedure in a radio access technology to which the present embodiment can be applied.
  • the UE transmits a random access preamble for random access to the base station.
  • the random access preamble is transmitted through PRACH.
  • the random access preamble is transmitted to the base station through PRACH composed of continuous radio resources in a specific slot that is periodically repeated.
  • a contention-based random access procedure is performed when the UE initially accesses a cell
  • a non-competition-based random access procedure is performed when random access is performed for beam failure recovery (BFR).
  • BFR beam failure recovery
  • the terminal receives a random access response to the transmitted random access preamble.
  • the random access response may include a random access preamble identifier (ID), UL grant (uplink radio resource), temporary C-RNTI (Temporary Cell-Radio Network Temporary Identifier) and TAC (Time Alignment Command). Since one random access response may include random access response information for one or more terminals, a random access preamble identifier may be included to inform which terminal the included UL Grant, temporary C-RNTI, and TAC are valid.
  • the random access preamble identifier may be an identifier for the random access preamble received by the base station.
  • the TAC may be included as information for the UE to adjust uplink synchronization.
  • the random access response may be indicated by a random access identifier on the PDCCH, that is, a Random Access-Radio Network Temporary Identifier (RA-RNTI).
  • RA-RNTI Random Access-Radio Network Temporary Identifier
  • the terminal Upon receiving a valid random access response, the terminal processes the information included in the random access response and performs scheduled transmission to the base station. For example, the terminal applies TAC and stores a temporary C-RNTI. In addition, by using UL Grant, data stored in the buffer of the terminal or newly generated data is transmitted to the base station. In this case, information capable of identifying the terminal should be included.
  • the terminal receives a downlink message for contention resolution.
  • the downlink control channel in the NR is transmitted in a control resource set (CORESET) having a length of 1 to 3 symbols, and transmits uplink / downlink scheduling information, slot format index (SFI), and transmit power control (TPC) information.
  • CORESET control resource set
  • SFI slot format index
  • TPC transmit power control
  • CORESET Control Resource Set
  • the UE may decode the control channel candidate using one or more search spaces in the CORESET time-frequency resource.
  • QCL Quad CoLocation
  • CORESET may exist in various forms within a carrier bandwidth within one slot, and CORESET may consist of up to 3 OFDM symbols in a time domain.
  • CORESET is defined as a multiple of 6 resource blocks from the frequency domain to the carrier bandwidth.
  • the first CORESET is indicated through the MIB as part of the initial bandwidth part configuration to receive additional configuration information and system information from the network.
  • the UE may configure by receiving one or more CORESET information through RRC signaling.
  • frequency, frame, subframe, resource, resource block, region, band, subband, control channel, data channel, synchronization signal, various reference signals, various signals or various messages related to NR (New Radio) can be interpreted as meaning used in the past or present or various meanings used in the future.
  • a NB-IoT (NarrowBand Internet of Things) terminal or an IoT terminal means a terminal supporting wireless access for cellular IoT.
  • the objectives of the NB-IoT technology include improved indoor coverage, support for large-scale low-speed terminals, low sensitivity, ultra-low-cost terminal costs, low power consumption, and optimized network architecture.
  • the technical idea may be applied not only to communication between a terminal and a base station, but also to communication between terminals (Device to Device), side link communication (Sidelink), and vehicle communication (V2X).
  • it can also be applied to communication between terminals in a next-generation radio access technology, and terms such as a signal and a channel of the present specification can be variously modified and applied according to the type of communication between terminals.
  • PSS and SSS may be changed and applied to primary D2D Synchronization Signal (PSSS) and Secondary D2D Synchronization Signal (SSSS) in communication between terminals.
  • PSSS primary D2D Synchronization Signal
  • SSSS Secondary D2D Synchronization Signal
  • the channel for transmitting broadcast information such as PBCH described above is changed to PSBCH
  • the channel for transmitting data in the sidelink such as PUSCH and PDSCH is changed to PSSCH
  • the channel for transmitting control information such as PDCCH and PUCCH is changed to PSCCH.
  • a discovery signal is required in communication between terminals, which is transmitted and received through PSDCH.
  • PSDCH Physical Downlink Control Channel
  • the technical idea will be described based on exemplary communication between the terminal and the base station, but the base station node may be replaced with another terminal as necessary to apply the technical idea.
  • the NR recently conducted in 3GPP has been designed to satisfy various QoS requirements required for each segmented and specific usage scenario as well as an improved data rate compared to LTE.
  • enhancement mobile BroadBand eMBB
  • massive MTC mMTC
  • Ultra Reliable and Low Latency Communications URLLC
  • URLLC Ultra Reliable and Low Latency Communications
  • radio resource units based on different numerology eg subcarrier spacing, subframe, TTI, etc.
  • numerology eg subcarrier spacing, subframe, TTI, etc.
  • NR defines a subframe as a type of time domain structure.
  • SCS Sub-Carrier Spacing
  • the subframe of NR is an absolute reference time duration, and slots and mini-slots may be defined as time units based on actual uplink / downlink data scheduling.
  • an arbitrary slot is composed of 14 symbols.
  • all symbols may be used for DL transmission, or all symbols may be used for UL transmission, or may be used in the form of DL portion + (gap) + UL portion depending on the transmission direction of the corresponding slot. have.
  • a mini-slot is defined consisting of fewer symbols than the aforementioned slots.
  • a short-length time-domain scheduling interval for transmitting / receiving mini-slot-based uplink / downlink data may be set, or a long length time-domain scheduling interval for transmitting / receiving uplink / downlink data through slot aggregation may be configured. have.
  • numerology having different SCS values in one NR carrier can be multiplexed and supported by TDM and / or FDM. Accordingly, a method of scheduling data according to latency requirements based on a slot (or mini-slot) length defined for each numerology is also considered. For example, when the SCS is 60 kHz, the length of the symbol is reduced to about 1/4 compared to the case of the SCS 15 kHz, so if one slot is composed of 14 OFDM symbols, the corresponding 15 kHz based slot length is 1 ms. On the other hand, the slot length based on 60 kHz is reduced to about 0.25 ms.
  • a packet overlapping transmission technique can be provided as one of techniques for URLLC service support.
  • redundant transmission is configured for one radio bearer by RRC
  • one secondary RLC entity and one secondary logical channel may be added to the radio bearer to process duplicate PDCP PDUs.
  • Duplicate transmission in a PDCP entity consists of submitting the same PDCP PDUs twice (once to the primary RLC entity and a second time to the secondary RLC entity). Packet overlapping transmission can be processed with two independent transmission paths, thereby increasing data transmission reliability and reducing delay.
  • the original PDCP PDU and the duplicated duplicate transmission PDCP PDU are not transmitted on the same carrier.
  • Two different logical channels may be included in the same MAC entity (CA situation) or different MAC entities (DC situation).
  • CA the logical channel mapping restriction operation is performed in the MAC entity so that the logical channel carrying the original PDCP PDUs and the logical channel carrying the PDCP PDUs for redundant transmission are not transmitted on the same carrier.
  • the PDCP entity may instruct the other RLC entity to discard the corresponding PDCP PDU.
  • the RRC When configuring redundant transmission for one DRB, the RRC sets an initial state (activated or deactivated). After configuring the redundant transmission, the status of the redundant transmission can be dynamically controlled through MAC CE. In the DC situation, the terminal applies the MAC CE command regardless of MCG or SCG.
  • the conventional packet transmission technology was provided through two independent RLC entities and logical channels.
  • data duplication transmission through two or more independent transmission paths may provide better reliability and low latency.
  • the technique of redundant data transmission through two or more independent transmission paths is not provided, and the redundant transmission technique using two independent transmission paths and the redundant transmission technique through more than two transmission paths are the overhead of the wireless network. It needs to be provided more dynamically in consideration of the like.
  • the present disclosure provides a data duplication transmission technology capable of satisfying URLLC requirements while minimizing an increase in the overhead of a wireless network by dynamically controlling it in the case where data is duplicated by configuring more than two transmission paths as described above. I want to.
  • the present invention will be described below based on NR. However, this is only for convenience of description, and the present disclosure may be applied even when an unlicensed band is used in LTE or any radio access technology, and this is also included in the scope of the present disclosure. Meanwhile, the present disclosure may also be applied to a dual connectivity (DC) or multi-RAT DC (MR-DC) scenario. For example, it can be used in one or more of the following environments:
  • NGEN-DC NG-RAN E-UTRA-NR Dual Connectivity
  • NE-DC NR-E-UTRA Dual Connectivity
  • NN-DC NR-NR Dual Connectivity
  • the embodiments described in the present invention may include the content of the information elements and procedures specified in TS 38.331, which is NR RRC standard or TS 38.323, which is NR PDCP standard. Even if the definition of the relevant information element and the related procedure are not included in this specification, the contents specified in the standard can be used in connection with this embodiment or covered by the scope of rights.
  • the embodiments described below may be used when data is duplicated through two or more paths in one cell group (CG) (CA situation).
  • CG cell group
  • MCG master cell group
  • SCG secondary cell group
  • MC Multi Connectivity, MC
  • it can be used when data is transmitted over two or more paths by a combination of CA redundant transmission and DC / MC redundant transmission.
  • it has two transmission paths through CA redundant transmission in one MCG, and one SCG has one transmission path, so it can also be used when data is duplicated through a total of three transmission paths.
  • a UE may be located in two or more overlapping cells or two or more base station coverage.
  • redundant data transmission over two or more independent transmission paths can provide better reliability and low latency.
  • the radio quality due to blockage or the like becomes unstable in a mobile station or a cell using a high frequency, it may be necessary to use two or more independent transmission paths.
  • using two or more independent transmission paths degrades resource efficiency. Therefore, in a state in which redundant transmission using two or more independent transmission paths is configured in a terminal, it is desirable to select and use a redundant transmission path efficiently.
  • NR technology has not disclosed a technology to support it. That is, when configuring redundant transmission for one DRB, the RRC sets an initial state (activated or deactivated). The base station indicates to the terminal the initial state (or state of uplink redundancy) of redundant transmission through one information element (pdcp-Duplication) included in the PDCP configuration information. If it is set to True, duplicate transmission is activated. Otherwise it is disabled.
  • pdcp-Duplication information element
  • the transmission path in the present specification means a path in which data is transmitted from a PDCP entity to a specific cell through an RLC entity, a MAC entity, and a PHY entity.
  • RLC entities to which PDCP PDUs are to be transmitted may be selected differently, and described as different transmission paths.
  • the MAC and PHY entities and the cell of the wireless network are different, it can be described as a different transmission path. That is, in order to duplicate the same data, when the RLC entity to which the PDCP PDU is submitted is different, the concept of different transmission paths will be described.
  • FIG. 8 is a diagram for describing a terminal operation according to an embodiment.
  • a terminal processes duplicate transmission for a radio bearer by being linked to one Packet Data Convergence Protocol (PDCP) entity based on configuration information for configuring duplicate transmission of data received from a base station.
  • PDCP Packet Data Convergence Protocol
  • a step of configuring a plurality of Radio Link Control (RLC) entities used to perform the operation may be performed (S810).
  • RLC Radio Link Control
  • the terminal may receive configuration information transmitted by the base station in order to configure the data duplication transmission function in the terminal.
  • the configuration information may include information necessary to configure a plurality of RLC entities for processing duplicate transmission to the radio bearer.
  • the configuration information may include RLC index information allocated to each RLC entity to distinguish a plurality of RLC entities.
  • the RLC index information is identification information for distinguishing each RLC entity and may be configured as an RLC ID.
  • the configuration information may include information indicating an initial activation state for each of the plurality of RLC entities.
  • the terminal configures a plurality of RLC entities based on the configuration information.
  • each of the plurality of configured RLC entities is configured to be activated or deactivated in a state indicated in the initial activation state.
  • the plurality of RLC entities may include one primary RLC entity configured to transmit the PDCP control PDU of the radio bearer.
  • the primary RLC entity is a specific RLC entity configured to transmit the PDCP control PDU, and when duplicate transmission is disabled, a PDCP PDU including the PDCP control PDU may be delivered through the primary RLC entity.
  • the primary RLC entity is an arbitrary term and there is no limitation on the term.
  • the primary RLC entity may always be set to the activated state.
  • the primary RLC entity may be configured as an activated state. Thereafter, the primary RLC entity is not converted to an inactive state. That is, even though the primary RLC entity is instructed to be inactive by the MAC CE transmitted by the base station, it may not be changed to inactive.
  • the primary RLC entity may transmit the PDCP control PDU even if it is indicated as inactive by MAC CE.
  • the primary RLC entity may be configured as an RLC entity that satisfies any one of the smallest cell group index value, the smallest logical channel ID, and the smallest RLC entity index value among the activated RLC entities. That is, the primary RLC object may be set as an RLC object that satisfies a preset condition among RLC objects configured in an activated state rather than setting a specific fixed RLC object among a plurality of RLC objects. For example, among the RLC entities configured to be activated by configuration information or MAC CE, the RLC entity to which the smallest cell group index value is assigned can be set as the primary RLC entity and transmit the PDCP control PDU.
  • the RLC entity assigned with the smallest logical channel ID value among the RLC entities configured to be activated by configuration information or MAC CE may be configured as the primary RLC entity and transmit the PDCP control PDU.
  • the RLC entity assigned the smallest RLC entity index value among the RLC entities configured to be activated by configuration information or MAC CE may be configured as the primary RLC entity and transmit the PDCP control PDU.
  • the preset condition may be configured by the base station or may be configured in the terminal in advance, and may be variously set, such as the largest cell group index value, the largest logical channel ID value, or the largest RLC entity index value. There are no restrictions on the preset conditions.
  • the terminal may perform a step of receiving a MAC control element (MAC Control element) including the indication information indicating the activation state change for the plurality of RLC entities (S820).
  • MAC Control element MAC Control element
  • the UE may receive a MAC CE including information indicating activation or deactivation for each of a plurality of RLC entities from the base station.
  • the MAC CE can be received after a plurality of RLC entities are configured in the terminal.
  • the MAC control element may include indication information in the form of a bitmap indicating the activation state of each of a plurality of RLC entities associated with each radio bearer.
  • the bitmap may be composed of only bits for the remaining RLC entities except for one primary RLC entity configured to transmit the PDCP control PDU of the radio bearer among the plurality of RLC entities.
  • FIG. 9 is a diagram illustrating a MAC CE including indication information according to an embodiment.
  • indication information indicating an activation state of the RLC entities for a total of eight radio bearers may be included in the MAC CE.
  • the bit described as R0X may mean RLC entity activation indication information for radio bearer 0. That is, R00 includes bit information indicating whether the RLC entity to which the RLC entity index 0 of the radio bearer 0 is allocated is activated. If the R00 value is indicated as 0, the RLC entity to which the RLC entity index 0 of the radio bearer 0 is assigned indicates an inactive state. Similarly, when the R00 value is indicated as 1, the RLC entity to which the RLC entity index 0 of the radio bearer 0 is assigned indicates the activation state.
  • the activation or deactivation state according to the bit value may be set opposite to that described above. That is, in the case of 0, the activation state may be indicated, and in the case of 1, the inactive state may be indicated. Alternatively, if 0, it may indicate that the current activation state is not changed, and if 1, the current activation state may be changed to another state. The opposite can also be applied.
  • the last 0 in R00 may mean the order of the index value of the low or high index rather than the index of the RLC entity. That is, in the case of R01, when four RLC objects are configured for radio bearer 0, rather than indicating RLC object index 1, it indicates the second RLC object according to the ascending or descending order of the index values excluding the primary RLC object. You can. For example, when the RLC object index is assigned to 0, 1, 2, 3, and the index 0 is set as the primary RLC object, R00 indicates RLC object index 1, R01 indicates RLC object index 2, R02 may indicate RLC entity index 3.
  • bitmap information may be configured only with bits indicating the activation state of the RLC entity except for the primary RLC entity that is always configured with the activation status. Specifically, when 4 RLC entities are configured for 8 radio bearers, 1 RLC entity is set as a primary RLC entity, so the activation status of the remaining 3 RLC entities is performed using 3 bits for each radio bearer. Can instruct.
  • the terminal may perform the step of changing the RLC entity indicated as the activated state to the activated state by the indication information (S830).
  • the terminal may change the status of the individual RLC entity to an activated or deactivated state.
  • the transmission path is changed because redundant transmission data is transmitted through the active RLC object.
  • the UE may perform the step of transmitting data repeatedly using the activated RLC entity (S840). For example, when four RLC entities are configured, two RLC entities may be activated through MAC CE, and data may be repeatedly transmitted through two transmission paths. Subsequently, if all four RLC entities are changed to an active state by MAC CE, the transmission path may be extended by transmitting duplicate transmission data through the four RLC entities. Similarly, when duplicate transmission is performed through RLC object indexes 1 and 2, the transmission paths can be changed to 0 and 3 when RLC object indexes 0 and 3 are activated through MAC CE and 1 and 2 are deactivated. have.
  • the base station can dynamically control the transmission path.
  • FIG. 10 is a diagram for explaining the operation of a base station according to an embodiment.
  • the base station is connected to a single PDCP (Packet Data Convergence Protocol) entity to configure the configuration information for configuring a plurality of radio link control (RLC) entity used to process the redundant transmission to the radio bearer
  • PDCP Packet Data Convergence Protocol
  • RLC radio link control
  • the configuration information may include information necessary to configure a plurality of RLC entities for processing duplicate transmission to the radio bearer.
  • the configuration information may include RLC index information allocated to each RLC entity to distinguish a plurality of RLC entities.
  • the RLC index information is identification information for distinguishing each RLC entity and may be configured as an RLC ID.
  • the configuration information may include information indicating an initial activation state for each of the plurality of RLC entities.
  • the terminal configures a plurality of RLC entities based on the configuration information.
  • each of the plurality of configured RLC entities is configured to be activated or deactivated in a state indicated in the initial activation state.
  • the plurality of RLC entities may include one primary RLC entity configured to transmit the PDCP control PDU of the radio bearer.
  • the primary RLC entity may always be set to the activated state.
  • the primary RLC entity may be configured as an activated state. Thereafter, the primary RLC entity is not converted to an inactive state. That is, even though the primary RLC entity is instructed to be inactive by the MAC CE transmitted by the base station, it may not be changed to inactive.
  • the primary RLC entity may transmit the PDCP control PDU even if it is indicated as inactive by MAC CE.
  • the primary RLC entity may be configured as an RLC entity that satisfies any one of the smallest cell group index value, the smallest logical channel ID, and the smallest RLC entity index value among the activated RLC entities. That is, the primary RLC object may be set as an RLC object that satisfies a preset condition among RLC objects configured in an activated state rather than setting a specific fixed RLC object among a plurality of RLC objects.
  • the preset condition may be configured by the base station or may be configured in the terminal in advance, and may be variously set, such as the largest cell group index value, the largest logical channel ID value, or the largest RLC entity index value. There are no restrictions on the preset conditions.
  • the base station may perform the step of transmitting the indication information indicating the activation state change for the plurality of RLC entities to the terminal (S1020).
  • the MAC control element may include indication information in the form of a bitmap indicating the activation state of each of a plurality of RLC entities associated with each radio bearer.
  • the bitmap may be composed of only bits for the remaining RLC entities except for one primary RLC entity configured to transmit the PDCP control PDU of the radio bearer among the plurality of RLC entities.
  • MAC CE may be transmitted after a plurality of RLC entities are configured in the terminal.
  • RLC entity is set as a primary RLC entity, so the 3 remaining RLC entities are used by using 3 bits for each radio bearer. It can indicate the activation state of.
  • the base station may perform a step of receiving data that is redundantly transmitted through the RLC entity activated by the indication information (S1030).
  • the terminal may change the status of the individual RLC entity to an activated or deactivated state. For example, when four RLC entities are configured, two RLC entities may be activated through MAC CE to receive duplicate data through two transmission paths. Subsequently, if all four RLC entities are changed to an active state by MAC CE, duplicate transmission data may be received through the four RLC entities.
  • the base station can dynamically control the transmission path.
  • First embodiment Method for instructing activation / deactivation of a redundant transmission path through RRC signaling
  • the base station may transmit information (1 bit) for indicating activation / deactivation for each transmission path for redundant transmission to the terminal. For example, when a base station configures two or more independent transmission paths (RLC entities) for a specific radio bearer in a terminal through an RRC message, information for indicating activation / deactivation for each transmission path (BOOLEAN, True) : Enabled, False: Disabled). That is, the configuration information transmitted from the base station to the terminal may include information indicating activation / deactivation of each RLC entity.
  • RLC entities independent transmission paths
  • information indicating the initial state of redundant transmission for a radio bearer (pdcp-Duplication) is set to active, and information indicating the initial state of redundant transmission for a transmission path configured for the radio bearer is activated.
  • pdcp-Duplication information indicating the initial state of redundant transmission for a transmission path configured for the radio bearer is activated.
  • redundant transmission through the transmission path set to activation is activated for the radio bearer. That is, when redundant transmission for a specific radio bearer is activated, redundant transmission may be performed through the activated transmission path.
  • the information for activating the transmission path may be information for indicating a transmission path through which the UE that has received the RRC message will perform the redundant transmission for the radio bearer in which the redundant transmission is activated.
  • the terminal will transmit the corresponding redundant transmission path. Through this, a data duplication transmission operation may be performed.
  • the redundant transmission through the transmission path set to activation for the radio bearer can be activated.
  • the information for activating the transmission path may be information for indicating a transmission path through which the UE that has received the RRC message will perform the redundant transmission for the radio bearer in which the redundant transmission is activated.
  • the terminal will transmit the corresponding redundant transmission path. Through this, it is possible to perform a data duplication transmission operation.
  • the base station performs measurement reporting of cells / cells / cell groups associated with a corresponding transmission path, characteristics per flow / wireless bearer (eg QoS parameters, for example, 5QI, QFI), traffic type, cell load, amount of transmitted data, buffered data, etc. Based on this, four independent transmission paths for a specific radio bearer can be configured in the terminal. For example, the base station may want to use only two independent transmission paths (MCG1, SCG1) based on the above-described information to be used for data duplication transmission.
  • MCG1, SCG1 independent transmission paths
  • the base station can set and activate / deactivate bits of the corresponding transmission path for MCG1 and SCG1, respectively, and set the activation / deactivation bit of the corresponding transmission path to False for SCG3 and SCG4, respectively, to indicate to the terminal.
  • the base station sets the activation / deactivation bit of the corresponding transmission path to True for MCG1 and SCG1, and the activation / deactivation bit of the corresponding transmission path to False for SCG3 and SCG4, respectively. I can order.
  • the transmission path providing the redundant transmission needs to be indicated in connection with the PDCP entity performing the redundant transmission for the PDCP PDUs.
  • the PDCP entity is linked to the corresponding DRB identification information (drb-Identity) and PDCP configuration information (pdcp-Config) through the DRB additional information (DRB-ToAddMod) included in the RRC message, and the corresponding PDCP entity has two or more transmission paths.
  • the RLC bearer configuration information RLC-BearerConfig
  • the PDCP entity of the terminal can know the transmission path associated with the logicalChannelIdentity associated with the corresponding drb-Identity.
  • index (ID) information for distinguishing and identifying the corresponding transmission path (RLC entity) may be included in the RRC message.
  • ID information for distinguishing and identifying the corresponding transmission path (RLC entity)
  • RLC entity index information for distinguishing and identifying the corresponding transmission path (RLC entity)
  • the information element may be information for indicating a transmission path (RLC entity) to which the UE that has received the RRC message performs redundant transmission for a radio bearer for which duplicate transmission is activated.
  • the information element may be used to indicate / change / switch duplicate activation for a radio bearer through MAC CE signaling described below.
  • the base station wants to configure two or more redundant transmission paths in the terminal, it may have various redundant transmission path combinations according to network deployment. For example, when three redundant transmission paths are configured in the terminal, various configurations are possible as follows.
  • three redundant transmission paths can be configured only in one cell group (MCG or master node) based on CA.
  • Third, one redundant transmission path may be configured in one cell group (MCG or master node), and two redundant transmission paths may be configured based on CA in another cell group (SCG1 or secondary node).
  • one redundant transmission path is configured in one cell group (MCG or master node), and one redundant transmission path is configured in another cell group (SCG1 or secondary node 1), and another cell group (SCG2 or secondary) is configured.
  • node 2 one redundant transmission path can be configured.
  • the base station In order to avoid the complexity due to the possibility of various combinations, if the base station wants to configure two or more redundant transmission paths in the terminal, the base station needs to easily identify and use possible duplicate transmission paths of the corresponding terminal. To this end, it is necessary to additionally define redundant transmission path (RLC entity) index (ID) information to identify the duplicate transmission path. In addition, when additionally defining index information, identification of each transmission path to be applied when activating redundant transmission through MAC CE can be easily performed. According to the conventional RRC standard, the corresponding duplicate transmission path (RLC entity) has been identified through a logical channel identifier (LCID). However, the logical channel identifier has a large number of bits.
  • the index information may be included as one information element in RLC bearer configuration information (RLC-BearerConfig).
  • RLC bearerConfig included in cell group configuration information (CellGroupConfig) classifies RLC entities through logical channel identification information, which is a sub information element, and each logical channel carrying duplicate data is transmitted on the same carrier.
  • the transmission path (RLC entity) index linked to the cell group identification information included in the corresponding cell group configuration information and logical channel identification information included in the corresponding RLC bearer configuration information facilitates the RLC entity to be activated / deactivated for redundant transmission. Can be identified.
  • index information may be added and included as one information element in the cell group information.
  • the index information is included in the PDCP configuration information, and information (pdcp-Duplication) indicating the initial state of duplicate transmission for the corresponding radio bearer is set to active, and a transmission path (RLC entity) for performing the corresponding duplicate transmission is If included, duplicate transmission may be performed through a corresponding duplicate transmission path.
  • RLC entities redundant transmission paths between different base stations. For example, assuming that up to 4 redundant transmission paths (RLC entities) are configured, in the case of DC, the master node and the secondary node must determine the redundant transmission paths for a specific radio bearer.
  • the master node may determine the number of transmission paths (RLC entities) to be activated for redundant transmission through different nodes.
  • the master node determines both the number of RLC entities to be activated for redundant transmission in the master node and the secondary node.
  • the master node delivers RLC entity (s) information to be activated for redundant transmission at the secondary node and / or RLC entity (s) number information to be activated for redundant transmission at the secondary node to the secondary node.
  • information on the number of RLC entities to be activated is transmitted through an SN addition message or an SN modification message.
  • the number of RLC entities to be activated may be included as an information element in the XnAP message, or may be included in a CG-ConfigInfo message, which is an inter-node RRC message included as a container in the XnAP message. Alternatively, information on the number of RLC entities to be activated may be included in any Inter-node RRC message.
  • the secondary node uses the information on the number of RLC objects to be activated to inform the master node of the RLC object (s) configuration information to be activated for redundant transmission at the secondary node and / or the number of RLC object (s) to be activated for redundant transmission at the secondary node. And the master node can instruct it to perform redundant transmission by delivering it to the terminal.
  • the index information for identifying the aforementioned redundant transmission path is the inter-node message (eg, inter-node RRC message / XnAP message / XnAP message transmitted from the master node to the secondary node) and / or the master node in the secondary node It can be included in the inter-node RRC message / XnAP message).
  • the index information is information that can uniquely identify a duplicate transmission path (RLC entity) in the terminal. Therefore, the duplicate transmission path (RLC entity) of the master node and the secondary node cannot have the same transmission path (RLC entity) index.
  • the index information and the range of index information values are shared between the master node and the secondary node through cell groups.
  • the master node only determines the RLC entity (s) to activate for redundant transmission at the master node.
  • the master node delivers RLC entity (s) information to be activated for redundant transmission in the master node configuration information and / or RLC entity (s) number information to be activated (available) for redundant transmission in the master node to the secondary node. And / or the maximum number of RLC object (s) (available) RLC object (s) / request RLC object (s) / minimum RLC object (s) requested by the master node that can be activated for redundant transmission at the secondary node. ) The number information is transmitted to the secondary node.
  • the master node transmits the aforementioned information to the secondary node through an SN addition message or an SN modification message.
  • the above-described information may be included as an information element in the corresponding XnAP message, or may be included in a CG-ConfigInfo message, which is an inter-node RRC message included as a container in the corresponding XnAP message.
  • the aforementioned information may be included in any Inter-node RRC message.
  • the secondary node uses the above-described information to determine the RLC object (s) to be activated for redundant transmission at the secondary node, and to configure the RLC object (s) to be activated for redundant transmission at the secondary node and / or to duplicate transmission at the secondary node.
  • the number of RLC entity (s) to be activated is transmitted to the master node, and the master node can be configured to perform redundant transmission by passing it to the terminal.
  • index information for identifying the above-described redundant transmission path (RLC entity) is inter-node message (eg, inter-node RRC message / XnAP message delivered from the master node to the secondary node) and / or delivered from the secondary node to the master node Inter-node RRC message / XnAP message).
  • the index information may be set to a value that uniquely identifies a duplicate transmission path (RLC entity) in the terminal.
  • the duplicate transmission path (RLC entity) of the master node and the secondary node cannot have the same transmission path (RLC entity) index.
  • the index information and the range of index information values are shared between the master node and the secondary node through cell groups. If the master node and / or the secondary node are separated into a central unit (CU) and a distribution unit (DU), index information may be included in the F1AP message.
  • CU central unit
  • DU distribution unit
  • whether to enable redundant transmission for a specific radio bearer through an RRC message may be provided through information (pdcp-Duplication) indicating an initial state of redundant transmission for a corresponding radio bearer. If two or more independent transmission paths are configured in the UE for a specific radio bearer through an RRC message, the PDCP entity performing duplicate transmission for PDCP PDUs activates duplicate transmission for PDCP PDUs to deliver the duplicate transmission delivery path to be delivered. Information needs to be directed.
  • a priority transmission path for transmitting PDCP data (PDCP data PDU or PDCP control PDU) is always activated and may be indicated.
  • PDCP data PDU or PDCP control PDU For convenience of description, when two or more RLC entities are configured for redundant transmission for one radio bearer, a path for transmitting a PDCP data PDU or a PDCP control PDU is always activated and is indicated as a priority transmission path.
  • the primary transmission path may be a primary transmission path. In the dual connectivity technology, the primary transmission path may indicate a path to transmit data when the UE has little uplink data to transmit.
  • the transmission speed can be increased by transmitting PDCP PDUs using any one of two paths (MCG: Master Cell Group, SCG: Secondary Cell Group) of the split bearer.
  • MCG Master Cell Group
  • SCG Secondary Cell Group
  • the primary transmission path in NR Rel-15 may indicate a path for transmitting a PDCP control PDU according to the introduction of redundant transmission technology.
  • the preferential transmission path may be described as a primary RLC entity described above from the perspective of the RLC entity.
  • the priority transmission path is always activated regardless of the activation of redundant transmission for the corresponding radio bearer, the RLC entity capable of transmitting PDCP data (PDCP data PDU or PDCP control PDU), the cell group to which the RLC entity belongs, and the corresponding RLC entity. It may be distinguished through one or more of the allowed serving cells (allowedServingCells) information element associated with. Data that needs to be transmitted without duplication, such as PDCP control PDU, is transmitted through the priority transmission path. Since the PDCP Control PDU does not have a Sequence Number (SN) field, it is not possible to distinguish duplicates in the receiving entity.
  • SN Sequence Number
  • the PDCP control PDU may cause confusion in application of a corresponding function when transmitting duplicates, it is possible to exclude duplicate transmissions. Therefore, the PDCP control PDU may be transmitted to an RLC entity or one RLC entity associated with a transmission path first.
  • the PDCP Control PDU does not have an SN field. Therefore, in order to perform redundant transmission, a field for distinguishing the duplicated PDCP control PDU may be additionally defined. For example, an SN field is added to the PDCP control PDU format, or one or more of the four R fields included in the conventional PDCP Control PDU format is increased from 0 to maximum value-1, and the maximum value is the same as the sequence number. It is necessary to specify and use a value that is cycled to zero.
  • the terminal (transmitted PDCP entity) Indicates the PDCP data volume as a MAC entity associated with all activated RLC entities.
  • the terminal indicates the PDCP data volume to the MAC entity associated with the corresponding RLC entity.
  • the terminal is a MAC entity associated with the remaining (activated) RLC entity (s) and indicates the PDCP data volume except for the PDCP control PDU.
  • the UE transmit PDCP entity is a MAC entity associated with the primary RLC entity and indicates the PDCP data volume.
  • the terminal is a MAC entity associated with the activated secondary RLC entity (s) and indicates the PDCP data volume except for the PDCP control PDU.
  • two or more RLC entities when configured for the corresponding radio bearer, it is activated and may indicate two primary transmission paths (primary paths and primary secondary paths) for redundant transmission of PDCP data. For example, when configuring four transmission paths for redundant transmission, it is possible to instruct two priority transmission paths with low radio quality and low cell load to perform redundant transmission through the corresponding two paths.
  • a field for indicating activation / deactivation information for each transmission path needs to be configured with a number of bits corresponding to the number of transmission paths.
  • a transmission path for example, primary secondary path or secondary path among secondary paths
  • the number of bits can be reduced.
  • the number of bits can be reduced to a log function value of 2 or less.
  • a transmission path to perform redundant transmission may be designated by default or in an initial state or preferentially among the four paths through 2 bits (00, 01, 10, 11).
  • the information indicating the initial state of the redundant transmission for the corresponding radio bearer (pdcp-Duplication) is set to active, in addition to the priority transmission path, if the default / initial / preferred redundant transmission path to be activated is included , Redundant transmission through the transmission path is activated for the radio bearer.
  • the terminal when the terminal receives a redundant activation indication for a specific radio bearer through the conventional redundant activation / deactivation MAC CE as shown in FIG. 11, in addition to the priority transmission path for the radio bearer, default / initial / priority If a redundant transmission path to be activated is configured, the terminal performs redundant transmission by enabling redundant transmission through the transmission path for the radio bearer through the redundant transmission path to be default / initial / first activated for the corresponding radio bearer.
  • the transmission path providing the redundant transmission needs to be indicated from the perspective of the PDCP entity performing the redundant transmission for the PDCP PDUs.
  • the priority transmission path or the default / initial / priority redundant transmission path information to be activated is included in the PDCP configuration information of the PDCP entity to be indicated. You can.
  • a transport path to be default / initial / prioritized may be indicated through one or more of cell group identification information, logicalChannelIdentity, and allowedServingCells associated with the RLC entity.
  • a preferred transmission path or a transmission path to be activated by default / initial / first may be determined implicitly.
  • the priority transmission path may be a cell / cell group having an index (eg, CellGroupId) for identifying the cell / cell group of the lowest index (excluding PCell in the case of cells, and MCG in the case of cell groups).
  • the default / initial / priority transmission path to be activated is a cell having an ID / index (eg, CellGroupId) to identify the cell / cell group with the lowest index, except for the priority transmission path (eg, primary path). It may be a cell group (excluding PCell in the case of a cell and MCG in the case of a cell group).
  • the priority transmission path may be a transmission path having the lowest index transmission path (RLC entity) index.
  • a transmission path to be activated by default / initial / priority may be a transmission path having a transmission path index (RLC entity) index of lowest index excluding a priority transmission path (for example, a primary path).
  • the primary transmission path or the default / initial / priority transmission path to be activated may be the last activated cell / cell group (excluding PCell in the case of a cell and MCG in the case of a cell group). .
  • the priority transmission path may be a transmission path to which a logical channel identifier (except for a logical channel identifier mapped to SRB) of the lowest index that can be mapped to the radio bearer is allocated.
  • a transmission path to be activated by default / initial / priority is assigned a logical channel identifier of the lowest index (except for a logical channel identifier mapped to SRB) that can be mapped to a corresponding radio bearer except for a priority transmission path. It can be a path.
  • a preferred transmission path or a transmission path to be activated by default / initial / first may be a transmission path to which the last activated logical channel identifier is allocated.
  • the redundant transmission path of the wireless bearer with redundant transmission enabled may be selected through the preferred transmission path according to the present embodiment or the default / initial / priority transmission path to be activated.
  • Second embodiment A method of instructing a redundant transmission path for performing redundant transmission for a radio bearer in which redundant transmission is activated through MAC CE
  • the base station may indicate activation / deactivation of redundancy through the MAC CE to the terminal.
  • the base station may include and transmit information indicating a redundant transmission path (RLC entity) for a radio bearer to activate redundancy through MAC CE. That is, the base station may transmit at least one of the information indicating the redundant transmission activation for the radio bearer and the information for indicating the redundant transmission path to the terminal through the MAC CE.
  • RLC entity redundant transmission path
  • MAC CE indicated by the base station to the terminal activates a duplicate transmission path for each transmission path.
  • Status eg 1-bit information to indicate activation / deactivation (True: enabled, False: disabled)
  • 1-bit information to indicate whether the transmission path will be used as a secondary path for redundant transmission Truee: corresponding transmission path Redundant transmission through, False: The transmission path does not duplicate transmission, or 1-bit information to instruct the RLC object included in the transmission path to be activated for duplicate transmission (True: Activate the RLC object, False : Activate the corresponding RLC object).
  • the above-described information on the entire redundant transmission path (or RLC entity) for the radio bearer included in the MAC CE may be included as bitmap information.
  • the priority transmission path (primary RLC entity to be activated) and redundant transmission paths (secondary RLC entities to be activated) are set to True (1) for each radio bearer, and the remaining transmission paths (secondary RLC entity to be disabled). Field) can be set to False (0).
  • the MAC CE is set to True (1) only for duplicate transmission paths (secondary RLC entities to be activated), not the priority transmission path (primary RLC entity to be activated) for each radio bearer, and the remaining transmission paths (secondary RLC to be disabled) Objects) and the priority transmission path (primary RLC object to be activated) may be set to False (0).
  • the MAC CE does not include a bit for a priority transmission path (a primary RLC entity to be activated) for each radio bearer, and a redundant transmission path (secondary RLC entities to be activated) rather than a priority transmission path (a primary RLC entity to be activated). For only, it is set to True (1), and the remaining transmission paths (secondary RLC entities to be deactivated) may be set to False (0). That is, bits indicating activation of a priority transmission path in bitmap information may be excluded.
  • 11 exemplarily shows a MAC CE indicating redundant transmission according to another embodiment.
  • redundant activation / deactivation MAC CE is identified by a MAC PDU subheader having an LCID 111000 value. It consists of one octet containing eight D fields.
  • the D field is defined as follows.
  • This field indicates the activation / deactivation status of PDCP replication of DRB i.
  • i is an ascending order of the DRB ID among the DRBs composed of the RCP entities associated with the PDCP replication and MAC entities.
  • the Di field is set to 1 to indicate that PDCP replication of DRB i should be activated.
  • This field indicates the activation / deactivation status of the PDCP duplication of DRB i where i is the ascending order of the DRB ID among the DRBs configured with PDCP duplication and with RLC entity (ies) associated with this MAC entity.
  • the D i field is set to one to indicate that the PDCP duplication of DRB i shall be activated.
  • the D i field is set to zero to indicate that the PDCP duplication of DRB i shall be deactivated.
  • the MAC CE shown in FIG. 11 only indicates whether or not to activate a redundant transmission function for a specific radio bearer, and does not indicate whether to activate each redundant transmission path. Accordingly, the base station may instruct the UE to transmit / reactivate the redundant transmission / reactivation path for each radio bearer through the new MAC CE that is distinguished from the duplicated activation / deactivation MAC CE of FIG. 11 having the LCID 111000 value.
  • a new MAC CE may equally include 8 D fields included in redundant transmission activation / deactivation MAC CE. Through this, it is possible to indicate the activation / deactivation status of PDCP duplication of DRB i in ascending order of DBR IDs among the DRBs for which PDCP duplication is configured.
  • the new MAC CE may be defined by including only the field indicating the redundant transmission path described below without including 8 D fields. Through this, by defining a fixed length MAC CE that does not include a D field, it is possible to efficiently operate the number of bits and to indicate the activation / deactivation transmission path (RLC entity) for each radio bearer in ascending order.
  • the new MAC CE may indicate a duplicate transmission path for PDCP duplication of DRB i in ascending order of DRB IDs among the DRBs for which PDCP duplication is configured.
  • the redundant transmission path indicates a transmission path (RLC entity) in which a redundant transmission is provided in addition to the priority transmission path when PDCP redundant transmission of a corresponding radio bearer is activated for a DRB configured with PDCP redundancy.
  • the duplicated transmission path for each wireless bearer is the cell group ID or the allowed serving cell (allowedServingCells) to which the duplicated transmission logical channel ID of the duplicated transmission RLC object associated with the PDCP object of the wireless bearer and the duplicated transmission RLC object or duplicated transmission logical channel ID belong. ).
  • the base station configures two or more redundant transmission paths in the terminal, if the maximum number of cell groups is fixed to 4 (for example, MCG, SCG1, SCG2, SCG3), each cell as shown in FIG.
  • the group ID may consist of 2 bits.
  • each logical channel ID field may be provided in 6 bits.
  • FIG. 13 exemplarily shows a MAC CE indicating a redundant transmission path according to another embodiment.
  • a new MAC CE may include 8 D fields included in a conventional redundant activation / deactivation MAC CE. Through this, it is possible to indicate the activation / deactivation status of PDCP duplication of DRB i in ascending order of DBR IDs among the DRBs for which PDCP duplication is configured.
  • the new MAC CE may be defined by including only the field indicating the redundant transmission path described below without including 8 D fields. Through this, by defining a fixed length MAC CE that does not include a D field, it is possible to efficiently operate the number of bits and to indicate the activation / deactivation transmission path (RLC entity) for each radio bearer in ascending order.
  • the new MAC CE may indicate an activation / deactivation redundancy transmission path (activation / deactivation RLC entity) for PDCP duplication of DRB i in ascending order of DRB IDs among the DRBs for which PDCP duplication is configured.
  • the redundant transmission path represents an activated / deactivated redundant transmission path (activated / deactivated RLC entity) in which redundant transmission is provided in addition to a priority transmission path when PDCP redundancy of a corresponding radio bearer is activated for a DRB configured with PDCP redundancy.
  • the MAC CE may be configured only with a bit indicating an activation state of a redundant transmission path (activated / deactivated RLC entity) in which redundant transmission is provided except for the priority transmission path.
  • a duplicate transmission path for each radio bearer may be identified by an index value for identifying a transmission path (RLC entity) for the radio bearer.
  • This is the duplicate transmission logical channel ID of the duplicate transmission RLC entity linked to the PDCP entity of the radio bearer and the cell group ID to which the duplicate transmission RLC entity or duplicate transmission logical channel ID belongs, or an index value associated with allowed serving cells (allowedServingCells). Can be linked to.
  • Each transmission path (RLC entity) is divided through information of one or more of cell group ID, logical channel ID, and allowedServingCells, and the index for the corresponding transmission path (RLC entity) is the upper layer (RRC message). It may be directed to the terminal through.
  • each transmission is performed using 4 bits in the duplicate transmission path field as shown in FIG. Paths can be distinguished.
  • the 4 bits may be used as bitmap information indicating an activation / deactivation transmission path (RLC entity) for the corresponding radio bearer.
  • RLC entity an activation / deactivation transmission path
  • each bit is activated (activated / deactivated) of the corresponding transmission path (RLC object) by ascending order of the transmission path (RLC object) index belonging to the radio bearer or by transmission path (RLC object) index belonging to the radio bearer. ).
  • the UE has a priority transmission path (eg, primary path / primary RLC entity) on the MAC CE. If set to inactive and received, it can be ignored. While the corresponding radio bearer is configured, the corresponding priority transmission path (eg, primary path / primary RLC entity) may always remain activated.
  • the primary transmission path eg, primary path / primary RLC entity
  • the UE may apply First, disable the transmission path (primary RLC entity).
  • one of the remaining transmission paths (RLC entities) received set as activation may be selected as a priority transmission path (primary RLC entity).
  • the UE may set the activation to determine the transmission path (RLC entity) having the lowest ID / index among the remaining transmission paths (RLC entity) received as the preferred transmission path (primary RLC entity).
  • the terminal is set to activation, and among the remaining transmission paths (RLC entities) received, a priority transmission path (primary RLC entity) based on rules / thresholds / conditions / criteria / decision configured by a network / base station indication. You can decide.
  • the base station is set to activation and includes information for indicating a priority transmission path (primary RLC entity) among the remaining transmission paths (RLC entity) received in the MAC CE or instructed to the terminal through a separate signaling. can do.
  • the UE may determine the transmission path (RLC entity) included in the MCG as the preferred transmission path (primary RLC entity) among the remaining transmission paths (RLC entity) received set to activation.
  • the UE may transmit data to be transmitted without duplication such as PDCP control PDU through the corresponding priority transmission path (primary RLC entity).
  • the UE is set to activation and RLC having the smallest (lowest) cell group index or smallest (lowest) logical channel ID or smallest (lowest) RLC index value among the remaining transmission paths (RLC entities) received.
  • Individuals can be selected as primary RLC individuals.
  • the base station wants to configure two or more redundant transmission paths in the terminal, if the maximum number of duplicate transmission paths is configured to 4, the remaining redundant transmissions are excluded except for the priority transmission path (primary RLC entity).
  • the path (RLC entity) field can be used to distinguish each enable / disable transmission path using 3 bits. For example, each bit is transmitted in ascending order of the transmission path (RLC object) index belonging to the radio bearer or the transmission path (RLC object) index belonging to the radio bearer except for the priority transmission path (primary RLC object). It may indicate the activation state (enable / disable) of the pathway (RLC entity).
  • each of the redundant transmission path fields is activated / deactivated using 3 bits.
  • the transmission path can be distinguished.
  • each activation / deactivation transmission path can be identified by using 2 bits in the path (RLC entity) field. For example, each bit is transmitted in ascending order of the transmission path (RLC object) index belonging to the radio bearer or the transmission path (RLC object) index belonging to the radio bearer except for the priority transmission path (primary RLC object). It may indicate the activation state (enable / disable) of the pathway (RLC entity).
  • each of the redundant transmission path fields is activated / deactivated using 2 bits.
  • the transmission path can be distinguished.
  • a path (RLC entity) field can be used to distinguish activation / deactivation of a corresponding transmission path using 1 bit.
  • the priority transmission path is always activated, and the UE can transmit the PDCP data PDU or PDCP control PDU through the priority transmission path.
  • the base station may not instruct the MAC CE to deactivate the priority transmission path through the aforementioned MAC CE, and the UE may PDPD data through the priority transmission path.
  • PDU or PDCP control PDU can be transmitted.
  • the PDCP control PDU transmission through the priority transmission path is always activated so that the UE can transmit the PDCP control PDU through the priority transmission path.
  • the base station may instruct the priority transmission path to disable PDCP data PDU transmission like the other redundant transmission paths.
  • the PDCP control PDU transmission is always transmitted through an activated priority transmission path, but for user data requiring reliable transmission, the base station can dynamically set a duplicate transmission path in the terminal.
  • the base station may initially designate a priority transmission path through RRC signaling. However, the base station can deactivate the priority transmission path through MAC CE. When the priority transmission path is deactivated through the MAC CE, the UE can select one of the activated transmission paths and transmit the PDCP control PDU.
  • a priority transmission path may not be configured through RRC signaling.
  • the UE may transmit a PDCP control PDU by selecting one of the transmission paths indicated to be activated by using one of the above-mentioned preferred transmission path designation methods. Thereafter, when the transmission path for transmitting the PDCP control PDU through the MAC CE is deactivated, the UE may select one of the transmission paths indicated for activation through the MAC CE and transmit the PDCP control PDU again using one of the aforementioned methods.
  • the UE may use one of the following methods to designate a priority transmission path.
  • the primary RLC entity does not perform duplicate transmission on the PDCP data PDU for the radio bearer.
  • the UE can transmit the corresponding PDCP control PDU through the deactivated primary RLC entity.
  • the primary RLC entity does not perform duplicate transmission on the PDCP data PDU for the radio bearer.
  • the PDCP control PDU may be transmitted through one RLC entity among activated RLC entities.
  • the UE may select an RLC entity having the smallest index value among RLC entities activated for PDCP control PDU transmission. For example, an RLC entity having the smallest cell group index or smallest logical channel ID or smallest RLC index value can be selected.
  • the terminal may randomly select one RLC entity among the activated RLC entities.
  • the UE may transmit the corresponding PDCP control PDU through one RLC entity among the activated RLC entities.
  • the UE may select an RLC entity having the smallest index value among RLC entities activated for PDCP control PDU transmission.
  • the UE may select an RLC entity having the smallest cell group index or smallest logical channel ID or smallest index value.
  • the terminal may arbitrarily select one RLC entity.
  • the redundant transmission path field may be provided in an order (for example, in ascending order) on the Di field only for radio bearers in which the Di field is set to 1 (duplication is enabled). That is, MAC CE may have a variable length. MAC CE is octet-aligned or byte-aligned. If there is a bit remaining in the last octet, it may be filled with padding bits.
  • FIG. 14 is a diagram illustrating an exemplary MAC CE indicating a redundant transmission path according to another embodiment.
  • FIG. 14 a case is shown in which only the redundant transmission path for the radio bearer activated for the above-described 2.2 embodiment is included.
  • only the radio bearers may include the redundant transmission paths in ascending order.
  • description will be made based on the 2.2 embodiment, but configuring the MAC CE to include only the redundant transmission path of the active radio bearer for any embodiment is also included in the scope of the present embodiment.
  • the base station may instruct the UE to transmit / reactivate the redundant transmission / reactivation path for each radio bearer through a new MAC CE that is distinguished from the duplicated activation / deactivation MAC CE of FIG. 11 having the LCID 111000 value.
  • the new MAC CE may include 8 D fields included in the conventional redundant transmission activation / deactivation MAC CE. Through this, it is possible to indicate the activation / deactivation state of the PDCP redundant transmission of DRB i in ascending order of DBR IDs among the DRBs configured for PDCP redundant transmission.
  • the new MAC CE may be defined by including only the field indicating the redundant transmission path described below without including 8 D fields. Through this, by defining a fixed length MAC CE that does not include the D field, it is possible to efficiently operate the number of bits, and to indicate the activation / deactivation transmission path (RLC entity) for each radio bearer in ascending order of the DRB ID.
  • the new MAC CE may indicate the activation state of the redundant transmission path for the PDCP redundant transmission of DRB i in ascending order of DRB IDs among the DRBs for which PDCP redundant transmission is configured. Through this, it is possible to indicate a transmission path for performing duplicate transmission for each radio bearer.
  • the redundant transmission path indicates a transmission path (RLC entity) in which a redundant transmission is provided in addition to the priority transmission path when PDCP redundant transmission of a corresponding radio bearer is activated for a DRB configured with PDCP redundant transmission. This may be configured with information for each radio bearer, or may be configured with common information for a radio bearer with redundant transmission activated.
  • one MAC CE may include activation status information of a duplicate transmission path (RLC entity) for one radio bearer.
  • RLC entity a duplicate transmission path
  • DRB identification information may be included in the MAC CE.
  • the new MAC CE may include activation status information of the transmission path (RLC entity) in ascending order of the cell group index or logical channel ID or RLC index in ascending order of the radio bearer ID for all radio bearers.
  • the redundant transmission path may be configured with information for each radio bearer, or may be configured with common information for a radio bearer with redundant transmission activated.
  • 15 exemplarily shows a MAC CE indicating redundant transmission according to another embodiment.
  • MAC CE may indicate a case in which common information is configured for a radio bearer in which redundant transmission is activated.
  • the base station configures two or more redundant transmission paths in the terminal, the maximum number of cell groups that can be configured in the terminal and the maximum duplicated transmission path for each cell group are fixed so that the terminal and the base station can identify the corresponding duplicate transmission path. .
  • the UE may be configured with up to 8 duplicate transmission paths.
  • Each fixed redundant transmission path may be configured in order. For example, if the duplicate transmission path is CG ascending, LCID ascending, MCG0 low LCID, MCG0 high LCID, SCG1 low LCID, SCG1 high LCID, SCG2 low LCID, SCG2 high LCID, SCG3 low LCID, SCG3 high LCID is identified.
  • Ascending order can be configured by assigning to MAC CE as shown in FIG. 15.
  • the UE may be configured with up to 4 duplicate transmission paths.
  • Third embodiment A method of instructing a redundant transmission path to perform redundant transmission for a radio bearer with redundant transmission activated through a PDCP control PDU
  • a method for a base station to indicate a duplicate transmission path for a radio bearer in which duplicate transmission is activated to the terminal explaineded.
  • the duplicate transmission is performed by submitting the PDCP data PDU from the PDCP entity to two linked RLC entities. That is, after the PDCP entity receives MAC CE for enabling / disabling duplicate transmission of the MAC entity, it performs a duplicate transmission operation according to the indicated information. If two or more independent transmission paths are configured in the UE for any radio bearer, the subject that changes / switches the duplicate transmission paths becomes a PDCP entity. Therefore, information indicating a transmission path for redundant transmission may be provided through a new PDCP control PDU.
  • the PDCP control PDU can be applied only to a radio bearer for which redundant transmission is activated or to be activated.
  • the PDCP control PDU may include information or fields included in MAC CE described in the above-described embodiment. have.
  • One of the reserved 010-111 values can be used for the PDU type value of the corresponding PDCP control PDU.
  • the PDCP PDU is submitted as an RLC entity on the redundant transmission path.
  • the PDPD Control PDU is transmitted through a priority transmission path (primary RLC entity).
  • the following describes how to process data remaining in the previously activated RLC entity when the redundant transmission path is changed using at least one of the above-described methods.
  • the base station receives a duplicate transmission path change for a radio bearer in which duplicate transmission is activated. If so, the terminal may change the redundant transmission path of the radio bearer with redundant transmission activated through the indicated redundant transmission path. At this time, if only the redundant transmission path is changed while the redundant transmission is activated for the corresponding radio bearer, data may remain on the RLC entity that previously performed the redundant transmission. Therefore, if data remains on the RLC entity, when the RLC entity is subsequently reconstructed, a problem may occur in processing the corresponding data.
  • a signal indicating a duplicate transmission path change (RLC entity deactivation) for a radio bearer with duplicate transmission already activated is received. If so, the terminal can change the redundant transmission path to the indicated redundant transmission path (RLC entity).
  • the terminal can process the data remaining in the RLC object changed to the inactive state through the embodiment below.
  • the terminal may reset the previously activated radio bearer duplicate transmission RLC entity.
  • the UE may allow the previous RLC entity to continuously perform transmission.
  • the RLC entity may be configured to discard the corresponding data (PDCP PDUs / RLC SDUs / RLC SDUs segments).
  • the PDCP entity may instruct the previous RLC entity to discard the corresponding data, thereby causing the previous RLC entity to discard the corresponding data.
  • a radio link failure problem may be caused if the previous RLC entity continues to fail to retransmit. Therefore, it may be desirable to reset the RLC entity as described above.
  • a radio link failure may not be detected, or a timer may be set to discard all pending data when the timer expires.
  • an RLC object may be discarded by instructing the PDCP object of the corresponding radio bearer to discard all duplicate PDCP PDUs / RLC SDUs / RLC SDUs segments that have not been processed by the RLC object on the previously activated redundant transmission path. .
  • 16 is a diagram showing the configuration of a terminal according to an embodiment.
  • a terminal 1600 that transmits data is linked to one Packet Data Convergence Protocol (PDCP) entity based on configuration information for configuring data duplication transmission received from a base station, for a radio bearer.
  • a control unit (1610) constituting a plurality of radio link control (RLC) objects used to process the duplicated transmission and a MAC control element (MAC control element) including instruction information indicating an activation state change for the plurality of RLC objects. It may include a receiving unit 1630 for receiving and a transmitting unit 1620 for transmitting data redundantly using the activated RLC entity.
  • RLC radio link control
  • MAC control element MAC control element
  • controller 1610 may change the RLC object indicated as the activated state by the indication information to the activated state.
  • the receiving unit 1630 may receive configuration information transmitted by a base station in order to configure a data duplication transmission function in a terminal.
  • the configuration information may include information necessary to configure a plurality of RLC entities for processing duplicate transmission to the radio bearer.
  • the configuration information may include RLC index information allocated to each RLC entity to distinguish a plurality of RLC entities.
  • the RLC index information is identification information for distinguishing each RLC entity and may be configured as an RLC ID.
  • the configuration information may include information indicating an initial activation state for each of the plurality of RLC entities.
  • the control unit 1610 configures a plurality of RLC entities based on the configuration information.
  • each of the plurality of configured RLC entities is configured to be activated or deactivated in a state indicated in the initial activation state.
  • the plurality of RLC entities may include one primary RLC entity configured to transmit the PDCP control PDU of the radio bearer.
  • the primary RLC entity is a specific RLC entity configured to transmit the PDCP control PDU, and when duplicate transmission is disabled, a PDCP PDU including the PDCP control PDU may be delivered through the primary RLC entity.
  • the primary RLC entity may always be set to the activated state.
  • the primary RLC entity may be configured as an activated state. Thereafter, the primary RLC entity is not converted to an inactive state.
  • the primary RLC entity may transmit the PDCP control PDU even if it is indicated as inactive by MAC CE.
  • the primary RLC entity may be configured as an RLC entity that satisfies any one of the smallest cell group index value, the smallest logical channel ID, and the smallest RLC entity index value among the activated RLC entities. That is, the primary RLC object may be set as an RLC object that satisfies a preset condition among RLC objects configured in an activated state rather than setting a specific fixed RLC object among a plurality of RLC objects.
  • the reception unit 1630 may receive a MAC CE including information indicating activation or deactivation for each of a plurality of RLC entities from the base station.
  • the MAC CE can be received after a plurality of RLC entities are configured in the terminal.
  • the MAC control element may include indication information in the form of a bitmap indicating the activation state of each of a plurality of RLC entities associated with each radio bearer.
  • the bitmap may be composed of only bits for the remaining RLC entities except for one primary RLC entity configured to transmit the PDCP control PDU of the radio bearer among the plurality of RLC entities. Therefore, in the MAC CE, bitmap information may be configured only with bits indicating the activation state of the RLC entity except for the primary RLC entity that is always configured with the activation status.
  • the controller 1610 may change the state of the individual RLC object to an activated or deactivated state based on the indication information indicating the activation state for each RLC object by MAC CE.
  • the transmission path is changed because redundant transmission data is transmitted through the active RLC object.
  • controller 1610 controls the operation of the overall terminal 1600 according to selectively changing the redundant transmission path required to perform the above-described embodiments.
  • the transmitter 1620 and the receiver 1630 are used to transmit and receive signals, messages, and data necessary to perform the above-described embodiments with the base station.
  • 17 is a diagram showing the configuration of a base station according to an embodiment.
  • a base station 1700 that controls data transmission of a terminal is connected to a single Packet Data Convergence Protocol (PDCP) entity, and uses a plurality of radio link controls (RLCs) used to process redundant transmissions to radio bearers.
  • PDCP Packet Data Convergence Protocol
  • RLCs radio link controls
  • the transmitting unit 1720 that transmits configuration information for configuring the object to the terminal to the terminal, and transmits the indication information instructing the activation state change for the plurality of RLC objects to the terminal, and the RLC object activated by the indication information
  • It may include a receiving unit 1730 for receiving data that is redundantly transmitted.
  • the configuration information may include at least one of RLC entity index information and initial activation status information for each of the plurality of RLC entities.
  • the configuration information may include information necessary to configure a plurality of RLC entities for processing duplicate transmission to the radio bearer.
  • the configuration information may include RLC index information allocated to each RLC entity to distinguish a plurality of RLC entities.
  • the RLC index information is identification information for distinguishing each RLC entity and may be configured as an RLC ID.
  • the configuration information may include information indicating an initial activation state for each of the plurality of RLC entities.
  • the plurality of RLC entities may include one primary RLC entity configured to transmit the PDCP control PDU of the radio bearer.
  • the primary RLC entity may always be set to the activated state.
  • the primary RLC entity may be configured as an activated state. Thereafter, the primary RLC entity is not converted to an inactive state.
  • the primary RLC entity may transmit the PDCP control PDU even if it is indicated as inactive by MAC CE.
  • the primary RLC entity may be configured as an RLC entity that satisfies any one of the smallest cell group index value, the smallest logical channel ID, and the smallest RLC entity index value among the activated RLC entities. That is, the primary RLC object may be set as an RLC object that satisfies a preset condition among RLC objects configured in an activated state rather than setting a specific fixed RLC object among a plurality of RLC objects.
  • the preset condition may be configured by the base station or may be configured in the terminal in advance, and may be variously set, such as the largest cell group index value, the largest logical channel ID value, or the largest RLC entity index value. There are no restrictions on the preset conditions.
  • the MAC control element may include indication information in the form of a bitmap indicating an activation state of each of a plurality of RLC entities associated with each radio bearer.
  • the bitmap may be composed of only bits for the remaining RLC entities except for one primary RLC entity configured to transmit the PDCP control PDU of the radio bearer among the plurality of RLC entities.
  • MAC CE may be transmitted after a plurality of RLC entities are configured in the terminal.
  • RLC entity is set as a primary RLC entity, so the 3 remaining RLC entities are used by using 3 bits for each radio bearer. It can indicate the activation state of.
  • controller 1710 controls the operation of the overall base station 1700 according to selectively changing the redundant transmission path required to perform the above-described embodiments.
  • the transmitter 1720 and the receiver 1730 are used to transmit and receive signals, messages, and data necessary for performing the above-described embodiments.
  • the above-described embodiments can be implemented through various means.
  • the embodiments may be implemented by hardware, firmware, software, or a combination thereof.
  • the method according to the embodiments includes one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), FPGAs (Field Programmable Gate Arrays), a processor, a controller, a microcontroller, or a microprocessor.
  • ASICs Application Specific Integrated Circuits
  • DSPs Digital Signal Processors
  • DSPDs Digital Signal Processing Devices
  • PLDs Programmable Logic Devices
  • FPGAs Field Programmable Gate Arrays
  • processor a controller, a microcontroller, or a microprocessor.
  • the method according to the embodiments may be implemented in the form of an apparatus, procedure, or function that performs the functions or operations described above.
  • the software code can be stored in a memory unit and driven by a processor.
  • the memory unit is located inside or outside the processor, and can exchange data with the processor by various known means.
  • system generally refer to computer-related object hardware, hardware and software. It can mean a combination of, software or running software.
  • the above-described components may be, but are not limited to, a process, processor, controller, control processor, entity, execution thread, program and / or computer driven by a processor.
  • an application running on a controller or processor and a controller or processor can be components.
  • One or more components can be in a process and / or thread of execution, and the components can be located on one device (eg, a system, computing device, etc.) or distributed across two or more devices.

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 technique de duplication de transmission de données dans une technologie d'accès sans fil de nouvelle génération/5G (nouvelle radio (NR)). Un mode de réalisation concerne un dispositif et un procédé de transmission de données par l'intermédiaire d'un terminal, comprenant les étapes consistant : à configurer une pluralité d'objets de commande de liaison radio (RLC) qui sont liés à un objet unique de protocole de convergence de données par paquets (PDCP) et utilisés pour traiter une transmission dupliquée correspondant à un support sans fil, sur la base d'informations de configuration permettant de configurer une transmission dupliquée de données reçues en provenance d'une station de base ; à recevoir un élément de commande MAC comprenant des informations d'indication indiquant un changement d'état d'activation concernant la pluralité d'objets RLC ; à changer, à un état actif, un objet RLC indiqué par les informations d'indication afin d'être à l'état actif ; et à effectuer une transmission dupliquée des données à l'aide de l'objet RLC activé.
PCT/KR2019/012156 2018-09-21 2019-09-19 Procédé et dispositif de transmission de données Ceased WO2020060234A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201980061954.4A CN112740749B (zh) 2018-09-21 2019-09-19 用于传输数据的方法和装置
US17/277,714 US11523303B2 (en) 2018-09-21 2019-09-19 Method and device for transmitting data

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
KR20180113549 2018-09-21
KR10-2018-0113549 2018-09-21
KR1020190061275A KR20200034921A (ko) 2018-09-21 2019-05-24 5G IoT를 위한 데이터 중복 전송 방법 및 장치
KR10-2019-0061275 2019-05-24
KR1020190114503A KR102385544B1 (ko) 2018-09-21 2019-09-18 데이터 전송 방법 및 장치
KR10-2019-0114503 2019-09-18

Publications (1)

Publication Number Publication Date
WO2020060234A1 true WO2020060234A1 (fr) 2020-03-26

Family

ID=69887480

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2019/012156 Ceased WO2020060234A1 (fr) 2018-09-21 2019-09-19 Procédé et dispositif de transmission de données

Country Status (1)

Country Link
WO (1) WO2020060234A1 (fr)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210219171A1 (en) * 2018-09-28 2021-07-15 Huawei Technologies Co., Ltd. Communication method and device
US20210336732A1 (en) * 2019-01-16 2021-10-28 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Method for data transmission and terminal device
CN113825168A (zh) * 2020-06-19 2021-12-21 北京三星通信技术研究有限公司 一种支持数据传输的方法及设备
CN114499790A (zh) * 2020-10-27 2022-05-13 上海朗帛通信技术有限公司 一种被用于无线通信的方法和设备
WO2024036520A1 (fr) * 2022-08-17 2024-02-22 北京小米移动软件有限公司 Procédé de détermination d'identifiant de canal logique de liaison latérale, et appareil
WO2024060148A1 (fr) * 2022-09-22 2024-03-28 Nec Corporation Procédé, dispositif et support de stockage informatique de communication
US12477611B2 (en) * 2020-05-21 2025-11-18 Huawei Technologies Co., Ltd. Communication method and apparatus

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180098250A1 (en) * 2016-09-30 2018-04-05 Huawei Technologies Co., Ltd. Ultra reliable low latency connection support in radio access networks
KR20180081446A (ko) * 2017-01-06 2018-07-16 주식회사 케이티 데이터 중복 전송을 제어하는 방법 및 그 장치
WO2018164499A1 (fr) * 2017-03-10 2018-09-13 주식회사 케이티 Procédé de transmission de rapport d'état de tampon, et dispositif associé

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180098250A1 (en) * 2016-09-30 2018-04-05 Huawei Technologies Co., Ltd. Ultra reliable low latency connection support in radio access networks
KR20180081446A (ko) * 2017-01-06 2018-07-16 주식회사 케이티 데이터 중복 전송을 제어하는 방법 및 그 장치
WO2018164499A1 (fr) * 2017-03-10 2018-09-13 주식회사 케이티 Procédé de transmission de rapport d'état de tampon, et dispositif associé

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"Remaining issues on PDCP duplication", R2-1805273. 3GPP TSG-RAN WG2 MEETING #101BIS, 6 April 2018 (2018-04-06), XP051415959 *
HUAWEI ET AL.: "Leftover Issues of MAC CE activation/deactivation of PDCP duplication", R2-1812075. 3 GPP TSG-RAN2 MEETING #103, 9 August 2018 (2018-08-09), XP051521698 *

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210219171A1 (en) * 2018-09-28 2021-07-15 Huawei Technologies Co., Ltd. Communication method and device
EP3843453A4 (fr) * 2018-09-28 2021-10-13 Huawei Technologies Co., Ltd. Procédé et dispositif de communication
US11974162B2 (en) 2018-09-28 2024-04-30 Huawei Technologies Co., Ltd. Communication method and device
US20210336732A1 (en) * 2019-01-16 2021-10-28 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Method for data transmission and terminal device
US12348439B2 (en) * 2019-01-16 2025-07-01 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Method for data transmission and terminal device
US12477611B2 (en) * 2020-05-21 2025-11-18 Huawei Technologies Co., Ltd. Communication method and apparatus
CN113825168A (zh) * 2020-06-19 2021-12-21 北京三星通信技术研究有限公司 一种支持数据传输的方法及设备
CN114499790A (zh) * 2020-10-27 2022-05-13 上海朗帛通信技术有限公司 一种被用于无线通信的方法和设备
CN114499790B (zh) * 2020-10-27 2025-01-24 上海朗帛通信技术有限公司 一种被用于无线通信的方法和设备
WO2024036520A1 (fr) * 2022-08-17 2024-02-22 北京小米移动软件有限公司 Procédé de détermination d'identifiant de canal logique de liaison latérale, et appareil
WO2024060148A1 (fr) * 2022-09-22 2024-03-28 Nec Corporation Procédé, dispositif et support de stockage informatique de communication

Similar Documents

Publication Publication Date Title
WO2020145610A1 (fr) Procédé et dispositif de transmission et de réception d'informations de commande de liaison montante
WO2021060786A1 (fr) Procédé de commande de communication de liaison latérale, et dispositif associé
WO2020189941A1 (fr) Procédé de réalisation d'une communication à l'aide d'un réseau non terrestre, et dispositif associé
WO2020060234A1 (fr) Procédé et dispositif de transmission de données
WO2023146337A1 (fr) Procédé et dispositif de commande de trafic
WO2021230614A1 (fr) Procédé et appareil de transmission de données de liaison montante
WO2020209657A1 (fr) Procédé permettant d'effectuer une communication de liaison latérale, et dispositif associé
WO2021187933A1 (fr) Procédé et dispositif de commande de nœud de relais
WO2022203289A1 (fr) Procédé et dispositif de commande de session mbs
WO2021206371A1 (fr) Procédé de commande de communication de liaison latérale et dispositif associé
WO2024030009A1 (fr) Procédé et dispositif permettant de transmettre une liaison montante dans un réseau sans fil
WO2019221443A1 (fr) Procédé et appareil permettant d'effectuer une écoute avant de parler (lbt) pour une communication sans fil dans une bande sans licence
WO2022050775A1 (fr) Procédé et dispositif de réduction du surdébit d'une transmission de signaux de référence de positionnement
WO2023211048A1 (fr) Procédé et dispositif de traitement de données par paquets
WO2020050630A1 (fr) Procédé et dispositif d'exécution d'une transmission sans fil dans une bande sans licence
WO2019221475A1 (fr) Procédé et dispositif de transmission d'informations de rétroaction harq dans une bande sans licence
WO2020032675A1 (fr) Procédé et appareil d'émission ou de réception de données dans une bande sans licence
WO2020027535A1 (fr) Procédé et dispositif de transmission et de réception d'informations de commande de liaison montante dans une bande sans licence
WO2024014862A1 (fr) Procédé et appareil d'utilisation d'un modèle d'apprentissage automatique/intelligence artificielle dans un réseau de communication sans fil
WO2023128220A1 (fr) Procédé et appareil pour effectuer un transfert conditionnel
WO2022005153A1 (fr) Procédé et appareil pour effectuer un saut de fréquence
WO2020209656A1 (fr) Procédé pour effectuer une communication de liaison latérale, et dispositif associé
WO2020166910A1 (fr) Procédé de commande de communication en liaison latérale, et dispositif associé
WO2020045861A1 (fr) Procédé et appareil de commande d'une opération d'accès aléatoire dans une bande sans licence
WO2019190264A1 (fr) Procédé et dispositif de transmission d'un canal de commande de liaison montante

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19861951

Country of ref document: EP

Kind code of ref document: A1