[go: up one dir, main page]

WO2016159634A1 - Procédé de reconfiguration d'un support sans fil et dispositif associé - Google Patents

Procédé de reconfiguration d'un support sans fil et dispositif associé Download PDF

Info

Publication number
WO2016159634A1
WO2016159634A1 PCT/KR2016/003203 KR2016003203W WO2016159634A1 WO 2016159634 A1 WO2016159634 A1 WO 2016159634A1 KR 2016003203 W KR2016003203 W KR 2016003203W WO 2016159634 A1 WO2016159634 A1 WO 2016159634A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdcp
radio bearer
data
wlan
bearer
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/KR2016/003203
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
Application filed by KT Corp filed Critical KT Corp
Priority to US15/562,463 priority Critical patent/US10485042B2/en
Priority to CN201680007805.6A priority patent/CN107211475B/zh
Priority claimed from KR1020160037352A external-priority patent/KR101870022B1/ko
Publication of WO2016159634A1 publication Critical patent/WO2016159634A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections

Definitions

  • the present invention relates to a technique for transmitting user plane data by adding a WLAN connection to a terminal where a base station establishes a wireless connection at a radio access network (RAN) level.
  • RAN radio access network
  • the present invention relates to a method and apparatus for configuring or reconfiguring a radio data bearer for transmitting user plane data.
  • LTE Long Term Evolution
  • LTE-Advanced of the current 3GPP series are high-speed and large-capacity communication systems that can transmit and receive various data such as video and wireless data beyond voice-oriented services.
  • the development of technology capable of transferring large amounts of data is required.
  • As a method for transmitting a large amount of data data can be efficiently transmitted using a plurality of cells.
  • the unlicensed frequency band that can not be used exclusively by a specific operator or a specific communication system can be shared by multiple operators or communication systems.
  • WLAN technology represented by Wi-Fi provides data transmission / reception services using frequency resources of the unlicensed band.
  • the mobile communication system also requires a study on the technology for transmitting and receiving data with the terminal using a corresponding Wi-Fi access point (AP).
  • AP Wi-Fi access point
  • the present invention devised in this background provides a specific method and apparatus for a base station to add / modify / release / change a radio bearer using at least one of a WLAN radio resource and a base station radio resource.
  • the present invention provides a method for a UE to reconfigure a radio bearer, the terminal comprising: data for a specific radio bearer configured to receive downlink data using only a wireless local area network (WLAN) radio resource from a base station; A PDCP data recovery procedure is performed in a Packet Data Convergence Protocol (PDCP) entity based on receiving a higher layer signaling including information for changing a radio bearer type and information for changing a data radio bearer type for a specific radio bearer. And performing a reordering procedure for the specific radio bearer in a PDCP entity.
  • PDCP Packet Data Convergence Protocol
  • the present invention provides a method for a terminal reconfiguring a radio bearer, the higher layer signaling including information for changing the data radio bearer type for a specific radio bearer configured to receive downlink data using only the base station radio resources from the base station Initiating a reordering procedure for the particular radio bearer in the Packet Data Convergence Protocol (PDCP) entity based on the receiving and information for changing the data radio bearer type for the particular radio bearer.
  • PDCP Packet Data Convergence Protocol
  • the present invention provides a method for a base station to reconfigure a radio bearer of the terminal, information for changing the data radio bearer type for a specific radio bearer configured to receive downlink data using only a wireless local area network (WLAN) radio resource; PDCP SDUs / PDUs (PDCP Service) that have not been verified to be successfully delivered from the PDCP entity based on the step of transmitting higher layer signaling, including a packet data convergence protocol (PDCP) status report from the terminal, and a PDCP status report from the terminal; Data Unit / Protocol Data Unit) provides a method comprising the step of retransmitting.
  • WLAN wireless local area network
  • the present invention also provides information for changing a data radio bearer type for a specific radio bearer configured to receive downlink data using only a wireless local area network (WLAN) radio resource from a base station in a terminal for reconfiguring a radio bearer.
  • a PDCP data recovery procedure is performed in a Packet Data Convergence Protocol (PDCP) entity based on information of changing a data radio bearer type for a specific radio bearer and a receiver that receives higher layer signaling.
  • PDCP Packet Data Convergence Protocol
  • a terminal device including a control unit for performing a reordering procedure for a bearer.
  • the present invention is a terminal for reconfiguring a radio bearer, receiving a higher layer signaling including information for changing the data radio bearer type for a specific radio bearer configured to receive the downlink data using only the base station radio resources from the base station It provides a terminal device including a receiver and a control unit for initiating a reordering procedure for the specific radio bearer in the Packet Data Convergence Protocol (PDCP) entity based on information for changing the data radio bearer type for the specific radio bearer.
  • PDCP Packet Data Convergence Protocol
  • the present invention also provides a base station for reconfiguring a radio bearer of a terminal, comprising information for changing a data radio bearer type for a specific radio bearer configured to receive downlink data using only a wireless local area network (WLAN) radio resource.
  • PDCP SDUs / PDUs PDCP Service Data Units
  • PDCP Packet Data Convergence Protocol
  • the base station can dynamically transmit and receive data with the terminal using the WLAN radio resources.
  • the present invention provides a specific method for reconfiguring a terminal and a radio bearer in transmitting user plane data by adding a WLAN radio resource in addition to the base station radio resource to reduce the lossless data transmission effect of the radio bearer mapped to the AM RLC. to provide.
  • 1 is a diagram illustrating a 2C solution structure in a dual connectivity situation.
  • 3 exemplarily illustrates a 1A solution structure in a dual connectivity situation.
  • FIG. 4 is a view for explaining the operation of the terminal according to an embodiment of the present invention.
  • FIG. 5 is a view for explaining the operation of the base station according to another embodiment of the present invention.
  • FIG. 6 is a view for explaining the operation of the terminal according to another embodiment of the present invention.
  • FIG. 7 is a view for explaining a terminal configuration according to another embodiment of the present invention.
  • FIG. 8 is a view for explaining the configuration of a base station according to another embodiment of the present invention.
  • the MTC terminal may mean a terminal supporting low cost (or low complexity) or a terminal supporting coverage enhancement.
  • the MTC terminal may mean a terminal supporting low cost (or low complexity) and coverage enhancement.
  • the MTC terminal may mean a terminal defined in a specific category for supporting low cost (or low complexity) and / or coverage enhancement.
  • the MTC terminal may mean a newly defined 3GPP Release 13 low cost (or low complexity) UE category / type for performing LTE-based MTC related operations.
  • the MTC terminal supports an enhanced coverage compared to the existing LTE coverage, or UE category / type defined in the existing 3GPP Release 12 or less that supports low power consumption, or newly defined Release-13 low cost (or low). complexity) can mean UE category / type.
  • the wireless communication system in the present invention is widely deployed to provide various communication services such as voice, packet data, and the like.
  • the wireless communication system includes a user equipment (UE) and a base station (base station, BS, or eNB).
  • a user terminal is a generic concept meaning a terminal in wireless communication.
  • user equipment (UE) in WCDMA, LTE, and HSPA, as well as mobile station (MS) in GSM, user terminal (UT), and SS It should be interpreted as a concept that includes a subscriber station, a wireless device, and the like.
  • 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 the viewpoint of the user terminal or the position of 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 user terminal and the base station are two transmitting and receiving entities used to implement the technology or technical idea described in this specification in a comprehensive sense and are not limited by the terms or words specifically referred to.
  • the user terminal and the base station are two types of uplink or downlink transmitting / receiving subjects used to implement the technology or the technical idea described in the present invention, and are used in a generic sense and are not limited by the terms or words specifically referred to.
  • the uplink (Uplink, UL, or uplink) refers to a method for transmitting and receiving data to the base station by the user terminal
  • the downlink (Downlink, DL, or downlink) means to transmit and receive data to the user terminal by the base station It means the way.
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • OFDM-FDMA OFDM-TDMA
  • OFDM-CDMA OFDM-CDMA
  • One embodiment of the present invention can be applied to resource allocation in the fields of asynchronous wireless communication evolving to LTE and LTE-Advanced through GSM, WCDMA, HSPA, and synchronous wireless communication evolving to CDMA, CDMA-2000 and UMB.
  • the present invention should not be construed as being limited or limited to a specific wireless communication field, but should be construed as including all technical fields to which the spirit of the present invention can be applied.
  • 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 standard is configured by configuring uplink and downlink based on one carrier or a pair of carriers.
  • the uplink and the downlink include a Physical Downlink Control CHannel (PDCCH), a Physical Control Format Indicator CHannel (PCFICH), a Physical Hybrid ARQ Indicator CHannel (PHICH), a Physical Uplink Control CHannel (PUCCH), an Enhanced Physical Downlink Control CHannel (EPDCCH), and the like.
  • Control information is transmitted through the same control channel, and data is configured by a data channel such as a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH).
  • PDSCH physical downlink shared channel
  • PUSCH physical uplink shared channel
  • control information may also be transmitted using an enhanced PDCCH (EPDCCH or extended PDCCH).
  • EPDCCH enhanced PDCCH
  • extended PDCCH extended PDCCH
  • 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.
  • a wireless communication system to which embodiments are applied may be a coordinated multi-point transmission / reception system (CoMP system) or a coordinated multi-antenna transmission scheme in which two or more transmission / reception points cooperate to transmit a signal.
  • antenna transmission system a cooperative multi-cell communication system.
  • the CoMP system may include at least two multiple transmission / reception points and terminals.
  • 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.
  • downlink refers to a communication or communication path from a multiple transmission / reception point to a terminal
  • uplink refers to a communication or communication path from a terminal to multiple transmission / reception points.
  • a transmitter may be part of multiple transmission / reception points, and a receiver may be part of a terminal.
  • a transmitter may be part of a terminal, and a receiver may be part of multiple transmission / reception points.
  • a situation in which a signal is transmitted and received through a channel such as a PUCCH, a PUSCH, a PDCCH, an EPDCCH, and a PDSCH may be expressed in the form of 'sending and receiving a PUCCH, a PUSCH, a PDCCH, an EPDCCH, and a PDSCH.
  • a description of transmitting or receiving a PDCCH or transmitting or receiving a signal through the PDCCH may be used as a meaning including transmitting or receiving an EPDCCH or transmitting or receiving a signal through the EPDCCH.
  • 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.
  • RRC signaling for transmitting RRC information including an RRC parameter.
  • 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 WLAN carrier in the present specification refers to a radio resource of a WLAN and may be described in various terms as necessary, such as a WLAN radio link, a WLAN radio, a WLAN radio resource, or a WLAN radio network.
  • a WLAN radio link, a WLAN radio, a WLAN carrier, or a WLAN radio network will be described as WLAN radio resources
  • a bearer using WLAN radio resources will be described as WLAN bearers.
  • the WLAN termination herein refers to a logical WLAN network node. For example, it may be a WLAN AP or a WLAN AC.
  • the WLAN termination may be a WLAN network node, such as an existing WLAN AP or an existing WLAN AC, or may be a WLAN network node with additional functionality for WLAN merge transmission to an existing WLAN AP or an existing WLAN AC.
  • the WLAN termination may be implemented as an independent entity or as a functional entity included in another entity.
  • the WLAN network node will be described as WLAN end point or WLAN AP as necessary.
  • radio resources provided by the base station eNB are described as base station radio resources, base station carriers, or E-UTRAN carriers, and a bearer using the base station radio resources is described as base station bearers.
  • 3GPP / WLAN interworking technology provides RAN assisted WLAN interworking functionality.
  • the E-UTRAN may help terminal-based two-way traffic steering between the E-UTRAN and the WLAN for terminals in the RRC_IDLE and RRC_CONNECTED states.
  • the E-UTRAN provides the assistance parameter to the terminal through broadcast signaling or dedicated RRC signaling.
  • the RAN help parameters include at least one of an E-UTRAN signal strength threshold, a WLAN channel utilization threshold, a WLAN backhaul data rate threshold, a WLAN signal strength (or WLAN signal strength threshold, eg BeaconRSSI threshold) and an offload preference indicator. It may include one.
  • the E-UTRAN may provide a list of WLAN identifiers to the terminal through broadcast signaling.
  • the terminal selects an access network selection and traffic control rule defined in TS 36.304.
  • RAN assistance parameters may be used to evaluate the traffic steering rules or ANDSF policies defined in the TS 24.312 document.
  • the terminal may indicate this to an upper layer of an access stratum (AS).
  • AS access stratum
  • the terminal When the terminal applies the access network selection and traffic control rules, the terminal performs traffic control in APN granularity between the E-UTRAN and the WLAN.
  • the RAN assisted WLAN interworking function provides only a method in which the E-UTRAN and the WLAN are built and stand alone.
  • the need for LTE WLAN integration capabilities to allow for tighter integration at the RAN level has also increased.
  • Rel-12 RAN assisted WLAN interworking was only possible for E-UTRAN and WLAN to operate independently in APN units. Accordingly, in transmitting UE user plane data, the E-UTRAN adds a 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 / or WLAN.
  • the carrier could not be configured to be used simultaneously.
  • the E-UTRAN transmits a WLAN carrier to the UE at the RAN level in consideration of the radio state and mobility of the UE while maintaining the E-UTRAN carrier. Configured to add like one carrier and could not transmit over E-UTRAN carrier and / or WLAN carrier.
  • the E-UTRAN adds a WLAN carrier as one carrier in the E-UTRAN at the RAN level to transmit user plane data over the E-UTRAN carrier and / or WLAN carrier on the E-UTRAN layer 2.
  • a method of splitting (or splitting or routing) user plane data and a method of interworking user plane data may be considered.
  • a method of interworking with the user plane data separation method based on 2C and 3C of the dual connectivity solution may be applied.
  • Dual Connectivity Solutions 2C and 3C are the solutions presented in the 3GPP Dual Connectivity section, described in more detail below.
  • 1 is a diagram illustrating a 2C solution structure in a dual connectivity situation.
  • a structure for adding and configuring a WLAN radio resource in the terminal is similar to the dual connectivity 2C solution, and transmits data to be transmitted through a WLAN carrier in conjunction with a WLAN AP in a PDCP entity in association with a WLAN AP and peers the PDCP entity. Can be configured to receive.
  • the PDCP entity of the master base station (MeNB) is connected with the RLC entity of the secondary base station (SeNB).
  • a structure for adding and configuring a WLAN radio resource in a terminal is similar to a dual connectivity 3C solution, and separates and transmits data to be transmitted through an E-UTRAN carrier and / or data to be transmitted through a WLAN carrier in a PDCP entity, and peering.
  • the received PDCP entity can receive (or merge) it.
  • the PDCP entity of the master base station (MeNB) is connected to the RLC entity of the master base station and the RLC entity of the secondary base station, and performs routing functions in the PDCP entity.
  • 3 exemplarily illustrates a 1A solution structure in a dual connectivity situation.
  • the base station needs an operation for adding, modifying, or releasing a terminal and a radio bearer (or a data radio bearer (hereinafter, referred to as a radio bearer)) by adding a WLAN carrier, but a specific method is not described. Did.
  • configuration / reconfiguration operations such as adding, modifying, changing, and releasing a radio bearer involve detailed operations of each layer 2 entity to which they are associated. Therefore, it is necessary to define the efficient operation of each layer2 object. However, no specific method has been disclosed.
  • An object of the present invention is to provide a radio bearer configuration or reconfiguration method for the base station to add / modify / release / change the terminal and the radio bearer by adding a WLAN carrier.
  • an object of the present invention is to provide efficient operation of each layer 2 entity associated with an operation such as adding, modifying, changing, or releasing a radio bearer.
  • the present invention may be provided in a scenario where a base station and a WLAN AP are non-co-located.
  • the base station and the WLAN AP may be connected or established through a non-ideal backhaul or near-ideal backhaul or an ideal backhaul.
  • the present invention may be provided in a scenario in which a base station and a WLAN AP are co-located.
  • an E-UTRAN In order for an E-UTRAN to add WLAN radio resources to a terminal at the RAN level as one carrier and to transmit and receive user plane data using the E-UTRAN carrier and the WLAN carrier, a protocol structure and operation of each detailed layer must be provided. .
  • E-UTRAN adds a WLAN radio resource or WLAN carrier as one carrier logically or conceptually configured by the UE and the base station adding functions / objects for data transmission through the WLAN carrier in addition to the existing E-UTRAN cell. It shows.
  • the E-UTRAN is indicated for convenience of description and may mean LTE / LTE-Advanced / arbitrary 3GPP radio access or base station.
  • User plane data may be split (or split or routing) or interworked on the sublayer.
  • the PDCP entity may transmit data to be transmitted through the WLAN carrier in association with the WLAN AP and allow the peered PDCP entity to receive it.
  • the PDCP entity transmits data to be transmitted through the WLAN carrier in association with the WLAN AP and marks the bearer receiving the peered PDCP entity as the WLAN bearer. This is for convenience of description and other terms meaning the concept may be used.
  • the WLAN bearer may be used for uplink data transmission and downlink data transmission.
  • the WLAN bearer may be used for downlink data transmission.
  • uplink data may be transmitted through an E-UTRAN carrier.
  • the WLAN bearer may be used for uplink data transmission, and the downlink data may be transmitted on the E-UTRAN carrier.
  • the aforementioned E-UTRAN carrier may mean a bearer using only radio resources of a base station in LTE-WLAN aggregation
  • a WLAN bearer may mean bearer using only WLAN radio resources in LTE-WLAN aggregation.
  • the WLAN bearer may change by switching radio resources to be used. That is, the switched WLAN bearer may be switched to use only base station radio resources by using only WLAN radio resources and reconfigured through an upper layer message, or may be switched to use only WLAN radio resources by using only base station radio resources and then reconfigured through an upper layer message. have. That is, the WLAN bearer will be described below using only WLAN radio resources. However, the WLAN bearer is assumed to be a switch bearer that may be changed to use only base station radio resources according to bearer reconfiguration.
  • the PDCP entity separates and transmits data to be transmitted through the E-UTRAN carrier and / or data to be transmitted through the WLAN carrier, and receives (or merges and receives) the peered PDCP entity. can do.
  • the PDCP entity similar to the dual connectivity 3C solution, the PDCP entity separates the data to be transmitted through the E-UTRAN carrier and / or the data to be transmitted via the WLAN carrier and transmits the bearer to receive it at the peered PDCP object. It is represented by a bearer (Integration bearer, aggregation bearer, WLAN split bearer). This is for convenience of description and other terms meaning the concept may be used.
  • the merge bearer may be used for uplink data transmission and downlink data transmission.
  • the downlink data may be configured to be transmitted through the E-UTRAN carrier and the WLAN carrier.
  • the uplink data may be configured to be transmitted through the E-UTRAN carrier and the WLAN carrier.
  • the merge bearer may be used for downlink data transmission.
  • the downlink data may be transmitted through the E-UTRAN carrier and the WLAN carrier.
  • uplink data may be transmitted through an E-UTRAN carrier.
  • the merge bearer may allow downlink data to be transmitted on the E-UTRAN carrier and the WLAN carrier. In this case, uplink data may be transmitted through a WLAN carrier.
  • the merge bearer may be used for uplink data transmission.
  • uplink data may be transmitted through an E-UTRAN carrier and a WLAN carrier.
  • downlink data may be transmitted through an E-UTRAN carrier.
  • uplink data may be transmitted through an E-UTRAN carrier and a WLAN carrier.
  • downlink data may be transmitted through a WLAN carrier.
  • the base station may add or configure a WLAN bearer by adding a WLAN carrier.
  • the terminal that has established the RRC connection may add a new radio bearer as a WLAN bearer through core network signaling.
  • the UE that has established the RRC connection may add a new radio bearer as a merge bearer through core network signaling.
  • a radio bearer (E-UTRAN bearer) configured in the terminal that has established the RRC connection may be reconfigured / modified / changed into a WLAN bearer.
  • a radio bearer (E-UTRAN bearer) configured in the terminal which has established the RRC connection may be reconfigured / modified / modified as a merge bearer.
  • the radio bearer (DRB) configured to transmit through the E-UTRAN carrier or the radio bearer (DRB) transmitted only through the E-UTRAN carrier to the terminal that has established the RRC connection with the base station described above
  • D Denotes a UTRAN bearer or a base station bearer. This is for convenience of description and other terms meaning the concept may be used.
  • the terminal may perform the following operation.
  • the terminal configures a PDCP entity.
  • the PDCP entity is configured according to the PDCP configuration information (PDCP-Config).
  • the terminal establishes an entity for transmitting user plane data through the WLAN carrier.
  • the object is configured according to the information for configuring the set object.
  • an entity for transmitting user plane data through a WLAN carrier in a terminal is described as a WLAN entity. This is for convenience of description and other terms meaning the concept may be used.
  • the terminal may perform the following operation.
  • the terminal sets the PDCP entity.
  • the PDCP entity is configured according to the PDCP configuration information (PDCP-Config).
  • the terminal sets the RLC entity.
  • the RLC entity is configured according to the RLC configuration information (RLC-Config).
  • the terminal establishes a WLAN entity.
  • the WLAN entity is configured according to the WLAN entity configuration information.
  • the present invention will be described by dividing a specific radio bearer configured in the terminal and the base station from the E-UTRAN bearer to the WLAN bearer or from the WLAN bearer to the E-UTRAN bearer for each embodiment.
  • FIG. 4 is a view for explaining the operation of the terminal according to an embodiment of the present invention.
  • a terminal In a method for reconfiguring a radio bearer, a terminal according to an embodiment of the present invention provides a data radio bearer type for a specific radio bearer configured to receive downlink data using only a wireless local area network (WLAN) radio resource from a base station.
  • WLAN wireless local area network
  • PDCP Packet Data Convergence Protocol
  • the terminal includes receiving higher layer signaling including information for changing a data radio bearer type for a specific radio bearer configured to receive downlink data using only WLAN radio resources from a base station (see FIG. S410).
  • the terminal may configure a radio bearer with a base station or a WLAN AP using the WLAN bearer addition or merge bearer addition method described above.
  • the specific radio bearer further configured in the terminal may be a WLAN bearer using only WLAN radio resources.
  • the WLAN bearer according to the present invention may be reconfigured after being changed to the E-UTRAN bearer by higher layer signaling as described above. Meanwhile, the UE may separately configure an E-UTRAN bearer using only base station radio resources.
  • the terminal may receive data radio bearer type information for a specific radio bearer (for example, a WLAN bearer) configured to receive downlink data using only WLAN radio resources from the base station through higher layer signaling.
  • radio bearer type information about a radio bearer may be included in an information element of an RRC connection reconfiguration message. That is, when the WLAN bearer is configured in the terminal, the radio bearer type information may include information indicating that the corresponding WLAN bearer is a bearer using only WLAN radio resources.
  • the terminal may receive information for changing the radio bearer type for the specific radio bearer from the base station.
  • the terminal may receive information for changing the information on the radio bearer type of the existing WLAN bearer into information on the radio bearer type indicating the E-UTRAN bearer from the base station. That is, when the radio bearer type information for the specific radio bearer is changed from the existing radio bearer type information, the terminal may recognize that the type of the specific radio bearer is changed.
  • the terminal includes performing a PDCP data recovery procedure on a Packet Data Convergence Protocol (PDCP) entity based on information for changing a data radio bearer type for a specific radio bearer (S420).
  • PDCP Packet Data Convergence Protocol
  • the terminal may perform a PDCP data recovery procedure in the PDCP entity.
  • the terminal needs to reconfigure the specific radio bearer in order to change the radio bearer type of the specific radio bearer from the WLAN bearer to the E-UTRAN bearer.
  • the PDCP entity in order to prevent data loss or omission of downlink data that has been received using only conventional WLAN radio resources, the PDCP entity must perform a PDCP data recovery procedure.
  • the PDCP entity may generate a PDCP status report and include the PDCP status report in a PDCP PDU (PDCP Protocol Data Unit) to deliver to the lower layer. That is, the PDCP entity may generate a PDCP status report in the PDCP layer and deliver the PDCP status report, which is created to transmit it to the base station, to a lower layer (eg, an RLC layer or a MAC layer).
  • a lower layer eg, an RLC layer or a MAC layer.
  • the terminal transmits a PDCP status report to the base station to help the base station retransmit the PDCP data when the specific radio bearer is reconfigured.
  • a specific PDCP data recovery operation will be described in more detail with reference to the following embodiments.
  • the terminal includes a step of performing a reordering procedure for a specific radio bearer in the PDCP entity (S430).
  • a specific radio bearer receiving downlink data is changed in type from a WLAN bearer to an E-UTRAN bearer
  • the UE performs a reordering procedure for the specific radio bearer in the PDCP entity. That is, in transmitting downlink data transmitted from the base station to the terminal using the WLAN radio resource to the terminal using the base station radio resource, in order to transmit data in order, to prevent data loss or loss. In order to do this, the terminal performs a reordering procedure for the received downlink data.
  • the terminal may additionally receive information for configuring the reordering timer from the base station, the information for configuring the reordering timer may be received through higher layer signaling.
  • the terminal transmits all PDCP SDUs stored for reordering to the upper layer in the ascending order of the associated COUNT value when the reordering timer expires. That is, similar to the RLC Unacknowledged Mode, when the reordering timer expires periodically, all PDCP SDUs received and stored out of the order are delivered to the upper layer, and downlink data is delivered to the upper layer in order.
  • the terminal may additionally perform a reordering procedure of the 3GPP TS 36.323 document.
  • the terminal may reconfigure a radio bearer configured to receive downlink data using only WLAN radio resources into a radio bearer configured to receive downlink data using only base station radio resources.
  • the PDCP entity in order to transmit data in sequence in this process, in order to prevent the loss or loss of downlink data, the PDCP entity reorders downlink data for a specific radio bearer, and reconstructs PDCP data of the base station. To help retransmission, a PDCP status report can be generated and sent to the base station.
  • FIG. 5 a method of reconfiguring a specific radio bearer carrying downlink data into a base station bearer will be described again from the base station perspective.
  • FIG. 5 is a view for explaining the operation of the base station according to another embodiment of the present invention.
  • a base station In a method for reconfiguring a radio bearer of a terminal, a base station according to an embodiment of the present invention provides a data radio bearer type for a specific radio bearer configured to receive downlink data using only a wireless local area network (WLAN) radio resource.
  • WLAN wireless local area network
  • PDCP SDUs for which delivery success is not confirmed in the PDCP entity on the basis of transmitting a higher layer signaling including information to be changed, receiving a Packet Data Convergence Protocol (PDCP) status report from the terminal, and a PDCP status report.
  • PDCP Packet Data Convergence Protocol
  • PDCP Service Data Unit
  • PDU PDCP Protocol Data Unit
  • a base station of the present invention provides higher layer signaling including information for changing a data radio bearer type for a specific radio bearer configured to receive downlink data using only a wireless local area network (WLAN) radio resource. It includes the step of transmitting (S610). As described above, the base station may generate and transmit information for changing the data radio bearer type for a specific radio bearer (eg, WLAN bearer) to change the WLAN bearer into an E-UTRAN bearer. For example, the base station may transmit information for changing the data radio bearer type through higher layer signaling, and the higher layer signaling may be an RRC connection reconfiguration message.
  • the base station may generate and transmit information for changing the data radio bearer type for a specific radio bearer (eg, WLAN bearer) to change the WLAN bearer into an E-UTRAN bearer.
  • the base station may transmit information for changing the data radio bearer type through higher layer signaling, and the higher layer signaling may be an RRC connection reconfiguration message.
  • the information for changing the data radio bearer type for a specific radio bearer may further include information for configuring a reordering timer used to perform the reordering procedure of the terminal.
  • the terminal receives the information for configuring the reordering timer to configure the reordering timer, and performs a reordering procedure using the reordering timer when a specific radio bearer is reconfigured.
  • the base station includes a step of receiving a Packet Data Convergence Protocol (PDCP) status report from the terminal (S520).
  • PDCP Packet Data Convergence Protocol
  • the base station changes the data radio bearer type for a specific radio bearer
  • the base station receives a PDCP status report of the specific radio bearer from the terminal.
  • the terminal receives information for changing the data radio bearer type of a specific radio bearer, the terminal generates a PDCP status report as a first PDCP PDU to be transmitted to a lower layer and transmits it to the base station.
  • the base station includes the step of retransmitting the PDCP SDU or PDCP PDU that is not confirmed whether the successful delivery in the PDCP entity based on the PDCP status report (S530).
  • the base station performs PDCP data recovery using the PDCP status report and retransmits downlink data to the terminal using only the base station radio resources.
  • the base station retransmits the PDCP PDU transmitted to the terminal using the WLAN radio resource to the terminal using the base station radio resource. That is, as a specific radio bearer is reconfigured, the PDCP PDU whose delivery success is not confirmed to the AM RLC entity is retransmitted to the terminal according to the PDCP data recovery procedure.
  • the terminal may perform the following operations.
  • the terminal resets the PDCP entity.
  • the WLAN entity may perform one or more of the following operations.
  • the UE transmits or retransmits PDCP SDUs whose successful transmission is not confirmed according to the PDCP reset, for data lost during the radio bearer change process, thereby performing lossless transmission.
  • this method must handle complex detailed operations such as header compression protocol reset and security key change, PDCP SDUs transmission or retransmission even for bearer change without change of PDCP entity, which can increase complexity and delay. have. Therefore, in the present invention, as described above, a method of reconfiguring a specific radio bearer without resetting the PDCP entity has been described.
  • the present invention describes a method of performing a PDCP data recovery procedure without resetting a PDCP entity.
  • the PDCP entity may be reconfigured or maintained.
  • the terminal may perform the following operations.
  • the RRC Connection Reconfiguration message for reconfiguring / modifying / changing a WLAN bearer into an E-UTRAN bearer includes information for changing the data radio bearer type.
  • the RRC connection reconfiguration message may include a DRB type in "drb-ToAddModList". If the DRB type of the specific radio bearer is received after being changed from the current type, the terminal may reconfigure the specific radio bearer.
  • the terminal performs PDCP data recovery previously submitted to the WLAN entity.
  • the WLAN entity may perform one or more of the following operations.
  • PDCP data recovery performs retransmission for all PDCP PDUs previously submitted to the reset AM RLC entity. Therefore, when changing a WLAN bearer into a WLAN bearer, retransmission must be performed for PDCP PDUs submitted to the WLAN entity before receiving a bearer change message (or before performing PDCP data recovery).
  • the radio bearer is configured to send a PDCP status report by the upper layer on the uplink, generate a PDCP status report and submit it to the first PDCP PDU for transmission to the lower layer.
  • the base station When PDCP data recovery for uplink is performed in the terminal, the base station should perform a reordering function for the corresponding PDCP data. Alternatively, when PDCP data recovery for downlink is performed in the base station, the terminal should perform a reordering function for the corresponding PDCP data.
  • PDCP data recovery can be performed when a bearer change occurs for a split split bearer in Rel-12 dual connectivity (e.g., when a split bearer changes to a split bearer without a PDCP reset or when a split bearer becomes a MCG without a PDCP reset). Only when changed to bearer).
  • the reordering function was performed when the split bearer is configured in the terminal.
  • the UE has a reordering function when the PDCP entity is associated with two AM RLC entities in a dual connectivity situation.
  • the reordering function was performed when the split bearer changed to the split bearer without PDCP resetting.
  • the PDCP entity is associated with one AM RLC entity after it was, according to the most recent reconfiguration, associated with two AM RLC entities without performing PDCP re reordering function was used.
  • the PDCP immediately started the reordering function upon receiving the dual connectivity split bearer configuration message, and applied a reordering method such as RLC UM through the set reordering timer (t-Reordering-r12). That is, all stored PDCP SDU (s) is transferred to the upper layer for reordering.
  • a reordering method such as RLC UM through the set reordering timer (t-Reordering-r12). That is, all stored PDCP SDU (s) is transferred to the upper layer for reordering.
  • the present invention may be set to perform a reordering procedure if PDCP data recovery is used in case of reconfiguring / modifying / modifying a WLAN bearer into an E-UTRAN bearer.
  • the base station may include information (or information for indicating this) for configuring the reordering timer for this to include in the RRC message to the terminal.
  • the base station may perform a reordering function for this.
  • the downlink data reception procedure provided by the PDCP may be used.
  • the PDCP SDU / PDU received by PDCP is immediately forwarded to the upper layer. That is, when the reordering function is not used, data transmitted through a single radio link can be directly transmitted to the upper layer without reordering the PDCP since the RLC guarantees in-sequence transmission.
  • the UE provides downlink data provided by the conventional PDCP when the aforementioned reordering function is not used.
  • Reordering can be improved to allow for reordering. For example, if the PDCP PDU received by the PDCP entity is due to an E-UTRAN bearer change in the WLAN bearer (or if it is due to the release of the WLAN entity or due to a specific operation of the WLAN entity), then reordering: You can do
  • Last_Submitted_PDCP_RX_SN to the PDCP SN of the last PDCP SDU delivered to upper layers
  • reordering is performed as follows. You can do that.
  • Last_Submitted_PDCP_RX_SN to the PDCP SN of the last PDCP SDU delivered to upper layers
  • the receiving side when the bearer type is changed from the WLAN bearer to the E-UTRAN bearer, the receiving side (for example, the UE in the downlink) performs the PDCP data recovery procedure without resetting the PDCP.
  • the reordering procedure may be performed using the reordering timer on the entity.
  • the specific radio bearer described above includes a switching function so that the E-UTRAN bearer may be reconfigured as a WLAN bearer. Therefore, a procedure according to the present invention when a specific radio bearer is configured to use only base station radio resources and is reconfigured to use only WLAN radio resources will be described below.
  • FIG. 6 is a view for explaining the operation of the terminal according to another embodiment of the present invention.
  • the terminal of the present invention receives higher layer signaling including information for changing data radio bearer type for a specific radio bearer configured to receive downlink data from a base station using only base station radio resources. And initiating a reordering procedure for the specific radio bearer in the Packet Data Convergence Protocol (PDCP) entity based on the information for changing the data radio bearer type for the specific radio bearer.
  • PDCP Packet Data Convergence Protocol
  • the terminal includes receiving higher layer signaling including information for changing a data radio bearer type for a specific radio bearer configured to receive downlink data using only base station radio resources from the base station (S610). ).
  • the terminal may receive information for changing a data radio bearer type for a specific radio bearer configured to receive downlink data.
  • information for changing the data radio bearer type uses only WLAN radio resources in the radio bearer type for receiving downlink data using the radio bearer using only the base station radio resources. It includes information to change to a radio bearer type for receiving downlink data.
  • the information for changing the data radio bearer type may be included in the RRC connection reconfiguration message.
  • the terminal checks the information for changing the data radio bearer type included in the higher layer signaling, and when the type information of the specific radio bearer is changed, performs a procedure for reconfiguring the specific radio bearer.
  • the terminal includes the step of initiating a reordering procedure for a specific radio bearer in the Packet Data Convergence Protocol (PDCP) entity based on the information for changing the data radio bearer type for the specific radio bearer (S620).
  • PDCP Packet Data Convergence Protocol
  • S620 the information for changing the data radio bearer type for the specific radio bearer
  • the terminal initiates a reordering procedure for the specific radio bearer in the PDCP entity. For example, the terminal counts the PDCP SDU using the reordering timer in the PDCP entity, and when the reordering timer expires, delivers the PDCP SDU to the higher layer.
  • the PDCP entity of the UE may initiate a reordering procedure without performing a PDCP data recovery procedure.
  • the UE may reconfigure the E-UTRAN bearer configured to receive the downlink data into the WLAN bearer without unnecessary delay and data loss.
  • the E-UTRAN bearer configured in the terminal may be reconfigured / modified / changed into the WLAN bearer through the RRC connection reconfiguration message.
  • the base station may transmit information to change the data radio bearer type of the E-UTRAN bearer in the RRC connection reconfiguration message to the terminal.
  • the conventional WLAN did not provide the same function as the RLC entity of the E-UTRAN. Therefore, when the E-UTRAN bearer is reconfigured / modified / modified to the WLAN bearer, loss may occur in the process of switching the corresponding user plane data from transmission through the E-UTRAN carrier to transmission through the WLAN carrier.
  • Radio Link Control For radio bearers mapped to AM Acknowledgment mode Radio Link Control (RLC), lossless data transmission should be guaranteed even when the E-UTRAN bearer configured in the terminal is reconfigured / modified / modified into a WLAN bearer through an RRC connection reconfiguration message. . To this end, the following embodiments can be used.
  • RLC Radio Link Control
  • the terminal may perform the following operations.
  • the terminal resets the PDCP entity.
  • the terminal resets the RLC entity.
  • the terminal establishes a WLAN entity.
  • the WLAN entity is configured or reconfigured according to the WLAN entity configuration information.
  • the UE performs one or more of the following operations for a radio bearer mapped to AM RLC.
  • a higher layer eg, RRC
  • the lower layer e.g. RLC
  • the AM RLC entity (or the terminal or the AM RLC entity of the terminal) performs one or more of the following operations.
  • RLC SDUs are derived from any byte segment of AMD PDUs whose SN is less than the maximum acceptable receive state variable (VR (MR)).
  • MR receive state variable
  • VR maximum acceptable receive state variable
  • the PDCP reset and the RLC reset are performed as described above, even if the UE discards all RLC SDUs and AMD PDUs that the transmitter did not transmit according to the RLC reset, the PDCP SDUs whose successful delivery is not confirmed according to the PDCP reset or Retransmission allows lossless transmission.
  • this method must handle complex detailed operations such as header compression protocol reset and security key change, PDCP SDUs transmission or retransmission even for bearer change without change of PDCP entity, which can increase complexity and delay. have.
  • a reconfiguration method for a specific radio bearer can be performed as follows without resetting PDCP.
  • the terminal when reconfiguring / modifying / changing an E-UTRAN bearer configured in a terminal through an RRC connection reconfiguration message to a WLAN bearer, the terminal may perform the following operation.
  • the PDCP entity may be reconfigured or maintained.
  • the terminal performs PDCP data recovery.
  • the terminal resets the RLC entity. Or, the terminal reconfigures the RLC entity.
  • the terminal configures the WLAN entity and configures or reconfigures the WLAN entity according to the WLAN entity configuration information.
  • the terminal when reconfiguring / modifying / changing an E-UTRAN bearer configured in a terminal through an RRC connection reconfiguration message to a WLAN bearer, the terminal may perform the following operation.
  • the PDCP entity is reconfigured according to the PDCP configuration information.
  • the terminal resets the RLC entity. Or, the terminal reconfigures the RLC entity.
  • the terminal configures the WLAN entity and configures or reconfigures the WLAN entity according to the WLAN entity configuration information.
  • the AM RLC entity (or the terminal or the AM RLC entity of the terminal) performs the above-described operation. Therefore, a loss may occur depending on the discarded data (SDUs or PDUs) due to the RLC reset.
  • the UE may perform PDCP data recovery.
  • the terminal (or PDCP entity or PDCP entity of the terminal) may perform one or more of the following operations.
  • the radio bearer is configured to send a PDCP status report on the uplink by the upper layer, generate a status report and submit it to the first PDCP PDU for transmission to the lower layer (if the radio bearer is configured by upper layers to send a PDCP status report in the uplink (statusReportRequired), compile a status report, and submit it to lower layers as the first PDCP PDU for the transmission).
  • the base station When PDCP data recovery for uplink is performed in the terminal, the base station should perform a reordering function for the corresponding PDCP data. When PDCP data recovery for downlink is performed at the base station, the terminal should perform a reordering function for the corresponding PDCP data.
  • PDCP data recovery can be performed when a bearer change occurs for a split split bearer in Rel-12 dual connectivity (e.g., when a split bearer changes to a split bearer without a PDCP reset or when a split bearer becomes a MCG without a PDCP reset). Only when changed to bearer).
  • the reordering function was performed when the split bearer is configured in the terminal.
  • the UE has a reordering function when the PDCP entity is associated with two AM RLC entities in a dual connectivity situation.
  • the reordering function was performed when the split bearer changed to the split bearer without PDCP resetting.
  • the PDCP entity is associated with one AM RLC entity after it was, according to the most recent reconfiguration, associated with two AM RLC entities without performing PDCP re reordering function was used.
  • the PDCP immediately started the reordering function upon receiving the dual connectivity split bearer configuration message, and applied a reordering method such as RLC UM through the set reordering timer (t-Reordering-r12). That is, all stored PDCP SDU (s) is transferred to the upper layer for reordering.
  • a reordering method such as RLC UM through the set reordering timer (t-Reordering-r12). That is, all stored PDCP SDU (s) is transferred to the upper layer for reordering.
  • the present invention may be set to perform a reordering procedure if PDCP data recovery is used in case of reconfiguring / modifying / modifying a WLAN bearer into an E-UTRAN bearer.
  • the base station may include information (or information for indicating this) for configuring the reordering timer for this to include in the RRC message to the terminal.
  • the base station may perform a reordering function for this.
  • the downlink data reception procedure provided by the PDCP may be used.
  • the PDCP PDU received by PDCP is immediately forwarded to the higher layer. That is, when the reordering function is not used, data transmitted through a single radio link can be directly transmitted to the upper layer without reordering the PDCP since the RLC guarantees in-sequence transmission.
  • reordering may be performed as follows.
  • Last_Submitted_PDCP_RX_SN to the PDCP SN of the last PDCP SDU delivered to upper layers
  • the reordering may be performed as follows.
  • Last_Submitted_PDCP_RX_SN to the PDCP SN of the last PDCP SDU delivered to upper layers
  • the terminal when reconfiguring / modifying / changing an E-UTRAN bearer configured in a terminal through an RRC connection reconfiguration message to a WLAN bearer, the terminal may perform the following operation.
  • the PDCP entity is reconfigured according to the PDCP configuration information.
  • the RLC entity is reconfigured according to the RLC configuration information.
  • the terminal configures the WLAN entity and configures or reconfigures the WLAN entity according to the WLAN entity configuration information.
  • the terminal when reconfiguring / modifying / changing an E-UTRAN bearer configured in a terminal through an RRC connection reconfiguration message to a WLAN bearer, the terminal may perform the following operation.
  • PDCP For PDCP data (eg PDUs or SDUs) sent on the uplink, PDCP does not trigger retransmission. Or PDCP does not trigger retransmission for PDCU PDUs submitted by the PDCP to the RLC entity.
  • the RLC entity completes the transmission or retransmission of all pending RLC SDUs or RLC PDUs.
  • the terminal establishes a WLAN entity.
  • the WLAN entity is configured or reconfigured according to the WLAN entity configuration information.
  • the RLC entity may be configured to complete transmission or retransmission without releasing the RLC entity.
  • the base station assumes that configuring / reconfiguring a WLAN bearer by adding a WLAN carrier is under E-UTRAN coverage. Accordingly, even though the E-UTRAN bearer configured in the terminal through the RRC connection reconfiguration message is reconfigured / modified / changed into the WLAN bearer, the terminal is in an environment capable of transmitting and receiving data with the base station through the E-UTRAN carrier / cell.
  • the UE may transmit or retransmit the radio bearer mapped to the AM RLC providing for lossless transmission through the RLC entity.
  • the RLC entity For uplink, the RLC entity performs transmission or retransmission for PDCP SDUs / PDUs received from the PDCP entity prior to bearer reconfiguration / modification / change. Alternatively, for the uplink, the RLC entity performs transmission or retransmission for RLC SDUs or RLC PUDs received from the PDCP entity prior to bearer reconfiguration / modification / change. Or, for uplink, the RLC entity performs transmission or retransmission for PDCP PDUs submitted by the PDCP entity before bearer reconfiguration / modification / change.
  • the PDCP entity transmits through the WLAN entity starting from the next PDCP PDU of the PDCP PDUs submitted by the PDCP entity before bearer reconfiguration / modification / modification. Or submit PDCP PDUs to the WLAN entity. Or deliver PDCP PDUs via a WLAN entity.
  • the RLC entity processes the RLC data received from the lower layer.
  • the PDCP entity For downlink, the PDCP entity processes the PDCP data received from the lower layer.
  • the RLC entity may be maintained until the WLAN bearer is reconfigured / modified / changed or released.
  • the RLC entity may be maintained until the transmission or retransmission of all PDCP PDUs (or RLC SDUs or RLC PDUs) received from the PDCP entity prior to bearer reconfiguration / modification / modification is completed successfully.
  • the RLC entity may maintain a certain time (timer) so that the transmission or retransmission of all PDCP PDUs received from the PDCP entity can be completed successfully before bearer reconfiguration / modification / change.
  • the RLC entity may be reconfigured or maintained for a fast switch from WLAN bearer to E-UTRAN bearer, or for uplink data transmission of WLAN bearer, or for temporary uplink data transmission.
  • information for instructing the performance of the aforementioned operation and / or related information may be included in the RRC message.
  • the above-described operation may be preconfigured to be performed.
  • the terminal when reconfiguring / modifying / changing an E-UTRAN bearer configured in a terminal through an RRC connection reconfiguration message to a WLAN bearer, the terminal may perform the following operation.
  • the PDCP entity is reconfigured according to the PDCP configuration information.
  • the RLC entity is reconfigured according to the RLC configuration information.
  • the terminal configures the WLAN entity and configures or reconfigures the WLAN entity according to the WLAN entity configuration information.
  • the terminal when reconfiguring / modifying / changing an E-UTRAN bearer configured in a terminal through an RRC connection reconfiguration message to a WLAN bearer, the terminal may perform the following operation.
  • the PDCP entity is reconfigured according to the PDCP configuration information.
  • the terminal may perform the following operation.
  • PDCP does not trigger retransmission for uplink PDCP data (eg, PDUs or SDUs). Or PDCP does not trigger retransmission for PDCU PDUs submitted by the PDCP to the RLC entity.
  • uplink PDCP data eg, PDUs or SDUs.
  • PDCP does not trigger retransmission for PDCU PDUs submitted by the PDCP to the RLC entity.
  • the RLC entity or WLAN entity completes the transmission or retransmission of all pending RLC SDUs or RLC PDUs.
  • the RLC entity or WLAN entity may complete the transmission or retransmission of all pending RLC SDUs or RLC PDUs on the WLAN carrier.
  • the RLC entity or WLAN entity may complete the transmission or retransmission of all pending PDCP PDUs on the WLAN carrier.
  • the RLC entity or WLAN entity performs transmission or retransmission for PDCP PDUs received from PDCP entity prior to bearer reconfiguration / modification / change.
  • the RLC entity or WLAN entity performs transmission or retransmission for RLC SDUs or RLC PUDs received from the PDCP entity prior to bearer reconfiguration / modification / change.
  • RLC entity or WLAN entity performs transmission or retransmission for PDCP PDUs submitted by PDCP entity before bearer reconfiguration / modification / change.
  • WLAN Bearer ⁇ Reconfigure / Modify / Change WLAN Bearer
  • the WLAN bearer can be changed to another WLAN AP / Network / SSID / BSSID / HESSID / through a specific WLAN AP / Network / SSID / BSSID / HESSID / Domain Name List.
  • a specific WLAN AP / Network / SSID / BSSID / HESSID / Domain Name List There may be a case in which it is necessary to reconfigure / modify / change the WLAN bearer through the Domain Name List. In this case, data transferred from the PDCP entity to the corresponding WLAN entity may be lost due to a change of WLAN AP / network / SSID / BSSID / HESSID / Domain Name List.
  • Radio Link Control For radio bearers mapped to AM Acknowledgment mode Radio Link Control (RLC), lossless data transmission should be ensured even when a WLAN bearer configured in a terminal is reconfigured / modified / modified into a WLAN bearer through an RRC connection reconfiguration message.
  • RLC Radio Link Control
  • the terminal may perform the following operations.
  • the terminal resets the PDCP entity.
  • the WLAN entity may perform one or more of the following operations.
  • the UE transmits or retransmits PDCP SDUs whose successful transmission is not confirmed according to the PDCP resetting for the data lost during the bearer change process, thereby performing lossless transmission.
  • this method must handle complex detailed operations such as header compression protocol reset and security key change, PDCP SDUs transmission or retransmission even for bearer change without change of PDCP entity, which can increase complexity and delay. have.
  • the PDCP data recovery operation may be performed while maintaining the PDCP entity reconfiguration or PDCP entity without the PDCP reset described above.
  • the terminal when reconfiguring / modifying / changing a WLAN bearer configured in a terminal through an RRC connection reconfiguration message, the terminal may perform the following operation.
  • the terminal performs a PDCP data recovery procedure previously submitted to the WLAN entity.
  • the WLAN entity may perform one or more of the following operations.
  • the PDCP data recovery procedure retransmits all PDCP PDUs previously submitted to the reset AM RLC entity. Therefore, when changing a WLAN bearer into a WLAN bearer, it is necessary to perform retransmission over the new WLAN network for PDCP PDUs submitted to the previous WLAN network before receiving the bearer change message (or before performing PDCP data recovery).
  • the radio bearer is configured to send a PDCP status report by the upper layer in the uplink, generate a PDCP status report and submit it to the first PDCP PDU for transmission to the lower layer.
  • the base station When PDCP data recovery for uplink is performed in the terminal, the base station should perform a reordering function for the corresponding PDCP data. When PDCP data recovery for downlink is performed at the base station, the terminal should perform a reordering function for the corresponding PDCP data.
  • PDCP data recovery can be performed when a bearer change occurs for a split split bearer in Rel-12 dual connectivity (e.g., when a split bearer changes to a split bearer without a PDCP reset or when a split bearer becomes a MCG without a PDCP reset). Only when changed to bearer).
  • the reordering function was performed when the split bearer is configured in the terminal.
  • the UE has a reordering function when the PDCP entity is associated with two AM RLC entities in a dual connectivity situation.
  • the reordering function was performed when the split bearer changed to the split bearer without PDCP resetting.
  • the PDCP entity is associated with one AM RLC entity after it was, according to the most recent reconfiguration, associated with two AM RLC entities without performing PDCP re reordering function was used.
  • the PDCP immediately started the reordering function upon receiving the dual connectivity split bearer configuration message, and applied a reordering method such as RLC UM through the set reordering timer (t-Reordering-r12). That is, all stored PDCP SDU (s) is transferred to the upper layer for reordering.
  • the base station may instruct the terminal by including information (or information for indicating this) to configure the reordering timer for this in the RRC message.
  • the base station may perform a reordering function for this.
  • the downlink data reception procedure provided by the PDCP may be used.
  • the PDCP PDU received by PDCP is immediately forwarded to the higher layer. That is, when the above-described reordering function is not used, since RLC guarantees in-sequence delivery, the PDCP can be delivered directly to a higher layer without reordering.
  • the terminal may improve the downlink data reception procedure provided by the conventional PDCP when the reordering function is not used. You may want to reorder.
  • Last_Submitted_PDCP_RX_SN to the PDCP SN of the last PDCP SDU delivered to upper layers
  • the PDCP SDU or PDCP PDU received by PDCP is due to a WLAN bearer change in the WLAN bearer (or due to the release of a WLAN entity or due to a specific operation of the WLAN entity), then reordering: You can do
  • Last_Submitted_PDCP_RX_SN to the PDCP SN of the last PDCP SDU delivered to upper layers
  • a terminal and a base station transmit and receive data through a specific radio bearer
  • it is performed without PDCP resetting to provide an effect of suppressing unnecessary delay and data retransmission.
  • lossless data transmission and reception are possible when reconfiguring a specific radio bearer.
  • a terminal and a base station apparatus capable of performing all the above-described operations of the present invention will be briefly described again with reference to the drawings.
  • FIG. 7 is a view for explaining a terminal configuration according to another embodiment of the present invention.
  • a terminal 700 reconfiguring a radio bearer may change a data radio bearer type for a specific radio bearer configured to receive downlink data using only a wireless local area network (WLAN) radio resource from a base station.
  • the PDCP data recovery procedure is performed in the PDCP entity based on the receiver 730 that receives higher layer signaling including the information and the information for changing the data radio bearer type for the specific radio bearer.
  • the controller 710 performs a reordering procedure for the specific radio bearer in the entity.
  • the receiver 730 may receive an RRC connection reconfiguration message from the base station including information for changing the data radio bearer type.
  • Information for changing the data radio bearer type for a specific radio bearer is from a radio bearer type for receiving downlink data using only WLAN radio resources to a radio bearer type for receiving downlink data using only base station radio resources. It may contain information to change. or,
  • the receiver 730 may receive higher layer signaling including information for changing a data radio bearer type for a specific radio bearer configured to receive downlink data using only base station radio resources.
  • information for changing the data radio bearer type for a specific radio bearer is downlinked using only a wireless local area network (WLAN) radio resource in a radio bearer type that receives downlink data using a base station radio resource only. It may also include information for changing to a radio bearer type for receiving link data.
  • WLAN wireless local area network
  • the receiver 730 may further receive information for configuring a reordering timer used to perform a reordering procedure in a PDCP entity, and may receive information for configuring a timer through higher layer signaling. have.
  • the controller 710 may transfer all PDCP SDUs stored for reordering to an upper layer in ascending order of the associated COUNT value when the reordering timer expires.
  • the controller 710 may generate a PDCP status report and include the PDCP status report in a PDCP PDU (PDCP Protocol Data Unit) to deliver it to a lower layer.
  • PDCP PDU PDCP Protocol Data Unit
  • controller 710 performs both the above-described PDCP data recovery procedure and reordering procedure when reconfiguring the WLAN bearer into the E-UTRAN bearer, and the above-described PDCP data when reconfiguring the E-UTRAN bearer into the WLAN bearer. It is also possible to perform only a reordering procedure without a recovery procedure.
  • the receiver 730 receives downlink control information, data, and a message from a base station through a corresponding channel.
  • the controller 710 controls the overall operation of the terminal according to the configuration / reconfiguration for the base station to add / modify / release / change the terminal and the radio bearer by the base station required to perform the present invention described above.
  • the transmitter 720 transmits uplink control information, data, and a message to a base station through a corresponding channel.
  • FIG. 8 is a view for explaining the configuration of a base station according to another embodiment of the present invention.
  • the base station 800 transmits higher layer signaling including information for changing data radio bearer type for a specific radio bearer configured to receive downlink data using only WLAN radio resources.
  • PDCP Protocol Data Unit PDCP PDU
  • PDCP SDU PDCP SDU
  • PDCP status report that receive a PDCP (Packet Data Convergence Protocol) status report from the terminal
  • a control unit 810 for retransmitting the data unit.
  • the transmitter 820 includes information for changing a data radio bearer type for a specific radio bearer.
  • the information for changing the data radio bearer type for a specific radio bearer is a radio bearer that receives downlink data using only base station radio resources in a radio bearer type that receives downlink data using a WLAN radio resource only. It may include information for changing to a type.
  • the information for changing the data radio bearer type for a specific radio bearer is a radio bearer that receives downlink data using only WLAN radio resources in a radio bearer type that receives downlink data using a base station radio resource only. It may include information for changing to a type.
  • the transmitter 820 may transmit information for configuring a reordering timer used for the terminal to perform the reordering procedure to the terminal.
  • information for configuring the reordering timer may be transmitted through higher layer signaling (eg, an RRC message).
  • control unit 810 controls the overall operation of the base station according to the configuration / reconfiguration for the base station to add / modify / release / change the terminal and the radio bearer by the base station required to perform the present invention described above .
  • the transmitter 820 and the receiver 830 are used to transmit and receive signals, messages, and data necessary for carrying out the present invention.

