Patent Description:
In a handover process of a related Long Term Evolution (LTE) system, a target base station determines whether the target base station is capable of accepting all bearers of a User Equipment (UE) in accordance with its load and a radio situation. When it is incapable of accepting all the bearers of the UE, the target base station notifies a source base station of the bearers that are incapable of being accepted through a handover response message, and the source base station needs to deactivate these bearers, so some services are incapable of being supported.

When a same mechanism is adopted in a <NUM>th-Generation (<NUM>) system, some flows may probably be deactivated in the handover process.

A document by <NPL>) discusses the basic principle of QoS handling during handover, including both the scenario where the aGW is involved in the preparation and where the aGW is involved in the completion of the handover.

A further document <CIT> relates to transmit QoS information to a target base station for admitted service flows during the handover operation.

The present invention relates to Quality of Service, QoS, processing methods as defined in the annexed claims, so as to prevent one or more flows from being directly deactivated when a target base station is incapable of meeting a QoS parameter of the one or more flows of a UE.

This invention is set out in the appended set of claims.

A solution of the above technical solutions has following advantages or beneficial effects. A processing procedure may be provided when the target base station is incapable of meeting the QoS requirement. For example, the QoS parameter capable of being accepted by the target base station and recommended with respect to the one or more flows may be carried in the first message, so that the target base station may notify the source base station of the QoS parameter capable of being accepted by the target base station when notifying the source base station that the target base station is incapable of meeting the QoS requirement on the one or more flows of the UE. As a result, it is able to prevent the source base station from directly deactivating the bearers incapable of being accepted by the target base station as compared with the related art, thereby to enable the target base station to support a corresponding service.

In order to illustrate the technical solutions of the present in a clearer manner, the drawings desired for the present disclosure will be described hereinafter briefly. Obviously, the following drawings merely relate to some embodiments of the present disclosure, and based on these drawings, a person skilled in the art may obtain the other drawings without any creative effort. Shapes and sizes of the members in the drawings are for illustrative purposes only, but shall not be used to reflect any actual scale.

The present disclosure will be described hereinafter in conjunction with the drawings and embodiments. It should be appreciated that, the following embodiments are for illustrative purposes only, but shall not be used to limit the scope of the present disclosure. Actually, the embodiments are provided so as to facilitate the understanding of the scope of the present disclosure, and convey the scope of the present disclosure completely to a person skilled in the art. The invention is defined by the attached independent claims. Advantageous embodiments are described in the attached dependent claims. Embodiments and/or examples mentioned in the description that do not fall under the scope of the claims are useful for understanding the invention.

<FIG> shows a bearer model in a LTE system in related art. In the LTE system in related art, a core network takes charge of generating a QoS parameter of an Evolved Radio Access Bearer (E-RAB). There is a one-to-one mapping relationship between air-interface Radio Bearers (RBs) and the E-RABs, so the QoS parameter of the E-RAB generated by the core network is directly adopted as a QoS parameter of the air-interface RB.

The scheme in the embodiments of the present disclosure may be applied to different network deployment structures. For ease of description, two possible network deployment structures for a future mobile communication system will be described hereinafter.

<FIG> shows typical LTE architecture. A plurality of cells is located within the coverage of an evolved Node B (eNB), and each UE in a connected state receives data from or transmits data to a cell via an air interface.

Deployment structure <NUM>: network side nodes include a Central Unit (CUs) and Distributed Units (DUs), and a UE side node includes a UE.

<FIG> shows a possible architecture for a future <NUM> mobile communication system. The network side nodes include a CU and DUs, and a plurality of DUs deployed in a certain region is controlled by one CU. The air-interface transmission is performed between the DUs and the UE via Transmission Reception Points (TRPs). Each UE may be served by one or more TRPs, so as to perform the data transmission.

The scheme in the embodiments of the present disclosure may be applied to the above two types of RAN architecture.

<FIG> shows <NUM> network architecture. The network architecture includes three logic entities, i.e., a CN-C (core network control plane functional entity) at the core network, a CN-U (core network user plane functional entity), and a gNB (a next-generation node B) and an evolved LTE (eLTE) eNB at an access network. An NG-C interface is established between the CN-C and the gNB for the transmission of control plane signaling, and an NG-U interface is established between the CN-U and the gNB for the transmission of user plane data. An Xn interface is established between the gNBs, and the Xn interface may support a control plane function (e.g., Xn-C) and a user plane function (e.g., Xn-C) simultaneously.

