METHOD AND DEVICE OF QUALITY OF SERVICE PROCESSING

Abstract

A method and a device of quality of service (QoS) processing are provided. The method includes: a first device determining whether the first device satisfies a QoS requirement of one or more flows of a UE; in the case that the first device does not satisfy the QoS requirement of the one or more flows of the UE, the first device transmitting a first message to a second device; where the first message includes one of or a combination of more than one of: QoS flow identifier (QFI), radio bearer (RB) ID, indication information indicating that the QoS requirement is not satisfied, or recommended QoS parameter.

Description

CROSS-REFERENCE TO RELATED APPLICATION

The present application claims a priority to Chinese patent application No. 201710186478.1 filed in China on Mar. 24, 2017, the disclosure of which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

The present disclosure relates to the field of communication technology, in particular to a method and a device of quality of service (QoS) processing.

BACKGROUND

In conventional Long Term Evolution (LTE) system, if current air interface resources can't satisfy QoS requirements, the Evolved Radio Access Bearer (E-RAB) will be released proactively and Core Network will be notified. In New Radio (NR) system, for Guaranteed Bit Rate (GBR) service, the notification control in the QoS parameters indicates whether the Core Network may be notified if the QoS of a certain flow can't be satisfy by the Radio Access Network (RAN) side. It means that in 5G system, for the GBR service, the radio access side is permitted to inform the Core Network that the current radio network condition can't satisfy the QoS requirements of the GBR service.

In a multi connectivity scenario, QoS flow may be split to a Secondary Node (secondary base station), thus what to do in the case that the QoS can't be satisfied by the Secondary Node needs to be taken into consideration. In a Central Unit (CU)—Distributed Unit (DU) split scenario, what to do in the case that the QoS can't be satisfied by the DU needs to be taken into consideration.

In conventional LTE system, if current air interface resources can't satisfy the QoS requirements, the E-RAB will be released proactively and the Core Network will be notified, thereby impacting service performance. At present, there is no mechanism for managing the GRB flow for multi connectivity scenario and CU-DU scenario at the RAN side.

SUMMARY

In view of the above, embodiments of the present disclosure provide a method and a device of QoS processing, such that in the case that a first device can't satisfy a QoS requirement in a multi connectivity scenario or a CU-DU scenario in a 5G system, the first device may act accordingly to satisfy the QoS requirement.

In a first aspect of embodiments of the present disclosure, a method of QoS processing is provided, the method including: a first device determining whether the first device satisfies a QoS requirement of one or more flows of a UE; and in the case that the first device does not satisfy the QoS requirement of the one or more flows of the UE, the first device transmitting a first message to a second device; where the first message includes one of or a combination of more than one of: QoS flow identifier (QFI), radio bearer (RB) ID, indication information indicating that the QoS requirement is not satisfied, or recommended QoS parameters.

Optionally, the first device determining whether the first device satisfies the QoS requirement of the one or more flows of the UE includes: the first device determining whether the first device satisfies the QoS requirement of the one or more flows of the UE in accordance with QoS parameter(s) of the one or more flows or in accordance with the QoS parameter(s) of the one or more flows and a mapping relation between data radio bearer (DRB) and flow.

Optionally, the method further includes: the first device receiving the QoS parameter(s) of the one or more flows transmitted by the second device and the mapping relation between DRB and flow on the second device.

Optionally, the first device is a secondary base station and the second device is a primary base station; or the first device is a distributed unit (DU) and the second device is a central unit (CU).

Optionally, the QoS parameter includes a suggested guaranteed bit rate and/or a suggested maximum bit rate.

In a second aspect of embodiments of the present disclosure, a method of QoS processing is further provided, the method including: a second device receiving a first message transmitted by a first device, where the first message is generated in the case that the first device does not satisfy QoS requirement of one or more flows of a UE; where the first message includes one of or a combination of more than one of: QoS flow identifier (QFI), radio bearer (RB) ID, indication information indicating that the QoS requirement is not satisfied, or recommended QoS parameter.

Optionally, the method further includes: the second device determining whether a bearer type change is needed in accordance with the first message; or the second device transmitting a second message to a core network in accordance with the first message.

Optionally, the second message includes one of or a combination of more than one of: the QFI, the indication information indicating that the QoS requirement is not satisfied, or a suggested QoS parameter.

Optionally, the first device is a secondary base station and the second device is a primary base station; or the first device is a DU and the second device is a CU.

Optionally, the QoS parameter includes a suggested guaranteed bit rate and/or a suggested maximum bit rate.

