WO2015005738A1 - Procédé et appareil pour exploiter des données d'une couche de commande de liaison radio dans un système de communication sans fil - Google Patents

Procédé et appareil pour exploiter des données d'une couche de commande de liaison radio dans un système de communication sans fil Download PDF

Info

Publication number
WO2015005738A1
WO2015005738A1 PCT/KR2014/006286 KR2014006286W WO2015005738A1 WO 2015005738 A1 WO2015005738 A1 WO 2015005738A1 KR 2014006286 W KR2014006286 W KR 2014006286W WO 2015005738 A1 WO2015005738 A1 WO 2015005738A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
layer
rlc
data
flow control
Prior art date
Application number
PCT/KR2014/006286
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
Application filed by 주식회사 팬택 filed Critical 주식회사 팬택
Publication of WO2015005738A1 publication Critical patent/WO2015005738A1/fr

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/10—Flow control between communication endpoints
    • H04W28/12—Flow control between communication endpoints using signalling between network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/36—Flow control; Congestion control by determining packet size, e.g. maximum transfer unit [MTU]
    • 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

Definitions

  • the present invention relates to wireless communication, and more particularly, to information transmission for operating data in a radio link control layer for a terminal dually connected to a plurality of base stations.
  • the radio link control (RLC) layer in the RB may be configured in the form of a sub-entity for each eNB or an entity for multiple eNBs.
  • the sub-entities for each base station are sub-entities defined in the RLC layer in the RB serviced by a plurality of base stations.
  • the RLC layer may be used in a structure in which each base station is independently located.
  • the sub-entity is not limited to being referred to as a substructure of the entity and may be treated the same as the entity.
  • An entity for a plurality of base stations is a single entity present in the RB serviced by the plurality of base stations.
  • a master RLC layer may be used in a structure in which a master RLC layer is located in a master base station and a slave RLC layer is located in a secondary base station. 3) For an RLC layer in a single RB serviced by a plurality of base stations, a master RLC layer may be defined at the master base station and a slave RLC layer may be defined at the secondary base station. At this time, a basic RLC function is implemented in the master RLC, and a segmentation / concatenation function is implemented only for downlink transmission data in the slave RLC layer.
  • the secondary base station transmits data received from the PDCP layer or the master RLC layer in a single RB of the master base station to the terminal through the RLC layer or to the terminal through the slave RLC layer, MAC layer, and PHY layer.
  • data in the single RB is distributed to each of a plurality of base stations defined in the RB according to a radio resource amount or a transmission rate allocated to the corresponding terminal.
  • a MAC layer In order to support different data flow control schemes for distributing data in the single RB between base stations, information for data operation is exchanged between a MAC layer and a layer responsible for flow control, for example, an RLC / PDCP layer. Is required.
  • the network through the master cell for the terminal It is to support additional data service through the secondary cell while maintaining a wireless connection and data service.
  • Another technical problem of the present invention is to provide a method and apparatus for operating data in a radio connection control layer for a dual connected terminal.
  • Another technical problem of the present invention is to provide a method and apparatus for transmitting information for data operation of a radio connection control layer for a dual connected terminal.
  • Another technical problem of the present invention is to provide a method and apparatus for controlling a data flow for distributing data in the radio bearer by configuring a bearer split for a plurality of base stations.
  • a method of operating a data of a first base station (eNB) in a wireless communication system supporting dual connectivity for a UE includes determining flow control request information for data flow control regarding the dual connection, and forwarding the flow control request information to a second base station configured with the dual connection, wherein the flow control
  • the request information is characterized in that the report information on the PDCP layer of the second base station.
  • a first base station for operating data in a wireless communication system supporting dual connectivity for a terminal.
  • the first base station includes a control unit for determining flow control request information for data flow control for the dual connection, a transmission unit for transmitting the flow control request information to a second base station configured with the dual connection,
  • Flow control request information is characterized in that the report information on the PDCP layer of the second base station.
  • information for controlling data flow in a bearer split structure may be exchanged between a plurality of base stations, thereby supporting a dual connected terminal.
  • FIG. 1 shows a wireless communication system to which the present invention is applied.
  • FIG. 2 is a block diagram illustrating a radio protocol structure for a user plane.
  • FIG. 3 is a block diagram illustrating a radio protocol architecture for a control plane.
  • FIG. 4 is a diagram illustrating an outline of an example of an RLC sublayer model to which the present invention is applied.
  • FIG 5 shows an example of a dual connection situation of a terminal applied to the present invention.
  • 6 to 8 illustrate an example in which a terminal establishes dual connectivity with a secondary base station and a master base station.
  • FIG. 9 is a flowchart illustrating an example of a method of operating data of a radio connection control layer according to the present invention.
  • FIG. 10 is a block diagram illustrating an example of an apparatus for operating data of a radio connection control layer according to the present invention.
  • the present specification describes a wireless communication network
  • the operation performed in the wireless communication network is performed in the process of controlling the network and transmitting data in the system (for example, the base station) that is in charge of the wireless communication network, or the corresponding wireless Work may be done at the terminal coupled to the network.
  • the E-UMTS system may be an Evolved-UMTS Terrestrial Radio Access (E-UTRA) or Long Term Evolution (LTE) or LTE-A (Advanced) system.
  • Wireless communication systems include Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier-FDMA (SC-FDMA), and OFDM-FDMA
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single Carrier-FDMA
  • OFDM-FDMA OFDM-FDMA
  • OFDM-FDMA Various multiple access schemes such as OFDM, TDMA, and OFDM-CDMA may be used.
  • an Evolved-UMTS Terrestrial Radio Access Network is a base station providing a control plane (CP) and a user plane (UP) to a user equipment (UE) 10. (20; evolved NodeB: eNB).
  • the terminal 10 may be fixed or mobile and may be called by other terms such as mobile station (MS), advanced MS (AMS), user terminal (UT), subscriber station (SS), and wireless device (Wireless Device). .
  • MS mobile station
  • AMS advanced MS
  • UT user terminal
  • SS subscriber station
  • Wireless Device Wireless Device
  • the base station 20 generally refers to a station communicating with the terminal 10, and includes a base station (BS), a base transceiver system (BTS), an access point, and a femto-eNB. It may be called other terms such as a pico base station (pico-eNB), a home base station (Home eNB), a relay (relay).
  • the base stations 20 are physically connected through an optical cable or a digital subscriber line (DSL), and may exchange signals or messages with each other through an X2 interface.
  • DSL digital subscriber line
  • the base station 20 connects with an Evolved Packet Core (EPC) 30 through the S1 interface, more specifically, a Mobility Management Entity (MME) and an S1-GW (Serving Gateway) through S1-MME. do.
  • EPC Evolved Packet Core
  • MME Mobility Management Entity
  • S1-GW Serving Gateway
  • the EPC 30 includes an MME, an S-GW, and a packet data network-gateway (P-GW).
  • the MME has access information of the terminal 10 or information on the capability of the terminal 10, and this information is mainly used for mobility management of the terminal 10.
  • the S-GW is a gateway having an E-UTRAN as an endpoint
  • the P-GW is a gateway having a PDN (Packet Data Network) as an endpoint.
  • Integrating the E-UTRAN and the EPC 30 may be referred to as an EPS (Evoled Packet System), and the traffic flows from the radio link that the terminal 10 connects to the base station 20 to the PDN connecting to the service entity are all IP. It works based on (Internet Protocol).
  • EPS Evoled Packet System
  • the air interface between the terminal and the base station is called a "Uu interface".
  • Layers of the radio interface protocol between the terminal and the network are the first layer L1 and the second layer L2 defined in a 3GPP (3rd Generation Partnership Project) series communication system (UMTS, LTE, LTE-Advanced, etc.). ), And may be divided into a third layer L3.
  • the physical layer belonging to the first layer provides an information transfer service using a physical channel
  • the RRC (Radio Resource Control) layer located in the third layer exchanges an RRC message for the UE. Control radio resources between network and network.
  • FIG. 2 is a block diagram showing a radio protocol architecture for a user plane
  • FIG. 3 is a block diagram showing a radio protocol architecture for a control plane.
  • the user plane is a protocol stack for user data transmission
  • the control plane is a protocol stack for control signal transmission.
  • a physical layer (PHY) layer provides an information transfer service to a higher layer using a physical channel.
  • the physical layer is connected to a medium access control (MAC) layer, which is an upper layer, through a transport channel.
  • MAC medium access control
  • Data is transmitted through a transport channel between the MAC layer and the physical layer. Transport channels are classified according to how data is transmitted over the air interface.
  • data is transmitted through a physical channel between different physical layers (ie, between physical layers of a transmitter and a receiver).
  • the physical channel may be modulated by an orthogonal frequency division multiplexing (OFDM) scheme and utilizes space generated by time, frequency, and a plurality of antennas as radio resources.
  • OFDM orthogonal frequency division multiplexing
  • the physical downlink control channel (PDCCH) of the physical channel informs the UE of resource allocation of a paging channel (PCH) and downlink shared channel (DL-SCH) and hybrid automatic repeat request (HARQ) information related to the DL-SCH.
  • the PDCCH may carry an uplink scheduling grant informing the UE of resource allocation of uplink transmission.
  • a physical control format indicator channel (PCFICH) informs the UE of the number of OFDM symbols used for PDCCHs and is transmitted every subframe.
  • the PHICH physical hybrid ARQ Indicator Channel
  • the physical uplink control channel (PUCCH) carries uplink control information such as HARQ ACK / NAK, scheduling request, and CQI for downlink transmission.
  • a physical uplink shared channel (PUSCH) carries an uplink shared channel (UL-SCH).
  • the PUSCH may include channel state information (CSI) information such as HARQ ACK / NACK and CQI when necessary according to the configuration and request of a base station.
  • CSI channel state information
  • the MAC layer may perform multiplexing or demultiplexing into a transport block provided as a physical channel on a transport channel of a MAC service data unit (SDU) belonging to the logical channel and mapping between the logical channel and the transport channel.
  • SDU MAC service data unit
  • the MAC layer provides a service to a Radio Link Control (RLC) layer through a logical channel.
  • RLC Radio Link Control
  • the logical channel may be divided into a control channel for transmitting control region information and a traffic channel for delivering user region information.
  • services provided from the MAC layer to a higher layer include data transfer or radio resource allocation.
  • Functions of the RLC layer include concatenation, segmentation, and reassembly of RLC SDUs.
  • the RLC layer In order to guarantee the various quality of service (QoS) required by the radio bearer (RB), the RLC layer has a transparent mode (TM), an unacknowledged mode (UM), and an acknowledged mode (Acknowledged Mode). Three modes of operation (AM).
  • unconfirmed mode configures real-time data transmission, such as data streaming or Voice over Internet Protocol (VoIP), and focuses on speed rather than reliability of data.
  • the acknowledgment mode focuses on the reliability of the data and is suitable for large data transmissions or data transmissions that are less sensitive to transmission delays.
  • the base station determines the mode of the RLC in the RB corresponding to each EPS bearer based on the Quality of Service (QoS) information of each EPS bearer that is connected to the terminal and configures the parameters in the RLC to satisfy the QoS.
  • QoS Quality of Service
  • the RLC SDUs are supported in various sizes, and for example, may be supported in units of bytes.
  • RLC protocol data units PDUs
  • PDUs are defined only when a transmission opportunity is notified from a lower layer (eg, MAC layer), and when the transmission opportunity is notified, the RLC PDUs are delivered to the lower layer.
  • the transmission opportunity may be informed with the size of the total RLC PDUs to be transmitted.
  • the transmission opportunity and the size of the total RLC PDUs to be transmitted may be separately reported.
  • the RLC layer will be described in detail with reference to FIG. 4.
  • Functions of the Packet Data Convergence Protocol (PDCP) layer in the user plane include delivery of user data, header compression, and ciphering. Functions of the PDCP layer in the user plane include the transmission of control plane data and encryption / integrity protection.
  • PDCP Packet Data Convergence Protocol
  • the RRC layer is responsible for the control of logical channels, transport channels, and physical channels in connection with configuration, re-configuration, and release of RBs.
  • RB means a logical path provided by the first layer (PHY layer) and the second layer (MAC layer, RLC layer, PDCP layer) for data transmission between the terminal and the network.
  • the configuration of the RB means a process of defining characteristics of a radio protocol layer and a channel to provide a specific service, and setting each specific parameter and operation method.
  • the RB may be further classified into a signaling RB (SRB) and a data RB (DRB).
  • SRB signaling RB
  • DRB data RB
  • the physical channel is composed of several symbols in the time domain and several sub-carriers in the frequency domain.
  • One sub-frame consists of a plurality of OFDM symbols in the time domain.
  • One subframe consists of a plurality of resource blocks, and one resource block consists of a plurality of OFDM symbols and a plurality of subcarriers.
  • each subframe may use specific subcarriers of specific symbols (eg, the first symbol) of the corresponding subframe for the physical downlink control channel (PDCCH).
  • the transmission time interval (TTI) which is a unit time for transmitting data, is 1 ms corresponding to one subframe.
  • FIG. 4 is a diagram illustrating an outline of an example of an RLC sublayer model to which the present invention is applied.
  • RLC entities are classified into different RLC entities according to data transmission schemes. For example, there is a TM RLC entity 400, a UM RLC entity 420, and an AM RLC entity 440.
  • the UM RLC entity 400 may be configured to receive or forward RLC PDUs over logical channels (eg, DL / UL DTCH, MCCH or MTCH).
  • the UM RLC entity may deliver or receive a UMD PDU (Unacknowledged Mode Data PDU).
  • the UM RLC entity consists of a sending UM RLC entity or a receiving UM RLC entity.
  • the transmitting UM RLC entity receives the RLC SDUs from the higher layer and sends the RLC PDUs to the peer receiving UM RLC entity via the lower layer.
  • the sending UM RLC entity constructs UMD PDUs from RLC SDUs, the total size of the RLC PDUs indicated by the lower layer by segmenting or concatenating the RLC SDUs when a specific transmission opportunity is notified by the lower layer.
  • the UMD PDUs are configured to be within and the related RLC headers are included in the UMD PDU.
  • the receiving UM RLC entity delivers the RLC SDUs to the upper layer and receives the RLC PDUs from the peer receiving UM RLC entity through the lower layer.
  • the receiving UM RLC entity detects whether the UMD PDUs have been received in duplicate, discards the redundant UMD PDUs, and when the UMD PDUs are received out of sequence.
  • Reorder the UMD PDUs detect loss of UMD PDUs in the lower layer to avoid excessive reordering delays, reassemble RLC SDUs from the rearranged UMD PDUs, and In addition, the reassembled RLC SDUs are delivered to an upper layer in an ascending order of an RLC sequence number, and UMD PDUs cannot be reassembled into an RLC SDU due to a loss of UMD PDUs belonging to a specific RLC SDU in a lower layer. Can be discarded.
  • the receiving UM RLC entity Upon RLC re-establishment, the receiving UM RLC entity will reassemble the RLC SDUs from the received UMD PDUs, if possible, out of sequence and forward them to the higher layer, and the remaining UMD PDUs that could not be reassembled into RLC SDUs are Discard all, initialize the relevant state variables and stop the associated timers.
  • the AM RLC entity 440 may be configured to receive or deliver RLC PDUs through logical channels (eg, DL / UL DCCH or DL / UL DTCH).
  • the AM RLC entity delivers or receives an AMD PDU or ADM PDU segment, and delivers or receives an RLC control PDU (eg, a STATUS PDU).
  • AM RLC entity 440 delivers STATUS PDUs to peer AM RLC entities to provide positive and / or negative acknowledgment of RLC PDUs (or portions thereof). This may be called STATUS reporting.
  • a polling procedure may be involved from the peer AM RLC entity to trigger STATUS reporting. That is, an AM RLC entity may poll the peer AM RLC entity to trigger STATUS reporting at the corresponding peer AM RLC entity.
  • the STATUS PDU is sent at the next transmission opportunity. Accordingly, the UE estimates the size of the STATUS PDU and considers the STATUS PDU as data available for transmission in the RLC layer.
  • the AM RLC entity is composed of a transmitting side and a receiving side.
  • the transmitter of the AM RLC entity receives the RLC SDUs from the upper layer and sends the RLC PDUs to the peer AM RLC entity via the lower layer.
  • the transmitter of the AM RLC entity configures AMD PDUs from the RLC SDUs, it subdivides the RLC SDUs to fit within the total size of the RLC PDU (s) indicated by the lower layer when a particular transmission opportunity is notified by the lower layer. (segment) Concatenate to construct AMD PDUs.
  • the transmitter of the AM RLC entity supports retransmission of RLC data PDUs (ARQ).
  • the AM RLC entity retransmits the RLC data PDU into AMD PDU segments. Re-segment.
  • the number of re-segmentation is not limited.
  • the transmitter of the AM RLC entity creates AMD PDUs from RLC SDUs received from the upper layer or AMD PDU segments from RLC data PDUs to be retransmitted, the relevant RLC headers are included in the RLC data PDU.
  • the receiver of the AM RLC entity delivers the RLC SDUs to the upper layer and receives the RLC PDUs from the peer AM RLC entity via the lower layer.
  • the receiver of the AM RLC entity When the receiver of the AM RLC entity receives the RLC data PDUs, it detects whether the RLC data PDUs have been received in duplicate, discards the duplicate RLC data PDUs, and receives the RLC data PDUs out of sequence. Reorder the order of RLC data PDUs, detect the loss of RLC data PDUs occurring in the lower layer, request retransmission to the peer AM RLC entity, and reassemble RLC SDUs from the rearranged RLC data PDUs. reassemble, and deliver the reassembled RLC SDUs to a higher layer in sequence.
  • the receiver of the AM RLC entity When resetting the RLC, the receiver of the AM RLC entity, possibly out of sequence, reassembles the RLC SDUs from the received RLC data PDUs and delivers them to the higher layer, all remaining RLC data PDUs that cannot be reassembled into RLC SDUs. Discard it, initialize the relevant state variables and stop the associated timers.
  • the following table shows an example of functions supported by the RLC sublayer.
  • one of a plurality of physically or logically divided base stations configured with dual connectivity to a terminal is a master base station (also referred to as a central base station, an anchor base station, or a serving base station).
  • the other (or more) base stations as secondary base stations (also called small base stations, assisting base stations or non-serving base stations).
  • the macro base station may be a master base station
  • the small base station may be a secondary base station.
  • FIG 5 shows an example of a dual connection situation of a terminal applied to the present invention.
  • the terminal 550 located in the service area of the master cell in the master base station 500 enters an area overlaid with the service area of the secondary cell in the secondary base station 510. .
  • the network configures dual connectivity for the terminal.
  • the F2 frequency band is assigned to the master base station
  • the F1 frequency band is assigned to the secondary base station.
  • the UE may receive a service through the F2 frequency band from the master base station and simultaneously receive a service through the F1 frequency band from the secondary base station.
  • the master base station is F2 and the secondary base station is described as using the F1 frequency band.
  • the present invention is not limited thereto, and the master base station and the secondary base station may also use the same F1 or F2 frequency band.
  • FIGS. 7 and 8 are bearer split cases serving through a master base station and a secondary base station in a single RB.
  • the bearer split may be referred to as multi flow, multiple node (eNB) transmission, inter-eNB carrier aggregation, or the like. Of course, this does not exclude the case where the present invention is not a bearer split.
  • the master base station includes a PDCP, RLC, MAC, and PHY layers, but the secondary base station includes an RLC, MAC, and PHY layers.
  • the PDCP layer of the master base station is connected to the RLC layer of the secondary base station using the Xn interface protocol through the backhaul.
  • the Xn interface protocol may be an X2 interface protocol defined between base stations in the LTE system.
  • Only the master base station has two PDCP layers, and each PDCP layer is connected to a different RLC layer.
  • the PDCP layer of the master base station and the RLC layer of the secondary base station are connected to the “# 2 RB” (second RB).
  • FIG. 6 is also called an independent RLC type or a single RLC entity type.
  • the master base station includes a PDCP, RLC, MAC, and PHY layers, but the secondary base station includes an RLC, MAC, and PHY layers.
  • the PDCP layer of the master base station is connected to the RLC layer of the secondary base station using the Xn interface protocol.
  • the Xn interface protocol may be an X2 interface protocol defined between base stations in the LTE system.
  • the PDCP layer of one master base station is connected to both the RLC layer of the master base station and the RLC layer of the secondary base station.
  • the RLC layer of the master base station is referred to as # 1 sub-entity (first sub-entity), and the RLC layer of the secondary base station is referred to as # 2 sub-entity (second sub-entity).
  • the sub-entities are divided into one-to-one matching of transmission and reception.
  • the sub-entity may be called an entity.
  • the RLC layer is in duplicate form. Each sub-entity is independent but there are two sub-entities (# 1 sub-entity and # 2 sub-entity) within one RB (ie # 1 RB).
  • RLC parameters should be configured separately for the RLC-AM # 1 sub-entity and the RLC-AM # 2 sub-entity, respectively. Because delay time that occurs when data serviced through each RLC-AM sub-entity is delivered to the UE may be different, timer values to be set in consideration of the delay time may be set for each sub-entity. This may be different from each other. If delay times of data transmitted through each sub-entity are the same, values of timers to be set for each sub-entity may be the same. This may be determined at the master base station, at a secondary base station, or at a network including a master base station and a secondary base station.
  • data to be delivered via PDCP in the same RB may be transmitted on one sub-entity of either an RLC-AM # 1 sub-entity or an RLC-AM # 2 sub-entity.
  • an identifier may be further transmitted by the terminal that receives the data to identify which sub-entity the data is transmitted through.
  • FIG. 7 is also called a sub-entity RLC type of bearer splitcase. However, the example of FIG. 7 is not necessarily applied only to the bearer split.
  • the master base station includes a PDCP, RLC, MAC, and PHY layers, but the secondary base station includes an RLC, MAC, and PHY layers.
  • the RLC layer of the master base station is connected to the RLC layer of the secondary base station using the Xn interface protocol.
  • the RLC layer of the secondary base station is connected to the RLC layer of the master base station. Therefore, two base stations are controlled through one RB (that is, RB # 1).
  • the RLC layer of the master base station may be referred to as a master RLC layer
  • the RLC layer of the secondary base station may be referred to as a slave RLC layer.
  • the splitting operation of the slave RLC includes a grouping of a plurality of RLC PDUs or a grouping of AMD PDU segments divided in a master RLC.
  • concatenation is possible for the AMD / UM PDU of the slave RLC layer of the base station.
  • the transmission between the terminal and the base station may be a single transmission instead of a time division multiplexing (TDM) transmission.
  • TDM time division multiplexing
  • the MAC scheduler is mainly responsible for scheduling radio resources, and the situation of the MAC layer of the secondary base station differs from that of the secondary base station.
  • the master RLC layer allocates (or splits, concatenates, or recombines) PDUs based on the MAC layer of the master base station, and the slave RLC layer performs division or concatenation based on the MAC layer of the secondary base station.
  • the dually connected terminal may include only one RLC layer. Therefore, it is also possible to perform uplink transmission only to the master base station in terms of uplink data transmission (for example, PUSCH) (also referred to as “single uplink”).
  • uplink data transmission for example, PUSCH
  • FIG. 8 is also called a master-slave RLC type among bearer split cases. However, the example of FIG. 8 is not necessarily applied only to the bearer split.
  • the MAC layer in the base station includes at least one dynamic resource scheduler, wherein the at least one dynamic resource scheduler allocates physical layer resources for DL-SCH and UL-SCH transport channels. do.
  • the scheduler When a plurality of terminals share a resource, the scheduler considers a traffic volume and QoS requirements of each terminal and associated RBs.
  • the grant (per UE grant) for each terminal is used only for granting the right to transmit on the UL-SCH. In other words, the “per UE per RB” grant does not exist. This means that there is only a UL grant on a terminal basis. That is, there is no physical channel resource allocation scheme that allows UL transmission for a specific RB.
  • the scheduler may allocate resources in consideration of radio conditions of the terminal identified through the measurements generated at the base station or the measurement reported by the terminal.
  • the radio resource allocation of the scheduler is valid in one or more Transmission Time Intervals (TTIs).
  • TTIs Transmission Time Intervals
  • Resource assignment is composed of a physical radio bearer (PRB) and a modulation and coding scheme (MCS).
  • PRB physical radio bearer
  • MCS modulation and coding scheme
  • an allocation for a time period longer than one TTI may require additional information (eg, an allocation time, an allocation repetition factor).
  • the bearer split refers to a structure in which a single RB is divided into two flows (or more flows) through a plurality of base stations and transmitted. Bearer splits are also referred to as multiflows in that information is delivered through a plurality of flows.
  • each base station may include a Packet Data Convergence Protocol (PDCP) layer, a MAC layer, and an RLC layer, but the layer responsible for flow control is limited to only one base station (ie, a master base station). Included. If the layer in charge of the flow control is a PDCP layer, the PDCP layer is included only in the master base station.
  • PDCP Packet Data Convergence Protocol
  • the MAC layer of the base station in the existing LTE system delivers information on the amount of data, transmission opportunities, etc. to be transmitted to the RLC layer to the RLC layer.
  • the RLC layer configures an RLC PDU by splitting or combining the RLC SDU data received from the PDCP layer located in the same base station based on the information received from the MAC layer. Thereafter, the MAC layer receives the RLC PDU configured in the RLC from the RLC layer in the form of a MAC SDU.
  • the present invention proposes a method and apparatus for transferring information between base stations (ie, a master base station or a secondary base station) of an RB corresponding to an EPS bearer (1-to-1).
  • base stations ie, a master base station or a secondary base station
  • a function performed by the flow control layer is performed to the PDCP layer or the master RLC layer.
  • the flow control layer may be configured in the master base station separately from the PDCP layer or the master RLC layer.
  • the secondary base station transmits data received from the PDCP layer in the single RB of the master base station to the RLC layer (or data received from the master RLC layer to the slave RLC layer) and transmits to the terminal through the MAC layer, PHY layer.
  • the data in the single RB is distributed to the secondary base station and the master base station according to the radio resource amount or transmission rate that each base station can allocate to the corresponding terminal.
  • a method and data distribution for defining information exchanged between a MAC layer and an RLC layer (or PDCP layer) to support data flow control for distribution of data in the single RB, and receiving the information from the MAC layer Suggest an operation method.
  • the present invention is a situation in which a terminal configures dual connectivity with a master cell in a master base station and a secondary cell in a secondary base station and configures RRC (Radio Resource Control) for supporting the dual connection.
  • RRC Radio Resource Control
  • a configuration of a bearer split limited to a single RB is described as an example, the scope of the present invention is not limited thereto, and the present invention may be applied to a bearer split for a plurality of RBs.
  • a bearer split for a signaling radio bearer may be configured, and in this case, a user plane (UP)
  • the defined bearer split scheme can be equally applied to SRBs defined in the control plane. That is, the configuration may be the same.
  • the terminal applied to the present invention may provide information distinguished for each RB (ie, information on whether bearer split is applied or not applied in each RB), and a plurality of RBs (eg, logical channel group). information commonly applied to the group) may be provided.
  • the configuration information for each RB is independent of each other.
  • the first RB includes information for configuring a bearer split (for example, “MF on”)
  • the information on the second RB transmitted simultaneously with the information on the first RB may be RB flow reconfiguration ( RB flow reconfiguration) information (eg, “MF off”) may be included.
  • PDCP layer in RLC layer a case in which one entity over multiple eNBs exists in a plurality of base stations and a case in which a sub-entity for each eNB exists in each base station.
  • Information is transmitted, while in the second embodiment, the master-slave RLC case is transmitted with information “slave RLC layer to master RLC layer”.
  • FIG. 9 is a flowchart illustrating an example of a method of operating data of a radio connection control layer according to the present invention.
  • the secondary base station determines “Transport block size” to be allocated to each subframe in the MAC layer (hereinafter referred to as MAC scheduler) (S910).
  • the MAC layer of the secondary base station may request the size of the transport block and the RLC layer to request "data amount information (i.e., RLC PDU indicated by the lower layer when a specific transmission opportunity is notified by the lower layer).
  • Total flow of the information) is determined based on the“ flow control request information ”to be reported to the PDCP layer (ie, PDCP layer of the master base station) (S920).
  • “data amount information” may be set based on PBR (Prioritized Bit Rate) that can be set for each logical channel. If the TB size that can be allocated in this TTI is larger than the sum of the PBRs of all logical channels, it is transmitted.
  • PBR Primary Bit Rate
  • the block size and the “data amount information” requested from the RLC layer may be different. Therefore, considering both parameters, it is possible to determine the request information to be transmitted to the PDCP layer (or a layer in charge of flow control (ie, a new layer in the master base station rather than the PDCP layer)). Alternatively, only the size of the transport block may be considered or only “data amount information” requested by the RLC layer may be used.
  • the flow control request information may be referred to as MAC request information as a message of a MAC layer.
  • the secondary base station transmits the flow control request information to the master base station (S930).
  • the flow control request information is transmitted from the secondary base station to the master base station during downlink transmission, and an X2 interface protocol or a signaling protocol configured for exchanging information between base stations may be used to transmit the flow control request information. That is, information about the amount of data transmitted through the secondary base station among the total amount of data to be transmitted through the RB is transmitted to the master base station.
  • the related information is generated and transmitted in the secondary base station, “information on the total size of the RLC PDUs indicated by the MAC layer when a specific transmission opportunity is notified to the RLC layer by a lower layer (eg, the MAC layer)”. Itself is reported to the PDCP layer in real time (e.g., "on receipt of the flow control request information") or indicated by the MAC layer when a particular transmission opportunity is notified to the RLC layer by the lower layer (e.g. The average value taken over a certain time period is periodically reported to the PDCP layer, or when a particular transmission opportunity is notified to the RLC layer by a lower layer (e.g., the MAC layer).
  • a predetermined filtering method for example, an IIR (infinite impulse response) filtering method. It may be in the form reported to the PDCP layer.
  • t is the current time point
  • alpha is the “transport block size” or “data amount information” generated at that time
  • throughput () is the “transport block size” or “data amount information used for flow control request information. "to be.
  • the flow control request information may include “total size of RLC PDUs indicated by lower layer when a specific transmission opportunity is notified by lower layer”. This is because RLC PDUs are defined only when a transmission opportunity is notified from a lower layer (eg, MAC layer) and RLC PDUs can be delivered to a lower layer when the transmission opportunity is notified. That is, the flow control request information may include data amount information requested by the MAC layer to the RLC layer.
  • the flow control request information may include a data forwarding indicator.
  • the data forwarding indicator may be an indicator requesting data transmission or data transmission stop (hereinafter, referred to as a “data transmission / stop transmission request indicator”). That is, the secondary base station evaluates “information on the total size of the RLC PDUs indicated by the MAC layer where a specific transmission opportunity is notified to the RLC layer by the MAC layer” for a certain time period and periodically transmits data or data to the PDCP layer. The indicator requesting the transmission stop is transmitted to the master base station.
  • the evaluation may be performed by receiving a current data on how to process the information generated by the secondary base station and the measured value (eg, “in real time” is reported to the PDCP layer or an average value taken during a certain time period is periodically reported or predetermined). Is performed by comparing the filtered value of the filtered value (for example, the IIR filtering method) periodically for a predetermined time period.
  • the data forwarding indicator may be an indicator requesting a data amount change (eg, increase or decrease) (hereinafter, referred to as a “data amount change request indicator”). That is, the secondary base station evaluates “information on the total size of the RLC PDUs indicated by the MAC layer where a specific transmission opportunity is notified to the RLC layer by the MAC layer” for a predetermined time period and periodically changes the data amount to the PDCP layer ( Yes, increase or decrease) sends an indicator to the master base station.
  • a data amount change request indicator eg, increase or decrease
  • the evaluation may be performed by receiving a current data on how to process the information generated by the secondary base station and the measured value (eg, “in real time” is reported to the PDCP layer or an average value taken during a certain time period is periodically reported or predetermined). Is performed by comparing the filtered value of the filtered value (for example, the IIR filtering method) periodically for a predetermined time period.
  • the data amount change request indicator may indicate a relative amount based on the amount of data received by the RLC layer in the current secondary base station.
  • the data amount change request indicator is '000' to maintain the amount of data currently received, '001' to decrease to 1/2 of the amount of data currently received, and 1 of the currently received data amount. If it is to be reduced to / 4, it can be defined as '010', and if it is to be reduced to the minimum data amount, it can be defined as '011'.
  • the data amount change request indicator may indicate '101' if it is to increase to twice the amount of data currently received, '110' if it is to increase to four times the amount of data currently received, and 'to increase to the maximum data amount'. 111 'may be defined.
  • the data amount change request indicator may be defined as '0' for maintaining the amount of data currently received and '1' for reducing to the minimum data amount.
  • the flow control request information may include a buffer information indicator generated based on the status information of the buffer in the secondary base station.
  • the buffer information indicator may be generated based on data processing time (or dwell time in the buffer) or loss rate (loss rate or data rate dropped (or discarded) from the buffer).
  • the buffer may be in the form of a bearer split.
  • the buffer may be a buffer in the RLC layer configured for a single RB.
  • the buffer may be at least one of buffers that may exist in all layers below the RLC in the RB.
  • the buffer information indicator may be an indicator requesting data transmission or data transmission stop, or an indicator requesting a data amount change (eg, increase or decrease).
  • the secondary base station evaluates “information on the total size of the RLC PDUs indicated by the MAC layer where a specific transmission opportunity is notified to the RLC layer by the MAC layer” for a certain time period, and periodically transmits data or data to the PDCP layer.
  • the indicator requesting the transmission stop is transmitted to the master base station.
  • the evaluation may be performed by receiving a current data on how to process the information generated by the secondary base station and the measured value (eg, “in real time” is reported to the PDCP layer or an average value taken during a certain time period is periodically reported or predetermined). Is performed by comparing the filtered value of the filtered value (for example, the IIR filtering method) periodically for a predetermined time period.
  • the flow control request information includes information such as processing delay, loss rate, and data throughput generated based on the state information of the buffer in the secondary base station. It may include.
  • the processing delay may mean data processing time or residence time in a buffer.
  • the loss rate may mean a data rate dropped from the buffer.
  • the buffer may be in the form of a bearer split.
  • the buffer may be a buffer in the RLC layer configured for a single RB.
  • the buffer may be at least one of buffers that may exist in all layers below the RLC in the RB.
  • the flow control request information is not related to the transmission from the RLC layer in the secondary base station to the PDCP layer in the master base station but from the slave RLC layer in the secondary base station to the master RLC layer in the master base station.
  • the secondary base station determines the size of a transport block to be allocated to each subframe in the MAC scheduler.
  • the secondary base station i.e., MAC scheduler
  • the secondary base station requests the size of the transport block and the slave RLC layer to request "data amount information (i.e., the total number of RLC PDUs indicated by the lower layer when a specific transmission opportunity is notified by the lower layer. Size ”) to determine“ flow control request information ”to be reported to the master RLC layer.
  • the secondary base station transmits the flow control request information to the master base station.
  • the flow control request information is transmitted from the secondary base station to the master base station during downlink transmission, and an X2 interface protocol or a signaling protocol configured for exchanging information between base stations may be used to transmit the flow control request information. That is, information about the amount of data transmitted through the secondary base station among the amount of data to be transmitted through the RB is transmitted to the master base station.
  • FIG. 10 is a block diagram illustrating an example of an apparatus for operating data of a radio connection control layer according to the present invention.
  • the secondary base station may include a controller 1005 and a transmitter 1010.
  • the controller 1005 may be a processor
  • the transmitter 1010 may be an antenna.
  • the controller 1005 may include a MAC scheduler.
  • the controller 1005 determines a "Transport Block Size" to be allocated to each subframe in the MAC layer (hereinafter, referred to as a MAC scheduler).
  • the control unit 1005 is based on the size of the transport block and the "data amount information (that is, the total size of the RLC PDUs indicated by the lower layer when a specific transmission opportunity is notified by the lower layer) requested to the RLC layer"
  • the “flow control request information” to be reported to the PDCP layer ie, the PDCP layer of the master base station is determined.
  • the transmitter 1010 transmits the flow control request information to the master base station.
  • the flow control request information is transmitted from the secondary base station to the master base station during downlink transmission, and an X2 interface protocol or a signaling protocol configured for exchanging information between base stations may be used to transmit the flow control request information. That is, information about the amount of data transmitted through the secondary base station among the total amount of data to be transmitted through the RB is transmitted to the master base station.

Landscapes

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

Abstract

La présente invention concerne un procédé et un appareil pour exploiter des données d'une couche de commande de liaison radio dans un système de communication sans fil. La présente invention consiste à déterminer la taille d'un bloc de transport à attribuer à chaque sous-trame dans une couche MAC, à déterminer des informations de requête de commande de flux qui sont des informations rapportées à une couche PDCP d'un nœud B évolué (eNB) maître, doublement connecté, sur la base de la taille du bloc de transport et d'informations de quantité de données que la couche MAC demande auprès d'une couche RLC, et à transmettre les informations de requête de commande de flux à l'eNB maître. Les informations de requête de commande de flux contiennent des informations sur une quantité de données transmise par l'intermédiaire de l'eNB parmi des quantités de données totales à transmettre par l'intermédiaire d'un porteur radio.
PCT/KR2014/006286 2013-07-11 2014-07-11 Procédé et appareil pour exploiter des données d'une couche de commande de liaison radio dans un système de communication sans fil WO2015005738A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR10-2013-0081759 2013-07-11
KR1020130081759A KR102081999B1 (ko) 2013-07-11 2013-07-11 무선 통신 시스템에서 무선 연결 제어 계층의 데이터 운용 방법 및 장치

Publications (1)

Publication Number Publication Date
WO2015005738A1 true WO2015005738A1 (fr) 2015-01-15

Family

ID=52280316

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2014/006286 WO2015005738A1 (fr) 2013-07-11 2014-07-11 Procédé et appareil pour exploiter des données d'une couche de commande de liaison radio dans un système de communication sans fil

Country Status (2)

Country Link
KR (1) KR102081999B1 (fr)
WO (1) WO2015005738A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017028337A1 (fr) * 2015-08-14 2017-02-23 宇龙计算机通信科技(深圳)有限公司 Procédé et système d'indication de signalisation de type de bloc de transmission
US10523385B2 (en) * 2015-09-30 2019-12-31 Samsung Electronics Co., Ltd. Method and device for transmitting signal of base station in wireless communication system
CN112752305A (zh) * 2019-10-29 2021-05-04 中国移动通信有限公司研究院 流量控制方法、装置、相关设备及存储介质
CN113133132A (zh) * 2019-12-31 2021-07-16 中国移动通信有限公司研究院 数据传输方法、装置、相关设备及存储介质
CN114786274A (zh) * 2015-01-30 2022-07-22 日本电气株式会社 辅助节点、主节点及其方法

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016127666A1 (fr) 2015-02-09 2016-08-18 华为技术有限公司 Procédé de délestage de paquets de données rlc, et station de base
KR102055921B1 (ko) * 2015-05-21 2019-12-13 주식회사 케이티 기지국 장치 및 통신 시스템
CN110248382B (zh) 2017-01-05 2020-09-08 华为技术有限公司 信息传输的方法和装置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20100133895A (ko) * 2009-06-12 2010-12-22 엘지전자 주식회사 무선 통신 시스템에서 흐름 제어 방법 및 장치
KR20130032376A (ko) * 2010-06-28 2013-04-01 퀄컴 인코포레이티드 다중-포인트 ｈｓｄｐａ 통신 네트워크에서 흐름 제어를 위한 시스템 및 방법

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20100133895A (ko) * 2009-06-12 2010-12-22 엘지전자 주식회사 무선 통신 시스템에서 흐름 제어 방법 및 장치
KR20130032376A (ko) * 2010-06-28 2013-04-01 퀄컴 인코포레이티드 다중-포인트 ｈｓｄｐａ 통신 네트워크에서 흐름 제어를 위한 시스템 및 방법

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3GPP; TSG-RAN: E-UTRA; Study on Small Cell Enhancements for E-UTRA and E-UTRAN - Higher layer aspects (Release 12", 3GPP TR 36.842 V0.2-.0, May 2013 (2013-05-01), Retrieved from the Internet <URL:http://www.3gpp_org/ftp/specs/archive/36_series/36.842> *
ALCATEL -LUCENT: "Discussion on UP protocol architecture comparison for dual connectivity", R2-131960, 3GPP TSG-RAN WG2 MEETING #82, 24 May 2013 (2013-05-24), Retrieved from the Internet <URL:ftp://ftp_3gpp_org/TSG_RAN/WG2_RL2/TSGR2_82/Docs/R2-131960_zip> *
ETRI: "Consideration on E-UTRAN Architecture for Dual Connectivity", R2-131883, 3GPP TSG-RAN WG2 MEETING #82, 24 May 2013 (2013-05-24), Retrieved from the Internet <URL:ftp://ftp.3gpp.org/TSG_RAN/WG2_RL2/TSGR2_82/Docs/R2-131883_zip> *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114786274A (zh) * 2015-01-30 2022-07-22 日本电气株式会社 辅助节点、主节点及其方法
WO2017028337A1 (fr) * 2015-08-14 2017-02-23 宇龙计算机通信科技(深圳)有限公司 Procédé et système d'indication de signalisation de type de bloc de transmission
US10523385B2 (en) * 2015-09-30 2019-12-31 Samsung Electronics Co., Ltd. Method and device for transmitting signal of base station in wireless communication system
CN112752305A (zh) * 2019-10-29 2021-05-04 中国移动通信有限公司研究院 流量控制方法、装置、相关设备及存储介质
CN113133132A (zh) * 2019-12-31 2021-07-16 中国移动通信有限公司研究院 数据传输方法、装置、相关设备及存储介质
CN113133132B (zh) * 2019-12-31 2022-10-21 中国移动通信有限公司研究院 数据传输方法、装置、相关设备及存储介质

Also Published As

Publication number Publication date
KR20150007593A (ko) 2015-01-21
KR102081999B1 (ko) 2020-04-14

Similar Documents

Publication Publication Date Title
US10397975B2 (en) Method and apparatus for performing activation/deactivation of serving cell in wireless communication system supporting dual connectivity
WO2015005738A1 (fr) Procédé et appareil pour exploiter des données d&#39;une couche de commande de liaison radio dans un système de communication sans fil
WO2014182134A1 (fr) Procédé et appareil pour le transfert séquentiel prenant en compte les flux multiples dans un système à double connectivité
WO2011019204A2 (fr) Appareil et procédé pour attribuer des ressources pour des canaux logiques dans un système de communication sans fil
WO2014182132A1 (fr) Procede et dispositif de transmission de donnees dans un systeme de communication sans fil prenant en charge une double connectivite
WO2010143900A2 (fr) Système et procédé de contrôle du flux dans un système de communication sans fil
WO2014163436A1 (fr) Procédé et appareil permettant de contrôler une liaison sans fil au sein d&#39;un système de communication compatible avec la double connectivité
WO2015199411A1 (fr) Procédé et appareil d&#39;attribution de données pour répartir des supports dans une double connectivité
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
WO2016159528A1 (fr) Procédé permettant de réaliser un rapport de statut de mémoire tampon dans un système de communication sans fil, et dispositif associé
WO2012021002A2 (fr) Appareil et procédé de signalement d&#39;une marge de puissance d&#39;un système de communication sans fil
WO2014142611A1 (fr) Procédé et appareil pour effectuer une transmission de données dans un système de communication sans fil
WO2014014260A1 (fr) Procédé et appareil de mesure de débit de paquets dans un système de communication sans fil
WO2015133869A1 (fr) Procédé et dispositif d&#39;émission d&#39;informations de commande d&#39;accès au support dans un système de communications sans fil prenant en charge les communications de dispositif à dispositif
WO2013048049A1 (fr) Procédé et appareil permettant de communiquer l&#39;état d&#39;un protocole pdcp
WO2014171596A1 (fr) Procédé et appareil d&#39;attribution de ressources dans un système de communication sans fil
WO2012008691A2 (fr) Procédé de transmission de données, station de base et équipement utilisateur correspondants
WO2015020461A1 (fr) Procédé et appareil de transmission de rapport d&#39;état de tampon dans un système de communication sans fil
WO2010021465A2 (fr) Procédé de déclenchement d’un rapport d’état dans un système de communication sans fil et récepteur
WO2017191933A1 (fr) Procédé et dispositif pour transmettre une unité de données
WO2019022468A1 (fr) Procédé et appareil de sélection de porteuse
KR102148243B1 (ko) 이중 연결을 지원하는 무선 통신 시스템에서 무선 링크 제어 계층에서의 데이터 제어 방법 및 그 장치
WO2012128549A2 (fr) Appareil et procédé de remise d&#39;un rapport de marge de puissance dans un système de communication sans fil
WO2016114579A1 (fr) Procédé pour sélectionner une transmission pucch dans un système d&#39;agrégation de porteuses et dispositif associé
WO2016114578A2 (fr) Procédé de réalisation d&#39;une adaptation de puissance pour une transmission de canaux pucch dans un système d&#39;agrégation de porteuses, et dispositif associé

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14823441

Country of ref document: EP

Kind code of ref document: A1