WO2013155709A1 - Procédé de configuration pour diffusion de données en flux, système de station de base et équipement d'utilisateur - Google Patents

Procédé de configuration pour diffusion de données en flux, système de station de base et équipement d'utilisateur Download PDF

Info

Publication number
WO2013155709A1
WO2013155709A1 PCT/CN2012/074459 CN2012074459W WO2013155709A1 WO 2013155709 A1 WO2013155709 A1 WO 2013155709A1 CN 2012074459 W CN2012074459 W CN 2012074459W WO 2013155709 A1 WO2013155709 A1 WO 2013155709A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
base station
secondary base
entity
rlc
Prior art date
Application number
PCT/CN2012/074459
Other languages
English (en)
Chinese (zh)
Inventor
黄曲芳
曾清海
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2012/074459 priority Critical patent/WO2013155709A1/fr
Priority to CN201280072392.1A priority patent/CN104247547B/zh
Priority to CN201810254570.1A priority patent/CN108337633B/zh
Priority to PCT/CN2012/085977 priority patent/WO2013155846A1/fr
Publication of WO2013155709A1 publication Critical patent/WO2013155709A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/18—Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/20—Interfaces between hierarchically similar devices between access points

Definitions

  • the present invention relates to the field of communications, and in particular, to a data offload configuration method, a base station system, and a user terminal.
  • Carrier carrier aggregation
  • UE User Equipment
  • CCs Component Carriers
  • the carrier aggregation of the Long Term Evolution (LTE) system can be roughly divided into intra-base station cell aggregation, inter-base station cell aggregation, and the like.
  • data can be transmitted via multiple cells.
  • data offloading can be divided into two categories: one is based on radio bearer (RB) data splitting, and the other is packet based data shunting.
  • RB-based data offloading refers to traffic splitting.
  • Packet-based data offloading scheme is based on real-time air interface conditions. Which base station the fixed data is transmitted through, so that the two communicating parties can select a suitable base station for transmission according to the quality of the air interface and the degree of congestion.
  • a technical problem to be solved by the embodiments of the present invention is to provide a data offload configuration method, a base station system, and a user terminal, to implement dynamic offloading.
  • a data offload configuration method includes:
  • the primary base station sends a first message to the secondary base station, where the first message is used to request data splitting from the secondary base station, where the first message includes an identifier of the radio bearer RB and a Qos parameter of the service quality requirement of the RB. So that the secondary base station determines the to-be-split RB and sets configuration parameters for the to-be-split RB;
  • the primary base station receives a second message from the secondary base station, where the second message includes configuration parameters of the to-be-split RB;
  • the primary base station sends a third message to the user terminal UE, where the third message includes the identifier of the to-be-offered RB and the configuration parameter of the to-be-offered RB, so that the UE establishes the Two PDCP entities and a second RLC entity are configured for data offloading;
  • the UE has a first PDCP entity, a first RLC entity, and a MAC real
  • the second PDCP entity and the second RLC entity are located between the first RLC entity and the MAC entity.
  • a downlink data transmission method includes:
  • the PDCP entity of the primary base station receives the data from the serving gateway SGW, and processes the data to form the first data.
  • the data offload type of the method is a partial offload, and the partial offload refers to the data part of an RB. Transmitted via the secondary base station, partially transmitted via the primary base station;
  • the RLC entity of the primary base station adds a first RLC sequence number to the first data, forms second data, and sends the data to be offloaded in the second data to the PDCP entity of the secondary base station; the PDCP entity of the secondary base station Transmitting the to-be-split data to an RLC entity of the secondary base station;
  • the secondary base station processes the to-be-divided data, and sends the processed to-be-split data to the UE.
  • a downlink data transmission method includes:
  • the PDCP entity of the primary base station receives the data from the serving gateway SGW, and processes the data to form the first data.
  • the data offload type of the method is complete offloading, and the complete offload refers to all data of one RB. Transmitting via a secondary base station;
  • the RLC entity of the primary base station receives the first data, and sends the first data to a PDCP entity of the secondary base station;
  • the PDCP entity of the secondary base station receives the first data from the primary base station, and sends the first data to an RLC entity of the secondary base station;
  • the secondary base station processes the first data, and sends the processed first data to the UE.
  • An uplink data transmission method includes:
  • the UE reports the BSR to the primary base station and/or the secondary base station, so that the primary base station and/or the secondary base station allocates uplink transmission resources to the UE;
  • the first PDCP entity of the UE processes the received data to form the first data;
  • the first RLC entity of the UE segments the first data into segments, adds the first RLC sequence number, and forms the second data.
  • the second RLC entity of the UE adds the second RLC sequence number to the received data to be offloaded to form third data, and sends the third data to the MAC entity of the UE; the physical layer of the UE will process The subsequent third data is sent to the secondary base station.
  • An uplink data transmission method includes:
  • the UE reports the BSR to the primary base station and/or the secondary base station, so that the primary base station and/or the secondary base station allocates uplink transmission resources for the U E;
  • the first PDCP entity of the UE processes the received data to form first data; the first RLC entity of the UE adds a first RLC sequence number to the first data, forms a second data, and the foregoing The second PDCP entity to be offloaded to the UE in the second data;
  • the second RLC entity of the UE adds the second RLC sequence number to form the third data according to the received uplink transmission resource allocated by the secondary base station, and then adds the second RLC sequence to form the third data.
  • Three data are sent to the MAC entity of the UE;
  • a base station comprising:
  • the service quality requires a Qos parameter, so that the secondary base station determines the to-be-offered RB and sets configuration parameters for the to-be-split RB;
  • the third message includes the identifier of the to-be-offered RB and the configuration parameter of the to-be-offered RB, so that the UE establishes a second PDCP entity for the to-be-split RB and a second RLC entity and performing data offload configuration;
  • a receiver configured to receive a second message from the secondary base station, where the second message includes configuration parameters of the to-be-split RB;
  • the UE has a first PDCP entity, a first RLC entity, and a MAC entity, and the second PDCP entity and the second RLC entity are located between the first RLC entity and the MAC entity.
  • a base station system includes a primary base station and a secondary base station, where the primary base station includes a PDCP entity and an RLC entity, and the secondary base station includes a PDCP entity and an RLC entity.
  • the PDCP entity of the primary base station is configured to receive data from the serving gateway SGW, and process the data to form first data, where the data transmission method is partially offloaded;
  • the RLC entity of the primary base station is configured to add a first RLC sequence number to the first data, form second data, and send the data to be offloaded in the second data to a PDCP entity of the secondary base station;
  • the PDCP entity of the secondary base station is configured to send the to-be-split data to an RLC entity of the secondary base station;
  • the secondary base station is configured to process the to-be-divided data, and send the processed to-be-split data to the UE.
  • a base station system includes a primary base station and a secondary base station, where the primary base station includes a PDCP entity and an RLC entity, and the secondary base station includes a PDCP entity and an RLC entity.
  • the PDCP entity of the primary base station is configured to receive data from the serving gateway SGW, and process the data to form first data, where the data transmission method is completed. Fully diverted;
  • the RLC entity of the primary base station is configured to receive the first data, and send the first data to a PDCP entity of the secondary base station;
  • the PDCP entity of the secondary base station is configured to receive the first data from the primary base station, and send the first data to an RLC entity of the secondary base station;
  • the secondary base station processes the first data, and sends the processed first data to the UE.
  • a user terminal including a first PDCP entity, a first RLC entity, a MAC entity, and a physical layer, further comprising: a 881 upper unit, a second PDCP entity, and a second RLC entity, the second PDCP entity and the second The RLC entity is located between the first RLC entity of the UE and the MAC,
  • the BSR reporting unit is configured to report a BSR to the primary base station and/or the secondary base station, so that the primary base station and/or the secondary base station allocate uplink transmission resources to the UE;
  • the first PDCP entity is configured to process the received data to form a first data
  • the first RLC entity is configured to perform segmentation concatenation of the first data, add a first RLC sequence number, form second data, and perform the foregoing according to the received uplink transmission resource allocated by the secondary base station.
  • the data to be offloaded in the second data is sent to the second PDCP entity; the second PDCP entity is configured to send the offloaded data to the second RLC entity of the UE;
  • the second RLC entity is configured to add the second RLC sequence number to the received data to be offloaded, form third data, and send the third data to the MAC entity of the UE;
  • the physical layer of the UE is configured to send the processed third data to the secondary base station.
  • a user terminal including a first PDCP entity, a first RLC entity, a MAC entity, and a physical layer, further includes: a 881 upper unit, a second PDCP entity, and a second RLC entity.
  • the second PDCP entity and the second RLC entity are located between the first RLC entity of the UE and the MAC,
  • the BSR reporting unit is configured to report a BSR to the primary base station and/or the secondary base station, so that the primary base station and/or the secondary base station allocate uplink transmission resources to the UE;
  • the first PDCP entity is configured to process the received data to form a first data
  • the first RLC entity is configured to add a first RLC sequence number to the first data, to form a second data, and send the to-be-split data in the second data to a second PDCP entity of the UE;
  • the second PDCP entity is configured to send the to-be-split data to a second RLC entity of the UE;
  • the second RLC entity is configured to add the second RLC sequence number to form a third data according to the received uplink transmission resource allocated by the secondary base station, and then add the second RLC sequence number to form the third data. Transmitting third data to a MAC entity of the UE;
  • the physical layer of the UE is configured to send the processed third data to the secondary base station.
  • the data offloading configuration method, the base station system, and the user terminal of the embodiment of the present invention change the prior art by setting a second PDCP entity and a second RLC entity between the first RLC entity of the UE and the MAC entity.
  • the processing flow of the split data has a faster response to the changes in the air interface measured at the bottom layer, and the dynamic shunting effect is better.
  • FIG. 1 is a schematic flowchart of a data offloading configuration method according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of signaling interaction of a data offloading configuration method according to an embodiment of the present invention
  • 3 is a schematic structural diagram of a protocol stack in an embodiment of the present invention
  • FIG. 4 is a schematic diagram of a front-back comparison of data offload configuration in an embodiment of the present invention.
  • FIG. 5 is a schematic flowchart of a downlink data transmission method according to an embodiment of the present invention.
  • FIG. 6 is a schematic diagram of a downlink data transmission process according to an embodiment of the present invention.
  • FIG. 7 is a second schematic diagram of a downlink data transmission process according to an embodiment of the present invention.
  • FIG. 8 is a schematic flowchart of a method for transmitting a downlink data according to an embodiment of the present invention
  • FIG. 9 is a schematic flowchart of an uplink data transmission method according to an embodiment of the present invention
  • FIG. 10 is a schematic diagram of an uplink data transmission process according to an embodiment of the present invention
  • FIG. 1 is a schematic diagram of a UE in an uplink data transmission process according to an embodiment of the present invention
  • FIG. 12 is a schematic flowchart of a method for transmitting an uplink data according to an embodiment of the present invention
  • FIG. 13 is a schematic structural diagram of a base station according to an embodiment of the present invention
  • FIG. 14 is a schematic structural diagram of a base station system according to an embodiment of the present invention.
  • FIG. 15 is a schematic structural diagram of a user terminal according to an embodiment of the present invention.
  • the embodiment of the invention provides a data offloading configuration method, a base station system and a user terminal, which have a quick response to the change of the air interface condition, and the dynamic shunting effect is good.
  • GSM Global System for Mobile Communications
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access Wireless
  • OFDMA Frequency Division Multiple Addressing
  • OFDMA Orthogonal Frequency-Division Multiple Access
  • SC-FDMA General Packet Radio Service
  • LTE Long Term Evolution
  • the user terminal which may be a wireless terminal or a wired terminal, may be a device that provides voice and/or data connectivity to the user, a handheld device with wireless connectivity, or other processing device connected to the wireless modem.
  • the wireless terminal can communicate with one or more core networks via a Radio Access Network (RAN), which can be a mobile terminal, such as a mobile phone (or "cellular" phone) and a mobile terminal.
  • RAN Radio Access Network
  • the computer for example, can be a portable, pocket, handheld, computer built-in or in-vehicle mobile device that exchanges language and/or data with the wireless access network.
  • PCS Personal Communication Service
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • a wireless terminal may also be called a system, a Subscriber Unit, a Subscriber Station, a Mobile Station, a Mobile, a Remote Station, an Access Point, Remote Terminal, Access Terminal, User Terminal, User Agent, User Device, or User Equipment.
  • a base station can refer to a device in an access network that communicates with a wireless terminal over one or more sectors over an air interface.
  • the base station can be used to exchange received air frames and IP packets with each other.
  • IP Internet Protocol
  • the base station can also coordinate attribute management of the air interface.
  • the base station may be a Base Transceiver Station (BTS) in GSM or CDMA, or may be a base station (NodeB) in WCDMA, or may be an evolved base station in LTE (NodeB or eNB or e-NodeB, evolutional Node B), the invention is not limited.
  • the base station controller may be a base station controller (BSC) in GSM or CDMA, or may be a radio network controller (RNC) in WCDMA, which is not limited in the present invention.
  • BSC base station controller
  • RNC radio network controller
  • system and “network” are often used interchangeably herein.
  • the term “and/or” is merely an association that describes an associated object, indicating that there may be three relationships.
  • ⁇ and / or ⁇ can mean: There are three cases of A, B and A, and B.
  • the character ",” in this paper, means that the context is an "or”. relationship.
  • the data part that is partially offloaded into one RB is transmitted via the secondary base station, and the part is transmitted via the primary base station; the data that is completely offloaded to one RB is all transmitted via the secondary base station.
  • This embodiment provides a data offload configuration method. As shown in FIG. 1 and FIG. 2, the method includes:
  • Step 101 The primary base station sends a first message to the secondary base station, where the first message is used to request data splitting from the secondary base station, where the first message includes an identifier of the radio bearer RB and a service quality requirement of the RB.
  • the Qos parameter is configured to enable the secondary base station to determine a to-be-split RB and set configuration parameters for the to-be-split RB.
  • the primary evolved NodeB refers to the serving base station of the UE
  • the secondary evolved NodeB refers to the carrier aggregation of the UE and performs data offloading.
  • Base station In the architecture of this embodiment, the RAN side is connected to the SGW through the primary base station.
  • the primary base station Before data offloading, first start the process of data offload configuration. After the primary base station decides to start data offloading, the primary base station sends the first message to the secondary base station through the X2 interface.
  • the first message may be a data offload request message, where the first message includes each
  • each RB identifier and the Qos parameter corresponding to each RB may be presented in the form of a list containing the offloaded RB, or may be presented in the form of an array.
  • the Qos parameter may include any one of the following or any combination thereof: RB priority, whether it can be preempted, uplink maximum bit rate, uplink guaranteed bit rate, downlink maximum bit rate, downlink guaranteed bit rate, maximum allowable delay, and the like.
  • the secondary base station After receiving the data offloading request message, the secondary base station sets configuration parameters for each RB to be offloaded according to the RB list, where the configuration parameter may include any one of the following or any combination thereof: Packet Data Convergence Protocol, abbreviated as PDCP) entity, Radio Link Control (RLC) entity, medium access control (MAC) entity, and physical layer (Phy).
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC medium access control
  • Physical layer Physical layer
  • the secondary base station determines, according to its own load condition, which RBs are allowed to access, to determine which RBs need to be configured with configuration parameters, and after determining the RB to be offloaded, according to the The RB establishes a PDCP entity and an RLC entity for each RB to be offloaded according to the Qos parameter, and sets configuration parameters.
  • PDCP is a wireless transmission protocol stack in UMTS or LTE. It is usually responsible for compressing and decompressing IP headers, encrypting and decrypting data packets, transmitting user data, and maintaining a sequence of radio bearers set up for the Lossless Wireless Network Service Subsystem (SRNS). number. If the PDCP is configured as "no compression, no encryption and decryption", the PDCP entity will transparently process the data packet, that is, it will not process it.
  • the RLC entity is located above the MAC entity and provides segmentation and retransmission services for user data.
  • the first message further includes: a traffic distribution type identifier, configured to indicate that the data offload transmission is a full offload or a partial offload.
  • a traffic distribution type identifier configured to indicate that the data offload transmission is a full offload or a partial offload.
  • the configuration parameter can be used to know whether the data on a certain RB is completely offloaded or partially offloaded.
  • the secondary base station After the secondary base station sets the configuration parameters for each RB to be offloaded, the secondary base station sends a second message to the primary base station.
  • the second message may be a data offload response message, where the data offload response message includes the to be offloaded. Configuration parameters for each RB.
  • the primary base station receives the data offload response message.
  • the parameters of the PDCP entity include: The length of the discard Timer used by the secondary base station.
  • the parameters of the RLC entity may include any one of the following or any combination thereof:
  • - RLC mode of RB AM or UM
  • the RLC status report used by the RB receiver disables the timer length
  • the parameters of the MAC entity may include any one of the following or any combination thereof:
  • BSR buffer status report
  • the parameters of the physical layer may include any one of the following or any combination thereof:
  • the above three parameters include period and offset in the time domain, and include frequency point information in the frequency domain;
  • the UE generates a relevant parameter in the preamble sequence used in the secondary base station cell
  • Step 103 The primary base station sends a third message to the user terminal UE, where the third message includes the identifier of the to-be-offloaded RB and the configuration parameter of the to-be-offered RB, so that the UE is the to-be-divided
  • the RB establishes a second packet data convergence protocol PDCP entity and a second radio link control layer protocol RLC entity and performs data offload configuration.
  • the primary base station sends a third message to the UE.
  • the third message may be a data offload configuration message, where the data offload configuration message includes an RB identifier and a configuration parameter of the to be offloaded RB, and after receiving the data offload configuration message, the UE receives the data offload configuration message.
  • the RB identifier and the configuration parameter of the to-be-offered RB, the second PDCP entity and the second RLC entity are established for the to-be-split RB, where the UE has the first PDCP entity, the first RLC entity, and the MAC The entity, the second PDCP entity and the second RLC entity are located between the first RLC entity and the MAC entity of the UE, as shown in FIG.
  • the third message may also include: a shunt class A type identifier is used to indicate that the data is split into a full split or a partial split.
  • the second PDCP entity of the UE logically corresponds to the PDCP entity of the secondary base station
  • the second RLC entity of the UE logically corresponds to the RLC entity of the secondary base station
  • the first PDCP entity of the UE corresponds to the PDCP entity of the primary base station
  • the first RLC entity of the UE corresponds to the RLC entity of the primary base station.
  • the "correspondence" here is a logical relationship. Since the data is in the process of transmission, the primary base station and the secondary base station perform operations on the data, and the UE needs to perform corresponding inverse operations when receiving data, therefore, as shown in the figure As shown in Figure 3, from the perspective of the protocol stack structure, the two sides are logically equivalent.
  • the UE sends a data offload configuration response message to the primary base station to notify the primary base station that the establishment of the second PDCP entity and the second RLC entity is complete. , As shown in Figure 4.
  • the primary base station receives the data offload configuration response message sent by the UE.
  • the process of processing the data to be offloaded in the prior art is changed by setting the second PDCP entity and the second RLC entity between the first RLC entity and the MAC entity of the UE, and the protocol modification is small, and The response to the change of the air interface measured at the bottom layer is faster, and the effect of dynamic shunting is better.
  • the secondary base station after the primary base station sends the data offload request message to the secondary base station, the secondary base station further determines whether a cell has been established for the UE:
  • the secondary base station has established a cell for the UE, set a PDCP entity and an RLC entity for each RB in the list according to the Qos parameter, and set configuration parameters;
  • the secondary base station If the secondary base station does not establish a cell for the UE, the secondary base station establishes a cell for the UE to carry the RB, and the secondary base station establishes a PDCP entity and an RLC entity for each RB, and also establishes between the cell and the UE.
  • Hybrid Automatic Repeat Request (HARQ) entity Generally, eight HARQ entities need to be established in each cell to correspond to one UE.
  • the data offload response message further includes: a preamble coding of the UE (a reamble), the preamble is allocated by the secondary base station after determining that the UE does not establish a connection and/or a synchronous connection with the secondary base station, and is configured to receive, by the primary base station, a data offload configuration sent by the UE.
  • the UE uses the preamble to initiate random access to a specific cell in the secondary base station to access the secondary base station.
  • the preamble may be allocated by a cell served by the secondary base station.
  • the data offload configuration message further includes a correspondence between the reamble and the reamble and the cell, so that the UE knows the preamble.
  • the data offload response message further includes: a BSR threshold, where the BSR threshold is allocated by the secondary base station, and is used by the UE to report a BSR, where the BSR is used by the primary base station and/or the secondary base station The UE allocates an uplink transmission resource.
  • the data offload configuration message further includes the BSR threshold, so that the UE knows the BSR threshold.
  • the method further includes: when the downlink data in the buffer of the secondary base station is lower than a buffer threshold set by the secondary base station, the primary base station receives the auxiliary Base station data request; or,
  • the primary base station sends data to the secondary base station according to the buffering situation of the secondary base station periodically reported by the secondary base station.
  • the secondary base station After the primary base station sends the data offload request message to the secondary base station, the secondary base station further sets a buffer threshold. When the downlink data in the buffer of the secondary base station is lower than the buffer threshold, the secondary base station requests data from the primary base station. .
  • the buffer threshold does not need to notify the primary base station, nor does it need to notify the UE, and therefore does not need to be carried in the data offload response message, or the secondary base station periodically reports the buffer status of the secondary base station to the primary base station, And causing the primary base station to send data to the secondary base station according to the reported buffering situation.
  • the method further includes:
  • the primary base station receives a data offload configuration ready message from the secondary base station or the UE, and starts data offload transmission.
  • the configuration of the secondary base station is completed and the UE and the secondary base After the station establishes a synchronous connection, it needs to notify the configuration of the control plane of the primary base station.
  • the structure of each node before and after configuration is as shown in Figure 4.
  • the data offload configuration ready message may be sent by the UE or may be sent by the secondary base station.
  • the primary base station may If the configuration is complete, if the primary base station receives the data offload configuration ready message, the primary base station needs to wait for the secondary base station to send a data offload configuration ready message before the data offloading can be performed.
  • the X2 port can apply to the primary base station to adjust the data sharing amount and update the configuration parameters.
  • the updated configuration parameters include the BSR threshold and the RB configuration parameters.
  • the update process includes the following steps:
  • the primary base station receives the data offload configuration modification request from the secondary base station; and the data offload configuration modification request message includes the RB configuration parameter to be modified and the BSR threshold to be modified;
  • the primary base station or the secondary base station sends a data offload configuration modification message to the UE, where the data offload configuration modification message includes the RB configuration parameter to be modified and the BSR threshold to be modified.
  • the update process can be as follows:
  • the first step the secondary base station sends a data offload configuration modification request message to the primary base station, where the data offload configuration modification request message includes the RB configuration parameter to be modified and the BSR threshold.
  • the second step the secondary base station receives the data offload from the primary base station. Configure a modification request response message;
  • the third step the secondary base station sends a data offload configuration modification message to the UE, where the data offload configuration modification message includes the RB configuration parameter to be modified and the BSR threshold.
  • Step 4 The secondary base station receives the data offload configuration modification response message returned by the UE.
  • the update process may also be specifically: The first step: the primary base station receives the data offload configuration modification request from the secondary base station; and the data offload configuration modification request message includes the RB configuration parameter and the BSR threshold to be modified;
  • the second step the primary base station sends a data offload configuration modification request response to the secondary base station; Xiao, 3 ⁇ 4;
  • the third step the primary base station sends a data offload configuration modification message to the UE, where the data offload configuration modification message includes the RB configuration to be modified. Parameters and BSR thresholds;
  • Step 4 The primary base station receives the data offload configuration modification response message returned by the UE.
  • the embodiment further provides a downlink (SGW-UE) data transmission method.
  • SGW-UE downlink
  • the method in this embodiment is based on a partially offloaded downlink data transmission method.
  • the method includes:
  • Step 201 The PDCP entity of the primary base station receives data from the SGW, and processes the data to form first data.
  • the partial offload here means that the data part of one RB is transmitted via the secondary base station and partly transmitted via the primary base station.
  • the processing performed by the PDCP entity of the primary base station includes data encryption and header compression.
  • the primary base station receives data from the SGW, and the secondary base station does not receive data from the SGW.
  • Step 202 The RLC entity of the primary base station adds a first RLC sequence number to the first data, and forms a second data, and sends the offloaded data to be offloaded in the second data to the PDCP entity of the secondary base station.
  • the RLC entity of the primary base station adds the first RLC sequence number to the first data and sends it to the PDCP entity in the secondary base station.
  • the PDCP entity in the secondary base station.
  • one RB packet is added with the sequence number "X+1" in the RLC entity of the primary base station, and the serial number " ⁇ +1" is added to the RLC entity of the primary base station.
  • Each RLC SDU corresponds to a single RLC sequence number.
  • Step 203 The PDCP entity of the secondary base station sends the offloaded data to the secondary base station.
  • RLC entity The PDCP entity of the secondary base station sends the offloaded data to the secondary base station.
  • the PDCP entity of the secondary base station after receiving the offloaded data from the primary base station, transparently processes the offloaded data, that is, does not process, and then sends the offloaded data to the RLC entity of the secondary base station. Since the basic functions of the PDCP entity have been implemented in the PDCP entity of the primary base station, such as data encryption, header compression, etc., the PDCP entity of the secondary base station can not process the offloaded data.
  • Step 204 The secondary base station processes the data to be offloaded, and sends the processed data to be offloaded to the UE.
  • the secondary base station processes the data to be offloaded.
  • the RLC entity of the secondary base station performs segmentation concatenation of the received offloaded data, and then adds a second RLC sequence number to form a third.
  • Data and the third data is sent to the MAC layer.
  • segment cascading includes three processes: segmentation, which is to segment and reassemble high-level PDU packets of different lengths into smaller RLC load units (PUs); cascading, when an RLC SDU When the content cannot fill a complete RLC PDU, the first segment of the next RLC SDU can also be placed in the PU, and the last segment of the previous RLC SDU is cascaded; padding, when the content of the RLC SDU cannot be filled When a full RLC PDU is full and cannot be cascaded, the remaining space can be filled with padding bits.
  • segmentation which is to segment and reassemble high-level PDU packets of different lengths into smaller RLC load units (PUs)
  • cascading when an RLC SDU When the content cannot fill a complete RLC PDU, the first segment of the next RLC SDU can also be placed in the PU, and the last segment of the previous RLC SDU is cascaded
  • padding when the content of the RLC SDU cannot be filled When a full RLC
  • the RLC entity of the secondary base station segments the data packets in stages, and adds a second RLC sequence number to form a third data, that is, an RLC PDU.
  • the two RLC entities respectively add a sequence number to the data packet generated by itself. ⁇ + ⁇ , and "P+1", then sent to the MAC entity.
  • the MAC entity of the secondary base station processes the third data, and then sends the third data to the physical layer, so that the physical layer (Phy) sends the processed third data to the user terminal.
  • the "processing" here can be specifically multiplexed, that is, the third data corresponding to one or more RBs are combined. If a TTI receives only the third data sent by one RB, no multiplexing is required.
  • Packets from multiple RBs are formed after multiplexing by the MAC entity of the secondary base station
  • the MAC PDU is finally sent to the physical layer for transmission.
  • the MAC entity puts the data packets with the sequence numbers " ⁇ + ⁇ , and "P+1" in the same MAC PDU, and adds "MAC Header" to form a MAC PDU
  • the physical layer sends the processed third data to the UE.
  • the part of the offloaded data is transmitted to the PDCP entity of the secondary base station, and is sent to the UE by the secondary base station, when the air interface condition of the secondary base station changes.
  • the MAC entity of the secondary base station can respond to the primary base station in time to implement dynamic offloading, and the modification of the protocol is small and easy to implement.
  • the method further includes:
  • the secondary base station pre-stores the second data to be offloaded in a cache of the RLC entity of the secondary base station.
  • the secondary base station may pre-store the second data in the cache of the RLC entity of the secondary base station.
  • the amount of data in the buffer is lower than a certain threshold, some data is transmitted.
  • the scheduler of the secondary base station decides to transmit data, the data packet can be directly taken out from the buffer of the secondary base station, so that the processing speed can be speeded up.
  • the RLC entity of the primary base station adds a first RLC sequence number to the first data, specifically:
  • the RLC entity of the primary base station performs segmentation concatenation processing on the first data, and adds a first RLC sequence number to the first data after the segmentation cascade.
  • the RLC entity of the primary base station performs concatenation processing on the first data, that is, several data packets from the PDCP entity are combined into one to form a larger data packet, but the maximum cannot be
  • the maximum packet size exceeding the protocol requirement is 8188 Bytes.
  • the two RLC SDUs are concatenated into one RLC PDU and then sent to the PDCP entity of the secondary base station.
  • the advantage of this approach is that multiple packets from the SGW share the primary base. A sequence number in the RLC entity of the station, so it occupies less RLC sequence number.
  • the primary base station pre-stores the first data to be offloaded in the cache of the RLC entity of the secondary base station
  • the RLC entity of the primary base station cascades the first data.
  • the physical layer of the UE After the physical layer of the secondary base station sends the processed data to be offloaded, the physical layer of the UE receives the fourth data from the secondary base station, and the fourth data sequentially passes through the MAC entity, the second RLC entity, and the second PDCP entity of the UE. And processing by the first RLC entity and the first PDCP entity to form fifth data.
  • the processing of the data packet by the UE is inverse to the processing of the data packet by the primary base station and the secondary base station, namely:
  • the physical layer of the UE receives the fourth data from the secondary base station
  • the MAC entity of the UE divides each data packet of the fourth data into several RLC PDUs; the second RLC entity of the UE restores each RLC PDU to a data packet before the segmentation cascade, and removes the second RLC sequence number, and sends a second PDCP entity to the UE;
  • the second PDCP entity of the UE sends the restored data packet to the first RLC entity of the UE;
  • the first RLC entity of the UE removes the first RLC sequence number of the data packet, and restores the cascading packet to multiple packets, and then sends the first RCP sequence to the UE.
  • the first PDCP entity of the UE restores the first process, obtains the fifth data, and finally obtains the data sent by the SGW.
  • the specific processing performed by the UE on the data packet can be analogized to the transmission method of the downlink data described above, and details are not described herein again.
  • the embodiment further provides a downlink data transmission method. As shown in FIG. 8, the method in this embodiment is based on a completely offloaded data transmission method, including:
  • Step 301 A PDCP entity of the primary base station receives data from the SGW, and processes the data to form first data.
  • the complete offloading means that the data of one RB is all transmitted via the secondary base station.
  • the processing performed by the PDCP entity of the primary base station includes data encryption and header compression.
  • the primary base station receives data from the SGW, and the secondary base station does not receive data from the SGW.
  • Step 302 The RLC entity of the primary base station receives the first data, and sends the first data to a PDCP entity of the secondary base station.
  • the RLC entity of the primary base station performs transparent processing on the first data, that is, does not perform any processing.
  • Step 303 The PDCP entity of the secondary base station receives the first data from the primary base station, and sends the first data to the RLC entity of the secondary base station.
  • the PDCP entity of the secondary base station After receiving the first data from the primary base station, the PDCP entity of the secondary base station transparently processes the first data, that is, does not perform any processing, and then sends the first data to the RLC entity of the secondary base station. Since the basic functions of the PDCP entity have been implemented in the PDCP entity of the primary base station, such as data encryption, header compression, etc., the PDCP entity of the secondary base station can not perform any processing on the offloaded data.
  • Step 304 The secondary base station processes the first data, and sends the processed first data to the UE.
  • the processing, by the secondary base station, the first data specifically includes the following content:
  • the RLC entity performs segmentation concatenation of the received first data, then adds a second RLC sequence number, forms third data, and sends the third data to the MAC entity.
  • the fourth data is formed, and the fourth data is sent to the physical layer, so that the physical layer sends the fourth data to the UE.
  • processing may specifically be multiplexing, that is, combining the third data corresponding to one or more RBs. If a Transmission Time Interval (TTI) receives only the third data sent by one RB, no multiplexing is required.
  • TTI Transmission Time Interval
  • the RLC entity of the primary base station does not need to allocate the RLC sequence number to the data packet, which simplifies the processing flow, reduces the signaling overhead, and speeds up the data. transmission.
  • the working principle of the primary and secondary base stations of the downlink data transmission method in this embodiment is the same as that of the foregoing embodiment, and details are not described herein again.
  • the physical layer of the UE receives the fourth data from the secondary base station, where the fourth data is processed by the MAC entity of the UE, the second RLC entity, the second PDCP entity, the first RLC entity, and the first PDCP entity. Form the fifth data.
  • the processing of the data packet by the UE and the processing of the data packet by the primary base station and the secondary base station are mutually reversed, and are not described herein again.
  • the embodiment further provides an uplink (UE-SGW) data transmission method.
  • UE-SGW uplink
  • the method in this embodiment is a method for transmitting uplink data, including:
  • Step 401 The UE reports the BSR to the primary base station and/or the secondary base station, so that the primary base station and/or the secondary base station allocates uplink transmission resources to the UE.
  • the UE When the UE is in the upper BSR, the UE only sends the BSR to the primary base station for the RBs that do not participate in the offloading. For the RBs participating in the offloading, if configured to be partially offloaded, the UE preferentially sends the BSR to the secondary base station.
  • the UE reports the BSR to the primary base station and/or the secondary base station, specifically: After determining that the total amount of the data to be transmitted is smaller than the pre-configured BSR threshold, the BSR is reported to the secondary base station; after determining that the total amount of the data to be offloaded is greater than the pre-configured BSR threshold, the BSR is reported to the secondary base station, and The primary base station reports the difference between the total amount of the offloaded data and the BSR threshold.
  • the BSR is reported only to the secondary base station. If the total amount of data to be offloaded is greater than the BSR threshold, the BSR threshold is reported to the secondary base station. Data, other data is reported to the primary base station, that is, the BSR is reported to the secondary base station, and the difference between the total amount of the offloaded data and the BSR threshold is reported to the primary base station. If configured to be fully offloaded, only 4 ⁇ 881 to the primary base station.
  • the BSR threshold is 600 Bytes.
  • the UE needs to report 800 Bytes, it reports 200 Bytes to the primary base station and 600 Bytes to the secondary base station.
  • the primary base station and the secondary base station allocate uplink transmission resources to the UE respectively, and the two base stations do not need to negotiate with each other.
  • Step 402 The first PDCP entity of the UE performs the first processing on the data to form the first data.
  • the processing performed by the first PDCP entity includes data encryption and header compression.
  • the MAC entity After receiving the uplink resource, if the uplink resource is allocated by the primary base station, the MAC entity directly requests data from the first RLC entity; if the uplink resource is allocated by the secondary base station, the MAC entity requests data from the second RLC entity. The second RLC entity then requests data from the first RLC entity.
  • Step 403 The first RLC entity of the UE performs segmentation concatenation of the first data, adds a first RLC sequence number, forms second data, and uses the second transmission data according to the received uplink transmission resource allocated by the secondary base station.
  • the offloaded data to be offloaded is sent to the second PDCP entity.
  • the first RLC entity of the UE performs segmentation concatenation of the first data, and then adds the first RLC sequence number to the second PDCP entity.
  • the first RLC entity of the UE performs segmentation concatenation of the first data, and then adds the first RLC sequence number to the second PDCP entity.
  • the MAC entity receives the uplink resource allocated by the secondary base station, and after scheduling the decision, determines that one of the RBs transmits 150 bytes, and the other RB transmits 180 bytes.
  • the first RLC entities of the two RBs respectively segment and concatenate the data packets in the cache, and add the first RLC sequence number to form two RLC PDUs.
  • One of the sizes is 150 Bytes, the first RLC number is "X+ 1", the other size is 180 Bytes, and the first RLC sequence number is "Y+ 1".
  • Step 404 The second PDCP entity of the UE sends the offload data to a second RLC entity of the UE.
  • the second PDCP entity After receiving the offloaded data, the second PDCP entity transparently processes the offloaded data, that is, does not perform any processing, and then sends the offloaded data to the second RLC entity. Since the basic functions of the PDCP entity have been implemented in the first PDCP entity, such as data encryption, header compression, etc., the second PDCP entity may not have to do any processing on the offloaded data.
  • Step 405 The second RLC entity of the UE adds the second RLC sequence number to the received offload data to form third data, and sends the third data to the MAC entity of the UE.
  • the RLC PDU After the RLC PDU is transparently transmitted from the PDCP layer, it reaches the secondary RLC layer.
  • the two second RLC entities respectively add the second RLC sequence numbers to form the RLC PDUs.
  • the two second RLC entities in FIG. 9 respectively add the second RLC to the data packets generated by themselves.
  • the serial numbers " ⁇ + ⁇ , and "P+1" are then sent to the MAC entity.
  • Step 406 The physical layer of the UE sends the processed third data to the secondary base station.
  • the MAC entity of the UE processes the third data to form fourth data, and sends the fourth data to the physical layer, so that the physical layer sends the processed third data to the primary base station and/or Secondary base station.
  • the MAC entity puts the data packets with the sequence numbers " ⁇ + ⁇ , and "P+1" in the same MAC PDU, and adds "MAC Header" to form a MAC PDU
  • the physical layer transmits the fourth data to the primary base station and/or the secondary base station.
  • the method further includes:
  • the UE pre-stores the first data to be offloaded in a cache of the second RLC entity. Further, the first RLC entity adds a first RLC sequence number to the first data, which is:
  • the first RLC entity concatenates the first data and adds a first RLC sequence number to the concatenated first data.
  • the first RLC entity performs concatenation processing on the first data, but does not perform segmentation, that is, several data packets from the first PDCP entity are combined into one to form a larger data packet, but the maximum The maximum size of the packet that cannot be exceeded by the protocol is 8188 Bytes.
  • the advantage of this method is that multiple data packets share one sequence number in the first RLC entity, so that less RLC sequence numbers are occupied, and when the amount of data is large and the air interface condition is good, the limitation of RLC window pushing is reduced. The resulting data delay.
  • the UE pre-stores the first data to be offloaded in the cache of the second RLC entity
  • the first RLC entity of the UE cascading the first data can be freely combined to implement, there are four implementations after the combination:
  • the physical layer of the secondary base station receives the fourth data from the UE, and the fourth data is sequentially processed by the MAC entity, the RLC entity, and the PDCP entity of the secondary base station, and the RLC of the primary base station. Processing of entities and PDCP entities, formation Fifth data.
  • the embodiment further provides an uplink data transmission method. As shown in FIG. 12, the method includes: Step 501: A UE reports a BSR to a primary base station and/or a secondary base station, so that the primary base station and/or the secondary base station allocates uplinks to the UE. Transfer resources.
  • Step 502 The first PDCP entity of the UE receives data from the application layer, and processes the data to form the first data.
  • Step 503 The first RLC entity of the UE adds a first RLC sequence number to the first data, forms second data, and sends the offload data to be offloaded in the second data to the second PDCP entity.
  • Step 504 The second PDCP entity of the UE receives the offload data, and sends the offloaded data to a second RLC entity of the UE.
  • Step 505 The second RLC entity of the UE adds the second RLC sequence number to form the third data according to the received uplink transmission resource allocated by the secondary base station, and then adds the second RLC sequence to form the third data. Data is sent to the MAC entity;
  • Step 506 The physical layer of the UE sends the processed third data to the secondary base station.
  • the fourth data is formed, and the fourth data is sent to the physical layer, so that the physical layer sends the fourth data to the secondary base station.
  • the data before receiving the uplink transmission resource allocated by the secondary base station, the data enters the second PDCP entity, and therefore, the first RLC entity of the UE only has data.
  • the packet is processed by a sequence number without segmentation of the data packet, and the work of segmenting the data packet requires a second RLC entity.
  • the other steps of this embodiment are the same as the first uplink data transmission method, and are no longer used here. Narration.
  • the physical layer of the secondary base station receives the fourth data from the UE, and the fourth data is sequentially processed by the MAC entity, the RLC entity, and the PDCP entity of the secondary base station, and the primary The processing of the RLC entity and the PDCP entity of the base station forms the fifth data.
  • the processing of the data packet by the primary base station and the secondary base station is inverse to the processing of the data packet by the UE, and will not be described here.
  • the method further includes:
  • the UE pre-stores the first data to be offloaded in a cache of the second RLC entity.
  • the data offloading type of the method is a partial offload
  • the UE reports the BSR to the primary base station and/or the secondary base station, specifically:
  • the BSR is reported only to the secondary base station
  • the BSR is reported to the secondary base station, and the difference between the total amount of the offloaded data and the BSR threshold is reported to the primary base station.
  • the UE reports only to the primary base station.
  • the embodiment further provides a base station, as shown in FIG. 13, including a transmitter 131 and a receiver 132, where
  • the RB establishes a second PDCP entity and a second RLC entity and performs a data offloading configuration; a receiver 132, configured to receive a second message from the secondary base station, where the second message includes configuration parameters of the to-be-split RB;
  • the UE has a first PDCP entity, a first RLC entity, and a MAC entity, and the second PDCP entity and the second RLC entity are located between the first RLC entity and the MAC entity.
  • the second message further includes: a buffer status report BSR threshold, where the BSR threshold is allocated by the secondary base station and used by the UE to report a BSR, where the BSR is used to enable the The primary base station and/or the secondary base station allocates uplink transmission resources to the UE.
  • the receiver 132 is further configured to: when the downlink data in the buffer of the secondary base station is lower than a buffer threshold set by the secondary base station, receive a data request of the secondary base station;
  • the transmitter 131 is further configured to send data to the secondary base station according to a buffer condition of the secondary base station periodically reported by the secondary base station.
  • the first message further includes: a traffic distribution type identifier, configured to indicate that the data traffic is completely offloaded or partially offloaded, where
  • the partial offloading refers to that the data portion of one RB is transmitted via the secondary base station, and is partially transmitted via the primary base station, and the complete offloading refers to that all data of one RB is transmitted via the secondary base station.
  • the present embodiment further provides a base station system, as shown in FIG. 14, including a primary base station 2 and a secondary base station 3.
  • the primary base station includes a PDCP entity 21 and an RLC entity 22, and the secondary base station includes a PDCP entity 31 and an RLC entity 32. among them,
  • the PDCP entity 21 of the primary base station 2 is configured to receive data from the serving gateway SGW, and process the data to form first data, where the data transmission method is partial offloading;
  • the RLC entity 22 of the primary base station 2 is configured to add a first RLC to the first data. Serial number, forming second data, and sending the data to be offloaded in the second data to the PDCP entity of the secondary base station;
  • the PDCP entity 31 of the secondary base station 3 is configured to send the to-be-split data to the RLC entity 32 of the secondary base station 3;
  • the secondary base station 3 is configured to process the to-be-divided data, and send the processed to-be-split data to the UE.
  • the RLC entity 22 of the primary base station 2 is further configured to perform segmentation concatenation processing on the first data, and add a first RLC sequence number to the first data after the segmentation cascade.
  • the primary base station in the base station system in this embodiment can perform the action of the primary base station in the foregoing method embodiment
  • the secondary base station in the base station system can perform the action of the secondary base station in the foregoing method embodiment
  • the partially-divided data is processed by the RLC entity of the primary base station, and then enters the PDCP entity of the secondary base station, and corresponds to the PDCP entity and the RLC entity of the secondary base station.
  • the second PDCP entity and the second RLC entity are set between the RLC entity and the MAC entity, and the processing flow of the data to be offloaded in the prior art is changed, and the change of the air interface condition measured by the bottom layer is faster, and the dynamic shunting effect is better.
  • the present embodiment further provides a base station system, as shown in FIG. 14, including a primary base station 2 and a secondary base station 3.
  • the primary base station includes a PDCP entity 21 and an RLC entity 22, and the secondary base station includes a PDCP entity 31 and an RLC entity 32.
  • the PDCP entity 21 of the primary base station 2 is configured to receive data from the serving gateway SGW, and process the data to form first data, where the data transmission method is completely offloaded;
  • the RLC entity 22 of the primary base station 2 is configured to receive the first data, and send the first data to the PDCP entity 31 of the secondary base station 3;
  • the PDCP entity 31 of the secondary base station 3 is configured to receive the first data from the primary base station 2, and send the first data to the RLC entity 32 of the secondary base station 3;
  • the secondary base station 3 processes the first data, and sends the processed first data to the UE.
  • the primary base station in the base station system in this embodiment can perform the action of the primary base station in the foregoing method embodiment
  • the secondary base station in the base station system can perform the action of the secondary base station in the foregoing method embodiment
  • the data that is completely offloaded does not need to be transmitted through the primary base station. Therefore, the RLC entity of the primary base station does not need to allocate the RLC sequence number to the data packet, which simplifies the processing flow, reduces signaling overhead, and speeds up data. Transmission.
  • the present embodiment sets a second PDCP entity and a second RLC entity between the first RLC entity and the MAC entity of the UE, and changes the data to be offloaded in the prior art.
  • the processing flow has a faster response to the changes in the air interface measured at the bottom layer, and the dynamic shunting effect is better.
  • the present embodiment further provides a user terminal, as shown in FIG. 15, including a first PDCP entity 41, a first RLC entity 42, a MAC entity 43, and a physical layer 44, and further includes: a BSR reporting unit 40 and a second PDCP entity 45. And a second RLC entity 46, the second PDCP entity 45 and the second RLC entity 46 being located between the first RLC entity 42 and the MAC 43 of the UE, where
  • the BSR reporting unit 40 is configured to report the BSR to the primary base station and/or the secondary base station, so that the primary base station and/or the secondary base station allocate uplink transmission resources for the U E;
  • a first PDCP entity 41 configured to perform first processing on the data to form first data
  • the first RLC entity 42 is configured to perform segmentation concatenation of the first data, add a first RLC sequence number, form second data, and send the second data according to the received uplink transmission resource allocated by the secondary base station.
  • the offloaded data to be offloaded is sent to the second PDCP entity 45;
  • a second PDCP entity configured to send the offloaded data to a second RLC entity 46 of the UE
  • a second RLC entity 46 configured to add the received offload data to the second RLC Sequence number, forming third data, and sending the third data to the MAC entity 43 of the UE;
  • the physical layer 44 of the UE is configured to send the processed third data to the secondary base station.
  • the BSR reporting unit is specifically configured to:
  • the BSR is reported to the secondary base station, and the difference between the total amount of the offloaded data and the BSR threshold is reported to the primary base station.
  • the UE in the base station system in this embodiment may perform the action of the UE in the foregoing method embodiment.
  • the user terminal in the embodiment of the present invention by setting a second PDCP entity and a second RLC entity between the first RLC entity and the MAC entity, and the second PDCP entity logically corresponds to the PDCP entity of the secondary base station, and the second RLC entity and the secondary
  • the RLC entity of the base station logically corresponds to change the processing flow of the data to be shunted in the prior art, and the response to the air interface condition measured by the bottom layer is faster, and the dynamic shunting effect is better.
  • the present embodiment further provides a user terminal, as shown in FIG. 15, including a first PDCP entity 41, a first RLC entity 42, a MAC entity 43, and a physical layer 44, and further includes: a BSR reporting unit 40 and a second PDCP entity 45. And a second RLC entity 46, the second PDCP entity 45 and the second RLC entity 46 being located between the first RLC entity 42 and the MAC 43 of the UE,
  • the BSR reporting unit 40 is configured to report the BSR to the primary base station and/or the secondary base station, so that the primary base station and/or the secondary base station allocate uplink transmission resources for the U E;
  • a first PDCP entity 41 configured to perform first processing on the data to form first data
  • the first RLC entity 42 is configured to add a first RLC sequence number to the first data, form second data, and send the offloaded data to be offloaded in the second data to the second PDCP entity 45 of the UE;
  • a second PDCP entity 45 configured to send the offloaded data to a second RLC entity 46 of the UE;
  • the second RLC entity 46 is configured to add the second RLC sequence number to form the third data according to the received uplink transmission resource allocated by the secondary base station, and then add the second RLC sequence to form the third data. Sent to the MAC entity 43;
  • the physical layer 44 is configured to send the processed third data to the secondary base station.
  • the BSR reporting unit is specifically configured to:
  • the BSR is reported to the secondary base station, and the difference between the total amount of the offloaded data and the BSR threshold is reported to the primary base station.
  • the UE in the base station system in this embodiment may perform the action of the UE in the foregoing method embodiment.
  • the user terminal in the embodiment of the present invention by setting a second PDCP entity and a second RLC entity between the first RLC entity and the MAC entity, and the second PDCP entity logically corresponds to the PDCP entity of the secondary base station, and the second RLC entity and the secondary
  • the RLC entity of the base station logically corresponds to change the processing flow of the data to be shunted in the prior art, and the response to the air interface condition measured by the bottom layer is faster, and the dynamic shunting effect is better.
  • the disclosed systems, devices, and methods may be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the modules or units is only a logical function division.
  • there may be another division manner for example, multiple units or components may be used. Combined or can be integrated into another system, or some features can be ignored, or not executed.
  • the coupling or direct coupling or communication connection between the various components shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be electrical, mechanical or otherwise.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software function unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may contribute to the prior art or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium.
  • the instructions include a plurality of instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: a USB flash drive, a removable hard disk, a read-only memory (ROM), and a random access memory (RAM, Random Access).