A control plane connection with UE as granularity may be established on the NG-C (a control plane connection corresponding to each UE may be identified with an NG-AP Identity (ID)), and a user plane connection (or user plane tunnel) with PDU session as granularity may be established on the NG-U. Each UE may merely maintain the NG-C connection with the CN-C, but a plurality of user plane connections (user plane tunnels) with PDU session as granularity to the CN-U via the NG-U interface may be established simultaneously. In addition, each UE may be served by one or more gNBs in the RAN simultaneously.

There is no such a concept as bearer in a future <NUM> core network, and the QoS parameter issued by the CN-C to the gNB may be configured with flow as granularity. In addition, the gNB may perform QoS management with RB as granularity, so it is necessary for the RAN to generate a RB-level QoS parameter for the interaction between the gNB and the UE and the interaction between the gNB and the other radio access entity.

The present disclosure provides in some non-claimed embodiments a QoS processing method which, as shown in <FIG>, includes Step <NUM> of transmitting, by a target base station, a first message to a source base station. The first message may at least include first information for notifying the source base station that the target base station is incapable of meeting a QoS requirement on one or more flows of a UE and second information of QoS parameter capable of being accepted by the target base station and recommended with respect to the one or more flows.

For example, during an Xn handover process, the target base station may notify, through a handover response message, the source base station of a flow list including the flows on which the QoS requirement is incapable of being met by the target base station, and the QoS parameter recommended with respect to these flows may also be carried in the handover response message. The source base station may determine a target base station that meets the QoS requirement in accordance with the QoS parameter recommended with respect to these flows.

According to the embodiments of the present disclosure, the QoS parameter capable of being accepted by the target base station and recommended with respect to the one or more flows may be carried in the first message, so that the target base station may notify the source base station of the QoS parameter capable of being accepted by the target base station when the target base station notifies the source base station that the target base station is incapable of meeting the QoS requirement on the one or more flows of the UE. As a result, it is able to prevent the source base station from directly deactivating the bearers incapable of being accepted by the target base station as compared with the related art, thereby to enable the target base station to support a corresponding service.

The present disclosure further provides in some non-claimed embodiments a QoS processing method which, as shown in <FIG>, includes the following steps.

Step <NUM>: transmitting, by a target base station, a first message to a source base station, wherein the first message may at least include first information for notifying the source base station that the target base station is incapable of meeting a QoS requirement on one or more flows of a UE and second information of QoS parameter capable of being accepted by the target base station and recommended with respect to the one or more flows.

For example, during an Xn handover process, the target base station may notify, through a handover response message, the source base station of a flow list including the flows on which the QoS requirement is incapable of being met, and the QoS parameter recommended with respect to these flows may also be carried in the handover response message.

Step <NUM>: transmitting, by the target base station, a second message to a core network. The second message may include third information for notifying the core network that the target base station is incapable of meeting the QoS requirement on the one or more flows of the UE.

For example, after the source base station has selected a proper target cell in accordance with the first message acquired in Step <NUM> and the handover process has been performed, the target base station may notify the core network that an RAN is incapable of meeting the QoS requirement on a certain flow or flows.

In a possible embodiment of the present disclosure, the second message may further include fourth information of the QoS parameter capable of being accepted by the target base station and recommended with respect to the one or more flows.

Referring again to <FIG>, in a non-claimed embodiment of the present disclosure, the QoS processing method may further include Step <NUM> of receiving, by the target base station, an updated QoS parameter of the one or more flows transmitted from the core network.

The core network is capable of updating the QoS parameter of the one or more flows in accordance with the QoS parameter in the second message capable of being accepted by the target base station and recommended with respect to the one or more flows.

According to the embodiments of the present disclosure, a processing procedure may be provided when the target base station is incapable of meeting the QoS requirement. The QoS parameter capable of being accepted by the target base station and recommended with respect to the one or more flows may be carried in the first message, so that the target base station may notify the source base station of the QoS parameter capable of being accepted by the target base station when the target base station notifies the source base station that the target base station is incapable of meeting the QoS requirement on the one or more flows of the UE. As a result, it is able to prevent the source base station from directly deactivating the bearers incapable of being accepted by the target base station as compared with the related art, thereby to enable the target base station to support a corresponding service.

It should be appreciated that, the processes shown in <FIG> may be applied to, but not limited to, a handover scenario.

Step <NUM>: receiving, by a source base station, a first message transmitted from a target base station, and acquiring, by the source base station, first information for indicating that the target base station is incapable of meeting a QoS requirement on one or more flows of a UE from the first message. The first message may further include second information of QoS parameter capable of being accepted by the target base station and recommended with respect to the one or more flows.

