WO2015065039A1 - 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 - Google Patents

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 Download PDF

Info

Publication number
WO2015065039A1
WO2015065039A1 PCT/KR2014/010243 KR2014010243W WO2015065039A1 WO 2015065039 A1 WO2015065039 A1 WO 2015065039A1 KR 2014010243 W KR2014010243 W KR 2014010243W WO 2015065039 A1 WO2015065039 A1 WO 2015065039A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
cell group
terminal
cell
pdcp
Prior art date
Application number
PCT/KR2014/010243
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 KR1020140038857A external-priority patent/KR102157798B1/ko
Application filed by 삼성전자 주식회사 filed Critical 삼성전자 주식회사
Priority to EP14857431.2A priority Critical patent/EP3065449B1/fr
Priority to EP21176384.2A priority patent/EP3927010A1/fr
Priority to US15/033,579 priority patent/US10149175B2/en
Priority to ES14857431T priority patent/ES2878127T3/es
Priority to CN201910940891.1A priority patent/CN110691425B/zh
Priority to CN201480059854.5A priority patent/CN105684501B/zh
Publication of WO2015065039A1 publication Critical patent/WO2015065039A1/fr
Priority to US16/206,897 priority patent/US11026102B2/en
Priority to US17/334,585 priority patent/US20210289368A1/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/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H04W28/065—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information using assembly or disassembly of packets
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • 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
    • 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
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup

Definitions

  • the present invention relates to a mobile communication system, and more particularly, to a method and apparatus for transmitting and receiving data using a plurality of carriers in a mobile communication system.
  • a mobile communication system has been developed for the purpose of providing communication while securing user mobility.
  • Such a mobile communication system has reached a stage capable of providing high-speed data communication service as well as voice communication due to the rapid development of technology.
  • the LTE system is a technology for implementing a high-speed packet-based communication having a transmission rate of up to 100 Mbps higher than the currently provided data rate and is almost standardized.
  • Carrier aggregation is a representative example of the new technology to be introduced.
  • Carrier aggregation means that a terminal uses a plurality of forward carriers and a plurality of reverse carriers, unlike a conventional terminal that transmits and receives data using only one forward carrier and one reverse carrier.
  • the present invention provides a method for transmitting and receiving data of a terminal, the method comprising: receiving a first control message from a first base station for controlling a first cell group; Adding a second cell group controlled by a second base station based on the first control message; Determining a bearer type for the first and second cell groups based on the first control message; If the determined bearer type is a first bearer type, receiving data through the first and second cell groups and transmitting data through any one of the first or second cell groups. It is characterized by.
  • the present invention also provides a method for transmitting and receiving data of a base station controlling a first cell group, the method comprising: determining whether to add a second cell group with another base station; Transmitting a first control message including a command for adding the second cell group controlled by the other base station and bearer type information for the first and second cell groups to the terminal; When the bearer type for the first cell and the second cell group is a first bearer type, transmitting data to the terminal through the first cell group; And when the bearer type for the first cell and the second cell group is the first bearer type, when the first cell group is selected based on uplink mode information, data from the terminal through the first cell group; Characterized in that it comprises the step of receiving.
  • the present invention in the data transmission and reception method of the base station controlling the second cell group, it is determined whether to add another base station and the second cell group to control the first cell group set in the terminal; Making; Transmitting data to the terminal through the second cell group when the bearer type for the first cell and the second cell group is a first bearer type based on a first control message set by the other base station; And when the bearer type for the first cell and the second cell group is the first bearer type, based on the first control message set by the other base station, the uplink mode information included in the first control message is determined. And indicating a second cell group, receiving data from the terminal through the second cell group.
  • the terminal for transmitting and receiving signals with the first and second base station; And receiving a first control message from the first base station controlling the first cell group, adding a second cell group controlled by the second base station based on the first control message, and adding to the first control message.
  • a control unit for controlling to transmit data through any one of the cell groups.
  • the base station for controlling the first cell group, the base station and the transceiver for transmitting and receiving signals with other base stations; And a command for determining whether to add the second cell group with the other base station, and adding a second cell group controlled by the other base station and bearer type information for the first and second cell groups.
  • the control message is transmitted to the terminal, and when the bearer type for the first cell and the second cell group is the first bearer type, data is transmitted to the terminal through the first cell group, and the first cell and the first cell are transmitted.
  • a control unit for controlling to receive data from the terminal through the first cell group when the first cell group is selected based on uplink mode information when the bearer type for the second cell group is the first bearer type. Characterized in that.
  • the base station for controlling the second cell group, the base station and the transceiver for transmitting and receiving signals with other base stations; And determining whether to add the other base station and the second cell group to control the first cell group configured in the terminal, and to the first cell and the second cell group based on the first control message set by the other base station. If the bearer type is a first bearer type, data is transmitted to the terminal through the second cell group, and based on the first control message set by the other base station, the first cell and the second cell group When the bearer type is the first bearer type, if the uplink mode information included in the first control message indicates the second cell group, the controller controls to receive data from the terminal through the second cell group. It is characterized by including.
  • a transmission / reception speed of a terminal may be improved.
  • FIG. 1 is a diagram illustrating a structure of an LTE system to which some embodiments of the present specification are applied.
  • FIG. 2 is a diagram illustrating a radio protocol structure in an LTE system to which some embodiments of the present disclosure are applied.
  • FIG. 3 is a diagram illustrating carrier aggregation in a base station to which some embodiments of the present disclosure are applied.
  • FIG. 4 illustrates a carrier aggregation scheme according to an embodiment of the present disclosure.
  • 5 is a view for explaining the structure of a radio bearer.
  • FIG. 6 is a diagram illustrating an uplink structure of a radio bearer.
  • FIG. 7 is a diagram illustrating an operation of a terminal that receives an uplink grant.
  • FIG. 8 is a diagram illustrating an operation of determining priority of PDCP data of multiple LCH bearers.
  • FIG. 9 is a diagram illustrating an operation of a terminal performing a scheduling request when PDCP data is generated.
  • FIG. 10 is a diagram illustrating a situation in which data arrives at a PDCP device of a multiple LCH bearer.
  • FIG. 11 is a diagram illustrating an example of a PDCP device order reordering operation of multiple LCH bearers.
  • FIG. 12 illustrates another example of a PDCP device order reordering operation of multiple LCH bearers.
  • FIG. 13 is a diagram illustrating an operation of processing a PDCP packet by a PDCP device of a multiple LCH bearer.
  • FIG. 14 is a diagram illustrating an order reordering operation of a PDCP device.
  • 15 is a diagram illustrating the overall operation of setting up and releasing multiple RLC bearers.
  • 16 is a diagram illustrating an operation of a PDCP device processing a PDCP packet.
  • 17 is a diagram illustrating a terminal device.
  • FIG. 18 is a diagram illustrating a base station apparatus.
  • FIG. 19 is a diagram illustrating an operation of determining, by a terminal, PDCP data to be reflected in a BS of an LCG when a PDCP is associated with two or more LCGs.
  • FIG. 1 is a diagram illustrating a structure of an LTE system to which some embodiments of the present specification are applied.
  • a radio access network of an LTE system includes a next-generation base station (Evolved Node B, ENB, Node B or base station) 105, 110, 115, and 120, an MME 125, and a Mobility Management Entity (S-GW). (130, Serving-Gateway).
  • the user equipment (hereinafter referred to as UE or terminal) 135 connects to an external network through the ENBs 105, 110, 115, and 120 and the S-GW 130.
  • the ENBs 105, 110, 115, and 120 correspond to existing Node Bs of the UMTS system.
  • the ENBs 105, 110, 115, and 120 are connected to the UE 135 via a radio channel and perform a more complex role of the existing Node B.
  • all user traffic including real-time services such as Voice over IP (VoIP) over the Internet protocol, is serviced through a shared channel, so state information such as UE buffer status, available transmit power status, and channel status
  • VoIP Voice over IP
  • One ENB 105, 110, 115, 120 typically controls a number of cells.
  • the LTE system uses Orthogonal Frequency Division Multiplexing (OFDM) as a radio access technology in a 20 MHz bandwidth.
  • OFDM Orthogonal Frequency Division Multiplexing
  • the ENBs 105, 110, 115, and 120 may use adaptive modulation & coding (hereinafter, referred to as adaptive modulation & coding) to determine a modulation scheme and a channel coding rate according to the channel state of the terminal 135.
  • adaptive modulation & coding adaptive modulation & coding
  • the S-GW 130 is a device that provides a data bearer, and generates or removes a data bearer under the control of the MME 125.
  • the MME 125 is a device that is responsible for various control functions as well as mobility management function for the terminal 135 is connected to a plurality of base stations.
  • FIG. 2 is a diagram illustrating a radio protocol structure in an LTE system to which some embodiments of the present disclosure are applied.
  • a wireless protocol of an LTE system includes packet data convergence protocols 205 and 240 (PDCP), radio link control 210 and 235 (RMC), and medium access control 215 and 230 (MAC) in a terminal and an ENB, respectively.
  • PDCP packet data convergence protocols
  • RMC radio link control 210 and 235
  • MAC medium access control 215 and 230
  • the PDCP (Packet Data Convergence Protocol) 205, 240 is responsible for operations such as IP header compression / restore, and the radio link control (hereinafter referred to as RLC) 210, 235 is a PDCP PDU (Packet Data Unit). ) Is reconfigured to an appropriate size to perform ARQ operations.
  • the MACs 215 and 230 are connected to several RLC layer devices configured in one terminal, and multiplex RLC PDUs to MAC PDUs and demultiplex RLC PDUs from MAC PDUs.
  • the physical layers 220 and 225 channel-code and modulate higher layer data, make an OFDM symbol, and transmit it to a wireless channel, or demodulate, channel decode, and transmit the received OFDM symbol through a wireless channel to a higher layer. .
  • FIG. 3 is a diagram illustrating carrier aggregation in a base station.
  • one base station can generally transmit and receive multiple carriers over several frequency bands. For example, when a carrier 315 having a forward center frequency of f1 and a carrier 310 having a forward center frequency of f3 are transmitted from the base station 305, one terminal conventionally uses one carrier of the two carriers. To transmit and receive data. However, a terminal having carrier aggregation capability may transmit and receive data through multiple carriers at the same time. The base station 305 may increase the transmission speed of the terminal 330 by allocating more carriers to the terminal 330 having carrier aggregation capability according to a situation. As described above, integrating forward and reverse carriers transmitted and received by one base station is called carrier aggregation in the base station. However, in some cases, unlike in FIG. 3, it may be necessary to integrate forward and reverse carriers transmitted and received from different base stations.
  • FIG. 4 is a diagram illustrating an inter-base station carrier in a carrier aggregation method according to an embodiment of the present specification.
  • the terminal 430 when the base station 1 405 transmits and receives a carrier having a center frequency of f1 and the base station 2 415 transmits and receives a carrier having a center frequency of f2, the terminal 430 has a carrier having a forward center frequency of f1.
  • the forward center frequency is integrated (combined) with the f2 carrier, one terminal is integrated with the carriers transmitted and received from two or more base stations, and in the present specification, this is referred to as inter-ENB carrier aggregation (or inter-base station). It is called CA).
  • carrier aggregation is understood as a terminal transmitting and receiving data through multiple cells at the same time. May be At this time, the maximum transmission rate increases in proportion to the number of carriers integrated.
  • the terminal receiving data through any forward carrier or transmitting data through any reverse carrier means that the control channel and the data channel provided by the cell corresponding to the center frequency and the frequency band characterizing the carrier It has the same meaning as transmitting and receiving data using.
  • carrier aggregation will be expressed in particular as 'multiple serving cells are set', and terms such as primary serving cell (hereinafter referred to as PCell) and secondary serving cell (hereinafter referred to as SCell), or activated serving cell will be used. .
  • PCell primary serving cell
  • SCell secondary serving cell
  • activated serving cell activated serving cell
  • a set of serving cells controlled by the same base station is defined as a cell group or a carrier group (CG).
  • the cell group is further divided into a master cell group (MCG) and a secondary cell group (SCG).
  • MCG means a set of serving cells controlled by a base station (hereinafter referred to as a master base station, MeNB) that controls a PCell
  • SCG means a base station that does not control a PCell, that is, a base station that controls only SCells (hereinafter referred to as a slave base station, Means a set of serving cells controlled by the SeNB).
  • a predetermined serving cell belongs to the MCG or the SCG is set by the base station in the process of setting the serving cell.
  • One MCG and one or more SCGs may be configured in one UE.
  • only one SCG is set for convenience of description. However, even if one or more SCGs are set, the contents of the present invention may not be changed. It can be applied as is.
  • serving cell 410 with center frequency f1 is serving cell belonging to MCG and serving cell 420 with center frequency f2. It is a serving cell belonging to this SCG.
  • MCG and SCG may be used instead of MCG and SCG for understanding.
  • terms such as a primary set and a secondary set or a primary carrier group and a secondary carrier group may be used.
  • a primary set and a secondary set or a primary carrier group and a secondary carrier group may be used.
  • the main purpose of the use of these terms is to distinguish which cell is under the control of the base station controlling the PCell of a specific terminal, and for the case where the cell is under the control of the base station controlling the PCell of a specific terminal or not And the operation of the corresponding cell may vary.
  • one user service is serviced by one Evolved Packet System (EPS) bearer, and one EPS bearer is connected to one radio bearer.
  • the radio bearer is composed of PDCP and RLC.
  • a PDCP device and an RLC device of one radio bearer may be located at different base stations to increase data transmission and reception efficiency.
  • different approaches are needed according to the type of user service.
  • the user service may form two RLC devices such as 515 to transmit and receive data with both the MeNB and the SeNB.
  • the user service can only send and receive data using only the serving cell of the MeNB by placing an RLC device only in the MeNB, such as 505. If there is a large data service but no available transmission resources in the macro cell, the user service can send and receive data using only the serving cell of the SeNB by placing the RLC device only in the SeNB as shown in 510.
  • 505 is designated as a single LCH MCG bearer (single-LCH-MCG-RB)
  • 510 is designated as a single LCH SCG bearer (single-LCH-SCG-RB)
  • 515 is designated as a multi-LCH bearer (multi-LCH-RB).
  • any RB data is defined to be transmitted only through the MCG or only through the SCG.
  • data is repeatedly transmitted through MCG and SCG.
  • LCH means a logical channel, and is a logical path between the RLC and the MAC, and indicates which RLC device any data is associated with.
  • RLC device and LCH are terms that can be used interchangeably.
  • the MCG-LCH is a logical channel configured for the serving cells of the MCG. In the MCG-LCH, data exchanged with the MCG serving cell among the RB data is processed.
  • the SCG-LCH is a logical channel configured for the serving cells of the SCG.
  • data exchanged with the SCG serving cell among the RB data is processed.
  • One or two LCH may be configured for one RB.
  • one is MCG-LCH and the other is SCG-LCH.
  • the uplink data transmission is an RB made only through the MCG.
  • the UE includes both the PDCP data 630 and the RLC data 635 of the RB.
  • the RLC data consists of RLC control data 640, data 645 stored in the RLC transmission buffer, and data 650 stored in the RLC retransmission buffer.
  • the RLC control data is an RLC status report message (RLC STATUS REPORT; control message of the RLC layer containing RLC ACK information and NACK information).
  • the uplink RLC control data is ACK / NACK information for the downlink RLC data.
  • the RLC data stored in the transmission buffer is RLC data that has not been transmitted yet.
  • the RLC data stored in the retransmission buffer is RLC data that has been transmitted once, and is composed of data that has not been confirmed yet or not yet retransmitted because it has not received ACK / NACK information (also referred to as an standing packet) and data that needs to be retransmitted by NACK. do.
  • the BS reflects only packets that need to be retransmitted, except for outstanding packets, among RLC data stored in the retransmission buffer.
  • Single-LCH-SCG-RB 610 There is only one RLC device, and the uplink data transmission is an RB made only through the SCG.
  • the UE In calculating the BS of the RB, the UE includes both PDCP data and RLC data of the RB.
  • Multi-LCH-MCG-RB 615 There are two RLC devices, but the high-link data transmission is an RB that is made only through the MCG. That is, PDCP data is transmitted only to MCG-LCH (or MCG-RLC device 640), and SCG-LCH (or SCG-RLC device 645) transmits only RLC control data for downlink data of the corresponding RB. do.
  • the UE In calculating the BS for the RB, the UE reflects both the amount of PDCP data and the amount of RLC data to the BS 650 reporting through MCG (or to MeNB), and reporting through SCG (or to SeNB).
  • BS 655 reflects only the amount of RLC control data.
  • Multi-LCH-SCG-RB 620 There are two RLC devices, but the high link data transmission is an RB that is only made through the SCG. That is, PDCP data is transmitted only to the SCG-LCH (or SCG-RLC device), and only the RLC control data for downlink data of the corresponding RB is transmitted in the MCG-LCH (or MCG-RLC device).
  • the UE In calculating the BS for the RB, the UE reflects only the amount of RLC control data to the BS 660 reporting (or to the MeNB) through the MCG, and the BS _665 reporting to the SCB (or to the SeNB). Reflects both the amount of PDCP data and the amount of RLC data.
  • Multi-LCH-duplicate-RB 625 There are two RLC devices, and high-level link data is duplicated through the SCG and MCG.
  • the terminal When the terminal is located in the vicinity of the macro cell, the mobility can be significantly reduced by repeatedly transmitting the same data through both the macro cell and the small cell. Therefore, the multi-LCH-duplicate-RB is set for the SRB when a predetermined condition is satisfied (i.e., when an inter-ENB CA is configured for a terminal of a macro cell boundary).
  • PDCP data is transmitted through both the SCG-LCH and MCG-LCH, the terminal reflects the amount of PDCP data and the amount of RLC data to both the BS 670 reported through the MCG and the BS 675 reported through the SCG. .
  • Table 1 Downlink Uplink Usage single-LCH-MCG-RB single-LCH-MCG-RB Services that are sensitive to service interruptions or delays, such as VoLTE single-LCH-SCG-RB single-LCH-SCG-RB Services that require high-speed data transmission and reception, such as FTP.
  • VoLTE single-LCH-SCG-RB single-LCH-SCG-RB Services that require high-speed data transmission and reception such as FTP.
  • FIG. 7 is a diagram illustrating an operation of a terminal that receives an uplink grant.
  • FIG. 7 illustrates an operation when a terminal having an inter-ENB CA configured to receive an uplink grant.
  • the UE receives an uplink grant (control information received through a Physical Downlink Control Channel; includes information on a transmission resource to be used for uplink transmission, an MCS level, and whether to transmit the first transmission) in an arbitrary serving cell.
  • the serving cell is a serving cell belonging to an arbitrary CG, and indicates uplink transmission for one of the serving cells of the corresponding CG.
  • step 710 the UE checks whether the CG is MCG or SCG. This is because the type of data reflected by the terminal to the BS in the case of MCG and the type of data reflected in the BS in the case of SCG are different. If the uplink grant is for the serving cell of the MCG, the terminal proceeds to step 715. If the uplink grant is for the serving cell of the SCG, the terminal proceeds to step 720.
  • the UE checks whether a BSR (Buffer Status Report) has been triggered for the MCG and has not been canceled yet.
  • BSR is a MAC CE that contains BS information for each LCG (Logical Channel Group).
  • the LCG is a group of logical channels, and each BS reflects information obtained by adding up the amount of transmittable data of the logical channels belonging to the LCG.
  • the triggering of the BSR for the MCG indicates that the following event has occurred.
  • ⁇ New transmittable data is generated in the logical channel belonging to the LCG that meets the following conditions.
  • the following data will be collectively referred to as 'MCG-data'.
  • the logical channel priority of the newly generated MCG-data is higher than the logical channel priority of the existing MCG-data.
  • the terminal also triggers a periodic BSR when the predetermined timer expires.
  • the terminal proceeds to step 725. If the BSR has not been triggered or is canceled even if triggered, the terminal proceeds to step 730. The triggered BSR is canceled when the transmission is included in the scheduled MAC PDU.
  • the UE reflects the 'MCG-data' to calculate the BS of each LCG. That is, the UE calculates BS by summing only MCG-data among transmittable RLC data of LCH belonging to LCG for each LCG and PDCP data of PDCP connected with LCH. For example, if LCH 3 and LCH 4 belong to any LCG, LCH 3 is the LCH of single-LCH-MCG-RB, and LCH 4 is the LCH of multi-LCH-SCG-RB, Consider both PDCP data and RLC data, and only LLC control data for LCH 4. The terminal determines the BS of the corresponding LCG by summing these two.
  • the UE determines the data to be transmitted using the uplink grant.
  • the UE first checks whether there is a CCCH SDU or C-RNTI MAC CE to transmit, and if so, includes them in the MAC PDU first.
  • the UE checks whether there is a triggered BSR for the MCG, and if so (and if there is space to include) generates the BSR and includes it in the MAC PDU.
  • the UE then checks whether there is a PHR triggered for the MCG, and if so (and if there is space to include), includes the PHR in the MAC PDU.
  • the UE selects data to be transmitted by reflecting the priority of the MCG-data to the MCG-data. In short, the UE preferentially transmits data having a high logical channel priority among MCG-data.
  • CCCH SDUs are as described in specifications 36.331 and 36.321.
  • C-RNTI MAC CE and PHR are as described in Specification 36.321.
  • the UE If extra space is left even after including all MCG-data, the UE includes a padding BSR, and the remaining space is filled with padding bits.
  • the MAC PDU is transmitted on the uplink and the process ends.
  • step 720 the UE checks whether the BSR is triggered on the SCG, and if so, proceeds to step 735 and, if not, to step 740.
  • the triggering of a BSR for an SCG means that a regular BSR for the SCG is triggered or a periodic BSR for the SCG is triggered.
  • a regular BSR for the SCG is triggered.
  • ⁇ New transmittable data is generated in the logical channel belonging to the LCG that meets the following conditions.
  • the following data will be collectively referred to as 'SCG-data'.
  • the logical channel priority of the newly generated SCG-data is higher than the logical channel priority of the existing SCG-data.
  • Periodic BSR for the SCG is triggered when the predetermined timer set by the base station expires.
  • step 735 the UE calculates the BS of each LCG by reflecting the SCG-data. That is, the UE calculates BS by summing only LCG-data among transmittable RLC data of LCH belonging to LCG for each LCG and PDCP data of PDCP connected to the LCH.
  • the terminal proceeds to step 740.
  • the UE determines data to be transmitted using the uplink grant.
  • the UE first checks whether there is a C-RNTI MAC CE to transmit, and if so, includes them in the MAC PDU first.
  • the UE checks whether there is a triggered BSR for the SCG, and if so (and if there is space to include) generates a BSR and includes it in the MAC PDU.
  • the UE next checks whether there is a PHR triggered for the SCG, and if so (and if there is space to include), includes the PHR in the MAC PDU.
  • the UE selects data to be transmitted by reflecting the priority of the SCG-data to the SCG-data. In short, the UE preferentially selects data having a high logical channel priority among SCG-data.
  • the UE If the extra space is left even after including all SCG-data, the UE includes the padding BSR, and the remaining space is filled with padding bits.
  • the MAC PDU is transmitted on the uplink and the process ends.
  • the logical channel priority is set for each logical channel and the base station instructs the terminal.
  • the terminal applies the logical channel priority as a priority of data generated from a PDCP device connected to the logical channel. If two logical channels are configured in one bearer, the terminal should determine which logical channel priority should be applied to data generated from the PDCP device.
  • the base station sets together which logical channel logical channel priority (logicalChannelPriority) to apply.
  • the setting may be explicit or implicit.
  • Explicit configuration indicates that in setting up a PDCP entity, when the PDCP entity is connected with more than one (or several) logical channels, the base station explicitly indicates which logical channel priority applies to the data of the PDCP entity. will be.
  • the implicit setting is the logical channel priority of the MCG LCH of the RB if the RCP is multi-LCH-MCG-RB if the PDCP entity is connected with more than one logical channel when data is generated from any PDCP entity. If the RB is multi-LCH-SCG-RB, the logical channel priority of the SCG LCH of the RB is applied.
  • the UE has LCH 1 825, LCH 2 830, LCH 3 835, LCH 4 840, LCH 5 845, and LCH 6 850.
  • RB 1 805, RB 2 810, RB 3 815, and RB 4 820 are set.
  • LCH 1 and LCH 2 belong to LCG 1
  • LCH 3 belongs to LCG 2
  • LCH 4 and LCH 5 belong to LCG 3.
  • LCH 6 does not belong to LCG.
  • the UE transmits data stored in LCH 1, LCH 2 and LCH 3, which are MCG LCH, to PDCP 1 and PDCP 2 of RB 1 and RB 2, which are MCG-RB.
  • the UE When new data that can be transmitted to PDCP 2 occurs, the UE similarly compares the priority of data stored in LCH 1, LCH 2, LCH 3, PDCP 1, and PDCP 2 with the priority of newly generated data to determine whether to trigger a BSR. Determine. At this time, the priority of data stored in PDCP 2 is applied to the priority 4 of LCH 2 according to the following rule.
  • Priority of data stored in PDCP connected to two or more logical channels follows the priority of MCG-LCH if the corresponding RB is MCG-RB, and the priority of SCG-LCH if SCG-RB.
  • Priority of data stored in PDCP connected to two or more logical channels may be determined in units of PDCP PDU or PDCP SDU. Priority of any PDCP SDU stored in PDCP of multiple bearers connected to two or more logical channels may be determined by applying the priority of MCG-LCH or the priority of SCG-LCH according to time and situation. Such prioritization in units of PDCP SDU or PDU may be applied when PDCP data of a multiple bearer is transmitted through both MCG and SCG.
  • the priority of a single bearer is fixed to one, the priority of a multiple bearer is determined by one of the priority of the MCG-LCH and the priority of the SCG-LCH at the time when new uplink transmission is possible in the MCG or SCG.
  • a time point when new uplink transmission is possible may be, for example, a time point when an uplink transmission resource for new transmission is allocated or a time point when a configured uplink transmission resource is generated.
  • the priority of the SDUs is determined according to the priority of the logical channel of the corresponding cell group. For example, if a new uplink transmission for the MCG serving cell is possible at any point in time, the terminal applies the priority of the MCG-LCH as the priority for the PDCP SDUs of the multiple bearer. If a new uplink transmission for the SCG serving cell is possible at another random time, the terminal applies the priority of the SCG-LCH as the priority for the PDCP SDUs of the multiple bearer.
  • the UE determines whether to transmit data using the uplink transmission resource of the MCG or whether to transmit data stored in the PDCP of any multi-LCH RB using the MCG uplink transmission resource. In determining, the priority assigned to the MCG-LCH of the multi-bearer and the amount of transmittable data stored in PDCP and MCG-RLC, the priority assigned to the MCG-LCH of another multi-bearer and the transmittable data stored in PDCP Quantity, priority assigned to single-LCH-MCG-RB, and the amount of transmittable data stored in PDCP and RLC devices.
  • a priority assigned to the SCG-LCH of the multiple bearer and an amount of transmittable data stored in PDCP and SCG-RLC a priority assigned to the SCG-LCH of another multiple bearer and an amount of transmittable data stored in PDCP, single Consider the priority assigned to the LCH-MCG-RB and the amount of transmittable data stored in the PDCP device and RLC device.
  • the UE applies the priority of LCH 4 to the transmittable data stored in PDCP 2, and transmits the transmittable data stored in PDCP 3.
  • LCH 5 priority is applied to.
  • the UE transmits certain data in consideration of the amount of transmittable data of PDCP 2, the amount of transmittable data of PDCP 3, the amount of transmittable data of PDCP 4, which is a single-LCH-SCG-RB, and their respective priorities. Determine if you will. For convenience, it is assumed that there is no transmittable data in the RLCs.
  • the UE applies the priority of LCH 2 to the transmittable data stored in PDCP 2 and transmits the transmittable data stored in PDCP 3.
  • the priority of LCH 3 is applied.
  • the UE transmits certain data in consideration of the amount of transmittable data of PDCP 2, the amount of transmittable data of PDCP 3, the amount of transmittable data of PDCP 1, which is a single-LCH-MCG-RB, and their respective priorities. Determine if you will. For convenience, it is assumed that there is no transmittable data in the RLCs.
  • the UE determines which LCH priority to apply to the PDCP SDU.
  • the UE may determine which priority to apply to the PDCP SDU according to a predetermined probability value indicated by the MeNB in advance. For example, if the MeNB indicates a probability value of "0.3: 0.7" for any multiple bearer, the UE applies a priority of MCG-LCH to 30% of SDUs among PDCP SDUs of the multiple bearer, and 70% The priority of SCG-LCH may be applied to the SDUs of.
  • the timing of determining the priority to apply to any SDU is, for example, when the PDCP SDU is stored in the PDCP transmission buffer, when the PDCP SDU arrives at the PDCP device, when the single bearer switches to multiple bearers (single bearer After receiving and successfully interpreting a control message indicating reconfiguration to a multi-bearer, a point in time when an SCG is initially set up and uplink transmission is possible in the SCG (for example, a UE instructed to set up a SCG is randomly selected in a PSCell). When the access is successfully completed).
  • PDCP 3 belongs to the SCG-RB, so the UE determines whether to trigger the BSR for the SCG in consideration of the data of the SCG-RB and the data of the SCG-LCH. That is, the UE compares the priority of the transmittable data previously stored in PDCP 3, LCH 4, LCH 5, and LCH 6 with the priority of newly generated data.
  • the priority of transmittable data of PDCP 3 is 7, which is the priority of LCH 5 according to rule 1. Note that PDCP 4 does not belong to the LCG, so it is not considered in the priority comparison.
  • the terminal calculates a BS for LCG 1 and a BS for LCG 2.
  • the BS of LCG 1 reflects the sum of data of LCH 1, data of LCH 2, data of PDCP 1, and data of PDCP 2.
  • the BS of LCG 2 reflects the data of LCH 3.
  • the data of the LCH x refers to transmittable data of the RLC device of the logical channel x.
  • the UE selects data to be transmitted on the uplink of the serving cell of the MCG, the UE selects data of LCH 1, LCH 2, LCH 3, which are MCG-LCH, and PDCP 1, PDCP 2, which are MCG-RB in consideration of priority. .
  • the UE selects data to be transmitted through the uplink of the serving cell of the SCG, the UE selects data of LCH 4, LCH 5, LCH 6, which are SCG-LCH, and PDCP 3, PDCP 4, which are SCG-RB, in consideration of priority. .
  • the PDCP of the multi-LCH-RB is associated with two or more LCGs.
  • PDCP 3 815 is also linked to LCH3 and also to LCH 5, so it is associated with LCG 2 and also with LCG 3.
  • the UE needs to determine which LCG's BS includes data of PDCP associated with the plurality of LCGs. In determining the LCG to report any PDCP data, if the PDCP is associated with one LCG, the terminal reports the data of the PDCP reflected to the BS of the LCG. If the PDCP is associated with two or more LCGs, the UE applies a predetermined rule to determine which LCG BS to reflect the PDCP data.
  • the PDCP is multi-LCH-MCG-RB
  • the PDCP data is reflected in the BS of the LCG to which the MCG-LCH belongs.
  • PDCP is multi-LCH-SCG-RB
  • PDCP data is reflected in BS of LCG to which SCG-LCH belongs.
  • data of PDCP 2 which is multi-LCH-MCG-RB is reflected in BS of LCG 1 to which LCH 2 which is MCG-LCH among LCH 2 and LCH 4 belongs.
  • Data of PDCP 3, which is a multi-LCH-SCG-RB, is reflected in the BS of LCG 3 to which LCH 5, which is SCG-LCH, of LCH 3 and LCH 5 belongs.
  • a related terminal operation is shown in FIG. 19.
  • a regular BSR or a periodic BSR is triggered by the UE configured with two or more CGs.
  • step 1910 the UE checks for which CG the BSR is triggered. If the BSR is triggered for the MCG, the UE proceeds to step 1915 and if the BSR is triggered for the SCG, the terminal proceeds to step 1950.
  • the UE checks whether there is data that can be transmitted in at least two MCG LCGs.
  • the transmittable data of any MCG LCG includes transmittable data of the RLC device of the LCH belonging to the MCG LCG and transmittable PDCP data of the MCG LCG.
  • the transmittable PDCP data of a predetermined MCG LCG is the PDCP device 865 of the LCH belonging to the corresponding MCG LCG among the LCHs (eg, 805) corresponding to a single-LCH-MCG-RB.
  • the transmittable PDCP data of a predetermined SCG LCG (for example, LCG 3, 860) includes the transmittable data stored in the PDCP device of the LCH belonging to the corresponding SCG LCG among the LCHs corresponding to the single-LCH-SCG-RB, and the multi- Among the LCHs (for example, 835, 845) corresponding to the LCH-SCG-RB (for example, 815), it is transmittable data stored in the PDCP device 875 of the LCH belonging to the SCG LCH (for example, 845).
  • the terminal proceeds to step 1920 and selects a short BSR as a BSR format.
  • the short BSR is a format including only one 6-bit BS. If there is data that can be transmitted in two or more MCG LCGs, the UE proceeds to step 1925 and selects a long BSR as a BSR format. Long BSR is a format including four 6-bit BSs.
  • step 1930 the UE checks whether extendedBSR-Sizes is set in the BSR configuration for the MCG (or for the MeNB or for the MAC device connecting the MCG serving cells and the MCG LCH). If extendedBSR-Sizes is set, the terminal proceeds to step 1935, and if not, the terminal proceeds to step 1940.
  • BS is an index of 6 bits. The BS for any LCG is determined with reference to a given Buffer Size level.
  • Buffer Size level is divided into those defined by Table 2 and those defined by Table 3.
  • the buffer size level defined by Table 2 is called the normal buffer size level and the buffer size level defined by Table 3 is called the extended buffer size level.
  • the normal buffer size level is efficient when the amount of reverse data is not large.
  • the extended buffer size level is efficient when the amount of reverse data is large.
  • the BS indicates whether to refer to the normal buffer size level or the extended buffer size level.
  • the BS of the LCG is determined according to the following method.
  • the base station applies the extended buffer size level if the extendedBSR-Sizes is set for the BSR for the MCG and applies the normal buffer size level if the extendedBSR-Sizes is not set for the LCG configured for the MCG.
  • the base station applies the extended buffer size level if the extendedBSR-Sizes is set for the BSR for the SCG, and applies the normal buffer size level if the extendedBSR-Sizes is not set for the LCG configured for the SCG.
  • Different buffer size levels can be applied to the BSR for the MCG and the BSR for the SCG (for example, the normal buffer size level is applied to the BS determination of the MCG LCG, and the extended buffer size level is applied to the BS determination of the SCG LCG or vice versa. ), Several types of buffer size levels may be set in one terminal. Therefore, the UE selects an appropriate buffer size level according to which CG the BSR is.
  • Index Buffer Size (BS) value [bytes]
  • Index Buffer Size (BS) value [bytes]
  • Index Buffer Size (BS) value [bytes]
  • Index Buffer Size (BS) value [bytes]
  • step 1935 the UE determines the BS of the MCG LCG in which data that can be transmitted exists based on the extended buffer size level of Table 3.
  • step 1940 the UE determines BSs of MCG LCGs in which transmittable data exists with reference to the normal buffer size levels of Table 2.
  • the amount of transmittable data of any MCG LCG is a sum of the amount of transmittable RLC data of the MCG LCG and the amount of transmittable PDCP data.
  • the amount of transmittable RLC data of any MCG LCG includes the amount of transmittable data of the RLC of the LCH belonging to that LCG.
  • the amount of transmittable PDCP data of any MCG LCG is the amount of transmittable PDCP data stored in the PDCP associated with the LCH belonging to the MCG LCG in single-LCH-MCG-RB and the MCG LCG among multi-LCH-MCG-RB.
  • the amount of transmittable PDCP data stored in the PDCP associated with the LCH is a sum of the amount of transmittable RLC data of the MCG LCG and the amount of transmittable PDCP data.
  • the amount of transmittable RLC data of any MCG LCG includes the amount of transmittable data of the RLC of the LCH belonging to that LCG.
  • the amount of transmittable data of any SCG LCG is the sum of the amount of transmittable RLC data of the corresponding SCG LCG and the amount of transmittable PDCP data.
  • the amount of transmittable RLC data of any SCG LCG includes the amount of transmittable data of the RLC of the LCH belonging to that LCG.
  • the amount of transmittable PDCP data of any SCG LCG is equal to the amount of transmittable PDCP data stored in the PDCP associated with the LCH belonging to the SCG LCG in single-LCH-SCG-RB and the SCG LCG in multi-LCH-SCG-RB.
  • the amount of transmittable PDCP data stored in the PDCP associated with the LCH is the sum of the amount of transmittable RLC data of the corresponding SCG LCG and the amount of transmittable PDCP data.
  • the amount of transmittable RLC data of any SCG LCG includes the amount of transmittable data of the RLC of the LCH belonging to that LCG.
  • step 1945 the UE generates a long BSR or short BSR in which the BS of the MCG LCG is stored and transmits the BSR through the serving cell of the MCG.
  • the UE checks whether there is data that can be transmitted in at least two SCG LCGs.
  • the transmittable data of any SCG LCG includes transmittable data stored in the RLC device of the LCH belonging to the SCG LCG and transmittable PDCP data of the SCG LCG.
  • the terminal proceeds to step 1955 and selects a short BSR as a BSR format. If there is data that can be transmitted in two or more SCG LCGs, the terminal proceeds to step 1960 and selects a long BSR as a BSR format.
  • the UE simultaneously transmits the BSR for the MCG and the BSR for the SCG, the formats of the BSR for the MCG and the BSR for the SCG may be different.
  • step 1965 the UE checks whether extendedBSR-Sizes is set in the BSR configuration for the SCG (or for the MeNB or for the MAC device connecting the MCG serving cells and the MCG LCH). If extendedBSR-Sizes is set, the terminal proceeds to step 1970, and if not, the terminal proceeds to step 1975.
  • step 1970 the UE determines the BS of the SCG LCG in which transmittable data exists with reference to the extended buffer size level of Table 3.
  • step 1975 the UE determines BSs of SCG LCGs in which transmittable data exists with reference to the normal buffer size levels of Table 2.
  • step 1980 the UE generates a long BSR or short BSR in which the BS of the SCG LCG is stored, transmits the BSR through the serving cell of the SCG, and ends the process.
  • FIG. 9 is a diagram illustrating an operation of a terminal performing a scheduling request when PDCP data is generated. Specifically, FIG. 9 illustrates a terminal operation for determining a serving cell to trigger an SR.
  • SR is a signal that the terminal transmits to the base station to request a transmission resource for transmitting the BSR when the regular BSR is triggered.
  • the SR may be transmitted through a transmission resource exclusively allocated to the terminal.
  • the transmission resource is set in the PUCCH, and the SR transmitted through the PUCCH is also called a Dedicated-Scheduling Request (D-SR). If a D-SR is not allocated to the UE, the UE requests transmission resource allocation to the base station through a random access process, which is called a RA-SR (Random Access-Scheduling Request).
  • D-SR Dedicated-Scheduling Request
  • new data is generated in any PDCP device, and a regular BSR is triggered by the new data.
  • step 910 the UE checks whether one LCH is set or two or more LCHs are set in the RB of the PDCP device. The UE proceeds to step 915 if one LCH is configured (ie, single-LCH-RB), and proceeds to step 920 if two or more LCHs are configured (ie, multi-LCH-RB).
  • step 915 the UE checks whether the new data is data generated from PDCP of MCG-RB or data generated from PDCP of SCG-RB. If the UE is data generated in the MCG-RB, the UE proceeds to step 925 to trigger the SR in the PCell. That is, if the SR resource is allocated to the PUCCH of the PCell, the terminal transmits the D-SR using the SR resource. If the SR resource is not allocated to the PUCCH of the PCell, the terminal performs random access in the PCell.
  • the terminal proceeds to step 930 to trigger the SR in a predetermined SCell.
  • the predetermined SCell is a SCell specified by a base station among SCells belonging to the SCG, and is named pSCell (primary SCell) for convenience.
  • the terminal transmits HARQ feedback for SCG cells, channel status information (CSI) for SCG cells, etc. using the PUCCH transmission resource of the pSCell.
  • the PUCCH and CSI are as defined in the standard 36.213.
  • SR transmission resources of the terminal may be allocated to the PUCCH of the pSCell. If the SR transmission resource is allocated to the PUCCH of the pSCell, the UE transmits the D-SR using the SR transmission resource. If not, the terminal performs random access in the pSCell.
  • step 920 the UE checks whether the new data is data generated from PDCP of MCG-RB, data generated from PDCP of SCG-RB, or data generated from PDCP of duplicate-RB. If the new data is data generated in the PDCP of the MCG-RB, the UE proceeds to step 935 to trigger the SR in the PCell, and if the data occurs in the PDCP of the SCG-RB, the terminal proceeds to step 945 to trigger the SR in the pSCell. If the new data is data generated from the PDCP of the duplicate-RB, the UE proceeds to step 940 to trigger the SR in the PCell and the SR in the pSCell.
  • the RLC When two logical channels are configured in one RB, the RLC performs an order reordering operation, but since the order reordering is not performed between RLC devices, the PDCP must perform a separate order reordering.
  • the PDCP transmitting apparatus 1010 in the RB 1005 in which one logical channel is set, the PDCP transmitting apparatus 1010 is in the order of packet [1], packet [2], packet [3], and packet [4].
  • the packet is delivered to the RLC transmitting apparatus 1015.
  • the packets are received at the RLC receiving apparatus 1020 via a MAC device and a wireless channel.
  • the order of the packets received by the RLC receiving apparatus 1020 is the order of the packets transmitted by the PDCP transmitting apparatus 1015. Can be different from.
  • the RLC receiving apparatus 1020 rearranges the misaligned order again and transmits the misaligned order to the PDCP receiving apparatus 1025. For example, the RLC receiving apparatus 1020 delivers the packet to the PDCP receiving apparatus 1025 in the order of packet [1], packet [2], packet [3], and packet [4].
  • the PDCP transmitter 1035 transmits a packet to two RLC transmitters 1040 and 1045.
  • the PDCP transmitter 1035 transmits a packet [1] and a packet [3] to the first RLC transmitter 1040 and a packet [2] and a packet [4] to the second RLC transmitter 1045.
  • the first RLC transmitting apparatus 1040 transmits a packet to the first RLC receiving apparatus 1050 and the second RLC transmitting apparatus 1045 transmits the packet to the second RLC receiving apparatus 1055.
  • the first RLC receiving apparatus 1050 rearranges the received packets in the order in which the first RLC transmitting apparatus 1040 receives the packets from the PDCP transmitting apparatus 1035.
  • the first RLC receiving apparatus 1050 (packets packets to the PDCP receiving apparatus 1060 in the order of packet [1] and packet [3].
  • the second RLC receiving apparatus 1055 is the second RLC transmitting apparatus.
  • the 1045 rearranges the order of the received packets in the order of receiving the packets from the PDCP transmitting apparatus 1035. That is, the second RLC transmitting apparatus 1045 receives the packets in the order of the packet [2] and the packet [4].
  • the order of the packets transmitted by the first RLC receiving apparatus 1050 and the second RLC receiving apparatus 1055 is not aligned, for example, the first RLC receiving apparatus 1050.
  • the packets transmitted by the second RLC receiving apparatus 1055 may be delivered in the order of packet [1], packet [2], packet [4], packet [3], packet [2], packet [4], It may be delivered in the order of packet [1], packet [3], and thus the PDCP receiving apparatus 1060 reorders the packets delivered by two or more RLC receiving apparatuses 1040 and 1045. You need to sort it once.
  • the present invention proposes a method of using a timer and a method of using variables as an order reordering method of a PDCP receiving apparatus. First, a method of using a timer will be described.
  • the PDCP receiving apparatus includes a predetermined timer, which is driven when a packet out of order occurs. If the order is not sorted until the timer expires, the unordered packets are considered ordered and are forwarded to higher layers.
  • a packet [n + 1] arrives at the PDCP receiving apparatus at an arbitrary t1 1105, and a packet [n + 3] arrives at the t2 1110. Since the packet [n + 3] is an out of order packet, the PDCP receiving apparatus associates and drives a timer with the packet [n + 3].
  • a packet [n + 4] is received at t3 (1115), a packet [n + 6] is received at t4 (1120), and the timer expires at t5 (1125).
  • the PDCP receiver receives the serial number associated with the expired timer, that is, packet [n + 1], which is a packet with a serial number lower than [n + 3], and a serial number higher than [n + 3], the serial number associated with an expired timer.
  • the length of the timer is preferably set to be a very long time including both the ARQ delay and HARQ delay of the lower layer, the length of the timer is instructed by the base station to the terminal.
  • the RLC receivers independently rearrange the order of packets and deliver them to the PDCP receiver.
  • the PDCP receiving apparatus may know that the packet having a serial number lower than [n] will not be transmitted from the RLC receiving apparatus 1.
  • the RLC receiving apparatus 2 delivered the packet [m]
  • the PDCP receiving apparatus can know that the packet having a serial number lower than the [m] from the RLC receiving apparatus 2 will not be delivered. Using this phenomenon, a simple but efficient order reordering operation can be defined.
  • the highest serial number (or one plus 1) of the packets received at RLC receiver 1 is called Next_COUNT_1, and the highest serial number (or one plus 1) of packets received at RLC receiver 2 is determined.
  • Next_COUNT_2 the PDCP receiving apparatus transmits the packets lower than the number to the higher layer based on the lower number of the two numbers, even though there are unreceived packets.
  • a packet [n + 1] arrives from the RLC apparatus 1 to the PDCP receiving apparatus at an arbitrary t1 1205. If there are no out-of-order packets (or unreceived packets), the PDCP order reordering device forwards the packet [n + 1] to the next processing device (which may be a higher layer or another functional device within the PDCP device) and Last_Submitted_COUNT. Is set to [n + 1]. Since packet [n + 1] was received from RLC device 1, the PDCP order reordering device sets Next_COUNT_1 to [n + 2].
  • Last_Submitted_COUNT is a variable representing the highest serial number of packets that have been reordered and delivered to higher layers or to the next functional device.
  • COUNT is a serial number that is used as an input value of packet deactivation / deactivation for security. It consists of HFN and PDCP SN and follows the specification in 36.323.
  • Next_COUNT_1 is a sum of 1 to the highest serial number of the serial numbers of packets received from the RLC device 1.
  • a packet [n + 3] arrives from RLC device 2 at any t2 1210 and the PDCP receiving device sets Next_COUNT_2 to [n + 4].
  • the PDCP receiving apparatus recognizes that the packet [n + 2] is an unreceived packet, and a packet out of order is generated due to the unreceived packet.
  • the PDCP receiving apparatus also recognizes that the packet [n + 2] is unlikely to be received from RLC apparatus 2 since it has already received a packet with a serial number higher than that of packet [n + 2] from RLC apparatus 2.
  • a packet [n + 4] is received from the RLC device 2 at any t3 1215, and the PDCP receiving device sets Next_COUNT_2 to [n + 5].
  • a packet [n + 6] is received from the RLC device 1 at an arbitrary t4 1240, and the PDCP device sets Next_COUNT_1 to [n + 7].
  • the PDCP receiving device Since a packet with a serial number higher than [n + 2] was received from RLC device 1, the PDCP receiving device recognizes that packet [n + 2] is unlikely to be received from RLC device 1 as well. Ignores or behaves as if a packet [n + 2] was received. That is, the PDCP receiving apparatus forwards the remaining packets in order, such as packet [n + 3] and packet [n + 4], to the next functional device if packet [n + 2] is received and Last_Submitted_COUNT [n + 4].
  • the terminal determines a smaller value of Next_COUNT_1 and Next_COUNT_2 ([n + 5] in the above example), and transmits all packets having a serial number lower than the small Next_COUNT to the next processing device.
  • the serial number of any unreceived packet lower than Next_COUNT_1 means that the packet is unlikely to be received from RLC device 1
  • the serial number of any unreceived packet lower than Next_COUNT_2 means that the packet is received from RLC device 2 That means there is no possibility to be. Therefore, if the serial number of any unreceived packet is lower than Next_COUNT_1 and lower than Next_COUNT_2, it indicates that the unreceived packet will not be received in the future and performs an order reordering operation accordingly.
  • the operation may be defined as follows.
  • the PDCP receiver records the highest serial number of the serial numbers of the packets received from the RLC device 1 in Next_COUNT_1.
  • the PDCP receiver records the highest serial number of the serial numbers of the packets received from the RLC device 2 in Next_COUNT_2.
  • the PDCP receiver sends all packets with serial numbers lower than the minimum of Next_COUNT_1 and Next_COUNT_2 to the next functional device.
  • FIG. 13 is a diagram illustrating an operation of processing a PDCP packet by a PDCP device of a multiple LCH bearer. 13 illustrates a method in which a PDCP receiving device configuring a PDCP device rearranges the order using variables.
  • the PDCP receiving device proceeds to step 1310 to determine the HFN of the received packet and discards the delayed received packet.
  • HFN Hexaper Frame Number
  • HFN and PDCP SN combine to form COUNT.
  • PDCP SN is explicitly indicated in the PDCP packet header, while HFN is not. Therefore, the PDCP receiving apparatus must determine the HFN of the received packet by itself.
  • the PDCP transmitting apparatus If the PDCP transmitting apparatus complies with a predetermined condition (transmitting the sequence out of the PDCP SN less than half of the sum of the serial numbers that can be indicated by the PDCP SN) in transmitting the packet, the PDCP receiving apparatus receives the most recently received. Uses the serial number of a PDCP packet (received PDCP SN, see specification 36.323), the highest serial number received so far (Next_PDCP_RX_SN, see specification 36.323), and a window of a predetermined size (Reordering_Window, see specification 36.323). HFN is determined.
  • header decompression is performed on the received packet. Discard after performing.
  • the packet may contain useful information for updating the header restoration context, and thus discarded after performing header restoration.
  • the procedure is as described in section 5.1.2.1.2 of 36.323. According to the standard, if the following conditions are met, the received packet is delayed or duplicated.
  • the PDCP receiving apparatus proceeds to step 1315 and combines the HFN and PDCP SN to determine the COUNT of the received packet, in the order of COUNT. Therefore, the packet is stored in an order reorder buffer. Further, if the received packet is a packet that does not require order reordering, i.e., if received COUNT is equal to summing 1 to last_submitted_COUNT (or if the received PDCP SN is equal to summing 1 to last_submitted_PDCP_RX_SN), the PDCP receiving apparatus receives the received packet. One PDCP packet is forwarded to the next processing unit.
  • the PDCP receiver proceeds to step 1320. If no packets need reordering, the PDCP receiver waits for the next PDCP packet to arrive.
  • the PDCP receiving apparatus determines whether the packet is received by the RLC apparatus 1 or the RLC apparatus 2. Alternatively, the PDCP receiving apparatus determines whether the packet is received on the first logical channel or the second logical channel.
  • the RLC device 1 or the first logical channel may be an RLC device or logical channel associated with the MCG
  • the RLC device 2 or a second logical channel may be an RLC device or logical channel associated with the SCG.
  • the PDCP device proceeds to step 1325. If the packet is received at the RLC device 2, the PDCP device proceeds to step 1330.
  • step 1325 the PDCP device checks whether the COUNT (received COUNT) of the received packet is greater than or equal to Next_COUNT_1. If the COUNT (received COUNT) of the received packet is greater than or equal to Next_COUNT_1, the PDCP device proceeds to step 1335 and updates Next_COUNT_1 to the value obtained by adding 1 to the received COUNT and proceeds to step 1345. If the count of the received packet is less than Next_COUNT_1, the PDCP receiving device proceeds directly to step 1345.
  • step 1330 the PDCP device checks whether the COUNT (received COUNT) of the received packet is greater than or equal to Next_COUNT_2. If the COUNT (received COUNT) of the received packet is greater than or equal to Next_COUNT_2, the PDCP device proceeds to step 1340 and updates Next_COUNT_2 to the sum of the received COUNT plus 1 and proceeds to step 1345. If the count of the received packet is less than Next_COUNT_2, the PDCP device proceeds directly to step 1345.
  • the PDCP device forwards packets satisfying condition 1 of the packets stored in the PDCP order reordering buffer to the next processing device.
  • a packet that satisfies condition 1 may mean, for example, a packet whose COUNT is lower than Min [Next_COUNT_1, Next_COUNT_2].
  • the PDCP device stores the remaining packets that do not satisfy the condition 1 in the order reordering buffer and waits until the next PDCP packet arrives from the lower layer.
  • a method of rearranging the order by the PDCP receiving apparatus using variables is as follows.
  • the PDCP receiver receives packets 1425 between Next_COUNT_1 and Next_COUNT_2. Is stored in the reorder buffer. In addition, the PDCP receiving apparatus forwards packets 1420 between Next_COUNT_1 and Last_Submitted_COUNT 1405 to a higher layer (or next functional device).
  • Next_COUNT_1 becomes higher than Next_COUNT_2 by receiving a packet from the RLC 1 device
  • the PDCP receiving device forwards packets 1430 between Next_COUNT_1 and Last_Submitted_COUNT to a higher layer (or next functional device), and packets between Next_COUNT_2 and Next_COUNT_1.
  • 1435 stores the sequence reordering buffer.
  • Figure 15 shows the overall operation associated with the generation and release of multi-LCH-RB.
  • the MeNB 1510 determines to add the serving cell of the SeNB 1515 to the terminal 1505, and the SeNB ( 1515) and a procedure for adding a serving cell (1520).
  • the UE 1505 configures the SCell of the SeNB 1515 for the first time (i.e., configures the first SCG SCell)
  • the MeNB 1510 and the SeNB 1515 provide a certain RB to the MeNB 1510. And determine which RB the SeNB 1515 will service.
  • the MeNB 1510 and the SeNB 1515 use a multi-LCH-RB for the downlink and a multi-LCH- for the uplink for an RB meeting a predetermined condition, for example, an RB requiring high-speed data transmission on the downlink.
  • MCG-RB or multi-LCH-SCG-RB can be set.
  • the MeNB 1510 transmits a predetermined RRC control message to the terminal 1505 (1525).
  • the RRC control message contains SCell configuration information and multi-LCH-rb configuration information.
  • SCell configuration information is for a newly added SCell, and includes information indicating whether the SCell is an MCG SCell or an SCG SCell.
  • the multi-LCH-rb configuration information is information on a radio bearer for which multi-LCH is configured and includes the following sub information.
  • the multi-LCH-rb information may be included in the RRC control message including the configuration information of the first SCG SCell.
  • Table 4 bearer identifier Identifier of the bearer for which multi-LCH is set.
  • SCG-LCH and RLC 2 configured by the following information are additionally mapped to the bearer of the identifier.
  • pdcp-Config This configuration information is included only when it is necessary to update the PDCP configuration information of an existing bearer for which mult-LCH is configured. If this configuration information is not included, the existing pdcp-Config is used as it is.
  • Uplink mode Indicates one of MCG-only, SCG-only, and duplicate. If MCG-only, the uplink PDCP packet is transmitted only through RLC device 1 (or only through MCG-LCH).
  • the uplink PDCP packet is transmitted only through RLC device 2 (or only through SCG-LCH). Even if any bearer is set to SCG-only, the packet already transmitted through the RLC device 1 is transmitted as it is. If duplicate, the uplink PDCP packet is duplicated through RLC device 1 and RLC device 2.
  • RLC-config Configuration information of the RLC ie, RLC device 1 for the MCG. It exists only when it is necessary to update configuration information of an existing RLC of an existing bearer for which multi-LCH is configured. If this configuration information does not exist, the existing RLC-config is used as it is.
  • RLC-config2 Configuration information of the RLC ie, RLC device 2) connected to the SCG.
  • the terminal If it is the same as RLC-config, it may not exist.
  • the terminal generates a new RLC device by applying RLC-config2 and connects the RLC device with the PDCP device of the bearer indicated by the bearer identifier.
  • logicalChannelIdentity2 Logical channel identifier for RLC device 2 (or SCG-LCH), and is used to identify the logical channel in the MAC header. The structure of the information is the same as logicalChannelIdnetity. If the logical channel identifier of MCG-LCH is used as it is, it is not signaled. In this case, the same value as the logical channel identifier of the RLC device 1 (or MCG-LCH) is used as the logical channel identifier of the RLC device 2.
  • logicalChannelConfig2 Configuration information on the SCG-LCH the structure of the information is the same as logicalChannelConfig. Through the above information, logical channel priority information, LCG information, etc. of the SCG-LCH are indicated. If it is the same as logicalChannelConfig of MCG-LCH, it is not signaled.
  • the terminal 1505 When the terminal 1505 receives the control message, the terminal 1505 generates an SCG-RLC for the bearer indicated by the bearer identifier and connects the PDCP device, and generates an SCG-LCH to connect the SCG-RLC and the MAC.
  • the terminal 1505 triggers a regular BSR for the SCG and a regular BSR for the MCG for a bearer configured to SCG-only. Only SCG-only data is reflected in the normal BSR for the SCG, and only MCG-only-data is reflected in the regular BSR for the MCG.
  • the triggering of the BSR after setting the multi-LCH as described above is because the BS is changed before and after the setting of the multi-LCH.
  • the terminal 1505 performs random access on the newly added SCG SCell (1530). Through the random access procedure, the terminal 1505 establishes uplink synchronization with the newly added SCG SCell and sets uplink transmission output.
  • the UE 1505 transmits a predetermined RRC control message to the MeNB 1510 to report that SCell configuration and multi-LCH configuration have been completed (1535).
  • the MeNB 1510 receives the information, the MeNB 1510 forwards downlink data of a bearer for which multi-LCH is configured to the SeNB 1515 (1540).
  • the terminal 1505 transmits the predetermined RRC control message and then starts a multi-LCH operation on a bearer in which the multi-LCH is configured. That is, in transmitting uplink data of a bearer set to MCG-RB, the UE 1505 always transmits PDCP data of the bearer to the MCG-RLC device and the MCG-LCH (1545). In transmitting uplink data of a bearer set to SCG-RB, the UE 1505 always transmits PDCP data of the bearer to the SCG-RLC device and the SCG-LCH (1545).
  • the UE 1505 In transmitting uplink data of a bearer set to duplicate, the UE 1505 always duplicates the PDCP data of the bearer to the SCG-RLC device and the SCG-LCH and the MCG-RLC device and the MCG-LCH (1545).
  • the terminal 1505 In receiving a downlink PDCP packet of a bearer configured to multi-LCH, the terminal 1505 applies 'order reordering using a timer' or 'order reordering using a variable' (1550).
  • the terminal 1505 performs data transmission / reception with the MeNB 1510 and the SeNB 1515 (1555).
  • the MeNB 1510 or SeNB 1515 decides to release the SCG SCell.
  • the MeNB 1510 and the SeNB 151 perform a procedure for releasing the SCG SCell (1560), and the MeNB 1510 sends a predetermined RRC control message to the terminal 1505 to instruct the SCG SCell release (1565). .
  • the terminal 1505 When the terminal 1505 receives the control message, the terminal 1505 releases the SCG SCell according to the instruction. The terminal 1505 if the control message indicates the release of the last SCG SCell (that is, if there are no more SCG SCells when the SCG SCell is released according to the instruction of the control message), the multi-LCH even if not otherwise indicated. -Release the SCG RLC and SCG LCH of the RBs (1570), and triggers a PDCP status report.
  • the UE 1505 In the process of releasing the SCG RLC, the UE 1505 reconfigures the downlink RLC PDUs stored in the SCG RLC to the RLC SDU, transfers the PD to the PDCP, and discards the uplink RLC PDUs and the uplink RLC SDUs stored in the SCG RLC.
  • the PDCP status report may be triggered for each radio bearer, and the terminal 1505 examines the serial number of the PDCP packet stored in the PDCP receiving buffer of the bearer where the PDCP status report is triggered, and relates to the serial number of the PDCP packet not received. Create a PDCP status report containing information.
  • the PDCP status report is control information used to prevent PDCP packet loss during handover or RRC connection reestablishment.
  • the handover or RRC connection re-establishment process involves re-establishment of all RLC devices configured in the terminal 1505 (re-establishment of a lower layer in the position of a PDCP device).
  • the UE 1505 triggers a PDCP status report for all DRBs that satisfy condition 2.
  • the terminal 1505 triggers a PDCP status report for all DRBs satisfying condition 3.
  • DRBs with statusReportRequired DRBs with statusReportRequired set
  • the statusReportRequired follows that described in the standards 36.331 and 36.323.
  • the UE 1505 transmits a predetermined RRC control message to the MeNB 1510 to report that the process has been successfully completed (1575).
  • the UE 1505 and the MeNB 1510 communicate with the uplink data and downlink through the MCG SCells. Send and receive link data.
  • FIG. 16 is a diagram illustrating an operation of a PDCP device processing a PDCP packet.
  • FIG. 16 illustrates an operation of a terminal that receives a PDCP packet in consideration of all types of RBs.
  • the UE checks whether the RLC device is an unacknowledged mode (UM) RLC or an acknowledgment mode (AM RLC) (step 36.322) in step 1610. If the UM RLC step 1615, if the AM RLC proceeds to step 1640.
  • UM unacknowledged mode
  • AM RLC acknowledgment mode
  • a UM RLC bearer If a UM RLC bearer is configured, it is more important to reduce delay than to reduce packet loss. Therefore, the terminal processes the received packet and immediately delivers it to the upper layer without applying order reordering. If the bearer is a single-LCH bearer, since the ordering is performed in the RLC device, the ordered packets arrive at the PDCP device. On the other hand, in a multi-LCH bearer, an out of order packet may be delivered. Due to the difference, the terminal performs different operations in both cases.
  • step 1615 the UE checks whether the bearer is a single-LCH bearer or a multi-LCH bearer, and proceeds to step 1620 for a single-LCH bearer and to step 1630 for a multi-LCH bearer.
  • step 1620 the terminal determines the HFN by comparing the serial number of the current packet and the serial number of the previous packet. In short, if the serial number of the current packet is lower than the serial number of the previous packet, it is determined that wraparound of the PDCP SN has occurred and the HFN is increased by one. If the serial number of the current packet is higher than the serial number of the previous packet, the current HFN is used as it is.
  • step 1625 the UE processes the packet using the HFN (for example, performs packet de-assertion and header restoration) and delivers the packet to a higher layer.
  • step 1630 the UE determines the HFN using the window and the serial number, and proceeds to step 1635.
  • step 1630 the UE checks whether there is an unreceived packet (or an unreceived packet between the serial number of the received packet and Last_submitted_COUNT or Last_submitted_SN) among packets having a serial number lower than the serial number of the received packet. If there is no such packet, the terminal processes the received packet and delivers it to the upper layer.
  • the packet is checked to see if there is an ordered packet, the packet is processed and delivered to a higher layer, and the remaining packets are stored in a buffer. Do it. For example, if Next_COUNT is updated due to the received packet, and if the updated Next_COUNT is smaller than another Next_COUNT, then packets are ordered due to the received packet, and packets are ordered based on the updated Next_COUNT. Determine whether or not.
  • step 1640 the UE checks whether the PDCP packet is delivered by re-establishment of the lower layer or release of the lower layer. If yes, go to step 1670; otherwise, go to step 1645. The reestablishment of the lower layer occurs due to handover, and the release of the lower layer occurs due to the release of the last SCG SCell.
  • step 1645 the UE checks whether the corresponding bearer is a multi-LCH bearer or a single-LCH bearer. If the single-LCH bearer proceeds to step 1650, if the multi-LCH bearer proceeds to step 1660. Steps 1650 and 1660 are the same as steps 1630. Step 1665 is the same as step 1635.
  • step 1655 the terminal processes the received packet and delivers it to a higher layer. Proceeding to steps 1650 and 1655 for a single-LCH bearer means that a separate order reordering process is not applied. Proceeding to steps 1660 and 1665 for the multi-LCH bearer means applying an order reordering process to the corresponding packet.
  • the UE checks whether the bearer is a data bearer (DRB) or a signaling bearer (SRB).
  • DRB data bearer
  • SRB signaling bearer
  • a data bearer when unsequential packets are re-established due to handover, RRC connection reestablishment, or when the last SCG SCell is released and the SCG-RLC is released, temporary packets are temporarily stored in a buffer. When subsequent packets arrive, they are forwarded to the upper layer as well.
  • the signaling bearer the occurrence of the event itself means that a new RRC procedure has been initiated, but all the conventional packets must be discarded, but unnecessary confusion can be prevented. If the bearer is a data bearer, the terminal proceeds to step 1675.
  • Step 1675 is the same as step 1630.
  • the UE processes the UE in which the HFN is determined, and stores PDCP SDUs in an unordered sequence in a buffer.
  • the PDCP SDU stored in the buffer is delivered to the upper layer along with the received packets after the RRC procedure is completed.
  • the terminal discards the received packet.
  • PDCP PDUs received from a functioning lower layer are processed as PDCP SDUs, not PDCP PDUs received due to re-establishment or release of lower layers.
  • the UE stores PDCP PDUs in a buffer and waits until the order is sorted.
  • the UE processes the received PDCP PDUs as PDCP SDUs and delivers the ordered SDUs to the upper layer and the order is not SDUs are stored in a buffer.
  • the terminal processes only PDUs arranged in an order as SDUs, and PDUs that are not ordered are stored in a buffer first and then processed as SDUs after being ordered, whereas in the case of a single bearer
  • the PDU processes the received PDUs as SDUs, delivers the ordered PDUs to the upper layer, and stores the SDUs out of order in the buffer.
  • the terminal may transmit and receive data to and from the MCG serving cell using LTE wireless technology, and may transmit and receive data using a wireless technology different from the SCG serving cell, for example, WIFI technology or HSPA technology.
  • LTE which is a reliable radio technology
  • MCG serving cell and to apply another radio technology to SCG serving cell.
  • one PDCP device performs order reordering for PDCP PDUs received through different radio technologies, and a lower layer of different radio technologies. Distribute the PDCP PDU to the device.
  • a timer-based sequence reordering technique or a method of transmitting a PDCP PDU only to a specific cell group that is, a specific radio technique.
  • one PDCP device may be connected to two lower layers using different radio technologies, and at least one of them may be defined as a bearer which is a lower layer using LTE technology.
  • FIG. 17 is a block diagram illustrating an example of a terminal device.
  • the terminal device includes an MCG-MAC device 1710, a control message processor 1765, various upper layer processors 1770, 1775, and 1785, a controller 1780, and an SCG-.
  • the transceiver receives data and a predetermined control signal through a downlink channel of a serving cell and transmits data and a predetermined control signal through an uplink channel.
  • the transceiver performs data transmission and reception and control signal transmission and reception through the plurality of serving cells.
  • the MCG-MAC device multiplexes the data generated by the RLC device or demultiplexes the data received from the transceiver 1605 and delivers the data to the appropriate RLC device.
  • the MCG-MAC device also processes BSR or PHR triggered for the MCG.
  • the control message processing unit is an RRC layer device and processes the control message received from the base station and takes necessary actions. For example, the RRC control message is received and various configuration information is transmitted to the controller.
  • the upper layer processor may be configured for each service. It processes data from user services such as File Transfer Protocol (FTP) and Voice over Internet Protocol (VoIP), and delivers it to the PDCP device.
  • FTP File Transfer Protocol
  • VoIP Voice over Internet Protocol
  • the controller controls the transceiver 1605 and the multiplexing and demultiplexing unit so as to check the scheduling command received through the transceiver, for example, reverse grants, so that backward transmission is performed at an appropriate time with an appropriate transmission resource.
  • the controller also performs various control functions for the terminal operation illustrated in FIG. 15.
  • PDCP devices are divided into single-LCH PDCPs (1745, 1750, 1760) and multi-LCH PDCP (_1755).
  • the single-LCH PDCP transmits and receives data only through MCG or SCG and is connected to one RLC transceiver.
  • the multi-LCH PDCP receives data through the MCG and SCG, and transmits the data through either the MCG or the SCG.
  • the multi-LCH PDCP is connected with two RLC receivers and one RLC transmitter.
  • the multi-LCH PDCP performs the order reordering operation shown in FIGS. 11 to 14.
  • FIG. 18 is a block diagram illustrating a configuration of a base station according to an exemplary embodiment of the present invention, wherein the base station includes a MAC device 1810, a control message processor 1865, a controller 1880, a transceiver 1805, and a PDCP device 1845 and 1850. , 1855, 1860, RLC devices 1820, 1825, 1830, 1835, 1840, and scheduler 1890.
  • the transceiver transmits data and a predetermined control signal through a forward carrier and receives data and a predetermined control signal through a reverse carrier.
  • the transceiver performs data transmission and reception and control signal transmission and reception to the plurality of carriers.
  • the MAC device multiplexes the data generated in the RLC device or demultiplexes the data received from the transceiver, and delivers the data to the appropriate RLC device or the control unit.
  • the control message processor processes the control message sent by the terminal to take a necessary action, or generates a control message to be delivered to the terminal and delivers the control message to the lower layer.
  • the scheduler allocates a transmission resource to the terminal at an appropriate time point in consideration of the buffer state and the channel state of the terminal, and processes the signal transmitted by the terminal to the transceiver or transmits the signal to the terminal.
  • the PDCP devices are divided into single-LCH PDCP and multi-LCH PDCP.
  • the single-LCH PDCP transmits and receives data only through MCG or SCG and is connected to one RLC transceiver.
  • the multi-LCH PDCP receives data through the MCG and SCG, and transmits the data through either the MCG or the SCG.
  • the multi-LCH PDCP is connected to one RLC receiver and two RLC transmitters.
  • the multi-LCH PDCP performs the order reordering operation shown in FIGS. 11 to 14.