Abstract

La présente invention concerne le domaine des communications et a pour objet, dans certains modes de réalisation, de mettre en œuvre une diffusion dynamique en flux. Un procédé de configuration pour diffusion de données en flux, un système de station de base et un équipement d'utilisateur (UE) sont décrits. Le procédé de configuration pour diffusion de données en flux d'après les modes de réalisation de la présente invention comporte les étapes suivantes : une station de base principale envoie un premier message à une station de base auxiliaire, permettant ainsi à la station de base auxiliaire de déterminer un RB à diffuser en flux et de spécifier un paramètre de configuration pour le RB à diffuser en flux ; un deuxième message est reçu en provenance de la station de base auxiliaire, le deuxième message comportant le paramètre de configuration du RB à diffuser en flux ; un troisième message est envoyé à l'UE, permettant ainsi à l'UE d'établir pour le RB à diffuser en flux une deuxième entité Protocole de convergence de données en mode paquets (PDCP) et une deuxième entité de protocole de couche de commande de liaison radioélectrique (RLC), et d'effectuer la configuration en vue de la diffusion de données en flux.
PCT/CN2012/074459 2012-04-20 2012-04-20 Procédé de configuration pour diffusion de données en flux, système de station de base et équipement d'utilisateur WO2013155709A1 (fr)