For example, during an Xn handover process, the target base station may notify, through a handover response message, the source base station of a flow list including the flows on which the QoS requirement is incapable of being met by the target base station, and the QoS parameter recommended with respect to these flows may also be carried in the handover response message.

Step <NUM>: transmitting, by the source base station, a third message to a core network. The third message may include fifth information for notifying the core network that the target base station is incapable of meeting the QoS requirement on the one or more flows of the UE.

In a possible embodiment of the present disclosure, the third message may further include sixth information of the QoS parameter capable of being accepted by the target base station and recommended with respect to the one or more flows.

According to the embodiments of the present disclosure, a processing procedure may be provided when the target base station is incapable of meeting the QoS requirement. The QoS parameter capable of being accepted by the target base station and recommended with respect to the one or more flows may be carried in the first message, so that the target base station may notify the source base station of the QoS parameter capable of being accepted by the target base station when notifying the source base station that the target base station is incapable of meeting the QoS requirement on the one or more flows of the UE. As a result, it is able to prevent the source base station from directly deactivating the bearers incapable of being accepted by the target base station as compared with the related art, thereby to enable the target base station to support a corresponding service.

Step <NUM>: receiving, by a source base station, a first message, and acquiring, by the source base station, first information for notifying the source base station that the target base station is incapable of meeting a QoS requirement on one or more flows of a UE from the first message. The first message may further include a second information of QoS parameter capable of being accepted by the target base station and recommended with respect to the one or more flows.

Step <NUM>: transmitting, by the source base station, a third message to a core network. The third message may include fifth information for notifying the core network that the target base station is incapable of meeting the QoS requirement on the one or more flows of the UE. In a possible embodiment of the present disclosure, the third message may further include sixth information of the QoS parameter capable of being accepted by the target base station and recommended with respect to the one or more flows.

Step <NUM>: receiving, by the source base station, an updated QoS parameter of the one or more flows transmitted from the core network.

Step <NUM>: selecting, by the source base station, a proper target base station in accordance with the updated QoS parameter of the one or more flows to reinitiate a handover process.

In addition, the source base station may further select a proper target base station in accordance with the updated QoS parameter of the one or more flows to reinitiate a handover process, so as to improve the entire handover procedure, thereby to enable the QoS requirement on the one or more flows of the UE to be accepted by the target base station.

The present disclosure further provides in some non-claimed embodiments a QoS processing method which, as shown in <FIG>, includes Step <NUM> of transmitting, by a target base station, a fourth message to a core network. The fourth message may include seventh information for notifying the core network that the target base station is incapable of meeting a QoS requirement on one or more flows of a UE.

In a possible embodiment of the present disclosure, the fourth message may further include eighth information of QoS parameter capable of being accepted by the target base station and recommended with respect to the one or more flows.

In a possible embodiment of the present disclosure, subsequent to Step <NUM>, the QoS processing method may further include receiving, by the target base station, an updated QoS parameter of the one or more flows transmitted from the core network.

In a possible embodiment of the present disclosure, upon the receipt of the updated QoS parameter of the one or more flows by the target base station, the target base station may transmit a handover response message to the core network. The core network may transmit a handover response message carrying the updated QoS parameter to the source base station. Then the source base station may transmit a handover command to the UE, and then the UE may access to a target cell.

It should be appreciated that, the QoS processes shown in <FIG> may be applied to a handover scenario or a PDU session establishment scenario.

In the PDU session establishment scenario, the target base station may also be called as a serving base station for the UE. When the serving base station for the UE is incapable of meeting the QoS requirement on the one or more flows for a PDU session, the serving base station may also notify, via a message, the core network that it is incapable of meeting the QoS requirement on the one or more flows of the UE.

Step <NUM>: receiving, by a target base station, a handover request message transmitted from the source base station via a core network.

Step <NUM>: transmitting, by the target base station, a fourth message to the core network. The fourth message may include seventh information for notifying the core network that the target base station is incapable of meeting a QoS requirement on one or more flows of a UE.

Step <NUM>: receiving, by the target base station, an updated QoS parameter of the one or more flows transmitted from the core network.

According to the embodiments of the present disclosure, a processing procedure may be provided when the target base station is incapable of meeting the QoS requirement. The QoS parameter capable of being accepted by the target base station and recommended with respect to the one or more flows may be carried in the fourth message, so that the target base station may notify the core network of the QoS parameter capable of being accepted by the target base station and the target base station is capable of accepting the updated QoS parameter of the one or more flows transmitted by the core network when the target base station is incapable of meeting the QoS requirement on the one or more flows of the UE. As a result, it is able to prevent the source base station from directly deactivating the bearers incapable of being accepted by the target base station as compared with the related art, thereby to enable the target base station to support a corresponding service.

