WO2018059148A1

WO2018059148A1 - Data forwarding method and device thereof

Info

Publication number: WO2018059148A1
Application number: PCT/CN2017/097491
Authority: WO
Inventors: 肖芳英; 刘仁茂; 山田升平
Original assignee: 夏普株式会社; 肖芳英
Priority date: 2016-09-30
Filing date: 2017-08-15
Publication date: 2018-04-05
Also published as: CN107889234A

Abstract

Provided are a method executed by an auxiliary base station, a method executed by a main base station, and a corresponding auxiliary base station and a main base station. The method executed by the auxiliary base station is used to forward data to the main base station, and the auxiliary base station and the main base station cooperatively send the data to a user equipment. The method comprises: receiving a downlink data transmission state frame from a main base station; and forwarding, to the main base station, data to be sent to a user equipment according to the received downlink data transmission state frame, wherein the downlink data transmission state frame is used to inform the auxiliary base station of the data correctly received or not received by the main base station and/or the data successfully forwarded to the user equipment. The solution can prevent problems, for example, an auxiliary base station forwards data successfully sent to a main base station but not confirmed to be successfully received by a user equipment (UE).

Description

Data forwarding method and device thereof

Technical field

The present disclosure relates to the field of wireless communication technologies, and more particularly, to a data forwarding method and apparatus therefor.

Background technique

In March 2016, at the RAN#71 plenary session of the 3rd Generation Partnership Project (3GPP), NTT DOCOMO proposed a new research project on 5G technology standards (see Non-patent literature: RP-160671) :New SID Proposal: Study on New Radio Access Technology), and approved. The goal of the research project is to develop a new wireless (New Radio: NR) access technology to meet all 5G application scenarios, requirements and deployment environments. NR mainly has three application scenarios: Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC) and Ultra Reliable and Low Laency Communications (URLLC). According to the planning of the research project, the standardization of NR is carried out in two phases: the first phase of standardization will be completed in mid-2018; the second phase of standardization will be completed by the end of 2019. The first-stage standard specification is forward-compatible with the second-stage standard specification, while the second-stage standard specification is based on the first-stage standard specification and meets all the requirements of the 5G NR technical standard.

In the existing user plane data transmission method, there may be a case where user plane data is transmitted between the secondary base station and the core network or the next generation core network, part of the data is transmitted by using the wireless resources of the secondary base station, and another part of the data is transmitted through the auxiliary The interface between the base station and the primary base station is sent to/from the primary base station and transmitted using the resources of the primary base station. If the downlink data transmission is performed by using the method, data bearer reconfiguration is required, for example, a secondary cell group (SCG) is separated (may be LTE-NR or eLTE-NR or NR-LTE or NR-eLTE). Or LTE-eLTE or eLTE-LTE SCG split bearer) reconfigured as a primary cell group (Master Cell Group: MCG) The bearer (LTE-NR or eLTE-NR or NR-LTE or NR-eLTE or LTE-eLTE or eLTE-LTE MCG bearer) may need to perform data forwarding operations according to the bearer configuration, and the data forwarding operation may be performed when switching Data forwarding process. Part of the data has been forwarded to the primary base station before the reconfigured SCG split bearer is the MCG bearer. Therefore, how to prevent the secondary base station from forwarding data that has been successfully transmitted to the primary base station but the user equipment UE has not confirmed the reception success is a problem to be solved.

Summary of the invention

To address some of the above problems, the present disclosure proposes a method performed by a secondary base station, a method performed by a primary base station, and a corresponding secondary base station and primary base station.

According to an aspect of the present invention, a method for forwarding data to a primary base station, where the secondary base station and the primary base station cooperate to transmit data to a user equipment, is proposed. The method includes: receiving a downlink data transmission status frame from a primary base station; and forwarding data to be transmitted to the user equipment to the primary base station according to the received downlink data transmission status frame. The downlink data transmission status frame is used to notify the secondary base station of data that the primary base station has correctly received or not received and/or data that has been successfully forwarded to the user equipment. The above solution can avoid, for example, the problem that the secondary base station forwards data that has been successfully transmitted to the primary base station but the user equipment UE has not confirmed the reception success.

According to another aspect of the present invention, a secondary base station is proposed for forwarding data to a primary base station. The secondary base station includes: a receiving unit, configured to receive a downlink data transmission status frame from the primary base station; and a forwarding unit, configured to forward, to the primary base station, a to be sent to the user equipment according to the received downlink data transmission status frame Data, wherein the downlink data transmission status frame is used to inform the secondary base station of data that the primary base station has correctly received or not received and/or data that has been successfully forwarded to the user equipment.

According to still another aspect of the present invention, a method performed by a primary base station is provided, the primary base station and the secondary base station cooperatively transmitting data to a user equipment. The method includes: generating a downlink data transmission status frame, where the downlink data transmission status frame is used to notify the secondary base station that the primary base station has correctly received or not received data and/or has successfully forwarded to the user equipment And transmitting the downlink data transmission status frame to the secondary base station; and receiving data sent by the secondary base station based on the downlink data transmission status frame. According to still another aspect of the present invention, a primary base is provided The station, the primary base station and the secondary base station cooperate to transmit data to the user equipment. The primary base station includes: a status indication generating unit, configured to generate a downlink data transmission status frame, where the downlink data transmission status frame is used to notify the secondary base station that the primary base station has correctly received or not received data and/or The data that has been successfully forwarded to the user equipment; the sending unit, configured to send the downlink data transmission status frame to the secondary base station; and the receiving unit, configured to receive, by the receiving, the secondary base station, based on the downlink data transmission status frame The data.

The foregoing solution of the present invention, by notifying the secondary base station of the data that the primary base station has correctly received or not received, and/or the data that has been successfully forwarded to the user equipment, avoids, for example, rescheduling the SCG split bearer as the MCG bearer, and the secondary base station forwarding. Those problems that have been successfully transmitted to the primary base station but the user equipment UE has not acknowledged the successful reception.

DRAWINGS

The above and other features of the present disclosure will become more apparent from the following detailed description in conjunction with the appended claims.

FIG. 1 is a schematic diagram showing an NR-eLTE dual connectivity deployment scenario;

Figure 2 shows a schematic diagram of an NR-NR dual connectivity deployment scenario;

FIG. 3 is a schematic diagram showing an LTE-NR dual connectivity deployment scenario;

FIG. 4 is a schematic diagram showing an eLTE-NR dual connectivity deployment scenario;

FIG. 5 illustrates a radio protocol layer 2 entity involved in an LTE dual connectivity deployment manner;

6 illustrates an example flow diagram of a method performed by a secondary base station for forwarding data to a primary base station in accordance with an embodiment of the present invention;

FIG. 7 shows an exemplary simplified structure of a secondary base station corresponding to the method shown in FIG. 6;

8 shows an example flow diagram of a method performed by a primary base station in accordance with an embodiment of the present invention;

FIG. 9 shows an exemplary simplified structure of a primary base station corresponding to the method shown in FIG.

detailed description

The present disclosure is described in detail below in conjunction with the drawings and specific embodiments. It should be noted that the present disclosure should not be limited to the specific embodiments described below. In addition, for the sake of brevity, omitted Detailed descriptions of well-known techniques that are not directly related to the present disclosure are provided to avoid obscuring the understanding of the present disclosure.

Some of the terms referred to in the present invention are described below, and the terms referred to in the present invention are defined herein unless otherwise specified. The present invention takes a dual connection as an example, but the method of the present invention is not limited to a dual connectivity scenario, and those skilled in the art can easily extend to a multi-connection scenario. In addition, the present invention is described by taking LTE, eLTE, NR, and corresponding core network and next-generation core network as an example. It should be noted that the present invention is not limited to the LTE, eLTE, NR, and corresponding core network and next generation. The core network can also be used in other wireless communication systems that evolve, such as 6G wireless communication systems.

