Quality of service flow scheduling method and device, network equipment and storage medium

Abstract

The embodiment of the invention provides a QoS flow scheduling method and device, network equipment and a storage medium. The QoS flow scheduling method executed by a first network device may comprise: determining a candidate configuration set of a QoS flow, the candidate configuration set comprising a plurality of sets of parameter configurations of the QoS flow;

Description

Method and device for scheduling quality of service flow, network equipment and storage medium Technical Field

[0001] The present disclosure relates to the field of wireless communication technology but is not limited to the field of wireless communication technology, and in particular to a method and apparatus for scheduling Quality of Service (QoS) flows, a network device, and a storage medium. Background Art

[0002] Each QoS (Flow) defines a QoS configuration, which has one or more QoS parameters that constrain the characteristics of the QoS flow. These QoS parameters include, but are not limited to, 5G Quality of Service Indicator (QI), priority level, QoS reflective attributes, and packet delay budget.

[0003] For example, QoS flows can be divided into Guaranteed Bit Rate (GBR) QoS flows and non-GBR QoS flows.

[0004] Typically, a base station, as an access network device, schedules and allocates resources for the corresponding QoS according to the QoS configuration of the QoS flow. In the prior art, the core network only provides a set of parameter configurations for the base station QoS flow.

[0005] Summary of the Invention

[0006] Embodiments of the present disclosure provide a QoS flow scheduling method and apparatus, a network device, and a storage medium network device.

[0007] A first aspect of an embodiment of the present disclosure provides a scheduling method for a QoS flow, which is performed by a first network device and includes: determining a candidate configuration set for the QoS flow, wherein the candidate configuration set includes: multiple sets of parameter configurations for the QoS flow.

[0008] A second aspect of an embodiment of the present disclosure provides a method for scheduling a QoS flow, wherein the method is performed by a second network device, and the method includes:

[0009] A QoS request message is sent, where the QoS request message indicates a candidate configuration set of a QoS flow; the candidate configuration set includes: multiple sets of parameter configurations of the QoS flow.

[0010] A third aspect of an embodiment of the present disclosure provides a scheduling device for a QoS flow, wherein the device includes: a determination module configured to determine a candidate configuration set for the QoS flow, wherein the candidate configuration set includes: multiple sets of parameter configurations for the QoS flow.

[0011] A fourth aspect of the embodiments of the present disclosure provides a QoS flow scheduling device, wherein the device includes:

[0012] The sending module is configured to send a QoS request message, where the QoS request message indicates a candidate configuration set of a QoS flow; the candidate configuration set includes: multiple sets of parameter configurations of the QoS flow.

[0013] A fifth aspect of an embodiment of the present disclosure provides a network device, comprising a processor, a transceiver, a memory, and an executable program stored in the memory and capable of being run by the processor, wherein when the processor runs the executable program, the scheduling method for QoS flows provided in the first or second aspect described above is executed.

[0014] A sixth aspect of the embodiments of the present disclosure provides a computer storage medium storing an executable program; after the executable program is executed by a processor, the scheduling method for the QoS flow provided in the first or second aspect can be implemented.

[0015] According to the technical solution provided by the embodiment of the present disclosure, the first network device will determine a candidate configuration set for QoS flow scheduling. The candidate configuration set may include a set of parameter configurations. These parameter configurations can be used for scheduling QoS flows in different situations, thereby realizing scheduling of QoS flows in different situations to meet the QoS flow scheduling requirements in different situations.

[0016] It should be understood that the foregoing general description and the following detailed description are merely exemplary and explanatory and are not restrictive of the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present invention and, together with the description, serve to explain the principles of the embodiments of the present invention.

[0018] FIG1 is a schematic structural diagram of a wireless communication system according to an exemplary embodiment;

[0019] FIG2A is a schematic flow diagram illustrating a method for scheduling a QoS flow according to an exemplary embodiment;

[0020] FIG2B is a schematic flow diagram illustrating a method for scheduling a QoS flow according to an exemplary embodiment;

[0021] FIG3A is a flow chart showing a method for scheduling a QoS flow according to an exemplary embodiment.

[0022] FIG3B is a schematic diagram showing a flow chart of a method for scheduling a QoS flow according to an exemplary embodiment;

[0023] FIG4 is a schematic flow diagram of a method for scheduling a QoS flow according to an exemplary embodiment;

[0024] FIG5 is a schematic flow diagram of a method for scheduling a QoS flow according to an exemplary embodiment;

[0025] FIG6 is a schematic flow diagram of a method for scheduling a QoS flow according to an exemplary embodiment;

[0026] FIG7 is a schematic structural diagram of a QoS flow scheduling device according to an exemplary embodiment;

[0027] FIG8 is a schematic structural diagram of a QoS flow scheduling device according to an exemplary embodiment;

[0028] Fig. 9 is a schematic structural diagram showing a network device according to an exemplary embodiment. DETAILED DESCRIPTION

[0029] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all possible implementations consistent with the present invention. Rather, they are merely examples of apparatuses and methods consistent with certain aspects of the present invention, as detailed in the appended claims.

[0030] The terms used in the embodiments of the present disclosure are for the purpose of describing specific embodiments only and are not intended to limit the embodiments of the present disclosure. The singular forms "a," "an," and "the" used in the embodiments of the present disclosure and the appended claims are also intended to include plural forms unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.

[0031] It should be understood that although the terms first, second, third, etc. may be used to describe various information in the embodiments of the present disclosure, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of the embodiments of the present disclosure, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0032] Please refer to Figure 1, which shows a schematic diagram of the structure of a wireless communication system provided by an embodiment of the present disclosure. As shown in Figure 1, the wireless communication system is a communication system based on cellular mobile communication technology, and the wireless communication system may include: a plurality of UEs 11 and a plurality of access devices 12.

[0033] UE11 may refer to a device that provides voice and / or data connectivity to a user. UE11 may communicate with one or more core networks via a Radio Access Network (RAN). UE11 may be an IoT UE, such as a sensor device, a mobile phone (or a "cellular" phone), and a computer with an IoT UE. For example, it may be a fixed, portable, pocket-sized, handheld, computer-built-in, or vehicle-mounted device. For example, a station (STA), a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote UE (remote terminal), an access terminal, a user terminal, a user agent, a user device, or a user UE (user equipment, UE). Alternatively, UE11 may also be a device of an unmanned aerial vehicle. Alternatively, UE11 may also be an in-vehicle device, for example, a driving computer with wireless communication capabilities, or a wireless communication device connected to an external driving computer. Alternatively, UE11 may also be a roadside device, for example, a street lamp, a traffic light, or other roadside device with a wireless communication function.

[0034] The access device 12 may be a network-side device in a wireless communication system. The wireless communication system may be a fourth generation mobile communication technology (4G) system, also known as a long term evolution (LTE) system; or, the wireless communication system may be a 5G system, also known as a new radio (NR) system or a 5G NR system. Alternatively, the wireless communication system may be a next generation system of the 5G system. The access network in the 5G system may be referred to as NG-RAN (New Generation-Radio Access Network). Alternatively, an MTC system.

[0035] Among them, the access device 12 can be an evolved access device (eNB) adopted in a 4G system. Alternatively, the access device 12 can also be an access device (gNB) that adopts a centralized distributed architecture in a 5G system. When the access device 12 adopts a centralized distributed architecture, it usually includes a centralized unit (CU) and at least two distributed units (DU). The centralized unit is provided with a protocol stack of a packet data convergence protocol (PDCP) layer, a radio link layer control protocol (RLC) layer, and a media access control (MAC) layer; the distributed unit is provided with a physical (PHY) layer protocol stack. The embodiment of the present disclosure does not limit the specific implementation method of the access device 12.

[0036] A wireless connection can be established between the access device 12 and the UE 11 via a wireless air interface. In different implementations, the wireless air interface is a wireless air interface based on the fourth generation mobile communication network technology (4G) standard; or, the wireless air interface is a wireless air interface based on the fifth generation mobile communication network technology (5G) standard, for example, the wireless air interface is a new air interface; or, the wireless air interface can also be a wireless air interface based on the next generation mobile communication network technology standard of 5G.

[0037] In some embodiments, UEs 11 may also establish E2E (End-to-End) connections, such as in vehicle-to-everything (V2X) communication scenarios such as V2V (vehicle-to-vehicle), V2I (vehicle-to-infrastructure), and V2P (vehicle-to-pedestrian).

[0038] In some embodiments, the wireless communication system may further include a network management device 13 .

[0039] Several access devices 12 are respectively connected to a network management device 13. The network management device 13 may be a core network device in a wireless communication system. For example, the network management device 13 may be a mobility management entity (MME) in an evolved packet core (EPC). Alternatively, the network management device may be other core network devices, such as a serving gateway (SGW), a public data network gateway (PGW), a policy and charging rules function (PCRF), or a home subscriber server (HSS). The embodiments of the present disclosure do not limit the implementation form of the network management device 13.

[0040] As shown in FIG2A , an embodiment of the present disclosure provides a method for scheduling a QoS flow, which is performed by a first network device. The method may include:

[0041] S100: Determine a candidate configuration set for a QoS flow, wherein the candidate configuration set includes: multiple sets of parameter configurations for the QoS flow.

[0042] The first network device may be an access network device. Exemplarily, the access network device includes but is not limited to a base station, and the base station may be an eNB or a gNB.

[0043] The parameter configuration herein may include one or more QoS parameters in the QoS configuration, including but not limited to GBR, reflective QoS attributes, packet data delay budget, priority level and / or 5QI.

[0044] These QoS parameters can be used by the base station to schedule and allocate resources to QoS flows.

[0045] The candidate configuration set includes at least one of the following:

[0046] Collaborative parameter configuration, wherein the collaborative parameter configuration is: parameter configuration for collaborative scheduling of multiple QoS flows;

[0047] Non-cooperative parameter configuration, wherein the non-cooperative parameter configuration is: parameter configuration for separate scheduling of QoS flows.

[0048] The collaborative parameter configuration is: parameter configuration for collaborative scheduling of multiple QoS flows, for example, two or more QoS flows are associated, and the QoS values ​​of some of these QoS flows will affect the quality of the business or services provided by these multiple QoS flows. At this time, in order to ensure the communication quality of the business or service, for example, in order to ensure that the delay is small enough, the rate is fast enough, and the bit error rate is low enough, etc., one or more of them, it is necessary to collaboratively schedule these QoS flows. The parameter configuration used at this time may be different from that in non-collaborative scenarios. For example, there are more stringent delay requirements, which is the collaborative parameter configuration.

[0049] As an embodiment, two or more QoS flows use their own parameter configurations when there is no collaborative scheduling. The description configuration includes one or more QoS parameters. The QoS description is specifically defined in Tables 1 to 3 below, such as parameter configuration 1 and parameter configuration 2. In the collaborative scheduling scenario, each will use its own collaborative scheduling parameter configuration, parameter configuration 1' and parameter configuration 2'. At this time, for QoS flow 1, the candidate configuration set includes multiple sets of parameter configurations, namely parameter configuration 1 and parameter configuration 1'; for QoS flow 2, the candidate configuration set includes multiple sets of parameter configurations, namely parameter configuration 2 and parameter configuration 2'.

[0050] Non-cooperative parameter configuration is also called separate scheduling parameter configuration, which is used for separate scheduling of each QoS flow. In the separate scheduling scenario, the first network device will perform separate scheduling for the QoS flow, for example, only referring to the QoS value of the QoS flow itself, etc., for separate scheduling.

[0051] As an example, there may be multiple candidate configurations for QoS flows in a single scheduling scenario: parameter configuration 1 and parameter configuration 2. Parameter configuration 2 will be used when the network detects an abnormality, and parameter configuration 1 will be used in other cases.

[0052] In one embodiment, there may be one or more sets of collaborative parameter configurations and / or non-collaborative parameter configurations.

