WO2015020344A1 - Appareil et procédé de transmission de données dans un système de communication radio d'un réseau hétérogène - Google Patents

Appareil et procédé de transmission de données dans un système de communication radio d'un réseau hétérogène Download PDF

Info

Publication number
WO2015020344A1
WO2015020344A1 PCT/KR2014/006961 KR2014006961W WO2015020344A1 WO 2015020344 A1 WO2015020344 A1 WO 2015020344A1 KR 2014006961 W KR2014006961 W KR 2014006961W WO 2015020344 A1 WO2015020344 A1 WO 2015020344A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
logical channel
data
radio bearer
terminal
Prior art date
Application number
PCT/KR2014/006961
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 WO2015020344A1 publication Critical patent/WO2015020344A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • H04W40/248—Connectivity information update
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup

Definitions

  • the present invention relates to wireless communication, and more particularly, to a data transmission apparatus and method in a heterogeneous network wireless communication system.
  • HetNet heterogeneous network
  • a macro cell In a heterogeneous network environment, a macro cell is a large coverage cell, and a small cell such as a femto cell and a pico cell is a small coverage cell. Coverage overlap occurs between multiple macro cells and small cells in a heterogeneous network environment.
  • the terminal may be configured with a radio bearer based on an EPS bearer (Evolved Packet System bearer) distinguished from each other through two or more base stations.
  • EPS bearer Evolved Packet System bearer
  • dual connectivity may be referred to as an operation in which a terminal consumes radio resources provided by at least two other network points.
  • the at least two other network points may be a plurality of base stations physically or logically separated.
  • One of the plurality of base stations may be a macro base station, and the other base stations may be small base stations.
  • each base station transmits downlink data and receives uplink data through an EPS bearer or radio bearer (RB) configured for one UE.
  • RB radio bearer
  • one RB may be configured in one base station or terminal, or the same one RB may be configured in two or more different base stations or terminals.
  • the terminal may perform uplink data transmission to two or more different base stations.
  • parameters for uplink data transmission should be clearly defined in dual connectivity, and a method capable of controlling uplink data transmission is required.
  • An object of the present invention is to provide an apparatus and method for transmitting data in a heterogeneous network wireless communication system.
  • Another technical problem of the present invention is to provide configuration information for configuring a dual connection between a terminal and two or more different base stations.
  • Another technical problem of the present invention is to provide a method for controlling uplink data transmission of a terminal for two or more different base stations.
  • a terminal provides a method for transmitting uplink data for a master eNodeB (MeNB) and at least one secondary eNB (SeNB) in a wireless communication system.
  • the method includes receiving radio bearer configuration information for dual connectivity from the master base station, and corresponding to both the master base station and the at least one secondary base station based on the radio bearer configuration information.
  • Configuring the same radio bearer in the terminal transmitting data of a master logical channel (LC) mapped to the same radio bearer to the master base station, and mapping to the same radio bearer And transmitting data of a secondary logical channel to the at least one secondary base station.
  • LC master logical channel
  • a terminal for transmitting uplink data to a master eNodeB (MeNB) and at least one secondary eNB (SeNB) in a wireless communication system.
  • the terminal corresponds to a receiver for receiving radio bearer configuration information for dual connectivity from the master base station and the master base station and the at least one secondary base station based on the radio bearer configuration information.
  • a radio bearer setting unit configured to configure the same radio bearer in the terminal, data of a master logical channel (LC) mapped to the same radio bearer, and a secondary mapped to the same radio bearer
  • a data generator for generating data of a logical channel, and a transmitter for transmitting data of the primary logical channel to the master base station and transmitting data of the secondary logical channel to the at least one secondary base station.
  • the mapping relationship between uplink grants for serving cells configured for each base station and a logical channel corresponding to the RB configured for each base station may be considered.
  • the terminal may support QoS for each base station through uplink by performing uplink scheduling based on the mapping relationship.
  • FIG. 1 is a diagram illustrating a network structure of a wireless communication system to which the present invention is applied.
  • FIG. 2 is a block diagram illustrating a radio protocol architecture 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 a structure of a bearer service in a wireless communication system to which the present invention is applied.
  • FIG. 5 is a diagram illustrating a dual connection situation of a terminal to which the present invention is applied.
  • FIG. 6 is an exemplary diagram of subdividing an example of uplink transmission in a dual connection to which the present invention is applied at each layer level.
  • FIG. 7 is an exemplary diagram of subdividing another example of uplink transmission in a dual connection to which the present invention is applied at each layer level.
  • FIG 8 is an exemplary diagram of subdividing another example of uplink transmission in a dual connection to which the present invention is applied at each layer level.
  • FIG. 9 is an explanatory diagram illustrating an example of a method of performing uplink scheduling of a terminal to which the present invention is applied.
  • FIG. 10 is an explanatory diagram illustrating another example of a method of performing uplink scheduling of a terminal to which the present invention is applied.
  • FIG. 11 is a flowchart illustrating a method of transmitting uplink data in a heterogeneous network wireless communication system according to an exemplary embodiment of the present invention.
  • FIG. 12 is an explanatory diagram illustrating a method of performing uplink scheduling of a terminal according to an embodiment of the present invention.
  • FIG. 13 is an explanatory diagram illustrating a method of performing uplink scheduling of a terminal according to another embodiment of the present invention.
  • FIG. 14 is an explanatory diagram illustrating a method of performing uplink scheduling of a terminal according to another embodiment of the present invention.
  • 15 is a block diagram of a terminal and a base station according to an example of 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.
  • FIG. 1 is a diagram illustrating a network structure of a wireless communication system to which the present invention is applied.
  • E-UMTS system an Evolved-Universal Mobile Telecommunications System
  • 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 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.
  • CP control plane
  • UP user plane
  • UE user equipment
  • eNB evolved NodeB
  • 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). have.
  • 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 for communicating with the terminal 10, and includes a base station (BS), a base transceiver system (BTS), an access point, an femto base station, and a pico-eNB. It may be called other terms such as a base station (pico-eNB), a home base station (Home eNB), a relay, and the like.
  • 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 is connected to an Evolved Packet Core (EPC) 30 through an S1 interface. More specifically, the base station 20 is connected to the Mobility Management Entity (MME) through the S1-MME interface, and is connected to the Serving Gateway (S-GW) through the S1-U interface. The base station 20 exchanges contents information of the MME and context information of the terminal 10 and information for supporting mobility of the terminal 10 through the S1-MME interface. In addition, the S-GW and the data to be serviced to each terminal 10 through the S1-U interface.
  • EPC Evolved Packet Core
  • the EPC 30 includes MME, S-GW, and 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.
  • the E-UTRAN and the EPC 30 may be integrated to be referred to as EPS (Evolved Packet System), and the traffic flows from the radio link to which the terminal 10 connects to the base station 20 to the PDN connected to the service entity are all IP. It works based on (Internet Protocol).
  • EPS Evolved Packet System
  • the air interface between the terminal 10 and the base station 20 is called a "Uu interface".
  • Layers of the radio interface protocol between the terminal 10 and the network may include a first layer L1 defined in a 3GPP (3rd Generation Partnership Project) -based wireless communication system (UMTS, LTE, LTE-Advanced, etc.), It may be divided into a second layer L2 and 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 the network and the 10.
  • 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 the upper layer by a medium access control (MAC) 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 over 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
  • a physical downlink control channel (PDCCH) of a physical channel informs a terminal of resource allocation of a PCH (Paging CHannel) and DL-SCH (DownLink Shared CHannel) and HARQ (Hybrid Automatic Repeat Request) information related to the DL-SCH,
  • the terminal may carry an uplink scheduling grant informing of resource allocation of uplink transmission.
  • the Physical Control Format Indicator CHannel (PCFICH) informs the UE of the number of OFDM symbols used for the 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.
  • the PUSCH Physical Uplink Shared CHannel
  • the PUSCH may include channel state information (CSI) information such as HARQ ACK / NACK and CQI.
  • 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.
  • 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.
  • the RLC layer uses a transparent mode (TM), an unacknowledged mode (UM), and an acknowledgment mode (AM) in order to guarantee various quality of services (QoS) required by a radio bearer (RB).
  • TM transparent mode
  • UM unacknowledged mode
  • AM acknowledgment mode
  • QoS quality of services
  • RB radio bearer
  • Unacknowledged mode is for real-time data transmission, such as data streaming or Voice over Internet Protocol (VoIP), which focuses on speed rather than reliability of data.
  • VoIP Voice over Internet Protocol
  • 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 configured to be 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 are defined only when a transmission opportunity is notified from a lower layer (eg, MAC layer) and 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 informed.
  • Functions of the Packet Data Convergence Protocol (PDCP) layer in the user plane include the transfer of user data, header compression and ciphering, and the transfer and control of encryption / integrity protection of control plane data.
  • 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.
  • a radio bearer (RB) refers to a logical path provided by a first layer (PHY layer) and a 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 classified into a signaling RB (SRB) and a data RB (DRB).
  • SRB signaling RB
  • DRB data RB
  • the non-access stratum (NAS) layer located above the RRC layer performs functions such as session management and mobility management. If there is an RRC connection between the RRC layer of the UE and the RRC layer of the E-UTRAN, the UE is in an RRC connected state, otherwise it is in an RRC idle state. do.
  • NAS non-access stratum
  • a terminal In order for a terminal to transmit user data (eg, an IP packet) to an external internet network or to receive user data from an external internet network, the terminal exists between mobile communication network entities existing between the terminal and the external internet network. Resources must be allocated to different paths. Thus, a path in which resources are allocated between mobile communication network entities and data transmission and reception is possible is called a bearer.
  • a bearer a path in which resources are allocated between mobile communication network entities and data transmission and reception is possible.
  • FIG. 4 is a diagram illustrating a structure of a bearer service in a wireless communication system to which the present invention is applied.
  • the end-to-end service refers to a service that requires a path between the terminal and the P-GW (EPS Bearer) and a P-GW and an external bearer for the Internet network and data service.
  • the external path is a bearer between the P-GW and the Internet network.
  • the terminal When the terminal transmits data to the external internet network, the terminal first transmits the data to the base station (eNB) through the radio RB. Then, the base station transmits the data received from the terminal to the S-GW through the S1 bearer.
  • the S-GW delivers the data received from the base station to the P-GW via the S5 / S8 bearer, and finally the data is delivered through the external bearer to a destination existing in the P-GW and the external Internet network.
  • the data can be delivered to the terminal through each bearer in the reverse direction as described above.
  • each bearer is defined for each interface to ensure independence between the interfaces.
  • the bearer at each interface will be described in more detail as follows.
  • the bearers provided by the wireless communication system are collectively called an Evolved Packet System (EPS) bearer.
  • An EPS bearer is a delivery path established between a UE and a P-GW for transmitting IP traffic with a specific QoS.
  • the P-GW may receive IP flows from the Internet or send IP flows to the Internet.
  • Each EPS bearer is set with QoS decision parameters that indicate the nature of the delivery path.
  • One or more EPS bearers may be configured per UE, and one EPS bearer uniquely represents a concatenation of one E-UTRAN Radio Access Bearer (E-RAB) and one S5 / S8 bearer.
  • E-RAB E-UTRAN Radio Access Bearer
  • the S5 / S8 bearer is a bearer of the S5 / S8 interface. Both S5 and S8 are bearers present at the interface between the S-GW and the P-GW.
  • the S5 interface exists when the S-GW and the P-GW belong to the same operator, and the S8 interface belongs to the provider (Visited PLMN) roamed by the S-GW, and the P-GW has subscribed to the original service (Home). PLMN).
  • the E-RAB uniquely represents the concatenation of the S1 bearer and the corresponding RB.
  • one-to-one mapping is established between the E-RAB and one EPS bearer. That is, one EPS bearer corresponds to one RB, S1 bearer, and S5 / S8 bearer, respectively.
  • the S1 bearer is a bearer at the interface between the base station and the S-GW.
  • RB means two types of data radio bearer (DRB) and signaling radio bearer (SRB).
  • DRB data radio bearer
  • SRB signaling radio bearer
  • RB is a DRB provided in the Uu interface to support a service of a user. . Therefore, the RB expressed without distinction is distinguished from the SRB.
  • the RB is a path through which data of the user plane is transmitted
  • the SRB is a path through which data of the control plane, such as the RRC layer and NAS control messages, are delivered.
  • One-to-one mapping is established between RB, E-RAB and EPS bearer.
  • EPS bearer types include a default bearer and a dedicated bearer.
  • an IP address is assigned and a default EPS bearer is created while creating a PDN connection. That is, a default bearer is first created when a new PDN connection is created.
  • a service for example, the Internet, etc.
  • VoD for example, VoD, etc.
  • a dedicated bearer is created. In this case, the dedicated bearer may be set to a different QoS from the bearer that is already set.
  • QoS decision parameters applied to the dedicated bearer are provided by a Policy and Charging Rule Function (PCRF).
  • PCRF Policy and Charging Rule Function
  • the PCRF may receive subscription information of a user from a Subscriber Profile Repository (SPR) to determine QoS determination parameters.
  • SPR Subscriber Profile Repository
  • Up to 15 dedicated bearers may be created, for example, and four of the 15 are not used in the LTE system. Therefore, up to 11 dedicated bearers can be created.
  • the EPS bearer includes a QoS Class Identifier (QCI) and Allocation and Retention Priority (ARP) as basic QoS determination parameters.
  • EPS bearers are classified into GBR (Guaranteed Bit Rate) bearers and non-GBR bearers according to QCI resource types.
  • the default bearer is always set to a non-GBR type bearer, and the dedicated bearer may be set to a GBR type or non-GBR type bearer.
  • the GBR bearer has GBR and MBR (Maximum Bit Rate) as QoS decision parameters in addition to QCI and ARP.
  • FIG. 5 is a diagram illustrating an example of a dual connectivity situation of a terminal to which the present invention is applied. This is the case for inter-frequency duplex connections.
  • the terminal 550 enters an area in which the service area of the macro cell F2 in the macro base station 500 and the service area of the small cell F1 in the small base station 510 overlap.
  • the macro base station 500 may be called a master base station (MeNB)
  • the small base station 510 may be called a secondary base station (SeNB).
  • the user data arriving at the macro base station 500 may be transmitted to the terminal 550 through the small base station 510.
  • the F2 frequency band is allocated to the macro base station 500
  • the F1 frequency band is allocated to the small base station 510.
  • the terminal 550 may receive the service through the F2 frequency band from the macro base station 500 and may receive the service through the F1 frequency band from the small base station 510.
  • the macro base station 500 uses F2 and the small base station 510 is described as using the F1 frequency band.
  • the present invention is not limited thereto, and both the macro base station 500 and the small base station 510 have the same F1 or F2 frequency. Bands can also be used.
  • FIG. 6 is an exemplary diagram of subdividing an example of uplink transmission in a dual connection to which the present invention is applied at each layer level.
  • a master base station (MeNB) providing a macro cell and a secondary base station (SeNB) providing a small cell all include a PDCP, RLC, MAC, and PHY layers.
  • the first RB (# 1 RB) is configured through the PDCP layer and RLC layer of the terminal and the PDCP layer and RLC layer of the master base station
  • the second RB (# 2 RB) is the PDCP layer and RLC layer and the secondary base station of the terminal It is composed of PDCP layer and RLC layer.
  • the RBs may be configured to include a part of MAC layer related to logical channel configuration.
  • the terminal is connected to the P-GW through a first EPS bearer (# 1 EPS bearer) and is connected to the P-GW through a second EPS bearer (# 2 EPS bearer).
  • a first EPS bearer # 1 EPS bearer
  • a second EPS bearer # 2 EPS bearer
  • each base station receives uplink data through an EPS bearer or RB (# 1 RB and # 2 RB) configured in each base station with respect to one terminal is also referred to as CN network split (Core Network split).
  • FIG. 7 is an exemplary diagram of subdividing another example of uplink transmission in a dual connection to which the present invention is applied at each layer level.
  • uplink transmission in a bearer split structure is shown.
  • one RB is configured through a plurality of base stations, and the terminal divides uplink data through the one RB into one or two flows (or more flows).
  • a logical channel group corresponding to the one RB and defined for each of the base stations may be defined as a bearer split.
  • the same radio bearer corresponding to all of the plurality of base stations may be defined as a bearer split.
  • the bearer split may be called multi flow, multiple node (eNB) transmission, inter-eNB carrier aggregation, etc. in that information is transmitted through a plurality of flows. Can be.
  • each base station may include a PDCP layer, a MAC layer and an RLC layer, but the layer responsible for flow control is included in only one base station (ie, a master base station). If the layer in charge of the flow control is a PDCP layer, the PDCP layer is included only in the master base station.
  • the MAC layer of each base station delivers information on data amount, transmission opportunity, etc. 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 an RLC PDU configured in the RLC layer from the RLC layer in the form of a MAC SDU.
  • the RLC layer of the secondary base station processes the data according to the data amount and transmission opportunity required by the MAC layer of the secondary base station, information on the processed data amount and transmission opportunity exists in the upper RLC layer. Should inform the flow control layer of the master base station.
  • the PDCP layer of the master base station may be connected to the RLC layer of the secondary base station using the Xn interface protocol, as shown in FIG. 7.
  • the Xn interface protocol is defined as an interface between the MeNB and the SeNB.
  • the Xn interface protocol may be an X2 interface protocol defined between base stations.
  • 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 called # 1 sub-entity
  • the RLC layer of the secondary base station is called # 2 sub-entity.
  • Sub-entities are divided into one-to-one matching between 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). In this case, 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 different for each sub-entity. Because there is. If the delay times of the 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 or at the secondary base station, or at a network including the master base station and the secondary base station. Accordingly, data to be delivered through the PDCP layer in the same RB may be transmitted through one of the RLC-AM # 1 sub-entities or one of the RLC-AM # 2 sub-entities.
  • an identifier may be further transmitted by the terminal that receives the data to identify which sub-entity the data is transmitted through.
  • the example of FIG. 7 is also called a sub entity RLC type, a separated RLC type, or an independent RLC type among bearer split types. However, the example of FIG. 7 is not necessarily applied only to the bearer split.
  • FIG 8 is an exemplary diagram of subdividing another example of uplink transmission in a dual connection to which the present invention is applied at each layer level.
  • the master base station includes the PDCP, RLC, MAC, and PHY layers, while the secondary base station includes the 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 master base station is called a master RLC layer
  • the RLC layer of the secondary base station is called 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 secondary base station forwards the data to the master RLC layer when data is received through the slave RLC layer. Therefore, the same data may be received through the slave RLC layer or the master RLC layer through the MAC in the MeNB. Therefore, uplink transmission between the terminal and the base station may be a single transmission instead of TDM transmission.
  • the dynamic scheduling of radio resources is mainly responsible for the MAC scheduler in each base station. Since the situation of the MAC layer of the macro base station and the situation of the MAC layer of the small base station are different, the macro RLC layer allocates (or splits, concatenates, or recombines) PDUs based on information provided by the MAC layer of the macro base station, and the slave RLC layer. Splits or connects based on information provided by the MAC layer of the small base station.
  • the dually connected UE includes only one PDCP layer and one RLC layer in a single RB for data to be transmitted to two or more different base stations for uplink transmission.
  • only one MAC layer may control uplink transmission according to uplink resource allocation information received from two or more different base stations for uplink transmission. 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 types. However, the example of FIG. 8 is not necessarily applied only to the bearer split.
  • the terminal maps uplink data generated at the application layer in the terminal to the EPS bearer based on QoS.
  • Uplink data is processed through the PDCP layer and the RLC layer in each RB, which is mapped 1: 1 in each EPS bearer.
  • the processed uplink data should be transmitted to the base station where each RB is configured. That is, uplink data generated in each RB in the terminal should be delivered to the base station in which the RB corresponding to the RB of the terminal is configured.
  • uplink data of all RBs can be integrated and managed in the MAC layer as shown in FIG. 9. As shown in FIG. 10, even when the MAC layer processes data based on uplink grants for each serving cell, a mapping relationship between each RB and a logical channel is ambiguous or does not exist.
  • a terminal consisting of a plurality of serving cells acquires an uplink grant that allocates uplink resources of each serving cell.
  • the uplink grant is reported from the physical layer of the terminal to the MAC layer.
  • the MAC layer of the terminal treats uplink resources of the physical layer individually allocated to each serving cell as one aggregated uplink resource set.
  • the MAC layer of the UE may schedule or allocate data of the logical channel processed in each RB according to a logical channel prioritization (LCP) procedure.
  • LCP logical channel prioritization
  • the LCP procedure is applied when performing a new transmission on the MAC. That is, it does not apply when HARQ retransmission.
  • LCP logical channel prioritization
  • a first logical channel (channel 1), a second logical channel (channel 2), and a second logical channel (channel 3) are configured in a terminal, and a primary serving cell : PC), a first secondary serving cell (SC1), a second secondary serving cell (secondary serving cell 2: SC2) is configured.
  • the MAC PDU is allocated a resource in which individual serving cells PC, SC1, SC2 are integrated.
  • the portion corresponding to the prioritized bit rate (PBR) among the uplink data in the first logical channel is the first MAC PDU. Is mapped to.
  • the PBR portion of the second logical channel having priority 2 and the PBR portion of the third logical channel having priority 3 are sequentially mapped to the MAC PDU.
  • Any MAC PDU consists of one MAC header and zero or one or more MAC SDUs and zero or one or more MAC CEs and padding that may optionally be added.
  • One MAC PDU header consists of one or more MAC PDU subheaders; Each subheader corresponds to a MAC SDU, MAC CE or padding.
  • the MAC PDU subheader consists of six header fields (R / R / E / LCID / F / L).
  • the last subheader and the fixed size MAC CE consist of four header fields (R / R / E / LCID).
  • the MAC PDU subheader corresponding to the padding has four header fields (R / R / E / LCID) because it can always be located last in the MAC PDU.
  • MAC PDU subheaders have the same order as the corresponding MAC SDUs, MAC CEs and padding. That is, the first subheader may correspond to padding when there is no first MAC CE or MAC SDUs when there is no first MAC CE or MAC CE.
  • MAC CEs are always placed before MAC SDUs. Padding may occur at the end of a MAC PDU except when 1 or 2 byte padding is required. The padding can be any value, so the terminal should always ignore it. Zero or more padding bytes are allowed when padding is performed at the end of the MAC PDU. If one-byte or two-byte padding is required, one or two MAC PDU subheaders corresponding to the padding are placed at the start of the MAC PDU before other subheaders. At most one MAC PDU may be transmitted for each transport block (TB) of each UE. At most one MCH MAC PDU may be transmitted for each TTI. Here, the MCH means a multicast channel.
  • TB transport block
  • MCH means a multicast channel.
  • a terminal consisting of a plurality of serving cells acquires an uplink grant that allocates uplink resources of each serving cell.
  • the terminal classifies (or individually) the physical layer resources allocated to each serving cell.
  • the UE allocates data of logical channels processed by each RB according to the LCP procedure based on each serving cell uplink resource. For example, in the embodiment of FIG. 10, a first logical channel (channel 1), a second logical channel (channel 2), a second logical channel (channel 3) are configured in a terminal, and a main serving cell (PCell), Assume that the first secondary serving cell SCell1 is configured. Uplink resources of the primary serving cell and the first secondary serving cell are separated and allocated to MAC PDUs for each serving cell.
  • the portion corresponding to the first logical channel PBR of the uplink data in the first logical channel having priority 1 is first mapped to the MAC PDU of the primary serving cell, and then to the second logical channel having priority 2.
  • a portion of the uplink data corresponding to the second logical channel PBR is next mapped to the MAC PDU of the primary serving cell. Since uplink resources of the primary serving cell are limited, only a part of the PBRs of the second logical channel are mapped to the MAC PDU.
  • the data mapped to the MAC PDU for the first secondary serving cell is a portion remaining after being mapped to the main serving cell of the uplink data in the first logical channel having priority number 1. At this time, only the uplink resources of the first secondary serving cell are mapped.
  • one RB in the terminal corresponds to a plurality of base stations.
  • one same RB (or EPS bearer) may be configured by two or more different base stations, and an uplink grant for a serving cell may also be configured by each base station.
  • the UE configures the MAC PDU (s) as shown in FIG. 9 or 10 and transmits it to two or more base stations through a single RB, two or more base stations are difficult to track their logical channel from the MAC PDU. This is because there is no definition of mapping relationship between RB and logical channel.
  • radio bearer configuration information for mapping between the RB and the logical channel
  • the radio bearer configuration information defined as described above may enable uplink transmission control in dual connectivity according to the embodiments of FIGS. 5 to 8.
  • the UE may be assigned a scheduling parameter from each base station to optimize data transmission for a single RB.
  • FIG. 11 is a flowchart illustrating a method of transmitting uplink data in a heterogeneous network wireless communication system according to an exemplary embodiment of the present invention.
  • a master base station MeNB
  • a secondary base station SeNB
  • the technical idea of the present invention also includes the case where there is more than one secondary base station.
  • the master base station (MeNB) generates radio bearer configuration information for dual connectivity and transmits it to the terminal (S1100).
  • the radio bearer configuration information may be transmitted by the secondary base station, not the master base station.
  • the radio bearer configuration information is RRC signaling and may control scheduling of uplink data for each logical channel.
  • the terminal configures the same radio bearer (RB) corresponding to both the master base station and the secondary base station in the terminal based on the radio bearer configuration information (S1105).
  • the same radio bearer may be one or multiple.
  • the same radio bearer is split or separated across a plurality of base stations and configured in the terminal. As the same radio bearer, a portion separated by the terminal and the master base station is called a radio bearer on the master side, and a portion separated by the terminal and the secondary base station is called a radio bearer on the secondary side.
  • Step S1105 is an embodiment of a procedure for configuring a dual connection to the terminal.
  • the double connection is of any type of Figs.
  • different radio bearers are configured in the master base station and the secondary base station. 7 and 8, the same radio bearer in step S1105 corresponds to # 1 RB.
  • the terminal may transmit uplink data to the base stations through the same radio bearer.
  • multiple logical channels may be mapped to the same radio bearer.
  • the plurality of logical channels may not correspond to only one base station, but may correspond to a master base station and at least one secondary base station.
  • the logical channel corresponding to the master base station is called a master logical channel
  • the logical channel corresponding to the secondary base station is called a secondary logical channel.
  • the primary logical channel is provided with data transmitted through the master radio bearer (abbreviated as 'data of the primary logical channel').
  • the secondary logical channel is provided with data transmitted through the secondary radio bearer (abbreviated as 'sub logical channel data').
  • the terminal performs uplink scheduling for transmitting data of the logical channel to the master base station and the secondary base station (S1110).
  • uplink scheduling may be called an LCP procedure.
  • the terminal generates data of the primary logical channel based on the LCP procedure and transmits it to the master base station (S1115).
  • radio resources of the master base station eg, a serving cell or a primary serving cell in a primary timing advancing group (pTAG)
  • the data of the primary logical channel may be a MAC PDU, an RLC PDU, or a PDCP PDU.
  • pTAG is defined as a time alignment group that includes the main serving cell.
  • a time alignment group is defined as a set of serving cells having the same time advance value and timing reference.
  • time advance means that the base station instructs each terminal in the base station to transmit the uplink signal from a certain point of time based on the downlink reception time in the timing reference cell to receive the uplink signal of each terminal at a desired time point.
  • the specific value indicated by the base station is called a time advance value.
  • the time advance value may be set differently for each serving cell.
  • the terminal generates data of the secondary logical channel based on the LCP procedure, and transmits it to the secondary base station (S1120).
  • the secondary base station For transmission of uplink data of a secondary logical channel, radio resources (eg, secondary serving cells) of the secondary base station are consumed. Steps S1115 and S1120 may be performed at the same time.
  • radio bearer configuration information defined in step S1100 will be described in more detail.
  • the radio bearer configuration information includes an ID of a master logical channel corresponding to a master base station and a master for controlling multiplexing or assembling data of the primary logical channel into a MAC PDU.
  • (master) Contains logical channel configuration information. Radio bearer configuration information according to the first embodiment may be defined as shown in Table 1 below.
  • DRB-ToAddMod :: SEQUENCE ⁇ eps-BearerIdentity INTEGER (0..15) OPTIONAL,-Cond DRB-Setup drb-Identity DRB-Identity, pdcp-Config PDCP-Config OPTIONAL,-Cond PDCP rlc-Config RLC-Config OPTIONAL,-Cond Setup logicalChannelIdentity INTEGER (3..10) OPTIONAL,-Cond DRB-Setup logicalChannelConfig LogicalChannelConfig OPTIONAL,-Cond Setup ... ⁇
  • the radio bearer configuration information DRB-ToAddMod includes an EPS bearer ID field, a bearer ID field, a PDCP configuration field, and a RLC configuration field. It includes a primary logical channel ID (logicalChannelIdentity) and primary logical channel configuration information (logicalChannelConfig).
  • the primary logical channel ID may be an integer of any one of 3 to 10.
  • Primary logical channel configuration information may be defined, for example, as shown in Table 2 below.
  • LogicalChannelConfig :: SEQUENCE ⁇ ul-SpecificParameters SEQUENCE ⁇ priority INTEGER (1..16), prioritisedBitRate ENUMERATED ⁇ kBps0, kBps8, kBps16, kBps32, kBps64, kBps128, kBps256, infinity, kBps512-v1020, kBps1024-v1020, kBps2048-v1020, spare5, spare4, spare3, spare2, spare1 ⁇ , bucketSizeDuration ENUMERATED ⁇ ms50, ms100, ms150, ms300, ms500, ms1000, spare2, spare1 ⁇ , logicalChannelGroup INTEGER (0..3) OPTIONAL-Need OR ⁇ OPTIONAL,-Cond UL ..., [[logicalChannelSR-Mask-r
  • the primary logical channel configuration information includes an UL specific parameters field.
  • the uplink specific parameter field may be, for example, a priority field indicating a priority, a priority bit rate (PBR) field and a bucket in multiplexing or assembling data of a main logical channel into a MAC PDU.
  • PBR priority bit rate
  • a bucket in multiplexing or assembling data of a main logical channel into a MAC PDU Contains a bucket size duration (BSD) field. Since the uplink specific parameter field is included in the primary logical channel configuration information, the priority field, the PBR field, and the BSD fields included in the uplink specific parameter field may all be considered to be included in the primary logical channel configuration information.
  • Priorities range from 1 to 16, with larger values indicating lower priorities.
  • the PBR field indicates a bit rate to be preferentially allocated when transmitting data for a logical channel.
  • the BSD field is a parameter that defines the bucket size.
  • the priority, PRB, of each logical channel may be set identically or differently.
  • the radio bearer configuration information may include an ID of a primary logical channel, primary logical channel configuration information, and secondary logical channel ID and secondary logical channel configuration information corresponding to the secondary base station. That is, in order to apply different LCP related parameters for each base station, a parameter set constituting a logical channel may be newly added for the secondary base station.
  • the sub logical channel configuration information is a set of parameters that control multiplexing or assembling data of the sub logical channel into a MAC PDU.
  • DRB-ToAddMod SEQUENCE ⁇ eps-BearerIdentity INTEGER (0..15) OPTIONAL,-Cond DRB-Setup drb-Identity DRB-Identity, pdcp-Config PDCP-Config OPTIONAL,-Cond PDCP pdcp-ConfigSeNB PDCP-Config OPTIONAL, --Cond BearerSplit-PDCP rlc-Config RLC-Config OPTIONAL,-Cond Setup rlc-ConfigSeNB RLC-Config OPTIONAL,-Cond BearerSplit-RLC rlc-ConfigSeNB RLC-Config OPTIONAL,-Cond BearerSplit-slaveRLC logicalChannelIdentity INTEGER (3..10) OPTIONAL,-Cond DRB-Setup logicalChannelConfig LogicalChannelConfig OPTIONAL,-Cond Setup logicalChannelIdentity INTEGER (3.
  • the radio bearer configuration information according to the second embodiment includes all the fields of Table 1, and further includes an ID (logicalChannelIdentitySeNB) and secondary logical channel configuration information (logicalChannelConfigSeNB) of the secondary logical channel.
  • ID logicalChannelIdentitySeNB
  • secondary logical channel configuration information logicalChannelConfigSeNB
  • the configuration information on the PDCP and RLC entities in the terminal corresponding to the PDCP and RLC entities in the SeNB is included according to whether the bearless split scheme is an independent PDCP scheme (Cond BearerSplit-PDCP) or an independent RLC scheme (Cond BearerSplit-PDCP).
  • the configuration information is different.
  • configuration information on the RLC entity in the terminal corresponding to the slave RLC entity in the SeNB is included, which is configuration information applied only when the UE receives downlink.
  • Secondary logical channel configuration information (LogicalChannelConfigSeNB) may be defined, for example, as shown in Table 4 below.
  • LogicalChannelConfigSeNB SEQUENCE ⁇ ul-SpecificParameters SEQUENCE ⁇ priority INTEGER (1..16), prioritisedBitRate ENUMERATED ⁇ kBps0, kBps8, kBps16, kBps32, kBps64, kBps128, kBps256, infinity, kBps512-v1020, kBps1024-v1020, kBps2048-v1020, spare5, spare4, spare3, spare2, spare1 ⁇ , bucketSizeDuration ENUMERATED ⁇ ms50, ms100, ms150, ms300, ms500, ms1000, spare2, spare1 ⁇ , logicalChannelGroup INTEGER (0..3) OPTIONAL-Need OR ⁇ OPTIONAL,-Cond UL ... ⁇ -ASN1STOP
  • the secondary logical channel configuration information includes an UL specific parameters field.
  • the uplink specific parameter field includes, for example, a priority field, a PBR field, and a BSD field indicating a priority in multiplexing or assembling data of a secondary logical channel into a MAC PDU.
  • unnecessary fields such as logicalChannelSR-Mask are omitted.
  • the uplink specific parameter field is included in the secondary logical channel configuration information
  • the priority field, the PBR field, and the BSD fields included in the uplink specific parameter field may all be considered to be included in the secondary logical channel configuration information.
  • Priorities range from 1 to 16, with larger values indicating lower priorities.
  • the PBR field indicates a bit rate to be preferentially allocated when transmitting data for a logical channel.
  • the BSD field is a parameter for defining the bucket size.
  • the terminal Upon receiving the radio bearer configuration information according to the second embodiment, the terminal performs the uplink scheduling, that is, the LCP procedure of step S1110 in the uplink scheduling scheme as shown in FIG. 12.
  • FIG. 12 is an explanatory diagram illustrating a method of performing uplink scheduling of a terminal according to an embodiment of the present invention.
  • a terminal performs communication on an uplink based on dual connectivity with a master base station and a secondary base station.
  • RB # 2 and RB # 3 are configured in the terminal, and RB # 1 is configured only between the master base station and the terminal.
  • RB # 2 and RB # 3 are divided into a master side RB and a secondary side RB by a bearer split, respectively.
  • logical channels 1, 2, and 3 correspond to the master base station
  • logical channels 4 and 5 correspond to the secondary base station.
  • Logical channel 1 is mapped to RB # 1.
  • Logical channel 2 (master base station) and logical channel 5 (secondary base station) are mapped to the same RB # 2 by a bearer split.
  • logical channel 3 (master base station) and logical channel 4 (secondary base station) are mapped to the same RB # 3 by a bearer split. That is, a single RB is allocated to different logical channels LC.
  • the UE independently performs the LCP procedure for each logical channel mapped to each base station in consideration of available resources provided by the serving cells in which each logical channel and each uplink are configured. For example, the terminal configures a first MAC PDU based on the priority of each logical channel, PBR, and logical channel configuration information such as BSD. Since the priority of logical channel 1 is 1, PBR of all the data of logical channel 1 is allocated to the first MAC PDU first. Next, since the priority of logical channel 2 is 2, a PBR of all data of logical channel 1 is allocated to the first MAC PDU.
  • the terminal may transmit the first MAC PDU using resources provided by a main serving cell (PCell) configured in the master base station and a first secondary serving cell (SCell1: SC1).
  • PCell main serving cell
  • SCell1 first secondary serving cell
  • the UE configures a second MAC PDU based on the priority of each logical channel, PBR, and logical channel configuration information such as BSD. Since the priority of logical channel 4 is 1, the PBR of all the data of logical channel 4 is first allocated to the second MAC PDU. Next, since the priority of logical channel 5 is 2, a PBR of all data of logical channel 5 is allocated to the second MAC PDU.
  • the terminal may transmit the second MAC PDU using the resources provided by the second secondary serving cell SC2 and the third secondary serving cell SC3 configured in the secondary base station.
  • This uplink scheduling scheme may be usefully used in a radio protocol structure in which RLCs operate independently, such as independent RLCs.
  • FIG. 12 is an example of generating MAC PDUs using a resource given by an uplink grant of serving cells in each base station as one integrated resource as shown in FIG. 9.
  • the terminal may independently generate uplink scheduling for each uplink grant for a serving cell in each base station to generate a MAC PDU.
  • the UE generates a third MAC PDU and a fourth MAC PDU to be allocated to the PC and the SC1, respectively, with respect to the master base station, and generates a fifth MAC PDU and the sixth MAC PDU to be allocated to the SC2 and SC3, respectively, with respect to the secondary base station.
  • a MAC control element (CE) to be transmitted for each base station may be independently generated and included in each MAC PDU. If a specific MAC CE is to be transmitted to a specific base station, it is included in the MAC PDU to be transmitted to the base station.
  • the radio bearer configuration information may include the ID of the primary logical channel, the primary logical channel configuration information, and the secondary logical channel configuration information about the secondary base station.
  • Radio bearer configuration information according to the third embodiment may be defined as shown in Table 5 below.
  • DRB-ToAddMod :: SEQUENCE ⁇ eps-BearerIdentity INTEGER (0..15) OPTIONAL,-Cond DRB-Setup drb-Identity DRB-Identity, pdcp-Config PDCP-Config OPTIONAL,-Cond PDCP pdcp-ConfigSeNB PDCP-Config OPTIONAL, --Cond BearerSplit-PDCP rlc-Config RLC-Config OPTIONAL,-Cond Setup pdcp-ConfigSeNB PDCP-Config OPTIONAL, --Cond BearerSplit-PDCP rlc-ConfigSeNB RLC-Config OPTIONAL, --Cond BearerSplit-slaveRLC logicalChannelIdentity INTEGER (3..10) OPTIONAL,-Cond DRB-Setup logicalChannelConfig LogicalChannelConfig OPTIONAL,-Cond Setup logicalChannelIdentity
  • the radio bearer configuration information according to the third embodiment includes all the fields of Table 1, and further includes secondary logical channel configuration information (logicalChannelConfigSeNB).
  • logicalChannelConfigSeNB secondary logical channel configuration information
  • the terminal Upon receiving the radio bearer configuration information according to the third embodiment, the terminal performs the uplink scheduling, that is, the LCP procedure of step S1110 in the uplink scheduling scheme as shown in FIG. 13.
  • FIG. 13 is an explanatory diagram illustrating a method of performing uplink scheduling of a terminal according to another embodiment of the present invention.
  • a terminal performs communication on an uplink based on a dual connection with a master base station and a secondary base station.
  • RB # 2 and RB # 3 are configured in the terminal, and RB # 1 is configured only between the master base station and the terminal.
  • RB # 2 and RB # 3 are divided into a master side RB and a secondary side RB by a bearer split, respectively.
  • logical channels 1, 2 and 3 correspond to the master base station, and logical channels 2 and 3 correspond to the secondary base station.
  • Logical channel 2 is mapped to master side RB # 2 and secondary side RB # 2
  • logical channel 3 is mapped to master side RB # 3 and secondary side RB # 3.
  • the terminal may perform a LCP procedure by defining a bucket for dividing the logical channel configured in this way for each base station.
  • the terminal should consider the amount of data to be transmitted to each base station for the same logical channel. For example, the terminal distinguishes the amount of data to be transmitted to each base station for the same logical channel, and provides the RLC entity for each base station with a transmission opportunity and total RLC PDU size according to the distinguished data amount. This is required by the MAC layer of the terminal to the separated RLC layer that exists above the MAC layer.
  • the terminal In order to implement this, the terminal must store data in the same logical channel in different virtual spaces, that is, buckets, which are distinguished for each base station.
  • the secondary logical channel configuration information is included in the radio bearer configuration information to define a bucket according to the present embodiment.
  • Different priority, PBR, BSD, etc. logical channel parameters may be set for different buckets within the same logical channel, and may include one or more of them.
  • the data of the primary logical channel is the data of bucket 1
  • the data of the secondary logical channel is the data of bucket 2.
  • the terminal operates different buckets for the same logical channel. For example, the terminal stores data of logical channel 2 mapped to RB # 2 in a first bucket of a master base station and a second bucket of a secondary base station.
  • the terminal independently performs the LCP procedure for each bucket stored on the bucket 1 and bucket 2 to configure MAC PDU_m and MAC PDU_s.
  • the terminal first configures the MAC PDU from the data to be transmitted through the master base station according to the existing LCP procedure.
  • PBR (B1) means a PBR applied to the bucket 1.
  • the UE configures a MAC PDU according to the LCP procedure from data to be transmitted through the secondary base station among data remaining in each logical channel capable of bearer splitting.
  • the terminal transmits MAC PDU_m and MAC PDU_s to the master base station and the secondary base station by using available resources (eg, a serving cell configured with uplink) provided by each base station.
  • available resources eg, a serving cell configured with uplink
  • the UE may perform uplink scheduling in the same manner as in FIG. 14 based on the radio bearer configuration information according to the third embodiment.
  • FIG. 14 is an explanatory diagram illustrating a method of performing uplink scheduling of a terminal according to another embodiment of the present invention.
  • a single RB is allocated to the same logical channel as in FIG. 13, but does not define a separate virtual space such as a bucket.
  • the UE performs the LCP procedure by dividing the available resources for each base station based on the priority.
  • one RLC entity for uplink transmission may be configured as one. That is, when providing a transmission opportunity and a total RLC PDU size to the separated RLC layer located above the MAC layer, the terminal may provide a single information for each logical channel to the RLC layer as before.
  • the terminal sequentially performs the LCP procedure for each logical channel mapped to each base station in consideration of available resources provided by the serving cells in which each logical channel and each uplink are configured. That is, the terminal first configures a first MAC PDU from data to be transmitted through the master base station according to the existing LCP procedure. Next, the UE configures a MAC PDU according to the LCP procedure from data to be transmitted through the secondary base station among data remaining in each logical channel capable of bearer splitting.
  • the terminal In performing the LCP procedure, the terminal should maintain a variable Bj for each logical channel j.
  • Bj is initialized to 0 when logical channel j is initially set, and is increased by PBR x TTI for each TTI.
  • the Bj value cannot exceed the bucket size, and if the Bj value is larger than the bucket size value, the Bj value should be set to the bucket size value.
  • the bucket size is the same as PBR ⁇ BSD.
  • the terminal must execute the LCP procedure when a new transmission is performed.
  • the terminal does not transmit data on the logical channel corresponding to the reserved radio bearer, and allocates resources to the logical channels through the following steps.
  • the terminal allocates resources in descending order of priority to all logical channels having a Bj value greater than zero. If the PBR value of any radio bearer is set to infinity, the terminal allocates resources for all data that can be transmitted in the radio bearer.
  • the terminal reduces the Bj value.
  • the reduction value is the total size of MAC SDUs provided to the logical channel in (1).
  • the Bj value may be negative.
  • the terminal allocates the resources to all logical channels in order of high priority until the data or uplink grant for the logical channel is exhausted regardless of all Bj values. If there are logical channels having the same priority, the same goes back to the logical channels.
  • the LCP procedure (1) to (3) and other related procedures related thereto may be independently applied to each uplink grant. Or it may be applied to the sum of the capacities of the uplink grants. In addition, it is up to the implementation of the terminal whether the uplink grant proceeds in the order. In addition, in such a case, it is also up to the implementation of the terminal to determine which MAC PDU to include the MAC CE.
  • the terminal may observe the following rules while the LCP procedure of (1) to (3) is in progress. i) If the entire SDU (or partially transmitted SDU or retransmitted RLC PDU) fits into the remaining resources, the UE does not subdivide any RLC SDU (or partially transmitted SDU or retransmitted RLC PDU). ii) If the UE has subdivided any RLC SDU from the logical channel, the size of the segment for filling uplink grant is maximized as much as possible. iii) The terminal maximizes data transmission.
  • the terminal does not transmit only padding BSR and / or padding (however, size of uplink grant) Is less than 7 bytes and no AMD PDU segment needs to be sent).
  • the terminal should consider the priority in the order shown in the following table.
  • the master base station when configuring the MAC PDU based on the LCP procedure, it is assumed that the master base station has a higher priority than the secondary base station.
  • the data of the primary logical channel is allocated to the MAC PDU with resources allocated in priority
  • the data of the secondary logical channel is allocated to the MAC PDU with the remaining resources.
  • the priority of the secondary base station may be higher than that of the master base station, and such inter-base priority may be determined in various ways.
  • the base station determines the priority between the base stations, and may transmit the information about the determined priority to the terminal by RRC signaling.
  • the priority of the base station including the main serving cell may be determined higher than that of the base station that does not.
  • the priority of a base station with many available resources may be determined higher than that of a base station that does not.
  • the priority of the base station to transmit the high priority MAC CE (compared to the priority of the data of the logical channel) may be determined to be higher than that of the other base station.
  • the secondary base station receiving the data of the secondary logical channel provides the data of the secondary logical channel to the PCDP layer of the master base station through the Xn interface in the RLC layer of the secondary base station along the path as shown in FIG. 7. can do.
  • the secondary base station receiving the data of the secondary logical channel may simply forward the data of the secondary logical channel from the RLC layer of the secondary base station to the RLC layer of the master base station along the path as shown in FIG. 8. That is, in the master-slave RLC configuration of FIG. 8, the secondary base station receiving the uplink data simply delivers all received data to the RLC layer in the master base station regardless of whether the RLC PDU is configured. Therefore, the RLC layer of the master base station may configure RLC PDUs by combining data transmitted from MAC layers in different base stations.
  • the mapping relationship between uplink grants for serving cells configured for each base station and a logical channel corresponding to the RB configured for each base station will be considered. Can be.
  • the terminal may support QoS for each base station through uplink by performing uplink scheduling based on the mapping relationship.
  • 15 is a block diagram of a terminal and a base station according to an example of the present invention.
  • the terminal 1500 includes a receiver 1505, a UE processor 1510, and a transmitter 1515.
  • the UE processor 1510 is composed of a radio bearer setting unit 1511 and a data processor 1512.
  • the receiver 1505 receives radio bearer configuration information from the MeNB 1550.
  • the radio bearer configuration information may be defined by any one of the radio bearer configuration information according to the first, second and third embodiments disclosed herein.
  • the radio bearer setting unit 1511 configures the terminal 1500 with the same radio bearer RB corresponding to both the MeNB 1550 and the SeNB 1580 based on the radio bearer configuration information.
  • the same radio bearer may be one or multiple.
  • the same radio bearer is split or separated across the MeNB 1550 and the SeNB 1580 to be configured in the terminal 1500.
  • a portion separated by the terminal 1500 and the MeNB 1550 is called an RB of the master side
  • a portion separated by the terminal 1500 and the SeNB 1580 is called an RB of the secondary side.
  • the dual connection may be of any type of FIGS. 6 to 8.
  • different radio bearers are configured in the master base station and the secondary base station.
  • the same radio bearer corresponds to # 1 RB.
  • the data processor 1512 performs uplink scheduling for transmitting data of a logical channel to the MeNB 1550 and the SeNB 1580.
  • uplink scheduling may be called an LCP procedure.
  • the data processor 1512 generates the data of the primary logical channel and the data of the secondary logical channel based on the LCP procedure. In this case, the data processor 1512 may generate a MAC PDU based on the scheme proposed in FIGS. 12 to 14.
  • the transmitter 1515 transmits the data generated by the data processor 1512 to the MeNB 1550 and the SeNB 1580, respectively.
  • the data transmitted to the MeNB 1550 may be mapped to the data of the primary logical channel as the first MAC PDU
  • the data transmitted to the SeNB 1580 may be mapped to the data of the secondary logical channel as the second MAC PDU.
  • the transmitter 1515 transmits data of the primary logical channel on the first serving cell using the uplink resources provided by the uplink grant of the MeNB 1550 and transmits the data of the secondary logical channel to the SeNB 1580.
  • the uplink resource provided by the uplink grant may transmit on the second serving cell.
  • the MeNB 1550 includes a transmitter 1555, a receiver 1565, and a MeNB processor 1560.
  • the MeNB processor 1560 is again composed of a message generator 1562 and a parameter determiner 1561.
  • the parameter determiner 1561 determines parameters required for radio bearer configuration and logical channel configuration. For example, the parameter determiner 1561 determines all the parameters defined in Tables 1-6. In addition, the parameter determiner 1561 may determine the priority between base stations in mapping logical channel data to the MAC PDU.
  • the message generator 1562 generates radio bearer configuration information including the determined parameter, and sends it to the transmitter 1555.
  • the transmitter 1555 transmits radio bearer configuration information to the terminal 1500.
  • the receiver 1565 receives main logical channel data transmitted from the terminal 1500.
  • the receiver 1565 may receive data provided from the RLC layer of the SeNB 1580 to the PDCP layer of the MeNB 1550.
  • the receiver 1565 may receive data transferred from the RLC layer of the SeNB 1580 to the RLC layer of the MeNB 1550.

Landscapes

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

Abstract

La présente invention concerne un appareil et un procédé de transmission de données dans un système de communication radio d'un réseau hétérogène. Le procédé de transmission de données de liaison montante selon la présente invention comprend les étapes suivantes : réception, en provenance d'une station de base maître, d'informations de configuration de support radio pour une double connectivité ; construction, dans un terminal, d'un support radio identique qui correspond à la fois à la station de base maître et à au moins une station de base secondaire sur la base des informations de configuration de support radio ; transmission, à la station de base maître, de données d'un canal logique principal associé au support radio identique ; et transmission, à la ou aux stations de base secondaires, de données d'un canal logique subalterne associé au support radio identique.
PCT/KR2014/006961 2013-08-09 2014-07-29 Appareil et procédé de transmission de données dans un système de communication radio d'un réseau hétérogène WO2015020344A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR10-2013-0095037 2013-08-09
KR1020130095037A KR102103343B1 (ko) 2013-08-09 2013-08-09 이종 네트워크 무선 통신 시스템에서 데이터 전송 장치 및 방법

Publications (1)

Publication Number Publication Date
WO2015020344A1 true WO2015020344A1 (fr) 2015-02-12

Family

ID=52461623

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2014/006961 WO2015020344A1 (fr) 2013-08-09 2014-07-29 Appareil et procédé de transmission de données dans un système de communication radio d'un réseau hétérogène

Country Status (2)

Country Link
KR (1) KR102103343B1 (fr)
WO (1) WO2015020344A1 (fr)

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017007148A1 (fr) * 2015-07-06 2017-01-12 Lg Electronics Inc. Procédé pour annuler un rapport d'état de tampon (bsr) ou une requête de planification (sr) dans une connectivité double et un dispositif à cet effet
WO2017171201A1 (fr) * 2016-03-27 2017-10-05 엘지전자(주) Procédé pour transmettre/recevoir des données dans un système de communication sans fil et dispositif prenant en charge ce dernier
WO2017171202A1 (fr) * 2016-03-27 2017-10-05 엘지전자(주) Procédé d'émission/réception de données dans un système de communication sans fil et dispositif prenant en charge ce procédé
EP3270622A4 (fr) * 2015-04-10 2018-03-07 Kyocera Corporation Équipement utilisateur et dispositif de communication sans fil
CN108282868A (zh) * 2017-01-05 2018-07-13 中兴通讯股份有限公司 控制信令配置方法及装置
CN108633079A (zh) * 2017-03-24 2018-10-09 中兴通讯股份有限公司 一种逻辑信道优先级处理的方法和装置
US10285212B2 (en) 2014-03-20 2019-05-07 Kyocera Corporation Master base station, mobile station, and communication control method
CN110199541A (zh) * 2017-01-16 2019-09-03 三星电子株式会社 用于在无线通信系统中处理数据的方法和装置
CN113347663A (zh) * 2017-01-24 2021-09-03 联发科技股份有限公司 无线传送接收单元中的承载转换方法及用户设备
CN113455100A (zh) * 2019-03-29 2021-09-28 华为技术有限公司 用于中继通信的方法和装置

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102306823B1 (ko) * 2015-03-11 2021-09-29 삼성전자 주식회사 무선 통신 시스템에서 면허 도움 접속 기술 활용 시 기지국의 데이터 스케쥴링을 위한 장치 및 방법
KR102055921B1 (ko) * 2015-05-21 2019-12-13 주식회사 케이티 기지국 장치 및 통신 시스템
US10855658B2 (en) 2015-09-24 2020-12-01 Kt Corporation Method for transmitting and receiving data using WLAN carriers and apparatus thereof
KR101915842B1 (ko) * 2015-09-24 2019-01-31 주식회사 케이티 Wlan 캐리어를 이용한 데이터 송수신 방법 및 그 장치
US10582559B2 (en) * 2015-11-05 2020-03-03 Lg Electronics Inc. Method for transmitting and receiving data in wireless communication system and apparatus supporting the same
JP6810162B2 (ja) 2016-04-27 2021-01-06 エルジー エレクトロニクス インコーポレイティド データユニットを受信する方法及び装置
CN108260210B (zh) 2016-12-29 2022-02-11 华为技术有限公司 一种数据传输方法及用户设备、无线接入设备

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20080029913A (ko) * 2006-09-29 2008-04-03 이노베이티브 소닉 리미티드 무선통신 시스템에서 무선베어러 매핑을 실행하는 방법 및장치
KR20110067690A (ko) * 2009-12-15 2011-06-22 한국전자통신연구원 캐리어 어그리게이션 환경에서 호 설정을 수행하는 장치

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100608844B1 (ko) * 2004-01-09 2006-08-08 엘지전자 주식회사 ＶｏＩＰ 서비스를 제공하는 무선통신 시스템

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20080029913A (ko) * 2006-09-29 2008-04-03 이노베이티브 소닉 리미티드 무선통신 시스템에서 무선베어러 매핑을 실행하는 방법 및장치
KR20110067690A (ko) * 2009-12-15 2011-06-22 한국전자통신연구원 캐리어 어그리게이션 환경에서 호 설정을 수행하는 장치

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL.: "Feasible scenarios and benefits of dual connectivity in small cell deployment", R2-130225, 3GPP TSG-RAN WG2 MEETING #81, 28 January 2013 (2013-01-28), ST. JULIAN'S, MALTA, XP050668294, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_81/Docs/> *
INTEL CORPORATION: "Scenarios and benefits of dual connectivity", R2-130570, 3GPP TSG RAN WG2 MEETING #81, 28 January 2013 (2013-01-28), ST. JULIAN'S, MALTA, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_81/Docs/> *
LG ELECTRONICS INC.: "Connectivity Models for Small Cell Enhancement", R2-130314, 3GPP TSG-RAN WG2 #81, 28 January 2013 (2013-01-28), ST. JULIAN'S, MALTA, XP050668059, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_81/Docs/> *

Cited By (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10285212B2 (en) 2014-03-20 2019-05-07 Kyocera Corporation Master base station, mobile station, and communication control method
US10440767B2 (en) 2015-04-10 2019-10-08 Kyocera Corporation User terminal and radio communication apparatus
EP3270622A4 (fr) * 2015-04-10 2018-03-07 Kyocera Corporation Équipement utilisateur et dispositif de communication sans fil
WO2017007148A1 (fr) * 2015-07-06 2017-01-12 Lg Electronics Inc. Procédé pour annuler un rapport d'état de tampon (bsr) ou une requête de planification (sr) dans une connectivité double et un dispositif à cet effet
US10397824B2 (en) 2015-07-06 2019-08-27 Lg Electronics Inc. Method for cancelling a buffer status report or a scheduling request in dual connectivity and a device therefor
WO2017171201A1 (fr) * 2016-03-27 2017-10-05 엘지전자(주) Procédé pour transmettre/recevoir des données dans un système de communication sans fil et dispositif prenant en charge ce dernier
WO2017171202A1 (fr) * 2016-03-27 2017-10-05 엘지전자(주) Procédé d'émission/réception de données dans un système de communication sans fil et dispositif prenant en charge ce procédé
US11800503B2 (en) 2016-03-27 2023-10-24 Lg Electronics Inc. Method for transmitting/receiving data in wireless communication system and device supporting same
US11153044B2 (en) 2016-03-27 2021-10-19 Lg Electronics Inc. Method for transmitting/receiving data in wireless communication system and device supporting same
CN108282868A (zh) * 2017-01-05 2018-07-13 中兴通讯股份有限公司 控制信令配置方法及装置
CN108282868B (zh) * 2017-01-05 2023-07-18 中兴通讯股份有限公司 控制信令配置方法及装置
CN110199541A (zh) * 2017-01-16 2019-09-03 三星电子株式会社 用于在无线通信系统中处理数据的方法和装置
CN110199541B (zh) * 2017-01-16 2023-07-14 三星电子株式会社 用于在无线通信系统中处理数据的方法和装置
CN113347663A (zh) * 2017-01-24 2021-09-03 联发科技股份有限公司 无线传送接收单元中的承载转换方法及用户设备
CN113347663B (zh) * 2017-01-24 2024-04-12 联发科技股份有限公司 无线传送接收单元中的承载转换方法及用户设备
CN108633079A (zh) * 2017-03-24 2018-10-09 中兴通讯股份有限公司 一种逻辑信道优先级处理的方法和装置
CN113455100A (zh) * 2019-03-29 2021-09-28 华为技术有限公司 用于中继通信的方法和装置
CN113455100B (zh) * 2019-03-29 2022-06-14 华为技术有限公司 用于中继通信的方法和装置

Also Published As

Publication number Publication date
KR102103343B1 (ko) 2020-05-04
KR20150018300A (ko) 2015-02-23

Similar Documents

Publication Publication Date Title
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
WO2018128462A1 (fr) Procédé et dispositif de transmission de règle pour un mappage de flux qos sur drb
WO2015046923A1 (fr) Procédé et appareil pour effectuer une activation/désactivation de cellule de desserte dans un système de communication sans fil prenant en charge une double connectivité
WO2017026671A1 (fr) Procédé permettant de réaliser un rapport d&#39;état de mémoire tampon dans un système de communication dispositif à dispositif (d2d), et dispositif associé
WO2018164469A1 (fr) Procédé et dispositif de transmission de données dans un scénario de partage cu-du
WO2016048051A1 (fr) Procédé et appareil de prise en charge de technologie d&#39;accès multi-radio
WO2015020461A1 (fr) Procédé et appareil de transmission de rapport d&#39;état de tampon 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
WO2017078297A1 (fr) Procédé permettant de réaliser un rapport d&#39;état de mémoire tampon de liaison latérale dans un système de communication dispositif à dispositif (d2d), et dispositif associé
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é
WO2010123259A2 (fr) Appareil et procédé de gestion de support radio dans un système de communication sans fil
WO2018199707A1 (fr) Procédé pour terminal transmettant des signaux pour communication v2x dans un système de communication sans fil et terminal utilisant le procédé
WO2014182134A1 (fr) Procédé et appareil pour le transfert séquentiel prenant en compte les flux multiples dans un système à double connectivité
WO2019066558A1 (fr) Procédé et appareil permettant de vider une mémoire tampon harq dans un système de communication sans fil
WO2018174688A1 (fr) Procédé d&#39;attribution de puissance d&#39;un terminal ayant de multiples porteuses configurées et terminal faisant appel audit procédé
WO2019160310A1 (fr) Procédé et appareil de modification d&#39;une règle de mappage
WO2011084005A2 (fr) Procédé et appareil destines à recevoir une commande d&#39;avance de temps dans un système de communication sans fil
WO2010143900A2 (fr) Système et procédé de contrôle du flux dans un système de communication sans fil
WO2019022468A1 (fr) Procédé et appareil de sélection de porteuse
WO2017007147A1 (fr) Procédé de déclenchement de rapport d&#39;état de tampon dans une connectivité double et dispositif correspondant
WO2019022471A1 (fr) Procédé et appareil de sélection de porteuse
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
WO2019017707A1 (fr) Procédé d&#39;exécution d&#39;une procédure lcp dans un système de communications sans fil, et dispositif associé
WO2015065076A1 (fr) Procédé et appareil de configuration de paramètres de réception discontinue dans un système de communications sans fil utilisant un schéma à double connectivité
EP3198988A1 (fr) Procédé et appareil de prise en charge de technologie d&#39;accès multi-radio

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

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

Country of ref document: EP

Kind code of ref document: A1