In a third aspect of embodiments of the present disclosure, a first device is further provided, the first device including: a first determination module, configured to determine whether the first device satisfies a QoS requirement of one or more flows of a UE; and a first transmission module, configured to transmit, in the case that the first device does not satisfy the QoS requirement of the one or more flows of the UE, a first message to a second device; where the first message includes one of or a combination of more than one of: QoS flow identifier (QFI), radio bearer (RB) ID, indication information indicating that the QoS requirement is not satisfied, or recommended QoS parameter.

Optionally, the first determination module is configured to: determine whether the first device satisfies the QoS requirement of the one or more flows of the UE, in accordance with QoS parameter(s) of the one or more flows or in accordance with the QoS parameter(s) of the one or more flows and a mapping relation between data radio bearer (DRB) and flow.

Optionally, the first device further includes: a first reception module, configured to receive the QoS parameter(s) of the one or more flows transmitted by the second device and the mapping relation between DRB and flow on the second device.

Optionally, the first device is a secondary base station e and the second device is a primary base station; or the first device is a DU and the second device is a CU.

Optionally, the QoS parameter includes a suggested guaranteed bit rate and/or a suggested maximum bit rate.

In a fourth aspect of embodiments of the present disclosure, a second device is further provided, the second device including: a second reception module, configured to receive a first message transmitted by a first device, where the first message is generated in the case that the first device does not satisfy a QoS requirement of one or more flows of a UE; where the first message includes one of or a combination of more than one of: QoS flow identifier (QFI), radio bearer (RB) ID, indication information indicating that the QoS requirement is not satisfied, or recommended QoS parameter.

Optionally, the second device further includes: a second determination module, configured to determine whether a bearer type change is needed in accordance with the first message; or a second transmission module, configured to transmit a second message to a core network in accordance with the first message.

Optionally, the second message includes one of or a combination of more than one of: the QFI, the indication information indicating that the QoS requirement is not satisfied, or a suggested QoS parameter.

Optionally, the first device is a secondary base station and the second device is a primary base station; or the first device is a DU and the second device is a CU.

Optionally, the QoS parameter includes a suggested guaranteed bit rate and/or a suggested maximum bit rate.

In a fifth aspect of embodiments of the present disclosure, a network device is further provided, including a memory, a processor and a computer program stored on the memory and executable by the processor, where the processor is configured to execute the computer program to implement steps of the method of QoS processing described above.

In a sixth aspect of embodiments of the present disclosure, a computer readable storage medium having a computer program stored thereon is further provided, where steps of the method of QoS processing described above are implemented when the computer program is executed by a processor.

A technical solution of the aforementioned technical solutions has advantages or beneficial effects as follows. Based on the embodiments of the present disclosure, in a multi connectivity scenario or a CU-DU scenario, the first device can transmit the first message to the second device in the case that the first device does not satisfy the QoS requirement, where the first message includes one of or a combination of more than one of: QFI, RB ID, indication information indicating that the QoS requirement is not satisfied, or recommended QoS parameter. In this way, when the first device does not satisfy the QoS requirement in the multi connectivity scenario or the CU-DU scenario in the 5G system, the first device can act accordingly to satisfy the QoS requirement, so as to solve the problem in the related technologies that E-RAB will be released proactively if current air interface resources can't satisfy a QoS requirement.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic structural diagram of a bearer model in LTE system according to related technologies;

FIG. 2 is a schematic diagram of a NR architecture according to related technologies;

FIG. 3 is a schematic diagram of an architecture of a 5G communication system;

FIG. 4 is a schematic diagram of a 5G network architecture;

FIG. 5 is a schematic diagram of dual connectivity;

FIG. 6 is another schematic diagram of dual connectivity;

FIG. 7 is a flow diagram of a method of QoS processing according to an embodiment;

FIG. 8 is a flow diagram of a method of QoS processing according to another embodiment;

FIG. 9 is a flow diagram of a process in which a Secondary Node reports QFI of flow and/or recommended QoS parameter in multi connectivity SCG bearer or SCG split bearer scenario according to an embodiment;

FIG. 10 is a flow diagram of a process in which a Secondary Node reports RB ID and/or recommended QoS parameter in CU-DU scenario according to an embodiment;

FIG. 11 is a structural diagram of a first device according to an embodiment;

FIG. 12 is a structural diagram of a second device according to an embodiment;

FIG. 13 is a structural diagram of a first device according to another embodiment; and

FIG. 14 is a structural diagram of a second device according to another embodiment.

DETAILED DESCRIPTION

Exemplary embodiments of the present disclosure are detailed in conjunction with drawings. It should be noted, the present disclosure may be implemented in various ways although the exemplary embodiments are illustrated in the drawings. The embodiments provided herein are not to limit the present disclosure, and on the contrary, they are provided for thoroughly understanding the present disclosure and completely conveying the scope of the present disclosure to those skilled in the art.