In the present invention, a base station that connects a control plane to an EPC or a next-generation core network under dual connectivity is referred to as a primary base station MeNB, and may include one or more of NR MgNB, LTE MeNB, and eLTE MeNB. A base station whose control plane is not connected to the EPC or the next-generation core network (ie, is not the primary base station) but provides transmission resources for user plane data transmission is referred to as a secondary base station SeNB, and may include one or more of NR SgNB, LTE SeNB, and eLTE SeNB. .

The X-Y MCG bearer involved in the present invention refers to a resource in which the MeNB is X, the SeNB is Y, and the radio protocol of the bearer is located in X and is provided by X. The X may be an NR MgNB, an LTE MeNB, or an eLTE MeNB; the Y may be an NR SgNB, an LTE SeNB, or an eLTE SeNB.

The X-Y SCG bearer means that the MeNB is X, the SeNB is Y, and the radio protocol of the bearer is located in Y and utilizes resources provided by Y. The X may be an NR MgNB, an LTE MeNB, or an eLTE MeNB; the Y may be an NR SgNB, an LTE SeNB, or an eLTE SeNB.

The XY MCG split bearer means that the primary base station is X, the secondary base station is Y, and the radio protocol of the bearer is located in X and Y, and the user plane data of the EPC or the next-generation core network ends at X but is utilized at the same time. Resources provided by X and Y. The X may be an NR MgNB, an LTE MeNB, or an eLTE MeNB; the Y may be an NR SgNB, an LTE SeNB, or an eLTE SeNB.

The XY SCG split bearer means that the primary base station is X, the secondary base station is Y, and the radio protocol of the bearer is located in X and Y, and the user plane data of the EPC or the next-generation core network terminates at Y but is utilized at the same time. Resources provided by X and Y. The X may be an NR MgNB, an LTE MeNB, or an eLTE MeNB; the Y may be an NR SgNB, an LTE SeNB, or an eLTE SeNB.

The X MCG bearer means that the MeNB is X, and the SeNB may be an NR SgNB, an LTE SeNB or an eLTE SeNB. The bearer's radio protocol is located in X and utilizes the resources provided by X. The X may be an NR MgNB, an LTE MeNB, or an eLTE MeNB.

The X SCG bearer refers to the MeNB being X, and the SeNB may be an NR SgNB, an LTE SeNB, or an eLTE SeNB. The radio protocol of the bearer is located in the SeNB and utilizes resources provided by the SeNB. The X may be an NR MgNB, an LTE MeNB, or an eLTE MeNB.

The X MCG split bearer refers to the MeNB being X, and the SeNB may be an NR SgNB, an LTE SeNB, or an eLTE SeNB. The radio protocol of the bearer is located in the X and SeNB, and the user plane data with the EPC or the next generation core network ends at X and utilizes resources provided by the X and SeNB. The X may be an NR MgNB, an LTE MeNB, or an eLTE MeNB.

The X SCG split bearer means that the MeNB is X, and the SeNB may be an NR SgNB, an LTE SeNB or an eLTE SeNB. The radio protocol of the bearer is located in the X and SeNB and utilizes resources provided by the X and SeNB at the same time. The X may be an NR MgNB, an LTE MeNB, or an eLTE MeNB.

NR MCG bearer: may include one or more of NR-eLTE MCG bearer, NR-NR MCG bearer, and NR-LTE MCG bearer.

LTE MCG bearer: may include one or more of LTE-eLTE MCG bearer, LTE-NR MCG bearer, and LTE-LTE MCG bearer.

eLTE MCG bearer: may include one or more of an eLTE-eLTE MCG bearer, an eLTE-NR MCG bearer, and an eLTE-LTE MCG bearer.

NR SCG bearer: may include one or more of an NR-eLTE SCG bearer, an NR-NR SCG bearer, and an NR-LTE SCG bearer.

LTE SCG bearer: may include one or more of LTE-eLTE SCG bearer, LTE-NR SCG bearer, and LTE-LTE SCG bearer.

eLTE SCG bearer: may include one or more of an eLTE-eLTE SCG bearer, an eLTE-NR SCG bearer, and an eLTE-LTE SCG bearer.

NR MCG split bearer: may include one or more of NR-eLTE MCG split bearer, NR-NR MCG split bearer, and NR-LTE MCG split bearer.

LTE MCG split bearer: may include one or more of LTE-eLTE MCG split bearer, LTE-NR MCG split bearer, and LTE-LTE MCG split bearer.

The eLTE MCG split bearer may include one or more of an eLTE-eLTE MCG split bearer, an eLTE-NR MCG split bearer, and an eLTE-LTE MCG split bearer.

NR SCG split bearer: may include one or more of NR-eLTE SCG split bearer, NR-NR SCG split bearer, NR-LTE SCG split bearer.

LTE SCG split bearer: may include one or more of LTE-eLTE SCG split bearer, LTE-NR SCG split bearer, and LTE-LTE SCG split bearer.

The eLTE SCG split bearer may include one or more of an eLTE-eLTE SCG split bearer, an eLTE-NR SCG split bearer, and an eLTE-LTE SCG split bearer.

The MCG bearer in the present invention may include one or more of the following: NR MCG bearer, LTE MCG bearer, eLTE MCG bearer, unless otherwise specified. The SCG bearer may include one or more of the following: an NR SCG bearer, an LTE SCG bearer, and an eLTE SCG bearer. The MCG split bearer may include one or more of the following: an NR MCG split bearer, an LTE MCG split bearer, and an eLTE MCG split bearer. The SCG split bearer may include one or more of the following: an NR SCG split bearer, an LTE SCG split bearer, and an eLTE SCG split bearer.

It is assumed in the present invention that the packet data convergence protocol PDCP entity is an entity that implements data separation and/or aggregation in the MeNB and/or the SeNB, that is, the user plane data is processed by the PDCP entity, and a part of the data is transmitted by using the resources provided by the base station where the PDCP entity is located. Another portion of the data is sent to/from another base station and transmitted using the resources provided by the base station. The names of entities that implement data separation and/or aggregation may be different for different MeNB types (eg, NR MgNB, LTE MeNB, and eLTE MeNB), but are collectively referred to as PDCP entities in the present invention, and the entities may implement data separation. And/or aggregation features. The PDCP-processed downlink data packet is called a PDCP Protocol Data Unit (PDU). Depending on the entity name that implements data separation in NR or eLTE, the data processed by the entity may have different names, but the present invention will They are collectively referred to as PDCP PDUs or generally referred to as user data, both of which are used interchangeably herein. A person skilled in the art may also replace the PDCP PDU with the name according to a specific name.

The primary cell group (MCG) is a group of serving cells associated with the primary base station, and includes one primary cell PCell, and may also include one or more secondary cells SCell. A secondary cell group (SCG) is a group of serving cells associated with a secondary base station, including a PSCell, and may also include one or more SCells. The PCell is a cell operating on a primary carrier frequency, and the UE performs an initial connection establishment process or initiates a connection re-establishment process on the cell or indicates a PCell during the handover process. The PSCell is an SCG cell, and the UE performs a cell that is immediately accessed when performing the SCG change procedure. The SCell is a cell operating on a secondary carrier frequency, and the SCell may be configured after the RRC connection establishment is established and may provide additional radio resources. It should be noted that, in different deployment scenarios or in different wireless communication systems, the naming of the base station, the primary base station, the secondary base station, the cell, the primary cell group, the secondary cell group, the bearer, and the core network may be different, and the present invention is also applicable. Different ways of using different names in different deployment scenarios or different wireless communication systems.

Figures 1 through 4 show schematic diagrams of various types of connection deployment scenarios.