The present disclosure further provides in some non-claimed embodiments a QoS processing method which, as shown in <FIG>, include Step <NUM> of receiving, by a core network, a fourth message transmitted from a target base station, and acquiring, by the core network, the seventh message from the fourth message, wherein the seventh information is configured for notifying the core network that the target base station is incapable of meeting a QoS requirement on one or more flows of a UE.

In a possible embodiment of the present disclosure, the fourth message may further include eighth information of a QoS parameter capable of being accepted by the target base station and recommended with respect to the one or more flows.

According to the embodiments of the present disclosure, a processing procedure may be provided when the target base station is incapable of meeting the QoS requirement. The QoS parameter capable of being accepted by the target base station and recommended with respect to the one or more flows may be carried in the fourth message, so that the target base station may notify the core network of the QoS parameter capable of being accepted by the target base station when the target base station is incapable of meeting the QoS requirement on the one or more flows of the UE.

Step <NUM>: receiving, by a core network, a fourth message transmitted from a target base station, and acquiring, by the core network, seventh information from the fourth message, wherein the seventh information is configured for notifying the core network that the target base station is incapable of meeting a QoS requirement on one or more flows of a UE.

Step <NUM>: transmitting, by the core network, an updated QoS parameter of the one or more flows to the target base station.

Step <NUM>: receiving, by the core network, a handover response message transmitted from the target base station.

Step <NUM>: transmitting, by the core network, a fifth message to a source base station. The fifth message may carry the updated QoS parameter of the one or more flows.

Upon the receipt of the updated QoS parameter of the one or more flows, the source base station may transmit a handover command, and then the UE may access to a target cell.

It should be appreciated that, the procedures in <FIG> and <FIG> may be adapted to an NG handover process. In other words, in the NG handover process, the target base station may notify the core network that the QoS requirement on the QoS parameter of the one or more flows is incapable of being met. In addition, the target base station may also provide the recommended QoS parameter.

In some embodiments of the present disclosure, in an Xn handover process, when the target base station determines that it is incapable of meeting the QoS requirement on some flows of the UE in accordance with its own condition, e.g., load, the target base station may transmit an instruction to the source base station. Meanwhile, the target base station may also carries the recommended QoS parameter of the flow. The source base station may determine a final target cell in accordance with the above-mentioned information. After the handover, the target base station may notify the core network that the QoS requirement on the flows of the UE is incapable of being met. In addition, the target base station may also carries the QoS parameter of the flows. Then, the core network may update the QoS parameter of the flow in accordance with the above-mentioned information, and issue the QoS parameter to the target base station.

To be specific, <FIG> shows the Xn handover process in which it, after the handover, notifies the core network (RAN) that it is incapable of meeting the QoS requirement on some flows.

Step <NUM>: the source base station (source node) transmits a handover request message to a plurality of target base stations (target cell <NUM> and target cell <NUM>).

Step <NUM>: the target base station performs acceptance control in accordance with the QoS parameter of the flow, and returns information of the flow that has been accepted successfully, information of the flow that is incapable of meeting the QoS requirement (merely the flow for notification control), and information of the flow that has been accepted unsuccessfully through handover request messages (handover request Acknowledgement (ACK) <NUM> and handover request ACK <NUM>).

With respect to the flow for notification control, when the target base station is incapable of meeting the QoS requirement on the flow, a corresponding instruction and the recommended QoS parameter capable of being accepted by the current base station (target cell <NUM> or target cell <NUM>) may be carried in the response message.

Step <NUM>: the source base station selects a final target cell (select the proper target cell) in accordance with the received response message, and transmits a handover cancel message to the other target cell.

Step <NUM>: the source base station transmits a handover command to the UE, and the UE accesses to the target cell.

Step <NUM>: the target base station indicates, in a path switching message to the core network, the core network that the target base station is incapable of meeting the QoS requirement on some flows, and the core network updates the QoS parameter and notifies the target base station of the updated QoS parameter through a path switching ACK message.

In some embodiments, in the Xn handover process, when the target base station determines that it is incapable of meeting the QoS requirement on some flows of the UE in accordance with its own condition, e.g., load, the target base station may transmit an instruction to the source base station. Meanwhile, the target base station may also carry the QoS parameter of the flow capable of being accepted by the target base station. Upon the receipt of the instruction, the source base station may notify the core network, and then the core network transmits the updated QoS parameter of the flow to the source base station. The source base station may select the target cell in accordance with the information from the target base station, so as to reinitiate the handover process for the target base station.