(1) Bearer Model in Conventional LTE System

Referring to FIG. 1, in conventional LTE system, core network is responsible for generation of QoS parameter of E-RAB, and since there is a one-to-one mapping relation between air interface Radio Bearer (RB) and the E-RAB, the E-RAB QoS parameter generated by the core network are directly used as QoS parameter of the air interface RB.

(2) RAN Side Architecture

Embodiments of the present disclosure may be applied in various network deployment structures. For convenience, two types of network deployment structures which may be employed in the future mobile communication are introduced.

The first deployment structure: base station+user equipment

Referring to FIG. 2, a typical New Radio (NR) architecture is illustrated. A gNB (base station) has multiple cells and the UE transmits/receives air interface data to/from the cell in a connected state.

The second deployment structure: network side node includes Central Unit (CU) and Distributed Unit (DU), and user side node includes UE.

Referring to FIG. 3, an architecture which may be employed in the future 5G mobile communication is illustrated. The network side node includes CU and DU, where one CU controls multiple DUs deployed in a certain area, and these DUs perform air interface transmission with the UE via Transmission Reception Point (TRP). One or more TRPs may serve a UE to perform data transmission at the same time.

Embodiments of the present disclosure are applicable to the two RAN architectures described above.

5G network architecture is illustrated in FIG. 4, where the network architecture includes three logical entities: NG-C (control plane function entity of core network) and NG-U (user plane function entity of core network) located in core network, and gNB (next generation base station) and eLTE eNB (base station of evolved LTE) located in access network. A NG-C interface is established between the NG-C and the gNB to transmit control plane signaling; and a NG-U is established between the NG-U and the gNB to transmit user plane data. An Xn interface, supporting both control plane function (e.g., Xn-C) and user plane function (e.g., Xn-U), is established between gNBs of radio access network.

A control plane connection at the granularity of UE may be established on the NG-C (where the control plane connection corresponding to each UE may be identified with a NG-AP ID), and a user plane connection (or referred to as user plane tunnel) at the granularity of PDU session may be established on the NG-U. A UE can only maintain one NG-C connection to the NG-C at a time; however, the UE may establish multiple user plane connections (or user plane tunnels) at the granularity of PDU session to NG-U on the NG-U interfaces. In radio access network, there may be one or more gNBs serving the UE at the same time.

(3) Dual Connectivity Mechanism

Currently, dual connectivity mechanism is supported in LTE system. The dual connectivity mechanism is to reduce the load of the Master RAN. In the mechanism, a UE accesses the Master RAN, control plane message is exchanged between the Master RAN and the UE, and the Master RAN may opt to migrate a part of or all of bearers to a Secondary RAN to transmit to the UE, as shown in FIG. 5.

As illustrated in FIG. 6, in the dual connectivity scenario, there are bear types including MCG bearer (Master Cell Group bearer), SCG bearer (Secondary Cell Group bearer), Split bearer and SCG split bearer.

(4) QoS Flow

The future 5G core network forgoes the concept of bearer, and QoS parameter issued by the NG-C of the core network to the gNB are configured at the granularity of flow. On the other hand, since the gNB of the access network still performs QoS management at the granularity of RB, it is needed for the access network to generate QoS parameter at RB level for interaction process between gNB and UE and interaction process between gNB and other radio access entity.

Referring to FIG. 7, a method of QoS processing according to an embodiment is illustrated, the method including the following steps.

Step 701, a first device determining whether the first device satisfies a QoS requirement of one or more flows of a UE.

In the embodiment, the determination may be performed through two modes as follows: (1) the first device determining whether the first device satisfies the QoS requirement of the one or more flows of the UE in accordance with QoS parameter(s) of the one or more flows; (2) the first device determining whether the first device satisfies the QoS requirement of the one or more flows of the UE in accordance with the QoS parameter(s) of the one or more flows and a mapping relation between data radio bearer (DRB) and flow.

Step 702, in the case that the first device can't satisfy the QoS requirement of the one or more flows of the UE, the first device transmitting a first message to a second device; where the first message includes one of or a combination of more than one of: QoS flow identifier (QFI), radio bearer (RB) ID, indication information indicating that the QoS requirement can't be satisfied, or recommended QoS parameter.

The method of QoS processing according to the embodiment may be applicable to a multi connectivity scenario, e.g., a multi connectivity SCG bearer or multi connectivity SCG split bearer scenario; or, the method of QoS processing according to the embodiment may be applicable to a CU-DU scenario. In the multi connectivity SCG bearer or multi connectivity SCG split bearer scenario, the first device is a secondary base station, and the second device is primary base station; and in the CU-DU scenario, the first device is the DU and the second device is the CU.