[0053] In one embodiment, for QoS flows that are determined to be scheduled only individually, such as services for typical users making traditional voice calls, the candidate configuration set may include multiple sets of non-cooperative parameter configurations, excluding cooperative parameter configurations.

[0054] In another embodiment, for a multimodal service of a multimodal device, there may be only coordinated scheduling but no separate scheduling. The candidate configuration set may include: multiple sets of coordinated parameter configurations, excluding non-coordinated parameter configurations.

[0055] In another embodiment, for QoS flows that are both individually scheduled and cooperatively scheduled, the candidate parameter configuration set may include both cooperative parameter configurations and non-cooperative parameter configurations. Exemplarily, the candidate parameter configuration set includes: at least one set of non-cooperative parameter configurations and at least one set of cooperative parameter configurations.

[0056] In an embodiment of the present disclosure, the candidate configuration set includes multiple sets of parameter configurations, which can be any one of the aforementioned collaborative parameter configurations and non-collaborative parameter configurations. The specific included parameter configurations can be determined based on the scheduling scenarios and / or possible scheduling situations of the QoS flow.

[0057] Exemplarily, in one embodiment, the non-coordinated parameter configuration includes: multiple sets of parameter configurations for independently scheduling QoS flows in different situations.

[0058] For example, different individual scheduling situations may include at least one of the following:

[0059] Separate scheduling situations corresponding to different network states;

[0060] Separate scheduling situations corresponding to different UE states;

[0061] Different business contract situations correspond to separate scheduling situations.

[0062] In some cases, when the remaining network bandwidth is large, QoS flow of high-definition video can be provided. At this time, in the case of separate scheduling, parameter configuration with high QoS value can be selected for separate scheduling of QoS flow, thereby improving the effective utilization of network resources.

[0063] In other cases, when the UE has few remaining resources, the QoS value of the QoS flow can be appropriately lowered. For example, when the clarity of the video QoS flow is appropriately lowered to reduce the video playback freeze phenomenon, a parameter configuration with a lower QoS value can be selected to perform separate scheduling of the QoS flow.

[0064] In some cases, the user and the operator can base their agreement on the service contract information. If a service with a high QoS value is signed, the user can use the parameter configuration with a high QoS value for separate scheduling. If a service with a high QoS value is not signed, the user can use the parameter configuration with a lower QoS value for separate scheduling.

[0065] As shown in FIG2B , an embodiment of the present disclosure provides a method for scheduling a QoS flow, which is performed by a first network device. The method includes:

[0066] S110: Determine a coordination parameter configuration for coordinated scheduling of multiple QoS flows.

[0067] As an embodiment, the collaborative parameter configuration is a parameter configuration when a QoS flow is collaboratively scheduled with other QoS flows. The parameter configuration here may include one or more QoS parameters in the QoS configuration. The QoS parameters include but are not limited to GBR, reflective QoS attributes, packet data delay budget, priority level, and / or 5QI.

[0068] As an embodiment, non-cooperative parameter configuration is: a QoS flow switches to another set of candidate QoS parameter configurations when a trigger event is met. The parameter configuration here may include one or more QoS parameters in the QoS configuration. The QoS parameters include but are not limited to GBR, reflective QoS attributes, packet data delay budget, priority level, and / or 5QI.

[0069] Illustratively, the aforementioned QoS parameters may be any one of Tables 1 to 3.

[0070]

[0071]

[0072] Table 1

[0073]

[0074]

[0075] Table 2

[0076]

[0077]

[0078] Table 3

[0079] It is worth noting that any QoS parameter shown in Tables 1 to 3 can be used alone or in combination with other QoS parameters.

[0080] This collaborative parameter configuration is used to enable devices to collaboratively schedule multiple QoS flows. This is typically done in a collaborative scheduling scenario. Typically, the multiple QoS flows being collaboratively scheduled are related, such as in a federated learning scenario, where training data is exchanged between any two different devices.

[0081] This non-cooperative parameter configuration is also used to execute the device's independent scheduling of a single QoS flow under the trigger conditions corresponding to different trigger events. For example, if a certain QoS indicator fails to reach the threshold, it will switch to another set of scheduling QoS parameters.

[0082] In one embodiment, the candidate configuration set includes: multiple sets of parameter configurations; the candidate configuration set includes: a set of reference parameter configurations and a difference configuration; the difference configuration indicates the difference between the non-reference parameter configuration in the multiple sets of parameter configurations and the reference parameter configuration; or, the candidate configuration set includes: multiple sets of parameter configurations; the candidate configuration set includes: a set of reference parameter configurations and a conversion relationship configuration, wherein the conversion relationship configuration indicates the conversion relationship between the non-reference parameter configuration in the multiple sets of parameter configurations and the reference parameter configuration.

[0083] The reference parameter configuration here can be any specified parameter configuration. For example, the reference parameter configuration can be the preset parameter configuration of the QoS flow in a separate scheduling scenario, and other non-reference parameter configurations can be any parameter configuration different from the reference parameter configuration.

[0084] For example, a set of reference parameter configurations is used for QoS parameters when no multimodal services are carried, i.e., there is no requirement for coordinated scheduling of multiple flows;

[0085] Exemplarily, if the candidate configuration set includes: a set of non-cooperative parameter configurations and at least one set of cooperative parameter configurations, the set of non-cooperative parameter configurations may be selected as the aforementioned reference parameter configuration, and all other cooperative parameter configurations may be selected as difference configurations.

[0086] As an embodiment, two or more QoS flows use their own QoS parameters, such as parameter configuration 1 and parameter configuration 2, when there is no collaborative scheduling. In the collaborative scheduling scenario, they will all use their own collaborative scheduling parameter configurations, parameter configuration 1' and parameter configuration 2'. At this time, for QoS flow 1, the candidate configuration set includes multiple sets of parameter configurations, namely parameter configuration 1 and parameter configuration 1'; at this time, parameter configuration 1 is the reference parameter configuration; parameter configuration 2 can be determined by the differential configuration and the reference parameter configuration. For example, the packet data delay estimated by parameter configuration 1 is 100ms, and the differential configuration indicates -50ms. Based on parameter configuration 1 and the differential configuration, the packet data delay of parameter configuration 2 is 50ms. For QoS flow 2, the candidate configuration set includes multiple sets of parameter configurations, namely parameter configuration 2 and parameter configuration 2'. At this time, parameter configuration 2 is determined by combining parameter configuration 2 and the differential configuration.

[0087] Exemplarily, if the candidate configuration set includes multiple sets of non-cooperative parameter configurations, one of the sets of non-cooperative parameter configurations may be selected as the aforementioned reference parameter configuration, and the other non-cooperative parameter configurations may be selected as difference configurations.

[0088] As an example, there may be multiple candidate configurations for QoS flows in a single scheduling scenario. Parameter configuration 1 and parameter configuration 2; when the network detects an abnormality, parameter configuration 2 will be used, and in other cases, parameter configuration 1 will be used. In this case, parameter configuration 1 is the reference parameter configuration; reference parameter configuration 2 is the difference configuration;

[0089] Exemplarily, if the candidate configuration set includes: a set of non-cooperative parameter configurations and at least one set of collaborative parameter configurations, the set of non-cooperative parameter configurations can be selected as the aforementioned reference parameter configuration, and all other collaborative parameter configurations can be selected as non-cooperative parameter configurations.

[0090] As another example, if the candidate configuration set includes: a set of collaborative parameter configurations and at least one set of non-collaborative parameter configurations, this set of collaborative parameter configurations can be selected as the reference parameter configuration, and the other parameter configurations are all non-collaborative parameter configurations, or, a set of non-collaborative parameter configurations with the smallest corresponding QoS value can be selected as the reference parameter configuration, and the other parameter configurations are all non-collaborative parameter configurations.

[0091] Exemplarily, first, the reference parameter configuration is a set of parameter configurations in the candidate configuration set.

[0092] During specific implementation, a reference parameter configuration is selected from multiple sets of parameter configurations in the candidate configuration set.

[0093] The reference parameter configuration may be at least one of the following sets of parameter configurations:

[0094] Parameter configuration for estimating the minimum packet data delay;

[0095] Parameter configuration for estimating the maximum packet data delay;

[0096] Any set of parameter configurations specified by the second network device;

[0097] A set of parameter configurations agreed upon by the protocol.

[0098] The candidate configuration set includes: multiple sets of parameter configurations; the candidate configuration set includes: a reference parameter configuration and a difference configuration; the difference configuration indicates the difference between the non-reference parameter configuration in the multiple sets of parameter configurations and the reference parameter configuration;

[0099] or,

[0100] The candidate configuration set includes: multiple sets of parameter configurations; the candidate configuration set includes: a set of reference parameter configurations and a conversion relationship configuration, wherein the conversion relationship configuration indicates the conversion relationship between the non-reference parameter configurations in the multiple sets of parameter configurations and the reference parameter configuration.

[0101] Regardless of collaborative parameter configuration or non-collaborative parameter configuration, QoS parameters are assigned to QoS flows.

[0102] Therefore, the same QoS parameters configured in different sets of parameters can be differentiated to obtain the aforementioned differences. Compared with using one or more bits to indicate the parameter value of the original QoS parameter, the bits are only used to indicate the difference value, which can reduce bit overhead.

[0103] The difference configuration may include, but is not limited to, directly indicating the difference value.

[0104] Similarly, the parameter values ​​of the same QoS parameters of different sets of parameter configurations can be converted using a conversion relationship. In this way, by carrying the indication of the conversion relationship through one or more bits, it has the characteristic of low bit overhead compared to completely carrying the parameter values ​​of all QoS parameters of each set of parameter configurations.

[0105] The conversion relationship configuration may include but is not limited to a direct conversion relationship identifier.

[0106] In some embodiments, the conversion relationship between the non-cooperative parameter configuration and the cooperative parameter configuration indicates at least one of the following:

[0107] a ratio between the reference parameter configuration and the same parameter of the non-reference parameter configuration;

[0108] a difference between the reference parameter configuration and the same parameter of the non-reference parameter configuration;

[0109] A conversion function between the same parameters of the reference parameter configuration and the non-reference parameter configuration.

[0110] For example, the packet data delay budget of the QoS flow in the cooperative scheduling scenario is 1 / 2 or 1 / 3 of the packet data delay budget in the individual scheduling scenario.

[0111] As another example, the packet data delay budget of the QoS flow in the cooperative scheduling scenario is a difference between the packet data delay budgets in the individual scheduling scenario, such as 10ms, 20ms, or 50ms.

[0112] The conversion function may be a conversion function composed of any four arithmetic operations or other conversion functions. For example, in some cases, when determining the conversion relationship between multiple QoS parameters in collaborative parameter configuration and non-collaborative parameter configuration, the ratio and difference alone cannot well reflect the conversion relationship between the two. It may be necessary to fit the conversion relationship between the two through function fitting. The conversion function may be a polynomial function or other function.

[0113] In some embodiments, the co-scheduled multiple QoS flows may include at least one of the following:

[0114] Different QoS flows corresponding to different multimodal input devices in the same multimodal input scenario;

[0115] In the same multimodal output scenario, different multimodal output devices correspond to different QoS flows;

[0116] QoS flows corresponding to different learning devices in the federated learning scenario.

[0117] If the coordination parameter configuration takes effect, the base station coordinates scheduling of multiple QoS flows. The base station coordinates resource allocation and scheduling for the associated QoS flows. This coordination is reflected in any of the following aspects:

[0118] Allocate radio resources for multiple QoS flows simultaneously;

[0119] Simultaneously release radio resources allocated to multiple QoS flows;

[0120] The amount of resources allocated to the multiple QoS flows is adjusted simultaneously, where the adjustment of the amount of resources includes: increasing the amount of resources and / or decreasing the amount of resources.

