[go: up one dir, main page]

WO2016043527A1 - Procédé et appareil pour traiter des données de plan d'utilisateur - Google Patents

Procédé et appareil pour traiter des données de plan d'utilisateur Download PDF

Info

Publication number
WO2016043527A1
WO2016043527A1 PCT/KR2015/009741 KR2015009741W WO2016043527A1 WO 2016043527 A1 WO2016043527 A1 WO 2016043527A1 KR 2015009741 W KR2015009741 W KR 2015009741W WO 2016043527 A1 WO2016043527 A1 WO 2016043527A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
user plane
wlan
carrier
entity
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/KR2015/009741
Other languages
English (en)
Korean (ko)
Inventor
홍성표
최우진
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
KT Corp
Original Assignee
KT Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from KR1020150067822A external-priority patent/KR20160030035A/ko
Priority claimed from KR1020150114278A external-priority patent/KR20160034182A/ko
Application filed by KT Corp filed Critical KT Corp
Priority to US15/511,296 priority Critical patent/US10334481B2/en
Priority to CN201580049891.2A priority patent/CN106717096B/zh
Publication of WO2016043527A1 publication Critical patent/WO2016043527A1/fr
Anticipated expiration legal-status Critical
Priority to US15/488,608 priority patent/US10064103B2/en
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/10—Access point devices adapted for operation in multiple networks, e.g. multi-mode access points