In the multi connectivity scenario, prior to establishing the multi connectivity for the UE, the method further includes: the first device receiving the QoS parameter(s) of the one or more flows transmitted by the second device and the mapping relation between DRB and flow on the second device.

In the embodiment, optionally, the QoS parameter includes a suggested guaranteed bit rate and/or a suggested maximum bit rate.

Based on the embodiments of the present disclosure, in the multi connectivity scenario or the CU-DU scenario, the first device can transmit the first message to the second device when the first device can't satisfy the QoS requirement, where the first message includes one of or a combination of more than one of: QFI, RB ID, indication information indicating that the QoS requirement can't be satisfied, or recommended QoS parameter. In this way, when the first device can't satisfy the QoS requirement in the multi connectivity scenario or the CU-DU scenario in the 5G system, the first device may act accordingly to satisfy the QoS requirement.

Referring to FIG. 8, a process of a method of QoS processing is illustrated, the method including the following specific steps.

Step 801, a second device receiving a first message transmitted by a first device, where the first message is generated in the case that the first device can't satisfy a QoS requirement of one or more flows of a UE; where the first message includes one of or a combination of more than one of: QoS Flow Identifier (QFI), Radio Bearer (RB) ID, indication information indicating that the QoS requirement can't be satisfied, or recommended QoS parameter.

The method of QoS processing according to the embodiment may be applicable to a multi connectivity scenario, e.g., a multi connectivity SCG bearer or multi connectivity SCG split bearer scenario; or, the method of QoS processing according to the embodiment may be applicable to a CU-DU scenario. In the multi connectivity SCG bearer or multi connectivity SCG split bearer scenario, the first device is a secondary base station, and the second device is a primary base station; and in the CU-DU scenario, the first device is a DU and the second device is a CU.

Optionally, in the multi connectivity scenario, the method further includes: the second device determining whether a bearer type change is needed in accordance with the first message.

Optionally, in the CU-DU scenario, the method further includes: the second device transmitting a second message to a core network in accordance with the first message.

Further, the second message includes one of or a combination of more than one of: the QFI, the indication information indicating that the QoS requirement can't not be satisfied, or a suggested QoS parameter.

In the embodiment, optionally, the QoS parameter includes a suggested guaranteed bit rate and/or a suggested maximum bit rate.

Based on the embodiments of the present disclosure, in the multi connectivity scenario or the CU-DU scenario, the first device can transmit the first message to the device when the first device can't satisfy the QoS requirement, where the first message includes one of or a combination of more than one of: QFI, RB ID, indication information indicating that the QoS requirement is not satisfied, or recommended QoS parameter. In this way, when the first device can't satisfy the QoS requirement in the multi connectivity scenario or the CU-DU scenario in the 5G system, the first device may act accordingly to satisfy the QoS requirement.

Hereinafter, the process of the method of QoS processing is explained with reference to the dual connectivity scenario and the CU-DU scenario.

(1) if core network sets notification control for one or more QoS flows: in the dual connectivity scenario, during the process of adding the Secondary Node (secondary base station), the Master Node (primary base station) may transmit QoS parameter of flow on which split is performed, DRB-flow mapping relation and QoS parameter of RB to the Secondary Node. After the process is completed, if resources of the Secondary Node can't satisfy the QoS requirement, one or more of related QFI, RB ID or recommended QoS parameter need to be reported to the Master Node. The Master Node determines, based on its policy, whether to perform a bearer type change or to notify the core network and report the related QFI and/or recommended QoS parameter to the core network.

(2) if core network sets notification control for one or more QoS flows: in the CU-DU scenario, during the process of the CU selecting the DU for the UE, the establishment request message may include QoS parameter of flow and DRB-flow mapping relation, in addition to QoS parameter of RB. After the process is completed, if resources of the DU can't satisfy the QoS requirement, related RB ID and recommended QoS parameter need to be reported to the CU, and the CU reports related QFI and/or recommended QoS parameter to the core network.

Optionally, the QoS parameter includes a guaranteed bit rate (GBR) and/or a maximum bit rate (MBR).

The first embodiment: in the multi connectivity SCG bearer/SCG split bearer scenario, the Secondary Node reports QFI of flow and/or recommended QoS parameter, as shown in FIG. 9.

Step 1, the UE establishes a user plane connection to the NGU via the Master RAN.

Step 2, the Master RAN selects the Secondary RAN, and determines to split a part of data flow of the PDU session to the Secondary RAN.