[0121] Of course, the above is only an example of the coordinated allocation and scheduling of multiple QoS flows, and the specific implementation is not limited to the above example.

[0122] In the disclosed embodiment, the first network device determines the collaborative parameter configuration of multiple QoS flows, thereby requiring collaborative scheduling of multiple QoS flows to reduce the scheduling asynchrony problem caused by independent scheduling of multiple QoS flows that require collaborative scheduling, and further reduces the waste of resources caused by such asynchrony problem or the phenomenon of poor service quality caused by the waste of resources.

[0123] As shown in FIG3A , an embodiment of the present disclosure provides a method for scheduling a QoS flow, which is performed by a first network device and may include:

[0124] S111: Receive a QoS request message, wherein the QoS request message includes configuration information of a candidate configuration set of a QoS flow,

[0125] The candidate configuration set includes at least: at least two sets of parameter configurations of the QoS flow.

[0126] Exemplarily, the candidate configuration set includes multiple sets of the following parameter configurations;

[0127] Coordination parameter configuration, used for the coordinated scheduling of this QoS flow and other QoS flows;

[0128] Non-cooperative parameter configuration is used for independent scheduling of this QoS flow.

[0129] In an embodiment of the present disclosure, an access network device such as a base station receives a QoS request message from a core network device. The QoS request message includes configuration information of a candidate configuration set of a QoS flow.

[0130] For example, QoS flow A and QoS flow B are two QoS flows in the same collaborative scheduling scenario. If the first network device receives a QoS request message and sends a QoS request message for QoS flow A, the candidate configuration set indicated by the QoS request message includes the system parameter configuration for collaborative scheduling with QoS flow B. In this case, after receiving the QoS request message, the first network device can use the collaborative parameter configuration in the candidate configuration set indicated by the QoS request message for QoS flow A to schedule QoS flow A when collaborative scheduling of QoS flow A and QoS flow B is required.

[0131] As shown in FIG3B , an embodiment of the present disclosure provides a method for scheduling a QoS flow, which is performed by a first network device and may include:

[0132] S112: Determine candidate configurations according to the protocol.

[0133] The protocols here include: standard protocols that have been recognized and standardized by the industry, and / or private protocols jointly customized by multiple manufacturers or manufacturers.

[0134] If the protocol specifies multiple candidate configuration sets for QoS flow scheduling, the first network device can know the candidate configuration set for the QoS flow by querying the protocol, and obtain the coordination parameter configuration based on the determined candidate configuration set.

[0135] Exemplarily, the candidate configuration set may be a set containing only coordinated parameter configurations, where the core network and / or protocol limit the coordinated parameter configurations to only those for QoS flows. Furthermore, exemplarily, the candidate configuration set may also include non-coordinated parameter configurations in addition to the coordinated parameter configurations. These non-coordinated parameter configurations may be referred to as independent parameter configurations, and may be used for independent scheduling of corresponding QoS flows.

[0136] In some embodiments, the candidate configuration set further indicates: a non-cooperative parameter configuration for separate scheduling of QoS flows.

[0137] If the need for coordinated scheduling of QoS flows A and B is eliminated, but QoS flow A is still being transmitted, QoS flow A can be independently scheduled using the non-coordinated parameter configuration of the QoS flows.

[0138] For example, in a recording scenario with multiple recording devices, if the QoS of different recording devices are transmitted separately, the two QoS flows may need to be co-scheduled. For example, by co-scheduling the co-transmission of QoS flows, it is ensured that the delay difference of the data flows transmitted by multiple recording devices when reaching the receiving end is not too large, thereby reducing the phenomenon that the image received by the receiving end is always missing a part due to the long arrival delay of the data flow of a certain recording device. In some scenarios, if the image recorded by a certain recording device is cut out, the data flow of the recording device A does not need to continue to be co-scheduled with other recording devices. In this scenario, the separate scheduling of the recording device A will be restored. In the separate scheduling scenario, the resources allocated to the route device A can be released, or the resources allocated to the recording device A can be reduced. Of course, the above is only an example, and the specific implementation is not limited to this example.

[0139] In one embodiment, the candidate configuration set indicates the collaborative parameter configuration and the non-collaborative parameter configuration, and the candidate configuration set includes a non-collaborative parameter configuration and a first difference configuration, wherein the first difference configuration indicates: a difference configuration of the collaborative parameter configuration relative to the non-collaborative parameter configuration;

[0140] or,

[0141] The candidate configuration set indicates the collaborative parameter configuration and the non-collaborative parameter configuration, and the candidate configuration set includes a collaborative parameter configuration and a second difference parameter configuration, wherein the second difference configuration includes: a difference configuration of the non-collaborative parameter configuration relative to the collaborative parameter configuration.

[0142] In some cases, the values ​​of certain QoS parameters of the collaborative parameter configuration and the non-collaborative parameter configuration are the same. If only the first difference configuration or the second difference configuration is included, the QoS configuration for both the collaborative parameter configuration and the non-collaborative parameter configuration can be reduced, thereby reducing the bit overhead.

[0143] In other cases, the values ​​of all QoS parameters of the collaborative parameter configuration and the non-collaborative parameter configuration may be different, but one is used as a reference value to obtain the difference between the two. The difference is smaller than the value of the QoS parameter being subtracted, so fewer bits can be used to indicate it, thereby reducing bit overhead.

[0144] Therefore, adopting this method can reduce bit overhead, and is particularly suitable for a method in which the core network sends the candidate configuration set to the access network.

[0145] In some embodiments, the candidate configuration set indicates the collaborative parameter configuration and the non-collaborative parameter configuration, and the candidate configuration set includes the non-collaborative parameter configuration and a first conversion identifier, wherein the first conversion identifier indicates a conversion relationship between the non-collaborative parameter configuration and the collaborative parameter configuration;

[0146] or,

[0147] The candidate configuration set indicates the collaborative parameter configuration and the non-collaborative parameter configuration, and the candidate configuration set includes the collaborative parameter configuration and a second conversion identifier, wherein the second conversion identifier indicates a conversion relationship between the non-collaborative parameter configuration and the collaborative parameter configuration.

[0148] In some embodiments, the first conversion identifier and the second conversion identifier indicate a conversion relationship.

[0149] For example, the bandwidth under independent scheduling and the bandwidth under cooperative scheduling can satisfy one or more conversion relationships, and the conversion relationship currently used can be determined by the first conversion identifier or the second conversion identifier carried by the candidate configuration set. This method of indicating cooperative parameter configuration and non-cooperative parameter configuration has the characteristic of low bit overhead and is particularly suitable for scenarios where the configuration information of the candidate configuration set needs to be transmitted between different network devices.

[0150] In some embodiments, the conversion relationship between the non-cooperative parameter configuration and the cooperative parameter configuration indicates at least one of the following:

[0151] a ratio between the non-cooperative parameter configuration and the same parameter of the cooperative parameter configuration;

[0152] a difference between the same parameter of the non-coordinated parameter configuration and the coordinated parameter configuration;

[0153] A conversion function between the same parameters of the non-cooperative parameter configuration and the cooperative parameter configuration.

[0154] For example, the packet data delay budget of the QoS flow in the cooperative scheduling scenario is 1 / 2 or 1 / 3 of the packet data delay budget in the individual scheduling scenario.

[0155] As another example, the packet data delay budget of the QoS flow in the cooperative scheduling scenario is a difference between the packet data delay budgets in the individual scheduling scenario, such as 10ms, 20ms, or 50ms.

[0156] The above different ratios or different differences may correspond to different first conversion identifiers and / or second conversion identifiers.

[0157] Different from the first difference configuration and the second difference configuration in the previous embodiment, if the first conversion identifier and / or the second conversion identifier indicate a difference value, they may not be the difference value itself. For example, the first conversion identifier and the second conversion identifier may be a difference value index or a difference value sequence number.

[0158] In other embodiments, the first conversion identifier and the second conversion identifier may at least convert different conversion relationships in the table, and the conversion relationship between the coordinated parameter configuration and the non-coordinated parameter configuration may be known by looking up the table.

[0159] In some embodiments, the QoS request message includes at least one of the following:

[0160] QoS establishment request message;

[0161] QoS modification request message.

[0162] The configuration information of the candidate configuration set is directly carried in the QoS establishment request message, so that when the corresponding QoS flow is established, the first network device knows the candidate configuration set of the QoS flow.

[0163] When the network status and / or the status of the UE participating in the communication changes, there may be a need to modify the QoS flow. At this time, the first network device will receive a QoS modification request message. The QoS modification request message carries the configuration information of the candidate configuration set. While modifying the QoS flow, the collaborative parameter configuration of the modified QoS flow can be synchronously known.

[0164] In short, no matter which method is adopted, if the first network device obtains the configuration information of the candidate configuration set by receiving a QoS request message, on the one hand, it can obtain the configuration information of the candidate configuration set that at least includes the collaborative parameter configuration without introducing a new message. On the other hand, it can obtain the configuration information in the QoS flow scheduling scenario when the QoS flow is initially established or modified. It covers most scenarios that require obtaining collaborative parameter configurations, and has the characteristics of simple implementation and wide coverage.

[0165] The QoS setup request message includes but is not limited to: a Protocol Data Unit (PDU) session resource setup request (PDU Session Resource Setup Request) and / or an Initial Context Setup Request (Initial Context Setup Request).

[0166] The QoS modification request message includes but is not limited to: a PDU session resource modification request (PDU Session Resource Modify Request).

[0167] In some embodiments, the method further comprises:

[0168] In response to determining that there is a co-scheduling requirement for QoS flows, co-scheduling at least two of the QoS flows according to the co-scheduling parameter configuration.

[0169] Co-scheduling of at least two QoS flows is performed only when there is a need for co-scheduling. When there is no need for co-scheduling, co-scheduling of QoS flows can be performed without referring to the co-scheduling parameter configuration, and individual scheduling of a single QoS flow can be performed.

[0170] When determining that multiple QoS flows are associated with each other, the first network device can determine that there is a need for coordinated scheduling of the QoS flows. For example, when the first network device receives resource scheduling requests from multiple UEs in the same UE group, it can determine that there is an associated relationship between the different QoS flows corresponding to the multiple UEs. Of course, this is merely an example of how the first network device can determine whether there is a need for coordinated scheduling of multiple QoS flows, and the specific implementation is not limited to this.

[0171] In response to a change in the coordinated scheduling situation, the coordinated parameter configuration of the coordinated scheduling is replaced according to the coordinated parameter configuration.

[0172] The situation of the collaborative scheduling changes, which may be at least one of the above situations.

[0173] If the above situation occurs, the second network device may send collaborative control information, which triggers the first device to switch the collaborative parameter configuration for collaboratively scheduling multiple QoS flows.

[0174] Any of the above situations can correspond to a trigger event, and the event identifier of the trigger event can be carried in the collaborative control information. In this way, when the first network device receives the collaborative control information, it will also know the trigger event that currently causes the transmission of the collaborative control information, and can further select the collaborative parameter configuration after switching based on the trigger event.

[0175] That is, in one embodiment, the coordinated control information may also indicate a triggering event requiring coordinated parameter configuration for coordinated scheduling of multiple QoS flows.

[0176] As an embodiment, two or more QoS flows use their own QoS parameters, such as parameter configuration 1 and parameter configuration 2, when there is no collaborative scheduling. However, in the collaborative scheduling scenario, QoS flow 1 cannot meet the requirements, which is considered to have detected a trigger event. Then, for the two collaborative QoS flows, their respective candidate collaborative scheduling parameter configurations, parameter configuration 1' and parameter configuration 2', will be used. In this case, for QoS flow 1, the candidate configuration set includes multiple sets of parameter configurations, namely parameter configuration 1 and parameter configuration 1'; for QoS flow 2, the candidate configuration set includes multiple sets of parameter configurations, namely parameter configuration 2 and parameter configuration 2'.

