WO2018174418A1 - Procédé et appareil de traitement de données pour une duplication de paquets - Google Patents

Procédé et appareil de traitement de données pour une duplication de paquets Download PDF

Info

Publication number
WO2018174418A1
WO2018174418A1 PCT/KR2018/002264 KR2018002264W WO2018174418A1 WO 2018174418 A1 WO2018174418 A1 WO 2018174418A1 KR 2018002264 W KR2018002264 W KR 2018002264W WO 2018174418 A1 WO2018174418 A1 WO 2018174418A1
Authority
WO
WIPO (PCT)
Prior art keywords
logical channel
packet
duplication
message
packet duplication
Prior art date
Application number
PCT/KR2018/002264
Other languages
English (en)
Korean (ko)
Inventor
백상규
아닐에기월
강현정
정정수
Original Assignee
삼성전자 주식회사
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from KR1020170126578A external-priority patent/KR102357594B1/ko
Application filed by 삼성전자 주식회사 filed Critical 삼성전자 주식회사
Priority to CN201880020299.3A priority Critical patent/CN110463255B/zh
Priority to CN202310580157.5A priority patent/CN116567716A/zh
Priority to EP18772600.5A priority patent/EP3589009B1/fr
Priority to EP21191862.8A priority patent/EP3934314B1/fr
Priority to US16/496,940 priority patent/US11140571B2/en
Publication of WO2018174418A1 publication Critical patent/WO2018174418A1/fr
Priority to US17/486,761 priority patent/US11700542B2/en
Priority to US18/349,816 priority patent/US20230354084A1/en

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
    • H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H04W28/0263—Traffic management, e.g. flow control or congestion control per individual bearer or channel involving mapping traffic to individual bearers or channels, e.g. traffic flow template [TFT]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H04L1/1614—Details of the supervisory signal using bitmaps
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0096—Indication of changes in allocation
    • H04L5/0098—Signalling of the activation or deactivation of component carriers, subcarriers or frequency bands
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0278—Traffic management, e.g. flow control or congestion control using buffer status reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0044—Arrangements for allocating sub-channels of the transmission path allocation of payload