In FIG. 1, an NR base station (NR Node B, abbreviated as gNB. The gNB is a logical node, and the logical node is responsible for wireless transmission/reception in one or more cells to/from the user equipment UE) as a master. The base station (called MgNB), that is, the control plane connection is between the MgNB and the next-generation core network (called NextGen Core). An Enhanced Long Term Evolution (eLTE) base station (referred to as an eLTE eNB) serves as a secondary base station. The user plane data stream is transmitted through the next generation core network through the NR base station and the eLTE eNB; specifically, there are four user plane data transmission modes: mode a1, user plane data is transmitted between the gNB and the next generation core network, and resources provided by the gNB are utilized. (The corresponding data bearer is called NR-eLTE Master Cell Group (MCG) bearer); mode a2, user plane data is transmitted between the eLTE eNB and the next-generation core network and utilizes resources provided by the eLTE eNB (corresponding data) The bearer is called the NR-eLTE Secondary Cell Group (SCG) bearer. In the manner a3, the user plane data is transmitted between the gNB and the next-generation core network, and part of the data is transmitted by using the wireless resource of the gNB, and the other data is transmitted. The interface between the gNB and the eLTE eNB is sent to/from the eLTE eNB and uses the radio resource transmission of the eLTE eNB (the corresponding data bearer is called NR-eLTE MCG split bearer); mode a4, the user plane data is in the eLTE eNB and the next generation core network. Inter-transmission, part of the data is directly transmitted by the radio resource of the eLTE eNB, and another part of the data is sent to/from the NR gNB through the interface between the gNB and the eLTE eNB and utilizes the radio resources of the NR gNB. Transmission (the corresponding data bearer is called NR-eLTE SCG split bearer). In modes a3 and a4, the user plane data utilizes resources provided by the gNB and the eLTE eNB simultaneously via the next generation core network.

In FIG. 2, the primary base station MgNB and the secondary base station SgNB are both gNBs, that is, the control plane connection is performed between the MgNB and the next generation core network, and the user plane data stream is transmitted through the next generation core network through the MgNB and the SgNB. Specifically, there are four types of user plane data transmission methods: mode b1, user plane data is transmitted between the MgNB and the next generation core network and utilized for resource transmission provided by the MgNB (the corresponding data bearer is called NR-NR MCG bearer); mode b2 User plane data is transmitted between the SgNB and the next generation core network and utilizes resources provided by the secondary base station SgNB (the corresponding data bearer is called NR-NR SCG bearer); mode b3, user plane data is transmitted between the MgNB and the next generation core network And a part of the data is transmitted by using the radio resource of the primary base station MgNB, and another part of the data is sent to/from the SgNB through the interface between the primary base station MgNB and the secondary base station SgNB and transmitted by using the wireless resource of the SgNB (the corresponding data bearer is called NR-NR). MCG separation bearer). In mode b4, the user plane data is transmitted between the SgNB and the next generation core network, part of the data is directly transmitted by the SgNB wireless resource, and the other data is sent to/from the MgNB through the interface between the SgNB and the MgNB and transmitted by using the wireless resource of the MgNB ( The corresponding data bearer is called NR-NR SCG split bearer). In modes b3 and b4, the user plane data is simultaneously transmitted by the resources provided by the MgNB and the SgNB via the next generation core network.

In FIG. 3, a long-term evolved base station LTE eNB is used as a primary base station (referred to as an LTE MeNB), that is, a control plane connection is performed between an LTE eNB and a core network (referred to as an EPC). The gNB acts as a secondary base station. The user plane data stream is transmitted via the EPC through the gNB and the LTE eNB. Specifically, there are four types of user plane data transmission modes: mode c1, user plane data is transmitted between the LTE eNB and the EPC, and resources provided by the LTE eNB are used (the corresponding data bearer is called LTE-NR MCG bearer); mode c2, The user plane data is transmitted between the gNB and the EPC, and uses the resource transmission provided by the gNB (the corresponding data bearer is called LTE-NR SCG bearer); in the manner c3, the user plane data is transmitted between the LTE eNB and the EPC, and part of the data utilizes LTE. The eNB's radio resource transmission, the other part of the data is sent to/from the gNB through the interface between the gNB and the LTE eNB and transmitted by the gNB's radio resources (the corresponding data bearer is called the LTE-NR MCG split bearer). In the mode c4, the user plane data is transmitted between the gNB and the EPC, part of the data is directly transmitted by using the radio resource of the gNB, and the other part is transmitted to/from the LTE eNB through the interface between the gNB and the LTE eNB, and the radio resource is transmitted by using the LTE eNB ( The corresponding data bearer is called LTE-NR SCG split bearer). In modes c3 and c4, the user plane data is simultaneously transmitted by the resources provided by the gNB and the LTE eNB via the EPC.

In FIG. 4, the eLTE eNB functions as a primary base station (referred to as an eLTE MeNB), that is, a control plane connection is performed between the eLTE eNB and the next generation core network. The gNB acts as a secondary base station. The user plane data stream is transmitted through the next generation core network through the gNB and the eLTE eNB. Specifically, there are four types of user plane data transmission modes: mode d1, user plane data is transmitted between the eLTE eNB and the next generation core network, and resources provided by the eLTE eNB are used (the corresponding data bearer is called an eLTE-NR MCG bearer); D2, user plane data is transmitted between the gNB and the next generation core network and utilizes resources provided by the gNB (the corresponding data bearer is called eLTE-NR SCG bearer); mode d3, user plane data is transmitted between the eLTE eNB and the next generation core network And a part of the data is transmitted by using the radio resource of the eLTE eNB, and another part of the data is sent to/from the gNB through the interface between the gNB and the eLTE eNB and transmitted by using the radio resource of the gNB (the corresponding data bearer is called the eLTE-NR MCG split bearer) . In the mode d4, the user plane data is transmitted between the gNB and the next generation core network, and part of the data is directly transmitted by using the radio resource of the gNB, and the other part is sent to/from the eLTE eNB through the interface between the gNB and the eLTE eNB and using the eLTE eNB. Radio resource transmission (the corresponding data bearer is called eLTE-NR SCG split bearer). In modes d3 and d4, the user plane data is simultaneously transmitted by the resources provided by the gNB and the eLTE eNB via the next generation core network.

In the user plane data transmission manners a4, b4, c4, and d4 of the dual connectivity deployment scenario, the user plane data is transmitted between the secondary base station and the core network or the next generation core network, and part of the data is transmitted by using the wireless resources of the secondary base station, and another A part of the data is sent to/from the primary base station through the interface between the secondary base station and the primary base station, and is transmitted by using resources of the primary base station. If the downlink data transmission is performed by using the method, data bearer reconfiguration is required, for example, the SCG is separated by a bearer (may be LTE-NR or eLTE-NR or NR-LTE or NR-eLTE or LTE-eLTE or eLTE-LTE SCG) The split bearer is reconfigured as an MCG bearer (LTE-NR or eLTE-NR or NR-LTE or NR-eLTE or LTE-eLTE or eLTE-LTE MCG bearer). The data forwarding operation may be performed according to the bearer configuration, and the data forwarding operation may adopt a data forwarding process when switching. Part of the data has been forwarded to the primary base station before the reconfigured SCG split bearer is the MCG bearer. Therefore, how to prevent the secondary base station from forwarding data that has been successfully transmitted to the primary base station but the user equipment UE has not confirmed the reception success is a problem to be solved.

The technical solution of the present invention has been made for this purpose.

Some embodiments of the present invention provide a method performed by a secondary base station for forwarding data to a primary base station, where the secondary base station and the primary base station cooperate to transmit data to the user equipment, for example, by using FIG. The dual connectivity deployment shown in Figure 4 cooperates to send data. As shown in FIG. 6, the method includes: Step 610: Receive a downlink data transmission status frame from a primary base station; Step 620: Forward, to the primary base station, data to be sent to the user equipment according to the received downlink data transmission status frame. The downlink data transmission status frame is used to notify the secondary base station of data that the primary base station has correctly received or not received and/or data that has been successfully forwarded to the user equipment.