Landscapes

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

Abstract

La présente invention concerne un système de communication mobile, et en particulier un procédé et un appareil de transmission/réception de données au moyen d'une pluralité de porteuses dans un système de communication mobile.
PCT/KR2014/010243 2013-10-29 2014-10-29 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 WO2015065039A1 (fr)

Priority Applications (8)

Application Number Priority Date Filing Date Title
EP14857431.2A EP3065449B1 (fr) 2013-10-29 2014-10-29 Procédés et appareils de transmission/réception de données à l'aide d'une pluralité de porteuses dans un système de communication mobile
EP21176384.2A EP3927010A1 (fr) 2013-10-29 2014-10-29 Procédé et appareil de transmission/réception de données à l'aide d'une pluralité de porteuses d'un système de communication sans fil
US15/033,579 US10149175B2 (en) 2013-10-29 2014-10-29 Method and apparatus for transmitting/receiving data using plurality of carriers in mobile communication system
ES14857431T ES2878127T3 (es) 2013-10-29 2014-10-29 Procedimientos y aparatos para transmitir/recibir datos utilizando una pluralidad de portadoras en un sistema de comunicación móvil
CN201910940891.1A CN110691425B (zh) 2013-10-29 2014-10-29 在移动通信系统中的终端、基站及其方法
CN201480059854.5A CN105684501B (zh) 2013-10-29 2014-10-29 在移动通信系统中使用多个载波传送/接收数据的方法和装置
US16/206,897 US11026102B2 (en) 2013-10-29 2018-11-30 Method and apparatus for transmitting/receiving data using plurality of carriers in mobile communication system
US17/334,585 US20210289368A1 (en) 2013-10-29 2021-05-28 Method and apparatus for transmitting/receiving data using plurality of carriers in mobile communication system

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
KR10-2013-0129230 2013-10-29
KR20130129230 2013-10-29
KR20130132103 2013-11-01
KR10-2013-0132103 2013-11-01
KR10-2014-0038857 2014-04-01
KR1020140038857A KR102157798B1 (ko) 2013-10-29 2014-04-01 이동 통신 시스템에서 복수의 캐리어를 이용하는 데이터 송수신 방법 및 장치

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US15/033,579 A-371-Of-International US10149175B2 (en) 2013-10-29 2014-10-29 Method and apparatus for transmitting/receiving data using plurality of carriers in mobile communication system
US16/206,897 Continuation US11026102B2 (en) 2013-10-29 2018-11-30 Method and apparatus for transmitting/receiving data using plurality of carriers in mobile communication system