Step 3, the Master RAN adds the Secondary RAN through the Xn interface, where the request message carries QoS parameter of flow (including per flow notification control).

Step 4, the Master RAN updates path information, and creates a tunnel from the Secondary RAN to the NGU.

Step 5, after the dual connectivity is established for the UE, if the Secondary Node determines that requirement of QoS flow can't be satisfied, the Secondary Node transmits a Secondary Node modification request message carrying the QFI and/or suggested QoS parameter to the Master RAN.

Step 6, the Master Node replies with a response message.

It is noted that, step 6 is optional.

The subsequent operations of the Master Node are as follows.

Scheme 1: the Master Node determines whether to perform a bearer type change, e.g., change into a MCG bearer, in accordance with the QoS information transmitted by the Secondary Node, and the MeNB (macro eNB) may initiate an Xn Secondary Node modification or release process to complete the bearer type change. For a SCG split bearer, the Master Node may re-negotiate RB QoS with the Secondary Node, and the Master Node may initiate a Secondary Node modification process to complete the negotiation of the RB parameters.

Scheme 2: the Master Node may directly initiate a PDU Session modification request, carrying the QFI and/or QoS information reported by the Secondary Node, to the core network in accordance with the QoS information transmitted by the Secondary Node.

It is noted, the Scheme 1 and Scheme 2 may be used in conjunction. For example, after the Scheme 1 is performed, the MeNB may determine whether the flow QoS requirement may be satisfied in accordance with the resource usage of the MeNB; if the flow QoS requirement can't be satisfied, the MeNB initiates a PDU Session modification request carrying the flow QFI and/or suggested QoS information.

The second embodiment: in the multi connectivity split bearer scenario, the Secondary Node reports the RB ID and/or recommended QoS parameter.

The second embodiment is similar to the first embodiment except for the step 5 and step 6, wherein if the Secondary Node determines that the requirement of the QoS flow can't be satisfied in accordance with QoS parameter of flow and DRB-flow mapping relation, the Secondary Node transmits a Secondary Node modification request message, carrying the RB ID and/or suggested QoS parameter, to the Master RAN.

The subsequent operations of the Master Node are as follows.

Scheme 1: the Master Node determines whether to perform a bearer type change, e.g., change into a MCG bearer, in accordance with the QoS information transmitted by the Secondary Node, and the MeNB may initiate an Xn Secondary Node modification or release process to complete the bearer type change; or the Master Node may re-negotiate RB QoS with the Secondary Node, and the Master Node may initiate a Secondary Node modification process to complete the negotiation of the RB parameters.

Scheme 2: having received the QoS information transmitted by the Secondary Node, the Master Node, in accordance with its own resource status, directly initiates a PDU Session modification request, carrying the QFI of the QoS flow and/or suggested QoS parameter to the core network.

The third embodiment: in the CU-DU scenario, the Secondary Node reports RB ID and/or recommended QoS parameter (also referred to as suggested QoS parameter), as shown in FIG. 10, which including the following steps.

Step 1: the Secondary Node determines that the QoS flow requirement can't be satisfied in accordance with QoS parameter of flow and DRB-flow mapping relation.

Step 2: the Secondary Node transmits a UE context modification request message to the Master RAN, where the message carries RB ID and/or suggested QoS parameter.

Step 3: optionally, the CU returns an acknowledge response.

Step 4: the CU initiates a modification request, carrying the QFI of the QoS flow and/or suggested QoS parameter, to the core network.

Based on the same inventive concept, embodiments of the present disclosure also provide a first device. Since the problem-solving principle of the first device is similar to the method of QoS processing as shown in FIG. 7 according to the embodiments of the present disclosure, the implementation of the first device may be learned by referring to the implementation of the method, thus a repeated description is omitted.

Referring to FIG. 11, the structure of the first device according to an embodiment is illustrated. The first device 1100 includes: a first determination module 1101, configured to determine whether the first device satisfies a QoS requirement of one or more flows of a UE; and a first transmission module 1102, configured to, in the case that the first device can't satisfy the QoS requirement of the one or more flows of the UE, transmit a first message to a second device; where the first message includes one of or a combination of more than one of: QoS flow identifier (QFI), radio bearer (RB) ID, indication information indicating that the QoS requirement is not satisfied, or recommended QoS parameter.

In the embodiment, optionally, the first device is a secondary base station and the second device is a primary base station; or the first device is a DU and the second device is a CU.

In the embodiment, optionally, the first determination module 1101 is configured to: determine whether the first device satisfies the QoS requirement of the one or more flows of the UE in accordance with QoS parameter(s) of the one or more flows or in accordance with the QoS parameter(s) of the one or more flows and a mapping relation between data radio bearer (DRB) and flow.