In some examples, the downlink data transmission status frame can include at least one of the following:

(a) a maximum sequence number of user data received from the secondary base station and successfully transmitted to the user equipment in order;

(b) the expected buffer size of the corresponding radio access bearer;

(c) a minimum expected buffer size for the user equipment;

(d) a data packet that the primary base station considers to be lost and not included in the downlink data transmission status frame transmitted to the secondary base station;

(e) An indication of whether the current downlink data transmission status frame is the last downlink data transmission status frame.

Whether the inclusion of the content (d) depends on a preset condition when it is decided not to use the downlink user data transmission process or to use the resources of the primary base station for downlink data transmission or the secondary base station to change from one secondary base station to another secondary base station. The preset condition may be determined by the MeNB implementation.

In some examples, if the current downlink data transmission status frame is the last downlink status report, the downlink data transmission status frame may also include the d).

In some examples, the preset condition is whether the reconfigured security information is the same as the security information of the secondary base station. In this case, when the reconfigured security information is different from the security information of the secondary base station, the content (d) may not be included in the downlink data transmission status frame. In contrast, when the reconfigured security information is the same as the security information of the secondary base station, the content (d) may be included in the downlink data transmission status frame.

In some examples, the preset condition is whether the processing capability of the primary base station is sufficient to process user data received from the secondary base station or the one secondary base station. When the processing capability of the primary base station is insufficient to process the user data received from the secondary base station or the one secondary base station, the content (d) may not be included in the downlink data transmission status frame. In contrast, when the processing capability of the primary base station is sufficient to process user data received from the secondary base station or the one secondary base station, the downlink data transmission status frame includes content (d).

In some examples, forwarding to the primary base station based on the received downlink data transmission status frame The data sent by the user equipment includes: when the coordinated mode of the secondary base station and the primary base station is changed from the secondary cell group to the primary cell group bearer, or when the coordinated mode of the secondary base station and the primary base station is separated from a secondary cell group, the bearer is reconfigured to When the other auxiliary cell group separates the bearer, when the received downlink data transmission status frame includes the content d), the downlink user data whose sequence number is not successfully received by the user equipment is successfully forwarded to the primary base station, where the The user data of the primary base station, and when the received downlink data transmission status frame does not contain the content d), forwards to the primary base station all downlink user data whose sequence number is not successfully received by the user equipment, and the inclusion has been sent to the primary User data of the base station.

A secondary base station is also provided in accordance with some embodiments of the present invention. The secondary base station is used to forward data to the primary base station. As shown in FIG. 7, the secondary base station includes: a receiving unit 710, configured to receive a downlink data transmission status frame from the primary base station; and a forwarding unit 720, configured to forward, to the primary base station, a user equipment to be forwarded according to the received downlink data transmission status frame. The transmitted data, wherein the downlink data transmission status frame is used to inform the secondary base station of data that the primary base station has correctly received or not received and/or data that has been successfully forwarded to the user equipment.

In some examples, the downlink data transmission status frame includes at least one of the following:

(b) the expected buffer size of the corresponding radio access bearer;

(c) a minimum expected buffer size for the user equipment;

In some examples, the preset condition is whether the reconfigured security information is the same as the security information of the secondary base station. In this case, when the reconfigured security information is different from the security information of the secondary base station, the content (d) may not be included in the downlink data transmission status frame. In contrast, in reconfiguration When the security information is the same as the security information of the secondary base station, the content (d) may be included in the downlink data transmission status frame.

In some examples, the forwarding unit 720 is further configured to: when the coordinated mode of the secondary base station and the primary base station changes from the secondary cell group to the primary cell group bearer, or when the coordinated mode of the secondary base station and the primary base station is from a secondary cell group When the split bearer reconfiguration is another auxiliary cell group split bearer, when the received downlink data transmission status frame includes the content d), the downlink user data whose sequence number is not successfully received by the user equipment is successfully forwarded to the primary base station, where And including the user data that has been sent to the primary base station, and when the received downlink data transmission status frame does not include the content d), forwarding, to the primary base station, all downlink user data whose sequence number is not successfully received by the user equipment, including User data that has been sent to the primary base station.

In addition, the secondary base station may also include other units/modules not shown in FIG. 7, such as an operation and maintenance system, etc., and details are not described herein again.

Some embodiments in accordance with the present invention also provide a method performed by a primary base station in which a primary base station and a secondary base station cooperate to transmit data to a user equipment, such as through the dual connectivity deployment illustrated in Figures 1-4. As shown in FIG. 8, the method includes: Step 810: Generate a downlink data transmission status frame, where the downlink data transmission status frame is used to notify the secondary base station that the primary base station has correctly received or not received data and/or has successfully forwarded the data to the secondary base station. Data of the user equipment; step 820, transmitting a downlink data transmission status frame to the secondary base station; and step 830, receiving data sent by the secondary base station based on the downlink data transmission status frame.

(b) the expected buffer size of the corresponding radio access bearer;

(c) a minimum expected buffer size for the user equipment;

(d) the downlink data that the primary base station considers to be lost and not included in the secondary base station Transmit the data packets in the status frame;

When it is decided that the downlink user data transmission process is no longer used or the downlink data transmission is no longer used by the primary base station or the secondary base station changes from one secondary base station to another secondary base station, whether or not the content (d) is included is determined according to a preset condition. The preset condition may be determined by the MeNB implementation.

In some examples, the preset condition is whether the reconfigured security information is the same as the security information of the secondary base station. In this case, when the reconfigured security information is different from the security information of the secondary base station, the content (d) is not included in the downlink data transmission status frame. In contrast, when the reconfigured security information is the same as the security information of the secondary base station, the content (d) is included in the downlink data transmission status frame.

In some examples, the preset condition is whether the processing capability of the primary base station is sufficient to process user data received from the secondary base station or the one secondary base station. When the processing capability of the primary base station is insufficient to process the user data received from the secondary base station or the one secondary base station, the content (d) is not included in the downlink data transmission status frame. In contrast, when the processing capability of the primary base station is sufficient to process user data received from the secondary base station or the one secondary base station, the content (d) is included in the downlink data transmission status frame.

In some examples, when the content d) is included in the last downlink data transmission status frame, the primary base station may encapsulate the user data received from the secondary base station according to the new Packet Data Convergence Protocol (PDCP) configuration information and direct it to the user equipment. send. In still other examples, when the content d) is included in the last downlink data transmission status frame, the primary base station transmits the user data received from the secondary base station to another secondary base station to be used by the other secondary base station. Send to the user device.

A primary base station is also provided in accordance with some embodiments of the present invention. The primary base station and the secondary base station cooperate to transmit data to the user equipment. As shown in FIG. 9, the primary base station includes: a status indication generating unit 910, configured to generate a downlink data transmission status frame, where the downlink data transmission status frame is used to notify the secondary base station of data that the primary base station has correctly received or not received and/or Or the data that has been successfully forwarded to the user equipment; the sending unit 920, configured to send a downlink data transmission status frame to the secondary base station; and the receiving unit 930, configured to receive data sent by the secondary base station according to the downlink data transmission status frame.

(b) the expected buffer size of the corresponding radio access bearer;

(c) a minimum expected buffer size for the user equipment;

(d) the data packet that the primary base station considers to be lost and not included in the downlink data transmission status frame transmitted to the secondary base station;

When it is determined that the downlink user data transmission process is no longer used or the downlink data transmission is not performed by using the resources of the primary base station or the secondary base station changes from one secondary base station to another secondary base station, the status indication generating unit is configured according to the preset. The condition determines whether or not the content (d) is included. The preset condition may be determined by the MeNB implementation.