Landscapes

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

Abstract

La présente invention a trait à une technologie par laquelle une station de base transmet, au niveau d'un réseau d'accès radio (RAN), des données de plan d'utilisateur en ajoutant une connexion de réseau local sans fil (WLAN) à un terminal dans lequel une connexion sans fil est établie. En particulier, la présente invention a trait à un procédé et à un dispositif pour configurer ou reconfigurer un support de données sans fil pour la transmission de données de plan d'utilisateur. Spécifiquement, la présente invention concerne un procédé et un dispositif, et le procédé par lequel un terminal reconfigure un support sans fil comprend les étapes suivantes : réception, depuis une station de base, d'une signalisation de couche supérieure incluant des informations pour changer un type de support sans fil de données pour un support sans fil spécifique configuré pour recevoir des données en liaison descendante à l'aide d'une seule ressource sans fil de WLAN ; exécution d'une procédure de récupération de données de protocole PDCP (protocole de convergence de données de paquets) dans une entité de protocole PDCP sur la base des informations pour changer le type de support sans fil de données pour le support sans fil spécifique ; et exécution d'une procédure de réorganisation pour le support sans fil spécifique dans l'entité de protocole PDCP.
PCT/KR2016/003203 2015-04-02 2016-03-29 Procédé de reconfiguration d'un support sans fil et dispositif associé Ceased WO2016159634A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US15/562,463 US10485042B2 (en) 2015-04-02 2016-03-29 Method for reconfiguring wireless bearer and device thereof
CN201680007805.6A CN107211475B (zh) 2015-04-02 2016-03-29 用于重新配置无线承载的方法及其装置

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
KR10-2015-0046974 2015-04-02
KR20150046974 2015-04-02
KR1020160037352A KR101870022B1 (ko) 2015-04-02 2016-03-29 무선 베어러 재구성 방법 및 그 장치
KR10-2016-0037352 2016-03-29