Priority Applications (4)

Application Number Priority Date Filing Date Title
PCT/CN2012/074459 WO2013155709A1 (fr) 2012-04-20 2012-04-20 Procédé de configuration pour diffusion de données en flux, système de station de base et équipement d'utilisateur
CN201280072392.1A CN104247547B (zh) 2012-04-20 2012-12-05 数据分流配置方法、基站系统和用户终端
CN201810254570.1A CN108337633B (zh) 2012-04-20 2012-12-05 数据分流配置方法、基站系统和用户终端
PCT/CN2012/085977 WO2013155846A1 (fr) 2012-04-20 2012-12-05 Procédé de configuration pour diffusion de données en flux, système de station de base et terminal d'utilisateur

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2012/074459 WO2013155709A1 (fr) 2012-04-20 2012-04-20 Procédé de configuration pour diffusion de données en flux, système de station de base et équipement d'utilisateur

Publications (1)

Publication Number Publication Date
WO2013155709A1 true WO2013155709A1 (fr) 2013-10-24

Family

ID=49382822

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/CN2012/074459 WO2013155709A1 (fr) 2012-04-20 2012-04-20 Procédé de configuration pour diffusion de données en flux, système de station de base et équipement d'utilisateur
PCT/CN2012/085977 WO2013155846A1 (fr) 2012-04-20 2012-12-05 Procédé de configuration pour diffusion de données en flux, système de station de base et terminal d'utilisateur