Definitions

  • the present invention relates to a data processing method and apparatus for packet duplication, and moreover, to a data structure for packet duplication.
  • a 5G communication system or a pre-5G communication system is called a Beyond 4G network communication system or a post LTE system.
  • 5G communication systems are being considered for implementation in the ultra-high frequency (mmWave) band (eg, such as the 60 Gigabit (60 GHz) band).
  • mmWave ultra-high frequency
  • FD-MIMO massive array multiple input / output
  • FD-MIMO massive array multiple input / output
  • Array antenna, analog beam-forming, and large scale antenna techniques are discussed.
  • 5G communication systems have advanced small cells, advanced small cells, cloud radio access network (cloud RAN), ultra-dense network (ultra-dense network) , Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, Coordinated Multi-Points (CoMP), and interference cancellation
  • cloud RAN cloud radio access network
  • ultra-dense network ultra-dense network
  • D2D Device to Device communication
  • wireless backhaul moving network
  • cooperative communication Coordinated Multi-Points (CoMP), and interference cancellation
  • Hybrid FSK and QAM Modulation FQAM
  • SWSC Slide Window Superposition Coding
  • ACM Advanced Coding Modulation
  • FBMC Fan Bank Multi Carrier
  • NOMA non orthogonal multiple access
  • SCMA sparse code multiple access
  • IoT Internet of Things
  • IoE Internet of Everything
  • M2M machine to machine
  • MTC Machine Type Communication
  • IT intelligent Internet technology services can be provided that collect and analyze data generated from connected objects to create new value in human life.
  • IoT is a field of smart home, smart building, smart city, smart car or connected car, smart grid, health care, smart home appliances, advanced medical services, etc. through convergence and complex of existing information technology (IT) technology and various industries. It can be applied to.
  • An object of the present invention is to provide a data processing method and apparatus, and further a data structure for packet duplication.
  • the present invention has been made in an effort to provide a radio bearer setup method, a packet duplication operation, and a buffer status reporting method when performing packet duplication.
  • a method of a terminal in a mobile communication system includes receiving information for mapping a logical channel from a base station to a component carrier (CC) and a data packet mapped in the logical channel according to the information. It may include transmitting to the base station through.
  • CC component carrier
  • a terminal of a mobile communication system receives information for mapping a logical channel to a component carrier (CC) from a transceiver and a base station for transmitting and receiving a signal, and receives a data packet processed in the logical channel. It may include a controller configured to transmit to the base station through the CC mapped according to the information.
  • CC component carrier
  • a method of a base station in a mobile communication system is a step of transmitting information for mapping a logical channel to the CC (Component Carrier) to the terminal and mapping the data packet processed in the logical channel according to the information It may include receiving from the terminal through the CC.
  • CC Component Carrier
  • a base station of a mobile communication system transmits a transceiver for transmitting and receiving a signal and information for mapping a logical channel to a component carrier (CC) to a terminal, and transmits the data packet processed in the logical channel. It may include a control unit configured to receive from the terminal through the CC mapped according to the information.
  • CC component carrier
  • An object of the present invention is to provide a data processing method and structure for packet duplication.
  • effective redundant transmission is possible in a communication environment having multiple links.
  • 1 is a diagram illustrating a radio bearer structure in an LTE CA environment.
  • FIG. 2 is a flowchart illustrating a transmitter for performing packet redundancy according to an embodiment of the present invention.
  • FIG. 3 is a diagram illustrating an embodiment of a bearer structure for packet duplication according to an embodiment of the present invention.
  • FIG. 4 is a diagram illustrating another embodiment of a bearer structure for packet duplication according to an embodiment of the present invention.
  • FIG. 5 is a diagram illustrating another embodiment of a bearer structure for packet duplication according to an embodiment of the present invention.
  • FIG. 6 illustrates another embodiment of a bearer structure for packet duplication according to an embodiment of the present invention.
  • FIG. 7 is a diagram illustrating another embodiment of a bearer structure for packet duplication according to an embodiment of the present invention.
  • FIG. 8 is a diagram illustrating another embodiment of a bearer structure for packet duplication according to an embodiment of the present invention.
  • FIG. 9 is a diagram illustrating an embodiment of a radio bearer setup message for packet duplication according to an embodiment of the present invention.
  • FIG. 10 is a diagram illustrating an embodiment of setting and releasing packet duplication according to an embodiment of the present invention.
  • FIG. 11 is a diagram illustrating another embodiment of setting and releasing packet duplication according to an embodiment of the present invention.
  • FIG. 12 illustrates another embodiment of setting and releasing packet duplication according to an embodiment of the present invention.
  • FIG. 13 is a diagram illustrating an embodiment of a method of starting packet transmission on a logical channel for packet duplication when packet duplication is initiated according to an embodiment of the present invention.
  • FIG. 14 is a diagram illustrating another embodiment of a method of starting packet transmission on a logical channel for packet duplication when packet duplication is started according to an embodiment of the present invention.
  • 15 is a diagram illustrating another embodiment of a method of starting packet transmission on a logical channel for packet duplication when packet duplication is initiated according to an embodiment of the present invention.
  • 16 is a diagram illustrating an embodiment of a procedure to be performed when packet duplication is released according to an embodiment of the present invention.
  • FIG. 17 illustrates another embodiment of a procedure performed when packet duplication is released according to an embodiment of the present invention.
  • FIG. 18 is a diagram illustrating a specific operation example when packet duplication is performed.
  • 19 is a diagram illustrating an embodiment of sending an uplink buffer status report when packet duplication is performed according to an embodiment of the present invention.
  • 20 is a diagram illustrating another embodiment of transmitting an uplink buffer status report when packet duplication is performed according to an embodiment of the present invention.
  • 21 illustrates another embodiment of transmitting an uplink buffer status report when packet duplication is performed according to an embodiment of the present invention.
  • 22 is a diagram illustrating an embodiment of applying a packet overlap count according to an embodiment of the present invention.
  • FIG. 23 is a diagram illustrating a format of a packet duplication activation message according to an embodiment of the present invention.
  • FIG. 24 is a diagram illustrating another format of a packet duplication activation message according to an embodiment of the present invention.
  • 25 is a diagram illustrating another format of a packet duplication activation message according to an embodiment of the present invention.
  • FIG. 26 is a diagram illustrating a format of a packet deactivation message according to an embodiment of the present invention.
  • FIG. 27 illustrates another format of a packet deactivation message according to an embodiment of the present invention.
  • FIG. 28 is a diagram illustrating another format of a packet deactivation message according to an embodiment of the present invention.
  • 29 is a diagram illustrating another format of a packet duplicate activation / deactivation message according to an embodiment of the present invention.
  • FIG. 30 illustrates another embodiment of a radio bearer setup message for packet duplication according to an embodiment of the present invention.
  • 31 illustrates another embodiment of a radio bearer setup message for packet duplication according to an embodiment of the present invention.
  • FIG. 32 illustrates another format of a packet duplicate activation message according to an embodiment of the present invention.
  • 33 is a view showing another format of a packet duplicate deactivation message according to an embodiment of the present invention.
  • 34 illustrates another format of a packet duplicate activation message according to an embodiment of the present invention.
  • 35 is a view showing another format of a packet duplicate deactivation message according to an embodiment of the present invention.
  • 36 illustrates a format of a message for dynamically changing a mapping relationship between a logical channel and a CC according to an embodiment of the present invention.
  • FIG. 37 is a diagram illustrating an embodiment of a procedure for setting packet duplication according to an embodiment of the present invention.
  • 38 is a diagram illustrating a terminal according to an embodiment of the present invention.
  • 39 is a diagram illustrating a base station according to an embodiment of the present invention.
  • FIG. 40 illustrates an embodiment of a bearer structure and primary logical channel determination for packet duplication according to an embodiment of the present invention.
  • 41 is a diagram illustrating a receiver operation according to an embodiment of the present invention.
  • 43 is a diagram illustrating a receiver operation according to an embodiment of the present invention.
  • each block of the flowchart illustrations and combinations of flowchart illustrations may be performed by computer program instructions. Since these computer program instructions may be mounted on a processor of a general purpose computer, special purpose computer, or other programmable data processing equipment, those instructions executed through the processor of the computer or other programmable data processing equipment may be described in flow chart block (s). It creates a means to perform the functions. These computer program instructions may be stored in a computer usable or computer readable memory that can be directed to a computer or other programmable data processing equipment to implement functionality in a particular manner, and thus the computer usable or computer readable memory. It is also possible for the instructions stored in to produce an article of manufacture containing instruction means for performing the functions described in the flowchart block (s).
  • Computer program instructions may also be mounted on a computer or other programmable data processing equipment, such that a series of operating steps may be performed on the computer or other programmable data processing equipment to create a computer-implemented process to create a computer or other programmable data. Instructions for performing the processing equipment may also provide steps for performing the functions described in the flowchart block (s).
  • each block may represent a portion of a module, segment, or code that includes one or more executable instructions for executing a specified logical function (s).
  • logical function e.g., a module, segment, or code that includes one or more executable instructions for executing a specified logical function (s).
  • the functions noted in the blocks may occur out of order.
  • the two blocks shown in succession may in fact be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending on the corresponding function.
  • ' ⁇ part' used in the present embodiment refers to software or a hardware component such as an FPGA or an ASIC, and ' ⁇ part' performs certain roles.
  • ' ⁇ ' is not meant to be limited to software or hardware.
  • ' ⁇ Portion' may be configured to be in an addressable storage medium or may be configured to play one or more processors.
  • ' ⁇ ' means components such as software components, object-oriented software components, class components, and task components, and processes, functions, properties, procedures, and the like. Subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables.
  • the functionality provided within the components and the 'parts' may be combined into a smaller number of components and the 'parts' or further separated into additional components and the 'parts'.
  • the components and ' ⁇ ' may be implemented to play one or more CPUs in the device or secure multimedia card.
  • CA LTE carrier aggregation
  • data flow is processed for each bearer, and data is mapped to one radio bearer.
  • Each radio bearer is mapped to a logical channel in a 1: 1 manner, and these logical channels are multiplexed in the MAC layer to be transmitted.
  • CA is a technology that combines several CC (Component Carrier) to collect and use multiple frequency resources, data multiplexed in the MAC layer is transmitted to one of the CC.
  • 1 shows an embodiment in which radio bearers 1 and 2 are mapped to logical channels 1 and 2 with PDCP devices and RLC devices, respectively.
  • logical channels 1,2 are multiplexed in the MAC layer and then data is transmitted to one of CC 1,2 and3.
  • the CC may be recognized as one cell by the terminal, and may be configured as a primary cell (PCell) or a secondary cell (SCell), and the same will be described below.
  • FIG. 2 is a flowchart of a transmitter 200 for performing packet duplication. If packet duplication is set for a specific radio bearer 210, data processed by the radio bearer 210 may go through a packet duplication procedure. Packet duplication is typically performed by duplicating data and then sending the data to different logical channels. At this time, the data packets duplicated by packet duplication are sent to different logical channels 220 and 230, or to different splits in split bearer environments, or to different CCs. , Different numerology (Numerology) or TTI type can be sent. Duplicating the data packet by performing packet duplication may be performed in one of the PDCP, RLC, and MAC layers, which are data processing layers. The data here may be in the form of an IP packet handled by the user. In another embodiment, this data may be a control signal in a protocol such as an RRC message.
  • Radio bearer A 310 is a bearer that allows packet duplication and radio bearer B 320 is a bearer that does not allow packet duplication.
  • 3 illustrates that a PDCP device (or entity) of a radio bearer A 310 replicates a PDCP PDU (Protocol Data Unit) and then transmits each replicated PDCP PDU to different RLC devices for processing. Each RLC device is mapped to logical channels 1 and 2 (330, 340), respectively.
  • the radio bearer B 320 is mapped to one logical channel (logical channel 3) because packet duplication is not allowed.
  • mapping between logical channel and CC (Component Carrier) is necessary for efficient packet transmission.
  • CC Component Carrier
  • the main purpose is to increase the reliability and reduce the transmission latency by transmitting the duplicated packets after processing separate data.
  • the duplicated data packets are transmitted to different CCs. It is necessary.
  • FIG. 1 In the embodiment of FIG. 1
  • logical channel 1 330 is mapped to CC 1 and CC 2 so that data packets of logical channel 1 330 can be transmitted through CC 1 and CC 2, and logical channel 2 340 is mapped to CC 3.
  • the data packet of logical channel 2 340 may be transmitted through CC3, and the data packet of logical channel 3 may be transmitted to CC2 and CC3.
  • mapping the logical channel to the neurology or TTI. That is, apart from mapping the logical channel to the CC or mapping to the CC, the logical channel may be mapped to a specific numerology and / or TTI for data packet transmission.
  • the mapping between the logical channel and the CC is not limited to the above-described packet duplication process, but may be performed separately from packet duplication.
  • Whether the bearer allows packet duplication may be determined according to the type of traffic the packet contains.
  • the type of traffic may be classified into voice, video streaming, web surfing data, and the like, and according to this classification, a certain kind of traffic may be set to allow packet duplication.
  • whether or not to duplicate packets may be set according to the QoS setting value of the data.
  • QOS configuration value may be represented by an ID indicating QoS, such as a QoS flow ID. In this case, it is also possible to allow packet duplication for a specific QoS flow ID.
  • a bearer in which a packet having a QoS flow ID of 0 to 15 is transmitted may be duplicated, and a bearer in which a packet having a remaining QoS flow ID is transmitted may not be duplicated.
  • Whether the bearer allows packet duplication may be determined by each of the aforementioned various criteria or a combination of two or more, and other criteria may be applied in addition to the aforementioned criteria.
  • the packet duplication may be applied to both the SRB transmitting the control signal and the DRB transmitting the data.
  • Radio bearer A 410 is a bearer that allows packet duplication and radio bearer B 420 is a bearer that does not allow packet duplication.
  • 3 illustrates that an RLC device (or entity) of the radio bearer A 410 replicates an RLC Protocol Data Unit (PDU) and then sends each replicated RLC PDU to different logical channels for processing.
  • the RLC device of radio bearer A 410 is mapped to logical channels 1,2.
  • Radio bearer B is mapped to one logical channel of logical channel 3 because packet duplication is not allowed.
  • mapping between logical channel and CC (Component Carrier) is necessary for efficient packet transmission.
  • CC Component Carrier
  • mapping the logical channel and the CC that is, by setting / defining a mapping relationship between the logical channel and the CC
  • the main purpose is to increase the reliability and reduce the transmission latency by transmitting the duplicated packets after processing separate data.
  • the duplicated data packets are transmitted to different CCs. It is necessary.
  • logical channel 1 is mapped to CC 1 and CC 2 so that data packets of logical channel 1 can be transmitted through CC 1 and CC 2
  • logical channel 2 is mapped to CC 3 so that data packets of logical channel 2 are referred to as CC 3.
  • the data packet of logical channel 3 may be transmitted through CC2 and CC3.
  • mapping the logical channel to the neurology or TTI. That is, apart from mapping the logical channel to the CC or mapping to the CC, the logical channel may be mapped to a specific numerology and / or TTI for data packet transmission.
  • the mapping between the logical channel and the CC is not limited to the above-described packet duplication process, but may be performed separately from packet duplication.
  • the packet duplication may be applied to both the SRB transmitting the control signal and the DRB transmitting the data.
  • logical channel 1 520 is configured as a primary logical channel and logical channel 2 530 is configured as a secondary logical channel for radio bearer A 510 that allows packet duplication.
  • the other bearer structure is as defined in FIG.
  • the primary and secondary logical channels may be designated by the base station through an RRC configuration.
  • the UE may be instructed to transmit data on the secondary logical channel through a packet redundancy activation message. A specific embodiment of such a packet duplication activation message will be described later.
  • the packet duplication may be applied to both the SRB transmitting the control signal and the DRB transmitting the data.
  • logical channel 1 620 is configured as a primary logical channel and logical channel 2 630 is configured as a secondary logical channel for radio bearer A 610 allowing packet duplication.
  • the other bearer structure is as defined in FIG.
  • the primary and secondary logical channels may be designated by the base station through an RRC configuration.
  • the UE may be instructed to transmit data on the secondary logical channel through a packet redundancy activation message. A specific embodiment of such a packet duplication activation message will be described later.
  • the packet duplication may be applied to both the SRB transmitting the control signal and the DRB transmitting the data.
  • FIG. 7 is another embodiment of a bearer structure for packet redundancy (700).
  • the PDCP device and the RLC device are omitted as a simplified structure in which a single radio bearer shown in the embodiments of FIGS. 3-6 is mapped to multiple logical channels and CCs.
  • the PDCP device and the RLC device may be one of the mapping methods of the embodiments of FIGS. 3-6.
  • the radio bearer 1 710 is duplicated and transmitted to the logical channels 1 720 and 3 750, and the logical channel 1 720 is connected to the CC1 730 and CC3 740.
  • Channel 3 750 is mapped to and transmitted to CC4 760 and CC5 770.
  • the packet duplication may be applied to both the SRB transmitting the control signal and the DRB transmitting the data.
  • FIG. 8 is another embodiment of a bearer structure for packet redundancy 800.
  • the PDCP device and the RLC device are omitted as a simplified structure in which a single radio bearer shown in the embodiments of FIGS. 3-6 is mapped to multiple logical channels and CCs.
  • the PDCP device and the RLC device may be one of the mapping methods of the embodiments of FIGS. 3-6.
  • the radio bearer 1 810 is transmitted in duplicated packets to logical channels 1 820 and 3 850, and logical channel 1 820 is connected to CC1 830 and CC3 840.
  • Channel 3 850 is mapped to and transmitted to CC4 860 and CC5 870.
  • FIG. 8 is another embodiment of a bearer structure for packet redundancy 800.
  • the PDCP device and the RLC device are omitted as a simplified structure in which a single radio bearer shown in the embodiments of FIGS. 3-6 is mapped to multiple logical channels and CCs.
  • each CC further supports a plurality of numerologies or TTI types.
  • type 1 of CC1 830 may have a 15 KHz subcarrier spacing and 1 ms TTI
  • type 2 835 may have a 30 KHz subcarrier spacing and 0.25 ms TTI.
  • Type 2 835 of CC1 830 that performs packet duplication of Radio Bearer 1 810, Type 1 and 2 845 of CC3 840, and Type 1 of CC4 860.
  • 2,3 865 which may be sent to type 1 875 of CC5 870.
  • the above description is that the specific neuralology and / or TTI type is pre-mapped to a logical channel and / or CC through which packet duplication is performed so that duplicate data packets are transmitted.
  • the above-described mapping is an embodiment and may be differently designated according to the configuration of the base station or the terminal, the type of traffic, the QoS flow ID, and the like.
  • the packet duplication may be applied to both the SRB transmitting the control signal and the DRB transmitting the data.
  • FIG. 9 illustrates an embodiment of a radio bearer setup message for packet duplication described in FIGS. 3 to 8.
  • the DRB ID set in FIG. 9 is 6 and the DuplicationMode field is set to True to indicate that packet duplication is allowed.
  • Logical channel IDs (indicated by the LogicalChannelIdentity field) that perform packet redundancy are 4 and 5, and packets sent to logical channel 4 can only be sent in 15KHz, 30KHz neutrals (indicated by the Correspondingnumerology field) of CC 1,2,3 This means that a packet transmitted on logical channel 5 uses all CC and can only be transmitted in 15KHz of neurology.
  • the numerology may be displayed at frequency intervals as shown in FIG. 9, but may be designated as a previously set numerology or TTI type.
  • Logical channel 4 is the primary logical channel and logical channel 5 is the secondary logical channel (indicated by the DuplicationType field).
  • each logical channel may independently send the same packet repeatedly, but may also perform an independent packet duplication by the value set in the NumberOfDuplication field.
  • Independent packet transmission means that the transmitter determines the NACK of the ARQ without receiving and performs the transmission once more.
  • the base station may set a packet duplication of the radio bearer by sending a duplication configuration message to the terminal (S1010). This message may include some of the configuration message of FIG. 9.
  • the UE upon receiving a duplication configuration message, the UE establishes a bearer for packet duplication and performs packet duplication (S1020). Thereafter, when the terminal receives a duplication release message from the base station (S1030), the terminal may release a bearer for packet duplication, release a secondary logical channel for packet duplication, or perform a procedure of not performing packet duplication ( S1040).
  • the base station may set the packet duplication of the radio bearer by sending a duplication configuration message to the terminal (S1110). This message may include some of the configuration message of FIG. 9.
  • the UE upon receiving a duplication configuration message, the UE configures a bearer for packet duplication. Subsequently, when the UE receives the duplication activation message (S1120), it performs the actual packet duplication (S1130). Until the duplication activation message is received, the logical channel for packet duplication is created but no actual data is sent to the logical channel. In this case, data transmission may be performed only through the primary logical channel.
  • the UE After the UE receives the duplication deactivation message from the base station (S1140) and stops the actual packet duplication (S1150). However, this does not change the bearer structure such as logical channels for packet duplication. If there is a secondary logical channel, data transmission to the secondary logical channel can be stopped. Thereafter, when the terminal receives a duplication release message from the base station (S1160), the terminal may release a bearer for packet duplication, release a secondary logical channel for packet duplication, or perform a procedure not performing packet duplication.
  • the base station may set the packet duplication of the radio bearer by sending a duplication configuration message to the terminal (S1210). This message may include some of the configuration message of FIG. 9.
  • the UE upon receiving a duplication configuration message, the UE establishes a bearer for packet duplication. Subsequently, when the terminal receives the duplication activation message (S1220) and the condition for the packet duplication (duplication condition) set in advance is satisfied (S1230), the terminal performs the actual packet duplication (S1240).
  • the condition for packet duplication may be when the radio link quality of the terminal and the base station is below a certain level.
  • the logical channel for packet duplication is created but no actual data is sent to the logical channel. In this case, data transmission may be performed only through the primary logical channel. If the condition for packet duplication is no longer satisfied or the condition for canceling packet duplication transmission is satisfied, packet duplication may not be performed even after receiving a duplication activation message.
  • the terminal receives the duplication deactivation message from the base station (S1250)
  • the actual packet duplication is stopped (S1260). However, this does not change the bearer structure such as logical channels for packet duplication. If there is a secondary logical channel, data transmission to the secondary logical channel can be stopped. Thereafter, when the terminal receives a duplication release message from the base station (S1270), the terminal may release a bearer for packet duplication, release a secondary logical channel for packet duplication, or perform a procedure of not performing packet duplication.
  • FIG. 13 illustrates an embodiment of a method of initiating packet transmission on a logical channel for packet duplication when packet duplication is initiated (1300).
  • transmission is performed only to the logical channel 1 (LC1, 1310) before the redundant transmission, and the transmission is also performed on the logical channel 2 (LC2, 1320) when packet duplication starts.
  • Packet redundancy may be based on a time point at which actual packet redundancy starts according to various embodiments shown and described with reference to FIGS. 10 to 12.
  • the packet in the buffer is selected from the earliest having the earliest sequence number (SN) among the packets transmitted from the existing logical channel 1 1310 but not receiving an ACK.
  • SN sequence number
  • the RLC SN (order number) of the logical channel 2 1320 may be started from the beginning, or the sequence number of the RLC device of the logical channel 1 1320 may be used as it is. If the same sequence numbers of the logical channel 1 1310 and the logical channel 2 1320 are used, the RLC device corresponding to the logical channel 2 1320 of the receiver is informed of a part of the RLC state information of the logical channel 1 1310. Can be. In this case, the corresponding information may be, for example, the beginning of the RLC SN (the RLC SN of the packet B) or the entire RLC variable (Variable). Also, according to an embodiment, it may be a PDCP SN or a PDCP COUNT corresponding to each RLC packet.
  • FIG. 14 illustrates another embodiment of a method of starting packet transmission on a logical channel for packet duplication when packet duplication is initiated (1400).
  • transmission is performed only to the logical channel 1 (LC1, 1410) before the redundant transmission, and then the transmission is also performed on the logical channel 2 (LC2, 1420) when packet duplication starts.
  • Packet redundancy may be based on a time point at which actual packet redundancy starts according to various embodiments shown and described with reference to FIGS. 10 to 12.
  • the logical channel is transmitted from the earliest sequence number (SN) to the untransmitted packet transmitted in the existing logical channel 1 1410 but not ACK and the untransmitted packet in the buffer.
  • SN earliest sequence number
  • the RLC SN (order number) of the logical channel 2 1420 may be started from the beginning, or the sequence number of the RLC device of the logical channel 1 1410 may be used as it is. If the same sequence numbers of the logical channel 1 1410 and the logical channel 2 1420 are used, the RLC device corresponding to the logical channel 2 1420 of the receiver is informed of a part of the RLC state information of the logical channel 1 1410. Can be. In this case, the corresponding information may be, for example, the beginning of the RLC SN (the RLC SN of the packet B) or the entire RLC variable (Variable). Also, according to an embodiment, it may be a PDCP SN or a PDCP COUNT corresponding to each RLC packet.
  • FIG. 15 illustrates another embodiment of a method of initiating packet transmission on a logical channel for packet duplication when packet duplication starts.
  • transmission is performed only to the logical channel 1 (LC1, 1510) before the redundant transmission, and the transmission is also performed on the logical channel 2 (LC2, 1520) when packet duplication starts.
  • Packet redundancy may be based on a time point at which actual packet redundancy starts according to various embodiments shown and described with reference to FIGS. 10 to 12.
  • a packet not transmitted in the existing logical channel 1 1510 may be transferred to the logical channel 2 1520 from the earliest having the highest sequence number (SN) (ie, Can be duplicated).
  • SN sequence number
  • packet duplication is performed from untransmitted packet E to logical channel 1 1510 and logical channel 2 1520.
  • Packet transfer can be performed (ie, replicated). In other words, data packets not sent down to logical channel 1 1510 may be replicated to logical channel 2 1520.
  • the RLC SN (order number) of logical channel 2 1520 may start from the beginning, or the sequence number of the RLC device of logical channel 1 1510 may be used as it is. If the same sequence numbers of the logical channel 1 1510 and the logical channel 2 1520 are used, the RLC device corresponding to the logical channel 2 1520 of the receiver is informed of a part of the RLC state information of the logical channel 1 1510. Can be.
  • the corresponding information may be, for example, the beginning of the RLC SN (the RLC SN of the packet B) or the entire RLC variable (Variable). Also, according to an embodiment, it may be a PDCP SN or a PDCP COUNT corresponding to each RLC packet.
  • FIG. 16 illustrates an embodiment of a procedure to be performed when packet duplication is released while performing data transmission by performing packet duplication (1600).
  • packet transmission is performed by performing packet duplication on logical channels 1 and 2 (1610 and 1620)
  • a time point at which actual packet duplication is released according to various embodiments described in the description of FIGS. 10 to 12. Indicates the action to be taken by.
  • packets A, C, and E receive an ACK on logical channel 1 (1610) at the moment when packet duplication is released, and B and D transmit, but ACK is not received, and packet B on logical channel 2 (1620).
  • E received an ACK, and A, C, and D transmitted, but ACK was not received.
  • a specific condition may be a method of continuously transmitting to the primary logical channel and the secondary logical channel emptying data and not transmitting.
  • FIG. 17 illustrates another embodiment of a procedure performed when packet duplication is released while performing data transmission by performing packet duplication (1700).
  • packet transmission is performed by performing packet duplication on logical channels 1 and 2 (1710, 1720)
  • a time point at which actual packet duplication is released according to various embodiments described in the description of FIGS. Indicates the action to be taken by.
  • packets A, C, and E receive an ACK on logical channel 1 (1710) at the moment when packet duplication is released, and B and D transmit, but ACK is not received, and packet B on logical channel 2 (1720).
  • E received an ACK, and A, C, and D transmitted, but ACK was not received.
  • a logical channel may be selected according to a specific condition.
  • a specific condition may be a method of continuously transmitting to the primary logical channel and the secondary logical channel emptying data and not transmitting.
  • the RLC device (or entity) of the logical channel 2 1720 notifies the RLC device of the logical channel 1 1710 that the packets successfully received the ACK are B and E.
  • the RLC device of 1710 may update the state of Packet B, which has not received an ACK, to a successful reception and may assume that the RLC device has successfully received.
  • the transmission of this information may directly inform the RLC sequence number (SN) of the packet transmitted from the RLC device of logical channel 2 1720 to the RLC device of logical channel 1 1720, or the RLC device of logical channel 2 1720
  • the PDCP sequence number (or RLC SN) of the packet is informed to the PDCP device of the radio bearer so that the PDCP device informs the RLC device of logical channel 1 (1710) the packet sequence number (RLC or PDCP SN). It may be. If the RLC sequence numbers of the logical channel 1 1710 and the logical channel 2 1720 for each packet are different, this value may be converted. At this time, the PDCP sequence number or PDCP COUNT value may be used in the process of conversion.
  • the RLC device of one logical channel may directly inform the RLC device of another logical channel of PDCP SN or PDCP COUNT information of the received packet with ACK or NACK of the corresponding packet.
  • FIG. 17 illustrates an embodiment in which a transmission state of each logical channel described above, that is, an RLC state information or an ACK reception state, is transmitted to another logical channel and reflected when the packet duplication transmission is released.
  • a transmission state of each logical channel described above that is, an RLC state information or an ACK reception state
  • such an operation is not limited to the time point at which the packet duplication transmission is released, and even in a situation in which normal packet duplication is performed, the procedure of reflecting the logical channel transmission between the logical channels can be performed.
  • the transmission of this information may directly inform the RLC sequence number (SN) of the packet transmitted from the RLC device of logical channel 2 1720 to the RLC device of logical channel 1 1720, or the RLC device of logical channel 2 1720
  • the PDCP order number of the corresponding packet may be informed to the PDCP device of the radio bearer so that the PDCP device informs the RLC device of logical channel 1 1710 of the corresponding packet order number. If the RLC sequence numbers of the logical channel 1 1710 and the logical channel 2 1720 for each packet are different, this value may be converted. At this time, the PDCP sequence number or PDCP COUNT value may be used in the process of conversion.
  • the transmission interval may be applied to a preset value so that this information transfer process does not occur too often.
  • the transmission status of a logical channel may be set to be transmitted from one logical channel to another every 10 ms.
  • Such an operation may also be applied to packet duplication applied to different HARQ devices in a HARQ situation instead of ARQ.
  • packet transmission may continue without packet duplication for packets that exist in the PDCP buffer and are not delivered to a lower layer such as an RLC.
  • PDCP PDU 1 1810 receives a packet arriving at the PDCP layer of the transmitter to the RLC layer, adds an RLC header, and then forwards to a lower layer below the MAC layer or is transmitting to the receiver.
  • PDCP PDU 2 1820 a packet arriving at the PDCP layer of the transmitter is delivered to the RLC layer and an RLC header is added, but it is not yet delivered to a lower layer below the MAC layer.
  • PDCP PDU 2 1820 may occur when a packet is pre-processed before being allocated radio resources of a UL grant.
  • PDCP PDU 3 1830 may be interpreted as a packet arriving at the PDCP layer of the transmitter does not request processing to the lower layer.
  • duplicate transmission may be started for packets that have not been delivered to the RLC layer among packets arriving at the PDCP layer of the transmitter.
  • PDCP PDU 3 1830 corresponds to this.
  • packets arriving at the PDCP layer of the transmitter are delivered to the RLC layer to which the RLC header is added, delivered to a lower layer below the MAC, or transmitted thereafter (eg, in FIG. 18).
  • PDCP PDU 1 1810) a packet arriving at the PDCP layer of the transmitter is delivered to the RLC layer to which an RLC header is added but not delivered to a lower layer below the MAC (for example, PDCP PDU 2 1820 of FIG. 18).
  • redundant transmission may be started for a packet (for example, PDCP PDU 3 18930 of FIG. 18) in which a packet arriving at the transmitter's PDCP layer is not delivered to the RLC layer.
  • the transmitter may transmit (or report) the packet information of the packet transmitted to the RLC layer, which has not been confirmed to be successfully received, to the PDCP layer.
  • the packet information transmitted to the PDCP layer may include a PDCP SN.
  • the transmitter may start packet duplication transmission by selecting packets corresponding to the received packet information.
  • an RLC or PDCP layer may manage which RLC sequence number (SN) and PDCP SN have a value. Based on this, the PDCP sequence number values of the packets in the RLC buffer that have not been successfully transmitted can be known.
  • radio bearers 1 and 2 do not duplicate packets and are mapped to logical channels 1 and 2, respectively. However, it is assumed that radio bearer 3 is mapped to logical channel 3 1910 and logical channel 4 1920 by applying packet overlap. Buffer status reporting is based on the buffer status of each logical channel. Therefore, at the time of sending the buffer status report, it is necessary to determine which buffer status should be sent to the logical channel with the packet duplication.
  • a logical channel may share the RLC state information or the ACK reception state described in the description of FIG. 17 before reporting the buffer status to another logical channel.
  • FIG. 20 illustrates another embodiment in which a terminal sends an uplink buffer status report to a base station when packet duplication is performed (2000).
  • radio bearers 1 and 2 do not duplicate packets and are mapped to logical channels 1 and 2, respectively.
  • radio bearer 3 is mapped to logical channel 3 (2010) and logical channel 4 (2020) by applying packet overlap.
  • Buffer status reporting is based on the buffer status of each logical channel. Therefore, at the time of sending the buffer status report, it is necessary to determine which buffer status should be sent to the logical channel with the packet duplication.
  • logical channel 4 (2020) set as a primary logical channel.
  • the base station may inform in advance which logical channel the terminal arbitrarily selects or which logical channel to use for buffer status reporting.
  • a logical channel may share the RLC state information or the ACK reception state described in the description of FIG. 17 before reporting the buffer status to another logical channel.
  • FIG. 21 illustrates an embodiment in which a terminal sends an uplink buffer status report to a base station when packet duplication is performed (2100).
  • radio bearers 1 and 2 do not have packet duplication and are mapped to logical channels 1 and 2, respectively.
  • radio bearer 3 is mapped to logical channel 3 2110 and logical channel 4 2120 by applying packet overlap.
  • Buffer status reporting is based on the buffer status of each logical channel. Therefore, at the time of sending the buffer status report, it is necessary to determine which buffer status should be sent to the logical channel with the packet duplication.
  • a logical channel may share the RLC state information or the ACK reception state described in the description of FIG. 17 before reporting the buffer status to another logical channel.
  • Packet duplication may be performed by applying the NumberOfDuplication described in FIG. 9, where the NumberOfDuplication field means to apply the number (or number of times) of packet duplication to a logical channel. In this case, it is necessary to apply a constant interval because too fast the packet duplication transmission can reduce the packet duplication efficiency.
  • the NumberOfDuplication value is set to 3, and when the packet is first transmitted, the duplication count is set to 3, which is the NumberOfDuplication value, to start the first transmission (2210). After that, the duplicated packet can be transmitted after the timer value set in advance, and the duplication count can be lowered to 2.
  • a duplicate packet may be transmitted after a predetermined timer value 2220 to reduce the duplication count to one. If duplication count is 0, no further duplicated packet transmission is performed (2240).
  • transmission of the duplicated packet may be performed by different logical channels or different HARQ devices.
  • FIG. 23 illustrates an embodiment of a format and a related embodiment of a duplication activation message defined in FIGS. 11 and 12 (2300).
  • the duplication activation message 2310 may be transmitted in a MAC CE (Control Element) format, and may be transmitted by indicating that the duplication activation message is displayed in the LCID (Logical Channel ID, Logical Channel ID) portion of the MAC CE.
  • LCID Logical Channel ID
  • a specific message may indicate that this message is a duplication activation message, and this message may be transmitted in DCI format.
  • the duplication activation message 2410 may be transmitted in a MAC CE (Control Element) format, and at this time, the duplication activation message 2410 may be transmitted by indicating that the duplication activation message is in the LCID (Logical Channel ID) portion of the MAC CE. Alternatively, if there is an ID field of the message in addition to the LCID, it may be displayed by indicating that it is a duplication activation message. Alternatively, a specific message may indicate that this message is a duplication activation message. In addition, a duplication activation message 2410 may be sent by adding an ID of a logical channel allowing packet duplication to the radio bearer. This message may also be sent in DCI format.
  • MAC CE Control Element
  • the duplication activation message 2410 may be transmitted by indicating that the duplication activation message is in the LCID (Logical Channel ID) portion of the MAC CE. Alternatively, if there is an ID field of the message in addition to the LCID, it may be displayed by indicating
  • FIG. 25 illustrates an exemplary embodiment of a format of a duplication activation message defined in FIGS. 11 and 12 (2500).
  • the duplication activation message 2510 may be transmitted in a MAC CE (Control Element) format, and at this time, the duplication activation message may be transmitted by indicating that it is a duplication activation message in the LCID (Logical Channel ID) portion of the MAC CE.
  • LCID Logical Channel ID
  • a specific message may indicate that this message is a duplication activation message.
  • it may be sent to the radio bearer including the CC information that allows packet duplication.
  • packet replication may be performed by activating a logical channel (or a logical channel mapped to the CC) that can be transmitted to the CC. This message may also be sent in DCI format.
  • FIG. 26 illustrates an exemplary embodiment of a format of a duplication deactivation message defined in FIGS. 11 and 12 (2600).
  • the duplication deactivation message 2610 may be transmitted in a MAC CE (Control Element) format, and may be transmitted by indicating that the duplication deactivation message is displayed in the LCID (Logical Channel ID, Logical Channel ID) portion of the MAC CE.
  • LCID Logical Channel ID
  • a specific message may indicate that this message is a duplication deactivation message, and such a message may be transmitted in DCI format.
  • FIG. 27 illustrates an embodiment of a format and a related embodiment of a duplication deactivation message defined in FIGS. 11 and 12 (2700).
  • the duplication deactivation message 2710 may be transmitted in a MAC CE (Control Element) format, and may be transmitted by indicating that the duplication deactivation message is in the LCID (Logical Channel ID, Logical Channel ID) portion of the MAC CE. Alternatively, if there is an ID field of the message in addition to the LCID, it may be displayed by indicating that it is a duplication deactivation message. Alternatively, a specific message may indicate that this message is a duplication deactivation message.
  • a duplication deactivation message 2710 may be transmitted by adding an ID of a logical channel to stop packet duplication to the radio bearer. This message may also be sent in DCI format.
  • FIG. 28 illustrates an embodiment of a format and a related embodiment of a duplication deactivation message defined in FIGS. 11 and 12 (2800).
  • the duplication deactivation message 2810 may be transmitted in a MAC CE (Control Element) format, and may be transmitted by indicating that the duplication deactivation message is in the LCID (Logical Channel ID) portion of the MAC CE.
  • LCID Logical Channel ID
  • a specific message may indicate that this message is a duplication deactivation message.
  • It may also send CC information to stop the packet duplication to the radio bearer.
  • packet replication may be stopped by deactivating a logical channel (or a logical channel mapped to the CC) that can be transmitted to the CC. This message may also be sent in DCI format.
  • FIG. 29 is a diagram illustrating another format of a packet redundancy enable / disable message according to an embodiment of the present invention (2900).
  • the duplication activation / deactivation message 2910 may be transmitted in a MAC CE format, and in this case, the duplication activation / deactivation message may be displayed on the LCID portion of the MAC CE.
  • FIG. 29 describes an embodiment of on-off, activating or deactivating packet duplication based on a duplication index. That is, as shown in FIG. 29, the duplication activation / deactivation message 2910 includes I1, I2,...
  • Duplication index of I8 is included, and each Duplication index may have a value of 1 (activated) or 0 (deactivated), and the values 1 and 0 may be reversed.
  • packet duplication is activated or deactivated based on the bitmap of the duplication index, thereby enabling / disabling packet duplication for a plurality of radio bearers / logical channels / CCs.
  • FIG. 30 illustrates another embodiment of a radio bearer setup message for packet duplication according to an embodiment of the present invention (3000).
  • a duplication index is allocated for each duplication radio bearer.
  • the duplication index value described in FIG. 29 is set to 1 to indicate activation, packet replication of the duplication radio bearer is activated.
  • FIG. 31 is a diagram illustrating another embodiment of a radio bearer setup message for packet duplication according to an embodiment of the present invention (3100).
  • a duplication index is allocated for each logical channel.
  • the duplication index value described in FIG. 29 is set to 1 to indicate activation, packet replication of the corresponding logical channel is activated.
  • the duplication index value is set to 0 to indicate deactivation, packet replication of the corresponding logical channel is deactivated.
  • the duplication activation message 3210 may be transmitted in the form of MAC CE (Control Element), and may be transmitted by indicating that the duplication activation message is in the LCID (Logical Channel ID) portion of the MAC CE. Alternatively, if there is an ID field of the message in addition to the LCID, it may be displayed by indicating that it is a duplication activation message. Alternatively, a specific message may indicate that this message is a duplication activation message.
  • the duplication activation message may be transmitted with an ID of a radio bearer that allows packet duplication. At this time, packet replication may be performed on the data packet transmitted through the corresponding radio bearer. This message may also be sent in DCI format.
  • the duplication deactivation message 3310 may be transmitted in a MAC CE (Control Element) format, and may be transmitted by indicating that the duplication deactivation message is in the LCID (Logical Channel ID, Logical Channel ID) portion of the MAC CE. Alternatively, if there is an ID field of the message in addition to the LCID, it may be displayed by indicating that it is a duplication deactivation message. Alternatively, a specific message may indicate that this message is a duplication deactivation message.
  • the duplication deactivation message may include an ID of a radio bearer that stops packet duplication separately and may be transmitted. At this time, packet replication for data packets transmitted through the corresponding radio bearer may be stopped / stopped. This message may also be sent in DCI format.
  • the duplication activation message 3410 may be transmitted in a MAC CE (Control Element) format, and may be transmitted by indicating that the duplication activation message is in the LCID (Logical Channel ID) portion of the MAC CE. Alternatively, if there is an ID field of the message in addition to the LCID, it may be displayed by indicating that it is a duplication activation message. Alternatively, a specific message may indicate that this message is a duplication activation message.
  • MAC CE Control Element
  • LCID Logical Channel ID
  • the duplication activation message may include a plurality of logical channel IDs and an E field for each logical channel ID, and when the specific E field has a value of 1 (or 0), the logic corresponding to the corresponding E field may be transmitted.
  • the channel ID may be added to the next byte.
  • the RadioBearerID may be included in the duplication activation message instead of the plurality of logical channel IDs. This message may also be sent in DCI format.
  • the duplication deactivation message 3510 may be transmitted in a MAC CE (Control Element) format, and may be transmitted by indicating that the duplication deactivation message is in the LCID (Logical Channel ID, Logical Channel ID) portion of the MAC CE. Alternatively, if there is an ID field of the message in addition to the LCID, it may be displayed by indicating that it is a duplication deactivation message. Alternatively, a specific message may indicate that this message is a duplication deactivation message.
  • MAC CE Control Element
  • LCID Logical Channel ID
  • a specific message may indicate that this message is a duplication deactivation message.
  • the duplication deactivation message may include a plurality of logical channel IDs and an E field for each logical channel ID, and when a specific E field has a value of 1 (or 0), the logic corresponding to the corresponding E field may be transmitted.
  • the channel ID may be added to the next byte.
  • the Duplication Deactivation message may include RadioBearerID instead of the plurality of logical channel IDs. This message may also be sent in DCI format.
  • the duplication carrier mapping message 3610 may be transmitted in a MAC CE (Control Element) format, and may be transmitted by indicating that it is a duplication carrier mapping message in the LCID (Logical Channel ID) portion of the MAC CE. Alternatively, if there is an ID field of the message in addition to the LCID, this may be indicated by a duplication carrier mapping message and transmitted. Alternatively, a specific message may indicate that this message is a duplication carrier mapping message.
  • MAC CE Control Element
  • LCID Logical Channel ID
  • the UE may change the mapping between the logical channel and the CC by receiving the duplication carrier mapping message 3610 of FIG. 36. However, even if the mapping between the logical channel and the CC is changed, the retransmission (for example, HARQ) operation in progress in the specific logical channel may be performed as it is.
  • the UE determines whether a triggering condition of a measurement report set in advance is met and measures a reference signal (RS), etc. (S3710). At this time, if the measured value satisfies the triggering condition (S3720), the terminal sends a measurement report message to the base station (S3730), and based on this, the base station instructs radio bearer setup for packet duplication (S3740).
  • This setting may be in the message format of FIG. 9 and some of the fields included in FIG. 9 may be applied.
  • the terminal and the base station may set up a radio bearer that performs packet duplication (S3750).
  • the format of this bearer may be one of the formats described in FIGS. 3-8.
  • 38 is a diagram illustrating a terminal according to an embodiment of the present invention (3800).
  • the terminal 3800 may include a transceiver 3810 and a controller 3830.
  • the controller 3830 may include at least one processor.
  • the transceiver 3810 and the controller 3830 may be electrically connected to each other.
  • the controller 3830 may control the transceiver 3810 to transmit and receive a signal. Transmitting and / or receiving a signal, information, a message, etc. by the controller 3830 may be interpreted by the controller 3830 controlling the transceiver 3810 to transmit and / or receive a signal, a message, and the like.
  • the terminal 3800 may transmit and / or receive a signal through the transceiver 3810.
  • the controller 3830 may control the overall operation of the terminal 3800.
  • the controller 3830 may control the operation of the terminal described with reference to FIGS. 1 to 37.
  • 39 is a diagram illustrating a base station according to an embodiment of the present invention (3900).
  • the base station 3900 may include a transceiver 3910 and a controller 3930.
  • the controller 3930 may include at least one processor.
  • the transceiver 3910 and the controller 3930 may be electrically connected to each other.
  • the controller 3930 may control the transceiver 3910 to transmit and receive a signal. Transmitting and / or receiving a signal, information, a message, etc. by the controller 3930 may be interpreted as the controller 3930 controlling the transceiver 3910 to transmit and / or receive a signal, a regular message, and the like.
  • the base station 3900 may transmit and / or receive a signal through the transceiver 3910.
  • the controller 3930 may control overall operations of the base station 3900.
  • the controller 3930 may control the operation of the base station described with reference to FIGS. 1 to 37.
  • 40 is an embodiment of a bearer structure for packet redundancy (4000).
  • one radio bearer is set to allow packet duplication and a radio bearer ID value is set to x.
  • the base station and the terminal may have one or more Signaling Radio Bearer (SRB) and Data Radio Bearer (Data Radio Bearer).
  • SRB Signaling Radio Bearer
  • Data Radio Bearer Data Radio Bearer
  • 40 illustrates that a PDCP device (or entity) of a radio bearer replicates a PDCP PDU (Protocol Data Unit) and then sends each replicated PDCP PDU to different RLC devices for processing.
  • Each RLC device is mapped to a logical channel respectively.
  • each logical channel ID is represented by y1 4010 and y2 4020.
  • mapping with a cell is necessary for efficient packet transmission.
  • a logical channel and a cell it is possible to limit the cells to which specific logical channel data can be sent.
  • Such a cell may be replaced with a component carrier (CC), a band width part (BWP), or the like.
  • CC component carrier
  • BWP band width part
  • logical channel 4010 with logical channel ID y1 is mapped to PCell (or PSCell, having PSCell if it is a secondary cell group) and SCell2, and logical channel 4020 with logical channel ID y2 is SCell3. Is mapped to.
  • data packets copied through packet duplication may be prevented from being transmitted to the same cell (or the same CC, the same BWP) even though the MAC device (entity) undergoes multiplexing.
  • the MAC device entity
  • two or more data packets duplicated in the same MAC PDU are not included, and the original PDCP PDU and the duplicated PDCP PDU are not transmitted in the same transport block.
  • the primary logical channel and the secondary logical channel described above with reference to FIGS. 5, 6, 9, 30, and 31 may be configured for bearers allowed for packet duplication.
  • the primary logical channel always transmits / receives a packet regardless of enabling packet redundancy, but the secondary logical channel transmits / receives a packet only when packet redundancy is enabled. That is, when packet redundancy is activated, the same PDCP PDU is transmitted on the primary logical channel and the secondary logical channel, respectively.
  • the PDCP PDUs may be called original PDCP PDUs and cloned PDCP PDUs, respectively. If packet redundancy is disabled, the PDCP PDUs are sent only on the primary logical channel.
  • the RLC device of the secondary logical channel may be re-establihsment.
  • Whether a specific logical channel is a primary logical channel or a secondary logical channel may be designated by an RRC configuration (RRC configuration) or the like, but may define a rule for distinguishing when the configuration is not necessary.
  • RRC configuration RRC configuration
  • the primary logical channel can be determined using one of the following rules:
  • -Logical channel with small logical channel ID value becomes primary logical channel. If there are three or more logical channels, the logical channel with the smallest logical channel ID value becomes the primary logical channel. The remaining logical channels become secondary logical channels.
  • -A logical channel with a large logical channel ID value becomes a primary logical channel. If there are three or more logical channels, the logical channel with the largest logical channel ID value becomes the primary logical channel. The remaining logical channels become secondary logical channels.
  • FIG. 41 illustrates a procedure of processing a packet corresponding to a bearer allowed for packet duplication (4100).
  • the receiver transmits the packet to the corresponding logical channel to process the packet (S4120, S4130). If the packet duplication is inactivated state, it is possible to check whether the corresponding packet corresponds to the primary logical channel (S4120, S4140), and if the packet is a primary logical channel, the packet is transmitted to the corresponding logical channel to be processed (S4130). Otherwise, this may be determined as a packet of the secondary logical channel, and the packet is discarded and not transmitted to the logical channel (S4150).
  • the MAC subheader informs the information of MAC layer data called MAC SDU (Service Data Unit).
  • the MAC subheader may include an R (Reserved, Reserved), F (Format, Format), LCID (Logical Channel ID, Logical Channel ID), L (Length, Length) field.
  • the R field is a reserved field and is usually set to 0, which is a default value.
  • the F field indicates the length of the L field.
  • the LCID field indicates a logical channel ID of data (MAC SDU).
  • the L field indicates the length of the MAC SDU. Normally, this value should be set to the correct value, and if an unset value (invalid value) is set, it can be considered that there is an error in the packet. For example, when the R field is set to 1, it may be treated as an unused value.
  • FIG. 43 illustrates a procedure of a receiver when a packet is received (4300).
  • the embodiment of FIG. 43 illustrates an embodiment of processing when a MAC PDU is received by a MAC entity.
  • the received MAC PDU may include a MAC SDU (S4310).
  • S4310 MAC SDU
  • At this time at least one unused value may be included in the MAC PDU.
  • the SDU including the corresponding value or its subheader can be checked. If the SDU cannot be identified correctly, the entire received MAC PDU can be discarded. Otherwise, if the MAC SDU can be identified, the MAC SDU or subheader is checked for unused values.
  • data is sent to the corresponding logical channel to process the packet (S4320, S4330). If the unused value is included, it is necessary to check whether the value is the LCID field used in the last RRC reset (the last reset of the last RRC reset) (S4320, S4340). If the LCID field was used for the last RRC reset, it may be a part generated before the latest RRC reset, and this part may not be an error in the transmission / reception process. In other words, the value used in the last reset may be a value not used by the last reset. In this case, only the corresponding MAC SDU may be discarded (S4350).
  • the unused value is an ID of a logical channel in which packet duplication is inactivated, it may be data generated when packet duplication is activated or data transmitted by a transmitter not aware of the deactivation. If such packet duplication is allowed, but the ID of the inactive logical channel is included, only the corresponding MAC SDU may be discarded (S4360, S4350). If an unused value other than the case described above is included, the entire MAC PDU may be discarded (S4360, S4370).