To be specific, <FIG> shows the Xn handover procedure in which it, before the handover, notifies the core network (the RAN) that it is incapable of meeting the QoS requirement on some flows.

Step <NUM>: the target base station performs acceptance control in accordance with the QoS parameter of the flow, and returns information of the flow that have been accepted successfully, information of the flow that is incapable of meeting the QoS requirement (merely the flow for notification control), and information of the flow that has been accepted unsuccessfully through a handover request response message (handover request ACK). With respect to the flow for notification control, when the target base station is incapable of meeting the QoS requirement on the flow, a corresponding instruction and the recommended QoS parameter capable of being accepted by the current base station may be carried in the response message.

Step <NUM>: the source base station transmits an instruction indicating that the RAN is incapable of meeting the QoS requirement to the core network.

Step <NUM>: the core network updates the QoS parameter for the UE and transmits the updated QoS parameter to the base station.

Step <NUM>: the source base station selects a proper target cell so as to initiate the handover process, and the updated QoS parameter is carried in the handover request message.

Step <NUM>: the source base station transmits a handover command to the UE, and the UE may access to the target cell.

Step <NUM>: the target base station may initiate a path switching process to the core network.

In some embodiments of the present disclosure, in the NG handover process, when the target base station determines, upon the receipt of the handover request from the core network, that it is incapable of meeting the QoS requirement on some flows of the UE in accordance with its own condition, e.g., load, the target base station may transmit an instruction to the core network. Meanwhile, the target base station may also carries the QoS parameter of the flow recommended by the target base station. The core network may adjust the QoS parameter of the flow and transmit the updated QoS parameter to the source base station and the target base station. The source base station may transmit a handover command carrying the updated QoS parameter to the UE, as shown in <FIG>.

Step <NUM>: the source base station may transit a handover request message to the target base station via the core network (CN).

Step <NUM>: the target base station may notify the CN that the RAN is incapable of meeting the QoS requirement on some flows.

Step <NUM>: the core network may transmit updated QoS parameter to the target base station.

Step <NUM>: the target base station may transmit a handover request ACK message to the core network.

Step <NUM>: the core network may transmit a handover response message carrying the updated QoS parameter to the source base station.

Step <NUM>: the source base station may transmit a handover command to the UE, and the UE may access to a target cell.

Based on a same inventive concept, the present disclosure further provides in some embodiments a QoS processing device. A principle of the QoS processing device for solving the problem is similar to that mentioned in the QoS processing method in <FIG>, so the implementation of the QoS processing device may refer to that of the QoS processing method, which will not be particularly defined herein.

The present disclosure further provides in some non-claimed embodiments a QoS processing device <NUM> for a target base station. As shown in <FIG>, the QoS processing device <NUM> includes a first notification module <NUM> configured to notify, through a first message, a source base station that the target base station is incapable of meeting a QoS requirement on one or more flows of a UE, and the first message further includes that a QoS parameter capable of being accepted by the target base station and recommended with respect to the one or more flows.

In a possible embodiment of the present disclosure, the QoS processing device <NUM> may further include a second notification module <NUM> configured to notify, through a second message, the core network that the target base station is incapable of meeting the QoS requirement on the one or more flows of the UE.

In a possible embodiment of the present disclosure, the second message may further include the QoS parameter capable of being accepted by the target base station and recommended with respect to the one or more flows.

In a possible embodiment of the present disclosure, the QoS processing device <NUM> may further include a first reception module <NUM> configured to receive an updated QoS parameter of the one or more flows transmitted from the core network.

Based on a same inventive concept, the present disclosure further provides in some embodiments a QoS processing device. A principle of the QoS processing device for solving the problem is similar to that mentioned in the QoS processing method in <FIG> and <FIG>, so the implementation of the QoS processing device may refer to that of the QoS processing method, which will not be particularly defined herein.

The present disclosure further provides in some non-claimed embodiments a QoS processing device for a source base station. As shown in <FIG>, the QoS processing device <NUM> includes: a second reception module <NUM> configured to determine, through a first message, that a target base station is incapable of meeting a QoS requirement on one or more flows of a UE; and a third notification module <NUM> configured to notify, through a third message, a core network that the target base station is incapable of meeting the QoS requirement on the one or more flows of the UE. The first message may further include QoS parameter capable of being accepted by the target base station and recommended with respect to the one or more flows.

In a possible embodiment of the present disclosure, the third message may further the QoS parameter capable of being accepted by the target base station and recommended with respect to the one or more flows.