In some examples, the preset condition is whether the reconfigured security information is the same as the security information of the secondary base station. In this case, when the reconfigured security information is different from the security information of the secondary base station, the status indication generating unit 910 does not include the content (d) in the downlink data transmission status frame. In contrast, when the reconfigured security information is the same as the security information of the secondary base station, the status indication generating unit 910 includes the content (d) in the downlink data transmission status frame.

In some examples, the preset condition is whether the processing capability of the primary base station is sufficient to process user data received from the secondary base station or the one secondary base station. When the processing capability of the primary base station is insufficient to process the user data received from the secondary base station or the one secondary base station, the status indication generating unit 910 does not include the content (d) in the downlink data transmission status frame. In contrast, when the processing capability of the primary base station is sufficient to process user data received from the secondary base station or the one secondary base station, the status indication generating unit 910 includes the content (d) in the downlink data transmission status frame.

In some examples, the sending unit 920 is further configured to: when the content d) is included in the last downlink data transmission status frame, encapsulate the user data received from the secondary base station according to the new packet data convergence protocol configuration information, and provide the user data to the user. When the device transmits, or when the content d) is included in the last downlink data transmission status frame, the user data received from the secondary base station is sent to another secondary base station to be transmitted by the other secondary base station to the user equipment.

The primary base station may further include a storage unit 940 for storing data or required data generated by each unit/module in the primary base station when performing its operations.

In addition, the main base station may also include other units/modules not shown in FIG. 9, such as an operation and maintenance system, etc., and details are not described herein again.

It should be noted that although an exemplary simplified block diagram of a secondary base station and a primary base station according to an embodiment of the present invention is shown in blocks in FIGS. 7 and 9, the method described in the present invention may also be in a processing device ( Executed, for example, in a central processing unit (CPU) or any other suitable processing device. For example, program instructions for performing the methods of the present invention may be stored in a memory and executed by a processing device.

FIG. 5 illustrates a radio protocol layer 2 entity involved in an LTE dual connectivity deployment manner, including a PDCP entity, a radio link control RLC entity, and a medium access control MAC entity. The interface between the MeNB and the SeNB is denoted as X2, and the control plane data and the user plane data may be transmitted on the same interface or transmitted on different interfaces. The functions provided by the PDCP entity include assigning sequence number SN, header compression ROHC, integrity protection (control plane only), encryption, adding PDCP headers, routing for data from the EPC. It should be noted that not all bearers require all the functions provided by the PDCP entity. For example, the signaling bearer does not require routing, the data bearer does not require integrity protection, and the split bearer in the dual connectivity deployment does not require head compression. The functions provided by the RLC entity include: transmission data buffering, segmentation/cascading, retransmission, addition of RLC headers, and the like. The functions provided by the RLC entity are also different depending on the configured RLC mode. For example, the RLC acknowledgment mode (RLC UM) has no retransmission function, and the RLC acknowledgment mode (RLC AM) has a retransmission function. The functions provided by the MAC entity include: multiplexing/demultiplexing, logical channel priority (for uplink only), random access, HARQ, and so on. It should be noted that in the dual connectivity, the UE may include two MACs, one corresponding to the MCG and the other corresponding to the SCG.

In the NR and/or eLTE communication system, the radio protocol layer also needs all or part of the functions provided by the PDCP entity, the RLC entity, and the MAC entity, and may also include other functions such as a PDCP entity, an RLC entity, and a MAC entity, such as a light beam (Bean). ) Management functions. The combination of functions and the layering manner may also be different from LTE. For example, in NR, the reordering function of the PDCP entity and the RLC entity may be integrated, provided only in one entity, for example, providing reordering function only in PDCP. For convenience of description, the present invention assumes that the radio protocol layer 2 of the NR and/or eLTE communication system also includes PDCP, RLC, MAC. It should be noted that the present invention is not limited The combination and layering manner of the functions provided by the PDCP entity, the RLC entity, and the MAC entity.

In the hybrid dual-connection deployment mode (the primary base station and the secondary base station are different types of base stations), the PDCP entity, the RLC entity, and the MAC entity of the LTE are respectively marked as an LTE PDCP entity, an LTE RLC entity, an LTE MAC entity, and a PDCP entity of the eLTE, The RLC entity and the MAC entity are respectively marked as an eLTE PDCP entity, an eLTE RLC entity, and an eLTE MAC entity; the PDCP entity, the RLC entity, and the MAC entity of the NR are respectively marked as an NR PDCP entity, an NR RLC entity, and an NR MAC entity; In the embodiments, if the entity type of the PDCP entity, the RLC entity, and the MAC entity is not explicitly indicated, that is, the PDCP entity, the RLC entity, and the MAC entity are not corresponding to the LTE, eLTE, and NR entities, The type of MeNB and SeNB can infer the corresponding PDCP entity, RLC entity, and MAC entity type.

The following describes an embodiment of transmitting a downlink data transmission status frame between the MeNB and the SeNB.

In the existing LTE dual connectivity (both the primary base station and the secondary base station are LTE eNBs), the Downlink Data Delivery Status procedure is used by the SeNB to provide feedback to the MeNB, so that the MeNB controls each E-RAB (enhanced type). The radio access bearer flows through the downlink user data stream of the SeNB.

When the SeNB decides to trigger feedback on the downlink data transmission process, the feedback (referred to as a downlink data transmission status frame) includes the following:

1. The maximum sequence number of the user data (the maximum sequence number of the PDCP PDU) received from the MeNB that has been successfully sent to the UE in sequence;

2. The expected buffer size of the corresponding E-RAB (in bytes);

3. The minimum expected buffer size (in bytes) for the corresponding UE;

4. The X2-U packet that the SeNB considers to be lost and not included in the downlink data transmission status frame reported to the MeNB.

If the E-UTRAN deployment decides that the downlink user data transmission procedure is no longer used, the downlink data transmission status frame sent by the SeNB to the MeNB does not include the d). The downlink user data transmission (Transfer of Downlink User Data) procedure is used to provide X2 when transmitting a data packet including a downlink PDCP PDU from a MeNB to an SeNB through an interface (referred to as X2-U) for transmitting data between the MeNB and the SeNB. -U specific serial number information.

In a dual connectivity deployment of any two combinations of NR, LTE, and eLTE, for a SCG split bearer, for example, a downlink data transmission state procedure may be used for the MeNB to provide feedback to the SeNB, such that the SeNB controls each bearer (eg, E-RAB) to flow through. Downstream user data stream of the MeNB. It should be noted that although the technical solution of the present invention is described herein by taking the SCG split bearer as an example, the technical solution of the present invention can also be applied to any dual-connection deployment that needs to transfer user data between, for example, the MeNB and the SeNB.

When the MeNB decides to provide feedback to the SeNB for the downlink data transmission process (the feedback is referred to as a downlink data transmission status frame), the feedback may include one or more of the following:

a) the maximum sequence number of the user data received from the SeNB that has been successfully sent to the UE in sequence (for example, the maximum sequence number of the PDCP PDU);

b) the expected buffer size (in bytes) of the corresponding E-RAB;

c) the minimum expected buffer size (in bytes) for the corresponding UE;

d) Xr-U packets that the MeNB considers to be lost and not included in the downlink data transmission status frame reported to the SeNB.

e) an indication of whether the current downlink data transmission status frame is the last downlink status report (downlink data transmission status frame).