In the embodiment, optionally, the first device 1100 further includes: a first reception module, configured to receive the QoS parameter(s) of the one or more flows transmitted by the second device and the mapping relation between DRB and flow on the second device.

In the embodiment, optionally, the QoS parameter includes a suggested guaranteed bit rate and/or a suggested maximum bit rate.

Based on the embodiments of the present disclosure, in a multi connectivity scenario or a CU-DU scenario, the first device can transmit the first message to the device when the first device can't satisfy the QoS requirement, where the first message includes one of or a combination of more than one of: QFI, RB ID, indication information indicating that the QoS requirement is not satisfied, or recommended QoS parameter. In this way, when the first device can't satisfy the QoS requirement in the multi connectivity scenario or the CU-DU scenario in the 5G system, the first device may act accordingly to satisfy the QoS requirement.

Based on the same inventive concept, embodiments of the present disclosure further provide a second device. Since the problem-solving principle of the second device is similar to the method of QoS processing as shown in FIG. 8 according to the embodiments of the present disclosure, the implementation of the second device may be learned by referring to the implementation of the method, thus a repeated description is omitted.

Referring to FIG. 12, the structure of the second device according to an embodiment is illustrated. The second device 1200 includes: a second reception module 1201, configured to receive a first message transmitted by a first device, where the first message is generated in the case that the first device can't satisfy QoS requirement of one or more flows of a UE; where the first message includes one of or a combination of more than one of: QoS flow identifier (QFI), radio bearer (RB) ID, indication information indicating that the QoS requirement is not satisfied, or recommended QoS parameter.

In the embodiment, optionally, the first device is a secondary base station and the second device is a primary base station; or the first device is a DU and the second device is a CU.

In the embodiment, optionally, the second device 1200 further includes: a second determination module, configured to determine whether a bearer type change is needed in accordance with the first message; or a second transmission module, configured to transmit a second message to a core network in accordance with the first message.

In the embodiment, optionally, the second message includes one of or a combination of more than one of: the QFI, the indication information indicating that the QoS requirement is not satisfied, or a suggested QoS parameter.

In the embodiment, optionally, the QoS parameter includes a suggested guaranteed bit rate and/or a suggested maximum bit rate.

Based on the embodiments of the present disclosure, in a multi connectivity scenario or a CU-DU scenario, the first device can transmit the first message to the second device when the first device can't satisfy the QoS requirement, where the first message includes one of or a combination of more than one of: QFI, RB ID, indication information indicating that the QoS requirement is not satisfied, or recommended QoS parameter. In this way, when the first device can't satisfy the QoS requirement in the multi connectivity scenario or the CU-DU scenario in the 5G system, the first device may act accordingly to satisfy the QoS requirement.

A network device is further provided in an embodiment, which including a memory, a processor and a computer program stored on the memory and executable by the processor, where the processor is configured to execute the computer program to implement steps of the methods of QoS processing described above.

Referring to FIG. 13, embodiments of the present disclosure provide a first device, including: a first processor 1304, configured to read program in a first memory 1305 and implement the following process: determining whether the first device satisfies a QoS requirement of one or more flows of a UE; and in the case that the first device can't satisfy the QoS requirement of the one or more flows of the UE, transmitting a first message to a second device; where the first message includes one of or a combination of more than one of: QoS flow identifier (QFI), radio bearer (RB) ID, indication information indicating that the QoS requirement is not satisfied, or recommended QoS parameter; and a first transceiver 1301, configured to receive and transmit data under the control of the first processor 1304.

In FIG. 13, a bus architecture (represented by a first bus 1300) may include an arbitrary quantity of buses and bridges connected to each other. Various circuits including one or more processors represented by the first processor 1304 and a memory represented by the first memory 1305 are coupled via the first bus 1300. The first bus 1300 may further couple other circuits together, such as a periphery component, a voltage stabilizer and a power management circuit, which is well known in the art and is not repeated herein. A first bus interface 1303 provides an interface between the first bus 1300 and the first transceiver 1301. The first transceiver 1301 may be one element, or may be multiple elements, such as multiple receivers and transmitters. The first transceiver 1301 provides a unit configured to communicate with other devices on a transmission medium. Data processed by the first processor 1304 is transmitted via the first transceiver 1301 and the first antenna 1302 on a radio medium. Furthermore, the first antenna 1302 receives data and transmits the data to the first processor 1304 via the first transceiver 1301.