Publications (1)

Publication Number Publication Date
WO2015065039A1 true WO2015065039A1 (fr) 2015-05-07

Family

ID=53004553

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2014/010243 WO2015065039A1 (fr) 2013-10-29 2014-10-29 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

Country Status (2)

Country Link
CN (1) CN110691425B (fr)
WO (1) WO2015065039A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110574487A (zh) * 2017-05-05 2019-12-13 高通股份有限公司 分组数据汇聚协议(pdcp)实体处的分组重复
CN110612739A (zh) * 2017-04-28 2019-12-24 三星电子株式会社 用于无线通信系统中的通信的方法和装置
WO2020067693A1 (fr) * 2018-09-28 2020-04-02 Samsung Electronics Co., Ltd. Procédé et appareil pour la transmission d'un rapport d'état de tampon dans un système de communication sans fil
US11700542B2 (en) 2017-03-23 2023-07-11 Samsung Electronics Co., Ltd. Method and apparatus for processing data for packet duplication

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110268048A1 (en) * 2010-05-03 2011-11-03 Nokia Siemens Networks Oy and Nokia Corporation Feedback For Inter-Radio Access Technology Carrier Aggregation
US20120002635A1 (en) * 2009-03-16 2012-01-05 Jae Hoon Chung Method and apparatus for supporting carrier aggregation
US20130083783A1 (en) * 2011-10-03 2013-04-04 Vivek Gupta Multi-RAT Carrier Aggregation for Integrated WWAN-WLAN Operation
WO2013104416A1 (fr) * 2012-01-11 2013-07-18 Nokia Siemens Networks Oy Préparation de cellule secondaire en vue d'une agrégation de porteuses inter sites

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE602004012862T2 (de) * 2004-10-01 2009-04-09 Matsushita Electric Industrial Co., Ltd., Kadoma-shi Dienstgüte-bewusste Ablaufsteuerung für Aufwärtsübertragungen über zugeordneten Kanälen
US8873474B2 (en) * 2008-10-17 2014-10-28 Telefonaktiebolaget L M Ericsson (Publ) Method and mobile terminal providing priority-based uplink scheduling information
CN101867871B (zh) * 2009-04-17 2013-02-13 电信科学技术研究院 一种选择逻辑信道进行数据处理的方法、系统和设备
EP2647259B1 (fr) * 2010-12-03 2018-01-03 Interdigital Patent Holdings, Inc. Procédés et appareil permettant d'exécuter une agrégation de porteuses selon plusieurs technologies d'accès radio
US20140334371A1 (en) * 2012-01-27 2014-11-13 Samsung Electronics Co., Ltd. Method and apparatus for transmitting and receiving data by using plurality of carriers in mobile communication systems
KR102157798B1 (ko) * 2013-10-29 2020-09-18 삼성전자 주식회사 이동 통신 시스템에서 복수의 캐리어를 이용하는 데이터 송수신 방법 및 장치

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120002635A1 (en) * 2009-03-16 2012-01-05 Jae Hoon Chung Method and apparatus for supporting carrier aggregation
US20110268048A1 (en) * 2010-05-03 2011-11-03 Nokia Siemens Networks Oy and Nokia Corporation Feedback For Inter-Radio Access Technology Carrier Aggregation
US20130083783A1 (en) * 2011-10-03 2013-04-04 Vivek Gupta Multi-RAT Carrier Aggregation for Integrated WWAN-WLAN Operation
WO2013104416A1 (fr) * 2012-01-11 2013-07-18 Nokia Siemens Networks Oy Préparation de cellule secondaire en vue d'une agrégation de porteuses inter sites

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL.: "Impact analysis of bearer split options for multi-site aggregation", R2-131784, 3GPP TSG-RAN WG2 MEETING #82, 20 May 2013 (2013-05-20), XP050700049, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran[WG2_RL2/TSGR2_82/docs/R2-131784.zip> *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11700542B2 (en) 2017-03-23 2023-07-11 Samsung Electronics Co., Ltd. Method and apparatus for processing data for packet duplication
CN110612739A (zh) * 2017-04-28 2019-12-24 三星电子株式会社 用于无线通信系统中的通信的方法和装置
CN110612739B (zh) * 2017-04-28 2024-05-03 三星电子株式会社 用于无线通信系统中的通信的方法和装置
CN110574487A (zh) * 2017-05-05 2019-12-13 高通股份有限公司 分组数据汇聚协议(pdcp)实体处的分组重复
WO2020067693A1 (fr) * 2018-09-28 2020-04-02 Samsung Electronics Co., Ltd. Procédé et appareil pour la transmission d'un rapport d'état de tampon dans un système de communication sans fil
US11350308B2 (en) 2018-09-28 2022-05-31 Samsung Electronics Co., Ltd Method and apparatus for transmitting buffer status report in wireless communication system