In one embodiment, if the NR (or NR-UTRAN) or E-UTRAN deployment decides that the downlink user data transmission procedure is no longer used (or the SeNB decides to no longer use the resources of the MeNB for downlink data transmission, such as changing or releasing At the time of the SeNB, the downlink data transmission status frame sent by the MeNB to the SeNB may include the d). The MeNB may decide whether to include the d) in the downlink data transmission status frame according to a preset condition. The preset condition may be determined by the MeNB implementation. For example, the MeNB determines whether the reconfigured security information is the same as the security information configured by the SeNB, and if so, includes the d) in the downlink data transmission status frame. If different, the d) is not included in the downlink data transmission status frame. Or the MeNB determines, according to its capability, whether the d) is included in the downlink data transmission status frame; when the MeNB determines that the PDCP PDU received from the SeNB can be processed, the downlink data state process includes the d); when the MeNB determines not to When the PDCP PDU received from the SeNB can be processed, the d) is not included in the downlink data transmission status frame. The MeNB may decide whether to include the d) in the downlink data transmission status frame according to its capability. The downlink user data transmission process is configured to provide Xr-U specific sequence number information when transmitting user data including downlink PDCP PDUs from the SeNB to the MeNB through an interface (referred to as Xr-U) for transmitting data between the MeNB and the SeNB. . The Xr-U specific sequence The number is the serial number assigned by the corresponding eNB.

In another embodiment, when the current downlink data transmission status frame is the last downlink status report, the downlink data transmission status frame may include the d).

In another embodiment, if one SCG split bearer (SeNB) is reconfigured to another SCG split bearer (SeNB), the downlink data transmission status frame sent by the MeNB to the source SeNB (ie, the SeNB before the change) may be Contains the d). The MeNB determines whether to include the d) in the downlink data transmission status frame according to a preset condition. The preset condition may be determined by the MeNB implementation. For example, the MeNB determines whether the reconfigured security information is the same as the security information configured by the source SeNB, and if so, includes the d) in the downlink data transmission status frame. If different, the d) is not included in the downlink data transmission status frame. Or the MeNB determines, according to its capability, whether the d) is included in the downlink data transmission status frame; and when the MeNB determines that the PDCP PDU received from the source SeNB can be processed, the d) is included in the downlink data transmission status frame; When the MeNB determines that the PDCP PDU received from the source SeNB cannot be processed, the d) is not included in the downlink data transmission status frame. The MeNB may decide whether to include the d) in the downlink data transmission status frame according to its capability.

In another embodiment, if the SCG split bearer is reconfigured as an MCG bearer, the downlink data transmission status frame sent by the MeNB to the SeNB may include the d). The MeNB may decide whether to include the d) in the downlink data transmission status frame according to a predefined condition. For example, the MeNB determines whether the reconfigured security information is the same as the security information configured by the source SeNB, and if so, includes the d) in the downlink data transmission status frame. If different, the d) is not included in the downlink data transmission status frame. Or the MeNB determines, according to its capability, whether the d) is included in the downlink data transmission status frame; and when the MeNB determines that the PDCP PDU received from the source SeNB can be processed, the d) is included in the downlink data transmission status frame; When the MeNB determines that the PDCP PDU received from the source SeNB cannot be processed, the d) is not included in the downlink data transmission status frame. The MeNB may decide whether to include the d) in the downlink data transmission status frame according to its capability.

It should be noted that, in the present invention, the content included in the downlink data transmission status frame is not limited to the contents defined by 1) to 5), and may include other contents. Its role at least includes the MeNB providing feedback to the SeNB to inform the SeNB that it has correctly received or not received data and/or data that has been successfully forwarded to the UE (ie, data that the UE has successfully received).

The following describes an embodiment in which the SeNB forwards data to the MeNB.

In a dual connectivity deployment scenario, when SCG split bearer reconfiguration is MCG bearer and/or SCG bearer reconfiguration is MCG bearer and/or MCG bearer reconfiguration is SCG bearer and/or MCG bearer reconfiguration is SCG split bearer/reconfiguration When the SCG separate bearer (that is, reconfigure one SCG bearer to another SCG bearer), etc., data forwarding may be required. The following describes the technical solution of the present invention by taking some bearer reconfiguration as an example, but it should be understood that the present invention can be applied to any other situation where data needs to be forwarded between different base stations. The data forwarding process may adopt a data forwarding process defined in the handover process. The behavior of the eNB that forwards the data is the same as the source eNB defined in the handover procedure; the behavior of the eNB receiving the forwarded data is the same as the target eNB defined in the handover procedure.

In one embodiment, the RLC acknowledgement mode (RLC AM) is configured for the SCG split bearer and/or the MCG split bearer, ie the RLC layer is configured to provide reliable data transmission (the data sink provides feedback to the data sender).

In one embodiment, the NR or E-UTEAN configuration configures the ROHC (or configuration reordering timer t-Reordering) for the UE, but does not include separate bearers (eg, MCG split bearers, SCG split bearers) and reconfigures the split bearers to MCG bearer. The primary base station and the secondary base station of the split bearer may be a gNB, an LTE eNB, and an eLTE eNB. The reordering timer is used to detect whether a PDCP PDU is lost.

In an embodiment, when the SCG split bearer is reconfigured as an MCG bearer, the SeNB forwards all downlink PDCCH SDUs that are not successfully acknowledged by the UE to the MeNB (the forwarded data may also include from the core network or the next generation). The data of the core network that has not been assigned the PDCP SN), but does not forward the data that has been sent to the MeNB. The data that has been sent to the MeNB may be data that has been successfully received by the MeNB but has not been successfully received by the UE. For example, when the SCG split bearer is reconfigured as an MCG bearer, the MeNB reports to the SeNB the data it has successfully received or the lost data in the downlink data transmission status frame. The SeNB may determine whether it is necessary to forward data that has been transmitted to the MeNB according to whether the downlink data transmission status frame from the MeNB includes a report of data that has been successfully received or lost data. If the downlink data transmission status frame from the MeNB does not include a report of data or lost data that has been successfully received but has not been successfully acknowledged by the UE, the SeNB forwards the number that has been transmitted to the MeNB. according to. If the downlink data transmission status frame from the MeNB contains data that has been successfully received but has not been acknowledged by the UE to successfully receive data or lost data, the SeNB does not forward data that the MeNB has successfully received. For example, if the downlink data transmission status frame from the MeNB includes d), the SeNB does not forward the data that the MeNB has successfully received. If the downlink data transmission status frame from the MeNB does not include d), the SeNB forwards the data that the MeNB has successfully received. Alternatively, when the SCG split bearer is reconfigured as an MCG bearer, the MeNB may indicate, by, for example, an indication that the SeNB needs to forward data that has been sent to the MeNB. Of course, other embodiments of the invention may be applied to other indications.

In another embodiment, when the SCG split bearer is reconfigured (the one SCG split bearer is configured as another SCG split bearer, ie, the MeNB is unchanged, the SeNB changes), the source SeNB not confirms that all SNs are successfully received by the UE. The downlink PDCP SDU is forwarded to the MeNB (the forwarded data may also include data from the core network or the next generation core network that has not been allocated PDCP SN), but does not forward data that has been sent to the MeNB. The data that has been sent to the MeNB may be data that has been successfully received by the MeNB but has not been successfully received by the UE. For example, when the SCG split bearer is reconfigured as an MCG bearer, the MeNB reports to the source SeNB the data it has successfully received or the lost data in the downlink data transmission status frame. The source SeNB may determine whether it is necessary to forward data that has been transmitted to the MeNB according to whether the downlink data transmission status frame from the MeNB contains a report of data that has been successfully received or lost data. If the downlink data transmission status frame from the MeNB does not contain a report of data or lost data that has been successfully received but has not been successfully acknowledged by the UE, the source SeNB forwards the data that has been transmitted to the MeNB. If the downlink data transmission status frame from the MeNB contains data that has been successfully received but has not been acknowledged by the UE to successfully receive data or lost data, the source SeNB does not forward data that the MeNB has successfully received. For example, if the downlink data transmission status frame from the MeNB includes d), the source SeNB does not forward the data that the MeNB has successfully received. If the downlink data transmission status frame from the MeNB does not include d), the source SeNB forwards the data that the MeNB has successfully received. Alternatively, when the SCG split bearer is reconfigured as an MCG bearer, the MeNB may indicate, by, for example, an indication that the SeNB needs to forward data that has been sent to the MeNB. Of course, other embodiments of the invention may be applied to other indications.