In a possible embodiment of the present disclosure, the QoS processing device <NUM> may further includes: a third reception module <NUM> configured to receive an updated QoS parameter of the one or more flows transmitted from the core network; and a handover module <NUM> configured to select a proper target base station in accordance with the updated QoS parameter of the one or more flows to reinitiate a handover process.

The present disclosure further provides in some non-claimed embodiments a QoS processing device <NUM> for a target base station. As shown in <FIG>, the QoS processing device <NUM> includes a fourth notification module <NUM> configured to notify, through a fourth message, a core network that the target base station is incapable of meeting a QoS requirement on one or more flows of a UE.

In a possible embodiment of the present disclosure, the fourth message may further include QoS parameter capable of being accepted by the target base station and recommended with respect to the one or more flows.

In a possible embodiment of the present disclosure, the QoS processing device <NUM> may further include a fourth reception module <NUM> configured to receive an updated QoS parameter of the one or more flows transmitted from the core network.

In a possible embodiment of the present disclosure, the QoS processing device <NUM> may further include a fifth reception module <NUM> configured to receive a handover request message transmitted from a source base station via the core network.

The present disclosure further provides in some non-claimed embodiments a QoS processing device <NUM> for a core network. As shown in <FIG>, the QoS processing device <NUM> includes a sixth reception module <NUM> configured to receive a fourth message transmitted from a target base station, so as to determine, through the fourth message, that the target base station is incapable of meeting a QoS requirement on one or more flows of a UE.

In a possible embodiment of the present disclosure, the fourth message may further include a QoS parameter capable of being accepted by the target base station and recommended with respect to the one or more flows.

In a possible embodiment of the present disclosure, the QoS processing device may further include: a first transmission module <NUM> configured to transmit an updated QoS parameter of the one or more flows to the target base station; and a seventh reception module <NUM> configured to receive a handover response message transmitted from the target base station.

In a possible embodiment of the present disclosure, the QoS processing device may further include a second transmission module <NUM> configured to transmit a fifth message to a source base station, the fifth message carries the update QoS parameter of the one or more flows.

The present disclosure further provides in some non-claimed embodiments a target base station which, as shown in <FIG>, includes a first processor <NUM>, a first transceiver <NUM> and a first memory <NUM>. The first processor <NUM> is configured to read a program stored in the first memory <NUM>, so as to transmit a first message to a source base station. The first message may at least include first information for notifying the source base station that the target base station is incapable of meeting a QoS requirement on one or more flows of a UE and second information of QoS parameter capable of being accepted by the target base station and recommended with respect to the one or more flows. The first transceiver <NUM> is configured to receive and transmit data under the control of the first processor <NUM>.

In <FIG>, the bus architecture (represented by a first bus <NUM>) may include a number of buses and bridges connected to each other, the first bus <NUM> connects various circuits for one or more processors such as the first processor <NUM> and one or more memories such as the first memory <NUM>. In addition, the first bus <NUM> may also be used to connect various other circuits, such as a circuit for a peripheral device, a circuit for a voltage stabilizer and a power management circuit. A first bus interface <NUM> may be provided between the first bus <NUM> and the first transceiver <NUM>, and the first transceiver <NUM> may consist of one element, or more than one element, e.g., a transmitter and a receiver for communication with various other devices over a transmission medium. Data processed by the first processor <NUM> may be transmitted on a wireless medium via the first transceiver <NUM> and a first antenna <NUM>. Further, the first antenna <NUM> may further receive data and transmit the data to the first processor <NUM> via the first transceiver <NUM>.

The first processor <NUM> may take charge of managing the first bus <NUM> as well as general processings, and may further provide various functions such as timing, peripheral interfacing, voltage adjustment, power source management and other control functions. The first memory <NUM> may store therein data for the operation of the first processor <NUM>. To be specific, the first processor <NUM> may be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA) or a Complex Programmable Logic Device (CPLD).

In a possible embodiment of the present disclosure, the first processor is further configured to transmit a second message to a core network, and the second message may include third information for notifying the core network that the target base station is incapable of meeting the QoS requirement on the one or more flows of the UE.

In a possible embodiment of the present disclosure, the first processor <NUM> is further configured to receive an updated QoS parameter of the one or more flows transmitted from the core network.

The present disclosure further provides in some non-claimed embodiments a source base station which, as shown in <FIG>, includes a second processor <NUM>, a second transceiver <NUM> and a second memory <NUM>. The second processor <NUM> is configured to read a program stored in the second memory <NUM>, so as to: receive a first message transmitted from a target base station, and acquire first information for notifying the source base station that the target base station is incapable of meeting a QoS requirement on one or more flows of a UE from the first message; and transmit a third message to a core network. The third message may include fifth information for notifying the core network that the target base station is incapable of meeting the QoS requirement on the one or more flows of the UE. The first message may further include second information of the QoS parameter capable of being accepted by the target base station and recommended with respect to the one or more flows. The second transceiver <NUM> is configured to receive and transmit data under the control of the second processor <NUM>.