Abstract

L'invention concerne une technique de communication qui fusionne une technologie d'IoT avec un système de communication 5G pour prendre en charge un débit de transmission de données supérieur à un système 4G ainsi qu'un système associé. L'invention peut être appliquée à des services intelligents (par exemple maisons intelligentes, bâtiments intelligents, villes intelligentes, voitures intelligentes ou voitures connectées, soins de santé, enseignement numérique, commerce de détail, services de sécurité et de sûreté et autres) basés sur la technologie de communication 5G et la technologie apparentée à l'IoT. L'invention concerne un système de communication 5G ou pré-5G destiné à prendre en charge un débit de transmission de données supérieur à un système de communication 4G, tel que LTE. Un mode de réalisation de l'invention concerne un procédé et une structure destinés à traiter des données pour une duplication de paquets. Selon le mode de réalisation de l'invention, l'invention concerne un procédé d'établissement de support radio, une opération de duplication de paquets et un procédé de rapport d'état de tampon, qui sont destinés à être utilisés dans la réalisation d'une duplication de paquets.
PCT/KR2018/002264 2017-03-23 2018-02-23 Procédé et appareil de traitement de données pour une duplication de paquets WO2018174418A1 (fr)

Priority Applications (7)

Application Number Priority Date Filing Date Title
CN201880020299.3A CN110463255B (zh) 2017-03-23 2018-02-23 用于处理用于分组复制的数据的方法和设备
CN202310580157.5A CN116567716A (zh) 2017-03-23 2018-02-23 用于处理用于分组复制的数据的方法和设备
EP18772600.5A EP3589009B1 (fr) 2017-03-23 2018-02-23 Procédé et appareil de traitement de données pour une duplication de paquets
EP21191862.8A EP3934314B1 (fr) 2017-03-23 2018-02-23 Procédé et appareil de traitement de données pour une duplication de paquets
US16/496,940 US11140571B2 (en) 2017-03-23 2018-02-23 Method and apparatus for processing data for packet duplication
US17/486,761 US11700542B2 (en) 2017-03-23 2021-09-27 Method and apparatus for processing data for packet duplication
US18/349,816 US20230354084A1 (en) 2017-03-23 2023-07-10 Method and apparatus for processing data for packet duplication

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
KR10-2017-0036822 2017-03-23
KR20170036822 2017-03-23
KR20170075075 2017-06-14
KR10-2017-0075075 2017-06-14
KR1020170126578A KR102357594B1 (ko) 2017-03-23 2017-09-28 패킷 중복을 위한 데이터 처리 방법 및 장치
KR10-2017-0126578 2017-09-28

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US16/496,940 A-371-Of-International US11140571B2 (en) 2017-03-23 2018-02-23 Method and apparatus for processing data for packet duplication
US17/486,761 Continuation US11700542B2 (en) 2017-03-23 2021-09-27 Method and apparatus for processing data for packet duplication