In another embodiment, when the MCG bearer is reconfigured as an SCG split bearer, data (including PDCP SDUs and/or PDCP PDUs) stored in the MeNB buffer that has not been successfully acknowledged by the UE may not be forwarded to the SeNB.

The following describes the processing procedure of the MeNB for locally saved data that has not been acknowledged by the UE to be successfully received.

In an embodiment, if the MeNB includes the d) in the last downlink data transmission status frame, the MeNB receives the user data that is received from the SeNB (ie, the data saved in the buffer area has not been sent to the UE and/or has not been confirmed by the UE. Receive successful data. Perform regular data processing and encapsulate it according to the new PDCP configuration information and send it to the user equipment.

In another embodiment, if the MeNB includes the d) in the last downlink data transmission status frame, the MeNB will receive the user data from the SeNB (ie, the UE saved in the buffer area has not been sent to the UE and/or has not been UE yet). The data indicating that the reception is successful is forwarded to another SeNB and carries an indication identifier in the forwarded data packet, the indication identifier being used to inform the PDCP SDU of the current data of the other SeNB or the PDCP PDU. The another SeNB may directly forward the PDCP PDU from the MeNB to the UE or process it and encapsulate it according to the new PDCP configuration information, and then send the packet to the UE.

The following describes an embodiment in which the MeNB processes the security information configured by the SeNB for the UE.

In an embodiment, when the MeNB receives the security information configured by the SeNB for the UE, the MeNB locally saves the security information configured by the SeNB for the UE.

In another embodiment, when the SCG split bearer is reconfigured as an MCG bearer and/or a reconfigured SCG bearer and/or an MCG bearer is reconfigured as an SCG split bearer, the SeNB sends the SeNB the security information configured by the SeNB for the UE. For example, the security information configured by the SeNB for the UE is carried in a SN Status Transfer message or other message or a newly defined message.

It should be noted that, in describing the foregoing embodiments, the present invention does not specifically specify the primary base station and the secondary base station type. The present invention is applicable to the primary base station, which may be an LTE eNB and/or an eLTE eNB and/or a gNB. The secondary base station may be deployed in any combination of the LTE eNB and/or the eLTE eNB and/or the gNB, and is also applicable to other dual connectivity deployments. Scene, such as 6G. The terminology used may vary in different communication systems, but the above process still applies.

The program running on the device according to the present invention may be a program that causes a computer to implement the functions of the embodiments of the present invention by controlling a central processing unit (CPU). The program or information processed by the program may be temporarily stored in a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memory system.

A program for realizing the functions of the embodiments of the present invention can be recorded on a computer readable recording medium. The corresponding functions can be realized by causing a computer system to read programs recorded on the recording medium and execute the programs. The so-called "computer system" herein may be a computer system embedded in the device, and may include an operating system or hardware (such as a peripheral device). The "computer readable recording medium" may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a recording medium of a short-term dynamic storage program, or any other recording medium readable by a computer.

The various features or functional blocks of the apparatus used in the above embodiments may be implemented or executed by circuitry (e.g., monolithic or multi-chip integrated circuits). Circuitry designed to perform the functions described in this specification can include general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, discrete Gate or transistor logic, discrete hardware components, or any combination of the above. A general purpose processor may be a microprocessor or any existing processor, controller, microcontroller, or state machine. The above circuit may be a digital circuit or an analog circuit. One or more embodiments of the present invention may also be implemented using these new integrated circuit technologies in the context of new integrated circuit technologies that have replaced existing integrated circuits due to advances in semiconductor technology.

Further, the present invention is not limited to the above embodiment. Although various examples of the embodiments have been described, the invention is not limited thereto. Fixed or non-mobile electronic devices installed indoors or outdoors can be used as terminal devices or communication devices such as AV devices, kitchen devices, cleaning devices, air conditioners, office equipment, vending machines, and other home appliances.

As above, the embodiments of the present invention have been described in detail with reference to the accompanying drawings. However, the specific structure is not limited to the above embodiments, and the present invention also includes any design modifications not departing from the gist of the present invention. In addition, various modifications may be made to the invention within the scope of the claims, and the embodiments obtained by appropriately combining the technical means disclosed in the different embodiments are also included in the technical scope of the present invention. Further, the components having the same effects described in the above embodiments may be substituted for each other.

Claims

A method for forwarding data to a primary base station, where the secondary base station and the primary base station cooperate to send data to a user equipment, where the method includes:

Receiving a downlink data transmission status frame from the primary base station;

Forwarding, to the primary base station, data to be sent to the user equipment according to the received downlink data transmission status frame,

The downlink data transmission status frame is used to notify the secondary base station of data that the primary base station has correctly received or not received and/or data that has been successfully forwarded to the user equipment.
The method of claim 1, wherein the downlink data transmission status frame comprises at least one of the following:

(a) a maximum sequence number of user data received from the secondary base station and successfully transmitted to the user equipment in order;

(b) the expected buffer size of the corresponding radio access bearer;

(c) a minimum expected buffer size for the user equipment;

(d) the data packet that the primary base station considers to be lost and not included in the downlink data transmission status frame transmitted to the secondary base station;

(e) An indication of whether the current downlink data transmission status frame is the last downlink data transmission status frame.
The method of claim 2, wherein the content (d) is included when the last downlink data transmission status frame is transmitted.
The method according to claim 2, wherein the downlink data transmission process is no longer used or the resources of the primary base station are no longer used for downlink data transmission or the secondary base station is changed from one secondary base station to another secondary base station. Whether or not the content (d) is included depends on the preset conditions.
The method according to any one of claims 1 to 4, wherein the preset condition is whether the reconfigured security information is the same as the security information of the secondary base station;

When the reconfigured security information is different from the security information of the secondary base station, the downlink data transmission status frame does not include the content (d);

When the reconfigured security information is the same as the security information of the secondary base station, the downlink data transmission status frame includes content (d).
The method according to any one of claims 1 to 4, wherein the predetermined condition is whether a processing capability of the primary base station is sufficient to process user data received from the secondary base station or the one secondary base station;

When the processing capability of the primary base station is insufficient to process user data received from the secondary base station or the one secondary base station, content (d) is not included in the downlink data transmission status frame;

When the processing capability of the primary base station is sufficient to process user data received from the secondary base station or the one secondary base station, the downlink data transmission status frame includes content (d).
The method according to any one of claims 1 to 4, wherein forwarding data to be transmitted to the user equipment to the primary base station according to the received downlink data transmission status frame comprises:

When the coordinated mode of the secondary base station and the primary base station changes from a secondary cell group to a primary cell group bearer, or when the coordinated mode of the secondary base station and the primary base station separates bearer reconfiguration from a secondary cell group When separating bearers for another auxiliary cell group:

When the received downlink data transmission status frame includes the content d), forwarding, to the primary base station, all downlink user data whose sequence number is not successfully received by the user equipment, and does not include the user that has been sent to the primary base station. Data, and

When the received downlink data transmission status frame does not include the content d), forwarding, to the primary base station, all downlink user data whose sequence number is not successfully received by the user equipment, including the user that has been sent to the primary base station data.
A secondary base station, configured to forward data to a primary base station, where the secondary base station includes:

a receiving unit, configured to receive a downlink data transmission status frame from the primary base station;

a forwarding unit, configured to forward, to the primary base station, data to be sent to the user equipment according to the received downlink data transmission status frame, and