[0177] In some embodiments, the method further comprises:

[0178] In response to a change in the situation of the separate scheduling, the parameter configuration used for the separate scheduling of the QoS flow is adjusted according to the non-cooperative parameter configuration.

[0179] For example, when at least one of the network conditions, UE conditions and / or service contract changes, it can be considered that the separate scheduling situation has changed. In the embodiment of the present disclosure, the parameter configuration used for separate scheduling of QoS flows will be adaptively adjusted.

[0180] Exemplarily, the method further includes:

[0181] In response to receiving notification of the triggering event, it is determined that circumstances of the individual schedule have changed.

[0182] The changes in the aforementioned separate scheduling situation can be configured as trigger conditions corresponding to the trigger event. The first network device, the second network device and / or the UE can detect whether a trigger event occurs. If the first network device itself detects the occurrence of a trigger event, it can switch the parameter configuration of the separate scheduling by itself. If the second network device or the UE detects the occurrence of a trigger event, the first network device will receive a notification, so that the first network device can configure the parameters used for separate scheduling of the QoS flow according to the notification.

[0183] In one embodiment, the change in the situation of the separate scheduling may include at least one of the following:

[0184] In response to a QoS value at the QoS flow falling below a QoS threshold, determining that an individual scheduling condition of the QoS flow has changed;

[0185] In response to reaching a QoS threshold after a change in the QoS value of the QoS flow, determining that an individual scheduling condition with the QoS flow has changed;

[0186] In response to a failure in resource allocation for the QoS flow, determining that a separate scheduling situation for the QoS flow has changed;

[0187] In response to a resource allocation failure at the QoS flow, individual scheduling situations with the QoS flow are changed.

[0188] In some embodiments, if the notification comes from the second network device, the notification is carried in a service request message.

[0189] Exemplarily, the service request message includes at least one of the following:

[0190] Service establishment request message;

[0191] Service modification request message.

[0192] In some embodiments, the notification further indicates the QoS flows whose conditions have changed and need to be separately scheduled.

[0193] In some embodiments, the method further comprises:

[0194] In response to receiving the notification that the individual scheduling situation is restored, the original parameter configuration of the individual scheduling of the QoS flow is restored.

[0195] The individual scheduling situation is restored, so the parameter configuration of the QoS flow can be adaptively restored to the original parameter configuration before the cut.

[0196] In some embodiments, if the candidate configuration set contains multiple sets of non-cooperative parameter configurations, a set of default parameter configurations or a specified set of parameter configurations can be the initial parameter configuration, that is, the parameter configuration used when the QoS flow is initially established is the initial parameter configuration. Subsequently, multiple sets of parameter configurations will be switched and used in the candidate configuration set depending on whether the trigger event is met.

[0197] As shown in FIG4 , an embodiment of the present disclosure provides a QoS flow scheduling method, which may be performed by a first network device. The method may include:

[0198] S210: In response to receiving the coordinated control information, determine a coordinated scheduling requirement for a flow with QoS.

[0199] The coordinated control information may come from the second network device that sends the QoS request message but is not limited to the second network device.

[0200] When the first network device schedules resources for multiple QoS flows with collaborative scheduling requirements, it performs collaborative scheduling according to the collaborative parameter configuration of the QoS flows.

[0201] The specific collaborative scheduling method can refer to the above embodiment, and can also be other collaborative scheduling methods other than the method provided in the above embodiment.

[0202] In short, this embodiment can be executed alone or in combination with the aforementioned S110 and the like.

[0203] After receiving the collaborative control information, it is determined that there is a collaborative scheduling requirement for QoS flow, and then after the corresponding QoSL flow is started, the collaborative scheduling of multiple QoS flows is performed; or the collaborative scheduling parameters of the already started multi-QoS flow collaborative scheduling are switched.

[0204] For example, the core network device indicates through collaborative control information that there is a collaborative scheduling requirement between multiple QoS flows.

[0205] In one embodiment, the collaborative control information may indicate the initiation of collaborative scheduling, so that upon receipt by the first network device, the collaborative scheduling of multiple QoS flows is initiated. In another embodiment, the collaborative control information may further include event information of a triggering event that triggers the transmission of the collaborative control information, or may further indicate determination information for determining the collaborative parameter configuration used in the collaborative scheduling. This determination information includes, but is not limited to, the aforementioned event information of the triggering event corresponding to different collaborative parameter configurations, and may also include a configuration identifier of the collaborative parameter configuration.

[0206] In some embodiments, the receiving collaborative control information includes:

[0207] A service request message including the collaborative control information is received.

[0208] The collaborative control information mentioned in the aforementioned embodiment can be carried in any message and transmitted between the first network device and other network devices (such as the second network device), and in the embodiment of the present disclosure, it can be carried in a service request message.

[0209] By carrying the coordinated control information in the service request message, the first network device can be informed of whether the QoS flow of the corresponding service has a coordinated scheduling requirement while making a service request and / or modifying the service.

[0210] Exemplarily, the service request message includes at least one of the following:

[0211] Service establishment request message;

[0212] Service modification request message.

[0213] In some embodiments, the collaborative control information further indicates QoS flows that require collaborative scheduling.

[0214] In one embodiment, the QoS flow requiring coordinated scheduling and the requirement for coordinated scheduling may be indicated by the same field. For example, the first field may include a service identifier, a flow identifier of the QoS flow, and / or a group identifier of the UE group. Different QoS flows corresponding to multiple UEs in the same UE group have a great function of requiring coordinated scheduling. If the field indicates a group identifier, it can be considered that the QoS flows of the multiple UEs in the UE group corresponding to the group identifier are QoS flows that require coordinated scheduling.

[0215] For example, if a collaborative control information contains the flow identifiers or service identifiers of multiple QoS flows, then based on the flow identifiers, service identifiers or group identifiers, on the one hand, it can be known which QoS flows need to be collaboratively scheduled, and it is equivalent to indicating the collaborative scheduling requirements of multiple QoS flows at the same time.

[0216] For another example, the service establishment request message of service A carries the service identifier, flow identifier, or group identifier of service B. At this time, the service identifier, flow identifier, or group identifier, on the one hand, is equivalent to indicating that the QoS flow of service A is a QoS flow for collaborative scheduling, and on the other hand, is equivalent to indicating that there is a collaborative scheduling requirement between the QoS flow of service A and the QoS flow of service B.

[0217] In another embodiment, the co-scheduling requirements of multiple QoS flows and the QoS flows that require co-scheduling may be indicated by different fields. For example, field A may include one or more bits to indicate whether there is a co-scheduling requirement, and field B indicates the flow identifier, service identifier and / or group identifier of the UE group of the QoS flows that require co-scheduling.

[0218] In some embodiments, the first network device does not receive explicitly indicated cooperative control information, but the cooperative control information is implicitly indicated.

[0219] For example, the second network device may group multiple QoS flows that require coordinated scheduling into the same OoS flow group. The grouping information of the QoS flow group may be considered as information implicitly indicating the coordinated scheduling requirement of the multiple QoS flows.

[0220] Therefore, in some embodiments, the coordinated control information is determined based on the grouping information of multiple QoS flows.

[0221] For example, when the second network device determines that there is a need for coordinated scheduling of multiple QoS flows, the first network device will receive grouping information of the multiple QoS flows sent by the second network device. The grouping information can be a group identifier or service identifier of the multiple grouped QoS flows. This grouping information not only indicates the multiple QoS flows that need to be coordinated, but also indicates the need for coordinated scheduling of the multiple QoS flows.

[0222] In one embodiment, the method further comprises: in response to receiving the non-coordinated control information, resuming the individual scheduling of the at least two co-scheduled QoS flows.

[0223] The non-cooperative control information here can be called independent control information.

[0224] In a scenario where multiple QoS flows are currently in coordinated scheduling, the non-coordinated control information is equivalent to instructing the corresponding QoS flow to exit the coordinated scheduling of multiple QoS flows and return to independent scheduling.

[0225] When multiple QoS flows are currently in a non-coordinated scheduling scenario, the non-coordinated control information is equivalent to instructing the corresponding QoS flows to maintain independent scheduling.

[0226] As shown in FIG5 , an embodiment of the present disclosure provides a method for scheduling a QoS flow, wherein the method is performed by a second network device and includes:

[0227] S310: Send a QoS request message, where the QoS request message indicates a candidate configuration set for a QoS flow; the candidate configuration set includes: multiple sets of parameter configurations for the QoS flow.

[0228] Exemplarily, the candidate configuration set includes at least one of the following:

[0229] Collaborative parameter configuration, wherein the collaborative parameter configuration is: parameter configuration for collaborative scheduling of multiple QoS flows;

[0230] Non-cooperative parameter configuration, wherein the non-cooperative parameter configuration is: parameter configuration for separate scheduling of QoS flows.

[0231] Here, the candidate parameter configuration set may include one or more sets of non-cooperative parameter configurations; similarly, the candidate configuration set may include one or more sets of cooperative parameter configurations.

[0232] Exemplarily, the non-coordinated parameter configuration includes: multiple sets of parameter configurations for separately scheduling QoS flows in different situations.

[0233] In some embodiments, the second network device may be a network device of a core network, and the network device of a core network is referred to as a core network device for short.

[0234] The second network device includes but is not limited to: AMF, SMF or UPF and other network devices.

[0235] The QoS request message indicates that the candidate configuration set for the QoS flow includes but is not limited to:

[0236] The QoS request message includes configuration information that explicitly indicates the candidate configuration set;

[0237] and / or,

[0238] The QoS request message includes information corresponding to the candidate configuration set and also indicates other contents. This indication method is equivalent to implicit indication.

[0239] The candidate configuration set includes: multiple sets of parameter configurations; the candidate configuration set includes: a reference parameter configuration and a difference configuration; the difference configuration indicates the difference between the non-reference parameter configuration in the multiple sets of parameter configurations and the reference parameter configuration;

[0240] or,

[0241] The candidate configuration set includes: multiple sets of parameter configurations; the candidate configuration set includes: a set of reference parameter configurations and a conversion relationship configuration, wherein the conversion relationship configuration indicates the conversion relationship between the non-reference parameter configurations in the multiple sets of parameter configurations and the reference parameter configuration.

[0242] In one embodiment, the conversion relationship between the same parameter of the reference parameter configuration and the non-reference parameter configuration indicates at least one of the following:

[0243] a ratio between the reference parameter configuration and the same parameter of the non-reference parameter configuration;

[0244] a difference between the reference parameter configuration and the same parameter of the non-reference parameter configuration;

[0245] A conversion function between the same parameters of the reference parameter configuration and the non-reference parameter configuration.

[0246] For example, the candidate configuration set indicates the collaborative parameter configuration and the non-collaborative parameter configuration, and the candidate configuration set includes a non-collaborative parameter configuration and a first difference configuration, wherein the first difference configuration indicates: a difference configuration of the collaborative parameter configuration relative to the non-collaborative parameter configuration;

[0247] or,

[0248] The candidate configuration set indicates the coordinated parameter configuration and the non-coordinated parameter configuration, and the candidate configuration set includes a system parameter configuration and a second difference parameter configuration, wherein the second difference configuration includes: a difference configuration of the non-coordinated parameter configuration relative to the coordinated parameter configuration.

[0249] The description of the first difference configuration and the second difference configuration here can be found in the aforementioned embodiment and will not be repeated here. If the candidate configuration set that includes both the collaborative parameter configuration and the non-collaborative parameter configuration is indicated by the second network device, the use of this first difference configuration and the second difference configuration to implement the indication of the two parameter configurations can reduce bit overhead and reduce the length of the signaling interaction between the first network device and the second network device.

[0250] For another example, the candidate configuration set indicates the coordinated parameter configuration and the non-coordinated parameter configuration, and the candidate configuration set includes the non-coordinated parameter configuration and a first conversion identifier, wherein the first conversion identifier indicates a conversion relationship between the non-coordinated parameter configuration and the coordinated parameter configuration;