Publications (1)

Publication Number Publication Date
WO2016159634A1 true WO2016159634A1 (fr) 2016-10-06

Family

ID=57006102

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2016/003203 Ceased WO2016159634A1 (fr) 2015-04-02 2016-03-29 Procédé de reconfiguration d'un support sans fil et dispositif associé

Country Status (1)

Country Link
WO (1) WO2016159634A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018171300A1 (fr) * 2017-03-21 2018-09-27 中兴通讯股份有限公司 Procédé et appareil pour déterminer un mode de support radio
WO2019051775A1 (fr) * 2017-09-15 2019-03-21 Oppo广东移动通信有限公司 Procédé et dispositif de changement de type de support, et support de stockage informatique
WO2020009414A1 (fr) * 2018-07-02 2020-01-09 삼성전자 주식회사 Procédé et dispositif de communication dans un système de communication mobile
EP3585087A4 (fr) * 2017-03-13 2020-04-15 Huawei Technologies Co., Ltd. Procédé de traitement de données, dispositif terminal, et station de base
US11336755B2 (en) 2019-07-08 2022-05-17 Mediatek Singapore Pte. Ltd. PDCP layer active protocol stack implementation to reduce handover interruption

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014113686A2 (fr) * 2013-01-17 2014-07-24 Interdigital Patent Holdings, Inc. Placement de protocole de convergence de paquet de données (pdcp)
WO2015020508A1 (fr) * 2013-08-09 2015-02-12 주식회사 팬택 Procédé et appareil de réorganisation de pdcp tout en prenant en considération de multiples flux dans un système à double connectivité

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014113686A2 (fr) * 2013-01-17 2014-07-24 Interdigital Patent Holdings, Inc. Placement de protocole de convergence de paquet de données (pdcp)
WO2015020508A1 (fr) * 2013-08-09 2015-02-12 주식회사 팬택 Procédé et appareil de réorganisation de pdcp tout en prenant en considération de multiples flux dans un système à double connectivité

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
NEC: "Introduction of Dual Connectivity", R2-145424, 3GPP TSG-RAN WG2 MEETING #88, 26 November 2014 (2014-11-26), San Francisco, USA, XP050920822 *
NOKIA NETWORKS ET AL.: "Reconfiguration Cases with Two Bearers", R2-144870, 3GPP TSG-RAN WG2 MEETING #88, 7 November 2014 (2014-11-07), San Francisco, USA, XP050877056 *
NVIDIA: "RRC and PDCP/RLC Interactions For Dual Connectivity", R2-145227, 3GPP TSG-RAN WG2 MEETING #88, 8 November 2014 (2014-11-08), San Francisco, USA, XP050877304 *

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3585087A4 (fr) * 2017-03-13 2020-04-15 Huawei Technologies Co., Ltd. Procédé de traitement de données, dispositif terminal, et station de base
US11096184B2 (en) 2017-03-13 2021-08-17 Huawei Technologies Co., Ltd. Data processing method, terminal device, and base station
US11924870B2 (en) 2017-03-13 2024-03-05 Huawei Technologies Co., Ltd. Data processing method, terminal device, and base station using RLC sequence numbers
WO2018171300A1 (fr) * 2017-03-21 2018-09-27 中兴通讯股份有限公司 Procédé et appareil pour déterminer un mode de support radio
CN108924947A (zh) * 2017-03-21 2018-11-30 中兴通讯股份有限公司 一种确定无线承载方式的方法及装置
JP2020511853A (ja) * 2017-03-21 2020-04-16 中興通訊股▲ふん▼有限公司Ｚｔｅ Ｃｏｒｐｏｒａｔｉｏｎ 無線ベアラ方式を決定する方法および装置
WO2019051775A1 (fr) * 2017-09-15 2019-03-21 Oppo广东移动通信有限公司 Procédé et dispositif de changement de type de support, et support de stockage informatique
WO2020009414A1 (fr) * 2018-07-02 2020-01-09 삼성전자 주식회사 Procédé et dispositif de communication dans un système de communication mobile
US11337125B2 (en) 2018-07-02 2022-05-17 Samsung Electronics Co., Ltd. Communication method and device in mobile communication system
US12452752B2 (en) 2018-07-02 2025-10-21 Samsung Electronics Co., Ltd. Communication method and device in mobile communication system
US11336755B2 (en) 2019-07-08 2022-05-17 Mediatek Singapore Pte. Ltd. PDCP layer active protocol stack implementation to reduce handover interruption
TWI770549B (zh) * 2019-07-08 2022-07-11 新加坡商聯發科技（新加坡）私人有限公司 減少行動中斷之方法和使用者設備