The first processor 1304 is in charge of managing the first bus 1300 and common processes, and may further provide various functions, e.g., timing, periphery interfaces, voltage adjusting, power source management and other controlling functions. The first memory 1305 may be configured to store data to be used by the first processor 1304 when performing operations. In specific, the first processor 1304 may be CPU, application specific integrated circuit (ASIC), field-programmable gate array (FPGA) or complex programmable logic device (CPLD).

Referring to FIG. 14, embodiments of the present disclosure provide a second device, including: a second processor 1404, configured to read program in a second memory 1405 and implement the following process: receiving a first message transmitted by a first device, where the first message is generated in the case that the first device can't satisfy a QoS requirement of one or more flows of a UE; where the first message includes one of or a combination of more than one of: QoS flow identifier (QFI), radio bearer (RB) ID, indication information indicating that the QoS requirement is not satisfied, or recommended QoS parameter; and a second transceiver 1401, configured to receive and transmit data under the control of the second processor 1404.

In FIG. 14, a bus architecture (represented by a second bus 1400) may include an arbitrary quantity of buses and bridges connected to each other. Various circuits including one or more processors represented by the second processor 1404 and a memory represented by the second memory 1405 are coupled via the first bus 1400. The second bus 1400 may further couple various other circuits together, such as a periphery component, a voltage stabilizer and a power management circuit, which is well known in the art and is not repeated herein. A second bus interface 1403 provides an interface between the second bus 1400 and the second transceiver 1401. The second transceiver 1401 may be one element, or may be multiple elements, such as multiple receivers and transmitters. The second transceiver 1401 provides a unit configured to communicate with other devices on a transmission medium. Data processed by the second processor 1404 is transmitted via the second transceiver 1401 and the second antenna 1402 on a radio medium. Furthermore, the second antenna 1402 receives data and transmits the data to the second processor 1404 via the second transceiver 1401.

The second processor 1404 is in charge of managing the second bus 1400 and common processes, and may further provide various functions, e.g., timing, periphery interfaces, voltage adjusting, power source management and other controlling functions. The second memory 1405 may be configured to store data to be used by the second processor 1404 performing operations. In specific, the second processor 1404 may be CPU, application specific integrated circuit (ASIC), field-programmable gate array (FPGA) or complex programmable logic device (CPLD).

A computer readable storage medium storing therein a computer program (instructions) is also provided in an embodiment, and steps of the methods of QoS processing described above are performed when the computer program (instructions) is executed by a processor.

It should be understood that “one embodiment” or “an embodiment” mentioned throughout the specification means that specific features, structures or characteristics associated with the embodiment are included in at least one embodiment of the present disclosure. Hence, terms of “according to one embodiment” or “according to an embodiment” in the specification are not limited to the same embodiment. In addition, those specific features, structures or characteristics can be combined in one or more embodiments in any appropriate manner.

It should be understood, numerical references for respective processes in the embodiments of the present disclosure do not indicate any execution sequence, and these numerical references are not to limit implementation processes of the embodiments of the present disclosure. Execution sequences of the processes are determined based on functions and internal logics of the processes.

In addition, terms of “system” and “network” in the specification may be interchanged.

It should be understood that, the term “and/or” merely describes a relationship between associated objects. Such term may indicate three situations. For example, A and/or B may indicate: mere A, both A and B, or mere B. Furthermore, the symbol “/” usually indicates an “or” relationship between associated objects prior to and after such symbol.

It should be understood that in the embodiments of the present disclosure, “B corresponding to A” indicates that B is associated with A and may be determined based on A. However, it should also be understood that determining B based on A does not mean determining B based on only A, and B may be determined based on A and/or other information.

It should be understood that the method and device provided in the embodiments of the present disclosure may be implemented in other ways. For example, the described embodiments directed to the device are merely exemplary. For example, the units are divided merely in logical function, which may be divided in another way in actual implementation, e.g., multiple units or components may be combined or integrated into another system, or some features may be ignored or not performed. In addition, the disclosed or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, which may be implemented in electronic, mechanical or other forms.

Furthermore, functional units in the embodiments of the present disclosure may be integrated into one processing unit, or may be physically independent, or two or more units are integrated into one unit. The integrated units may be implemented by hardware or by combination of hardware and software.

Integrated units implemented as software functional units may be stored on a computer readable storage medium. The software functional units are stored on a storage medium and include several instructions for enabling a computer device (which may be a personal computer, a server, a network apparatus or the like) to execute partial steps of methods according to embodiments of the present disclosure. The storage medium may include medium that can store program code, such as a USB flash disk, a mobile Hard Disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an an optical disk.

Optional embodiments are described hereinabove. It should be noted that various improvements and polishments can be made by those ordinary skilled in the art without departing from the principle of the present disclosure. The improvements and polishments fall within the protection scope of the present disclosure.