[0251] or,

[0252] The candidate configuration set indicates the collaborative parameter configuration and the non-collaborative parameter configuration, and the candidate configuration set includes the collaborative parameter configuration and a second conversion identifier, wherein the second conversion identifier indicates a conversion relationship between the non-collaborative parameter configuration and the collaborative parameter configuration.

[0253] The first conversion identifier and / or the second conversion identifier both indicate the conversion relationship between the collaborative parameter configuration and the non-collaborative parameter configuration. For example, in the embodiment of the present disclosure, the first conversion identifier and the second conversion identifier can both be indexes or numbers of the corresponding conversion relationships. After the first network device receives the configuration information of the candidate configuration set, it first determines a set of configurations in the collaborative parameter configuration and the non-collaborative parameter configuration from the candidate configuration set, and then finds the conversion relationship based on the first conversion identifier or the second conversion identifier, and inputs the determined parameter configuration as a known quantity into the conversion relationship to obtain another set of parameter configurations. The configuration information only contains one conversion identifier, which has the characteristic of low bit overhead compared to the parameter value carrying the overall parameter configuration.

[0254] Exemplarily, the conversion relationship between the non-cooperative parameter configuration and the cooperative parameter configuration indicates at least one of the following:

[0255] a ratio between the non-cooperative parameter configuration and the same parameter of the cooperative parameter configuration;

[0256] a difference between the same parameter of the non-coordinated parameter configuration and the coordinated parameter configuration;

[0257] A conversion function between the same parameters of the non-cooperative parameter configuration and the cooperative parameter configuration.

[0258] In some embodiments, the QoS request message includes at least one of the following:

[0259] QoS establishment request message;

[0260] QoS modification request message.

[0261] Exemplarily, the QoS establishment request message includes but is not limited to: a Protocol Data Unit (PDU) session resource establishment request (PDU Session Resource Setup Request) and / or an Initial Context Setup Request (Initial Context Setup Request).

[0262] The QoS modification request message includes but is not limited to: a PDU session resource modification request (PDU Session Resource Modify Request).

[0263] As shown in FIG6 , an embodiment of the present disclosure provides a method for scheduling a QoS flow, which is performed by a second network device. The method for scheduling a QoS flow may include:

[0264] S410: In response to a coordinated scheduling requirement of a QoS flow, send coordinated control information, wherein the coordinated control information indicates the coordinated scheduling requirement.

[0265] In the embodiment of the present disclosure, the second network device will send down collaborative control information, which can trigger the first network device to perform collaborative scheduling of multiple QoS flows.

[0266] After the first network device receives the collaborative scheduling request, it can perform collaborative scheduling of multiple QoS flows according to the collaborative parameter configuration sent by the second network device, or it can perform collaborative scheduling of multiple QoS flows according to the collaborative parameter configuration determined by the first network device through other means (for example, based on a protocol).

[0267] In summary, the QoS flow scheduling method provided in the embodiment of the present disclosure can be executed independently or in combination with the aforementioned scheduling method for other QoS flows applied to the second network device.

[0268] In one embodiment, the sending of the coordinated control information includes:

[0269] Send a service request message containing the collaborative control information.

[0270] In the embodiment of the present disclosure, the collaborative control information is included in the service request message, so there is no need to involve dedicated signaling to transmit the collaborative control information, and the collaborative control information is sent when there is a service request or service modification. It has the characteristic of realizing multiple functions with one message, reducing the amount of information interaction between the first network device and the second network device.

[0271] In some embodiments, the method further includes: monitoring QoS values ​​of a plurality of QoS flows having an associated relationship.

[0272] Monitoring the QoS values ​​of multiple QoS flows herein may include: monitoring the QoS values ​​of QoS parameters such as actual delay, allocated bandwidth, packet loss rate, and / or the like of the QoS flows. Exemplarily, monitoring the QoS values ​​of multiple QoS flows herein may include: the first network device itself monitoring the QoS values ​​of the multiple QoS flows, or receiving, from the UE, the QoS values ​​of the QoS flows monitored by the UE.

[0273] In some embodiments, the method may include:

[0274] It is determined whether there is a need for coordinated scheduling of multiple QoS flows according to the monitored QoS values.

[0275] Of course, whether there is a demand for coordinated scheduling of multiple QoS flows may also be determined based on resource allocation results at the beginning of establishing the multiple QoS flows.

[0276] Illustratively, the method may include:

[0277] In response to a QoS value of at least one QoS flow among the plurality of QoS flows being lower than a QoS threshold, determining a collaborative scheduling requirement for the QoS flows;

[0278] In response to the QoS value of any one of the multiple QoS flows reaching a QoS threshold after the QoS value of at least one QoS flow of the multiple QoS flows changes, determining a collaborative scheduling requirement for the QoS flows;

[0279] In response to a resource allocation failure for at least one QoS flow among the plurality of QoS flows, determining a co-scheduling requirement for the QoS flows;

[0280] In response to a resource allocation failure for each of the plurality of QoS flows, a co-scheduling requirement for the QoS flows is determined.

[0281] It is worth noting that: in response to the QoS value of at least one QoS flow among the multiple QoS flows being lower than the QoS threshold, in response to the QoS value of any QoS flow among the multiple QoS flows reaching the QoS threshold after the QoS value of at least one QoS flow among the multiple QoS flows changes, in response to the failure of resource allocation of at least one QoS flow among the multiple QoS flows, in response to the failure of resource allocation of each QoS flow among the multiple QoS flows, it can be considered that it corresponds to a trigger event. Once the trigger event occurs, it is determined that there is a need for collaborative scheduling, and collaborative control information is sent to the first network device.

[0282] Monitor the QoS values ​​of one or more QoS parameters, such as actual bandwidth, bit error rate, and packet loss rate, for multiple associated QoS flows. If the QoS value of at least one QoS flow is detected to be lower than the QoS threshold, the QoS value of that QoS flow will cause the overall quality of the associated multiple QoS flows to decline. If other QoS flows continue to maintain large resource allocations, it will lead to resource waste and poor communication quality.

[0283] If the QoS value of each of the multiple associated QoS flows reaches the QoS threshold, it indicates that the multiple QoS flows can be combined to provide users with better communication quality, and it can be considered that coordinated scheduling is required. For example, if the actual delay of each of the multiple QoS flows is less than the packet data delay budget for coordinated scheduling, this indicates that the network environment has a high transmission rate. If each QoS flow is scheduled independently according to the larger packet data delay budget, it will not be able to effectively use communication resources and cannot provide the high QoS allowed by the current network environment.

[0284] Similarly, during the QoS flow creation phase, it can be determined whether the scheduling of the remaining QoS flows needs to be maintained based on the resource allocation results of multiple QoS flows, or whether the resources of multiple QoS flows need to be collaboratively scheduled after the resource allocation of each QoS flow is completed.

[0285] Exemplarily, if the resource allocation of at least one QoS flow among multiple QoS flows with an associated relationship fails, and the resource allocation failure of the QoS flow will make the communication service provided by the combination of multiple QoS flows impossible to implement or of extremely poor quality, then it can be considered that there is a collaborative scheduling requirement, and the first network device can be triggered to temporarily release the resources that have been allocated to other QoS flows among the multiple QoS flows, or delay the resource allocation of other associated QoS flows, for example, after successfully allocating resources for the QoS flow, allocate resources for other QoS flows associated with the QoS flow.

[0286] In some embodiments, the collaborative control information is also used for QoS flows that require collaborative scheduling.

[0287] How the coordinated control information indicates the QoS flow that needs to be coordinated and scheduled can be found in the above-mentioned corresponding embodiments, which will not be repeated here.

[0288] In some embodiments, the method further comprises:

[0289] In response to the disappearance of the demand for coordinated scheduling of the multiple QoS flows, non-coordinated control information is sent, wherein the non-coordinated control information indicates to resume the individual scheduling of the multiple QoS flows.

[0290] In an embodiment of the present disclosure, if the demand for collaborative scheduling of multiple QoS flows disappears, the disappearance of the collaborative scheduling demand is indicated by non-cooperative control information. If the multiple QoS flows are currently still in a collaborative scheduling scenario, the first network device will restore the separate scheduling of each QoS flow after receiving the non-cooperative control information. If any one of the multiple QoS flows has entered an independently scheduled non-cooperative scheduling scenario due to other reasons, the first network device will continue to maintain the separate scheduling of the corresponding QoS flow.

[0291] The present disclosure provides a QoS flow scheduling method, which may be performed by a second device. The method further includes:

[0292] In response to a change in the situation of the individual schedule, a notification indicating the change in the situation of the individual schedule is sent.

[0293] If it is determined that the situation of separate scheduling has changed, a notification indicating that the situation of separate scheduling has changed will be sent to the first network device, so that the first network device can adjust the parameter configuration used for scheduling of the single QoS flow in time according to the situation change.

[0294] In some embodiments, the notification includes notification of the occurrence of a triggering event.

[0295] In some embodiments, the notification is carried in a service request message.

[0296] In some embodiments, the service request message includes at least one of the following:

[0297] Service establishment request message;

[0298] Service modification request message.

[0299] Exemplarily, the QoS establishment request message includes but is not limited to: a Protocol Data Unit (PDU) session resource establishment request (PDU Session Resource Setup Request) and / or an Initial Context Setup Request (Initial Context Setup Request).

[0300] The QoS modification request message includes but is not limited to: a PDU session resource modification request (PDU Session Resource Modify Request).

[0301] In some embodiments, the notification further indicates the QoS flows whose conditions have changed and need to be separately scheduled.

[0302] In some embodiments, the method further comprises:

[0303] Sends a notification indicating that the individually scheduled situation has been restored.

[0304] The notification indicating restoration of the separate scheduling situation enables the first network device to restore the original parameter configuration or default parameter configuration of the separate scheduling of the QoS flow.

[0305] For newly added multi-UE application scenarios such as multimodal services and federated learning services, we have added coordinated scheduling of QoS flows. For example, we have added candidate configuration sets for QoS flows and increased base station coordinated scheduling processing. For example, the base station can perform resource allocation and scheduling for multiple QoS flows based on the coordinated parameter configurations in the candidate configuration sets.

[0306] When a QoS establishment / modification request is sent from the core network to the base station, it may carry a candidate configuration set of a QoS flow; the candidate configuration set of the QoS flow may be used by the base station, i.e., the QoS flow, for configuration in a coordinated scheduling scenario;

[0307] As an embodiment, the core network may carry a candidate configuration set for a cooperative scheduling scenario when notifying the parameter configuration for a non-cooperative scheduling scenario;

[0308] For example, one or more candidate coordination parameter configurations may be provided to a certain QoS flow for use in a coordinated scheduling scenario; the coordinated scheduling scenario herein is a scenario in which multiple QoS flows are coordinatedly scheduled.

[0309] In some cases, some parameters of the coordinated parameter configuration may be the same as or different from the non-coordinated parameter configuration in the non-coordinated scheduling scenario.

[0310] For example, the parameter configuration of the packet delay budget (Packet Delay Budget) in the QoS flow 1 in the non-cooperative scheduling scenario is 100ms;

[0311] At the same time, in the collaborative scheduling scenario, the parameter value of the packet data delay budget in QoS flow 1 is also given as 50ms;

[0312] At the same time, in the collaborative scheduling scenario, the parameter value of the packet data delay budget in QoS flow 1 is also given as 20ms;

[0313] The coordinated control parameters of the QoS flow can be configured from the core network to the base station through explicit signaling, or can be agreed upon by protocol.

[0314] As an embodiment, the core network can carry the parameter configuration in the cooperative scheduling scenario when notifying the parameter configuration in the non-cooperative scheduling scenario; the non-cooperative scheduling scenario is: multiple QoS flows are not coordinated and scheduled, but each flow is independently scheduled and has no connection with each other.