Similar Documents

Publication Publication Date Title
WO2019160342A1 (fr) Procédé et appareil prenant en charge une mobilité sans rach utilisant des faisceaux préalablement attribués dans un système de communication sans fil
WO2021066511A1 (fr) Coordination de capacité pour mobilité avec daps
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
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
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
WO2019031883A1 (fr) Procédé et dispositif de rétablissement d'un pdcp dans un système de communication sans fil
WO2015064972A1 (fr) Procédé et appareil de configuration de connexion double dans un réseau de communication mobile
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
WO2020027491A1 (fr) Procédé de traitement de données dans un nœud relais, et dispositif associé
WO2018079947A1 (fr) Procédé de prise en charge de mobilité d'équipement utilisateur dans un système de communication sans fil et dispositif associé
WO2016148357A1 (fr) Procédé et appareil de transmission/réception de données pour terminal dans un système de communication sans fil
WO2018004278A1 (fr) Procédé et dispositif pour transmettre ou recevoir des données dans un état de double connectivité
WO2017010589A1 (fr) Procédé et appareil de transmission et de réception de données, par un terminal, dans un système de communication sans fil
WO2019212249A1 (fr) Procédé de traitement de données via un nœud relais, et appareil associé
WO2017138769A1 (fr) Procédé de mise à jour d'emplacement de terminal dans un système de communication sans fil et appareil de prise en charge associé
WO2018164499A1 (fr) Procédé de transmission de rapport d'état de tampon, et dispositif associé
WO2022086233A1 (fr) Procédé et dispositif de transmission de multidiffusion
WO2018169242A1 (fr) Procédé de réception d'un message de commande en double, et dispositif associé
WO2016159634A1 (fr) Procédé de reconfiguration d'un support sans fil et dispositif associé
WO2017138768A1 (fr) Procédé d'émission/réception de données dans un système de communication sans fil et dispositif de prise en charge de ce dernier
WO2019059638A1 (fr) Procédé de traitement de données au moyen d'un noeud de relais et appareil associé
WO2015152554A1 (fr) Procédé de commande de fonctionnement de cellule secondaire d'un terminal, et appareil associé
WO2015046780A1 (fr) Procédé de transmission de données de liaison montante, et appareil correspondant

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 15562463

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 08/12/2017)

122 Ep: pct application non-entry in european phase

Ref document number: 16773415

Country of ref document: EP

Kind code of ref document: A1