Publications (1)

Publication Number Publication Date
WO2018174418A1 true WO2018174418A1 (fr) 2018-09-27

Family

ID=63586155

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2018/002264 WO2018174418A1 (fr) 2017-03-23 2018-02-23 Procédé et appareil de traitement de données pour une duplication de paquets

Country Status (3)

Country Link
US (2) US11700542B2 (fr)
CN (1) CN116567716A (fr)
WO (1) WO2018174418A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110972335A (zh) * 2018-09-29 2020-04-07 华为技术有限公司 一种模式切换方法、数据流分流方法及装置
CN111510950A (zh) * 2019-01-31 2020-08-07 电信科学技术研究院有限公司 传输处理方法、终端及网络设备

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113015215B (zh) * 2018-03-29 2022-12-23 维沃移动通信有限公司 数据发送方法及用户设备
US11304092B2 (en) * 2018-09-12 2022-04-12 Ofinno, Llc Session packet duplication control
EP3876618A4 (fr) * 2018-10-31 2022-06-08 Ntt Docomo, Inc. Équipement d'utilisateur et appareil de station de base
CN111436066A (zh) * 2019-02-14 2020-07-21 维沃移动通信有限公司 数据包承载路径确定、信息发送方法和设备
US11805446B2 (en) * 2019-03-25 2023-10-31 Lg Electronics Inc. Conditional supplementary link activation and transmission
CN117715208A (zh) * 2019-03-29 2024-03-15 华为技术有限公司 一种数据传输方法及装置
US20220201639A1 (en) * 2019-04-02 2022-06-23 Telefonaktiebolaget Lm Ericsson (Publ) Ims registration
US11678314B2 (en) * 2019-06-24 2023-06-13 Qualcomm Incorporated Packet duplication carrier enhancements

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20100122054A (ko) * 2009-05-11 2010-11-19 엘지전자 주식회사 다중 반송파를 지원하는 무선 통신 시스템에서 중복 데이터를 송신 및 수신하는 방법 및 장치
US20160094446A1 (en) * 2013-05-16 2016-03-31 Zaigham Kazmi Multiple radio link control (rlc) groups
KR20160095203A (ko) * 2012-11-07 2016-08-10 퀄컴 인코포레이티드 듀얼 접속의 버퍼 상태 리포팅 및 로직 채널 우선순위화

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU2004319437B2 (en) 2004-05-07 2009-03-05 Telefonaktiebolaget L M Ericsson (Publ) Lossless radio link control entity (RLC) re-establishment avoiding service data unit (SDU) duplication
WO2008054158A2 (fr) 2006-11-01 2008-05-08 Lg Electronics Inc. Procédé et transmission et de réception de données liaison descendante dans un système de communication sans fil
US8989004B2 (en) 2010-11-08 2015-03-24 Qualcomm Incorporated System and method for multi-point HSDPA communication utilizing a multi-link PDCP sublayer
CN110691425B (zh) 2013-10-29 2023-04-07 三星电子株式会社 在移动通信系统中的终端、基站及其方法
KR102157798B1 (ko) 2013-10-29 2020-09-18 삼성전자 주식회사 이동 통신 시스템에서 복수의 캐리어를 이용하는 데이터 송수신 방법 및 장치
US10004098B2 (en) 2014-01-29 2018-06-19 Samsung Electronics Co., Ltd. Method and apparatus for transmitting and receiving data using a plurality of carriers in mobile communication system
EP3417664A1 (fr) 2016-02-18 2018-12-26 Nokia Solutions and Networks Oy Sélection de liaison montante pour réseau sans fil, sur la base de la pondération de cellule(s) de réseau et de la pondération spécifique de liaison pour des liaisons sans fil
US10986530B2 (en) * 2017-03-10 2021-04-20 Kt Corporation Buffer state report transmission method and device therefor
EP3603322B1 (fr) 2017-03-24 2023-08-16 Nokia Technologies Oy Gestion de duplication de pdcp et de récupération de données dans une nouvelle technologie d'accès radio

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20100122054A (ko) * 2009-05-11 2010-11-19 엘지전자 주식회사 다중 반송파를 지원하는 무선 통신 시스템에서 중복 데이터를 송신 및 수신하는 방법 및 장치
KR20160095203A (ko) * 2012-11-07 2016-08-10 퀄컴 인코포레이티드 듀얼 접속의 버퍼 상태 리포팅 및 로직 채널 우선순위화
US20160094446A1 (en) * 2013-05-16 2016-03-31 Zaigham Kazmi Multiple radio link control (rlc) groups

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Data duplication in lower layers (HARQ", R2-1702032, 3GPP TSG-RAN WG2 #97, 20 February 2017 (2017-02-20), XP051212561 *
HUAWEI: "Redundancy Schemes below PDCP Layer", R2-1701201, 3GPP TSG-RAN2 MEETING #97, 4 February 2017 (2017-02-04), XP051211890 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110972335A (zh) * 2018-09-29 2020-04-07 华为技术有限公司 一种模式切换方法、数据流分流方法及装置
EP3852481A4 (fr) * 2018-09-29 2021-11-10 Huawei Technologies Co., Ltd. Procédé de commutation de mode et procédé et appareil de distribution de flux de données
CN110972335B (zh) * 2018-09-29 2022-04-12 华为技术有限公司 一种模式切换方法、数据流分流方法及装置
CN111510950A (zh) * 2019-01-31 2020-08-07 电信科学技术研究院有限公司 传输处理方法、终端及网络设备
CN111510950B (zh) * 2019-01-31 2021-12-17 大唐移动通信设备有限公司 传输处理方法、终端及网络设备

Also Published As

Publication number Publication date
US11700542B2 (en) 2023-07-11
US20220014961A1 (en) 2022-01-13
US20230354084A1 (en) 2023-11-02
CN116567716A (zh) 2023-08-08

Similar Documents

Publication Publication Date Title
WO2018174418A1 (fr) Procédé et appareil de traitement de données pour une duplication de paquets
WO2018230920A1 (fr) Procédé et appareil de commande de transmission de paquet
WO2020027599A1 (fr) Procédé et dispositif de gestion de la transmission de paquets dupliqués dans un système de communication sans fil
WO2016163690A1 (fr) Procédé de prise en charge d'une harq dans un système de communication à l'aide d'une bande de fréquences sans licence et dispositif intégrant le procédé appliqué
WO2010131850A2 (fr) Procédé et appareil d'émission et de réception de données doubles dans un système de communication sans fil multiporteuse
WO2019035645A2 (fr) Procédé et système de gestion de duplication de paquets et de reprise de rb dans un système de communication sans fil
WO2015111965A1 (fr) Système et procédé de transmission de données de priorité d'une pluralité de stations de base
WO2021071234A1 (fr) Procédé et dispositif de sélection de ressource psfch dans une v2x nr
WO2021215829A1 (fr) Procédé et appareil permettant d'effectuer une transmission de psfch dans une v2x en nr
WO2022086239A1 (fr) Procédé et système de gestion d'opérations sans perte pour mbs dans un réseau de communication 5g
WO2021125712A1 (fr) Procédé et appareil de gestion de temporisateur associé à la transmission de segmentation d'un message rrc dans un système de communication mobile de prochaine génération
WO2017026847A1 (fr) Dispositif et procédé de traitement d'une pluralité de demandes de ressources dans un système de communication sans fil
WO2022014992A1 (fr) Procédé et dispositif d'opération sps pour réception mbs
WO2021206496A1 (fr) Procédé et appareil permettant d'effectuer des communication sl mode 1 en nr v2x
WO2021071244A1 (fr) Procédé et appareil pour transmettre une rétroaction harq à la station de base dans nr v2x
WO2022030975A1 (fr) Procédé et appareil permettant d'effectuer une communication de liaison latérale (sl) en fonction de ressources attribuées par une station de base en v2x nr
WO2021066613A1 (fr) Procédé et dispositif permettant de transmettre un bloc de transport dans v2x nr
WO2019160248A1 (fr) Appareil et procédé de traitement de paquets dans un système de communication sans fil
WO2022086184A1 (fr) Procédé et appareil de rapport d'informations csi de liaison latérale dans un système nr v2x
WO2022080843A1 (fr) Procédé et dispositif de détermination d'une ressource dans v2x nr
WO2022031147A1 (fr) Procédé et appareil pour réaliser une communication de liaison latérale nr sur une porteuse lte
WO2021145585A1 (fr) Procédé et dispositif de transmission et de réception de données de liaison latérale dans un système de communication
WO2021071243A1 (fr) Procédé et dispositif de rapport de rétroaction harq à la station de base dans nr v2x
WO2021040435A1 (fr) Procédé et appareil permettant de réaliser une réservation de ressources par terminal dans v2x nr
WO2015065039A1 (fr) Procédé et appareil de transmission/réception de données à l'aide d'une pluralité de porteuses dans un système de communication mobile

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018772600

Country of ref document: EP

Effective date: 20190923