[0315] In one embodiment, the parameter configuration of the coordinated scheduling scenario carries only an incremental part (or a difference part) relative to the non-coordinated parameter configuration in the candidate parameter configuration sent by the core network, thereby reducing signaling overhead.

[0316] As an embodiment, a protocol may be established to determine how a QoS flow is changed from a parameter configuration in a cooperative scheduling scenario to a parameter configuration in a non-cooperative scheduling scenario; for example, the parameter Packet Delay Budget is reduced to half of the original value.

[0317] At this time, the core network can only carry a valid flag when notifying the parameter configuration in the coordinated scheduling scenario, that is, the parameter configuration in the coordinated scheduling scenario is valid;

[0318] It is worth noting that:

[0319] The QoS establishment / modification request message initiated by the core network can be one or more of the following messages:

[0320] Packet data session resource setup request (PDU SESSION RESOURCE SETUP REQUEST);

[0321] Packet data session resource modification request (PDU SESSION RESOURCE MODIFY REQUEST);

[0322] Initial context setup request (INITIAL CONTEXT SETUP REQUEST).

[0323] After receiving the requirement for QoS coordination from the core network, the base station uses the coordination parameter configuration of the QoS flow.

[0324] As an embodiment: the service establishment / modification request initiated by the core network will carry collaborative control information.

[0325] As an embodiment, the collaborative control information indicates whether the core network expects the access network to perform collaborative scheduling on the data flow, etc. The collaborative control information indicates what kind of collaborative processing the core network expects to perform on the data flow.

[0326] In some embodiments, coordination control information can be implicitly carried in packet information. For example, if the core network notifies the base station that QoS Flow 1 and QoS Flow 2 of a PDN session both belong to a group requiring coordination, this implicitly indicates the core network's desire for QoS coordination for these two data flows, i.e., which candidate configuration set to use. In one embodiment, QoS Flow 1 and QoS Flow 2 both belong to a group requiring coordination, which can span multiple terminal devices.

[0327] As an embodiment: the candidate configuration set may be agreed upon in advance, or the core network may display a notification.

[0328] For example, the parameter configuration of the packet delay budget in Qos flow 1 in the non-cooperative scheduling scenario is: 100ms; and

[0329] The parameter configuration of the packet data delay budget (Packet Delay Budget) in QoS flow 2 in the non-cooperative scheduling scenario is: 100ms.

[0330] When co-scheduling QoS flow 1 and QoS flow 2:

[0331] The packet data delay budget parameter in QoS flow 1 and QoS flow 2 is 50ms in parameter configuration 1 in the cooperative scheduling scenario.

[0332] The coordinated control information can be the core network's expectation of how to process other data flows in the same coordinated group when the base station detects a specific trigger event. That is, changes in one QoS flow will affect parameter changes in other QoS flows;

[0333] For example, when using collaborative parameter configuration, if a flow fails to meet QoS requirements, it is likely that the QoS parameters of other QoS flows will also be adjusted down or up. For example, if the rate of camera 1 decreases, the cameras that collaborate with it may also reduce or increase the collection accuracy to compensate.

[0334] As an embodiment: if the core network notifies the base station that QOs flow 1 of a certain PDN session and QOs flow 2 both belong to a group that needs to be coordinated, and the rate of QOs flow 1 of the PDN session is lower than a certain threshold; that is, the base station detects that event A occurs.

[0335] At this time, the base station detects that A occurs, and will use Qos flow 2 to adopt the candidate control parameter set (downgrade / or increase);

[0336] The notification indicating a change in the situation of individual scheduling can also be the core network's expectation of processing a data flow when the base station detects a specific triggering event. For example, if the rate of QoS flow 1 is detected to be lower than a certain threshold, the base station detects the occurrence of event B. At this time, when the base station detects the occurrence of B, it will use QoS flow 1 to adopt other parameter configurations in the candidate non-cooperative parameter configuration, thereby causing the parameter configuration currently used by the QoS flow to be lowered or increased.

[0337] Exemplarily, the specific triggering event may also be a change in wireless signal quality or base station load detected by the base station, which are all situations where the aforementioned individual scheduling situation changes, and of course, may also be a triggering event for the aforementioned coordinated control information transmission;

[0338] Exemplarily, the specific triggering event may be that the core network notifies the base station through an initiated QoS establishment / modification request message.

[0339] After receiving the request from the core network to stop QoS coordinated scheduling, the base station can also fall back to the non-coordinated scenario and perform non-coordinated scheduling of the corresponding QoS flow according to the non-coordinated parameter configuration.

[0340] As shown in FIG7 , an embodiment of the present disclosure provides a QoS flow scheduling device, wherein the device includes:

[0341] The determination module 610 is configured to determine a candidate configuration set for a QoS flow, wherein the candidate configuration set includes: multiple sets of parameter configurations for the QoS flow.

[0342] The QoS flow scheduling device can be applied to a first network device including an access network, such as a base station.

[0343] In some embodiments, the determination module 610 may be a program module; after being executed by a processor, the program module can implement determination of candidate parameter sets for collaborative scheduling of multiple QoS flows.

[0344] In another embodiment, the determination module 610 may be a soft-hard combination module; the soft-hard combination module includes but is not limited to: a programmable array; the programmable array includes but is not limited to: a field programmable array and / or a complex programmable array.

[0345] In some other embodiments, the determination module 610 may be a pure hardware module; the pure hardware module includes but is not limited to a dedicated integrated circuit.

[0346] In some embodiments, the candidate configuration set includes at least one of the following:

[0347] Collaborative parameter configuration, wherein the collaborative parameter configuration is: parameter configuration for collaborative scheduling of multiple QoS flows;

[0348] Non-cooperative parameter configuration, wherein the non-cooperative parameter configuration is: parameter configuration for separate scheduling of QoS flows.

[0349] In some other embodiments, the non-cooperative parameter configuration includes:

[0350] Multiple sets of parameter configurations for scheduling QoS flows independently in different situations.

[0351] In some embodiments, the determining module 610 is configured to receive a QoS request message, wherein the QoS request message includes configuration information of a candidate configuration set of a QoS flow; or determine the candidate configuration set according to a protocol.

[0352] In some embodiments, the candidate configuration set includes: multiple sets of parameter configurations; the candidate configuration set includes: a reference parameter configuration and a difference configuration; the difference configuration indicates the difference between a non-reference parameter configuration in the multiple sets of parameter configurations and the reference parameter configuration;

[0353] or,

[0354] The candidate configuration set includes: multiple sets of parameter configurations; the candidate configuration set includes: a set of reference parameter configurations and a conversion relationship configuration, wherein the conversion relationship configuration indicates the conversion relationship between the non-reference parameter configurations in the multiple sets of parameter configurations and the reference parameter configuration.

[0355] In some embodiments, the conversion relationship between the same parameter of the reference parameter configuration and the non-reference parameter configuration indicates at least one of the following:

[0356] a ratio between the reference parameter configuration and the same parameter of the non-reference parameter configuration;

[0357] a difference between the reference parameter configuration and the same parameter of the non-reference parameter configuration;

[0358] A conversion function between the same parameters of the reference parameter configuration and the non-reference parameter configuration.

[0359] Exemplarily, the candidate configuration set indicates the coordinated parameter configuration and the non-coordinated parameter configuration, and the candidate configuration set includes a non-coordinated parameter configuration and a first difference configuration, wherein the first difference configuration indicates: a difference configuration of the coordinated parameter configuration relative to the non-coordinated parameter configuration;

[0360] or,

[0361] The candidate configuration set indicates the coordinated parameter configuration and the non-coordinated parameter configuration, and the candidate configuration set includes a system parameter configuration and a second difference parameter configuration, wherein the second difference configuration includes: a difference configuration of the non-coordinated parameter configuration relative to the coordinated parameter configuration.

[0362] In another exemplary embodiment, the candidate configuration set indicates the coordinated parameter configuration and the non-coordinated parameter configuration, and the candidate configuration set includes the non-coordinated parameter configuration and a first conversion identifier, wherein the first conversion identifier indicates a conversion relationship between the non-coordinated parameter configuration and the coordinated parameter configuration;

[0363] or,

[0364] The candidate configuration set indicates the collaborative parameter configuration and the non-collaborative parameter configuration, and the candidate configuration set includes the collaborative parameter configuration and a second conversion identifier, wherein the second conversion identifier indicates a conversion relationship between the non-collaborative parameter configuration and the collaborative parameter configuration.

[0365] In some embodiments, the QoS request message includes at least one of the following:

[0366] QoS establishment request message;

[0367] QoS modification request message.

[0368] In some embodiments, the apparatus further comprises:

[0369] The co-scheduling module is configured to, in response to determining a co-scheduling requirement of a QoS flow, co-schedule at least two of the QoS flows according to a coordination parameter configuration.

[0370] In some embodiments, the apparatus further comprises:

[0371] The co-scheduling requirement module is configured to determine the co-scheduling requirement of the QoS flow in response to receiving the co-control information.

[0372] In some embodiments, the receiving module is configured to receive a service request message containing the collaborative control information.

[0373] In some embodiments, the service request message includes at least one of the following:

[0374] Service establishment request message;

[0375] Service modification request message.

[0376] In some embodiments, the collaborative control information further indicates QoS flows that require collaborative scheduling.

[0377] In some embodiments, the coordinated control information is determined based on grouping information of multiple QoS flows.

[0378] In some embodiments, the apparatus further comprises:

[0379] The resuming module is configured to resume the individual scheduling of the at least two QoS flows that are co-scheduled in response to receiving the non-coordinated control information.

[0380] In some embodiments, the apparatus further comprises:

[0381] The separate scheduling module is configured to adjust the parameter configuration used for separate scheduling of the QoS flow according to the non-cooperative parameter configuration in response to changes in the separate scheduling situation.

[0382] In some embodiments, the apparatus further comprises:

[0383] The situation change module is configured to determine that a situation of the individual schedule has changed in response to receiving a notification of a triggering event.

[0384] In some embodiments, the notification is carried in a service request message.

[0385] In some embodiments, the service request message includes at least one of the following:

[0386] Service establishment request message;

[0387] Service modification request message.

[0388] In some embodiments, the notification further indicates the QoS flows whose conditions have changed and need to be separately scheduled.

[0389] In some embodiments, the apparatus further comprises:

[0390] The original parameter configuration restoring module is configured to restore the original parameter configuration of the QoS flow independent scheduling in response to receiving the notification of the independent scheduling situation being restored.

[0391] As shown in FIG8 , an embodiment of the present disclosure provides a QoS flow scheduling device, wherein the device includes:

[0392] The sending module 710 is configured to send a QoS request message, where the QoS request message indicates a candidate configuration set for a QoS flow;

[0393] The candidate configuration set includes: multiple sets of parameter configurations for the QoS flow.

[0394] In some embodiments, the sending module 710 may be a program module; after the program module is executed by a processor, the sending of the QoS request message can be achieved.

[0395] In some embodiments, the sending module 710 may be a soft-hard combination module; the soft-hard combination module includes but is not limited to: various programmable arrays; the programmable arrays include but are not limited to: field programmable arrays and / or complex programmable arrays.

[0396] In some other embodiments, the sending module 710 may be a pure hardware module; the pure hardware module includes but is not limited to: a dedicated integrated circuit.

[0397] In some embodiments, the candidate configuration set includes at least one of the following:

[0398] Collaborative parameter configuration, wherein the collaborative parameter configuration is: parameter configuration for collaborative scheduling of multiple QoS flows;

[0399] Non-cooperative parameter configuration, wherein the non-cooperative parameter configuration is: parameter configuration for separate scheduling of QoS flows.