The downlink data transmission status frame is used to notify the secondary base station of data that the primary base station has correctly received or not received and/or data that has been successfully forwarded to the user equipment.
The secondary base station according to claim 8, wherein the downlink data transmission status frame comprises at least one of the following:

(a) a maximum sequence number of user data received from the secondary base station and successfully transmitted to the user equipment in order;

(b) the expected buffer size of the corresponding radio access bearer;

(c) a minimum expected buffer size for the user equipment;

(d) the data packet that the primary base station considers to be lost and not included in the downlink data transmission status frame transmitted to the secondary base station;

(e) An indication of whether the current downlink data transmission status frame is the last downlink data transmission status frame.
The secondary base station according to claim 9, wherein the content (d) is included when the last downlink data transmission status frame is transmitted.
The secondary base station according to claim 9, wherein the determining whether the downlink user data transmission process is no longer used or the resource of the primary base station is no longer used for downlink data transmission or the secondary base station changes from one secondary base station to another auxiliary network Whether or not the content (d) is included in the base station depends on a preset condition.
The secondary base station according to any one of claims 8 to 11, wherein the preset condition is whether the reconfigured security information is the same as the security information of the secondary base station;

When the reconfigured security information is different from the security information of the secondary base station, the downlink data transmission status frame does not include the content (d);

When the reconfigured security information is the same as the security information of the secondary base station, the downlink data transmission status frame includes content (d).
The secondary base station according to any one of claims 8 to 11, wherein the preset condition is whether a processing capability of the primary base station is sufficient to process user data received from the secondary base station or the one secondary base station ;

When the processing capability of the primary base station is insufficient to process user data received from the secondary base station or the one secondary base station, content (d) is not included in the downlink data transmission status frame;

When the processing capability of the primary base station is sufficient to process user data received from the secondary base station or the one secondary base station, the downlink data transmission status frame includes content (d).
The secondary base station according to any one of claims 8 to 11, wherein the forwarding unit is further configured to:

When the coordinated mode of the secondary base station and the primary base station changes from a secondary cell group to a primary cell group bearer, or when the coordinated mode of the secondary base station and the primary base station separates bearer reconfiguration from a secondary cell group When separating bearers for another auxiliary cell group:

When the content d) is included in the received downlink data transmission status frame, the primary base is The station forwards all downlink user data whose serial number is not successfully received by the user equipment, and does not include user data that has been sent to the primary base station, and

When the received downlink data transmission status frame does not include the content d), forwarding, to the primary base station, all downlink user data whose sequence number is not successfully received by the user equipment, including the user that has been sent to the primary base station data.
A method performed by a primary base station, where the primary base station and the secondary base station cooperate to send data to the user equipment, where the method includes:

Generating a downlink data transmission status frame, where the downlink data transmission status frame is used to notify the secondary base station of data that the primary base station has correctly received or not received and/or data that has been successfully forwarded to the user equipment;

Transmitting the downlink data transmission status frame to the secondary base station;

Receiving data sent by the secondary base station based on the downlink data transmission status frame.
The method of claim 15, wherein the downlink data transmission status frame comprises at least one of the following:

(a) a maximum sequence number of user data received from the secondary base station and successfully transmitted to the user equipment in order;

(b) the expected buffer size of the corresponding radio access bearer;

(c) a minimum expected buffer size for the user equipment;

(d) the data packet that the primary base station considers to be lost and not included in the downlink data transmission status frame transmitted to the secondary base station;

(e) An indication of whether the current downlink data transmission status frame is the last downlink data transmission status frame.
The method of claim 16 wherein the content (d) is included when the last downlink data transmission status frame is transmitted.
The method according to claim 16, wherein the downlink data transmission process is no longer used or the resources of the primary base station are no longer used for downlink data transmission or the secondary base station is changed from one secondary base station to another secondary base station. When the content (d) is included according to the preset condition.
The method according to any one of claims 15 to 18, wherein the preset condition is whether the reconfigured security information is the same as the security information of the secondary base station;

When the reconfigured security information is different from the security information of the secondary base station, the content (d) is not included in the downlink data transmission status frame;

When the reconfigured security information is the same as the security information of the secondary base station, the content (d) is included in the downlink data transmission status frame.
The method according to any one of claims 15 to 18, wherein the predetermined condition is whether a processing capability of the primary base station is sufficient to process user data received from the secondary base station or the one secondary base station;

When the processing capability of the primary base station is insufficient to process user data received from the secondary base station or the one secondary base station, content (d) is not included in the downlink data transmission status frame;

The content (d) is included in the downlink data transmission status frame when the processing capability of the primary base station is sufficient to process user data received from the secondary base station or the one secondary base station.
A method according to any one of claims 15 to 18, further comprising:

When the content d) is included in the last downlink data transmission status frame, the user data received from the secondary base station is encapsulated according to the new packet data convergence protocol configuration information, and sent to the user equipment, or

When the content d) is included in the last downlink data transmission status frame, user data received from the secondary base station is transmitted to another secondary base station to be transmitted by the other secondary base station to the user equipment.
A primary base station, the primary base station and the secondary base station jointly send data to the user equipment, where the primary base station includes:

a status indication generating unit, configured to generate a downlink data transmission status frame, where the downlink data transmission status frame is used to notify the secondary base station that the primary base station has correctly received or not received data and/or has successfully forwarded to the Data of the user equipment;

a sending unit, configured to send the downlink data transmission status frame to the secondary base station;

And a receiving unit, configured to receive data sent by the secondary base station according to the downlink data transmission status frame.
The primary base station according to claim 22, wherein said downlink data transmission status frame comprises at least one of the following:

(a) a maximum sequence number of user data received from the secondary base station and successfully transmitted to the user equipment in order;

(b) the expected buffer size of the corresponding radio access bearer;

(c) a minimum expected buffer size for the user equipment;

(d) the data packet that the primary base station considers to be lost and not included in the downlink data transmission status frame transmitted to the secondary base station;

(e) An indication of whether the current downlink data transmission status frame is the last downlink data transmission status frame.
The secondary base station according to claim 23, wherein the content (d) is included when the last downlink data transmission status frame is transmitted.
The primary base station according to claim 23, wherein the downlink data transmission process is no longer used or the resource of the primary base station is no longer used for downlink data transmission or the secondary base station is changed from one secondary base station to another auxiliary network. At the time of the base station, the status indication generating unit determines whether to include the content (d) according to a preset condition.
The primary base station according to any one of claims 22 to 25, wherein the preset condition is whether the reconfigured security information is the same as the security information of the secondary base station;

When the reconfigured security information is different from the security information of the secondary base station, the status indication generating unit does not include the content (d) in the downlink data transmission status frame;

When the reconfigured security information is the same as the security information of the secondary base station, the status indication generating unit includes the content (d) in the downlink data transmission status frame.
The primary base station according to any one of claims 22 to 25, wherein the predetermined condition is whether a processing capability of the primary base station is sufficient to process user data received from the secondary base station or the one secondary base station ;

When the processing capability of the primary base station is insufficient to process user data received from the secondary base station or the one secondary base station, the status indication generating unit does not include the content (d) in the downlink data transmission status frame. Medium;

The status indication generating unit includes the content (d) in the downlink data transmission status frame when the processing capability of the primary base station is sufficient to process user data received from the secondary base station or the one secondary base station.
The primary base station according to any one of claims 22 to 25, wherein the transmitting unit is further configured to:

When the content d) is included in the last downlink data transmission status frame, the user data received from the secondary base station is encapsulated according to the new packet data convergence protocol configuration information, and sent to the user equipment, or

When the content d) is included in the last downlink data transmission status frame, to another secondary base station Transmitting user data received from the secondary base station to be transmitted by the another secondary base station to the user equipment.