In <FIG>, bus architecture (represented by a second bus <NUM>) may include a number of buses and bridges connected to each other, the second bus <NUM> connects various circuits for one or more processors such as the second processor <NUM> and one or more memories such as the second memory <NUM>. In addition, the second bus <NUM> may also be used to connect various other circuits, such as a circuit for a peripheral device, a circuit for a voltage stabilizer and a power management circuit. A second bus interface <NUM> may be provided between the second bus <NUM> and the second transceiver <NUM>, and the second transceiver <NUM> may consist of one element, or more than one element, e.g., a transmitter and a receiver for communication with various other devices over a transmission medium. Data processed by the second processor <NUM> may be transmitted on a wireless medium via the second transceiver <NUM> and a second antenna <NUM>. Further, the second antenna <NUM> may further receive data and transmit the data to the second processor <NUM> via the second transceiver <NUM>.

The second processor <NUM> may take charge of managing the second bus <NUM> as well as general processings, and may further provide various functions such as timing, peripheral interfacing, voltage adjustment, power source management and other control functions. The second memory <NUM> may store therein data for the operation of the second processor <NUM>. To be specific, the second processor <NUM> may be a CPU, an ASIC, an FPGA or a CPLD.

In a possible embodiment of the present disclosure, the second processor <NUM> is further configured to: receive an updated QoS parameter of the one or more flows transmitted from the core network; and select a proper target base station in accordance with the updated QoS parameter of the one or more flows to reinitiate a handover process.

The present disclosure further provides in some non-claimed embodiments a target base station which, as shown in <FIG>, includes a third processor <NUM>, a third transceiver <NUM> and a third memory <NUM>. The third processor <NUM> is configured to read a program stored in the third memory <NUM>, so as to transmit a fourth message to a core network. The fourth message may include seventh information for notifying the core network that the target base station is incapable of meeting a QoS requirement on one or more flows of a UE. The third transceiver <NUM> is configured to receive and transmit data under the control of the third processor <NUM>.

In <FIG>, bus architecture (represented by a third bus <NUM>) may include a number of buses and bridges connected to each other, the third bus <NUM> connects various circuits for one or more processors such as the third processor <NUM> and one or more memories such as the third memory <NUM>. In addition, the third bus <NUM> may also be used to connect various other circuits, such as a circuit for a peripheral device, a circuit for a voltage stabilizer and a power management circuit. A third bus interface <NUM> may be provided between the third bus <NUM> and the third transceiver <NUM>, and the third transceiver <NUM> may consist of one element, or more than one element, e.g., a transmitter and a receiver for communication with various other devices over a transmission medium. Data processed by the third processor <NUM> may be transmitted on a wireless medium via the third transceiver <NUM> and a third antenna <NUM>. Further, the third antenna <NUM> may further receive data and transmit the data to the third processor <NUM> via the third transceiver <NUM>.

The third processor <NUM> may take charge of managing the third bus <NUM> as well as general processings, and may further provide various functions such as timing, peripheral interfacing, voltage adjustment, power source management and any other control functions. The third memory <NUM> may store therein data for the operation of the third processor <NUM>. To be specific, the third processor <NUM> may be a CPU, an ASIC, an FPGA or a CPLD.

In a possible embodiment of the present disclosure, the third processor <NUM> is further configured to receive an updated QoS parameter of the one or more flows transmitted from the core network.

In a possible embodiment of the present disclosure, the third processor <NUM> is further configured to receive a handover request message transmitted from a source base station via the core network.

The present disclosure further provides in some non-claimed embodiments a core network side device which, as shown in <FIG>, includes a fourth processor, a fourth transceiver <NUM> and a fourth memory <NUM>. The fourth processor <NUM> is configured to read a program stored in the fourth memory <NUM>, so as to receive a fourth message transmitted from a target base station. The fourth message may include seventh information for notifying a device at the core network side that the target base station is incapable of meeting a QoS requirement on one or more flows of a UE.