[0400] In some embodiments, the non-coordinated parameter configuration includes: multiple sets of parameter configurations for independently scheduling QoS flows in different situations.

[0401] In some embodiments, the candidate configuration set includes: multiple sets of parameter configurations; the candidate configuration set includes: a reference parameter configuration and a difference configuration; the difference configuration indicates the difference between a non-reference parameter configuration in the multiple sets of parameter configurations and the reference parameter configuration;

[0402] or,

[0403] The candidate configuration set includes: multiple sets of parameter configurations; the candidate configuration set includes: a set of reference parameter configurations and a conversion relationship configuration, wherein the conversion relationship configuration indicates the conversion relationship between the non-reference parameter configurations in the multiple sets of parameter configurations and the reference parameter configuration.

[0404] In some embodiments, the conversion relationship between the non-cooperative parameter configuration and the cooperative parameter configuration indicates at least one of the following:

[0405] a ratio between the reference parameter configuration and the same parameter of the non-reference parameter configuration;

[0406] a difference between the reference parameter configuration and the same parameter of the non-reference parameter configuration;

[0407] A conversion function between the same parameters of the reference parameter configuration and the non-reference parameter configuration.

[0408] Exemplarily, the candidate configuration set indicates the coordinated parameter configuration and the non-coordinated parameter configuration, and the candidate configuration set includes a non-coordinated parameter configuration and a first difference configuration, wherein the first difference configuration indicates: a difference configuration of the coordinated parameter configuration relative to the non-coordinated parameter configuration;

[0409] or,

[0410] The candidate configuration set indicates the coordinated parameter configuration and the non-coordinated parameter configuration, and the candidate configuration set includes a system parameter configuration and a second difference parameter configuration, wherein the second difference configuration includes: a difference configuration of the non-coordinated parameter configuration relative to the coordinated parameter configuration.

[0411] In another exemplary embodiment, the candidate configuration set indicates the coordinated parameter configuration and the non-coordinated parameter configuration, and the candidate configuration set includes the non-coordinated parameter configuration and a first conversion identifier, wherein the first conversion identifier indicates a conversion relationship between the non-coordinated parameter configuration and the coordinated parameter configuration;

[0412] or,

[0413] The candidate configuration set indicates the collaborative parameter configuration and the non-collaborative parameter configuration, and the candidate configuration set includes the collaborative parameter configuration and a second conversion identifier, wherein the second conversion identifier indicates a conversion relationship between the non-collaborative parameter configuration and the collaborative parameter configuration.

[0414] In some embodiments, the QoS request message includes at least one of the following:

[0415] QoS establishment request message;

[0416] QoS modification request message.

[0417] In some embodiments, the apparatus further comprises:

[0418] The coordinated control information module is configured to send coordinated control information in response to a coordinated scheduling requirement of a flow with QoS, wherein the coordinated control information indicates the coordinated scheduling requirement.

[0419] In some embodiments, the collaborative control information module is configured to send a service request message containing the collaborative control information.

[0420] In some embodiments, the apparatus further comprises:

[0421] The collaborative scheduling requirement module is configured to perform at least one of the following:

[0422] In response to a QoS value of at least one QoS flow among the plurality of QoS flows being lower than a QoS threshold, determining a collaborative scheduling requirement for the QoS flows;

[0423] In response to the QoS value of any one of the multiple QoS flows reaching a QoS threshold after the QoS value of at least one QoS flow of the multiple QoS flows changes, determining a collaborative scheduling requirement for the QoS flows;

[0424] In response to a resource allocation failure for at least one QoS flow among the plurality of QoS flows, determining a co-scheduling requirement for the QoS flows;

[0425] In response to a resource allocation failure for each of the plurality of QoS flows, a co-scheduling requirement for the QoS flows is determined.

[0426] In some embodiments, the collaborative control information is also used for QoS flows that require collaborative scheduling.

[0427] In some embodiments, the method further comprises:

[0428] The non-cooperative control information module is configured to send non-cooperative control information in response to the disappearance of the cooperative scheduling demand of multiple QoS flows, wherein the non-cooperative control information indicates the restoration of the individual scheduling of multiple QoS flows.

[0429] In some embodiments, the sending module is further configured to send non-cooperative control information in response to disappearance of the demand for coordinated scheduling of multiple QoS flows, wherein the non-cooperative control information indicates the resumption of individual scheduling of multiple QoS flows.

[0430] In some embodiments, the sending module is configured to send a notification indicating a change in the individual scheduling situation in response to a change in the individual scheduling situation.

[0431] In some embodiments, the notification includes notification of the occurrence of a triggering event.

[0432] In some embodiments, the notification is carried in a service request message.

[0433] In some embodiments, the service request message includes at least one of the following:

[0434] Service establishment request message;

[0435] Service modification request message.

[0436] In some embodiments, the notification further indicates the QoS flows whose conditions have changed and need to be separately scheduled.

[0437] In some embodiments, the sending module is further configured to send a notification indicating that the individual scheduling situation has been restored.

[0438] An embodiment of the present disclosure provides a network device, including:

[0439] a memory for storing processor-executable instructions;

[0440] Processor, respectively memory connected;

[0441] The processor is configured to execute the QoS flow scheduling method provided by any of the aforementioned technical solutions.

[0442] The processor may include various types of storage media, which are non-transitory computer storage media that can continue to store information after the network device loses power.

[0443] Here, the network equipment includes: access network equipment of the access network and / or core network equipment of the core network.

[0444] The processor may be connected to the memory via a bus or the like, and configured to read an executable program stored in the memory, for example, at least one of the methods shown in FIG. 2A , FIG. 2B , FIG. 3A , FIG. 3B and FIG. 4 to FIG. 6 .

[0445] As shown in Figure 9, an embodiment of the present disclosure shows the structure of a network device. For example, the network device 900 can be provided as a network-side device. The network device can be the aforementioned access device and / or core network device.

[0446] 9 , network device 900 includes a processing component 922, which further includes one or more processors, and memory resources represented by memory 932 for storing instructions executable by processing component 922, such as applications. The applications stored in memory 932 may include one or more modules, each corresponding to a set of instructions. Furthermore, processing component 922 is configured to execute instructions to perform any of the aforementioned methods applied to the access device, such as those described in FIG. 2 , FIG. 3A , FIG. 3B , and FIG. 4 through FIG. 6 .

[0447] The network device 900 may also include a power supply component 926 configured to perform power management for the network device 900, a wired or wireless network interface 950 configured to connect the network device 900 to a network, and an input / output (I / O) interface 958. The network device 900 may operate based on an operating system stored in the memory 932, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, or the like.

[0448] The present disclosure also provides a non-transitory computer-readable storage medium including instructions, such as a memory 932 including instructions, which can be executed by the processing component 920 of the network device to perform the above method. For example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0449] After the instruction is executed by the processor, it can implement the QoS flow scheduling method provided by any of the aforementioned technical solutions, for example, execute at least one of the methods shown in Figures 2A, 2B, 3A, 3B and 4 to 6.

[0450] Other embodiments of the present invention will readily occur to those skilled in the art after considering the specification and practicing the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the invention that follow from the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, with the true scope and spirit of the invention being indicated by the following claims.

[0451] It should be understood that the present invention is not limited to the exact construction described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. A scheduling method for Quality of Service (QoS) flows, wherein, executed by a first network device, the method includes: determining a candidate configuration set for the QoS flow, wherein the candidate configuration set includes: multiple sets of parameter configurations for the QoS flow.

2. The method according to claim 1, wherein, the candidate configuration set includes at least one of the following: coordination parameter configuration, wherein the coordination parameter configuration is: parameter configuration for coordinated scheduling of multiple QoS flows; non - coordination parameter configuration, wherein the non - coordination parameter configuration is: parameter configuration for individual scheduling of a QoS flow.

3. The method according to claim 2, wherein, the non - coordination parameter configuration includes: multiple sets of parameter configurations for individually scheduling the QoS flow under different circumstances.

4. The method according to any one of claims 1 to 3, wherein, the determining of the candidate configuration set for the QoS flow includes: receiving a QoS request message, wherein the QoS request message contains configuration information of the candidate configuration set for the QoS flow; or, determining the candidate configuration set according to a protocol.

5. The method according to any one of claims 1 to 4, wherein, the candidate configuration set includes: multiple sets of parameter configurations; the candidate configuration set includes: a set of reference parameter configurations and difference configurations; the difference configurations indicate the differences of non - reference parameter configurations in the multiple sets of parameter configurations relative to the reference parameter configuration; or, the candidate configuration set includes: multiple sets of parameter configurations; the candidate configuration set includes: a set of reference parameter configurations and conversion relation configurations, wherein the conversion relation configurations indicate the conversion relations between non - reference parameter configurations and the reference parameter configuration in the multiple sets of parameter configurations.

6. The method according to claim 5, wherein, the conversion relation indicates at least one of the following: the ratio between the same parameters of the reference parameter configuration and the non - reference parameter configuration; the difference between the same parameters of the reference parameter configuration and the non - reference parameter configuration; the conversion function between the same parameters of the reference parameter configuration and the non - reference parameter configuration.

7. The method according to any one of claims 1 to 6, wherein, the QoS request message includes at least one of the following: QoS establishment request message; QoS modification request message.

8. The method according to any one of claims 1 to 7, wherein, the method further includes: in response to determining a coordinated scheduling requirement for the QoS flow, coordinately scheduling at least two of the QoS flows according to the coordination parameter configuration.

9. The method according to claim 8, wherein, the method further includes: in response to receiving coordination control information, determining a coordinated scheduling requirement for the QoS flow.

10. The method according to claim 9, wherein, the method further includes: receiving a service request message containing the coordination control information.

11. The method according to claim 10, wherein, the service request message includes at least one of the following: service establishment request message; service modification request message.

12. The method according to any one of claims 8 to 11, wherein, the coordination control information further indicates the QoS flows that need to be coordinately scheduled.

13. The method according to claim 12, wherein, the cooperative control information is determined according to the packet information of multiple QoS flows.

14. The method according to any one of claims 1 to 13, wherein, the method further includes: responding to receiving non - cooperative control information, restoring the separate scheduling of at least two of the QoS flows under cooperative scheduling.

15. The method according to any one of claims 2 to 14, wherein, the method further includes: responding to a change in the situation of separate scheduling, adjusting the parameter configuration used for the separate scheduling of the QoS flow according to the non - cooperative parameter configuration.

16. The method according to claim 15, wherein, the method further includes: responding to receiving a notification of a trigger event, determining that a change has occurred in the situation of separate scheduling.

17. The method according to claim 16, wherein, the notification is carried in a service request message.

18. The method according to claim 17, wherein, the service request message includes at least one of the following: a service establishment request message; a service modification request message.

19. The method according to any one of claims 16 to 18, wherein, the notification further indicates the QoS flows for which a change in the situation of separate scheduling is required.

20. The method according to any one of claims 2 to 14, wherein, the method further includes: responding to receiving a notification of the restoration of the situation of separate scheduling, restoring the original parameter configuration for the separate scheduling of the QoS flow.

21. A scheduling method for QoS flows, wherein, executed by a second network device, the method includes: sending a QoS request message, the QoS request message indicating a candidate configuration set for the QoS flow; the candidate configuration set includes: multiple sets of parameter configurations for the QoS flow.

22. The method according to claim 21, wherein, the candidate configuration set includes at least one of the following: a cooperative parameter configuration, wherein the cooperative parameter configuration is: a parameter configuration for the cooperative scheduling of multiple QoS flows; a non - cooperative parameter configuration, wherein the non - cooperative parameter configuration is: a parameter configuration for the separate scheduling of the QoS flow.

23. The method according to claim 22, wherein, the non - cooperative parameter configuration includes: multiple sets of parameter configurations for separately scheduling the QoS flow under different circumstances.