Family Applications After (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/085977 WO2013155846A1 (fr) 2012-04-20 2012-12-05 Procédé de configuration pour diffusion de données en flux, système de station de base et terminal d'utilisateur

Country Status (1)

Country Link
WO (2) WO2013155709A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105309006A (zh) * 2014-03-27 2016-02-03 华为技术有限公司 数据分流的方法和基站
CN106031229A (zh) * 2014-08-06 2016-10-12 株式会社Ntt都科摩 用户装置以及基站
CN108282817A (zh) * 2017-01-05 2018-07-13 华为技术有限公司 信息传输的方法和装置
WO2020063737A1 (fr) * 2018-09-28 2020-04-02 华为技术有限公司 Procédé et dispositif de communication
US11184943B2 (en) 2017-06-20 2021-11-23 Beijing Xiaomi Mobile Software Co., Ltd. Function allocating method and device, message transmitting method and device, and user equipment

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113163512B (zh) 2013-11-15 2023-10-24 荣耀终端有限公司 一种建立无线承载的方法及基站
WO2018013110A1 (fr) * 2016-07-13 2018-01-18 Intel Corporation Support multiconnectivité et commutation rapide de cellules pour technologies d'accès radio cellulaire à ondes millimétriques
RU2740161C1 (ru) 2017-06-16 2021-01-12 Гуандун Оппо Мобайл Телекоммьюникейшнс Корп., Лтд. Способ передачи данных, оконечное устройство и сетевое устройство
CN109151914B (zh) 2017-06-16 2024-04-12 华为技术有限公司 一种通信方法及接入网设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101795494A (zh) * 2009-02-03 2010-08-04 中国移动通信集团公司 一种lte-a系统内的数据分流方法、装置及系统
CN101965064A (zh) * 2009-07-23 2011-02-02 中兴通讯股份有限公司 分组数据聚合协议数据的传输方法与装置
CN102026398A (zh) * 2009-09-15 2011-04-20 普天信息技术研究院有限公司 Lte中继系统中分组汇聚协议的实现方法和装置
CN102421146A (zh) * 2011-11-29 2012-04-18 中兴通讯股份有限公司 一种实现载波业务分流的方法和装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020101848A1 (en) * 2000-12-05 2002-08-01 Ivan Lee Systems and methods for on-location, wireless access of web content
CN100531432C (zh) * 2006-06-20 2009-08-19 华为技术有限公司 一种负载分流方法和装置
CN102177743B (zh) * 2009-09-24 2013-04-17 华为技术有限公司 一种网络流量分流方法、设备及系统
CN102244895B (zh) * 2010-05-13 2015-12-16 中兴通讯股份有限公司 一种增强移动性的分流方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101795494A (zh) * 2009-02-03 2010-08-04 中国移动通信集团公司 一种lte-a系统内的数据分流方法、装置及系统
CN101965064A (zh) * 2009-07-23 2011-02-02 中兴通讯股份有限公司 分组数据聚合协议数据的传输方法与装置
CN102026398A (zh) * 2009-09-15 2011-04-20 普天信息技术研究院有限公司 Lte中继系统中分组汇聚协议的实现方法和装置
CN102421146A (zh) * 2011-11-29 2012-04-18 中兴通讯股份有限公司 一种实现载波业务分流的方法和装置

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10602404B2 (en) 2014-03-27 2020-03-24 Huawei Technologies Co., Ltd. Data offloading method and base station
CN105309006B (zh) * 2014-03-27 2019-05-28 华为技术有限公司 数据分流的方法和基站
CN105309006A (zh) * 2014-03-27 2016-02-03 华为技术有限公司 数据分流的方法和基站
CN106031229A (zh) * 2014-08-06 2016-10-12 株式会社Ntt都科摩 用户装置以及基站
CN106031229B (zh) * 2014-08-06 2019-12-13 株式会社Ntt都科摩 用户装置以及基站
CN108282817A (zh) * 2017-01-05 2018-07-13 华为技术有限公司 信息传输的方法和装置
CN110169117A (zh) * 2017-01-05 2019-08-23 华为技术有限公司 信息传输的方法和装置
US10779195B2 (en) 2017-01-05 2020-09-15 Huawei Technologies Co., Ltd. Information transmission method and apparatus
CN108282817B (zh) * 2017-01-05 2021-08-20 华为技术有限公司 信息传输的方法和装置
US11516704B2 (en) 2017-01-05 2022-11-29 Huawei Technologies Co., Ltd. Information transmission method and apparatus
US11184943B2 (en) 2017-06-20 2021-11-23 Beijing Xiaomi Mobile Software Co., Ltd. Function allocating method and device, message transmitting method and device, and user equipment
WO2020063737A1 (fr) * 2018-09-28 2020-04-02 华为技术有限公司 Procédé et dispositif de communication
US11974162B2 (en) 2018-09-28 2024-04-30 Huawei Technologies Co., Ltd. Communication method and device

Also Published As

Publication number Publication date
WO2013155846A1 (fr) 2013-10-24

Similar Documents

Publication Publication Date Title
CN108337633B (zh) 数据分流配置方法、基站系统和用户终端
US10708940B2 (en) Method and apparatus for reporting buffer state by user equipment in communication system
US10721754B2 (en) Data transmission method and apparatus
WO2013155709A1 (fr) Procédé de configuration pour diffusion de données en flux, système de station de base et équipement d'utilisateur
CN105338572B (zh) 一种双连接中分割承载的数据分配方法和装置
KR102067589B1 (ko) 무선 통신에서 패킷 프로세싱을 병렬화하는 방법 및 시스템
JP5180325B2 (ja) Ｐｄｃｐ状態報告の送信方法
EP1797659B1 (fr) Mac-e lent pour emission autonome dans un acces de paquets de ligne montante haute vitesse (hsupa) avec commande temporelle d'emission specifique de service
WO2017124941A1 (fr) Procédé de transmission de données, équipement utilisateur et station de base
US9319320B2 (en) Traffic flow establishment method and device and traffic flow modification method and device
TWI657708B (zh) 用於新型無線電系統的分段與級聯方法及使用者設備
US8774221B2 (en) Apparatus and method for reporting buffer status of UE in mobile communication system
EP3737183B1 (fr) Procédés et dispositifs de communication et support de stockage lisible par ordinateur
JP2013500675A (ja) アップリンク周波数上でデータブロックを送信する方法及び装置
EP3737145A1 (fr) Procédé, dispositif et système de communication
WO2013152743A1 (fr) Procédé et dispositif de transmission de signaux
WO2012155783A1 (fr) Procédé et système de transmission de données
JPWO2018084202A1 (ja) 無線端末及び基地局
CN116746264A (zh) 一种通信方法及装置
EP1919230A1 (fr) Procédé pour affectation de capacité pour le transfert de paquets d'émission de trafic en continu dans un réseau d'accès radio
US20230217426A1 (en) Resource allocation method and apparatus and system
US20240121658A1 (en) Data transmission method and apparatus, device, and storage medium
WO2012136067A1 (fr) Procédé et système d'optimisation de qualité de service, et élément de réseau côté réseau
JP6261886B2 (ja) 無線基地局装置およびバッファ制御方法
CN117835333A (zh) 通信方法及通信装置

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12874731

Country of ref document: EP

Kind code of ref document: A1