Claims

1. A method of quality of service (QoS) processing, comprising: determining, by a first device, whether the first device satisfies a QoS requirement of one or more flows of a user equipment (UE); andtransmitting, by the first device, a first message to a second device, in the case that the first device does not satisfy the QoS requirement of the one or more flows of the UE;wherein the first message comprises one of or a combination of more than one of: QoS flow identifier (QFI), radio bearer (RB) ID, indication information indicating that the QoS requirement is not satisfied, or recommended QoS parameter.

2. The method according to claim 1, wherein determining, by the first device, whether the first device satisfies the QoS requirement of the one or more flows of the UE comprises: determining, by the first device, whether the first device satisfies the QoS requirement of the one or more flows of the UE, in accordance with QoS parameter(s) of the one or more flows or in accordance with the QoS parameter(s) of the one or more flows and a mapping relation between data radio bearer (DRB) and flow.

3. The method according to claim 2, further comprising: receiving, by the first device, the QoS parameter(s) of the one or more flows transmitted by the second device and the mapping relation between DRB and flow on the second device.

4. The method according to claim 1, wherein, the first device is a secondary base station and the second device is a primary base station; orthe first device is a distributed unit (DU) and the second device is a central unit (CU).

5. The method according to claim 2, wherein the QoS parameter comprises a suggested guaranteed bit rate and/or a suggested maximum bit rate.

6. A method of quality of service (QoS) processing, comprising: receiving, by a second device, a first message transmitted by a first device, wherein the first message is generated in the case that the first device does not satisfy a QoS requirement of one or more flows of a user equipment (UE);wherein the first message comprises one of or a combination of more than one of: QoS flow identifier (QFI), radio bearer (RB) ID, indication information indicating that the QoS requirement is not satisfied, or recommended QoS parameter.

7. The method according to claim 6, further comprising: determining, by the second device, in accordance with the first message, whether a bearer type change is needed; ortransmitting, by the second device, in accordance with the first message, a second message to a core network.

8. The method according to claim 7, wherein the second message comprises one of or a combination of more than one of: the QFI, the indication information indicating that the QoS requirement is not satisfied, or a suggested QoS parameter.

9. The method according to claim 6, wherein, the first device is a secondary base station and the second device is a primary base station; orthe first device is a distributed unit (DU) and the second device is a central unit (CU).

10. The method according to claim 6, wherein the QoS parameter comprise a suggested guaranteed bit rate and/or a suggested maximum bit rate.

11. A first device, comprising a memory, a processor and a program stored on the memory and executable by the processor, wherein the processor is configured to execute the program to: determine whether the first device satisfies a QoS requirement of one or more flows of a user equipment (UE); andtransmit, in the case that the first device does not satisfy the QoS requirement of the one or more flows of the UE, a first message to a second device;wherein the first message comprises one of or a combination of more than one of: QoS flow identifier (QFI), radio bearer (RB) ID, indication information indicating that the QoS requirement is not satisfied, or recommended QoS parameter.

12. The first device according to claim 11, wherein the processor is configured to: determine whether the first device satisfies the QoS requirement of the one or more flows of the UE, in accordance with QoS parameter(s) of the one or more flows or in accordance with the QoS parameter(s) of the one or more flows and a mapping relation between data radio bearer (DRB) and flow.

13. The first device according to claim 12, wherein the processor is further configured to: receive the QoS parameter(s) of the one or more flows transmitted by the second device and the mapping relation between DRB and flow on the second device.

14. The first device according to claim 11, wherein, the first device is a secondary base station and the second device is a primary base station; orthe first device is a distributed unit (DU) and the second device is a central unit (CU).

15. The first device according to claim 12, wherein the QoS parameter comprises a suggested guaranteed bit rate and/or a suggested maximum bit rate.

16. A second device, comprising a memory, a processor and a program stored on the memory and executable by the processor, wherein the processor is configured to execute the program to implement steps of the method of QoS processing according to claim 6.

17. The second device according to claim 16, wherein the processor is further configured to: determine, in accordance with the first message, whether a bearer type change is needed; ortransmit, in accordance with the first message, a second message to a core network.

18. The second device according to claim 17, wherein the second message comprises one of or a combination of more than one of: the QFI, the indication information indicating that the QoS requirement is not satisfied, or a suggested QoS parameter.

19. The second device according to claim 16, wherein, the first device is a secondary base station and the second device is a primary base station; orthe first device is a distributed unit (DU) and the second device is a central unit (CU).

20. The second device according to claim 16, wherein the QoS parameter comprises a suggested guaranteed bit rate and/or a suggested maximum bit rate.

21-22. (canceled)