24. The method according to claim 21, wherein, the candidate configuration set includes: multiple sets of parameter configurations; the candidate configuration set includes: a set of reference parameter configurations and a difference configuration; the difference configuration indicates the differences between the non - reference parameter configurations and the reference parameter configuration among the multiple sets of parameter configurations; or, the candidate configuration set includes: multiple sets of parameter configurations; the candidate configuration set includes: a set of reference parameter configurations and a conversion relationship configuration, wherein the conversion relationship configuration indicates the conversion relationship between the non - reference parameter configurations and the reference parameter configuration among the multiple sets of parameter configurations.

25. The method according to claim 24, wherein, the conversion relationship of the same parameters between the reference parameter configuration and the non - reference parameter configuration indicates at least one of the following: the ratio between the same parameters of the reference parameter configuration and the non - reference parameter configuration; The difference between the same parameters of the reference parameter configuration and the non-reference parameter configuration; The conversion function between the same parameters of the reference parameter configuration and the non-reference parameter configuration.

26. The method according to any one of claims 21 to 25, wherein, The QoS request message includes at least one of the following: QoS establishment request message; QoS modification request message.

27. The method according to any one of claims 21 to 26, wherein, The method further includes: In response to the co-scheduling requirement of the QoS flow, sending co-control information, wherein the co-control information indicates the co-scheduling requirement.

28. The method according to claim 27, wherein, The sending of the co-control information includes: Sending a service request message including the co-control information.

29. The method according to claim 27 or 28, wherein, The method further includes at least one of the following: In response to the QoS value of at least one QoS flow among the multiple QoS flows being lower than the QoS threshold, determining the co-scheduling requirement of the QoS flow; In response to the QoS value of any one of the multiple QoS flows reaching the QoS threshold after the QoS value of at least one QoS flow among the multiple QoS flows changes, determining the co-scheduling requirement of the QoS flow; In response to the resource allocation failure of at least one QoS flow among the multiple QoS flows, determining the co-scheduling requirement of the QoS flow; In response to the resource allocation failure of each QoS flow among the multiple QoS flows, determining the co-scheduling requirement of the QoS flow.

30. The method according to any one of claims 27 to 29, wherein, The co-control information is also used for the QoS flow that needs co-scheduling.

31. The method according to any one of claims 21 to 30, wherein, The method further includes: In response to the disappearance of the co-scheduling requirement of the multiple QoS flows, sending non-co-control information, wherein the non-co-control information indicates the restoration of the separate scheduling of the multiple QoS flows.

32. The method according to any one of claims 22 to 31, wherein, The method further includes: In response to the change in the situation of separate scheduling, sending a notice indicating the change in the situation of separate scheduling.

33. The method according to claim 32, wherein, The notice includes: a notice of the occurrence of a trigger event.

34. The method according to claim 32 or 33, wherein, The notice is carried in the service request message.

35. The method according to claim 34, wherein, The service request message includes at least one of the following: Service establishment request message; Service modification request message.

36. The method according to any one of claims 22 to 35, wherein, The notice also indicates the QoS flow for which the situation of separate scheduling has changed.

37. The method according to any one of claims 2 to 14, wherein, The method further includes: Sending a notice indicating the restoration of the situation of separate scheduling.

38. A scheduling device for QoS flow, wherein, The device includes: A determination module, configured to determine a candidate configuration set for a QoS flow, where the candidate configuration set includes: multiple sets of parameter configurations for the QoS flow.

39. The apparatus according to claim 38, wherein, the candidate configuration set includes at least one of the following: A collaborative parameter configuration, where the collaborative parameter configuration is: a parameter configuration for the collaborative scheduling of multiple QoS flows; A non-collaborative parameter configuration, where the non-collaborative parameter configuration is: a parameter configuration for the individual scheduling of a QoS flow.

40. The apparatus according to claim 39, wherein, the non-collaborative parameter configuration includes: Multiple sets of parameter configurations for individually scheduling QoS flows in different situations.

41. The apparatus according to any one of claims 38 to 40, wherein, the determination module is configured to receive a QoS request message, where the QoS request message contains configuration information of a candidate configuration set for a QoS flow; or determine the candidate configuration set according to a protocol.

42. The apparatus according to any one of claims 39 to 41, wherein, the candidate configuration set includes: multiple sets of parameter configurations; the candidate configuration set includes: a set of reference parameter configurations and a difference configuration; the difference configuration indicates the differences between non-reference parameter configurations and the reference parameter configuration among the multiple sets of parameter configurations; or, the candidate configuration set includes: multiple sets of parameter configurations; the candidate configuration set includes: a set of reference parameter configurations and a conversion relationship configuration, where the conversion relationship configuration indicates the conversion relationship between non-reference parameter configurations and the reference parameter configuration among the multiple sets of parameter configurations.

43. The apparatus according to claim 42, wherein, the conversion relationship indicates at least one of the following: The ratio between the same parameters of the reference parameter configuration and the non-reference parameter configuration; The difference between the same parameters of the reference parameter configuration and the non-reference parameter configuration; The conversion function between the same parameters of the reference parameter configuration and the non-reference parameter configuration.

44. The apparatus according to any one of claims 38 to 43, wherein, the QoS request message includes at least one of the following: A QoS establishment request message; A QoS modification request message.

45. The apparatus according to any one of claims 38 to 44, wherein, the apparatus further includes: A collaborative scheduling module, configured to, in response to determining a collaborative scheduling requirement for a QoS flow, collaboratively schedule at least two of the QoS flows according to the collaborative parameter configuration.

46. The apparatus according to claim 45, wherein, the apparatus further includes: A collaborative scheduling requirement module, configured to, in response to receiving collaborative control information, determine a collaborative scheduling requirement for a QoS flow.

47. The apparatus according to claim 46, wherein, the apparatus further includes: A collaborative control information module, configured to receive a service request message containing the collaborative control information.

48. The apparatus according to claim 47, wherein, the service request message includes at least one of the following: A service establishment request message; A service modification request message.

49. The apparatus according to any one of claims 46 to 48, wherein, The collaborative control information further indicates the QoS flows that need to be collaboratively scheduled.

50. The apparatus according to claim 49, wherein the collaborative control information is determined according to the packet information of multiple QoS flows.

51. The apparatus according to any one of claims 38 to 50, wherein the apparatus further comprises: a recovery module configured to, in response to receiving non-collaborative control information, recover the separate scheduling of at least two of the QoS flows that are collaboratively scheduled.

52. The apparatus according to any one of claims 39 to 51, wherein the apparatus further comprises: a separate scheduling module configured to, in response to a change in the situation of separate scheduling, adjust the parameter configuration used for the separate scheduling of the QoS flow according to the non-collaborative parameter configuration.

53. The apparatus according to claim 52, wherein the apparatus further comprises: a situation change module configured to, in response to receiving a notification of a trigger event, determine that a change has occurred in the situation of separate scheduling.

54. The apparatus according to claim 53, wherein the notification is carried in a service request message.

55. The apparatus according to claim 54, wherein the service request message includes at least one of the following: a service establishment request message; a service modification request message.

56. The apparatus according to any one of claims 53 to 55, wherein the notification further indicates the QoS flows for which a change has occurred in the situation of separate scheduling.

57. The apparatus according to any one of claims 37 to 51, wherein the apparatus further comprises: an original parameter configuration recovery module configured to, in response to receiving a notification of the recovery of the situation of separate scheduling, recover the original parameter configuration for the separate scheduling of the QoS flow.

58. A scheduling apparatus for QoS flows, wherein the apparatus comprises: a sending module configured to send a QoS request message, the QoS request message indicating a candidate configuration set for the QoS flow; the candidate configuration set includes: multiple sets of parameter configurations for the QoS flow.

59. The apparatus according to claim 58, wherein the candidate configuration set includes at least one of the following: a collaborative parameter configuration, wherein the collaborative parameter configuration is: a parameter configuration for the collaborative scheduling of multiple QoS flows; a non-collaborative parameter configuration, wherein the non-collaborative parameter configuration is: a parameter configuration for the separate scheduling of the QoS flow.

60. The apparatus according to claim 59, wherein the non-collaborative parameter configuration includes: multiple sets of parameter configurations for separately scheduling the QoS flow under different situations.

61. The apparatus according to any one of claims 58 to 59, wherein the candidate configuration set includes: multiple sets of parameter configurations; the candidate configuration set includes: a set of reference parameter configurations and a difference configuration; the difference configuration indicates the differences between the non-reference parameter configurations and the reference parameter configuration among the multiple sets of parameter configurations; or the candidate configuration set includes: multiple sets of parameter configurations; the candidate configuration set includes: a set of reference parameter configurations and a conversion relationship configuration, wherein the conversion relationship configuration indicates the conversion relationships between the non-reference parameter configurations and the reference parameter configuration among the multiple sets of parameter configurations.

62. The apparatus according to claim 61, wherein, the conversion relationship between the non - collaborative parameter configuration and the collaborative parameter configuration indicates at least one of the following: the ratio between the same parameters of the reference parameter configuration and the non - reference parameter configuration; the difference between the same parameters of the reference parameter configuration and the non - reference parameter configuration; the conversion function between the same parameters of the reference parameter configuration and the non - reference parameter configuration.

63. The apparatus according to any one of claims 58 to 62, wherein, the QoS request message includes at least one of the following: a QoS establishment request message; a QoS modification request message.

64. The apparatus according to any one of claims 59 to 63, wherein, the sending module is further configured to send collaborative control information in response to a collaborative scheduling requirement for QoS flows, wherein the collaborative control information indicates the collaborative scheduling requirement.

65. The apparatus according to claim 64, wherein, the sending module is further configured to send a service request message including the collaborative control information.

66. The apparatus according to claim 64 or 65, wherein, the sending module is further configured to perform at least one of the following: determine a collaborative scheduling requirement for QoS flows in response to the QoS value of at least one QoS flow among the multiple QoS flows being lower than a QoS threshold; determine a collaborative scheduling requirement for QoS flows in response to the QoS value of any QoS flow among the multiple QoS flows reaching the QoS threshold after the QoS value of at least one QoS flow among the multiple QoS flows changes; determine a collaborative scheduling requirement for QoS flows in response to resource allocation failure for at least one QoS flow among the multiple QoS flows; determine a collaborative scheduling requirement for QoS flows in response to resource allocation failure for each QoS flow among the multiple QoS flows.

67. The apparatus according to any one of claims 64 to 66, wherein, the collaborative control information is also used for the QoS flows that need collaborative scheduling.

68. The apparatus according to any one of claims 64 to 67, wherein, the sending module is further configured to send non - collaborative control information in response to the disappearance of the collaborative scheduling requirement for multiple QoS flows, wherein the non - collaborative control information indicates the restoration of separate scheduling for multiple QoS flows.

69. The apparatus according to any one of claims 59 to 68, wherein, the sending module is configured to send a notification indicating a change in the situation of separate scheduling in response to a change in the situation of separate scheduling.

70. The apparatus according to claim 69, wherein, the notification includes: a notification of a triggering event occurring.

71. The apparatus according to claim 69 or 70, wherein, the notification is carried in a service request message.

72. The apparatus according to claim 71, wherein, the service request message includes at least one of the following: a service establishment request message; a service modification request message.

73. The apparatus according to any one of claims 59 to 72, wherein, The notification also indicates a QoS flow in which the situation requiring separate scheduling has changed.

74. The apparatus according to any one of claims 59 to 73, wherein the sending module is further configured to send a notification indicating the restoration of the situation of separate scheduling.

75. A network device, comprising a processor, a transceiver, a memory, and an executable program stored on the memory and capable of being run by the processor, wherein when the processor runs the executable program, it executes the method provided in any one of claims 1 to 20, or 21 to 37.

76. A computer storage medium storing an executable program; after being executed by a processor, the executable program can implement the method provided in any one of claims 1 to 20, or 21 to 37.

Images