Also Published As

Publication number Publication date
CN110691425B (zh) 2023-04-07
CN110691425A (zh) 2020-01-14

Similar Documents

Publication Publication Date Title
WO2015046976A1 (fr) Procédé et appareil d&#39;émission et de réception de données au moyen de plusieurs porteuses dans un système de communication mobile
WO2018128501A1 (fr) Procédé de transmission d&#39;un canal de commande de liaison montante d&#39;un terminal dans un système de communication sans fil, et dispositif associé
WO2018128452A1 (fr) Procédé de transmission de paquets de données sans perte sur la base d&#39;une structure de qualité de service (qos) dans un système de communication sans fil et dispositif associé
WO2017007171A1 (fr) Procédé pour déclencher un rapport d&#39;état de mémoire tampon en double connectivité et dispositif associé
WO2014163288A1 (fr) Procédé servant à réaliser une attribution de priorité de canal logique et son dispositif de communication
WO2013055145A1 (fr) Procédé et dispositif de transmission de signal de commande inversé dans un système de communication mobile
WO2013168850A1 (fr) Procédé et appareil de commande de réception discontinue dans un système de communication mobile
WO2021215829A1 (fr) Procédé et appareil permettant d&#39;effectuer une transmission de psfch dans une v2x en nr
WO2016021983A1 (fr) Procédé et appareil de communication sans fil dans un système de communication sans fil prenant en charge des communications de dispositif à dispositif
WO2014112850A1 (fr) Procédé et appareil pour fournir efficacement des informations de configuration de duplexage par répartition dans le temps à un équipement utilisateur et à déterminer le chronométrage de transmission sens montant dans un système de communication mobile supportant le duplexage par répartition dans le temps
WO2014025141A1 (fr) Procédé pour transférer un rapport d&#39;état et dispositif de communication de celui-ci dans un système de communication sans fil
WO2013176473A1 (fr) Procédé et dispositif d&#39;émission et de réception de données dans un système de communication mobile
WO2011126311A2 (fr) Procédé et appareil permettant de traiter des informations de planification dans un système de communication mobile
WO2017003118A1 (fr) Procédé de transmission de données dans une connectivité double et dispositif pour cela
WO2015020344A1 (fr) Appareil et procédé de transmission de données dans un système de communication radio d&#39;un réseau hétérogène
WO2021162509A2 (fr) Procédé et appareil d&#39;exécution de sélection de ressources et d&#39;exécution de harq dans un v2x nr
WO2017007148A1 (fr) Procédé pour annuler un rapport d&#39;état de tampon (bsr) ou une requête de planification (sr) dans une connectivité double et un dispositif à cet effet
WO2010131850A2 (fr) Procédé et appareil d&#39;émission et de réception de données doubles dans un système de communication sans fil multiporteuse
WO2015111965A1 (fr) Système et procédé de transmission de données de priorité d&#39;une pluralité de stations de base
WO2015020461A1 (fr) Procédé et appareil de transmission de rapport d&#39;état de tampon dans un système de communication sans fil
WO2019035670A1 (fr) Procédé et appareil de transmission et de réception de paquets en double dans un système de communication mobile de prochaine génération
WO2021125712A1 (fr) Procédé et appareil de gestion de temporisateur associé à la transmission de segmentation d&#39;un message rrc dans un système de communication mobile de prochaine génération
WO2017007147A1 (fr) Procédé de déclenchement de rapport d&#39;état de tampon dans une connectivité double et dispositif correspondant
WO2020226389A1 (fr) Procédé et dispositif pour rapporter une capacité d&#39;ue dans un système de communication sans fil
WO2021194123A1 (fr) Procédé et appareil de planification inter-porteuse dans un système de communication mobile de nouvelle génération

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2014857431

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 15033579

Country of ref document: US

Ref document number: 2014857431

Country of ref document: EP