Definitions

  • the present invention is to provide a method and apparatus that can operate in the same way even if the PDCP function in the E-UTRAN uses a WLAN carrier.
  • a terminal receives additional configuration information for additional configuration of a WLAN carrier using an unlicensed frequency band and a WLAN carrier according to the additional configuration information. Or receiving downlink user plane data through a base station carrier using a licensed frequency band and transmitting uplink user plane data including via a WLAN carrier or a base station carrier according to additional configuration information. do.
  • the present invention also provides a method for processing user plane data by a base station, the method comprising: generating and transmitting additional configuration information for additional configuration of a WLAN carrier using an unlicensed frequency band and according to the additional configuration information, the WLAN carrier or licensed frequency And transmitting downlink user plane data over a band-based base station carrier and receiving uplink user plane data over a WLAN carrier or base station carrier in accordance with additional configuration information.
  • the present invention provides a method for processing data by a terminal, comprising the steps of configuring an interface and a user plane entity for transmitting and receiving data through the base station and the WLAN carrier and receiving user plane data from the base station through the interface; And transmitting control information indicating whether reception of the user plane data is successful to the base station through the interface or an interface between the terminal and the base station.
  • the user plane entity provides a method characterized in that configured in association with each data radio bearer.
  • the present invention also provides a method further comprising receiving radio bearer configuration information including configuration information for configuring the user plane entity through higher layer signaling.
  • the control information is provided by the user plane entity or PDCP entity.
  • the control information provides a method characterized in that the transmission is triggered based on at least one of polling of the base station, a period set by the base station and a timer.
  • the present invention provides a terminal for processing data, comprising: an interface for transmitting and receiving data through a WLAN carrier and a base station; and a controller configuring a user plane entity; a receiving unit receiving user plane data from the base station through the interface;
  • a terminal apparatus including a transmission unit for transmitting control information indicating whether reception of user plane data is successfully transmitted to the base station through the interface or an interface between the terminal and the base station.
  • the user plane entity provides a terminal device, characterized in that configured in association with each data radio bearer.
  • the present invention also provides a terminal device further comprising receiving radio bearer configuration information including configuration information for configuring the user plane entity through higher layer signaling.
  • FIG 3 is a diagram illustrating an example of a Layer 2 configuration diagram for the downlink in the isolation structure according to the present invention.
  • FIG. 5 is a diagram illustrating an example of a Layer2 configuration diagram for downlink in an interworking structure according to the present invention.
  • FIG. 6 is a diagram illustrating another example of a Layer2 configuration diagram for downlink in an interworking structure according to the present invention.
  • FIG. 7 is a diagram illustrating another example of a Layer2 configuration diagram for downlink in an interworking structure according to the present invention.
  • FIG. 8 is a diagram illustrating another example of a Layer2 configuration diagram for downlink in an interworking structure according to the present invention.
  • FIG. 11 is a diagram illustrating another example of a layer 2 configuration diagram for an uplink in which WLAN aggregation or WLAN interworking is configured.
  • FIG. 12 illustrates another example of a layer 2 configuration diagram for an uplink in which WLAN aggregation or WLAN interworking is configured.
  • FIG. 14 is a view for explaining the operation of the terminal according to an embodiment of the present invention.
  • 15 is a diagram for explaining an operation of a base station according to another embodiment of the present invention.
  • FIG. 16 illustrates an example of a data transmission path using an E-UTRAN carrier and a WLAN carrier.
  • 17 is a diagram illustrating another example of a data transmission path using an E-UTRAN carrier and a WLAN carrier.
  • 20 is a view for explaining the operation of the terminal according to an embodiment of the present invention.
  • 24 is a diagram for explaining an operation of a base station according to another embodiment of the present invention.
  • 26 is a diagram illustrating a configuration of a base station according to another embodiment of the present invention.
  • a base station or a cell generally refers to a station that communicates with a user terminal, and includes a Node-B, an evolved Node-B, an Sector, a Site, and a BTS.
  • Other terms such as a base transceiver system, an access point, a relay node, a remote radio head (RRH), a radio unit (RU), and a small cell may be called.
  • RRH remote radio head
  • RU radio unit
  • a base station or a cell is a generic meaning indicating some areas or functions covered by a base station controller (BSC) in CDMA, a Node-B in WCDMA, an eNB or a sector (site) in LTE, and the like. It should be interpreted as, and it is meant to cover all the various coverage areas such as megacell, macrocell, microcell, picocell, femtocell and relay node, RRH, RU, small cell communication range.
  • BSC base station controller
  • the base station may be interpreted in two senses. i) the device providing the megacell, the macrocell, the microcell, the picocell, the femtocell, the small cell in relation to the wireless area, or ii) the wireless area itself. In i) all devices which provide a given wireless area are controlled by the same entity or interact with each other to cooperatively configure the wireless area to direct the base station.
  • the base station may indicate the radio area itself to receive or transmit a signal from a viewpoint of a user terminal or a neighboring base station.
  • megacells macrocells, microcells, picocells, femtocells, small cells, RRHs, antennas, RUs, low power nodes (LPNs), points, eNBs, transmit / receive points, transmit points, and receive points are collectively referred to as base stations. do.
  • the uplink transmission and the downlink transmission may use a time division duplex (TDD) scheme that is transmitted using different times, or may use a frequency division duplex (FDD) scheme that is transmitted using different frequencies.
  • TDD time division duplex
  • FDD frequency division duplex
  • a cell means a component carrier having a coverage of a signal transmitted from a transmission / reception point or a signal transmitted from a transmission point or a transmission / reception point, and the transmission / reception point itself. Can be.
  • the multiple transmit / receive point is at least one having a base station or a macro cell (hereinafter referred to as an eNB) and a high transmission power or a low transmission power in a macro cell region, which is wired controlled by an optical cable or an optical fiber to the eNB. May be RRH.
  • an eNB a base station or a macro cell
  • a high transmission power or a low transmission power in a macro cell region which is wired controlled by an optical cable or an optical fiber to the eNB. May be RRH.
  • the physical downlink control channel described below may mean PDCCH or EPDCCH, and may also be used to include both PDCCH and EPDCCH.
  • the EPDCCH which is an embodiment of the present invention, may be applied to the portion described as the PDCCH, and the EPDCCH may be applied to the portion described as the EPDCCH as an embodiment of the present invention.
  • the eNB performs downlink transmission to the terminals.
  • the eNB includes downlink control information and an uplink data channel (eg, a physical downlink shared channel (PDSCH), which is a primary physical channel for unicast transmission, and scheduling required to receive the PDSCH.
  • a physical downlink control channel (PDCCH) for transmitting scheduling grant information for transmission on a physical uplink shared channel (PUSCH) may be transmitted.
  • PUSCH physical uplink shared channel
  • the E-UTRAN provides the assistance parameter to the terminal through broadcast signaling or dedicated RRC signaling.
  • the RAN help parameters may include at least one of an E-UTRAN signal strength threshold, a WLAN channel usage threshold, a WLAN backhaul data rate threshold, a WLAN signal strength, and an offload preference indicator.
  • the E-UTRAN may provide a list of WLAN identifiers to the terminal through broadcast signaling.
  • the above-described interworking function has a problem in that the E-UTRAN and the WLAN are independently established and interworked so that the base station can not control the radio resource more tightly in consideration of the radio state or mobility of the terminal.
  • the E-UTRAN adds the WLAN carrier as one carrier in the E-UTRAN at the RAN level in consideration of the radio state and mobility of the UE and thus the E-UTRAN carrier and the WLAN carrier.
  • the E-UTRAN adds the WLAN carrier as one carrier in the E-UTRAN at the RAN level in consideration of the radio state and mobility of the UE and thus the E-UTRAN carrier and the WLAN carrier.
  • WLAN Termination herein refers to a logical WLAN network node.
  • it may be a WLAN access point (AP) or WLAN access controller (AC).
  • the WLAN termination may be a WLAN network node, such as an existing WLAN termination or an existing WLAN AC, or may be a WLAN network node with additional functionality for WLAN merge transmission to an existing WLAN termination or an existing WLAN AC.
  • the WLAN termination may be implemented as an independent entity or as a functional entity included in another entity.
  • E-UTRAN adds a WLAN or WLAN carrier as one carrier, logically or conceptually, the UE and base station add WLAN carrier or WLAN PHY / MAC (or L1 / L2) transmission capability in addition to the existing E-UTRAN cell It can mean doing.
  • each transmission / reception structure may be combined with each other or applied independently.
  • FIG. 1 is a diagram illustrating an example of a Layer2 configuration diagram for downlink according to the present invention.
  • the E-UTRAN may transmit user plane data by providing a separation / merge function in the RLC layer as shown in FIG. 1.
  • the RLC layer provides the ability to segment and / or concatenate the RLC SDUs in order to fit the PDUs within the total size of the RLC PDU indicated by the lower layer at a particular transmission opportunity notified by the lower layer.
  • the RLC layer provides error correction through ARQ for acknowledgment mode (AM) data transmission.
  • AM acknowledgment mode
  • the RLC layer Since data transmission (or retransmission) over a WLAN carrier is provided over the WLAN PHY / MAC (or L1 / L2) layer, the RLC layer works with other standards, the WLAN MAC layer, to enable segmentation and / or concatenation. It may be unnecessary to do so.
  • the RLC layer can provide HARQ reordering function. Therefore, when the E-UTRAN wants to use the WLAN carrier as one carrier in the RLC layer, the HARQ reordering function (or reordering of the RLC layer) is used to receive data received through the E-UTRAN and another WLAN carrier. By adding, data can be transmitted in order.
  • the E-UTRAN supports transmission using a plurality of WLANs (or WLAN APs) for any purpose, such as WLAN coverage enhancement, reordering even if the RLC layer accommodates multiple WLANs (or WLAN APs). Can be applied.
  • the transmitting side of the AM RLC entity may not segment and / or concatenate the RLC SDUs, which are to be delivered separately to the WLAN termination 120 when forming AMD PDUs from the RLC SDUs.
  • the aforementioned aggregation entity may be an independent entity or may be a functional or logical entity of another network entity.
  • the aforementioned aggregation entity may be a functional entity included in the integrated device.
  • An aggregation entity creates a tunnel (e.g., a GTP tunnel or an IPSEC tunnel) necessary for transmitting data through a WLAN carrier between the base station and the terminal, and the base station between the layer 2 entity (e.g. PDCP entity) of the base station and the layer 2 entity of the terminal. And a function such as data transmission through a WLAN carrier between the terminal and the terminal.
  • a tunnel e.g., a GTP tunnel or an IPSEC tunnel
  • the aforementioned aggregation entity may be a functional entity included in the WLAN end.
  • An aggregation entity creates a tunnel (e.g., a GTP tunnel or an IPSEC tunnel) necessary for transmitting data through a WLAN carrier between the base station and the terminal, and the base station between the layer 2 entity (e.g. PDCP entity) of the base station and the layer 2 entity of the terminal. And a function such as a data transmission relay through the WLAN carrier between the terminal.
  • the aforementioned aggregation entity may be a functional entity included in the base station.
  • the terminal may deliver the RLC PDUs received through the WLAN carrier to the RLC entity in the corresponding terminal.
  • the terminal may deliver the received RLC PDUs to the corresponding RLC entity in the terminal using the WLAN L1 / L2 protocol in the terminal.
  • the terminal may deliver the PDCP SDUs / PDUs received through the WLAN carrier to the corresponding PDCP entity in the terminal.
  • the terminal may deliver the received PDCP PDUs to the corresponding PDCP entity in the terminal using the WLAN L1 / L2 protocol in the terminal.
  • FIG. 2 is a diagram illustrating another example of a Layer2 configuration diagram for the downlink according to the present invention.
  • FIG. 2 shows another example of a layer 2 configuration diagram in which an E-UTRAN adds a WLAN carrier as one carrier and transmits user plane data in the RLC layer to provide a separation / merge function.
  • the aggregation entity when configured as a functional entity included in the base station 110 as shown in FIG. 2, it may be configured to be included in the RLC entity. As another example, when the aggregation entity is configured as a functional entity included in the base station as shown in FIG. 2, it may be configured as a separate entity that is distinguished from the RLC entity.
  • FIG. 3 is a diagram illustrating an example of a Layer2 configuration diagram for downlink in a separation structure according to the present invention
  • FIG. 4 is a diagram illustrating another example of a Layer2 configuration diagram for downlink in a separation structure according to the present invention. to be.
  • the PDCP layer provides header compression and ciphering for user plane data.
  • data may be sequentially received using the PDCP reordering function for providing Release 12 dual connectivity.
  • the E-UTRAN supports the transmission using multiple WLANs (or WLAN terminations) for any purpose, such as WLAN coverage enhancement, data in order using the PDCP reordering function to provide Release 12 dual connectivity. Can be received.
  • the data transfer procedure of the PDCP entity may require an indication of successful delivery of PDCP PDUs from the subordinate entity.
  • indication information about successful delivery of PDCP PDUs may be received from an aggregation entity or the PDCP entity itself. For example, a periodic or aperiodic status report or acknowledgment transmission may be performed.
  • the E-UTRAN transmits the user plane data by using the separation / merge structure as shown in FIGS. 1 to 4.
  • Receive must be performed at the RLC layer or PDCP layer in order to receive.
  • WLANs may have lower coverage than E-UTRAN networks, may provide slower state monitoring for the wireless link, or may not be able to manage radio resources by the network, thereby greatly increasing delay in reordering, thereby limiting performance. .
  • window stalling may occur in an RLC entity or PDCP entity that performs a window operation.
  • data transmission through separation / merge may require additional buffer capacity or power consumption of the terminal.
  • the E-UTRAN may consider a method for transmitting user plane data only through the WLAN carrier.
  • this will be described as an interlocking structure and each embodiment will be described by dividing according to the structure.
  • FIG. 5 is a diagram illustrating an example of a Layer2 configuration diagram for downlink in an interworking structure according to the present invention.
  • the RLC layer segments and / or concatenates RLC SDUs to fit the PDUs within the total size of the RLC PDU indicated by the lower layer to a particular transmission opportunity notified by the lower layer. Provide the function.
  • the RLC layer provides error correction through ARQ for acknowledgment mode (AM) data transmission.
  • the RLC layer can perform segmentation and / or concatenation for interworking with another standard, the WLAN MAC layer. It may be unnecessary to do so.
  • the RLC layer can provide error correction through ARQ for acknowledgment mode (AM) data transmission. This allows you to receive confirmation of successful delivery over the WLAN.
  • the E-UTRAN supports transmission using a plurality of WLANs (or WLAN APs) for any purpose, such as WLAN coverage enhancement, the RLC layer uses HARQ reordering function (or reordering of the RLC layer). By receiving and reordering data received through different WLAN APs, the data can be transmitted in order.
  • the transmitting side of the AM RLC entity may not segment and / or concatenate the RLC SDUs to be delivered to the WLAN termination when forming AMD PDUs from the RLC SDUs.
  • segmentation and / or concatenation to have a constant size may be efficient to use the WLAN carrier.
  • the RLC layer may perform segmentation and / or concatenation functions as in conventional RLC operations.
  • FIG. 6 is a diagram illustrating another example of a Layer2 configuration diagram for downlink in an interworking structure according to the present invention.
  • the E-UTRAN may provide a function for interworking user plane data in the PDCP layer and transmit the same as shown in FIG. 7.
  • FIG. 8 is a diagram illustrating another example of a Layer2 configuration diagram for downlink in an interworking structure according to the present invention.
  • the E-UTRAN may provide a function of interworking user plane data in the PDCP layer as shown in FIG. 8 and transmit the same.
  • the aggregation entity when configured as a functional entity included in the base station 110 as shown in FIG. 8, it may be configured to be included in the PDCP entity. For example, it is configured by adding interlocking / switching / routing steps of PDCP PDUs within a PDCP entity, or adding interlocking / switching / routing steps of PDCP SDUs before performing sequence numbering on PDCP SDUs. Can be configured. Or it may be included after the sequence numbering step for the PDCP SDUs in the PDCP entity. As another example, when the aggregation entity is configured as a functional entity included in the base station 110 as shown in FIG.
  • this may be configured as a separate entity that is distinguished from the PDCP entity in a lower layer of the PDCP entity.
  • the aggregation entity when configured as a functional entity included in the base station 110, it may be configured as a separate entity that is distinguished from the PDCP entity in the upper layer of the PDCP entity.
  • the PDCP layer provides header compression and ciphering for user plane data. If the E-UTRAN supports the transmission using a plurality of WLANs (or WLAN APs) for any purpose, such as WLAN coverage enhancement, the data may be sequentially ordered using the PDCP reordering function for providing Release 12 dual connectivity. Can be received. Therefore, there is an advantage that the overhead of the RLC function processing and header addition can be reduced compared to the interworking method through the RLC layer.
  • the data transfer procedure of the PDCP entity may require indication of successful delivery of PDCP PDUs from the subordinate entity. To solve this, indication information about successful delivery of PDCP PDUs may be received from the aggregation entity or the PDCP entity itself. For example, a periodic or aperiodic status report or acknowledgment transmission may be received.
  • the base station uses the separation / merge structure as shown in FIG. 1, 2, 3, or 4 to downlink user plane data.
  • the base station may transmit downlink user plane data using an interworking structure (or a dedicated bearer structure) as shown in FIG. 5, 6, 7, or 8.
  • the method for transmitting uplink user plane data may be provided in various ways. Hereinafter, each method will be described in detail.
  • the E-UTRAN transmits user plane data by adding a WLAN carrier as one carrier
  • the E-UTRAN transmits to the specific bearer (s).
  • the uplink user plane data transmission may use the base station radio link or configure a base station dedicated bearer.
  • uplink user plane data transmission for the particular bearer (s) may be configured to use a base station carrier or to configure and use only a base station dedicated bearer.
  • FIG. 9 is a diagram illustrating an example of a layer 2 configuration diagram for an uplink in which WLAN aggregation or WLAN interworking is configured.
  • the terminal 900 may transmit uplink user plane data through the base station when the E-UTRAN transmits user plane data by adding a WLAN carrier as one carrier. Alternatively, the terminal may transmit uplink user plane data only through the base station.
  • the uplink user plane data may use an uplink transmission procedure with a conventional base station.
  • existing MAC procedures such as a logical channel priority (LCP) procedure and a buffer status report (BSR) procedure
  • LCP logical channel priority
  • BSR buffer status report
  • no additional process or function of the terminal is required.
  • the E-UTRAN transmits user plane data by adding a WLAN carrier as one carrier
  • the E-UTRAN transmits to the specific bearer (s).
  • the uplink user plane data transmission for may use a WLAN carrier or a WLAN dedicated bearer.
  • the uplink user plane data transmission for that particular bearer (s) may be made to use a WLAN carrier or only a WLAN dedicated bearer.
  • the UE may configure a WLAN group to transmit uplink user plane data through the WLAN carrier and transmit the WLAN.
  • uplink user plane data may be transmitted only through the WLAN.
  • the WLAN group may be variously represented as a WLAN radio link or WLAN termination group or WLAN termination group or WLAN group or non E-UTRAN group.
  • a group for mapping radio bearers for transmitting uplink user plane data through a WLAN carrier or a group of radio bearers for transmitting uplink user plane data through a WLAN carrier will be described as WLAN groups.
  • the WLAN group for transmitting the above-described uplink user plane data through the WLAN may include an associated RLC entity and a PDCP entity.
  • the WLAN group to transmit uplink user plane data via the WLAN may be configured independently of the conventional MAC layer or MAC entity.
  • the UE may establish (establish) the PDCP entity (s) and RLC entity (s) for the bearer (s) associated with the WLAN group through RRC dedicated signaling received from the base station. That is, the bearer configuration information received from the base station may include PDCP-CONFIG information and RLC-CONFIG information. Alternatively, the bearer configuration information may include PDCP-CONFIG information and RLC-CONFIG information without being associated with MAC-MainConfig.
  • the UE receiving the RRC dedicated signaling may deliver the RLC PDUs to the aggregation entity in the RLC entity of the corresponding radio bearer or may transmit the WLAN through the WLAN.
  • the transmitting side of the AM RLC entity in the terminal may perform retransmission of the RLC data PDUs.
  • the transmitting side of the AM RLC entity in the terminal may not segment and / or concatenate the RLC PDUs to be forwarded to the request from the WLAN end or separately to the WLAN end when retransmitting the RLC data PDUs. .
  • the transmitting side of the AM RLC entity in the terminal may include the associated RLC header in the RLC data PDU when forming AMD PDUs from the RLC SDUs, or when retransmitting the RLC data PDUs (segments).
  • the RLC layer may be efficient to use the WLAN carrier for segmenting and / or concatenating to have a certain size in transmitting data over the WLAN carrier.
  • the RLC layer may perform segmentation and / or concatenation functions as in conventional RLC operations.
  • the size information for this may be configured in the terminal through an RRC reconfiguration message, or may be set internally.
  • the terminal submits / forwards an RLC data PDU to an aggregation entity. Or, the terminal transmits the RLC data PDU on the WLAN carrier.
  • the UE may transmit information including information for identifying a radio bearer at an aggregation entity of the base station. . That is, the terminal may transmit uplink user plane data including information for enabling the base station to deliver the RLC PDUs received through the WLAN carrier to the RLC entity in the corresponding base station.
  • the terminal may include information for mapping the RLC PDUs transmitted by the terminal to the RLC entity in the base station in a WLAN MAC header or LLC header or IP header or UDP header or GTP header or IPSEC header between the WLAN terminal and the terminal. Can be transmitted.
  • the information for mapping the RLC PDUs transmitted by the terminal to the RLC entity in the base station may preferably use information for identifying a corresponding radio bearer.
  • a logical channel identifier having a value between 3 and 10 may be used as information for mapping the RLC PDUs transmitted by the terminal to the RLC entity in the base station.
  • eps-BearerIdentity may be used as information for mapping the RLC PDUs transmitted by the aforementioned terminal to the RLC entity in the base station.
  • dRB-Identity may be used as information for mapping the RLC PDUs transmitted by the aforementioned terminal to the RLC entity in the base station.
  • index information for identifying a corresponding radio bearer is newly defined and used as information for mapping the RLC PDUs transmitted by the terminal to the RLC entity in the base station, and the DRB configuration information (DRB-ToAddMod) in the terminal is defined.
  • index information for identifying the aforementioned radio bearer may be added and configured in the configuration.
  • the terminal may establish an aggregation entity in the terminal peered to the aforementioned aggregation entity.
  • the terminal may establish an aggregation entity in the terminal peered to the aforementioned aggregation entity in the RLC entity.
  • the aggregation entity in the terminal peering to the aforementioned aggregation entity receives RLC PDUs from the RLC entity and information for mapping the RLC PDUs transmitted by the aforementioned terminal to the RLC entity in the base station (for example, the aforementioned identification information). Or tunnel endpoint information).
  • the WLAN carrier may be delivered to the aforementioned aggregation entity and the aggregation entity may be delivered to the corresponding RLC entity.
  • the terminal may map the RLC PDUs transmitted by the aforementioned terminal to the RLC entity in the base station so that the base station may map the RLC PDUs to be transmitted through the WLAN carrier in the RLC layer with the RLC entity in the base station (for example, as described above). Associate identification information or tunnel endpoint information). Then, it forwards (transfers / transfers / submits) to a logical entity (or layer) for transmitting the WLAN carrier.
  • FIG. 11 is a diagram illustrating another example of a layer 2 configuration diagram for an uplink in which WLAN aggregation or WLAN interworking is configured.
  • the terminal may configure a WLAN group to transmit uplink user plane data through the WLAN and transmit the WLAN link through the WLAN carrier. It may also be configured to transmit only on the WLAN carrier.
  • the aforementioned WLAN group may include an associated PDCP entity.
  • the WLAN group may be configured independent of the MAC layer or MAC entity.
  • the terminal may establish PDCP entity (s) for the bearer (s) associated with the WLAN group through the RRC dedicated signaling received from the base station.
  • the bearer configuration information may include PDCP-CONFIG information.
  • the bearer configuration information may include PDCP-CONFIG information without being associated with MAC-MainConfig and RLC-CONFIG information.
  • the bearer configuration information may not include RLC-CONFIG information and may include only PDCP-CONFIG information without being associated with MAC-MainConfig information.
  • the terminal submits / delivers PDCP data (PDCP SDU or PDCP PDU) to an aggregation entity. Or, the terminal transmits the PDCP SDU / PDU through the WLAN carrier.
  • the terminal submits PDCP SDUs / PDUs to an aggregation entity, or the terminal transmits PDCP SDUs / PDUs on a WLAN carrier, where the base station transmits PDCP SDUs / PDUs received on the WLAN radio link to the corresponding PDCP entity in the base station. It can be sent with information to make it available for delivery.
  • the terminal may use the new header information (for example, new information in the PDCP header or new information in the new header that uses PDCP SDUs / PDUs as payloads) to map the PDCP SDUs / PDUs transmitted by the terminal to the PDCP entity in the base station. )
  • the terminal includes PDCP PDUs for mapping information for PDCP SDUs / PDUs transmitted by the terminal to the PDCP entity in the base station, WLAN MAC header or LLC header or IP header or UDP (User Datagram Protocol) header between the WLAN terminal and the terminal
  • the packet may be included in a GPRS Tunneling Protocol (GTP) header or an Internet Protocol Security Protocol (IPSEC) header.
  • GTP GPRS Tunneling Protocol
  • IPSEC Internet Protocol Security Protocol
  • a logical channel identifier having a value between 3 and 10 may be used as information for mapping the PDCP PDUs transmitted by the aforementioned terminal to the PDCP entity in the base station.
  • eps-BearerIdentity may be used as information for mapping the PDCP PDUs transmitted by the aforementioned terminal to the PDCP entity in the base station.
  • dRB-Identity may be used as information for mapping the PDCP PDUs transmitted by the aforementioned terminal to the PDCP entity in the base station.
  • index information for identifying a corresponding radio bearer is newly defined and used as information for mapping PDCP PDUs transmitted by the terminal to a PDCP entity in a base station, and used in the DRB configuration information (DRB-ToAddMod) in the terminal. It may be configured to add the index information for identifying the aforementioned radio bearer.
  • the aggregation entity in the terminal peering to the aforementioned aggregation entity receives PDCP PDUs from the PDCP entity and maps the PDCP PDUs transmitted by the aforementioned terminal to the PDCP entity in the base station (for example, the above-described identification information). Or tunnel endpoint information). And it can be delivered to the aggregation entity described above through the WLAN and the aggregation entity can be delivered to the corresponding PDCP entity.
  • the terminal may utilize a WLAN termination in proximity as the uplink user plane data is processed through a WLAN carrier or a WLAN dedicated bearer in a WLAN merging situation. Therefore, there is an advantage that can reduce the power consumption of the terminal. In addition, there is an advantage that can reduce the use of E-UTRAN radio resources by offloading the uplink traffic of the base station.
  • the E-UTRAN transmits user plane data by adding a WLAN carrier as one carrier
  • a WLAN carrier as one carrier
  • uplink user plane data transmission for a specific bearer (s) is performed by a base station.
  • the carrier and the WLAN carrier can be used.
  • FIG. 12 illustrates another example of a layer 2 configuration diagram for an uplink in which WLAN aggregation or WLAN interworking is configured
  • FIG. 13 illustrates WLAN aggregation or WLAN interworking.
  • FIG. 4 shows another example of a layer 2 diagram for the configured uplink.
  • the UE may transmit uplink user plane data through the base station carrier and the WLAN carrier in the E-UTRAN transmitting the user plane data by adding the WLAN carrier as one carrier.
  • FIG. 12 shows a split or routed uplink data to a base station carrier and a WLAN carrier in a PDCP entity.
  • the terminal transmits uplink user plane data through the base station carrier and the WLAN carrier, so that the terminal receives uplink data rate / throughput when WLAN aggregation or WLAN interworking is configured to receive downlink data.
  • the terminal transmits uplink user plane data through the base station carrier and the WLAN carrier, so that the terminal receives uplink data rate / throughput when WLAN aggregation or WLAN interworking is configured to receive downlink data.
  • the WLAN radio link quality temporarily deteriorates
  • performance may be improved by transmitting or retransmitting uplink data through the E-UTRAN.
  • the terminal performs a buffer status reporting procedure for performing uplink data transmission through the MAC of the E-UTRAN.
  • a base station dedicated bearer or a WLAN dedicated bearer may be configured for uplink data transmission, or the terminal may perform a buffer status reporting procedure for transmitting uplink data through the MAC of the E-UTRAN. To report only a portion (or a certain amount) of the data available for transmission of the PDCP entity and the amount of available data of the RLC entity or, in the case of FIG. 13, the data available for transmission of the PDCP entity. can do.
  • uplink user plane data transmission may be performed using the above-described method of using a base station carrier or a method of using a WLAN carrier.
  • the base station may configure the terminal to transmit user plane data by adding a WLAN carrier in addition to the base station carrier using an upper layer message (eg, an RRC reconfiguration message).
  • the base station may configure the RRC CONNECTED terminal to transmit a user plane data by adding a WLAN carrier using an upper layer message (RRC Reconfiguration message).
  • the base station receives the downlink user plane data for a specific radio bearer through the aforementioned interworking structure (or WLAN dedicated bearer structure or WLAN radio link using structure) and the uplink user plane data is described above. It can be configured to transmit through a link utilization structure (or a base station dedicated bearer structure).
  • the downlink RLC data PDU may be transmitted from the RLC entity of the base station to the RLC entity of the terminal through the WLAN carrier as described with reference to FIGS. 5 and 6.
  • the uplink RLC data PDU may be transmitted from the terminal RLC entity to the base station RLC entity through the base station carrier as described with reference to FIG. 9.
  • the uplink RLC status report for the downlink RLC data PDU may be transmitted from the terminal RLC entity to the base station RLC entity via the base station carrier.
  • the downlink RLC STATUS REPORT for the uplink RLC data PDU may be transmitted from the base station RLC entity to the terminal RLC entity through the base station carrier.
  • the reordering function may not be performed.
  • the RLC SDU can be delivered to the PDCP entity without performing the reordering function.
  • the T-reordering timer can be configured to zero or less.
  • the downlink PDCP data PDU may be transmitted from the PDCP entity of the base station to the PDCP entity of the terminal through the WLAN carrier as described with reference to FIGS. 7 and 8.
  • the uplink PDCP data PDU may be transmitted from the terminal PDCP entity to the base station PDCP entity through the base station carrier.
  • the data transfer procedure of the PDCP entity may require confirmation of successful delivery of PDCP SDUs / PDUs from the subordinate entity.
  • the aggregation entity or the PDCP entity itself can receive indication information on successful delivery of PDCP SDUs / PDUs. For example, a periodic or aperiodic status report or acknowledgment transmission may be performed.
  • the base station receives the downlink user plane data for a specific radio bearer through the aforementioned interworking structure (or WLAN dedicated bearer structure or WLAN radio link using structure), and the uplink user plane data is described in the aforementioned WLAN radio link.
  • the base station receives the downlink user plane data for a specific radio bearer through the aforementioned interworking structure (or WLAN dedicated bearer structure or WLAN radio link using structure), and the uplink user plane data is described in the aforementioned WLAN radio link.
  • the downlink RLC data PDU may be transmitted from the RLC entity of the base station to the RLC entity of the terminal through the WLAN carrier as shown in FIGS. 5 and 6.
  • the uplink RLC data PDU may be transmitted from the terminal RLC entity to the base station RLC entity through the WLAN carrier as shown in FIG. 10.
  • the uplink RLC STATUS REPORT for the downlink RLC data PDU may be transmitted from the terminal RLC entity to the base station RLC entity via the WLAN carrier.
  • the downlink RLC STATUS REPORT for the uplink RLC data PDU may be transmitted from the base station RLC entity to the terminal RLC entity via the WLAN carrier.
  • the reordering function may not be performed.
  • the RLC SDU can be delivered to the PDCP entity without performing the reordering function.
  • the T-reordering timer can be configured to zero or less.
  • the downlink PDCP data PDU may be transmitted from the PDCP entity of the base station to the PDCP entity of the terminal through the WLAN radio link as shown in FIGS. 7 and 8.
  • the uplink PDCP data PDU may be transmitted from the terminal PDCP entity to the base station PDCP entity through the WLAN carrier as shown in FIG. 11.
  • Data transfer procedures for PDCP entities may require confirmation of successful delivery of PDCP PDUs from subordinate entities.
  • the aggregation entity or the PDCP entity itself can receive indication information on successful delivery of PDCP PDUs. For example, a periodic or aperiodic status report or acknowledgment transfer operation may be performed.
  • information for instructing the radio bearer configuration information (DRB-ToAddMod) to transmit or receive downlink or uplink data through a WLAN carrier (or downlink / uplink WLAN radio link use or downlink WLAN).
  • Information for identifying a radio link using bearer type may be included and transmitted.
  • information (or downlink / uplink) for instructing the RLC configuration information (RLC-CONFIG) to transmit and / or receive downlink and / or uplink data through a WLAN carrier.
  • Information for identifying a WLAN radio link usage or a downlink WLAN radio link usage bearer type may be transmitted.
  • information for instructing the PDCP configuration information (PDCP-CONFIG) to transmit and / or receive downlink and / or uplink data through a WLAN carrier.
  • Information for identifying a WLAN radio link usage or a downlink WLAN radio link usage bearer type may be transmitted.
  • the base station receives the downlink user plane data for a specific radio bearer through the aforementioned separation / merge structure, and transmits the uplink user plane data through the aforementioned base station radio link utilization structure (or base station dedicated bearer structure). Can be configured to do this.
  • the downlink RLC data PDUs may be transmitted from the RLC entity of the base station to the RLC entity of the terminal through the base station radio link and / or the WLAN radio link as shown in FIGS. 1 and 2. Can be.
  • the uplink RLC data PDU may be transmitted from the terminal RLC entity to the base station RLC entity through the base station carrier.
  • the uplink RLC STATUS REPORT for the downlink RLC data PDU may be transmitted from the terminal RLC entity to the base station RLC entity via the base station carrier.
  • the downlink RLC STATUS REPORT for the uplink RLC data PDU may be transmitted from the base station RLC entity to the terminal RLC entity via the base station carrier.
  • the downlink RLC STATUS REPORT for the uplink RLC data PDU may be transmitted from the base station RLC entity to the terminal RLC entity through the base station carrier and the WLAN carrier.
  • the downlink PDCP data PDU may be transmitted from the PDCP entity of the base station to the PDCP entity of the terminal through the base station radio link and / or the WLAN radio link as shown in FIGS. 3 and 4. Can be.
  • the uplink PDCP data PDU may be transmitted from the terminal PDCP entity to the base station PDCP entity through the base station carrier. Data transfer procedures for PDCP entities may require confirmation of successful delivery of PDCP PDUs from subordinate entities.
  • the aggregation entity or the PDCP entity itself can receive indication information on successful delivery of PDCP PDUs. For example, a periodic or aperiodic status report or acknowledgment transfer operation may be performed.
  • the radio bearer configuration information may include information for instructing the terminal to receive downlink data through a base station carrier or a WLAN carrier (or information for distinguishing such bearer types).
  • a base station carrier or a WLAN carrier or information for distinguishing such bearer types
  • RLC-CONFIG RLC configuration information
  • PDCP-CONFIG PDCP configuration information
  • the base station receives the downlink user plane data for a specific radio bearer through the aforementioned separation / merge structure, and transmits the uplink user plane data through the WLAN carrier utilization structure (or WLAN dedicated bearer structure) described above. Can be configured to do this.
  • the downlink RLC data PDU may be transmitted from the RLC entity of the base station to the RLC entity of the terminal through the base station carrier and / or the WLAN carrier as shown in FIGS. 1 and 2.
  • the uplink RLC data PDU may be transmitted from the terminal RLC entity to the base station RLC entity through the WLAN radio link / carrier as shown in FIG. 10.
  • the uplink RLC STATUS REPORT for the downlink RLC data PDU may be transmitted from the terminal RLC entity to the base station RLC entity via the WLAN carrier.
  • the downlink RLC STATUS REPORT for the uplink RLC data PDU may be transmitted from the base station RLC entity to the terminal RLC entity via the base station carrier.
  • the downlink RLC STATUS REPORT for the uplink RLC data PDU may be transmitted from the base station RLC entity to the terminal RLC entity through the base station carrier and the WLAN carrier.
  • the downlink PDCP data PDU may be transmitted from the PDCP entity of the base station to the PDCP entity of the terminal through the base station carrier and / or the WLAN carrier, as shown in FIGS. 3 and 4. .
  • the uplink PDCP data PDU may be transmitted from the terminal PDCP entity to the base station PDCP entity through the WLAN carrier.
  • Data transfer procedures for PDCP entities may require confirmation of successful delivery of PDCP PDUs from subordinate entities.
  • the aggregation entity or the PDCP entity itself can receive indication information on successful delivery of PDCP PDUs. For example, periodic or aperiodic status reports or acknowledgment transfer operations may be performed.
  • the radio bearer configuration information may include information for instructing the terminal to receive downlink data through a base station carrier or a WLAN carrier (or information for distinguishing such bearer types). have. Or in the case of the aforementioned RLC layer separation / merge structure, information for instructing the UE to receive downlink data through the base station carrier and / or the WLAN carrier in the RLC configuration information (RLC-CONFIG) (or to distinguish such bearer types). Information) may be included and transmitted.
  • information for instructing the terminal to receive downlink data through the base station carrier and / or the WLAN carrier in the PDCP configuration information (or to distinguish such bearer types).
  • Information may be included and transmitted.
  • DRB-ToAddMod radio bearer configuration information
  • RLC-CONFIG RLC configuration information
  • PDCP-CONFIG PDCP configuration information
  • Information for instructing the terminal to transmit uplink data through the WLAN carrier (or information for specifying an uplink data path) and / or information for configuring the foregoing (eg, base station PDCP PDUs).
  • Information for instructing to provide confirmation of successful delivery may be included and transmitted.
  • the base station includes information for identifying a transmission path of downlink user plane data and / or information for identifying a transmission path of uplink user plane data for each radio bearer. That is, the terminal recognizes the reception structure of the downlink user plane data so that the terminal can receive and process the downlink user plane data through the corresponding entity. Alternatively, the terminal may set up a transmission structure of uplink user plane data to transmit data therethrough.
  • the base station may attempt downlink transmission only over the WLAN carrier for downlink transmission.
  • the backhaul delay is large, even if downlink data is transmitted through a separation structure that merges the base station carrier and the WLAN carrier, reordering may require a lot of processing, thereby degrading performance.
  • the radio bearer configured to receive data through only the WLAN carrier (for example, FIGS. 5, 6, and 7). Delays and data interruptions to process Figure 8) to modify the base station bearer may occur.
  • the base station transmits information for configuring / adding / modifying downlink data transmission bearers through the WLAN carrier to the terminal through an RRC reconfiguration message.
  • the configuration information for configuring / adding / modifying downlink data transmission bearers over a WLAN carrier may be configured to transmit downlink data (PDCP SDUs or PDCP PDUs) to a terminal through a WLAN carrier (for example, a GTP tunnel or an IPSEC tunnel). Tunnel endpoint information) or the terminal may include information for classifying downlink data received through a WLAN carrier into PDCP entities (or aggregation entities).
  • the aforementioned RRC reconfiguration message includes radio bearer configuration information (DRB-ToAddMod) for configuring the terminal to transmit uplink data through the base station carrier.
  • DRB-ToAddMod radio bearer configuration information
  • the terminal finds a problem with the WLAN radio link, it may report it to the base station. Or the base station directly finds a problem with the WLAN radio link. The base station may then operate as follows.
  • the base station transmits downlink data through the base station carrier. That is, data may be received using radio bearer configuration information (DRB-ToAddMod) configured to transmit uplink data.
  • DRB-ToAddMod radio bearer configuration information
  • the base station transmits information for releasing / modifying the downlink data transmission bearer through the WLAN carrier to the terminal through an RRC reconfiguration message.
  • the radio bearer configuration information DRB-ToAddMod may be delivered through delta signaling.
  • the base station may instruct to deliver the PDCP SDUs / PDUs successfully received in the PDCP entity / Aggregation entity of the terminal to the base station. Instruction information for this may be configured through an RRC reconfiguration message.
  • the base station may retransmit PDCP SDUs or PDCP PDUs based on this.
  • the base station may submit PDCP SDUs or PDCP PDUs as subordinate entities based on this.
  • the WLAN carrier when a user equipment transmits user plane data by adding a WLAN carrier to an E-UTRAN carrier, the WLAN carrier is simultaneously transmitted to the E-UTRAN carrier for the downlink and / or uplink on a radio bearer basis. There is an effect of using or to select the E-UTRAN carrier and WLAN carrier to transmit user plane data.
  • FIG. 14 is a view for explaining the operation of the terminal according to an embodiment of the present invention.
  • the terminal may include receiving downlink user plane data through a WLAN carrier or a base station carrier using a licensed frequency band according to the additional configuration information (S1420).
  • the terminal may include transmitting uplink user plane data including through the WLAN carrier or the base station carrier according to the additional configuration information (S1430).
  • downlink user plane data may be received through the WLAN carrier in association with a Packet Data Convergence Protocol (PDCP) entity of a base station, and uplink user plane data may be transmitted only through the base station carrier.
  • PDCP Packet Data Convergence Protocol
  • downlink user plane data may be received through the WLAN carrier in association with a Packet Data Convergence Protocol (PDCP) entity of the base station and uplink user plane data may be transmitted only through the WLAN carrier.
  • the downlink user plane data may be received through the WLAN carrier and the base station carrier separately from the base station or the Packet Data Convergence Protocol (PDCP) entity, and the uplink user plane data may be transmitted only through the base station carrier.
  • the downlink user plane data may be received through the structure of each embodiment described with reference to FIGS. 1 to 8.
  • the uplink user plane data may be transmitted through the structure of each embodiment described with reference to FIGS. 9 to 13.
  • the terminal when the terminal transmits uplink user plane data through only the WLAN carrier, the terminal may add information to identify the radio bearer in the aggregation entity to the uplink user plane data.
  • the terminal may receive and transmit downlink user plane data and uplink user plane data by a combination of the above-described downlink structure and uplink structure.
  • 15 is a diagram for explaining an operation of a base station according to another embodiment of the present invention.
  • a base station In a method for processing user plane data, a base station according to another embodiment of the present invention generates and transmits additional configuration information for additional configuration of a WLAN carrier using an unlicensed frequency band and according to the additional configuration information.
  • the method may include transmitting downlink user plane data through a base station carrier using a licensed frequency band and receiving uplink user plane data through a WLAN carrier or a base station carrier according to additional configuration information.
  • the base station may transmit and receive downlink user plane data and uplink user plane data by a combination of the above-described downlink structure and uplink structure.
  • the terminal and the base station of the present invention may perform the terminal operation and the base station operation of the present invention described above, respectively.
  • a user terminal receives additional configuration information for additional configuration of a WLAN carrier using an unlicensed frequency band, and according to the additional configuration information, a downlink user through a WLAN carrier or a base station carrier using a licensed frequency band. It may include a receiver for receiving the plane data and a transmitter for transmitting the uplink user plane data included through the WLAN carrier or the base station carrier according to the additional configuration information.
  • the receiver may receive the information to identify the radio bearer in the aggregation entity in addition to the uplink user plane data.
  • the base station 1600 may receive uplink data from the terminal 1620 using an eNB carrier.
  • downlink data may be transmitted using a WLAN carrier through the WLAN end 1610. That is, the eNB carrier may handle uplink transmission, and the WLAN carrier may handle downlink transmission, respectively.
  • the aforementioned eNB carrier refers to an E-UTRAN carrier and means a carrier formed through an E-UTRAN radio resource.
  • the terminal when the upper layer requests PDCP re-establishment, the terminal performs the following operation.
  • E-UTRAN adds WLAN as one carrier to transmit user plane data for a specific radio bearer, separating or interworking user plane data at the PDCP layer, and over a WLAN carrier (or E-UTRAN carrier and WLAN User plane data).
  • the PDCP entity must receive indication / acknowledgement of successful delivery of PDCP PDUs from the entity transmitting or receiving PDCP PDUs over the WLAN carrier, so that the PDCP SDUs can be retransmitted when performing PDCP re-establishment.
  • the PDCP entity may be controlled to generate PDCP data within a limited PDCP sequence number only after receiving an indication / confirmation of successful delivery of PDCP PDUs from an entity transmitting or receiving PDCP PDUs through a WLAN carrier.
  • an entity that interfaces with the PDCP entity at the base station and / or the terminal to transmit or receive PDCP PDUs over the WLAN carrier should be able to provide an indication / acknowledgement for successful delivery of the PDCP PDUs to the interfaced PDCP entity.
  • the present invention provides a method for enabling a base station to perform a conventional PDCP transmission function in processing data by adding a WLAN carrier as one carrier.
  • the user plane entity may be configured in association with each data radio bearer. That is, it may be determined whether a user plane entity is configured for each data radio bearer. For example, in the case of a data radio bearer not using a WLAN carrier, the user plane entity is not configured, but a user plane entity may be configured only in the case of a data radio bearer using a WLAN carrier.
  • the terminal may receive configuration information for configuring the user plane entity from the base station.
  • Configuration information for configuring a user plane entity may be included in the radio bearer configuration information and received. That is, for the user plane entity configured for each radio bearer, each radio bearer configuration information may include configuration information for the user plane entity. For example, in the case of a radio bearer transmitting and receiving data using only an E-UTRAN carrier, the radio bearer configuration information may not include configuration information for configuring a user plane entity. In contrast, in the case of a data radio bearer using a WLAN carrier, the radio bearer configuration information may include configuration information for configuring a user plane entity.
  • the radio bearer configuration information may be received through higher layer signaling. For example, the radio bearer configuration information may be received in an RRC message such as an RRC connection reconfiguration message.
  • the terminal of the present invention includes receiving user plane data from the base station through the configured interface (S2020). For example, as described with reference to FIGS. 16 to 19, the terminal may receive user plane data using a WLAN carrier according to each scenario. In this case, data may be received through an interface using a WLAN carrier configured in step S2010. That is, the terminal may process data received through the WLAN carrier through the user plane entity.
  • the terminal of the present invention includes transmitting control information indicating whether reception of the user plane data to the base station through an interface or an interface between the terminal and the base station (S2030).
  • the control information is information for confirming or indicating the normal arrival of data transmitted by the aforementioned PDCP entity, and the highest PDCP SDU / PDU sequence number successfully received / delivered in sequence to the UE among those PDCP SUDs / PDUs received from eNB / WLAN termination), the transport packet information including the PDCP sequence number that is considered lost, and the PDCP data of the highest PDCP sequence number successfully received by the terminal through the WLAN carrier.
  • the control information may be provided in the user plane entity or PDCP entity.
  • the user plane entity may check whether the received PDCP PDU is normally received, and if a missing or out of order PDCP PDU is received, the user plane entity may include information about this in the control information and transmit the information to the base station.
  • the PDCP entity may check whether the received PDCP PDU is normally received, and if a missing or out of order PDCP PDU is received, information on the PDCP PDU may be included in the control information and transmitted to the base station.
  • the transmission of the control information may be triggered based on the polling of the base station, a period set by the base station, or a timer. In this case, the terminal may receive in advance a cycle or timer information for transmitting the control information.
  • control information may be transmitted to the base station through an interface configured to process data using the WLAN carrier.
  • control information may be transmitted to the base station through an interface through the E-UTRAN carrier between the terminal and the base station. That is, the control information may be transmitted through an interface using a WLAN carrier or may be transmitted through an interface using only an E-UTRAN carrier.
  • the control information on whether or not the normal reception is provided to the base station, and according to the PDCP transmission or PDCP reset within a limited PDCP sequence number.
  • PDCP PDU retransmission function can be provided.
  • the functions provided by the conventional PDCP entity may be similarly provided in the case of data transmission and reception using a WLAN carrier.
  • the terminal and base station, or terminal and WLAN termination of the present invention may be provided with a Ux user plane protocol for carrying control information to provide an indication or confirmation of successful delivery of PDCP PDUs on the Ux interface.
  • the Ux user plane protocol is a protocol for controlling E-UTRAN wireless network user plane data transmission on the Ux interface, and is referred to as a Ux UP or Ux UP protocol for convenience of the following description.
  • the entity in the terminal or base station that processes the aforementioned Ux UP protocol may be a user plane entity or a Ux UP protocol entity or a Ux protocol instance or a Ux interworking entity or a Ux interworking instance or a interworking entity or a interworking protocol entity or interworking. It may be variously expressed as a working entity, an aggregation entity, or a transport protocol entity. However, hereinafter, it is described as a user plane entity or a Ux UP protocol entity for convenience of understanding.
  • a user plane entity may be associated with only one radio bearer (eg, data radio bearer).
  • each user plane entity may be associated with only one E-RAB.
  • the user plane entity may be configured at the base station and the terminal where the radio bearer is setup / added / configured on the Ux interface.
  • the base station includes an RRC including user plane entity configuration information for setting a user plane entity in radio bearer configuration information (DRB-ToAddMod) configured to be radio bearer-specific (or radio bearer-specific). It can be delivered to the terminal through a reconfiguration (RRC Reconfiguration) message.
  • RRC Reconfiguration reconfiguration
  • the Ux UP protocol may provide control information for confirming / indicating successful delivery of PDCP SDUs / PDUs transmitted from a base station to a terminal through a WLAN carrier.
  • the Ux UP protocol may provide control information for confirming / indicating successful delivery of PDCP SDUs / PDUs transmitted from the terminal to the base station via the WLAN carrier.
  • the user plane entity When user plane data for a particular radio bearer (or E-RAB) is sent over the Ux interface, the user plane entity will operate a procedure to provide control information to confirm / indicate successful delivery of PDCP SDUs / PDUs. Can be.
  • E-RAB radio bearer
  • the base station assigns a consecutive Ux-UP sequence number to each transmitted Ux-UP packet.
  • the terminal detects whether a Ux-UP packet is lost at a predetermined period set by the base station or when a request of the base station occurs. Or, the terminal detects whether the Ux-UP packet is lost by the polling field setting included in the Ux-UP packet header at all times.
  • the terminal may detect whether the packet is lost by the reordering function of the PDCP entity and transmit it to the user plane entity.
  • the UE receives the highest Ux-UP sequence number successfully received, the highest PDCP sequence number successfully received, and the PDCP sequence considered to be lost.
  • One or more pieces of information may be transmitted to the base station.
  • the UE may receive the highest Ux-UP sequence number and the highest PDCP sequence number successfully received when the request of the base station occurs at regular intervals or in accordance with the polling field setting.
  • Information on one or more of the PDCP sequence numbers that are considered lost may be sent to the base station.
  • the terminal detects whether the Ux-UP packet is lost at regular intervals set by the base station or at the request of the base station or by the polling field setting included in the Ux-UP packet header from the base station or at all times. If an out of sequence or lost Ux-UP packet is detected, the terminal declares the highest PDCP sequence number successfully received, the sequence number of the Ux-UP packet declared to be lost by the terminal, and is lost by the terminal. Information on at least one of the PDCP PDUs sequence numbers may be transmitted to the base station.
  • control information may be transmitted through the uplink Ux interface.
  • control information may be transmitted through the uplink Uu interface between the base station and the terminal.
  • the Uu interface represents an interface between a conventional base station and a terminal through an E-UTRAN carrier. If transmitted through the Uu interface, the control information may be provided through the PDCP Control PDU.
  • a PDCP STATUS report can be used. Or, it may be provided through a PDCP Control PDU of a new format for transmitting control information.
  • the terminal may declare that a Ux-UP packet that has not been received according to a predetermined period set by the base station or a request of the base station is lost. Alternatively, the terminal may declare that the Ux-UP packet which is not always received according to the polling field setting included in the Ux-UP packet header from the base station is lost. Alternatively, the terminal may declare the Ux-UP packet not received after receiving the out of order Ux-UP packet as lost. Alternatively, the terminal may receive a Ux-UP packet out of order, and may declare that the Ux-UP packet not received after the expiration time by the base station has been lost.
  • the user plane entity checks whether or not the user plane data received by the WLAN carrier is normally received and transmits control information.
  • a method of identifying out of order data or missing data using a separate sequence number for data received through a WLAN carrier in a user plane entity has been described.
  • the Ux UP protocol does not provide a sequence number for user data (or PDCP SDUs / PDUs) transmitted through the WLAN carrier, but uses the sequence number of the SDUs / PDCP PDUs to PDCP to the terminal through the WLAN carrier.
  • Control information may be provided to confirm / indicate successful delivery of SDUs / PDUs.
  • the UE detects whether a Ux-UP packet is lost at a predetermined period set by the base station or a request or polling field setting of the base station or constantly.
  • the terminal may transmit the highest received PDCP sequence number to the base station.
  • the terminal may transmit to the base station the highest PDCP sequence number successfully received at regular intervals or at the request of the base station or according to the polling field setting included in the Ux-UP packet header from the base station.
  • the terminal detects a certain period set by the base station or a request or polling field setting of the base station or whether the Ux-UP packet is constantly lost. If an out-of-order Ux-UP packet is detected or a lost Ux-UP packet is detected, one or more pieces of information of the highest PDCP sequence number successfully received and the PDCP PDUs sequence number declared as lost by the terminal are detected. May be transmitted to the base station. Alternatively, the terminal may transmit to the base station at least one of a period or a request or polling field setting of the base station or the highest PDCP sequence number which is successfully received at all times and the PDCP PDUs sequence number declared as lost by the terminal. Even in this case, information on the highest PDCP sequence number successfully received and the PDCP PDUs sequence numbers declared to be lost by the terminal may be included in the control information.
  • control information may be transmitted through the uplink Ux interface.
  • control information may be transmitted through the uplink Uu interface between the base station and the terminal. If control information is transmitted through the Uu interface, it may be provided through the PDCP Control PDU.
  • control information can be transmitted using the PDCP STATUS report. Alternatively, the control information may be transmitted through the PDCP Control PDU in a new format.
  • the UE is a Ux-UP packet at regular intervals set by the base station, or at the request of the base station, or by the polling field setting included in the Ux-UP packet header from the base station, or constantly, or the terminal is out of order. After receiving, or after the UE receives the out of order Ux-UP packet and the expiration time by the base station has elapsed, it may declare that the Ux-UP packet not received is lost.
  • the base station may remove the buffered PDCP SDUs / PDUs according to the feedback of the successfully delivered PDCP SDUs / PDUs.
  • the UE may remove the buffered PDCP SDUs / PDUs according to the feedback of the successfully delivered PDCP SDUs / PDUs.
  • FIG. 22 illustrates another example of a user plane protocol structure for user plane data transmission according to the present invention.
  • the WLAN end 1610 indicates that routing is performed at the IP layer in FIG. 22, it is also included in the scope of the present invention that the WLAN end 1610 performs routing / switching or MAC switching on the Data Link Layer.
  • a GTP tunnel may be set up in the base station 1600 and the terminal 1620.
  • the base station 1600 uses a downlink tunnel to separate or interwork with a WLAN carrier and transmit user data to be transmitted through a GTP protocol ( Or GTP-U protocol or WLAN interworking tunnel protocol or any tunnel protocol).
  • the UE 1620 uses an uplink tunnel to separate or interwork with the WLAN carrier to transmit user data to be transmitted through the GTP protocol. (Or GTP-U protocol or WLAN interworking tunnel protocol or any tunnel protocol).
  • the above-described tunnel between the base station 1600 and the terminal 1620 is a user data packet (or encapsulated between a given pair of tunnel endpoints).
  • E-UTRAN Layer 2 SDU / PDU or E-UTRAN Layer 2 User Data is a user data packet (or encapsulated between a given pair of tunnel endpoints).
  • the tunnel between the base station 1600 and the terminal 1620 may be a given tunnel endpoint ( tunnel endpoints may be used to carry PDCP SDUs or PDCP PDUs between pairs.
  • the tunnel between the base station 1600 and the terminal 1620 is a given tunnel endpoint ( tunnel endpoints may be used to carry RLC PDUs between pairs.
  • the tunnel protocol header (eg, GTP header or header on any tunnel based on header encapsulation) of the tunnel between the base station 1600 and the terminal 1620 includes a tunnel endpoint identification (eg, TEID) field. Include. This field indicates the receiving tunnel protocol entity (GTP-U protocol entity or GTP protocol entity or interworking entity or interworking protocol entity or GTP tunnel entity or GTP-U tunnel entity or GTP entity or GTP-U entity or interworking entity or unambiguously identifies tunnel endpoints in an aggregation entity or a aggregation protocol entity or a transport protocol entity, hereinafter referred to as a tunnel protocol entity.
  • a tunnel protocol entity e.g, GTP header or header on any tunnel based on header encapsulation
  • the tunnel endpoint included in the tunnel protocol header may indicate the tunnel to which a particular user data packet belongs.
  • Tunnel endpoint identification information (eg, TEID) included in the tunnel protocol header may demultiplex incoming traffic and allow it to be delivered to the corresponding user plane radio bearer entity.
  • the terminal receiving the data through the downlink tunnel may receive the received data through the tunnel end.
  • the PDCP SDUs / PDUs may be delivered to the peered or corresponding PDCP entity in the terminal through the point identification information.
  • the merging entity may be an interworking entity, an LTE-WLAN adaptation entity, an interworking function, a logical entity for LTE-WLAN aggregation, an LTE-WLAN merging entity, etc. Used to include all of them. Also, in some cases, the merge entity may mean the above-described user plane entity.
  • the aforementioned merge entity may be an independent entity or may be a functional entity of another network entity.
  • the merging entity may be a functional entity included in the integrated device.
  • the merging entity may be a functional entity included within the WLAN end.
  • the merging entity may be a functional entity included in the base station.
  • the merge entity may be implemented as a layer entity higher than L1 / L2.
  • a functional entity included in a WLAN end when configured as a functional entity included in a WLAN end, it may operate as a layer entity higher than WLAN L1 / L2 to transmit user plane data to the terminal through WLAN L1 / L2.
  • a functional entity included in the base station when configured as a functional entity included in the base station, it may operate as a higher layer entity (for example, an IP layer or a session layer or an application layer) to transmit user plane data to a terminal through a WLAN end.
  • the user plane data when configured as a functional entity included in the base station, the user plane data can be transmitted to the terminal through the WLAN end by operating as an entity performing a function for delivering PDCP PDUs through the WLAN end.
  • the merging entity may be configured as a function in WLAN L2 to allow the WLAN L2 entity to implement the actions for it.
  • the merging entity may receive PDCP PDUs from the PDCP entity of the base station.
  • the PDCP PDUs may be requested to the PDCP entity of the base station to receive PDCP PDUs.
  • the merging entity may transmit the received PDCP PDUs to the terminal through the WLAN carrier.
  • the merging entity may transmit the received PDCP PDUs to the terminal using the WLAN L1 / L2 protocol.
  • the merge entity may transmit the received PDCP PDUs to the terminal through a WLAN end (or WLAN carrier) using IP communication.
  • the terminal may deliver the PDCP PDUs received on the WLAN carrier to the PDCP entity in the corresponding terminal.
  • the terminal may deliver the received PDCP PDUs to the corresponding PDCP entity in the terminal using the WLAN L1 / L2 protocol in the terminal.
  • the base station may separate data traffic belonging to a specific bearer in the PDCP layer through the base station and the WLAN end. That is, the PDCP entity may separately submit PDCP PDUs into an associated RLC entity and / or an associated merge entity in order to transmit user plane data through an E-UTRAN carrier and a WLAN carrier on a radio bearer basis.
  • the base station allows a terminal to transmit to a specific bearer through a WLAN carrier (or through a WLAN L1 / L2 protocol or WLAN radio reception). It can be configured to deliver the received PDCP PDUs to the PDCP entity of the corresponding specific bearer in the terminal.
  • the base station allows the terminal to communicate over a WLAN carrier (or via a WLAN L1 / L2 protocol or WLAN radio for that particular bearer).
  • the received PDCP PDUs may be transmitted including information for delivering to the PDCP entity of the corresponding specific bearer in the terminal.
  • FIG. 23 is a diagram illustrating another example of a user plane protocol structure for user plane data transmission according to the present invention.
  • PDCP PDUs user plane data
  • GTP-U can carry PDCP PDUs.
  • the E-UTRAN adds the WLAN carrier as one carrier and configures LTE-WLAN merging for transmitting downlink user data traffic using the E-UTRAN carrier and the WLAN carrier simultaneously
  • the base station 1600 and the WLAN termination A user data bearer is set up at an interface between the 1610 and a user plane protocol instance (UP Protocol entity) is set up at the base station 1600 and the WLAN end 1610 as shown in FIG. 23.
  • UP Protocol entity UP Protocol entity
  • Each user plane protocol instance or UP protocol entity on the interface between the base station 1600 and the WLAN end 1610 is associated with one E-RAB. Accordingly, each E-RAB associates with the user plane data bearer on the interface between the base station 1600 and the WLAN end 1610 or the endpoint of the user plane data bearer of the base station 1600 associated with the bearer and the bearer.
  • Each endpoint of the WLAN end 1610 may be identified using a GTP Tunnel endpoint Information Element (IE).
  • IE GTP Tunnel endpoint Information Element
  • the coalescing entity included in the WLAN end 1610 described above may include user plane instances / entities in the WLAN end 1610 described above.
  • the merge entity may operate in association with the user plane instance / entity within the WLAN end 1610 described above.
  • the merging entity may operate as a user plane instance / entity within the WLAN end 1610 described above.
  • PDCP PDUs user plane data
  • the base station 1600 includes PDCP PDUs (user plane data) to be delivered to the terminal 1620 through the WLAN terminal 1610 in the data field of the IP packet, and the WLAN terminal 1610 using the IP address of the terminal 1620 as the destination address. Can be sent to the terminal 1620 through PDCP PDUs (user plane data)
  • PDCP PDUs user plane data on the interface between base station 1600 and WLAN end 1610 may be WLAN L2 (or WLAN MAC).
  • the base station 1600 includes the PDCP PDUs (user plane data) to be delivered to the terminal 1620 through the WLAN end 1610 in the data field of the WLAN L2 (or WLAN MAC) frame and receives the WLAN MAC address of the terminal 1620. The address may be sent to the terminal 1620 through the WLAN end 1610.
  • the user plane protocol instance (UP Protocol entity) included in the aforementioned WLAN end 1610 is determined to trigger a feedback for downlink data delivery, it is successfully sent to the terminal 1620 among PDCP PDUs received from the base station 1600.
  • Information such as the highest PDCP PDU sequence number transmitted to the buffer size, the buffer size for the corresponding E-RAB, the user plane protocol instant packet that is considered to be lost may be transmitted to the base station 1600.
  • the base station 1600 may receive information on successful reception of PDCP PDUs from the terminal 1620 by the following methods.
  • the function of receiving control information on successful reception of PDCP PDUs from the terminal 1620 may be included in the aforementioned merge entity function.
  • the merge entity receives the received RCP entity through a partial RLC entity peered thereto. can do.
  • the merge entity may receive and process it through the PDCP peered thereto.
  • an interface connected between a base station and a terminal through a WLAN carrier is defined as a Ux interface.
  • the UP protocol entity may provide some function (eg, RLC status reporting function) for the ARQ procedure of the RLC layer. That is, a new user plane entity (eg, user plane sublayer entity) in the terminal may provide some function for an ARQ procedure (eg, RLC status reporting function) of the conventional RLC layer.
  • RLC status reporting function eg, RLC status reporting function
  • this is a separate user plane entity separate from the RLC entity for handling PDCP PDUs received over the LTE radio link.
  • it may be referred to as a WLAN RLC entity that is distinct from an LTE RLC entity.
  • this is referred to as a user plane object. This is for convenience of description and the name is not limited.
  • User plane entities may send PDCP PDUs to their peer user plane entities.
  • the user plane entity may provide control information for providing an indication / confirmation of successful delivery of PDCP PDUs on the Ux interface.
  • the present invention as described above provides the effect that the conventional PDCP function to operate the same even when the base station and the terminal to transmit and receive data by adding a WLAN carrier.
  • the present invention provides an effect of performing a retransmission procedure by checking whether data reception is completed even when the base station and the terminal adds and transmits WLAN data.
  • 26 is a diagram illustrating a configuration of a base station according to another embodiment of the present invention.
  • the receiver 2630 may receive control information indicating whether reception of the user plane data is successful from the terminal through an interface or an interface between the terminal and the base station.
  • the control information may be provided by the user plane entity or PDCP entity of the terminal.
  • the control information may be received by the transmission is triggered based on at least one of the polling of the base station, a period set by the base station and a timer.

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 traiter des données de plan d'utilisateur par un terminal et une station de base, et, plus particulièrement, un procédé et un appareil pour transmettre et recevoir des données de plan d'utilisateur par ajout d'un réseau local sans fil (WLAN) à une porteuse E-UTRAN au niveau d'un réseau d'accès radio (RAN). La présente invention concerne notamment un procédé et un appareil pour traiter des données de plan d'utilisateur par un terminal, le procédé comprenant les étapes consistant à : recevoir des informations de configuration supplémentaires pour configurer de manière supplémentaire une porteuse de WLAN à l'aide d'une bande de fréquences non autorisée ; recevoir des données de plan d'utilisateur de liaison descendante par l'intermédiaire d'une porteuse de station de base à l'aide de la porteuse de WLAN ou d'une bande de fréquences autorisée selon les informations de configuration supplémentaires ; et transmettre des données de plan d'utilisateur de liaison montante incluses par l'intermédiaire de la porteuse de WLAN ou de la porteuse de station de base selon les informations de configuration supplémentaires.
PCT/KR2015/009741 2014-09-18 2015-09-16 Procédé et appareil pour traiter des données de plan d'utilisateur Ceased WO2016043527A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US15/511,296 US10334481B2 (en) 2014-09-18 2015-09-16 Method and apparatus for processing user plane data
CN201580049891.2A CN106717096B (zh) 2014-09-18 2015-09-16 用于处理用户平面数据的方法及装置
US15/488,608 US10064103B2 (en) 2014-09-18 2017-04-17 Method and apparatus for processing user plane data

Applications Claiming Priority (10)

Application Number Priority Date Filing Date Title
KR20140124570 2014-09-18
KR10-2014-0124570 2014-09-18
KR10-2014-0133265 2014-10-02
KR20140133265 2014-10-02
KR10-2015-0067822 2015-05-15
KR1020150067822A KR20160030035A (ko) 2014-09-05 2015-05-15 Lte-wlan 분리/연동 프로토콜 제공방법 및 장치
KR10-2015-0114273 2015-08-13
KR10-2015-0114278 2015-08-13
KR1020150114273A KR101853527B1 (ko) 2014-09-05 2015-08-13 Wlan 캐리어를 이용한 데이터 처리 방법 및 그 장치
KR1020150114278A KR20160034182A (ko) 2014-09-18 2015-08-13 사용자 플레인 데이터 처리 방법 및 그 장치

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US15/511,296 A-371-Of-International US10334481B2 (en) 2014-09-18 2015-09-16 Method and apparatus for processing user plane data
US15/488,608 Division US10064103B2 (en) 2014-09-18 2017-04-17 Method and apparatus for processing user plane data

Publications (1)

Publication Number Publication Date
WO2016043527A1 true WO2016043527A1 (fr) 2016-03-24

Family

ID=55533498

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2015/009741 Ceased WO2016043527A1 (fr) 2014-09-18 2015-09-16 Procédé et appareil pour traiter des données de plan d'utilisateur

Country Status (1)

Country Link
WO (1) WO2016043527A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2563584A (en) * 2017-06-16 2018-12-26 Tcl Communication Ltd Bearer control

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140050086A1 (en) * 2011-04-29 2014-02-20 Nageen Himayat Control and data plane solutions for carrier-aggregation based wlan offload
US8824298B2 (en) * 2011-10-03 2014-09-02 Intel Corporation Multi-RAT carrier aggregation for integrated WWAN-WLAN operation

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140050086A1 (en) * 2011-04-29 2014-02-20 Nageen Himayat Control and data plane solutions for carrier-aggregation based wlan offload
US8824298B2 (en) * 2011-10-03 2014-09-02 Intel Corporation Multi-RAT carrier aggregation for integrated WWAN-WLAN operation

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
INTEL CORPORATION: "Stage-2 details of WLAN/3GPP Radio Interworking for LTE", R2-143177, 3GPP TSG RAN WG2 MEETING #87, 8 August 2014 (2014-08-08) *
SAMSUNG: "AS/NAS modeling for WLAN/3GPP radio interworking", R2-142214, 3GPP TSG RAN WG2 MEETING #86, 9 May 2014 (2014-05-09), pages 1 - 2 *
SONY: ""Ue capabilities for WLAN Interworking", R2-143162, 3GPP TSG RAN WG2 MEETING #87, 8 August 2014 (2014-08-08), pages 1 - 2 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2563584A (en) * 2017-06-16 2018-12-26 Tcl Communication Ltd Bearer control
US11018817B2 (en) 2017-06-16 2021-05-25 Jrd Communication (Shenzhen) Ltd Bearer control
GB2563584B (en) * 2017-06-16 2022-05-04 Tcl Communication Ltd Bearer control
US11700091B2 (en) 2017-06-16 2023-07-11 JRD Communication (Shenzhen) Ltd. Bearer control

Similar Documents

Publication Publication Date Title
WO2020263028A1 (fr) Dispositif et procédé pour réaliser un transfert intercellulaire dans un système de communication sans fil
WO2021066466A1 (fr) Procédé et appareil pour effectuer un transfert intercellulaire dans système de communication sans fil
WO2015115854A1 (fr) Procédé et appareil de transmission/réception de données au moyen d'une pluralité de porteuses dans un système de communications mobiles
WO2020197361A1 (fr) Procédé et appareil de transfert sans interruption de transmission et de réception de données dans un système de communication mobile de prochaine génération
WO2018030798A1 (fr) Procédé et appareil de gestion d'opération de plan utilisateur dans un système de communication sans fil
WO2020045948A1 (fr) Procédé et appareil pour réaliser une double connectivité dans un réseau hétérogène
WO2020027508A1 (fr) Procédé et appareil de communication de nœud sans fil dans un système de communications sans fil
WO2020022849A1 (fr) Procédé et appareil destinés à une communication sans fil d'un nœud sans fil dans un système de communication sans fil
WO2020067813A1 (fr) Appareil et procédé permettant d'établir une double connectivité dans un système de communication sans fil
EP3100376A1 (fr) Procédé et appareil de transmission/réception de données au moyen d'une pluralité de porteuses dans un système de communications mobiles
WO2017039042A1 (fr) Procédé et dispositif de transmission/réception de données de terminal dans un système de communication sans fil
WO2019066588A1 (fr) Procédé et système de gestion d'une opération pdcp dans un système de communication sans fil
EP3479647A1 (fr) Procédé d'établissement d'une interface fronthaul, procédé de mise en uvre d'un accès pour un équipement utilisateur, procédé et appareil de mise en uvre d'un transfert intercellulaire pour un équipement utilisateur, procédé de transfert de données, équipement utilisateur et station de base
WO2018203739A1 (fr) Procédé d'établissement d'une interface fronthaul, procédé de mise en œuvre d'un accès pour un équipement utilisateur, procédé et appareil de mise en œuvre d'un transfert intercellulaire pour un équipement utilisateur, procédé de transfert de données, équipement utilisateur et station de base
WO2020222527A1 (fr) Procédé et appareil permettant d'effectuer une procédure de transfert intercellulaire dans système de communication sans fil
WO2019199140A1 (fr) Procédé et dispositif d'attribution de ressources permettant de prendre en charge une communication de véhicule dans un système de communication mobile de prochaine génération
WO2019031883A1 (fr) Procédé et dispositif de rétablissement d'un pdcp dans un système de communication sans fil
WO2018079998A1 (fr) Procédé de réalisation de transfert dans un système de communication sans fil, et dispositif associé
WO2016153130A1 (fr) Procédé et dispositif pour transmettre ou recevoir des données par un terminal dans un système de communication sans fil
WO2018182366A1 (fr) Procédé de traitement de données en fonction des tcp/ip
WO2019031941A1 (fr) Procédé permettant de prendre en charge un transfert intercellulaire et appareil correspondant
WO2020027491A1 (fr) Procédé de traitement de données dans un nœud relais, et dispositif associé
WO2015064972A1 (fr) Procédé et appareil de configuration de connexion double dans un réseau de communication mobile
WO2019135649A1 (fr) Procédé et dispositif permettant l'amélioration de performances de communication dans un système de communication sans fil
WO2016148357A1 (fr) Procédé et appareil de transmission/réception de données pour terminal dans un système de communication sans fil

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 15511296

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205N DATED 26/05/2017)

122 Ep: pct application non-entry in european phase

Ref document number: 15842159

Country of ref document: EP

Kind code of ref document: A1