In <FIG>, bus architecture (represented by a fourth bus <NUM>) may include a number of buses and bridges connected to each other, the fourth bus <NUM> connects various circuits for one or more processors such as the fourth processor <NUM> and one or more memories such as the fourth memory <NUM>. In addition, the fourth bus <NUM> may also be used to connect various other circuits, such as a circuit for a peripheral device, a circuit for a voltage stabilizer and a power management circuit. A fourth bus interface <NUM> may be provided between the fourth bus <NUM> and the fourth transceiver <NUM>, and the fourth transceiver <NUM> may consist of one element, or more than one element, e.g., a transmitter and a receiver for communication with various other devices over a transmission medium. Data processed by the fourth processor <NUM> may be transmitted on a wireless medium via the fourth transceiver <NUM> and a fourth antenna <NUM>. Further, the fourth antenna <NUM> may further receive data and transmit the data to the fourth processor <NUM> via the fourth transceiver <NUM>.

The fourth processor <NUM> may take charge of managing the fourth bus <NUM> as well as general processings, and may further provide various functions such as timing, peripheral interfacing, voltage adjustment, power source management and various other control functions. The fourth memory <NUM> may store therein data for the operation of the fourth processor <NUM>. To be specific, the fourth processor <NUM> may be a CPU, an ASIC, an FPGA or a CPLD.

In a possible embodiment of the present disclosure, the fourth processor <NUM> is further configured to: transmit updated QoS parameter of the one or more flows to the target base station; and receive a handover response message transmitted from the target base station.

In a possible embodiment of the present disclosure, the fourth processor <NUM> is further configured to transmit a fifth message to a source base station. The fifth message may include ninth information indicating the update QoS parameter of the one or more flows.

The present disclosure further provides in some embodiments a computer-readable storage medium storing therein a computer program (instruction). The computer program (instruction) is executed by a processor so as to implement the above-mentioned QoS processing methods in <FIG>.

It should be further appreciated that, such phrases as "one embodiment" and "one of the embodiments" intend to indicate that the features, structures or characteristics are contained in at least one embodiment of the present disclosure, rather than referring to a same embodiment. In addition, the features, structures or characteristics may be combined in any embodiment or embodiments in an appropriate manner.

It should be further appreciated that, serial numbers of the steps shall not be used to define the order of the steps, and instead, the order of the steps shall be determined in accordance with their functions and internal logics.

In addition, the terms "system" and "network" may be replaced with each other.

It should be appreciated that, the expression "and/or" is merely used to describe the relationship between objects, and it includes three relationships. For example, "A and/or B" may represent that, there is only A, there are both A and B, and there is only B. Further, the symbol "/" herein usually refers to "or".

It should be further appreciated that, the expression "B corresponding to A" means that B is associated with A and may be determined in accordance with A. However, when B is determined in accordance with A, it means that B may be determined in accordance with A and/or any other information.

It should be further appreciated that, the device and method may be implemented in any other ways. For example, the embodiments for the apparatus are merely for illustrative purposes, and the units are provided merely on the basis of their logic functions. During the actual application, the units may be provided in other manners; for example, some units and elements may be combined together or integrated into another system. Alternatively, some features may be omitted or not executed. In addition, the coupling connection, direct coupling connection or communication connection between the units or elements discussed herein may be implemented via interfaces, and the indirect coupling connection or communication connection between the devices or units may be implemented in an electrical or mechanical form or in any other form.

In addition, the functional units in the embodiments of the present disclosure may be integrated into a processing unit, or the functional units may exist independently, or two or more functional units may be combined together. These units may be implemented in the form of hardware, or hardware plus software.

Claim 1:
A Quality of Service, QoS, processing method, comprising:
receiving (<NUM>), by a target base station, a handover request message from a source base station, wherein the target base station and the source base station are communicatively connected to a core network;
performing (<NUM>), by the target base station, acceptance control in accordance with a first QoS parameter of one or more flows of a User Equipment, UE;
transmitting, by the target base station, a first message to the source base station;
wherein the first message is a handover request acknowledgement message, and at least comprises first information and second information;
the first information comprises: information of a flow that has been accepted successfully, information of a flow that is incapable of meeting the QoS requirement, and information of a flow that has been accepted unsuccessfully through the handover request message; and
the second information is information of a second QoS parameter capable of being accepted by the target base station and recommended with respect to the one or more flows,
receiving (<NUM>), by the target base station, an access message from the UE;
wherein the QoS processing method further comprises:
transmitting (<NUM>), by the target base station, a second message to the core network,
wherein the second message is a path switching message, and comprises third information; and
the third information is configured for notifying the core network that the target base station is incapable of meeting the QoS requirement on the one or more flows of the UE;
characterized in that the QoS processing method further comprises:
in response to the transmission by the target base station of the second message, receiving, by the target base station, an updated second QoS parameter of the one or more flows transmitted from the core network through a path switching acknowledgement message.